question

10646420 avatar image
0 Votes"
10646420 asked SadiqhAhmed-MSFT commented

ASR - Minium 99GB of ram on Windows VM

Hello.
I'm running some tests with ASR integrated with vmware environment.
Until I upgrade the configuration server and process server to last version, 9.43.0.0, I was able to protect windows VMs without any trouble.
But after I upgrade to 9.43.0.0, when I try to protect Windows VMs, asr portal show me an error: "The memory on the machine is less than 1GB...", but the VM has 6GB of ram.
Looking at configuration server logs, I found the logs from this specific VM protection, and there it shows that the prerequisite amount of memory for the VM is 99GB.
So, I did an upgrade on this windows VM from 6GB of ram to 105GB, than I was able to enable protection.
I've attached some screenshots from the log and asr portal.
I think there is an error/bug into ASR software.
Anybody can help me report to MS developers?


119481-selection-049.png
119329-screenshot-from-2021-07-30-11-21-50.png


azure-site-recovery
· 9
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I'm also affected by this bug

99 Gb are only required on windows hosts, on linux versions(tested on redhat 8.3 and ubuntu 20.04) it's working with more than 1 GB

0 Votes 0 ·
10646420 avatar image 10646420 AiramSuarezPerdices-5648 ·

I'll try to do a fresh installation of ASR OVA template for vmware environment. Have you tried this?
Maybe this bug was caused by the upgrade process.

0 Votes 0 ·

@SadiqhAhmed-MSFT yes, this issue started after this upgrade.
Before that, I was on 9.42.1.0 version.


0 Votes 0 ·

I can confirm the same bug when updating existing 9.42.0.0 or 9.42.1.0 agents to 9.43.0.0, after having installed Update Rollup 56 on an existing Azure Site Recovery environment (VMware-to-Azure).

@SadiqhAhmed-MSFT your solution works, but this makes push installation effectively unusable.

Is the ASR product team already aware of this bug? Can we expect it to get fixed soon?

0 Votes 0 ·

Glad to know it helped.

Yes, ASR team is aware of this bug and fix will be rolled out soon.

1 Vote 1 ·

@SadiqhAhmed-MSFT do you have any news about fixing this issue?

No actual ASR updates have been released since rollup 56 where the bug was introduced; rollup 57 contains only updates for the public preview of the new VMware to Azure protection solution.

0 Votes 0 ·

@SadiqhAhmed-MSFT , can we get an update on this? Has the fix already been released? We've just installed rollup 56 and are facing the same problem.

0 Votes 0 ·
Show more comments

1 Answer

SadiqhAhmed-MSFT avatar image
3 Votes"
SadiqhAhmed-MSFT answered VenugopalB-9267 commented

@10646420 Recommend you to try the following:

open a command prompt c:> dir /s /b Microsoft-ASR_UA_9.43*

Go to folder

You will find Microsoft-ASR_UA_9.43.0.0_Windows_GA_16Jul2021_release.exe in this location

Extract installer as follows

Microsoft-ASR_UA_9.43.0.0_Windows_GA_16Jul2021_release.exe /q /x:setup
It will extract installer inside setup folder

Go to setup folder. Open V2A-MOBILITYSERVICE-REQUIREMENTS.JSON

Remove following

{

     "CheckName": "MachineMemoryCheck",
     "OperationName" : "PreCheckMachineMemoryValidation",
     "IsMandatory" : "true",
     "Params": {
         "RequiredMemoryInGB": "0.99"
     }

}

Now run installer
UnifiedAgentInstaller.exe "/Platform" "Vmware" "/Silent" "/Role" "MS" "/InstallLocation" "C:\Program Files (x86)\Microsoft Azure Site Recovery"
It will install the product.
open a command prompt and go to agent installation folder.

Now run configurator
c:\Program Files (x86)\Microsoft Azure Site Recovery\agent>UnifiedAgentConfigurator.exe


If the response helped, do "Accept Answer" and up-vote it.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

The installation process of mobility agent is in push mode.
So do I need do this process in configuration server or on VM client (sever which I want to protect)?
Thanks in advanced

0 Votes 0 ·

This process worked like a charm!!
So after extract the installer I copied it and ran the manual installation process on the VM which I want to protect.
After that I was able to enable protection on azure ASR portal.

I'm unable to mark your reply as "Accept Answer" maybe you should post it on Answers block.

0 Votes 0 ·

hello Sadiqh,

I am coming from https://github.com/MicrosoftDocs/azure-docs/issues/80601

Could you please elaborate the last two lines and what has to be updated in the configurator.exe window?

129192-image.png


0 Votes 0 ·
image.png (3.3 KiB)