Overview - OnePass for Celerra
Note: If you are transitioning from the Celerra File Archiver Agent, see Transitioning From Traditional Archiver to OnePass.
The OnePass feature is a comprehensive solution incorporating the traditional backup and archiving processes in a single operation. It enables you to move data to a secondary storage and use it to function as both backup and archive copy.
Stubs are retained on the primary storage which point to the data moved as part of backup. The archived data will be available for quick and easy retrieval.
The proxy computer that initiates recall operations uses Common Internet File System (CIFS) connection to access the data residing on the Celerra file server. For more information on backup and archive operations for CIFS shares, see Data Protection for NFS Shares, CIFS Shares, and UNC Paths.
This integrated agent is able to selectively age off items based on data and stubs that are deleted on the primary storage. This allows you to reclaim space in your secondary storage.
OnePass for Celerra file server offers the following key features:
OnePass enables you to easily manage the backed up data in your environment, by providing pre-defined archiving rules.
In the event of a serious system failure, such as the breakdown of hardware, software, or operating systems, the solution provides a point-in-time recovery of files at any given time.
You can now specify the time period for which you want to retain the deleted files in the backup cycle. This enables you to restore the deleted files from the latest backup cycle. This will be useful for the OnePass clients where you perform frequent incremental backups.
Archived data is pruned and secondary storage space is reclaimed based on the stub retention setting and the storage policy cycle - based retention criteria.
Below is a basic chart comparing the OnePass with the Celerra Archiver and NAS iDataAgent:
OnePass for Celerra
|Space saving on File Server|
|Secondary Storage Space Reclamation using Synthetic Full Backups|
What Is Archived
The subclient filter does not filter the MediaAgent disk library mount paths from the subclient content. Therefore, you must specify the volumes that contain disk library mount paths for subclient filter. Otherwise, the entire disk library will be archived.
The following file types/objects are automatically filtered out of archive operations by the system, and cannot be archived.
- Install folder
- Job Results folder
- Index cache folder
- Log files folder
- Windows system32 folder
- Alias mount points to drive letter volumes*
- Unix data residing on a Windows NFS share
- Files with attributes of encrypted or sparse
- Files with attributes of hidden and system
Files Excluded from Archiving (Stubbing)
- Server Message Block (SMB) 1.0 protocol
- SMB 2.0 protocol
- SMB 3.0 protocol
|Archiving is a process of periodically moving unused or infrequently used data on a host computer to secondary storage, thereby reducing the size of data on the primary storage.|
|Stubs are placeholders of the original data after it has been migrated to the secondary storage. Stubs replace the archived files in the location selected by the user during the archive. However, stubs will only be created if the subclient properties were configured to create them during archive.|
|The archived data can be recovered in any of the following three methods:
|If the subclient is configured to create stubs, you can perform a recall operation from a Windows workstation for recovering the stubs. A recall is any action that causes an open and read to be executed on the stub, which automatically initiates a recovery operation.|
|Multiple stub recoveries are submitted to the Job Controller as one job called a Persistent Recovery job. The job will wait for approximately 5 seconds in order to allow other stub recovery requests being submitted on the same client to be batched into the same job.|