Skip to main content

cyber protect disapointment

Thread needs solution

After so many years of Acronis experience, 1 corrupted file brought the backup system to its knees.

It did show a strange message saying that the backup was stopped by the user and advising to run CHKDSK.

And started a loop of backing up and backup stopped by the user.

Not saying if it was the source or the destination drive, anyway chkdsk /F and chkdsk /scan didn't find anything.

apparently chkdsk only looks for bad sectors.

After hours of chkdsk, memory checks, I decided to simply copy the files to the backup drive with Total Commander.

Then TC found a corrupted file that I deleted and the copy went through till the end.

After the corrupted file was deleted I did a normal backup, it completed an validated.

Well it is very disapointing that cyber protect or true image are not smart enough to show that a file is corrupted instead of freaking out and sending wrong messages.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Hello,

Thank you for sharing your experience with Acronis. We understand the frustration caused by the backup system's reaction to a corrupted file. Please be advised that the integrity of the disks and the respective storage/files is the responsibility of the users. Acronis performs backups based on the data it receives and does not have the capability to prevent or diagnose corruption at the file level.

In situations where issues arise, such as the strange message suggesting the backup was stopped by the user and advising to run CHKDSK, it's essential to note that Acronis relies on system notifications and error messages. In this case, the loop of backing up and stopping may have been triggered by the system's response to the corrupted file.

We appreciate your thorough troubleshooting efforts with CHKDSK, memory checks, and using Total Commander to identify and delete the corrupted file. It's indeed disappointing when backup systems encounter difficulties without providing clear indications of the problem's nature.

Your feedback is valuable, and we will forward it to our development team for consideration. We aim to enhance our products continually, and user experiences like yours help us identify areas for improvement.

If you encounter any further issues or have additional feedback, please don't hesitate to reach out to our support team at Acronis Support.