A Migrate / Store project moves scanned data from primary storage to secondary storage. When configuring a new Migrate / Store project, if a scan was previously done, StorCycle graphically displays all scanned data within the selected storage location by file size and age. This allows a user to easily select to move all scanned files or only a portion based on particular file sizes or file age from primary storage to a lower-cost storage medium.
File age is the most important property for determining which files should be migrated. The older the file, the less likely that it is to be accessed. File age is typically determined by the date the file was last accessed, but StorCycle also optionally allows file age to be based on the last modified date or creation date of the file. To change the basis for file age, see Configure Global Settings.
File size is also important for determining which files to migrate:
| • | Migration of smaller files from primary storage does not have as big of an impact on freeing up space and improving performance when compared to moving large files. |
| • | Small files transfer to secondary storage at a slower rate (MB/s) than large files. |
| • | Small files have a larger impact on the count of files/objects in object storage. Object storage systems like the Spectra BlackPearl system typically have an object count maximum. Packing, described in Configuring Storage, can address this issue. |
When migrating data, users have the choice of whether to scan before migrating.
| • | Scan before Migrate / Store — Perform a new scan, and then migrate files that meet the specified criteria for age and size. Use this option if a prior scan result is not available, if it has been a long time since the latest scan, or if there has been a large content change in the storage location. |
| • | Use Last Scan — Migrate files that meet the specified criteria for age and size based on the most recent scan result. This is the most efficient choice. |
Continue with Create a Migrate / Store Project