Restoring the Imprivata Database from a Backup

If the Imprivata database becomes corrupt or otherwise compromised, you can restore it from a backup file.

NOTE: Only a Super Administrator can restore the Imprivata database. For a G4 (fourth generation) enterprise, you can restore the database only from a database appliance.

Synchronizing the Imprivata Database

When you restore the Imprivata database from a backup, the restoration process automatically synchronizes both database appliances in a G4 enterprise.In a G4 enterprise, only database appliances contain an instance of the database.

Independent of a database restoration, you may need to synchronize the Imprivata database to fix a replication problem.

NOTE: Synchronization can only be performed by a Super Administrator on a database appliance for a G4 enterprise. Contact Imprivata Customer Support for assistance with this procedure.

CAUTION: If you have a network device on which SQLNet inspection is enabled, Imprivata recommends that you disable SQLNet inspection before synchronizing the Imprivata database to prevent interference with inter-appliance communication.

To synchronize the Imprivata database on both database appliances in a G4 enterprise:

  1. Open the Imprivata Appliance Console to the System page > Operations tab.

  2. Click Synchronize.
  3. Click OK on the dialog box to begin synchronizing.

During synchronization, the Imprivata Admin Console remains available on all appliances in a G4 enterprise. All appliances in the enterprise use the database on the appliance from which the operation was started. There is no service outage to Imprivata end-users.

The synchronization can take anywhere from 20 minutes to more than four hours. The duration depends mainly on the size of the Imprivata database, and particularly on the number of rows of audit log data in the database. The duration is also affected by the location of the two database appliances in a G4 enterprise, with respect to each other. In a G4 enterprise, if the data has not finished copying from the source database to the target database within five hours, the operation times out and the synchronization fails.