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 Hitachi TrueCopy Universal Replicator
This section lists the pre-requisites to enable data replication using Hitachi TrueCopy/Universal Replicator when the hosts are part of a Microsoft failover cluster. For Hitachi TrueCopy/Universal Replicator based replication, all virtual machines consuming storage from a device group must belong to the same resiliency group.
Prerequisites:
Ensure that HORCM is installed on a host and the Hitachi TrueCopy/Universal Replicator device groups are already set up for replication between the primary and remote arrays.
Ensure that Hitachi Command Device is presented to the array control host. You can designate any host, including the Hyper-V Server, as the array control host.
Note:
The TrueCopy/HUR PVOLs & SVOLs must mapped to different hosts from different data centers.
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 (R1) 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. In order to share the virtual machine configurations between cluster nodes, make sure to have another CSV (non-replicated). The user must set default virtual machine location to point to the non replicated CSV.
Ensure that you have all the 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.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.
Veritas Resiliency Platform configurations:
Add Microsoft Windows 2012 R2 host using Add Hosts option under Infrastructure Management Server (IMS).
Add the array control host where the TrueCopy/HUR device groups are configured, to the each IMS using the Add Hosts operation.
Add HiCommand Device Manager using the Add Enclosure option. Provide the discovery host name.
Perform add host and add enclosure operations for the IMS at the disaster recovery data center as well.
This section lists the pre-requisites to enable data replication using Hitachi TrueCopy/Universal Replicator when the hosts are not part of a Microsoft failover cluster.
Prerequisites:
Ensure that Hitachi Command Device is presented to the array control host. You can designate any host, including the Hyper-V Server, as the array control host.
Note:
The replicated and primary LUNs must be mapped to different hosts from different data centers.
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 centre under the Hyper-V Manager and kept their data files (.vhdx) on the replicated volumes. Do not keep their configuration files (.xml) on any replicated drive. Also, make sure that the default virtual machine configuration location under Hyper-V Manager Settings is not on a replicated drive.
Ensure the respective remote disks (TC SVOL disk and ShadowImage SVOL) are in the offline state on the Hyper-V server at the DR data center. And also verify that no drive letter is assigned to the volumes present on these offline disks.
Note:
For the support of rehearse operation, you must add the snapshot devices to the DR data center's SRDF device group, and thereafter map them to the DR data center's Hyper-V hosts.
Once you have performed the necessary configurations, proceed with Resiliency Platform specific tasks.
Veritas Resiliency Platform configurations:
Add the host where the HTC/HUR device groups are configured, to the Infrastructure Management Server (IMS) using the Add Hosts operation.
Add HiCommand Device Manager using the Add Enclosure option. Provide the discovery host name.
Perform add host and add enclosure operations for IMS at the disaster recovery data center as well.
Limitations:
Logical grouping of disks (Windows Server Storage space storage pool) is not supported.