Skip to main content

Backup numbering

Thread needs solution

I have scheduled a disk backup to run twice a week. The backup made today has the exact same number as the previous one, apart from the date. See attachment. Can someone explain this. I would have thought the the number after the b would be different.

Attachment Size
untitled.jpg 26.51 KB
0 Users found this helpful

Martin,

You are correct normally the third image would have a 3 after it, I notice these are all full images.

Are you running the task manually? I notice there is a 4 day gap between the second and third image.

Do you have some kind of consolidation or maximum archive size set up?

This task is set to run on Wednesdays & Sundays. They are full images and created by the schedule and NOT manually. NO consolidation or maximum archive size set up

Martin,

I'm not able to try and replicate your problem right now, possibly from this Friday onwards.

Thanks for the reply. I'll await your response and hopefully others may have some ideas. The back is scheduled to run again tomorrow. I'll let you know how it is numbered.

Very strange, I can't think of a reason why it should have used the same number twice. This can happen if a task is run manually or an image is manually deleted instead of via TI.

I haven't got a full image only task set up at the moment, I'll set one up and see if I get the similar results to yours.

What is strange from your screenshot is that the first two are one day apart, not three days as expected.

Any chance, was the partition restored during the past few days perhaps folloiwng the backup 1 or 2?

Was the task edited and any changes made in the configuration?

How was the first backup created? Via the Backup now or manually or created via the scheduler?

I think you might have it, I did have to do a restore last week following a virus. Will the back up numbering continue as it should from now? The task is set to run later on today so I guess I'll find out then.
The task has not been edited.
The first back up was created after setting up the task and checking the option to run the task now. The following backup was created on the scheduled date via schedule.

I think Grover has nailed the problem!

After a restore it is generally a good idea to either make a new tasks, or stop the current task and restart the schedule, True Image has no way of knowing it is now operating in an evironment that has been recovered, it will see that it hasn't made an image after checking the current system time against the last run time and attempt to carry on where it thinks it left off. This can cause confusion, especially if an image is restored just before a schedule is about to take place, you will end up with your older images overwritten in some circumstances. Hence the reason why a recovered environment should have new tasks assigned.

Thanks,
I have recreated the task and set up a new schedule. Just need to wait and see how numbering goes. Hopefully all will be well