You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| 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 selectan existing vault.
1283
+
- Extension settings
1284
+
- Update settings: Allow ASR to manage
1285
+
- Automation account: you are able to selectan 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 waitfor 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`.
0 commit comments