October 16, 2016 at 5:08 am
Hi all,
Its a new build and we have to migrate clustered sql servers instances.
In old, sql server is 2005,2008 and 2012 and in new its 2014.
Below steps I was thinking:
1) Install sql server 2-node cluster in new servers
2) Install sql server instances
This will create MASTER,MSDB,MODEL, TEMPDB,RESOURCE databases.
3) script everyhting from master and msdb like jobs,linked servers,logins,permissions,roles,credentials etc from source and run in new sql server 2014
This will populate master and msdb databases in target with information as in source
4) Over the SAN, drives would be copied. So, just attach the user databases in target
Would you like to add/remove in above steps?
Regards,
Yasir
October 16, 2016 at 5:47 am
Looks fine to me, normally I script transferable logins from the source and after attachment then run the scripts on the destination.
😎
Quick question out of curiosity, why SQL Server 2014 and not SQL Server 2016?
October 16, 2016 at 5:57 am
After attaching the databases, you should consider upping their compatibility levels, to take advantage of all the new features. After testing, of course.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
October 16, 2016 at 6:09 am
Hi Eirikur,
Thanks for replying.
Its a client requirement to install 2014.
October 16, 2016 at 7:07 am
For clustering, I need to gather maximum info from existing clustered environment.
Can you share some checklist for migrating clustered environment?
October 19, 2016 at 9:21 am
ysrhashmi (10/16/2016)
4) Over the SAN, drives would be copied. So, just attach the user databases in target
Introducing these into the cluster as disk resources can be tricky unless you know what you're doing. Do the LUNs contain just user database files?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 20, 2016 at 1:19 am
No, LUNS would be containing system databases and user databases both.
Its like C:,D:,E:,F:
Since its an upgrade also, I cannot restore backups of system databases onto new versions.
Can you explain what all precautions need to be taken to migrate instances and databases?
Regards,
Yasir
October 20, 2016 at 7:15 am
so just backup user databases from the source servers and restore them onto the new cluster
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 21, 2016 at 1:14 pm
Once you have the databases on the new SQL 2014 server run integrity check and update stats. Also, then run a full db backup... SO... if something goes wrong you have a good starting point. Like someone else stated if the apps support it change the compatibility to SQL 2014.
I hope your plan includes heavy testing on a non prod SQL 2014... remember the optimizer has changed drastically in 2014.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply