SafeCom G2 Enterprise Disaster Recovery Manual

SafeCom G2 Enterprise Disaster Recovery Manual D60612-06 September 2009

Trademarks: SafeCom, SafeCom Go, SafeCom P:Go, SafeCom OnLDAP, SafeCom epay and the SafeCom logo are trademarks of SafeCom a/s. Company and product names mentioned in this manual are trademarks or registered trademarks of their respective owners. SafeCom a/s cannot be held responsible for any technical or typographical errors and reserves the right to make changes to products and documentation without prior notification. Patent: SafeCom has received the following British patent GB 2350 713 B, US patent US 6,952,780 B2 and Europe EUR EP1 120 701. Feedback: If you have any feedback or ideas concerning this manual or the SafeCom product, then please send an e-mail to feedback@safecom.eu Copyright 1999-2009 SafeCom a/s SafeCom a/s Energivej 15 DK-2750 Ballerup Denmark Phone: +45 4436 0240 E-mail: info@safecom.eu Web: safecom.eu D60612-06 2

Table of contents 1 Introduction... 6 1.1 Disaster recovery... 6 1.2 Audience... 6 1.3 Servers and naming conventions... 7 1.4 Available documentation... 8 1.5 About this manual... 8 1.6 Document history... 8 2 Prerequisites... 9 2.1 Introduction... 9 2.2 Store files in network folder... 9 2.3 Record SafeCom solution information... 9 2.4 SafeCom license key code... 10 2.5 SafeCom server SQL passwords... 11 2.6 Determine the Cluster Name... 11 2.7 Domain user... 12 2.8 SafeCom G2 Server software installation files... 12 2.9 SQL scripts and command files... 12 2.10 Backup of SafeCom database... 13 2.10.1 On SU-SQL-1 make a full database backup... 13 2.10.2 On SU-SQL-1 make a log backup... 13 2.11 SQL database mirroring... 14 2.11.1 On SU-SQL-1 make a full database backup... 14 2.11.2 On SU-SQL-1 make a log backup... 14 2.11.3 On SU-SQL-2 enable TCP/IP protocol... 15 2.11.4 On SU-SQL-2 start SQL Server Agent... 15 2.11.5 On SU-SQL-2 create the databases... 15 2.11.6 On SU-SQL-2 restore the databases... 16 2.11.7 On SU-SQL-2 restore the logs... 16 2.11.8 On SU-SQL-1 enable and start mirroring... 17 2.12 Backup of printer configurations... 17 3 SafeCom master server...18 3.1 Introduction... 18 3.2 Recovery overview... 19 3.2.1 On SU-M-1 stop SafeCom Service... 20 3.2.2 On SU-M-2 stop SafeCom Service... 20 3.2.3 On SU-SQL-1 make ODBC point to SU-SQL-1... 20 3.2.4 On SU-SQL-1 edit and run new_master_server.sql/cmd... 20 3.2.5 On SU-SQL-1 modify SQL user: safecom... 21 3.2.6 On SU-M-2 make ODBC point to SU-SQL-1... 21 3.2.7 On SU-M-2 start SafeCom Service... 21 3.2.8 On SU-M-2 enter SafeCom license key code... 21 3.2.9 On each SafeCom slave restart SafeCom Service... 21 3.2.10 Completion check... 22 4 SQL master server (mirroring)...23 4.1 Introduction... 23 4.2 Recovery overview... 24 4.2.1 On SU-SQL-2 break mirror... 25 4.2.2 On SU-SQL-2 create SQL user: safecominstall... 25 4.2.3 On SU-SQL-2 start SQL Server Agent... 25 4.2.4 On SU-SQL-1 stop SQL Server Agent to stop replication... 25 4.2.5 On SU-M-1 stop SafeCom Service... 25 4.2.6 On SU-M-1 change ODBC to SU-SQL-2... 26 4.2.7 On SU-M-1 start SafeCom Service... 26 D60612-06 3

