Job State Issues
Running vmProtect 7.0.5173 Windows Agent
(The Windows Agent is the only tenable option for this environment since backups are destined to rotating USB 3 external drives.
I'm having reliability issues with this version of vmProtect. The first issue is that if the destination directory does not exist (in this case a directory on a local drive) when the job runs, the job progress changes to waiting, rather than creating the destination directory, and never proceeds.
And that progress change is the big issue. If the job's progress changes to anything other than Succeeded or Running, the job will never complete, nor will it send an alert that there is a problem. It just sits there "waiting". This can be cause by missing destination directories, missing destination drives, host availability issues(even temporary), job interruption issues such as agent host reboots or target host connectivity issues.
To overcome this hung state, I must manually cancel the job. At which point it will still not ever run as the progress indicates canceled, instead remaining in a canceled state. I must then manually run the job from Task view. Then, after the successful completion of the manually run job, the state returns to Idle, Succeeded and normal scheduled operation continues.
My questions are; is this going to be fixed? If so, is there any idea when? Does vmProtect 8 also behave in this fashion?
At present, vmProtect 7 is great for me, when it works. But, it is not sufficiently robust that I can fire and forget. I must constantly check on it, discover that it has stopped working properly, and frequently fiddle with the jobs. This creates a sense of distrust. That is a very bad feeling to have about your backups.
P.S. Encryption of the backup files would be a nice bonus.
Edit: Replaced State with Progress for clarity and accuracy.
