Source Storage Locations
While storage locations are essentially UNC / Network paths, StorCycle Sources can be configured for a path down to a particular folder.
- Rather than configuring a top-level network share as a Source with simple path, multiple StorCycle sources can be configured from the same share
StorCycle jobs are architected in a way where, for the most part, only a single job can be active within the same directory path structure. If an organization must have multiple projects running from a common share, it will be important to configure either the Source Locations or Project Working Directory in an intentional way to avoid path collisions.
Source Locations are where data is moved out of and where data is restored to.
Essentially, Source locations are paths to network shares and buckets.
| Source | Use With |
| NAS | CIFS or NFS Shares |
| Spectra NAS | Spectra BlackPearl NAS or Spectra Verde |
| S3* | AWS, Google Cloud Platform, Generic S3 devices or platforms |
*S3 Sources can be scanned and migrated to Spectra BlackPearl Nearline systems only.
After, data which migrated from S3 sources can only be restored from BlackPearl to a different NAS Source location: S3 → (archive) → BlackPearl→ (restore) → NAS
Support for S3 to S3 Migrations and Restore to S3 Sources is a planned roadmap item.
|
1. Name
|
 |
|
2. Device
|
 |
|
3. Details
|
 |
| 3. Details - Peak Hours |
 |
|
Configuration Steps 1. Name
2. Device
3. Details
|
 |
¶ CIFS & NFS Source Locations: Shares and Paths
|
When CIFS/NFS Storage locations are configured in StorCycle, a full UNC path can be used. It is important to understand shares and paths, and how StorCycle utilizes these for Storage Locations and Projects. Single Source for Multiple Projects: Depending on the organizational workflow, it may be advantageous to either configure a single StorCycle storage location which is used for all migration projects or configure specific StorCycle storage locations for each migrate project which will eventually run. For Example, if a Source Location is configured with //192.0.0.1/NetworkShare, future Migrate projects can be configured at any sub-level below ‘NetworkShare’. A project could be configured for the directories ‘ProjectA’, ‘ProjectB’, and ‘ProjectC’. Single Share for Multiple Sources Alternatively, Source locations can be configured for each Project directory. In this case, a Source will exist for ‘ProjectA’, ‘ProjectB’ and ‘ProjectC’, and individual Migrate projects will be configured for each.
Overlapping Working Directories Note, that StorCycle will not be able to run concurrent jobs to and from overlapping directories. If a Project was configured to run from the ‘ProjectC’ directory and another project was configured to run from ‘ProjectC/Data’ directory, StorCycle will not be able to run the projects at the same time - whether a migrate, scan or restore. |
 |
¶ S3 Source Locations
|
StorCycle supports S3 source locations, including AWS, Google Cloud Platform, and other standard S3 implementations. S3 Source locations are able to be scanned and data migrated to Spectra BlackPearl Nearline systems ONLY. After migration, this S3 data can then only be restored to CIFS/NFS Source locations. This limitation is temporary and future versions of StorCycle will provide full support for S3 migration to any Target, and restore to any S3 Source. |