Hello,
I’m having issues with DPM backups on CSV volumes.
I’m trying to backup 2 or more VM concurrently on a Hyper-V cluster with 2 nodes.
I have the following problem: when I backup 2 VM that are on 2 different nodes, but on the same CSV,the Failover Clustering service restarts on one of the nodes.
Of course, this causes a failover to the remaining host and downtime for the VMs…
No issue if backed-up VMs are on the same node or on a different CSV.
The situation is very similar to the one described in the following KB :http://support.microsoft.com/kb/975354
But the hotfix is already installed on both nodes…
Environment :
· Hyper-V OS : Windows 2008 Datacenter R2
· SAN : EqualLogic PS6000
· SAN Hardware Snapshot Provider : DELL EqualLogic VSS HW Provider - version 3.3.1.4944
· DPM : DPM 2010 RTM
Below you will find the errors found on a host that presents the issue.
Event 5121 at 2:00:34 AM
Cluster Shared Volume 'Volume1' ('EQLPRD3') is no longer directly accessible from
this cluster node. I/O access will be redirected to the storage device over the network through the node that owns the volume. This may result in degraded performance. If redirected access is turned on for this volume, please turn it off. If redirected access is turned off, please troubleshoot this node's connectivity to the storage device and I/O will resume to a healthy state once connectivity to the storage device is reestablished.
Event 1038 at 2:01:44 AM
Ownership of cluster disk 'EQLPRD2' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.
Event 1038 at 2:01:45 AM
Ownership of cluster disk 'Quorum' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.
Event 4201 at 2:01:46 AM
Isatap interface isatap.{55DFCEFD-ED71-4C57-9277-8FBD5219D184} is no longer active.
Event 7031 at 2:01:51 AM
The Cluster Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
Has anyone seen and solved this problem or is it a normal behavior (which I doubt) ?
Thanks for the help.
