Responding after significant replica server activity

A replica server might have significant activity while the primary GuardiumĀ® Key Lifecycle Manager server is down. Select an announced maintenance interval, when network traffic is stopped, to back up the replica server and restore the backup file to the primary server.

About this task

No alerts are issued if the replica server provides keys to a device. Validate that there is a need to back up the replica computer and then restore the backup file to the primary server. For example, you might determine whether a write request caused a key to be served to a device. Use the Served Data List REST Service to query the database and to list served data. Less significant information might be available in the audit log for read requests from devices.

Procedure

  1. At an announced time when network traffic is stopped, back up the replica computer.
  2. Restore the backup file from the replica computer onto the primary computer on which Guardium Key Lifecycle Manager server customarily runs.

What to do next

Verify that the primary Guardium Key Lifecycle Manager server is active and that the backup file was successfully restored.