ibm system storage n series virtual storage console … system storage n series virtual storage...

IBM System Storage N series

Virtual Storage Console 4.1 for VMwarevSphere Release Notes

GC52-1351-09

��

Contents

Virtual Storage Console 4.1 for VMware vSphere Release Notes . . . . . . . . . . . . 1

New and changed features. . . . . . . . . . . . . . . . . . . . . . . . . . 5

Virtual Storage Console for VMware vSphere limitations . . . . . . . . . . . . . . . 7High-latency networks affect time required for rendering . . . . . . . . . . . . . . . . 7VSC for VMware vSphere halts when installed on vCenter Server managing multiple ESX/ESXi hosts 7Limitations that affect the Monitoring and Host Configuration capability . . . . . . . . . . . 8Limitations that affect the Provisioning and Cloning capability . . . . . . . . . . . . . . 8Limitations that affect the Optimization and Migration capability . . . . . . . . . . . . . 8Limitations that affect the Backup and Recovery capability and Restore Agent. . . . . . . . . 10

Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Known issues with VSC for VMware vSphere capabilities . . . . . . . . . . . . . . . 13

No IP address found if VMkernel and storage systems not in same network . . . . . . . . 14VSC for VMware vSphere log export and file downloads fail when using IE 9. . . . . . . . 15Volume container not destroyed even if the last LUN had been deleted . . . . . . . . . . 16VSC for VMware vSphere fails to establish a secure connection with storage system. . . . . . 16Restarting the service delays start of VSC for VMware vSphere for 90 seconds . . . . . . . 16Application configuration error . . . . . . . . . . . . . . . . . . . . . . . 16Out of memory or script errors . . . . . . . . . . . . . . . . . . . . . . . 17Error message "permission denied" when accessing the vSphere Client . . . . . . . . . . 17Clicking several links concurrently in the navigation pane results in an error . . . . . . . . 18Error message "A script on this page is causing Internet Explorer to run slowly..." . . . . . . 18Problem occurs when starting the vSphere Client if Virtual Storage Console server is unavailable 18Security certificate warnings displayed . . . . . . . . . . . . . . . . . . . . . 18

Known issues with Monitoring and Host Configuration . . . . . . . . . . . . . . . . 19Information on guest OS timeout scripts . . . . . . . . . . . . . . . . . . . . 20Information on QFull settings in vSphere 5.1 . . . . . . . . . . . . . . . . . . . 20Monitoring and Host Configuration tasks not updating correctly in vSphere 5.1 . . . . . . . 20Information on the NFS VAAI Plugin . . . . . . . . . . . . . . . . . . . . . 20ESXi might finish alignment with different LBAs than stated with the -- preview . . . . . . 20mbralign fails to align on Windows Server 2003 64-bit systems . . . . . . . . . . . . . 21mbralign for ESXi takes a long time to align files . . . . . . . . . . . . . . . . . 21VM does not boot after running mbralign . . . . . . . . . . . . . . . . . . . . 21Data collection fails with "unknown error" on Windows Server 2008 and 2008 R2 systems . . . . 21Storage Details - SAN panel has no details . . . . . . . . . . . . . . . . . . . 22MPIO Settings still shows Alert icon after running Set Recommend Values . . . . . . . . . 23Storage configuration updates not displayed by Monitoring and Host Configuration . . . . . 23Windows cluster disk reservation lost after faults in ALUA configuration . . . . . . . . . 23Windows guest OS might crash during storage faults because of virtual memory use . . . . . 23ESX with Windows Server 2003 MSCS guest uses partner path after controller giveback . . . . 24ESX or ESXi 4 in an FC or FCoE configuration with ALUA might show all dead paths for someLUNs after a controller fault . . . . . . . . . . . . . . . . . . . . . . . . 25Virtual machine disk I/O throughput can drop without sufficient physical memory . . . . . . 25

© Copyright IBM Corp. 2013 iii

Cisco 10-Gb network or FCoE switch port in error disabled state . . . . . . . . . . . . 26vSphere Client shows inactive datastores for ESX/ESXi hosts . . . . . . . . . . . . . 26Host discovery fails when VMware DPM powers down servers . . . . . . . . . . . . 26

Known issues with Provisioning and Cloning . . . . . . . . . . . . . . . . . . . 27NTFS partitions on dynamic disks not detected during space reclamation operation . . . . . . 28Provisioning and Cloning fails to discover storage systems if licensed_feature.iscsi.enable=off . . 28Provisioning a datastore on a newly added vFiler unit fails . . . . . . . . . . . . . . 28Wrong disk format displayed after cloning a thin disk virtual machine on an NFS datastore . . . 29(Data ONTAP operating in 7-Mode) Fibre Channel datastore mount fails when initiator uses sameLUN ID in igroups on both cluster storage systems. . . . . . . . . . . . . . . . . 29Cannot mount NFS datastores created using the -actual parameter . . . . . . . . . . . 29Misalignment detection on iSCSI (VMFS) datastores does not work on vCenter 4.0 Update 2 . . . 29Fibre Channel datastore mount failure during Backup and Recovery mount and unmountprocesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29VMware vSphere 5.x datastore limits do not apply in mixed vSphere environments . . . . . . 30Qtree Redeploy limitations . . . . . . . . . . . . . . . . . . . . . . . . . 30Cloning fails with move error in log . . . . . . . . . . . . . . . . . . . . . . 30"Clone operation in progress" error after canceling task . . . . . . . . . . . . . . . 31Hardware compatibility error . . . . . . . . . . . . . . . . . . . . . . . . 31VM creation progress indicators do not match . . . . . . . . . . . . . . . . . . 31Storage controller data can take several seconds to load . . . . . . . . . . . . . . . 31Canceled tasks are not deleted from Recent Tasks pane . . . . . . . . . . . . . . . 32Misaligned VM file system impacts performance . . . . . . . . . . . . . . . . . 32Datastore Destroy operation fails . . . . . . . . . . . . . . . . . . . . . . . 33Performance is degraded when requesting large number of clones. . . . . . . . . . . . 33Password in custom specification not accepted . . . . . . . . . . . . . . . . . . 33VMs are not created . . . . . . . . . . . . . . . . . . . . . . . . . . . 33VMs remain after Destroy operation . . . . . . . . . . . . . . . . . . . . . . 33Multiple IPs are used on storage system . . . . . . . . . . . . . . . . . . . . 34Connectivity to storage controller is lost . . . . . . . . . . . . . . . . . . . . 34Redeploy fails on new virtual hard drive . . . . . . . . . . . . . . . . . . . . 34NFS error during Redeploy. . . . . . . . . . . . . . . . . . . . . . . . . 34Do not use e0M port . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Internet script error during Redeploy . . . . . . . . . . . . . . . . . . . . . 35vFiler unit restrictions are ignored if physical storage system is added with root privileges . . . 35

Known issues with Optimization and Migration . . . . . . . . . . . . . . . . . . . 35Unlisted VMDK snapshot results in virtual machine going into Other folder . . . . . . . . 35Optimization and Migration screen sometimes needs a manual update . . . . . . . . . . 36Optimized datastores incorrectly appear in misaligned folder if no storage credentials are supplied 36Display of virtual machines or datastores sometimes stops briefly . . . . . . . . . . . . 36Virtual machines spanning multiple datastores incorrectly listed as misaligned . . . . . . . 37

Known issues with Backup and Recovery . . . . . . . . . . . . . . . . . . . . . 37Discovery of FC and iSCSI datastores might fail if the FC or iSCSI feature is not enabled on somehardware platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Restoring a VMFS virtual machine causes loss of independent disks . . . . . . . . . . . 39VMDKs attached to a virtual machine are fewer than reported . . . . . . . . . . . . . 39VMDKs should be removed from original datastore . . . . . . . . . . . . . . . . 40List of available virtual entities does not change if two datacenters have the same name . . . . 40Restoring a virtual machine to a current datastore fails . . . . . . . . . . . . . . . 40Restoring a virtual machine fails with the error “remove Hard disk 2” . . . . . . . . . . 40

iv IBM System Storage N series: Virtual Storage Console 4.1 for VMware vSphere Release Notes

Restoring a VMDK to an alternate datastore causes loss of the original VMDK on a virtualmachine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Virtual machine cannot power on after NFS datastore is restored . . . . . . . . . . . . 41Unable to mount an NFS volume if the export policy for the parent volume and the mountedbackup volume are not the same . . . . . . . . . . . . . . . . . . . . . . . 41Mounted backup not automatically removed when the restore session expires . . . . . . . . 41Problem occurs during unmount of backup copy of datastore . . . . . . . . . . . . . 42Single file restore on a Windows Server 2008 sometimes fails to bring disk online . . . . . . 42Single file restore does not automatically support VMDKs with multiple partitions . . . . . . 42Successful backup job might trigger a notification during backup . . . . . . . . . . . . 43Virtual machine is unresponsive during a backup . . . . . . . . . . . . . . . . . 43Running a script during backup results in an error . . . . . . . . . . . . . . . . . 43Backup and Recovery cannot verify whether the scripts ran successfully . . . . . . . . . 43vCenter Server displays an error message that virtual machine has two VMDKs with same UUID 43Mounting more than 15 disks on virtual machine fails . . . . . . . . . . . . . . . . 44Automount is enabled by default . . . . . . . . . . . . . . . . . . . . . . . 44Problem occurs during unmount of backup copy of datastore . . . . . . . . . . . . . 44Unable to verify which disk is being restored. . . . . . . . . . . . . . . . . . . 44Virtual machine is unresponsive during a backup that uses a VMware snapshot . . . . . . . 45CLI times out during a backup . . . . . . . . . . . . . . . . . . . . . . . 45Unable to download Restore Agent setup file using Internet Explorer on Windows 2003 . . . . 45Unable to retrieve deleted backup in offline session of Restore Agent (378453) . . . . . . . . 45Problem occurs during restore of virtual machine or datastore from a mounted backup on thesame ESX server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Unable to delete restore session even if source virtual machine has been deleted . . . . . . . 46Virtual machine cannot power on after it is restored and added to the vCenter Server . . . . . 46Cannot power on a virtual machine that has a VMware consistency snapshot . . . . . . . . 46Disconnecting the FC initiator used to mount a LUN clone from the ESX server results in themounted backup being removed from the server . . . . . . . . . . . . . . . . . 46Attaching a .sfr file using Outlook Web Access (OWA) might fail . . . . . . . . . . . . 46Deleting a nonexistent restore session results in an error . . . . . . . . . . . . . . . 47Drive letters that are used for network mapped drives might be incorrectly displayed as availabledrive letters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Notification e-mail for restore session contains an IPv6 address. . . . . . . . . . . . . 47Restore session fails when using vFiler root volume . . . . . . . . . . . . . . . . 47

Fixed issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Fixed issues: Multiple VSC for VMware vSphere capabilities . . . . . . . . . . . . . . 49Fixed issues: Monitoring and Host Configuration . . . . . . . . . . . . . . . . . . 50Fixed issues: Provisioning and Cloning . . . . . . . . . . . . . . . . . . . . . . 50Fixed issues: Optimization and Migration . . . . . . . . . . . . . . . . . . . . . 51Fixed issues: Backup and Recovery . . . . . . . . . . . . . . . . . . . . . . . 52

Where to find additional information . . . . . . . . . . . . . . . . . . . . . . 53

Websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Copyright and trademark information . . . . . . . . . . . . . . . . . . . . . 57Trademark information . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Contents v

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

vi IBM System Storage N series: Virtual Storage Console 4.1 for VMware vSphere Release Notes

Virtual Storage Console 4.1 for VMware vSphere ReleaseNotes

Virtual Storage Console 4.1 for VMware vSphere consists of four capabilities:Monitoring and Host Configuration, Provisioning and Cloning, Optimizationand Migration, and Backup and Recovery. These capabilities allow you towork with VMware and N series storage systems.

The installation instructions and information about using each of thecapabilities in Virtual Storage Console for VMware vSphere are in the VirtualStorage Console 4.1 for VMware vSphere Installation and Administration Guide.

Version numbers for Virtual Storage Console for VMware vSpherecapabilities

While this is the 4.1 release of Virtual Storage Console for VMware vSphere,the different components of Virtual Storage Console for VMware vSpheremight use different numbering schemes internally.

The following table summarizes the capability version numbers for VirtualStorage Console 4.1 for VMware vSphere:

