Delay between backups on SQL Backup Pro

Comments

• petey Redgate › Posts: 2,358 New member

  March 20, 2014 5:28AM

  Could you please post the backup command you are using to back up your databases? Thanks.

  Peter Yeoh
  SQL Backup Consultant Developer
  Associate, Yohz Software
  Beyond compression - SQL Backup goodies under the hood, updated for version 8

  0 · Share on Twitter
• ike@ikeellis.com Posts: 3 Bronze 1

  March 20, 2014 5:57PM

  I opened a ticket. I don't want to make you do repeated work. I'll post the results of the ticket here for Google.

  Ike Ellis

  0 · Share on Twitter
• petey Redgate › Posts: 2,358 New member

  March 20, 2014 9:28PM

  If it helps, the most common cause of the delay is when you:
  

  - backup a lot of databases using the BACKUP DATABASES syntax - to the same folder - and use the ERASEFILES option to delete older backup files

  In these situations, there will be a lot of files in that single folder, and after every database backup, SQL Backup will scan every single file in that folder to determine which file it needs to delete. This issue will be compounded if you back up to a network share, as the scanning process will take even longer.
  
  What you can do is to place each database's backup files in its own separate folder using the <DATABASE> tag e.g. instead of
  

  EXEC master..sqlbackup '-sql "BACKUP DATABASES [*] TO DISK = [\\netshare\backups\<AUTO>]... " '
  

  use

  EXEC master..sqlbackup '-sql "BACKUP DATABASES [*] TO DISK = [\\netshare\backups\<DATABASE>\<AUTO>]... " '
  

  Now, SQL Backup needs to scan only that specific database's folder to determine which file(s) to delete, which speeds things up significantly. If that is still too slow, you can add another subfolder based on the backup type using the <TYPE> tag e.g.
  

  EXEC master..sqlbackup '-sql "BACKUP DATABASES [*] TO DISK = [\\netshare\backups\<DATABASE>\<TYPE>\<AUTO>]... " '
  

  Peter Yeoh
  SQL Backup Consultant Developer
  Associate, Yohz Software
  Beyond compression - SQL Backup goodies under the hood, updated for version 8

  0 · Share on Twitter
• TaylorT Posts: 1

  February 19, 2016 6:34AM

  petey wrote:

  If it helps, the most common cause of the delay is when you:
  

  - backup a lot of databases using the BACKUP DATABASES syntax - to the same folder - and use the ERASEFILES option to delete older backup files

  In these situations, there will be a lot of files in that single folder, and after every database backup, SQL Backup will scan every single file in that folder to determine which file it needs to delete. This issue will be compounded if you back up to a network share, as the scanning process will take even longer.
  
  What you can do is to place each database's backup files in its own separate folder using the <DATABASE> tag e.g. instead of
  

  EXEC master..sqlbackup '-sql "BACKUP DATABASES [*] TO DISK = [\\netshare\backups\<AUTO>]... " '
  

  use

  EXEC master..sqlbackup '-sql "BACKUP DATABASES [*] TO DISK = [\\netshare\backups\<DATABASE>\<AUTO>]... " '
  

  Now, SQL Backup needs to scan only that specific database's folder to determine which file(s) to delete, which speeds things up significantly. If that is still too slow, you can add another subfolder based on the backup type using the <TYPE> tag e.g.
  

  EXEC master..sqlbackup '-sql "BACKUP DATABASES [*] TO DISK = [\\netshare\backups\<DATABASE>\<TYPE>\<AUTO>]... " '
  

  
  Brilliant post Petey. With over 400 databases things were taking forever. Now I have them all in their own folders. Thanks for saving me a lot of time.

  I think this phen375 review is amazing.

  0 · Share on Twitter