System Recovery

The PPS Server Suite contains the live backup software Stoll Pps DB Backup that needs to be setup and activated after the installation.

Constraints of Usage:

• Sufficient disk space for a rolling backup.
  Standard value: 1GB per machine by the number of backup generations (days)
• For security purposes, save the backup on an external data medium.
• Do not use internal disk of the PPS server.
• USB 3.0 or higher recommended
• Backup on network drive is perhaps not performant enough
• Provide a UPS for the PPS server in order to enable at any time a reliable backup or recovery.
• Preview a safe storage location
  Safe regarding:
• Storm, water. lightning, fire, earth quakes
• Unauthorized access
• Update to a new version of PostgreSQL software may lead to incompatibility.
  Former backups may be no longer usable by the new version.
• Save former backups separately
  Within the time period of the rolling backup you can restore any desired moment. But no older state, unless you saved them somewhere else.

Notes about Configuration and Usage:

• In the PPS under Configuration \ Other configuration \ SKR3 Backup is displayed the status of the backup. In case of errors, for ex. Data medium full, an error status appears. Configure for yourself (as soon as available) an E-Mail alarm for error messages, so that you are promptly informed about faults.
• The Stoll Pps DB Backup Restore Config program checks whether the backup was created properly and displays the state in the State column of the Restore Points table under the Restore backup tab. Further inspections about the integrity of the data are performed by the database software during the recovery. When detecting an error, a message is displayed. In the c:\skr3log\StollPpsDbBackupRestoreLog.txt log file, the action carried out and its result are logged.
• Before carrying out an update of the PPS Server Suite, always create a copy of the current backup and save it at a safe location.
• Regularly save a backup from the previous day on a safe location before carrying out the backups.
• On each day, the Base back up is created at first. This backup is a full backup of the present data and backs up also the files of the PPS 2.0.x SKR3_DB_15\DB_Root folder (formerly SKR3_DB\DB_9_4_Root). Incremental backups are added to the Base backup until the next day. Actually they are carried out as soon as there are any changes in the database, with a reduced time delay.
• The Base backup corresponds to the last state of the previous day but it is more compact.
• Files are accessed during the backup of the current day.
• Copying will not be possible until the backup function is deactivated.
• Or the next day, when the following backup is created.
• The closer the recovery moment is to the Base backup, the faster a backup can be reloaded into the database.
• The older a backup is, the less updated is the data. The Recovery function of the PPS and SKR3 buffer can recover more recent parts of the order data and machine events with information that is buffered in the machine. Released and running orders are recovered in the PPS and can be checked and completed.
• The distribution of the individual databases to the different drives does not need to be taken into account when restoring the database. You can recover the database in spite of a changed distribution.
• In case you have entered permissions in the SKR3_DB_15\DB_Root\PG_15\pd_hba.conf (starting with PPS 2.0.x, formerly SKR3_DB\DB_9_4_Root\PG_9.5\pd_hba.conf)or SSL connections in the SKR3_DB_15\DB_Root\PG_15\postgresql.conf (starting with PPS 2.0.x, formerly SKR3_DB\DB_9_4_Root\PG_9.5\postgresql.conf) for enabling the access to the database, they will be reset to the moment of the Base back up by a recovery.
• A recovery to the state where no SSL connections were setup will fail if you had setup SSL connections for the database. First cancel the previous SSL configuration and then restart the SKR3 service.