This page describes the recovery of a single Site Server (which is not part of any Spooler Controller group) that was installed using the Server installer package – a Site Server deployment scenario. It is expected that the server is no longer functional and a new one will be used to replace it.

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.

In case of a Standalone Site Server, all data stored inside the Terminal Server cache will be lost, so you will need to reinstall all affected Dispatcher Paragon Embedded Terminals after Site Server is recovered. If you want to avoid that, please, consider etcd cluster of at least three nodes.

Site Server Recovery

Prepare a server (or a virtual machine) with the same hostname/IP as the original Site Server had used.
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. Site Server GUID (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 Site Server using the same build installation package.
1. Enable optional features if they were used before (see step 2.a).
2. Configure the connection to Management Server(s) the same way as was configured before.
3. Provide the wizard with the same Site Server GUID that was used before (see step 2.b).
4. Finish the installation.
  See Site Server Deployment for a detailed procedure.
If Dispatcher Paragon Payment System with an embedded PostgreSQL database was installed on the Site Server that is being restored, perform the following steps:
1. Stop almost all Dispatcher Paragon services after installation is finished.
  1. Leave only the YSoft Bundled PostgresSQL 11 service running.
  2. Stop all other Dispatcher Paragon services.
    - You can use the following PowerShell script to perform the task:
      Get-Service *YSoft* | Where-Object {$_.Name -notmatch 'YSoftPGSQL'} | Stop-Service
2. Run the pgAdmin administration tool <DispatcherParagon_DIRECTORY>\PGSQL\bin\pgAdmin4.exe (e.g., c:\DispatcherParagon\PGSQL\bin\pgAdmin4.exe)
3. In the Object browser window, double-click the SafeQ 6 item and connect to the server
  1. Delete the current SQDB6_YPS database:
  2. Create a new SQDB6_YPS database:
    1. Right-click Databases > Create > Databese...
    2. Create a new SQDB6_YPS database with Owner set to postgres:
  3. Restore SQDB6_YPS database from the backup file:
    1. Right-click the database name and select Restore... option.
    2. Select your backup file
    3. Click Restore.
    4. The backup will be restored.
    5. Popup appears with information that procedure ended successfully
    6. Click on More details to see log.
4. Start 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.
  - You can use the following PowerShell script to perform the task:
    Get-Service *YSoft* | Where-Object {$_.Name -ne 'YSoftSQ-SPOCGS'} | Start-Service
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 a customized configuration (such as your own certificates for the web services), seek the relevant documentation and set up the configuration again.
Check the Management Web interface, the Spooler Controller must be correctly shown as online.
Reinstall all Dispatcher Paragon Embedded Terminals that are managed by the affected Spooler Controller.