We have GFS enabled on a Windows based SOBR Capacity Tier extent, offloading to Azure. This has been working well, but we are migrating to the new Linux based hardened repository, and planning to use the SOBR capacity tier here.
My question is: how do we make sure that the GFS data won't all be re-offloaded to Azure from scratch? Is there a way to "remap" these jobs/backup files so that only the changes are offloaded?
Thanks in advance
-
- Veteran
- Posts: 323
- Liked: 25 times
- Joined: Jan 02, 2014 4:45 pm
- Contact:
-
- Veeam Software
- Posts: 540
- Liked: 193 times
- Joined: Mar 07, 2016 3:55 pm
- Full Name: Ronn Martin
- Contact:
Re: Capacity Tier - Moving from Windows to Linux SOBR
Unless I'm missing something you should be able to add the new Linux repo to the SOBR and then place the Windows SOBR extent into maintenance mode. If needed you can evacuate the Windows extent backups into the new Linux extent or just wait for them to age out...
-
- Veteran
- Posts: 323
- Liked: 25 times
- Joined: Jan 02, 2014 4:45 pm
- Contact:
Re: Capacity Tier - Moving from Windows to Linux SOBR
Thanks. And Veeam will still perform a comparison between what's on performance tier, and what's on Azure (capacity-tier), and only offload the differences to capacity tier based GFS settings?
-
- Veeam Software
- Posts: 540
- Liked: 193 times
- Joined: Mar 07, 2016 3:55 pm
- Full Name: Ronn Martin
- Contact:
Re: Capacity Tier - Moving from Windows to Linux SOBR
Correct since you're not creating a new SOBR / SOBR policy
Who is online
Users browsing this forum: No registered users and 8 guests