On This Page
| Table of Contents |
|---|
Overview
Usage Overview
License Details
Enabled Options
...
| Note |
|---|
The License page is not applicable if you are running DryvIQ in a Kubernetes environment. |
Overview
The Licensing page allows you to review your license details, refresh your existing license, or add a new license through the DryvIQ Platform. This page provides information to help you understand how your license usage is calculated and how job runs affect the usage.
Understanding License Usage
The Licensing page displays the data under management, byte limit remaining and used, and the percent of the byte limit used. The “Volume used” is the analyzed bytes being counted towards the data under management and not the amount of content transferred. Again, DryvIQ does not calculate the limit based on the amount of content transferred; it calculates the limit based on the amount of content analyzed.
| Info |
|---|
DryvIQ uses standard base-2 conversion for transfer values. Any content that has been evaluated by DryvIQ counts towards the licensed byte Limit (data under management), even if it was not transferred to the destination. Simulation Jobs do not count towards the licensed byte limit until they are converted to jobs. |
Volume Used Calculations
Job runs affect the “Volume used” calculations as follows:
First Run (New Jobs), Duplicated Jobs, Recreated Jobs: For the initial job run, the “Volume used” increments by the size of the all items tracked in the following three statuses: Succeeded, Revised in Transfer, and Ignored.
If a folder is set to be ignored, none of the folder contents will be tracked or included in the “Volume used.”
Delta Job Runs and Job Resets: For subsequent job runs, the “Volume used” increments by the size of the new items tracked in the same three statuses as above or any changes to items from the succeeded or Revised in Transfer status.
“Volume used” increments by the full size of the changed item and NOT the difference in size due to the change.
Deleted Jobs: If a job is deleted, the “Volume used” remains unchanged and does not decrement.
Simulation Jobs: Simulation jobs do not count towards the “Volume used” until simulation is disabled and the job is run as a standard job (in normal mode).
Versions: When a job runs with versioning enabled, the “Volume used” increases for each version of a file managed by that job. This is important to understand since the job overview page only displays the item as a single item and doesn’t reflect its versions. If the job is set to only preserve the latest version, only the current version counts towards the “Volume used” since DryvIQ only evaluates the current version of the file. If changes are made to the file, the latest version will be analyzed and tracked due to the change and count towards the “Volume used.”
Permissions: If permissions change on a file but the file itself is not updated, DryvIQ doesn’t transfer the file; therefore, the file isn’t included in the “Volume used.”
Exceeded Byte Limits
Jobs will run provided the byte limit has not been reached.
If a job is running and the byte limit is reached during that job run, the job will finish the current run.
If a job attempts to start once the byte limit has been reached, the job will fail with a license warning.
License Expiration
Once a license expires, the application functions will no longer be available.
If attempting to use a license that has reached its activation limit, the license will not activate, and a warning message will display that the license cannot be used.
If the expired license is renewed, you must refresh the key on the DryvIQ Licensing page in Settings:
Click Settings and select Licensing.
Click on the Refresh link.
If the link is disabled (known issue), click Add new key and enter the renewed license. Click Activate, and the application will be updated with the renewed license and ready for use.