Highlighted
Contributor
Contributor

VCB Snaphot gives Protocol error from VMX

Since a week or 2 (since we moved from ESX3.5 to vSphere) we're experiencing problems while making VCB snapshots / backup's.

Our vCenter records it as: "A general system error occured: Protocol error from VMX" while making a snapshot before the VCB is made.

Because of this error, the actual VCB never takes place.

I read several post about disabling / enabling VSS, disabling / enabling the SYNC driver, reinstalling the VM Tools etc.

None of these options work.

The vcbmounter commando we use is with the SAN parameter. We also tested it with the HOTADD parameter, but without any succes.

Strange thing is, is that this does not occur on all our VM's, just a few that keep coming back with this error.

Are there any other options I can try to tackle this problem?

Thanks,

Michael.

Tags (3)
0 Kudos
6 Replies
Highlighted
Champion
Champion

FIrst off, run a manual vcbMounter command with the "-L 6" option to produce a verbose log. These can be found under your %TEMP% directory - usually c:\windows\temp - and of course on the screen. If you can't figure the logs out, ATTACH them as a file, do not just paste the output because the board software messes it all up.

Without looking at the logs, my initial guess is that you did not upgrade VCB to 1.5U1, which is required for ESX 4. This would be the reason for the protocol errors on some of the VMs. Upgraded VM hardware is not recognized by the previous version. The VMs that have not had their hardware upgraded will be OK most likely. The new version of VCB can be found on the vCenter DVD.

Dave Convery

VMware vExpert 2009

Careful. We don't want to learn from this.

Bill Watterson, "Calvin and Hobbes"

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"
0 Kudos
Highlighted
Contributor
Contributor

Hi Dave, thanks for your reply.

We have the latest VCB running that came with vSphere.

Just noticed something weird. If I want to make a vcb with verbose logging, I add -L 6 to the commandline.

But what is the use of the config.js file if there is already stated: LOGLEVEL=6 ... ? Strange.

I've attached the log file from one of the VM's that fail.

Michael.

0 Kudos
Highlighted
Champion
Champion

The config.js file is only invoked when using the VCB Framework, so you need to add the option manually if you do not use the framework.

The only thing I see is that the snapshot failed. Is there a permissions issue? Are VMware Tools properly installed on the VM? (I know you said it was, but double check?)

Dave Convery

VMware vExpert 2009

Careful. We don't want to learn from this.

Bill Watterson, "Calvin and Hobbes"

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"
0 Kudos
Highlighted
VMware Employee
VMware Employee

Hi everyone,

Please see KB Protocol error from VMX that also may fix this issue.

0 Kudos
Highlighted
VMware Employee
VMware Employee

Hi everyone,

Please see KB "Protocol error from VMX" error when taking a Windows vm snapshot that also may fix this issue.

0 Kudos
Highlighted
VMware Employee
VMware Employee

I wouldn’t worry too much, this thread was last touched in 2009.


Forum Usage Guidelines: https://communities.vmware.com/docs/DOC-12286
VMware Training & Certification blog: http://vmwaretraining.blogspot.com
0 Kudos