Restore db to another server

I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
(SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
it was cancelled after 10% write; error 34113 on BackupExec server, and
repeated error 57859 on destination SQL server.
When rerun job, no data is written and job cancels with same error in
BackupExec server, and new error in destination SQL server: 57859 --
"Exclusive access couldn not be obtained because the database is in use." (It
seems to me it's not in use, nobody uses this server yet.)
Strange thing is, I can restore another (test) database from same tape
without any problems.
Happy to get any hints or guidelines, I'm kinda stuck.
I deleted the restored database on new SQL server an reran the restore job,
and everything worked OK -- and so I will never know what went wrong the
first time, but will nevertheless be able to spend the weekend with family
instead of SQL.
Thanks for taking time, if you took any.
"JSL" wrote:

> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
> I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
> it was cancelled after 10% write; error 34113 on BackupExec server, and
> repeated error 57859 on destination SQL server.
> When rerun job, no data is written and job cancels with same error in
> BackupExec server, and new error in destination SQL server: 57859 --
> "Exclusive access couldn not be obtained because the database is in use." (It
> seems to me it's not in use, nobody uses this server yet.)
> Strange thing is, I can restore another (test) database from same tape
> without any problems.
> Happy to get any hints or guidelines, I'm kinda stuck.
|||Next time, use sp_who to see who is using the database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JSL" <JSL@.discussions.microsoft.com> wrote in message
news:90762CE8-604D-4BD5-A1DE-9645952022C9@.microsoft.com...[vbcol=seagreen]
>I deleted the restored database on new SQL server an reran the restore job,
> and everything worked OK -- and so I will never know what went wrong the
> first time, but will nevertheless be able to spend the weekend with family
> instead of SQL.
> Thanks for taking time, if you took any.
> "JSL" wrote:

Restore db to another server

I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
(SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
it was cancelled after 10% write; error 34113 on BackupExec server, and
repeated error 57859 on destination SQL server.
When rerun job, no data is written and job cancels with same error in
BackupExec server, and new error in destination SQL server: 57859 --
"Exclusive access couldn not be obtained because the database is in use." (It
seems to me it's not in use, nobody uses this server yet.)
Strange thing is, I can restore another (test) database from same tape
without any problems.
Happy to get any hints or guidelines, I'm kinda stuck.I deleted the restored database on new SQL server an reran the restore job,
and everything worked OK -- and so I will never know what went wrong the
first time, but will nevertheless be able to spend the weekend with family
instead of SQL.
Thanks for taking time, if you took any.
"JSL" wrote:
> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
> I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
> it was cancelled after 10% write; error 34113 on BackupExec server, and
> repeated error 57859 on destination SQL server.
> When rerun job, no data is written and job cancels with same error in
> BackupExec server, and new error in destination SQL server: 57859 --
> "Exclusive access couldn not be obtained because the database is in use." (It
> seems to me it's not in use, nobody uses this server yet.)
> Strange thing is, I can restore another (test) database from same tape
> without any problems.
> Happy to get any hints or guidelines, I'm kinda stuck.|||Next time, use sp_who to see who is using the database.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JSL" <JSL@.discussions.microsoft.com> wrote in message
news:90762CE8-604D-4BD5-A1DE-9645952022C9@.microsoft.com...
>I deleted the restored database on new SQL server an reran the restore job,
> and everything worked OK -- and so I will never know what went wrong the
> first time, but will nevertheless be able to spend the weekend with family
> instead of SQL.
> Thanks for taking time, if you took any.
> "JSL" wrote:
>> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
>> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
>> I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
>> it was cancelled after 10% write; error 34113 on BackupExec server, and
>> repeated error 57859 on destination SQL server.
>> When rerun job, no data is written and job cancels with same error in
>> BackupExec server, and new error in destination SQL server: 57859 --
>> "Exclusive access couldn not be obtained because the database is in use." (It
>> seems to me it's not in use, nobody uses this server yet.)
>> Strange thing is, I can restore another (test) database from same tape
>> without any problems.
>> Happy to get any hints or guidelines, I'm kinda stuck.

Restore db to another server

I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
(SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
it was cancelled after 10% write; error 34113 on BackupExec server, and
repeated error 57859 on destination SQL server.
When rerun job, no data is written and job cancels with same error in
BackupExec server, and new error in destination SQL server: 57859 --
"Exclusive access couldn not be obtained because the database is in use." (I
t
seems to me it's not in use, nobody uses this server yet.)
Strange thing is, I can restore another (test) database from same tape
without any problems.
Happy to get any hints or guidelines, I'm kinda stuck.I deleted the restored database on new SQL server an reran the restore job,
and everything worked OK -- and so I will never know what went wrong the
first time, but will nevertheless be able to spend the weekend with family
instead of SQL.
Thanks for taking time, if you took any.
"JSL" wrote:

> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
> I'm restoring db from tape w. BackupExec 9.0. The first time I did a resto
re
> it was cancelled after 10% write; error 34113 on BackupExec server, and
> repeated error 57859 on destination SQL server.
> When rerun job, no data is written and job cancels with same error in
> BackupExec server, and new error in destination SQL server: 57859 --
> "Exclusive access couldn not be obtained because the database is in use."
(It
> seems to me it's not in use, nobody uses this server yet.)
> Strange thing is, I can restore another (test) database from same tape
> without any problems.
> Happy to get any hints or guidelines, I'm kinda stuck.|||Next time, use sp_who to see who is using the database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JSL" <JSL@.discussions.microsoft.com> wrote in message
news:90762CE8-604D-4BD5-A1DE-9645952022C9@.microsoft.com...[vbcol=seagreen]
>I deleted the restored database on new SQL server an reran the restore job,
> and everything worked OK -- and so I will never know what went wrong the
> first time, but will nevertheless be able to spend the weekend with family
> instead of SQL.
> Thanks for taking time, if you took any.
> "JSL" wrote:
>sql

Restore Database Dialog Shows Old Backup File Location

We're running SQL 7.0 (SP4,MS03-031) on Windows 2000. We recently
moved our database backups from the D:\ drive to the E:\ drive. In
the process, we dropped all of our old backup devices and created new
ones pointing to the new drive. The backups have been running
successfully for several weeks now; sending data to the new location.
The other day I needed to restore a database. While reviewing the
restore database dialog information, I noticed that the old path
(D:\)appeared under "Restore from" column. The other information;
type, backup set date and size are correct and apply to the backup
file on the E:\ drive. I attempted the restore and naturally received
an error.
I've checked sysdevices and found it has the correct location for the
backup files.
Any ideas why this could be and any suggestions on how to fix it?
Thanks!
Michael Brule
Database Administrator
The Phoenix CompaniesThe first 3 links should be relevant but the rest may also be of interest:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly
SQL Server MVP
"michael brule" <michael.brule@.phoenixwm.com> wrote in message
news:55f7800f.0402181409.25c474c4@.posting.google.com...
> We're running SQL 7.0 (SP4,MS03-031) on Windows 2000. We recently
> moved our database backups from the D:\ drive to the E:\ drive. In
> the process, we dropped all of our old backup devices and created new
> ones pointing to the new drive. The backups have been running
> successfully for several weeks now; sending data to the new location.
> The other day I needed to restore a database. While reviewing the
> restore database dialog information, I noticed that the old path
> (D:\)appeared under "Restore from" column. The other information;
> type, backup set date and size are correct and apply to the backup
> file on the E:\ drive. I attempted the restore and naturally received
> an error.
> I've checked sysdevices and found it has the correct location for the
> backup files.
> Any ideas why this could be and any suggestions on how to fix it?
> Thanks!
> Michael Brule
> Database Administrator
> The Phoenix Companies|||I had the same problem before.
You can restore the database from the restore diaglog
panel by choosing "From device" rather than "database".
Fix the problem permanently is to delete the old backup
files on D:\ drive, the restore diaglog panel should show
correctly after the backup run on E:\ drive.|||Thanks for the replies, Andrew and Johnny!
Andrew: The information you provided seemed to concern issues
surrounding moving a database to a new location My question was about
moving database backup files. The databases remain in their original
location.
Johnny: Actually, we moved the backup directory to the new location.
Neither that directory nor any of its files remains in the original
location. Numerous backups have been run since.
Thanks!
Michael Brule
Database Administrator
The Phoenix Companies|||Some of the links refer to methods that can be used to move to a new server
or just a new location. You can either use RESTORE with the MOVE option or
sp_attach_db. Both are covered in there as well as BooksOnLine.
--
Andrew J. Kelly
SQL Server MVP
"michael brule" <michael.brule@.phoenixwm.com> wrote in message
news:55f7800f.0402190654.660f72e5@.posting.google.com...
> Thanks for the replies, Andrew and Johnny!
> Andrew: The information you provided seemed to concern issues
> surrounding moving a database to a new location My question was about
> moving database backup files. The databases remain in their original
> location.
> Johnny: Actually, we moved the backup directory to the new location.
> Neither that directory nor any of its files remains in the original
> location. Numerous backups have been run since.
> Thanks!
> Michael Brule
> Database Administrator
> The Phoenix Companies|||Sorry.
The files in the new location ie E:\ have to be deleted as
well.
Overwritten the existing backup files still showed the old
backup directory path in the restore panel. If you don't
want to delete all the backup files in one go, you may
delete the oldest backup files until all are recycled.

Restore a database from Yukon to SQL 2000 SP4 edition?

Hello,
I have a siuation that need restore a testing database that currently running on Yukon server to SQL 2000 SP4 staging server. I am getting an error when I go with filelistonly option to see if its possible.
### Error Starts ###
Server: Msg 3169, Level 16, State 1, Line 1
The backed-up database has on-disk structure version 603. The server supports version 539 and cannot restore or upgrade this database.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE FILELIST is terminating abnormally.
### Error Ends ###

Yes, I am trying to downgrade it, any way that I can do?

Thanks in advance.

Sunny Jung

Sunny,

There is no way to downgrade. You can try to export the data and them import it. But this isn't a scenario we test.

Dan

Restore a basebase on sql server 2000 sp4 from a backup from sql server 2000 sp3

Is this safe. or can it cause any problems.
The reson I ask is because I see the following error "[DBNetlinb]
connectioncheckfordata" when I execute (from query analyser or osql)
Insert Into temptable select ... from [databasesource].source ...
both databases running on the same server
I have an number of insert to temptable and only one of them fails. But if I
use a top it works.
Insert Into temptable select top 1000... from [databasesource].source ..
.
And another thing I have tested it before the upgrade from sp3 to sp4 and
everything work fine.
Any clue.
Thank
LasseServer
I have just restored a database from SP3 to SP4. Works fime for me.
"Server Applications" <NoSpam@.dk.dk> wrote in message
news:O5zPA3e5FHA.1464@.tk2msftngp13.phx.gbl...
> Is this safe. or can it cause any problems.
> The reson I ask is because I see the following error "[DBNetlinb]
> connectioncheckfordata" when I execute (from query analyser or osql)
> Insert Into temptable select ... from [databasesource].source ...
> both databases running on the same server
> I have an number of insert to temptable and only one of them fails. But if
> I
> use a top it works.
> Insert Into temptable select top 1000... from [databasesource].source
..
> And another thing I have tested it before the upgrade from sp3 to sp4 and
> everything work fine.
> Any clue.
> Thank
> Lasse
>

Restore a basebase on sql server 2000 sp4 from a backup from sql server 2000 sp3

Is this safe. or can it cause any problems.
The reson I ask is because I see the following error "[DBNetlinb]
connectioncheckfordata" when I execute (from query analyser or osql)
Insert Into temptable select ... from [databasesource].source ...
both databases running on the same server
I have an number of insert to temptable and only one of them fails. But if I
use a top it works.
Insert Into temptable select top 1000... from [databasesource].source ...
And another thing I have tested it before the upgrade from sp3 to sp4 and
everything work fine.
Any clue.
Thank
Lasse
Server
I have just restored a database from SP3 to SP4. Works fime for me.
"Server Applications" <NoSpam@.dk.dk> wrote in message
news:O5zPA3e5FHA.1464@.tk2msftngp13.phx.gbl...
> Is this safe. or can it cause any problems.
> The reson I ask is because I see the following error "[DBNetlinb]
> connectioncheckfordata" when I execute (from query analyser or osql)
> Insert Into temptable select ... from [databasesource].source ...
> both databases running on the same server
> I have an number of insert to temptable and only one of them fails. But if
> I
> use a top it works.
> Insert Into temptable select top 1000... from [databasesource].source ...
> And another thing I have tested it before the upgrade from sp3 to sp4 and
> everything work fine.
> Any clue.
> Thank
> Lasse
>

Restore a basebase on sql server 2000 sp4 from a backup from sql server 2000 sp3

Is this safe. or can it cause any problems.
The reson I ask is because I see the following error "[DBNetlinb]
connectioncheckfordata" when I execute (from query analyser or osql)
Insert Into temptable select ... from [databasesource].source ...
both databases running on the same server
I have an number of insert to temptable and only one of them fails. But if I
use a top it works.
Insert Into temptable select top 1000... from [databasesource].source ...
And another thing I have tested it before the upgrade from sp3 to sp4 and
everything work fine.
Any clue.
Thank
LasseServer
I have just restored a database from SP3 to SP4. Works fime for me.
"Server Applications" <NoSpam@.dk.dk> wrote in message
news:O5zPA3e5FHA.1464@.tk2msftngp13.phx.gbl...
> Is this safe. or can it cause any problems.
> The reson I ask is because I see the following error "[DBNetlinb]
> connectioncheckfordata" when I execute (from query analyser or osql)
> Insert Into temptable select ... from [databasesource].source ...
> both databases running on the same server
> I have an number of insert to temptable and only one of them fails. But if
> I
> use a top it works.
> Insert Into temptable select top 1000... from [databasesource].source ...
> And another thing I have tested it before the upgrade from sp3 to sp4 and
> everything work fine.
> Any clue.
> Thank
> Lasse
>