Skip to main content

Backup disappears immediately so cannot be validated

Beginner
Posts: 1
Comments: 4

I tried to perform a regular backup but forgot to plug in the disk I use for backups. Having realised the error, I plugged the disk in and tried the backup again. This proceeded normally, but when the time came to validate the backup, it was unable to open the file. When I checked with Windows Explorer, it did not exist!

I tried the backup again. While it was proceeding, I checked that the .tib file it was writing to did exist. After completing the backup, it again couldn't find the file to validate it. I checked with Windows Explorer again, which showed it did not exist.

How can I get out of this cycle?

(Using Windows 7 and True Image Home 2012)

Legend
Posts: 43
Comments: 13041

Top

Neil, welcome to these User Forums.

It has been a long time since I used ATI 2012 but I do not remember ever seeing a problem such as you are describing, so it is very difficult to offer suggestions with so little information.

Have you checked what the log files show for this situation?

In reply to by Steve Smith

Beginner
Posts: 1
Comments: 4

Top

Hi Steve,

Thank you for your reply.

I actually perform 2 full backups every week on a 3-week cycle. The first is a partition backup of an external drive (J:/). This is the one which caused the problem. After 3 attempts, I tried the other backup, which is a disk image of my internal drive. This was successful.

If next week's backup (or the one in 3 weeks time, when this particular point in the cycle recurs) produces the same problem, I'll let you know. For the time being, I still have backups of the J drive that are 1 and 2 weeks old.

Where do I find the log files?

Regards,

Neil

Legend
Posts: 43
Comments: 13041

Top

Neil, please see the ATI 2012 User Guide: Backup and recovery tab

Operations menu

Clicking the gear icon in the box of a selected backup or right-clicking in the free area of the box opens an Operations menu containing the following items:

  • View log - click to open the log for the current backup.
Legend
Posts: 43
Comments: 13041

Top

See also the section for: Viewing log which shows how this looks.

In reply to by Steve Smith

Beginner
Posts: 1
Comments: 4

Top

Thanks Steve.

I have looked at the logs and transcribed them into a text file, which I have uploaded - maybe it means something to you. I tried the Knowledge Base but it couldn't find any entries with the error codes given in the logs.

ATIH2012 is no longer supported by Acronis.

Regards,

Neil

Legend
Posts: 43
Comments: 13041

Top

Neil, sorry but don't see any attached file for the logs.

In reply to by Steve Smith

Beginner
Posts: 1
Comments: 4

Top

It appears when I upload it, then disappears again! Trying again

Attachment Size
456233-150041.txt 4.08 KB
Legend
Posts: 43
Comments: 13041

Top

Neil, the log data shows a confused application in that it first creates your D:\My backups\Backup A2.tib file then deletes the same file before saying it had created it again but using no time to do so, then complaining that the file couldn't be found!

I would recommend using the option to Clone your backup settings and create a duplicate backup task, giving it a new / unique name then running that new backup.

The issue here may be some corruption in the Acronis database related to the problem backup task.

In reply to by Steve Smith

Beginner
Posts: 1
Comments: 4

Top

Hi Steve,

I created a clone from Backup A1 rather than Backup A2, in case there was some corruption in the Backup A2 settings that would propagate to the clone. Both backups are a simple backup of the J partition, just run in different weeks.

The clone was named (1)Backup A1 and I renamed it to Backup A20 then ran it.

I saw when it was running that it was backing up to D:/My backups/(1)Backup A1.tib. A bit annoying, but it ran and validated OK. Then I checked the D drive. The original Backup A1.tib had disappeared!

I don't know what will happen when I next run Backup A1 in a couple of weeks. Maybe I'll have to forget about cloning and delete the existing backups one by one and create them again from scratch.

Thanks for your help.

Regards,

Neil