Configure a migrate / store project to find and move objects to secondary storage.
Notes:
| • | If a migrate / store project includes a recurring schedule or is a single run project scheduled to run in the future, it can be disabled or paused. See Disable a Migrate / Store Project or Pause a Migrate / Store Project. |
| • | The StorCycle solution migrates / stores empty directories. |
| • | The StorCycle solution does not migrate / store files that have been previously migrated / stored, even if the file has changed on the source storage location. If you want to migrate / store the file again, you must first move it to another path location. |
| • | When the StorCycle solution migrates / stores or restores files, it also migrates / stores or restores associated directories. While the StorCycle solution ensures that a file does not already exist on the target and does not overwrite the file, it may overwrite existing directories. |
| • | When the Windows version of the StorCycle solution overwrites a directory, it resets the permissions / ACLs based on the permissions / ACLs that are on the directory that it is migrating. |
| • | When the Linux version of the StorCycle solution overwrites a directory, it does not reset the permissions / ACLs (because Linux does not have an "Auto Inherit" flag like Windows). |
| • | The StorCycle solution migrates / stores and restores the access, created, and modified times, and the DACLs (Windows or Linux) or group/owner/mode (Linux). For BlackPearl and S3 targets, these attributes are added to the objects as metadata. |
| • | For Windows system files and CIFS file shares: |
| • | The StorCycle solution does not migrate / store Alternative Data Streams or SACLs. |
| • | Having the target directory for a migrate / store job open in Windows Explorer may cause "The process cannot access the file because it is being used by another process" errors. |
| • | For Linux systems, extended attributes (xattr) are migrated / stored and restored. Since the value of an extended attribute may include binary data, the StorCycle solution encodes the data in base64. |
| • | When the StorCycle solution migrates / stores symbolic links to Spectra or non-Spectra NAS, they are migrated / stored as a text file containing the symbolic link path, even if the target does not support symbolic links. The symbolic link on the source is replaced by a StorCycle link (HTML link or symbolic link) if you selected one of these options. |
| • | When the StorCycle solution migrates / stores symbolic links to a BlackPearl system or S3 storage location, they are migrated / stored as a zero byte object, with the symbolic link path stored in the object metadata. The symbolic link on the source is replaced by a StorCycle link (HTML link or symbolic link) if you selected one of these options. |
| • | When the StorCycle solution migrates / stores symbolic links to an Amazon Glacier storage location, no object is stored in Amazon Glacier, however the symbolic link path is stored by the StorCycle solution. The symbolic link on the source is replaced by a StorCycle link (HTML link or symbolic link) if you selected one of these options. |
Use the instructions below to configure a new migrate / store project.
| 1. | Click Migrate / Store in the taskbar. The Migrate / Store screen displays showing configured recurring and single run migrate / store projects and current and completed migrate / store jobs. |
|
|
| 2. | Click New Migrate / Store Project to start the Migrate / Store wizard. |
Continue with Migrate / Store Wizard—Project Name
