> Expert > CommCell Recovery > CommServe Recovery > Disaster Recovery Backups > Configuration of DR Backups > Configuration of the Export Destination

Configuring a Local Drive or Network Share as the Export Destination for Disaster Recovery (DR) Backups

A local or network path is setup as the export destination for Disaster Recovery (DR) backups during CommServe installation. This location can be changed if necessary.

During the export phase of DR Backups, a metadata backup of the SQL databases is copied to the default staging directory located in software_installation_directory\CommserveDR and then exported to the specified export destination.

Before You Begin

  • Make sure the DR export location is not within the area of risk for a production CommServe disaster. The export location must be accessible by the standby CommServe host when recovering the CommServe database.

    Recommended

    • 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.

  • If you plan to use a domain level user account for a network share, make sure the user has permissions granted to create a token object on the CommServe host.

    1. From Local Security Policy, navigate to User Right Assignment.

    2. Right-click Create a Token Object and then select Properties.

    3. Click Add User or Group. Enter the domain user account name and click OK.

  • This user account must also have read/write permissions to the following folder:

    C:\Program Files\CommVault\Log Files\

Procedure

  1. In the CommCell Browser, right-click the CommServe, click Control Panel, and then click DR Backup Settings.

    The DR Backup Settings dialog box appears.

  2. In the Export Settings tab, select one of the following Backup Metadata Destination Folder Type:

    • Use Network Share

    • Use Local Drive

  3. Select the number of backup copies you want to retain in the Number of full Metadata backups to be retained box.

  4. Enter the export path in the Back Up Metadata to this Folder box. Consider the following while specifying the export path:

    • If you are exporting to a network drive, then specify a directory with a valid UNC network path. For example: \\server\share\path.

    • If you are backing up to a local drive, then specify any directory on the local drive.

    • The directory file path selected for this phase should not be located on a FAT drive. A FAT drive is not supported because it limits the file size to 4GB.

    • If there is no library configured, it is recommended to specify a directory in a network location.

  5. Click Change to specify the user account that has administrative permissions for the destination directory.

    If you are using an UNC path, you must use a qscript to change the credentials. For more information on this QScript, see Changing the Username and Password for an UNC Path.

  6. Click OK.

Result

The specified export location is saved.

If your existing export location is currently configured using an administrative share, administrative users will receive the Security Alert: Administrative shares configured alert, once every 24 hours.

Reconfigure the administrative using a dedicated share to turn-off the alert. For more information, see Removing Administrative Shares from Windows Servers.

Loading...