Recovering the CommServe Database Using the Command Line Interface

The CommServe Recovery Assistant tool can be run using the command line interface to recover the CommServe databases from a disaster recovery (DR) backup.

Before You Begin

• Review CommServe Recovery Using DR Backups.

• Verify that the destination CommServe host installed with the same (or higher) service pack and hotfix pack as the database that is available in the DR backup that you plan to restore.

  Note

  If the service pack and hotfix pack are not the same (or higher), services may not restart after the restore.

• Verify that the SQL Server on the destination CommServe host is on the same or higher version and CU pack as the database that is available in the DR backup that you plan to restore.

• Make sure that you have the latest version of the DR backup (SET_XXX folder) in the destination CommServe host.

  • If you have the DR backup files in the network location, copy the files to the local disk on the CommServe host.

  • If the latest copy of the DR backup metadata does not exist in the export location, you must retrieve the metadata from the backup media. For more information on retrieving DR backups from media, See Retrieving Disaster Recovery (DR) Backups from Media.

• Before restoring the databases on the CommServe, manually stop the IIS service on remote Web Servers using the IISreset command. IIS service can be restarted after successfully restoring the database on the CommServe.

• Run a full backup of the CommServe databases on the destination CommServe host to ensure that no current activity is lost. For more information on performing a DR backups, see Performing Disaster Recovery (DR) Backups.

• If you are using this procedure to recover the CommServe database from a disaster or for hardware refresh or to test DR recovery in maintenance mode, stop services on the original production CommServe host. For more information on stopping services, see Stopping a Service.

Procedure

1. From the command line, navigate to Software_Installation_Directory/Base and type the following command after substituting the appropriate parameter values.

   CSRecoveryAssistant.exe -operation operation mode -skipdump -dbdumplocation db dump location [-dbfilelocation 'path to extract the database files'] [-groupName 'test failover group name'] [-license 'path to new license file'] [-tononcluster] [-tocluster 'physical node1,physical node2']

   Note

   The parameters marked within [ ] are optional.

   For more information on the supported parameters, see Command Line Parameters for CommServe Recovery Assistant Tool.

Examples

• To recover the databases to the same CommServe host:

  CSRecoveryAssistant.exe -operation Recovery -dbdumplocation "c:\dr\set_xxx"

• To recover the databases to a different CommServe host:

  CSRecoveryAssistant.exe operation Recovery -dbdumplocation "c:\dr\set_xxx" -license "c:\license\xxxxx.xml"

• Alternatively, If the database is already restored apply the license file as follows:

  CSRecoveryAssistant.exe -operation Recovery -skipdump -license "c:\license\xxxxx.xml"

• To stage the CommServe databases for troubleshooting purposes in the default location:

  CSRecoveryAssistant.exe -operation Staging -dbdumplocation "c:\dr\set_xxx"

• To stage the CommServe databases for troubleshooting purposes in a different location:

  Note

  Make sure to pre-create the folder before executing the command.

  CSRecoveryAssistant.exe -operation Staging -dbdumplocation "c:\dr\set_xxx" -dbfilelocation "c:\Program Files\Commvault\ContentStore1\testdr" -dblogfilelocation "c:\Program Files\Commvault\ContentStore1\testdr"

• Alternatively to restore the CommServe databases to a different location:

  Note

  Make sure to pre-create the folder before executing the command.

  CSRecoveryAssistant.exe -operation Recovery -dbdumplocation "c:\dr\set_xxx" -dbfilelocation "c:\Program Files\Commvault\ContentStore1\testdr" -dblogfilelocation "c:\Program Files\Commvault\ContentStore1\testdr"

• To perform the following:

  • Disable all clients except the clients present in a client group

  • Disable Schedules

  • Disable Workflows

  • Suspend all jobs

  • Suspend all activities except Data Recovery which will be enabled.

    CSRecoveryAssistant.exe -operation Maintenance -skipdump -groupName "Test_Failover_Group"

• To disable all activities, schedules and suspend jobs:

  CSRecoveryAssistant.exe -operation Recovery -dbdumplocation "c:\dr\set_xxx" -disableddbactivity -disableallschedules -suspendalljobs

• To enable all activities, schedules and resume jobs:

  CSRecoveryAssistant.exe -operation Recovery -dbdumplocation "c:\dr\set_xxx" -enableddbactivity -enableallschedules -resumealljobs

Result

After the DR restore, you will notice a considerable increase in the job ID for new jobs. This increase is added to avoid conflicts with job IDs referenced in the deduplication databases (DDBs) when the DDBs are resynchronized.

What To Do Next

• Restart the IIS service on remote Web Servers.

• Start all services on the destination CommServe host. For more information on starting services, see, Starting a Service.

• Complete the steps described in Recovering the CommServe Computer Using DR Backups.