March 9, 2012 at 12:12 am
The new data center is almost ready to install new OS (Windows Server 2008 R2) and new SQL Server version (SQL Server 2008 R2 EE).
Right now we have a box (MSCS Cluster) with almost 100 databases on SQL Sever 2000 EE and Windows Server 2003.
Due to the fact that this old HW is out of maintenance, we would like to temporary move this box to the new data center without changing anything.
The idea is to create a new VM (Windows Server 2003) in the new data center, install on it SQL Server 2000 EE with exactly the same parameters of the old one including database and log path, and then:
1. shutdown SQL Server on the old box
2. copy all users databases + system databases master, model and msdb to the new data center
3. shutdown the new installed SQL Server 2000
4. substitute system db master model and msdb of this new installation with the old ones copied from the old box to maintain logins, jobs, alerts....
5. start up SQL Server on the new data center
Do you think that this can be a practical way?
Any suggestions?
Thank you very much.
Frank
Franco
March 9, 2012 at 12:19 am
Which hypervisor are you using?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 9, 2012 at 12:34 am
The new data center is based on vmWare.
Franco
March 9, 2012 at 1:11 am
one thing i would say as well is with the move from 2000 to 2008 I would only copy the user databases not the system databases, dont restore them over the new copies of master/model/msdb
you will need to script out all server objects like logins, jobs, linked servers etc due to the changes in the system databases in the newer versions
March 9, 2012 at 1:17 am
I don't need to upgrade to sql 2008 right now.
If you read my post you will see that I only need to replicate or move sql 2K to a new box.
Franco
March 9, 2012 at 1:20 am
Sorry, I was focused on the Server 2008 and SQL 2008R2 line at the top.
March 9, 2012 at 12:05 pm
Is VMs physical to virtual (P2V) process and option?
March 11, 2012 at 1:38 am
It's a MSCS Cluster, so no PTV available.
We would like to install a new single machine, same name, same parameters, same memory, same disks, same path, same everything... in the new data center.
Franco
March 14, 2012 at 3:08 am
Has anybody done the same thing?
My concern is because the old instance in the old data center is clustered and the new instance in the new datacenter will be non cluster.
There are some information at the database level that is related to the fact that SQL Server is now clustered?
We will maintain the same server name, same disks, same path, same memory, same number of processors.
Our goal is to be able to start the new sql server in the new datacenter with all the same user databases, including master,model and msdb.
Please advise.
Franco
March 14, 2012 at 3:20 am
you wont able to restore the master to new data center directly. you can transfer the logins and script out theSQL agent job and move to new server.
March 14, 2012 at 9:30 am
Could you please explain to me why?
Franco
March 14, 2012 at 9:42 am
I've never tried it, but I thought that the master db was aware of the cluster, and if you are trying to replace a non-clustered master with a clustered master, you will have issues.
I'd be curious if this works.
March 14, 2012 at 9:52 am
Steve, thank you very much for your reply.
In fact this was also my concern, the cluster.
There is a very good article here:
http://vyaskn.tripod.com/moving_sql_server.htm
But it's not talking about cluster.
Franco
March 14, 2012 at 1:00 pm
I found this reply from MVP Andrew J.Kelly, in another forum:
The database knows nothing of if it is or ever was in a clustered server or
not.
Andrew J. Kelly SQL MVP
Any other ideas?
Franco
March 14, 2012 at 1:37 pm
Nope, asked a few people, no one is sure.
Ultimately, I'd test it. Make a VM, set it up, copy the master.mdf over and see if it works.
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply