TIH 2013 is getting naming of incremental backup chains completely mixed up

Frank, Just curious. Could you provide some information, please. Hopefully we will be able to provide some recommendations.

1. Does your destination storage folder contain the files of several tasks or only one task?

2. Has these tasks been edited?

3. How do you initiate the backups? Do you open the program and click "Backup now" option; or do you use a desktop shortcut to start the backup? If shortcut used, was the shortcut created using the "Backup settings" shortcut creation option?

4. Has your restored your system during the time these backups have accumulated?

5.Would you mind providing a screenshot of your backup files storage folder. Sort the contents and the display on date & time so the display sequence looks like my attachment below or in the same sequence as created.

Hi, and thanks for your reply. Here are the answers to your questions:

1. Does your destination storage folder contain the files of several tasks or only one task?

- One folder has only the the files of one task. The other folder also contains only the files of one task plus 2 files that do not belong to a specific task.

2. Has these tasks been edited?

- No

3. How do you initiate the backups?

- I always start the program and click "Backup now"

4. Has your restored your system during the time these backups have accumulated?

- It happened with and without a system restore. There was no difference.

5.Would you mind providing a screenshot of your backup files storage folder. Sort the contents and the display on date & time so the display sequence looks like my attachment below or in the same sequence as created.

- Well, I would like to but first I have to find out how to copy a screenshot into a comment.

OK, no screenshot but the file list:

File list of F:\Backup\Data\Notebook

08.02.2013 09:02

.
08.02.2013 09:02 ..
06.01.2013 16:39 47.298.742.784 Daten_2013-01-06_full_b1_s1_v1.tib
12.01.2013 19:17 116.267.008 Daten_2013-01-12_inc_b1_s2_v1.tib
29.01.2013 08:35 47.519.283.712 Daten_2013-01-29_full_b2_s1_v1.tib
02.02.2013 12:55 118.305.280 Daten_2013-02-02_inc_b2_s2_v1.tib
08.02.2013 08:54 373.983.744 Daten_2013-02-08_inc_b1_s3_v1.tib
08.02.2013 09:02 68.859.392 Daten_2013-02-08_inc_b1_s4_v1.tib
6 files, 95.495.441.920 Bytes
2 Directories, 788.950.061.056 Bytes free

File list of F:\Backup\System\Notebook

08.02.2013 08:35

.
08.02.2013 08:35 ..
08.02.2013 08:45 29.965.124.096 SystemFortlaufend_2013-02-08_full_b1_s1_v1.tib
16.11.2012 13:14 7.687.675.904 Win7-Basis.tib
19.11.2012 09:27 11.484.876.288 Win7-Grund.tib
3 files, 49.137.676.288 Bytes
2 directories, 788.950.061.056 Bytes free

Script file for data backup:
[common_options allow_multi_volume_snapshot="false" allow_reset_archive_bit="false" app_settings_backup="false" description="" exclude_by_mask="true" exclude_hidden="false" exclude_system="true" execution_count="15" fast_incremental="true" ignore_encryption="false" increment_type="incremental" ocb="false" rotation_count="5" rotation_scheme="1" skip_security="false" smart_backup="false" take_screenshot="false" use_vss="false"] [/common_options]

[stream_options allow_silent_media="false" cache_network_write="false" compression_level="normal" encryption_algorithm="none" format="tib" freespace="0" ignore_bad_sectors="false" reattempt_count="5" reattempt_on="true" reattempt_pausesec="30" silent_asz_cleanup="true" silent_mode="false" type="file" ver="1"]
[quota chain_count="2" scheme_flags="18" type="8"][/quota]
[/stream_options]

