Product Documentation
- Section I. Overview and planning
- Introduction to Resiliency Platform
- About Resiliency Platform features and components
- Replication in a Resiliency Platform deployment
- About Veritas Resiliency Platform Data Mover
- Recovery options using Resiliency Platform
- Deployment checklist
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploying the virtual appliances in AWS through AWS Marketplace
- Deploying the virtual appliances in AWS using OVA files
- Deploying the Data Gateway in AWS
- Deploying the virtual appliances in Azure using PowerShell script
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in vCloud
- Deploying the virtual appliances in HUAWEI CLOUD
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Apply Updates
- About applying updates to Resiliency Platform
- Setting up the YUM server
- Deploy and configure
- Section III. Setting up and managing the resiliency domain
- Managing the resiliency domain
- Getting started with a new Resiliency Platform configuration
- Managing Resiliency Managers
- Managing Infrastructure Management Servers
- Managing on-premises data centers
- Managing cloud configurations
- Managing private cloud configurations
- Integrating with NetBackup
- Integrating with InfoScale Operations Manager
- Managing the resiliency domain
- Section IV. Adding the asset infrastructure
- Manage Resiliency Platform host assets
- Prerequisites for adding hosts
- Removing hosts
- Preparing host for replication
- Manage VMware assets
- Managing VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Prerequisites for adding VMware virtualization servers
- Managing VMware virtualization servers
- Manage Veritas Replication VIB
- Manage Hyper-V assets
- Manage Gateways
- About Replication Gateway pair
- Managing Data Gateway
- Manage enclosure assets
- Adding a discovery host
- Configuration prerequisites for adding storage enclosures to an IMS
- Adding storage enclosures
- Adding RecoverPoint appliance for replication
- Manage Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- About network objects
- Manage settings
- Managing user authentication and permissions
- Configuring authentication domains
- Managing user authentication and permissions
- Manage networks
- Section VI. Working with resiliency groups
- Organize assets
- Viewing resiliency group details
- Manage virtual business services
- Organize applications
- Managing custom applications
- Managing service objectives
- Organize assets
- Section VII. Configuring for disaster recovery
- Configure using Resiliency Platform Data Mover
- Managing virtual machines for remote recovery (DR) in Amazon Web Services
- Prerequisites for configuring VMware virtual machines for recovery to AWS
- AWS Customization options panel
- Managing virtual machines for remote recovery (DR) to Azure
- Managing virtual machines for remote recovery (DR) to OpenStack
- Managing virtual machines for remote recovery (DR) to HUAWEI CLOUD
- Managing virtual machines for remote recovery (DR) to Orange Recovery Engine
- Managing virtual machines for remote recovery (DR) in vCloud Director
- Managing virtual machines for remote recovery (DR) using Resiliency Platform Data Mover
- Managing physical machines for remote recovery (DR) using Resiliency Platform Data Mover
- Configure using NetBackup
- Configure using 3rd party replication technology
- Preparing VMware virtual machines for using array-based replication
- Preparing Hyper-V virtual machines for using array-based replication
- Managing virtual machines for remote recovery (DR) using 3rd party replication technology
- Managing applications for remote recovery (DR)
- Preparing VMware virtual machines for using array-based replication
- Configure using Resiliency Platform Data Mover
- Section VIII. Managing disaster recovery
- Perform DR operations for virtual machines
- Performing the rehearsal operation for virtual machines
- Perform DR operations on a VBS
- Perform DR operations for applications
- Evacuate assets
- Manage Resiliency Plans
- About custom script
- Perform DR operations for virtual machines
- Section IX. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Section X. Using Resiliency Platform APIs
- Section XI. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Resolving the Admin Wait state
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
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. |
Engine: API Gateway operation failed | HTTP Error in Communicating with AWS Data Gateway or unable to get datastream info from API Gateway | Check if the credentials are correct or check if IAM role is properly set on the cloud Replication Gateway. | 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 | 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 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 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. | 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. |
Transceiver: Local Remote UpdateSetIDs misaligned error | Internal errors in the replication solution | Perform a full synchronization. | Yes. |
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 | 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. | No. |
Applier: Disk Error | Opening and reading the update set files has failed. | 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. | Maybe. |
Applier: Target Disk Error | Opening and writing on a target disk has failed | 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. | 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 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. | 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. |
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 | 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. | 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 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. | 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. |