I have several problems, and they all seem to be related to VMMS.
1) I cannot get a good backup with Backup Exec 2014 on two different machines unless VMMS is recycled. Even then, sometime the backup will fail. One backup is 10 hours and one is 3 hours. The 10 hours one usually fails on the Exchagne 2010 server - it is
1.2TB across 4 VHDXs.
2) I tried to move a VM from one host to another and it would fail. Had to restart VMMS on the destination server before the VM would move
Some things I have done:
1) Fresh install on Windows 2012 R2 on a server, updated, joined to domain, left in default 'Computers' OU.
2) Converted all VHDs to VHDX
3) Re-created all VMs - only reused the VHDX files
4) Converted VHD/VHDX from dynamic to fixed size
All servers are 2012 R2, domain connected, and Hyper-V is the only role. All guest services are up to date. There are no login restrictions.
Some of the errors:
Failed to fix-up absolute VHD paths in configuration of virtual machine 'VMNAME': Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been
enforced. (0x8007052F). (Virtual machine ID D547F8AF-109D-4A06-A312-3B25940BB921)
At the same time in the Application log:
A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried, the error may not reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PrepareForSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Name: Microsoft Hyper-V VSS Writer
Writer Instance ID: {d5e01751-b485-48eb-bc63-1c512e8db85c}
Command Line: C:\Windows\system32\vmms.exe
Process ID: 6624
Nothing of interest in the System log.
If I restart the VMMS service, it will work. This happened at 8:02pm and there are no account login restrictions.
I had moved a VM last night and this morning went to add another VHDX to the machine, it failed with this error:
'FS01' failed to add device 'Virtual Hard Disk'. (Virtual machine ID 182CEB70-7F75-4C14-AF1D-C300488B19FA)
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>14140</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-11-22T15:20:33.480335100Z" />
<EventRecordID>390</EventRecordID>
<Correlation />
<Execution ProcessID="6148" ThreadID="8836" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>vmhost01.domain.local</Computer>
<Security UserID="S-1-5-18" />
</System>
- <UserData>
- <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<VmName>FS01</VmName>
<VmId>182CEB70-7F75-4C14-AF1D-C300488B19FA</VmId>
<Parameter0>Virtual Hard Disk</Parameter0>
</VmlEventLog>
</UserData>
</Event>
Restarted VMMS and it worked as expected. VMMS is running as Local System account. Is there a benefit to running it as a different account?
