Veeam server on virtual machine

[trackstar]

Hello,

Do most of you have the Veeam Server as a virtual machine or physical machine? We are looking at building the Veeam server as a virtual machine located in our VBlock. If a disaster were to happen and my Veeam server goes down. What is the process to bring the Veeam up with the ability to restore...

I am thinking of the following:

1)Install Veeam on new virtual machine/physical machine
2) Gain access to the Veeam backup directories
3) Import backup to restore

[johnlong]

I have 2 veeam servers on physical boxes. 1 in the main datacenter and one in my DR site. I use the one in the main office to perform backup tasks and the one in the DR site performs replication.

[infused]

I have it as a virtual machine at present.

[kjc3303]

I have 2 veeam servers on physical boxes. 1 in the main datacenter and one in my DR site. I use the one in the main office to perform backup tasks and the one in the DR site performs replication.

I do this with VMs

1)Install Veeam on new virtual machine/physical machine
2) Gain access to the Veeam backup directories
3) Import backup to restore

Your process looks fine, there is also a command line utility called extract.exe which will restore your backups without installing a Veeam server

Kev

[veremin]

Also, it might be worth utilizing configuration backup feature which was introduced in 6.5 version and which is responsible for retrieving configuration data from the VB&R SQL database.

Therefore, in case of disaster you can just re-install VB&R from the scratch and then import necessary configuration. It will guarantee that previously used Backup infrastructure configuration data, Jobs configuration data, as well as, Veeam Backup & Replication settings will be preserved.

More information regarding this feature can be found in the corresponding User Guide (p.297).

Hope this helps.
Thanks.

[foggy]

What is the process to bring the Veeam up with the ability to restore...

There's also an existing topic discussing that particular question, worth reviewing: What is the best way of protecting the Veeam Backup server?

[trackstar]

Thanks guys.

[flavor4real]

I have three virtual Veeam Servers. One serves as Main Veeam B&R, where the other is a proxy. The 3rd Veeam B&R backs up a few templates, the proxy and the Main Veeam B&R. The configuration on the 1st Veeam and the 3rd Veeam B&R is backed up to another network location.

Might be a bit to much but if something goes down, I have several options to restore ...

[foggy]

Might be a bit to much but if something goes down, I have several options to restore ...

That sounds reasonable. Some sort of redundancy in terms of backup will never hurt.

[trackstar]

Out of curiosity, if a Veem machine is on a virtual machine and by adding the repository storage (a linux client), how are the data being transferred during backup? So is the data being backup goes from the VMware host (datastore) to the Linux and bypassing the Veeam server?

[foggy]

The data flow is as follows: Disk > Backup proxy > Network > Backup repository > Disk.

The default backup proxy installed as a part of Veeam B&R is used in this case.

[trackstar]

The data flow is as follows: Disk > Backup proxy > Network > Backup repository > Disk.

The default backup proxy installed as a part of Veeam B&R is used in this case.

In short, the processed data is transferred directly to the repository.

[foggy]

In short, the processed data is transferred directly to the repository.

Through the proxy server.

[Backerupper]

We run all virtual within our vBlock.

Single main backup server (be sure to schedule the config backup and there is nothing to worry about there)

Single proxy in HA-AMP and a single proxy in each cluster.
HA-AMP proxy is via network (hot-add doesn't play well with NFS)
Cluster proxies are hot-add

Setup works very well for us.