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
Check if Urbackup client application is getting crashed when the backup starts.
If so then you can check application logs for more info.
How can I check if client app is getting crashed when the backup starts. Should I start file backup again during working hours and check client app at that time??
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
Seems to be like a VSS issue.
You can google for the VSS error -
Writer WIDWriter has failure state VSS_WS_FAILED_AT_BACKUP_COMPLETE with error S_OK
All right I will. Thanks.
Do u know anythingg about VSS? Does your helps end here?
Shall check and update you on this, give me some time.
Hey, how it’s going?
Open command prompt on the client machine and run the below command,
vssadmin list writers
share the output of the above command.
Ref below url for VSS related errors,
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
C:> diskshadow
DISKSHADOW> list shadows all
can u share the output of above cmd.
When was the client last restarted.
Did u try to restart the client and then try to trigger the backup.
At the time of backup failure, do see any error message in system event logs.
Last week restarted. But issue is continuing since the beginning of March.
Did u try to restart the client and then try to trigger the backup.
* yeah so many times
At the time of backup failure, do see any error message in system event logs.
* actually not check at exactly time, but trying to backup every morning in every workdays
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.
y don’t u install previous version of client software and try.
You say I have to install previous version of client’s UrBackup software and try? If that is, then why? Where did you get this opinion or solution?
BTW an update just came out for this client software 
Am I going to apply the update or through the old version?
Try install older version and see if you face the same error.
Try with the update and see. If it does not work go backup older stable version.
I have the same problem with a virtualized Windows Server 2016, image backup is disabled. This means that only the file backup is used.
Apparently you still need the VSS?
Since the installation of Urbackup, the VSS has become more unstable.
I have the feeling that the forced updates from Windows play a role here. And if the VSS access does not work because of a running update, the status of the VSS remains unstable. Which services such as the update service could still play a role there?
(Translated with www.DeepL.com/Translator)