Backup and restore runtime requirements
You must prevent timeout failure by increasing the time interval that is allowed for backup and restore transactions for large key populations. Specify a larger value for the totalTranLifetimeTimeout setting in the server.xml file.
- Ensure that the task occurs during a time interval that allows a halt to key serving activity.
- For a backup task, the Guardium® Key Lifecycle Manager server must be running in a normal operational state. The IBM® Security Guardium Key Lifecycle Manager database instance must be available.
- For a restore task, the IBM Security Guardium Key Lifecycle Manager database
instance must be accessible through the IBM Security Guardium Key Lifecycle Manager data
Before you start a restore task, ensure that you have the password that was used when the backup file was created. Restored files must be written to the same Guardium Key Lifecycle Manager server from which the data was previously backed up. Alternatively, the restored files must be written to a replica computer.
- Ensure that the directories, which are associated with the tklm.backup.dir property exist. Also, ensure read and write access to these directories for the system and IBM Security Guardium Key Lifecycle Manager administrator accounts under which the Guardium Key Lifecycle Manager server and the Db2® server run.