Running Veeam (VBR) server on a VM

[trackstar]

Hello,


Currently our backup is written to the local drive of a Windows server (on a Dell physical machine) and a copy job copies the backup to another local drive (iSCSI drive mount from AWS using storage gateway).

Our Dell machine needs to be replaced soon. Instead of buying another Dell machine, we are thinking of running VBR on a virtual machine. Then use the budget to buy something like Object First Appliance to give us that immutable storage. Of course the final destination of the backup data will be onto AWS.

Has anyone run VBR on a VM? Also, my understanding is a hardened Linux OS serves as "immutable" storage. Correct?

TT

[david.domask]

Hi trackstar,

Running Veeam Backup and Replication on a VM is pretty normal, just remember to plan for "all hosts down" emergencies, that is, how will your bring VBR back up if you lose all the hosts? That's the main concern, is how will you recover in a disaster. Having a stand-by machine that you can install Veeam to and restore the configuration database to should be enough to get your plan started.

As for your question on immutable storage, linux servers can be configured as Hardened Repositories, correct. Keep in mind however that for security purposes, a physical machine makes the most sense. (A hardened repository on a VM has a major flaw for immutability if an attacker can just delete the VM). I recommend set aside some time to read our Security Best Practices guide and understand our perspective and approach to security, it should help fuel discussions with your team on how you want to approach securing your backup environment further.

[trackstar]

Right on the emergency situation. Won't be putting the VBR on VM (where our main vCenter is). It will probably be on a standalone VMware host. We have a few standalone VMware hosts that are apart from our vCenter main cluster.

I was thinking the same regarding a harden Linux VM where it could be wiped or changed

[trackstar]

So on a Linux hardened, backup data written to the immutable storage still can be deleted per retention policy, right? Just making sure I understand the term.

[david.domask]

hi trackstar,

> backup data written to the immutable storage still can be deleted per retention policy, right?

This page describes how retention works with regards to immutable backups on Hardened Repositories.

An immutability retention overrides a job retention: if the job retention period is shorter than the immutability period, Veeam Backup & Replication does not delete backup files when the retention period is over, but only when the immutability period expires.

There are a few other nuances, but in short Veeam is aware of the retention and immutability of a given backup, and will remove the expired backups once both retention period and immutability period are completed.

[tyler.jurgens]

Right on the emergency situation. Won't be putting the VBR on VM (where our main vCenter is). It will probably be on a standalone VMware host. We have a few standalone VMware hosts that are apart from our vCenter main cluster.

I was thinking the same regarding a harden Linux VM where it could be wiped or changed

Don't forget to have it on separate storage as well. Also, if its in the same physical location - have a plan for recovery that allows you to get that VBR back up in case of a full site disaster (offsite configuration backup is a good start).