[Solved] Unable to edit job - save grayed out
I'm trying to edit an existing job but whilst I can open it to edit, the save button is grayed out. See attached screenshot.
What am I doing wrong?
Thanks, Rob.
Attachment | Size |
---|---|
unable_to_save.png | 122.99 KB |

- Log in to post comments

I have the same problem as well. Same version (11.0.17318). Using Win7 x64 enterprise SP1.
Have tried cloning the job and editing that - no success.
Have tried exporting and importing - no success.
Have tried editing xml file - don't know what to put in place of the arl: tag.
Any change I make does not activate the Save button at the bottom of the Edit Backup Job screen so I am unable to save any changes.
Yes, I can just make a new backup job but it gets rather tedious as I have a long list of exclusions and other options set.
Any assistance is appreciated.
- Log in to post comments

Where is the vault located? Can you access it if you navigate to it in the navigation tree? Apparently it can't save because something is wrong with the location and the schedule is missing for the same reason.
- Log in to post comments

The original save location (vault?) is on an external drive - originally this drive was mounted as drive G now it is drive F. I have tried to change the location to the same directory on Drive F. Although I can select F and the proper directory _and_ the original archive and all of that is accepted by the "Archive" dialog, the Save button on the Edit Backup Plan does not become active.
I can see that my new backup location under 'Where to back up' is the new one that I have selected.
- Log in to post comments


If you change the arl:/.... to new path to the vault (like C:\somepath , no quotes) and import it back (changing plan name too) it seems to work.
- Log in to post comments

Schedule is: Manual Backup
Type: incremental
-------
I created another job. Set all of the same options, with the exception of using the Archive that was previously created. It ran fine and validated.
-------
So the problem seems to be that if the backup location is invalid, editing the job is not permitted.
- Log in to post comments

I tried your suggestion and it worked. Here is what I did:
Export backup job to xml.
Edit in Notepad++ (or anything that makes xml readable/editable)
Changed the following: (NOTE: all > and < are changed to ] and [ )
[path]
arl:/FF749D0B-7362-4A63-997F-FEF361335C7A/F3A95887-364C-453A-9815-779A4C36E6AD
[/path]
to this:
[path]
arl:f:\backups
[/path]
I also changed the name between the [Title][/Title] tags.
I saved this under a new name.
In ABR11, I imported the edited XML file.
I selected the job and edited it. It shows 'invalid location'. The Save button, however, was available. I was then able to change the location and save it.
Thanks for your help. This makes a usable work-around. I hope Acronis Dev's will add this to the bug list. (or explain why it is working this way)
- Log in to post comments

f:\backups should be without arl. Then it is can be saved right after editing.
- Log in to post comments

Sometimes I was able to work around this by changing schedule for the backup, making the changes I really wanted to make, changing the schedule back and then saving (it was a valid option then). Extra work, but not as much as recreating the whole thing. Hope this helps.
- Log in to post comments

I've been having this problem off and on since I started using ABR 11.
Sometimes I can export and import and it'll be editable. I'm running into the problem today and everything I tried has failed. Right now I'm stuck at recreating the tasks!!!
This is really annoying and I wish this would get fixed.
- Log in to post comments

By following the steps I posted on 2012-01-29 and with the information that dev-anon so kindly provided, I have been able to export/edit/import without issue. (other than having to do this to edit the destination on an existing job)
- Log in to post comments

I checked and there was nothing with the arl prefix. My backups go to a D: partition on the local drive.
I also tried changing the Title with no success.
- Log in to post comments

What is sitting between the [path] [/path] tags?
Have you tried changing that?
- Log in to post comments


I updated to the new release of ABR 11 and the Edit problem still exists. I tried it with a newly created plan after it was executed. Build 17437
- Log in to post comments


Err... of anything in particular? Of the dimmed Save button?
- Log in to post comments

Of the whole backup plan editing page with all its fields, from 'what to backup' to the bottom.
- Log in to post comments

Problem has been resolved.
In my plans that I have been creating, the Full Backup was defined to run "Once" with a date/time just after the time I would be saving it (e.g. Apr 2, 2012 10:00:00 am).
So when I try to edit that plan, ABR doesn't like the fact that the Full Backup was defined to something to run in the past. If I "Remove" the existing Full Backup schedule, the Save button is undimmed and I can save the plan.
The most recent build (17437) now displays a "red flag" to indicate a general area to where the problem is. In my case it says "Some backup tasks in the backup plan are scheduled to run in the past." It doesn't point directly to the Full Backup, but it was easy to figure out.
I still don't think this should prevent editing... giving a warning would be better. After all, when I first created/edited it, it worked as I expected.
- Log in to post comments