Skip to content

Commit 7c1023a

Browse files
committed
Latest UI changes
1 parent d206291 commit 7c1023a

File tree

2 files changed

+19
-16
lines changed

2 files changed

+19
-16
lines changed

articles/migrate/common-questions-server-migration.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,11 @@ Test migration simulates the actual migration by creating a test Azure VM using
103103
Once you have migrated your VM/server successfully, you can view and manage the VM from the Virtual Machines page. Connect to the migrated VM to validate.
104104
Alternatively, you can review the ‘Job status’ for the operation to check if the migration was successfully completed. If you see any errors, resolve them, and retry the migration operation.
105105

106-
### What happens if I don’t complete the migration?
106+
### What happens if I don’t stop replication after migration?
107+
108+
When you stop replication, the Azure Migrate: Server Migration tool cleans up the managed disks in the subscription that were created for replication. If you do not stop replication after a migration, you will continue to incur charges for these disks. Stop replication will not impact the disks attached to machines that have already been migrated.
109+
110+
### What happens if I don’t complete migration after migration?
107111

108112
When you complete migration, the Azure Migrate: Server Migration tool cleans up the managed disks in the subscription that were created for replication. If you do not click **Complete migration** after a migration, you will continue to incur charges for these disks. Complete migration will not impact the disks attached to machines that have already been migrated.
109113

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

Lines changed: 14 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -89,24 +89,24 @@ The Azure Migrate appliance compresses data and encrypts before uploading. Data
8989
## Replication status
9090

