Skip to content

Commit 68130f9

Browse files
Clarify note on existing VM snapshots
Simplified wording regarding existing snapshots for clarity.
1 parent db357f1 commit 68130f9

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ After the migration is successful and the VM restarts in Azure, ensure that you
3737
## Replication cycles
3838

3939
> [!NOTE]
40-
> Be sure to check for any existing snapshots on the VM from earlier replication attempts, partner applications, or active backup tools (e.g., VEEAM), as this will block agentless replication setup in Azure Migrate.
40+
> Be sure to check for any existing snapshots on the VM from earlier replication attempts, partner apps, or active backup tools (e.g., VEEAM), as this will block agentless replication setup in Azure Migrate.
4141
> Snapshot-based backups conflict with Azure Migrate’s agentless change tracking and replication process and should not be used concurrently.
4242
4343
A replication cycle is the periodic process of transferring data from an on-premises environment to Azure managed disks. A full replication cycle consists of the following steps:

0 commit comments

Comments
 (0)