Search <book_title>...

Veritas™ Resiliency Platform 2.2 Solutions for VMware

Last Published: 2017-05-25

Product(s): Resiliency Platform & CloudMobility (2.2)

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	Resolution	Needs full sync?
Engine: Local UpdateSetIDs misaligned Error	Internal errors in the replication solution.	Perform a full synchronization.	Yes.
Engine: Target Disk not found Error	After reboot, the target disk is not found.	Check the target disk and attach it. Clear the admin wait and resume replication.	No.
Transceiver: ConsistencyGroup is in invalid replication state on target gateway Error	Replication is not started on the target gateway.	Start the replication on the target gateway.	No.
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).	Start the replication on the target gateway.	No.
Transceiver: ConsistencyGroup not found on remote gateway Error	The consistency group 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 takeover, 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.	Check `/var/log/messages` for any disk errors or file system errors. Check `vxgwaplrd` and `vxgwtxrxd` logs for any errors. 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.	Maybe.
Transceiver: Data Corruption Error	Replication data files are corrupted	If the files are corrupted, resolution will require fsck/check disk. Perform a full synchronization.	Yes.
Applier: Disk Error	Opening and reading the update set files has failed.	Check `/var/log/messages` to see if there are any errors for disk or file system errors. Check `vxgwaplrd` and `vxgwtxrxd` logs for any errors. 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.	Maybe.
Applier: Target Disk Error	Opening and writing on a target disk has failed	Check `/var/log/messages` to see if there are any errors for the target disk. 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 `/var/log/messages` for iSCSI errors. For network errors, full synchronization may not be needed. Login to Storage Proxy and check for tgtd status and errors.	Maybe.
Applier: Target Disk not found Error	The target disk is not found on the gateway	If the issue occurred during replication, check if the disk is attached to the cloud Replication Gateway. Also check OpenStack. If the issue occurred during Resycn operation, check that the disk is attached to the on-premises Replication Gateway. Also check iSCSI connection. Check `/var/log/messages` for any disk or virtio or virtblk or iSCSI errors. Check `vxgwaplrd` logs. 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.	Maybe.
Applier: Data Corruption Error	Replication data files are corrupted.	If the files are corrupted, the resolution requires fsck and check disk. Perform a full synchronization.	Yes.
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	Check `/var/log/messages` for any disk errors or file system errors. Check `/var/opt/VRTSitrpgw/log/vxgwiorecvd.log` log for `admin_wait_event` with a `message` value. For example, `"admin_wait_event": 2, "message": "Update set file write error."` Check whether the current update set is accessible. If the replication data directory is full, add a disk using the CLISH menu. For more information on CLISH menu, see the Deployment guide. 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.	Maybe.
IOReceiver: Data Corruption Error	Replication data files are corrupted.	If the files are corrupted, the resolution requires fsck and check disk. Perform a full synchronization.	Yes.