Best Way to Test DC and Network Fileshare Server Backups

Peter_Gibbons 61 Reputation points
2021-06-01T15:37:46.947+00:00

I've been doing some research but am having a tough time finding best practices for testing DC and network fileshare server backups. I have backup service that regularly sends me notifications that our domain controller and fileshare servers have successfully been backed up offsite but I would like to periodically test the backups to make sure I know how to recover after an incident and also to confirm that my assumptions about what is backing up are correct.

I have created a testing vlan on our network and was thinking I could setup a test server to pull the backups onto. Is this the right approach?

I am trying to figure out how to test the DC backup on the testing vlan without creating any redundancy conflicts with the genuine DCs running on our operations vlan. Even though though there is no traffic between vlans, I'm concerned that restoring a DC backup with the same domain name could wreak havoc in our environment.

Is it possible to test the DC backup on a test domain, i.e. create a test domain--"AD.test.edu" and import the DC backup to inspect AD Users and Groups, DHCP, DNS and other services?

Testing the fileshare server seems more straightforward as it will be isolated on the testing vlan and is not running any other network services other than hosting the shared files.

Please forgive me if these hypotheses are wildly impractical or misguided.

Thanks in advance for any guidance you can offer.

Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2021-06-02T12:25:08.563+00:00

    best practice for testing a backup in an isolated network environment so that it does not create conflict with services running on our operations vlan

    As long as the environment is isolated from production it won't be a problem.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

12 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-06-01T16:00:42.41+00:00

    Its always recommended to have at least two domain controllers for high availability and disaster mitigation. If the role holder fails you can simply seize roles to another healthy domain controller without downtime, then do cleanup prior to rebuilding the failed one.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  2. Peter_Gibbons 61 Reputation points
    2021-06-01T16:25:14.297+00:00

    As always, thank you for your timely response DSPatrick.

    We do have two DCs running on our domain, but we only back up the configuration of the primary DC offsite.

    I want to do disaster recovering testing with this offsite backup to make sure we can get our domain back online in the event of a ransomware or other attack that would cause use to shutdown our network or otherwise lose access to our domain services.

    Do best practices exist for testing recovery from such undesirable scenarios?

    0 comments No comments

  3. Anonymous
    2021-06-01T18:53:55.56+00:00

    You could probably do your recovery testing in an isolated environment.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  4. Peter_Gibbons 61 Reputation points
    2021-06-01T19:16:45.723+00:00

    Thank you. Last question should be: Do you know if there any known issues with replicating an existing domain in an isolated environment? Any issues to watch out for/avoid?

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.