InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 18 May 2013 02:08:32 GMT20http://www.sqlservercentral.com/Forums/Topic1391769-357-1.aspxIt turned out that fixing the database mirroring made my database restoration difficulties go away.... though it took my host a fair while to get that straightened out.And you were right about runaway log file size ... the backups shrunk _noticeably_ after the fix.Thanks again for the help.Fri, 21 Dec 2012 08:46:42 GMTBriChttp://www.sqlservercentral.com/Forums/Topic1391769-357-1.aspxYes, that's database mirroring. No, it would not have caused the backup error. It's likely to cause you lots more fun unless you resume the mirroring or remove the mirroring entirely (like full transaction logs, drives out of space and such entertainment)Mon, 03 Dec 2012 12:53:20 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1391769-357-1.aspxThanks everyone for the responses. I'm a hobbyist programmer so my self-training has many holes. CheckDB was one of those holes. However, running it now seemed relatively positive, as much as I can make out the output. It was much like the sample output on the MSDN page. And at the end it said,[code]CHECKDB found 0 allocation errors and 0 consistency errors in database 'mydatabase'[/code]So that was a relief of sorts.However, I noticed something that should have been obvious to me the first time around that is perhaps a related detail.In the database listing in SQL Management Studio it has (Principal, Suspended) behind the database name. This is on the web host and after a quick search it seems that this is related to a database mirroring arrangement (that I didn't know about). Could this cause the backup problem?Mon, 03 Dec 2012 11:33:39 GMTBriChttp://www.sqlservercentral.com/Forums/Topic1391769-357-1.aspxCheckout these below mansion references would be help you.http://msdn.microsoft.com/en-us/library/ms177429.aspxhttp://msdn.microsoft.com/en-us/library/ms175510.aspxhttp://msdn.microsoft.com/en-us/library/ms177429%28v=sql.100%29.aspxThanksMon, 03 Dec 2012 03:05:24 GMTjohnwebsofthttp://www.sqlservercentral.com/Forums/Topic1391769-357-1.aspxThe source database is probably damaged. Discard that backup, it's likely to be fairly useless. You shouldn't be worrying about the backup at this point, worry about the DB that the backup was taken of.How often do you run CheckDB on the source database and when did it last run without errors?Mon, 03 Dec 2012 01:23:07 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1391769-357-1.aspxtry restoring the backup and then run DBCC CHECKDB and look for any error messages[url] http://blogs.msdn.com/b/venkn/archive/2010/03/16/failing-to-restore-sql-server-database-backup-with-internal-consistency-error.aspx[/url]Sun, 02 Dec 2012 23:26:11 GMTJayanth_Kuruphttp://www.sqlservercentral.com/Forums/Topic1391769-357-1.aspxI recently backed up a database and when trying to restore it to my local machine I got this error:[code="sql"]Msg 3182, Level 16, State 2, Line 1The backup set cannot be restored because the database was damagedwhen the backup occurred. Salvage attempts may exploit WITH CONTINUE_AFTER_ERROR[/code]I tried several different backups (e.g., with the crc check/verifying the backup options checked/unchecked). I tried restoring within the management studio gui and via T-SQL script. Each time the same error.I can successfully restore if I include the 'continue_after_error' but I'm unaware of what the error was and it leaving it this way will give me a nagging feeling of doom to come.What should I be doing to troubleshoot this? I'm a relative beginner with respect to database administration and until now, things have gone smoothly in all my backups/restores.Sun, 02 Dec 2012 22:31:07 GMTBriC