Based on our current Commvault infrastructure:
-
We have one CommServe and a Media Agent at the DC location.
-
A Standby CommServe has recently been configured in Azure, and we successfully tested a planned failover. During the test, we were able to run backup and restore jobs using the Standby host while the Production CommServe (services) was down.
Now, we would like to extend our testing to include the Media Agent as well, specifically for a scenario where both the Production CommServe and the Media Agent at DC are unavailable.
From the planned failover test, we have confirmed that the Standby CommServe can take over. However, in the event of a complete DC outage (CommServe and Media Agent down together), we need clarity on how to proceed.
Our current policy setup is:
-
Primary copies → Local storage (without DDB).
-
Secondary copies → Cloud storage (with Commvault DDB).
We would like guidance on how to best configure a Media Agent in Azure so that it can act as a standby. The goal is to ensure that if DC goes down completely, we can failover to the Standby CommServe in Azure and use the Standby Media Agent to perform restores to cloud servers.
My assumption is to setup Media agent in cloud and attach existing cloud library to it. However, I am confused if the standy Media agent needs DDB on it? or It can access the library as is, for restores.
