Marcelo, I've merged your post into the corresponding discussion, you can find some considerations regarding Veeam B&R server replication above. It is a viable approach to protecting Veeam B&R, however, the best practice, as you've noted, is to backup Veeam B&R configuration.

I want to replicate my Veeam backup Server within my site. Reason is the following: We have two datacenters with a layer two connection between. All our VMware clusters are spread over these datacenters. Half of the ESXi Servers from a Cluster in site A and the other half in site B.
I plan to install a virtual veeam backup Server and different veeam proxy Servers. The veeam backup server should run on a single ESXi host in site A with local disks. The VMware vCenter Server also runs on this single ESXi host. What I want now, it to replicate both VM's to another single ESXi Server in site B. My question now is: is it possible to replicate the veeam backup Server in this manner with veeam replication? I want to be able to bring online vcenter Server and veeam backup Server as fast as possible if site A Fails. Reason to not run vcenter Server and veeam backup Server on a "normal" ESXi Cluster is because I want to be completely independent from any other infrastructure compontens like shared storage etc... for this two machines.

Definitely, it is possible. Some of the implications of replicating Veeam B&R backup server are discussed in this thread, as well as other ways of protecting it, among which backup of Veeam B&R configuration is the most commonly recommended approach.

Thanks for the fast answer. I now that backup of veeam B&R configuration is the common Approach. But then I have to install a new Server, install B&R and restore the config. I want to have a faster recovery solution, so I thougth about replicating the virtual machine. If I choose "Application Aware processing" for my replication Job for the B&R Server, do I have then a consistent backup of the b&R database or not (in V8)?
If in my Scenario Site A fails and I have to start the replicated B&R Server in site B. Am I able to start this Server in site B without having B&R running?

The fastest recovery solution would be to have Veeam B&R instance responsible for replication jobs in the target site. That will allow for automated failover/failback operations right from its UI.

sandsturm wrote:If I choose "Application Aware processing" for my replication Job for the B&R Server, do I have then a consistent backup of the b&R database or not (in V8)?

Veeam B&R database is automatically excluded from VSS processing, so replica will have database in crash-consistent state. However, even large dynamic SQL databases are typically ok with that and able to recover fine in 99% of cases.

sandsturm wrote:If in my Scenario Site A fails and I have to start the replicated B&R Server in site B. Am I able to start this Server in site B without having B&R running?

The idea with a Veeam B&R instance in the second datacenter sounds quite nice. Do I understand you right to do it the following manner:
- Function of Veeam B&R (Server A) in site A: Backup to local disk for Backups of vCenter Server and other Management Servers
- Function of Veeam B&R (Server B) in site B: Replicationjob configured for Server A with the replica metadata on a local Repository (Server B local)
- no backup of the Server A on Server A or do I need a local backup of this Server also?

Just wondering if it would be possible (or supported) to run Veeam Endpoint Backup on the Veeam Backup Server (running as a VM)?

At the moment we run the configuration backup, but just thinking if we had an endpoint backup of the machine (just stored on a NAS or other non-backup repository storage) it would make restoring the machine quicker than the current plan of installing os, updating os, configuring os, installing veeam, restoring veeam config.

Ryan,
Yes, you can backup virtual machines with Endpoint as well.
VBR also can backup/replicate itself. Though, please be aware that if this machine is also used as a default virtual proxy, CBT will not be utilized.
Thanks!

I'm sure this is discussed elsewhere, but I can't find it in the forums. We have VEEAM B&R running on a physical server. What is the best method to back this server up? We don't have any other backup programs. Do some use the free VEEAM backup endpoint tool? I know supposedly it's easy to reinstall VEEAM and reattach to the database, but believe me, it's not that easy and when you have a few other things on the server those are important to backup as well.

We just had a case where an HP update blue screened our VEEAM server and it really worried me.

The recommended way of protecting Veeam B&R is using its built-in configuration backup functionality. However, if the server runs some other workloads, you can also use Veeam Endpoint Backup to protect it.

Question: We do a configuration backup. We have a separarte sql server Problem: Several servers are indexed during backup (these files are saved locally through veeam) - how will I "restore" those in case of disaster if I am not directly backing up my Veeam B&R server as Veeam suggests?

Dont know if this has been mentioned before but hey ho (12 pages of posts to check ) but im my dev platform i simply backed up the Veeam virtual server as a separate task (self backup to the cloud connect) once all other backup tasks are completed to ensure that database is the most up to date for consistancy. This is not ideal as it takes up more space in the repository for each instance/customer but in a DR scenario you can bring the Veeam server back and then your good to go. Ideally an off-site copy would be best like cloud connect repo but a DR site would be just as good. This means the extra SQL maintenance plan management is not required and is easier to restore than rebuilding the setup and recovering the DB which of course there is a chance it does not come back properly.

Of course this only works if the SQL database and stores of the config files are local to itself and not on an independent share.

larimerE wrote:Question: We do a configuration backup. We have a separarte sql server Problem: Several servers are indexed during backup (these files are saved locally through veeam) - how will I "restore" those in case of disaster if I am not directly backing up my Veeam B&R server as Veeam suggests?

cffit wrote:Is there documentation on how to backup the VEEAM physical server with VEEAM Endpoint? Do I install the full VE on my VEEAM server?

Not sure that I understand what you mean by saying "full VE", but if you want to protect VBR server with Veeam Endpoint Backup, just install VEB and configure backup job to do full image backups. You can point your backup job to any supported designation target, for example a CIFS share.

cupplesey wrote:Dont know if this has been mentioned before but hey ho (12 pages of posts to check ) but im my dev platform i simply backed up the Veeam virtual server as a separate task (self backup to the cloud connect) once all other backup tasks are completed to ensure that database is the most up to date for consistancy. This is not ideal as it takes up more space in the repository for each instance/customer but in a DR scenario you can bring the Veeam server back and then your good to go. Ideally an off-site copy would be best like cloud connect repo but a DR site would be just as good. This means the extra SQL maintenance plan management is not required and is easier to restore than rebuilding the setup and recovering the DB which of course there is a chance it does not come back properly.

So just to be clear, it is supported to have both VEEAM B&R and VEEAM Endpoint Backup on the same server?

Yes, it is supported. From VEB's perspective VBR server is a "yet-another-mssql-machine" thus it can be backed up like any other one with no problem. As a sidenote: if you are interested in how Endpoint deals with mssql, then please take a look at this thread and this guide..

Is it possible with the same license to have the Veeam Backup server in SiteA, and a second Veeam server acting as the Replication server in SiteB so that it is immediately available in case of a SiteA disaster to orchestrate the startup of replicated SiteA's VMs in SiteB ?

Yes, as long as the number of sockets on the hosts you're backing up/replicating VMs from does not exceed the number specified in the license. Consider using Enterprise Manager to have visibility across both backup servers.