B&R 6.0 Physical Domain Controller as Proxy

[Andrew1344]

It seems I cannot Add the Physical Microsoft Windows Server 2003 Domain Controller as a server in B&R 6.0. I get the following error:

Failed to install deployment Service......

I believe it is a permission isuue. Since it is a DC, there is no local user group.

What is the work around?

Any help would be appreciated...

[foggy]

Andrew, Veeam B&R is a solution for backing up virtual machines only.

[Andrew1344]

I was told that 6.0 now has that capability..........

[Sethbartlett]

It has the capability to make physical machines proxies, but not back them up.

[Gostev]

I think this is what OP tries to do though - leverage physical machine as a proxy or repository? He does not say anything about backing it up... if this box has lots of hard drives, why not use it backup repository for example?

I agree this is probably permissions issue - I will ask QC to try to do the same on Monday, and see if there are any issues adding DC.

[tsightler]

I've used a DC as a proxy in my lab. You simply must add it using an account that has Domain Admin permissions.

[ZachW]

Yeah, I use a DC as my main proxy within my lab as well.. And have worked with countless other people who do the same. If you continue to run into issues just create a ticket at veeam.com/support.

[foggy]

I was confused by the topic's title...

[rfn]

[merged]

Hi,

In our DR site we have an extra Domain Controller running on DR hardware (it's still on our local LAN). I'm wondering if I could use that as a backup proxy to be able to use hot add for writes when doing replication. Right now we have to use NBD for our replication target.

Is that a bad idea?

Would it require multiple vCPU or doesn't it need to any heavy processing?

[dellock6]

Uhm, seems moderators merged your post by mistake, two different questions
Anyway, on replica it's better to use virtual proxies as targets, since they can use hotadd for writing in destination datastores. You cannot use SAN mode for writes...
Luca.

[Gostev]

Was not me who merged this, but looks like correct merge. Both the topic above, and the merged question are about using DC as a backup proxy.

René, I don't see any issues with this approach if the DC you are talking about is virtual. Additional vCPU is always a good idea, although target proxy does not use much CPU resources unlike source one.

[rfn]

Hi,

That sounds perfect... It's of course a virtual DC I will try it out and monitor the CPU usage and adjust vCPU as needed. Thank you!