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
Showing posts with label appreciate. Show all posts
Showing posts with label appreciate. Show all posts
Saturday, February 25, 2012
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")
- RichardI 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 MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<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|||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:18=A0pm, "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.asph=
ttp://sqlblog.com/blogs/tibor_karaszi
> <Richard.G...@.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 =A0DISK =3D 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? =A0(If it matters, the recovery model is "Full")
> > -Richard- Hide quoted text -
> - 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 ...
=2E
=2E
=2E
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:15=A0am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Richard
> If you add WITH CONTINUE_AFTER_ERROR =A0your backup should complered
> succefully
> <Richard.G...@.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 =A0DISK =3D 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? =A0(If it matters, the recovery model is "Full")
> > -Richard- Hide quoted text -
> - 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|||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.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<Richard.Gohs@.pa-tech.com> wrote in message
news:e0d09f1c-ff0b-4899-abd1-5eee822f08a7@.e39g2000hsf.googlegroups.com...
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
> 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...
>
> > 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- Hide quoted text -
> - 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
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")
- RichardI 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 MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<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|||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:18=A0pm, "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.asph=
ttp://sqlblog.com/blogs/tibor_karaszi
> <Richard.G...@.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 =A0DISK =3D 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? =A0(If it matters, the recovery model is "Full")
> > -Richard- Hide quoted text -
> - 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 ...
=2E
=2E
=2E
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:15=A0am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Richard
> If you add WITH CONTINUE_AFTER_ERROR =A0your backup should complered
> succefully
> <Richard.G...@.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 =A0DISK =3D 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? =A0(If it matters, the recovery model is "Full")
> > -Richard- Hide quoted text -
> - 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|||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.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<Richard.Gohs@.pa-tech.com> wrote in message
news:e0d09f1c-ff0b-4899-abd1-5eee822f08a7@.e39g2000hsf.googlegroups.com...
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
> 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...
>
> > 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- Hide quoted text -
> - 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
Sunday, February 12, 2012
backup issue
To all,
As always, I appreciate your help.
In an active/active cluster environment, I have a 68GB
database. Creates a 63GB .BAK file to a separate drive at
night that is on one of the physical nodes of the cluster,
but the physical drive is not assigned to the cluster.
The .BAK is only thing on the drive.
After performing chkdsk maintenance, I got deleting
indexing entry...MFT file. (I think this may be related to
Microsoft's KB327009)
So I've rebooted a couple times performing chkdsk /f and
the disk comes back clean. I backup the db again manually,
doing a restore verify of course, says it's good. At night
when the maintenance job runs, in the morning it says the
file is not a valid backup set. I run chkdsk and get
errors. At night we have a 3rd party backup program that
kicks off and around the same time I have this error in my
system logs: Event ID 12503 - The Distributed Link
Tracking log was corrupt on volume Z: and has been re-
created. This log is used to automatically repair file
links, such as Shell Shortcuts and OLE links, when for
some reason those links become broken.
I have deleted and re-created the job, and this past week.
I've been running the job manually in the evening, the job
will run once successfully at night, but if I allow it to
backup through the jobs the following night. I get that
it's not a valid backup set again. Confusing huh?
Has anyone experienced such a thing? And if so, please
share how you fixed it? If not, any suggestions are
greatly appreciated, because I'm fresh out of ideas.
Thanks,
JosieJosie,
Hello!
Looking at your problem, it appears to me that you could be looking at some
disk corruption. The best place to start would be the Event logs and see
if:-
1. You see any corruption or hardware errors
2. Did the backups actually complete successfully?
3. Is the database corrupt? (Run checkdb)
With SQL Server backups, we usually have commands such as RESTORE
VERIFYONLY and RESTORE HEADERONLY to verify the state of a backup device. A
backup can be deemed as successful only after it's been fully restored, and
a checkdb is run on it.
I'd suggest you look at the event logs, and maybe get your hardware vendors
engaged as well. Have you tried backing up the db to another drive?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
As always, I appreciate your help.
In an active/active cluster environment, I have a 68GB
database. Creates a 63GB .BAK file to a separate drive at
night that is on one of the physical nodes of the cluster,
but the physical drive is not assigned to the cluster.
The .BAK is only thing on the drive.
After performing chkdsk maintenance, I got deleting
indexing entry...MFT file. (I think this may be related to
Microsoft's KB327009)
So I've rebooted a couple times performing chkdsk /f and
the disk comes back clean. I backup the db again manually,
doing a restore verify of course, says it's good. At night
when the maintenance job runs, in the morning it says the
file is not a valid backup set. I run chkdsk and get
errors. At night we have a 3rd party backup program that
kicks off and around the same time I have this error in my
system logs: Event ID 12503 - The Distributed Link
Tracking log was corrupt on volume Z: and has been re-
created. This log is used to automatically repair file
links, such as Shell Shortcuts and OLE links, when for
some reason those links become broken.
I have deleted and re-created the job, and this past week.
I've been running the job manually in the evening, the job
will run once successfully at night, but if I allow it to
backup through the jobs the following night. I get that
it's not a valid backup set again. Confusing huh?
Has anyone experienced such a thing? And if so, please
share how you fixed it? If not, any suggestions are
greatly appreciated, because I'm fresh out of ideas.
Thanks,
JosieJosie,
Hello!
Looking at your problem, it appears to me that you could be looking at some
disk corruption. The best place to start would be the Event logs and see
if:-
1. You see any corruption or hardware errors
2. Did the backups actually complete successfully?
3. Is the database corrupt? (Run checkdb)
With SQL Server backups, we usually have commands such as RESTORE
VERIFYONLY and RESTORE HEADERONLY to verify the state of a backup device. A
backup can be deemed as successful only after it's been fully restored, and
a checkdb is run on it.
I'd suggest you look at the event logs, and maybe get your hardware vendors
engaged as well. Have you tried backing up the db to another drive?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
backup issue
To all,
As always, I appreciate your help.
In an active/active cluster environment, I have a 68GB
database. Creates a 63GB .BAK file to a separate drive at
night that is on one of the physical nodes of the cluster,
but the physical drive is not assigned to the cluster.
The .BAK is only thing on the drive.
After performing chkdsk maintenance, I got deleting
indexing entry...MFT file. (I think this may be related to
Microsoft's KB327009)
So I've rebooted a couple times performing chkdsk /f and
the disk comes back clean. I backup the db again manually,
doing a restore verify of course, says it's good. At night
when the maintenance job runs, in the morning it says the
file is not a valid backup set. I run chkdsk and get
errors. At night we have a 3rd party backup program that
kicks off and around the same time I have this error in my
system logs: Event ID 12503 - The Distributed Link
Tracking log was corrupt on volume Z: and has been re-
created. This log is used to automatically repair file
links, such as Shell Shortcuts and OLE links, when for
some reason those links become broken.
I have deleted and re-created the job, and this past week.
I've been running the job manually in the evening, the job
will run once successfully at night, but if I allow it to
backup through the jobs the following night. I get that
it's not a valid backup set again. Confusing huh?
Has anyone experienced such a thing? And if so, please
share how you fixed it? If not, any suggestions are
greatly appreciated, because I'm fresh out of ideas.
Thanks,
Josie
Josie,
Hello!
Looking at your problem, it appears to me that you could be looking at some
disk corruption. The best place to start would be the Event logs and see
if:-
1. You see any corruption or hardware errors
2. Did the backups actually complete successfully?
3. Is the database corrupt? (Run checkdb)
With SQL Server backups, we usually have commands such as RESTORE
VERIFYONLY and RESTORE HEADERONLY to verify the state of a backup device. A
backup can be deemed as successful only after it's been fully restored, and
a checkdb is run on it.
I'd suggest you look at the event logs, and maybe get your hardware vendors
engaged as well. Have you tried backing up the db to another drive?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
As always, I appreciate your help.
In an active/active cluster environment, I have a 68GB
database. Creates a 63GB .BAK file to a separate drive at
night that is on one of the physical nodes of the cluster,
but the physical drive is not assigned to the cluster.
The .BAK is only thing on the drive.
After performing chkdsk maintenance, I got deleting
indexing entry...MFT file. (I think this may be related to
Microsoft's KB327009)
So I've rebooted a couple times performing chkdsk /f and
the disk comes back clean. I backup the db again manually,
doing a restore verify of course, says it's good. At night
when the maintenance job runs, in the morning it says the
file is not a valid backup set. I run chkdsk and get
errors. At night we have a 3rd party backup program that
kicks off and around the same time I have this error in my
system logs: Event ID 12503 - The Distributed Link
Tracking log was corrupt on volume Z: and has been re-
created. This log is used to automatically repair file
links, such as Shell Shortcuts and OLE links, when for
some reason those links become broken.
I have deleted and re-created the job, and this past week.
I've been running the job manually in the evening, the job
will run once successfully at night, but if I allow it to
backup through the jobs the following night. I get that
it's not a valid backup set again. Confusing huh?
Has anyone experienced such a thing? And if so, please
share how you fixed it? If not, any suggestions are
greatly appreciated, because I'm fresh out of ideas.
Thanks,
Josie
Josie,
Hello!
Looking at your problem, it appears to me that you could be looking at some
disk corruption. The best place to start would be the Event logs and see
if:-
1. You see any corruption or hardware errors
2. Did the backups actually complete successfully?
3. Is the database corrupt? (Run checkdb)
With SQL Server backups, we usually have commands such as RESTORE
VERIFYONLY and RESTORE HEADERONLY to verify the state of a backup device. A
backup can be deemed as successful only after it's been fully restored, and
a checkdb is run on it.
I'd suggest you look at the event logs, and maybe get your hardware vendors
engaged as well. Have you tried backing up the db to another drive?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
backup issue
To all,
As always, I appreciate your help.
In an active/active cluster environment, I have a 68GB
database. Creates a 63GB .BAK file to a separate drive at
night that is on one of the physical nodes of the cluster,
but the physical drive is not assigned to the cluster.
The .BAK is only thing on the drive.
After performing chkdsk maintenance, I got deleting
indexing entry...MFT file. (I think this may be related to
Microsoft's KB327009)
So I've rebooted a couple times performing chkdsk /f and
the disk comes back clean. I backup the db again manually,
doing a restore verify of course, says it's good. At night
when the maintenance job runs, in the morning it says the
file is not a valid backup set. I run chkdsk and get
errors. At night we have a 3rd party backup program that
kicks off and around the same time I have this error in my
system logs: Event ID 12503 - The Distributed Link
Tracking log was corrupt on volume Z: and has been re-
created. This log is used to automatically repair file
links, such as Shell Shortcuts and OLE links, when for
some reason those links become broken.
I have deleted and re-created the job, and this past week.
I've been running the job manually in the evening, the job
will run once successfully at night, but if I allow it to
backup through the jobs the following night. I get that
it's not a valid backup set again. Confusing huh?
Has anyone experienced such a thing? And if so, please
share how you fixed it? If not, any suggestions are
greatly appreciated, because I'm fresh out of ideas.
Thanks,
JosieJosie,
Hello!
Looking at your problem, it appears to me that you could be looking at some
disk corruption. The best place to start would be the Event logs and see
if:-
1. You see any corruption or hardware errors
2. Did the backups actually complete successfully?
3. Is the database corrupt? (Run checkdb)
With SQL Server backups, we usually have commands such as RESTORE
VERIFYONLY and RESTORE HEADERONLY to verify the state of a backup device. A
backup can be deemed as successful only after it's been fully restored, and
a checkdb is run on it.
I'd suggest you look at the event logs, and maybe get your hardware vendors
engaged as well. Have you tried backing up the db to another drive?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
As always, I appreciate your help.
In an active/active cluster environment, I have a 68GB
database. Creates a 63GB .BAK file to a separate drive at
night that is on one of the physical nodes of the cluster,
but the physical drive is not assigned to the cluster.
The .BAK is only thing on the drive.
After performing chkdsk maintenance, I got deleting
indexing entry...MFT file. (I think this may be related to
Microsoft's KB327009)
So I've rebooted a couple times performing chkdsk /f and
the disk comes back clean. I backup the db again manually,
doing a restore verify of course, says it's good. At night
when the maintenance job runs, in the morning it says the
file is not a valid backup set. I run chkdsk and get
errors. At night we have a 3rd party backup program that
kicks off and around the same time I have this error in my
system logs: Event ID 12503 - The Distributed Link
Tracking log was corrupt on volume Z: and has been re-
created. This log is used to automatically repair file
links, such as Shell Shortcuts and OLE links, when for
some reason those links become broken.
I have deleted and re-created the job, and this past week.
I've been running the job manually in the evening, the job
will run once successfully at night, but if I allow it to
backup through the jobs the following night. I get that
it's not a valid backup set again. Confusing huh?
Has anyone experienced such a thing? And if so, please
share how you fixed it? If not, any suggestions are
greatly appreciated, because I'm fresh out of ideas.
Thanks,
JosieJosie,
Hello!
Looking at your problem, it appears to me that you could be looking at some
disk corruption. The best place to start would be the Event logs and see
if:-
1. You see any corruption or hardware errors
2. Did the backups actually complete successfully?
3. Is the database corrupt? (Run checkdb)
With SQL Server backups, we usually have commands such as RESTORE
VERIFYONLY and RESTORE HEADERONLY to verify the state of a backup device. A
backup can be deemed as successful only after it's been fully restored, and
a checkdb is run on it.
I'd suggest you look at the event logs, and maybe get your hardware vendors
engaged as well. Have you tried backing up the db to another drive?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Subscribe to:
Posts (Atom)