Rename a backup job
So after creating a job, then cloning it, I simply want to name it something THAT I WANT IT TO BE NAMED, now what Acronis wants it to be names.
Yet another case of programmers having NO CLUE how to think like a user, make things straightforward.
I am technician, with software saavy, and can't find it.
Programmers really miss the boat when they make their software worse, harder, more complicated, and not easier and more straightforward.
https://www.acronis.com/en-us/support/updates/index.html
CONSUMER PRODUCTS
-
Acronis True Image 2020 for PC ( Build # 20770, 595.5 MB )2019-08-29Release notes
Known issues and limitations of this version
- Please note that the new technology for disk-level backup is introduced in Acronis True Image and is being improved, so it may currently have the following limitations:
- TI-169821 Backup conversion to VHD format is not present for the new backup format.
- TI-171553 Moving the backup through the Acronis True Image console is not present for the new backup format.
- TI-169548 Renaming local backups is not possible for the new backup format.
- TI-172340 Backup mounting option is not present for the new backup format.
I, too, would like to be able to give the backup file the name I choose. The older version used to pick up the name I gave the backup scheme. However, this new version gives it the name of the source which is terrible!
Katherine, you can change the Backup task name (used for the files) at any time before you create the first backup for the task. You cannot change the name after that point.
The default name given is for the source disk etc but you can change this with no issue!
The above shows how I have been able to set my own names even though the Source panel shows the name that would have been used by default for the source disk.
Maybe an option for Acronis to make an very simple version of Acronis like the 2010/2011 version so they can take the time that is needed for a stable 2020+ version (1-2 years?). I use old versions for other people who bought 2020 versions so to be sure there is something to restore if needed.
After using it more than 10 years I really can't advise people to go for a 2020 (updated 2019/2018/2017) version without a bad feeling of cheating.
LOL No rename is like a 1st year college project.
Even "Clone Settings" just seems to make some weird clone with '(1)' in front of it, that can only be cloned or deleted. Sure, you could start a backup but you'd be forced to keep that name.
So we must start from scratch as the only way to chose a name?
Erol, unfortunately you are correct at this time until Acronis bring back the missing features for the new .tibx format backups. These options are offered in their premium business products that the .tibx format was brought from to ATI, so shouldn't be too difficult for them to implement here too!
Yes, the feature to rename a clone backup job is important and save a bunch of time. Removing this feature is a detraction to the software after it has been included for years. I hope they bring it back soon or I will advise my customers to use a different imaging software program.
Jim Qualizza wrote:... I will advise my customers to use a different imaging software program.
For your customers that have an older version of ATI, you could just advise them to stay with the old version for the time being. But definitely submit a Feedback telling Acronis how you feel about ATI 2020.
My impression is that the release of ATI was drive by a management schedule rather than product readiness. It would have been much better for company reputation and customer good will if Acronis had delayed release until the product was ready ... even if it was delayed for a year. Some missing functions (such as renaming a backup task) will almost certainly added in a future update but I'm afraid the damage has been done.
Plus one on being able to clone and rename backup jobs. I use this to create a backup config, then clone and rename the backups weekly.
I suspect that it proved more difficult than expected in porting *.tibx code from 64bit code (used in Backup 12.5) to 32bit code used by ATI.
Ian
Hello Everyone,
all comments regarding the absent Rename feature were added as votes to the respective implementation task, thank you! The product team will review the feedback and prioritize the development accordingly.
It's reassuring I suppose that my inability to find a way to rename a cloned backup plan was not a dementia indicator. But it's jaw-dropping that such a simple feature doesn't exist, especially when cloning an existing plan, and hasn't been fixed in almost 5 months (since the initial post, probably longer). Wow.
Hello Peter, thank you for sharing your feedback! forwarded it to the product management
I've got a quick and dirty solution, though not perfect. If you rename your destination folder using something like the name you'd like for the source (e.g., F full backup to J), when you click on a backup job, you'll at least see that name in the destination box so you can differentiate your backup jobs. You must keep the name short so it will fit in the box. This is a kludge, but It works for me while we wait... this is truly ridiculous, however.
Hi
Just find out about this problem in my new version 2020 - it is an absolute joke. What are they thinking - or rather not thinking. You can clone but only to get a ridiculous name adding numbers in parenthesis in fromt. You don't clone if it wasn't because you needed to do something else indicated by another name. I remember how bad it was when we got the 2016 version going from using 2013 whatever it was called. And now 4 years later it is still full of these crazy oversights. Come on. Fix it.
And this custom file system browser that did not work at all 4 years ago is still there and can't see all folders, e.g. to Exclude Drobox folder, and you have to paste in the path manually. Again - come on it is a joke. It shows product managers are ignorant money people and not interested in the product and the users = customers.
/Hoegge
Hi!
I have the same issue as you all. This is really making backing up useless if I don't know which backup I should restore to in the future.
I cannot recommend this product to anyone until renaming backups will be possible, which is a real shame.
At the moment I'm able to use Acronis with the old .tib-format. I just have an old backup with .tib-format that I keep and continue to backup from. But unfortunately often Acronis doesn't "validate" the backups, and I have to restore from the boot-usb-stick. Really inconvenient. Aconis should either return to .tib or fix the renaming issue ASAP (it is already as late as it should be).
I'm wondering why they can't fix this after all these months. They know about this issue for a long time, but they haven't showed any signs of working on it.
Hello Everyone,
Renaming of local backups is one of the current limitations of the TIBX backup format. The functionality may be added for TIBX backups in the future versions of the product. Please refer to https://kb.acronis.com/content/63425
I've registered your comments as votes for the feature implementation, thank you!
CAUTION! WARNING! CAUTION! WARNING!
The following is unsupported, may not work, etc. etc. But it DID work for me! (I think!) Trying a backup now
I had a job called DAILY. I deleted it along with the backup file. I created a new job DAILY and it wanted to call it DAILY(1) and I seemed to have no option to rename it. BEFORE you create ANY backups with that job, I was able to do the following:
CAUTION! WARNING! CAUTION! WARNING!
First, turn off Active Protection. This is so you can edit these files. Go to
C:\ProgramData\Acronis\TrueImageHome\Scripts
You will see some funny name files. Edit each one (Notepad or another text editor) until near the top you see
<display>DAILY</display>
where DAILY is the name of the job you want to change. Change it to what you want. Further down find the line
<volume_location partition_id="" uri="K:\Acronis\Desktop\DAILY.tibx" volume_id="0" />
and change the uri (probably the file name) to what you want.
I suspect you can only do this BEFORE you have run any backups with this name. Save the file and start Acronis again. Verify all the settings for the job are correct.
CAUTION! WARNING! CAUTION! WARNING!
I'm sure this is NOT an approved solution nor may it work in all cases and may have unexpected side effects. If this works for you, let others know too. I am NOT an Acronis tech, moderator of this forum nor act in any other official capacity. I'm just your homegrown hacker that figured that "under the hood" there had to be a way to change it. So I looked... and this is what I found.
I hope I gave enough disclaimers :-)
Bill, welcome to these public User Forums.
While your suggested hack sounds like it should work in principle, there are some flaws in the logic!
Information about all backup tasks is stored in an internal database which will remain unchanged by your hack, plus ATI also uses metadata to store information once any backup files are created.
The other point here is that no hack is needed for when creating a new backup task as you can still change the name provided that you do so early on in the task configuration before it is run for the first time and creates any files.
I concur with Steve, his answer is correct.
This is really too bad, possibly even a deal breaker for me, as a user since 2009. I've been designing and coding systems for over 40 years. This product should NEVER have been released without renaming clones existing tasks. When you upgrade you largely expect to at LEAST have a stable baseline of features. This is NOT a trivial issue for anyone who sets up more than setup a single backup. It's a shame. Acronis loses some significant credibility here on this one.
Dear RJ Miller,
I've passed your feedback to the product team, thank you! Please accept our sincere apologies for any inconvenience cased by this change.
OK, I've made the mistake of renaming an ATI backup before I discovered it was verboden. I have also forgotten what was *exactly* the name of the file before I renamed it. (A side effect of it being 2AM.) Is there any way to find out what name ATI is expecting the filename to be to I can rename it back??
Alexander, welcome to these public User Forums.
Please download the MVP Log Viewer tool (link in my signature below) and use this to review the log files for your backup operations. This should provide more information on the renamed file if you can identify when the backup task ran that created it?
The log should show you a line similar to the one below from one of my logs.
Operation Win 10 SSD Inc E started by schedule.
Where the name following Operation and before started by schedule is the file name, so for the above, the file is Win 10 SSD Inc E.tibx
Thank you for the pointer to MVP Log Viewer. It was helpful. It didn't solve my problem however.
The backup files I renamed were created with ATI running from Windows 10 bootable optical media onto a portable 4 TB SATA drive. There are no log files to view. I did do a system report and saved the output and *that* had a log file with the name of the ATI file I couldn't remember. It seems that the name of the ATI file is *in* the tibx file and standalone ATI loses its little mind when it encounters it not being what it thinks it should be. I got a simple "restore failed" pop-up message on open, when I tried to recover files, with no additional information in the log file. I'm pretty sure I've figured out two out of the three I renamed. The third, the one I really needed (of course), which had a typo in the name, by sheer luck was in the system report, so I've been able to figure that out, too.
Is there a (development?) tool (a backup file analyzer perhaps?) that examines ATI *.tibx files and generates a report (including what it thinks its name might be)? Maybe there's an Acronis developer out there with such a beast? It'd be great as part of a recovery suite.... One can dream.
Alexander, there are logs produced when creating backups from the standalone ATI media but you have to view and save these before leaving that environment, as they are volatile and lost as soon as you close the ATI application.
It is interesting that you found the name of the tib file in the System Report contents, I can only assume that the main Windows ATI GUI found the file after you rebooted into Windows and before you renamed the file.
While there is no rename option (in ATI 2020) for .tibx files in the ATI GUI, this is being brought back in ATI 2021 (currently in Beta test), though doesn't work the same as earlier versions!
It should not normally be an issue with renaming a standalone Full backup .tibx file provided that you use a valid name and there is no associated task for that file in the ATI GUI. I have been using a process that does rename the .tibx file to produce a fully independent full backup .tibx file on my own system.
If you have created either an incremental or differential backup chain, i.e. Full plus a further incremental or differential file, then these should not be renamed because of the metadata linkage between files in the chain.
The system report was saved because I saved it. I'd clicked the "system report" button to see what it did (after I'd read the help). The report was interesting in its detail. Having everything I knew about my laptop configuration in one place was useful, so I clicked the button to save it and I put it with the backup files. (It'll be useful for anyone who might be recovering my laptop.) Finding the report had been stuffed into a .ZIP file was a surprise. Windows native tools to handle ZIP files are, shall we say, limited in their scope. Clicking around inside a .ZIP file with Windows Explorer is laborious.
I must say that having standalone ATI just go *poof* with no more information than a pop-up window giving me two words for a diagnostic was *really* annoying. There was absolutely nothing in the log file. (Is there a way to turn on debugging?) I'm still not entirely sure that renaming the file caused the failure (it may just not work). Now that that backup file is back to its original name (I hope), I'll see if it works any better. Wish me luck.
Hi everyone!
So if I understand correctly, they will fix a bug that has destroyed the whole purpose of the backup software, and only apply the bug-fix in a new version of Acronis, namely the 2021 version.... and charge again for the new version? As if they sold me a backup software that I can't use, and then possibly wish to force me to buy it again, just to fix a bug that has destroyed the software I've already purchased?
This is unreasonable, and if Acronis wants to charge me for a software-breaking bug-fix, it will only make sense for me to not be a faithful acronis customer anymore and look elsewhere for another backup software. Don't you guys agree?
With best regards
John
John, sorry but your comments have lost me? This topic was raised because Alexander had renamed a backup file that he created using the bootable rescue media but then forgot what the original name was and needed to restore it.
Yes, there are limitations introduced by Acronis with the new .tibx format backup files, and these do include not being able to rename backup tasks using .tibx files, but this in no way "has destroyed the whole purpose of the backup software" as you have put it.
ATI 2020 still works and is more than capable to delivering on the purpose of Backup & Recovery, so am puzzled why you further say "they sold me a backup software that I can't use, and then possibly wish to force me to buy it again, just to fix a bug that has destroyed the software I've already purchased?"
Sorry but you must be using something very different to myself and other users who have ATI 2020!
Hi Steve!
I have to apologize for my frustration. Somehow I started to react on my frustration along the comments of this topic. But acronis 2020 is really not usable for me. I'll try to explain my situation a little better.
I usually create a backup manually, before changing or installing something in windows. It's a safety procedure that makes me feel safe, because I can roll back my pc to a state that was working well, if I've done some changes that had poor effects on my pc's performance.
To be able to use a backup software in this way, it's not only necessary to be able to create a backup, but it's also absolutely necessary to be able to name each individual backup, to be able to identify and differentiate the state of my pc and the reason of the backups.
If I make a backup before installing a new graphics driver, and 2 weeks later regret the driver update, then I have to find the right backup version among all the other backups I've made meanwhile.
So naming a backup is essential for me. And creating a full backup each time is time consuming in a level, that makes the experience way too tedious to make it possible for easy and fast backups, whenever I need or feel for it.
So to be able to even use my purchased Acronis 2020, I have actually somehow managed to have an old .tib-file, that I never completely remove, and just continue to make differential backups from that! (incremental backups don't work as well, because Acronis can't recognize/validate the files sometimes, and if I want to restore, then I have to do it via the bootable recovery software).
A backup program is only as good as its recovery possibility, and one necessity is to be able to recognize the correct recovery file, which during the time of this comment is not possible with .tibx-files.
I hope that you guys can understand my situation and frustration a little better, and I wish that Acronis decides to create a free update to fix this particular issue. Otherwise I have to once again search for another backup program that fits my needs... Which is really sad... But I can only use my money as a "vote" and "support" for companies with good policies. I'm a little sceptical that my voice/comment will change a company's "bug-fix-policy"...
I'm sorry if I changed the topic somehow, I won't continue my comment anymore, since it doesn't belong here in this current topic, sorry!
With best regards,. John
John, as with all things, there are ways around most of the limitations in ATI 2020.
You can continue making .tib disk backups as with earlier versions by using a little bit of editing of the underlying script (.tib.tis) file before running the backup task for the first time.
See forum topic: How to create a Disk backup as .tib (not .tibx) which will create a new backup task using the older .tib format in the Windows ATI 2020 GUI.
Backup tasks can be renamed if you do so before first running the new task - this has not changed.
Full backup files can be renamed if this is done before the task creating them runs for a second time, but has to be done either in Explorer or using either a Pre or Post command to do the rename. I have been using this process (with a Post Command) to create renamed, fully independent full backup files.
In terms of recovery from any backups, I personally haven't had any issues in doing so using either incremental or full backups. I don't tend to use differential backups other than when testing out problem scenarios. If you have particular issues with recovery, then please raise a new topic here in the forums and we would be more than happy to try to help.
I got an older version of Acronis on a used computer. It was pirated. I used it for awhile but wanted to do "the right thing" so I bought the 2020 version. Talk about three steps forward and four steps back. My biggest complaint is that there is no way to clone a backup job and then rename it. This makes this software pretty close to useless for me and the way I use it. So let's think about this. You order a new car from the local car dealer. You pay. The dealer calls and says it has arrived. You do down there and they toss you the keys and you get in and start it up and begin to drive away and there's horrible clanging and grinding and sparks -- and the car can't even be used. You get out and look around and WOW! It only has three wheels! You bring the dealer over and show them, and they say oh, well, yeah, we noticed that too. But just do the best you can and if we ever get around to it we'll mail you another wheel. Maybe. Maybe not! Have a nice day! You'd have them in court so fast it would make their dizzy-dealer-pinheads spin. There needs to be a law that programmers FIRST must have some real life experience. They must have mowed a lawn. They must have changed a flat tire on a dark and stormy night. They must have built a cabinet with their own two hands. Making things WORK is more than just theories. I'm sorry Acronis can't grasp that. I'm sorry I "upgraded". I'm sorry I paid them a lot of money. This is beyond ludicrous. And it's STILL not fixed! Bloody fools. I want my money back. Maybe it's not too late to file a credit card dispute.
I'll add another vote for the rename function. I could also offer some surprise and dismay that it doesn't just work, but other people have handled that quite adequately.
Ich hatte die ATI Version 2017 und auf die Version 2020 geupdatet.
Wegen diesen Fehlern habe ich die Version 2020 zurückgegeben und die Version 2019 gekauft.
ATI 2019 funktioniert einwandfrei.
Sorry I don't speak English very well.
I had updated from the 2017 version to the 2020 version
Because of these errors I returned the 2020 version and bought the 2019 version.
ATI 2019 works fine ;)
Hi Steve!
Thanks for the answer and the effort!
But the least I would expect from a company that wants to keep its customers, is that to offer an easy workaround as fast as possible.
If the .tibx file is a real hassle to implement basic backup-renaming features, then I would expect at least to have an official and stable solution by adding support for both .tib and .tibx.
Obviously the .tib-format is still supported. Why not just put it in the options of a new backup to add a new .tib-backup instead. Which is for people (and I believe it's all of Acronis customers) who need a renaming feature to be present.
Right now, renaming is not possible with .tibx. And going through a very complicated and time-/energyconsuming and headache-inducing workaround is not a good support alternativ from a company that wants to keep its customers.
This is easy programming, it's not a solution, but it's a service and act of respect to the customers to be able to use Acronis with ease until the beta-version-.tibx format is ready for a real release.
I'm sorry if I sound agitated, I don't mean to, but the .tibx-format was not ready for release, let alone to be the only official way to create new backups throughout an entire paid version of an Acronis software, with no official support of creating .tib-format, even though it's still supported by the software.
The tedious workaround to create .tib-format is inexcusable as an official workaround by the company customer support.
Hopefully Acronis decides to add the easiest checkbox as a free update, to be able to easily add a new .tib-backup as an alternative to .tibx.
Please, please, consider it Acronis. I really want to have a reason to stay faithful to Acronis, don't force me into another backup software!
With best regards,
John
Amen to the above comments.
Not being able to easily rename a cloned backup is a time waster.
Hi again everybody!
Acronis True Image 2021 has arrived and the changelog says renaming is now possible!
This should be the best news ever for Acronis customers! But something is wrong...
I tried it recently, and all it does is creating a new full .tibx backup and removing the previous one from the list (it asks you first).
I guess this is the only workaround they could've think of, and I would have been OK with it temporarily, but unfortunately it doesn't remember my backup settings at all when it creates a new backup with the new name. So everytime I change name, I also have to go in the backup-settings and change everything in there. Is this a bug or is this just something that Acronis has missed?
The second thing is that the recovery doesn't find the previous backup if the name has changed. Is this also a bug? Is there a convenient(!!!) way to find the older backup with a different name?
Thanks for helping out! I'm still optimistic about the 2021 version! I'm still using the old .tib backup meanwhile.
With best regards,
John
I had not noticed the settings problem - it may be that it worked in the beta but got broken in the release build - something for me to check. If you have a replica it is deleted if you do a rename (at least that was the case in Beta 2).
Ian
Hi!
I just want to mention that the latest update has fixed the settings not being resetted when renaming .tibx files!
Now tibx is actually starting to work at its basic levels! The only question is, if I rename a backup (and remove it from the list according to the prompt after renaming), how I actually will find the old backup when it's time to restore. It's not in the restore list if the backup has been renamed.
And as some people already have noticed, the tibx backup is really slow. My pc only contains ssds (with plenty of storage space, Samsung EVO 860), and I have an i7 8700K cpu, and yet I get slow backups of a drive that only contains my OS, a few small programs and some small files on my desktop. When backup button is pressed, it takes several minutes to start writing to my ssd, then it writes at maximum speeds about 100-200MB/s (max speed of my ssd is 550MB/s), which takes it between 6-12 minutes. Even with differential/incremental backups.
Is there a hardware limitation to my pc or is it a software limitation than makes the backups so much slower?
With best regards,
John
So, it's currently February of 2021, and this issue was first reported in this thread in September of 2019, about 17 months, and the issue is still not fixed.
And regardless that Steve up above indicates that you CAN rename the cloned backup profile if you do so early in the process before you begin adding files or making any changes to that profile, you can't, at all. Ever.
What you CAN do is rename a newly created backup profile. That works.
What does NOT work, is trying to rename a cloned backup profile. That does not work. There is zero options to do so in the drop down menu on the cloned profile.
From the second you create the cloned backup, you cannot change the name. There is simply NO option for rename anymore like there used to be on previous versions when this feature very clearly WAS an option, and an option that always worked.
I've purchased 8 licenses, total, since as far back as Acronis 2012, but I only know for sure that the ability to rename a cloned backup profile has existed and worked correctly since Acronis 2013, which means that there is absolutely ZERO reason why, 8 years later, it should not still have that feature and that it should not work exactly as it is supposed to.
I have noticed this problem ever since upgrading my licenses to Acronis 2020 from Acronis 2016. In Acronis 2016 this feature worked as intended, with no problems.
Acronis, this is a basic feature of the program. I don't think there is really any argument against this not only needing to be a fix that gets fast tracked but that it should never have been excluded from any version of the program to begin with.
I'm quite sure that 100% of your license holders would be 100% pleased to see this get addressed in the immediate future.
Thanks.
Leonard, welcome to these public User Forums.
This issue was reported for ATI 2020 which went out of support in September 2020 without it being resolved.
It is resolved in ATI 2021 as shown by the following screen images.
Note: this is how Acronis often works in providing fixes to issues in a later build or version, being the latter in this instance, along with fixes for other limitations found in ATI 2020 for backups using .tibx files.
That's great Steve, except that there is literally no reason why a license holder should HAVE to pay to upgrade to a newer version just to get a fix for a problem that has existed throughout the entire lifecycle of a product. Particularly when that version is a very recent one. It's not like we're talking holding on to a version that is four or five years old or something, although, even then, having a little bit of loyalty for your customers that have supported you in the past is something that successful companies often look back on as part of the reason for their success.
Making users pay to upgrade in order to see fixes to products they've already purchased, many times before, is not the best way to ensure customer retention, I assure you.
I'm sorry, but this is a poor solution (Read: Not a solution) for people who've preferred to purchase the perpetual license rather than be indentured monthly for the subscription prices. To be honest, I'll be happy as can be to see subscription licenses go away someday when consumers come to realize what a bag of poop that is. And not just from here, from everywhere.
Regardless though, thanks for the heads up on the newer version being fixed, but it would still be nice to see the version I already paid for get an update that fixes this problem rather than having to pay for a newer version that will probably also have some kind of problem that requires me to upgrade to the next version, each time at an additional cost with very little extra benefit to me other than the fix itself, so I am disinclined to be cooperative in that regard. Thanks.
Leonard, I am happy to agree with all your sentiments expressed above but like yourself, I do not work for Acronis and have minimal influence on their policies involved here!
I certainly wouldn't recommend upgrading to ATI 2021 in its current guise with the enforced injection of the new Acronis Cyber Protection features that remain active in the background even when the user has 'turned off all Acronis Protection permanently!'
Getting access to fixes for things broken in ATI 2020 is not a reason to upgrade, especially when options like renaming cloned backup tasks is something only used rarely for most users!
I too totally dislike the trend towards subscription services for software and apart from being gifted a subscription to ATI 2021 for being an MVP, do not have any other subscriptions and wouldn't ever purchase the ATI one if I were not an MVP!
We are in agreement Steve.
Steve Smith wrote:Leonard, I am happy to agree with all your sentiments expressed above but like yourself, I do not work for Acronis and have minimal influence on their policies involved here!
I certainly wouldn't recommend upgrading to ATI 2021 in its current guise with the enforced injection of the new Acronis Cyber Protection features that remain active in the background even when the user has 'turned off all Acronis Protection permanently!'
Getting access to fixes for things broken in ATI 2020 is not a reason to upgrade, especially when options like renaming cloned backup tasks is something only used rarely for most users!
I too totally dislike the trend towards subscription services for software and apart from being gifted a subscription to ATI 2021 for being an MVP, do not have any other subscriptions and wouldn't ever purchase the ATI one if I were not an MVP!
I guess it's a question what's more important for a company, probably the sales and customer department is al lot bigger than the development's, as they leave some major problems for years to solver (partly). The pre 2016 versions had almost no problems, but if you make a backup you can only hope the restore will work when needed.
Update on tibx renaming, It is July 7th 2021.
Just to confirm...
Using Cyber Backup (which I assume creates the same tibx files?), it appears to ok to create a backup plan, using the Backup Name Option to name the tibx file. And as long as the created file's filename is not changed, the file can be moved to a different location and still work? I have tested this by "validating" the file in the new location.
I started work with PCs in 1980 and have qualifications as a senior engineer from Microsoft and Cisco (and Novell!). There are ways to to deal with the very inconvenient inability to rename or move Acronis backups.
You can backup onto an external drive and then rename the files to your heart's content on a machine which does not have Acronis Cyber or Trueimage installed.
Alternatively you can uninstall Acronis from the PC in use and then rename files.
It used to be possible to use the Task Manager to delete Acronis processes usiung the rtask manager but that has been stopped by Acronis.
As far as the Acronius database is concerned it is of little or no use to bme so when I reinstall the application I can easily 'Add' the backups that are of special interest to me.
Having been a user of Acronis Backup applications for many years I have learned that the functionality of the core product is very reliable( - except when it comes to corrupted files). Howver, the user interface is and always has been lacking in the very basics of ergonomics.
Am I right in thinking that Acronis is a Russion company?
I think the request is to rename the backup job that you see in the scheduler for "this computer" rather than just renaming the files.
just saw on the web:
"Acronis is a global company, founded by a Singaporean citizen in Singapore in 2003 and incorporated in Switzerland in 2008. We have over 2,000 employees in 34 countries and 19 offices around the world. Our technology is built, tested, stored, distributed and licensed in our headquarters in Schaffhausen, Switzerland."
Swiss. All my personal correspondence from them shows Switzerland.