I have a Windows 2016 server that was working fine, but the last couple of months has started failing with the error
Client disconnected and image is not persistent (Timeout: true).
The server has 1 physical disk with a C and E partition. The E partition, which is the large one, backups up with no error. It is only the C drive which this is happening on.
Sometimes in the urbackup client debug log is the warning:
WARNING: Writer ASR Writer has failure state VSS_WS_WAITING_FOR_BACKUP_COMPLETE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent
But it doesn’t always happen at the same time as the timeout, so I don’t know if it’s related.
Event Viewer shows no errors, and vssadmin list writers all show [1] Stable and No error.
Full error from the urbackup client:
Starting unscheduled incremental image backup of volume “C:”… Basing image backup on last incremental or full image backup Client disconnected and image is not persistent (Timeout: true). Transferred 5.95827 MB - Average speed: 27.76 KBit/s Time taken for backing up client cms: 31m 26s Backup failed
Is there any way to increase a timeout to see if that fixes anything? The server is showing no errors anywhere apart from the backup not working for the C: partition.
When it fails it is always ~30 minutes after starting, and in those 30 minutes there is no CPU or disk activity. So it looks like urbackup is waiting for the shadow copy to be ready, but one isn’t being created.
I have noticed tonight that there is an error in the event viewer at the same time as the backup starts. Event 513 from CAPI2: Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
(I don’t know if it wasn’t there before or if I ignored it because it wasn’t from VSS).
Microsoft says this can be ignored, but I have followed the steps to grant the permissions to prevent the error, but the backup still fails after 30 minutes.
The same error appeared when veeam performed a backup too, but those ones complete ok.
To further analyse the problem a client debug log would be useful. The client log file is per default located at C:\Program Files\UrBackup\debug.log on Windows. Run C:\Program Files\UrBackup\enable_debug_logging.bat as admin to enable debug logging. Once debug logging is enabled reproduce the problem.
Attach the log files to your new post or send them to bugreports@urbackup.org because they may contain data which should not be public.
Thanks for the reply. I saw the debug.log which is where I got the warning message above from so I assumed debug logging was already enabled. But now I have run the batch file I am getting more info in the debug log
I have experienced something similar with a Windows 11 (upgraded from 10 a week earlier).
Turned out that vss was somehow corrupted and was in a loop continuously drilling down and never able to complete. It took me several attempts at resetting the vss components. Plus, turning off the service until AFTER the reinstall because the reinstall silently failed with the service on.
Yes, I thought it must be something to do with VSS just don’t know why veeam wasn’t affected by it.
“Unfortunately” it hasn’t gone wrong since I enabled debug logs, but this could be because at the same time as enabling debugging I also had another look for stuff I could cleanup on the C: drive. SoftwareDistribution was 15GB which I thought was kind of large since I had already run cleanmgr so I deleted that, maybe that brought the shadow copy creation time down enough that it doesn’t timeout now.
There was always at least 50GB free space on the disk so it wasn’t running out of space.
