Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

Backup and disaster recovery procedures are recommended tasks to be carried out at a regular basis to avoid performance degradation.

Complete system backups to an external disk should be performed at regular time intervals, and preferably at times when the traffic load is low, e.g. at night. The reasonable time interval might be depending on how the system is configured, the amount of traffic, etc, and may vary from installation to installation.

General Requirements

Regardless of the method chosen for the provisioning of backup and restore operations, there are requirements that must be met: 

  1. When an instance is restored from a backup image, the database backup must be older than the disk backup. The reason for this is to avoid database references to non-existing data.

  2. Temporary files must be excluded from the backups. This is to avoid inconsistent or partial data. 

Temporary files can be identified by various identifiers that form the file names:

  • Temporary files – Prefixed with "TEMP."

  • DupUDR function temporary files – They are in a separate folder called "tmp". 

  • InterWorkFlow temporary files – Stored in a separate folder called "DR_TMP_DIR". 

  • Archiving function files – Stored in a separate folder called "pending". 


This chapter includes the following sections:


  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.