Admin Wait state codes
The resiliency group shows the Admin Wait state if an issue occurs during replication of a protected virtual machine. The resiliency group requires manual intervention to fix the issue before the replication can resume.
Table: Admin Wait state codes
Admin Wait string | Cause | Full sync? | Resolution |
|---|---|---|---|
Engine: Local UpdateSetIDs misaligned Error | Internal errors in the replication solution. | Yes. | Perform a full synchronization. |
Engine: Target Disk not found Error | After reboot, the target disk is not found. | No. | Check the target disk and attach it. Clear the admin wait and resume replication. |
Engine: API Gateway operation failed | HTTP Error in Communicating with AWS Data Gateway or unable to get datastream info from API Gateway | No. | Check if the credentials are correct or check if IAM role is properly set on the cloud Replication Gateway. |
Transceiver: ConsistencyGroup is in invalid replication state on target gateway Error | Replication is not started on the target gateway. | No. | Start the replication on the target gateway. |
Transceiver: Replication stopped on target gateway Error | Replication on the target gateway is stopped in the process of sending data from the source gateway (Internal error). | No. | Start the replication on the target gateway. |
Transceiver: ConsistencyGroup not found on remote gateway Error | Veritas Replication Set is not configured on the remote gateway. | Delete the resiliency group and create a new resiliency group. Configure DR for the new resiliency group. | |
Transceiver: Remote Gateway is not target gateway Error | After recover, when the source gateway comes back online, both gateways can have the source role. | Run abort CG procedure for the on-premises Replication Gateway. Or run prepare for failback whenever it is ready to reverse sync from cloud Replication Gateway to the on-premises Replication Gateway. | |
Transceiver: Disk Error | Opening and reading the update set files has failed. | Maybe. | Check Check Check whether the current update set is accessible. If the files cannot be restored even after manual intervention like mount/fsck/check disk, the disk must be replaced in the configuration and full synchronization is required. |
Transceiver: Data Corruption Error | Replication data files are corrupted | Yes. | If the files are corrupted, resolution will require fsck/check disk. Perform a full synchronization. |
Transceiver: Local Remote UpdateSetIDs misaligned error | Internal errors in the replication solution | Yes. | Perform a full synchronization. |
Transceiver: Error in compressing update set | Opening or reading the Update set files has failed or the repliation directory is full to store compressed Update set | No. | Check /var/log/messages for any disk errors or file system errors. Check /var/opt/VRTSitrpgw/log/vxgwpolicy.log log for admin_wait_event with a message value. Check whether the current update set is accessible. If the replication data directory is full, add a disk using the KLISH menu. See See Klish menu options for Replication Gateway. If the files cannot be restored even after manual intervention like mount/fsck/check disk, the disk must be replaced in the configuration. |
Applier: Disk Error | Opening and reading the update set files has failed. | Maybe. | Check Check Check whether the current update set is accessible. If the files cannot be restored even after manual intervention like mount/fsck/check disk, the disk must be replaced in the configuration and full synchronization is required. |
Applier: Target Disk Error | Opening and writing on a target disk has failed | Maybe. | Check If error cannot be resolved, the disk must be replaced in the configuration and full synchronization is required. If the issue occurred during Resycn operation, check the iSCSI connection, and check For network errors, full synchronization may not be needed. Login to Storage Proxy and check for tgtd status and errors. |
Applier: Target Disk not found Error | The target disk is not found on the gateway | Maybe. | If the issue occurred during replication, check if the disk is attached to the cloud Replication Gateway. If the issue occurred during Resycn operation, check that the disk is attached to the on-premises Replication Gateway. Also check iSCSI connection. Check Check If the disk was not attached, attach it and clear the admin wait flag. Full synchronization is not required if the update sets were not deleted. Otherwise, full synchronization is required. |
Applier: Data Corruption Error | Replication data files are corrupted. | Yes. | If the files are corrupted, the resolution requires fsck and check disk. Perform a full synchronization. |
Applier: Error in decompressing update set | Opening or reading the compressed update set files has failed or the replication directory is full to store uncompressed update set | Yes. | Check /var/log/messages for any disk errors or file system errors. Check /var/opt/VRTSitrpgw/log/vxgwpolicy.log log for admin_wait_event with a message value. Check whether the current compressed update set is accessible. If the replication data directory is full, add a disk using the KLISH menu. See See Klish menu options for Replication Gateway. If the files cannot be restored even after manual intervention like mount/fsck/check disk, the disk must be replaced in the configuration and full synchronization is required. |
IOReceiver: Disk Error | Opening or reading or writing the update set files has failed. Or the replication data directory is full. /var/opt/ VRTSitrpgw/ repldata | Maybe. | Check Check:
Check whether the current update set is accessible. If the replication data directory is full, add a disk using the KLISH menu. See Klish menu options for Replication Gateway. If the files cannot be restored even after manual intervention like mount/fsck/check disk, the disk must be replaced in the configuration and full synchronization is required. |
IOReceiver: Data Corruption Error | Replication data files are corrupted. | Yes. | If the files are corrupted, the resolution requires fsck and check disk. Perform a full synchronization. |
Engine: Sync End Marker not available | Target Replication Gateway unable to accommodate complete sync data caused by intermittent infra failures. | No | Simply resolving this admin-wait will resume replication. Replication Gateway data state will be inconsistent for some time till synchronization finishes. Moreover staging storage on the target Replication Gateway for this CG can be increased. |