Veeam Cloud Connect server domain joined?

[rtstephn]

We are building a Veeam Cloud Connect Enterprise server for our branch offices to backup to. Is it recommended to have the VCCE Veeam server be domain joined? We plan to keep this VCCE Veeam server independently from our HQ Veeam B&R Server. Our HQ Veeam server is domain joined.
Two of our backup repositories are Windows domain joined, and we have a couple Linux repositories that are not domain joined.

Are there pros or cons to domain joined VCCE Veeam server?
Thank you in advance!

Rich

[Vitaliy S.]

Hi Richard,

Recommendations for Veeam Cloud Connect are the same as for regular Veeam backup servers, since the software dependencies are absolutely the same for both servers. Not having it joined to a domain would allow you to use that server after losing the DC.

Thanks!

[rtstephn]

Thank you for the reply!

So the domain joined scenario is only for convenience then? And I will loose no management functionality (or other capabilities) with a stand-alone VCCE server?

It sounds like it would be more resilient being non-domain joined...?
Rich

[Gostev]

That is correct. And especially in light of recently added Insider Protection functionality, you really do want to keep your VCC-E deployment as isolated from your production environment as humanly possible. So that even if your production environment is completely compromised, your backups are still safe.

[rtstephn]

Much Appreciated! Thank you for clarifying the advantages of the off-domain approach.