We have been experiencing problems with our nightly full database backups taking too long to run and spilling over into business hours in the morning. This adversely affects system performance. We have a history with this problem and for a long time thought that it was based on contention to the storage device where the backups are written (as we have multiple database clusters). But we have spaced out the backup routines accordingly and even replaced the storage device. Still, some nights the backups run exactly as planned and other nights, in at least one of our pools, take an extremely disproportionate amount of time to run. It is starting to feel like a problem with our Redgate configuration. Any suggestions?
Comments
1 comment
-
Hi Todd,
If you need to kill a running backup process, I think that the best way to simply to stop the SQL Backup Agent Service on the SQL Server. This will terminate any backups that SQL Backup may be running as part of a SQL Agent schedule.
If you have any more questions, please let me know.
Add comment
Please sign in to leave a comment.