Yeah, that sounds like a good plan to have two copies local and one offsite to VCC. Also having the Linux Immutable is a good idea.
Hello @Massimiliano.Fontana ,
Good strategy, but be careful with the backup size x retention x %dedup.
Veeam has a calculator where you can check.
https://calculator.veeam.com/
I’d just make sure to utiliize fast clone storage technology → ReFS for Windows; XFS for Linux, where you’ll be keeping your backup data. I’d make sure to keep your Veeam Config DB data on a separate server than your VBR server in case, for whatever reason, you lose the storage on your VBR server & can ‘t recover your config DB data to restore your server on a new one. Lastly..I recommend adding at least 1 VM as a Proxy to occasionally offload some of the backup/copy processing from the VBR server to another (VM) server. Otherwise, not much else to add.
Hi @Massimiliano.Fontana -
I’m just following up on your backup strategy post. Did any of the comments provided help you with your strategy? If so, we ask you select which one best helped you as ‘Best Answer’ so others with a similar question may benefit.
If you do have further questions, don’t hesitate to ask.
Thank you.