You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/site-recovery/migrate-overview.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,16 +23,16 @@ Using Azure Migrate for migration provides many advantages:
23
23
- 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.
24
24
- Azure Migrate can be used to identify modernization opportunities and migration previews.
25
25
- 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.
28
28
- We're prioritizing new migration features for the Migration and modernization tool only. These features aren't targeted for Site Recovery.
29
29
30
30
## When to use Site Recovery?
31
31
32
32
Site Recovery should be used:
33
33
34
34
- 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.
36
36
37
37
## Which service to use for migration?
38
38
@@ -49,7 +49,7 @@ Suggestions to choose between Azure Migrate and Site Recovery:
49
49
50
50
-**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.
51
51
-**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.
53
53
-**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.
0 commit comments