Back up critical configuration data

The main OpsCenter configuration directory contains critical data, such as the opscenterd.conf configuration file. The cluster topology, configuration profiles, credentials, repositories, and job history for Lifecycle Manager (LCM) is stored in the lcm.db database. Your organization is responsible for backing up these files, in addition to the critical configuration data outlined in this procedure.

DataStax strongly recommends that you enable automatic failover from the primary OpsCenter instance to a designated backup OpsCenter instance.

Location of the files used in this procedure
Filename	File Description	Paths per type of installation
`lcm.db`	Lifecycle Manager database	Package installations: `/var/lib/opscenter/lcm.db` Tarball installations: `INSTALL_DIRECTORY/lcm.db`
`lcm.key`	Lifecycle Manager database encryption key	Package installations: `/etc/opscenter/lcm.key` Tarball installations: `INSTALL_DIRECTORY/keys/lcm.key`
`passwd.db`	password database	Package installations: `/etc/opscenter/passwd.db` Tarball installations: `INSTALL_DIRECTORY/passwd.db`
`opscenterd.conf`	Opscenterd configuration	Package installations: `/etc/opscenter/opscenterd.conf` Tarball installations: `INSTALL_DIRECTORY/conf/opscenterd.conf`

The following steps indicate mirroring data between a primary OpsCenter instance and a backup OpsCenter instance:

Mirror the contents of the main configuration directory on the primary OpsCenter instance to the backup OpsCenter instance. For package installations, this is /etc/opscenter. For tarball installations, this is INSTALL_DIRECTORY/conf.
```
scp /etc/opscenter/* secondary:/etc/opscenter
```
Do not mirror the failover_configuration_directory across OpsCenter installs when configuring OpsCenter to support failover.
Mirror the contents of the persist_directory location that indicates the current status of the Repair Service. The location of the persist directory for the Repair Service depends on the type of installation. For package installations, this is /var/lib/opscenter/repair_service. For tarball installations, this is INSTALL_DIRECTORY/repair_service.
```
scp /var/lib/opscenter/repair_service/* secondary:/var/lib/opscenter/repair_service
```
Repair Service progress is stored on the filesystem. If using an NFS mount to mirror to, the Repair Service starts up after a failover from approximately the same point where it was interrupted. If manually copying directories or using rysnc, the Repair Services resumes from whenever the Repair Service directory was last synced. Otherwise, the Repair Service simply restarts rather than continuing from where it left off.

The diagnostic tarball includes the repair persistence files. See repair_service_incremental.json and repair_service_subrange.json.
Back up the Lifecycle Manager database, encryption key, and security certificates:
1. Mirror the Lifecycle Manager database lcm.db. For package installs, this is located at /var/lib/opscenter/lcm.db. For tarball installs, this is located at INSTALL_DIRECTORY/lcm.db.
  scp /var/lib/opscenter/lcm.db secondary:/var/lib/opscenter/lcm.db
2. Mirror the Lifecycle Manager database encryption key lcm.key. For package installs, this is located at /etc/opscenter/lcm.key. For tarball installs, this is located at INSTALL_DIRECTORY/keys/lcm.key.
  scp /etc/opscenter/lcm.key secondary:/etc/opscenter/lcm.key
3. If Lifecycle Manager has generated any certificates for clusters configured to use node-to-node or client-to-node encryption, mirror the Lifecycle Manager certificate authority. For package installs, this is located at /var/lib/opscenter/ssl/lcm. For tarball installs, this is located at INSTALL_DIRECTORY/ssl/lcm/cacerts.
  scp -r /var/lib/opscenter/ssl/lcm secondary:/var/lib/opscenter/ssl/
If SSL is enabled, mirror the contents of the ssl configuration directory on the primary OpsCenter instance to the backup OpsCenter instance. For package installs, this is /var/lib/opscenter/ssl. For tarball installations, this is INSTALL_DIRECTORY/ssl.
```
scp /var/lib/opscenter/ssl/* secondary:/var/lib/opscenter/ssl
```
If OpsCenter role-based security is enabled, mirror the roles and password database passwd.db. For package installs, this is located at /etc/opscenter/passwd.db. For tarball installs, this is located at INSTALL_DIRECTORY/passwd.db.
```
scp /etc/opscenter/passwd.db secondary:/etc/opscenter/passwd.db
```

Back up critical configuration data

Was this helpful?

Give Feedback