All jobs that are run on virtual machines by Vimalin are run sequentially. The reason for running everything sequentially is that this keeps the used CPU and disk resources at a minimum. As such your host stays responsive even while Vimalin is running.

Because every job needs to run sequentially, these jobs end up in the backup queue. We identify two different types of jobs, tasks that are meant to run now, for example a “backup now” instruction or a “delete this backup” task. Then there’s also the backup job that you can schedule. The schedule is calculated once every minute unless a job is running (no need to calculate it then).

The Backup Queue screen gives you an overview of what tasks will be run and when they are scheduled to run. If you scheduled too many tasks by accident then here you can delete them.

If you try to remove a task that was put there by the scheduler – instead of on demand – then removing that task might not have the desired effect as the task might be put back there by the scheduler (within a minute). You will get a warning if that’s the case.