Customer esx en hyper v backup to datacenter

[cgeorge]

What is the best setup for the following :
We have a datacenter and we would like to backup esx or hyper v systems from customer to our datacenter.
Do we install de veeam b&r server in our datacenter and use a storage repository there and add the customer esx or hyper v machines and pull the vm's to the storage repository in our datacenter?
Do we have to install a proxy @ the customer site also?
What licenses do we need for this kind of setup?
Or are there better setups?

[foggy]

Carol, Veeam B&R server location actually does not matter a lot, you can install it anywhere you are comfortable to manage your backups. What is essential in your scenario, is installing proxy servers at customer's site to enable efficient VM data retrieval and backup repository at your datacenter to put backups to.

Regarding licensing, you need licenses to cover all hosts you are going to protect VMs on.

[cgeorge]

Nice, that's what we need.
Now just the pricing for the licensing

[foggy]

Please contact our sales representative responsible for your region. Thanks!

[cgeorge]

What about the different domains form us and our customers?
Can veeam work with VLAN's?

[Vitaliy S.]

What about the different domains form us and our customers?

Well, if you have trust-relationship between these domains then I see no issues with this scenario (need to know what you're trying to achieve).

Can veeam work with VLAN's?

Veeam B&R is relying on Windows network routing system, so it doesn't matter whether you have VLANs or not.

[cgeorge]

Say our veeam server is in our domain xxx.lan and we have to backup a hyperv or vcenter server that is in customers yyy.lan.
If you try to backup an exchange server in the customer yyy.lan with vss (application awaerness image processing), you have to specify guest os credentials?
We won't allow trust-relationships with the customer domains.
We would at an extra virtual nic to our veeam server in the same vlan as the customers network.

[Vitaliy S.]

you have to specify guest os credentials?
We won't allow trust-relationships with the customer domains.

That would work.