Skip to content

Commit d6ecc37

Browse files
authored
Update concepts-vmware-agentless-migration.md
1 parent d1d90c5 commit d6ecc37

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -185,6 +185,9 @@ As a best practice, you should always complete the migration after the VM has mi
185185
## Impact of churn
186186

187187
We try to minimize the amount of data transfer in each replication cycle by allowing the data to fold as much as possible before we schedule the next cycle. Because agentless replication folds in data, the _churn pattern_ is more important than the _churn rate_. When a file is written again and again, the rate doesn't have much impact. However, a pattern in which every other sector is written causes high churn in the next cycle.
188+
If the current delta replication cycle takes longer due to high churn, the start of the next cycle will be delayed. Delta replication cycle will require more time to create a recovery point if there is more data to upload for a specific disk. Consequently, the final migration will also take longer, resulting in a longer VM shutdown period.
189+
190+
If the churn exceeds the available datastore capacity, the datastore may run out of space, which can impact production writes and cause the source VM to become unresponsive. Mitigation to this is to increase the datastore size. If there are other VMs being replicated simultaneously, it is recommended to migrate one VM at a time.
188191

189192
## Management of replication
190193

0 commit comments

Comments
 (0)