Configuration of Disaster Recovery (DR) Backups


On this page

Disaster Recovery (DR) Backups are executed using the following phases:

  • Export

    During the export phase, the software copies a metadata backup of the CommServe database to the default staging directory that is in software_installation_directory\CommserveDR.

    Note: The staging directory should not be on a mounted path or should not use a symbolic link. In such cases, contact your software provider to change the default staging directory.

    You can specify a local path or a network path as a destination location to export the metadata.

    You can set up the following additional export destinations:

    • Commvault Cloud Services portal

    • Cloud storage library


    • You must store the Disaster Recovery (DR) backup in a dedicated network location that is accessible from both the production host and the new server host that is used for recovery.

    • Do not use a local disk or local clustered disk because it is not safe and recommended.

    • Use a UNC path to access the network location. Make sure that this dedicated location is not used for any other CommServe task.

    • Do not use administrative shares as an export location. For example, \\MyServer\E$\.

    • For a network location that is on a Windows mount path, the software enables ransomware protection by default. For a network location that is on a Linux mount path, you must enable ransomware protection manually.

    • Do not use the Commvault installation directory as a backup location for DR backups to local disk. By default, the Commvault software enables ransomware protection for DR backup folders on Windows.

  • Backup

    During the backup phase, the metadata available in the staging directory in the CommServe, along with the configured log files, are backed up using the DR storage policy as follows:

    • A default DR storage policy (CommServeDR) is automatically created when the first library is configured in the CommCell.

      By default, the primary copy of the DR storage policy is created as a WORM copy to prevents accidental deletion of data that is not qualified for aging.

    • A secondary copy for the DR backup data is automatically created when you configure the first tape library. An Auxiliary Copy schedule which runs every 15 minutes is automatically created. If necessary, you can change the frequency of this Auxiliary Copy operation.

FAQ: Are DR backups protected against Ransomware attacks?