Backing Up Configurations

During normal production operations, you rely on directory replication to maintain multiple, current copies of AM's configuration. To recover from the loss of a server or from a serious administrative error, back up directory data and configuration files.

To backup your external configuration directory server, see the chapter Backup and Restore in the DS Maintenance Guide.

To Back Up Instance Configuration Data

This procedure backs up the configuration files stored with the server. This backup is to be restored when rebuilding a failed server.

Consider the following when using this procedure:

Refer to the documentation for your external directory server or work with your directory server administrator to back up and restore configuration data stored in the directory service. For more information about DS, see the chapter Backup and Restore in the DS Maintenance Guide.
Do not restore configuration data from a backup of a different major version of AM. The structure of the configuration data can change from release to release.

Follow these steps for each AM server that you want to back up:

Stop AM or the container in which it runs.

Back up AM server files.

This example uses the default configuration location, and excludes logs. $HOME is the home directory of the user who runs the web container where AM is deployed, and AM is deployed in Apache Tomcat under openam:

$ cd $HOME
$ zip --recurse-paths \
  AM-config-dir-backup-`date -u +%F-%H-%M`.zip \
  "openam" ".openamcfg/*" \
  --exclude "openam/var/debug/*" "openam/var/audit/*" \
    "openam/var/stats*" "openam/opends/*"
...
$ ls AM-config-dir-backup-2020-08-01-12-00.zip
AM-config-dir-backup-2020-08-01-12-00.zip

Start AM or the container in which it runs.