Skip to content

Commit e5597fa

Browse files
authored
Corrected typo
Recovery plans can be used to trigger failover of up to 100 machines at a time, not 50.
1 parent 4657a88 commit e5597fa

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/site-recovery/vmware-physical-large-deployment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@ You can prepare in advance for failover as follows:
206206
To run a large-scale failover, we recommend the following:
207207

208208
1. Create recovery plans for workload failover.
209-
- Each recovery plan can trigger failover of up to 50 machines.
209+
- Each recovery plan can trigger failover of up to 100 machines.
210210
- [Learn more](recovery-plan-overview.md) about recovery plans.
211211
2. Add Azure Automation runbook scripts to recovery plans, to automate any manual tasks on Azure. Typical tasks include configuring load balancers, updating DNS etc. [Learn more](site-recovery-runbook-automation.md)
212212
2. Before failover, prepare Windows machines so that they comply with the Azure environment. [Failover limits](#plan-azure-subscriptions-and-quotas) are higher for machines that comply. [Learn more](site-recovery-failover-to-azure-troubleshoot.md#failover-failed-with-error-id-170010) about runbooks.

0 commit comments

Comments
 (0)