Question about best practices to use GFS policies with Vault

[Stokkolm]

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]

are you wanting different GFS settings to what is on the orignail backup job?

[Stokkolm]

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.

[benthomas]

@Stokkolm there are 2 paths to getting GFS backups to Vault.

1. Create a backup copy job that targets Vault and setup your GFS settings in there. This would be my recommended approach, as it gives maximum control over GFS settings, scheduling of copies, reporting and retries. I would highly recommend upgrading to VDP v13 before this as there are massive improvements for writing to Vault (And other Object Storage with immutability) in v13. https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
2. Enable GFS settings on your existing backup jobs (https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13), and create a SOBR from your existing Repository and add Vault as a Capacity Tier. You can then configure the SOBR as Move-only where older backups will be offloaded to Vault based on your configured period, or Copy and Move, so that backups are immediately copied to Vault as soon as they're created on the performance tier, and then the performance tier copy will be removed/offloaded after the configured interval. This is a simpler set and forget option compared to BCJ, but it doesn't yet include all the new object storage improvements that came in v13 for direct to object. https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

[Stokkolm]

Thank you very much, this is exactly what I was looking to determine. It sounds like in the future option 2 might be preferred, but right now option 1 is better. Managing two jobs per workload is a bit more work, but those benefits seem like they're worth it for now. Thank you so much!