OPERATIONS
NAS, S3 & backups
Choose storage by its job: fast disk, shared files or durable object backups.
Use local SSD for active desktops first
Keep the guest's active disk on local SSD/NVMe during the pilot. It limits dependency on a central storage box and avoids routing every desktop I/O through a small shared network.
Add a NAS for shared files and local recovery
A NAS can store image backups, approved customer file shares and media projects. Give every tenant a separate authorized share and quota. Do not mount a global share inside every guest. RAID can tolerate some disk failures; it is not a backup against deletion, ransomware or losing the NAS itself.
Add S3-compatible object storage for off-site copies
Use object storage for encrypted backups, exports and optional customer artifacts. S3 is an object API, not additional RAM or a drop-in low-latency VM disk. Versioning, deletion markers and retention locks affect when data disappears. Account for transfer, request, retrieval and storage charges.
A practical first topology
Local SSD holds the active workspace. A local backup target holds quick recovery copies. A separate off-site object provider holds encrypted copies with a defined retention window. Keep encryption keys, backup credentials and the ability to delete backups away from the customer guest.
Deletion and restore
Track every backup and key version associated with a tenant. A valid deletion must not be reversed by restoring old metadata. Reapply deletion records and revoked credentials before reopening a restored service. Test restore speed using realistic datasets before promising a recovery time.