Skip to content

Commit af9b9b7

Browse files
authored
Merge pull request #176813 from Sharmistha-Rai/master
Data disk size
2 parents 7d87ca8 + 00a8651 commit af9b9b7

File tree

4 files changed

+44
-1
lines changed

4 files changed

+44
-1
lines changed

articles/site-recovery/hyper-v-vmm-azure-tutorial.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,30 @@ In the Microsoft Azure Recovery Services Agent Setup Wizard, configure these set
8787

8888
![Install agent](./media/hyper-v-vmm-azure-tutorial/mars-install.png)
8989

90+
### Install the Recovery Services agent on Windows core Hyper-V hosts
91+
92+
Install the agent on each Windows core Hyper-V host containing VMs that you want to replicate.
93+
94+
1. On the Windows Core Hyper-V host, create a directory by running the following command:
95+
96+
```powershell
97+
New-Item -Path C:\ASR -ItemType Directory
98+
```
99+
100+
2. Download the installer for the Microsoft Azure Recovery Services agent:
101+
102+
```powershell
103+
Invoke-WebRequest -Uri <put the URI here> -OutFile .\ASR\MARSsoftware.exe
104+
```
105+
106+
3. Execute the installer:
107+
108+
```powershell
109+
.\MARSsoftware.exe
110+
```
111+
112+
4. Once the Microsoft Azure Recovery Services agent installation completes, you can close the Wizard console.
113+
90114
## Set up the target environment
91115

92116
1. Select **Prepare infrastructure** > **Target**.
264 KB
Loading

articles/site-recovery/upgrade-mobility-service-preview.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,25 @@ If any of these need to be updated, then the **Status** reflects the same. Click
114114

115115
![replication appliance components](./media/upgrade-mobility-service-preview/appliance-components.png)
116116

117+
### Turn off auto-update
118+
119+
1. On the server running the appliance, open the Registry Editor.
120+
2. Navigate to **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAppliance**.
121+
3. To turn off auto-update, create a registry key **AutoUpdate** key with DWORD value of 0.
122+
123+
![Set registry key](./media/upgrade-mobility-service-preview/registry-key.png)
124+
125+
126+
### Turn on auto-update
127+
128+
You can turn on auto-update by deleting the AutoUpdate registry key from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAppliance.
129+
130+
To delete the registry key:
131+
132+
1. On the server running the appliance, open the Registry Editor.
133+
2. Navigate to **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureAppliance**.
134+
3. Delete the registry key **AutoUpdate**, that was previously created to turn off auto-update.
135+
117136
### Resolve issues with component upgrade
118137

119138
If prerequisites to upgrade any of the components are not met, then it cannot be updated. The reasons/prerequisites include, but not limited to,

articles/site-recovery/vmware-physical-azure-support-matrix.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -246,7 +246,7 @@ Guest/server NFS | No
246246
Guest/server iSCSI | For Migration - Yes<br/>For Disaster Recovery - No, iSCSI will failback as an attached disk to the VM
247247
Guest/server SMB 3.0 | No
248248
Guest/server RDM | Yes<br/><br/> N/A for physical servers
249-
Guest/server disk > 1 TB | Yes, disk must be larger than 1024 MB<br/><br/>Up to 8,192 GB when replicating to managed disks (9.26 version onwards)<br></br> Up to 4,095 GB when replicating to storage accounts
249+
Guest/server disk > 1 TB | Yes, disk must be larger than 1024 MB<br/><br/>Up to 32,767 GB when replicating to managed disk (9.41 version onwards)<br></br> Up to 4,095 GB when replicating to storage accounts
250250
Guest/server disk with 4K logical and 4k physical sector size | No
251251
Guest/server disk with 4K logical and 512-bytes physical sector size | No
252252
Guest/server volume with striped disk >4 TB | Yes

0 commit comments

Comments
 (0)