# Multi-Tenant Backup

DevFeed: [Multi-Tenant Backup](<https://devfeed.tech/articles/multi-tenant-backup-77545.md>)

Original publisher: [Read original article](<https://www.verge.io/blog/protection/vergeos-multi-tenant-backup/>)

Author: George Crump

Published: 2026-09-02T12:35:24Z

Content type: article

Language: en

Sources: [VergeIO](<https://devfeed.tech/sources/vergeio.md>)

Topics: [tenant data protection](<https://devfeed.tech/topics/tenant-data-protection.md>), [Shared Responsibility Model](<https://devfeed.tech/topics/shared-responsibility-model.md>), [Software-Defined Data Center](<https://devfeed.tech/topics/software-defined-data-center.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [backup](<https://devfeed.tech/tags/backup.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [protection](<https://devfeed.tech/tags/protection.md>), [tenancy](<https://devfeed.tech/tags/tenancy.md>)

## AI overview

The article explains how VergeOS multi-tenant backup uses Virtual Data Center isolation boundaries. Each tenant is added to Veeam Backup & Replication as its own VergeOS Manager with a separate engine ID, so backup jobs, retention, reporting, and restores remain scoped to that tenant.

## Source excerpt

Most teams treat the Virtual Data Center as a cloud-provider feature, but enterprises carry the same tenancy problem under different names: production and development, a subsidiary, a regulated department. VergeOS enforces that boundary at the infrastructure layer, and Veeam inherits it, tenant by tenant, each one its own VergeOS Manager. The post Multi-Tenant Backup appeared first on VergeIO.