October 29, 2009

SMVI 2.0: Released for Download

Today we have formally released an updated version of SnapManager for Virtual Infrastructure (SMVI 2.0), which can be downloaded from the NetApp NOW site.

In a nutshell, SMVI 2.0 provides several enhancements to the previous releases with the most anticipated being the level of restore granularity down to the individual file from within a VMDK.

Below is a list a list of all the enhancements available with the 2.0 release.

  • AutoSupport Integration
  • Backup GUI redesign
  • Support for Independent Disks
  • Snapshot naming changes
  • Support for pre/post backup scripts
  • Enhanced backup search
  • Restore disk to different datastore regardless of protocol
  • Single File Restore support
    • Self-Service Restore
    • Limited Service Restore
    • Administrative Restore

For a more in-depth description and explanation of the above enhancements please take a look at a previous SMVI 2.0 blog post.

October 26, 2009

NetApp Virtual Storage Console (VSC) for ESX ready for Download

The VSC plugin, previewed here, provides NetApp storage visibility to the VMware administrator, displaying:

  • The amount of storage available / used in the datastore / LUN / Volume / Aggregate that the datastore is contained in
  • The amount of savings recognized by NetApp’s Deduplication technology
  • The overall health and status of the controller
  • The ability to optimize VMware hosts for connectivity to NetApp storage (Host timeouts, path settings, etc..)

Summary of supported functionality in the 1.0 release includes:

  • Support for ESX 4.0 and ESXi 4.0 hosts.
  • Limited support for ESX 3.5 and ESXi 3.5 hosts (listed and details provided, but setting not set – requires using EHU for host settings)
  • Viewing the status of storage controllers from a SAN (FC, iSCSI) perspective.
  • Viewing the status of storage controllers from a NAS (NFS) perspective.
  • Viewing the status of ESX hosts, including ESX version and overall status.
  • Checking at a glance whether the following are configured correctly, and if not, automatically setting the correct values without needing to access the ESX console. You can select multiple ESX hosts and update settings for all hosts with a single command.
  • Storage adapter timeouts
  • Multipathing settings
  • NFS settings
  • Collecting diagnostic information from the ESX hosts, storage controllers, and Fibre Channel switches.
  • Tools to identify and correct misaligned disk partitions (MBR Tools)
  • Tools to set proper guest operating system disk timeout values

NetApp FAS series customers can download the VSC from the NOW site today.

For IBM N-Series customers, the IBM branded version will be distributed directly from IBM. I do not know, whether IBM has published it yet.

 

October 15, 2009

Sneak Preview: SnapManager for Hyper-V (SMHV)

Server Virtualization is one of the most disruptive technologies that has hit the industry the past 20 years. Arguably, the only thing that comes to it, is the transition from Mainframes to Open Systems.

That said, server virtualization also presents some challenges that require customers to re-think their infrastructures because some things tend to become challenging. Backup and Recovery is an example of that.

Server Virtualization challenges that I/O limitations of Physical servers and can introduce new bottlenecks which can make it rather difficult to backup the large amounts of data now residing on the physical. Although traditional backup methods have served us well for years, unfortunately, in server virtualization environments don't scale particularly well, never mind that in some cases, they contradict the most basic values of server virtualization technology.

Continuing our integration theme with various server virtualization technologies, today i'm going to show you what we're doing in order to accelerate Backup and Recovery of Virtual Machines in Microsoft Hyper-V R2 environments and do so in manner where we do not impact the performance of the VM, the physical server host itself or the array. 

Continue reading "Sneak Preview: SnapManager for Hyper-V (SMHV)" »

October 02, 2009

ESXi - mbrscan/mbralign

As most of you know the mbrscan/mbralign utilities NetApp provides as part of the NetApp Host Utilities Kit for ESX server 5.1 require an ESX console. For those with ESXi, and depending on the protocol deployed, you may or may not be able to leverage these tools.

In particular, for those who are running NFS, there is a simple workaround which I will describe below. 

Requirements:

In order to align partitions you will need the following:

1) mbrscan/mbralign

2) Linux Guest

Steps:

1) Export and Mount the NFS volume/datastore directly onto the Linux Guest

# mkdir /nfs_datastore