Virtual StorageConsoleversion

Monitoringand HostConfiguration

Optimizationand Migration

Provisioningand Cloning

Backup andRecovery

4.1 4.1 1.1 4.1 5.0

System Requirements for Virtual Storage Console forVMware vSphere

Before you install the Virtual Storage Console for VMware vSphere software,you must ensure that your storage system conforms to the software,hardware, and operating system requirements.

For the most up-to-date information on the system requirements, see theinteroperability matrix, available on the IBM N series support website, whichis accessed and navigated as described in Websites.

© Copyright IBM Corp. 2013 1

Updates to the Virtual Storage Console 4.1 for VMwarevSphere Release Notes

The Release Notes are updated between product releases, as new informationis uncovered. It is a good practice to check the Release Notes on a regularbasis so that you can find out about any changes to the software.

The Release Notes were updated in October 2012 to add the followinginformation:v The Provisioning and Cloning capability cannot clone virtual machines that

have FaultTolerance enabled. See“Virtual machines with FaultToleranceenabled cannot be cloned” on page 8

v Several issues have been seen when using Optimization and Migration witha virtual machine that has FaultTolerance enabled. See “Optimization andMigration issues seen when FaultTolerance enabled” on page 9

v If you are running Internet Explorer 9 with the Do not save encryptedpages to disk option enabled, an error occurs when you attempt to exportVSC for VMware vSphere log files. See “VSC for VMware vSphere logexport and file downloads fail when using IE 9” on page 15

v In some environments, VSC for VMware vSphere does not delete thevolume container even though the last LUN has been deleted and theoption "Delete a volume if the last LUN in it has been deleted" is enabled.See “Volume container not destroyed even if the last LUN had beendeleted” on page 16

v Because of an issue with Data ONTAP, VSC for VMware vSphere fails toconnect to a storage system using SSL if the ssl.v2.enable option is set tofalse. See “VSC for VMware vSphere fails to establish a secure connectionwith storage system” on page 16

v You can now download either a 60-second or a 190-second guest OS scriptthat you can use to set the SCSI I/O timeout values for supported Linux,Solaris, and Windows guest operating systems. See “Information on guestOS timeout scripts” on page 20

v vSphere 5.1 handles Task Set Full (QFull) conditions differently fromvSphere 4.x and 5.0. See “Information on QFull settings in vSphere 5.1” onpage 20

v In a vSphere 5.1 environment, the Update feature of the Monitoring andHost Configuration capability sometimes appears to hang. See “Monitoringand Host Configuration tasks not updating correctly in vSphere 5.1” onpage 20

v If you execute the Reclaim Space feature on a virtual machine that hasNTFS partitions on a dynamic disk, Provisioning and Cloning incorrectlyreports that there were no NTFS partitions. See “NTFS partitions ondynamic disks not detected during space reclamation operation” on page 28

2 IBM System Storage N series: Virtual Storage Console 4.1 for VMware vSphere Release Notes

v In environments where the storage system is running Data ONTAPoperating in 7-Mode and the parameter licensed_feature.iscsi.enable is set tooff, Provisioning and Cloning fails to discover the storage system. See“Provisioning and Cloning fails to discover storage systems iflicensed_feature.iscsi.enable=off” on page 28

v In some cases, efforts to provision a new datastore on a newly added vFilerunit fail unless you first add a datastore to the physical storage systemcontaining the vFiler unit. See “Provisioning a datastore on a newly addedvFiler unit fails” on page 28

v In some cases, the cloning feature of the Provisioning and Cloningcapability incorrectly displays the cloned disk format as thin even thoughyou specified the thick disk format. See “Wrong disk format displayed aftercloning a thin disk virtual machine on an NFS datastore” on page 29

v If the Optimization and Migration capability encounters a virtual machineswith an unlisted VMDK snapshot during a scan operation, it places thatvirtual machine in the Other folder. See “Unlisted VMDK snapshot resultsin virtual machine going into Other folder” on page 35

v In some cases, the Optimization and Migration screen fails to automaticallyupdate and must be manually updated. See “Optimization and Migrationscreen sometimes needs a manual update” on page 36

v When you use the Optimization and Migration capability withoutsupplying credentials for the storage systems, optimized virtual machinessometimes appear in the misaligned folder. See “Optimized datastoresincorrectly appear in misaligned folder if no storage credentials aresupplied” on page 36

v When you are mounting a backup, if the parent NFS volume has acustomized export policy but the ESX server to which you are mounting thevolume has a default export policy, an error occurs in the Backup andRecovery capability and the mount operation fails. See “Unable to mountan NFS volume if the export policy for the parent volume and the mountedbackup volume are not the same” on page 41

v When using the Backup and Recovery capability to create a backup job, thelist of available virtual entities that you can select for a backup job does notchange depending on the datacenter that you select if two datacenters havethe same name. See “List of available virtual entities does not change if twodatacenters have the same name” on page 40

v VSC for VMware vSphere no longer displays a warning stating that InternetExplorer 9 is not a supported web browser. Virtual Storage Console 4.1 forVMware vSphere removes that warning. See “Internet Explorer 9 warningmessage no longer applies in VSC 4.1 for VMware vSphere” on page 49

Virtual Storage Console 4.1 for VMware vSphere Release Notes 3

New and changed features

