April 24, 2009 at 6:59 am
In the past our systems team has moved a server to new hardware by removing all disks, including the C drive with operating system and moving them to new hardware, successfully. For sql server we've always created a new box with a fresh sql install ( usually giving the new server the same name and IP address, but not always ), detached/copied/reattached the databases and migrated logins.
Now the proposal is to move ALL disks include the OS drive from a sql server to a new server. Have you had success doing that?
April 24, 2009 at 9:02 am
Hi,
First of all I dont understand why you want to move all the disks and why it is needed. Instead you can do a backup and restore. This is what ms recommends to move databases from one server to another server. I think you will not be successful. Also checkout with your hardware team and also check whether the new server hardware is supported by sql server or not. And also checkout what is the ram between these two servers and network cards. Because sometimes even though you have enough memory you will be surprised when you learn that sql server is not utilising and the memory is lying idle. I think you might require to configure your memory configurations on the new server after successful move.
Thanks
Chandra Mohan N
[font="Verdana"]Thanks
Chandra Mohan[/font]
April 24, 2009 at 9:10 am
My concern wouldn't be with CPU or memory. I assume you're going up with both, otherwise why move?
My concern is drivers and Windows. SQL doesn't care. You get the drive letters correct and it works fine. The issues with moving hardware are often Windows based.
April 24, 2009 at 10:54 am
Another reason for doing it this way, I have many maintenance plans, jobs PLUS LOG SHIPPING running on the existing sql box. New box will have same network name and IP.
I have a script for migrating logins but if this approach works it would be easier. I'm waiting to hear if anyone has actually done it ( new hardware, no fresh install of sql, move ALL disks from old server to new including those with system DBs and OS ).
I'm not overly concerned about drivers, etc as those can always be updated, network cards swapped out etc. If the old box had a C and F ( data ) drive and the new box does also, where's the downside?
April 24, 2009 at 11:33 am
IS this virtual Server to Virtual server move or physical server to Physical server move. If it is physical to physical move i would suggest not going for it becase i have seen firmware and O/S intraction issues.
April 24, 2009 at 11:36 am
DB2008 (4/24/2009)
IS this virtual Server to Virtual server move or physical server to Physical server move. If it is physical to physical move i would suggest not going for it becase i have seen firmware and O/S intraction issues.
It's physical to physical server. What do you mean by intraction issues?
April 24, 2009 at 12:00 pm
I think he means interaction issues, issues conflicting between firmware and the install.
April 24, 2009 at 12:03 pm
SQL doesn't care about IP, network, etc. It does care about local paths, as those are how it finds the database files. If those change, you can fix things.
What you describing is a DR situation. It functions the same, and you don't have disks.
You install a new server, install SQL, THEN restore master, msdb and all other databases (or attach the files). This gives you your logins, jobs, log shipping, etc.
This gives you a server. When you are ready, rename the windows server, rename the SQL Server (sp_dropserver, sp_addserver) and then change the IP. Be sure the old server is disconnected.
April 24, 2009 at 12:12 pm
Our systems team has done this numerous times with servers that don't house sql server. Almost all are windows 2003 server OS. If this will work for sql it would make my life easier since the system DBs and client DBs are moved with the disks so theoretically all databases, logins, sql agent jobs, maintenance plans and log shipping are moved.
( yes we will keep the same disk drive arrangement with OS and system DBs on C, client data on F and pagefile on another drive ).
Whatever OS/firmware issues have occurred when doing this on non-sql boxes were apparently minor and a known quantity. Old box is taken down and off network first. New box has same name and IP.
April 24, 2009 at 12:24 pm
If the OS team is comfortable, and drive letters are the same, you should be fine.
Backup, be sure you're covered, and I'm sure things will be OK.
April 24, 2009 at 5:13 pm
Like one of the replier indicated, backup and restore.. Or, backup, detach, copy detached to the new destination and attach.
You can not just copy the drives that have associated DLLs simply said.
good luck.
Cheers,
John Esraelo
April 24, 2009 at 6:13 pm
John Esraelo (4/24/2009)
Like one of the replier indicated, backup and restore.. Or, backup, detach, copy detached to the new destination and attach.You can not just copy the drives that have associated DLLs simply said.
good luck.
Nothing will be copied. If the new server has any disk drives, they will all be removed. The drives from the old server, including the C drive and the attached powervault disk array, will be removed from the old server and installed in the new server.
April 24, 2009 at 7:26 pm
I see, hmmm, I would still watch out for the hardware compatilities and RAID array controller compatibilities too..
make sure you have a very good verified backup of all the databases including the master for that matter first. In fact, I would try to restore the backup somewhere else to make sure that it is restorable in case something goes wrong.
good luck.
Cheers,
John Esraelo
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply