Install one of the supported operating systems for YSoft SafeQ server

Make sure that server has the same IP address and hostname settings as before the failure.

Install one of the supported databases (or select the embedded database during installation of YSoft SafeQ in the next step)

• Database type MUST be the same as before the failure.

• YSoft SafeQ database backup from master node is a MUST for the restoration of the master node.

Perform this step on all running CML servers

 Skip this step in case there exists just one CML node in the environment (non-clustered installation)

Verify synchronization

Check that all data are synchronized between all running YSoft SafeQ nodes.

• go to System => System information => Services column

• all values in Database pool priority column must have value 0
  
  Note: Database pool priority on the original master node will probably be non zero (as it is not running and cannot be synchronized).

  

Perform this step on all CML servers that remained functional (did not crash)

 Skip this step in case there exists just one CML node in the environment (non-clustered installation)

Using the program pgAdmin III or MS SQL management studio connect to the SQDB5 database:

• Connect using the first database account (not Sync).

• Enter the password you have selected during CML installation when asked for it.

2a.  Find out the master node db_flag using the following query:

• select db_flag from cluster_server where id = (select min(id) from cluster_server)
   

2b. Run the following queries. Replace x by the proper db_flag for the master node (obtained in the previous step) before running them :

• delete from cluster_sync_update_10 where server_flag & x = x;

• delete from cluster_sync_update_20 where server_flag & x = x;

• delete from cluster_sync_update_30 where server_flag & x = x;

Perform the database backup of SQDB5 database on CML2 (the second node of the cluster).
In case that you have just 1CML node in your environment, skip this step as you will use the database backup created by regular daily backup.

Perform following step on the node which you are recovering:

1a. Perform the installation

Install YSoft SafeQ in the new location according to Installing YSoft SafeQ CML instructions.

Installation requirements:

• Install only one CML server node (Do not connect it in to existing cluster!)

• Use the same database type as for other nodes that are installed already

• Untick the "Start SafeQ services after the installation is finished" option

1b. Restore databases

Restore databases according to CML - Database restore instructions with following exceptions:

• Restore SQDB5 from the backup made on CML2 in the previous steps (in case of standalone CML installation use the backup created by regular daily backup)

• Restore SQDB5_SQDW from the backup created by regular daily backup of the original master node (1st installed node)

• Do not start YSoft SafeQ services at the end of the restoration procedure but continue with the next step of this guide

1c. Run these queries at master node on SQDB5

• delete from cluster_sync_update_10;

• delete from cluster_sync_update_20;

• delete from cluster_sync_update_30;

1d. Modify the database

Using the program pgAdmin III or MS SQL management studio connect to the SQDB5 database:

• Enter the password you have selected during CML installation (for database user, do not use the account Sync).

• Open cluster_server table and change localhostvalue as follows:

  • localhost = 1 for the first row (row that contains name and IP address of the server you are restoring)

  • localhost = 0 for all others rows

    

1e. Using pgAdmin III or MS SQL management studio run following query:

• delete from smartq_validator

1f. Replace the configuration files

Overwrite existing configuration files with original configuration backup:

• <SAFEQ_DIR>\conf

• <SAFEQ_DIR>\terminalserver\TerminalServer.exe.config

• <SAFEQ_DIR>\tomcat\conf

• Delete or rename <SAFEQ_DIR>\conf\update.conf file (it would block the start of YSoft SafeQ CML service)

WARNING: This step requires the password for database/sync users in the database is the same as it was before the failure. Skip this step and configure server manually if you do not have exactly the same configuration as before the server failure! However (if you have ORS connected) keep in mind:

• localGUID in startup.conf must be configured the same way as before the failure
  

1g. Restore spooled jobs

Restore your backup of temp and spool directory

• Copy spool directory from original YSoft SafeQ server to <SAFEQ_DIR>\server\spool

• Copy temp directory from original YSoft SafeQ server to <SAFEQ_DIR>\server\temp

• Copy folder containing scripts for scanning (if scan to script is used) to the same location as it was on the original server

1h. Start services on Master node:

Open Services (e.g. Start => Run => services.msc) and start all YSoft SafeQ services in any order:

• YSoft SafeQ CML

• YSoft SafeQ CML DBS

• YSoft SafeQ Terminal Server
  

• YSoft SafeQ LDAP Replicator Service

• YSoft SafeQ Web Interface

Log in to the web interface (YSoft SafeQ Web interface => System => System information) of the master node.

• Verify that all servers are showing status ONLINE (the node you are connected to may show status LOCAL)

• Verify that synchronization between the nodes in the cluster is functional. See table DBsync database & system pools (non-local servers only). Values in column Database pool priority must not be growing constantly. They shall be changing and they shall be often around 0.

Test authentication/print/copy/scan. All functions must be working. Also accounting must return the correct data.

In case of non-clustered environment (1CML only), cache on every ORS has to be deleted. For specific instructions see article ORS - How to delete corrupted cache.