Migrate to a another object storage repo

[Bjoern]

Hi there,

we have some Azure Blob Container which we use to extend our vbo365 repos with.
I want to migrate one of those repos.
Found this KB article: https://www.veeam.com/kb3067
Does this mean i cannot migrate data from an Object Storage repository to another?

Best regards,
Bjoern

[Mildur]

Yes, you can't use Move-VBOEntityData to migrate between object storages.

I would try to clone the Blob Container (with Microsoft or Third Party Tools), add it to the VBO Server and change the backup job to use the new Blob Container. If you can take incremental backups and restores to and from the new location, then I think, everything is fine. But it could be unsupported.
I am not sure, if that works. You should test it. I cannot test the behaviour because I don't have an lab environment for that.

[Bjoern]

thx Mildur.
Forget to mention that the migration target is not azure but wasabi. Well, i will set up a test szeanrio tommorow, try to copy the data to wasabi and then test if it works.
If migration to a different object repo (in a different cloud) is not supported, then from my point of view it looks like a vendor lock now.

[Mildur]

I am not sure, that this will work. Azure and Wasabi are different types of object storages.

[Bjoern]

Test was successful.
Just copied the azure blob container to a wasabi bucket. Then i added the wasabi bucket to vbo365 as a new Object Repository.
When i tried to add the backup repository an error ocurred during repository rescan: The object storage repository is already in use by another repository on the same backup proxy.
So i removed the "old" backup repository which is extended with azure blob repository and tried again with success.
Created a new job which then ran as "Full". But this was actually just a "Full Rescan". Transferred data was of incremental size.
After that i was able to restore data from all restore points.
Actually there is no need to migrate backups right now, i just wanted to have an exit strategy in place. Just in case
But i prefer if this would work with Move-VBOEntityData. Would be much easier.

[Mildur]

Thanks for the feedback and the testing

[HannesK]

Hello,
Looks like it's similar like with VBR backups: that kind of migration works, but not officially documented / supported.

Note: The old backup repository should always be disconnected before the copy process is started. Otherwise the data becomes inconsistent during migration.

Just for curiosity: how did you do the copy? I did some tests around that and it's hard to copy (hundreds of) millions of objects between cloud providers. There are some object storage migration offerings where you can pay per TB that claim that they can scale, but I did not find a standalone software that can do that kind of migration with good performance.

Best regards,
Hannes

[Bjoern]

I used Flexifiy.io for the copy, but the (test-)repo was just 4.6 GB. Performance was ok(54sec).
But this was my first cloud to cloud migration, so i´m not an expert
Here are some recommendations by wasabi for cloud-to-cloud migration: https://wasabi-support.zendesk.com/hc/e ... recommend-

[HannesK]

ah, I cannot remember flexify.io was on the list when I checked it. thanks!

yes, that's around 700Mbit/s for your migration. Probably they can do it faster with more data. Otherwise migrating a significant amount of TB would become hard

[paul.timson]

Hi, Just for completeness, we are a CSP and we use our on premises S3 but I believe the same procedures would apply.

We moved to ZADARA to provide our S3 because of the immutability we wanted and our existing platform only had it on the 'roadmap'.

We used 'rclone' to perform the migration from S3 buckets and it worked fine. Our platform team did all the work so I'm not sure on the performance but it works. You do need to ensure you have documented procedures of course, because you need to stop offloads whilst the migration is done, so depending upon the size of buckets it can take time and your Tier 1 (performance) will need expanding to cope during this time. With pay as you go at least you can expand the capacity temporarily whilst you do.

We would prefer this to be something VEEAM build into the product as using 3rd party (not necessarily supported) tools isn't ideal. I'm sure there are VEEAM guys working on it but the sooner it comes I think it will help lots of people, especially with the growth of data and the use of object.

[nish]

Hi All,
Thanks to Bjoern for the solution!
I've just finished the move 16TB of O365 backups from Azure Blob to Wasabi following his advise.
I used rclone to copy the data.

[sumeet]

Hi Nikola,
Congratulations on your successful repo migration.
Can you please help with duration of moving 16 TB repository?

Thanks,
-Sumeet.

[infused]

Hi Guys.

Does anyone have a solution for migrating between blob storage between different MSPs? Like a script to transfer, or even if this is possible?

Looking to the future where this is going to become quite an issue.

[Mildur]

Hi Hayden

Please see the answers in this topic. And Wasabi has listed some cloud to cloud migration tools for object storage data.
Unfortunately our product currently doesn't officially support such migration, but the migration was done successfully by other customers.

Official support may change with a future version. We know that it is important to have such functionality. But no ETA yet.

Best,
Fabian

[infused]

Thanks for the update.

[Matt.Sharpe]

Hi Guys,

Wondering if anyone has or knows of anyone successfully migrating object to object storage for 365? I know the provided scripts don't support this...

I imagine it would involve a 3rd party S3 browser of some kind, but wondering if anyone has done this?

[Mildur]

Hi Matt

I moved your request. Please the previous comments in this topic.
It works, but we cannot provide support in case something goes wrong.

May I know source and target object storage you plan to migrate?

Best,
Fabian