I need "Name backup files using the archive name, as in Acronis True Image Echo" option to work! B&R 11 Adv
Hello all,
I’m having trouble again using the legacy naming mode option with Acronis Backup & Recovery 11 Advanced Workstation on my work domain. I’m using the latest build on some PCs, and the previous build on others but the problem remains for about 8 PCs.
The “File Naming” checkbox that allows me to “Name backup files using the archive name, as in Acronis True Image Echo” doesn’t show up when I try to create tasks for those certain PCs. I read in the knowledge base help that “Since the removable device mode determines the naming scheme for backup files, the Name backup files using the archive name... check box does not appear when the backup destination is a removable device. “ [source: http://kb.acronis.com/content/29054 ] . But as you can see from my screenshot attached, the backup location is the same for both examples, so I don’t know why it thinks one is a removable device and the other is not. [Edit: sorry, I did black out sensitive network info in my screen shots, but I assure that the backup vault is the same network drive.] Also I do not know how to tell it to use “Removable Media Mode” as explained in the kb article I linked to above. I’m not even sure if that’s what I need to do. I’ve found little other info on this. This link explains the functionality but not how to control whether the checkbox appears or not when creating a task: http://www.acronis.com/support/documentation/ABR11/index.html#10483.html
I’m at a loss here. I really need that simplified naming mode due to the nature of our backup schema. I can’t manually erase the variable time stamps on the archive names every day; I really need the consistent naming. Any help is appreciated!
In the screen shot attached, the first/top one is a "good" example of being able to select the legacy naming mode. The second/bottom one is a PC with the same specs & OS going to the same vault with the same domain user but it's not allowing me to see the "File Naming" option.
Thank you again.
We did use True Image Workstation and Acronis B&R10 previously, but almost all of the PCs that now have B&R11 Advanced are new Windows 7 machines. I also gave most of the archives new names for backing up with B&R11.
We back up to a server with removable drives that rotate in and out. That is why the static naming convention is needed- if the files don't overwrite each other, and they don't with the date-stamp on the end, then the drives fill up too fast with redundant copies.
I generally connect remotely to the PCs through Acronis to make the backups. Is that affecting it?
Is there any workaround?
Thanks
Has anyone out there even had this problem?
If machines with agent see the vault by its UNC path ( \\servername\share\... ) it doesn't matter what is the physicla media there - for them it's just a shared folder. I can only suggest to make sure that you do not edit or create a backup plan in such a way that it uses already existing archive. 0 in this case use 'simplified naming' is hidden. 'Removable drive' mode switch appears only if the device is connected to the same machine that performs the backup.
I genreally connect remotely to the PCs through Acronis to make the backups. Is that effecting it?
If you mean clicking 'connect directly' in list of machines while the Management Console is connected to the Management Server - no, it shouldn't.
Thank you for your help.
When I edit the backup plan and choose the location, it does indeed call it a network share. I give the archive a new name, and I still don't get the option to check "Name backup files using the archive name".
How do I make sure that I am not using an already existing archive? The archive name is new. Even if I create a new task I still don't get the option I need when I specify the network location.
When you click on 'Location...' link when some location is already selected, a dialog will appear. In its right part list of archives in this vault will appear after a while. If you change archive name to something that is not listed there, and press OK, the legacy naming option should be back.
Just in case - this option is not available when you create a centralized backup plan, but it seems not to be your case.
>Even if I create a new task I still don't get the option I need when I specify the network location.
As I understand, this problem appears only with several specific machines with agents. Does this option appear if you select a local folder as a destination when editing a existing task or creating a new one?
>As I understand, this problem appears only with several specific machines with agents. Does this option appear if you select a local folder as a >destination when editing a existing task or creating a new one?
Hi Fedor,
When I choose local storage, I actually don't get any thing where the option for legacy naming should be [graphic attached.]
You're right- I create each backup plan individually. This problem was present months ago, but seemed to go away. Then, with the last 5-6 new computers that I installed B&R 11 onto, this problem is back. I didn't change the way I created these tasks.
If I click on "Location..." and choose an entirely new network location that's never had an Acronis backup on it before, I still can't get the legacy naming option to come up, just "Access Credentials...". I don't think it matters if I create a new task or edit an existing one.
I'm afraid to edit tasks on working machines now, for fear of losing this option permenantly and making a mess of our rotating backup drives. I do set the task to run under a different domain account than the one I'm logged into, but I don't see that being a problem.
Thanks for your response. Any other ideas?
What are build numbers of Management Console and Agents? You can check it in Help->About - for console not connected to any remote machine it will display build # of console itself. It's better to use latest builds (17440) on both ends or, at least, console build should not be less that the one of agent.
THANK YOU!
You lead me to the solution. Indeed, the console was one build behind the trouble machines/agents. I upgraded the console and was successfully able to change the tasks to use legacy naming on the computers in question. The backups ran last night and the naming scheme was as I needed.
I really appreciate your help. This issue seems to be resolved!