4.2.8 On SU-M-1 open SafeCom Administrator... 26 4.2.9 On SU-M-1 enter SafeCom recovery license key code... 26 4.2.10 On SU-SQL-2 edit and run remove_db_replication.cmd... 27 4.2.11 On SU-M-1 add server SU-S-2... 27 4.2.12 On SU-M-1 delete server SU-S-2... 27 4.2.13 On SU-M-1 enter SafeCom original license key code... 27 4.2.14 On SU-SQL-2 create new subscriptions... 28 4.2.15 On SU-SQL-2 stop the Log Reader Agent... 31 4.2.16 On SU-SQL-2 execute sp_replrestart on sccore... 31 4.2.17 On SU-SQL-2 start the Log Reader Agent... 31 4.2.18 On SU-SQL-2 reinitialize the subscription... 32 4.2.19 On SU-SQL-2 prevent replication from expiring... 32 4.2.20 Completion check... 32 5 SQL master server...33 5.1 Introduction... 33 5.2 Recovery overview... 34 5.2.1 On SU-SQL-2 enable TCP/IP protocol... 35 5.2.2 On SU-SQL-2 start SQL Server Agent... 35 5.2.3 On SU-SQL-2 create SQL user: safecominstall... 35 5.2.4 On SU-SQL-1 stop SQL Server Agent to stop replication... 35 5.2.5 On SU-M-1 stop SafeCom Service... 35 5.2.6 On SU-M-1 change ODBC to SU-SQL-2... 36 5.2.7 On SU-M-1 start SafeCom Service... 36 5.2.8 On SU-M-1 open SafeCom Administrator... 36 5.2.9 On SU-M-1 enter SafeCom recovery license key code... 36 5.2.10 On SU-M-1 stop SafeCom Service... 36 5.2.11 On SU-SQL-2 restore the SafeCom databases... 37 5.2.12 On SU-SQL-2 edit and run remove_db_replication.cmd... 37 5.2.13 On SU-M-1 start SafeCom Service... 37 5.2.14 On SU-M-1 add server SU-S-2... 38 5.2.15 On SU-M-1 delete server SU-S-2... 38 5.2.16 On SU-M-1 enter SafeCom original license key code... 38 5.2.17 On SU-SQL-2 create new subscriptions... 39 5.2.18 On SU-SQL-2 stop the Log Reader Agent... 42 5.2.19 On SU-SQL-2 execute sp_replrestart on sccore... 42 5.2.20 On SU-SQL-2 start the Log Reader Agent... 42 5.2.21 On SU-SQL-2 reinitialize all subscriptions... 43 5.2.22 On SU-SQL-2 prevent replication from expiring... 43 5.2.23 Completion check... 43 6 SafeCom slave server...44 6.1 Introduction... 44 6.2 Recovery overview... 44 6.2.1 On SU-S-2 check Windows Firewall... 45 6.2.2 On SU-S-2 install the SafeCom G2 server software... 45 6.2.3 On SU-M-1 add the server... 45 6.2.4 Enable offline tracking... 45 6.2.5 On SU-M-1 run move_to_server.cmd... 46 6.2.6 On SU-S-2 restore print queues... 46 6.2.7 Update devices to reference SU-S-2... 47 6.2.8 Completion check... 48 7 Complete site DR...49 7.1 Introduction... 49 7.2 Recovery overview... 50 7.2.1 On SU-M-2 stop SafeCom Service... 51 7.2.2 On SU-SQL-2 restore the SafeCom databases... 51 7.2.3 On SU-SQL-2 edit scserverinfo... 51 7.2.4 On SU-M-2 start SafeCom Service... 51 D60612-06 4

7.2.5 On SU-M-2 add server SU-S-2... 52 7.2.6 On SU-M-2 delete server SU-S-2... 52 7.2.7 On SU-SQL-2 create new subscriptions... 52 7.2.8 On SU-SQL-2 reinitialize all subscriptions... 56 7.2.9 On SU-SQL-2 prevent replication from expiring... 56 7.2.10 Restart SafeCom Service on all slaves... 56 8 Roll back...57 8.1 Introduction... 57 8.2 SafeCom master server... 57 8.3 SafeCom slave server... 57 8.4 SQL master server (mirroring)... 57 8.5 SQL master server... 57 9 Administrator s installation notes...58 9.1 Introduction... 58 9.2 Servers... 58 9.2.1 SafeCom master server... 59 9.2.2 SQL master server... 60 9.2.3 SafeCom slave server... 61 D60612-06 5

1 Introduction 1 Introduction 1.1 Disaster recovery This manual covers the disaster recovery process for a SafeCom multi server solution covering the following situations: SafeCom master server is lost. SQL master server is lost and mirroring is used. SQL master server is lost. SafeCom slave server is lost. 1.2 Audience The audience for this manual is people familiar with the content of: SafeCom G2 Administrator s Manual D60600 SafeCom Installation Prerequisites Checklist D10910 SafeCom Installation Completion Checklist D10911 These people MUST also have hands-on experience with the following applications: SafeCom Administrator SafeCom Service Microsoft ODBC Data Source Administrator Microsoft SQL Server 2008 and 2005 Microsoft Cluster Service FTP D60612-06 6

1 Introduction 1.3 Servers and naming conventions SafeCom master server There is one SafeCom master server in the solution. It is responsible for scheduled user import and collecting tracking information from the SafeCom slave servers. SU-M-1 - SafeCom master server SU-M-2 - SafeCom recovery master server SafeCom slave servers The SafeCom slave servers are responsible for printing and hosts the SafeCom Pull Print queues. All the SafeCom enabled MFPs and printers are split across the slave servers. The slave server is using a local MSDE or SQL database. SU-S1-CL, SU-S2-CL, - SafeCom slave server clustered 1, 2, SU-S-1, SU-S-2, SU-S-3, - SafeCom recovery slave server SQL master server One clustered SQL server that holds the database used by the SafeCom master server. SU-SQL-1 - SQL master server SU-SQL-2 - SQL recovery master server Domain Controller SafeCom Solution SQL Master Recovery servers SQL Master SU-DOM 172.16.7.100 SU-SQL-1 172.16.7.98 SU-SQL-2 172.16.7.97 SQL SQL SafeCom Master SafeCom Master SU-M-1 172.16.7.101 SU-M-2 172.16.7.99 SafeCom Server SU-S-2 172.16.7.113 SafeCom Slave Clustered SafeCom Slave Clustered SafeCom Server MSDE MSDE SU-S1-N1 172.16.7.102 SU-S1-N2 172.16.7.103 SU-S1-CL 172.16.7.104 SU-S1-V1 172.16.7.105 SU-S1-V2 172.16.7.106 MSDE SU-S2-N1 172.16.7.107 SU-S2-N2 172.16.7.108 SU-S2-CL 172.16.7.109 SU-S2-V1 172.16.7.110 SU-S2-V2 172.16.7.111 MSDE SU-S-1 172.16.7.112 SafeCom Server SU-S-3 172.16.7.114 MSDE D60612-06 7

