Backup of database fails ...

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Richard.Gohs@pa-tech.com - 13 Mar 2008 21:13 GMT

If anyone has any ideas on this one ... I'd appreciate it very
much ...

... I've got one database on our server that refuses to backup ...
several other database work just fine ...

... when I issue ...

BACKUP DATABASE [Kurtz_Inc_MSCRM] TO DISK = N'D:\MSSQL\BACKUP
\Kurtz_Inc_MSCRM_backup_manual.bak'

... it responds immediately with ...

Msg 3636, Level 16, State 2, Line 1
An error occurred while processing 'BackupMetadata' metadata for
database id 8 file id 65537.
Msg 3046, Level 16, State 2, Line 1
Inconsistent metadata has been encountered. The only possible backup
operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or
NO_TRUNCATE option.
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.

... if I include the "WITH CONTINUE_AFTER_ERROR" ... I still get the
same error.

Thoughts? (If it matters, the recovery model is "Full")

- Richard

Reply to this Message

Tibor Karaszi - 13 Mar 2008 22:18 GMT

I interpret the error message such as you have a corrupt database and the message suggest you to do
the very last log backup (TRUNCATE_ONLY) before you clean up the database by restoring a clean
backup and all subsequent log backups. Did you DBCC CHECKDB the database?

Signature

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

> If anyone has any ideas on this one ... I'd appreciate it very
> much ...
[quoted text clipped - 25 lines]
>
> - Richard

Reply to this Message

Richard.Gohs@pa-tech.com - 18 Mar 2008 12:03 GMT

On Mar 13, 5:18 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@hotmail.nomail.com> wrote:

> I interpret the error message such as you have a corrupt database and the message suggest you to do
> the very last log backup (TRUNCATE_ONLY) before you clean up the database by restoring a clean
[quoted text clipped - 38 lines]
>
> - Show quoted text -

Tibor,

FYI ... the reason I can't really go back to the backup is that the
database appears to be functional from the users point of view ...
(it's a Microsoft CRM 3.0 install) ... and users have been putting
additional data into it - and - I don't have log backups back to the
time of the last full backup (which I suspect means I'm hosed)

Running dbcc checkdb results in ...

.
.
.
CHECKDB found 0 allocation errors and 0 consistency errors in database
'Kurtz_Inc_MSCRM'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.

Thanks,
Richard

Reply to this Message

Tibor Karaszi - 19 Mar 2008 08:51 GMT

Hmm, if CHECKDB comes out clean but you get below error for BACKUP DATABASE then I would be very
nervous and open a case immediately with MS Support...

> > An error occurred while processing 'BackupMetadata' metadata for
> > database id 8 file id 65537.
> > Msg 3046, Level 16, State 2, Line 1
> > Inconsistent metadata has been encountered. The only possible backup
> > operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or

If course assuming that the database ID above mentioned is the same as the one you checkdb and
attempt to backup.

Signature

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

On Mar 13, 5:18 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@hotmail.nomail.com> wrote:

> I interpret the error message such as you have a corrupt database and the message suggest you to
> do
[quoted text clipped - 40 lines]
>
> - Show quoted text -

Reply to this Message

Uri Dimant - 16 Mar 2008 11:15 GMT

Richard

If you add WITH CONTINUE_AFTER_ERROR your backup should complered
succefully

> If anyone has any ideas on this one ... I'd appreciate it very
> much ...
[quoted text clipped - 25 lines]
>
> - Richard

Reply to this Message

Richard.Gohs@pa-tech.com - 18 Mar 2008 12:04 GMT

> Richard
>
[quoted text clipped - 36 lines]
>
> - Show quoted text -

Uri,

That's one of my problems (from the original post) ... adding "WITH
CONTINUE_AFTER_ERROR" seems to have no effect ... I get same error
immediately after issuing the backup command.

Thanks,
Richard

Reply to this Message