Virtual Storage Console 4.1 for VMware vSphere is an upgrade from VirtualStorage Console 4.0 for VMware vSphere and adds several new features.These features include the following:v vSphere 5.1 is now supported, but only with the VMware thick (C#) client.

This release of VSC for VMware vSphere does not support vSphere 5.1 withthe VMware web client.

v The VSC for VMware vSphere Application Programming Interface thatworks in a VMware vCloud Director deployment is now available.

v A FlexClone license is no longer required for the Backup and Recoverycapability if the storage system is running Data ONTAP 8.1 or lateroperating in 7-Mode.

v You can use silent mode to perform unattended installations and uninstallsof VSC for VMware vSphere.

v The service name has been changed to Virtual Storage Console for VMwarevSphere to better align with the product name.

v FilerView is not supported with storage systems running Data ONTAP 8.1or later. To manage LUNs on storage systems running Data ONTAP 8.1 orlater operating in 7-Mode, you can download OnCommand SystemManager.

v A new guest OS timeout script has been added that allows you to set theSCSI I/O timeout value to 60 seconds.

v While the NFS Plug-in for VMware VAAI is not shipped with VSC forVMware vSphere, you can use the Monitoring and Host Configurationcapability to install it.

v The Provisioning and Cloning capability adds support for the following:– During cloning operations, you can select a vServer as a target.– You can specify whether the new clones are powered on when the

cloning operation completes and, if so, whether they are all powered onat once or whether they are powered on in a staggered manner.

– The Reclaim Space feature now restores virtual machines to the poweredon or powered off state they were in before the operation started.

v The Optimization and Migration capability shows the status of thealignment process.

v The Backup and Recovery capability has added support for the following:– Vfiler tunneling on the physical storage system that contains the vFiler

units.


– Restoring virtual machines and VMDKs to the current datastore afteryou move a virtual machine using Storage vMotion or SDRS.


Virtual Storage Console for VMware vSphere limitations

To use VSC for VMware vSphere most efficiently, you should be aware that itsperformance can be affected by known issues with a particular feature, suchas a network, or by features that a VSC for VMware vSphere capability doesnot support, such as a specific operating system version. You should alsoknow that some of these limitations have workarounds that you can use.v “High-latency networks affect time required for rendering”v “VSC for VMware vSphere halts when installed on vCenter Server

managing multiple ESX/ESXi hosts”v “Limitations that affect the Monitoring and Host Configuration capability”

on page 8v “Limitations that affect the Provisioning and Cloning capability” on page 8v “Limitations that affect the Optimization and Migration capability” on page

8v “Limitations that affect the Backup and Recovery capability and Restore

Agent” on page 10

High-latency networks affect time required for rendering

High-latency networks take longer to render objects. The rendering time isalso affected by the number of vSphere clients and whether these clients areon the same machine as the vCenter Server.

For example, suppose you want to load SAN details on 300 remote vSphereclients over a high-latency network. This task can take several minutes.

Workaround: There is no workaround because this is normal behavior forhigh-latency networks.

VSC for VMware vSphere halts when installed on vCenter Server managingmultiple ESX/ESXi hosts

Installing VSC for VMware vSphere on a vCenter Server that is managing alarge number of ESX/ ESXi hosts can cause VSC for VMware vSphere to stopworking properly.

What happens is that the vCenter Server consumes all the CPU in order tomanage the ESX/ESXi hosts. As a result, the vSphere Plugin Frameworkservice cannot respond to requests from the VSC for VMware vSpherecapabilities. This causes the capabilities to stop working.


Workaround: Make sure that VSC for VMware vSphere has sufficient CPUand memory resources to run with the number of ESX/ESXi hosts in yourenvironment. The amount of memory and resources required varies based onyour system setup.

Limitations that affect the Monitoring and Host Configuration capability

Before you use the Monitoring and Host Configuration capability of VSC forVMware vSphere, you must be aware that you cannot use the capability incertain circumstances.

mbralign is not supported on Windows Server 2008 andabove

The mbralign program is not supported on Windows Server 2008, WindowsServer 2008 R2, or Windows Server 2008 R2 SP1. By default, these versions ofWindows Server 2008 are configured with GPT. Because of the offset of thefile system, these systems normally do not need to be aligned.

Note: In this situation with mbralign, the term Windows Server 2008 is usedto refer to Windows Server 2008, Windows Server 2008 R2, and WindowsServer R2 SP1.

Workaround: If you use mbralign with Windows Server 2008, errors mightoccur when you boot the disk. So you must restore the Windows Server 2008virtual machine by using the backup files that mbralign created. The mbralignprogram creates backup *-flat.vmdk and *.vmdk files in the same directory asthe source .vmdk file.

Limitations that affect the Provisioning and Cloning capability

At this time, there is one limitation that affects the Provisioning and Cloningof VSC for VMware vSphere.

Virtual machines with FaultTolerance enabled cannot becloned

The Provisioning and Cloning capability cannot clone virtual machines thathave FaultTolerance enabled. This type of cloning operation is not supportedby vCenter Servers. The Provisioning and Cloning capability follows thevCenter server guidelines for cloning.

Limitations that affect the Optimization and Migration capability

At this time, there are some limitations that affect the Optimization andMigration capability of VSC for VMware vSphere.


Optimization and Migration issues seen when FaultToleranceenabled

Several Optimization and Migration issues have been found when workingwith virtual machines that have FaultTolerance enabled.

If a virtual machine has FaultTolerance enabled, Optimization and Migrationcannot perform the following tasks:v Scan the virtual machine when it is powered on and residing on a VMFS

datastore.v Migrate the virtual machine.

If you are using vSphere 5.1 and you attempt to migrate a virtual machinewith FaultTolerance enabled, the migration fails, and the associated taskremains incomplete. You must restart the vCenter service to clear this task.

In addition, Optimization and Migration lists the primary and secondaryvirtual machines in a FaultTolerance configuration.

Windows Server 2008 R2 SP1 virtual machines incorrectlyshown as unaligned

The Optimization and Migration capability cannot scan virtual machines thatare running Windows Server 2008 R2 SP1, so it lists them as unaligned andplaces them in the Other folder in the Virtual Machine Alignment panel.

This issue is the result of a limitation of VMware's Virtual Disk DevelopmentKit (VDDK).

Normally these disks are aligned, so this should not create a problem.

Time required for scanning datastores increases in largeenvironments

If you have a large number of virtual machines, the Optimization andMigration capability scan operation can take a long time.

For example, in tests using 1,371 virtual machines, three ESX hosts, and 140datastores, the scan took 40 minutes.

When scanning virtual machines, the Optimization and Migration capabilityuses VMware snapshots. Taking these snapshots increases the time requiredfor the scan. As a result, as more virtual machines are scanned, the longer thescan takes.

It is a good practice to schedule scans for non-critical production times.

Virtual Storage Console for VMware vSphere limitations 9

Limitations that affect the Backup and Recovery capability and Restore Agent

Before you back up and restore datastores or virtual machines, you must beaware that you cannot use the Backup and Recovery capability of VSC forVMware vSphere as well as the Restore Agent in certain circumstances.

Following are some restrictions to using the Backup and Recovery capability:v Backup and Recovery does not support initiating a multipath SnapMirror

configuration from a backup.However, because Backup and Recovery does support a single-pathSnapMirror initiation from a backup, you can use a multipath SnapMirrorconfiguration along with Backup and Recovery if you ensure that theSnapMirror process occurs on a frequent schedule and is triggered from thestorage system rather than from within Backup and Recovery through theSnapMirror job option.

v Backup and Recovery does not back up traditional volumes; it only backsup FlexVol volumes.

v Backup and Recovery does not restore a datastore that has been removedfrom vCenter Server after a backup.

v Backup and Recovery cannot mount VMFS-5 file system backups on ESX4.x hosts.

v Backup and Recovery does not support multiple vCenter Serverssimultaneously.

v Backup and Recovery does not support datastores spanning more than onevolume.

v Backup and Recovery does not support VMFS datastores created with twoor more LUN extents.

v Backup and Recovery cannot take VMware snapshots of Windows virtualmachines that have iSCSI LUNs connected through Microsoft iSCSISoftware Initiator or that have NPIV RDM LUNs.

You can back up such virtual machines without selecting the PerformVMware consistency snapshot option. However, raw device maps are notbacked up and are not recoverable from these backups.

For more information, see VMware knowledge base article 1009073 Unable totake a quiesced VMware snapshot of a virtual machine.

In addition to the limitations that affect the Backup and Recovery capability,there are also limitations that affect the Restore Agent, which works with theBackup and Recovery capability during the restore process. The Restore Agentlimitations include the following:v It does not support the mounting of GPT partitioned disks on Windows XP.v It does not support dynamic disks.


http://kb.vmware.com/kb/1009073


v It does not support IDE controllers.

Virtual Storage Console for VMware vSphere limitations 11

Known issues

You must be aware of certain known issues and workarounds for VirtualStorage Console 4.1 for VMware vSphere so that you can use the productmore effectively. Some of these issues apply to all capabilities, while othersapply to only a single capability.v “Known issues with VSC for VMware vSphere capabilities”v “Known issues with Monitoring and Host Configuration” on page 19v “Known issues with Provisioning and Cloning” on page 27v “Known issues with Optimization and Migration” on page 35v “Known issues with Backup and Recovery” on page 37

Known issues with VSC for VMware vSphere capabilities

VSC for VMware vSphere capabilities has the following known issues:v “No IP address found if VMkernel and storage systems not in same

network” on page 14v “VSC for VMware vSphere log export and file downloads fail when using

IE 9” on page 15v “Volume container not destroyed even if the last LUN had been deleted” on

page 16v “VSC for VMware vSphere fails to establish a secure connection with

storage system” on page 16v “Restarting the service delays start of VSC for VMware vSphere for 90

seconds” on page 16v “Application configuration error” on page 16v “Out of memory or script errors” on page 17v “Error message "permission denied" when accessing the vSphere Client” on

page 17v “Clicking several links concurrently in the navigation pane results in an

error” on page 18v “Error message "A script on this page is causing Internet Explorer to run

slowly..."” on page 18v “Problem occurs when starting the vSphere Client if Virtual Storage

Console server is unavailable” on page 18v “Security certificate warnings displayed” on page 18


No IP address found if VMkernel and storage systems not in samenetwork

Provisioning and Cloning and Optimization and Migration tasks might end inerror if at least one VMkernel IP address and one storage system IP addressare not in the same network.

If kernel and storage system IP addresses are not in the same network, thefollowing error is logged:

Unable to continue. No ip addresses found when cross-referencing kernel ipaddresses and addresses on the controller.Unable to find a matching network to NFS mount volume to these hosts.

Workaround: Perform either of the following tasks:v Make sure that at least one VMkernel IP address and one storage system IP

address are in the same network.v To allow mounting across all subnets or to specify allowed networks, use

the following settings in the preferences file. These settings allow only thespecified networks to map NFS datastores or iSCSI-based VMFS datastores,respectively:

default.allow.nfs.mount.networksdefault.allow.iscsi.mount.networks

In the following example, all NFS networks that share a common subnet canbe used to mount datastores:

<entry key="default.allow.nfs.mount.networks" value="ALL"/>

In the following example, only the 192.168.51.0 and 10.11.0.0 networks canmap iSCSI-based VMFS datastores:

<entrykey="default.allow.iscsi.mount.networks"value="192.168.51.0;10.11.0.0"/>

There is a separate preferences file for Provisioning and Cloning and forOptimization and Migration. These files have the following default locations:

Note: [VSC_home] is your VSC for VMware vSphere installation directory.v Provisioning and Cloning

[VSC_home]\etc\kamino\kaminoprefs.xml

v Optimization and Migration


[VSC_home]\etc\caster\kaminosdkprefs.xml

VSC for VMware vSphere log export and file downloads fail when using IE9

In some cases, exporting VSC for VMware vSphere log files fails. Thisproblem occurs when you are running Internet Explorer 9 with the Do notsave encrypted pages to disk option enabled.

The following error messages are displayed:Unable to download export-logs from [your VSC host].Unable to open this Internet site.The requested site is either unavailable or cannotbe found. Please try again later.

This issue affects all versions of VSC for VMware vSphere.

Workaround: There are two ways to resolve this issue. IBM recommends thatyou first try Method 1. If that does not work, then try Method 2.

Method 1

From the Tools menu in Internet Explorer 9, perform the following tasks:1. Click Internet Options.2. Click the Advanced tab.3. Clear the check from the Do not save encrypted pages to disk check box

in the Security area.4. Click OK.

This is the default Internet Explorer setting.

Method 2

If Method 1 does not work, then perform these following tasks:1. Start the Registry Editor.2. For a per-user setting, locate the following registry key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\InternetSettings

For a per-computer setting, locate the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings

3. On the Edit menu, click Add Value, and then add the following value:"BypassSSLNoCacheCheck"=Dword:00000001

4. Exit the Registry Editor.

Known issues 15

Related information:

Microsoft KB article: Error message when you download files by usingInternet Explorer 9 from secure websites

Volume container not destroyed even if the last LUN had been deletedIn some environments, VSC for VMware vSphere does not delete the volumecontainer even though the last LUN has been deleted and the option "Delete avolume if the last LUN in it has been deleted" is enabled.

This issue has been seen in environments using vFiler units with DataONTAP operating in 7-Mode.

Workaround: There is no workaround for this issue at this time.

VSC for VMware vSphere fails to establish a secure connection withstorage system

VSC for VMware vSphere fails to connect to a storage system using SSL. Thisproblem is seen when the storage system has the ssl.v2.enable option set tofalse because it is attempting to use SSLv3. This issue occurs because of theway Data ONTAP implements SSL.

Workaround: To prevent this issue, you must make sure the ssl.v2.enableoption is turned on. After VSC for VMware vSphere establishes a connectionwith the storage system, it then uses an SSLv3 connection.

This issue is resolved in Data ONTAP 8.0.4 and 8.1.1.

Restarting the service delays start of VSC for VMware vSphere for 90seconds

When you restart the Virtual Storage Console for VMware vSphere service,you must wait 90 seconds before you can start vSphere Client.

If you start the vSphere Client before the 90 seconds has completed, you get amessage saying the connection failed. The VSC for VMware vSphere plug-inis displayed as disabled.

After the 90 seconds has passed, you can launch the vSphere Client withoutany problem.

This issue is connected to the disk I/O speed and the amount of time it takesvSphere Plugin Framework to unpack the VSC for VMware vSphere .warfiles.

Application configuration errorYou may see an error similar to the following when using the Provisioningand Cloning capability to clone a virtual machine from non-N series or VMFS


http://support.microsoft.com/kb/2549423


datastores, or when trying to import virtual machines into VMware View. Itmay also occur in the Optimization and Migration capability when scanningnon-N series or VMFS datastores.

This application has failed to start because the applicationconfiguration is incorrect. Reinstalling the application may fix thisproblem.

Workaround: Run Windows updates to install the latest C++ runtimelibraries.

Out of memory or script errorsWhen VSC for VMware vSphere displays inventory items in a new modalwindow, vCenter allocates a new instance of an Internet Explorer window.When you apply an operation or cancel the current one, VSC for VMwarevSphere dismisses the window but cannot clear the memory consumed by thevpxclient process.

For example, if you open and cancel the destroy datastore feature severaltimes, the vpxclient process memory consumption grows, but does not shrink,even when the window is dismissed.

Workaround: Restart the vSphere Client.

Error message "permission denied" when accessing the vSphere ClientAfter installing VSC for VMware vSphere, you might see this message whenyou launch the vSphere Client to access VSC for VMware vSphere because ofthe proxy configuration in Internet Explorer.

Workaround: Disabling the Internet Explorer proxy configuration enablesaccess to VSC for VMware vSphere using the vSphere Client.

To turn off the proxy settings, complete the following steps:1. Close any vSphere Clients that are open.2. Navigate to the Control Panel.3. Click Internet Options and select the Connections tab.4. Click LAN Settings.5. Clear all the check boxes and click OK.

After you disable the proxy settings, launch the vSphere Client and click theIBM tab to verify that the error message does not appear.

Known issues 17

Clicking several links concurrently in the navigation pane results in anerror

If you click several links concurrently in the vSphere Client navigation pane,access to items in the pane might fail with the following error message:

An error has occurred in the script on this page

Workaround: If this error message appears, restart the vSphere Client. Toavoid this problem, click another link in the navigation pane only after thecurrent panel appears.

Error message "A script on this page is causing Internet Explorer to runslowly..."

You might see this message if VSC for VMware vSphere takes too long tocomplete an operation. You can adjust your Internet Explorer settings to avoidthis message.

This message does not indicate a problem with VSC for VMware vSphereother than a script taking longer to run than the timeout setting in InternetExplorer.

For instructions on adjusting the Internet Explorer timeout setting, seeMicrosoft Knowledge Base article 175500 Error message: "A script on this pageis causing Internet Explorer to run slowly".

Problem occurs when starting the vSphere Client if Virtual StorageConsole server is unavailable

If the Virtual Storage Console server is unavailable when starting the vSphereClient, the IBM N series icon does not appear.

Workaround: Restart the vSphere Client when the Virtual Storage Consoleserver is available.

Security certificate warnings displayedDepending on your web browser and security configuration, you might seesecurity certificate warnings displayed when installing and using VSC forVMware vSphere. You can safely ignore these warnings and proceed to therequested program or web page. VSC for VMware vSphere uses self-signedSSL certificates.

You might see warnings similar to the following:

The security certificate presented by this website was not issued by atrusted certificate authority.




You can also add self-signed certificates or a certificate signed by a CertificateAuthority.

Known issues with Monitoring and Host Configuration

Because Virtual Storage Console 4.0 for VMware vSphere exhibits someunexpected and potentially undesirable behavior, you should be aware ofthese issues and, if available, a workaround for resolving an issue.v “Information on guest OS timeout scripts” on page 20v “Information on QFull settings in vSphere 5.1” on page 20v “Monitoring and Host Configuration tasks not updating correctly in

vSphere 5.1” on page 20v “Information on the NFS VAAI Plugin” on page 20v “ESXi might finish alignment with different LBAs than stated with the --

preview” on page 20v “mbralign fails to align on Windows Server 2003 64-bit systems” on page 21v “mbralign for ESXi takes a long time to align files” on page 21v “VM does not boot after running mbralign” on page 21v “Data collection fails with "unknown error" on Windows Server 2008 and

2008 R2 systems” on page 21v “Storage Details - SAN panel has no details” on page 22v “MPIO Settings still shows Alert icon after running Set Recommend Values”

on page 23v “Storage configuration updates not displayed by Monitoring and Host

Configuration” on page 23v “Windows cluster disk reservation lost after faults in ALUA configuration”

on page 23v “Windows guest OS might crash during storage faults because of virtual

memory use” on page 23v “ESX with Windows Server 2003 MSCS guest uses partner path after

controller giveback” on page 24v “ESX or ESXi 4 in an FC or FCoE configuration with ALUA might show all

dead paths for some LUNs after a controller fault” on page 25v “Virtual machine disk I/O throughput can drop without sufficient physical

memory” on page 25v “Cisco 10-Gb network or FCoE switch port in error disabled state” on page

26v “vSphere Client shows inactive datastores for ESX/ESXi hosts” on page 26v “Host discovery fails when VMware DPM powers down servers” on page

26

Known issues 19

Information on guest OS timeout scriptsVSC for VMware vSphere now supports two guest OS (GOS) timeout scriptsthat you can use to set the SCSI I/O timeout values for supported Linux,Solaris, and Windows guest operating systems. The timeout values ensurecorrect failover behavior.

These scripts are provided as .ISO files in the Tools panel of the Monitoringand Host Configuration capability. There are two scripts for each operatingsystem:v A 60-second scriptv A 190-second script

In most cases, the recommended value is 60 seconds.

Information on QFull settings in vSphere 5.1vSphere 5.1 handles Task Set Full (QFull) conditions differently from vSphere4.x and 5.0. You must set the QFull settings for each device.

Monitoring and Host Configuration tasks not updating correctly invSphere 5.1

In environments using vSphere 5.1, the Update feature on Monitoring andHost Configuration does not work correctly. Tasks sometimes appear to behang. This is an issue with vSphere 5.1.

Information on the NFS VAAI PluginThe NFS VAAI Plugin does not ship with VSC for VMware vSphere. Youmust download the plug-in from the IBM N series support website (accessedand navigated as described in “Websites” on page 55) and manually install it.

ESXi might finish alignment with different LBAs than stated with the --preview

When you use mbralign for ESXi, the resulting LBAs might be different fromthe ones stated with the -- preview option. This difference does not preventthe alignment from occurring or pose a problem for the virtual machines.

The ESXi version of mbralign is based on the mbralign from ESX HostUtilities 5.1. The ESX version was updated to include bug fixes after the ESXiversion was created. The ESXi version of mbralign successfully performsalignments, so it has not been updated even though the --preview optiondisplay might not be correct.

Workaround: There are two ways to handle this issue:v Use mbralign for ESX.

Migrate the virtual machines from the ESXi server to the ESX server. Alignthem. Then migrate them back.


v Continue to use mbralign for ESXi and note that the resulting LBAs mightbe slightly different.

mbralign fails to align on Windows Server 2003 64-bit systemsThe mbralign program cannot align files on Windows Server 2003 64-bitversions. The program does not work with the NTFS 64-bit boot sectors.

Workaround: You can restore the Windows Server 2003 64-bit VM by usingthe backup file that the mbralign program created.

mbralign for ESXi takes a long time to align filesThe mbralign program for ESXi can take a much longer time to align filesthan the mbralign program used with the ESX Host Utilities 5.2.1.

This happens because the mbralign program runs in the technical supportconsole of ESXi, which is a busybox console. As a result, the number ofresources available for the application are reduced. The limited amount ofmemory causes an increase in the amount of time it takes to align the VMDKfiles.

Workaround: There is no workaround at this time because there currently isno way to increase the amount of memory in the technical support console ofESXi.

VM does not boot after running mbralignIn certain situations, a virtual machine might not boot after running thembralign program. You can revert to the backup VMDK files saved bymbralign.

There are several problems that can prevent a VM from booting after runningthe mbralign program. The workaround, however, is the same: revert to thebackup VMDK files saved by the mbralign program.

Avoid the following situations when running the mbralign program:v Do not run mbralign for a VM when the VM is powered on.v Do not run mbralign on SLES 11 guests.v Do not use the --force option when running the mbralign program on

Windows 7, Windows Server 2008, or Windows Server 2008 R2 guests.

Data collection fails with "unknown error" on Windows Server 2008 and2008 R2 systems

When running the data collection programs with VSC for VMware vSphereinstalled on a Windows Server 2008 or Windows Server 2008 R2 system, youget an "unknown error" message.

Known issues 21

In this situation, the system displays the following error message: unknownerror has occurred please see logs for details

The VSC for VMware vSphere service typically runs under the Local Systemaccount. For Windows Server 2008 and Windows Server 2008 R2, theWindows security features prevent the data collection programs from runningcorrectly under the Local System account.

Workaround: If you receive the preceding error message when running thedata collection programs, configure the VSC for VMware vSphere service torun using an Administrator account.

In the Windows Server 2008 or Windows Server 2008 R2 Services application,change the Log On properties of the VSC for VMware vSphere service to runas an Administrator account instead of the Local System account.

Storage Details - SAN panel has no detailsThe Storage Details - SAN panel in the Monitoring and Host Configurationcapability displays no details. The status of one or more storage controllers onthe Overview panel is "Unmanaged."

The storage controller must be running a minimum version of Data ONTAPsoftware that supports interfaces needed by the SAN functionality of theMonitoring and Host Configuration capability. Versions of Data ONTAPsoftware prior to 7.3.1.1 do not have these interfaces, and the Monitoring andHost Configuration capability cannot discover SAN resources. However, thecontroller itself is discovered by the Monitoring and Host Configurationcapability.

If all controllers are unmanaged (not running the minimum Data ONTAPversion), then the Storage Details - SAN panel displays nothing. When acontroller is unmanaged, neither SAN nor NAS details for that controller areavailable.

The NAS functionality of the Monitoring and Host Configuration capabilitycan work with earlier versions of Data ONTAP software. It is possible forNAS details to be displayed when SAN details cannot be displayed.

Check the IBM N series interoperability matrix on IBM N series support website (accessed and navigated as described in “Websites” on page 55) todetermine the supported versions of Data ONTAP software. At the time theseRelease Notes were published, Data ONTAP 7.3.1.1 or later was required forSAN functionality.


MPIO Settings still shows Alert icon after running Set Recommend ValuesAfter running Set Recommended Values, the MPIO Settings column for anESX host on the Monitoring and Host Configuration capability Overviewpanel might still show an Alert icon.

If a storage controller is skipped during discovery, the Monitoring and HostConfiguration capability is unable to set the MPIO settings for the paths tothat controller. The Alert icon continues to be displayed after running SetRecommended Values.

Workaround: You can check the Discovery Status panel to see if you have anyskipped controllers. If you have a skipped controller, right-click the controllerand select Modify Credentials. Clear the Skipped check box and entercredentials for the controller. Run an Update, and then run Set RecommendedValues again.

Storage configuration updates not displayed by Monitoring and HostConfiguration

When you add or remove storage resources, such as LUNs or NFS exports,the changes are not immediately displayed by the Monitoring and HostConfiguration capability.

The Monitoring and Host Configuration capability gets its configurationinformation from the vCenter Server. You must first rescan the storageadapters for the ESX host to discover changes. Then you select Update on theMonitoring and Host Configuration capability Overview panel to discover thenew resources.

Windows cluster disk reservation lost after faults in ALUA configurationA Windows cluster (Windows Server 2003 MSCS or Windows Server 2008failover cluster) running as a guest on ESX 4.0 reports disk reservations lost.The cluster service is unavailable and delayed write errors might be reported.The LUNs used by the cluster have ALUA enabled.

This problem can occur with all ESX path selection policies.

Workaround: When using ESX guest operating systems in a Windows clusterconfiguration, disable ALUA on the LUNs and use the FIXED path selectionpolicy.

Windows guest OS might crash during storage faults because of virtualmemory use

Windows guest operating systems on ESX 4.0 servers might crash during astorage fault due to a kernel in page stack error because the virtual memoryon a SAN disk is temporarily unavailable.

Known issues 23

The Windows event log might contain errors similar to the following:Event ID: 51Event Type: WarningEvent Source: DiskDescription: An error was detected on device\Device\Harddisk0\DR0 during a paging operation.

Event ID: 9Source: %HBA_DRIVER_NAME%Description: The device, \Device\ScsiPort0,did not respond within the timeout period.

Workaround: There are several possible workarounds you can try, includingthe following:v Allocating sufficient physical memory to the guestsv Placing the pagefile on local diskv Minimizing the virtual memory size on the Windows guests where possible

to minimize its usage

Note that having the pagefile on local disk does not allow vMotion on theguest to work properly, because vMotion requires a shared disk.

ESX with Windows Server 2003 MSCS guest uses partner path aftercontroller giveback

After controller giveback, the I/O path to a LUN used by a Windows Server2003 MSCS guest continues to use a partner (proxy) path. The controllerissues a partner path misconfigured message, and performance might bedegraded.

This issue occurs in a VMware ESX configuration with two Windows Server2003 MSCS guests clustered across physical ESX hosts accessing shared diskresources from a LUN on an high-availability (HA) pair. Before the issueoccurs, one controller successfully fails over to its partner. However, aftercontroller giveback, the I/O path to the LUN continues to use a partner path.This issue occurs only when the controller that usually owns the LUN is thecontroller that failed over.

During controller failover, all I/O to the failed controller switches to thepartner controller. After giveback, the I/O should return to the original paththrough the original controller. If the I/O continues through the partnercontroller, the routing is less efficient. The storage controller issues messagessaying the partner path is misconfigured to notify you that I/O is using apartner path.

In this MSCS configuration, ESX continues to use the partner path becausethat path has a SCSI reservation for the LUN. ESX uses the partner path to theLUN until the disk resource ownership is transitioned to the other VM or the


current partner path becomes unavailable. The ESX host then selects a newpath. By design, the ESX host returns to the initial preferred path that wasspecified for the LUN if it is available.

Workaround: You can manually transition the disk resources to the ESX hostwhere the other MSCS guest is located. The ESX host for that guest sends aSCSI RESERVE command to the disk, and ESX selects a local path to the LUN.

ESX or ESXi 4 in an FC or FCoE configuration with ALUA might show alldead paths for some LUNs after a controller fault

Running ESX 4 or ESXi 4 in an FC or FCoE configuration with ALUA, theESX host might indicate that all paths to a LUN are dead after one of thestorage controllers experiences a fault. This can happen in a High Availabilityconfiguration.

This issue can occur if the ESX path evaluation initiated after the faulthappens before the controller's ALUA state transition is completed.

No action is needed. If there are valid physical paths to the LUN, thecondition is cleared by either of the following events:v Periodic path evaluation occurs, which happens every 300 seconds.v An I/O is sent to the LUN.

Either event enables the host to determine the proper ALUA state and updatethe path state.

Virtual machine disk I/O throughput can drop without sufficient physicalmemory

VMware virtual machine disk I/O throughput can drop significantly whenmemory usage on other virtual machines increases. This issue occurs whenphysical memory is overcommitted and ESX must use memory reclamationand swapping.

The ESX and ESXi memory management techniques allow memoryovercommitment on the host, which works well on typical deploymentswhere the virtual machines are lightly loaded. When the working set memoryin all virtual machines combined plus the virtualization overhead exceeds thephysical memory available on the host, ESX or ESXi uses memory reclamationand swapping to provide additional memory needed for the applications. Thiscan impact the disk I/O performance. When predictable disk I/Operformance is needed and when the host does not have sufficient physicalmemory, the memory reclamation impact in a virtual machine can be limitedby reserving sufficient memory for that virtual machine.

Known issues 25

See the Managing Memory Resources chapter in the vSphere ResourceManagement Guide for additional information about memory virtualizationand performance considerations.

Cisco 10-Gb network or FCoE switch port in error disabled stateAfter storage controller faults, the ports on a Cisco 10-Gb network or FCoEswitch might go into error disabled (errdisable) state. The error disabled stateis caused by too many flow-control (pause) frames being sent to the port. Youcan configure your switch to automatically recover from this problem.

Cisco Ethernet switch ports respond to a large number of flow-control framesby disabling the port. This is intended to protect the switch from variousfailures and configuration problems. By default, after the port is disabled, itmust be re-enabled manually.

During storage controller faults, the number of flow-control frames sent to theswitch can exceed the limit and cause the port to be disabled.

Workaround: You can configure the switch to automatically recover the portfrom this state after a specified interval by using the following switchcommands:

errdisable recovery cause pause-rate-limiterrdisable recovery interval 30

For more information about the errdisable command, see the documentationfor your Cisco switch.

vSphere Client shows inactive datastores for ESX/ESXi hostsAfter a storage fault, the vSphere Client might show one or more datastoresfor an ESX/ESXi 4.1, 4.1u1, or ESXi 5.0u1 host as inactive. VMware featuresthat require the datastore to be active are not available.

Features including VMware vMotion, VMware High Availability, VMwareDistributed Resource Scheduler, and VMware Fault Tolerance are not availablewhen the datastore status is inactive.

The workaround is to rescan the storage adapters by selecting StorageAdapters on the Configuration tab in the vSphere Client and clicking Rescan.After the rescan, the vSphere Client shows the correct datastore status.

Host discovery fails when VMware DPM powers down serversMonitoring and Host Configuration discovers only hosts that are connectedand powered on.


http://www.vmware.com/pdf/vsphere4/r40/vsp_40_resource_mgmt.pdf

http://www.vmware.com/pdf/vsphere4/r40/vsp_40_resource_mgmt.pdf

If hosts are powered down by VMware Distributed Power Management,Monitoring and Host Configuration does not discover them. Be sure all hostsare powered on and not in standby before host discovery begins.

Known issues with Provisioning and Cloning

Because Virtual Storage Console 4.1 for VMware vSphere exhibits someunexpected and potentially undesirable behavior, you should be aware ofthese issues and, if available, a workaround for resolving an issue.v “NTFS partitions on dynamic disks not detected during space reclamation

operation” on page 28v “Provisioning and Cloning fails to discover storage systems if

licensed_feature.iscsi.enable=off” on page 28v “Provisioning a datastore on a newly added vFiler unit fails” on page 28v “Wrong disk format displayed after cloning a thin disk virtual machine on

an NFS datastore” on page 29v “(Data ONTAP operating in 7-Mode) Fibre Channel datastore mount fails

when initiator uses same LUN ID in igroups on both cluster storagesystems” on page 29

v “Cannot mount NFS datastores created using the -actual parameter” onpage 29

v “Misalignment detection on iSCSI (VMFS) datastores does not work onvCenter 4.0 Update 2” on page 29

v “Fibre Channel datastore mount failure during Backup and Recovery mountand unmount processes” on page 29

v “VMware vSphere 5.x datastore limits do not apply in mixed vSphereenvironments” on page 30

v “Qtree Redeploy limitations” on page 30v “Cloning fails with move error in log” on page 30v “"Clone operation in progress" error after canceling task” on page 31v “Hardware compatibility error” on page 31v “VM creation progress indicators do not match” on page 31v “Storage controller data can take several seconds to load” on page 31v “Canceled tasks are not deleted from Recent Tasks pane” on page 32v “Misaligned VM file system impacts performance” on page 32v “Datastore Destroy operation fails” on page 33v “Performance is degraded when requesting large number of clones” on

page 33v “Password in custom specification not accepted” on page 33v “VMs are not created” on page 33

Known issues 27

v “VMs remain after Destroy operation” on page 33v “Multiple IPs are used on storage system” on page 34v “Connectivity to storage controller is lost” on page 34v “Redeploy fails on new virtual hard drive” on page 34v “NFS error during Redeploy” on page 34v “Do not use e0M port” on page 35v “Internet script error during Redeploy” on page 35v “vFiler unit restrictions are ignored if physical storage system is added with

root privileges” on page 35

NTFS partitions on dynamic disks not detected during space reclamationoperation

The Reclaim Space feature provided by Provisioning and Cloning does notsupport dynamic disks. If you execute this feature on a virtual machine thathas NTFS partitions on a dynamic disk, it incorrectly reports that there are noNTFS partitions.

Provisioning and Cloning fails to discover storage systems iflicensed_feature.iscsi.enable=off

If a storage system is running Data ONTAP operating in 7-Mode and theparameter licensed_feature.iscsi.enable is set to off instead of on,Provisioning and Cloning reports an exception and does not discover thestorage controller.

This problem only occurs with Provisioning and Cloning. Monitoring andHost Configuration is able to add the storage controller.

Workaround: To enable Provisioning and Cloning to discover the storagecontroller, you must set licensed_feature.iscsi.enable to on.

Provisioning a datastore on a newly added vFiler unit failsIn some cases, efforts to provision a new datastore on a vFiler unit fail. Thisfailure occurs if you use Monitoring and Host Configuration to first add thevFiler unit and then add the physical storage system containing the vFilerunit. You cannot create a datastore on the vFiler unit unless you first createone on the physical storage system.

If you add the vFiler unit before adding the physical storage system and thenuse Provisioning and Cloning to try to create a datastore on the vFiler unit,you get the following error message:No datastore types are available. Please check if any of your hostsare in standby, maintenance mode or are in a disconnected state invCenter. Also check storage controller licenses and supportedESX host protocols.


Workaround: To prevent this problem, you must create a datastore on thephysical storage system right after you add it to VSC for VMware vSphere.After you do that, you can successfully create datastores on the vFiler unit.

Wrong disk format displayed after cloning a thin disk virtual machine onan NFS datastore

The cloning feature of the Provisioning and Cloning capability incorrectlydisplays the disk format when you specify thick format for the clone, but theoriginal virtual machine uses a thin disk format and is on an NFS datastore.The Provisioning and Cloning capability reports that the cloned virtualmachine is using thin format.

The operation actually reserves enough volume space for the thick diskformat. It just reports the format of the cloned disk incorrectly.

This issue is only seen when the original virtual machine uses thin diskformat and resides on an NFS datastore.

(Data ONTAP operating in 7-Mode) Fibre Channel datastore mount failswhen initiator uses same LUN ID in igroups on both cluster storagesystems

Mounting a datastore fails when you are using the FC protocol and theinitiator in the igroups on both storage systems in a clustered pair uses thesame LUN ID while one igroup is already using that ID.

This issue applies storage systems running Data ONTAP operating in 7-Mode.

To avoid a potential problem in the event of a failover, Data ONTAP does notallow igroup sharing across clustered storage systems.

Cannot mount NFS datastores created using the -actual parameterThe Provisioning and Cloning capability does not support mounting of NFSdatastores that have been exported using the -actual parameter.

Misalignment detection on iSCSI (VMFS) datastores does not work onvCenter 4.0 Update 2

Misalignment detection not supported in vCenter 4.0 Update 2 but supportedin vCenter 4.1 and 5.0.

Workaround: If you are running vCenter 4.0 Update 2, confirm that youriSCSI (VMFS) datastores are aligned prior to cloning operations.

Fibre Channel datastore mount failure during Backup and Recoverymount and unmount processes

If you attempt to mount an FC datastore using the Provisioning and Cloningcapability while a mount or unmount is in progress by the Backup andRecovery capability, the datastore mount might fail.

Known issues 29

Workaround: Do not mount a datastore with the Provisioning and Cloningcapability while performing a mount or unmount using the Backup andRecovery capability.

VMware vSphere 5.x datastore limits do not apply in mixed vSphereenvironments

In mixed-version vSphere environments, the maximum VMFS datastore sizeand maximum number of NFS datastores revert to vSphere 4 limits.

Qtree Redeploy limitationsThe Provisioning and Cloning capability does not support redeploying qtreesin certain cases.

The Redeploy feature is not supported in the following cases:v On qtrees residing on vFiler volumesv From NTFS qtrees to mixed qtrees

Cloning fails with move error in logA cloning task might fail when the controller cannot resolve its host name orwhen a controller resolves its host name to an IP address other than one itowns. In either case, the ndmpcopy operation fails.

When cloning fails, an error similar to the following error is logged:

ERROR com.netapp.rcu.server.jzapi.FilerUtil - Move of /vol/win7_64bit_test/ntap_rcu1268850273837/.tmpNdmpDir/Win7_64bitflat.vmdk to /vol/win7_64bit_test/ntap_rcu1268850273837/0000hd0000-flat.vmdk failed.

The following example shows a configuration in which the IP address10.61.177.220 was removed from a controller and the etc/hosts file was notupdated. The etc/hosts file contains both IP addresses.

#Auto-generated by setup Thu Nov 19 15:47:12 GMT 2009127.0.0.1 localhost 10.61.177.220 kc3140 <= (This is wrong)10.61.177.221 kc3140-e0M

The output of ifconfig -a shows that only the 10.61.177.221 address isoperational on this controller:

kc3140> ifconfig -ae0M: flags=0x2948867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500inet 10.61.177.221 netmask 0xffffff00 broadcast 10.61.177.255ether 00:a0:98:0a:22:06 (auto-100tx-fd-up) flowcontrol full

Workaround: Ensure that the controller can resolve its name to a valid IPaddress. In this example, map 10.61.177.221 to kc3140:


#Auto-generated by setup Thu Nov 19 15:47:12 GMT 2009127.0.0.1 localhost10.61.177.221 kc3140

"Clone operation in progress" error after canceling taskAfter a clone operation is canceled and the canceled message is displayed inthe Recent Tasks pane, a new clone operation request can result in an error.

If the Web service has not finished cleaning up the canceled task before a newrequest is made, the following error is displayed:

A clone operation is already in progress. Once it’s completed, try again.

Workaround: Wait a few seconds after canceling a clone operation beforestarting a new one.

Hardware compatibility errorThe destination ESX host, or the ESX hosts in the destination datacenter orcluster, are not checked for complete hardware compatibility prior to cloning.If the source and destination are not compatible, the cloning operation fails.

When a cloning operation fails due to hardware incompatibility, an error islogged. For example, a request to clone a source virtual machine with fourvirtual CPUs to an ESX host with only one physical CPU would result in thefollowing error:

Virtual Machine requires 4 CPUs to operate, but the host hardware provides1.

Workaround: Ensure that the destination hardware is compatible with thesource before executing a cloning operation.

VM creation progress indicators do not matchYou can safely ignore the mismatch of progress indicators for virtual machinecreation in vSphere Client panels.

Storage controller data can take several seconds to loadThe fields in the Specify Storage Controllers screen can take several seconds toload.

The Provisioning and Cloning capability cross-references datastore andcontroller information while loading storage controller data. The delay variesdepending on the sizes of the environment, the server running VSC forVMware vSphere, and the server running vCenter.

Known issues 31

Canceled tasks are not deleted from Recent Tasks paneCanceled Provisioning and Cloning tasks might remain displayed in thevSphere Client Recent Tasks pane indefinitely.

Workaround: To clear these tasks, do one of the following:v Restart the Windows service

1. Select Control Panel > Administrative Tools > Services.2. Right-click VMware vCenter Server and select Restart.

v Run the following commands from the command line1. net stop vpxd

2. net start vpxd

Misaligned VM file system impacts performanceIf the file system in the virtual machine is not properly aligned, a warning isdisplayed before the cloning operation begins. This allows you to correct themisalignment and avoid propagating the misalignment to the clones.Messages are also logged in the messages file on the controller and in theAutoSupport data.

Performance is significantly impacted by the block alignment of the virtualmachine file system to the controller. The Provisioning and Cloning capabilityinspects the source VMDK file of any virtual machine that is cloned. Theresult of this inspection is recorded in the log file. If the file system in thevirtual machine is not properly aligned, the following message is logged:

Partition 1 of /vol/test/ntap_rcu1236650660984/0000hd0000-flat.vmdk is NOTaligned. (LBA=63). Partition number of volume_path-flat.vmdk is NOTaligned.

For more information on alignment issues, see the following VMwaretechnical white papers, available in the ISV Solutions Resource Library, whichis accessed and navigated as described in “Websites” on page 55:v Technical report: IBM System Storage N series and VMware Virtual

Infrastructure 3 Storage - Best practicesv Technical report: Aligning file systems in virtual environments with IBM

System Storage N series - Best practicesv Technical report: Storage Block Alignment with VMware Virtual

Infrastructure and IBM System Storage N series - Correctly aligning LUNsand virtual disk files

v Technical report: VMware ESX Server 3.0 on IBM System Storage N seriesBest-practices backup case study


Datastore Destroy operation failsDuring a datastore Destroy operation, if any host cannot disconnect thedatastore, the operation fails.

Failure of the Destroy operation can be caused by a virtual machine beingpowered up after the Destroy process is initiated.

Workaround: Resolve the issue that caused the datastore disconnect to fail.Then perform the Destroy operation from the ESX host that cannot disconnect.

Performance is degraded when requesting large number of clonesCloning performance is affected by many factors, including vCenter Serverhardware configuration, number and hardware configuration of the ESX hosts,and the current load on either or both.

Workaround: Performance can degrade if you request a very large number ofclones in a single operation. If this occurs, reduce the number of clonesrequested per operation. For example, instead of requesting 2,000 clones,perform two operations of 1,000 clones each.

Password in custom specification not acceptedThe password in a custom specification might not be applied. This occurs inWindows operating systems only.

Workaround: Power up the source virtual machine, set the password in thesource virtual machine, and power it down. Then rerun the cloning request.

VMs are not createdDuring storage system takeover or giveback, virtual machine clone creationfails because the Provisioning and Cloning capability cannot communicatewith the storage controller.

Workaround: Resubmit the cloning request when the takeover or givebackprocess is complete.

VMs remain after Destroy operationAfter running the Destroy operation on a datastore, some of the VMs mightstill appear in the inventory tree.

Attempting to remove these destroyed VMs results in the following errormessage:

The request refers to an object that no longer exists or has never existed.

Workaround: Restart the vSphere Client.

Known issues 33

Multiple IPs are used on storage systemAny matching network between the storage system and the ESX VMkernel isused to mount datastores.

To prevent a network from being used to mount datastores, use the followingsetting in the preferences file:

default.restrict.mount.networks

The preferences file is stored by default in the following location, where[VSC_home] is your VSC for VMware vSphere installation directory:

[VSC_home]\etc\kamino\kaminoprefs.xml

In the following example, the networks 192.168.2.0 and 10.1.0.0 are ignoredwhen determining the storage system IP address to use for the next datastore.

<entry key="default.restrict.mount.networks" value="192.168.2.0;10.1.0.0"/>

Connectivity to storage controller is lostIf connection to the storage controller is lost, Provisioning and Cloning tasksin progress will fail.

Workaround: Resolve the communication issue. No additional steps need tobe taken in the application. The Provisioning and Cloning capability creates anew connection for each new task.

Redeploy fails on new virtual hard driveIf you attempt a Redeploy operation after adding a new virtual hard drive tothe source virtual machine rather than modifying the contents of the existinghard drives, the operation fails.

When a new virtual hard drive is added to the virtual machine source afterclones are created, the new hard drive does not exist on the clones. Therefore,there is no destination datastore identified for the new hard drive and theRedeploy operation fails.

Workaround: After adding a new virtual hard drive to a source virtualmachine, create new clones from the source rather than performing aRedeploy operation.

NFS error during RedeployThe Redeploy operation fails if an ISO is mounted to the clones that are to beredeployed.


Workaround: Remove the ISO mapping and run the operation again.

Do not use e0M portWhen adding storage controllers for use with the Provisioning and Cloningcapability, do not select the e0M port when specifying interfaces to use on thestorage controller.

Internet script error during RedeployOccasionally, an internet script error displays after clicking the Redeploy link.Click OK on the error message and the procedure completes normally.

vFiler unit restrictions are ignored if physical storage system is addedwith root privileges

If a physical filer and its vFiler units are added to the Provisioning andCloning capability, any restrictions on the vfiler unit are ignored if thephysical storage system has root privileges.

For example, a user added in vFiler context without destroy capabilities coulddestroy datastores if the vFiler unit's physical storage system was added withroot privileges.

Workaround: To restrict access to a vFiler unit, only the vFiler unit, and notthe physical storage system, should be added to the Provisioning and Cloningcapability.

Known issues with Optimization and Migration

Virtual Storage Console 4.1 for VMware vSphere exhibits some unexpectedand potentially undesirable behavior, you should be aware of these issuesand, if available, a workaround for resolving an issue.v “Unlisted VMDK snapshot results in virtual machine going into Other

folder”v “Optimization and Migration screen sometimes needs a manual update” on

page 36v “Optimized datastores incorrectly appear in misaligned folder if no storage

credentials are supplied” on page 36v “Display of virtual machines or datastores sometimes stops briefly” on page

36v “Virtual machines spanning multiple datastores incorrectly listed as

misaligned” on page 37

Unlisted VMDK snapshot results in virtual machine going into Otherfolder

If the Optimization and Migration capability encounters a virtual machinewith an unlisted VMDK snapshot while performing a scan operation, it places

Known issues 35

that virtual machine in the Other folder. The Optimization and Migrationutility does not support configurations with unlisted snapshots.Related information:

VMware KB article 1005049: Determining if there are leftover delta files orsnapshots that VMware vSphere or Infrastructure Client cannot detect

Optimization and Migration screen sometimes needs a manual updateIn some cases, the Optimization and Migration screen fails to automaticallyupdate and must be manually updated. This issue has been seen only on theVirtual Machine Alignment panel when a node is selected in the folder tree.To manually update the page, click Refresh.

Optimized datastores incorrectly appear in misaligned folder if no storagecredentials are supplied

The Optimization and Migration capability sometimes incorrectly putsoptimized datastores in the misaligned folder. This issue occurs when you donot supply storage credentials for the IBM N series storage systems.

This issue or similar issues where a datastore is placed in the wrong foldercan also occur if you use non-IBM N series storage systems, which, bydefault, do not have IBM N series storage credentials.

To avoid this problem, make sure you set up storage credentials for eachstorage system. See the VSC for VMware vSphere installation guide forinformation on setting up storage credentials.

If you want to migrate datastores from non-IBM N series storage systems, youcan use the Optimization and Migration capability to do this. After you havemigrated the datastores, make sure they are on IBM N series storage systemsthat use storage credentials.

Display of virtual machines or datastores sometimes stops brieflyIf you use the Optimization and Migration capability to scan a virtualmachine running vCenter Server, you might not be able to see informationabout the virtual machines or datastores for a brief period of time.

This is a temporary problem that occurs when the following is true:v The virtual machine being scanned is running vCenter Server.v The virtual machine requires that a VMware snapshot be made.

The snapshot occurs when the virtual machine is on VMFS or when thecontroller containing it cannot be reached. After being created, the snapshot isdeleted, which interrupts communication with the network until VSC forVMware vSphere reestablishes communication.




Virtual machines spanning multiple datastores incorrectly listed asmisaligned

In some cases, the Optimization and Migration capability places virtualmachines in the Other folder even though they are aligned. The Optimizationand Migration capability does this because it cannot access the virtualmachines after scanning them.

This situation is seen when virtual machines reside in multiple datastores andsome of the datastores are on VMFS. As part of the scan process theOptimization and Migration capability creates a snapshot of the datastore.

At this time there is no workaround for this issue.

Known issues with Backup and Recovery

Virtual Storage Console 4.1 for VMware vSphere exhibits some unexpectedand potentially undesirable behavior, you should be aware of these issuesand, if available, a workaround for resolving an issue.v “Discovery of FC and iSCSI datastores might fail if the FC or iSCSI feature

is not enabled on some hardware platforms” on page 39v “Restoring a VMFS virtual machine causes loss of independent disks” on

page 39v “VMDKs attached to a virtual machine are fewer than reported” on page 39v “VMDKs should be removed from original datastore” on page 40v “List of available virtual entities does not change if two datacenters have

the same name” on page 40v “Restoring a virtual machine to a current datastore fails” on page 40v “Restoring a virtual machine fails with the error “remove Hard disk 2”” on

page 40v “Restoring a VMDK to an alternate datastore causes loss of the original

VMDK on a virtual machine” on page 41v “Virtual machine cannot power on after NFS datastore is restored” on page

41v “Unable to mount an NFS volume if the export policy for the parent

volume and the mounted backup volume are not the same” on page 41v “Mounted backup not automatically removed when the restore session

expires” on page 41v “Problem occurs during unmount of backup copy of datastore” on page 42v “Single file restore on a Windows Server 2008 sometimes fails to bring disk

online” on page 42v “Single file restore does not automatically support VMDKs with multiple

partitions” on page 42

Known issues 37

v “Successful backup job might trigger a notification during backup” on page43

v “Virtual machine is unresponsive during a backup” on page 43v “Running a script during backup results in an error” on page 43v “Backup and Recovery cannot verify whether the scripts ran successfully”

on page 43v “vCenter Server displays an error message that virtual machine has two

VMDKs with same UUID” on page 43v “Mounting more than 15 disks on virtual machine fails” on page 44v “Automount is enabled by default” on page 44v “Problem occurs during unmount of backup copy of datastore” on page 44v “Unable to verify which disk is being restored” on page 44v “Virtual machine is unresponsive during a backup that uses a VMware

snapshot” on page 45v “CLI times out during a backup” on page 45v “Unable to download Restore Agent setup file using Internet Explorer on

Windows 2003” on page 45v “Unable to retrieve deleted backup in offline session of Restore Agent

(378453)” on page 45v “Problem occurs during restore of virtual machine or datastore from a

mounted backup on the same ESX server” on page 45v “Unable to delete restore session even if source virtual machine has been

deleted” on page 46v “Virtual machine cannot power on after it is restored and added to the

vCenter Server” on page 46v “Cannot power on a virtual machine that has a VMware consistency

snapshot” on page 46v “Disconnecting the FC initiator used to mount a LUN clone from the ESX

server results in the mounted backup being removed from the server” onpage 46

v “Attaching a .sfr file using Outlook Web Access (OWA) might fail” on page46

v “Deleting a nonexistent restore session results in an error” on page 47v “Drive letters that are used for network mapped drives might be incorrectly

displayed as available drive letters” on page 47v “Notification e-mail for restore session contains an IPv6 address” on page

47v “Restore session fails when using vFiler root volume” on page 47


Discovery of FC and iSCSI datastores might fail if the FC or iSCSI featureis not enabled on some hardware platforms

The Backup and Recovery capability might fail to discover FC or iSCSIdatastores on certain systems unless the licensed_feature.fcp.enable orlicensed_feature.iscsi.enable options are enabled on those systems. TheBackup and Recovery capability does not check the state of the option andoperates as if the FC or iSCSI license is enabled on the system.

Workaround: You can check if the FC or iSCSI license is enabled by using thelicense command and then enabling the correspondinglicensed_feature.fcp.enable or licensed_feature.iscsi.enable option onyour system.

Restoring a VMFS virtual machine causes loss of independent disksIf you restore a virtual machine that resides on a VMFS datastore and has anindependent disk attached (either persistent or nonpersistent), theindependent disks, when excluded from a backup, cannot be restored.

Workaround: Save these independent disks in their respective datastores afterthe restore operation finishes by detaching them and reattaching them asfollows:1. Click Edit VM Settings.2. Remove the independent disk.3. Restore the virtual machine from the backup.4. Click Edit VM Settings and reattach the independent disk.

VMDKs attached to a virtual machine are fewer than reportedDuplicate VMDKs might be reported when restoring a VMDK from a backup.This issue occurs when restoring a virtual machine that has VMwaresnapshots and two VMDKs, and the second VMDK is stored on a datastorethat is different than the first.

Workaround:Move the VMDK on the source datastore to the destinationdatastore and attach it to the copy of the virtual machine. This corrects thenumber of VMDKs reported.

To move a VMDK, complete the following steps:1. Mount the backup that contains the copy of the virtual machine.2. Register the copy.

To avoid a naming conflict with the original virtual machine, you shouldrename the copy.

3. After you register the virtual machine, delete or consolidate existingVMware Snapshots.

Known issues 39

4. Edit the virtual machine settings to detach, and, optionally, delete theoriginal VMDK.

5. Copy the VMDK from the mounted datastore to the destination datastore.6. Attach the newly copied VMDK to the virtual machine.7. Unregister the virtual machine that you registered in Step 2.8. Unmount the backup.

VMDKs should be removed from original datastoreAfter you restore a VMFS virtual machine, VMDKs should be removed fromthe original datastore and appear in the newly created folder on thedestination datastore. Typically, the folder name consists of the original namewith a sequence number added to it.

Workaround: If the VMDK remains in the original datastore after restoringthe virtual machine, you might want to delete it, to free space on thedatastore. Before you delete any files or folders on the original datastore,review the contents of the destination folder to ensure that the backuprestored properly.

List of available virtual entities does not change if two datacenters havethe same name

In the Backup wizard, the list of available virtual entities that you can selectfor a backup job does not change depending on the datacenter that you selectif two datacenters have the same name. Typically, the virtual entitiescorresponding to the selected datacenter should appear.

Workaround: When you create a backup job, you must select a datacenter inthe Inventory tree and then select the specific virtual machine or datastorecorresponding to that datacenter.

Restoring a virtual machine to a current datastore failsIf you use vMotion to migrate a virtual machine from one ESX server toanother after you back up the data, the restore operation fails.

Workaround:There is no workaround for this issue.

Restoring a virtual machine fails with the error “remove Hard disk 2”If you restore a virtual machine from a backup of a previous version of VSCfor VMware and it has an independent disk attached, the operation fails.

Workaround: Detach the independent disk before starting the restoreoperation:1. Click Edit VM Settings.2. Remove the independent disk.3. Restore the virtual machine from the backup.


4. Click Edit VM Settings and reattach the independent disk.

Restoring a VMDK to an alternate datastore causes loss of the originalVMDK on a virtual machine

If there is not enough space on the alternate datastore to hold the VMDK, therestore operation fails and you receive an error message stating that resourcesare unusable on the virtual machine.

Workaround: When restoring a VMDK, ensure that there is enough free spaceon the datastore for the VMDK.

Virtual machine cannot power on after NFS datastore is restoredYou cannot power on the virtual machine after restoring the datastore if theunderlying volume has run out of space during the restore operation.

Workaround:Provision more space on the volume and try to manually poweron the virtual machine.

Unable to mount an NFS volume if the export policy for the parent volumeand the mounted backup volume are not the same

When you are mounting a backup, if the parent NFS volume has acustomized export policy but the mounted backup volume has a defaultexport policy, an error occurs and the mount operation fails.

Workaround: If you are mounting a backup copy to a different ESX serverthan the server on which the parent NFS volume is mounted, you must makesure that the export policy for the parent volume is the same as the exportpolicy for the mounted backup volume. If you are using a customized exportpolicy for the parent volume, then you must mount the backup to the sameESX server on which the volume was initially mounted and not to a differentESX server.

Mounted backup not automatically removed when the restore sessionexpires

Although the restore session and mounted backup should be automaticallyremoved when the restore session expires, this did not occur.

Workaround: You must restart the SnapManager for Virtual Infrastructureserver service and delete the SFR session manually, as follows:1. From All Programs > Administrative Tools > Services, right-click

SnapManager VI service in the list of services and select Start.

2. From Home > Solutions and Applications, select IBM > Backup andRecovery > Single File Restore , select the expired restore session ID, andclick Delete.

Known issues 41

Problem occurs during unmount of backup copy of datastoreIf the ESX server shuts down unexpectedly while the Backup and Recoverycapability is attempting to delete a restore session and dismount a backupcopy of a datastore from that server, the Backup and Recovery capabilitydetects the failure and aborts the operation. It is assumed that the backupcopy is still mounted on the ESX server. If the datastore was unmounted bythe ESX server prior to the unexpected shutdown, this results in the Backupand Recovery capability maintaining information in the metadata that is nolonger valid.

Workaround: You can contact IBM Technical Support for assistance withresolving errors in the metadata file.

Single file restore on a Windows Server 2008 sometimes fails to bringdisk online

When you use the single file restore feature of SnapManager for VirtualInfrastructure to mount a VMDK to the same Windows Server 2008 R2 virtualmachine from which the backup was taken, it sometimes fails to bring thedisk online.

In the Windows Server 2008 R2 release, the SAN policy was changed toprevent disks from automatically coming online if the disk signature matchesan existing disk signature.

If you have a Limited Self Service Restore job, you must manually mark thedisk online using a tool such as diskpart or the Disk Management MMCplug-in. After you do that, drive letters are assigned to the partitions.

If you have a Self Service restore job, you are prompted to assign a driveletter. In this case, single file restore then automatically brings the disk onlineand assigns the drive letter to the first partition on the disk. If this is thesystem-reserved partition, it is the only partition that receives a drive letter. Ifyou have more partitions on the disk, you must manually assign the driveletter using a tool such as diskpart or the Disk Management MMC plug-in.

Single file restore does not automatically support VMDKs with multiplepartitions

The single file restore feature of SnapManager for Virtual Infrastructureautomatically assigns a drive letter to a single partition on a restored VMDK.If there are other partitions on the VMDK, you must manually assign thedrive number or mount point.

This issue occurs because Backup and Recovery Restore Agent only sees thefirst drive letter assigned to a VMDK. As a result, it only presents the optionto mount the drive letter of the first partition. You can manually assign driveletters using a tool such as diskpart or the Disk Management MMC plug-in.


After you manually add drive letters for the additional partitions, the Backupand Recovery Restore Agent recognizes them, so you do not need to performany manual steps to remove the drive letters.

Successful backup job might trigger a notification during backupWhen a scheduled backup job is configured to send email for warnings orerrors, a successful backup might trigger a warning, because the Backup andRecovery capability was unable to create any vCenter tasks during thebackup.

Even though the email you receive from the Backup and Recovery capabilityindicates a warning, the backup job completes successfully.

Workaround: Re-register VSC for VMware vSphere with the vCenter Server orrestart the vCenter Server.

Virtual machine is unresponsive during a backupWhen you back up a datastore of a powered-on virtual machine that isexperiencing heavy I/O activity, the vCenter Server might time out. Duringthis time, the host might be disconnected from the vCenter Server.

Workaround: Check the performance of your storage system and make sureyou have installed the latest VMware patches.

Running a script during backup results in an errorRunning a script using perl script.pl in the Backup and Recovery capabilityuser interface or CLI does not work for the Perl system command.

Workaround: You must remove the word Perl from the system command andspecify script.pl in the script.

Backup and Recovery cannot verify whether the scripts ran successfullyIf the path for Perl was not set up correctly, the Backup and Recoverycapability might not be able to verify whether the Perl script ran successfullyduring pre-backup or post-backup phase.

vCenter Server displays an error message that virtual machine has twoVMDKs with same UUID

When using the Restore Agent or the Backup and Recovery user interface toperform an offline disk attachment, you might receive an error message aboutduplicate Universally Unique Identifiers (UUIDs).

Workaround:

To allow duplicate UUIDs, complete the following steps:1. Use Restore Agent to mount a disk from a backup copy of the virtual

machine.

Known issues 43

2. After mounting the disk, launch the vSphere Client.3. Select a virtual machine in the vSphere Client window.4. Ensure that the VMware administrator does not need to reply to any

questions in the vSphere Client window.5. You might need to click the first two tabs in the vSphere Client for the

virtual machine.6. Attach a disk from a backup copy of the virtual machine, using either the

Backup and Recovery user interface or the VSC CLI.7. Repeat Steps 2 through 6.

Mounting more than 15 disks on virtual machine failsEach virtual machine can have up to four SCSI controllers, and each controllercan hold up to 15 disks. If the virtual machine already has 15 disks on eachcontroller, you cannot add more disks.

Workaround: Ensure that you have available SCSI IDs on the SCSI controllersthat are currently attached to the virtual machine. You can add an additionalcontroller if needed and the limitation has not been reached.

Automount is enabled by defaultThe automount feature is enabled by default on Windows (XP, Vista, andWindows 7) operating systems, and the feature cannot be disabled. Windowsautomatically assigns a drive letter and mounts the disks. In offline mode,disks are mounted to a drive letter when they are attached to the virtualmachine.

Problem occurs during unmount of backup copy of datastoreIf the ESX server shuts down unexpectedly while the Backup and Recoverycapability is attempting to delete a restore session and dismount a backupcopy of a datastore from that server, the Backup and Recovery capabilitydetects the failure and aborts the operation. It is assumed that the backupcopy is still mounted on the ESX server. If the datastore was unmounted bythe ESX server prior to the unexpected shutdown, this results in the Backupand Recovery capability maintaining information in the metadata that is nolonger valid.

Workaround: You can contact technical support for assistance with resolvingerrors in the metadata file.

Unable to verify which disk is being restoredDuring backup and restore of a virtual disk, the disk is identified by the nameused in vCenter Server (such as Hard Disk 1). There is no correlation inSnapManager for Virtual Infrastructure between this name and the drive letterused by the underlying virtual machine operating system.


Workaround: Before running a restore operation, mount the backup andmanually verify that the disk corresponds to the drive to be restored.

Virtual machine is unresponsive during a backup that uses a VMwaresnapshot

Running a backup job that uses a VMware snapshot might result in the loss ofremote desktop connectivity and the virtual machine being unresponsive untilthe backup is finished running.

Workaround: Run the backup job without using a VMware snapshot.

CLI times out during a backupDuring a backup, if the SnapManager for Virtual Infrastructure server doesnot respond in a timely manner, the CLI times out and the following messageappears:

Connection to SMVI server was refused. Ensure that the server is running.

Workaround: If the Backup and Recovery capability detects this error, makesure that the server is running and then perform the backup.

Unable to download Restore Agent setup file using Internet Explorer onWindows 2003

Using Internet Explorer on Windows 2003 to download the Restore Agentsetup file might result in a message saying that Internet Explorer cannotdownload the file.

Workaround: You must modify the security settings for the Internet Explorerbrowser. For details, see the documentation for your version of the browser.

Unable to retrieve deleted backup in offline session of Restore Agent(378453)

You cannot retrieve deleted data from a backup mounted in an offline sessionof Restore Agent. For a limited self-service restore session, any changes thatyou make to the disks in a backup remain until the restore session ends,because the volume clone is removed only after the session expires and thedisks are removed.

Workaround: You need to re-create or generate a new restore session andmount the backup again so that you can retrieve the deleted backup.

Problem occurs during restore of virtual machine or datastore from amounted backup on the same ESX server

When performing a restore of a virtual machine or datastore from a mountedbackup on the same ESX server, a problem might occur during the renamedatastore task.

Known issues 45

The problem is a result of the restore operation using the same name for thenew cloned datastore. You can ignore this error because the restore operationuses a unique ID instead of the display name for the datastore. During therestore operation, one or more datastores are tagged. These datastores areautomatically deleted when the restore operation is complete.

Unable to delete restore session even if source virtual machine has beendeleted

Using the force option fails to delete a restore session even if the sourcevirtual machine has been deleted. The restore session is automaticallyremoved when the session expires.

Virtual machine cannot power on after it is restored and added to thevCenter Server

When you restore a virtual machine from a backup and then add it to thevCenter Server, the virtual machine is not available in the vCenter Serverinventory.

For more information, see VMware knowledge base article 1012333 vCenterServer stops responding after adding an ESX host to Inventory

Cannot power on a virtual machine that has a VMware consistencysnapshot

When powering on a virtual machine after completing a successful backup, anerror occurs that causes the VMware snapshot removal process to abort.Guidelines for implementing virtual machines with VMware snapshots are notincluded in the Virtual Storage Console for VMware vSphere documentation.

For more information, see VMware knowledge base article 1007849Consolidating snapshots

Disconnecting the FC initiator used to mount a LUN clone from the ESXserver results in the mounted backup being removed from the server

The Backup and Recovery capability does not allow you to specify whichinitiators (iSCSI or FC) you want to have a LUN mapped to. If you back up adatastore of an iSCSI-based LUN and then mount it on the host, the Backupand Recovery capability might use FC instead of iSCSI initiators. If you thenremove the FC initiator from the storage system, the mounted backup isremoved from the server.

Attaching a .sfr file using Outlook Web Access (OWA) might failA restore session configuration might not be downloaded correctly if it isattached as a .sfr file using Outlook Web Access (OWA).

Workaround: Check the Microsoft support site for more information aboutOWA server configuration or access the e-mail message using a non-OWAmailbox.





Deleting a nonexistent restore session results in an errorWhen you attempt to delete a nonexistent restore session using the name of avalid virtual machine or a virtual machine for which this session does notexist, an error message appears in the CLI output.

Drive letters that are used for network mapped drives might be incorrectlydisplayed as available drive letters

Drive letters that are used for network mapped drives might be displayed asavailable drive letters in the Restore Agent of the Backup and Recoverycapability because of a Microsoft API bug.

Notification e-mail for restore session contains an IPv6 addressWhen you create a restore session in SnapManager for Virtual Infrastructure,the notification e-mail for the restore session contains an IPv6 address for thevirtual machine instead of an IPv4 address.

Workaround: You can prevent IPv6 addresses from appearing in thenotification e-mail. You only need to complete this procedure once and thesystem generates the correct IPv4 addresses.

To avoid IPv6 addresses appearing in the notification e-mail for a restoresession, complete the following steps:1. Shut down the SnapManager for Virtual Infrastructure server (via

Windows Services).2. Open the wrapper.conf file.

This file is stored in the following location:

Virtual Storage Console\smvi\server\etc\wrapper.conf

3. Locate the following section of the file:# Java Additional Parameterswrapper.java.additional.1=-XX:MaxPermSize=128mwrapper.java.additional.2=-Dcom.sun.management.jmxremotewrapper.java.additional.3=-Dcommon.dir=.wrapper.java.additional.4=-Dorg.apache.cxf.Logger=org.apache.cxf.common.logging.Log4jLogger

4. Add the following to this section of the file.

wrapper.java.additional.5=-Djava.net.preferIPv4Stack=true

5. Start the SnapManager for Virtual Infrastructure server (via WindowsServices) and verify the email notification for the restore session.

Restore session fails when using vFiler root volumeThe restore operation for a virtual machine using the vFiler root volumeresults in the following error:

Known issues 47

Storage system error: The vfiler root volume vol4041vf1 cannot have clones.

Workaround: Remove the FlexClone license or setstorage.provision.volumeCloneLun=false in smvi.override and restart theSnapManager for Virtual Infrastructure server.


Fixed issues

Virtual Storage Console 4.1 for VMware vSphere includes product fixes thatyou should know about; it also includes workarounds if an issue cannot beresolved.

The following sections contain information on these issues. The issues areorganized according to the Virtual Storage Console for VMware vSpherecapability to which they apply.v “Fixed issues: Multiple VSC for VMware vSphere capabilities”v “Fixed issues: Monitoring and Host Configuration” on page 50v “Fixed issues: Provisioning and Cloning” on page 50v “Fixed issues: Optimization and Migration” on page 51v “Fixed issues: Backup and Recovery” on page 52

Fixed issues: Multiple VSC for VMware vSphere capabilities

Some known issues from previous releases that affect multiple Virtual StorageConsole for VMware vSphere capabilities have been fixed in Virtual StorageConsole 4.1 for VMware vSphere.

Internet Explorer 9 warning message no longer applies inVSC 4.1 for VMware vSphere

The 4.1 release of VSC for VMware vSphere fixes an issue where a warningmessage was displayed if you used Internet Explorer 9 as your web browser.

VSC for VMware vSphere now lets you type in a host nameduring installation

You can now enter any valid host name or domain name when you installVSC for VMware vSphere. Previously you had to select a Virtual StorageConsole for VMware vSphere server from a dropdown box of IP addresseswhen you installed VSC for VMware vSphere.

Starting with version 4.0 of VSC for VMware vSphere, the drop-down box letsyou either select one of the IP addresses it displays or enter a new host name.If VSC for VMware vSphere is not able to resolve the host name you enter, itdisplays a warning message.


Fixed issues: Monitoring and Host Configuration

Some known issues are fixed in the Monitoring and Host Configurationcapability of Virtual Storage Console 4.1 for VMware vSphere.

Space used for the snapshot reserve now calculatedcorrectly

Previous releases of VSC for VMware vSphere incorrectly calculated the valueof the reserve-used-actual field when determining amount of space used for thesnapshot reserve.

This issue is fixed in VSC 4.1 for VMware.

Problem with ALUA Capable field displaying incorrect statusnow fixed

The ALUA Capable field in the SAN Storage Controllers panel of theMonitoring and Host Configuration tab now correctly displays the ALUAstatus.

In previous versions of VSC for VMware vSphere, this field incorrectlyreported the ALUA status as Enabled when it was disabled and Disabledwhen it was enabled.

Fixed issues: Provisioning and Cloning

Some known issues are fixed in the Provisioning and Cloning capability ofVirtual Storage Console 4.1 for VMware vSphere.

Provisioning and Cloning resource selections now savedcorrectly

In previous VSC for VMware vSphere releases, Provisioning and Cloning letyou select certain volumes, interfaces, and aggregates for use in its operation.However, Provisioning and Cloning did not display this information correctlybecause it did not save the resource selections properly.


Volumes with multiple datastore LUNs no longer incorrectlydestroyed

In previous VSC for VMware vSphere releases, if you manually enabled theDelete volume if last LUN option, Provisioning and Cloning destroyed thecontainer volume even if there were still LUNs on it.



Issue with remote datastore replication on clustered ESXhost resolved

In previous versions of VSC for VMware vSphere, if you selected a clusteredESX host that was disconnected as the destination in the Add RemoteDatastore Replication wizard, the task would fail when you attempted tomount the datastore.


Datastore Remote Replication fails if source and destinationaggregates are not the same bit type

Datastore Remote Replication fails if you establish a relationship with a sourcedatastore that resides in a 32-bit aggregate and a destination that resides in a64-bit aggregate.

Replication also fails with a source datastore in a 64-bit aggregate and adestination in a 32-bit aggregate. The failure occurs because SnapMirrorcannot establish a mirroring relationship between aggregates of different bittypes.

Workaround: Select source and destination aggregates that are both 32-bit orboth 64-bit.

This issue is fixed.

Fixed issues: Optimization and Migration

Some known issues that affected Optimization and Migration have been fixedin this release of VSC for VMware vSphere.

Issue with scan operations and SSL connections nowresolved

The Optimization and Migration scan operations sometimes halted withoutupdating the "last scanned" field. This issue occurred when all the VSC forVMware vSphere connections to the storage system were configured over aSecure Sockets Layer (SSL) and the httpd.admin.enable options were set todisable any non-SSL paths.


Fixed issues 51

Fixed issues: Backup and Recovery

Some known issues are fixed in the Backup and Recovery capability of VirtualStorage Console 4.0 for VMware vSphere.

Mounting a backup fails if the number of NFS datastores onthe ESX server is reached

When the ESX server reaches the maximum number of NFS datastores (eight,by default), an error occurs when mounting a backup.

On ESX server 4.0 and vCenter Server 4.0, the following error appears:Error mounting10.61.69.110:/vol/smsql1_mount_vmdk_d57e99b7109d4826b5be474dbd6927d3 asdatastore 4253abc4-9b2b-4b14-8d96-c6d4f3076152 to 10.61.71.221: Errorduring theconfiguration of the host: NFS Error: Unable to Mount filesystem: NFShas reachedthe maximum number of supported volumes

On ESX server 4.1 and vCenter Server 4.1, the following error appears:Error mounting10.61.69.110:/vol/smsql1_mount_vmdk_367f895d63f243fc941084bfcb0b0a03 asdatastore1f3fdb56-af0b-4cec-bd84-76f173d9261f to 10.61.71.221: UnmarshallingError: prefix xsdis not bound to a namespace

Workaround: You must either increase the maximum number of volumes onthe ESX server or temporarily remove any datastores that are not required.


Where to find additional information

The following table describes documents with the most current informationabout host requirements, supported configurations, and procedures forinstalling and managing Virtual Storage Console 4.1 for VMware vSphere.

To learn about... Go to this information source...

New and changed features, limitations, knownissues, fixed issues, and documentation corrections

Virtual Storage Console for VMware vSphere ReleaseNotes

How to download and install VSC for VMwarevSphere

Virtual Storage Console for VMware vSphereInstallation and Administration Guide

How to discover and add storage controllers inVSC for VMware vSphere


How to collect VSC for VMware vSphere log files Virtual Storage Console for VMware vSphereInstallation and Administration Guide

How to provision or clone a virtual machine Virtual Storage Console for VMware vSphereInstallation and Administration Guide

How to perform online alignment and migrationof virtual machines


How to add storage systems using the Backup andRecovery capability


How to back up a virtual machine or datastoreusing the Backup and Recovery capability


How to find troubleshooting information Virtual Storage Console for VMware vSphereInstallation and Administration Guide

How to find preference files, logs, and export files Virtual Storage Console for VMware vSphereInstallation and Administration Guide

How to find programmable APIs Virtual Storage Console for VMware vSphereInstallation and Administration Guide

The latest supported configurations www.ibm.com/storage/support/nseries/

Supported Fibre Channel SAN topologies The FC and iSCSI Configuration Guide

VSC for VMware vSphere GUI VSC for VMware vSphere online Help

Backup and Recovery GUI Backup and Recovery online Help


http://www.ibm.com/storage/support/nseries/

Configuring your host for the Host Utilities The HP-UX Host Utilities Installation and SetupGuide

The Linux Host Utilities Installation and Setup Guide

The AIX Host Utilities Installation and Setup Guide

The Windows Host Utilities Installation and SetupGuide


Websites

IBM maintains pages on the World Wide Web where you can get the latesttechnical information and download device drivers and updates. Thefollowing web pages provide N series information:v A listing of currently available N series products and features can be found

at the following web page:www.ibm.com/storage/nas

v The IBM System Storage N series support website requires users to registerin order to obtain access to N series support content on the web. Tounderstand how the N series support web content is organized andnavigated, and to access the N series support website, refer to the followingpublicly accessible web page:www.ibm.com/storage/support/nseries/This web page also provides links to AutoSupport information as well asother important N series product resources.

v IBM System Storage N series products attach to a variety of servers andoperating systems. To determine the latest supported attachments, go to theIBM N series interoperability matrix at the following web page:www.ibm.com/systems/storage/network/interophome.html

v For the latest N series hardware product documentation, includingplanning, installation and setup, and hardware monitoring, service anddiagnostics, see the IBM N series Information Center at the following webpage:http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

v See the Independent software vendors (ISV) Solutions Resource Library andVMware content at the following web page:www-03.ibm.com/systems/storage/solutions/isv/isv_vmware.html


http://www.ibm.com/storage/nas

http://www.ibm.com/storage/support/nseries/

http://www.ibm.com/systems/storage/network/interophome.html

http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

http://www-03.ibm.com/systems/storage/solutions/isv/isv_vmware.html

Copyright and trademark information

This section includes copyright and trademark information, and importantnotices.

Copyright information

Copyright ©1994 - 2013 Network Appliance, Inc. All rights reserved. Printedin the U.S.A.

Portions copyright © 2013 IBM Corporation. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corp.

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

References in this documentation to IBM products, programs, or services donot imply that IBM intends to make these available in all countries in whichIBM operates. Any reference to an IBM product, program, or service is notintended to state or imply that only IBM’s product, program, or service maybe used. Any functionally equivalent product, program, or service that doesnot infringe any of IBM’s or NetApp’s intellectual property rights may beused instead of the IBM or NetApp product, program, or service. Evaluationand verification of operation in conjunction with other products, except thoseexpressly designated by IBM and NetApp, are the user’s responsibility.

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to thefollowing license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. INNO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,


INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at anytime, and without notice. NetApp assumes no responsibility or liability arisingfrom the use of products described herein, except as expressly agreed to inwriting by NetApp. The use or purchase of this product does not convey alicense under any patent rights, trademark rights, or any other intellectualproperty rights of NetApp.

The product described in this manual may be protected by one or more U.S.A.patents, foreign patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by thegovernment is subject to restrictions as set forth in subparagraph (c)(1)(ii) ofthe Rights in Technical Data and Computer Software clause at DFARS252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark information

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, othercountries, or both. A complete and current list of other IBM trademarks isavailable on the Web at http://www.ibm.com/legal/copytrade.shtml

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States andother countries.

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo,Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePointPredictor, Bycast, Campaign Express, ComplianceClock, Cryptainer,CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort,DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,


FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol,FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything,Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster,MultiStore, NearStore, NetCache, NOW (NetApp on the Web), Onaro,OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX,SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, ServiceBuilder, Shadow Tape, Simplicity, Simulate ONTAP, SnapCopy, SnapDirector,SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator, SnapMirror,SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator,SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, TechOnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager,VPolicy, WAFL, Web Filer, and XBB are trademarks or registered trademarksof NetApp, Inc. in the United States, other countries, or both.

All other brands or products are trademarks or registered trademarks of theirrespective holders and should be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

Copyright and trademark information 59

Notices

This information was developed for products and services offered in theU.S.A.

IBM may not offer the products, services, or features discussed in thisdocument in other countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state orimply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe onany IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not giveyou any license to these patents. You can send license inquiries, in writing to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, N.Y. 10504-1785U.S.A.

For additional information, visit the web at:http://www.ibm.com/ibm/licensing/contact/

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes willbe incorporated in new editions of the publication. IBM may make


improvements and/or changes in the product(s) and/or the program(s)described in this publication at any time without notice.

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseweb sites. The materials at those web sites are not part of the materials forthis IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environmentsmay vary significantly. Some measurements may have been made ondevelopment-level systems and there is no guarantee that these measurementswill be the same on generally available systems. Furthermore, somemeasurement may have been estimated through extrapolation. Actual resultsmay vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly availablesources. IBM has not tested those products and cannot confirm the accuracyof performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should beaddressed to the suppliers of those products.

If you are viewing this information in softcopy, the photographs and colorillustrations may not appear.


Notices 63

��

NA 210-05531_A0, Printed in USA

GC52-1351-09

ibm system storage n series virtual storage console … system storage n series virtual storage...

Documents