You can initiate a Disaster Recovery (DR) backup job on-demand.
A daily schedule for a full DR backup is automatically created when the CommServe is installed. Based on the security requirements of the CommServe and the recovery point objectives of the disaster recovery plan in your environment, scheduling multiple DR backup jobs in a day is recommended.
A disaster recovery plan should consist of at least one full backup performed every day and multiple differential DR backups performed several times during the day. Differential DR backups will back up only that data that has changed since the last full backup. Hence, this backup is smaller in size and takes less time to complete.
DR backup jobs have the highest priority in the CommCell. If a DR backup job cannot be completed, the Job Manager will retry the job, up to a total of 5-hours at 30-minute intervals for a maximum of 10 times.
Note
-
For minimum impact to production jobs, we recommend performing DR backups when no other CommCell jobs are running.
-
By default, the HistoryDB, WFEngine, and CVCloud databases are included in the DR backup job - if the Workflow Engine and Metrics Reporting Server are installed on the CommServe host. (We highly recommend that you include these databases in the backup.) For additional information on the Commvault databases, see FAQ -What are the databases critical for CommServe disaster recovery.
Before You Begin
-
Login to CommCell Console as user with CommCell level Administrative Management capability.
-
Make sure CommCell services are running on the CommServe host.
Procedure
-
From the CommCell Browser, right-click the CommServe point to All Tasks and then click Disaster Recovery Backup.
The Disaster Recovery Backup Options dialog box appears.
-
Select one of the following backup types:
-
Full - Select this option to back up the entire metadata. By default the Full backup type option is selected.
-
Differential - Select this option to back up only that data that has changed since the last full backup. This backup is smaller in size and takes less time to complete. Use differential backup type if there are limitations in disk space or network bandwidth. However, you can use this backup to restore the CommServe databases, only when the last full backup is accessible.
Note
A Differential backup will be automatically converted to a Full backup in the following cases:
-
If a new database is added.
-
When the export destination for DR Backups is changed. For more information on this setting, see Configuring the Export Destination for Disaster Recovery (DR) Backups.
-
If the nMinDBLogUsage additional setting is added, and if one of the log files reaches the percentage set in this setting compared to the total size allocated for the log in SQL Server. For more information on this setting, see Setting up Log Truncation With Disaster Recovery (DR) Backups.
-
-
-
If sufficient space is not available on the CommServe host, to compress the database backup file (*.dmp), select the Enable database(s) backup compression check box.
Note
Do not select this option for Microsoft SQL Server Express Editions which is installed with the Commvault Express Editions. For example, the Edge Express solution.
-
Optional: Select the databases that should be included in the backup from the Select databases to backup list.
By default, additional databases installed on the CommServe host, (for example, WFEngine, CVCloud etc.) are included in the backup. If necessary, the databases can be excluded from the backup by clearing the option. However, we recommend that you include these databases in the backup.
-
Optional: On the Client Selection tab, select the Client(s) from which the log files should be included.
You can also select the clients containing the MediaAgents to back up the log files from MediaAgents. This is useful for troubleshooting purposes, especially in Deduplication configurations.
-
Click the Job Initiation tab, select Schedule and then click the Configure button.
-
In the Schedule Details dialog box, type a name in the Schedule Name box.
-
Select the appropriate scheduling options.
-
Type the Start Time to start the schedule.
-
Click OK.
-
-
Click OK.
Result
For each DR backup, SET_XXX directory is created under the configured export location. (xxx is a sequential number for the directory.) The highest number is associated with the latest DR backup. Each folder contains the following files:
File |
Description |
---|---|
commserv_FULL.dmp |
This full dump file represents a full backup of the CommServe database. |
commserv_DIFF_xxx.dmp |
This dump file represents a differential backup of the CommServe database. |
Mongo_GlobalConfigManager_xxx.7z |
This dump file represents a full backup of GlobalConfigManager database in MongoDB. |
Other Files |
Depends on the software module installed/configured, such as, workflow database files. |
Note
-
Full backup of the Mongo databases is also taken during differential DR backup, as a result SET folder will have multiple mongoDB database dumps (.7z files), with time stamp appended.
When the Mongo database needs to be restored, then the database dump with latest time stamp must be selected for restoration.
-
The DR backup operation runs a database consistency check on all the databases included in the DR backup. If the consistency check fails on any database, the DR backup job fails and all job activities on the CommServe server are disabled.