What events are triggered during a Deduplication Database (DDB) backup

1.	What events are triggered during a Deduplication Database (DDB) backup process?
Answer» The following events occur when the DDB backup job starts: For a few seconds, all communication with the active DDB is halted. To ensure that the DDB is in a dormant stage, the information in memory is committed to memory. The DDB process uses VSS (Windows) or LVM (Linux) snapshots to make a snapshot of the volume. The file systems Extended 3 File System (ext3) and VERITAS Volume Manager (VxVM) are also supported on the Linux platform. All communication with the DDB is resumed when the snapshot is created, and the DDB is automatically backed up from that snapshot. If a VSS (Windows) or LVM (Linux) snapshot fails, the DDB backup falls back on a live volume backup. The snapshot is erased after a successful DDB backup. The Job Controller displays the DDB Backup job in a running condition at this point. If the DDB MediaAgent restarts during a DDB backup job, the job is marked as Pending. The DDB backup job resumes from the beginning after the restart. The DDB backup JOBS for the AUXILIARY copy OPERATION are disabled by default, and these jobs appear as UNAVAILABLE when viewed from the primary copy. Allowing DDB Backup Tasks from Being Copied to Secondary Copy describes how to enable or prohibit DDB backup jobs from being copied to secondary copy during the auxiliary copy procedure.

What events are triggered during a Deduplication Database (DDB) backup process?

Answer»

The following events occur when the DDB backup job starts:

For a few seconds, all communication with the active DDB is halted. To ensure that the DDB is in a dormant stage, the information in memory is committed to memory.
The DDB process uses VSS (Windows) or LVM (Linux) snapshots to make a snapshot of the volume.
The file systems Extended 3 File System (ext3) and VERITAS Volume Manager (VxVM) are also supported on the Linux platform.
All communication with the DDB is resumed when the snapshot is created, and the DDB is automatically backed up from that snapshot.
If a VSS (Windows) or LVM (Linux) snapshot fails, the DDB backup falls back on a live volume backup.
The snapshot is erased after a successful DDB backup. The Job Controller displays the DDB Backup job in a running condition at this point.
If the DDB MediaAgent restarts during a DDB backup job, the job is marked as Pending. The DDB backup job resumes from the beginning after the restart.
The DDB backup JOBS for the AUXILIARY copy OPERATION are disabled by default, and these jobs appear as UNAVAILABLE when viewed from the primary copy.
Allowing DDB Backup Tasks from Being Copied to Secondary Copy describes how to enable or prohibit DDB backup jobs from being copied to secondary copy during the auxiliary copy procedure.