Application integration · Rubrik
Rubrik archives to a Myota S3 object target over standard S3, with no changes to your SLA Domains or schedules. Every archive is encrypted and Shard and Spread™ across independent locations at write time, so immutability is a property of the data, not a policy on the archive.
How the integration works
Point Rubrik’s archival tier (CloudOut over the S3 API, with Object Lock) at the Myota S3 endpoint. SLA Domains, schedules, and retention stay exactly as they are. Cortex monitors archive job health from the storage layer; it does not see inside the encrypted backup payload.
What it delivers
Every archive encrypted at write and spread across independent locations. No location holds reassemblable data.
→Reconstruct from any two of four locations, with no rehydration step.
→Myota presents as a standard S3 archive target. SLA Domains and schedules are untouched.
→Myota holds a ransom-immune, multi-cloud archive; Rubrik recovers into an isolated recovery environment, so no single provider can deny recovery.
→
