This page describes the recovery of a single node of a Management Server cluster that was installed using the Server installer package – a First Server or Additional Management Server deployment scenario.

1. Prepare a server (or a virtual machine) with the same hostname/IP as the original Management Server had used.

2. Check the backup of the configuration files and note the following:

   1. Which optional features were installed:

      1. Mobile Print Server – The MPS folder is available in backup files

      2. Dispatcher Paragon Payment System – The YPS folder is available in backup files

   2. Management Server GUID. It is noted in the safeq.properties file as the value of the communicator.cml.guid option. For example:

      backup\Management\conf\safeq.properties

      # COMMUNICATOR

      communicator.cml.guid = MGMT3

   3. SPOC GUID. It is noted in the guid.conf file as the value of the LocalGUID option. For example:

      backup\SPOC\conf\modules\guid.conf

      localGUID = j23892stpkfmvri9

3. Reinstall Management Server using the same build installation package.

   1. Select the Other servers and Additional Management server options.

   2. Enable optional features if they were used before (see step 2.a.).

   3. Provide the wizard with the same Management Server GUID that was used before (see step 2.b.).

   4. If you have YSoft SafeQ 6 MU11 or later build, also provide the wizard with the same SPOC GUID that was used before (see step 2.c.).

   5. Finish the installation.

      See Dispatcher Paragon Management Server cluster deployment for a detailed procedure.

4. If you have Dispatcher Paragon MU10 or older build.

   1. Stop all Dispatcher Paragon services after the installation is finished.
      You can use the following PowerShell script to perform the task:

      Get-Service *YSoft* | Stop-Service

   2. Edit <install_dir>\SPOC\conf\modules\guid.conf and rewrite the localGUID to the value that was used before (see step 2. c.).

   3. Delete the SPOC cache by deleting the whole folder <install_dir>\SPOC\SpoolCache.

   4. Start the Dispatcher Paragon services with the Automatic startup type again.

      Do not start the Dispatcher Paragon Spooler Controller Group Service. It will be started by the Dispatcher Paragon Spooler Controller service when the proper configuration is ready.
      

      1. You can use the following PowerShell script to perform the task:

         Get-Service *YSoft* | Start-Service

5. Add the GUIDs, ports, and IP addresses of other Management Server cluster nodes into the configuration of Dispatcher Paragon Spooler Controller on the reinstalled Management Server.

   1. Open the <install_dir>\SPOC\conf\modules\spoc.conf file on the other Management Server cluster node and copy the content of the Connections to CML server nodes: GUID, IP and PORT section (this node contains the correct configuration where all Management Server cluster nodes are listed).

   2. Paste these values into the Connections to CML server nodes: GUID, IP and PORT section of the <install_dir>\SPOC\conf\modules\spoc.conf file on the reinstalled Management Server and save the changes.

   3. Restart the Dispatcher Paragon Spooler Controller service on the reinstalled Management Server to apply the changes.

   4. For more information see Dispatcher Paragon Management Server cluster deployment section Reconfiguration of Dispatcher Paragon Site Servers to connect to all Dispatcher Paragon Management Servers.
      

6. If the reinstalled node was the one on which the Dispatcher Paragon license was activated, re-activate the Dispatcher Paragon license using your preferred method (online/offline). See Management Interface - License Activation for detailed instructions.

7. Check that Spooler Controller is correctly connected on the management web.

8. Restore the customized configuration:

   1. If you had services running under a specific domain account, set it up again.

   2. If you used customized scripts on the server (e.g., for batch files launched by Rule-Based Engine or customized batch files used by Workflow Processing System), restore those scripts from backup.

   3. If you used customized configuration (such as your own certificates for the web services), seek the relevant documentation and set up the configuration again.