The Set Targets screen of the Migrate / Store wizard allows you to configure the target storage location for the Migrate / Store project and specify the replacement option on the source.
|
|
|
Figure 78 The Set Targets screen of the Migrate / Store wizard. |
| 1. | From the Target(s) drop-down menu, select up to three previously configured storage locations. See Configure Storage for instructions for configuring a storage location. |
|
CAUTION |
Do not configure multiple source storage locations to migrate / store to the same NAS target storage location, such that the directory and file names could conflict on the target. For example, if Storage Locations A and B both contain a top-level directory dir1 which contains a file named file1.txt, and the file from both locations are migrated to the same NAS target, the migrate / store will fail. |
|
IMPORTANT |
Spectra Logic recommends making two copies of migrated data in two geographically-separated locations. This can be done by selecting two targets in the StorCycle Migrate / Store wizard or by selecting a BlackPearl system with data policy set to migrate data to any combination of tape, disk, and cloud. |
|
IMPORTANT |
To replace migrated / stored files with symbolic links, the migrate / store project must have only one NAS target. Additional BlackPearl or S3 targets are optional. |
Notes:
| • | If the source is an S3 storage location, the target must be a BlackPearl storage location that does not have packing enabled. |
| • | You cannot mix encrypted targets and non-encyrpted targets in a single migrate / store project. |
| 2. | Select the Replacement Option for the files after they are copied to secondary storage. |
|
IMPORTANT |
If the NAS target storage location has a retention policy set and you select Remove Source File: create Symbolic link or Remove Source File: create HTML link then the links are removed from the source when the files are removed from the NAS target. |
| Note: | When a migrate / store project is configured to delete the source file, or replace the source file with an HTML or symbolic link, the StorCycle solution checks the file timestamp and size to ensure that the file has not changed between the time it was migrated / stored and when it is deleted or replaced. If the file changed during this time, then the file is not deleted or replaced from the source storage, and a note is added to the job logs. |
| • | If the source is an S3 storage location, you can not replace the files with HTML or Symbolic links. |
| • | If the targets are encrypted storage locations, you can not replace the files with Symbolic links. |
| • | Keep Source File —The original copy of the object is kept in primary storage. |
| • | Remove Source File: no links—The original copy of the object is removed from primary storage. The directory structure is left in place. The empty directories can be deleted. Upon restore, any missing directories will be recreated. |
| • | Remove Source File: create Symbolic link—The original copy of the object is replaced with a symbolic link which transparently opens the file from secondary storage. |
| Notes: |
| • | To replace migrated / stored files with symbolic links, the migrate / store project must have only one NAS target. Additional BlackPearl or S3 targets are optional. |
| • | If the source is an S3 storage location, you can not replace the files with Symbolic links. |
| • | If the targets is an encrypted storage location, you can not replace the files with Symbolic links. |
| • | Remove Source File: create HTML link—The original copy of the object is replaced with an HTML link with instructions for restoring the file from secondary storage. |
| Notes: |
| • | If the network does not support reverse DNS lookups, then the IP address of the storage location is used in the HTML link created during a Migrate / Store job. |
| • | If you entered a Hostname Override (see Configure Global Settings), the URL entered is used in the HTML link created during a Migrate / Store job. |
| • | If the source is an S3 storage location, you can not replace the files with HTML links. |
| • | Remove Source Files and any Empty Directories—The original copy of the object is removed from primary storage. Any empty directories are deleted. Upon restore, any missing directories will be recreated. |
| • | Remove Source Files: replace with single HTML link—An HTML link to restore the entire project is placed in the project's root directory and all files are removed. |
| Notes: |
| • | If the network does not support reverse DNS lookups, then the IP address of the storage location is used in the HTML link created during a Migrate / Store job. |
| • | If you entered a Hostname Override (see Configure Global Settings), the URL entered is used in the HTML link created during a Migrate / Store job. |
| • | If the source is an S3 storage location, you can not replace the files with HTML links. |
| 3. | If desired, under Tags, click the plus (+) sign to add a new line for entering tags to apply to this task for searching purposes. Search by Tag allows you to search for any sub string within the tag. See Search by Tag for more information. |
| 4. | Click Next to continue. |
Continue with Migrate / Store Wizard—Schedule
