Question: I’m wondering if Commvault can be made to “auto retry” backing up a database if there are certain types of errors (when the database is online, and other DB’s are able to be backed up, just some failure occurs with a single DB)
Why: We have been having some issues with backing up MSSQL DB’s and its very intermittent. I know “find out what the connectivity/issue is” is probably the right approach, but time and rarity keep this from being a priority. People have asked “Can CommVault just retry?”
Example:
2 Db’s had failures in a backup of a MSSQL instance with about 50 Db’s in it.
Error 1 = “Error encountered when closing the virtual device. Please see SQL Server vdi.log for more details.”.
Reasoning for retry: In this case it appears there was some sort of disconnection (somewhere, somehow) for just this single DB when the backup ran. This would be a case where I would want CommVault to try again maybe 1 time after x minutes or something, as the DB is online, just something happened and its likely to backup if a second attempt is made.
Error 2 = “Error encountered during backup. Error: [Microsoft.SqlServer.Management.Common.ExecutionFailureException:Unable to access availability database 'X-REDACTED-X' because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later. BACKUP DATABASE is terminating abnormally. An exception occurred while executing a Transact-SQL statement or batch.]”
Reasoning for retry: In this case, I would not care if CommVault retries 1 extra time, but it's not going to matter, we just don’t want it “retrying forever” as its never going to get a successful backup as long as its in this state, but maybe it would… like maybe it was being configured by a DBA, or some other odd reason its neither primary or secondary for just a few minutes.
Best answer by Scott Reynolds
View original
