Adding vCD to Veeam

[levtech1]

Hi All,

when adding vCD to VBR should the Public FQDN be used or an internal DNS name? should it just go to one cell or is there a best practice?

[Andreas Neufert]

I think from a API perspective a cell is the point where Veeam can use.

Veeam can work with IP, short or FQDN names. It is a question what you want to see in the management interface.

[levtech1]

Hi Andreas,

Thank you for the reply but i understand that the cell is the point it can use but what "Should" it use? today i have Veeam pointing to the public FQDN.

[dellock6]

Hi Lev
we only use the api of vcloud cells and nothing more, all the data retrieved from vcloud are metadata, since all the backups and restores of actual data is done through the underlying vcenter/esxi. So, using public or private dns of the cells is more about the design you want to do, for us is the same.
Also, for a clustered group of cells, if you want to load balance and make it highly available also for Veeam, you should use the shared dns name. In short terms, I usually suggest to use the same dns that is given to end users and keep it simple.

[ftravinsky]

I'd like to continue this thread with an extra question:

Why do we need vCD system administrator account to manage vCD through Veeam? Any ETAs on having this done with simple org admin?
As a tenant I am not allowed to create reverse replications from vCD back to the on-premise.

[ftravinsky]

https://helpcenter.veeam.com/docs/backu ... ml?ver=100

(you cannot use the organization administrator account to add vCloud Director)

Actually, any elaboration ongoing with VMware on this one?

[veremin]

As a tenant I am not allowed to create reverse replications from vCD back to the on-premise.

Just to be sure - are you talking about Cloud Connect here? Thanks!

[ftravinsky]

Usually, Veeam Cloud Connect comes along with vCD platform of the IaaS provider, so, as a tenant, I can’t tell for sure if it relates to Cloud Connect or VMWare vCloud Director API.

You can work with VMs managed by vCloud Director directly in the Veeam Backup & Replication console.

Currently, this vCD management feature (which HelpCenter article points to) can’t be used by tenants with Org admin account, only by the provider himself due to vCD admin account is required by vCD API.

Just pointing that you can elaborate with VMWare on easing this requirement.