Hello,
we have a Windows Server 2012 R2 with DPM 2012 R2 Update Rollup 10 installed.
The Storage Pool is connected via iSCSI. The DPM database is on another server with Windows Server 2012 R2 in the same network.
I have several issues now.
On every virtual machine whether i do a consistency check, replica creation or recovery point i get disconnected from my
RDP session to the DPM server after about 1 minute, but can logon again directly afterwards.
This is not a real problem, but annoying. I have some customers who are working with Remote Apps in another subnet.
If i am trying to do jobs in DPM, they are telling me that they get disconnected and / or their system is running very slow.
Dont know if this caused by DPM, but it looks like that to me.
A few other virtual machines cannot get any job done. In the DPM console the error is following:
The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The writer experienced a non-transient error. If the backup process
is retried,
the error is likely to reoccur.
(0x800423F4))
In the event log i get iSCSI errors:
Connection to the target was lost. The initiator will attempt to retry the connection.
The initiator could not send an iSCSI PDU. Error status is given in the dump data.
Initiator failed to connect to the target. Target IP address and TCP Port number are given in dump data.
And a disk error:
Disk 3 has been surprise removed.
And not always, but sometimes a few DPM related errors, here the whole console crashes:
Event 940, MSPDM The description for Event ID 940 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Unable to connect to the database because of a fatal database error. It is unlikely that the database itself has been damaged. Review the event log and take appropriate action. Make sure that SQL Server is running.
Event 999, MSDPM The description for Event ID 999 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unexpected error caused a failure for process 'mmc'. Restart the DPM process 'mmc'.
The iSCSI target gets connected automatically again after the job failed.
If i type in "vssadmin list writers" no errors are shown.
DPM was working a few days ago, it still had some failed jobs sometimes but nothing like this situation now.
No Updates were installed since then. Because there are errors from so many sources, i dont know where
to look first. It looks like my DPM Server is dropping all network connections at some point during the job.
Looking forward to get some help from you guys!
