Failure to Suspend or Resume LDT Operation

LDT-ALERT: Failed to suspend rekey on GuardPoint [GuardPoint]

Solution: An I/O error is the most common cause of failure when updating the persistent state of a GuardPoint. For I/O errors, you must fix the problem at the host OS or storage level.

The appropriate corrective action depends on when this problem occurs and the reason for the suspension. If the suspend request was at the host level as part of a QoS schedule, or it was initiated by a user on the CipherTrust Manager, the failure occurred at the host level rather than the specified GuardPoint.

Otherwise, the source is probably the initiation of a suspension on a specific GuardPoint before backup. If the backup operation is in progress when this alert message occurs, you must fix the cause of the suspension failure and then restart the backup. If the backup has already completed when the alert message occurs, the backup image on the GuardPoint may have inconsistent data and LDT metadata. Discard this backup image and do a fresh backup.

If you cannot find and fix the host OS or storage issue, contact Thales Support for troubleshooting and recovery.

LDT-ALERT: Failed to resume rekey on GuardPoint [GuardPoint]

LDT-ALERT: Failed to resume rekey on all GuardPoints

Solution: An I/O error is the most common cause of failure when updating persistent state of a GuardPoint. For I/O errors, you must fix the problem at the host OS or storage level.

The appropriate corrective action depends on when this problem occurs and the source of the problem. If the resume request was at the host level as part of a QoS schedule, or the resume request was initiated by a user on the CipherTrust Manager, the failure occurred at the host level rather than the specified GuardPoint.

Otherwise, the source is probably initiation of a resume operation on a specific GuardPoint after a backup is completed.

If you cannot find and fix the host OS or storage issue, contact Thales Support for troubleshooting and recovery.