Skip to content

Commit 1ee1bb8

Browse files
tfosmarktfosmark
authored
Merge pull request MicrosoftDocs#20648 from BaileyLawson/patch-7
Minor grammatical and accuracy changes.
2 parents 3d22cc5 + 0656e14 commit 1ee1bb8

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

‎articles/site-recovery/azure-stack-site-recovery.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ Select and verify target resources.
205205
3. In **RPO threshold**, specify the recovery point objective (RPO) limit.
206206
- Recovery points for replicated data are created in accordance with the time set.
207207
- This setting does not affect replication, which is continuous. It simply issues an alert if the threshold limit is reached without a recovery point being created.
208-
4. In **Recovery point retention**, Specify how long each recovery point is kept. Replicated VMs can be recovered to any point in the specified time window.
208+
4. In **Recovery point retention**, specify how long each recovery point is kept. Replicated VMs can be recovered to any point in the specified time window.
209209
5. In **App-consistent snapshot frequency**, specify how often application-consistent snapshots are created.
210210

211211
- A app-consistent snapshot is a point-in-time snapshot of the app data inside the VM.
@@ -228,13 +228,13 @@ Make sure you've completed all the tasks in [Step 1: Prepare machine](#step-1-pr
228228
3. In **Machine type**, select **Physical machines**.
229229
4. Select the process server (configuration server). Then click **OK**.
230230
5. In **Target**, select the subscription and the resource group in which you want to create the VMs after failover. Choose the deployment model that you want to use for the failed-over VMs.
231-
6. Select the Azure storage account in which you want to stored replicated data.
231+
6. Select the Azure storage account in which you want to store the replicated data.
232232
7. Select the Azure network and subnet to which Azure VMs connect when they're created after failover.
233233
8. Select **Configure now for selected machines** to apply the network setting to all machines you select for protection. Select **Configure later** if you want to select the Azure network separately for each machine.
234-
9. In **Physical Machines**, click **+Physical machine**. Specify the name of IP address of each machine, and the operating system you want to replicate.
234+
9. In **Physical Machines**, click **+Physical machine**. Specify the name, IP address and OS type of each machine you want to replicate.
235235

236236
- Use the internal IP address of the machine.
237-
- If you specify the public IP address replication might not work as expected.
237+
- If you specify the public IP address, replication may not work as expected.
238238

239239
10. In **Properties** > **Configure properties**, select the account that the process server will use to automatically install Mobility Service on the machine.
240240
11. In **Replication settings** > **Configure replication settings**, check that the correct replication policy is selected.
@@ -274,8 +274,8 @@ When you run a test failover, the following happens:
274274
place.
275275
2. Failover processes the data using the specified recovery point:
276276
- **Latest processed**: The machine fails over to the latest recovery point processed by Site Recovery. The time stamp is shown. With this option, no time is spent processing data, so it provides a low RTO (recovery time objective).
277-
- **Latest app-consistent**.The machine fails over to the latest app-consistent recovery point.
278-
- **Custom**. Select the recovery point used for failover.
277+
- **Latest app-consistent**: The machine fails over to the latest app-consistent recovery point.
278+
- **Custom**: Select the recovery point used for failover.
279279

280280
3. An Azure VM is created using the processed data.
281281
4. Test failover can automatically clean up Azure VMs created during the drill.
@@ -314,7 +314,7 @@ Then run a failover as follows:
314314

315315
### Fail back to Azure Stack
316316

317-
When you primary site is up and running again, you can fail back from Azure to Azure Stack. To do this, you need to download the Azure VM VHD, and upload it to Azure Stack.
317+
When your primary site is up and running again, you can fail back from Azure to Azure Stack. To do this, you need to download the Azure VM VHD, and upload it to Azure Stack.
318318

319319
1. Shut down the Azure VM, so that the VHD can be downloaded.
320320
2. To start downloading the VHD, install [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/).

0 commit comments

Comments
 (0)