Restore to different version of 2003 OS

Hello,
I have a client with a database and want to use a second server as warm spare.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:
> Hello,
> I have a client with a database and want to use a second server as warm spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
> > Hello,
> > I have a client with a database and want to use a second server as warm spare.
> > Primary server is 2003 Std and the spare is 2003Ent.
> > I've heard that the OS must be the same to restore.
> > I can understand the SQL needs the same version 2000 and service pack level
> > on each server but what about the OS?
> >
> > Thanks in advance
> >
> > Kevin

Restore to different version of 2003 OS

Hello,
I have a client with a database and want to use a second server as warm spare.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David
|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin
|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:

> Hello,
> I have a client with a database and want to use a second server as warm spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack level
> on each server but what about the OS?
> Thanks in advance
> Kevin
|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
[vbcol=seagreen]
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:

Restore to different version of 2003 OS

Hello,
I have a client with a database and want to use a second server as warm spar
e.
Primary server is 2003 Std and the spare is 2003Ent.
I've heard that the OS must be the same to restore.
I can understand the SQL needs the same version 2000 and service pack level
on each server but what about the OS?
Thanks in advance
Kevin"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
>
The OS can be different.
David|||To restore a system database, the SQL build numbers must match exactly. To
restore a non-system database, the major levels must match (I.E 7.0, 8.0,
9.0 etc). The operating system does not matter as long as it is supported
for that release of SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Kevin1aB" <Kevin1aB@.discussions.microsoft.com> wrote in message
news:5B30FD35-4E84-474F-8240-E812C27E548A@.microsoft.com...
> Hello,
> I have a client with a database and want to use a second server as warm
> spare.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack
> level
> on each server but what about the OS?
> Thanks in advance
> Kevin|||While I agree with what the others have posted, you are going to test this
all first, right?
"Kevin1aB" wrote:

> Hello,
> I have a client with a database and want to use a second server as warm sp
are.
> Primary server is 2003 Std and the spare is 2003Ent.
> I've heard that the OS must be the same to restore.
> I can understand the SQL needs the same version 2000 and service pack leve
l
> on each server but what about the OS?
> Thanks in advance
> Kevin|||Thanks to all who posted. I will test it in the next week or so.
Regards,
Kevin B
"ChrisR" wrote:
[vbcol=seagreen]
> While I agree with what the others have posted, you are going to test this
> all first, right?
> "Kevin1aB" wrote:
>

restore question on sql2000

Hi
I have a 60 GB sql 2000 STD edition database backup.
I take backup on a remote machine A where I can restore it.
But I have to restore the same database on another machine B where it can
not restore it.
I have already copied the file over a very slow network and when I say
restore and select the backup file I do not see any datafiles listed. I clic
k
on "VIEW CONTENTS" and there is nothing.
What could cause this as same backup seen on the Machine A is fine but when
moved to machine B I can not "view the contents" and restore it.
All the version across all these machines are same.
Tks
MangeshHi
I found the reason. The copy command is still running on the Machine A for
12 hrs.
I did not know that copy command creates the file size as that of source
when it starts copy unlike ftp.
Thanks
Mangesh
"Mangesh Deshpande" wrote:

> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I cl
ick
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but whe
n
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh|||Hi Mangesh,
You can try using Query Analyzer from ServerB to restore DB's from remote
locations. It is possible the backup gets corrupt during the copy. At leas
t
you can try listing the contents remotely; try this:
--
-- i.e. EXEC xp_cmdshell 'command' <-- remove any <ENTER> bewteen quotes (''
)
-- ServerA is the remote DB Server
-- Share the remote backup folder, in this example is ShareDriveA
-- account is a domain account with access to the shared folder
-- accountpassword (account password)
-- ACCOUNTDOMAIN is the domain where 'account' belongs to
EXEC xp_cmdshell 'net use \\ServerA\ShareDriveA accountpassword
/USER:ACCOUNTDOMAIN\account'
GO
-- to test if the account you used has access to the remote folder
EXEC xp_cmdshell 'dir \\ServerA\ShareFolderA\BackupFolder'
GO
-- to list the backup contents
RESTORE FILELISTONLY
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\Back
upFile.BAK'
-- to finally restore the backup
RESTORE DATABASE DatabaseName
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\Back
upFile.BAK'
WITH REPLACE,
MOVE 'LogicalFileName_Data' TO 'C:\SQLdata\DatabaseName.MDF',
MOVE 'LogicalFileName_Log' TO 'C:\SQLdata\DatabaseName.LDF'
--
"Mangesh Deshpande" wrote:

> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I cl
ick
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but whe
n
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh

restore question on sql2000

