Two days ago the final release of UR4 for SCDPM 2012 R2 came around. There’s still no deduplication support available but this isn’t the point right now. If you use Uninterrupted Data Protection with Virtual Machine Manager, you may encounter the same error as me:
Description: DPM was unable to establish a connection with the Virtual Machine Manager (VMM) server.
Exception Message: Type: System.ServiceModel.EndpointNotFoundException, Message: Could not connect to
net.tcp://dpm-03.contoso.com:6070/VmmHelperService/TcpEndpoint. The connection attempt lasted for a time span of
00:00:05.0829204. TCP error code 10061: No connection could be made because the target machine actively refused it
[IPv4/IPv6 Adress]:6070. (ID 33400)
For whatever reason most of the DPM Servers I already updated forgot what they have been doing for months.
Re-establishing the connection helped.
Set-DPMGlobalProperty -DpmServerName <DPMServerName> -KnownVMMServers <VMMServerName>
The full error message is:
“DPM could not run the backup/recovery job for the data source because it is owned by a different DPM server.
Data source: \Online\DC-01 Owner DPM Server: DPM-02.contoso.com. (ID 3184 Details: Internal error code: 0x809909B3)”
Server 2012 R2 fantaboulous dedup feature is one of my favourites.
But I had a mysterious error within the logs about “Not enough storage” which was definitely not true.
At the end the error message is misleading and it was to less memory at night times when the server tried to dedup his storage due to a rare condition with concurrent other VMs and dynamic ram. So it happend not often and the errors weren’t in my sight.
The Power Shell gave me this:
LastOptimizationTime : 24.06.2014 01:26:49
LastOptimizationResult : 0x8007000E
LastOptimizationResultMessage : Not enough storage is available to complete this operation.
Getting more minimum memory and scaling up the weight solved the problem.
A couple of days ago (12.05.2014) there was an updates released which fixing UEFI issues on Windows Server 2012/Windows 8 and above.
On some machines the update will fail as described here.
But as suggested within the forum it seems to be working to disable “secure boot” and repeat the update run.
In my cases all machines could install and run properly.