Salta al contenuto principale

Error backup date cannot be found.

Thread needs solution

I am running True Image Home 2010 (build 7,046)
I get the error backup date cannot be found.
The date is marked in red in the calender.
I thought that this version has corrected this problem!
I think it has something to do with consolidation.

Can anyone help me with this problem?

0 Users found this helpful

Anacapa,

A little more information is needed.

Where are you imaging to? Same disk another partition, another internal drive or an external drive?

What type of task and schedule is causing the problem?

Does running a manual task work?

When you look on the drive that holds the image(s), can you actually see the image or part of the archive that is causing the problem? In other words, is it making an image of some kind and then reporting it as failed?

If you are running Vista or W7, posting a snip image of the archive would be useful.

With 64bit Windows 7, getting same errors occasionally.
Imaging to external drive.
Actually, it appears that all has been imaged OK. Can see files there.
Scheduled running and manual running both produce errors.
I am not sure what snip image of archive means, but here is part of the listing on the external drive to which the image is put:

MyBackup8_15_20109h21m_Map_6 Day Differential Then Full.tib
>MyBackup8_15_20109h21m_Map_6 Day Differential Then Full
>>C:
>>D:
>>E:

Note that only C: is included in the scheduled tasks. D: is an empty DVD drive and E: is a "Removable Drive". D: Data does show up via the archived listing, however. (It may be related to the partitions on C:\.) There is nothing included under E:. All C: seems to be there OK.

Here are the first few folders listed under D:
D:
>boot
>dev
>etc
>home
>initrd

Note that for several days, no backup errors were generated. Going to a new complete backup, the built-in optional selection after 6 days of incremental, may have something to do with it, but I am not sure. But the error first showed up when the scheduled full backup was triggered. I then waited a day, and the scheduled event produced another full backup instead of the expected incremental...which also produced this error. Then I did a manual operation after the scheduled full backup...which also produced this error...which also generated a full backup instead of an expected differential. This suggests a link between the scheduler and this error, but for now, it looks like this ability...automatic scheduling of 6 incremental between full backups...is broken.
If this continues, I will try a scheduling of full backup weekly plus another of daily incrementals to see what happens...pending further info developments here.

I am also getting some "no such script" errors which return after being eliminated via the Scheduling Manager. They are removed thereby and are no longer in the list...but a week later they have returned. I have no idea as to whether these are tied together or not. [I will later on add this paragraph to the thread that is addressing that error specifically.]

PS Just noticed that all errors followed a consolidate Backup operation as listed in the event log.

The error follows this information entry in the logs:
Consolidate Backup Archive Location: [tib file name with path] Destination [tib file name with path]

The Destination tib file name with path is identical to the Location tib file name with path except that it has appended thereto one of those script strings.

So I guess this is a consolidation problem...

Sam,

1. A Snip Image is one made with the Windows 7 Snipping tool ( "start\programs\accessories", I have my copy pinned to the start button).

2. It would appear you might have a corrupted task script or the scheduler has become confused, if it is making full images when they should be incremental. Delete the task and make a new one. If that fails then you might need to download the Acronis task zapping tool to clear the TI database and start afresh.

3. I assume from your list of programs on your DVD drive, you have either a Linux CD in the tray or the Acronis Rescue CD.

Thanks for the quick response.
Thanks for the snip info...can't imagine why I have not run across that before...

Note that I edited my first reply with a PS....after what is may be a key observation.
The "first" full image is being made at the right time...following a 6 day incremental schedule. The problem occurs when handling the resultant consolidation. This occurs at the "correct" time as scheduled. However, when then run manually, there is another Full Image then...along with the error.
When this is followed with a non-scheduled manual run, the new image is created and no error results.

I am already familiar with the task zapping tool for other reasons. But to go there without really knowing what is causing the problem bothers me...since the problem may recur.

But here is something odd: The DVD tray is empty. Has been for weeks.

But even with today's manual run, with the DVD drive still empty, I get several non-empty folders and a few small files mapped to the D: drive. The D: root files have the following names: cdrom, initrd.img, initrd.img.old, lib64, vmlinuz, vmlinuz.old

So, as you have also concluded, I think they are really from a linux partition or portion thereof lingering on in the C: Drive after updating from an XP along side a Linux partition to a Windows 7 without (supposedly) such Linux partition. Is this a source of trouble here? If so, how do I prevent this? (I do not care if this is there if it otherwise poses no problems.)