NetApp VVol Demo 2014

welcome to the NetApp VM granular management demo or V vowels on cluster data ontap you are probably familiar with the vSphere architecture vCenter server manages ESXi servers that consume storage from data ONTAP using NFS Isaac as the FCN FCoE this is managed by the virtual storage console or BSC via C communicates with V Center using vSphere api's and communicates with cluster data ontap using net f AP is known as zap e's vevo adds another component a vendor provider or vp the vp communicates with vCenter server using vasa or vmware api's for storage awareness and with cluster data on tab also using Zaffis the administrator uses the vSphere web client logged into the vCenter server to manage the entire environment the virtual storage console plug-in is accessible from the home page of the vSphere web client under storage systems you can see all the dead up clusters that are available to VSC that have been registered and authenticated in this lab we have one running version a 2.1 under configuration is where we register and unregister the vasca vendor provider and you can see here the vendor provider has already registered under the vasa provider menu is where we managed capability profiles for NetApp storage by default you have gold silver and bronze and in this lab we've added the vault NFS and evil eyes cousin let's go provision of eval datastore under inventory trees we select host and clusters and you can provision the data store at the data center cluster or host level we use the net app wizard to the completed tasks for both of vmware and NetApp sides first we give it a name and select a protocol next we pick a matching storage capability profile if the cluster and stored virtual machine and then we picked the volumes to become part of that data store you can pick one or several there's also an option to create additional volumes at this time and now we have our vivo let's go look more closely we select the data stores menu click our data store and now looking at protocol endpoints we can see the NFS mounts that are used internally to access all NFS evolves under related objects you can see the backing storage you can see each flexball there's only one in its example and de size and other properties as well as a number of levels in the datastore so now let's create a virtual machine just like to one of the servers selected the new VM can you give it a name pick the host for it to run on then we select storage notice here that the VM sort of policy is grayed out there are two things we have to do to make that available live a new VM wizard over to the work-in-progress area and then go to the home screen and select VM storage policies and here going to create a new one click the new VM stores policy icon we give it a name rulz we pick the net MVP under their rules from vendor-specific capabilities we have the option of picking an existing profile which is an NFS CP or creating one out of individual capabilities the next screen shows us that storage is compatible with this work capability profile we just picked second one-time task needs to be done to enable VM storage policies is to enable them under policies and profiles or here in the new virtual machine wizard you can actually jump into the part where you can configure that and enable that feature on the ESX servers click the link click each server and click enable and again this is a one-time task we can pick our beam storage policy and that gives us the list of data stores that are compatible and incompatible with a storage policy so let's go to hosting clusters under inventory trees and there's our new VM let's jump over to data stores and we look closely at the data store that we created before and you can see under the vacuum storage that there are two V Vols on that data store now one for that virtual disk one foot of the in configuration files so let's see what happens when we power on the Virtual Machine go back and look at the data store again and we see that slide to the right and the number of evolves is now three that third vevo is the V swap file for the new memory memory swab of the VM the next step is to take a snapshot of the VM you right-click the VM click take snapshot let me give it a name and we uncheck snapshot the virtual machines memory back on the data stores tab we select our data store backing storage and move the bar to the right and you can see the number of evals is now for that extra of evil is a copy of the virtual disk yeah I will go into the snapshot manager select the snapshot and then delete it this is a much faster more efficient process than previous implementation because no data has to be moved from Delta files back into the original VMDK so now let's clone the VM give the new VM a name pick a compete resource and select storage if we pick the same VM storage policy act me NFS the same datastore will be compliant which enables it to stay within the same net flexball which allows us to use NetApp flex clone to create a clone of the VM once the clone is complete you see we have more of evils

Channel: Graham Smith

Views: 8,125

Rating: 5 out of 5

Keywords: VM Volumes, NetApp, VMware, VVOL, Virtualization, Data Storage Device (Product Category)

Id: caXlscYaWhU

Length: 7min 52sec (472 seconds)

Published: Fri Aug 29 2014