creating Recovery Points fail after updating to System Center 2012 R2 UR4 – Connection to VMM lost/refused

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.
Server name: 

SCMVMM-01.
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>

 

 

pfsense on Hyper-V – my personal light sword of open source routers

Thanks to a reader of the blog and another friend of mine who is sticking closer to the pfsense topic than me, I got a hint about the latest snapshot of pfsense which now has the Hyper-V integration services built in.
You can get an overview of the BSD Integration Services (BIS) at the official FreeBSD wiki.

I’m really happy to see what’s coming around.

What the heck is he talking about?
Continue reading

Hyper-V virtual machine backup leaves the VM in a locked state … does it?

Update 10.10.2014

Now I have a better view and I can see that one other cluster have the described problem.
With VMM you can get the message if you try to move, start up a VM:

Error (12711)
VMM cannot complete the WMI operation on the server (hyper-v-03.contoso.com) because of an error: [MSCluster_Resource.Name=&quot;SCVMM SOF-Prev-02&quot;]
[…]
The requested operation can not be completed because a resource has locked status (0x1748)
[…]

Failover Cluster Manager will say “The resource $VM is locked.”

From roughly around 70 VMs almost a third can’t be moved, started up or something else.

Really painful is the fact that you can’t do anything with the Hyper-V Host itself.
Trying to get ’em in paused mode for example.

Hyper-V-resource locked

Dynamic Optimizing is getting crazy as well. 😉
Applying the Hotfix seems to be working.

Continue reading