Opalis Integration Server has been designed to store its data in a central location to facilitate easy backup operations.  By using centralized data storage the details of an Opalis Integration Server installation are easily backed up by creating a backup of the Opalis database using the backup tools provided by the database application.

Backing up the database backs up the information for all configuration components including (but not limited to):

• Policies
• Objects (including Integration Pack object definitions and configurations)
• Log History
• Opalis Events
• Licenses
• Counter Definitions
• Variable Definitions
• Schedules

Backing up the database does not back up elements such as program files, debug logs, object input/output files or database connectivity settings.

Program files and database connectivity settings can be replaced by re-installing the application.  The Database Configuration utility installed with the Management Server and each Action Server is provided to establish a connection to an existing database and will re-create the database connectivity settings.

Object input/output and debug logs must be backed up using a file system backup application, such as NTBackup.  Apply best practices for backing up file system data according to the backup application that you use.  These types of files are not needed for the successful restoration of an environment and therefore do not need to be restored as part of any disaster recovery or business continuity process.

If a database backup is taken while policies are actively executing then the backup data will include runtime state information that should be cleared if the backup is restored. 

If a database backup is restored, the following T-SQL should be executed after the database has been restored and prior to bringing any Action Servers online in order to clear any incomplete or pending policy instances that were captured as part of backing up an active environment:

UPDATE POLICY_REQUEST_HISTORY SET Active=0 WHERE Active=1
UPDATE POLICIES SET Published=0 WHERE Published=1
TRUNCATE TABLE POLICY_PUBLISH_QUEUE