Hi
I have a 60 GB sql 2000 STD edition database backup.
I take backup on a remote machine A where I can restore it.
But I have to restore the same database on another machine B where it can
not restore it.
I have already copied the file over a very slow network and when I say
restore and select the backup file I do not see any datafiles listed. I click
on "VIEW CONTENTS" and there is nothing.
What could cause this as same backup seen on the Machine A is fine but when
moved to machine B I can not "view the contents" and restore it.
All the version across all these machines are same.
Tks
Mangesh
Hi
I found the reason. The copy command is still running on the Machine A for
12 hrs.
I did not know that copy command creates the file size as that of source
when it starts copy unlike ftp.
Thanks
Mangesh
"Mangesh Deshpande" wrote:

> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh
|||Hi Mangesh,
You can try using Query Analyzer from ServerB to restore DB's from remote
locations. It is possible the backup gets corrupt during the copy. At least
you can try listing the contents remotely; try this:
-- i.e. EXEC xp_cmdshell 'command' <-- remove any <ENTER> bewteen quotes ('')
-- ServerA is the remote DB Server
-- Share the remote backup folder, in this example is ShareDriveA
-- account is a domain account with access to the shared folder
-- accountpassword (account password)
-- ACCOUNTDOMAIN is the domain where 'account' belongs to
EXEC xp_cmdshell 'net use \\ServerA\ShareDriveA accountpassword
/USER:ACCOUNTDOMAIN\account'
GO
-- to test if the account you used has access to the remote folder
EXEC xp_cmdshell 'dir \\ServerA\ShareFolderA\BackupFolder'
GO
-- to list the backup contents
RESTORE FILELISTONLY
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK '
-- to finally restore the backup
RESTORE DATABASE DatabaseName
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK '
WITH REPLACE,
MOVE 'LogicalFileName_Data' TO 'C:\SQLdata\DatabaseName.MDF',
MOVE 'LogicalFileName_Log' TO 'C:\SQLdata\DatabaseName.LDF'
"Mangesh Deshpande" wrote:

> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh

restore question on sql2000

Hi
I have a 60 GB sql 2000 STD edition database backup.
I take backup on a remote machine A where I can restore it.
But I have to restore the same database on another machine B where it can
not restore it.
I have already copied the file over a very slow network and when I say
restore and select the backup file I do not see any datafiles listed. I click
on "VIEW CONTENTS" and there is nothing.
What could cause this as same backup seen on the Machine A is fine but when
moved to machine B I can not "view the contents" and restore it.
All the version across all these machines are same.
Tks
MangeshHi
I found the reason. The copy command is still running on the Machine A for
12 hrs.
I did not know that copy command creates the file size as that of source
when it starts copy unlike ftp.
Thanks
Mangesh
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh|||Hi Mangesh,
You can try using Query Analyzer from ServerB to restore DB's from remote
locations. It is possible the backup gets corrupt during the copy. At least
you can try listing the contents remotely; try this:
--
-- i.e. EXEC xp_cmdshell 'command' <-- remove any <ENTER> bewteen quotes ('')
-- ServerA is the remote DB Server
-- Share the remote backup folder, in this example is ShareDriveA
-- account is a domain account with access to the shared folder
-- accountpassword (account password)
-- ACCOUNTDOMAIN is the domain where 'account' belongs to
EXEC xp_cmdshell 'net use \\ServerA\ShareDriveA accountpassword
/USER:ACCOUNTDOMAIN\account'
GO
-- to test if the account you used has access to the remote folder
EXEC xp_cmdshell 'dir \\ServerA\ShareFolderA\BackupFolder'
GO
-- to list the backup contents
RESTORE FILELISTONLY
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK'
-- to finally restore the backup
RESTORE DATABASE DatabaseName
FROM DISK = '\\ServerA\ShareFolder\BackupFolder\BackupFile.BAK'
WITH REPLACE,
MOVE 'LogicalFileName_Data' TO 'C:\SQLdata\DatabaseName.MDF',
MOVE 'LogicalFileName_Log' TO 'C:\SQLdata\DatabaseName.LDF'
--
"Mangesh Deshpande" wrote:
> Hi
> I have a 60 GB sql 2000 STD edition database backup.
> I take backup on a remote machine A where I can restore it.
> But I have to restore the same database on another machine B where it can
> not restore it.
> I have already copied the file over a very slow network and when I say
> restore and select the backup file I do not see any datafiles listed. I click
> on "VIEW CONTENTS" and there is nothing.
> What could cause this as same backup seen on the Machine A is fine but when
> moved to machine B I can not "view the contents" and restore it.
> All the version across all these machines are same.
> Tks
> Mangesh