"Azure Backup could not communicate with VSS writers due to errors in VSS. (ID 100183)" RRS feed

  • 질문

  • Hi guys, See if you guys can give a hand with this scenario. 

    At work we have a server who basically has one job,  trough the Azure safe DPM, backup our files from the file server to our azure private cloud. But has being happening for a while that on the online recovery point task he fail, the error that shows is Related to VSS writes. The SQL Server VSS Writer service is running as wish, so I quite lost in what could be the problem.

    If i reboot the whole machine and startup all the services manually they go back to work and communicate but after some weeks everything crash again 

    Did someone face any similar issue? 



    Status: Failed
    Description: Backup failed as Azure Backup could not communicate with VSS writers due to errors in VSS. (ID 100183)
    More information
    End time: 16/03/2020 22:01:17
    Start time: 16/03/2020 22:00:41
    Time elapsed: 00:00:36
    Data transferred: 0 MB
    Cluster node -
    Source details: E:\
    Protection group members: 7
    Protection group: File Server
    2020년 3월 17일 화요일 오후 3:28

모든 응답

  • Hi,

    Are you using Microsoft Azure Backup Server (MABS) or DPM?

    Also what version & build are you using?

    Could you provide more information about your backup environment and what kind of workloads you're having issues backing up with?

    Best regards,

    Blog: LinkedIn:

    2020년 3월 17일 화요일 오후 10:13
  • I'm Using DPM 13.0.415.0 version, on a windows server 2012 R2  9600 under the same domain that my file server. And in this specific protection group is all about files from the users, (.doc .xls  some images etc) but I'm also sending to cloud me ERP files in a different protection group (.dll .reg and my database) and in this protection group works fine! no a single alert! 

    2020년 3월 18일 수요일 오전 10:21
  • This is Microsoft Azure Backup Server (MABS) which is not DPM, it is "based on DPM" but still a different product.

    You are currently using MABS v3, which is unfortunately not supported on Windows Server 2012 R2, please see the system requirements here:

    As this is not a supported scenario, there's no guarantee that things will work as they should, I would first of all suggest you to have a supported scenario and then check if the problem persists.

    Blog: LinkedIn:

    • 답변으로 제안됨 Leon Laude 2020년 4월 6일 월요일 오후 9:01
    2020년 3월 18일 수요일 오전 11:06