Backing up a remote location

[Souko]

Hello

I have a VB&R server and a repository in my main office. We also have a remote location with its repository.

We have been backing up VMs from the remote office into their own repository, but managed by the VB&R server in the main office. I am noticing the backups take longer than the ones in the main office.

Is the backup data traveling from the VMs at the remote office to the VB&R server in the main office and back again to the repository in the remote office?

Should I install a second VB&R server in the remote office just for the VM jobs in that remote location?

I appreciate your help. Thank you.

[Mildur]

Hi Ricardo,

You haven't shared what kind of hypervisor you use for your VMs. But if it's VMware, then the case is almost clear.

Your backup server operates as a Backup Proxy to protect VMs from ESXi hosts. Data traffic will always flow this way:
- ESXi datastore → Backup Proxy → Backup Repository

Should I install a second VB&R server in the remote office just for the VM jobs in that remote location?

If we are talking about VMware, then you should deploy a new VM to the remote office ESXi host and configure your backup job to use only the proxy from the remote office. This way, you can keep a single backup server, and the backup traffic will remain within the remote office.

Best,
Fabian

[Souko]

Sorry about that, Fabian.

We are using Hyper-V as our hypervisor.