Recovering the CommServe Database Using the Recovery Assistant Tool for Linux

You can recover your Linux CommServe database from a disaster recovery (DR) backup to the same or a different Linux CommServe host using the CommServe Recovery Assistant tool for Linux.

The tool is primarily used in the following scenarios:

• To rebuild a CommServe host in the event of a disaster

• To upgrade or move the CommServe database to a new hardware

• To restore DR Backup to rollback the CommServe server to a previous version

The tool restores the database to the specified restore path, and can upgrade the database from a previous version or service pack. For example, if the database available in the DR backup that you plan to restore has an older service pack and the destination CommServe host has the most recent service pack, then the database is upgraded to the service pack available in the destination CommServe host.

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.

Procedure

1. If possible, run a full backup of the CommServe databases to ensure that no current activity is lost.

   For more information on performing DR backups, see Performing Disaster Recovery (DR) Backups.

   For more information on performing a backup without losing current activity, see Performing a No Loss Recovery of the CommServe Host.

2. Stop services on the original production CommServe host, if it is active. For more information on stopping services, see Commands to Control Services on UNIX Clients.

3. To run the Recovery Assistant tool, log on to the destination Linux CommServe computer as root, go to <software installation path>/Base64, and execute the following command:

   ./CSRecoveryAssistant.sh -operation Recovery -dbdumplocation "<path to the database dump folder>" -dbfilelocation "<database data files restore location>" -dblogfilelocation "<database log files restore location>"

   Example:

   ./CSRecoveryAssistant.sh -operation Recovery -dbdumplocation "/DRBackup/SET_001" -dbfilelocation "/opt/commvaultDB" -dblogfilelocation "/opt/commvaultDB"

   The command completes and exits.

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.

• The tool performs the following operations on the CommServe system:

  • Stops services on your CommServe computer

  • Restores the database to the specified restore path

  • Verifies and upgrades the database if required

  • Synchronizes the CommServe system and the restored database

  • Runs post operations on the CommServe computer

What To Do Next

• Restart the IIS service on Windows web servers and all Commvault services on all web servers.

• Start all services on the destination CommServe host. For more information on starting services, see Commands to Control Services on UNIX Clients.

• Complete the steps described in CommServe Recovery Using DR Backups.