If you use something like Wasabi, there are ways within Wasabi to easily move data from one bucket to another etc. but if you are trying to move data from Azure to Wasabi, or AWS to Azure, or to move individual clients from one repository to another, options are a lot more limited. I'm doing one bucket/repo per job, and 3+ jobs per client, and this makes it a lot easier, but getting to this point (from previous implementation) was difficult. We have thousands of buckets to manage now, which creates its own challenges, but it's been the best solution so far.We really need a native mechanism to migrate data from one object repository to another. This capability is essential for rebalancing storage consumption across systems.
The main challenge with large datasets today is that backup jobs must be disabled to prevent new writes while data is being copied. Ideally, the migration utility you’re developing will support ongoing backups during the migration process so operations are not disrupted.
You'll see a lot of clients migrating data, with or without support because we won't have a choice. We can't wait years for you to develop a tool.
Statistics: Posted by pat_ren — Sep 23, 2025 2:08 am
