Hi Ruslan,
Let's start from SQL 2014 topic. The case is that we decided to skip this release as there were no customer demand at the time. I anyhow know that there is customers using this release, but from combatibility guide you won't found SQL 2014.
Then how to move from old to never release. This guidange is not SQL vesion specific and can be used in other cases as well. The guidance expects that you have a service break and application is turned off to avoid data corruptions.
1. Turn of CCtr services
2. Take backup of existing databases
3. Restore backup to new SQL server
Please note that a backup contains also other data from the source, like database location in file system
4. In IA change database destinations to point to the new destination (expecting that old cluster and new has different name). Once changed do 'syncronize instances'
5. Once syncronized select "upgrade all software" on HAC level (HAC node -> VU name -> software -> right click -> Ipgrade All Software). This forces installer to run database update scripts and new database destination is succesfully written to configuration.
6. Run command 'apply changes to host / local host' to finish the task.
7. Turn on the services and test that everything is working fine.
And of course we recommend to take backups before starting the procedure and you should also practice this on QA/DEV environment before going to production.
//Jukka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.