Skip to content

Commit 61e4a97

Browse files
committed
ASR
1 parent 9fcb994 commit 61e4a97

File tree

1 file changed

+45
-0
lines changed

1 file changed

+45
-0
lines changed

README.md

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1259,6 +1259,51 @@ You should be able to access Admin Server and have the same domain configuration
12591259
12601260
### Use Azure Site Recovery
12611261
1262+
Azure Site Recovery will back up the disk of VM once you enable and protect the replica, you need not move the domain configuration to shared storage.
1263+
1264+
#### Enable Azure Site Recovery
1265+
1266+
Follow the step to enable ASR:
1267+
1268+
- Go to Azure Portal and open adminVM
1269+
- Select Operations -> Disaster recovery
1270+
- Basics
1271+
- Disaster Recovery between Availability Zones? **Yes**
1272+
- Advanced settings
1273+
- Target settings, please node down the target resource group, you will use it in the automation script.
1274+
| General settings | Source | Target |
1275+
|-----------|-----------|-----------|
1276+
|Subscription | Source subscription | Target subscription |
1277+
| VM resource group | Do not change | Append `-asr` to the end of source resource group name. |
1278+
| Virtual network | Do not change | Do not change |
1279+
| Availability | Availability zone 1 | Availability zone 3 |
1280+
| Proximity placement group | Not applicable | Select new group |
1281+
- Replication settings.
1282+
- Recovery service vault, you are able to select an existing vault.
1283+
- Extension settings
1284+
- Update settings: Allow ASR to manage
1285+
- Automation account: you are able to select an existing automation account.
1286+
- Click Review and start replication
1287+
1288+
It takes about 1 hour for the resources ready. Once the deployment completes, you are able to find the replica from Recovery service vault.
1289+
1290+
#### Failover Manually
1291+
1292+
ASR allow you to test failover in a seperated vnet. You are able to test failover to validate vM resource, but the Admin Server fails to access managed servers in a seperate vnet.
1293+
1294+
Follow the steps to start failover.
1295+
1296+
- Open your recovery service vault from Azure Portal.
1297+
- Select Protected items -> Replicated istems, you should find the adminVM listed and the status is **Protected**, if not, you have to wait for the status becomes **Protected**.
1298+
- Open adminVM, the **Failover** should be available, otherwise, you have troubleshoot and resolve error before moving on.
1299+
- Click Failover and start the process, please check `shutdown virtual machine` if your adminVM is running.
1300+
1301+
It takes about 15 min to completed the failover steps. You still need to assign the virtual IP address to the target machine:
1302+
1303+
- Remove secondary IP from source adminVM: go to Azure Portal -> open source adminVM -> select **Settings** -> select **Networking** -> open the network interface -> select **Settings** -> select **IP Configurations** -> remove `ipconfig2` which was configured with virtual IP of Admin Server.
1304+
- Assign secondary IP to target adminVM: go to Azure Portal -> open target adminVM -> select **Settings** -> select **Networking** -> open the network interface -> select **Settings** -> select **IP Configurations** -> Add `ipconfig2` with static IP address, here is `10.0.0.16`.
1305+
- Wait for Admin Server ready.
1306+
12621307
## Validate
12631308
12641309
Validate the Forms testing application.

0 commit comments

Comments
 (0)