In the meantime I have 22 jobs. And so I realise that the handling of the jobs is annoying.
So I have some suggestions that would make the handling of more then 5-10 jobs easier:
It would be great to be able to sort the jobs without export and import of the jsons.
Is would also be nice to see the queued jobs (so the next jobs that will come directly after the current running => jobs started with “run now and queued” and jobs in the queue because they are scheduled
And also a possibility to say “Pause Duplicati after the current running job” or “Pause Duplicati after stopping the current running job [after upload or immediately]”
Deletion of a job is not possible while a job is running. The delete is queued. Why? Edit of a job is not queued. The edit + save is done immediately.
Export all configurations (eg. in a ZIP-File) would be very, very great!
1 Like
kees-z
January 9, 2018, 11:58am
2
thommyX:
It would be great to be able to sort the jobs without export and import of the jsons.
Similar discussions can be found here:
I’d like to be able to re-order my backup jobs on the Duplicati main landing page. Is that possible? If not, please consider for an upcoming release.
thommyX:
Is would also be nice to see the queued jobs (so the next jobs that will come directly after the current running => jobs started with “run now and queued” and jobs in the queue because they are scheduled
Similar request here:
The only way to see backup activity is in the green rectangle at the top of the screen. There is no easy way to see in the Web UI which backup tasks are waiting for completion of another task.
This could be improved by changing the icons before each task in the backup list (eventually replace them by an animated GIF).
A rotating or scrolling icon could indicate that this backup task is running. For a static icon, a little Play button (triagle) should suffice.
A little Pause symbol (2 small re…
thommyX:
Deletion of a job is not possible while a job is running. The delete is queued. Why? Edit of a job is not queued. The edit + save is done immediately.
I guess it has something to do with the fact that you can delete the local database and/or the remote files when deleting a backup job.
thommyX:
And also a possibility to say “Pause Duplicati after the current running job” or “Pause Duplicati after stopping the current running job [after upload or immediately]”
Export all configurations (eg. in a ZIP-File) would be very, very great!
Yes, that would be handy.
You can get some of that from main menu About → System Info then scroll down to “System state properties”:
The way the queue works a single job is not supposed to appear more than once, so if you seem to be experiencing that then there’s a bug.
One way to check what’s in the queue is to use the main menu “About” item, then click on the “System info” button, then scroll down to the “Server state properties” section and find the following lines:
activeTask is the ID of the currently running task (if any)
proposedSchedule is the “not yet in queue, but expected to be put in queue at …” list
schedul…
At the moment I see this:
activeTask : {"Item1":18,"Item2":"29"}
...
schedulerQueueIds : [{"Item1":19,"Item2":"25"}]
So 18, 29, 19 and 25? I do not know which job is 18, 19, 25 or 29. I have 22 jobs so it is not the position in the gui.
I believe it’s the order of creation. Only having 2 jobs myself I forget how hard an ID only is to use.
I’ll see if I can find an easy way to correlate them to job names.