best practices veeam backup and recovery installation

Gateway Servers can be physical or virtual, at the moment only Windows machines are supported as Gateways for deduplication appliances.

So for example you could have 2 pooled Gateway Servers for each VBR server, for access to the DD Storage Unit dedicated to that VBR server. Looking at your diagram, I would second suggestion: you can create different Storage Units / Mtrees (exposed via different interfaces / on different networks) and assign them to different Gateway Servers, each of them managed by a different VBR server. Starting from VBR v12, you can even pool them for added resiliency and performance (they are leveraged in a round-robin fashion). Not only for potential version mismatch issues… but for concurrency and resource management as well! Every VBR server will set their own number of concurrent tasks for the repo… but of course it will not be “aware” of other tasks assigned to the repo by the other VBR servers! You could easily end up overloading the shared repo. This is why, if you need to use the same storage, I’d at least have a separate folder for each repo and have three separate repo’s independently of each other.Īnd as previously, noted, Enterprise Manager will make this easier and may be required depending on how your servers are licensed.Īs already mentioned by basically everyone on this thread 😁 I definitely would not recommend having multiple VBR servers share an infrastructure component (in this case, a repository). I did have an environment where I had two different versions of VBR going to the same repo for a bit, the older VBR existed because an older version of Veeam Agent for Windows was using the repo and we couldn’t easily upgrade at the time. I can’t imagine if the entire repo is encrypted what kind of havoc that could create - might be okay, might not be, but I wouldn’t want to find out in production. I can’t speak for what Chris is talking about regarding repo’s being upgraded and inaccessible to not-yet-upgraded VBR server’s, but it generally seems like a bad idea. While that might be handy for restoring a VM from a different VBR server at one location to a different location (strange use case, but the only advantage I can come up with) and it can be confusing for sure.

If you use the same repo for all servers, note that all servers will see each others backups as imported/foreign objects (or encrypted objects if your backups are encrypted) because it has no information about those restore points in it’s own database but it will see those restore points in the repo. My recommendation would be that you create 3 separate folders on your backing storage, one for each repo, one repo for each server. But a very slight change might work for you.

Best practices veeam backup and recovery installation