Shraddhan
June 9th, 2006, 12:24 PM
I started up TI9.0 build 3567 in order to merely find out its build number. Nothing else. I opened a can of worms. I was immediately confronted with the following message:
"C0064006C: Incremental backup is not possible. The file you have chosen is not the Acronis True Image backup, or the file is corrupted..." etc.
The point is, I did NOT choose any file! I merely started the program.
Earlier today, I added a partition in previously unused hard disk space, and installed the Vista operating system there. My backups used to be made to an external USB drive with label M. The new partition now has this label, and the USB drive is now labelled N. Could this be the reason for this message?
But why should the message appear anyway, seeing that I did not even select a task? The message text continues:
"Do you wish to proceed with the current file name? If you click OK, the chosen file will be overwritten and the full backup will be created." - but I didn't want to do anything in the first place, and there is no chosen file that I know of. Moreover, the message box does not have a button labelled OK.
The last paragraph reads:
"Otherwise, if you want to create an incremental backup, click Cancel and choose the valid archive file name..." - no, I do not want to create an incremental backup either. And there is no button labelled Cancel.
So I clicked on No and looked at the task log. Apparently TI had earlier started up a scheduled backup to the partition with letter M, which is now the Vista partition. So:
(1) Why didn't it simply start to create a new backup on this partition? From time to time I update the generations of the backup files. When I do this, TI finds no existing backup and does a full backup, without comment. Is the problem due to a missing destination folder, rather than an empty one?
(2) Why was there no warning from TI that it had failed? I have a backup done evey day, and I assume that they run properly. I don't want to have to check the logs every day just to find out if there was a problem. (If TI emailed me to tell me to check the logs, that would be fine. I could implement a program to do this, run automatically at the end of the backup, if only I knew how to detect that TI had failed.)
(3) And of course I can not edit the task because it now has an invalid destination path, and tasks with invalid destination paths can NOT be edited, in spite of the advice to do so - or has this been fixed by now?
Shraddhan
"C0064006C: Incremental backup is not possible. The file you have chosen is not the Acronis True Image backup, or the file is corrupted..." etc.
The point is, I did NOT choose any file! I merely started the program.
Earlier today, I added a partition in previously unused hard disk space, and installed the Vista operating system there. My backups used to be made to an external USB drive with label M. The new partition now has this label, and the USB drive is now labelled N. Could this be the reason for this message?
But why should the message appear anyway, seeing that I did not even select a task? The message text continues:
"Do you wish to proceed with the current file name? If you click OK, the chosen file will be overwritten and the full backup will be created." - but I didn't want to do anything in the first place, and there is no chosen file that I know of. Moreover, the message box does not have a button labelled OK.
The last paragraph reads:
"Otherwise, if you want to create an incremental backup, click Cancel and choose the valid archive file name..." - no, I do not want to create an incremental backup either. And there is no button labelled Cancel.
So I clicked on No and looked at the task log. Apparently TI had earlier started up a scheduled backup to the partition with letter M, which is now the Vista partition. So:
(1) Why didn't it simply start to create a new backup on this partition? From time to time I update the generations of the backup files. When I do this, TI finds no existing backup and does a full backup, without comment. Is the problem due to a missing destination folder, rather than an empty one?
(2) Why was there no warning from TI that it had failed? I have a backup done evey day, and I assume that they run properly. I don't want to have to check the logs every day just to find out if there was a problem. (If TI emailed me to tell me to check the logs, that would be fine. I could implement a program to do this, run automatically at the end of the backup, if only I knew how to detect that TI had failed.)
(3) And of course I can not edit the task because it now has an invalid destination path, and tasks with invalid destination paths can NOT be edited, in spite of the advice to do so - or has this been fixed by now?
Shraddhan