Windows 7 with Ghost backup error on external USB drive

Asked By 30 points N/A Posted on -

I was struggling with this for the past few days.

The problem I have is: I need to schedule backups for different times for my HDDs which are M(9GB), N(18GB), O(15GB) and P(35GB). Everything goes fine till the backup job for P drive fails and gives the following error message.

Error EC8F17B7: Cannot create recovery points for job: Drive Backup of Projects (P:).
Error E7D1001F: Unable to write to file.
Error EBAB03F1: The requested operation could not be completed due to a file system limitation. (UMI:V-281-3215-6071).
I use Windows 7 (64-bit version) and Ghost 15 ( I have a separate login and the backups run under it.
The backup destination has the full right to read and write from my login.
Backup destination is an NTFS drive on an external USB drive.
Answered By 0 points N/A #152828

Windows 7 with Ghost backup error on external USB drive


There are several causes to this error message occur per the following below:

Problem 1. Hard drive problem for instance file system errors or bad sectors.

Solve 1. To avoid this problem, run the Windows Disk Error Checking Utility (chkdsk or f from a command prompt) / try read-through the option "Ignore bad sectors during copy" while the Backup Wizard is in progress.

Problem 2. Several USB devices are connecting to the computer.

Solve 2. You have to disconnect all devices except for the USB destination hard drive.

Problem 3. The USB drive are not seen in Windows.

Solve 3. You have to ensure the status of the drive in Windows disk management. If the drive has not seen or seen incorrectly in Windows, BESR cannot use that drive. You have to contact the manufacturer of your drive if this happens to ensure that, your BIOS and Windows settings are correct. Occasionally simply unplugging, and then plugging in the USB drive can bring it back online.

Problem 4. The SAN (Storage Area Network) Volume can be origin conflicts.

Solve 4. You have to update to the latest version. Frequently changes are making to be compatible with SAN volumes. If it is possible then disconnect the SAN to establish if there is a conflict with the SAN.

I hope you will be solving the problem.

Login/Register to Answer

Related Questions