Protocol Error From Vmx Netapp
your search results by suggesting possible matches as you type. Forums Blogs Tech OnTap Newsletter Register · Sign In · Help Products and Solutions FAS, ONTAP and OnCommand Backup and Restore E-Series, SANtricity and Related Plug-ins Virtualization and Cloud Network Storage Protocols AutoSupport and My AutoSupport All Flash FAS, EF-Series, and SolidFire Systems FlexPod and Converged Infrastructure Developer Network NetApp University and Training Community Base Camp NetApp Community : Forums : Products and Solutions : Network Storage Protocols : Network Storage Protocols Discussions : SMVI - A general system error occurred: Protocol error from VMX Subscribe Reply Topic Options Subscribe to RSS Feed Bookmark Subscribe Printer Friendly Page « Message Listing « Previous Topic Next Topic » Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content ttrulis01 SMVI - A general system error occurred: Protocol error from VMX 2009-08-13 10:28 AM Labels: NFS I have an smvi job scheduled daily that fails. I have attached the error log. It looks like SMVI attempts to create the VMware snapshot and fails due to a protocol error from VMX. Doing a quick search on VMWare forums states its a problem with a custom quiescing scripts http://communities.vmware.com/message/1016429#1016429- is this a problem with SMVI's script to trigger the VMWare snapshot?As a side note I can manually create the VMWare snapshot. Also to note there are three smvi snapshots already in snapshot manager that look like they have never been committed. I have attached the .bmp file that shows this. I imagine it could be the error is being thrown due to the existing smvi snapshots present. Then my question is why is smvi not committing these snapshots? Solved! SEE THE SOLUTION SMVI_Snapshots.bmp 746 KB Me too Tags: errorprotocolsmvisnapshotvmware View All (5) Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content amiller_1 Re: SMVI - A general system error occurred: Protocol error from VMX 2009-08-14 10:36 AM What protocol are you using to connect to the NetApp? NFS or iSCSI/FC?
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet A general system error occurred: Protocol error from VMX Article:000085658 Publish: Article URL:http://www.veritas.com/docs/000085658 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account http://community.netapp.com/t5/Network-Storage-Protocols-Discussions/SMVI-A-general-system-error-occurred-Protocol-error-from-VMX/td-p/26839 now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem VMware snapshot backup jobs are failing with status 156. Error "A general system error occurred: Protocol error from VMX" found in https://www.veritas.com/support/en_US/article.000085658 vCenter. Error Message A general system error occurred: Protocol error from VMX Cause VMware cannot create a quisced snapshot for backup. Solution This issue is out of scope of NetBackup support. We need to involve the VMware team to get this issue resolved. VMware is aware of this issue and has released a KB with regards to this. http://kb.vmware.com/kb/1037071 Affected VMware products:VMware ESX 4.1.xVMware ESXi 4.1.x EmbeddedVMware ESXi 4.1.x InstallableVMware ESXi 5.0.xApplies ToNBU 7.1.0.1 in Windows Server 2008 R2 (Master / Backup Host), ESX 4.1 Update 2 and VMware clients Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-Protection (VDAP) and reported in the Tivoli Storage Manager for Virtual Environments: Data Protection for VMware data mover transport tdp4ve tsm4ve error fail Technote (troubleshooting) This document applies only to http://www-01.ibm.com/support/docview.wss?uid=swg21662673 the following language version(s): English Problem(Abstract) The following are common error messages returned by VMware vStorage API for Data Protection (VDAP). The Tivoli Storage Manager for Virtual Environments: Data Protection for VMware data mover uses these APIs to backup and restore virtual machines in a vCenter Server environment. The VDAP is made up of two major components. The vSphere Management SDK and the Virtual Disk Development Kit (VDDK). For more protocol error information about VDAP, see the VMware FAQ at http://kb.vmware.com/kb/1021175 Symptom When you experience a virtual machine backup or restore problem with Data Protection for VMware data mover, a detailed error message from the vStorage API will be reported by the data mover. These vStorage API error messages can be found on the data mover, which is the machine running the Tivoli Storage Manager Backup/Archive Client and the messages are in protocol error from the dsmerror.log file. Often the error message will be reported to the console if the client is running in the command-line mode. In these messages, note the name of the Tivoli Storage Manager Backup/Archive Client function and the error message text. You will need these values when you read the "Resolving the problem" sections of this document. Example: 01/22/2014 13:10:20 ANS9365E VMware vStorage API error for virtual machine 'win2012 - maximovm12'. TSM function name : VixDiskLib_Open TSM file : vmvddksdk.cpp (1735) API return code : 13 API error message : You do not have access rights to this file Cause There are many causes and it depends on the error message and it can also depend on the transport used to backup or restore the virtual machine. Environment Tivoli Storage Manager data mover for virtual environments Diagnosing the problem The error message will be output to the Tivoli Storage Manager data mover error log and the console. Resolving the problem VMware also has a “Best Practices” document that describes the use of the advanced transport mechanisms (SAN, HotAdd and NBD/NBDSSL). A link to that best practices document is supplied in each message explanation where it might be helpful to review the VMware best practices. Message: VixDiskLib_Open => "Yo