none
Unable to finish BMR backups RRS feed

  • Question

  • Dear folks,

    We hare having issue with a DPM 1807 server on Server 2016 with MBS.

    BMR backups of other 2016 Servers fail with WSB logging error 517 "The sempahore timeout period has expired":

    In addition, backup event 5 is logged:

    The backup operation that started at <time> has failed with following error code '0x8078015B' (Windows Backup encountered an error when accessing the remote shared folder. Please retry the operation after making sure that the remote shared folder is available and accessible.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.


    We have noticed that the everything goes well until the DPM server build up enough buffered I/O (modified memory). It then starts writing the buffered stuff to disk; at that time the network load drops to almost nothing, and the backup fails soon afterwards.

    Server 2008R2 backs up fine; maybe also because the BMRs are smaller and hence have less chance to fail.

    Things tried:

    • Disabling all write cache on the ReFS MBS drive, but with no success
    • Assigning more memory to the server
    • Playing with network parameters (offload, RSS, etc) on both client and DPM server
    • Playing with ReFS tunable parameters
    • Update to August 2018 CU for Server 2018
    • Went through info on https://social.technet.microsoft.com/Forums/en-US/740fd820-2f31-458f-a974-70671d969430/event-log-source-disk-event-id-51-an-error-was-detected-on-device-deviceharddisk3dr76-during-a?forum=dataprotectionmanager and  https://social.technet.microsoft.com/Forums/lync/en-US/0ab7099f-93e4-4010-a856-53deec58b0a8/event-viewer-disk-alerts-dpm-2016?forum=dataprotectionmanager without success

    How can we force the server not to buffer so much write or otherwise make those backups successful?



    Sunday, October 21, 2018 9:24 PM

Answers

  • Not sure why the link to the announcement does not work, but this is the content which I don't believe has been discussed in this post.

    Symptoms:

    On DPM server:

    DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code: 
     0x6B48C3A0). (ID 30229 Details: Internal error code: 0x80990ED0)

    OR 

    You may also encounter an error “The storage involving the current operation could not be read from or written to. (ID 40003)”

    Log Name:      DPM Alerts
    Source:        DPM-EM
    Date:          7/7/2017 11:11:36 AM
    Event ID:      3106
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      <servername>
    Description:
    The replica of Non VSS Datasource Writer on <servername> is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3106)
    The storage involving the current operation could not be read from or written to. (ID: 40003)

    On Protected server:

    Log Name:      Microsoft-Windows-Backup
    Source:        Microsoft-Windows-Backup
    Date:          5/8/2018 10:43:42 AM
    Event ID:      5
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      <Servername>
    Description:
    The backup operation that started at '?2018?-?05?-?08T15:17:32.312386000Z' has failed with following error code '0x8078015B' (Windows Backup encountered an error when accessing the remote shared folder. Please retry the operation after making sure that the remote shared folder is available and accessible.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    And 

    Log Name:      Microsoft-Windows-SmbClient/Connectivity
    Source:        Microsoft-Windows-SMBClient
    Date:          5/21/2018 4:23:49 PM
    Event ID:      30809
    Task Category: None
    Level:         Error
    Keywords:      (64)
    User:          N/A
    Computer:      <servername>
    Description:
    A request timed out because there was no response from the server.

    And

    Server name: <Servername>
    Session ID:0x17801D0000031
    Tree ID:0x1
    Message ID:0x4000015
    Command: Flush
    Guidance:
    The server is responding over TCP but not over SMB. Ensure the Server service is running and responsive, and the disks do not have high per-IO latency, which makes the disks appear unresponsive to SMB. Also, ensure the server is responsive overall and not paused; for instance, make sure you can log on to it.


    Log Name:      Microsoft-Windows-SMBServer/Operational
    Source:        Microsoft-Windows-SMBServer
    Date:          5/21/2018 4:25:37 PM
    Event ID:      1020
    Task Category: (1020)
    Level:         Warning
    Keywords:      (8)
    User:          SYSTEM
    Computer:      <ServerName>
    Description:
    File system operation has taken longer than expected.
    Client Name: <IP>
    Client Address: <IP:Port>
    User Name: <Username>
    Session ID: 0x17801D0000031
    Share Name: <sharename>
    File Name: WINDOWSIMAGEBACKUP\<Servername>\<Backupdate>\<GUID>.VHDX
    Command: 7
    Duration (in milliseconds): 353151
    Warning Threshold (in milliseconds): 120000
    Guidance:
    The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB


    Cause:
    SMB timeout is too short for IO latency for BMR on REFS.

    Resolution\Workaround:

    Option 1: 

    Set registry and reboot protected server. 

    Note:  The 1200 second setting is a 20 minute timeout.  This is not a rigid number but has been tested with success.   Depending on latency you can adjust as needed.  To get suspected latency please review REFS event logs on DPM\MABS server. 


    1. Add the registry key below on the protected server

    reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v SessTimeout  /t REG_DWORD /d 1200

    Option 2: 

    If you cannot reboot server (Note:  Ensure you check the list of dependencies for the Lanmanworkstation service as those services will need to be started again too) 

    1.Add the registry key below on the protected server

    reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v SessTimeout  /t REG_DWORD /d 1200


    2.Stop/Start      Lanmanworkstation service

    Note: There are some other services that depend on Lanmanworkstation, just start those back.

    Regards
    Mike Jacquet

      

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, January 6, 2020 3:32 PM
    Moderator

All replies

  • Hi,

    Did you modify the pagefile size on your DPM Server? 

    DPM requires a pagefile size that is 0.2 percent the size of all recovery point volumes combined, in addition to the recommended size (generally, 1.5 times the amount of RAM on the computer). For example, if the recovery point volumes on a DPM server total 3 TB, you should increase the pagefile size by 6 GB.


    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Monday, October 22, 2018 5:48 AM
  • Hi Matej,

    Thank you for the suggestion.

    the page file is 32Gb on about 14TB of disk storage, so that's roughly around 0.2%.

    Monday, October 22, 2018 6:00 AM
  • Hi,

    have you tried enabling bandwidth throttling in DPM for the protected server to see whether it could help?


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, October 22, 2018 6:29 AM
  • I havem Leon,

    this applies only for non-BMR backups as I understand and had no effect on limiting the bandwidth :/

    Monday, October 22, 2018 6:35 AM
  • Right on, this was indeed a BMR, morning coffee didn't kick in yet..

    Did you try running the BMR backup manually on the affected protected server?

    1. Create a network share on a remote machine that has lots of free space: \\server\share\

    2. From a Command Prompt (Admin) on the protected server, type the following command:
    wbadmin.exe start backup -allcritical -backuptarget:\\server\share


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, October 22, 2018 7:08 AM
  • I have tried this and:

    Backing up to another NTFS share = success
    Backing up to a share on the same ReFS drive as the MBS = success
    Backing up to NTFS share on VHDX on ReFS drive:
        This worked, but in between suffered from the same erratic transfer speeds
        I assume this this could just as well have failed, since once every 20 or so times the BMR actually succeeds, too
    Monday, October 22, 2018 11:41 AM
  • You could try performing a BMR backup to the DPM replica volume via the BMR share using NT AUTHORITY\SYSTEM account, this should be very identical to as DPM performing a BMR backup.

    wbadmin.exe start backup -allcritical -backuptarget:\\DPM_server\BMR_share_GUID

    You can get the share by typing net share in a Command Prompt (Admin) on the DPM server.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, October 22, 2018 1:23 PM
  • Any trick of getting the share online first?

    Unless DPM thinks it's doing a backup the disk isn't mounted, so it errors out with device not ready.

    Monday, October 22, 2018 2:34 PM
  • Seems indeed to be a bit troublesome in newer DPM versions as you say the disk isn't mounted.

    Did you try the following?

    https://blogs.technet.microsoft.com/dpm/2017/04/14/how-to-increase-dpm-2016-replica-when-using-modern-backup-storage-mbs/


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, October 23, 2018 7:28 AM
  • Replica size isn't the problem; it's currently 300 Gb with about 180 Gb for BMR backup.

    The error is "Sempahore timeout expired"; not out of disk space.

    Tuesday, October 23, 2018 10:39 AM
  • When you were playing with the tunable parameters, did you restart the DPM server after each change?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, October 23, 2018 10:48 AM
  • The following were set and then rebooted:

    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
    
    "RefsEnableInlineTrim"=dword:00000001
    "RefsDisableDeleteNotification"=dword:00000001
    "RefsEnableLargeWorkingSetTrim"=dword:00000001
    "RefsNumberOfChunksToTrim"=dword:00000020
    "RefsDisableCachedPins"=dword:00000001
    "RefsProcessedDeleteQueueEntryCountThreshold"=dword:00000800
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Configuration\DiskStorage]
    "DuplicateExtentBatchSizeInMB"=dword:00000064
    
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk]
    "TimeOutValue"=dword:00000078

    Tuesday, October 23, 2018 6:41 PM
  • You might want to try the Update Rollup 6 which was released today.

    This update fixes the following issues:

    • Virtual Hard Disk (VHD) missing during mount or unmount operations.
    • VHD mount or unmount takes a long time to finish.
    • Data Protection Manager performance is decreased because of multiple update agent jobs.
    • Data Protection Manager console crashes while recovering data from online recovery points.
    • Data Protection Manager crashes when you move protected clients to another disk.
    • Data Protection Manager System State and Bare Metal Recovery (BMR) fails intermittently for multiple servers.
    • Indefinite looping occurs for consistency check jobs for Resilient Change Tracking (RCT) on a virtual machine (VM) because of I/O errors.
    • Update Rollup 5 for Data Protection Manager 2016 cannot enumerate SQL Server 2017 Availability Group databases for protection.
    • Data Protection Manager 2016 Update Rollup Agent causes a restart of the protected server.


    Note: A fresh installation of the Update Rollup Agent could cause a restart of the protected server.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, October 23, 2018 11:31 PM
  • Mhh the update crashed preparing in RunDpmPatch.exe

    Unhandled exception; just like so often with DPM :}

    Exception Info: System.Configuration.ConfigurationErrorsException
       at Microsoft.Internal.EnterpriseStorage.Dls.Utils.ApplicationSettings.GetMsiInstallPath(System.String)

    [...]

    Possibly this isn't compatible to version 1807 judging by the error looking for an install path?

    Wednesday, October 24, 2018 11:00 AM
  • Oh right, you were using DPM 1807, the rollup is for DPM 2016, my bad! Hopefully they will fix issues in DPM 19XX.

    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Wednesday, October 24, 2018 11:38 AM
    Wednesday, October 24, 2018 11:36 AM
  • I'll report if something develops :}

    Wednesday, October 24, 2018 11:51 AM
  • I have the same exact issue with DPM 1807. Please post if you find the solution.
    Thursday, October 25, 2018 5:41 PM
  • In my case it seems that only physical servers are affected, 2016 Std  1607 and 2012 R2.
    Thursday, October 25, 2018 5:55 PM
  • We have tried moving to a test server with DPM 2016 UR6 instead of 1807, but all Server 2016 payloads still fails to to BMR backups with semaphore timeout expired.
    Friday, December 7, 2018 10:06 AM

  • We have recently upgraded much of our Windows estate to Windows Server 2016 and as part of this work we also upgraded our DPM Server to DPM 2016 1801. Since doing so, the BMR/System State backups for Windows 2016 servers frequently fail. The BMR backups on our Windows 2008R2 servers continued to work without any problems. Looking through the backup/event logs we see the following logged when the backups fail:

    0x8078015B  Windows Backup encountered an error when accessing the remote shared folder
    0x80070079 The semaphore timeout period has expired

    I spent quite some time trying to find a solution to this problem, initially without a great deal of success. If I removed the server from the protection group in DPM, cleared the backup history, and then re-added the server, I would find that the BMR backups worked once or twice before failing consistently once again. If I ran Windows backup on the protected computer, backing up the BMR to local disk it would also work fine. The same BMR backup to a share on the DPM server also worked consistently. Further digging revealed that the DPM server presents a share to the protected computer for the duration of the backup. Testing revealed that the share was removed from the DPM server before the BMR backup completes, resulting in the backup failing. I attempted various configuration changes to try and resolve the problem, but none of these worked. For completeness, here is what I tried unsuccessfully:

    1. Creating/modifying the following registry keys on both the DPM server and the protected server
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SPP\CreateTimeout and set decimal value to 3600000. To increase VSS timeout.
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VSS\Settings\IdleTimeout and set decimal value to 3600000. To increase VSS timeout.
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Disk\TimeOutValue and changed decimal value from 60 to 180.
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\TcpMaxDataRetransmissions with a decimal value of 5.
    2. Running “wbadmin delete catalog” on the protected server to clear the backup catalog.
    3. Checking for shadow copies and removing them on the protected server using the command “vssadmin list shadows”.
    4. Increasing the paging file to 16Gb from 2Gb on the DPM server.
    5. Attempting to throttle the bandwidth using the bandwidth throttling in DPM.
    6. Modifying the disk allocation to 100Gb for the backup within DPM.
    7. Running chkdsk /f on the protected server.
    8. Modifying the maximum size of storage allocated to volumes for shadow copies to have no limit at all.

    As I said, none of the above helped at all. What has finally led to us being consistently able to run BMR backups reliably on Windows 2016 servers was throttling the bandwidth between the protected server and the DPM server using a QoS profile on the protected server itself. I’ve read somewhere that the throttling built into DPM does not apply to BMR backups. I’m not sure whether that’s true, but trying that did not help us at all. It’s very simple to create a QoS profile in Windows 2016, and it’s not necessary to install any additional software, roles or features. To do so, simply carry out the following steps:

    1. Start “Local Group Policy Editor” by typing gpedit.msc on the protected computer.
    2. Browse to Local Computer Policy > Computer Configuration > Windows Settings > Policy-based QoS.
    3. Right click and select “Create New Policy”.
    4. Provide a name for the policy, uncheck “Specify DSCP Value” and set an outbound throttle rate (I used 100MBps successfully).
    5. Select “All applications” (though if your backup server provides other functions you may wish to restrict this just to the Windows Backup application.
    6. Select “Any source IP address” and enter the IP address of the backup server in the destination field.
    7. Select both the TCP and UDP protocols, and any source/destination port.
    8. The policy takes immediate effect without a requirement to reboot.

    Since applying this policy our BMR backups on Windows 2016 have worked reliably and consistently. Hopefully this is of help to others as well, as this can be quite a frustrating problem!

    Simon Edwins
    Senior IT Security Specialist
    Rothamsted Research

    • Proposed as answer by Simon Edwins Thursday, June 6, 2019 3:05 PM
    • Unproposed as answer by namezero111111 Thursday, June 6, 2019 3:46 PM
    Thursday, June 6, 2019 3:05 PM
  • Hi Simon,

    we reason they might in this case (for now) is that ReFS doesn't get overloaded when data just trickles in.

    The actual workaround for now is to avoid ReFS like the plague by running on Server 2012R2 and getting the "advantages" of legacy backup storage.

    See here for an extended discussion: https://social.technet.microsoft.com/Forums/en-US/7e4e4da4-1168-46cd-900f-9ca2bc364d5a/dpm-2016-mbs-performance-downward-spiral

    Thursday, June 6, 2019 3:48 PM
  • Hi,

    The solution is in this announcement.

    DPM 2016 BMR backups fail intermittently - ID 30229 Details: Internal error code: 0x80990ED0

    Regards
    Mike Jacquet


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, January 3, 2020 9:55 PM
    Moderator
  • Hi,

    The solution is in this announcement.

    DPM 2016 BMR backups fail intermittently - ID 30229 Details: Internal error code: 0x80990ED0

    Regards
    Mike Jacquet


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    The link is broken :}
    Saturday, January 4, 2020 6:54 AM
  • The link works, you just have to click on the ”Announcement” section on the top of the page to see it.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Saturday, January 4, 2020 9:51 AM
  • Ahh got it thanks.

    Many things have been tried, the issue is unresolved for now.

    See https://social.technet.microsoft.com/Forums/en-US/7e4e4da4-1168-46cd-900f-9ca2bc364d5a/dpm-2016-mbs-performance-downward-spiral?forum=dataprotectionmanager for the entire thread on this  discussion.

    The underlying storage doe snot react. Yes, we know. The problem is REFS.
    None of the REFS parameters there have made any difference, and the suggested paths is 18 months old.

    Saturday, January 4, 2020 12:15 PM
  • Not sure why the link to the announcement does not work, but this is the content which I don't believe has been discussed in this post.

    Symptoms:

    On DPM server:

    DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code: 
     0x6B48C3A0). (ID 30229 Details: Internal error code: 0x80990ED0)

    OR 

    You may also encounter an error “The storage involving the current operation could not be read from or written to. (ID 40003)”

    Log Name:      DPM Alerts
    Source:        DPM-EM
    Date:          7/7/2017 11:11:36 AM
    Event ID:      3106
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      <servername>
    Description:
    The replica of Non VSS Datasource Writer on <servername> is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3106)
    The storage involving the current operation could not be read from or written to. (ID: 40003)

    On Protected server:

    Log Name:      Microsoft-Windows-Backup
    Source:        Microsoft-Windows-Backup
    Date:          5/8/2018 10:43:42 AM
    Event ID:      5
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      <Servername>
    Description:
    The backup operation that started at '?2018?-?05?-?08T15:17:32.312386000Z' has failed with following error code '0x8078015B' (Windows Backup encountered an error when accessing the remote shared folder. Please retry the operation after making sure that the remote shared folder is available and accessible.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    And 

    Log Name:      Microsoft-Windows-SmbClient/Connectivity
    Source:        Microsoft-Windows-SMBClient
    Date:          5/21/2018 4:23:49 PM
    Event ID:      30809
    Task Category: None
    Level:         Error
    Keywords:      (64)
    User:          N/A
    Computer:      <servername>
    Description:
    A request timed out because there was no response from the server.

    And

    Server name: <Servername>
    Session ID:0x17801D0000031
    Tree ID:0x1
    Message ID:0x4000015
    Command: Flush
    Guidance:
    The server is responding over TCP but not over SMB. Ensure the Server service is running and responsive, and the disks do not have high per-IO latency, which makes the disks appear unresponsive to SMB. Also, ensure the server is responsive overall and not paused; for instance, make sure you can log on to it.


    Log Name:      Microsoft-Windows-SMBServer/Operational
    Source:        Microsoft-Windows-SMBServer
    Date:          5/21/2018 4:25:37 PM
    Event ID:      1020
    Task Category: (1020)
    Level:         Warning
    Keywords:      (8)
    User:          SYSTEM
    Computer:      <ServerName>
    Description:
    File system operation has taken longer than expected.
    Client Name: <IP>
    Client Address: <IP:Port>
    User Name: <Username>
    Session ID: 0x17801D0000031
    Share Name: <sharename>
    File Name: WINDOWSIMAGEBACKUP\<Servername>\<Backupdate>\<GUID>.VHDX
    Command: 7
    Duration (in milliseconds): 353151
    Warning Threshold (in milliseconds): 120000
    Guidance:
    The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB


    Cause:
    SMB timeout is too short for IO latency for BMR on REFS.

    Resolution\Workaround:

    Option 1: 

    Set registry and reboot protected server. 

    Note:  The 1200 second setting is a 20 minute timeout.  This is not a rigid number but has been tested with success.   Depending on latency you can adjust as needed.  To get suspected latency please review REFS event logs on DPM\MABS server. 


    1. Add the registry key below on the protected server

    reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v SessTimeout  /t REG_DWORD /d 1200

    Option 2: 

    If you cannot reboot server (Note:  Ensure you check the list of dependencies for the Lanmanworkstation service as those services will need to be started again too) 

    1.Add the registry key below on the protected server

    reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters /v SessTimeout  /t REG_DWORD /d 1200


    2.Stop/Start      Lanmanworkstation service

    Note: There are some other services that depend on Lanmanworkstation, just start those back.

    Regards
    Mike Jacquet

      

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Monday, January 6, 2020 3:32 PM
    Moderator
  • This doesn't fix the underlying issue of an ever slowing REFS sotrage system in conjunction with DPM. BMRs will still take days to complete.
    Tuesday, January 7, 2020 12:26 PM
  • With all due respect, why do you keep insisting on marking this as answer when it isn't?
    Thursday, January 9, 2020 6:57 AM
  • Hi 

    As per the thread title "Unable to finish BMR backups" and the original problem description below, the solution in the announcement is the solution. This issue is not a DPM issue, DPM is the victim of the SMB timeout.


    <snip>

    BMR backups of other 2016 Servers fail with WSB logging error 517 "The sempahore timeout period has expired":

    In addition, backup event 5 is logged:

    The backup operation that started at <time> has failed with following error code '0x8078015B' (Windows Backup encountered an error when accessing the remote shared folder. Please retry the operation after making sure that the remote shared folder is available and accessible.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
    >snip<

    If you have performance issues or other errors then open a new forum post to address the separate issue.

    Regards
    Mike Jacquet


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, January 9, 2020 5:32 PM
    Moderator
  • Sure, close if you wish; I won't fight this.

    The root cause might not be DPM, but it still becomes unusable due to it.

    We have since reverted to DPM2012R2 and never looked back, err, forward :D

    Thursday, January 9, 2020 7:48 PM