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
Resolving the Admin Wait state
During replication of a resiliency group, an issue may occur which requires manual intervention for a Veritas Replication Set on the Replication Gateway. For example, there may be disk corruption or a disk may not be accessible. Any of the replication services, including the I/O Receiver, the Transceiver, the Applier, or the Replication Engine, may detect an issue when sending, receiving, or applying an update. The operation fails, and the replication state of the Resiliency Group shows in the web console as Admin Intervention Required.
To debug further, determine the type of issue and which Veritas Replication Set is affected by logging into the Replication Gateway and performing step 1 in the procedure described below. A Veritas Replication Set consists of all the disks for a protected virtual machine.
After the issue is manually resolved, you must clear the Admin Wait state. On the Replication Gateway where the Veritas Replication Set has the Admin Wait state, use the following steps. This procedure assumes that the replication is from the production data center to the recovery data center. If the issue occurred during the prepare for failback operation, the replication direction is reversed.
To clear the Admin Wait state
- You can clear the admin wait from recovery site Gateway. Login to the recovery site Gateway as admin user. This will invoke the CLISH interface:
monitor> datamover repl-sets
The output of this command shows the VRS-ID of the Veritas Replication Set. It also displays a column for Admin Intervention, which shows the Admin Wait string indicating the type of error and the service that reported the error.
See Admin Wait state codes .
- After resolving the underlying issue, clear the Admin Wait state on the Replication Set from recovery site Gateway using the following command of CLISH:
manage> datamover operation clear-admin-wait
You need to enter the VRS-ID of the Veritas Replication Set.
You also have an option to specify if you want a full sync to clear the Admin Wait.
- Verify if the Admin Wait state has been resolved by using the following command of CLISH:
monitor> datamover repl-sets