On SU-SQL-2 restore the SafeCom databases

1. On SU-SQL-2 open SQL Server Management Studio.

2. Login to the SQL server and browse to Databases.

3. For each of SafeCom SQL databases:

• sccore

• scevent

• scpurse

• sctracking

4. Right-click sccore and select Tasks, Restore, Database…

5. Click From device. Click […].

6. In the Specify Backup dialog click Add and browse to the Backup File sccore.bak. Click OK.

7. Click OK.

8. In the Restore column check the sccore database.

9. In Select a page click Options. Check Overwrite the existing database.

Leave Recovery state at the default (RESTORE WITH RECOVERY).

Click OK. Wait while executing and click OK when completed.

10. Repeat step 3-9 for the remaining SafeCom SQL databases.

5.2.12 On SU-SQL-2 edit and run remove_db_replication.cmd

1. On SU-SQL-2 login as a user with local admin rights.

2. Edit the remove_db_replication.cmd file so there is one osql line per SafeCom slave server and change the SQL instancenames to match the installation.

osql -S su-s-1\safecommsde -E -i remove_db_replication.sql osql -S su-s-2\safecommsde -E -i remove_db_replication.sql osql -S su-s1-vs2\safecommsde -E -i remove_db_replication.sql osql -S su-s2-vs2\safecommsde -E -i remove_db_replication.sql

In this example there are four SafeCom slave servers all running MSDE as indicated by text safecommsde. Save the file.

3. Double-click remove_db_replication.cmd file.

5.2.13 On SU-M-1 start SafeCom Service

1. On SU-M-1 start the SafeCom Service.

D60612-06 37

5 SQL master server

5.2.14 On SU-M-1 add server SU-S-2

1. On SU-M-1 open SafeCom Administrator.

2. Login to the server. On the Server menu, click Add server.

3. Enter IP address.

4. Click Test Server to verify that the SafeCom recovery slave server, SU-S-2, is running. Click Close.

5. Enter Computer name. The computer name should match the Group reported in the Test Server dialog. You can copy and paste the name (SU-S-2) from the Details tab in the Test Server dialog. Click Add.

6. The server is now being added which may take some minutes. Please be patient. When the Test Server on the added server in SafeCom

Administrator reports the Server is running properly the database replication from the SQL master server to the SafeCom recovery slave server have completed. Click Close.

5.2.15 On SU-M-1 delete server SU-S-2

1. On SU-M-1 open SafeCom Administrator.

2. Login to the server. Click the SU-S-2 server and on the Server menu, click Delete server. Click Yes. The SafeCom slave server, SU-S-2, must be running.

5.2.16 On SU-M-1 enter SafeCom original license key code

1. On SU-M-1 start SafeCom Administrator.

2. Login to the server. On the Group menu, click License.

Refer to the safecom_g2_disaster_recovery_form_60614.xls file mentioned in section 2.4.

3. Enter the SafeCom original license key code and click Apply. Click Close.

5 SQL master server

5.2.17 On SU-SQL-2 create new subscriptions

1. On SU-SQL-2 open the SQL Server Management Studio.

2. Login to the SQL server and browse to Replication, Local Publications and [sccore]:sccoreTrans.

3. Right-click [sccore]:sccoreTrans and click New Subscriptions…

4. The New Subscription Wizard appears. Click Next.

5. In the Publication dialog click Next.

6. In the Distribution Agent Location dialog click Next.

7. In the Subscribers dialog click Add Subscriber and select Add SQL Server Subscriber…

Note: Do not check the first Subscriber on the list (SU-SQL-2\SAFECOM) as this is the SQL recovery master server and it does not need to subscribe to itself.

D60612-06 39

5 SQL master server

8. In the Connect to Server dialog enter the Server name and change Authentication to SQL Server Authentication.

Enter safecom as Login and enter the Password for the SQL safecom user as supplied in the safecom_g2_disaster_recovery_form_60614.xls file mentioned in section 2.5.

9. Click Connect.

10. Repeat step 7-9 for each subscriber (SafeCom slave server).

11. In the Subscribers dialog click Next.

12. In the Distribution Agent Security dialog click […] to set security. This must be done for each subscriber (SafeCom slave server).

5 SQL master server

13. In the Distribution Agent Security dialog check Run under the SQL Server Agent service. Check By impersonating the process account.

Check Using the following SQL Server login. Enter safecom as Login and enter the Password for the SQL safecom user as supplied in the

safecom_g2_disaster_recovery_form_60614.xls file mentioned in section 2.5.

14. Click OK.

15. Repeat step 12-14 for each subscriber (SafeCom slave server).

16. Click Next.

17. In the Complete the Wizard dialog click Finish.

18. The Creating Subscription(s) dialog appears. Click Close when done.

D60612-06 41

5 SQL master server

5.2.18 On SU-SQL-2 stop the Log Reader Agent

1. On SU-SQL-2 open the Replication Monitor.

2. Click on [sccore]sccoreTrans.

3. Click on the Warnings and Agents tab.

4. Right-click Log Reader Agent and click Stop Agent.

5.2.19 On SU-SQL-2 execute sp_replrestart on sccore

1. On SU-SQL-2 open the SQL Server Management Studio.

2. Login to the SQL server.

3. Click New Query.

4. Change master to sccore in the drop down list of available databases.

5. In the query editor enter sp_replrestart.

6. Click Execute.

Note: If you do not execute the sp_replrestart the replication may not run because the highest log sequence number (LSN) value at the Distributor does match the highest LSN value at the Publisher.

5.2.20 On SU-SQL-2 start the Log Reader Agent

1. On SU-SQL-2 open the Replication Monitor.

2. Click on [sccore]sccoreTrans.

3. Click on the Warnings and Agents tab.

4. Right-click Log Reader Agent and click Start Agent.

5 SQL master server