Because of a corrupt mainboard we tried to restore our SQL Server 7
databases to a new computer but get the same error for all backups we
try to restore:
---
ODBC: Nachr.-Nr. 0, Schweregrad 19, Status 1
SqlDumpExceptionHandler: Prozess 21 erzeugte eine schwere
Ausnahmebedingung c0000005 EXCEPTION_ACCESS_VIOLATION.Sql Server
beendet diesen Prozess.
---
The Windows event log shows an event ID 17052. What can be wrong?I check out www.eventid.net for this issue and found something about it and
wanted to share with you. Maybe you can find something useful.
From www.EventId.net
Adrian Grigorof (Last update 1/4/2005):
This appears to be a generic event that can be recorded by the MS SQL Server
service for a wide range of problems. See the information for various errors
(ordered by the error number).
Error: 0, Description: SqlDumpExceptionHandler: Process 10 generated fatal
exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating
this process. - This type of error indicates a bug in one of the MS SQL
Server binaries. Installation of the latest service pack recommended. If
that does not fix it then call Microsoft Product support. Some newsgroup
postings suggest that this may occur due to lack of space on drive
containing the SQL logs
Event ID: 17052
Source MSSQLSERVER
Type Error
Description You do not have sufficient operating system permission to open
the SQLServerAgent status event.
Comments Adrian Grigorof (Last update 7/28/2004):
From a newsgroup post: "Installing SP3 or SP3a on MS SQL Server 2000
Enterprise Edition caused this problem in my case (MSSQLServer service is
running under different local user account than the SqlServerAgent service
and MSSQLServer is not given Administrator privileges). I see this buggy
behavior on various installations: W2K Advanced Server SP4 or W2K3. SP3 or
SP3a. Default instance or named instance. New freshly installed server or
old one. The only condition is that the MSSQLServer and SQLServerAgent
services run with different user accounts and the MSSQLServer
one does not have admin rights. Before SP3 installation everything runs OK.
What helps: Add MSSQLServer service account to Administrators group. OR Run
MSSQLServer and SQLServerAgent with the same account.
What doesn't help: Changing the services' user accounts using Enterprise
Manager. Add services' accounts to Power Users."
An answer from a MS engineer in a newsgroup post: "I suspect that the issue
is addressed in the cross-database ownership chain which uses in Microsoft
SQL Server Service Pack 3 (SP3). Based on my research, SP3 provides a new
security enhancement related option for configuring cross-database ownership
chaining; enable cross-database ownership chaining for all databases during
setup. With this new option, you can control whether or not you permit
cross-database ownership chaining. By default, this option is disabled.
Microsoft recommends that you use the default option, because it makes your
database server more secure.
However, database objects may have different owners. When an object such as
a view, a stored procedure, or a user-defined function references another
object, an ownership chain can be established. When the ownership chain is
unbroken, SQL Server checks permissions on the source object but not on the
target objects.
Therefore, it is recommended that you change the configuration of the
cross-database ownership chaining. You can reference the following
step-by-step article to perform such a change: M810474 (Cross-Database
Ownership Chaining Behavior Changes in SQL Server).
Additionally, I also suggest you running the MSSQLServer service with a
local account and
SQLServerAgent with Admin privilege to see if the jobs work fine. Otherwise,
it seems that you
should run these both services with the FULL privileges."
From a newsgroup post: "This is most likely a permissions issue. Make sure
the account SQLAgent starting under has permissions to:
- Replace A process level token
- Increase Quotas
- Logon as a service.
Books online states that the account needs to be a member of the local
admins group as well."
Anonymous (Last update 7/28/2004):
I got this error after I have created different accounts for sqlserver and
sqlagent service.
Ekrem Önsoy
"dentaku" <dentaku@.web.de> wrote in message
news:1189672135.231927.120740@.d55g2000hsg.googlegroups.com...
> Because of a corrupt mainboard we tried to restore our SQL Server 7
> databases to a new computer but get the same error for all backups we
> try to restore:
> ---
> ODBC: Nachr.-Nr. 0, Schweregrad 19, Status 1
> SqlDumpExceptionHandler: Prozess 21 erzeugte eine schwere
> Ausnahmebedingung c0000005 EXCEPTION_ACCESS_VIOLATION.Sql Server
> beendet diesen Prozess.
> ---
> The Windows event log shows an event ID 17052. What can be wrong?
>|||We have plenty of free disk and memory space (multiple GBs). We also
have the latest microsoft service packs and updates. And our DB user
is an admin (DBO rights didn't help either).
All restore verifyonly/filelistonly/headeronly requests returned no
error. But every time I try to restore the database (file) I get this
error and the sql error log files says
Bypassing recovery for database 'mine' because it is marked IN LOAD.
I can delete this database, and restore again, but with always the
same error.
Showing posts with label corrupt. Show all posts
Showing posts with label corrupt. Show all posts
Friday, March 30, 2012
RESTORE WITH VERIFYONLY Problem
Hi there,
I am having a problem with Microsoft SQL Server 2000, a copy of one of
my backups was corrupt, which I only discovered on the server I wanted
to res. Running the RESTORE WITH VERIFYONLY gave me the standard error
about there being an issue with the media set/family, which I could
accept.
However when I then opened query analyser against the original server
and ran the verifyonly restore command (and I have done it twice with
different results).
Myself and a colleague ran this against the original server and
received very odd messages. They received a weird error like this:
Command Issued:
RESTORE WITH ONLY Disk='C:\abc.BAK'
And received a error back saying that it could not find the file 'X:
\db_files\C:\abc.BAK' (where X:\db_files is the actual path where the
db files are kept!!!)
Later on, I ran the same command however, this time I received an
error telling me that the device was an invalid tape object! I was
running the same command, with the DISK='<drive>:\XYZ.BAK'
Has anyone ever seen something like this?
Obviously the error numbers would be useful here, but I don't have
these on me at the moment.
Any help appreciated.On Jan 29, 9:32 pm, Marc <mvandenhee...@.gmail.com> wrote:
> Hi there,
> I am having a problem with Microsoft SQL Server 2000, a copy of one of
> my backups was corrupt, which I only discovered on the server I wanted
> to res. Running the RESTORE WITH VERIFYONLY gave me the standard error
> about there being an issue with the media set/family, which I could
> accept.
> However when I then opened query analyser against the original server
> and ran the verifyonly restore command (and I have done it twice with
> different results).
> Myself and a colleague ran this against the original server and
> received very odd messages. They received a weird error like this:
> Command Issued:
> RESTORE WITH ONLY Disk='C:\abc.BAK'
> And received a error back saying that it could not find the file 'X:
> \db_files\C:\abc.BAK' (where X:\db_files is the actual path where the
> db files are kept!!!)
> Later on, I ran the same command however, this time I received an
> error telling me that the device was an invalid tape object! I was
> running the same command, with the DISK='<drive>:\XYZ.BAK'
> Has anyone ever seen something like this?
> Obviously the error numbers would be useful here, but I don't have
> these on me at the moment.
> Any help appreciated.
Also I should of added that SP 4 has been applied on this server...|||Mark
What is it ? T_SQL?
RESTORE WITH ONLY Disk='C:\abc.BAK'
Perhaps you meant
RESTORE VERIFYONLY FROM DISK = 'C:\abc.BAK'
"Marc" <mvandenheever@.gmail.com> wrote in message
news:12a10458-6e70-4817-b7a4-edf360167106@.d4g2000prg.googlegroups.com...
> Hi there,
> I am having a problem with Microsoft SQL Server 2000, a copy of one of
> my backups was corrupt, which I only discovered on the server I wanted
> to res. Running the RESTORE WITH VERIFYONLY gave me the standard error
> about there being an issue with the media set/family, which I could
> accept.
> However when I then opened query analyser against the original server
> and ran the verifyonly restore command (and I have done it twice with
> different results).
> Myself and a colleague ran this against the original server and
> received very odd messages. They received a weird error like this:
> Command Issued:
>
> RESTORE WITH ONLY Disk='C:\abc.BAK'
> And received a error back saying that it could not find the file 'X:
> \db_files\C:\abc.BAK' (where X:\db_files is the actual path where the
> db files are kept!!!)
> Later on, I ran the same command however, this time I received an
> error telling me that the device was an invalid tape object! I was
> running the same command, with the DISK='<drive>:\XYZ.BAK'
> Has anyone ever seen something like this?
> Obviously the error numbers would be useful here, but I don't have
> these on me at the moment.
> Any help appreciated.
>
>|||On Jan 29, 9:43 pm, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Mark
> What is it ? T_SQL?RESTOREWITH ONLY Disk='C:\abc.BAK'
> Perhaps you meantRESTOREVERIFYONLYFROM DISK = 'C:\abc.BAK'
> "Marc" <mvandenhee...@.gmail.com> wrote in message
> news:12a10458-6e70-4817-b7a4-edf360167106@.d4g2000prg.googlegroups.com...
> > Hi there,
> > I am having a problem with Microsoft SQL Server 2000, a copy of one of
> > my backups was corrupt, which I only discovered on the server I wanted
> > to res. Running theRESTOREWITHVERIFYONLYgave me the standard error
> > about there being an issue with the media set/family, which I could
> > accept.
> > However when I then opened query analyser against the original server
> > and ran theverifyonlyrestorecommand (and I have done it twice with
> > different results).
> > Myself and a colleague ran this against the original server and
> > received very odd messages. They received a weird error like this:
> > Command Issued:
> >RESTOREWITH ONLY Disk='C:\abc.BAK'
> > And received a error back saying that it could not find the file 'X:
> > \db_files\C:\abc.BAK' (where X:\db_files is the actual path where the
> > db files are kept!!!)
> > Later on, I ran the same command however, this time I received an
> > error telling me that the device was an invalid tape object! I was
> > running the same command, with the DISK='<drive>:\XYZ.BAK'
> > Has anyone ever seen something like this?
> > Obviously the error numbers would be useful here, but I don't have
> > these on me at the moment.
> > Any help appreciated.
Yes sorry that is simply a typo...
I am having a problem with Microsoft SQL Server 2000, a copy of one of
my backups was corrupt, which I only discovered on the server I wanted
to res. Running the RESTORE WITH VERIFYONLY gave me the standard error
about there being an issue with the media set/family, which I could
accept.
However when I then opened query analyser against the original server
and ran the verifyonly restore command (and I have done it twice with
different results).
Myself and a colleague ran this against the original server and
received very odd messages. They received a weird error like this:
Command Issued:
RESTORE WITH ONLY Disk='C:\abc.BAK'
And received a error back saying that it could not find the file 'X:
\db_files\C:\abc.BAK' (where X:\db_files is the actual path where the
db files are kept!!!)
Later on, I ran the same command however, this time I received an
error telling me that the device was an invalid tape object! I was
running the same command, with the DISK='<drive>:\XYZ.BAK'
Has anyone ever seen something like this?
Obviously the error numbers would be useful here, but I don't have
these on me at the moment.
Any help appreciated.On Jan 29, 9:32 pm, Marc <mvandenhee...@.gmail.com> wrote:
> Hi there,
> I am having a problem with Microsoft SQL Server 2000, a copy of one of
> my backups was corrupt, which I only discovered on the server I wanted
> to res. Running the RESTORE WITH VERIFYONLY gave me the standard error
> about there being an issue with the media set/family, which I could
> accept.
> However when I then opened query analyser against the original server
> and ran the verifyonly restore command (and I have done it twice with
> different results).
> Myself and a colleague ran this against the original server and
> received very odd messages. They received a weird error like this:
> Command Issued:
> RESTORE WITH ONLY Disk='C:\abc.BAK'
> And received a error back saying that it could not find the file 'X:
> \db_files\C:\abc.BAK' (where X:\db_files is the actual path where the
> db files are kept!!!)
> Later on, I ran the same command however, this time I received an
> error telling me that the device was an invalid tape object! I was
> running the same command, with the DISK='<drive>:\XYZ.BAK'
> Has anyone ever seen something like this?
> Obviously the error numbers would be useful here, but I don't have
> these on me at the moment.
> Any help appreciated.
Also I should of added that SP 4 has been applied on this server...|||Mark
What is it ? T_SQL?
RESTORE WITH ONLY Disk='C:\abc.BAK'
Perhaps you meant
RESTORE VERIFYONLY FROM DISK = 'C:\abc.BAK'
"Marc" <mvandenheever@.gmail.com> wrote in message
news:12a10458-6e70-4817-b7a4-edf360167106@.d4g2000prg.googlegroups.com...
> Hi there,
> I am having a problem with Microsoft SQL Server 2000, a copy of one of
> my backups was corrupt, which I only discovered on the server I wanted
> to res. Running the RESTORE WITH VERIFYONLY gave me the standard error
> about there being an issue with the media set/family, which I could
> accept.
> However when I then opened query analyser against the original server
> and ran the verifyonly restore command (and I have done it twice with
> different results).
> Myself and a colleague ran this against the original server and
> received very odd messages. They received a weird error like this:
> Command Issued:
>
> RESTORE WITH ONLY Disk='C:\abc.BAK'
> And received a error back saying that it could not find the file 'X:
> \db_files\C:\abc.BAK' (where X:\db_files is the actual path where the
> db files are kept!!!)
> Later on, I ran the same command however, this time I received an
> error telling me that the device was an invalid tape object! I was
> running the same command, with the DISK='<drive>:\XYZ.BAK'
> Has anyone ever seen something like this?
> Obviously the error numbers would be useful here, but I don't have
> these on me at the moment.
> Any help appreciated.
>
>|||On Jan 29, 9:43 pm, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Mark
> What is it ? T_SQL?RESTOREWITH ONLY Disk='C:\abc.BAK'
> Perhaps you meantRESTOREVERIFYONLYFROM DISK = 'C:\abc.BAK'
> "Marc" <mvandenhee...@.gmail.com> wrote in message
> news:12a10458-6e70-4817-b7a4-edf360167106@.d4g2000prg.googlegroups.com...
> > Hi there,
> > I am having a problem with Microsoft SQL Server 2000, a copy of one of
> > my backups was corrupt, which I only discovered on the server I wanted
> > to res. Running theRESTOREWITHVERIFYONLYgave me the standard error
> > about there being an issue with the media set/family, which I could
> > accept.
> > However when I then opened query analyser against the original server
> > and ran theverifyonlyrestorecommand (and I have done it twice with
> > different results).
> > Myself and a colleague ran this against the original server and
> > received very odd messages. They received a weird error like this:
> > Command Issued:
> >RESTOREWITH ONLY Disk='C:\abc.BAK'
> > And received a error back saying that it could not find the file 'X:
> > \db_files\C:\abc.BAK' (where X:\db_files is the actual path where the
> > db files are kept!!!)
> > Later on, I ran the same command however, this time I received an
> > error telling me that the device was an invalid tape object! I was
> > running the same command, with the DISK='<drive>:\XYZ.BAK'
> > Has anyone ever seen something like this?
> > Obviously the error numbers would be useful here, but I don't have
> > these on me at the moment.
> > Any help appreciated.
Yes sorry that is simply a typo...
Friday, March 23, 2012
Restore sql server database
I did one complete backup, and two transaction log backups.
The first of log backups is corrupt.
So I have to make a restore with the complete backup and only the
second log backup.
Is it possible?
Thanks.Hi,
if any of u r log backup is corrupt u cant restore subsequential log back
files.
Amol Lembhe
"giminera@.libero.it" wrote:
> I did one complete backup, and two transaction log backups.
> The first of log backups is corrupt.
> So I have to make a restore with the complete backup and only the
> second log backup.
> Is it possible?
> Thanks.
>
The first of log backups is corrupt.
So I have to make a restore with the complete backup and only the
second log backup.
Is it possible?
Thanks.Hi,
if any of u r log backup is corrupt u cant restore subsequential log back
files.
Amol Lembhe
"giminera@.libero.it" wrote:
> I did one complete backup, and two transaction log backups.
> The first of log backups is corrupt.
> So I have to make a restore with the complete backup and only the
> second log backup.
> Is it possible?
> Thanks.
>
Restore sql server database
I did one complete backup, and two transaction log backups.
The first of log backups is corrupt.
So I have to make a restore with the complete backup and only the
second log backup.
Is it possible?
Thanks.Hi,
if any of u r log backup is corrupt u cant restore subsequential log back
files.
Amol Lembhe
"giminera@.libero.it" wrote:
> I did one complete backup, and two transaction log backups.
> The first of log backups is corrupt.
> So I have to make a restore with the complete backup and only the
> second log backup.
> Is it possible?
> Thanks.
>
The first of log backups is corrupt.
So I have to make a restore with the complete backup and only the
second log backup.
Is it possible?
Thanks.Hi,
if any of u r log backup is corrupt u cant restore subsequential log back
files.
Amol Lembhe
"giminera@.libero.it" wrote:
> I did one complete backup, and two transaction log backups.
> The first of log backups is corrupt.
> So I have to make a restore with the complete backup and only the
> second log backup.
> Is it possible?
> Thanks.
>
Wednesday, March 7, 2012
Restore of backup fails, backup file corrupt?
We made a backup of one of our databases. The backup was done to disk. First a full backup and then differentials. When we try to restore this backup we run into problems... The restore of the full backup works without problems, the first differential (#2 in the backup set) can also be restored without problems. But when we try to restore one of the other sets (3 -> 31) we get the following errors:
"Server: Msg 3136, Level 16, State 1, Line
Cannot apply the backup on device 'e:\voyager.bak' to database 'Voyagerback'
Server: Msg 3013, Level 16, State 1, Line
RESTORE DATABASE is terminating abnormally.
I pasted the commands we use to restore the backup and their results below. Are we doing anything wrong? Is there any way to verify the integrity of a backup file besides VERIFYONLY (which tells us that the backup is ok)
Thanks
Stijn
RESTORE HEADERONL
FROM DISK='e:\voyager.bak
NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25 11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 3549184 56000000003700001 56000000003900001 56000000003700001 49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 206848 115000000034600001 115000000034800001 115000000034600001 115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 3942400 144000000031100001 144000000031300001 144000000031100001 115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
//cut some lines out to save spac
NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000 166209536 2868000000025300001 2868000000025500001 2868000000025300001 154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 175319040 2984000000024100001 2984000000030800001 2984000000024100001 154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 198846464 3358000000038400001 3358000000038600001 3358000000038400001 154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
--
RESTORE FILELISTONL
FROM DISK='e:\voyager.bak
Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880 3518437208064
Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 3518437208064
--
RESTORE VERIFYONL
FROM DISK='e:\voyager.bak
WITH FILE=3
The backup set is valid
--
RESTORE DATABASE Voyagerbac
FROM DISK='e:\voyager.bak
WITH NORECOVERY
MOVE 'Voyager_dat' TO 'e:\voyager.mdf'
MOVE 'Voyager_log' TO 'e:\voyager.ldf
Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file 1
Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file 1
RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865 MB/sec).
--
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH FILE=31,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
Server: Msg 3136, Level 16, State 1, Line 1
Cannot apply the backup on device 'e:\voyager.bak' to database 'Voyagerback'.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.Stijn
Try to specify
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH FILE=31,
RECOVERY,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
"Stijn" <anonymous@.discussions.microsoft.com> wrote in message
news:B56E7D6D-49C3-4C50-B2D0-F43980DF3949@.microsoft.com...
> We made a backup of one of our databases. The backup was done to disk.
First a full backup and then differentials. When we try to restore this
backup we run into problems... The restore of the full backup works without
problems, the first differential (#2 in the backup set) can also be restored
without problems. But when we try to restore one of the other sets (3 ->
31) we get the following errors:
> "Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally."
> I pasted the commands we use to restore the backup and their results
below. Are we doing anything wrong? Is there any way to verify the
integrity of a backup file besides VERIFYONLY (which tells us that the
backup is ok)?
> Thanks!
> Stijn.
>
> RESTORE HEADERONLY
> FROM DISK='e:\voyager.bak'
> NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25
11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194
W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3549184 56000000003700001 56000000003900001 56000000003700001
49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
206848 115000000034600001 115000000034800001 115000000034600001
115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3942400 144000000031100001 144000000031300001 144000000031100001
115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> //cut some lines out to save space
> NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000
166209536 2868000000025300001 2868000000025500001 2868000000025300001
154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
175319040 2984000000024100001 2984000000030800001 2984000000024100001
154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
198846464 3358000000038400001 3358000000038600001 3358000000038400001
154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
>
> --
> RESTORE FILELISTONLY
> FROM DISK='e:\voyager.bak'
> Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880
35184372080640
> Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
> --
> RESTORE VERIFYONLY
> FROM DISK='e:\voyager.bak'
> WITH FILE=31
> The backup set is valid.
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH NORECOVERY,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file
1.
> Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file
1.
> RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865
MB/sec).
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH FILE=31,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
>|||Same problem with the RECOVERY option..
Anyway thanks for your reply!|||I would check the backup history tables in msdb, perhaps someone did a
database backup to some other backupdevice between number 2 and number 3 on
your backup device? Watch out for VERIFYONLY. It basically only verifies
that the file/tape is readable. Only way to do a proper verification is to
do an actual restore. Yukon will be better in this aspect.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Stijn" <anonymous@.discussions.microsoft.com> wrote in message
news:B56E7D6D-49C3-4C50-B2D0-F43980DF3949@.microsoft.com...
> We made a backup of one of our databases. The backup was done to disk.
First a full backup and then differentials. When we try to restore this
backup we run into problems... The restore of the full backup works without
problems, the first differential (#2 in the backup set) can also be restored
without problems. But when we try to restore one of the other sets (3 ->
31) we get the following errors:
> "Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally."
> I pasted the commands we use to restore the backup and their results
below. Are we doing anything wrong? Is there any way to verify the
integrity of a backup file besides VERIFYONLY (which tells us that the
backup is ok)?
> Thanks!
> Stijn.
>
> RESTORE HEADERONLY
> FROM DISK='e:\voyager.bak'
> NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25
11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194
W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3549184 56000000003700001 56000000003900001 56000000003700001
49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
206848 115000000034600001 115000000034800001 115000000034600001
115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3942400 144000000031100001 144000000031300001 144000000031100001
115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> //cut some lines out to save space
> NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000
166209536 2868000000025300001 2868000000025500001 2868000000025300001
154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
175319040 2984000000024100001 2984000000030800001 2984000000024100001
154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
198846464 3358000000038400001 3358000000038600001 3358000000038400001
154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
>
> --
> RESTORE FILELISTONLY
> FROM DISK='e:\voyager.bak'
> Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880
35184372080640
> Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
> --
> RESTORE VERIFYONLY
> FROM DISK='e:\voyager.bak'
> WITH FILE=31
> The backup set is valid.
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH NORECOVERY,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file
1.
> Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file
1.
> RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865
MB/sec).
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH FILE=31,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
>
"Server: Msg 3136, Level 16, State 1, Line
Cannot apply the backup on device 'e:\voyager.bak' to database 'Voyagerback'
Server: Msg 3013, Level 16, State 1, Line
RESTORE DATABASE is terminating abnormally.
I pasted the commands we use to restore the backup and their results below. Are we doing anything wrong? Is there any way to verify the integrity of a backup file besides VERIFYONLY (which tells us that the backup is ok)
Thanks
Stijn
RESTORE HEADERONL
FROM DISK='e:\voyager.bak
NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25 11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 3549184 56000000003700001 56000000003900001 56000000003700001 49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 206848 115000000034600001 115000000034800001 115000000034600001 115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 3942400 144000000031100001 144000000031300001 144000000031100001 115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
//cut some lines out to save spac
NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000 166209536 2868000000025300001 2868000000025500001 2868000000025300001 154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 175319040 2984000000024100001 2984000000030800001 2984000000024100001 154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 198846464 3358000000038400001 3358000000038600001 3358000000038400001 154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228 1033 196609 80 4608 8 0 194 W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_A
--
RESTORE FILELISTONL
FROM DISK='e:\voyager.bak
Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880 3518437208064
Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 3518437208064
--
RESTORE VERIFYONL
FROM DISK='e:\voyager.bak
WITH FILE=3
The backup set is valid
--
RESTORE DATABASE Voyagerbac
FROM DISK='e:\voyager.bak
WITH NORECOVERY
MOVE 'Voyager_dat' TO 'e:\voyager.mdf'
MOVE 'Voyager_log' TO 'e:\voyager.ldf
Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file 1
Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file 1
RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865 MB/sec).
--
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH FILE=31,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
Server: Msg 3136, Level 16, State 1, Line 1
Cannot apply the backup on device 'e:\voyager.bak' to database 'Voyagerback'.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.Stijn
Try to specify
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH FILE=31,
RECOVERY,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
"Stijn" <anonymous@.discussions.microsoft.com> wrote in message
news:B56E7D6D-49C3-4C50-B2D0-F43980DF3949@.microsoft.com...
> We made a backup of one of our databases. The backup was done to disk.
First a full backup and then differentials. When we try to restore this
backup we run into problems... The restore of the full backup works without
problems, the first differential (#2 in the backup set) can also be restored
without problems. But when we try to restore one of the other sets (3 ->
31) we get the following errors:
> "Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally."
> I pasted the commands we use to restore the backup and their results
below. Are we doing anything wrong? Is there any way to verify the
integrity of a backup file besides VERIFYONLY (which tells us that the
backup is ok)?
> Thanks!
> Stijn.
>
> RESTORE HEADERONLY
> FROM DISK='e:\voyager.bak'
> NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25
11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194
W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3549184 56000000003700001 56000000003900001 56000000003700001
49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
206848 115000000034600001 115000000034800001 115000000034600001
115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3942400 144000000031100001 144000000031300001 144000000031100001
115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> //cut some lines out to save space
> NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000
166209536 2868000000025300001 2868000000025500001 2868000000025300001
154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
175319040 2984000000024100001 2984000000030800001 2984000000024100001
154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
198846464 3358000000038400001 3358000000038600001 3358000000038400001
154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
>
> --
> RESTORE FILELISTONLY
> FROM DISK='e:\voyager.bak'
> Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880
35184372080640
> Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
> --
> RESTORE VERIFYONLY
> FROM DISK='e:\voyager.bak'
> WITH FILE=31
> The backup set is valid.
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH NORECOVERY,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file
1.
> Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file
1.
> RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865
MB/sec).
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH FILE=31,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
>|||Same problem with the RECOVERY option..
Anyway thanks for your reply!|||I would check the backup history tables in msdb, perhaps someone did a
database backup to some other backupdevice between number 2 and number 3 on
your backup device? Watch out for VERIFYONLY. It basically only verifies
that the file/tape is readable. Only way to do a proper verification is to
do an actual restore. Yukon will be better in this aspect.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Stijn" <anonymous@.discussions.microsoft.com> wrote in message
news:B56E7D6D-49C3-4C50-B2D0-F43980DF3949@.microsoft.com...
> We made a backup of one of our databases. The backup was done to disk.
First a full backup and then differentials. When we try to restore this
backup we run into problems... The restore of the full backup works without
problems, the first differential (#2 in the backup set) can also be restored
without problems. But when we try to restore one of the other sets (3 ->
31) we get the following errors:
> "Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally."
> I pasted the commands we use to restore the backup and their results
below. Are we doing anything wrong? Is there any way to verify the
integrity of a backup file besides VERIFYONLY (which tells us that the
backup is ok)?
> Thanks!
> Stijn.
>
> RESTORE HEADERONLY
> FROM DISK='e:\voyager.bak'
> NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25
11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194
W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3549184 56000000003700001 56000000003900001 56000000003700001
49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
206848 115000000034600001 115000000034800001 115000000034600001
115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3942400 144000000031100001 144000000031300001 144000000031100001
115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> //cut some lines out to save space
> NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000
166209536 2868000000025300001 2868000000025500001 2868000000025300001
154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
175319040 2984000000024100001 2984000000030800001 2984000000024100001
154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
198846464 3358000000038400001 3358000000038600001 3358000000038400001
154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
>
> --
> RESTORE FILELISTONLY
> FROM DISK='e:\voyager.bak'
> Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880
35184372080640
> Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
> --
> RESTORE VERIFYONLY
> FROM DISK='e:\voyager.bak'
> WITH FILE=31
> The backup set is valid.
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH NORECOVERY,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file
1.
> Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file
1.
> RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865
MB/sec).
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH FILE=31,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
>
Restore of backup fails, backup file corrupt?
We made a backup of one of our databases. The backup was done to disk. Fir
st a full backup and then differentials. When we try to restore this backup
we run into problems... The restore of the full backup works without probl
ems, the first differential
(#2 in the backup set) can also be restored without problems. But when we t
ry to restore one of the other sets (3 -> 31) we get the following errors:
"Server: Msg 3136, Level 16, State 1, Line 1
Cannot apply the backup on device 'e:\voyager.bak' to database 'Voyagerback'
.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally."
I pasted the commands we use to restore the backup and their results below.
Are we doing anything wrong? Is there any way to verify the integrity of a
backup file besides VERIFYONLY (which tells us that the backup is ok)?
Thanks!
Stijn.
RESTORE HEADERONLY
FROM DISK='e:\voyager.bak'
NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 51891
20 49000000034700001 49000000035100001 4
9000000034700003 0 2002-09-25 11:16:
01.000 2002-09-25 11:16:02. 000 52 228 1033 196609 80 4608 8 0 194 W
-UNION1 0
{1362433B-7E4A-465F-A852-C
76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_C
I_AS
NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 35491
84 56000000003700001 56000000003900001 5
6000000003700001 49000000034700003 2
002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228 1033 196609 80 4608 8
0 194 W-UNION1 0 {1362433B-
7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Lati
n1_General_CP1_CI_AS
NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 20684
8 115000000034600001 115000000034800001
115000000034600001 11500000003390000
3 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228 1033 196609 80 4608
8 0 194 W-UNION1 0 {136243
3B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_L
atin1_General_CP1_CI_AS
NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 39424
00 144000000031100001 144000000031300001
144000000031100001 1150000000339000
03 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228 1033 196609 80 460
8 8 0 194 W-UNION1 0 {13624
33B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_
Latin1_General_CP1_CI_AS
//cut some lines out to save space
NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000 1662
09536 2868000000025300001 28680000000255
00001 2868000000025300001 1540000000
51100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228 1033 196609
80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF
} SQL_Latin1_General_CP1_CI_AS
NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 1753
19040 2984000000024100001 29840000000308
00001 2984000000024100001 1540000000
51100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228 1033 196609
80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF
} SQL_Latin1_General_CP1_CI_AS
NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 1988
46464 3358000000038400001 33580000000386
00001 3358000000038400001 1540000000
51100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228 1033 196609
80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF
} SQL_Latin1_General_CP1_CI_AS
RESTORE FILELISTONLY
FROM DISK='e:\voyager.bak'
Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880 35184372080640
Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
RESTORE VERIFYONLY
FROM DISK='e:\voyager.bak'
WITH FILE=31
The backup set is valid.
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH NORECOVERY,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file 1
.
Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file 1.
RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865 MB
/sec).
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH FILE=31,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
Server: Msg 3136, Level 16, State 1, Line 1
Cannot apply the backup on device 'e:\voyager.bak' to database 'Voyagerback'
.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.Stijn
Try to specify
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH FILE=31,
RECOVERY,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
"Stijn" <anonymous@.discussions.microsoft.com> wrote in message
news:B56E7D6D-49C3-4C50-B2D0-F43980DF3949@.microsoft.com...
> We made a backup of one of our databases. The backup was done to disk.
First a full backup and then differentials. When we try to restore this
backup we run into problems... The restore of the full backup works without
problems, the first differential (#2 in the backup set) can also be restored
without problems. But when we try to restore one of the other sets (3 ->
31) we get the following errors:
> "Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally."
> I pasted the commands we use to restore the backup and their results
below. Are we doing anything wrong? Is there any way to verify the
integrity of a backup file besides VERIFYONLY (which tells us that the
backup is ok)?
> Thanks!
> Stijn.
>
> RESTORE HEADERONLY
> FROM DISK='e:\voyager.bak'
> NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25
11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194
W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3549184 56000000003700001 56000000003900001 56000000003700001
49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
206848 115000000034600001 115000000034800001 115000000034600001
115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3942400 144000000031100001 144000000031300001 144000000031100001
115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> //cut some lines out to save space
> NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000
166209536 2868000000025300001 2868000000025500001 2868000000025300001
154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
175319040 2984000000024100001 2984000000030800001 2984000000024100001
154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
198846464 3358000000038400001 3358000000038600001 3358000000038400001
154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
>
> --
> RESTORE FILELISTONLY
> FROM DISK='e:\voyager.bak'
> Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880
35184372080640
> Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
> --
> RESTORE VERIFYONLY
> FROM DISK='e:\voyager.bak'
> WITH FILE=31
> The backup set is valid.
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH NORECOVERY,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file
1.
> Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file
1.
> RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865
MB/sec).
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH FILE=31,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
>|||Same problem with the RECOVERY option...
Anyway thanks for your reply!|||I would check the backup history tables in msdb, perhaps someone did a
database backup to some other backupdevice between number 2 and number 3 on
your backup device? Watch out for VERIFYONLY. It basically only verifies
that the file/tape is readable. Only way to do a proper verification is to
do an actual restore. Yukon will be better in this aspect.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Stijn" <anonymous@.discussions.microsoft.com> wrote in message
news:B56E7D6D-49C3-4C50-B2D0-F43980DF3949@.microsoft.com...
> We made a backup of one of our databases. The backup was done to disk.
First a full backup and then differentials. When we try to restore this
backup we run into problems... The restore of the full backup works without
problems, the first differential (#2 in the backup set) can also be restored
without problems. But when we try to restore one of the other sets (3 ->
31) we get the following errors:
> "Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally."
> I pasted the commands we use to restore the backup and their results
below. Are we doing anything wrong? Is there any way to verify the
integrity of a backup file besides VERIFYONLY (which tells us that the
backup is ok)?
> Thanks!
> Stijn.
>
> RESTORE HEADERONLY
> FROM DISK='e:\voyager.bak'
> NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25
11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194
W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3549184 56000000003700001 56000000003900001 56000000003700001
49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
206848 115000000034600001 115000000034800001 115000000034600001
115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3942400 144000000031100001 144000000031300001 144000000031100001
115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> //cut some lines out to save space
> NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000
166209536 2868000000025300001 2868000000025500001 2868000000025300001
154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
175319040 2984000000024100001 2984000000030800001 2984000000024100001
154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
198846464 3358000000038400001 3358000000038600001 3358000000038400001
154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
>
> --
> RESTORE FILELISTONLY
> FROM DISK='e:\voyager.bak'
> Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880
35184372080640
> Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
> --
> RESTORE VERIFYONLY
> FROM DISK='e:\voyager.bak'
> WITH FILE=31
> The backup set is valid.
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH NORECOVERY,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file
1.
> Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file
1.
> RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865
MB/sec).
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH FILE=31,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
>
st a full backup and then differentials. When we try to restore this backup
we run into problems... The restore of the full backup works without probl
ems, the first differential
(#2 in the backup set) can also be restored without problems. But when we t
ry to restore one of the other sets (3 -> 31) we get the following errors:
"Server: Msg 3136, Level 16, State 1, Line 1
Cannot apply the backup on device 'e:\voyager.bak' to database 'Voyagerback'
.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally."
I pasted the commands we use to restore the backup and their results below.
Are we doing anything wrong? Is there any way to verify the integrity of a
backup file besides VERIFYONLY (which tells us that the backup is ok)?
Thanks!
Stijn.
RESTORE HEADERONLY
FROM DISK='e:\voyager.bak'
NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 51891
20 49000000034700001 49000000035100001 4
9000000034700003 0 2002-09-25 11:16:
01.000 2002-09-25 11:16:02. 000 52 228 1033 196609 80 4608 8 0 194 W
-UNION1 0
{1362433B-7E4A-465F-A852-C
76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_C
I_AS
NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 35491
84 56000000003700001 56000000003900001 5
6000000003700001 49000000034700003 2
002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228 1033 196609 80 4608 8
0 194 W-UNION1 0 {1362433B-
7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Lati
n1_General_CP1_CI_AS
NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 20684
8 115000000034600001 115000000034800001
115000000034600001 11500000003390000
3 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228 1033 196609 80 4608
8 0 194 W-UNION1 0 {136243
3B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_L
atin1_General_CP1_CI_AS
NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 39424
00 144000000031100001 144000000031300001
144000000031100001 1150000000339000
03 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228 1033 196609 80 460
8 8 0 194 W-UNION1 0 {13624
33B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_
Latin1_General_CP1_CI_AS
//cut some lines out to save space
NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000 1662
09536 2868000000025300001 28680000000255
00001 2868000000025300001 1540000000
51100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228 1033 196609
80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF
} SQL_Latin1_General_CP1_CI_AS
NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 1753
19040 2984000000024100001 29840000000308
00001 2984000000024100001 1540000000
51100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228 1033 196609
80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF
} SQL_Latin1_General_CP1_CI_AS
NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000 1988
46464 3358000000038400001 33580000000386
00001 3358000000038400001 1540000000
51100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228 1033 196609
80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF} {1362433B-7E4A-465F-A852-C76DF919B2BF
} SQL_Latin1_General_CP1_CI_AS
RESTORE FILELISTONLY
FROM DISK='e:\voyager.bak'
Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880 35184372080640
Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
RESTORE VERIFYONLY
FROM DISK='e:\voyager.bak'
WITH FILE=31
The backup set is valid.
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH NORECOVERY,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file 1
.
Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file 1.
RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865 MB
/sec).
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH FILE=31,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
Server: Msg 3136, Level 16, State 1, Line 1
Cannot apply the backup on device 'e:\voyager.bak' to database 'Voyagerback'
.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.Stijn
Try to specify
RESTORE DATABASE Voyagerback
FROM DISK='e:\voyager.bak'
WITH FILE=31,
RECOVERY,
MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
MOVE 'Voyager_log' TO 'e:\voyager.ldf'
"Stijn" <anonymous@.discussions.microsoft.com> wrote in message
news:B56E7D6D-49C3-4C50-B2D0-F43980DF3949@.microsoft.com...
> We made a backup of one of our databases. The backup was done to disk.
First a full backup and then differentials. When we try to restore this
backup we run into problems... The restore of the full backup works without
problems, the first differential (#2 in the backup set) can also be restored
without problems. But when we try to restore one of the other sets (3 ->
31) we get the following errors:
> "Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally."
> I pasted the commands we use to restore the backup and their results
below. Are we doing anything wrong? Is there any way to verify the
integrity of a backup file besides VERIFYONLY (which tells us that the
backup is ok)?
> Thanks!
> Stijn.
>
> RESTORE HEADERONLY
> FROM DISK='e:\voyager.bak'
> NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25
11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194
W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3549184 56000000003700001 56000000003900001 56000000003700001
49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
206848 115000000034600001 115000000034800001 115000000034600001
115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3942400 144000000031100001 144000000031300001 144000000031100001
115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> //cut some lines out to save space
> NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000
166209536 2868000000025300001 2868000000025500001 2868000000025300001
154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
175319040 2984000000024100001 2984000000030800001 2984000000024100001
154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
198846464 3358000000038400001 3358000000038600001 3358000000038400001
154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
>
> --
> RESTORE FILELISTONLY
> FROM DISK='e:\voyager.bak'
> Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880
35184372080640
> Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
> --
> RESTORE VERIFYONLY
> FROM DISK='e:\voyager.bak'
> WITH FILE=31
> The backup set is valid.
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH NORECOVERY,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file
1.
> Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file
1.
> RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865
MB/sec).
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH FILE=31,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
>|||Same problem with the RECOVERY option...
Anyway thanks for your reply!|||I would check the backup history tables in msdb, perhaps someone did a
database backup to some other backupdevice between number 2 and number 3 on
your backup device? Watch out for VERIFYONLY. It basically only verifies
that the file/tape is readable. Only way to do a proper verification is to
do an actual restore. Yukon will be better in this aspect.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Stijn" <anonymous@.discussions.microsoft.com> wrote in message
news:B56E7D6D-49C3-4C50-B2D0-F43980DF3949@.microsoft.com...
> We made a backup of one of our databases. The backup was done to disk.
First a full backup and then differentials. When we try to restore this
backup we run into problems... The restore of the full backup works without
problems, the first differential (#2 in the backup set) can also be restored
without problems. But when we try to restore one of the other sets (3 ->
31) we get the following errors:
> "Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally."
> I pasted the commands we use to restore the backup and their results
below. Are we doing anything wrong? Is there any way to verify the
integrity of a backup file besides VERIFYONLY (which tells us that the
backup is ok)?
> Thanks!
> Stijn.
>
> RESTORE HEADERONLY
> FROM DISK='e:\voyager.bak'
> NULL NULL 1 NULL 0 1 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
5189120 49000000034700001 49000000035100001 49000000034700003 0 2002-09-25
11:16:01.000 2002-09-25 11:16:02.000 52 228 1033 196609 80 4608 8 0 194
W-UNION1 0 {1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 2 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3549184 56000000003700001 56000000003900001 56000000003700001
49000000034700003 2002-09-24 11:52:27.000 2002-09-24 11:52:29.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 3 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
206848 115000000034600001 115000000034800001 115000000034600001
115000000033900003 2003-06-19 07:41:25.000 2003-06-19 07:41:25.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 4 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
3942400 144000000031100001 144000000031300001 144000000031100001
115000000033900003 2002-09-24 01:22:22.000 2002-09-24 01:22:23.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> //cut some lines out to save space
> NULL NULL 5 NULL 0 29 2 SA W-UNION1 Voyager 539 2002-09-25 03:50:21.000
166209536 2868000000025300001 2868000000025500001 2868000000025300001
154000000051100003 2004-01-09 13:39:07.000 2004-01-09 13:39:53.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 30 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
175319040 2984000000024100001 2984000000030800001 2984000000024100001
154000000051100003 2004-01-15 10:55:45.000 2004-01-15 10:56:09.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
> NULL NULL 5 NULL 0 31 2 sa W-UNION1 Voyager 539 2002-09-25 03:50:21.000
198846464 3358000000038400001 3358000000038600001 3358000000038400001
154000000051100003 2004-01-30 16:44:24.000 2004-01-30 16:44:49.000 52 228
1033 196609 80 4608 8 0 194 W-UNION1 0
{1362433B-7E4A-465F-A852-C76DF919B2BF}
{1362433B-7E4A-465F-A852-C76DF919B2BF} SQL_Latin1_General_CP1_CI_AS
>
> --
> RESTORE FILELISTONLY
> FROM DISK='e:\voyager.bak'
> Voyager_dat C:\MSDE\MSSQL\Data\Voyager.mdf D PRIMARY 5242880
35184372080640
> Voyager_log C:\MSDE\MSSQL\Data\Voyager.ldf L NULL 1048576 35184372080640
> --
> RESTORE VERIFYONLY
> FROM DISK='e:\voyager.bak'
> WITH FILE=31
> The backup set is valid.
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH NORECOVERY,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Processed 624 pages for database 'Voyagerback', file 'Voyager_dat' on file
1.
> Processed 1 pages for database 'Voyagerback', file 'Voyager_log' on file
1.
> RESTORE DATABASE successfully processed 625 pages in 1.051 seconds (4.865
MB/sec).
> --
> RESTORE DATABASE Voyagerback
> FROM DISK='e:\voyager.bak'
> WITH FILE=31,
> MOVE 'Voyager_dat' TO 'e:\voyager.mdf',
> MOVE 'Voyager_log' TO 'e:\voyager.ldf'
> Server: Msg 3136, Level 16, State 1, Line 1
> Cannot apply the backup on device 'e:\voyager.bak' to database
'Voyagerback'.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
>
Subscribe to:
Posts (Atom)