Article ID: 54300
Article Type: Technical Reference
Specifying the Volume to Back Up
To perform block-level backup operations on a snapshot-capable volume, configure the volume as subclient content. The volume that you back up can be a from a local disk or from a hardware snapshot engine that is supported by Commvault.
The Phases of Block-Level Backup Operations
Block-level backup operations have the following phases:
Both of these phases have several sub-phases. For Commvault native engine backup operations, both phases run as a single job. For hardware snapshots, the snapshot copy phase and the backup copy phase run separately as two jobs.
Snapshot Copy Sub-Phases
The QSnap driver monitors the device and creates a bitmap by tracking the changed blocks, while writes are performed on the volume that is being monitored. A block device config file, which holds the volume details and properties, is also created.
Backup Copy Sub-Phases
For Commvault native engine backups, a spool copy is automatically configured. After the backup copy job runs, the snapshots are deleted. For hardware backups, the snapshots are deleted according to the storage policy settings.
File Indexing After Block-Level Backup Job Completion
If you enable the Index files after backup option, files are cataloged offline as a separate job after the block-level backup completes.