Skip to content

Commit ea6f26d

Browse files
author
Ankita Dutta
committed
incub 3
1 parent c50cca8 commit ea6f26d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/site-recovery/migrate-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,16 +23,16 @@ Using Azure Migrate for migration provides many advantages:
2323
- The Migration and modernization tool is purpose-built for server migration to Azure. It's optimized for migration. You don't need to learn about concepts and scenarios that aren't directly relevant to migration.
2424
- Azure Migrate can be used to identify modernization opportunities and migration previews.
2525
- Some key features like OS upgrade are only available with Azure Migrate
26-
- There are no tool usage charges for migration for 180 days, from the time replication is started for a VM. This gives you time to complete migration. You only pay for the storage and network resources used in replication, and for compute charges consumed during test migrations.
27-
- Azure Migrate supports all migration scenarios supported by Site Recovery. In addition, for VMware VMs, Azure Migrate provides an agentless migration option.
26+
- There are no tool usage charges for migration for 180 days, from the time replication is started for a virtual machine. This gives you time to complete migration. You only pay for the storage and network resources used in replication, and for compute charges consumed during test migrations.
27+
- Azure Migrate supports all migration scenarios supported by Site Recovery. In addition, for VMware virtual machines, Azure Migrate provides an agentless migration option.
2828
- We're prioritizing new migration features for the Migration and modernization tool only. These features aren't targeted for Site Recovery.
2929

3030
## When to use Site Recovery?
3131

3232
Site Recovery should be used:
3333

3434
- For disaster recovery of on-premises machines to Azure.
35-
- For disaster recovery of Azure VMs, between Azure regions.
35+
- For disaster recovery of Azure virtual machines, between Azure regions.
3636

3737
## Which service to use for migration?
3838

@@ -49,7 +49,7 @@ Suggestions to choose between Azure Migrate and Site Recovery:
4949

5050
- **For new migration**: If you're beginning a new migration and don't have either Azure Site Recovery or Migrate in place, we recommend that you use Azure Migrate.
5151
- **For disaster recovery of on-premises machines to Azure**: For disaster recovery of on-premises machines to Azure, we recommend that you use Azure Site Recovery. You can also use this service to migrate machines to Azure once it has been determined that they should be moved off-premise.
52-
- **For disaster recovery of Azure VMs between Azure region**: For disaster recovery of Azure VMs between Azure regions, we recommend that you use Azure Site Recovery. Although you can use Azure Migrate to initially move them into Azure.
52+
- **For disaster recovery of Azure virtual machines between Azure region**: For disaster recovery of Azure virtual machines between Azure regions, we recommend that you use Azure Site Recovery. Although you can use Azure Migrate to initially move them into Azure.
5353
- **If you're already using Azure Site Recovery**: If you're currently using Azure Site Recovery to actively protect your machines, continue to use it for replication. However, consider using Azure Migrate for conducting business cases and dependency analysis.
5454

5555
## Next steps

0 commit comments

Comments
 (0)