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:
![](https://uploads-eu-west-1.insided.com/commvault-eu/attachment/936d736c-3c25-407b-ae9f-5f8142364a49.png)
… and:
![](https://uploads-eu-west-1.insided.com/commvault-eu/attachment/73fc20d2-e35c-4634-a3ee-f09f481af982.png)
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!