[archive_options check_network_timeout="false" id="6914428215463011033" network_timeout="0"]
[volumes_locations>
[volume_location uri="F:\Backup\Data\Notebook\Daten_2013-01-06_full_b1_s1_v1.tib" volume_id="2317485564"]
[volume_location uri="F:\Backup\Data\Notebook\Daten_2013-01-12_inc_b1_s2_v1.tib" volume_id="116080184"]
[volume_location uri="F:\Backup\Data\Notebook\Daten_2013-02-08_inc_b1_s3_v1.tib" volume_id="1489526442"]
[volume_location uri="F:\Backup\Data\Notebook\Daten_2013-02-08_inc_b1_s3_v1.tib" volume_id="1489526442"]
[volume_location uri="F:\Backup\Data\Notebook\Daten_@date@.tib" volume_id="0"]
[/volume_location][/volume_location][/volume_location][/volume_location][/volume_location][/volumes_locations]
[/archive_options]

System backup script:
[archive_options check_network_timeout="false" id="7144446309723714420" network_timeout="0"]
[volumes_locations]
[volume_location uri="F:\Backup\System\Notebook\SystemFortlaufend_2013-02-08_full_b1_s1_v1.tib" volume_id="430986975"]
[volume_location uri="F:\Backup\System\Notebook\SystemFortlaufend_@date@.tib" volume_id="0"]
[/volume_location][/volume_location][/volumes_locations]
[/archive_options]
[common_options allow_multi_volume_snapshot="false" allow_reset_archive_bit="false" app_settings_backup="false" description="" exclude_by_mask="true" exclude_hidden="false" exclude_system="false" execution_count="2" fast_incremental="true" ignore_encryption="false" increment_type="incremental" ocb="false" rotation_count="5" rotation_scheme="1" skip_security="false" smart_backup="false" take_screenshot="false" use_vss="false"]
[stream_options allow_silent_media="false" cache_network_write="false" compression_level="normal" encryption_algorithm="none" format="tib" freespace="0" ignore_bad_sectors="false" reattempt_count="5" reattempt_on="true" reattempt_pausesec="30" silent_asz_cleanup="true" silent_mode="false" type="disk" ver="1"]
[quota chain_count="2" scheme_flags="18" type="8"][/quota]
[/stream_options] [/common_options]

Hi FS,

See attachment #5 inside signature below for information on uploading attachments, etc. Usually the uploading an attachment will suffice without going to the extra effort of displaying the capture.

As I reviewed your information, I believe your 2013-02-08-inc-b1_s3_v1 was caused by your restoring your system sometime after Feb2.
After the system restore, the s3 would have been the next in line for numbering as TrueImage was not aware of the b2 backup--thus you got b1_S3 which was the next number due--since the system was put back to what it was sometime Feb 2-Feb 8.

My experience has been that after a restore, (cease to use the old tasks) it is best to create new tasks and new storage folders as TrueImage cannot exactly pick up exactly where it left off as there are internal changes we do not see.

In Summary, my belief is your results are typical where a restore has taken place. Starting over with new task is usually the easiest fix or workaround. Even if you had done a restore using a backup done 5 minutes prior, the program would note there is unseen differences and the next backup would end up being slightly different in number like a 2013-02-08-inc-b1_s3_v1-1.

I am "guessing" that the system backup was accidentally put in the same folder as the other two files when the task was created--but that is only a guess.

My suggestion is just start over is the easiest solution.
Good luck.

You can also see these "-1" file show up when you edit the task, and change the retention rules, or backup scheme for example. As Grover's alluded to, don't edit tasks. Create new ones when changing the backup name, scheme, retention rules or destination.

Thanks for the answers.

Yes, the system restore does explain the current situation. However, the other examples all happened when there was *no* system restore. Especially the case where there was a file "backp_inc_b1_s7_v1.tib". The backup job states 1 full backup and 5 increments. How can there ever be an "s7" file?

My impression is that Acronis has never managed to get this right and it is worse in TIH 2013 than it was in TIH 2010 (the version I used before).

I know that editing tasks does only get everything mixed up so I never edit a task after it has been created.

Hi FS,
You wrote in your original post:

backp_full_b1_s1_v1.tib
backp_inc_b1_s2_v1.tib
backp_inc_b1_s3_v1.tib
backp_inc_b1_s4_v1.tib
backp_inc_b1_s5_v1.tib
backp_inc_b1_s6_v1.tib
backp_full_b2_s1_v1.tib
backp_inc_b1_s7_v1.tib #7 being discussed
-----------------------------
I can understand your frustration. As I understand it, once the restore occurs (or an edit) , the next backup would reset the inc counter so your 5 new inc would be added to the existing inc count. Most likely, the upcoming 8th would have been a new chain starting with b2 and because there is already a b2, it would have abnormal numbering. This type behavior is why whenever I do a restore, I cease to use the existing tasks and create new tasks whenever I do a restore or need to change a parameter. I agree it is not an optimum solution but the solution works and is a only a minor inconvenience. I honestly do not know what solution Acronis could offer which would be the correct solution for all users when an existing backup chain exists and the numbering is already in process.

Hi, GroverH,

as I said before there was *no* system restore before this. I only had a restore once a few weeks ago. All the other cases I showed have *nothing* to do with a system restore. No system restore. No.

Regards,

Frank

Hi Frank et al,
I have been having the exact same problem. Also no System Restores involved:

Attached is a picture showing somewhat proper naming for some several sequences:
full_b14_s1, inc_b14_s1, s2, s3, s4, s5, s6,
full_b15_s1, inc_b15_s1, 23, s3, s4, s5, s6,
full_b16_s1, inc_b16_s1, s2, s3, s4, s5, s6,
full_b17_s1
then arbitrarily reverting to
inc_b12_s16, s17...

Notice also the crazy extensions on full_b13_s1_v1-3, inc_b13_s2_v1-3, and inc_b13_s3_v1-2

I too wish this would be fixed.
Any explanations or solutions?

I'm having the same problem with True Image 2014. I do an incremental full disk backup once a day and save it to an external hard drive in a specific folder. I also do an incremental file backup for my Outlook, Favorites, and My Documents 4 times a day and save it to a different folder. While it seems to be storing the information correctly, the backup/recover page will usually say the full disk backup has not yet taken place. I have been an Acronis user since 2008 and prior to True Image 2013 never had a problem. Then at the end of last year there started to be these issues. Frankly that's why I upgraded to 2014 assuming the problem had been corrected.

When I do a simulated "recover" it only does a file recover and intersperses the full disk backup with the file recovery. My concern is that if I had to do a full disk restore it wouldn't work.

Lenny,
Would you mind doing a screen capture of your main menu showing the listing of tasks.
Also, a captue of storage folders showing the listing of tib backup files.
Before capturing the storage folders, sort the folders on
Detail and then on date/time.
The display should show the tib files listed in date/time sequence as shown in posting #1 above.

This problem seems to be occurring when consolidation is involved.
Which option do you havet set? Automatic cleanup or consolidation?
Maybe a capture of your backup schemes would help.

How is the storage disk attached? Is this NAS or network involved or usb3?