sql backup files: ideas

Showing posts with label ideas. 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 10, 2012

backup files not deleting

Hello:
I have a few ideas about what to do on this. But, I still would like to
solicit some opinions, if you don't mind.
We have a SQL Server 2000 client who has a maintenance plan that conducts a
backup of its databases. And, each database is using the Full Recovery Mode
l.
The backup of the databases itself is working perfectly. But, the backup
files (bak files) are not being removed. You see, the maintenance plan
specifies that backup files are to be removed every 2 days. That's not
happening?
Why would that be? I mean, why would part of the maintenance plan (the
backing up of the databases) work but another part of the plan (the removal
of the database files) not work?
Thanks!
childofthe1980sHere is a very good overview as to why this may not work some times fro Bill
at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Thanks
Hari
"childofthe1980s" wrote:

> Hello:
> I have a few ideas about what to do on this. But, I still would like to
> solicit some opinions, if you don't mind.
> We have a SQL Server 2000 client who has a maintenance plan that conducts
a
> backup of its databases. And, each database is using the Full Recovery Mo
del.
> The backup of the databases itself is working perfectly. But, the backup
> files (bak files) are not being removed. You see, the maintenance plan
> specifies that backup files are to be removed every 2 days. That's not
> happening?
> Why would that be? I mean, why would part of the maintenance plan (the
> backing up of the databases) work but another part of the plan (the remova
l
> of the database files) not work?
> Thanks!
> childofthe1980s

backup files not deleting

Hello:
I have a few ideas about what to do on this. But, I still would like to
solicit some opinions, if you don't mind.
We have a SQL Server 2000 client who has a maintenance plan that conducts a
backup of its databases. And, each database is using the Full Recovery Model.
The backup of the databases itself is working perfectly. But, the backup
files (bak files) are not being removed. You see, the maintenance plan
specifies that backup files are to be removed every 2 days. That's not
happening?
Why would that be? I mean, why would part of the maintenance plan (the
backing up of the databases) work but another part of the plan (the removal
of the database files) not work?
Thanks!
childofthe1980sHere is a very good overview as to why this may not work some times fro Bill
at MS:
-- Log files don't delete --
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Thanks
Hari
"childofthe1980s" wrote:
> Hello:
> I have a few ideas about what to do on this. But, I still would like to
> solicit some opinions, if you don't mind.
> We have a SQL Server 2000 client who has a maintenance plan that conducts a
> backup of its databases. And, each database is using the Full Recovery Model.
> The backup of the databases itself is working perfectly. But, the backup
> files (bak files) are not being removed. You see, the maintenance plan
> specifies that backup files are to be removed every 2 days. That's not
> happening?
> Why would that be? I mean, why would part of the maintenance plan (the
> backing up of the databases) work but another part of the plan (the removal
> of the database files) not work?
> Thanks!
> childofthe1980s

Saturday, February 25, 2012

Backup of database fails ...

Backup of database fails ...

Friday, February 10, 2012

backup files not deleting

backup files not deleting

sql backup files

Blog Archive

About Me