- Stop any processes that might be accessing your SharePoint databases
- Back up all your SharePoint databases on SQL A.
- Restore them on SQL B.
- Set up a SQL alias on SharePoint that points SQL A to SQL B
Stop any processes that might be accessing your SharePoint databases
Open services.msc and stop:
· SharePoint 2010 Administration
· SharePoint 2010 Timer
· SharePoint Server Search 14
· SharePoint Tracing
· World Wide Web Publishing Service
Check your actual database server in Central Admin and be sure that you are using a SQL alias.
(a SQL alias can be made by using the CLICONFG-command)
Check which databases are being used by SharePoint within Central Admin
Backup all these databases on SQL server A (SQLCluster) with SQL Management Studio
Put all databases on Offline after making the SQL Backup
Copy all BAK-files (SQL Backup files) to the new SQL server
Set up a SQL alias on SharePoint that points SQL A to SQL B (Start-Run-cliconfg)
Enter the same SQL Server alias but change the connection parameters to the new servername\instancename