sql backup files: refuses

Showing posts with label refuses. 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

Friday, February 24, 2012

Backup MS SQL Server using ASP.NET

Hi!

For the moment I’m hooked up with this hosting company that refuses to give me any backup files of my Microsoft SQL Server database/tables. I’ve even asked if the can do it just once but they still won’t. I don’t know what they are doing because they won’t even let me use Enterprise Manager so, from what I know, can’t use the scripts that I’ve found that use stored procedures.

Which is the easiest way to do a full backup just using the built in functionality of ASP.NET 1.3 and with limited permission on the SQL server? The goal is to move everything to a new company.

A friend recommended this way:

Create a class that holds both the table structure and a dataset for the data.
Each instance of these class is then stored in a collection that we serialize and store on the web server.
When this is done we reverse the process at the new hosting company.

Would this work / be the easiest way?

ThanksYou can take help of SQLDMO in this case, refer http://www.aspfree.com/c/a/VB.NET/Simple-BackupRestore-Utility-With-SQLDMO-Using-VBNET/ and http://codingforums.com/archive/index.php?t-25387.html for information.

HTH|||Thanks!
I've got the same advice on another forum, http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=66036 (remove if it's not ok to link), who also suggested using DMO.|||Hey...I think that was me. :)

How you doing Satya?|||Hi Derrick
Thanks, I'm fine.. hope you had a good holiday as I don't see on the forums since a month (I think).
Its good to catch other forums too ... different from routine :)

How you doing Satya?

Saturday, February 25, 2012

Backup of database fails ...

Backup of database fails ...

Friday, February 24, 2012

Backup MS SQL Server using ASP.NET

sql backup files

Blog Archive

About Me