The Commvault file archiving solution enables you to move data to a secondary storage and use it to function as an archive copy. You can move data to disk, tape, or cloud libraries. The archived data will be available for quick and easy retrieval.
You can recall the archived data by using stubs or placeholders in the original locations. Stubs are retained on the primary storage which point to the data moved as part of the archive operation.
You can use the archiving reports to view vital information, such as the compression rate and the space saved by archiving.
Key Features
-
Archiving enables you to easily manage the backup data in your environment, by providing pre-defined archiving rules.
-
Files are indexed when you perform archive operations, so you can search and retrieve archived files easily.
Support
You can archive data on the following file system clients:
-
Macintosh
-
Windows
-
UNIX
You can archive data on the following network file system clients:
-
NAS
-
NetApp
-
EMC Celerra
-
Hitachi NAS (BlueArc), EMC Unity, and Isilon
-
-
Network Share
Terminology
Archiving |
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. |
Stub |
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. |
Data Recovery |
The archived data can be recovered in any of the following three methods:
|
Stub Recovery |
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. |
Persistent Recovery |
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. |