Issue
You may identify this issue through either the CloudM Migrate interface or your Windows system logs:
-
CloudM Migrate UI / Logs: The migration stops and displays the error:
"Insufficient memory to continue the execution of the program"
-
Windows Event Logs: The System log reports "Resource Exhaustion" errors coinciding with the migration stop. Look for the following source:
Microsoft-Windows-Resource-Exhaustion-Detector
See CloudM Migrate System Requirements.
Root Cause
This error indicates that the machine running CloudM Migrate (Primary or Secondary server) has exhausted its available memory resources. This occurs when the physical RAM is full and the Windows Pagefile (Virtual Memory) has reached its limit.
This is common when:
Migrating large items or complex folder structures.
Running too many concurrent migration threads for the server's specification.
The server specifications do not meet the requirements for the workload.
Resolution
There are three ways to resolve this issue, listed in order of recommended troubleshooting.
Option 1: Adjust Windows Virtual Memory (Pagefile)
The quickest software-based fix is to increase the amount of hard drive space Windows can use as "temporary RAM" (the Pagefile).
Steps to configure:
On the migration server, press Start and search for "Advanced System Settings".
Open View advanced system settings.
Go to the Advanced tab and locate the Performance section.
Click Settings > Advanced.
Under Virtual Memory, click Change.
Recommended Settings:
System Managed: Uncheck "Automatically manage paging file size," select the drive, and choose System managed size. Click Set.
-
Custom Size (Power User): For dedicated migration servers, we recommend manually setting the pagefile to 2 times the installed RAM (e.g., if you have 16GB RAM, set the Pagefile to 32,768MB).
Note: Microsoft typically recommends 1.5x (see Introduction to the page file), but CloudM recommends 2x for heavy migration workloads.
Click OK and Restart the server for changes to take effect.
Option 2: Increase Physical RAM
If adjusting the virtual memory does not resolve the issue, the server likely requires more physical hardware resources.
Action: Provision additional RAM for the Virtual Machine (VM) or physical server.
Refer to the CloudM Migrate System Requirements to ensure your server meets the recommended specifications for your user count.
Option 3: Reduce Migration Load
If hardware upgrades are not immediately possible, you can reduce the memory pressure by lowering the migration concurrency.
Action: In your CloudM Migrate Service Manager, lower the Maximum User Migrations (concurrent entity threads) or Maximum Complete Migrations (concurrent batches) settings.
Note: This will slow down the overall migration speed but will increase stability.