Introduction

In order to quickly restore a CXO-Cockpit application it is important to make frequent backups. CXO-Cockpit will never be the main data storage of the actual data, it will contain either a copy of the main data source or it will connect directly to the main data source. This article will not cover the backup of the main data source, it will mainly provide guidelines for backing up the CXO_Cockpit configuration and report definitions.

The CXO-Cockpit configuration is stored in some application files, but mainly in the repository database.

File Backup

File backup is not really necessary, because the software can always be reinstalled. However to quickly restore a CXO-Cockpit application it can be helpful to have backups of the following files from the web/application server:

• Installation archive of the installed CXO-Cockpit version
• .config files of the Program Files\CXO Solutions\CXO-Cockpit subfolders
• web.config file of Program Files\CXO Solutions\CXO-Cockpit\Website
• Customised images from Program Files\CXO Solutions\CXO-Cockpit\Website\CustomStyles\Images
• customization.css from Program Files\CXO Solutions\CXO-Cockpit\Website\CustomStyles

The frequency of the file backup does not need to be very high. Typically this needs to happen after installation or configuration changes.

Database Backup

Every CXO-Cockpit application uses a repository database. This repository is most important to backup, because it contains all report configuration like report definitions, security setup, etc. The name of the repository database is normally cxo_repository_APPNAME.

For free models this is all that needs to be backed up.

For CXO-Cockpit applications that use an integration adapter it is also important to backup the:

• Fact Database called cxo_fact_SOURCESYSTEMNAME

• Staging Database called cxo_staging_SOURCESYSTEMNAME

The frequency of the backup depends on the level of configuration changes, typically a weekly backup will be sufficient.