Hi Reza
Veeam doesn't provide an option to "sync configuration between two backups server". We have a configuration backup & restore option. Or you can use Veeam Replica jobs to sync the entire backup server (if it's a VM) to a secondary location.
In my understanding you have a backup server as a VM and the backups are in a virtual disk on the ESXi datastore as well?
Can you share the goal of "that syncs with the main Veeam server"?
- Disaster Recovery purpose?
- Testing restores?
- Redundancy?
- High availability?
Some challenges I see in your concept:
- backup data on a virtual disk in the vSphere datastore: In case you loose your ESXI hosts, backups can not be accessed until you install a new ESXi host, create a new VM and mount the virtual disks. Valuable time lost for the recovery. Also an attacker can just delete your backup server VM and all your backups are lost.
- No second backup copy: We recommend our customer the 3-2-1 rule (or 3-2-1-1-0). Which means, you should have 3 copies (1 production, 2x backups) of your data, 2 different medias and 1 backup offsite. I suggest you install a second backup repository in your second building for the second backup copy. Preferably a Hardened Repository which allows you to have immutable backups.
Best,
Fabian
Veeam doesn't provide an option to "sync configuration between two backups server". We have a configuration backup & restore option. Or you can use Veeam Replica jobs to sync the entire backup server (if it's a VM) to a secondary location.
In my understanding you have a backup server as a VM and the backups are in a virtual disk on the ESXi datastore as well?
Can you share the goal of "that syncs with the main Veeam server"?
- Disaster Recovery purpose?
- Testing restores?
- Redundancy?
- High availability?
Some challenges I see in your concept:
- backup data on a virtual disk in the vSphere datastore: In case you loose your ESXI hosts, backups can not be accessed until you install a new ESXi host, create a new VM and mount the virtual disks. Valuable time lost for the recovery. Also an attacker can just delete your backup server VM and all your backups are lost.
- No second backup copy: We recommend our customer the 3-2-1 rule (or 3-2-1-1-0). Which means, you should have 3 copies (1 production, 2x backups) of your data, 2 different medias and 1 backup offsite. I suggest you install a second backup repository in your second building for the second backup copy. Preferably a Hardened Repository which allows you to have immutable backups.
Best,
Fabian
Statistics: Posted by Mildur — Feb 12, 2024 8:33 am