This chapter describes how to restore the cluster in case that all the nodes has failed. There are following prerequisites:

YSoft SafeQ database backup from the master node (1st node of the cluster) is a MUST for restoration of cluster after the failure.
It is expected that also the configuration files backup exists.

Spool directory is not restored. Users will have to send their jobs for the print again.

Warning

If you are going to recover the first CML node of the cluster (master) or the standalone CML server on a new computer (meaning on a new installation of operating system or on a different server), you must request the license reactivation on a new hardware. For more information see chapter Transferring license to new system - hardware or operating system change.

Step 1 - how to configure print drivers in case of cluster failure (optional)

If the cluster is not operational and you need to sustain the printing functionality until the cluster is restored, see Printing without CML (CML cluster Failure). The guide will help you with the configuration of the direct printing from the workstation to the MFP.

All jobs printed during the cluster failure will not be accounted.

Step 2 - restore hardware after the server failure (optional)

Restore hardware required for YSoft SafeQ server.

WARNING: Make sure that all servers has the same IP address as they had before the failure.

Step 3 - restore software after the server failure

1

Install one of the supported operating systems for YSoft SafeQ server

Make sure that the same drives as in the system before the failure exists (e.g. for YSoft SafeQ and spool directory)

2

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

Database type MUST be the same as before the failure.

Step 4 - install CML Master node (1st node)

1	Install 1st node according to the Installing YSoft SafeQ CML instructions. Do not start services after the installation! (untick checkbox at option Start SafeQ services after the installation is finished)
2	Restore database SQDB5 and SQDB5_SQDW from the existing backup. Do not start YSoft SafeQ services at the end of the restore procedure but instead continue with the next step of this guide.
3	Overwrite configuration files with the existing backup of the configuration. Content of the following folders has to be replaced: <SAFEQ_DIR>\conf <SAFEQ_DIR>\terminalserver\.config <SAFEQ_DIR>\tomcat\conf Copy folder containing scripts for scanning (if scan to script is used) to the same location as it was on the original server 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 keep in mind: localGUID in startup.conf must be configured the same way as before the failure*
4	Open the Services window (e.g. Start => Run => services.msc) and set YSoft SafeQ services to run under the same account as before the failure.
5	Start all YSoft SafeQ services: YSoft SafeQ CML YSoft SafeQ CML DBS YSoft SafeQ LDAP Replicator Service YSoft SafeQ Web Interface YSoft SafeQ Terminal Server

Step 5 - install slave nodes

Repeat following steps for all slave nodes.

1

Install remaining cluster nodes according to the CML - Recovery procedure for slave node.

2

Open the Services window (e.g. Start =>Run => services.msc) and set YSoft SafeQ services to run under the same account as before the failure.

Step 6 - restore printing via YSoft SafeQ and verify the proper functionality

Repeat following steps for all slave nodes.

1	If you have pointed print drivers directly to the MFPs, point them back to the YSoft SafeQ servers.
2	Log in to the web interface (YSoft SafeQ Web interface => System => System information) 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 and 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.
3	Test authentication/print/copy/scan. All functions must be working. Also accounting must return the correct result.
4	Once all the nodes are restored, cache on every ORS has to be deleted. For specific instructions see article ORS - How to delete corrupted cache.