What was the command you entered?
Questionst that occur to me: After your attempt to run the backup, was there
a file with the name specified? Was it there earlier? Could you do a
RESTORE ... HEADERONLY from the backup file? Had you tried one before the
aborted command? What are the create/write dates on the file? Is it mixed
full and differential backups? Is this file referenced in any other backup
commands? Have you been intializing this file between differentials to it?
What have you changed lately? Do you use a stored proc to run your backups?
What's the create date on the stored proc?
If this particular backup doesn't contain anyting critical, I guess I'd do a
new full backup (to a different file, of course), delete this file and then
do a new differential.
"tim groulx" <ti****@verizon.net> wrote in message
news:40**********************@news.newsgroups.ws.. .
I have recently started receiving failures on a differential backup that
previously succeeded. Nothing has changed with the structure of the db.
Here is the message, any ideas are welcomed. Thanks.
Executed as user: fsafood-net\bisqlservice. The backup data in
'E:\SQL_Backups\Biz_Sales\Biz_Sales_Diff.bak' is incorrectly formatted.
Backups cannot be appended, but existing backup sets may still be
usable. [SQLSTATE 42000] (Error 3266) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013) Associated statement is not
prepared [SQLSTATE HY007] (Error 0) The media family on device
'E:\SQL_Backups\Biz_Sales\Biz_Sales_Diff.bak' is incorrectly formed. SQL
Server cannot process this media family. [SQLSTATE 42000] (Error 3241)
VERIFY DATABASE is terminating abnormally. [SQLSTATE 42000] (Error
3013). The step failed.
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
