Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On This Page

Table of Contents

Overview

Usage Overview

License Details

Enabled Options

...

Overview

The License page allows you to review your license details. This page provides information to help you understand how your license usage is calculated and how job runs affect the usage.

Usage Overview

This section displays what’s currently available for your license. In addition to identifying the number of activations used and the number of nodes online, this section helps you track how much of your license byte limit has been used. 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 Details

This section identifies information about the version of DryvIQ you are running as well as the expiration date for your license. 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. You will need to contact DryvIQ Customer Support for assistance.

Data Migrated

This section relates to the licensing for your migrations. It identifies the total byte limit for the license, how much of the limit has been used, and how much remains. The Volume used value is calculated based on the amount of data that is migrated.

  • First Run (New Jobs): For the initial job run, the “Volume used” increments by the size of the items migrated.

  • Delta Job Runs, Job Resets, Duplicated Jobs, and Recreated Job: The “Volume used” increments by the size of the new items migrated as part of that job run. For edited items, the increment will be the full size of the changed item(s) and NOT the difference in size due to the changes.

  • 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 moves the current version of the file. If changes are made to the file, the latest version will be migrated 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.”

Govern/Discover Data Under Management

This section relates to the licensing for Govern and/or Discover. It identifies the total byte limit for the license, how much of the limit has been used, and how much remains. The Volume used value is calculated based on the amount of data that is scanned.

First Scan: For the initial scan, the “Volume used” increments by the size of the data that is scanned,

Subsequent scans: For subsequent scans, the “Volume used” increments by the size of the new items tracked or by the size of items that need to be scanned again due to changes. “Volume used” increments by the full size of the changed item and NOT the difference in size due to the change.

Note that duplicating data sources can impact the “Volume used.” If you assign a single data source to multiple policies, DryvIQ will only count a file in that location once. However, if you create multiple data sources using the same location, DryvIQ will count the content again. For example,

  • If a file is scanned by one policy that uses a unique data source, the file is counted once.

  • If the file is scanned by two policies that use the same data source, the file is counted once.

  • If a file is scanned by two policies that use two separate data sources that use the same location, the file is counted twice.

Enabled Options

This sections allows you to view the options that have been enabled for your license. This section is for reference only.

Enabled Platforms

This section allows you to view which platforms are enabled for your license. This determines which connections you can create.