# mount IP_adress_of_NFS_Server:/vol/nfs_datastore  /nfs_datastore

2) Download mbrscan/mbraling into some directory in the Linux Guest. I use /sbin but /usr/sbin is probably a better choice for non-OS binaries/utilities.

 

Mbrscan

Before you proceed with this step, you will need to make sure that either, your VMs have VMware Snapshots, or they are powered-off, otherwise mbrscan will fail.

Single VM

If you'd like to scan a single VM run:

# /usr/sbin/mbrscan <path to the flat.vmdk>

Multiple VMs

If you have a lot of VMs in the Datastore use "find" which will scan the entire datastore and will report the alignment status of all the vmkds for each VM present.

# find /nfs_datastore -name "*-flat.vmdk" -maxdepth 3 -exec /usr/sbin/mbrscan {}";"

Mbralign

Upon detecting which VMs, or rather vmdks, require partition alignment, you can use mbralign to address the issue.

Make sure you have enough space in the datastore to accommodate another copy of the target flat.vmdk and .vmdk files, because prior to partition alignment mbralign will make backup copies of these files.  Additionally, the target VM needs to be powered off and you can't have a VMware snapshot associated with it during this process.

However, if you do happen to have a VMware snapshot, the tool is intelligent enough to detect it and it will throw an error:

root@rhel1 WinXp2]# /sbin/mbralign WinXp2-flat.vmdk

Error: WinXp2.vmdk has a snapshot (WinXp2-000001.vmdk).  All snapshots must be removed before using this tool.

Unlike mbrscan, mbralign, works on a single vmdk at a time so:

# /usr/sbin/mbralign <path to the flat.vmdk>

After the process completes, power-up your vm and make sure everything is functioning properly. Then, make sure to remove the backup files.

Unmount

Once everything is functioning properly, remember to unmount the NFS datastore from the Linux Guest.

# cd /

# umount /nfs_datastore

Pretty simple stuff.

Technorati Tags: ,,

September 01, 2009

SnapManager for Virtual Infrastructure 2.0

As some of you may have seen NetApp, yesterday, announced, an enhanced version of SnapManager for VI (SMVI 2.0) which among other things provides support for Single File Restores from within a VMDK. However, this is not the only enhancement provides by 2.0.

What's New with SMVI 2.0

Autosupport Integration

With SMVI 2.0, we've integrated Autosupport. This feature can be enabled or disabled on the fly. When it's enabled, SMVI will send Autosupport messages to the storage system. On a Storage System with Autosupport enabled these messages and events will be tracked by the NetApp Support Center. Basically, it's "Call Home" functionality for Host side Software.

autosupport

Continue reading "SnapManager for Virtual Infrastructure 2.0" »

August 26, 2009

vSphere: Upgrading from non-ALUA to ALUA

Since vSphere provides ALUA support and enables Round-Robin I/O via the default PSP, here are the steps to migrate from a non-ALUA to an ALUA configuration and enabe the Round-Robin algorithm using a NetApp disk array.

1) Make sure you're running a supported  ONTAP version such as any version above 7.3.1

FAS2020A> version
NetApp Release 7.3.1.1: Mon Apr 20 22:58:46 PDT 2009

2) Enable the ALUA flag on the ESX igroups on each NetApp controller

FAS2020A> igroup show -v vmesx_b
    vmesx_b (FCP):
        OS Type: vmware
        Member: 21:00:00:1b:32:10:27:3d (logged in on: vtic, 0b)
        Member: 21:01:00:1b:32:30:27:3d (logged in on: vtic, 0a)
        ALUA: No

FAS2020A> igroup set vmesx_b alua yes

FAS2020A> igroup show -v vmesx_b
    vmesx_b (FCP):
        OS Type: vmware
        Member: 21:00:00:1b:32:10:27:3d (logged in on: vtic, 0b)
        Member: 21:01:00:1b:32:30:27:3d (logged in on: vtic, 0a)
        ALUA: Yes

3) VMotion the VMs to another host in the Cluster and reboot the ESX host

4) After the Reboot, the SATP will change to VMW_SATP_ALUA and the PSP to VMW_PSP_MRU.

