Backup of database fails ...

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
Richard
If you add WITH CONTINUE_AFTER_ERROR your backup should complered
succefully
<Richard.Gohs@.pa-tech.com> wrote in message
news:f98ed696-ed40-4655-98ad-3d9849c0404a@.n75g2000hsh.googlegroups.com...
> 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
|||On Mar 13, 5:18Xpm, "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
> backup and all subsequent log backups. Did you DBCC CHECKDB the database?
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> <Richard.G...@.pa-tech.com> wrote in message
> news:f98ed696-ed40-4655-98ad-3d9849c0404a@.n75g2000hsh.googlegroups.com...
>
>
>
>
>
>
> - 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
|||On Mar 16, 6:15Xam, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Richard
> If you add WITH CONTINUE_AFTER_ERROR Xyour backup should complered
> succefully
> <Richard.G...@.pa-tech.com> wrote in message
> news:f98ed696-ed40-4655-98ad-3d9849c0404a@.n75g2000hsh.googlegroups.com...
>
>
>
>
>
>
> - 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