Select the product you need help with

How to increase the timeout for Migration Jobs in System Center 2012 Virtual Machine Manager

Article ID: 2790310 - View products that this article applies to.

Symptoms

With System Center 2012 Virtual Machine Manager (VMM 2012) SP1, we now allow multiple migrations to occur and we can specify the maximum number of concurrent migration jobs in the properties of the host. What this means is that if we set the migration value to 2 then the third migration job will be queued until one of the earlier jobs is complete, and by default this job will wait 15 minutes before it times out and fails the job.

When this happens you will see errors similar to the following in the VMM Admin Console:

Error (23007)
Migration timeout because: VMM cannot complete the host operation on the serverName.domain.com server because of the error: Storage migration for 'serverName' was not finished because maximum storage migration limit '2' was reached, please wait for completion of an ongoing migration operation (Virtual machine ID 2425AE00-994F-40D7-A69B-1D1F9BAB9783).
Resolve the host issue and then try the operation again.

A VMM Trace will show events similar to the following:

00005365 9.20626545 [388] 0184.0008::06/24-23:57:57.717 04VirVMTask.cs(211): GetFinalResult, got error: 32768 => [Storage migration for 'VMName' was not finished because maximum storage migration limit '2' was reached, please wait for completion of an ongoing migration operation (Virtual machine ID 29FF9E76-1475-48B9-893E-2F98705B3735).]
00005366 9.20648384 [388] 0184.0008::06/24-23:57:57.717 16DeployVmSubtask.cs(10151): Win8 live migration failed with error
00005367 9.20675373 [388] 0184.0008::06/24-23:57:57.717 16DeployVmSubtask.cs(10151): Microsoft.Carmine.WSManWrappers.WSManException: VMM cannot complete the host operation on the serverName.domain.com server because of the error: Storage migration for 'VMName' was not finished because maximum storage migration limit '2' was reached, please wait for completion of an ongoing migration operation (Virtual machine ID 29FF9E76-1475-48B9-893E-2F98705B3735).

Back to the top | Give Feedback

Resolution

To work around this, you can increase the timeout between jobs by creating the following registry key and restarting the VMM service:

1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
2. Create a new DWORD value
3. Set the name to LiveMigrationQueueTimeoutSecs
4. Set the value to 00000708 HEX. This will set the Timeout to 30 minutes.
5. Restart the VMM service

Back to the top | Give Feedback

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Back to the top | Give Feedback