1 Introduction 1.4 Available documentation SafeCom G2 Administrator s Manual D60600 A comprehensive Manual that the administrator should consult to make a successful SafeCom solution. Includes information about SafeCom Tracking, SafeCom Rule Based Printing, SafeCom Client Billing and SafeCom Pay. 1.5 About this manual This manual applies to Microsoft SQL Server 2005 and SafeCom G2 Server version S82 070.370*05, S82 070.380*02 and S82 070.380*04. 1.6 Document history Revision D60612-06 SafeCom G2 Server version S82 070.380*07. Added details about how the SafeCom Controller can be changed to reference the recovery slave server by sending the current.cf2 file via FTP (6.2.7). Revision D60612-05 SafeCom G2 Server version S82 070.380*04. Correction to chapter 7 Complete site DR. Revision D60612-04 SafeCom G2 Server version S82 070.380*04. Added chapter 7 Complete site DR. Revision D60612-03 SafeCom G2 Server version S82 070.380*04. Updated to reflect that the Add server process may take some minutes to complete (4.2.11 and 5.2.14). Added chapter 8 Roll back. Revision D60612-02 SafeCom G2 Server version S82 070.380*04. Introduced the SafeCom Disaster Recovery Form D60614. This is an Excel Sheet designed to store SafeCom recovery licenses and safecom SQL user passwords (2.4 and 2.5). Added section: How to find the cluster name (2.6). Added section: Start the Log Reader Agent (4.2.17 and 5.2.20). Revision D60612-01 SafeCom G2 Server version S82 070.380*04. Initial version. D60612-06 8

2 Prerequisites 2 Prerequisites 2.1 Introduction The prerequisites are listed in detail in the following subsections. Please study this document carefully in order to be best prepared for a disaster recovery situation. Note: The recovery process for SafeCom master server and SQL master server is dependent on ready-available license key code (2.4) and password (2.5) and requires the following: Purchase of SafeCom DR License, Enterprise (p/n 276010) or SafeCom DR License (p/n 275010). Communicating with license@safecom.eu to get the Form worksheet in the safecom_g2_disaster_recovery_form_60614.xls file completed. 2.2 Store files in network folder Quite a few of the prerequisites involve access to certain files. It is recommended to decide on a network folder for these files so they are easy to access in the recovery situation. Folder: 2.3 Record SafeCom solution information Chapter 9 Administrator s installation notes contain forms that allow you to record relevant information about the SafeCom solution, such as version info, IP addresses, SQL instance names etc. Please make sure that these forms are completed and available. D60612-06 9

2 Prerequisites 2.4 SafeCom license key code Because the SafeCom license key is linked to the computer name of the SafeCom master server a new license key must be obtained from SafeCom and installed. Special agreement must be made with SafeCom in order to acquire an extra SafeCom license key for recovery purpose. On a cluster server it needs to be the Cluster Name (2.6) instead of the Computer Name. License key code for SafeCom recovery master server. Example: safecom_g2_disaster_recovery_form_60614.xls Used in section 3.2.8 License key code that allows an extra SafeCom Additional Server. Example: safecom_g2_disaster_recovery_form_60614.xls Used in section 4.2.9 and 5.2.9. Figure 1 The safecom_g2_disaster_recovery_form_60614.xls, page 1 D60612-06 10

2 Prerequisites 2.5 SafeCom server SQL passwords In the event that the SQL master is lost it is necessary to specify password for each SQL safecom user running on the SafeCom master and slave servers. Special agreement must be made with SafeCom in order to acquire these passwords. SQL safecom user passwords. On a cluster server it needs to be the Cluster Name (2.6) instead of the Computer Name. Example: safecom_g2_disaster_recovery_form_60614.xls Used in section 3.2.5, 4.2.14 and 5.2.17 Figure 2 The safecom_g2_disaster_recovery_form_60614.xls, page 2 2.6 Determine the Cluster Name The cluster name is only relevant for the servers where the SafeCom is running. It is not relevant for SQL servers without SafeCom. It is typically only SafeCom slave servers that are clustered. 1. Open Cluster Administrator. 2. Browse to Groups, Cluster Group. 3. Right-click Cluster Name and select Properties. 4. Click on the Parameters tab. 5. Name contains the cluster name. D60612-06 11

2 Prerequisites 2.7 Domain user There is a domain user that is a member of the local administrator group on each server that is part of the SafeCom solution. The user account is used to execute SQL scripts on the SafeCom servers. 2.8 SafeCom G2 Server software installation files The SafeCom G2 server software MUST be the same version on all the SafeCom servers in the solution. Example: S82 070.370*05. Make sure to have a copy of the software around in case it needs to be installed in preparation for the recovery (recommended) or during the recovery process. Ensure that any patches are available as well. SafeCom G2 Server software installation files. Example: 07037005.exe or safecom_g2_380_04.exe 2.9 SQL scripts and command files The below SQL scripts and command files are required in the recovery process: new_master_server.sql and new_master_server.cmd This SQL script updates the SafeCom databases to reference the SafeCom recovery master server. The script can be executed by running the SafeCom supplied command file new_master_server.cmd on the SafeCom recovery master server. Used in section 3.2.4. break_mirror.sql and break_mirror.cmd This SQL script breaks the mirror. Used in section 4.2.1. remove_db_replication.sql and remove_db_replication.cmd This SQL script removes the replication on the SafeCom slave servers so they are ready to become part of the replication from the SQL recovery master server. Used in section 4.2.10 and 5.2.12. move_to_server.sql and move_to_server.cmd This SQL script moves users and devices from one server to another. Used in section 6.2.5. D60612-06 12

