On SU-SQL-2 prevent replication from expiring

The replication from the SQL master server to the slave(s) may get dropped if the subscription is not synchronized within 72 hours.

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

2. Login to the SQL server and browse to Replication, Local Publication.

3. Right-click [sccore]:sccoreTrans and select Properties.

4. On the General page check Subscription never expire, but they can be deactivated until they are reinitialized. Click OK.

5. You may wish to Lauch Replication Monitor to monitor that the replication is running.

4.2.20 Completion check

1. Please refer to SafeCom Installation Completion Checklist D10911 to test that the disaster recovery process has been completed successfully.

5 SQL master server

5 SQL master server

5.1 Introduction

This chapter describes the steps necessary to switch to an SQL recovery master server, SU-SQL-2.

Servers involved:

• SafeCom master server, SU-M-1.

• SQL master server, SU-SQL-1, and SQL recovery master server, SU-SQL-2.

• In order to create the replication in an as simple as possible manner the recovery process involves adding (and removing) an additional SafeCom recovery slave server, SU-S-2.

Preparation:

• Prepare the additional SafeCom recovery slave server, SU-S-2, in advance with correct firewall configuration (6.2.1) and SafeCom G2 server

software (6.2.2). This will save time in the recovery process.

Interruption:

• Interruption to administration will occur during most of the recovery process.

• There is no interruption to printing during this process (assuming all printing is handled by the SafeCom slaves and not by the SafeCom master server).

D60612-06 33

5 SQL master server

5.2 Recovery overview

You are STRONGLY ADVISED to print a separate copy of this page 34 so you can check mark the steps as you work through the process.

Overview of the recovery process:

Prepare SU-SQL-2:

1. On SU-SQL-2 enable TCP/IP protocol (5.2.1) 2. On SU-SQL-2 start SQL Server Agent (5.2.2)

3. On SU-SQL-2 create SQL user: safecominstall (5.2.3) Stop replication:

4. On SU-SQL-1 stop SQL Server Agent to stop replication (5.2.4) Create the databases on SU-SQL-2:

5. On SU-M-1 stop SafeCom Service (5.2.5) 6. On SU-M-1 change ODBC to SU-SQL-2 (5.2.6) 7. On SU-M-1 start SafeCom Service (5.2.7) 8. On SU-M-1 open SafeCom Administrator (5.2.8)

9. On SU-M-1 enter SafeCom recovery license key code (5.2.9) 10. On SU-M-1 stop SafeCom Service (5.2.10)

Restore the databases on SU-SQL-2:

11. On SU-SQL-2 restore the SafeCom databases (5.2.11)

12. On SU-SQL-2 edit and run remove_db_replication.cmd (5.2.12) Add and delete swing server on SU-M-1:

13. On SU-M-1 start SafeCom Service (5.2.13) 14. On SU-M-1 add server SU-S-2 (5.2.14) 15. On SU-M-1 delete server SU-S-2 (5.2.15)

16. On SU-M-1 enter SafeCom original license key code (5.2.16) Setup replication on SU-SQL-2:

17. On SU-SQL-2 create new subscriptions (5.2.17) 18. On SU-SQL-2 stop the Log Reader Agent (5.2.18) 19. On SU-SQL-2 execute sp_replrestart on sccore (5.2.19) 20. On SU-SQL-2 start the Log Reader Agent (5.2.20) 21. On SU-SQL-2 reinitialize all subscription (5.2.21) 22. On SU-SQL-2 prevent replication from expiring (5.2.22) Completion check:

23. Completion check (5.2.23)

5 SQL master server

5.2.1 On SU-SQL-2 enable TCP/IP protocol

1. On SU-SQL-2 click Start, point to All Programs, Microsoft SQL Server 2005, Configuration Tools and SQL Server Configuration Manager.

2. Browse to SQL Server 2005 Network Configuration and Protocols for MSSQLSERVER.

3. Right-click TCP/IP and select Enable.

4. In Services restart SQL Server (instancename).

5.2.2 On SU-SQL-2 start SQL Server Agent

1. On SU-SQL-2 in Services change SQL Server Agent (instancename) to Automatic startup.

2. In Services start SQL Server Agent (instancename).

5.2.3 On SU-SQL-2 create SQL user: safecominstall

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

2. Login to the SQL server and browse to Security and Logins. Right-click Logins and click New Login…

3. On the General page set Login name to safecominstall. Check SQL

Server authentication and set Password to safecom_2_DB. Clear Enforce password policy.

4. Click on the Server Roles page. Check sysadmin. Click OK.

5.2.4 On SU-SQL-1 stop SQL Server Agent to stop replication

Note: This step may prove unnecessary if the computer has crashed.

1. On SU-SQL-1 open the Control Panel.

2. Click Administrative Tools. Click Services.

2. Right-click the SQL Server Agent (instancename) and click Stop.

Note: If SQL database mirroring is used proceed to section 5.2.6.

5.2.5 On SU-M-1 stop SafeCom Service

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

D60612-06 35

5 SQL master server

5.2.6 On SU-M-1 change ODBC to SU-SQL-2

1. On SU-M-1 open the Control Panel.

2. Click Administrative Tools. Click Data Sources (ODBC).

3. The ODBC Data Source Administrator dialog appears.

Click on the System DSN tab.

4. For each of SafeCom SQL data source names:

• sccoremssql

• sceventmssql

• scpursemssql

• sctrackingmssql 5. Click Configure.

6. In Microsoft SQL Server DSN Configuration dialog change Server to the SQL instance name on SU-SQL-2 (SU-SQL-2/safecom).

7. Click Finish (Do not click Next).

8. The ODBC Microsoft SQL Server Setup dialog appears. Click OK.

Do not click Test Data Source… since this will fail at this stage.

9. Repeat step 4-8 for the remaining SafeCom SQL data source names.

5.2.7 On SU-M-1 start SafeCom Service

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

5.2.8 On SU-M-1 open SafeCom Administrator

1. On SU-M-1 open SafeCom Administrator and login to verify that there are only the two built-in users: ADMIN (Administrator) and TECH (Technician).

When done close SafeCom Administrator.

5.2.9 On SU-M-1 enter SafeCom recovery 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 recovery license key code and click Apply. Click Close.

5.2.10 On SU-M-1 stop SafeCom Service

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

5 SQL master server