Skip to main content
Solved

Physical Dc Protection

A
Forum|alt.badge.img+1

Hello Veeam Gnus ;)

Got myself totally confused so can someone unpick this for me?

I need to protect a single physical DC which has all FSMO roles. So guessing I don’t need a Protection group as its 1 computer. So do I just create a Veeam Agent job and add the DC ? But can I use a gMSA ? I want to use the Explorer and I am sure I read that you can’t use a gMSA with explorers ? In which case I need to create a domain account and add to BuiltIn Administrators group in AD ? (InfoSec are not going to like that !)

Presume I also will not need a GiP because the Agent job will install the Agent on the DC which will remain persistent ?

Have I got that all right ? I’m seeing double after reading so much !

 

Thanks Guys

 

Phil

 

Best answer by Chris.Childerhose

Airless wrote:

I forgot to add that as per best practice, the VBR server is in its own workgroup and not part of the domain.

So everything still applies from your OP anyway even being in a WG.

View original
    Did this topic help you find an answer to your question?

    5 comments

    Chris.Childerhose
    Forum|alt.badge.img+21
    • Chris.Childerhose
    • Veeam Legend, Veeam Vanguard
    • 8467 comments
    • November 29, 2024

    You are correct on all counts.  The agent will be installed to the DC and that is how VBR will manage doing the backups.  It is unfortunate that gMSA is not supported with the Explorers but it states that right in the documentation.

    Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    dloseke
    1 person likes this
    • dloseke
      dloseke
    A
    Forum|alt.badge.img+1
    • Airless
    • Author
    • Comes here often
    • 26 comments
    • November 29, 2024

    I forgot to add that as per best practice, the VBR server is in its own workgroup and not part of the domain.

    Chris.Childerhose
    dloseke
    2 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • dloseke
      dloseke
    Chris.Childerhose
    Forum|alt.badge.img+21
    • Chris.Childerhose
    • Veeam Legend, Veeam Vanguard
    • 8467 comments
    • Answer
    • November 29, 2024
    Airless wrote:

    I forgot to add that as per best practice, the VBR server is in its own workgroup and not part of the domain.

    So everything still applies from your OP anyway even being in a WG.

    Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    dloseke
    1 person likes this
    • dloseke
      dloseke
    A
    Forum|alt.badge.img+1
    • Airless
    • Author
    • Comes here often
    • 26 comments
    • November 29, 2024

    Superb ! Thanks Chris - I will crack on.

    Chris.Childerhose
    dloseke
    2 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • dloseke
      dloseke
    Chris.Childerhose
    Forum|alt.badge.img+21
    • Chris.Childerhose
    • Veeam Legend, Veeam Vanguard
    • 8467 comments
    • November 29, 2024
    Airless wrote:

    Superb ! Thanks Chris - I will crack on.

    Not a problem.  Let us know how it goes.

    Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    dloseke
    1 person likes this
    • dloseke
      dloseke

    Comment


    Terms & Conditions