2 Prerequisites 2.10 Backup of SafeCom database A backup exists of the SafeCom databases so this can be restored on the SQL recovery master server. The databases should be backed up regularly. Refer to the SQL 2005 Server documentation. 2.10.1 On SU-SQL-1 make a full database backup 1. On SU-SQL-1 open SQL Server Management Studio. 2. Login to the SQL server and browse to Databases. 3. For each of SafeCom SQL databases create the corresponding backup file: sccore.bak scevent.bak scpurse.bak sctracking.bak 4. Right-click sccore, select Tasks and click Back Up 5. In the Backup type list box, select Full. 6. Repeat step 3-5 for the remaining SafeCom SQL databases. 2.10.2 On SU-SQL-1 make a log backup 1. On SU-SQL-1 open SQL Server Management Studio. 2. Login to the SQL server and browse to Databases. 3. For each of SafeCom SQL databases create the corresponding log file: sccore.trn scevent.trn scpurse.trn sctracking.trn 4. Right-click sccore, select Tasks and click Back Up 5. In the Backup type list box, select Transaction Log. 6. Repeat step 3-5 for the remaining SafeCom SQL databases. D60612-06 13

2 Prerequisites 2.11 SQL database mirroring The disaster recovery process of the SQL master server can be simplified if database mirroring is used for increased database availability. Throughout this document think of SU-SQL-1 as the principal server and SU-SQL-2 as the mirror server (4.2). SQL database mirroring involves the four SafeCom databases (sccore, scevent, scpurse and sctracking). It does not include replication and subscription; hence these must be created and reinitialized as part of the SQL master server recovery process. For SQL database mirroring to work the following is required: The SQL servers must run SQL Server 2005 SP2 or later. The SQL servers must be running the same edition of SQL Server 2005. They should run on comparable systems (can handle identical workloads). Overview of the SQL database mirroring setup process: Backup databases on SU-SQL-1: 1. On SU-SQL-1 make a full database backup (2.11.1) 2. On SU-SQL-1 make a log backup (2.11.2) Create and restore databases on SU-SQL-2: 3. On SU-SQL-2 enable TCP/IP protocol (2.11.3) 4. On SU-SQL-2 start SQL Server Agent (2.11.4) 5. On SU-SQL-2 create the databases (2.11.5) 6. On SU-SQL-2 restore the databases (2.11.6) 7. On SU-SQL-2 restore the logs (2.11.7) Enable mirroring: 8. On SU-SQL-1 enable and start mirroring (2.11.8) 2.11.1 On SU-SQL-1 make a full database backup 1. On SU-SQL-1 make a full database backup (2.10.1) of the four SafeCom databases. Example: sccore.bak, scevent.bak, scpurse.bak and sctracking.bak. The files must be stored on a local folder on the server. Example: C:\sc-bak. 2. Copy the files to the same location on SU-SQL-2, C:\sc-bak. 2.11.2 On SU-SQL-1 make a log backup 1. On SU-SQL-1 make a log backup (2.10.2) of the four SafeCom databases. Example: sccore.trn, scevent.trn, scpurse.trn and sctracking.trn. The files must be stored on a local folder on the server. Example: C:\sc-trn. 2. Copy the files to the same location on SU-SQL-2, C:\sc-trn. D60612-06 14

2 Prerequisites 2.11.3 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. On SU-SQL-2 in Services restart SQL Server (instancename). 2.11.4 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). 2.11.5 On SU-SQL-2 create the databases 1. On SU-SQL-2 open SQL Server Management Studio. 2. Login to the SQL server and browse to Databases. 3. Create each of SafeCom SQL databases: sccore scevent scpurse sctracking 4. Right-click Databases and click New Database 5. Enter sccore as Database name. Click OK. 6. Repeat step 3-5 for the remaining SafeCom databases. D60612-06 15

2 Prerequisites 2.11.6 On SU-SQL-2 restore the 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. In the Restore Database dialog 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. Change the Recovery state to the second option (RESTORE WITH NORECOVERY). This creates the database with tables and prepares it to receive content once mirroring is started. Click OK. Wait while executing and click OK when completed. 10. Repeat step 3-9 for the remaining SafeCom SQL databases. 2.11.7 On SU-SQL-2 restore the logs 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, Transaction Log 5. Click From device. Click [ ]. 6. In the Restore Transaction Log dialog check From file or tape. Click [ ]. 7. In the Specify Backup dialog click Add and browse to the Backup File sccore.trn. Click OK. 8. Click OK. 9. In Select a page click Options. Check Overwrite the existing database. Change the Recovery state to the second option (RESTORE WITH NORECOVERY). Click OK. Wait while executing and click OK when completed. 10. Repeat step 3-9 for the remaining logs. D60612-06 16

2 Prerequisites 2.11.8 On SU-SQL-1 enable and start mirroring 1. On SU-SQL-1 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 Properties. 5. In Select a page click Mirroring. 6. Click Configure Security The Configure Database Mirroring Security Wizard appears. 7. Select No to include witness server instance. Click Next. 8. Click Next. 9. In Mirror Server Instance specify SU-SQL-2\SAFECOM. Click Connect. Click Next. 10. In Service Accounts click Next. 11. In Complete the Wizard click Finish. 12. Wait for the configuring of endpoints to complete. Click Close. 13. Click Start Mirroring. 14. Click OK. 15. Repeat step 3-14 for the remaining SafeCom SQL databases. 2.12 Backup of printer configurations The Microsoft Print Migrator 3.1 available at microsoft.com/printserver can be used to back up and restore all print shares and user permissions. Print Migrator does not back up the actual SafeCom Pull Port and SafeCom Push Port monitors, only the port attributes. Prior to the restore operation, you must reinstall the original set of SafeCom port monitors to ensure complete functionality. D60612-06 17

