Protocol Error From Vmx Vsphere
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vSphere™ > VMware ESXi 4 > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 2 Replies Latest reply: Jun 17, 2012 7:28 PM by Lesta A general system error occurred: Protocol error from VMX Lesta May 3, 2012 7:19 PM Really just posting this for someone else who gets this weird errorThis is a good one!Running Symantec BE2010 R3 all hotfixes (according to live update)Vcenter 4.1.0 258902ESXi 4.1.0 502767VMs2003 SP2 32 bit2003 R2 SP2 64 BitVM Tools 8.3.12In the BE log get the "usual error""The job failed with the following error: Unable to create a snapshot of the virtual machine. The virtual machine may be https://kb.vmware.com/kb/1007346 too busy to quiesce to take the snapshot"In the VMWare log - "A general system error occurred: Protocol error from VMX."Yet the machines that gets the error in the log can snapshot with quiesce in VCenter fine.For some reason , when the backups run on these two machines (many more on the host ), their times move ahead 8 hours and the backup failsIf I re-run they backup job immediately, the https://communities.vmware.com/thread/400746?tstart=0 time is still 8 hours ahead so the backup works.If I retry after the time has been reset, the job will fail againThe time stays forward for the duration of the backup job.I am not sure if the time is reset at the end of the job or that a standard windows time sync resets it.The resolution was to check the Host. Its time was set 8 hours ahead.EVEN THO the VM Tools client was set NOT to update time from hostA snapshot in vCenter with Quisce, worked fine. It was only when thet backup was run that the error occurredStange but true catergory 1791Views Tags: none (add) vmxContent tagged with vmx, quiesceContent tagged with quiesce This content has been marked as final. Show 2 replies 1. Re: A general system error occurred: Protocol error from VMX Rubeck Jun 13, 2012 12:00 AM (in response to Lesta) Hi..I know this thread is a few days old, but here goes:You say you can snapshot with quiesce just fine using vCenter... You did uncheck the "Snapshot virtual machine's memory" when testing this right?I do believe that this option is excluded when your backup software hits the vStorage API to take a snap before backup.... Have you looked at these KB articles to
backup job failing Availability for the Always-On Enterprise Post a reply 6 posts • Page 1 of 1 VM backup job failing by Stig » Thu May 27, 2010 https://forums.veeam.com/veeam-backup-replication-f2/vm-backup-job-failing-t3994.html 11:11 pm people like this post Hi all,I am pretty new to Veeam so im hoping you gurus here will have some patience for my questions Ok so all backups in Veeam https://forum.acronis.com/forum/30278 are running fine and all created in the same way.Only one box which our devs are using seems to pop up an error every night and does not perform a backup.Here protocol error is the VM summary:0 of 0 files processed Total VM size: 136.49 GBProcessed size: 0.00 KBProcessing rate: 0 KB/sBackup mode: SAN/NBD without changed block trackingStart time: 27/05/2010 7:32:26 PMEnd time: 27/05/2010 7:32:34 PMDuration: 0:00:08Creating snapshotCreateSnapshot failed, vmRef "vm-166", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "True"A general protocol error from system error occurred: Protocol error from VMX.Looking at the snapshot manager in vCenter i dont see any snapshots there.Really hoping someone will be able to assist here as im quite baffled by this. Stig Novice Posts: 3 Liked: never Joined: Thu May 27, 2010 10:57 pm Full Name: Michael Sztyk Private message Top Re: VM backup job failing by Vitaliy S. » Fri May 28, 2010 7:59 am people like this post Hello Michael,Could you please tell us if you're able to do the snapshot of this VM manually using vSphere Client?Also I will move this topic to Veeam Backup and Replication section, as this is FastSCP forum, so please continue posting there. Thank you! Vitaliy S. Product Manager Posts: 18009 Liked: 954 times Joined: Mon Mar 30, 2009 9:13 am Full Name: Vitaliy Safarov Private messageWebsite Top Re: VM backup job failing by Stig » Tue Jun 01, 2010 1:24 am people like this post Thanks for your reply Vitaliy.I have done a manual snapshot using vSphere and that worked like a charm, very quick.Deleted the snapshot after that.As a side not, with all p
Registration E-mail: * Password: * Useful Links How to get Support? All Product Documentation Frequently asked questions by product Acronis Backup 12 FAQ Acronis Backup 11.7 FAQ Acronis Backup & Recovery FAQ Acronis True Image 2017 FAQ Acronis True Image 2017 Mac: FAQ Upgrading to Acronis True Image 2017 Grover's True Image Guides Acronis Disk Director 12 FAQ Acronis Disk Director 11 FAQ Product pages Acronis Home Products Acronis Business Products Acronis Forum Archive Home › Forums › Acronis Business Products Discussions › Acronis Backup for VMware (version 9) Forum 30278: backup sometimes fails when creating snapshot Login to post comments 2 replies [Last post] Mon, 2012-03-12 09:30 Tom Tunstill Offline Beginner Joined: 2012-03-12 Posts: 1 My backups sometimes fail with the error below. This doesn't happen every time. vSphere Client shows errors are occurring when the tool is creating the snapshot with the message 'a general system error occurred:Protocol error from VMX'. I don't have problems creating snapshots manually for these VMS. Has anyone seen this issue before? Thanks Tom. Task 'dev and test' failed: 'Failed to create a backup. Additional info: -------------------- Error code: 3 Module: 435 LineInfo: 555b5abba09500ab Fields: Message: Failed to create a backup. -------------------- Error code: 32786 Module: 114 LineInfo: 28314c961de7d3b2 Fields: Message: Failed to prepare for backing up. -------------------- Error code: 353 Module: 149 LineInfo: a71592046cb2c5f8 Fields: Message: Failed to back up the group. -------------------- Error code: 2 Module: 218 LineInfo: 338a407ad20e0987 Fields: Message: Error occurred while running the backup and recovery engine. -------------------- Error code: 1080 Module: 1 LineInfo: d1ab7fa1e56ec747 Fields: Message: -------------------- Error code: 13 Module: 149 LineInfo: d1ab7fa1e56ec8b7 Fields: Message: Failed to perform the requested operation. -------------------- Er