Cirrus Migrate Cloud Licensing and Subscriptions
This article describes the Cirrus Migrate Cloud licensing model for migration operations and explains how to use licenses.
Contact Sales for the Free Trial and other licensing inquiries including volume licenses and enterprise licenses. You can also send inquiries to info@cirrusdata.com
Cirrus Migrate Cloud typically licenses migration operations by the number of source hosts.
Once a host migration license is activated on a host with CMC installed, you can perform migration from the licensed host to either the same host (local migration) or another host (remote migration) for the next 60 consecutive days. If the licensed host requires more than 2TiB of migration, a separate add-on license will be needed.
This article describes the licensing terms and conditions in detail.
Licenses are consumable items that can be stored in a license key. The following types of licenses are used in this licensing scheme.
Host Migration License
When a migration session is created on a host (source) with CMC installed for the very first time, a Host Migration License is consumed from the project and added to the host. This license remains active for 60 days, and comes with 2TiB of Migration Capacity Quota.
See below for the definition and usage of Migration Capacity Quota.
Host Migration License Extension (30d)
When a Host Migration License has expired or is about to expire, a Host Migration License Extension (30d) license can be consumed to extend the host's license for 30 days from the previous expiration date.
Host Migration License Extension (60d)
When a Host Migration License has expired or is about to expire, a Host Migration License Extension (60d) license can be consumed to extend the host's license for 60 days from the previous expiration date.
Migration Capacity Quota Add-On (1T)
A Host Migration License comes with 2TiB of Migration Capacity Quota. Quota is deducted when migration sessions are created on that host (see below). A Migration Capacity Quota Add-On (1T) license can be consumed to increase the Migration Capacity Quota for 1TiB (1099511627776 bytes) from the previous remaining quota for that host.
When applicable, hosts will automatically consume extension licenses from the project's Project License Key for renewal and capacity add-on licenses for new migration sessions. See below for more details about License Renewals.
In addition to license types, the following licensing-related terminologies are commonly used.
Licenses
Licenses are consumable items that can be stored in a license key. When they are consumed as described above, they will be removed from your Project License Key.
Migration Capacity Quota
Migration Capacity Quota is the amount of migration can be created from a particular host. When a migration session is created, this quota amount equals the sum of all source volumes' block device sizes and will be deducted from the source host's Migration Capacity Quota.
Block Device Size is defined as the exact number of bytes the block storage device reports when inquired by the host operating system, regardless of the content (filesystem/application data/files) of the block device.
User License Key
Every Cirrus Data Cloud user has a User License Key that can be used to store licenses that they own. To go to your license key, click on your avatar at the top and select My License Key.
Licenses can be transferred between your user license key and any other project license key, provided that you are an admin of the project. See How to Transfer License Credits to Project? to learn more.
Project License Key
Every Cirrus Data Cloud project has a Projects License Key that can be used to store licenses that are assigned to a project. All hosts within a project will consume licenses directly from the Project License Key.
Licenses can be transferred from your user license key and any other project license key, provided that you are an admin of the project. See How to Transfer License Credits to Project? to learn more.
Unconsumed balances in a Project License Key can also be transferred back to your user license key, provided that you are an admin of the project. See How to Transfer License Credits Out of a Project? to learn more.
Note: Unconsumed balances refer to those licenses transferred to a project but not yet consumed by a host. Host Migration Licenses and other add-on licenses already consumed (activated) by a host cannot be returned to a Project License Key
This section describes the various license operations performed by Cirrus Migrate Cloud.
A Host Migration License is activated automatically when a migration session is created on the host for the very first time. During activation, a Host Migration License will be consumed from the Project License Key of the project to which the host is registered.
To reduce necessary human interaction particularly in scaled operations, Host Migration Licenses automatically renew and extend migration capacity quota when needed. During renewal, applicable licenses will automatically be consumed from the Project License Key of the project to which the host is registered.
When new migration sessions are created and the selected source volumes are larger than the remaining Migration Capacity Quota in the host migration license, Migration Capacity Quota Add-On (1T) licenses will be consumed automatically from the Project License Key to support the new migration session. This applies to the first session as well (session that activates the Host Migration License).
If the first session is larger than the included 2 TiB quota, additional add-on licenses will be consumed at the same time.
If Project License Key does not have sufficient add-on licenses, session creation will fail.
A Host Migration License expires 60 days after its original activation time.
On the day of expiration, at 00:00 UTC, for hosts that have active migration sessions, a renewal will automatically be attempted. A Host Migration License Extension (30d) license will be consumed from the Project License Key of the project which the host is registered to. If project license key does not have a sufficient license, use of a Host Migration License Extension (60d) will be attempted.
For hosts that do not have any active migration sessions, no renewal will be attempted.
License Automatic Renewal is ALWAYS ON to avoid service interruption. You (as admin of the project) will receive email alerts 7 days and 3 days before any auto-renew attempts.
A Host Migration License expires when its expiration time is reached and its project's Project License Key does not have sufficient extension licenses for auto renewal.
When a Host Migration License has expired, you will no longer be able to create new migration sessions on the expired host.
Existing sessions from the expired host will enter a Grace Period of no less than 21 days.
During the Grace Period, migration synchronization processes from active sessions will not be interrupted. However, the follow actions will be restricted:
Trigger Synchronization
Resume Session (after suspension)
Trigger cMotion
Trigger Final Cutover
Execute Migration Session Workflow Actions like Snapshots
Once the Grace Period expires, your active migration sessions may be subject to termination. Upon termination, your migration progress will be lost and you may also experience data loss if you have sessions that were in cMotion status when the Grace Period expired.
You (as admin of the project) will receive an email alert from Cirrus Data Cloud when a host migration license expires. If the migration session enters the Grace Period due to the presence of active migration sessions (host migration license expired and failed to renew), you will continue to receive email notifications** once every 24 hours.
You (as admin of the project) can delete an activated host migration license at any time, provided that there are no active migration sessions.
Once a host license is deleted, it will return to the same original state as when the host was initially registered to the project. No auto renewal will occur, and new migration sessions from the host will consume another Host Migration License instead of an extension license.
Cirrus Data Cloud supports the the following subscriptions:
Credit-based prepaid licensing requires various types of licenses (see above) to be purchased before migration can start. This is the default subscription for all users.
Prepaid licensing is similar to a prepaid phone card where migration licenses can be pre-purchased, consumed and refilled at any time. Licenses purchased will be delivered to your User License Key. Once you receive the licenses, you may transfer any of your project's project license key, provided that you are an admin of the project. See How to Transfer License Credits to Project? to learn more.
To learn more about purchasing license credits, see Purchasing Migration License Credits.
Subscription-based licensing allows users to subscribe to a licensing plan based on usage. Users with active subscriptions will be billed on a monthly basis according to the subscription plan.
Projects can be connected to an individual user's active subscription plan. Once connected, all license consumptions from all the hosts in that project will be metered and billed to the user's subscription, including migration sessions created by other authorized users in that project.
You can manage your subscriptions and current metered usage using our Self-service Customer Portal .
Subscription-based licensing is coming soon. More details will be available here.
#app-hint:license-key
Contact Sales for the Free Trial and other licensing inquiries including volume licenses and enterprise licenses. You can also send inquiries to info@cirrusdata.com
Licensing Model (Migration)
Cirrus Migrate Cloud typically licenses migration operations by the number of source hosts.
Once a host migration license is activated on a host with CMC installed, you can perform migration from the licensed host to either the same host (local migration) or another host (remote migration) for the next 60 consecutive days. If the licensed host requires more than 2TiB of migration, a separate add-on license will be needed.
This article describes the licensing terms and conditions in detail.
License Types
Licenses are consumable items that can be stored in a license key. The following types of licenses are used in this licensing scheme.
Host Migration License
When a migration session is created on a host (source) with CMC installed for the very first time, a Host Migration License is consumed from the project and added to the host. This license remains active for 60 days, and comes with 2TiB of Migration Capacity Quota.
See below for the definition and usage of Migration Capacity Quota.
Host Migration License Extension (30d)
When a Host Migration License has expired or is about to expire, a Host Migration License Extension (30d) license can be consumed to extend the host's license for 30 days from the previous expiration date.
Host Migration License Extension (60d)
When a Host Migration License has expired or is about to expire, a Host Migration License Extension (60d) license can be consumed to extend the host's license for 60 days from the previous expiration date.
Migration Capacity Quota Add-On (1T)
A Host Migration License comes with 2TiB of Migration Capacity Quota. Quota is deducted when migration sessions are created on that host (see below). A Migration Capacity Quota Add-On (1T) license can be consumed to increase the Migration Capacity Quota for 1TiB (1099511627776 bytes) from the previous remaining quota for that host.
When applicable, hosts will automatically consume extension licenses from the project's Project License Key for renewal and capacity add-on licenses for new migration sessions. See below for more details about License Renewals.
Terminology
In addition to license types, the following licensing-related terminologies are commonly used.
Licenses
Licenses are consumable items that can be stored in a license key. When they are consumed as described above, they will be removed from your Project License Key.
Migration Capacity Quota
Migration Capacity Quota is the amount of migration can be created from a particular host. When a migration session is created, this quota amount equals the sum of all source volumes' block device sizes and will be deducted from the source host's Migration Capacity Quota.
Block Device Size is defined as the exact number of bytes the block storage device reports when inquired by the host operating system, regardless of the content (filesystem/application data/files) of the block device.
User License Key
Every Cirrus Data Cloud user has a User License Key that can be used to store licenses that they own. To go to your license key, click on your avatar at the top and select My License Key.
Licenses can be transferred between your user license key and any other project license key, provided that you are an admin of the project. See How to Transfer License Credits to Project? to learn more.
Project License Key
Every Cirrus Data Cloud project has a Projects License Key that can be used to store licenses that are assigned to a project. All hosts within a project will consume licenses directly from the Project License Key.
Licenses can be transferred from your user license key and any other project license key, provided that you are an admin of the project. See How to Transfer License Credits to Project? to learn more.
Unconsumed balances in a Project License Key can also be transferred back to your user license key, provided that you are an admin of the project. See How to Transfer License Credits Out of a Project? to learn more.
Note: Unconsumed balances refer to those licenses transferred to a project but not yet consumed by a host. Host Migration Licenses and other add-on licenses already consumed (activated) by a host cannot be returned to a Project License Key
License Operations
This section describes the various license operations performed by Cirrus Migrate Cloud.
Activation
A Host Migration License is activated automatically when a migration session is created on the host for the very first time. During activation, a Host Migration License will be consumed from the Project License Key of the project to which the host is registered.
Automatic Renewal / Quota Extension
To reduce necessary human interaction particularly in scaled operations, Host Migration Licenses automatically renew and extend migration capacity quota when needed. During renewal, applicable licenses will automatically be consumed from the Project License Key of the project to which the host is registered.
Migration Capacity Quota Extension
When new migration sessions are created and the selected source volumes are larger than the remaining Migration Capacity Quota in the host migration license, Migration Capacity Quota Add-On (1T) licenses will be consumed automatically from the Project License Key to support the new migration session. This applies to the first session as well (session that activates the Host Migration License).
If the first session is larger than the included 2 TiB quota, additional add-on licenses will be consumed at the same time.
If Project License Key does not have sufficient add-on licenses, session creation will fail.
Host Migration License Renewal
A Host Migration License expires 60 days after its original activation time.
On the day of expiration, at 00:00 UTC, for hosts that have active migration sessions, a renewal will automatically be attempted. A Host Migration License Extension (30d) license will be consumed from the Project License Key of the project which the host is registered to. If project license key does not have a sufficient license, use of a Host Migration License Extension (60d) will be attempted.
For hosts that do not have any active migration sessions, no renewal will be attempted.
License Automatic Renewal is ALWAYS ON to avoid service interruption. You (as admin of the project) will receive email alerts 7 days and 3 days before any auto-renew attempts.
Expired Licenses
A Host Migration License expires when its expiration time is reached and its project's Project License Key does not have sufficient extension licenses for auto renewal.
When a Host Migration License has expired, you will no longer be able to create new migration sessions on the expired host.
Existing sessions from the expired host will enter a Grace Period of no less than 21 days.
During the Grace Period, migration synchronization processes from active sessions will not be interrupted. However, the follow actions will be restricted:
Trigger Synchronization
Resume Session (after suspension)
Trigger cMotion
Trigger Final Cutover
Execute Migration Session Workflow Actions like Snapshots
Once the Grace Period expires, your active migration sessions may be subject to termination. Upon termination, your migration progress will be lost and you may also experience data loss if you have sessions that were in cMotion status when the Grace Period expired.
You (as admin of the project) will receive an email alert from Cirrus Data Cloud when a host migration license expires. If the migration session enters the Grace Period due to the presence of active migration sessions (host migration license expired and failed to renew), you will continue to receive email notifications** once every 24 hours.
Deletion
You (as admin of the project) can delete an activated host migration license at any time, provided that there are no active migration sessions.
Once a host license is deleted, it will return to the same original state as when the host was initially registered to the project. No auto renewal will occur, and new migration sessions from the host will consume another Host Migration License instead of an extension license.
Subscriptions
Cirrus Data Cloud supports the the following subscriptions:
Prepaid (DEFAULT)
Credit-based prepaid licensing requires various types of licenses (see above) to be purchased before migration can start. This is the default subscription for all users.
Prepaid licensing is similar to a prepaid phone card where migration licenses can be pre-purchased, consumed and refilled at any time. Licenses purchased will be delivered to your User License Key. Once you receive the licenses, you may transfer any of your project's project license key, provided that you are an admin of the project. See How to Transfer License Credits to Project? to learn more.
To learn more about purchasing license credits, see Purchasing Migration License Credits.
Pay-As-You-Go (Coming Soon)
Subscription-based licensing allows users to subscribe to a licensing plan based on usage. Users with active subscriptions will be billed on a monthly basis according to the subscription plan.
Projects can be connected to an individual user's active subscription plan. Once connected, all license consumptions from all the hosts in that project will be metered and billed to the user's subscription, including migration sessions created by other authorized users in that project.
You can manage your subscriptions and current metered usage using our Self-service Customer Portal .
Additional Subscription Plans
Subscription-based licensing is coming soon. More details will be available here.
#app-hint:license-key
Updated on: 08/03/2023
Thank you!