none
VEEAM backup jobs periodically fail with VSS error RRS feed

  • Question

  • I am running VEEAM Backup & Replication 9.5 on a Windows Server 2012 R2. VEEAM is configured to backup VM's from 2 Hyper-V Servers that are running Windows Server Data Center 2012 R2. While all VM's backup successfully 'on occasion', often, I get the following error:

    Failed to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Veeam application-aware processing) Details: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'
    [/b]

    I go to the VM Server identified, run the command "vssadmin list writers", and see that a number of VSS entries says 'timed out. I stop/start the Volume Shadow Copy service then restart the server. The backup jog then completes successfully. This issue will occur again after the 2nd or 3rd successful backup and again, I have to restart the server to get successful backups.

    Obviously I cannot continue restarting these affected servers (all of which has databases including Exchange Server 2013). Is there anything that would likely cause the VSS services to periodically time out and fail a backup? Thanks
    Monday, August 21, 2017 4:18 AM

All replies

  • Hi,

    Please see if following wiki helps

    Backup Fails with Error Message "Writer Missing" or "Failed" or "Timed Out" or "Waiting for Completion" in VSSADMIN

    https://social.technet.microsoft.com/wiki/contents/articles/7309.backup-fails-with-error-message-writer-missing-or-failed-or-timed-out-or-waiting-for-completion-in-vssadmin.aspx

    And since you use veeam, it's the 3rd party backup software, we suggest you could temporarily disable  it and use build-in windows server backup to do a check.

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 21, 2017 12:00 PM
    Moderator
  • Hi,

    Could the above reply be of help? If yes, you may mark it as answer, if not, feel free to feed back

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 25, 2017 9:37 AM
    Moderator
  • Working with VEEAM support, we discovered that the failures only occurs with 3 servers containing databases when VEEAN 'Application Awareness' is turned on. When I turn off 'Application Awareness', the jobs complete successfully. The issue has not been resolved.
    Friday, August 25, 2017 12:17 PM
  • Hi bizzie247,

    >Working with VEEAM support, we discovered that the failures only occurs with 3 servers containing databases when VEEAN 'Application Awareness' is turned on. When I turn off 'Application Awareness', the jobs complete successfully

    Thanks for your updates. That seems to be a workaround, right?

    And if possible, you could also consider to disable VEEAM, use build-in feature WSB to do a check.

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 28, 2017 2:14 AM
    Moderator
  • No, according to VEEAM, this is not a workaround. Not using Application Awareness' has a good potential for a dirty shutdown which means the backups are no good where the database is concerned when restoring and I don't have the benefit of a granular file, mailbox or single email restore.
    Monday, August 28, 2017 3:23 AM
  • Hi bizzie247,

    Thanks for your feedback. Since it may still involve the VEEAM configuration, you may still consult the software vendor. And if you have more update, please feel free to share us.

    Appreciate your support and understanding.

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 28, 2017 8:21 AM
    Moderator