Hi Guys,
I got an error when I restored database. I tryed to restore a database that
is 8G. I got an error that is "An internal consistency error occured. Contact
technical support for assistance. RESTORE DATABASE is terminating
abnormally", then the database was marked Loading and in suspect mode. I try
to use command restore database policy with recovery, then got
errorimmediately:
File 'changept' was only partially restored by a database or file restore.
The entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I did restore this database two weeks ago in other database server and was
successful, but it is failed in this new server now. I don't know what reason
is. I need the help. Thank in advance.
Hi
"Iter" wrote:
> Hi Guys,
> I got an error when I restored database. I tryed to restore a database that
> is 8G. I got an error that is "An internal consistency error occured. Contact
> technical support for assistance. RESTORE DATABASE is terminating
> abnormally", then the database was marked Loading and in suspect mode. I try
> to use command restore database policy with recovery, then got
> errorimmediately:
> File 'changept' was only partially restored by a database or file restore.
> The entire file must be successfully restored before applying the log.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I did restore this database two weeks ago in other database server and was
> successful, but it is failed in this new server now. I don't know what reason
> is. I need the help. Thank in advance.
Have you copied the backup onto this server? The backup itself may be
corrupted try doing a RESTORE HEADERONLY command from query analyser. It is
not clear how you are restoring this file, try using query analyser to
restore the database if you are using EM then you can post the command you
are using. As this is a new server, the database does not need to exist
before you restore it. Are you putting the files in a different location?
Check that you have permissions and enough space to do this.
If the database exists on a different server you may want to either detach
the database and copy the MDF/LDF files and re-attach them (to both servers!)
or backup from one server to the other using a UNC path for the backup file,
so that you don't have to copy the backup file.
HTH
John
|||>I try to use command restore database policy with recovery, then got
> errorimmediately:
> File 'changept' was only partially restored by a database or file restore.
> The entire file must be successfully restored before applying the log.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I did restore this database two weeks ago in other database server and was
> successful, but it is failed in this new server now. I don't know what reason
> is. I need the help. Thank in advance.
Can we assume that this is the actual same backup file you are talking about
having restored before? This looks like there may be multiple backups in this
file and it is trying to restore a log file backup before restoring the full
backup.
Showing posts with label restore. Show all posts
Showing posts with label restore. Show all posts
Friday, March 30, 2012
I got an error when I restored database
Hi Guys,
I got an error when I restored database. I tryed to restore a database that
is 8G. I got an error that is "An internal consistency error occured. Contac
t
technical support for assistance. RESTORE DATABASE is terminating
abnormally", then the database was marked Loading and in suspect mode. I tr
y
to use command restore database policy with recovery, then got
errorimmediately:
File 'changept' was only partially restored by a database or file restore.
The entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I did restore this database two weeks ago in other database server and was
successful, but it is failed in this new server now. I don't know what reaso
n
is. I need the help. Thank in advance.Hi
"Iter" wrote:
> Hi Guys,
> I got an error when I restored database. I tryed to restore a database tha
t
> is 8G. I got an error that is "An internal consistency error occured. Cont
act
> technical support for assistance. RESTORE DATABASE is terminating
> abnormally", then the database was marked Loading and in suspect mode. I
try
> to use command restore database policy with recovery, then got
> errorimmediately:
> File 'changept' was only partially restored by a database or file restore.
> The entire file must be successfully restored before applying the log.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I did restore this database two weeks ago in other database server and was
> successful, but it is failed in this new server now. I don't know what rea
son
> is. I need the help. Thank in advance.
Have you copied the backup onto this server? The backup itself may be
corrupted try doing a RESTORE HEADERONLY command from query analyser. It is
not clear how you are restoring this file, try using query analyser to
restore the database if you are using EM then you can post the command you
are using. As this is a new server, the database does not need to exist
before you restore it. Are you putting the files in a different location?
Check that you have permissions and enough space to do this.
If the database exists on a different server you may want to either detach
the database and copy the MDF/LDF files and re-attach them (to both servers!
)
or backup from one server to the other using a UNC path for the backup file,
so that you don't have to copy the backup file.
HTH
John|||>I try to use command restore database policy with recovery, then got
> errorimmediately:
> File 'changept' was only partially restored by a database or file restore.
> The entire file must be successfully restored before applying the log.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I did restore this database two weeks ago in other database server and was
> successful, but it is failed in this new server now. I don't know what rea
son
> is. I need the help. Thank in advance.
Can we assume that this is the actual same backup file you are talking about
having restored before? This looks like there may be multiple backups in thi
s
file and it is trying to restore a log file backup before restoring the full
backup.
I got an error when I restored database. I tryed to restore a database that
is 8G. I got an error that is "An internal consistency error occured. Contac
t
technical support for assistance. RESTORE DATABASE is terminating
abnormally", then the database was marked Loading and in suspect mode. I tr
y
to use command restore database policy with recovery, then got
errorimmediately:
File 'changept' was only partially restored by a database or file restore.
The entire file must be successfully restored before applying the log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I did restore this database two weeks ago in other database server and was
successful, but it is failed in this new server now. I don't know what reaso
n
is. I need the help. Thank in advance.Hi
"Iter" wrote:
> Hi Guys,
> I got an error when I restored database. I tryed to restore a database tha
t
> is 8G. I got an error that is "An internal consistency error occured. Cont
act
> technical support for assistance. RESTORE DATABASE is terminating
> abnormally", then the database was marked Loading and in suspect mode. I
try
> to use command restore database policy with recovery, then got
> errorimmediately:
> File 'changept' was only partially restored by a database or file restore.
> The entire file must be successfully restored before applying the log.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I did restore this database two weeks ago in other database server and was
> successful, but it is failed in this new server now. I don't know what rea
son
> is. I need the help. Thank in advance.
Have you copied the backup onto this server? The backup itself may be
corrupted try doing a RESTORE HEADERONLY command from query analyser. It is
not clear how you are restoring this file, try using query analyser to
restore the database if you are using EM then you can post the command you
are using. As this is a new server, the database does not need to exist
before you restore it. Are you putting the files in a different location?
Check that you have permissions and enough space to do this.
If the database exists on a different server you may want to either detach
the database and copy the MDF/LDF files and re-attach them (to both servers!
)
or backup from one server to the other using a UNC path for the backup file,
so that you don't have to copy the backup file.
HTH
John|||>I try to use command restore database policy with recovery, then got
> errorimmediately:
> File 'changept' was only partially restored by a database or file restore.
> The entire file must be successfully restored before applying the log.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> I did restore this database two weeks ago in other database server and was
> successful, but it is failed in this new server now. I don't know what rea
son
> is. I need the help. Thank in advance.
Can we assume that this is the actual same backup file you are talking about
having restored before? This looks like there may be multiple backups in thi
s
file and it is trying to restore a log file backup before restoring the full
backup.
Monday, March 26, 2012
I can't restore my master DB
I have 2 servers (Prod & Staging)
Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
Staging is running SQL 2k Enterprise SP2
I can't get the versions to match, thus I can't restore any of my backed up databases to the staging server from the production one.
Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device g:\DBBACKUP\Master.bak cannot be restored because it was created by a different version of the server (134218407) than this server (134218262).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I would determine what versions you are running on both, and then upgrade
staging to match production. Is this possible?
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"HELP! Can't Restore DB's" <HELP! Can't Restore
DB's@.discussions.microsoft.com> wrote in message
news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> I have 2 servers (Prod & Staging)
> Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> Staging is running SQL 2k Enterprise SP2
> I can't get the versions to match, thus I can't restore any of my backed
up databases to the staging server from the production one.
>
> Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device g:\DBBACKUP\Master.bak cannot
be restored because it was created by a different version of the server
(134218407) than this server (134218262).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
|||I figured out the problem. A network guy implemented a security fix that altered the version on the production box and he didn't implement the same fix on the Staging box.
"Gregory A. Larsen" wrote:
> I would determine what versions you are running on both, and then upgrade
> staging to match production. Is this possible?
>
> --
> ----
> ----
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "HELP! Can't Restore DB's" <HELP! Can't Restore
> DB's@.discussions.microsoft.com> wrote in message
> news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> up databases to the staging server from the production one.
> be restored because it was created by a different version of the server
> (134218407) than this server (134218262).
>
>
Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
Staging is running SQL 2k Enterprise SP2
I can't get the versions to match, thus I can't restore any of my backed up databases to the staging server from the production one.
Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device g:\DBBACKUP\Master.bak cannot be restored because it was created by a different version of the server (134218407) than this server (134218262).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I would determine what versions you are running on both, and then upgrade
staging to match production. Is this possible?
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"HELP! Can't Restore DB's" <HELP! Can't Restore
DB's@.discussions.microsoft.com> wrote in message
news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> I have 2 servers (Prod & Staging)
> Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> Staging is running SQL 2k Enterprise SP2
> I can't get the versions to match, thus I can't restore any of my backed
up databases to the staging server from the production one.
>
> Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device g:\DBBACKUP\Master.bak cannot
be restored because it was created by a different version of the server
(134218407) than this server (134218262).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
|||I figured out the problem. A network guy implemented a security fix that altered the version on the production box and he didn't implement the same fix on the Staging box.
"Gregory A. Larsen" wrote:
> I would determine what versions you are running on both, and then upgrade
> staging to match production. Is this possible?
>
> --
> ----
> ----
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "HELP! Can't Restore DB's" <HELP! Can't Restore
> DB's@.discussions.microsoft.com> wrote in message
> news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> up databases to the staging server from the production one.
> be restored because it was created by a different version of the server
> (134218407) than this server (134218262).
>
>
I can't restore my master DB
I have 2 servers (Prod & Staging)
Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
Staging is running SQL 2k Enterprise SP2
I can't get the versions to match, thus I can't restore any of my backed up databases to the staging server from the production one.
---
Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device g:\DBBACKUP\Master.bak cannot be restored because it was created by a different version of the server (134218407) than this server (134218262).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.I would determine what versions you are running on both, and then upgrade
staging to match production. Is this possible?
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"HELP! Can't Restore DB's" <HELP! Can't Restore
DB's@.discussions.microsoft.com> wrote in message
news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> I have 2 servers (Prod & Staging)
> Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> Staging is running SQL 2k Enterprise SP2
> I can't get the versions to match, thus I can't restore any of my backed
up databases to the staging server from the production one.
> ---
> Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device g:\DBBACKUP\Master.bak cannot
be restored because it was created by a different version of the server
(134218407) than this server (134218262).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>|||I figured out the problem. A network guy implemented a security fix that altered the version on the production box and he didn't implement the same fix on the Staging box.
"Gregory A. Larsen" wrote:
> I would determine what versions you are running on both, and then upgrade
> staging to match production. Is this possible?
>
> --
> ----
> ----
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "HELP! Can't Restore DB's" <HELP! Can't Restore
> DB's@.discussions.microsoft.com> wrote in message
> news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> > I have 2 servers (Prod & Staging)
> >
> > Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> > Staging is running SQL 2k Enterprise SP2
> >
> > I can't get the versions to match, thus I can't restore any of my backed
> up databases to the staging server from the production one.
> >
> > ---
> >
> > Server: Msg 3168, Level 16, State 1, Line 1
> > The backup of the system database on device g:\DBBACKUP\Master.bak cannot
> be restored because it was created by a different version of the server
> (134218407) than this server (134218262).
> > Server: Msg 3013, Level 16, State 1, Line 1
> > RESTORE DATABASE is terminating abnormally.
> >
>
>
Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
Staging is running SQL 2k Enterprise SP2
I can't get the versions to match, thus I can't restore any of my backed up databases to the staging server from the production one.
---
Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device g:\DBBACKUP\Master.bak cannot be restored because it was created by a different version of the server (134218407) than this server (134218262).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.I would determine what versions you are running on both, and then upgrade
staging to match production. Is this possible?
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"HELP! Can't Restore DB's" <HELP! Can't Restore
DB's@.discussions.microsoft.com> wrote in message
news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> I have 2 servers (Prod & Staging)
> Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> Staging is running SQL 2k Enterprise SP2
> I can't get the versions to match, thus I can't restore any of my backed
up databases to the staging server from the production one.
> ---
> Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device g:\DBBACKUP\Master.bak cannot
be restored because it was created by a different version of the server
(134218407) than this server (134218262).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>|||I figured out the problem. A network guy implemented a security fix that altered the version on the production box and he didn't implement the same fix on the Staging box.
"Gregory A. Larsen" wrote:
> I would determine what versions you are running on both, and then upgrade
> staging to match production. Is this possible?
>
> --
> ----
> ----
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "HELP! Can't Restore DB's" <HELP! Can't Restore
> DB's@.discussions.microsoft.com> wrote in message
> news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> > I have 2 servers (Prod & Staging)
> >
> > Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> > Staging is running SQL 2k Enterprise SP2
> >
> > I can't get the versions to match, thus I can't restore any of my backed
> up databases to the staging server from the production one.
> >
> > ---
> >
> > Server: Msg 3168, Level 16, State 1, Line 1
> > The backup of the system database on device g:\DBBACKUP\Master.bak cannot
> be restored because it was created by a different version of the server
> (134218407) than this server (134218262).
> > Server: Msg 3013, Level 16, State 1, Line 1
> > RESTORE DATABASE is terminating abnormally.
> >
>
>
Friday, March 23, 2012
I can't restore my master DB
I have 2 servers (Prod & Staging)
Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
Staging is running SQL 2k Enterprise SP2
I can't get the versions to match, thus I can't restore any of my backed up
databases to the staging server from the production one.
---
Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device g:\DBBACKUP\Master.bak cannot be
restored because it was created by a different version of the server (13421
8407) than this server (134218262).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.I would determine what versions you are running on both, and then upgrade
staging to match production. Is this possible?
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"HELP! Can't Restore DB's" <HELP! Can't Restore
DB's@.discussions.microsoft.com> wrote in message
news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> I have 2 servers (Prod & Staging)
> Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> Staging is running SQL 2k Enterprise SP2
> I can't get the versions to match, thus I can't restore any of my backed
up databases to the staging server from the production one.
> ---
> Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device g:\DBBACKUP\Master.bak cannot
be restored because it was created by a different version of the server
(134218407) than this server (134218262).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>|||I figured out the problem. A network guy implemented a security fix that alt
ered the version on the production box and he didn't implement the same fix
on the Staging box.
"Gregory A. Larsen" wrote:
> I would determine what versions you are running on both, and then upgrade
> staging to match production. Is this possible?
>
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "HELP! Can't Restore DB's" <HELP! Can't Restore
> DB's@.discussions.microsoft.com> wrote in message
> news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> up databases to the staging server from the production one.
> be restored because it was created by a different version of the server
> (134218407) than this server (134218262).
>
>
Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
Staging is running SQL 2k Enterprise SP2
I can't get the versions to match, thus I can't restore any of my backed up
databases to the staging server from the production one.
---
Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device g:\DBBACKUP\Master.bak cannot be
restored because it was created by a different version of the server (13421
8407) than this server (134218262).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.I would determine what versions you are running on both, and then upgrade
staging to match production. Is this possible?
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"HELP! Can't Restore DB's" <HELP! Can't Restore
DB's@.discussions.microsoft.com> wrote in message
news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> I have 2 servers (Prod & Staging)
> Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> Staging is running SQL 2k Enterprise SP2
> I can't get the versions to match, thus I can't restore any of my backed
up databases to the staging server from the production one.
> ---
> Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device g:\DBBACKUP\Master.bak cannot
be restored because it was created by a different version of the server
(134218407) than this server (134218262).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>|||I figured out the problem. A network guy implemented a security fix that alt
ered the version on the production box and he didn't implement the same fix
on the Staging box.
"Gregory A. Larsen" wrote:
> I would determine what versions you are running on both, and then upgrade
> staging to match production. Is this possible?
>
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "HELP! Can't Restore DB's" <HELP! Can't Restore
> DB's@.discussions.microsoft.com> wrote in message
> news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> up databases to the staging server from the production one.
> be restored because it was created by a different version of the server
> (134218407) than this server (134218262).
>
>
I cant restore a SQL7 Database to a New SQL2000 Server
I assume that you were given a database backup file. Then the instructions y
ou were given are
incorrect or at least confusing.
Do not create the database first, will only mess for you. You can delete you
r current database.
Then just create the backup device and do the restore. The database is creat
ed along with the
restore process.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Chris Coates" <ccoates@.gfs.com> wrote in message news:eAdEGRB5DHA.2760@.TK2MSFTNGP09.phx.gbl...[QU
OTE]
> I am replacing an old SQL7 Server with a new server that runs SQL 2000. I
> was given directions on how to do this and was told to restore the SQL7
> databases to the new server.
> In order to do this I created an empty database with the same name on the
> new server, created a backup device and ran a backup of the empty database
.
> I testes a restore of the empty database and it worked fine. I then replac
ed
> the empty database .BAK file with the latest .BAK database backup of the
> original database and attempted a restore.
> I get the following error.
>
>
> The SQL Error Log shows the following message:
> Bypassing recovery for database 'Continuum' because it is marked IN LOAD.
>
> What am I doing wrong?
>
> Thanks for your help.
>
> ccoates
>
>[/QUOTE]Also, unless you are going to restore additional transaction log backups,
make sure you check the option that says "Leave Database Operational. No
additional transaction log backups can be restored". That is on the Options
tab of Restore database.
You can restore over an existing database so long as no one is using it |
you check force restore over existing database on the options tab | and make
sure the destination file locations are correct.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Chris Coates" <ccoates@.gfs.com> wrote in message
news:eAdEGRB5DHA.2760@.TK2MSFTNGP09.phx.gbl...
database.
replaced
Add on to Tibers post, perform these steps
1. Copy the SQL 7 backup to D:\mssql\backup\dbname.bak
2. Execute the below command from Query analyzer
Restore filelistonly from disk='D:\mssql\backup\dbname.bak'
The above command will give you the details of Logical name and Physical
name
3. Create a folder in D drive (D:\mssql\data) where your .MDF and .LDF
resides
5. Execute the below command from Query Analyzer
restore database dbname from disk='D:\mssql\backup\dbname.bak' with
move 'logical_dataname' to 'd:\mssql\data\dbname.mdf',
move 'logical_logname' to 'd:\mssql\data\dbname.ldf',stats=10
The logical_dataname and Logical_logname should be taken based on the output
of Restore filelistonly command (Step 2)
6.Create your logins , similar to SQL 7
Thanks
Hari
MCDBA
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e3zY5UB5DHA.2656@.TK2MSFTNGP11.phx.gbl...
you were given are
your current database.
created along with the
http://groups.google.com/groups?oi=...ublic.sqlserver
news:eAdEGRB5DHA.2760@.TK2MSFTNGP09.phx.gbl...
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
From you information provided, you encouter a error message 'Bypassing
recovery for database 'Continuum' because it is marked IN LOAD.' when you
were restoring a backup file which is from SQL 7 to SQL 2000, right?
Thanks to our MVP and other community members' replies. It is not necessary
to create a new database in backup and restore process and they have
provide the proper steps for backup and restore. Here I just want to add
something more that when restoring backup sets from an earlier version of
SQL Server, a database upgrade may be required. This upgrade is performed
automatically when WITH RECOVERY is specified. That is:
restore database database_name from disk='you_back.bak' with recovery
Hope this helps. If you still have questions about it, please feel free to
post new message here and I am ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.sql
ou were given are
incorrect or at least confusing.
Do not create the database first, will only mess for you. You can delete you
r current database.
Then just create the backup device and do the restore. The database is creat
ed along with the
restore process.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Chris Coates" <ccoates@.gfs.com> wrote in message news:eAdEGRB5DHA.2760@.TK2MSFTNGP09.phx.gbl...[QU
OTE]
> I am replacing an old SQL7 Server with a new server that runs SQL 2000. I
> was given directions on how to do this and was told to restore the SQL7
> databases to the new server.
> In order to do this I created an empty database with the same name on the
> new server, created a backup device and ran a backup of the empty database
.
> I testes a restore of the empty database and it worked fine. I then replac
ed
> the empty database .BAK file with the latest .BAK database backup of the
> original database and attempted a restore.
> I get the following error.
>
>
> The SQL Error Log shows the following message:
> Bypassing recovery for database 'Continuum' because it is marked IN LOAD.
>
> What am I doing wrong?
>
> Thanks for your help.
>
> ccoates
>
>[/QUOTE]Also, unless you are going to restore additional transaction log backups,
make sure you check the option that says "Leave Database Operational. No
additional transaction log backups can be restored". That is on the Options
tab of Restore database.
You can restore over an existing database so long as no one is using it |
you check force restore over existing database on the options tab | and make
sure the destination file locations are correct.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Chris Coates" <ccoates@.gfs.com> wrote in message
news:eAdEGRB5DHA.2760@.TK2MSFTNGP09.phx.gbl...
quote:
> I am replacing an old SQL7 Server with a new server that runs SQL 2000. I
> was given directions on how to do this and was told to restore the SQL7
> databases to the new server.
> In order to do this I created an empty database with the same name on the
> new server, created a backup device and ran a backup of the empty
database.
quote:
> I testes a restore of the empty database and it worked fine. I then
replaced
quote:|||Hi,
> the empty database .BAK file with the latest .BAK database backup of the
> original database and attempted a restore.
> I get the following error.
>
>
> The SQL Error Log shows the following message:
> Bypassing recovery for database 'Continuum' because it is marked IN LOAD.
>
> What am I doing wrong?
>
> Thanks for your help.
>
> ccoates
>
>
Add on to Tibers post, perform these steps
1. Copy the SQL 7 backup to D:\mssql\backup\dbname.bak
2. Execute the below command from Query analyzer
Restore filelistonly from disk='D:\mssql\backup\dbname.bak'
The above command will give you the details of Logical name and Physical
name
3. Create a folder in D drive (D:\mssql\data) where your .MDF and .LDF
resides
5. Execute the below command from Query Analyzer
restore database dbname from disk='D:\mssql\backup\dbname.bak' with
move 'logical_dataname' to 'd:\mssql\data\dbname.mdf',
move 'logical_logname' to 'd:\mssql\data\dbname.ldf',stats=10
The logical_dataname and Logical_logname should be taken based on the output
of Restore filelistonly command (Step 2)
6.Create your logins , similar to SQL 7
Thanks
Hari
MCDBA
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e3zY5UB5DHA.2656@.TK2MSFTNGP11.phx.gbl...
quote:
> I assume that you were given a database backup file. Then the instructions
you were given are
quote:
> incorrect or at least confusing.
> Do not create the database first, will only mess for you. You can delete
your current database.
quote:
> Then just create the backup device and do the restore. The database is
created along with the
quote:
> restore process.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
quote:
>
> "Chris Coates" <ccoates@.gfs.com> wrote in message
news:eAdEGRB5DHA.2760@.TK2MSFTNGP09.phx.gbl...
quote:|||Hi Chris,
I[QUOTE]
the[QUOTE]
database.[QUOTE]
replaced[QUOTE]
LOAD.[QUOTE]
>
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with
your issue.
From you information provided, you encouter a error message 'Bypassing
recovery for database 'Continuum' because it is marked IN LOAD.' when you
were restoring a backup file which is from SQL 7 to SQL 2000, right?
Thanks to our MVP and other community members' replies. It is not necessary
to create a new database in backup and restore process and they have
provide the proper steps for backup and restore. Here I just want to add
something more that when restoring backup sets from an earlier version of
SQL Server, a database upgrade may be required. This upgrade is performed
automatically when WITH RECOVERY is specified. That is:
restore database database_name from disk='you_back.bak' with recovery
Hope this helps. If you still have questions about it, please feel free to
post new message here and I am ready to help!
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.sql
Monday, March 12, 2012
I amRe: HELP!!! Can not restore database from only back up I have
I had to transfer my database from one server to another. Both are running SQL 2000. I backed the database up and moved it to the new server however when I try to do a restore I get the following message:
The media set for database "xxx' has 2 family members but only 1 are provided. RESTORE DATABASE is terminating abnormally.
I did some searching and found a couple of posts that mentioned something about the back up including 2 files.
My problem is that the machine I backed this up from crashed when it was shut down and would not reboot so all of the data and the original database do not exist. Is there any hope of restoring this database. It is pretty critical.
Thanks,
Melissa :-)
Do "restore filelistonly from <backup_device>" to see what is in the backup device. Also, please post the "restore" command here so we can see what's going on.|||When you say "My problem is that the machine I backed this up from crashed when it was shut down and would not reboot so all of the data and the original database do not exist" - can you pull the drive that contained the original databases out of the machine and add it to the new one? (I'm assuming from your description that the database is on a DAS drive rather than a SAN)|||I wish. The administrator who was trying to get the machine to boot determined it was beyond help and reformatted the drive and installed a new operating system on it. So all is lost.
Melissa : -(
|||Ok here is the results from the restore filelistonly we ran:
LiveStats.XSP
C:\Program Files\Microsoft SQL Server\MSSQL\Data\LiveStats.XSP.mdf D PRIMARY 1188560896 35184372080640 LiveStats.XSP_log
C:\Program Files\Microsoft SQL Server\MSSQL\Data\LiveStats.XSP_log.LDF L NULL 13623296 35184372080640
I just did the restore from the menu.
I am using the restore wizard. Right clicking on the blank database (I also tried restoring without creating a blank database) Selecting Restore. Then I select From Device>>>browse to the location the back up file is>>>Restore backup set...database complete and I am not changing anything under the options tab.
Melissa :-)
|||Please! Please! Please! tell me there is a way to restore this database. It is the only copy I have of webstats for almost 100 clients for the past year. The raw files were on the same hard drive that got wiped out.
Melissa :-)
|||What happens when you run this (directly through a client connection, not from any wizard):
restore database LiveStats.XSP from <backupdevice>
|||Server: Msg 3132, Level 16, State 1, Line 1The media set for database 'LiveStatsXSP' has 2 family members but only 1 are provided. All members must be provided.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.|||
Greetings.
It looks as if there is more to the backup than the one file which you are specifying.
Is there a chance that your backup produced more than one file, and that you still have access to both?
The command RESTORE LABELONLY FROM <backup_device> will tell us more about the mackup media.
|||Here are the results from the Restore Label Only
NULL {525AA069-12A6-4E37-92CF-737C4FD9E4E2} 2 2 {F9E38D61-0000-0000-0000-000000000000} 1 0 NULL Microsoft SQL Server 4608 2006-06-30 16:42:25.000
Unfortunately that is the only file that was zipped up and moved to the new server. :-(
|||That error tells us that when the backup was done, it was a striped backup, so the data was written to two different files in alternating stripes similar to the way a striped disk works. That means that we have to find that other file for us to have any chance of restoring the database.
The good news is that it is highly likely to be in the same location as the first backup file that you're using to restore.
The bad news is that without that other file, we cannot restore the database. Do you have ANY other copies of the backup anywhere? Even a system backup might be helpful.
|||Wow. Allowing the user to stripe across two devices is so risky. I was hoping to use a dummy striped member but it looks like you have the GUID set for each mediaset. Thus, the restore still fails. Another suggestion
, make it like RAID-5. Only allow striping across 3 or more devices.|||I had a feeling the news was not going to be good. It sounds like I am pretty much out of luck.I can not find a back up of that data anywhere.
I guess some lessons are just more painful to learn than others. If there is anything else I can try please let me know.
Melissa
Subscribe to:
Posts (Atom)