none
Client went offline during backup!

    Question

  • Currently for backup our client I am using UrBackup web application. Server client is not getting file backup. I can not find the source of this error. The problem continues as of the date of 02/27/18. HTTP Port is also true. It is 55415.

    Client UrBackup version: 2.1.16
    Server UrBackup version: 2.2.11
    OS: Windows Server 2016

    FULL ERROR MESSAGE:

    Removing snapshot on “IOMDC” for path “C” failed: FAILED

    Client IOMDC went offline.

    Backup failed

    ___________________________________________________________________________

    BTW this is logs info for the last file backup:

    Starting unscheduled full file backup…
    Indexing of “C” done. 8558 filesystem lookups 0 db lookups and 0 db updates
    IOMDC: Loading file list…
    IOMDC: Started loading files…
    Waiting for file transfers…
    Removing snapshot on “IOMDC” for path “C” failed: FAILED
    Writer WIDWriter has failure state VSS_WS_FAILED_AT_BACKUP_COMPLETE with error S_OK
    Client IOMDC went offline.
    Waiting for file hashing and copying threads…
    Waiting for metadata download stream to finish
    Writing new file list…
    All metadata was present
    Transferred 10.9297 GB - Average speed: 199.362 MBit/s
    Time taken for backing up client IOMDC: 9m 3s
    Backup failed

    ___________________________________________________________

    AND THIS CMD:

    C:\Windows\system32>Diskshadow.exe
    Microsoft DiskShadow version 1.0
    Copyright © 2013 Microsoft Corporation
    On computer: IOMDC, 4/24/2018 4:25:30 PM

    DISKSHADOW> list shadows all

    Querying all shadow copies on the computer …
    No shadow copies found in system.

       



    • Edited by mcnsvr Wednesday, April 25, 2018 11:41 AM
    Wednesday, April 25, 2018 11:27 AM

All replies

  • When I write this on cmd :          vssadmin list writers  

    Waiting for responses.
    These may be delayed if a shadow copy is being prepared.

    Writer name: 'Task Scheduler Writer’
    Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
    Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
    State: [1] Stable
    Last error: No error

    Writer name: 'VSS Metadata Store Writer’
    Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
    Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
    State: [1] Stable
    Last error: No error

    Writer name: 'Performance Counters Writer’
    Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
    Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
    State: [1] Stable
    Last error: No error

    Writer name: 'System Writer’
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {9c40324e-5b64-4914-8e8f-af2045193c8c}
    State: [1] Stable
    Last error: No error

    Writer name: 'Shadow Copy Optimization Writer’
    Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    Writer Instance Id: {6cffcb00-e396-4d3b-9d15-f7ffefe02d1f}
    State: [1] Stable
    Last error: No error

    Writer name: 'ASR Writer’
    Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Writer Instance Id: {3c4a8bdc-521e-436b-a92b-f27be06ec065}
    State: [1] Stable
    Last error: No error

    Writer name: 'SqlServerWriter’
    Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
    Writer Instance Id: {ea69fa24-7ff8-4cfd-94c7-a448732283a4}
    State: [1] Stable
    Last error: No error

    Writer name: 'WIDWriter’
    Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
    Writer Instance Id: {783f9413-3de0-4693-b18e-1281249648c6}
    State: [1] Stable
    Last error: No error

    Writer name: 'Registry Writer’
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {c8c21ec8-0f18-46d2-a5b1-68f8715e8cd0}
    State: [1] Stable
    Last error: No error

    Writer name: 'COM+ REGDB Writer’
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {2508bde5-0a57-4a80-b3dc-8803e5962658}
    State: [1] Stable
    Last error: No error

    Writer name: 'IIS Config Writer’
    Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
    Writer Instance Id: {5ca81ffa-62b1-4a79-ade0-57c7c9ec3fd1}
    State: [1] Stable
    Last error: No error

    Writer name: 'WMI Writer’
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {2e1a1ab6-ee54-48d5-b018-700aac50f96e}
    State: [1] Stable
    Last error: No error

    Writer name: 'Certificate Authority’
    Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
    Writer Instance Id: {618edf84-9d7b-4b46-b3fb-1a4556bb3931}
    State: [1] Stable
    Last error: No error

    Writer name: 'DFS Replication service writer’
    Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
    Writer Instance Id: {3c85c131-87b5-4579-bb65-51c5e529465b}
    State: [1] Stable
    Last error: No error

    Writer name: 'NPS VSS Writer’
    Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
    Writer Instance Id: {f721b36c-708b-4a73-ba7f-c8db8fd13c0f}
    State: [1] Stable
    Last error: No error

    Writer name: 'NTDS’
    Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
    Writer Instance Id: {9561264d-fb6d-40c2-81e1-def65df725ff}
    State: [1] Stable
    Last error: No error

    Writer name: 'IIS Metabase Writer’
    Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
    Writer Instance Id: {0974942a-4849-4dd7-8c43-55365ad39984}
    State: [1] Stable
    Last error: No error

    Wednesday, April 25, 2018 11:28 AM
  • Hi mcnsvr,

    According to the vss writer list, no error. Vss service seems work fine. Maybe you could disable UrBackup web application, use windows server backup to do a try.

    Since this is windows server backup forum, we mainly focus on the problem about build-in backup feature WSB (windows server backup). The  details analysis about 3rd party software backup log is  out of our support. I'm afraid for 3rd party backup software, you may still need to contact the backup software vendor for more suggestion.

    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.

    Thursday, April 26, 2018 2:06 AM
    Moderator