TI2013 Backup actually creating a clone

David Littleboy wrote:

All went fine, but no older chains deleted,

A new backup task will not delete old backups that were created with a different task. In fact, you wouldn't want it to do so. A backup task's limits will manage only the backups it (the backup task) creates.

I don't know what that first screenshot shows.

Grover's new backup and restore guides are very useful in explaining how to create tasks and how limits and chains work: http://forum.acronis.com/forum/29618

Screenshot1 showed the resulting backup, the other was the settings used.
I've re-set everything as per the guide (completely deleted the old task/backup set first)
I'll let you know how things progress
T/Y

Ok, well the backup has been running now successfuly since my last response, but while it is creating a new full version after xx increments it is not deleting the older full version or any incremental versions as was supposed to be set. (And I followed the guide)
Currently its likely to fail as out of space on the next run, and I'll need to start again from scratch.

You made changes or a new scheme so we do not know what settings you used. If you want answers about your current situation, show us a capture of your scheme and your storage folder. Sort your storage folder via details as per attached link.

Regarding your first capture1.jpg attachment. This does not provide any info. A picture of the storage folder would be better.

Regarding capture.jpg
As you chose incremental type combined with elapsed days, the program will not begin any deleteion until after 6 days after the creation of the last incremental 6. The reason for the delay is that any deletion of inc 1 or 2 or 3 will cause all newer incs of the same chain to be non-usable so instead, it has to wait until the end of the inc's before starting the day count. If you were to choose the dif type rather than the inc type, then the day count would begin on first diff file.

Each time you make a change, the count will restart or results may not be as expected. My suggestion is not to make any edits. If a change needed, start a new task pointing to a new empty sub-folder.

This was a completely new backup, all previous backups and storage had been deleted, so the previous images are not currently relevent.
The new backup/task was created as per your highlighted link (2)

Based on the information provided or assumed based on that info.
The last backup added was a full on August 10. If the task is still a "scheduled task", there should have been a backup added on Sept 10. The next scheduled backup is Oct 10 and it is expected to be
_inc_b2_s2_v1

If task acvtive, the backup will continue and complete all inc of b2 and complete the full-B3.
Immediately upon completion of Full_b3, chain1 or all of b1 and its files will be deleted to meet your criteria of maintaining a storage of 2 chains.

If the Sept 10 did not run because of a full disk indication, future backups will fail until additional storage space is provided via the removal of old backups.

The dates are dd/mm/yy (Month being October)
I had the backup running fine on the same size drive, but I had to reconfigure the partitions on other drives therefore my backup drive was given a new letter.
Subsequent I created a completly new backup, on the same formated drive, but silly me had forgotten to take pics of the previous succesfull settings, so they are all new.
Previously a full backup was made, then about 5 incremantal backups after this a new full backup was made, and the origonal full backup was deleted, I cannot remenber whether all incremantal versions were deleted at the same time, to start afresh.
This is what I'm wishing to get back to, does that make sense?
The backup drive being used is only 298gb
T/Y

Ok. New inc should be created on the 9, 10,11,12,13 of month 10
New full (b3) created on the 14th.
Seconds after b 3 (S1) created, then B1 (all slices )will be deleted leaving all of B2 and the full start of b3
Then, all will continue with the creation of all slices of b3 and the creation of b4,s1 and the deletion of B2 all slices,
And then continued repetition of each full created followed by the deletion of the oldest chain (all 6 slices).
Your escalator of backups is in motion.

It appears you have the settings to get what you want if the above is what you want.

At some point in the future, if you need to create a new task, perhaps change the drive letter on your storage disk to a high series (such as x or y or Z) so changes in insertion of flash drives or printers does not change your storage letter.