My backup times suddenly doubled
SQLJeff
Posts: 3 New member
in SQL Backup
I went from less than 4 hours to over 7. the database grew roughly 200GB from 2.5TB to 2.7TB. There haven't been any material changes and all-flash subsystem isn't having any issues that I am aware of. Any thoughts on where to start? tried all 4 levels of compression. the only change was adding CPUs to the VM and subsequent wizards suggested more threads. Putting it back to same threads as before didn't help. Post-backup copy and mirror also are dreadfully slow while a windows copy of SQB file takes an hour.
Tagged:
Answers
The default folder where the logs are stored is C:\ProgramData\Red Gate\SQL Backup\Log\<instance name>.
Thank you.
SQL Backup log file 10.1.7.1571
The May restore averaged 89.555 MB/sec, while the recent restore on November 30 averaged 86.855 MB/sec, which is fairly similar. There is a slight discrepancy for the November restore, where SQL Server reports that the restore took 32870 seconds. The restore started at 2 AM, and only completed at 11:33 AM, when it should have completed at 11:07 AM. It's possible that the 24 extra minutes were due to SQL Server having to initialize the database files, if instant file initialization was not possible.
The throughput between backups and restores can be expected to be similar if you were backing up and restoring from the same servers using the same set of disks with the same connectivity. If you copied a file of about 500 MB from the \\lucreserver\DBBackups\MedRisk\ share to the G:\SQLData\ folder on the server you are trying to restore to, what is the reported Windows transfer rate?
Thanks.