I dont have a solution to this as yet but I have the same issue. It happens
to be on 2 nodes of a Hyper-V cluster, and it's happening on both Nodes as
you explained. What makes my issue different is that I have removed the DPM
agent recently as I suspected it at a BSOD.
However it did work fine the last time.
I'm going to remove the agent manually on both nodes this time and reboot,
then push it out again and reboot both nodes and see if that does it.
Something that has changed within our environment is that the server has had
a windows mirror setup within disk admin of the system/boot and data volumes.
Any help would be appreciated.
Stu
In the service startup we check for the DPM trusted groups to be present in
the machines.
If this is a V2/V3 on non DC deployment
Please check if you have the below groups
1. DPMRADcomTrustedMachinesGroup
2. DPMRADmTrustedMachinesGroup
If this is is a v3 deployment on domain controllers
Please check for the below groups:
1. DPMRADcomTrustedMachinesGroup$<protectedservername>
2. DPMRADmTrustedMachinesGroup$<protectedservername>
If these groups are not present please do a setdpmserver -dpmservername
<dpmservername> on the PS to get back the groups.
Thanks,
C. Chandraneel
--
This posting is provided “AS IS” with no warranties, and confers no rights
"Henry" <He...@discussions.microsoft.com> wrote in message
news:9A2575EC-AC41-48D1...@microsoft.com...