3 SafeCom master server 3 SafeCom master server 3.1 Introduction This chapter describes the steps necessary to switch to a SafeCom recovery master server, SU-M-2. It is assumed that the SafeCom database used by the SafeCom master server resides on a separate SQL master server, SU-SQL-1. Servers involved: SafeCom master server, SU-M-1. SafeCom recovery master server, SU-M-2. SQL master server, SU-SQL-1. Each SafeCom slave server (restart of SafeCom Service is required). Interruption: Interruption to administration will occur during most of the recovery process. Interruption to printing will occur in step 9 when the SafeCom Service is restarted on each SafeCom slave (3.2.9). D60612-06 18

3 SafeCom master server 3.2 Recovery overview You are STRONGLY ADVISED to print a separate copy of this page 19 so you can check mark the steps as you work through the process. Overview of the recovery process: Stop SafeCom Service on SafeCom master servers: 1. On SU-M-1 stop SafeCom Service (3.2.1) 2. On SU-M-2 stop SafeCom Service (3.2.2) Prepare SQL master server to use new SafeCom master: 3. On SU-SQL-1 make ODBC point to SU-SQL-1 (3.2.3) 4. On SU-SQL-1 edit and run new_master_server.sql/cmd (3.2.4) 5. On SU-SQL-1 modify SQL user: safecom (3.2.5) Make the SafeCom recovery master use the SQL master: 6. On SU-M-2 make ODBC point to SU-SQL-1 (3.2.6) 7. On SU-M-2 start SafeCom Service (3.2.7) 8. On SU-M-2 enter SafeCom license key code (3.2.8) Restart SafeCom Service on each SafeCom slave: 9. On each SafeCom slave restart SafeCom Service (3.2.9) Completion check: 10. Completion check (3.2.10) D60612-06 19

3 SafeCom master server 3.2.1 On SU-M-1 stop SafeCom Service Note: This step may prove unnecessary if the computer has crashed. 1. On SU-M-1 stop the SafeCom Service and change it to Manual startup. 3.2.2 On SU-M-2 stop SafeCom Service 1. Power on SU-M-2. 2. On SU-M-2 stop the SafeCom Service. 3.2.3 On SU-SQL-1 make ODBC point to SU-SQL-1 Note: This is required to run the sql/cmd file as described in section 3.2.4. 1. On SU-SQL-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 Add. Select SQL Server as driver. Click Finish. 6. Enter sccoremssql in Name and the SQL instance name on SU-SQL-1 (SU-SQL-1/safecom) in Server. 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. 3.2.4 On SU-SQL-1 edit and run new_master_server.sql/cmd 1. On SU-SQL-1 login as a user with local admin rights. 2. Edit the new_master_server.sql script and changed the variables @MasterServerName and @MasterServerIp. SELECT @MasterServerName SELECT @MasterServerIp = 'SU-M-2'; = '172.16.7.99'; In this example the server name is SU-M-2 and the IP address is 172.16.7.99. Save the file. 3. Double-click new_master_server.cmd. 4. Open the log file new_master_server.log and verify that the script did execute and changed a row for each SafeCom slave server. D60612-06 20

