Redstor's Archiving service saves disk space by removing redundant, obsolete and trivial (ROT) data. Archiving is managed from the ESE Agent interface.
How it works
Rules are set (e.g. older than x years, not accessed in x months) by which files are selected to be archived. Each eligible file is stubbed, i.e. replaced with a much smaller (“sparse”) file. The originals files are stored on Redstor’s Storage Platform but are immediately accessible from the user’s computer via the sparse files. When a sparse file is accessed, its relevant data is immediately rehydrated onto the user’s computer. Files can also be selected for bulk rehydration.
Please note: Archiving only works on 64-bit operating systems (Windows, Ubuntu, RHEL and CentOS). See our System Requirements and Compatibility Matrix for more details.
- Archiving saves disk usage costs by moving data from high-cost primary storage (local) to the lower-cost Storage Platform - helps customers deal with growing volumes of data without purchasing more primary storage.
- Archived data is always available on demand on the originating computer.
- Data redundancy is ensured before archiving occurs as multiple copies of files are held in separate locations.
See Archiving in action here:
To activate and configure Archiving immediately, see Article 1175.
The Archiving process
- Compatibility and version checks performed.
- Account is checked for an active Archiving licence.
- ESE confirms that the data has been backed up.
- ESE confirms that the mirroring of data has completed so that two copies of the data exist in the lower tier storage.
- The rehydration service is installed and checked. If it already exists, it is updated to the appropriate version and its status verified before archiving can proceed.
- If the above checks are successful, all eligible files are stubbed, based on the archival selection.
- Files that no longer fulfil the archival selection criteria are rehydrated.
- When stubs are accessed, only the relevant data is rehydrated. This results in a stub being partially rehydrated. Also, files removed from the backup selection are automatically rehydrated at the next cycle.
- Archiving is triggered after backups to ensure that archived data is consistent.
- Files required by critical applications and frequently modified will not be stubbed. For example, SQL Server and Microsoft Exchange database files.
- Logs are generated during the process and all actions taken can be reviewed in the Logs tab.
A file will be stubbed if it:
- is in the archive selection
- is in the most recent backup on the SS
- is in the most recent backup on the MS
- is not in the system state selection (or selected by any VSS writer)
- has not been recently modified (based on not accessed in x days)
- has not been recently accessed (based on not accessed in x days)
- is greater or equal to 1KB
- is less than or equal to 64GB
- is not open
A file will be rehydrated if it:
- has recently been modified (based on not accessed in x days)
- is not in the archive selection
- is not in the most recent backup on the SS
- is not in the most recent backup on the MS
- is not a stub from this account
For more technical information, see our Archiving Q&A.