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
- About Elastic Networking Adapter (ENA) support in Resiliency Platform
- Recovery to cloud data center
- Recovering virtual machines to AWS
- Recovering virtual machines to Azure
- Recovering virtual machines to Google Cloud Platform
- Recovering virtual machines to vCloud Director
- Recovering virtual machines to Orange Recovery Engine
- Recovering physical machines using Resiliency Platform
- Recovery to on-premises data center
- Deployment checklist
- Checklist for recovery of virtual machines to AWS
- Checklist for recovery of virtual machines to Azure
- Checklist for recovery of virtual machines to Orange Recovery Engine
- Checklist for recovery of virtual machines to Google Cloud Platform
- Checklist for recovery of virtual machines to vCloud Director
- Checklist for recovery to on-premises data center using Resiliency Platform Data Mover
- Checklist for recovery of virtual machines using NetBackup
- Checklist for recovery of virtual machines using third-party replication technology
- Checklist for recovery of application using third-party replication technology
- Checklist for recovery of virtual machines to AWS
- System requirements
- Manage licenses
- Using the Web Console
- Introduction to Resiliency Platform
- Section II. Deploying and configuring the virtual appliances
- Deploy and configure
- Deploy and download the Resiliency Platform virtual appliances
- About deploying the Resiliency Platform virtual appliances
- Downloading the Veritas Resiliency Platform virtual appliances
- Deploying virtual appliances in AWS
- Deploying virtual appliances in Azure
- Deploying virtual appliances in Google Cloud Platform
- Deploying the virtual appliances in Google Cloud Platform using OVA files
- Prerequisites for deploying the virtual appliances in Google Cloud Platform
- Deploying the virtual appliances in Google Cloud Platform using OVA files
- Deploying virtual appliances in vCloud Director
- Deploying the virtual appliances in Orange Recovery Engine
- About configuring the Resiliency Platform components
- Virtual appliance security features
- About hotfixes
- Deploy and download the Resiliency Platform virtual appliances
- Depoly virtual appliances through Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Prerequisites for deploying the virtual appliances in AWS
- Deploying the virtual appliances in Azure through Azure Marketplace
- Deploying the virtual appliances in AWS through AWS Marketplace
- Apply Updates
- About applying updates to Resiliency Platform
- Step 1: Prepare for upgrade
- Step 2: Upgrading the Resiliency Platform (Detach / attach the disk)
- About applying updates to Resiliency Platform
- 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
- Recovering virtual machines to premises target data center
- Recovering virtual machines to cloud target data center
- Support for NetBackup Cloud Recovery Server configured with Veritas Alta Recovery Vault as storage account
- Integrating with InfoScale clusters
- Prerequisites for supporting InfoScale cluster node in Veritas Resiliency Platform
- Configuring InfoScale clusters in Resiliency Platform
- Managing the custom application or replication type in Resiliency Platform
- 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 NetBackup primary pairing
- Manage Recovery Readiness Bundle
- Manage Resiliency Platform host assets
- Section V. Managing networks
- Manage networks
- Managing network objects in Resiliency Platform
- Network objects in Resiliency Platform
- DNS server configuration settings
- Managing network pairs
- Mapping network objects (Production and Rehearsal mapping)
- Manage networks
- Section VI. Managing settings
- Manage settings
- Managing settings for alerts and notifications and miscellaneous product settings
- Throttling the notifications
- Managing user authentication and permissions
- Configuring authentication domains
- Managing settings for alerts and notifications and miscellaneous product settings
- Manage settings
- Section VII. Working with resiliency groups
- Organize assets
- Editing a resiliency group
- Deleting a resiliency group
- Viewing resiliency group details
- Manage virtual business services
- About virtual business services
- Organize applications
- Managing service objectives
- Organize assets
- Section VIII. 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) from AWS region to AWS region
- Managing virtual machines for remote recovery (DR) to Azure
- Managing virtual machines for remote recovery (DR) from Azure to Azure
- 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) to Google Cloud Platform
- 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
- Managing the virtual machines for recovery to Azure using NetBackup MSDP-C.
- 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 IX. Managing disaster recovery
- Perform DR operations for virtual machines
- About Rehearse operation
- Performing the rehearsal operation for virtual machines
- Performing the recover operation for resiliency group
- Recovering virtual machines with multiple recovery points
- About Rehearse operation
- 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 X. Managing certificates
- Section XI. Product settings
- View activities
- Manage reports
- View logs
- Manage Risk Notifications
- Managing settings for alerts and notifications and miscellaneous product settings
- Throttling the notifications
- Section XII. Using Resiliency Platform APIs
- Section XIII. Troubleshooting and Using command line interface
- Troubleshoot
- Recovery of Resiliency Platform components from disaster scenarios
- Troubleshooting: NetBackup issues
- Resolving the Admin Wait state
- Troubleshooting: IP customization
- Use klish menu
- Use Application Enablement SDK
- Troubleshoot
About licenses
To create and protect resiliency groups using virtual machines or applications, you need to install a subscription license of Veritas Resiliency Platform. Each resiliency group is associated with a license subscription. The license is provided for a predefined number of meters for a set duration of time.
When a resiliency group is configured for the first time, a demo license is made available for 60 days with limited meter counts, letting you evaluate the Resiliency Platform. This demo license is installed and activated automatically when you configure the resiliency group for recovery in Resiliency Platform.
Demo licenses have limited meters available as mentioned below:
Veritas Resiliency Platform FETB (Per-FETB)
Veritas Resiliency Platform Compute (Per-Core)
Veritas Resiliency Platform Compute (Per-VM)
Veritas Resiliency Platform Compute Infoscale per core (x86)
Veritas Resiliency Platform Compute Infoscale per core (unix)
After the demo license is expired, it is replaced automatically with the new subscription license available in the data center. This will happen when the nightly schedule scan which is triggered daily. This scan will check for the expired licenses which are consumed. If the licenses are consumed, then it searches for any valid licenses with sufficient meter count and meter type and replace automatically.
You can also replace the license using
option. This option will allow you to manually replace any consumed valid license with same meter with a valid license available with sufficient meter count.You will have to buy a new subscription license to continue if you do not have unused subscription license.
You cannot add more assets to resiliency group after the expiration date is lapsed, but you can perform disaster recovery operations on that resiliency group. No separate license is required for monitoring the assets.
Demo and subscription license are available with below meter types:
Table: Meter types with its description:
Meter Type | Description |
---|---|
Per Front-End Terabyte | Resiliency group is created using virtual machines or applications. While protecting Virtual Machine, size of the disks attached to virtual machine would be considered for consumption against FETB irrespective of the disk type like thin or thick. While protecting application, the application size discovered by Veritas Resiliency Platform would be used to calculate the consumption of FETB. |
Per Core | Resiliency group is created using applications that are deployed on the physical hosts and no Per-FETB license is available. If there are multiple resiliency groups configured with different applications that are hosted on a single physical server, then total consumption of Per Core license equals to number of cores of respective physical machine. |
Per Virtual Machine | Resiliency group is created using virtual machines or applications that are deployed on the virtual machines and no Per-FETB license is available.
|
InfoScale Per Core (x86) |
|
InfoScale Per Core (Unix) |
|
After the expiration date is lapsed there is a grace period of 30 days for that license. When you are nearing the expiration date, you will receive daily notifications from the license service, 30 days prior to the license expiry date. After the end date is lapsed, you can either purchase a new license or replace the existing expired license with a new valid license if available.
After the grace period is lapsed, you cannot modify the resiliency groups by adding virtual machine that are associated with the license. Neither can you create new resiliency groups using an expired license. But existing resiliency group will be fully functional even after the grace period is over. You can remove the virtual machines from the resiliency group even after the grace period is over.
Resiliency Platform 10.3 supports one to one mapping of license subscription with a resiliency group; which means each resiliency group is associated with a license. You can create multiple resiliency groups using one license but you cannot use multiple licenses for a resiliency group. If a resiliency group is created using a subscription license, and if you delete the resiliency group, then the meters of that license are released and added back into the license.
Let us take an example. There are two licenses: LIC_1 and LIC_2 of Per Virtual Machine meter-type. Number of meters in the license file are 60 and 100 respectively.
Create a resiliency group with 20 virtual machines using LIC_1 license. The consumed quantity of LIC_1 will be 20.
Now, if you want to create a new resiliency group with 60 virtual machines using the LIC_1 license, then create resiliency group operation fails as there are no sufficient meters left in the license. So, either add more meters to the LIC_1 by renewing it or create the resiliency group with LIC_2 license.
See Managing licenses.