CommVault allows the installation of a CommVault Simpana Disaster Recovery CommServe to ensure the operations can be easily resumed after losing the active CommServe due to system outage or site-loss.
In this particular setup, we are using a protection mechanism on three different levels:
- Microsoft SQL Database mirroring has been configured to allow a near-zero replication to reduce configuration data loss when an issue occurs;
- CommVault Simpana Disaster Recovery Storage Policy which is dumping the database to a network location every 6 hours;
- CommVault Simpana Disaster Recovery Storage Policy which copies the database dump to a tape every 6 hours.
The interactive GUI-based installer requires the databases to be available in read/write modus and the services to be able to be started. The specific configuration on the CommServe DR doesn’t allow a service restart (DB is unavailable), nor the DB upgrade (DB is in mirroring modus). Hence, the installation will be unsuccessful.
The installation of the hotfixes and service packs on the Disaster Recovery CommServe are required, to guarantee a successful failover when required.
Luckily they build in a workaround to update the software without stopping and reconfiguring the DR methodology.
Copy the binaries to the system, open a command prompt with administrative privileges and navigate to the installation directory which has the InstallUpdates executable (“.\hotfix folder\cd_update\” or “.\servicepack\WindowsX64\“).
Execute the following command: “InstallUpdates.exe -silent -vm instance001 -nostartsvc -binaryonly -donotupdatedb” to execute a silent install without touching the database, nor starting the CommVault services.
- -silent: silent install of the software;
- -vm: defines the instance to be upgraded. In case you are patching a CommServe, the instance should be instance001 according to best practices;
- -nostartsvc: do not start the CommVault Services during the update process;
- -binaryonly: only update the CommVault binaries;
- -donotupdatedb: leave the database intact.
During the upgrade, the progress is not displayed within the Command Prompt. To follow the progress of the service pack- or hotfix installation, open the “updateinfo.log” (<install directory\log files) with gxtail.
To verify successful installation, open a registry and navigate to: “HKLM\SOFTWARE\CommVault Systems\Galaxy\Instance001\UpdateSummary\<componentID>” and verify if the patch has been applied by consulting the REG_SZ “CurrentAdditionalUpdates”.
In this particular example, we are installing hotfix 8 for service pack 11. This hotfix is only applicable for the following components: CommCell Console (id 701), WebConsole (id 726), WebServer (252) & WorkflowEngine (23). The easiest way to verify to which components are applicable for this hotfix, is by consulting the Active CommServer patch information.
Hope this helps!