edh wrote: ↑Feb 20, 2025 6:56 pm
This is our experience—keep in mind that we all recognize that Blob is not S3 and that many S3 implementations are not alike.
We migrated a 200TB bucket from Wasabi to our Minio, and it worked correctly. The migration took a weekend because Wasabi limits the number of concurrent connections per access key. We achieved an incoming traffic of 14Gbps, limited by our backend.
To do this, we made sure that the bucket had the same name in both the source and destination to maintain the same paths at the Veeam Office 365 level. We used a migration tool that copies the object metadata and can handle hundres threads.
Obviously, while the data is being copied, you must remove it from the source VBO to ensure there is no activity.
Once all the objects have been copied, you create a new storage and perform a resync. When the first task finishes, you will see all the old points.
This method is not officially supported, so I recommend testing it with your own tenant and with just a few GBs.
Hi,
is there an update to the original feature request?
An official way would be very interesting for us, as we cannot scale our S3 systems infinitely and offload migrations to other data center areas are very likely.
@Polina
it would be nice if you could implement it without the need of a rescan like it is today. Migrating buckets is easy but the rescan of the new bucket (especially SP/Temas/OD) often takes a lot of time and let us miss SLA`s...
"On the roadmap" has been known to mean several years or never. We need to have a solution for this now. Flexify.io was suggested. Any other suggestions?