Netapp Error In Fetching Number Of Vmfs Datastores
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 : Backup and Restore : Backup and Restore Discussions : [SnapDrive Error]:Error in fetching vmfs datastores. 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 AndreasTrute [SnapDrive Error]:Error in fetching vmfs datastores. [Edited] 2015-04-17 02:58 AM - edited 2015-12-18 01:04 AM Labels: SnapManager Hello Communitywe have a little problem with SME 6.1.0 (1434) and SD 7.1 in conjunction with VMWare 5.5.The environment of our customers:VMWare 5.5 inclusive iSCSI serviceExchange 2010 DAG 3x and 2x CASSME runs on DAG3DAG3 server has connected vmdk boot LUN and 2 RDM LUN via VMWare iSCSITo our problem:SME job runs so far without spec except the backup verification brings a SD error:SME BackupJob LOG[10: 00: 42,573] BackupVerification job of JobID 5902 starts to run on server NAME[10: 00: 42,573] The destination volume of the source logical disk C: \ Exchange Data \ db01 \ FlexClone State is Success and SnapMirror State is Unknown.[10: 00: 49,576] Mounting Snapshot [exchsnap__NAME_04-17-2015_10.00.13__daily] for LUN C: \ Exchange Data \ db01 \ created from computerNAME[10: 00: 49,576] Mount point directory [C: \ Exchange Data][10: 00: 51,105] snapshot will be mounted on subdirectory [MPDisk576][10
onOctober 25, 2013 at10:39 Posted In: Stuff "vmdk is larger than the maximum size supported by netapp error datastore" [SnapDrive Error]: Please specify valid VMFS datastore name. (SnapDrive Error Code: 0xc0041033) Have a read of this: http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=600206 Create a new vmfs5 datastore and then add the netapp error in key listed in the article. No need to restart snapdrive. snapdrive will then use that as the file to back the RDM when it does a verification. GD Star Ratingloading... └ Tags: 2003, esxi5.5, vmdk Comment ¬ Cancel replyYou must be logged in to post a comment. Categories America computers Economics IT Mobile netapp sccm Stuff symantec vmware windows Blogroll Adam's Blog Maid2Clean Tez Mercer ©2009-2015 Barry Mercers blog | Powered by WordPress with Easel | Subscribe: RSS | Back to Top ↑
Weblog The weblog of an IT pro specializing in virtualization, networking, open source, and cloud computing iSCSI from NetApp to ESX Server 15 December 2006 Network Appliance storage systems are becoming more and more visible in VMware deployments due to their iSCSI support and the synergies that are gained when combining VMware’s functionality with the functionality of Network Appliance’s Data ONTAP operating system. I’ll touch on those synergies in a future article, but in the meantime here’s how to configure a NetApp storage system to present iSCSI storage to one or more servers running ESX Server. Configuring the NetApp Storage System Configuring the NetApp storage system is really pretty simple. (OK, so maybe it’s only simple if you know what you are doing and have done it before.) It basically boils down to four steps: Create the flexible volumes (FlexVols) that will store the LUNs for ESX Server. Create the LUNs that ESX will use to establish a VMFS datastore. Create the initiator group(s) (igroups) that will enable connectivity from the ESX server(s) to the NetApp storage system. Map the LUNs to the appropriate igroup. This enables visibility of the LUNs to connected systems based on igroup. Once these four steps are done, we are ready to move on to configuring ESX Server to utilize the NetApp-provided storage. Create the Flexible Volume(s) As needed, you’ll need to create flexible volumes (FlexVols) in which to store the LUNs. The command would look something like this: vol create fv_serverluns -s volume