VB365 Migration: S3 to S3 Without Duplicating 1.2PB (Metadata Questions) We’re planning a large-scale migration of Veeam Backup for Microsoft 365, moving the object repository from one S3 backend to another S3 backend (cluster to cluster). We’re talking about approximately 1.2PB of data.The challenge: we want to complete the migration without losing restore points / effective retention, and without duplicating the storage footprint during the retention period (duplicating 1.2PB is not an option).I’d like to ask the community:1️⃣ Has anyone performed an S3 → S3 migration of VB365 data at this scale? What approach worked for you (storage-level replication, incremental sync with aws s3 sync, rclone, endpoint switch, etc.)? What “gotchas” did you encounter (eventual consistency, versioning, object lock, throttling, API limits, lifecycle policies, etc.)? How did you validate that the backup chain / restore points remained intact? 2️⃣ Metadata / internal structure in S3 Does anyone have detailed knowledge of what metadata Veeam relies on when storing VB365 da
