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.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.