Upgraded from 2008 R2 to 2012, now my backup script will not execute, help. Log included.

  • Uninstalled SQL 2008 R2 and installed SQL Server Express 2012 - Re-Attached the DB and everything is working fine. BUT, now my backup script will not work. I understand the error, but I dont understand why or what the fix is.

    ERROR in Log File:

    Msg 3268, Level 16, State 1, Line 1

    Cannot use the backup file 'C:\DWBackup\DWBackup.bak' because it was originally formatted with sector size 512 and is now on a device with sector size 4096.

    Msg 3013, Level 16, State 1, Line 1

    BACKUP DATABASE is terminating abnormally.

    My Script:

    SQLCMD -S.\DINERWARE -E -Q "BACKUP DATABASE CH TO DISK='C:\DWBackup\DWBackup.bak'WITH INIT" -oC:\DWbackup\DWBackupLog.log

    This script has always worked and works on my other 2012 instances.

    Formatting this hard disk is not an option. As I am working remotely.

    Thank you for looking and any educated suggestions.

    Google no real help here.

  • Quick suggestion, switch to Ola Hallengren's maintenance scripts[/url]

    😎

  • I would expect deleting the current file via explorer so that the backup is creating a fresh file to work.

    Copy or move the existing file elsewhere to be safe. Have you tried restoring the current file (to another database name)?

    ---------------------------------------------------------------------

  • george sibbald (1/10/2016)


    I would expect deleting the current file via explorer so that the backup is creating a fresh file to work.

    Copy or move the existing file elsewhere to be safe. Have you tried restoring the current file (to another database name)?

    Fresh worked, I need to think deeper, i could have figured this out!

    Thank you none the less!

  • Eirikur Eiriksson (1/10/2016)


    Quick suggestion, switch to Ola Hallengren's maintenance scripts[/url]

    😎

    Thank you for the suggestion.

    Why is this code better than mine? I will look at them and read up, can you comment tho?

    Thanks!!!!! 🙂

  • no problem. It is an issue with constantly overwriting the same file, it is possible that sooner or later they can get corrupted, so longer term if you have the space you might want to look into keeping multiple backup copies and cycling them out, the scripts eirikur suggests would handle that for you.

    ---------------------------------------------------------------------

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply