This page describes the recovery of a single management node (which might be part of a Spooler Controller group) and that was installed using the Server installer package – First server deployment scenario.

Please enable license reactivation before transferring the license to a new server (e.g., when the original hardware fails or when an OS is reinstalled).

This guide assumes that you have a backup of databases and a backup of configuration (and binary) files available.

Jobs stored on the non-functional server will be lost and users will need to submit them again.

Recovery

Prepare a server (or a virtual machine) with the samehostname/IP as the original Management Server had used.
If you are using an external database (on another server), check its state.
1. If the external database is damaged, perform a Recovering Databases but skip the Finalization part for now.
Check the backup of the configuration files and note the following:
1. Which optional features were installed:
  1. Mobile Print Server - an MPS folder is available in backup files.
  2. Dispatcher Paragon Payment System - a 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 = MGMT1
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 = ectp5o8ep0op3hzi
Reinstall Management Server using the same version build of the installation package.
1. Enable optional features if they were used before (see step 3.a.).
2. Provide the wizard with the same Management Server GUID that was used before (see step 3.b.).
3. If you have Dispatcher Paragon MU11 or later build, also provide the wizard with the same SPOC GUID that was used before (see step 3.c.).
4. Finish the installation.
  See First server installation for a detailed procedure.
Stop almost all Dispatcher Paragon services except the Dispatcher Paragon Bundled PostgresSQL service (available if embedded a PostgresSQL DB is used) after installation finishes.
You can use the following PowerShell script to perform the task:
Get-Service *YSoft* | Where-Object { $_.Name -ne 'YSoftPGSQL' } | Stop-Service
If you are using an embedded PostgreSQL database, perform a Recovering Databases but skip the Finalization part for now (as new empty databases were created during the installation).
If you have Dispatcher Paragon MU10 or older build, edit <install_dir>\SPOC\conf\modules\guid.conf, and rewrite the localGUID to the value that was used before (see step 3.c.).
Delete the SPOC cache by deleting the whole folder <install_dir>\SPOC\SpoolCache.
Start the Dispatcher Paragon services with the Automatic startup type again.
Do not start Dispatcher Paragon Spooler Controller Group Service. It will be started by the Dispatcher Paragon Spooler Controller service when the proper configuration is ready.
You can use the following PowerShell script to perform the task:
Get-Service *YSoft* | Where-Object { $_.Name -ne 'YSoftSQ-SPOCGS' } | Start-Service
Re-activate the Dispatcher Paragon license using your preferred method (online/offline). See Management Interface - License Activation for detailed instructions.
Restore 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 the backup.
3. If you used customized configuration (such as your own certificates for the web services), seek the relevant documentation and set the configuration up again.
Check that Spooler Controller is correctly connected on the management web.

Finalization

Clear the Cache on Other Spooler Controllers and Start All Services Again

Cache on Spooler Controllers needs to be deleted after Database restore to avoid possible inconsistencies.

Delete Spooler Controller cache directory on all servers

Delete Dispatcher Paragon Spooler Controller cache by deleting whole folder <SPOC_DIR>\SpoolCache (e.g. C:\DispatcherParagon\SPOC\SpoolCache)

Start Management service again

Open the Services window (e.g. Start > Run > services.msc) and start the following services:

Start Dispatcher Paragon Management Service

Verify the Spooler Controller cache recovery settings

Go to tab System > Configuration on Dispatcher Paragon Management web interface and set orsCacheRecovery property to enabled.

In case of Dispatcher Paragon Spooler Controller cache data corruption, cache can be manually deleted and all job-related metadata will be recovered from Dispatcher Paragon Management Server.

If you omit this step, all jobs stored on the Dispatcher Paragon Spooler Controller might be lost after the end of procedure.

Start the remaining services on all servers

Do not start Dispatcher Paragon Spooler Controller Group Service manually. If Dispatcher Paragon Spooler Controller is part of Spooler Controller group then this service will start automatically when its configuration is ready.

Start remaining Dispatcher Paragon services with Automatic startup type in no particular order

Verify the correct Spooler Controller functionality

Once the Dispatcher Paragon Spooler Controller cache is deleted and Dispatcher Paragon Spooler Controller services are running, verify the correct Dispatcher Paragon Spooler Controller functionality according to the article Spooler Controller Health Check.

Reconfigure the etcd Cluster in Terminal Server if Failover for Embedded Terminals Is Being Used

If failover for embedded terminals is being used and parameter enableEtcd is enabled, then the etcd cluster in Terminal Server must also be reconfigured.
1. Follow Reconfiguring or Recovering an etcd Cluster in Terminal Server.