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
Configuring Hyper-V virtual machines for disaster recovery using HPE 3PAR Remote Copy
This section lists the prerequisites and limitations to enable data replication using HPE 3PAR Remote Copy when the hosts are part of a Microsoft failover cluster.
Prerequisites:
Ensure that the Infrastructure Managment Server (IMS) is able to communicate with 3PAR array using SSH.
Confirm that HPE 3PAR array user has edit or super role to perform HPE 3PAR Remote Copy operations.
Ensure that all the virtual machines consuming storage from a HPE 3PAR Remote Copy group belong to the same resiliency group.
Ensure that the HPE Remote Copy groups are set up for replication between the primary and the remote arrays. Ensure that the group names are unique across all data centers. Group name on the recover data center is auto generated by HPE. Do not modify the name.
Ensure to enable the Hyper-V and Failover Cluster roles on the Windows Server 2012 R2 hosts at the production and recovery (DR) data centers.
Ensure that you have created Microsoft failover cluster using the required nodes at the production and recovery data centers.
Ensure that you have created the cluster shared volume (CSV) on the replicated shared disk at the primary data center's Hyper-V Server.
Create virtual machines on the primary data center's Microsoft failover cluster with their data disks (.vhdx) on the replicated CSVs.
Ensure that you have all the Hyper-V integration services enabled for these virtual machines.
Ensure to create virtual machines in the Microsoft failover cluster at the production data center.
Ensure that the Hyper-V virtual network switch name that is used by the replicated virtual machines, is same across all the Hyper-V hosts.
Ensure that the virtual volume on the target data center is masked to the Hyper-V on the target data center.
Ensure to add all the Hyper-V servers of a cluster to Veritas Resiliency Platform.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.
Veritas Resiliency Platform configurations:
Add the 3PAR enclosure to the IMS using the Add enclosure operation.
Add Microsoft Windows 2012 R2 host using Add Hosts option under IMS.
Perform add host and add enclosure operations for the IMS at the recovery data center as well.
Limitations:
HPE 3PAR Remote Copy synchronous replication is not supported.
3PAR storage connectivity via iSCSI is not supported.
Having the same WWN for both source and target LUNs in a RemoteCopy replication pair is not supported for LUNs mapped to the Windows application hosts or Windows Hyper-V servers.
Having the same WWN as the target LUN assigned to the snapshot LUNs during rehearsals is not supported for Windows application hosts or Windows Hyper-V servers.
This section lists the prerequisites and limitations to enable data replication using HPE 3PAR Remote Copy when the hosts are not part of a Microsoft failover cluster.
Prerequisites:
Ensure that the IMS is able to communicate with 3PAR array using SSH.
Confirm that HPE 3PAR array user has edit or super role to perform HPE 3PAR Remote Copy operations.
Ensure that the HPE Remote Copy groups are set up for replication between the primary and remote arrays.
Ensure that you have created the volumes on the primary Hyper-V host where the LUNs are read/write enabled. Veritas Resiliency Platform supports only one volume per replicated disk. Veritas Resiliency Platform does not support Windows Storage Space Storage Pool.
Ensure that you have created virtual machines at the primary data center under the Hyper-V Manager and kept their data files (.vhdx) on the replicated volumes.
Ensure the respective remote disks are in the offline state on the Hyper-V server at the recovery data center. And also verify that no drive letter is assigned to the volumes present on these offline disks.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.
Veritas Resiliency Platform configurations:
Add the 3PAR enclosure to the IMS using the Add enclosure operation.
Perform add host and add enclosure operations for IMS at the recovery data center as well.
Limitations:
Logical grouping of disks (Windows Server Storage space storage pool) is not supported.
HPE 3PAR Remote Copy synchronous replication is not supported.
3PAR storage connectivity via iSCSI is not supported.