works as designed From the OneFS 8.2 Release Notes: SmartLink files and inline access In previous releases, the connection between OneFS file system storage and cloud storage was known as a stub file. Now, this connection is called a SmartLink file. SmartLink files permit inline access to the archived data.Inline access enables users connecting to a cluster through supported protocols to access cloud data directly through a SmartLink file, rather than requiring a connection from a client computer. hth -- Peter    
We are using CloudPools with Azure as an archive. We use SyncIQ to copy a directory structure to a new location in another Access Zone. We break the SyncIQ relationship to make the target writable (essential). There is a FilePool policy that migrates the data at that target to Azure. Lastly we TreeDelete the original source files. All that works fine. My problem is in retrieving data. As it is an archive we do not want to use 'isi cloud recall' as that brings the actual file data back, replacing the SmartLink. I absolutely need the data to stay safe in Azure, where it has redundancy that we cannot provide on-site. There are documented 'CloudPools expected behaviors' that state: 'You can view and modify cloud data by accessing SmartLink files through supported protocols (NFS, SMB, Swift, and HDFS). If you attempt to access a SmartLink file directly on the cluster, through a command running on the cluster, or through an unsupported protocol, an I/O error is generated. Local access for SmartLink files is blocked for these commands: tar, gzip, scp, AVscan, and Job Engine jobs. Cloning of a SmartLink file is also prevented and will return an EINVAL error.' I have tested just using 'cp' to copy a SmartLinked file back to another location on the local Isilon. It doesn't give an I/O error as it suggests above. It retrieves the data content and caches it with the SmartLink, much as I would expect if I had used one of the supported 'redirected' protocols listed (SMB, NFS, HDFS and Swift). It is of course slow. I am reluctant to create a share and use an external server just to get a copy of the data back if a user requests it. That would mean creating a share on the archive access zone, and a target share where I need to put the data, and using an external server to pull the data back from Azure, and then store it back into the Isilon. That clearly is supported, but if I can use 'cp' locally that would avoid the data going 3 times across the external interfaces. So I guess my question is, whether what I observed was just luck, or is there any redirector for 'cp' or any other local commands? William
CloudPools 2.0 - using 'cp' locally seems to work....