5) You will need to change the PSP to VMW_PSP_RR. There are 2 options
a) With the NetApp ESX Host Utilities Kit 5.1
  1a) #/opt/netapp/santools/config_mpath -m 
      -a CtlrA:username:password -a CtlrB:username:password
  2a)  You will get a message to Reboot the host 
b) Manually
  1a) # esxcli nmp satp setdefaultpsp --satp VMW_SATP_ALUA 
       --psp VMW_PSP_RR
  2a) Reboot
6) On the ESX Host verify the new setting per device
    # esxcli nmp device 

naa.60a9800050334b356b4a51312f417541
    Device Display Name: NETAPP Fibre Channel Disk (naa.60a9800050334b356b4a51312f417541)
    Storage Array Type: VMW_SATP_ALUA
    Storage Array Type Device Config: {implicit_support=on;explicit_support=off;explicit_allow=on;alua_followover=on;{TPG_id=2,TPG_state=AO}{TPG_id=3,TPG_state=ANO}}
    Path Selection Policy: VMW_PSP_RR
    Path Selection Policy Device Config: {policy=rr,iops=1000,bytes=10485760,useANO=0;lastPathIndex=3: NumIOsPending=0,numBytesPending=0}
    Working Paths: vmhba2:C0:T2:L1, vmhba1:C0:T2:L1

July 20, 2009

NetApp Collector & Analyzer for Virtual Environments

A little bit over a year ago we undertook a project to develop a NetApp Collector & Analyzer tool that would be used to collect all storage relevant performance data from physical hosts in order to properly size our disk arrays for customers embarking on server virtualization projects. 

Now, one would ask why would NetApp try to re-invent the wheel given there are a lot of tools that can provide this capability such as VMware's Capacity Planner, Microsoft's Assessment and Planning Toolkit, and Windows native tools like Perfmon and Logman. The reason we decide to proceed with a project like this, is because either the above tools do not collect all the performance counters we need, and/or the analysis phase can be quite complex.

Having to go over 1000s of CSV files, analyze them, plot the output and decide on what values to input into our Sizing Tool is no simple task and takes time and resources. The reality is, the entire process can be quite a pain in the a$$.

So we developed a NetApp Collector and Analyzer Tool that will...collect tall he relevant performance data we're interested in and will perform analysis of 1000s of CSV files produced with the push of a button.

collector

  This is an agentless collection with the requirement being windows user with WMI access. You can set things as the:

  • Collection Interval
  • Collection Duration
  • Output Directory to dump a zip file containing the CSVs
  • Can add individual hosts
  • Can import Hosts from a CVS
  • Can export hosts to a CSV
  • Can encrypt host credentials read from a CSV

  After you've collected the data, you'd fire up the NetApp Analyzer tool. Prior to doing that, you want to unzip the zip file containing the CSVs. Then you'd start the Analyzer and you will point to to the directory the CSVs are located.

analysis

Depending on the Number of Hosts, Collection intervals and Duration, the amount of the CSVs and the size of each CSV will vary.  For example, for a 7 day run at 5 minute interval (default) for 49 hosts, I ended up with 1500 CSV files to be analyzed each of which had a 32k size. 

Under normal circumstances, analysis of 1500 files, would be a huge task, however using the NetApp Analyzer the entire process took about 15-20 minutes.

So what were the results I got back?

Analyzer1 Results

The above shows an overview of the results in terms of AVG and MAX numbers as well as the different workload characteristics. We would then take these number and input then into our NetApp Application Sizer which will produce a configuration interms of the Disk Array required and necessary capacity to sustain this load.

If you look at the above screenshot, there's a substantial deviation between the AVG and the MAX. So what would you size for? AVG or MAX? It depends.

From the above graph we see there are some spikes so we need to figure out what causes them by showing the data to the customer and asking questions. In this particular case, the spikes occur every day at approximately 9:00pm. These spikes are most likely due to some form of a backup procedure.

After, you decide, based on customer input, as to what to size for, you would use the above data points as input into the NetApp's Custom Application Sizer which will produce the necessary array and relevant configurations for the customer.

The NetApp Collector and Analyzer is available to all NetApp SEs and NetApp partners to assist their customers in server virtualization projects and proper storage sizing. It can be download from Field Portal. If you have difficulty locating it, search for "Collector". 

The NetApp Custom Application sizer is a web based tool also accessible to partners thru Field Portal.