9191
When a VM undergoes replication(data copy), there are a few possible states:
92-
- **Initial replication (Queued)**: The VM is queued for replication (or migration) as there are other VMs that are consuming the on-premises resources (during replication or migration). Once the resources are free, this VM will be processed.
92+
- **Initial replication queued**: The VM is queued for replication (or migration) as there may be other VMs that are consuming the on-premises resources (during replication or migration). Once the resources are free, this VM will be processed.
9393
- **Initial replication in progress**: The VM is being scheduled for initial replication.
94-
- **Initial sync**: The VM is undergoing initial replication. When the VM is undergoing initial replication, you cannot proceed with test migration and migration. You can only stop replication at this stage.
95-
- **Initial sync (x%)**: The initial replication is active and has progressed by x%.
94+
- **Initial replication**: The VM is undergoing initial replication. When the VM is undergoing initial replication, you cannot proceed with test migration and migration. You can only stop replication at this stage.
95+
- **Initial replication (x%)**: The initial replication is active and has progressed by x%.
9696
- **Delta sync**: The VM may be undergoing a delta replication cycle that replicates the remaining data churn since the last replication cycle.
97-
- **Pause in progress**: The VM is undergoing an active delta replication cycle and will be paused at some time.
97+
- **Pause in progress**: The VM is undergoing an active delta replication cycle and will be paused in some time.
9898
- **Paused**: The replication cycles have been paused. The replication cycles can be resumed by performing a resume replication operation.
99-
- **Resuming (Queued)**: The VM is queued for resuming replication as there are other VMs that are currently consuming the on-premises resources.
100-
- **Resume in progress (x%)**: Replication cycle is being resumed for the VM and has progressed by x%.
99+
- **Resume queued**: The VM is queued for resuming replication as there are other VMs that are currently consuming the on-premises resources.
100+
- **Resume in progress (x%)**: The replication cycle is being resumed for the VM and has progressed by x%.
101101
- **Stop replication in progress**: Replication cleanup is in progress. When you stop replication, the intermediate managed disks (seed disks) created during replication will be deleted. [Learn more](#stop-replicationcomplete-migration).
102102
- **Complete migration in progress**: Migration cleanup is in progress. When you complete migration, the intermediate managed disks (seed disks) created during replication will be deleted. [Learn more](#stop-replicationcomplete-migration).
103103
- **** : When the VM has successfully migrated and/or when you have stopped replication, the status changes to “-“. Once you stop replication / complete migration and the operation finishes successfully, the VM will be removed from the list of replicating machines. You can find the VM in the virtual machines tab in the replicate wizard.
104104

105105
### Other states
106106

107107
- **Initial replication failed**: The initial data could not be copied for the VM. Follow the remediation guidance to resolve.
108-
- **Repair replication**: There was an issue in the replication cycle. You can select the link to understand possible causes and actions to remediate (as applicable). If you had opted for **Automatically repair replication** by selecting **Yes** when you triggered replication of VM, the tool will try to repair it for you. Else, select on the VM, and select **Repair Replication**. If you did not opt for **Automatically repair replication** or the above step did not work for you, then stop replication for the virtual machine, reset changed block tracking on the virtual machine, and then reconfigure the replication.
109-
- **Repair replication (Queued)**: The VM is queued for replication repair as there are other VMs that are consuming the on-premises resources. Once the resources are free, the VM will be processed for repair replication.
108+
- **Repair pending**: There was an issue in the replication cycle. You can select the link to understand possible causes and actions to remediate (as applicable). If you had opted for **Automatically repair replication** by selecting **Yes** when you triggered replication of VM, the tool will try to repair it for you. Else, select the VM, and select **Repair Replication**. If you did not opt for **Automatically repair replication** or if the above step did not work for you, then stop replication for the virtual machine, reset the changed block tracking on the virtual machine, and then reconfigure the replication.
109+
- **Repair replication queued**: The VM is queued for replication repair as there are other VMs that are consuming the on-premises resources. Once the resources are free, the VM will be processed for repair replication.
110110
- **Resync (x%)**: The VM is undergoing a data resynchronization. This can happen if there was some issue / mismatch during data replication.
111111
- **Stop replication/complete migration failed**: Select the link to understand the possible causes for failure and actions to remediate (as applicable).
112112

@@ -118,16 +118,15 @@ When a VM undergoes replication(data copy), there are a few possible states:
118118
- **Test migration pending**: The VM is in delta replication phase, and you can now perform test migration (or migration).
119119
- **Test migration clean up pending**: After test migration is complete, perform a test migration clean up to avoid charges in Azure.
120120
- **Ready to migrate**: The VM is ready to be migrated to Azure.
121-
- **Migration in progress (Queued)**: The VM is queued for migration as there are other VMs that are consuming the on-premises resources during replication (or migration). Once the resources are free, the VM will be processed.
122-
- **Migration in progress**: The VM is migrating. You can select the link to check the ongoing migration job. This job consists of five stages: Prerequisites check for migration, shutting down the virtual machine (optional step), prepare for migration, creation of Azure VM, start the Azure VM.
123-
- **Test migration in progress**: The VM is undergoing a test migration. You can select the link to check the ongoing migration job.
124-
- **Date, timestamp**: The migration / test migration date and timestamp.
121+
- **Migration in progress queued**: The VM is queued for migration as there are other VMs that are consuming the on-premises resources during replication (or migration). Once the resources are free, the VM will be processed.
122+
- **Test migration/Migration in progress**: The VM is undergoing a test migration/migration. You can select the link to check the ongoing migration job.
123+
- **Date, timestamp**: The migration/test migration date and timestamp.
125124

126125
### Other states
127126

128-
- **Completed with info**: The migration / test migration job completed with information. You can select the link to check the last migration job for possible causes and actions to remediate (as applicable).
129-
Failed: The migration / test migration job failed. You can select the link to check the last migration job for possible causes and actions to remediate.
130-
- ****: Initial replication is progress. You can perform a migration or test migration after the replication process transitions to a delta sync (incremental replication) phase.
127+
- **Completed with info**: The migration/test migration job completed with information. You can select the link to check the last migration job for possible causes and actions to remediate (as applicable).
128+
- **Failed**: The migration/test migration job failed. You can select the link to check the last migration job for possible causes and actions to remediate.
129+
- ****: Initial replication is in progress. You can perform a migration or test migration after the replication process transitions to a delta sync (incremental replication) phase.
131130

132131
## Scheduling logic
133132

0 commit comments

Comments
 (0)