3 SafeCom master server 3.2.5 On SU-SQL-1 modify SQL user: safecom 1. On SU-SQL-1 open SQL Server Management Studio. 2. Login to the SQL server and browse to Security and Logins. Double-click safecom. 3. On the General page change Password to that of SU-M-2. Refer to the safecom_g2_disaster_recovery_form_60614.xls file mentioned in section 2.5. Clear Enforce password policy. Click OK. 3.2.6 On SU-M-2 make ODBC point to SU-SQL-1 1. On SU-M-2 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-1 (SU-SQL-1/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. 3.2.7 On SU-M-2 start SafeCom Service 1. On SU-M-2 set the SafeCom Service to Automatic startup. 2. On SU-M-2 start the SafeCom Service. 3.2.8 On SU-M-2 enter SafeCom license key code 1. On SU-M-2 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 license key code and click Apply. Click Close. 3.2.9 On each SafeCom slave restart SafeCom Service 1. On each SafeCom slave server restart SafeCom Service. If the SafeCom slave is clustered use the Cluster Administrator to move the virtual server to the second node. D60612-06 21

3 SafeCom master server 3.2.10 Completion check 1. Please refer to SafeCom Installation Completion Checklist D10911 to test that the disaster recovery process has been completed successfully. D60612-06 22

4 SQL master server (mirroring) 4 SQL master server (mirroring) 4.1 Introduction This chapter describes the steps necessary to switch to an SQL recovery master server, SU-SQL-2, when SQL database mirroring (2.11) is in use. Servers involved: SafeCom master server, SU-M-1. SQL master server, SU-SQL-1, is the principal server and the SQL recovery master server, SU-SQL-2, is the mirror server. 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: SQL database mirroring has been configured as described in 2.11. 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 23

4 SQL master server (mirroring) 4.2 Recovery overview You are STRONGLY ADVISED to print a separate copy of this page 24 so you can check mark the steps as you work through the process. Overview of the recovery process: Break mirroring: 1. On SU-SQL-2 break mirror (4.2.1) 2. On SU-SQL-2 create SQL user: safecominstall (4.2.2) 3. On SU-SQL-2 start SQL Server Agent (4.2.3) 4. On SU-SQL-1 stop SQL Server Agent to stop replication (4.2.4) Setup SafeCom master server to work with SU-SQL-2: 5. On SU-M-1 stop SafeCom Service (4.2.5) 6. On SU-M-1 change ODBC to SU-SQL-2 (4.2.6) 7. On SU-M-1 start SafeCom Service (4.2.7) 8. On SU-M-1 open SafeCom Administrator (4.2.8) 9. On SU-M-1 enter SafeCom recovery license key code (4.2.9) Remove the replication: 10. On SU-SQL-2 edit and run remove_db_replication.cmd (4.2.10) Add and delete swing server on SU-M-1: 11. On SU-M-1 add server SU-S-2 (4.2.11) 12. On SU-M-1 delete server SU-S-2 (4.2.12) 13. On SU-M-1 enter SafeCom original license key code (4.2.13) Setup replication on SU-SQL-2: 14. On SU-SQL-2 create new subscriptions (4.2.14) 15. On SU-SQL-2 stop the Log Reader Agent (4.2.15) 16. On SU-SQL-2 execute sp_replrestart on sccore (4.2.16) 17. On SU-SQL-2 start the Log Reader Agent (4.2.17) 18. On SU-SQL-2 reinitialize the subscription (4.2.18) 19. On SU-SQL-2 prevent replication from expiring (4.2.19) Completion check: 20. Completion check (4.2.20) D60612-06 24

4 SQL master server (mirroring) 4.2.1 On SU-SQL-2 break mirror 1. On SU-SQL-2 login as a user with local admin rights. 2. Double-click break_mirror.cmd file. 4.2.2 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. 4.2.3 On SU-SQL-2 start SQL Server Agent Note: This step may prove unnecessary if SQL Server Agent is running already. 1. On SU-SQL-2 in Services change SQL Server Agent (instancename) to Automatic startup. 2. In Services start SQL Server Agent (instancename). 4.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. 1. Right-click the SQL Server Agent (instancename) and click Stop. Note: If SQL database mirroring is used proceed to section 5.2.6. 4.2.5 On SU-M-1 stop SafeCom Service 1. On SU-M-1 stop the SafeCom Service. D60612-06 25

4 SQL master server (mirroring) 4.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. 4.2.7 On SU-M-1 start SafeCom Service 1. On SU-M-1 start SafeCom Service. 4.2.8 On SU-M-1 open SafeCom Administrator 1. On SU-M-1 open SafeCom Administrator and login to verify that all the users and devices are present. 4.2.9 On SU-M-1 enter SafeCom recovery license key code 1. In SafeCom Administrator click 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. D60612-06 26

4 SQL master server (mirroring) 4.2.10 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. Note: The replication on the SQL mirror server, SU-SQL-2, MUST also be removed. osql -S su-sql-2\safecom -E -i remove_db_replication.sql 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. 4.2.11 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 dialog 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. 4.2.12 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. 4.2.13 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. D60612-06 27

4 SQL master server (mirroring) 4.2.14 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 28

4 SQL master server (mirroring) 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). D60612-06 29

4 SQL master server (mirroring) 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 71-73 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 30

4 SQL master server (mirroring) 4.2.15 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. 4.2.16 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. 4.2.17 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. D60612-06 31

4 SQL master server (mirroring) 4.2.18 On SU-SQL-2 reinitialize the subscription 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 the subscription of the SafeCom slave server and select Reinitialize All Subscriptions. 4. Check Generate the new snapshot now. Click Mark For Reinitialization. 4.2.19 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. D60612-06 32

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) D60612-06 34

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. D60612-06 36

5 SQL master server 5.2.11 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. D60612-06 38

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). D60612-06 40

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. D60612-06 42

5 SQL master server 5.2.21 On SU-SQL-2 reinitialize all 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 the subscription of the SafeCom slave server and select Reinitialize All Subscriptions. 4. Check Generate the new snapshot now. Click Mark For Reinitialization. 5. Repeat step 3-4 for each SafeCom slave server. 5.2.22 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. 5.2.23 Completion check 1. Please refer to SafeCom Installation Completion Checklist D10911 to test that the disaster recovery process has been completed successfully. D60612-06 43

6 SafeCom slave server 6 SafeCom slave server 6.1 Introduction This chapter describes the steps necessary to install a SafeCom recovery slave server, SU-S-2. This recovery process assumes that the SafeCom recovery slave server is not clustered and the database is MSDE and resides locally. 6.2 Recovery overview You are STRONGLY ADVISED to print a separate copy of this page 44 so you can check mark the steps as you work through the process. Overview of the recovery process: Prepare the SafeCom recovery slave server: 1. On SU-S-2 check Windows Firewall (6.2.1) 2. On SU-S-2 install the SafeCom G2 server software (6.2.2) Add the SafeCom recovery slave server: 3. On SU-M-1 add the server (6.2.3) 4. Enable offline tracking (6.2.4) 5. On SU-M-1 run move_to_server.cmd (6.2.5) Restore print queues: 6. On SU-S-2 restore print queues (6.2.6) 7. Update devices to reference SU-S-2 (6.2.7) Completion check: 8. Completion check (6.2.8) D60612-06 44

