Backup failed, specified file does not exist
From my research (citing this article: https://goo.gl/1kUM4Z), it seems my issue may be one of portable/external drive location.
I changed my USB/card reader on my PC between backup operations, which changed the associated drive letters. Could it be that although I re-selected the correct drive as destination, ATI is still looking for the initial backup tif file at the previous drive letter?
Here's the respective log file....
2018-05-26T10:22:55:042-06:00 22440 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2018-05-26T10:22:55:043-06:00 22440 I00640002: Operation HAF922 started manually.
2018-05-26T10:22:58:559-06:00 22440 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2018-05-26T10:22:58:561-06:00 22440 I013C0000: Operation: Backup
2018-05-26T10:23:03:605-06:00 22440 W000B007F: Error 0xb007f: The initial full backup version is not accessible at the moment.
| trace level: warning
| line: 0x65e40aa0b48718c
| file: c:\bs_hudson\workspace\332\products\imager\archive\impl\operations\archive_operation_backup.cpp:763
| function: TrueImage::Archive::BackupArchiveOperationImpl::TraceFirstVolumeExistance
| line: 0x65e40aa0b48718c, c:\bs_hudson\workspace\332\products\imager\archive\impl\operations\archive_operation_backup.cpp:763, TrueImage::Archive::BackupArchiveOperationImpl::TraceFirstVolumeExistance
| $module: ti_demon_vs_11530
|
| error 0x40007: Error occurred while opening the file.
| line: 0xf35f747b3b21fc55
| file: c:\bs_hudson\workspace\332\core\file\windows\winnt_dir.cpp:1356
| function: winnt_dir::iterator::iterator
| line: 0xf35f747b3b21fc55, c:\bs_hudson\workspace\332\core\file\windows\winnt_dir.cpp:1356, winnt_dir::iterator::iterator
| function: FindFirstFileW
| path: \\?\H:\HAF922_full_b1_s1_v1.tib
| $module: ti_demon_vs_11530
|
| error 0xfff0: The request could not be performed because of an I/O device error
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\332\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\332\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x8007045d
| $module: ti_demon_vs_11530
2018-05-26T10:23:30:805-06:00 22440 E00040011: Error 0x40011: The specified file does not exist.
| trace level: error
| line: 0x84b9b45b3f5f386f
| file: c:\bs_hudson\workspace\332\core\backup\archive.cpp:248
| function: `anonymous-namespace'::UniFileSpace::OpenDirOfFile
| line: 0x84b9b45b3f5f386f, c:\bs_hudson\workspace\332\core\backup\archive.cpp:248, `anonymous-namespace'::UniFileSpace::OpenDirOfFile
| $module: ti_demon_vs_11530
2018-05-26T10:25:17:473-06:00 22440 E01E50023: Error 0x1e50023: The specified file does not exist: .
| trace level: error
| line: 0x4d3f22948e29f1cd
| file: c:\bs_hudson\workspace\332\products\imager\archive\impl\utils.cpp:246
| function: `anonymous-namespace'::GenerateGuiErrorWithPath
| line: 0x4d3f22948e29f1cd, c:\bs_hudson\workspace\332\products\imager\archive\impl\utils.cpp:246, `anonymous-namespace'::GenerateGuiErrorWithPath
| $module: ti_demon_vs_11530
|
| error 0xb03e9: Cannot open the backup.
| line: 0x65e40aa0b486f4a
| file: c:\bs_hudson\workspace\332\products\imager\archive\impl\operations\archive_operation_backup.cpp:185
| function: TrueImage::Archive::BackupArchiveOperationImpl::DoPrepare
| line: 0x65e40aa0b486f4a, c:\bs_hudson\workspace\332\products\imager\archive\impl\operations\archive_operation_backup.cpp:185, TrueImage::Archive::BackupArchiveOperationImpl::DoPrepare
| $module: ti_demon_vs_11530
|
| error 0x4000f: Canceled.
| line: 0x1d8eab676a3f694d
| file: c:\bs_hudson\workspace\332\products\imager\archive\impl\operations\archive_message_callback.cpp:804
| function: TrueImage::Archive::ArchiveMsgReadCallbackProcessor::ProcessOpenError
| line: 0x1d8eab676a3f694d, c:\bs_hudson\workspace\332\products\imager\archive\impl\operations\archive_message_callback.cpp:804, TrueImage::Archive::ArchiveMsgReadCallbackProcessor::ProcessOpenError
| $module: ti_demon_vs_11530
|
| error 0x40011: The specified file does not exist.
| line: 0x84b9b45b3f5f386f
| file: c:\bs_hudson\workspace\332\core\backup\archive.cpp:248
| function: `anonymous-namespace'::UniFileSpace::OpenDirOfFile
| line: 0x84b9b45b3f5f386f, c:\bs_hudson\workspace\332\core\backup\archive.cpp:248, `anonymous-namespace'::UniFileSpace::OpenDirOfFile
| $module: ti_demon_vs_11530
2018-05-26T10:25:17:517-06:00 22440 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bce5f
| file: c:\bs_hudson\workspace\332\products\imager\demon\main.cpp:617
| function: main
| line: 0x9f2c53c72e8bce5f, c:\bs_hudson\workspace\332\products\imager\demon\main.cpp:617, main
| $module: ti_demon_vs_11530

- Log in to post comments

Scott, when you changed your USB/card reader, what actually changed in respect of your backup drive here? Did you change the backup drive at all, or is the backup drive connected via the changed components here?
If you are using the same original backup drive for the task, with the same drive letter assigned and your task is still producing this error, then I suspect that the hardware change has caused the drive to perhaps get a different unique identifier, making ATI believe it is a different drive?
It might be easiest to remove the current backup task, then use the option to 'Add existing backup' and select your full backup image file from the drive to be added. This will create a task with the full file name in the GUI where you will need to trim the task name then reconfigure the task settings again.
- Log in to post comments

Hardware...only the USB/card reader hub was changed; portable/external drive is the same. Existing backup file seems to be good, as I can access the data.
I followed your instructions to 'Add existing backup'. Initially, it through the below error. I re-selected the destination and now it seems to be running properly.
"The backup cannot be started. Plug in the external drive containing the files of this backup."
- Log in to post comments

Scott, good to hear that the backup now looks to be running properly again.
- Log in to post comments
In reply to Scott, good to hear that the… by truwrikodrorow…

It's running...thanks.
- Log in to post comments