Skip to main content
Solved

DR site's DB appears fried

  • 11 October 2023
  • 2 replies
  • 46 views

So we’ve been having issues with the DR site’s CV backup.  I’ve managed to access the COMMVAULT instance in management studio, to see these lovely notes:

… and:

This is a system that I’ve inheirited and still learn new things about every other day.  My best thought here is that I simply need to nuke and repave (rebuild) this entire CV server.  It’s not the end of the world and would be a good learning experience for me.  

 

But I have to ask - is there a faster way?  I really don’t think just backing up the main site’s DB and recreating everything here can be trusted (different server names, etc.) 

This is CV 2022 (11.28.x) running on server 2022.  Based on being CV v11.28, you might already know it’s SQL Server 2014.

Thougths?

 

Merci! 

 

2 replies

V
Rank
Userlevel 2
Badge +5

You typically wouldn’t want to back up the CS DB on the DR site, that said you can pull the databases out of restoring mode.

 

https://documentation.commvault.com/2023e/essential/105030_getting_database_out_of_restoring_mode.html

R
Rank
Badge +3

As the Commvault product evolves, so does the engine it runs on. The SQL Server for the Commvault (CV) v11.28.* needs SQL Server 2016 or newer. This is mentioned here: 

https://documentation.commvault.com/2022e/expert/2801_commserve_server_system_requirements_windows_02.html

If you uninstalled all of CV software from the machine and the SQL Server 2014, your new installation package (which can include the SQL Server 2019) would default to installing the new SQL Server 2019. 

Understand that this would allow you to be compliant with the pre-requisites. Also know that this would allow you ensure that your CS DB can be failed over to the Standby, but you would not be able to fail-back. This is because the SQL Server on the old is still SQL Server 2014. 

So the path could be as follows:

  1. Failover to the Standby (with the new SQL Server 2019).
  2. After ensuring all restores are functioning correctly…
  3. Uninstall the CV and SQL 2014 from the old ProdCS.
  4. Re-install the CV + SQL Server 2019 again on the Prod (Following the instructions for installing on a Standby CS.) The documentation for this can be found here: https://documentation.commvault.com/2022e/essential/106129_installing_standby_commserve_host.html
  5. Ensure that the CS LiveSync is backing up and replicating back to the ProdCS. 

At this point, you can choose to allow the CS to continue to function on the Standby (AKA: Node2).

Or you can choose to failover back to the orgingal Prod CS (AKA: Node1). 

The most important fact is that the Commserv DB is secured to the most recent point in time. 

 

Hope this helps. 

 

Reply


Terms & ConditionsCookie settings