Direkt zum Inhalt

how to change backup name in TI 2016 to one of my choosing

Thread needs solution

Hi,

A few days ago I updated my TI 2013 to TI 2016. I have two external drives that I use for my backups. When using TI 2013 I could name my backups as I pleased so I knew which External Drive they were on when viewing all my backups on Acronis.

As an example when I backed up on my Omega external I would call it 'Omega C Drive and the date' and if backing up on my Aluratek external I would use 'Aluratek C Drive and the date'. That way I could quickly find it when using Acronis.

However now it just shows my C Drive Disk number and not the External Drive I am sending it too.

Can someone point me in the right direction on how to rename my backups as I previously did in TYI 2013?

Thanks and regards,

2harts4ever

0 Users found this helpful

Click on the round circle to the right of the drive number. You should see Rename in the menu that appears. Click on that and thus allow for renaming the disk.

Enchantech,

Thanks ... I decided to try what you said on the backup I just did to my Iomega external drive. First, I just put the word 'Iomega' in front of the disk drive number in the backup listing on my Acronis program. I then noticed I didn't get an option to 'recover files' so I went to my files on the external Iomega drive and inserted 'Iomega' before the same backup listing there too.

When I went back to my Acronis TI program, I then had the option to 'recover files'.

So, if I would put the name of my External Drive before the disk number BEFORE making the backup would it then automatically be listed the same way in the external disk files?

Thanks and regards,
2harts4ever

2harts4ever wrote:
So, if I would put the name of my External Drive before the disk number BEFORE making the backup would it then automatically be listed the same way in the external disk files?

Yes, that is what is supposed to happen (I have not confirmed that it works with ATI 2016; definitely worked with ATI 2015).

Ian

This link can help.
http://forum.acronis.com/forum/91956

Be careful about any change of name on the actual tib file. Acronis history file will be tracking the original name.
YOu may get a missing file error message on the file where a rename occurred via windows explorer.
Any rename function will apply to backups yet to come and will not apply to backups already completed.

IanL-S and GroverH,

Thank you both for your responses.

GroverH good to see you in my posts again. It has been several years since I started with Acronis TI and it seems you have always been here for me when I am in trouble. My upgrade to TI 2016 is from TI 2013 so I am struggling to get the hang of it.

Thanks for your patience as usual.

Regards,
2harts4ever

I just upgraded from Acronis 2014 to version 2016.  With previous versions I was able to name my saved file, for example: "160310 E6530 to WD5TB" so that each backup saved on the external hard drive was linked to the particular computer being backed up and the name of the drive in use along with the date of the backup.  This is useful because I have several external HDD's to back up to and several PC to back up.  This way when I go to recover a backup there won't be any mistakes matching the .tib file to the correct PC.

When i started using the Acronis 2016 version, I renamed the files the same way.  Now I'm getting all sorts of error messages like "Failed to open item E:\My backups\Entire PC (B-PC)_full_b9_s1_v1.tib"   When I make a backup with Acronis 2016, I can't find any option that allows me to choose the name of the bakup.  This default naming system does not allow me to keep track of the various Hard Drives and PC's that I mix the backups and PC's on.

How can I make backups with the naming conventions I used with Acronis 2014?

Thanks,  

Anthony Jordan

Anthony, when you create a new backup, you can always change the backup name to anything of your choosing - it just uses a generic one as a place holder, but if you don't change it, that's what it will use. You can always rename it though, by clicking on the drop down arrow next to the name (see screenshot).

 

Anhang Größe
345294-127273.jpg 57.14 KB

To control the actual name assigned to the tib backup file, the user must control or rename the task name before the actual backup occurs.
The name assigned to the tib file (true image backup) will be whatever name esists as the task name at time backup occurs, plus the addition of the ending suffux as described in the Backup Naming Link below, such as _Full_B1_S1_V1.

Once a tib backup file exists, the existing tib name CANNOT be changed/renamed, or backup becomes non-usable.
 All tib name controls must occur BEFORE the tib file is created. Once tib backup file created, renaming the task name will change only the name of future backups yet to occur, original tib name must/will/ remain unchanged.

So, to control the actual name of the tib backup file, the user must control or rename the task name before the actual backup occurs. Tasks can be created as non-scheduled tasks or later scheduled so ample time is allowed for fine-tuning the task name before the backup occurs. It is BEST that no two tasks have the same task name. I often precede my task name with a numeric number (each task number different) so the numbers can be seen along the left margin when all the task names appear together. This can help to keep the tasks identified.

     A backup file name has the following attributes:

         Backup name. (Assigned from existing task name)    
         Backup method (full, inc, diff: full, incremental, differential).
         Number of backup chain (in the form of b#).
         Number of backup version (in the form of s#).
         Number of volume (in the form of v#).

Backup File Naming

More detail about Re-naming backup tasks & tib backup files-- 2016-2015

2015 & 2016 versions --How to save a non-scheduled task.

Also note that it is more important than ever that the backup schemes be configured as custom automatic cleanup, so the program will delete the oldest chains automatically and manual deletion by the user is not needed. Custom Backup Schemes --All recent versions