How can we help you today? How can we help you today?

Issue deleting V5.3 Backup Files

I've tested backing up to a local folder and copying to a network drive. The script is below. In both cases, it appears the file deletion (set to delete before the backup) hung when trying to decide wether or not to delete a V5.3 backup. I waited nearly 15 minutes before killing the service. During that time, the backup file was in use, and could not be renamed or removed. I tested this several times, moving V5.3 backup files in and out, and the problem definitely followed the V5.3 files.

Try to reproduce:

From a source DB, back it up with V5.3 to a backup fiolder.

Back up that same DB using V6 to the same folder.

Back up again with V6, but this time tell it to only retain the last 1 backup file, and delete before backup.

That should hang.


EXECUTE master..sqlbackup '-SQL "BACKUP DATABASES [DB1,DB2,DB3] TO DISK = ''C:\SQLBackups\Database\<database>\<AUTO>.sqb'' WITH ERASEFILES = 1B, ERASEFILES_REMOTE = 1B, MAILTO = ''dan.w@s.com'', PASSWORD = ''<ENCRYPTEDPASSWORD>sdgtr4e55=</ENCRYPTEDPASSWORD>'', DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 5, COMPRESSION = 4, COPYTO = ''\\Server\is\dw\sqlbackups\database\sql2005\dBs', KEYSIZE = 256, THREADCOUNT = 2, VERIFY"'


Thanks,
Dan W.
DWolford1234
0

Comments

3 comments

Sort by
  • mattchandler
    Hi Dan,

    Thanks for raising this with us. I can reproduce this on a test machine here.

    Clearly this is a serious issue, and we will want to fix it before the final release. For the time being, I hope you can carry on using the pre-release without too much inconvenience. As you saw, a work-around is to manually remove 5.3 backups from the folders you are backing up to.

    Thanks again!
    Matt Chandler,
    Software tester on SQL Backup
    mattchandler
    0
  • ChrisAVWood
    Will this also be a problem with deleting 5.4 backups?

    Thanks

    Chris
    ChrisAVWood
    0
  • mattchandler
    I'm afraid this is happening on the pre-release build with all encrypted backups version 5.4 or earlier. We've raised this internally so it will be fixed for the final release.

    Sorry for the inconvenience!
    mattchandler
    0

Add comment

Please sign in to leave a comment.