VMProtect Errors
I am trial testing VMProtect6 for our environment. We have about 30 machines. I am testing on one low-production use host with about 10 machines on it. Here is our setup:
ESXi 4.0 \ Dell Poweredge Servers \ VSphere 4.0 \ ISCSI SAN storage \ Network NAS box for backup testing. Using the latest VMProtect version. (2 processor license)
We originally were testing only on a couple guests without issue. Then we added a few more machines to the backup task and now are getting the below errors:
Error 1: VMProtect stops and in the VSphere console I have this prompt: (See attached UUID Error)
Error 2: VMProtect Fails and not all machines backup. Attached are the logs: logs.zip
I think in error 2 the issue is that I had a VMDR appliance in the list, but then I removed the machine from the backup task. Now I seem to get repeated errors.
(Notice the error from 2.25 near the end)
Any help would be appreciated.
Steve
Attachment | Size |
---|---|
log.zip | 73.44 KB |
uuid_error.pdf | 27.47 KB |

- Log in to post comments

Anton... Thanks for your reply. The issue ended up not being CBT.
For issue number 1: UUID ERROR: We somehow have 3 virtual machines that somehow have the same disk UUID. This most likely happened in our early VMWare days using sysprep images and somehow us not marking new machines correctly when first powered on. (VMWare will ask is this machine a copy or did you move a machine?.. We must have answered moved instead of copy)
What happens in VMProtect is when it goes to backup machine A, machine B and C have the same UUID. Even if machine B\C were not part of the backup job VMProtect will snapshot and then mount the disks of machine B\C as part of machine A. VMware will also stop the VMProtect machine until you answer the prompt. (See UUID_error.pdf in post 1)
Once you answer the question VMprotect will continue.
For issue number 2: I think this happens when you have snapshots existing and them you consolidate the snapshots back to the root vmdk. I am not 100% sure on this. Then VMProtect goes to backup next time and throws a hissy since some of the machine VMDK's are missing.
Again.. I am not sure on this.
I am sure on number 1.
Steve
- Log in to post comments