SOLUS3 Database Migration to SQL2012. : Nicolas Attwood Authorised by :

Transcription

1 SOLUS3 Database Migration to SQL2012 Author : Nicolas Attwood Authorised by : Version : 1.1 Date : 25/06/2013

2 Table of Contents PAGE 1 INTRODUCTION PURPOSE: SCOPE: ASSUMPTIONS AND CONSTRAINTS: PROCESS DISCONNECTING THE SOLUS3 DATABASE MOVING THE DATABASE AMENDING SOLUS DOCUMENT CONTROL Version: 1.1 Page 2 of 21

3 1 INTRODUCTION 1.1 Purpose: Procedure document for migrating the SOLUS3 SQL database and SIMS, FMS and Discover SQL targets from a SQL 2008/R2 instance to a SQL 2012 instance. 1.2 Scope: All requests from schools which have logged a call to the IT Helpdesk. 1.3 Assumptions and Constraints: It is assumed that the person carrying out this task: Has a login with System Administration rights to the server which they are carrying out the procedure on. That the procedure is being carried out on a Windows 7 or Windows Server 2008/R2 server. Has checked that the school has applied at least the update for SOLUS3. Knows that the server meets the recommended Capita Hardware Specification. Is an ICT technician with adequate technical knowledge and knowledge of the local network. Is from a CSD supported school with a valid SIMS license. Has a server which is a CSD Schools standard configuration. Has already migrated SIMS, FMS and Discover (if applicable) to SQL Has installed SQL Server 2012 Management Studio. Important Please be aware that even if you have purchased a server from CSD, unless a CSD engineer has configured the machine for you the server may have been set up differently. This may mean that some drives on your server setup, do not match to places that are specified in this procedure document. Version: 1.1 Page 3 of 21

4 2 PROCESS 2.1 Disconnecting the SOLUS3 Database Important Please make sure that you are signed into the server as administrator. If you are not sure if you are logged in as Administrator, STOP NOW! This process needs to be carried out with a login with administrator rights to minimise any potential issues. If you don t know the administrator user name and password, please contact your IT support to find out or arrange for them to carry out the migration on your behalf. Important Please make sure you have installed SQL Server 2012 Management Studio. If you have not, STOP NOW! This process is a lot easier with SQL Server 2012 Management Studio and cannot be carried out with DbAttach. If you have not installed SQL Server 2012 Management Studio, it can be downloaded using these links. Important If you are moving the SOLUS3 database to a new server with a different name, please uninstall all the SOLUS3 agents from all the workstations and from the SOLUS3 UI. This will save time and prevent a problem with the SOLUS3 agents connecting to the server. Click Start All Programs Microsoft SQL Server 2012 Open SQL Server Management Studio. Log onto the SIMS2008 server instance. TIP E.G. server instance: myserver\sims2008 Make sure the authentication selected from the dropdown menu is SQL Server Authentification. Use the SA username and password to log into the server instance. Version: 1.1 Page 4 of 21

5 Once logged into the SIMS2008 server instance, expand Databases. Right click on the solus3_deployment_server and open Tasks. Select Back Up Version: 1.1 Page 5 of 21

6 Click OK and let the backup process run through. If successful, the message above will appear. This backup gives us some extra security if anything goes wrong. Version: 1.1 Page 6 of 21

7 Right click on the solus3_deployment_server again and open Tasks. Select Detach Tick Drop Connections and Update Statistics. Click OK and then allow the process run through. Once finished, right click the server instance and select Disconnect. Version: 1.1 Page 7 of 21

8 2.2 Moving the Database Open My Computer by using the Computer shortcut on the desktop or by clicking Start Computer Navigate to the DATA folder, in the SQL instance folder. TIP Examples of DATA folder locations are: G:\Capita\MSSQL10_50.SIMS2008\MSSQL\DATA G:\MSSQL10_50.SIMS2008\MSSQL\DATA S:\MSSQL10_50.SIMS2008\MSSQL\DATA D:\MSSQL10_50.SIMS2008\MSSQL\DATA TIP Pleases be aware if you have SQL 2008 and not SQL 2008 R2, the SQL folder instance folder will start with MSSQL10. Copy solus3_deployment_server.mdf and solus3_deployment_server.ldf. Both files do need to be copied or else the migration will fail. Paste the files into the DATA folder for SQL Depending on if you are performing an upgrade or TIP SQL 2012 folder instance will start with MSSQL11 Important If you are copying the solus3_deployment_server database to another server, you will need to install SOLUS3 on the new server, then detach and remove the solus3 database created by the install. Then paste in the solus3_deployment_server database files and then you will be able to attach them. Version: 1.1 Page 8 of 21

