SQL backups do not resume upon suspending? Resuming causes SQL backups to start over or skip current database and move to next one? So should we prefer the job to be killed if it is going to pending state repeatedly and not suspend it. This way, next schedule can kick in and run successfully.
Userlevel 6
+15
- Vaulter
- 326 replies
-
28 November 2023
Hi
Yes, if a SQL backup job is interrupted part way thru a database backup, the DB being protected at the time will start from scratch (say 500GB/1TB was processed, we will disregard the 500GB and restart the DB from 0GB).
If multiple databases were being protected in the one job, any that were succcessful prior to the DB that was interrupted can be committed and will be restorable if you allow the job to complete with errors.
You can control restartability / retry options by referring to the following article:
https://documentation.commvault.com/2023e/expert/6559_configuring_restartability_for_job_type.html
https://documentation.commvault.com/2023e/expert/6320_setting_total_running_time_for_jobs.html
Let me know how you go.
Regards,
Chris
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.