6 SafeCom slave server 6.2.1 On SU-S-2 check Windows Firewall 1. On SU-S-2 if Windows Firewall is enabled on SU-S-2 it may prevent SafeCom from working. Add the ports as exceptions or disable the firewall. 6.2.2 On SU-S-2 install the SafeCom G2 server software If the SafeCom recovery slave server is clustered and/or is using an SQL server you should refer to the appropriate section in SafeCom G2 Administrator s Manual D60600. 1. On SU-S-2 launch the SafeCom G2 installation. 2. Click Next. Click Server. 3. Check Basic installation. Click Next. 4. Read the end-user license agreement and click Yes to accept it. 5. Choose the destination folder for the SafeCom program files. Click Next. 6. Current settings are displayed. Click Back to change settings or Next to accept and start the installation. The Microsoft SQL Server Desktop Engine (MSDE) is also installed. 7. Check Yes, I want to restart my computer now. Click Finish. Note: The computer must be restarted otherwise the SafeCom Port Monitors may not be available and MSDE may not run properly. 6.2.3 On SU-M-1 add the server 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. 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. 6.2.4 Enable offline tracking 1. In SafeCom Administrator open the Server properties dialog of the SafeCom recovery slave server, SU-S-2. 2. Click on the Tracking tab. 3. Check Offline. Click OK. D60612-06 45

6 SafeCom slave server 6.2.5 On SU-M-1 run move_to_server.cmd 1. On SU-M-1 login as a user with local admin rights. 2. Edit the move_to_server.sql script and change the variables. SELECT @FromServer SELECT @ToServer = 'SU-S-1'; = 'SU-S-2'; In this example users and devices are moved from the server names SU-S-1 to SU-S-2. Note: The devices reference to the server needs to be changed in the device as described in section 6.2.7. 3. Double-click move-to-server.cmd. 4. Open the log file move_to_server.log and verify that the script did execute and changed a row for each SafeCom slave server. 6.2.6 On SU-S-2 restore print queues 1. Use the restore option in Microsoft Print Migrator to restore the print queues (assuming you have used it for backup). 2. Check that the SafeCom Pull Ports are indeed referencing the new SafeCom recovery slave server and not the old lost one. D60612-06 46

6 SafeCom slave server 6.2.7 Update devices to reference SU-S-2 1. The SafeCom-enabled devices must be configured to reference the SU-S-2 when the original SafeCom slave server is lost. This change can be accomplished with these methods: On the SafeCom Controller by opening the Advanced Configuration web page. Click SafeCom and enter the SafeCom Server IP address. Click Save and Continue. Click Restart. By producing a SafeCom Controller configuration, current.cf2, and FTP it to the SafeCom Controller (See step 1a, 1b and 1c below). Put the FTP commands into a prepared BAT file that has been configured in advance with the IP addresses of the SafeCom Controllers. The content of the current.cf2 file: BEGIN_CONFIGURATION SAFECOMMON IP_ADDRESS "172.16.6.164" IP_ADDRESS_IP 172.16.6.164 PORT_NO 7500 END BEGIN_CONFIGURATION IDAPS BOOT YES END Both IP_ADDRESS and IP_ADDRESS_IP must be changed to reference the SafeCom server (SU-S-2). 1a. From the command prompt window, issue the ftp command. Enter: ftp <IP address> The SafeCom Controller prompts you for a username and a password. Both are adm by default. 1b. Put the SafeCom Controller into software update mode by downloading the software file into the codes folder. Enter: cd config put current.cf2 The command prompt window displays the text "Restarting... Login again to update the software". 1c. Logout of the ftp session. Enter: quit D60612-06 47

6 SafeCom slave server 6.2.8 Completion check 1. Please refer to SafeCom Installation Completion Checklist D10911 to test that the disaster recovery process has been completed successfully. D60612-06 48

7 Complete site DR 7 Complete site DR 7.1 Introduction This chapter describes the steps required to swap from an entire production site to a DR site, that is, all server components are lost. DR site preparation: 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). 4. On SU-M-2 do a SafeCom Advanced installation that uses the SU-SQL-2 as the master SQL server. 5. On SU-M-2 enter SafeCom recovery license key code. 6. On each server that will act as slave in the DR site do a SafeCom basic installation. Do NOT add them as slave, but let them run as master server. The linking together happens as part of the actual recovery process. 7. Make a list with server IP addresses and server names. The list is needed in section 7.2.3. D60612-06 49

7 Complete site DR 7.2 Recovery overview You are STRONGLY ADVISED to print a separate copy of this page 49 so you can check mark the steps as you work through the process. Overview of the recovery process: Stop SafeCom Service on SU-M-2: 1. On SU-M-2 stop SafeCom Service (7.2.1) Restore the databases on SU-SQL-2: 2. On SU-SQL-2 restore the SafeCom databases (7.2.2) 3. On SU-SQL-2 edit scserverinfo (7.2.3). Add and delete swing server on SU-M-2: 4. On SU-M-2 start SafeCom Service (7.2.4). 5. On SU-M-2 add server SU-S-2 (7.2.5). 6. On SU-M-2 delete server SU-S-2 (7.2.6). Setup replication on SU-SQL-2: 7. On SU-SQL-2 create new subscriptions (7.2.7). 8. On SU-SQL-2 reinitialize all subscriptions (7.2.8). 9. On SU-SQL-2 prevent replication from expiring (7.2.9). Restart all slaves: 10. Restart SafeCom Service on all slaves (7.2.10). D60612-06 50

