Storage Locations are network shares or buckets which will either be conifgured as Source locations, where data is migrated out of, or Target locations, where data is archived to.
To monitor the cost savings from migrating from the Primary Storage Tier to the Perpetual Storage Tier, for each storage location enter a department (see Departments) and a cost per terabyte (TiB). StorCycle will then monitor the amount of data moved between storage locations and calculate an associated cost savings.
The use of local storage (for example \\localhost\c$) for source or target storage locations is not supported.
Source Location Best Practices
StorCycle Storage Locations that are sources of data (data to be migrated) can be configured to be at the top-level directory of a storage server share or at a sub-directory lower down in the directory structure path.
Consider the following when deciding where to place the StorCycle source Storage Locations:
When versioning is enabled, multiple versions of a file from the source storage location are kept on the target storage location after multiple migrate / store jobs. Each file name has a code appended to the file name that indicates the date and time that the file was migrated / stored in the format yyyymmddhhmmss using a 24-hour clock. Versioning can be configured on a per source storage location basis to create versions for all files in the source or only files that changed, and to keep a set number of versions of a file, deleting the oldest when necessary.
See Versioning for more details.
Notes:
To add storage location security to a new or existing source storage location, an administrator can assign an AD / LDAP group to the source storage location which restricts access to scan, migrate / store, and restore jobs, as well as file listings associated with the source, to members of the designated group and administrators. If AD / LDAP is not configured, access is restricted to administrators. The StorCycle solution queries the AD / LDAP server if a user attempts to configure a new restore job to or scan or migrate / store job from the controlled source. For recurring jobs (scans and migrate / stores), the StorCycle solution queries the domain server each time it attempts to initiate the job. The StorCycle solution also queries the server when a user tries to access information regarding a job to / from a controlled source, such as the Catalog File Listings. The StorCycle solution does not query the AD / LDAP server when assigning groups to source locations, so groups can be assigned without the domain server configured and non-existent groups can be assigned.
Configuring storage location security is a step in the configuration process for all types of source storage location.
See AD/LDAP Groups for more details
Notes:
Job Ownership - Within the Job Details page for scans, migrate / stores, and restores, the StorCycle solution lists the ‘Created By’ user. This is the user whose permissions are assessed during recurring jobs. If a job is edited, a new field is present in the Job Details called ‘Updated By’. If an Updated By user exists, the StorCycle solution uses this user’s group memberships to assess permissions.
Target Location Best Practices
StorCycle Storage Locations that are targets for migrated data can be configured to be at the top-level directory of a storage server share, at a sub-directory lower down in the directory structure path, or to buckets depending on the storage type.
Consider the following when deciding the StorCycle target Storage Locations to create:
The StorCycle solution supports single key encryption for all storage targets. For more information, please see Encryption.
Note: Using encryption may have a performance impact on the StorCycle server's CPU.
A storage location retention policy allows you to select the desired number of days to retain files on a storage location before the StorCycle solution automatically deletes the files for compliance or capacity recovery.
Notes:
When configuring a Spectra NAS storage location, you can select to Enable Snapshot to create a snapshot after a migrate / store job, a retention policy delete, or a delete files job using this target location.
Notes:
CAUTION: Restoring to an earlier BlackPearl snapshot on the volume leads to loss of data (and access) from the StorCycle solution. Migrate /store operations following the restore point will no longer be restore-able from the StorCycle solution.