Action limitations for volume types
Volume types have different action limitations.
Action type | Source limitations | Other restrictions |
---|---|---|
Copy from |
|
Copy from SharePoint Online supports copy to CIFS, FileNet, and SharePoint 2007/2010/2013/2016/Online target sets. Copy from Box supports copying files to CIFS, NFS, FileNet, and Box target sets. Copy from Connections supports copying files to CIFS targets. Copy from OneDrive for Business supports copying files to CIFS and NFS shares. |
Copy to | Primary Volume
|
For copy policies that target SharePoint volumes, the destination can write documents into an existing custom library. Two known SharePoint library configuration requirements are as follows.
For copy policies that target FileNet volumes, creating directories or re-creating the directory structure is not supported. |
Copy to (Box volume) |
|
Box volumes can be added only from IBM StoredIQ Administrator, not from IBM StoredIQ Data Server. Preserve owners is only supported for SharePoint and CIFS source volumes. Map permissions is only supported for CIFS source volumes. |
Copy to (OneDrive volume) |
|
OneDrive volume can be added only from IBM StoredIQ Administrator, not from IBM StoredIQ Data Server. For copy policies that target OneDrive volumes, the destination folder needs to be set to the name of an existing drive at least. It cannot be left blank. |
Copy to (retention) |
|
|
Copy to SharePoint Online |
|
The Copy to SharePoint Online function does not include the ability to update some file system metadata or custom metadata. For example, the target file's Create Time and Modified Time reflect the time of the copy, not the source file's Create Time and Modified Time. |
Delete |
|
The Delete action removes data objects (not directories) from the source volume and is limited to system level objects. If a responsive object targeted for deletion is within a container object (such as a .zip or .tar file), the container level object is the object that is deleted. Thus, any other objects within the container file are also deleted. A Delete action on a responsive object attached to a CIFS based .msg, .eml, or .pst file also results in the container object being deleted including any other objects attached to or contained within the container object. The respective logging information reflects the container level object, indicating success or failure or the action. For desktop volumes, certain files must not be deleted. For more information, see Special considerations for desktop delete actions. |
Discovery export from |
|
|
Discovery export to |
|
Considered discovery export volumes (category) not harvested |
Move from |
|
Move from Box supports copying files to CIFS, NFS, FileNet, and Box target sets. |
Modify security |
|
|
Move to |
|
For move policies that target FileNet volumes, creating directories or re-creating the directory structure is not supported. |