Weird Backup file names

1 . The backup numbering confusion was caused by the first original task naming the backups to be "My partitions" and along comes the next new task but it also allowed the name "My Partitions" to be assigned as the task name so the result is two tasks with the same tib backup file name and both the program and the user become confused--which would be normal in that circumstances. This problem continues into #2.

2. The naming confusion relates to a user learning curve problem due to the complexity of the program file naming.
First, there is the name assigned to the tib backup file name; and then there is an additional separate task name. The both may be alike or they can differ. It is up to the user to keep the name separated but that is not in the thought process of a new user.

As the task was being created, the task started out with the default name of "my partitions" being assigned to the "backup file name" which means the default file name for the task name also started out as "my partitions". You did change the name assigned to the task (also known as "Backup name" but you did not know to also change the name assigned to the backup file. The task name and the backup tib file name are two different entities. Normally, the correct name as to be applied to the backup files name when you are in creating the name and path inside the storage folder directory tree. Changing the task name (or backup name) does not change the tib backup file name.

3.

I only want one full backup on Drive E: because I am running out of space.

Not sure I am understanding in that all the files you have illustrated are stored on Drive E. Some on the root folder and others inside the "My Backups" folder. Also be aware that the procedures used by the program NOT to delete the oldest file UNTIL a new replacement has been created. This worsens the space situation in that you must provide for that temporary space until after the new full has been created. Perhaps you should be looking for additional storage space.

4. You need to stop using the existing Liz-Full backup task and start fresh with a new task and point the new task into a folder such as E:\MyBackups\Liz Full_Backups. My policy is to always create a new folder or sub-folder for each task. Had you done this, the current mixing of backup names would not have occurred. The would still have been the same but each backup storage would have been in different locations. I will try to create you an example of how to set the file naming but it will not be at least until Monday night.

5. Look at the next link for an example of what you should expect with a new task scheme set to delete after 7 days. Your current does not but a new replacement can.

The first deletion should occur 7 days after backup B1. s6.v1 is 7 days old, at which time the first 6 backups (chain 1 will be deleted in its entirety). B2 will have begun and s2-S6 will be created. After b2. s6.v1 becomes 7 days old, it will be deleted. Or that is the way it is supposed to work and your example shows none of this. This example illustrate the deletion poliicy you can expect based on your settings of 5 inc and delete older than 7 days.

http://forum.acronis.com/forum/45927

Your biggest problem is the learning curve which is normal for us all.

Edit-Addendum:
Here is a video link to show you how to assign a custom name to the tib backup file and change the task name (also called backup name) to a different name. This was put together quickly but still should be helpful. The storage folder name can be prior created or created while creating the task name. In viewing, you may have to move the verical scrool bar so you can see more when things are happending at the bottom of the screen.

http://screencast.com/t/IaxVq1tQME

I have a real problem with this software. Why do I have to have a 'learning curve' to get rid of one backup and start a new one. This is way too complicated. Tell me how to get rid of all the disk backups I've got on the system with their associated links and files, so I can start fresh. I am about to ask for a full refund and get a program that doesn't require a degree in programing to make work.

Frustrated user

I understand your frustration which is why I am trying to assist. The video can help.

Don't forget you only have a 30 day window from date of purchase to qualify for a refund.

Data stored in the archives.xml file.
C:\ProgramData\Acronis\TrueImageHome\Database\archives.xml

The xml file can be renamed or deleted and will be automativally recreated.

ALL tasks will need to be recreated and pointing to new storage folders.

To get rid of all the history which tracks the backups, rename the archives.xml files to old-archives.xml
The file will be auto-recreated.

If any tasks remain, delete the tasks. To do so, in upper right corner, (just to left of search Window) ,there is a double gearwheel.
Click the downarrow. Clck the "Remove from list" and then select the "All backups".
It may pause the computer for a minute or so and the result will be all tasks listed on your main screen (if any) will be gone.

If you want to physically delete your actual tib backkup files, you can use the Windows search feature and search for *.tib across all your disks and delete any you fnd via Windows explorer. I would only do the file delete as a last resort and keeping at least one good full backup until you have better replacements.

Another option would be to uninstall the program and then re-install.

For new users who have owned their product less than 30 days, support direct from Acronis is available rather than help from other users as provided by the forum.

Once the product has been registerd, owners of less than 30 days can contact Acronis support via the LIVE CHAT opton or via email.
More information about direct support is available along the left margin of this webpage.

Seems to be working now