Skip to content

Commit 64642cc

Browse files
committed
Minor edits
1 parent 6d00872 commit 64642cc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/migrate/concepts-vmware-agentless-migration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -202,8 +202,8 @@ You can also increase and decrease replication bandwidth based on a schedule usi
202202
Azure Migrate provides a configuration-based mechanism through which customers can specify the time interval during which they don't want any replications to proceed. This time interval is called the blackout window. The need for a blackout window can arise in multiple scenarios such as when the source environment is resource constrained or when customers want replication to go through only during non-business hours, etc.
203203

204204
> [!NOTE]
205-
> The existing replication cycles at the start of the blackout window will complete before the replication pauses.
206-
> For any migration initiated during the blackout window, the final replication will not run, causing the migration to fail.
205+
> - The existing replication cycles at the start of the blackout window will complete before the replication pauses.
206+
> - For any migration initiated during the blackout window, the final replication will not run, causing the migration to fail.
207207
208208
A blackout window can be specified for the appliance by creating/updating the file GatewayDataWorker.json in C:\ProgramData\Microsoft Azure\Config. A typical file would be of the form:
209209

0 commit comments

Comments
 (0)