We are running SQL 2000 sp4, only one user database (SAP) the database is 63 GB.
The ldf files were trashed so I went to tape to restore.
We are using veritas backup exec 9.1 sp4. Veritas is on the same server. I can restore the master db and the msdb fine. However when we attempt to restore the DEV db it runs for 2 hours and then fails with a communication error from veritas.
When we restore the master the DEV db comes up suspect as there are no files for it to attach to) so we cannot attach to it to restore, so I have deleted it and attempted to restore - same communication error. I have recreated a db named DEV with the mdf etc created to the size needed plus some to be sure, no good same behavior (behavior described below).
The job starts and it creates all the folders for the database (there are 1 MDF, 5 NDF, and 4 LDF files each in its own folder). Then it begins to create teh individual files it gets ~half way through at about an hour-hour and fifteen. During this time there are a large number of writes being performed by SQL (I assume it is creating the structures). Then it switches over to reading from tape a large number of read by beengine for another 45-1.5 hours then the job fails with the error unable to communicate with the device. I ahve noticed that once it starts reading from tape the db is gone from enterprise manager, and the mdf etc. files that were being created are now gone.
Help this has gone on for three days!!!I advise my clients NEVER to use Veritas to backup databases. I have seen many occasions where the clients thought they were getting backups, but in fact were not.
My standard procedure is to use SQL Server tools to backup the databases and logs (that's what they were designed for...), and then use Veritas to backup the resulting files.
Call Veritas and see if they can help.|||I have been on the phone for two days off and on with them. We will be changing our procedure when we get past this. For 6 years we have had no problems backing up and restoring our databases...always a first time.:eek:|||SQL Server backups are so easy and reliable when scheduled through SQL Server Agent, I honestly don't know why anybody would use 3rd party software to do this.|||Point taken, however that is no help with where I am at now.|||Veritas sold you on using their backup tools, and the errors you are getting appear to be coming from Veritas, so I would keep tossing the ball back into their court.
When you get through this, I and others on the forum would be happy to advise you on setting up a more robust data recovery system.|||Thanks, we will be proceeding in that direction shortly after we get done...first some sleep though...hmmm and maybe a beer or two!!|||We do use LiteSpeed here blindman. :) It actually has worked wonders here. It still creates backup files, but they are 30% of the size and are produced twice as quick. Plus,the backups are encrypted when they are shipped off-site.
Veritas has burned me more times than I care to remember. I would NEVER use it to backup SQL Server. Also, I wouldn't use any third-party service that tries to backup the actual .mdf and .ldf files. As you stated, it's better to back them up using the Agent or something like LiteSpeed. Then, move those backup files to tape with Veritas, etc.|||Issue resolved, thanks for the comments. We will be looking into SQL backups starting next week.
Just in case anyone else hits this issue:
The problem was veritas was timing out attempting create the structures for the database. It uses VDI as the default connection to a db. The VDI is set to 25 minutes for a time out by default. CHange to named pipes and it works fine. HKEY Local machine\software\veritas\backupexec\engine\SQL Server\Force Named Pipe Backup/restore set this to 1 and restart services.
Follow on question:
THis was a 63 GB db and took 6 hours to create structures and restore data; ok it is a development system so not a huge issue. However our production SAP database is over 180 GB! What is the best way IYO to backup and restore a DB of this size - or should we be going with some sort of mirroring?|||mirrorring with some kind of raided drive is usually good but does not solve the problem of what happens when the office burns down.
without knowing more about your situation, I would say you should use a combination of full, differential and transaction log backups to another peice of hardware on your network and not directly to tape. This will be a little faster and will not be such a resource burden. Then you move these backups on this seperate machine to a tape drive connected to it.
It really all depends on your business needs and you should do a little reading on disaster recovery, but I would do a full backup on the weekends, maybe a differential every night during the witching hour and T-Log backups during the day to ensure full recovery.|||I would say make an investment in SQL LiteSpeed by Quest. It will allow your backups to run much faster and they will be much smaller. We have loved it since we purchased it.
Also, you might want to look at buying a faster disk set to backup on. If you had a seperate drive array that was 2 RAID 0 or 4 RAID 10 disks, you would find your backup speed go to minutes instead of hours. We backup hundreds of GB in less time than you take for the one database. We have a backup server with four RAID-10 drives. All backups on the network go to that share. Even with pushing them over the network, we are much faster than your solution.|||nanny nanny boo boo to you too
Showing posts with label fails. Show all posts
Showing posts with label fails. Show all posts
Wednesday, March 7, 2012
Restore of database fails
Hi,
I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
using the restore option with the UNC name (\\servername\G$\path\file), since
the restore is to be performed over the network (Novell) to a disk on the
remote computer. This however fails with OS error=5(access is denied). The
user who performs this operation is administrator on the computer. Could you
please inform why this is not possible and if there is a better way to
perform this operation.
Thanks!
Susanne
Hi Susanne
It's the account that runs the SQLServer service that needs to have access
to the UNC path. You can test the access by logging on to the server as the
user that runs the SQL server service and then verify that you now can get
to the file.
Regards
Steen
Susanne wrote:
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
> server by using the restore option with the UNC name
> (\\servername\G$\path\file), since the restore is to be performed
> over the network (Novell) to a disk on the remote computer. This
> however fails with OS error=5(access is denied). The user who
> performs this operation is administrator on the computer. Could you
> please inform why this is not possible and if there is a better way
> to perform this operation.
> Thanks!
> Susanne
|||That's exactly the point. I can access the file using Windows Exporer on the
server, however not when trying to restore the database (using SQL Enterprise
Manager).
"Steen Persson" wrote:
> Hi Susanne
> It's the account that runs the SQLServer service that needs to have access
> to the UNC path. You can test the access by logging on to the server as the
> user that runs the SQL server service and then verify that you now can get
> to the file.
> Regards
> Steen
> Susanne wrote:
>
>
|||Suzanne
We do this a lot and on the target SQL Server Machine set the logon in the
services startup properties to a domain user with access to the unc path (I
just used <domain>\Administrator)
evan
"Susanne" <Susanne@.discussions.microsoft.com> wrote in message
news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
> using the restore option with the UNC name (\\servername\G$\path\file),
since
> the restore is to be performed over the network (Novell) to a disk on the
> remote computer. This however fails with OS error=5(access is denied).
The
> user who performs this operation is administrator on the computer. Could
you
> please inform why this is not possible and if there is a better way to
> perform this operation.
> Thanks!
> Susanne
|||But then you have to change the account that runs the SQLServer srvice to an
account that has the access or grant the existing account the required
access. If you can't do that, you'll have to copy the files to the server
and then do the retstore from a local file.
Regards
Steen
Susanne wrote:[vbcol=seagreen]
> That's exactly the point. I can access the file using Windows Exporer
> on the server, however not when trying to restore the database (using
> SQL Enterprise Manager).
>
>
> "Steen Persson" wrote:
|||It is a comfort to read that this can be done. I have tried to restore, after
changing the logon for the SQL Server Manager to Administrator and restarting
the service, but it still doesn't work. I get the same error. Unfortunately,
there is not enough of space on the target server so I can run the restore
from a local disk.
"evan b" wrote:
> Suzanne
> We do this a lot and on the target SQL Server Machine set the logon in the
> services startup properties to a domain user with access to the unc path (I
> just used <domain>\Administrator)
> evan
> "Susanne" <Susanne@.discussions.microsoft.com> wrote in message
> news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> since
> The
> you
>
>
|||Hi Susanne
I have to admit that I don't know if there can be amy issues when you are
using a Novell network, but I doubt.
You say that you have changed the logon for SQL Server Manager, but what do
you mean with that? It's the account that runs the SQL Server Service that
you need to set to an account that has access to the share. When you have
done that, then log on to the server using tihs account and then verify that
you can access the share with that account. If it still doesn't work, then
try to post the code you are using - maybe there are something in you code
that isn't correct.
Regards
Steen
Susanne wrote:[vbcol=seagreen]
> It is a comfort to read that this can be done. I have tried to
> restore, after changing the logon for the SQL Server Manager to
> Administrator and restarting the service, but it still doesn't work.
> I get the same error. Unfortunately, there is not enough of space on
> the target server so I can run the restore from a local disk.
> "evan b" wrote:
I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
using the restore option with the UNC name (\\servername\G$\path\file), since
the restore is to be performed over the network (Novell) to a disk on the
remote computer. This however fails with OS error=5(access is denied). The
user who performs this operation is administrator on the computer. Could you
please inform why this is not possible and if there is a better way to
perform this operation.
Thanks!
Susanne
Hi Susanne
It's the account that runs the SQLServer service that needs to have access
to the UNC path. You can test the access by logging on to the server as the
user that runs the SQL server service and then verify that you now can get
to the file.
Regards
Steen
Susanne wrote:
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
> server by using the restore option with the UNC name
> (\\servername\G$\path\file), since the restore is to be performed
> over the network (Novell) to a disk on the remote computer. This
> however fails with OS error=5(access is denied). The user who
> performs this operation is administrator on the computer. Could you
> please inform why this is not possible and if there is a better way
> to perform this operation.
> Thanks!
> Susanne
|||That's exactly the point. I can access the file using Windows Exporer on the
server, however not when trying to restore the database (using SQL Enterprise
Manager).
"Steen Persson" wrote:
> Hi Susanne
> It's the account that runs the SQLServer service that needs to have access
> to the UNC path. You can test the access by logging on to the server as the
> user that runs the SQL server service and then verify that you now can get
> to the file.
> Regards
> Steen
> Susanne wrote:
>
>
|||Suzanne
We do this a lot and on the target SQL Server Machine set the logon in the
services startup properties to a domain user with access to the unc path (I
just used <domain>\Administrator)
evan
"Susanne" <Susanne@.discussions.microsoft.com> wrote in message
news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
> using the restore option with the UNC name (\\servername\G$\path\file),
since
> the restore is to be performed over the network (Novell) to a disk on the
> remote computer. This however fails with OS error=5(access is denied).
The
> user who performs this operation is administrator on the computer. Could
you
> please inform why this is not possible and if there is a better way to
> perform this operation.
> Thanks!
> Susanne
|||But then you have to change the account that runs the SQLServer srvice to an
account that has the access or grant the existing account the required
access. If you can't do that, you'll have to copy the files to the server
and then do the retstore from a local file.
Regards
Steen
Susanne wrote:[vbcol=seagreen]
> That's exactly the point. I can access the file using Windows Exporer
> on the server, however not when trying to restore the database (using
> SQL Enterprise Manager).
>
>
> "Steen Persson" wrote:
|||It is a comfort to read that this can be done. I have tried to restore, after
changing the logon for the SQL Server Manager to Administrator and restarting
the service, but it still doesn't work. I get the same error. Unfortunately,
there is not enough of space on the target server so I can run the restore
from a local disk.
"evan b" wrote:
> Suzanne
> We do this a lot and on the target SQL Server Machine set the logon in the
> services startup properties to a domain user with access to the unc path (I
> just used <domain>\Administrator)
> evan
> "Susanne" <Susanne@.discussions.microsoft.com> wrote in message
> news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> since
> The
> you
>
>
|||Hi Susanne
I have to admit that I don't know if there can be amy issues when you are
using a Novell network, but I doubt.
You say that you have changed the logon for SQL Server Manager, but what do
you mean with that? It's the account that runs the SQL Server Service that
you need to set to an account that has access to the share. When you have
done that, then log on to the server using tihs account and then verify that
you can access the share with that account. If it still doesn't work, then
try to post the code you are using - maybe there are something in you code
that isn't correct.
Regards
Steen
Susanne wrote:[vbcol=seagreen]
> It is a comfort to read that this can be done. I have tried to
> restore, after changing the logon for the SQL Server Manager to
> Administrator and restarting the service, but it still doesn't work.
> I get the same error. Unfortunately, there is not enough of space on
> the target server so I can run the restore from a local disk.
> "evan b" wrote:
Restore of database fails
Hi,
I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
using the restore option with the UNC name (\\servername\G$\path\file), sinc
e
the restore is to be performed over the network (Novell) to a disk on the
remote computer. This however fails with OS error=5(access is denied). The
user who performs this operation is administrator on the computer. Could you
please inform why this is not possible and if there is a better way to
perform this operation.
Thanks!
SusanneHi Susanne
It's the account that runs the SQLServer service that needs to have access
to the UNC path. You can test the access by logging on to the server as the
user that runs the SQL server service and then verify that you now can get
to the file.
Regards
Steen
Susanne wrote:
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
> server by using the restore option with the UNC name
> (\\servername\G$\path\file), since the restore is to be performed
> over the network (Novell) to a disk on the remote computer. This
> however fails with OS error=5(access is denied). The user who
> performs this operation is administrator on the computer. Could you
> please inform why this is not possible and if there is a better way
> to perform this operation.
> Thanks!
> Susanne|||That's exactly the point. I can access the file using Windows Exporer on the
server, however not when trying to restore the database (using SQL Enterpris
e
Manager).
"Steen Persson" wrote:
> Hi Susanne
> It's the account that runs the SQLServer service that needs to have access
> to the UNC path. You can test the access by logging on to the server as th
e
> user that runs the SQL server service and then verify that you now can get
> to the file.
> Regards
> Steen
> Susanne wrote:
>
>|||Suzanne
We do this a lot and on the target SQL Server Machine set the logon in the
services startup properties to a domain user with access to the unc path (I
just used <domain>\Administrator)
evan
"Susanne" <Susanne@.discussions.microsoft.com> wrote in message
news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
> using the restore option with the UNC name (\\servername\G$\path\file),
since
> the restore is to be performed over the network (Novell) to a disk on the
> remote computer. This however fails with OS error=5(access is denied).
The
> user who performs this operation is administrator on the computer. Could
you
> please inform why this is not possible and if there is a better way to
> perform this operation.
> Thanks!
> Susanne|||But then you have to change the account that runs the SQLServer srvice to an
account that has the access or grant the existing account the required
access. If you can't do that, you'll have to copy the files to the server
and then do the retstore from a local file.
Regards
Steen
Susanne wrote:[vbcol=seagreen]
> That's exactly the point. I can access the file using Windows Exporer
> on the server, however not when trying to restore the database (using
> SQL Enterprise Manager).
>
>
> "Steen Persson" wrote:
>|||It is a comfort to read that this can be done. I have tried to restore, afte
r
changing the logon for the SQL Server Manager to Administrator and restartin
g
the service, but it still doesn't work. I get the same error. Unfortunately,
there is not enough of space on the target server so I can run the restore
from a local disk.
"evan b" wrote:
> Suzanne
> We do this a lot and on the target SQL Server Machine set the logon in the
> services startup properties to a domain user with access to the unc path (
I
> just used <domain>\Administrator)
> evan
> "Susanne" <Susanne@.discussions.microsoft.com> wrote in message
> news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> since
> The
> you
>
>|||Hi Susanne
I have to admit that I don't know if there can be amy issues when you are
using a Novell network, but I doubt.
You say that you have changed the logon for SQL Server Manager, but what do
you mean with that? It's the account that runs the SQL Server Service that
you need to set to an account that has access to the share. When you have
done that, then log on to the server using tihs account and then verify that
you can access the share with that account. If it still doesn't work, then
try to post the code you are using - maybe there are something in you code
that isn't correct.
Regards
Steen
Susanne wrote:[vbcol=seagreen]
> It is a comfort to read that this can be done. I have tried to
> restore, after changing the logon for the SQL Server Manager to
> Administrator and restarting the service, but it still doesn't work.
> I get the same error. Unfortunately, there is not enough of space on
> the target server so I can run the restore from a local disk.
> "evan b" wrote:
I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
using the restore option with the UNC name (\\servername\G$\path\file), sinc
e
the restore is to be performed over the network (Novell) to a disk on the
remote computer. This however fails with OS error=5(access is denied). The
user who performs this operation is administrator on the computer. Could you
please inform why this is not possible and if there is a better way to
perform this operation.
Thanks!
SusanneHi Susanne
It's the account that runs the SQLServer service that needs to have access
to the UNC path. You can test the access by logging on to the server as the
user that runs the SQL server service and then verify that you now can get
to the file.
Regards
Steen
Susanne wrote:
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
> server by using the restore option with the UNC name
> (\\servername\G$\path\file), since the restore is to be performed
> over the network (Novell) to a disk on the remote computer. This
> however fails with OS error=5(access is denied). The user who
> performs this operation is administrator on the computer. Could you
> please inform why this is not possible and if there is a better way
> to perform this operation.
> Thanks!
> Susanne|||That's exactly the point. I can access the file using Windows Exporer on the
server, however not when trying to restore the database (using SQL Enterpris
e
Manager).
"Steen Persson" wrote:
> Hi Susanne
> It's the account that runs the SQLServer service that needs to have access
> to the UNC path. You can test the access by logging on to the server as th
e
> user that runs the SQL server service and then verify that you now can get
> to the file.
> Regards
> Steen
> Susanne wrote:
>
>|||Suzanne
We do this a lot and on the target SQL Server Machine set the logon in the
services startup properties to a domain user with access to the unc path (I
just used <domain>\Administrator)
evan
"Susanne" <Susanne@.discussions.microsoft.com> wrote in message
news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
> using the restore option with the UNC name (\\servername\G$\path\file),
since
> the restore is to be performed over the network (Novell) to a disk on the
> remote computer. This however fails with OS error=5(access is denied).
The
> user who performs this operation is administrator on the computer. Could
you
> please inform why this is not possible and if there is a better way to
> perform this operation.
> Thanks!
> Susanne|||But then you have to change the account that runs the SQLServer srvice to an
account that has the access or grant the existing account the required
access. If you can't do that, you'll have to copy the files to the server
and then do the retstore from a local file.
Regards
Steen
Susanne wrote:[vbcol=seagreen]
> That's exactly the point. I can access the file using Windows Exporer
> on the server, however not when trying to restore the database (using
> SQL Enterprise Manager).
>
>
> "Steen Persson" wrote:
>|||It is a comfort to read that this can be done. I have tried to restore, afte
r
changing the logon for the SQL Server Manager to Administrator and restartin
g
the service, but it still doesn't work. I get the same error. Unfortunately,
there is not enough of space on the target server so I can run the restore
from a local disk.
"evan b" wrote:
> Suzanne
> We do this a lot and on the target SQL Server Machine set the logon in the
> services startup properties to a domain user with access to the unc path (
I
> just used <domain>\Administrator)
> evan
> "Susanne" <Susanne@.discussions.microsoft.com> wrote in message
> news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> since
> The
> you
>
>|||Hi Susanne
I have to admit that I don't know if there can be amy issues when you are
using a Novell network, but I doubt.
You say that you have changed the logon for SQL Server Manager, but what do
you mean with that? It's the account that runs the SQL Server Service that
you need to set to an account that has access to the share. When you have
done that, then log on to the server using tihs account and then verify that
you can access the share with that account. If it still doesn't work, then
try to post the code you are using - maybe there are something in you code
that isn't correct.
Regards
Steen
Susanne wrote:[vbcol=seagreen]
> It is a comfort to read that this can be done. I have tried to
> restore, after changing the logon for the SQL Server Manager to
> Administrator and restarting the service, but it still doesn't work.
> I get the same error. Unfortunately, there is not enough of space on
> the target server so I can run the restore from a local disk.
> "evan b" wrote:
Restore of database fails
Hi,
I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
using the restore option with the UNC name (\\servername\G$\path\file), since
the restore is to be performed over the network (Novell) to a disk on the
remote computer. This however fails with OS error=5(access is denied). The
user who performs this operation is administrator on the computer. Could you
please inform why this is not possible and if there is a better way to
perform this operation.
Thanks!
SusanneHi Susanne
It's the account that runs the SQLServer service that needs to have access
to the UNC path. You can test the access by logging on to the server as the
user that runs the SQL server service and then verify that you now can get
to the file.
Regards
Steen
Susanne wrote:
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
> server by using the restore option with the UNC name
> (\\servername\G$\path\file), since the restore is to be performed
> over the network (Novell) to a disk on the remote computer. This
> however fails with OS error=5(access is denied). The user who
> performs this operation is administrator on the computer. Could you
> please inform why this is not possible and if there is a better way
> to perform this operation.
> Thanks!
> Susanne|||That's exactly the point. I can access the file using Windows Exporer on the
server, however not when trying to restore the database (using SQL Enterprise
Manager).
"Steen Persson" wrote:
> Hi Susanne
> It's the account that runs the SQLServer service that needs to have access
> to the UNC path. You can test the access by logging on to the server as the
> user that runs the SQL server service and then verify that you now can get
> to the file.
> Regards
> Steen
> Susanne wrote:
> > Hi,
> > I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
> > server by using the restore option with the UNC name
> > (\\servername\G$\path\file), since the restore is to be performed
> > over the network (Novell) to a disk on the remote computer. This
> > however fails with OS error=5(access is denied). The user who
> > performs this operation is administrator on the computer. Could you
> > please inform why this is not possible and if there is a better way
> > to perform this operation.
> > Thanks!
> > Susanne
>
>|||Suzanne
We do this a lot and on the target SQL Server Machine set the logon in the
services startup properties to a domain user with access to the unc path (I
just used <domain>\Administrator)
evan
"Susanne" <Susanne@.discussions.microsoft.com> wrote in message
news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
> using the restore option with the UNC name (\\servername\G$\path\file),
since
> the restore is to be performed over the network (Novell) to a disk on the
> remote computer. This however fails with OS error=5(access is denied).
The
> user who performs this operation is administrator on the computer. Could
you
> please inform why this is not possible and if there is a better way to
> perform this operation.
> Thanks!
> Susanne|||But then you have to change the account that runs the SQLServer srvice to an
account that has the access or grant the existing account the required
access. If you can't do that, you'll have to copy the files to the server
and then do the retstore from a local file.
Regards
Steen
Susanne wrote:
> That's exactly the point. I can access the file using Windows Exporer
> on the server, however not when trying to restore the database (using
> SQL Enterprise Manager).
>
>
> "Steen Persson" wrote:
>> Hi Susanne
>> It's the account that runs the SQLServer service that needs to have
>> access to the UNC path. You can test the access by logging on to the
>> server as the user that runs the SQL server service and then verify
>> that you now can get to the file.
>> Regards
>> Steen
>> Susanne wrote:
>> Hi,
>> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
>> server by using the restore option with the UNC name
>> (\\servername\G$\path\file), since the restore is to be performed
>> over the network (Novell) to a disk on the remote computer. This
>> however fails with OS error=5(access is denied). The user who
>> performs this operation is administrator on the computer. Could you
>> please inform why this is not possible and if there is a better way
>> to perform this operation.
>> Thanks!
>> Susanne|||It is a comfort to read that this can be done. I have tried to restore, after
changing the logon for the SQL Server Manager to Administrator and restarting
the service, but it still doesn't work. I get the same error. Unfortunately,
there is not enough of space on the target server so I can run the restore
from a local disk.
"evan b" wrote:
> Suzanne
> We do this a lot and on the target SQL Server Machine set the logon in the
> services startup properties to a domain user with access to the unc path (I
> just used <domain>\Administrator)
> evan
> "Susanne" <Susanne@.discussions.microsoft.com> wrote in message
> news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> > Hi,
> > I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
> > using the restore option with the UNC name (\\servername\G$\path\file),
> since
> > the restore is to be performed over the network (Novell) to a disk on the
> > remote computer. This however fails with OS error=5(access is denied).
> The
> > user who performs this operation is administrator on the computer. Could
> you
> > please inform why this is not possible and if there is a better way to
> > perform this operation.
> > Thanks!
> > Susanne
>
>|||Hi Susanne
I have to admit that I don't know if there can be amy issues when you are
using a Novell network, but I doubt.
You say that you have changed the logon for SQL Server Manager, but what do
you mean with that? It's the account that runs the SQL Server Service that
you need to set to an account that has access to the share. When you have
done that, then log on to the server using tihs account and then verify that
you can access the share with that account. If it still doesn't work, then
try to post the code you are using - maybe there are something in you code
that isn't correct.
Regards
Steen
Susanne wrote:
> It is a comfort to read that this can be done. I have tried to
> restore, after changing the logon for the SQL Server Manager to
> Administrator and restarting the service, but it still doesn't work.
> I get the same error. Unfortunately, there is not enough of space on
> the target server so I can run the restore from a local disk.
> "evan b" wrote:
>> Suzanne
>> We do this a lot and on the target SQL Server Machine set the logon
>> in the services startup properties to a domain user with access to
>> the unc path (I just used <domain>\Administrator)
>> evan
>> "Susanne" <Susanne@.discussions.microsoft.com> wrote in message
>> news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
>> Hi,
>> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
>> server by using the restore option with the UNC name
>> (\\servername\G$\path\file), since the restore is to be performed
>> over the network (Novell) to a disk on the remote computer. This
>> however fails with OS error=5(access is denied). The user who
>> performs this operation is administrator on the computer. Could you
>> please inform why this is not possible and if there is a better way
>> to perform this operation.
>> Thanks!
>> Susanne
I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
using the restore option with the UNC name (\\servername\G$\path\file), since
the restore is to be performed over the network (Novell) to a disk on the
remote computer. This however fails with OS error=5(access is denied). The
user who performs this operation is administrator on the computer. Could you
please inform why this is not possible and if there is a better way to
perform this operation.
Thanks!
SusanneHi Susanne
It's the account that runs the SQLServer service that needs to have access
to the UNC path. You can test the access by logging on to the server as the
user that runs the SQL server service and then verify that you now can get
to the file.
Regards
Steen
Susanne wrote:
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
> server by using the restore option with the UNC name
> (\\servername\G$\path\file), since the restore is to be performed
> over the network (Novell) to a disk on the remote computer. This
> however fails with OS error=5(access is denied). The user who
> performs this operation is administrator on the computer. Could you
> please inform why this is not possible and if there is a better way
> to perform this operation.
> Thanks!
> Susanne|||That's exactly the point. I can access the file using Windows Exporer on the
server, however not when trying to restore the database (using SQL Enterprise
Manager).
"Steen Persson" wrote:
> Hi Susanne
> It's the account that runs the SQLServer service that needs to have access
> to the UNC path. You can test the access by logging on to the server as the
> user that runs the SQL server service and then verify that you now can get
> to the file.
> Regards
> Steen
> Susanne wrote:
> > Hi,
> > I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
> > server by using the restore option with the UNC name
> > (\\servername\G$\path\file), since the restore is to be performed
> > over the network (Novell) to a disk on the remote computer. This
> > however fails with OS error=5(access is denied). The user who
> > performs this operation is administrator on the computer. Could you
> > please inform why this is not possible and if there is a better way
> > to perform this operation.
> > Thanks!
> > Susanne
>
>|||Suzanne
We do this a lot and on the target SQL Server Machine set the logon in the
services startup properties to a domain user with access to the unc path (I
just used <domain>\Administrator)
evan
"Susanne" <Susanne@.discussions.microsoft.com> wrote in message
news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> Hi,
> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
> using the restore option with the UNC name (\\servername\G$\path\file),
since
> the restore is to be performed over the network (Novell) to a disk on the
> remote computer. This however fails with OS error=5(access is denied).
The
> user who performs this operation is administrator on the computer. Could
you
> please inform why this is not possible and if there is a better way to
> perform this operation.
> Thanks!
> Susanne|||But then you have to change the account that runs the SQLServer srvice to an
account that has the access or grant the existing account the required
access. If you can't do that, you'll have to copy the files to the server
and then do the retstore from a local file.
Regards
Steen
Susanne wrote:
> That's exactly the point. I can access the file using Windows Exporer
> on the server, however not when trying to restore the database (using
> SQL Enterprise Manager).
>
>
> "Steen Persson" wrote:
>> Hi Susanne
>> It's the account that runs the SQLServer service that needs to have
>> access to the UNC path. You can test the access by logging on to the
>> server as the user that runs the SQL server service and then verify
>> that you now can get to the file.
>> Regards
>> Steen
>> Susanne wrote:
>> Hi,
>> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
>> server by using the restore option with the UNC name
>> (\\servername\G$\path\file), since the restore is to be performed
>> over the network (Novell) to a disk on the remote computer. This
>> however fails with OS error=5(access is denied). The user who
>> performs this operation is administrator on the computer. Could you
>> please inform why this is not possible and if there is a better way
>> to perform this operation.
>> Thanks!
>> Susanne|||It is a comfort to read that this can be done. I have tried to restore, after
changing the logon for the SQL Server Manager to Administrator and restarting
the service, but it still doesn't work. I get the same error. Unfortunately,
there is not enough of space on the target server so I can run the restore
from a local disk.
"evan b" wrote:
> Suzanne
> We do this a lot and on the target SQL Server Machine set the logon in the
> services startup properties to a domain user with access to the unc path (I
> just used <domain>\Administrator)
> evan
> "Susanne" <Susanne@.discussions.microsoft.com> wrote in message
> news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
> > Hi,
> > I am trying to move an SQL2000 database (abt 10 GB) to a Win2000 server by
> > using the restore option with the UNC name (\\servername\G$\path\file),
> since
> > the restore is to be performed over the network (Novell) to a disk on the
> > remote computer. This however fails with OS error=5(access is denied).
> The
> > user who performs this operation is administrator on the computer. Could
> you
> > please inform why this is not possible and if there is a better way to
> > perform this operation.
> > Thanks!
> > Susanne
>
>|||Hi Susanne
I have to admit that I don't know if there can be amy issues when you are
using a Novell network, but I doubt.
You say that you have changed the logon for SQL Server Manager, but what do
you mean with that? It's the account that runs the SQL Server Service that
you need to set to an account that has access to the share. When you have
done that, then log on to the server using tihs account and then verify that
you can access the share with that account. If it still doesn't work, then
try to post the code you are using - maybe there are something in you code
that isn't correct.
Regards
Steen
Susanne wrote:
> It is a comfort to read that this can be done. I have tried to
> restore, after changing the logon for the SQL Server Manager to
> Administrator and restarting the service, but it still doesn't work.
> I get the same error. Unfortunately, there is not enough of space on
> the target server so I can run the restore from a local disk.
> "evan b" wrote:
>> Suzanne
>> We do this a lot and on the target SQL Server Machine set the logon
>> in the services startup properties to a domain user with access to
>> the unc path (I just used <domain>\Administrator)
>> evan
>> "Susanne" <Susanne@.discussions.microsoft.com> wrote in message
>> news:08EC523C-8FCF-401A-B8FA-4BE58FD8F269@.microsoft.com...
>> Hi,
>> I am trying to move an SQL2000 database (abt 10 GB) to a Win2000
>> server by using the restore option with the UNC name
>> (\\servername\G$\path\file), since the restore is to be performed
>> over the network (Novell) to a disk on the remote computer. This
>> however fails with OS error=5(access is denied). The user who
>> performs this operation is administrator on the computer. Could you
>> please inform why this is not possible and if there is a better way
>> to perform this operation.
>> Thanks!
>> Susanne
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.
>
>
Restore of a Database in Analysis Server Failure
Hi Everyone,
We have an Analysis Services database which has 9 cubes. Whenever I do an Archive/Restore it fails giving the following error:
* Unexpected error encountered while updating repository item cannot be found in the collection corresponding to the requested name or ordinal.
* Restoration Cancelled
* DSO function failed
Please advise.
Regards,
Kalyanis your repository in access or in sql server? if you migrated it to sql server and your repository is corrupted you can get it back. however if it is in the access db you may have a different outcome than you wish.
have you tried to restore your cube to another AS to see if the backup is corrupted>?
We have an Analysis Services database which has 9 cubes. Whenever I do an Archive/Restore it fails giving the following error:
* Unexpected error encountered while updating repository item cannot be found in the collection corresponding to the requested name or ordinal.
* Restoration Cancelled
* DSO function failed
Please advise.
Regards,
Kalyanis your repository in access or in sql server? if you migrated it to sql server and your repository is corrupted you can get it back. however if it is in the access db you may have a different outcome than you wish.
have you tried to restore your cube to another AS to see if the backup is corrupted>?
Restore MSSQL7 Backup data to MSSQL2000
Dear all,
I want to transfer data from SQL7 to SQL2000, so I backup the data and
restore it in SQL2000. But it fails to do so due to different version. Do
everyone know how to do this? Thanks
Rdgs
Ellis
Hi,
Did you tried to restore a SYSTEM database ? System database can not be
restored from SQL 7 to SQL 2000. How ever all the
user databases can be backed up from SQL 7 and can be restored to SQL 2000
with out any issues. During the restore itself it
does a version conversion. But execute the procedure "SP_UPDATESTATS" after
the restoration to get the optimal performance.
Note:
FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option to
copy the data is use DTS.
Thanks
Hari
MCDBA
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> I want to transfer data from SQL7 to SQL2000, so I backup the data and
> restore it in SQL2000. But it fails to do so due to different version. Do
> everyone know how to do this? Thanks
> Rdgs
> Ellis
>
|||Thanks a lot !!! It's very useful
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#JxmhPmhEHA.3476@.tk2msftngp13.phx.gbl...
> Hi,
> Did you tried to restore a SYSTEM database ? System database can not be
> restored from SQL 7 to SQL 2000. How ever all the
> user databases can be backed up from SQL 7 and can be restored to SQL 2000
> with out any issues. During the restore itself it
> does a version conversion. But execute the procedure "SP_UPDATESTATS"
after
> the restoration to get the optimal performance.
>
> Note:
> FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option
to[vbcol=seagreen]
> copy the data is use DTS.
> Thanks
> Hari
> MCDBA
> "Ellis Yu" <ellis.yu@.transfield.com> wrote in message
> news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
Do
>
I want to transfer data from SQL7 to SQL2000, so I backup the data and
restore it in SQL2000. But it fails to do so due to different version. Do
everyone know how to do this? Thanks
Rdgs
Ellis
Hi,
Did you tried to restore a SYSTEM database ? System database can not be
restored from SQL 7 to SQL 2000. How ever all the
user databases can be backed up from SQL 7 and can be restored to SQL 2000
with out any issues. During the restore itself it
does a version conversion. But execute the procedure "SP_UPDATESTATS" after
the restoration to get the optimal performance.
Note:
FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option to
copy the data is use DTS.
Thanks
Hari
MCDBA
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> I want to transfer data from SQL7 to SQL2000, so I backup the data and
> restore it in SQL2000. But it fails to do so due to different version. Do
> everyone know how to do this? Thanks
> Rdgs
> Ellis
>
|||Thanks a lot !!! It's very useful
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#JxmhPmhEHA.3476@.tk2msftngp13.phx.gbl...
> Hi,
> Did you tried to restore a SYSTEM database ? System database can not be
> restored from SQL 7 to SQL 2000. How ever all the
> user databases can be backed up from SQL 7 and can be restored to SQL 2000
> with out any issues. During the restore itself it
> does a version conversion. But execute the procedure "SP_UPDATESTATS"
after
> the restoration to get the optimal performance.
>
> Note:
> FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option
to[vbcol=seagreen]
> copy the data is use DTS.
> Thanks
> Hari
> MCDBA
> "Ellis Yu" <ellis.yu@.transfield.com> wrote in message
> news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
Do
>
Restore MSSQL7 Backup data to MSSQL2000
Dear all,
I want to transfer data from SQL7 to SQL2000, so I backup the data and
restore it in SQL2000. But it fails to do so due to different version. Do
everyone know how to do this' Thanks
Rdgs
EllisHi,
Did you tried to restore a SYSTEM database ? System database can not be
restored from SQL 7 to SQL 2000. How ever all the
user databases can be backed up from SQL 7 and can be restored to SQL 2000
with out any issues. During the restore itself it
does a version conversion. But execute the procedure "SP_UPDATESTATS" after
the restoration to get the optimal performance.
Note:
FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option to
copy the data is use DTS.
Thanks
Hari
MCDBA
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> I want to transfer data from SQL7 to SQL2000, so I backup the data and
> restore it in SQL2000. But it fails to do so due to different version. Do
> everyone know how to do this' Thanks
> Rdgs
> Ellis
>|||Thanks a lot !!! It's very useful
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#JxmhPmhEHA.3476@.tk2msftngp13.phx.gbl...
> Hi,
> Did you tried to restore a SYSTEM database ? System database can not be
> restored from SQL 7 to SQL 2000. How ever all the
> user databases can be backed up from SQL 7 and can be restored to SQL 2000
> with out any issues. During the restore itself it
> does a version conversion. But execute the procedure "SP_UPDATESTATS"
after
> the restoration to get the optimal performance.
>
> Note:
> FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option
to
> copy the data is use DTS.
> Thanks
> Hari
> MCDBA
> "Ellis Yu" <ellis.yu@.transfield.com> wrote in message
> news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
> > Dear all,
> > I want to transfer data from SQL7 to SQL2000, so I backup the data
and
> > restore it in SQL2000. But it fails to do so due to different version.
Do
> > everyone know how to do this' Thanks
> >
> > Rdgs
> > Ellis
> >
> >
>
I want to transfer data from SQL7 to SQL2000, so I backup the data and
restore it in SQL2000. But it fails to do so due to different version. Do
everyone know how to do this' Thanks
Rdgs
EllisHi,
Did you tried to restore a SYSTEM database ? System database can not be
restored from SQL 7 to SQL 2000. How ever all the
user databases can be backed up from SQL 7 and can be restored to SQL 2000
with out any issues. During the restore itself it
does a version conversion. But execute the procedure "SP_UPDATESTATS" after
the restoration to get the optimal performance.
Note:
FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option to
copy the data is use DTS.
Thanks
Hari
MCDBA
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> I want to transfer data from SQL7 to SQL2000, so I backup the data and
> restore it in SQL2000. But it fails to do so due to different version. Do
> everyone know how to do this' Thanks
> Rdgs
> Ellis
>|||Thanks a lot !!! It's very useful
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#JxmhPmhEHA.3476@.tk2msftngp13.phx.gbl...
> Hi,
> Did you tried to restore a SYSTEM database ? System database can not be
> restored from SQL 7 to SQL 2000. How ever all the
> user databases can be backed up from SQL 7 and can be restored to SQL 2000
> with out any issues. During the restore itself it
> does a version conversion. But execute the procedure "SP_UPDATESTATS"
after
> the restoration to get the optimal performance.
>
> Note:
> FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option
to
> copy the data is use DTS.
> Thanks
> Hari
> MCDBA
> "Ellis Yu" <ellis.yu@.transfield.com> wrote in message
> news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
> > Dear all,
> > I want to transfer data from SQL7 to SQL2000, so I backup the data
and
> > restore it in SQL2000. But it fails to do so due to different version.
Do
> > everyone know how to do this' Thanks
> >
> > Rdgs
> > Ellis
> >
> >
>
Restore MSSQL7 Backup data to MSSQL2000
Dear all,
I want to transfer data from SQL7 to SQL2000, so I backup the data and
restore it in SQL2000. But it fails to do so due to different version. Do
everyone know how to do this' Thanks
Rdgs
EllisHi,
Did you tried to restore a SYSTEM database ? System database can not be
restored from SQL 7 to SQL 2000. How ever all the
user databases can be backed up from SQL 7 and can be restored to SQL 2000
with out any issues. During the restore itself it
does a version conversion. But execute the procedure "SP_UPDATESTATS" after
the restoration to get the optimal performance.
Note:
FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option to
copy the data is use DTS.
Thanks
Hari
MCDBA
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> I want to transfer data from SQL7 to SQL2000, so I backup the data and
> restore it in SQL2000. But it fails to do so due to different version. Do
> everyone know how to do this' Thanks
> Rdgs
> Ellis
>|||Thanks a lot !!! It's very useful
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#JxmhPmhEHA.3476@.tk2msftngp13.phx.gbl...
> Hi,
> Did you tried to restore a SYSTEM database ? System database can not be
> restored from SQL 7 to SQL 2000. How ever all the
> user databases can be backed up from SQL 7 and can be restored to SQL 2000
> with out any issues. During the restore itself it
> does a version conversion. But execute the procedure "SP_UPDATESTATS"
after
> the restoration to get the optimal performance.
>
> Note:
> FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option
to
> copy the data is use DTS.
> Thanks
> Hari
> MCDBA
> "Ellis Yu" <ellis.yu@.transfield.com> wrote in message
> news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
Do[vbcol=seagreen]
>
I want to transfer data from SQL7 to SQL2000, so I backup the data and
restore it in SQL2000. But it fails to do so due to different version. Do
everyone know how to do this' Thanks
Rdgs
EllisHi,
Did you tried to restore a SYSTEM database ? System database can not be
restored from SQL 7 to SQL 2000. How ever all the
user databases can be backed up from SQL 7 and can be restored to SQL 2000
with out any issues. During the restore itself it
does a version conversion. But execute the procedure "SP_UPDATESTATS" after
the restoration to get the optimal performance.
Note:
FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option to
copy the data is use DTS.
Thanks
Hari
MCDBA
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
> Dear all,
> I want to transfer data from SQL7 to SQL2000, so I backup the data and
> restore it in SQL2000. But it fails to do so due to different version. Do
> everyone know how to do this' Thanks
> Rdgs
> Ellis
>|||Thanks a lot !!! It's very useful
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:#JxmhPmhEHA.3476@.tk2msftngp13.phx.gbl...
> Hi,
> Did you tried to restore a SYSTEM database ? System database can not be
> restored from SQL 7 to SQL 2000. How ever all the
> user databases can be backed up from SQL 7 and can be restored to SQL 2000
> with out any issues. During the restore itself it
> does a version conversion. But execute the procedure "SP_UPDATESTATS"
after
> the restoration to get the optimal performance.
>
> Note:
> FYI, You can not restor a SQL 2000 database backup to SQL 7. Only option
to
> copy the data is use DTS.
> Thanks
> Hari
> MCDBA
> "Ellis Yu" <ellis.yu@.transfield.com> wrote in message
> news:eLIJgImhEHA.3140@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
Do[vbcol=seagreen]
>
Subscribe to:
Posts (Atom)