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
About network groups
Network group is a collection of similar type of network objects in a data center. Using Resiliency Platform console, you can create network groups of:
Subnets only, if your target data center is AWS
Port group/VLANs, if your data center is in VMware environment (It may be source data center or target data center or both)
Let us consider a scenario where there are some logical sub group of virtual machines in a resiliency group. Each sub group denotes one recovery domain so that even if virtual machines in one sub group becomes unavailable then virtual machines in other sub groups keep the application available. When you are recovering on AWS cloud data center, you may want the virtual machines in a resiliency group to be a part of different availability zones.
To do this, you need to set up the network pairing where the network objects on the source data center are logically paired with more than one network object in the AWS target data center. Since one network object in one data center cannot be directly paired with more than one network object in target data centers, you need to create network groups.
You can create network groups of VLANs or port groups if your source data center or target data center or both data centers are in VMware environment. These network group are created so that the virtual machines that are connected to different port groups can be migrated to single a network. All the port groups having the same name and ID should be grouped into one network group.
You are not allowed to create network groups if your data center is of Hyper-V virtual machines, Azure, vCloud Director, OpenStack or HUAWEI CLOUD.
Following is an example of how to use network groups.
The source data center is VMware vSphere and the target data center is AWS. All the virtual machines in the resiliency group on the source data center are connected to same subnet PremSN1. You want some of those virtual machines to be part of availability zone AZ1 connected to subnet AZ1_SN1 and other virtual machines to be part of availability zone AZ2 with subnet AZ2_SN1. You also have subnet AZ1_SN2 in AZ1, and subnet AZ2_SN2 in AZ2. These are to be used for rehearsal purposes.
Now perform the following tasks:
- Set purpose of PremSN1, AZ1_SN1 and AZ2_SN1 as Production.
- Set purpose of AZ1_SN2 and AZ2_SN2 as Rehearsal.
- Create a network group AZNG1 consisting of AZ1_SN1 and AZ2_SN1.
- Map the subnets AZ1_SN1 with AZ1_SN2, and AZ2_SN1 with AZ2_SN2.
- Pair subnet PremSN1 with the network group AZNG1
During the migrate operation, the virtual machines that become part of AZ1 are connected to subnet AZ1_SN1. The virtual machines that become part of AZ2 get connected to subnet AZ2_SN1. When performing rehearsals, the virtual machines that become part of AZ1 are connected to subnet AZ1_SN2 and the virtual machines that become part of AZ2 get connected to subnet AZ2_SN2.