Hi,<o:p></o:p>
I am hoping someone on here can help with a very frustrating problem.<o:p></o:p>
I have a 5TB volume that has failed to create online recovery points to Azure Backup since 5th February. Local recovery points to disk are completing without any issues 3 times a day.<o:p></o:p>
I have 25 other volumes ranging between 1TB and 500MB that are creating online recovery points on a nightly basis without any problems.<o:p></o:p>
The Online recovery point job runs for between 30 and 35 hours and can transfer between 95GB and 130GB then fails with the message "An unexpected error occurred while the job was running. (ID 104)" or "The Windows Azure Backup Agent cannot connect to the OBEngine service. (ID 100052)"<o:p></o:p>
Type: Online
recovery point
Status: Failed
Description: An unexpected error occurred while the job was running. (ID 104)
More information
End time: 14/03/2016 12:01:20
Start time: 13/03/2016 05:48:57
Time elapsed: 30:12:23
Data transferred: 133,262.14 MB
Cluster node -
Source details: P:\
Protection group members: 14
Details
Protection group: Files Server<o:p></o:p>
<o:p> </o:p>
<o:p> </o:p>
Type: Online recovery point
Status: Failed
Description: The Windows Azure Backup Agent cannot connect to the OBEngine service. (ID 100052)
More information
End time: 04/03/2016 04:04:17
Start time: 02/03/2016 21:15:48
Time elapsed: 30:48:28
Data transferred: 96,133.74 MB
Cluster node -
Source details: P:\
Protection group members: 14
Details
Protection group: Files Server<o:p></o:p>
<o:p> </o:p>
I have checked the available capacity on the local drives and there is still 300GB capacity free on the scratch drive.
I have tried deleting the files in this directory and let DPM recreate them, but the result is still the same.<o:p></o:p>
I have also checked that we are running the latest Azure backup agent, and as of 15/03/16 we are (2.0.9028).<o:p></o:p>
<o:p> </o:p>
Has anyone experienced similar problems and successfully rectified them or have any ideas of how I can resolve this situation?