In this article, you will learn
- which directories should be included in the backup,
- which services need to be stopped during the backup, and
- how you can restore the application.
1. Introduction
Regular backups are essential to prevent data loss and to ensure the security of the application. Backing up data allows for a quick recovery of normal operations in the event of errors or system failures. This article outlines the key procedures for data backup and restoration to ensure long-term system availability.
2. Backup
A backup of the server – a complete backup – must be implemented under all circumstances, as recovery in the event of a failure is not possible without it. Be sure to coordinate the backup strategy in advance with your IT administrators.
2.1. Manual Backup
Before a manual backup can be performed using your chosen backup software, certain preparations must be made. Please observe the following instructions:
The following directories must be included in the backup:
-
PMS data directory (default
C:\PMS_DATAand possiblyD:\PMS_DATA) -
PMS program directory (default:
C:\Program Files\PPD)
If you use user-defined directories that are located outside the PMS_DATA directories, these must also be included these in the backup. This also applies, among others, to monitored Hotfolders and directories for storing images used in overlays for Print Items as well as variable Production Jobs.
Stopping Services for the Backup
During the backup process, the services PMS and PPD-PostGreSQL must be stopped. This can be done using the following commands in the Windows command prompt:
- net stop zunicomm
- net stop pms
- net stop ppd-postgresql
2.2. Automatic Backup
Since the application does not provide any tools for creating backups and this is outside the scope of our development, we recommend acquiring appropriate backup software to secure your data. This ensures the ability to quickly restore a production environment or that your own existing IT backup strategy can be applied effectively.
A suitable software solution for creating snapshots or backups is, among others, Veeam (https://www.veeam.com), which we also use as our internal backup solution.
Backup is required
It is absolutely necessary to create a daily (incremental) backup or snapshot of the daily system state to prevent or minimize production downtime.
We cannot assume any responsibility for production outages. It is the users responsibility to ensure that functioning and up-to-date backups are in place.
3. Recovery
If you need to restore a saved system state, hopefully you have the option of using an automatically generated snapshot. Manual recovery is significantly more time-consuming and more prone to errors!
3.1. Manual Recovery
Manual Recovery is essentially equivalent to a reinstallation of the application, including the restoration of certain directories from the most recent backup.
To do this, proceed as follows:
- Run the setup routine – see Installing the Application. Preferably, use the same version that was present at the time the backup was created.
Equivalent or newer version
Under no circumstances an older version should be installed!
- After completing the installation, the services PMS, ZuniComm, and PPD-PostgreSQL must be stopped (see note Stopping Services for Backup).
- We recommend deleting all files from the following directories before restoring data from the backup:
-
PMS data directory (default
C:\PMS_DATAand possiblyD:\PMS_DATA) - If a newer version was installed, you must also delete the PPD program directory (default
C:\Program Files\PPD) before proceeding to the next step, and replace it with the corresponding directory from the backup.
-
PMS data directory (default
- Restore the saved directories from the backup to their original locations.
- After restarting the stopped services ZuniComm, PMS, and PPD-PostgreSQL, the system is ready for use again:
- net start zunicomm
- net start pms
- net start ppd-postgresql
Recovery on a new server
If the system is installed on new hardware, you must notify the license server administrator within five days, otherwise the application will automatically stop running. Please contact your application service partner to arrange this.
3.2. Automated Recovery
If you have used backup software and have received a corresponding backup or snapshot from the server, the recovery of the production environment can be performed in a standardized and reliable manner within a manageable timeframe.
To restore a backup, follow the restoration procedures provided by the vendor of the backup solution.
Article update: Workflow 1.20.0 – 07/2025