Cheers

 

June 08, 2009

Virtual Storage Console

Back in March, I posted a blog and a video that was shown at VMworld Europe 2009 regarding the upcoming vCenter Host Utilities Kit. Since then I've gotten several inquires about it.  So let me dig a little deeper and provide a bit more insight.

First of all, the ESX Host Utilities Kit has been renamed to Virtual Storage Console (VCS). In fact, the last standalone ESX Host Utilities Kit that supports vSphere is the 5.1 version that's already posted on the NOW site. The next release will be the VSC 1.0.

UPDATE 09/02/2009: Although the VSC 1.0 has been formally announced by NetApp it is NOT yet available for download from NOW. However, it is getting ready for release but, again, I will not be able to publicly state release dates given it is NDA.

What is it?

VSC is NetApp specific software that enables administrators to manage and monitor NetApp specific storage side attributes of ESX-ESXi hosts. VSC functions as a plugin to vCenter and uses NetApp specific APIs to set and retrieve information from the array .

By default VSC uses SSL and SSL signed certificates. Furthermore any array credentials and passwords are stored using 128bit encryption.

What does it do? 

VSC adds a tab into vCenter and enables the following:

  • View Status of Storage Controllers
  • View Status of physical hosts, including versions and overall status

 esx_ctlr_status1

 

 

 

 

 

 

 

 

 

  •   Check for the proper configuration of ESX settings as it applies to:
    • Multipathing Settings
    • NFS timeouts
    • HBA driver timeouts
  • Provide the ability to set the appropriate to set the appropriate timeouts on multiple ESX hosts simultaneously with a single mouse click 

 

settings2

  • Launch FilerView from within VSC  for storage provisioning
filerview

 

  • Provides access to mbrtools (mbrscan, mbralign, mbrcreate) to identify and correct partition alignment issues

mbrtools

 

  • Ability to set credentials to access storage controllers
  • Ability to collect diagnostics from the ESX hosts, FC switches and Storage controllers
diags
  • Capacity Reports on:
    • Datastore
    • LUN
    • Volume
    • Aggregate
  • Deduplication Reports
    • Deduplication State
    • Deduplication Status
    • Space Savings
  • LUN Status
    • Pathname
    • NAA ID
    • Status - Online/Offline
    • Protocol
    • ALUA - Enable/Disable

storage_properties

Requirements:

  • DataONTAP 7.3.1.1 or later
  • VCenter Server 4.0
  • ESX/ESXi 4.0

How about ESX 3.5?

In order to use all of the VSC functionality, ESX 4.0 is needed and vCenter 4.0. However, at a minimum, vCenter 4.0 is required. ESX 3.5 hosts will be discovered however the appropriate timeouts can not be modified from within the console.

VSC Status

VSC is currently under Beta and we believe we'll have it available as soon as the Beta process is complete. I can not comment any further on this without getting into NDA specifics. 

May 27, 2009

mbraling in ESX Host Utilities 5.1

First of all, I'd like to apologize since I haven't posted in over a month but it's been a pretty tough couple of months for me and my family.

My mother was diagnosed with NHL lymphoma on April 18 and then within 30 days, she passed away. Very rapid and shocking developments that forced me to fly back and forth some 8,000 miles away. What makes it even harder was the fact that she was only 69 years old. 

On a happier note, over the past 4-5 mos I've gotten more that 40 requests from partners and customers asking for access to the mbralign utility. For those who don't know what it does, you may want to take a look at  this post.

As of May 21, 2009, NetApp released a new version of the ESX Host Utilities (HUK), 5.1, which now contains both the mbrscan and mbraling utilities. Both utilities are now fully supported by NetApp and documentation is provided as part of the ESX HUK 5.1 Install and Configuration Guide available in the Download section of the Now Site

