Question Migrate Specific Backups From Microsoft Azure Blob to Wasabi

I am pretty sure Wasabi has some of their own tools for this purpose (never used them).  Also if you have Object Lock/Versioning turned on that complicates things with tools that can copy data as most do not copy versions causing issues and why you would need to use Veeam for the move.

I know S3Sync tool can do version copy but have not truly tested it.  We have done some migrations using rClone but ran in to this exact problem with those that have Versioning turned on.  😖

So from experience if you can get Veeam to move them that is the best route to go even with such a large data set.

Currently, immutability is not configured on Azure but will be activated on the new bucket. I don't know if there might be any implications.

The idea was to possibly copy the annual backups from Azure to Wasabi, for example, but I don't think it's possible to select only the annual backups - it's all or nothing.

Yes I believe it is all or nothing to be honest as Veeam will need all the chain information to allow access to the backups.

 Moving backups from a non-immutable repository to an immutable one is possible, there shouldn’t be any negative implications, as long as you use the move backup functionality in Veeam.

I don’t believe it’s possible to move over just the annual backups, unless you want to export those restore points to the new object repository. You’d lose the benefit of any block cloning if you exports those out one by one though.

It would be best to move the entire chain. Perhaps you could lower the short term retention and uncheck all GFS settings except the yearly points to clear up backups you don’t want moved.

Thanks ​@Tommy O'Shea .
Moving data through Veeam between two public clouds, I admit I'm a bit hesitant. I'm going to think about the idea of reducing retentions, which might be a solution.