Skip to content

Commit dbada43

Browse files
committed
fixed acrolinx
1 parent 335c8e3 commit dbada43

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/active-directory-domain-services/tutorial-perform-disaster-recovery-drill.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,22 +17,22 @@ ms.author: justinha
1717

1818
# Tutorial: Perform a disaster recovery drill using replica sets in Microsoft Entra Domain Services
1919

20-
This topic shows how to perform a disaster recovery (DR) drill for Microsoft Entra Domain Services using replica sets. This will simulate one of the replica sets going offline by making changes to the network virtual network properties to block client access to it. It is not a true DR drill in that the replica set will not be taken offline.
20+
This topic shows how to perform a disaster recovery (DR) drill for Microsoft Entra Domain Services using replica sets. This excercise simulates one of the replica sets going offline by making changes to the network virtual network properties to block client access to it. It's not a true DR drill in that the replica set isn't taken offline.
2121

22-
The DR drill will cover:
22+
The DR drill covers:
2323

2424
1. A client machine is connected to a given replica set. It can authenticate to the domain and perform LDAP queries.
2525
1. The client's connection to the replica set will be terminated. This will happen by restricting network access.
26-
1. The client will then establish a new connection with the other replica set. Once that happens, the client will be able to authenticate to the domain and perform LDAP queries.
27-
1. The domain member will be rebooted, and a domain user will be able to log in post reboot.
28-
1. The network restrictions will be removed, and the client will be able to connect to original replica set.
26+
1. The client then establishes a new connection with the other replica set. Once that happens, the client is able to authenticate to the domain and perform LDAP queries.
27+
1. The domain member will be rebooted, and a domain user can sign in after reboot.
28+
1. The network restrictions are removed, and the client can connect to original replica set.
2929

3030
## Prerequisites
3131

3232
The following requirements must be in place to complete the DR drill:
3333

3434
- An active Domain Services instance deployed with at least one extra replica set in place. The domain must be in a healthy state.
35-
- A client machine that is joined to the Domain Services hosted domain. The client must be in its own virtual network, virtual network peering enabled with both replica set virtual networks, and the virtual network must have the IP addresses of all domain controllers in the replica sets listed in DNS.
35+
- A client machine that's joined to the Domain Services hosted domain. The client must be in its own virtual network, virtual network peering enabled with both replica set virtual networks, and the virtual network must have the IP addresses of all domain controllers in the replica sets listed in DNS.
3636

3737
## Environment validation
3838

@@ -49,7 +49,7 @@ The following requirements must be in place to complete the DR drill:
4949

5050
## Perform the disaster recovery drill
5151

52-
You will be performing these operations for each replica set in the Domain Services instance. This will simulate an outage for each replica set. When domain controllers are not reachable, the client will automatically fail over to a reachable domain controller and this experience should be seamless to the end user or workload. Therefore it is critical that applications and services don't point to a specific domain controller.
52+
You need to perform these operations for each replica set in the Domain Services instance. The operations simulate an outage for each replica set. When domain controllers aren't reachable, the client automatically fails over to a reachable domain controller. This experience should be seamless to the end user or workload. Therefore, it's critical that applications and services don't point to a specific domain controller.
5353

5454
1. Identify the domain controllers in the replica set that you want to simulate going offline.
5555
1. On the client machine, connect to one of the domain controllers using `nltest /sc_reset:[domain]\[domain controller name]`.
@@ -67,7 +67,7 @@ These operations demonstrate that the domain is still available even though one
6767

6868
## Summary
6969

70-
After you complete these steps, you will see domain members continue to access the directory if one of the replica sets in the Domain Services is not reachable. You can simulate the same behavior by blocking all network access for a replica set instead of a client machine, but we don't recommend it. It wont change the behavior from a client perspective, but it will impact the health of your Domain Services instance until the network access is restored.
70+
After you complete these steps, you see domain members continue to access the directory if one of the replica sets in the Domain Services isn't reachable. You can simulate the same behavior by blocking all network access for a replica set instead of a client machine, but we don't recommend it. It won't change the behavior from a client perspective, but it impacts the health of your Domain Services instance until the network access is restored.
7171

7272
## Next steps
7373

0 commit comments

Comments
 (0)