Skip to content

Commit 7459c9d

Browse files
Merge pull request #239412 from ankitaduttaMSFT/broken-links
fixing broken links
2 parents 33941cd + 4d51144 commit 7459c9d

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

articles/site-recovery/hyper-v-azure-common-questions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Common questions for Hyper-V disaster recovery with Azure Site Recovery
33
description: This article summarizes common questions about setting up disaster recovery for on-premises Hyper-V VMs to Azure using the Azure Site Recovery site.
4-
ms.date: 12/28/2022
4+
ms.date: 05/26/2023
55
ms.service: site-recovery
66
ms.topic: conceptual
77
ms.author: ankitadutta
@@ -44,7 +44,7 @@ If you want to replicate to a secondary datacenter, then Hyper-V VMs must be on
4444

4545

4646
### Can I replicate Hyper-V generation 2 virtual machines to Azure?
47-
Yes. Site Recovery converts from generation 2 to generation 1 during failover. At failback the machine is converted back to generation 2. [Read more](https://azure.microsoft.com/blog/2015/04/28/disaster-recovery-to-azure-enhanced-and-were-listening/).
47+
Yes. Site Recovery converts from generation 2 to generation 1 during failover. At failback the machine is converted back to generation 2. [Read more](https://azure.microsoft.com/blog/new-azure-migrate-and-azure-site-recovery-enhancements-for-cloud-migration/).
4848

4949

5050
### Can I deploy Site Recovery with VMM if I only have one VMM server?

articles/site-recovery/hyper-v-azure-support-matrix.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Support for disaster recovery of Hyper-V VMs to Azure with Azure Site Rec
33
description: Summarizes the supported components and requirements for Hyper-V VM disaster recovery to Azure with Azure Site Recovery
44
ms.service: site-recovery
55
ms.topic: conceptual
6-
ms.date: 04/04/2023
6+
ms.date: 05/26/2023
77
author: ankitaduttaMSFT
88
ms.author: ankitadutta
99
---
@@ -176,7 +176,7 @@ FC disk | Not supported | Prerequisites check fails if unsupported.
176176
Hard disk format | VHD <br/><br/> VHDX | Site Recovery automatically converts VHDX to VHD when you fail over to Azure. When you fail back to on-premises, the virtual machines continue to use the VHDX format.
177177
BitLocker | Not supported | BitLocker must be disabled before you enable replication for a VM.
178178
VM name | Between 1 and 63 characters. Restricted to letters, numbers, and hyphens. The VM name must start and end with a letter or number. | Update the value in the VM properties in Site Recovery.
179-
VM type | Generation 1<br/><br/> Generation 2--Windows | Generation 2 VMs with an OS disk type of basic (which includes one or two data volumes formatted as VHDX) and less than 2 TB of disk space are supported.<br></br>Linux Generation 2 VMs aren't supported. [Learn more](https://azure.microsoft.com/blog/2015/04/28/disaster-recovery-to-azure-enhanced-and-were-listening/).|
179+
VM type | Generation 1<br/><br/> Generation 2--Windows | Generation 2 VMs with an OS disk type of basic (which includes one or two data volumes formatted as VHDX) and less than 2 TB of disk space are supported.<br></br>Linux Generation 2 VMs aren't supported. [Learn more](https://azure.microsoft.com/blog/new-azure-migrate-and-azure-site-recovery-enhancements-for-cloud-migration/).|
180180

181181
## Recovery Services vault actions
182182

articles/site-recovery/site-recovery-runbook-automation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ manager: gaggupta
66
ms.service: site-recovery
77
ms.topic: conceptual
88
ms.author: ankitadutta
9-
ms.date: 08/10/2022
9+
ms.date: 05/26/2023
1010
---
1111

1212
# Add Azure Automation runbooks to recovery plans
@@ -194,7 +194,7 @@ In some scenarios you might not be able to create separate variables for each re
194194
- For example, a SharePoint recovery has two front ends. A basic line-of-business (LOB) application has only one front end.
195195
- In this scenario you can't create separate variables for each recovery plan.
196196
197-
In the following example, we create a [complex variable](/powershell/module/servicemanagement/azure.service/set-azureautomationvariable) in the Azure Automation account.
197+
In the following example, we create a [complex variable](https://learn.microsoft.com/powershell/module/az.automation/set-azautomationvariable) in the Azure Automation account.
198198
199199
We do this by specifying multiple values, using Azure PowerShell.
200200

0 commit comments

Comments
 (0)