Specified file does not exist
ATIH 2011 build 6868, Windows 7 64-bit
I created a new task (incremental). I thought I was starting a new backup sequence, but apparently TI didn't get the message.
I'm backing up to a 3TB USB drive.
This is what it said, in two e-mails about 10 minutes apart:
First e-mail
Normal Incremental Job Task is waiting for user interaction.
Description:
Information: Specify location of the volume 3.
Details: Click Browse to specify volume location, Retry to try again, or click Cancel.
Second e-mail
1 Information 7/27/2011 11:00:02 PM Operation Normal Incremental Job started.
2 Information 7/27/2011 11:00:16 PM Analyzing partition '0-0'...
3 Information 7/27/2011 11:00:16 PM Analyzing partition 'C:'...
4 Information 7/27/2011 11:00:17 PM Analyzing partition 'D:'...
5 Information 7/27/2011 11:00:18 PM Analyzing partition '0-0'...
6 Information 7/27/2011 11:00:18 PM Analyzing partition 'F:'...
7 Information 7/27/2011 11:00:20 PM Analyzing partition '0-0'...
8 Information 7/27/2011 11:00:20 PM Analyzing partition 'J:'...
9 Information 7/27/2011 11:00:25 PM Analyzing partition '0-0'...
10 Information 7/27/2011 11:00:26 PM Analyzing partition 'G:'...
11 Information 7/27/2011 11:00:26 PM Priority changed to Low.
12 Information 7/27/2011 11:00:27 PM Create Incremental Backup Archive From: Main Drive (C:) Compression: Normal
13 Information 7/27/2011 11:00:30 PM Pending operation 147 started: 'Creating partition image'.
14 Information 7/27/2011 11:00:30 PM Locking partition C:...
15 Information 7/27/2011 11:05:15 PM Backing up to file: "J:\My backups\Incremental_Backup_Chain35.tib"
16 Information 7/27/2011 11:17:56 PM Pending operation 144 started: 'Saving partition structure'.
17 Information 7/27/2011 11:17:56 PM Validate Backup Archive Location: "J:\My backups\Incremental_Backup_Chain35.tib"
18 Information 7/27/2011 11:17:56 PM Pending operation 3 started: 'Validate Backup Archive'.
19 Information 7/27/2011 11:28:20 PM The specified file does not exist.
20 Warning 7/27/2011 11:28:20 PM Specify location of the volume 3.
Click Browse to specify volume location, Retry to try again, or click Cancel.: ⎂Retry//⎂Cancel/
21 Information 7/27/2011 11:38:20 PM Specify location of the volume 3.
Click Browse to specify volume location, Retry to try again, or click Cancel.: ⎂Retry//⎂Cancel/: User response: ⎂Cancel
22 Warning 7/27/2011 11:38:21 PM Terminated by user.
So what is going on here?
In the second message, it says it is backing up to "...Chain35.tib" Where is that "35" coming from?
Why can't it find volume 3? Granted, I did move some backups around with varying degrees of success; but this was supposed to start from scratch. Does ATIH look for previous backups and try to pick up where it left off?
In any case, I decided to delete all of the backups and then the XML files in the database folder. I defined a brand new task (the same as the old one, except in name), and it is running now.
We shall see what we shall see, but I'd like to understand how I got into this pickle
When it validates, ATI validates the entire chain. Volume 3 is the third backup in the chain.
You did the right thing deleting the backup task and the database.
ATI is not supposed to work with GPT disks without the Plus Pack. http://kb.acronis.com/content/2974
The thing is, I was trying to start a new chain from scratch. I didn't realize it would try to pick up where a previous task left off.
Does that mean that if you set up two different tasks, they will share a chain? Does that happen even if you figure out how (more accurately, when) you give your archives a different name?
I blew away everything: tasks, database, and the .tib files themselves. That last caused me some anguish, not because I'm afraid of losing data (I'm a belt-and-suspenders kind of guy these days) but just on general principles.
Fortunately, I bought the Plus Pack in case I ever need to do a bare-metal rebuild. I hadn't planned on buying a new backup drive, but my old one was beeping and the manufacturer said it needed service. 3TB was attractively priced.
Of course, since I bought the new drive the old one hasn't beeped.
Unless the *.tib backup file is corrupt, it is never necessary to delete.
When you start a new task, it is best directed to a new folder which does not contain any prior tib backup files. The user does have a choice as to where the target folder is located and its name.
The 35 is probably saying it is the 5th incr on backup chain #3.
Unless the *.tib backup file is corrupt, it is never necessary to delete.
Since either ATIH was confused, or I was, or we both were, I figured a clean slate was best. In retrospect it would have made more sense to move them out of the way, but I was out of patience and past caring. I figured I didn't need those backups.
What, me worry?
Actually, my really critical stuff is backed up to the cloud and is also on a CD in a fireproof, waterproof safe. I don't know if the CD would melt in a really good fire, or not, but at least the safe floats.
When you start a new task, it is best directed to a new folder which does not contain any prior tib backup files. The user does have a choice as to where the target folder is located and its name.
It took me a while to notice that you can only set the .tib file name when you first create a task, even though the screen lets you do it later.
The 35 is probably saying it is the 5th incr on backup chain #3.
Wouldn't that be xxx(3)5.tib?
Whatever... the full backup and the first incremental did run without complaint.