Error reading from CBU backup.

Help - CB
#1

:-[. I backed up my hard drive with the latest version and reloaded windows. Now when I try to restore I get read error and no data. I can’t afford to loose my data. How can I get it back? It’s on an external tb hard drive?

#2

I too have a similar problem. I backed up my hard drives to a Self-Extracting .EXE on an external drive. Then I installed Windows 7 x64 and tried to restore my files. I get the following error:

“F:\backup_full_files.exe is not a valid Win32 Application.”

If I try to open up the .exe in Comodo (version 4.0 or version 3.0) I get a ‘PASSWORD’ required box, but I did not SET a password!

So now I am locked out of my files…I have nearly 5-6 YEARS worth of information and data in that backup file, and I can’t seem to open it. This is VERY disturbing from a customer point of view…makes me distrust completely what could be a very good product.

Any solutions found yet?

#3

Can you please post a screenshot with the error? Also the CBU.exe.log and CBU.exe.logold.log in %TEMP%\ComodoLogsFolder?
To retrieve your data you can also try to mount (right click on backup file → choose “CBU Mount”)

Thanks

#4

Yes, you can use this split file tool.
You can split the file to the size in bytes of CSE.exe
You must make sure that you split at exact size of CSE.exe in the installation folder.

If you used an older version of Comodo Backup to create the backup, then you must split at the exact size of that CSE.exe for that installation (it may be different for 32bit and 64bit ).

Then, the second split (larger) can be restored with Comodo Backup like a regular cbu file.

Thanks

#5

Here are my files.

[attachment deleted by admin]

#6

Can you please let me know where the backup is stored. Is it on network, local disk, external disk, online storage, ftp server? The logs don’t show this information.
Also, did you try to mount the backup?

Thanks

#7

It is a fantom external drive attached to my laptop by esata cable. I get an error trying to mount the drive.

#8

I got the same read error with 4.7! Is there any way to gt my data back or attempt a repair on the cbu file.

#9

I can’t read from backups either. This may have begun with 4.0.7.; my incremental backup worked but that may have been prior to 4.0.7. update.

Neither the full backup nor its increment are readable/mountable; they are stored on a local partition.

Logs are attached.

[attachment deleted by admin]

#10

Try to copy the backup file on an internal drive or network drive.
It seems to be an issue with the destination.
Please post the logs compressed (%TEMP%\ComodoLogsFolder) when you attempt to mount it.

Thanks

#11

Error 29 was fixed in 4.0.7 build.
The problem was with backup, so you might need to recreate the backups.
If you want to restore the data, it should all be restorable but error 29 may occur at the end of the restore process.

Thanks

#12

I have moved my 211 GB CBU File to the main hard drive and tried to mount. Here are the log files you wanted.

Thank you
Rich

[attachment deleted by admin]

#13

Thank you for the logs.
The problem is caused by indexation data in cbu file which was fixed with 4.0.7 version, but the backup is created with an earlier version.

To avoid the issue, try to restore the files to a new location Uncheck the “restore to default location” option in restore step 2 and set the restore location an empty folder.
When restoring, please enable logging to file in restore step 3 and post the log if any issues are encountered.

Thanks

#14

Attached is my compressed log and screen shot of the failed restore at 43%. I really want to get the user folder back.

Thank you

[attachment deleted by admin]

#15

Please try again to restore with the attached GUI.exe (place it in the installation folder)
Please, make sure that logging to file is enabled in restore step 3.
The problem should be fixed.

Thanks

[attachment deleted by admin]

#16

Thank you so very much Emanuel. My data is back. I did get an error 29(read error) during the restoration of properties. Can that be fixed? If not, not a biggie, my data is back!! I have attached the log. :-TU ;D 8)

[attachment deleted by admin]

#17

That was fixed already.

The error also occurred while restoring (at the end), but the issue is with the backup file so it can’t be avoided unless the backup file is created with 4.0.7.14 and later versions.

Thanks