-
Stokkolm
- Influencer
- Posts: 18
- Liked: 5 times
- Joined: Feb 11, 2016 11:11 pm
- Full Name: John Zetterman
- Contact:
Question about best practices to use GFS policies with Vault
From what I have gathered, there seems to be two ways to move data to Vault. I could set up a Scale Out Backup Repository and configure it to copy to Vault as a capacity tier (not an archive), but that doesn't allow me to set GFS retention. Secondarily, I can just use backup copy jobs where I can set GFS policies. Most of the documentation around best practices that I've found says that SOBR is preferred, but I've hit the GFS issue I described. Is my best/only option to simply just use backup copy jobs?
-
benthomas
- Veeam Software
- Posts: 88
- Liked: 28 times
- Joined: Apr 22, 2013 2:29 am
- Full Name: Ben Thomas
- Location: New Zealand
- Contact:
Re: Question about best practices to use GFS policies with Vault
are you wanting different GFS settings to what is on the orignail backup job?
Ben Thomas | Senior Solution Engineer @ Veeam | Veeam Vanguard 2023-2025 | VMCE | Microsoft MVP 2018-2024 | BCThomas.com
-
Stokkolm
- Influencer
- Posts: 18
- Liked: 5 times
- Joined: Feb 11, 2016 11:11 pm
- Full Name: John Zetterman
- Contact:
Re: Question about best practices to use GFS policies with Vault
I bought Vault with the intention of using GFS policies to ship data into Vault, so none of my jobs currently leverage them as I didn't have a place to put them before. There was good documentation around setting Vault up, but it's been tough to figure out how to actually leverage Vault once you have it configured in VBR. So that's really what I'm looking for guidance on.
Who is online
Users browsing this forum: No registered users and 1 guest