StorCycle utilizes a YAML configuration file for some settings which are not accessible in the user interface.
Spectra Logic does not recommend modifying any setting in the YAML file without advisement from Spectra Logic Support or Professional Services.
auth:
timeout: 8h0m0s
currency: USD
db:
driver: mongo
name: ssc
port: 27017
interval: 300
license:
path: C:\ProgramData\Spectra Logic Corporation\Spectra StorCycle\config\license.lic
log:
path: C:\ProgramData\Spectra Logic Corporation\Spectra StorCycle\log
queue:
driver: memory
scanfileagecriterion: 0
server:
address: ""
cleanhtmllinks: false
globalhashtype: b2b256
name: ""
port: 443
secure: true
swagger:
path: C:\Program Files\Spectra Logic Corporation\Spectra StorCycle\swagger
ui:
path: C:\Program Files\Spectra Logic Corporation\Spectra StorCycle\app
work:
directory: C:\ProgramData\Spectra Logic Corporation\Spectra StorCycle\work
path: C:\ProgramData\Spectra Logic Corporation\Spectra StorCycle\config\work.json
Spectra Logic does not recommend making any modification to the YAML file without advisement and approval from Spectra Logic Engineering and Support. Below is a list of optional edit settings. Note, if you would like to make use of any of these settings, please contact Spectra Support or your Spectra Sales Representative for review.
The variables listed below are not the actual terms used in the YAML. Do not modify the YAML file with any of the options below as they are provided for informational purposes only.
| Setting | What it does |
| Number of Concurrent Jobs | StorCycle runs 10 jobs (migrate, scan, restore, db backup, etc) at a time. This can be increased or decreased. An increase beyond ten concurrent jobs typically requires a drastic upgrade of the StorCycle server. |
| Number of Go Routines | Controls the number of go routines for each job. |
| Failure to Apply Metadata as Warning / Error |
Option to either consider a StorCycle ‘failure to apply metadata’ as a Warning or an Error. Warning = Files will archive without metadata and a warning will be generated Error = File will not archive because metadata cannot apply |
| Disable Post Archive Action Delay | StorCycle requires two successful database backups before source data is removed or replaced. This can be overridden and StorCycle will remove/replace source files during the standard migrate operation. |
| Wait for BlackPearl Data to persist |
When sending data to a Spectra BlackPearl Nearline system, data will first land on cache before written to a tape library. This option will wait for data to fully persist to tape before considering a job complete. When disabled, StorCycle will consider jobs complete when landing data to cache
|
| Delay after BlackPearl Put | This option can set a delay (in seconds) for how long StorCycle should wait before performing a removal/replacement of source file after a BlackPearl PUT job. This option should be considered in addition to or in replacement of any modification to 'Wait for BlackPearl data to persist". |
| Minimum Chunk Size for S3 Transfers |
S3 data transfers will happen in bulk movements, where jobs are divided into smaller parts or chunks. Depending on the S3 target in use, chunk sizing may impact performance and functionality. Essentially, S3 transfers will need to define a chunk size and a total number of chunks to transfer at a time. By tuning the chunk size, performance can be modified. The minimum chunk size for AWS S3 is 5242880 bytes. |
| Advanced Search |
Advanced Search can be enabled which will change the behavior of the search query fields. Default search will always try to match the first three letters with the first three letters of a file name. Advanced search will allow you to search within path separators for files and directories. |