Skip to main content

Getting rid of added stuff on backup names

Thread needs solution

I really wish to not have 2013 add things like _full_b1_s1_v1 to the backup name

I simply wish a full backup with name like "computer-A.tib" that I can overwrite as I wish

and keep my own - version A, B, C, D etc..

I write backup to a network share area -- then I sync directories and files to another area on the server using a sync tools that updates "changed files"

the acronis "need" to add the extra to the file name means too many back up file names and I cannot simply do 2-4 full backups that I rotate as I wish..

anyway to get back control of names -- like I had with 2010

0 Users found this helpful

You can, when you create a new backup task, name it what you want. At the point that you select the destination location, you may enter your desired filename for the backup. That's the only time that you can choose a name. If you try to edit the task later, you'd just be changing the name of the backup task but not the filename.

Note that True Image will still append that other information to your backup name, to provide a consistent means of identifying various characteristics of the backup type.

Tuttle, what Steve wants is to be able to name his backups without the extraneous information ATIH-2013 appends to the name of the backup. For example, if he wants to name his backup "computer-A.tib" he does not want anything added to the end of that name. That is what he meant when he mentioned "anyway to get back control of names -- like I had with 2010".

There is no way to avoid the "backup naming rules" ATIH-2013 appends to the name of the backup.

If Acronis really wanted the "backup naming rules" it introduced with ATIH-2013 to be "flexible and convenient" (as they say it is) they would've made it an option and not a hard requirement.

Paul Adrian wrote:

Tuttle, what Steve wants is to be able to name his backups without the extraneous information ATIH-2013 appends to the name of the backup.

I understand what he wants, and I explained that it is not possible.

it should be a option.........................

I have used Acronis versions for a long time.. I have a clean process to backup and recovery my various PC's --

this mandatory "add" is making extra work for me and likely other -- it clean up and control of the number of backup images

I write them to one place on my network and replicate/sync them this area to 2 other places.. The size of this stayed relatively static when I controlled the names of he rotating backup and the sync software updated the newer file with same name

this new naming is growing files of various names in my sync location and I have to go manually clean up

I finally needed to switch from 2010 as I have a new laptop with windows 8 and GPT drive.. even this is not fully bug free in current 2013, but I have a way to back and recovery.. hopefully an new version with bugs fixes is out soon and things will be better.. I would like this new naming feature to be optional.............. and I have the choice to name like I did in 2010.

Steve, I agree with you that it should be an option, and I voiced that during the beta testing for ATIH-2013 - hopefully if they hear it enough they will consider making it an option.

It is impossible to know how many people have not moved to ATIH-2013 because of that, but if they hear it enough and realize it's costing them money they'll make the change.

Paul Adrian wrote:

It is impossible to know how many people have not moved to ATIH-2013 because of that, but if they hear it enough and realize it's costing them money they'll make the change.

I doubt it's a significant number. I doubt that filename suffixes are a deal breaker.

If you think that it should be an option, by all means suggest it to Acronis. We MVPs don't make the decisions, so I'm just reporting what the situation is, not endorsing it nor criticizing it. For me the suffixes make sense, for you maybe not.

I'm not quite understanding how the naming convention is causing extra files to appear in an archive.

True Image ought to be able to clear up an archive automagically, if you could explain how your prefered system works as opposed to how TI works, it might help in explaining to Acronis why some flexibility is needed. It has to be said, that many people in the past requiring support have been confused as to what files are what in their archive, hence one of the reasons Acronis added the type and slice number to image names.

Just an aside, ABR11.5 Workstation still uses the old style naming convention, you might find the added flexibility in making images useful, although it does require more input from the user than TI, unlees of course one of the inbuilt alogrithms is selected.

Unfortunately images produced by the two products are not readable between them.

I never make incremental backups myself, always full, and name my backups after which ATIH2013 adds in all cases

_full_b1_s1_v1

e.g. today's is "Inteli5_2013-06-24_full_b1_s1_v1.tib".

I wrung my hands about the extra verbiage at first, but in the end it's a don't care to me so long as I can ID the backup reliably. No doubt Acronis added this for reasons of people renaming backups such that restores didn't work properly. But in any case they should have an option to turn it off for power users.

tomf wrote:
and name my backups after which ATIH2013 adds in all cases

_full_b1_s1_v1

Yes, as we have confirmed, ATI will always add the identifying suffix. There's no debate about it, it is always added.

Do not forget the part where I say -- I sync replicate by images to 2 other storage areas.... the added names = totally new file versus overwrite an old one in my 2-4 file full backup rotation scheme.....................

extra work for be to go delete file manually to keep in check the number of latest files I wish to keep

I get it that a scheme can delete and manage file within the specific place acronis is directly storage files

I always have copies of images on more than one disk or disk array

in 2010 -- I created 2-4  full backups per PC that I store on my LAN - I would then basically rotate among these backup names when I executed the backups..  I then had file directories written to by acronis -- sync'ed / replicated to 2 other places..

always had images in places I can get to restore using bootable media

so that is my workflow that 2013 glitched up --  I now have to go to my sync'ed areas and manually delete old images

Steven Toney wrote:

yep - I know -- wailing and gnashing of teeth -- LOL

Most would say my own backups are crazy--at least for Home PCs--where I backup files every day to all of an on-board USB 3.0 stick, my ReadyNAS network setup, and then I have a WHS2011 server that keeps PC backups every day as well, none of which involves Acronis (the first two are done automatically with free SyncBack).

Then once a week I make a full Acronis .tib for each PC, to a USB drive that I plug-then-unplug to keep the full backups safe from power glitches.

So basically I have multiple file backups that are automatic, and full PC backups to Acronis (though of course the WHS2011 backups are full as well) that are manually done, then I have a diary iDailyDiary wherein I log any issues or updates I might have with a PC so if I have a problem and have to recover to a week-old or more backup I can see what I'd have to do to update the PC to TODAY (though note I do have file backups that are as recent as "this morning" or "last" from WHS).

Anyway this all probably appears complicated but really isn't. Maybe Steven you can find an approach that works for you yet is simpler to keep track of than what you are doing now.