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 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.
From 3.2 version, demo licenses will have limited meters available:
Per Core: 64
Per Virtual Machine: 10
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 4-meter types:
Table: Meter types can be used by following virtual machines:
Meter Type | Description |
---|---|
Per Core | Application on physical machine 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 | • Virtual machine (with 3rd party replication enabled and using Resiliency Platform Data Mover) • Applications on virtual machine • Virtual machine without adding Hypervisor |
InfoScale Per Core (Unix) | • InfoScale application on physical machine (Unix) |
InfoScale Per Core (x86) | • InfoScale application on physical machine (x86) |
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 3.4 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.