Epic Solution Best Practices

InterSystems Caché

We recommend that you use the following configuration guidelines when you use the Epic Solution.

  1. Configure the client that you use for the InterSystems Caché databases to use encryption. For information on how to configure encryption for a client, see client encryption.
  2. Configure storage policies for each data set.

    Note: Verify with InterSystems and Epic that these are the latest guidelines.

    Data Covered by Storage Policy

    Best Practice

    InterSystems Caché databases

    Set the storage policy data retention to 14 or more days and 2 cycles.

    InterSystems Caché journal files

    Set the storage policy data retention to 14 or more days.

    Note: This value is based on a default installation. You can modify this value based on your Recovery Point Objective (RPO).

  3. Use the InterSystems Caché Integrity Checker to verify the data. For information on how to use the utility, go to the InterSystems website, Caché Data Integrity Guide.
  4. Use multiple data readers when you back up the Intersystems Caché databases. For information on how to configure multiple data readers, see Configuring File System Multi-Streaming.
  5. Run daily full backups of the Intersystems Caché database subclient. If you cannot complete a full backup within 24 hours, you must optimize or upgrade the backup infrastructure to ensure that the backups can complete.
  6. Use the restore by job option when you restore the Intersystems Caché databases from a magnetic library or tape copy. The number of streams that you use for the restore must match the number of streams that were used in the backup job. For information on how to perform the restore, see Restore by Jobs.
  7. Use the same operating system for both the production Caché server and the backup copy proxy machine so that there are no incompatibilities in file systems or volume structures.
  8. If you use AIX for Caché server, add a file system freeze to the pre-script and a file system thaw to the post-script. For more information, contact your IBM or Epic representative.
  9. If you use Red Hat 7.x or CentOS 7.x for the backup copy proxy, disable lvmetad:”.
    1. Disable and stop the lvm2-lvmetad service. To do this, run the following command:

      systemctl disable lvm2-lvmetad
      systemctl stop lvm2-lvmetad

    2. Disable lvmetad in to the LVM config file. To do this, run the following command:

      edit /etc/lvm/lvm.conf to include use_lvmetad = 0

  10. For all remaining servers, see Epic Business Continuity Technical Solutions Guide for addition backup guidelines.

Last modified: 10/2/2018 11:56:16 AM