Application integration · Commvault

Commvault backups that can’t be ransomed.

Commvault writes backups to a Myota S3 object target over standard S3, with no changes to your storage policies or schedules. Every backup is encrypted and Shard and Spread™ across independent locations at write time, so immutability is a property of the data, not a setting on the library.

Talk to usThe use case

How the integration works

A cloud library that can’t be read

Point Commvault at the Myota S3 endpoint as a cloud storage library. Storage policies, schedules, and retention stay exactly as they are. Cortex monitors backup job health from the storage layer; it does not see inside the encrypted backup payload.

What it delivers

Protection that lives in the backup itself

Encrypted fragments

Every backup encrypted at write and spread across independent locations. No location holds reassemblable data.

Immutable, always recoverable

Reconstruct from any two of four locations, with no rehydration step.

No changes to Commvault

Myota presents as a standard object library. Policies and schedules are untouched.

Storage economy

A single sharded set at about 2x the protected data, against the stacked full copies of a replicated chain.