InfoArchive volume metrics and archived data exposure

InfoArchive volume metrics charge for the data you have placed under management, which makes archived data a direct source of audit exposure. The very purpose of the product, holding large volumes of retired information, is also where the finding grows fastest.

InfoArchive is OpenText's long term archiving and information retention platform, part of the OpenText content portfolio governed by the OpenText EULA. Unlike a seat based product, it is often measured on volume, which means the metric is tied to how much data the platform holds rather than to how many people use it. That changes the nature of the audit risk completely. Where a seat product inflates through miscounted people, a volume product inflates through how the data itself is measured, classified, and bounded. Understanding the volume metric is the whole game.

How InfoArchive volume metrics create exposure

When a product is licensed on volume, every gigabyte under management is potentially chargeable, and archives only grow. Organisations deploy InfoArchive precisely to retire and retain data they are obligated to keep, so the volume climbs steadily over the life of the deployment. If the measured volume drifts above the licensed entitlement, the gap becomes a finding, and because the data is retained for compliance reasons it cannot simply be deleted to close the gap.

The exposure is sharpened by the fact that the EULA places compliance on the licensee and gives OpenText the right to copy relevant records during an audit. The volume number the audit produces is therefore the starting point for the finding, and the way that number is calculated deserves close scrutiny. Volume metrics share the same structural risk as other capacity based measures, which is why it helps to read this alongside Content Server CPU and instance based metrics explained.

Where the volume count inflates

Compressed versus uncompressed measurement

InfoArchive stores data efficiently, and the volume that matters for licensing may be the managed data, not the raw footprint including every index, copy, and overhead structure. An audit can inflate the figure by measuring the total storage consumed rather than the licensable volume defined by the contract. The distinction can move the number substantially.

Replicas, backups and disaster recovery copies

Archives are replicated for resilience and copied for disaster recovery. Those copies are infrastructure, not additional licensable volume, yet a measurement that sweeps every storage location can count the same data several times. Separating the primary managed volume from its copies is a core reduction. The same principle applies to standby systems, which we cover in Documentum disaster recovery instances and licensing.

Retired applications still counted

InfoArchive is often used to retire legacy applications and hold their data. If an application has been fully retired and its data is held purely for retention, the way that volume is treated may differ from active, queryable archives. How retirement affects scope is a question in its own right, examined in InfoArchive application retirement and license scope.

Non production archives counted as production

Test, development, and staging archives may exist alongside the production archive. Whether and how non production volume is licensed depends on the entitlement, and counting non production data at production rates is a common overcharge.

Defending InfoArchive volume metrics under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. In that window we control the channel so that a raw storage measurement does not become the agreed licensable volume. For a volume product, the definition of what is being measured is the single most important thing to control from the start.

Reconstruct. We build the effective license position independently. We establish exactly what the contract defines as licensable volume, measure the genuine managed data against that definition, separate replicas, backups, and disaster recovery copies, scope non production archives, and account for retired applications. The reconstructed figure is what we defend, not the vendor's raw storage total.

Rebut. We challenge the measurement line by line. Copies and backups come out. Overhead and index structures are excluded where the contract measures managed data. Non production archives are treated on their own terms. Retired application data is scoped to its retention status. Each adjustment ties back to the entitlement definition.

Resolve. We settle on the corrected volume and, where it serves you, convert forward into an OpenPass agreement with a clearly defined volume metric, so a growing archive does not generate a fresh finding every renewal cycle.

An anonymised outcome

The financial logic of a volume finding is the same as any other. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost of the audit. An inflated volume figure therefore multiplies through all four. While our anonymised insurance engagement, case file E-01, centred on a Documentum seat count and fell from $7.2M to $1.6M, a 78 percent reduction, the underlying method is identical for volume: define the metric precisely, measure only what the contract actually licenses, and remove everything that does not belong in the count.

The discipline a volume metric demands

Archived data exposure feels different from a seat finding because there is no population to reconcile, only a number that grows on its own. That can make a volume finding feel inevitable, as though the only options are to pay or to delete data the organisation is obligated to keep. Neither is true. The volume metric is a contractual definition, and contractual definitions can be read, tested, and held to. The number an audit produces is a measurement made under assumptions, and those assumptions are exactly what a defense examines.

The practical work is forensic. It means establishing what the contract counts as licensable volume, then measuring the archive against that definition rather than against a storage administrator's view of total consumption. It means identifying every copy, replica, and backup and proving they are the same data, not new data. It means treating non production and retired application archives according to their actual status. Done carefully, this work frequently reveals that the genuine licensable volume is well below the figure the audit started with.

The buyer that understands its own volume metric before the audit measures for it holds the advantage. A finding built on raw storage totals is a weak claim, and the gap between that total and the defensible managed volume is where the reduction lives. The data does not have to be deleted, and the bill does not have to be paid as presented. It has to be measured correctly, and that is a question of evidence and contract reading, not of capacity.

Where to go next

For the full method behind an OpenText finding, read our complete OpenText audit defense playbook for 2026 and our ECM and Documentum audit defense track. To see how the volume question interacts with application retirement, read InfoArchive application retirement and license scope. If an InfoArchive finding has arrived and the volume figure looks inflated, open a case and we will measure the archive against what your contract actually licenses.