backup fail after last update
-
@joearnon It means that there is already another job working on this VM at the same time.
-
@julien-f well, there is no other job on the VM's, and it happens on all my predefined jobs. only automatic jobs does not work from the last update. i did not do any change in the jobs, and they worked fine for the past 4 month. I've only updated the version of orchestra and it started.
-
@joearnon So this 2 particulat VMs failed every time? When you tried to start the job manually they work fine? May be try changing the schedule to test?
-
@tony no, its all my jobs. this is an example of a job that fails. i can give you all my jobs but you;ll see the same error.
if i run the jobs manually, even all together, all works fine. but it's annoying, and disturbing. -
@joearnon Are you sure they all failed? From the log you posted only 2 out of 5 failed, the other 3 backed up just fine.
-
@tony the job failed, not all the VM's failed. some has one VM fail, some has 4 VM's fail.
-
@joearnon So are the VMs that failed always the same ones or are they random? Are they all on the same SR?
-
@tony random VM's, not on the same SR.
-
@joearnon Hmm... if they are random VMs, then it probably isn't scheduling issue since that would normally cause the same set of VMs to be locked. Not sure whats going on... may be you can disable all but one backup job to see if that changes anything.
-
-
-
@joearnon Can you post logs of both backup instances (of the same job) that ran, see if they are different and in which way?
You can also try to reconfigure the back up job to only a single tag parameter to see if that is the issue.
