Good afternoon all, not sure if this has been requested but I would like to ask if this is either on the roadmap for v8, or possibly a future release.
We have a project to retire an on-prem object storage cluster which requires migrating customer data to another object storage provider. For VBR this isn't an issue but for VB365, it turns out there is no supported way to move VB365 data from one OSR to another.
I found some unsupported-but-worked methods in other forums posts that leveraged rclone or other S3 file utilities. The copy was a success and rclone's check/comparison of source and destination came back happy, but I am currently working with support to understand why the restore points aren't showing up for this customer (case 07246796).
That said, are there any plans to formally add a method of copying VB365 restore points/data from one object storage provider to another?
-
- Service Provider
- Posts: 17
- Liked: 5 times
- Joined: Feb 02, 2022 2:24 pm
- Full Name: Adam Lion
- Contact:
-
- Product Manager
- Posts: 10316
- Liked: 2754 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Feature Request - OSR to OSR Migration for VB365
Hi Adam
Yes, it's on our roadmap. After version 8. But I cannot provide an ETA yet.
I'm glad to see that you have solved the missing restore points by a resync of the object storage repository.
Best,
Fabian
Yes, it's on our roadmap. After version 8. But I cannot provide an ETA yet.
I'm glad to see that you have solved the missing restore points by a resync of the object storage repository.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 17
- Liked: 5 times
- Joined: Feb 02, 2022 2:24 pm
- Full Name: Adam Lion
- Contact:
Re: [Feature Request] OSR to OSR Migration for VB365
Hi Fabian, thanks for the reply and update and that is certainly welcome news that it's on the roadmap. Understood that it is not coming in v8 but I am sure a lot of us will be happy to see that feature released.
Clearing out the PersistentCache folder on the proxy did the trick for this one, btw.
Clearing out the PersistentCache folder on the proxy did the trick for this one, btw.
Who is online
Users browsing this forum: No registered users and 763 guests