New Additions to the HUK

  • Support for vSphere.
  • Support for role-based access control (RBAC) user names so that root access to storage controllers is not required.
  • The mbralign program that fixes misaligned VMDK partitions.
  • New timeout values added to config_hba to support software iSCSI initiators using 10 Gb Ethernet. 
  • Updated SNIA API libraries for Emulex and QLogic adapters.
  • An -expert option for the Host Utilities install command that installs the Host Utilities components but does not set timeouts or paths.
  •  

    April 03, 2009

    SnapDrive for Windows 6.1 Update

    I've talked about Snapdrive at least once the past 2 years, here , but for those not familiar with it,  I will provide a high level overview.

    SnapDrive (aka SDW) is part of NetApp's Server Suite Software that simplifies provisioning and increases availability, reliability of application data by tightly integrating with our SnapManager solutions part of Application Manageability SW Suite. 

    NMS

    • SDW Key FeaturesSDW1
      • Simplified provisioning and robust Snapshot™ management
      • On-the-fly LUN creation
      • File system consistent Snapshot copies
      • Instantaneous Backups 
      • Rapid restores
    • Increased Storage Utilization and Efficiency
      • Dynamic LUN Expansion
      • Dynamic LUN Shrink with Windows Server 2008 (New)
      • Immediate creation of space efficient clones of application data
      • NTFS Block Space Reclamation for Physical and Virtual environments

    As it is typical with any software product out there, with every release there are bug fixes and new functionality. The 6.1 release follows that rule as well. So what's new?

    • Server Virtualization
      • Support for Windows Server 2008 Hyper-V
        • Parent OS (Server Core, Full Install, Hyper-V Server)
      • VMware GuestOSSDW11
        • Allow creation of RDM LUN when OS vmdk resides in NFS Datastore
          • Drop down window lists Target VMFS Datastore(s) for Mapping file
    • Infrastructure
      • IPv6 support
        • iSCSI over IPv6
        • HTTP/HTTPS over IPv6
        • SMTP notification over IPv6
      • FCoE support
    • Security
      • Storage Access Control
    • Storage Efficiency
      • Space Reclamation of Thin Provisioned volumes
      • Online shrink of NTFS and LUN

    Hype-V Support Specifics

      • LUN provisioning and Snapshot managementSDW 2
      • Support for Windows Failover Clustering
      • Support for Hyper-V quick Migration
      • VSS auto-recovery
        • Backup and Restore
      • Enables 3rd party VSS Requestors for Backup and Restore
      • Integrates with NetApp's HyperVIBE solution
      • MMC Changes
        • Displays details about Hyper-V VMs
        • Displays details about Physical Host

    Storage Access Control

    Without a doubt, one the areas that SDW needed to improve was Access Control. With previous releases, each volume, qtree, lun was available for SDW operations. Pre-SnapDrive 6.1SDW4

    With the 6.1 release, this has been addressed, and now the functions of the Storage Admin can be separated from the functions of the Server admin for delegated environments. 

    The new release uses an array base XML file to store access control information. Access control is applied at 3 levels, Volume, Qtree, LUN and there are 3 Access Control Types: Read, Write, and Delete.  

    For every SnapDrive® operation, an Access SDW5Check is performed by reading the content of this file. Access Check verifies whether a SnapDrive user can perform an operation on a given storage system resource. This file is under the control of Storage Administrator.

    Any attempt to create a LUN, a Snapshot, or restore without proper authorization  will fail and will be logged.

    SDW6

     

     

     

     

    LUN Grow-Shrink

    With this release we've combined the LUN Grow capability previously available with SnapDrive, with the new LUN Shrink operation now available with Windows Server 2008,  using a Single interface. Just drag the Slide Bar to either direction depending on what you want to accomplish. SDW7

     

     

     

     

     

     

    Usability Improvements

    • Select a Snapshot, click it, View the LUN(s) , and mount whichever one you'd like onto the host by selecting the "Connect Disk" option. There's no need to type the LUN Path. SDW8
    • Add Volume Labels so LUNs can be identified in Disk Management and Explorer

    SDW9

    • SnapDrive will now Auto-Populate all Microsoft Clustered Nodes

    SDW10

    In summary, the new SDW release, enables backup and restore of Hyper-V VMs, improves upon existing VMware capabilities, addresses Storage Efficiencies by providing NTFS block reclamation for Thin Provisioned volume and LUN shrink, in Virtual and Physical environments. Additionally, it adds IPv6 support, introduces FCoE support and Storage Access Control. SDW 6.1 is scheduled to post on the NOW site within the few days.

    Technorati Tags: ,
    © NetApp, Inc.  |  "Safe Harbor" Statement  |  Privacy Policy