Skip to main content

Backup Fails without error information

Thread needs solution

I have been fighting a backup failure since July. My client has 3 systems that all use TruImage. We started with version 2019 back in early Jan, 2019. In July 2019 two of the systems started failing without any information other than system failed backup. In September one of the systems started working again after we have done the things that Acronis support had suggested. We are really unable to determine what fixed this system but it is still running. The system that is still failing has been entirely replaced. New build of Windows 10 on new hardware. The system still fails doing a full backup without any indication of why. Wondering if anyone my have seen this kind of issue and has some resolutions.

0 Users found this helpful

Douglas, welcome to these public User Forums.

Sorry but we would need to see much more information to even start to guess why your one Win 10 system is failing to backup?

Please download the MVP Log Viewer tool (link in my signature below) and use this to review the log file for your backup operation. This should provide more information on why you are seeing any notification messages?

Ideally, an Acronis System Report is needed for this type of issue as the ti_demon backup log only gives very basic information since ATI 2020, so the backup_worker logs would also be needed.  The report produces a zip file which can be uploaded to the forum if less than 8MB in size, otherwise shared via a cloud service such as OneDrive.

Well it took me  a while but here is a system report link to DropBox.     I also added some smaller files in the original request.  Hopefully they are visible to you.

https://www.dropbox.com/s/feol2q6560tmpt5/SystemReport.zip?dl=0  This is probably view only but can be changed if necessary,

 

 

 

Douglas,

Your error is with Windows VSS service which is used to create a snapshot of the selected data to be backed up.  In general terms the error you received can be a number of things but your VSS Doctor logs look fine.  Because of that I recommend that you run chkdsk against all partitions on the drive.  Unlettered partitions need to have drive letters temporarily assigned so that chkdsk can be run.

If your drive is an SSD then chkdsk  drive letter /f should be used.

If your drive is an HDD then replace the option /f with /r.

Report back here.  If errors and found and corrected try to run the backup again.