Data backup recommendations

The following lists recommended practices for backing up application files and external databases. These guidelines cover regular operation of Interchange and before upgrading to a new version or service pack.

Although broad in scope, these practices are intended to avoid worst-case issues that may arise in a production environment or when upgrading.

  1. Back up the installation directory on a regularly scheduled basis. Follow your company's policy for data backups or make up your own backup schedule. If you store data in one or more directories other than common\data, back up those, too.
  2. If you use Windows, turn off the server before backing up files. This is recommended because Windows locks files in use by an application, which prevents files from being copied while locked. UNIX and Linux systems do not lock files.
  3. Back up the external database on a regularly scheduled basis. Schedule database backups to occur at about the same time as file system backups. For the trading engine, it's important to synchronize these backups because the database references certificate data in the common\conf\keys directory.
  4. Export the private keys for the encryption, signing, and SSL certificates for each community profile. Keep the key backups in a secure location.
  5. Before upgrading to a new version or service pack, do the following:
    1. Turn off the server. All processing must be halted before upgrading.
    2. Back up files as described in step 1.
    3. Back up the external database as described in step 2.
    4. Back up private keys as described in step 3.
  6. Unless data are backed up before upgrading, you cannot revert to the previous version if the need arises. Even with proper backups, retreating to the state before the upgrade may be difficult or impossible due to hardware or software issues unique to your network. In the worst case, you may have to re-install the application and begin anew with a fresh database.

Related topics

Related Links