7 Complete site DR 7.2.1 On SU-M-2 stop SafeCom Service 1. On SU-M-2 stop the SafeCom Service. 7.2.2 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. 7.2.3 On SU-SQL-2 edit scserverinfo 1. Edit the scserverinfo table to reflect the server IP addresses and names that applies to the DR site. Note: If you solution is a Pay solution you need to open the scserversettings table and change MnyIp field for the master server (ServerId 1) to reflect the IP address of the DR master SU-M-2. Note: If your solution (not likely) is using online tracking you need to open the scserversettings table and change the TsIp field for the master server (ServerId 1) to reflect the IP address of the DR master SU-M-2. 7.2.4 On SU-M-2 start SafeCom Service 1. On SU-M-2 start the SafeCom Service. D60612-06 51

7 Complete site DR 7.2.5 On SU-M-2 add server SU-S-2 1. On SU-M-2 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. 7.2.6 On SU-M-2 delete server SU-S-2 1. On SU-M-2 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. 7.2.7 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. D60612-06 52

7 Complete site DR 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. 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). D60612-06 53

7 Complete site DR 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). D60612-06 54

7 Complete site DR 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 55

7 Complete site DR 7.2.8 On SU-SQL-2 reinitialize all 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 the subscription of the SafeCom slave server and select Reinitialize All Subscriptions. 4. Check Generate the new snapshot now. Click Mark For Reinitialization. 5. Repeat step 3-4 for each SafeCom slave server. 7.2.9 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. 7.2.10 Restart SafeCom Service on all slaves 1. Restart SafeCom Service on all slaves. D60612-06 56

8 Roll back 8 Roll back 8.1 Introduction This chapter contains hints as to how you can roll back after a Disaster Recovery. It may be that you have been rehearsing the DR process and want to revert back to the original setup. 8.2 SafeCom master server The roll back process involves going through the steps in chapter 3, but this time think of SU-M-1 as the SafeCom recovery master server and SU-M-2 as the SafeCom master server. 8.3 SafeCom slave server The roll back process involves going through the steps in chapter 6. Please ensure the SafeCom and MSDE has been completely deleted from the SafeCom slave server that you wish to make part of the solutions again. 8.4 SQL master server (mirroring) The roll back process assumes the original principal SQL server is unavailable, and therefore the first step is to setup the SQL mirroring again (2.11), but this time the original mirror server will become the principal server and the original principal server (or a replacement) will become the mirror server. Once the mirroring is in place it is a matter of going through the steps in chapter 4. 8.5 SQL master server The roll back process involves going through the steps in chapter 5, but this time think of SU-SQL-1 as SU-SQL-2 and vice versa. D60612-06 57

9 Administrator s installation notes 9 Administrator s installation notes 9.1 Introduction This chapter contains forms that allow you to record relevant information about the SafeCom solution. The information is relevant when multiple people are involved in the solution over time in connection with for example maintenance and support. 9.2 Servers If the solution is a multi server solution it is recommended to produce a diagram (using Microsoft Visio or a similar tool). The diagram should include the different servers and ports used. This section contains three types of tables: SafeCom master Server SQL master Server SafeCom slave Server The right-most column in the tables contains one or more letters. Use the letters with the legend below: Legend: A If the SafeCom server is clustered all other SafeCom components (devices, port monitors, etc.) must reference Virtual Server and not the nodes. Otherwise failover will not function properly. B The SafeCom license key code is based on the Computer Name, unless the master server is clustered in which case it is based on the Cluster Name. C A SafeCom multi server solution requires the SafeCom master server to use Microsoft SQL Server. Enter MSDE or SQL. If the SQL server resides on another server then added the word Remote and fill-in the SQL master server table. D Enter the SafeCom G2 version. Example: S82 070.370*05. A SafeCom multi server solution requires all SafeCom servers to be on the same version. E Enter the Windows OS information. Example: Windows 2003 SP2 64-bit. F Normally a cluster has two nodes. Add more rows if required. G If the SQL server is clustered the ODBC reference to the SQL server should be NetworkName\instancename. Otherwise it should be computername\instancename. H Normal practice is to install and use MSDE on SafeCom slave servers. D60612-06 58

9 Administrator s installation notes 9.2.1 SafeCom master server Cluster Group Virtual Server 1 Virtual Server 2 Node 1 Node 2 SafeCom master server IP Address Computer Name MSDE / SQL SafeCom G2 version S82 070. Windows OS IP Address Cluster Name Disk Resource (Q) IP Address Network Name Disk Resource Spool folder SC print job folder MSDE/SQL folder IP Address Network Name Disk Resource Spool folder IP Address Heartbeat IP Network Name IP Address Heartbeat IP Network Name Cluster information A B C D E B A A A A F F F F F F D60612-06 59

9 Administrator s installation notes 9.2.2 SQL master server Cluster Group Virtual Server Node 1 Node 2 Folder IP Address Computer Name SQL SQL instancename Windows OS IP Address Cluster Name Disk Resource (Q) IP Address Network Name Disk Resource IP Address Heartbeat IP Network Name IP Address Heartbeat IP Network Name MSDE/SQL SQL master server Cluster information G G F F F F F F D60612-06 60

9 Administrator s installation notes 9.2.3 SafeCom slave server Cluster Group Virtual Server 1 Virtual Server 2 Node 1 Node 2 SafeCom slave server IP Address Computer Name MSDE / SQL SafeCom G2 version S82 070. Windows OS IP Address Cluster Name Disk Resource (Q) IP Address Network Name Disk Resource Spool folder SC print job folder MSDE/SQL folder IP Address Network Name Disk Resource Spool folder IP Address Heartbeat IP Network Name IP Address Heartbeat IP Network Name Cluster information A B C D E A A A A F F F F F F D60612-06 61