AD forest recovery
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit 8722df6 · +23 −0 lines · also on GitHub
The file is new at this commit, or was moved here from another path: every line shows as added.
1
+---
2
+description: "Learn more about: AD Forest Recovery - Devising an AD Forest Recovery Plan"
3
+title: AD Forest Recovery - Devising an AD Forest Recovery Plan
4
+ms.author: daveba
5
+author: iainfoulds
6
+manager: daveba
7
+ms.date: 06/10/2023
8
+ms.topic: article
9
+ms.assetid: 17381f30-55f2-4e00-977a-b701675fa4ff
10
+---
11
+# AD Forest Recovery - Devising an AD Forest Recovery Plan
12
+
13
+>Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 and 2012 R2, Windows Server 2008 and 2008 R2
14
+
15
+Depending on your environment and business requirements, you might or might not need to perform all the steps described in this guide to perform a successful forest recovery. Given that this guide serves only as a template for forest recovery, it is vital that you devise a custom forest recovery plan that suits your environment and meets your business needs.
16
+
17
+For example, in your forest recovery plan, you should have a detailed topology map of your forests. The map should list all the information about the DCs, such as their names, their roles and backup status, and the trust relationships between them.
18
+
19
+You should practice your forest recovery plan at least once a year. Also, it is a good idea to perform a forest recovery drill when there are membership changes to the Enterprise Admins or Domain Admins group. This helps ensure that your information technology (IT) staff fully understands the forest recovery plan.
20
+
21
+## Next steps
22
+
23
+[!INCLUDE [ad-forest-recovery-guide-links](includes/ad-forest-recovery-guide-links.md)]
Microsoft's Markdown source from MicrosoftDocs/windowsserverdocs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 09:39 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.