HP StorageWorks Automated Storage Manager Release Notes (5697-0391, June 2010)

Issue: Backup and/or Restore operations in ASM may fail if there is more than one File Volume (partition)

configured on an iSCSI-Based LUN (disk)

Workaround: Do not perform backup or restore operations in ASM on storage where more than one File

Volume is hosted on a single iSCSI LUN. ASM never provisions more than one volume on iSCSI LUNs, and

this situation will not be encountered for storage provisioned by ASM.

Issue: Data protection settings are not modified for storage areas that are promoted by ASM

If data protection settings (snapshots and backup) are applied to a remote user-defined storage area, and

then a SQL Server database or Exchange database is manually migrated to this storage area, ASM automatically

promotes the application to a SQL or Exchange Storage area during the discovery process. ASM does not,

however, adjust the data protection settings that were originally applied to the area. This may lead to failures

when taking snapshots or running backups.

Workaround: When SQL Server or Exchange databases that are part of user-defined storage areas are

promoted to SQL or Exchange storage areas in ASM, disable and delete all data protection settings for those

areas (snapshots and backup) and reset them using ASM.

Issue: ASM may fail to run the correct operations on storage recently modified with non-ASM tools

If you use a non-ASM tool (such as the Array Configuration Utility, for example) to modify storage settings,

you must allow ASM time to recognize those new settings during the discovery process. If you attempt to

perform storage operations before the discovery process is complete, ASM will erroneously attempt to perform

storage operations such as growing non-existent logical disks.

Workaround: When modifying storage settings outside of ASM, allow enough time for the ASM discovery

process to recognize those new storage settings before performing any other ASM operations.

Issue: When attempting to provision storage on ASM, an error message appears

When attempting to provision storage, an error message indicating that “no storage could be found or created

to satisfy the request” may be issued. This error can appear when attempting to provision storage across

multiple disk types.

Workaround: Virtual arrays that span multiple disk types cannot be created. When provisioning storage, the

maximum amount of space you can allocate is limited by the largest amount of space available for a single

disk type. You cannot completely utilize the space on all of the disks if the disks are of different types.

Issue: When opening ASM on HP X1800 Network Storage Systems, the error message The snap-in is not

responding is displayed

Workaround: ASM may take up to three minutes to load on HP X1800 Network Storage Systems. This delay

can be ignored. ASM runs at normal speed when the application is fully loaded.

Data Protector Express

This section describes issues related to HP StorageWorks Data Protector Express (DPX), a service

required to enable data protection features on the HP ASM. Note that DPX is not installed on HP

StorageWorks X1000 and X3000 Network Storage Systems by default. The following issues apply

only to storage systems with DPX installed and enabled.