SureBackup Error: Powering on / Failed to lock the file

[Fiskepudding]

During a SureBackup job I get these errors on one VM: " Powering on" and "Failed to lock the file".

What can cause this?
This VM is in a SureBackup job with 22 other VMS, thats passed.

[Vitaliy S.]

Hi Espen,

Kindly ask you to avoid posting log snippets as it is mentioned in our forum rules. As to your issue, what if you select a different restore point for this VM.... do you still see the same error?

Thanks!

[Fiskepudding]

Sorry about that.

I can re-run the entire job, (same restorepoint), and it passes.
Actually just did today.
It failed at 07:00 (scheduled) , manually startet at 09:28, it was ok.

The log also shows it is using same backup point.

I am not saying that it fails every time, far from it, was just wondering what can cause this error the few times it happens.
I get these angry [Failed] e-mails from Veeam

[Vitaliy S.]

Hmm....is this the only VM that fails? Do you have any antivirus scans scheduled to the same time by any chance?

[Fiskepudding]

Only one fails, but the VM can varry..
And again, it does not happen often.

No AV scans.

Not a big deal really, I can easy let this one go, as long as it do not get worse with time.

[Vitaliy S.]

Hmm...since it is a random VM, I believe there should be some process locking the files. Does this happen on a particular time?

[Fiskepudding]

Hmm.. looking at the logs, I can only see the "power on" issue happening 1 other time.
One happened at 28.11.2013 07:47:48 i, and the other 16.12.2013 07:44:04. So the time of day is quite close.

They are also a bit different. Both starts with the Error "power on."
While the first I reported shows a "Error: Failed to lock the file"

The other has these following messages" (Same second as the power on error):
"Error Results: Cannot detect VM starting because of timeout"
"Error Error: Results: OS did not boot in the allotted time"

I have the job set up to process 5 simultaneous VMs. Could that be a problem?
I have had problems with that on a rather slow NAS before.
But this job is not using a slow lab or a slow repository.
And usually the job runs without any hiccups.

[Vitaliy S.]

Potential storage performance problems can indeed cause this... would it be possible to re-configure your job to start 4 VMs at a time? That would help us to nail down the issue.

[Fiskepudding]

Have already set the job to 4 VMs, so we just have to wait and see
Will post back if I see some changes. It wil take some time to validate this, last time there were 14 days between the power on errors.
I guess a month will be enough time to conclude.

Thanx.

[Vitaliy S.]

Sounds like a plan, however I would also ask our technical team investigate the log files, as they might have other thoughts on this behavior.

[Fiskepudding]

ok, it happened again, so I created a case: 00493087. I post back when it develops.