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
Prerequisites for configuring Hyper-V virtual machines for recovery to vCloud Director
Before you run the wizard to configure disaster recovery protection for a resiliency group of Hyper-V virtual machines, ensure that you have met the following prerequisites for virtual machine configuration:
If you add new disks, ensure that they are visible from the guest operating system.
Ensure that the Hyper-V integrations services are installed and running inside the virtual machines.
If you want to do IP customization, ensure that the virtual machines are updated with the latest Hyper-V integration services.
Ensure that you have disabled the 'Quick removal' policy for disks in Windows Server 2008 R2 and disabled the 'write-cache' policy for disks in Windows Server 2012 R2.
When protecting Hyper-V virtual machines that use Dynamic Memory, ensure that the Maximum RAM value is set to a reasonable value. This value is used to assign the memory size to the virtual machines on the target (recovery) site. If Maximum RAM is set to a very high value then while configuring the resiliency group for remote recovery, the operation may fail.
Both the source and recovery (target) gateway must have external storage equivalent to 12GB for each virtual machine protected by the gateway pair. For example, if a gateway pair supports 10 virtual machines, the source and recovery (target) gateway must each have 120GB of external storage.
A maximum of 58 volumes or disks can be attached to the Replication Gateway on on-premises where as up to 45 disks can be attached to the Replication Gateway on vCloud Director. The total number of disks from the virtual machines in the resiliency group and the number of disks that are already attached to the gateway should not exceed this number. This is a VMware limitation.
If the status of the virtual machine on the recovery data center is not correctly displayed, then you need to refresh the cloud discovery or the virtualization server discovery.
Ensure that correct values are defined for all the following settings in the Network Specification tab on the vCloud Director Web console for the vCloud network to which the virtual machines will connect to.
Gateway address
Network mask
Primary and Secondary DNS
DNS suffix
If one or more of these values are not defined, then after performing the migrate or takeover operation, the virtual machines may not get attached to the Infrastructure Management Server (IMS) in vCloud Director. Subsequently you cannot migrate back to production data center.
A Windows host is already added to resiliency domain using 'Prepare Host for Replication' operation. If you now add a non-initialized data disk to the host on IDE controller, you need to initialize the disk, reboot the host and refresh Hyper-V server before you can protect the host for DR.
If you want to migrate the virtual machines on some specific datastores in vCloud, then you need to create a storage policy. If you do not create a storage policy, the virtual machines are migrated to any of the available datastores.
Provision a SCSI disk of size 1 GB to be used for Replication block tracking. IDE disk is not supported.
The virtual machine needs to have its boot order changed, so that Network boot comes before Boot from disk. This is done by accessing BIOS settings from the virtual machine console when the virtual machine is booting up. This needs to be done only once; after preparing the host for replication or before creating a resiliency group. Ensure that it is done before running the Migrate operation.
Ensure that legacy network adapter is added and is first in the boot order. Ensure that it is done before running the Migrate operation.
Additional legacy network adapter must be attached to each virtual machine that is to be protected. The legacy network adapter must have a static IP whose subnet mapping is done.