9 Attaching the SOLUS3 Database Select Connect and then Database Engine Log onto the SIMS2012 server instance. TIP E.G. server instance: myserver\sims2008 Make sure the authentication selected from the dropdown menu is SQL Server Authentication. Use the SA username and password to log into the server instance. Once logged into the SIMS2012 server instance, right click on Databases. Then select Attach Version: 1.1 Page 9 of 21

10 Click Add and navigate to the DATA folder where the solus3_deployment_server.mdf and solus3_deployment_server.ldf where stored. Version: 1.1 Page 10 of 21

11 Select the solus3_deployment_server.mdf and click OK. Version: 1.1 Page 11 of 21

12 The Attach Databases UI should now be populated. Please check in the database details to make sure that there is a data and log file type. If there is click OK and start the process for attaching databases. If successful, the database should now appear in Databases for the SIMS2012 server instance. Version: 1.1 Page 12 of 21

13 2.3 Amending SOLUS3 Click Start All Programs Solus 3 Open SOLUS 3 Deployment Server connection string editor Change the instance from sims2008 to sims2012, keeping the server name the same. Click Test And Save If successful the following message will appear. Click Start All Programs Solus 3 Open SOLUS 3 Deployment Server UI connection string editor and check to see if the change has been made. Version: 1.1 Page 13 of 21

14 Open SOLUS3, either by the shortcut SOLUS 3 Deployment Server UI on the desktop or by clicking Start All Programs Solus 3 SOLUS 3 Deployment Server UI Select System Settings Check under the SOLUS3 tab that the Deployment database instance name has changed to SIMS2012. If the setting is incorrect, amend and then save. Otherwise click close to return to main menu. Open SOLUS3 Agents and click Update Environment. Click Move SQL database targets. Version: 1.1 Page 14 of 21

15 Select all the databases you want to move and click Next. If the SQL System Administrator password was changed when the SQL 2012 instance was installed, please change the password now and click Next. If you did not change the password when the SQL 2012 instance was installed, click Next. Version: 1.1 Page 15 of 21

16 Unless you have put in some of the SQL server targets already you will need to create a new SQL server target. Click Select, add the server which you installed the SQL 2012 instance on and click Save. Add the Instance Name and Binn folder location. Click Next. Version: 1.1 Page 16 of 21

17 Check to make sure that these are the databases which you want to migrate and then click Finish. If successful, the message above should appear. If you now check the settings in channels, all relevant settings should now be changed to the SQL 2012 instance. Version: 1.1 Page 17 of 21

18 Click System Settings. Click Workstation Settings. Version: 1.1 Page 18 of 21

19 Although the settings may be correct, the actual configuration within the connect.ini file will be wrong. Click and browse to where SOLUS3 access the connect.ini. Right click the connect.ini file and select Edit. Edit the server instance to the SQL 2012 server instance and then save. Select the connect.ini file and then click Open. Any settings that are incorrect will now be correct. Click the tick box for If ALL entries in the local connect.ini file should be overwritten tick this check box. Version: 1.1 Page 19 of 21

20 Click Send Connect.ini to agents. Do the same for the FMSconnect.ini file. Any settings that are incorrect will now be correct. Click the tick box for If ALL entries in the local fmsconnect.ini file should be overwritten tick this check box. Click Send FMSconnect.ini to agents. If you have Discover, make sure the settings are correct for the Sims server and Discover server and then click Update Discover config. Once done click Save or Close. You now have successfully migrated SOLUS3. Version: 1.1 Page 20 of 21

21 DOCUMENT CONTROL Changes History Version Date Amended By Change CR No 0.a 26 th June a 12 th Febuary 2014 Initial Draft for review (no action taken on this version) N/A Nicolas Attwood Procedure document creatation. N/A /02/14 Tina Jackaman Re Branded Approval (CSD) Role Name Signed Date Authorisation (Client) Role Name Signed Date Reviewers Reviewer(s) Name(s) Role & Review Responsibilities Once authorised Name All CSD Staff All Service Transformation Teams Distribution List Organisation Customer Service Direct Customer Service Direct Version: 1.1 Page 21 of 21