Application integration · Veeam
Myota is Veeam Ready Cyberstorage. Veeam Backup & Replication writes to a Veeam Ready Object certified Myota target over standard S3, with no changes to your jobs, schedules, or retention. 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 repository.
How the integration works
Veeam writes through load-balanced gateway servers to the Myota S3 endpoint. Existing jobs, schedules, and retention stay exactly as they are. Myota works with any Veeam Backup & Replication version that supports S3-compatible object storage repositories.
What Myota adds
Every backup is encrypted at write time and spread across independent locations. No single location holds reassemblable data.
→Reconstruct from any two of four locations, with no rehydration. Two can be lost or compromised and recovery still works.
→Immutability, key, and secret management run in a centralized system with least-privilege IAM and automated rotation.
→A single sharded set at about 2x the protected data, against the stacked full copies of a resilient chain: a third less than a three-copy 3-2-1, and half of a four-copy 3-2-1-1-0.
→Myota presents as a standard object target. Jobs, schedules, and retention are untouched.
→Reference architecture
One production datacenter, 1,000 VMs and 100 physical servers. Proxies in network mode, traffic encrypted end to end. The Myota cluster runs two-of-four: four locations, any two of which reconstruct the data. Thirty days primary and thirty days offsite retention, 10% daily change, an eight-hour window at 10 Gbps. Myota sizes to your environment, from a single site to many, on-premises or across clouds.
What you get
Flat writes with no penalty, faster at-scale reads, about an hour to restore a terabyte. Resiliency without redundancy.
Deployment
Point Veeam at a Myota S3 endpoint on Cortex Bundle (Myota-hosted target), or protect your existing Veeam repository with Cortex Software. Cortex monitors backup job health from the storage layer. Targets are any S3-compatible object storage: AWS S3, Azure Blob, Wasabi, Backblaze B2, NetApp StorageGRID, Dell ECS, Pure Storage FlashBlade, Cloudian HyperStore.
