StorCycle Indentify Inactive Primary Tier Data image
Running out of Primary Tier storage? Want to move to a flash-based storage system, but have too much data for the move to be cost effective? Backups taking too long to complete and costing too much? Not sure what data has gone cold, so additional disk or flash is added to primary storage? StorCycle solves these challenges through its ability to identify inactive data based on user-defined policies, and then migrate this data to a protected and less expensive Perpetual Tier of storage.

Scans

StorCycle provides a scan feature enabling a scan of all files in the configured storage location.The scan identifies important information such as file size, file type, and file age (last access, last accessed date, last modified date, and creation date) to help users make informed decisions as to what data they would like to migrate to a perpetual tier of storage. StorCycle is capable of scanning specific directories or the entire file system of any storage location accessible by the StorCycle server . Once a scan is completed, users can view the results to see how much data is in the pre-defined primary storage location and gain insight to the location’s contents such as age and size. The scan results can also be used as part of a migration job to move some or all of the files to the Perpetual Tier of storage.

Scanning Primary Tier Data Image

How Scanning Works

Fast scan speed is critical for a successful storage management solution. StorCycle has been developed from the ground up to maximize scan performance. There are two limitations that must be considered when developing a successful file scanner for a data management solution – the rate at which information can be collected from the primary storage system about the files being scanned, and the rate at which that collected data can be recorded in the database of the storage management solution.

StorCycle uses server memory to the greatest extent possible to best address these limitations. Scan data is collected in memory and then written to the StorCycle database in batches to optimize write performance. StorCycle also uses hundreds of parallel programming threads to collect scan data. With these optimizations, organizations not using job throttling (see below) can expect to see a scan rate on the order of thousands of files per second. This performance will vary depending on the storage, server and network environment. Thousands of files per second equates to millions or tens of millions of files per hour and tens of millions or hundreds of millions of files per day.

Job Throttling

To ensure that Spectra StorCycle does not overuse the resources of the source storage system, job throttling is available for all storage location sources. When configuring a storage location in StorCycle, the default setting will be “Do Not Limit Transfer during Peak Hours.” To enable throttling, the user can change this setting to “Limit Transfer during Peak Hours,” as shown in the image to the right. This setting can be changed when creating the new storage location or at a later time by editing the storage location.

When the “Limit Transfer” value is selected to activate throttling, the administrator can set “Peak Hours” and “Off-peak Hours” behavior as shown in the image below. Peak Hours is defined by the day of week and time of day. For example, if the administrator wanted to set Peak hours to Monday-Friday, 8a.m. to 5p.m., they would use the settings as shown to the right.

Peak Hours and Off-peak Hours include the following settings:

  • Max transfer (archive/restore) bandwidth, in MB/s
  • Max scan rate, in scan objects per second

Administrators can set different maximum transfer rate and scan rate values to see which settings are appropriate for their environment. Recommended default values are provided.

Idenify inactive data image

X