HP AK373A - StorageWorks All-in-One Storage System 1200r 5.4TB SAS Model NAS... How to use

HP StorageWorks Automated Storage
Manager
release notes
Part number: 5697-8166
Second edition: July 2009

Version
HP StorageWorks Automated Storage Manager (ASM) version 3.8.0
Description
These release notes cover HP StorageWorks Automated Storage Manager as of June 2009.
Update recommendation Recommended
Product models
The HP StorageWorks Automated Storage Manager 3.8.0 is supported on the following storage
system models:
•HP StorageWorks X1400 Network Storage System
•HP StorageWorks X1600 Network Storage System
•HP StorageWorks X1800 Network Storage System
•HP StorageWorks X1800sb Network Storage Blade
•HP ProLiant ML110 G5 Storage Server
•HP ProLiant DL160 G5 Storage Server
•HP ProLiant DL185 G5 Storage Server
•HP ProLiant DL380 G5 Storage Server
•HP StorageWorks 400 All-in-One Storage System
•HP StorageWorks 400t All-in-One Storage System
•HP StorageWorks 400r All-in-One Storage System
•HP StorageWorks 600 All-in-One Storage System
•HP StorageWorks 1200 All-in-One Storage System
•HP StorageWorks 1200r All-in-One Storage System
•HP StorageWorks All-in-One SB600c Storage Blade
Operating systems
Microsoft® Windows® Storage Server™ 2008 Standard x64 Edition
Microsoft® Windows® Storage Server™ 2003 Standard R2 SP2 x32/x64 Edition
Languages
When the language files are installed on the storage system, the following languages are available:
•French
•Italian
•German
•Japanese
HP StorageWorks Automated Storage Manager 3

•Simplified Chinese
•Spanish
•Russian
Enhancements
Automated Storage Manager version 3.8.0
Automated Storage Manager (HP ASM) is a storage hosting and management tool that simplifies
hosting application and shared folder storage, data protection, managing storage, and monitoring
storage. Designed for IT generalists, HP ASM software enables you to create, migrate, manage, and
protect shared storage without the need for storage expertise. It includes tools to quickly and easily
migrate and manage data using automated best practice settings.
Benefits of using ASM include the following:
•ASM can be installed on existing ProLiant Storage Server 64–bit platforms
•File share creation and scheduled snapshots
•Hosting block-based storage for Exchange, SQL, and other applications
•Support for backup of file shares or application stores to disk, tape, or other removable media
using application-aware snapshots (HP Data Protector Express required)
•Streamlined data replication for file shares or application storage (HP StorageWorks Storage
Mirroring required)
The following limitations apply to ASM:
•No SAN Gateway support
•No clustering support
•No MSA 2000 or EVA support
•No support for creating or growing LUNs larger than 2 terabytes
•No dynamic disk support
•No IPV6 support
HP StorageWorks Storage Mirroring Software update
An evaluation version of the HP StorageWorks Storage Mirroring Software version 5.1 is available
for use with ASM version 3.8.0. You can install the 5.1 version from the HP Web site (http://
www.hp.com/) for your evaluation. If you have already licensed a previous version, the license
includes 1 year of free upgrades. When prompted, enter the key evaluation to begin the evaluation
period if you have not already purchased a license.
IMPORTANT:
ASM version 3.8.0 supports HP StorageWorks Storage Mirroring Software (SWSM) version 5.1 only.
Older versions of SWSM are no longer supported in ASM version 3.8.0.
4

Issues and workarounds
Automated Storage Manager (ASM)
This section describes issues related to HP Automated Storage Manager (HP ASM) version 3.8.0.
Issue: When updating older versions of ASM to ASM version 3.8.0, the Final Upgrade Steps page of the
installer incorrectly identifies the folder for the ASM Agent Installer as C:\hpnas\Components\Automated
Storage Manager\.
Workaround: The correct folder location of the ASM Agent Installer is C:\hpnas\Components\All-in-One
Storage Manager.
Issue: Snapshots fail with the error VSS_E_PROVIDER_VETO after updating older versions of ASM to ASM
version 3.8.0.
When updating older versions of ASM to version 3.8.0, the previous version of Microsoft iSCSI Target Client
is not uninstalled. This results in users not being prompted for VSS Hardware Provider credentials. As a result,
all snapshots fail with the VSS_E_PROVIDER_VETO error.
Workaround: Uninstall the previous version of Microsoft iSCSI Target Client before updating to ASM version
3.8.0. If you have already updated to ASM version 3.8.0, modify the logon credentials of the VSS Hardware
Provider service manually and then restart the service.
Issue: After updating storage servers running ASM version 3.5 to ASM version 3.8.0, SQL Server applications
are discovered as user-defined applications by ASM.
In addition to these applications being discovered as user-defined applications, subsequent ASM discovery
operations do not automatically promote these applications to SQL Server applications and any associated
SQL Server databases are not discovered by ASM. This is an intermittent issue.
Workaround: Restart the application server.
Issue: Exchange, SQL Server, and user-defined application data restored to an alternate location cannot be
deleted
The data cannot be deleted due to insufficient privileges. All iSCSI LUNs created by Automated Storage
Manager on a Windows server as part of hosting Exchange, SQL Server, and user-defined application storage,
contain System Volume Information, a hidden system folder. This folder is by default only accessible to the
SYSTEM user, and not to the Administrators group. There may also be other similar folders, such as SIS Common
Store, if Single Instance Storage is enabled on the volume.
Workaround: Change the privileges as follows:
1. Navigate to the System Volume Information folder in the restored data.
2. Right-click the folder and select Properties.
3. On the Security tab, add the Administrators group and select Full Control for its permissions.
The folder can now be deleted by an administrator. Repeat this process for any other folders that are inaccessible
by administrators.
HP StorageWorks Automated Storage Manager 5

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: Migrating storage using ASM may cause an error during volume creation
When migrating storage using the ASM, the Create Volume task may fail.
Workaround: This is due to an error in Microsoft Virtual Disk Service (VDS). Restart the specific wizard to
launch the task again.
In some cases, the Create Volume task will fail after storage has already been provisioned and an iSCSI LUN
has been created on the storage system. If this occurs, running the wizard again will result in another iSCSI
LUN (vhd file) being created on the storage system and the initial iSCSI LUN will take up extra space without
being utilized. For information about how to properly delete the unused iSCSI LUN, see the white paper
Reclaiming storage on the HP StorageWorks Automated Storage System at http://h71028.www7.hp.com/
ERC/downloads/4AA1-1026ENW.pdf.
Issue: Data protection settings are not modified for storage areas that are promoted by ASM
If data protection settings (replication, 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, running backups, or running replication.
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 (replication, snapshots, and backup) and reset them using ASM.
Issue: Replicating a storage component whose application data exists in a single iSCSI LUN results in extra
space utilization on the replication target
When a single iSCSI LUN is presented to a SQL or Exchange server, the database file and database transaction
log file are both created on the volume contained in the iSCSI LUN. If the iSCSI LUN was created on the
storage system as a user-defined application, ASM will discover that the database files are now in the volume
and it will promote the user-defined application to a SQL Server or Exchange application instance. If the SQL
Server or Exchange application instance is replicated to another system, the iSCSI LUN is replicated to the
target system twice: once for the database file and again for the log file.
In general, the amount of space used on the replication target is equal to the size of each iSCSI LUN that
contains multiple components multiplied by the number of components in that iSCSI LUN. If multiple components
exist in multiple iSCSCI LUNs, the sum of the product of the sizes is the total consumed space. Snapshot space
usage is similar.
For example, a single iSCSI LUN of 200MB that contains a volume that has both the database file and the
log file would consume 400 MB of space on the replication target (200MB x 2 = 400MB). Likewise, an
Exchange server with one storage group of three mail stores on one iSCSI LUN of 500MB and the log and
public store on a separate iSCSI LUN of 250 MB would consume 2000MB of space on the replication target
(500MB x 3 + 250MB x 2).
Workaround: As a best practice, when configuring storage for SQL Server and Exchange databases, create
the database files on one iSCSI LUN and create the associated log and system files on a separate iSCSI LUN.
This way, when storage areas are replicated, there will be one component per iSCSI LUN and space will be
utilized on the replication target more efficiently.
6

Issue: ASM cannot connect to the SQL server on an application server
Certain requirements must be met before ASM can connect to a SQL application.
Workaround:
•Ensure that a supported version of SQL Server is installed. ASM does not support any developer editions
of SQL Server. ASM supports SQL Server 2000 (SP4 or greater), SQL Server 2005 (SP2 or greater), and
SQL Server 2008.
•Ensure that SQL-DMO is installed. SQL-DMO is installed by default with most editions of SQL Server 2000
and SQL Server 2005. SQL-DMO is not installed by default on SQL Server 2008. See issue 1000856963
in this document for more details.
•Ensure that you have appropriate credentials configured on your SQL Server. The SQL user must have the
ability to log in locally to the application server and have 'dbadmin' privileges on the SQL Server you are
connecting to. Log into your SQL Server with this user account if you continue to have issues. See the ASM
Help topic Configure Application Credentials for more information on connecting to a SQL Server through
ASM.
Issue: Application credential error appears while running the Host a SQL Server Database Wizard
When attempting to host a SQL Server 2008 database using the Host a SQL Server Database Wizard, an
application credential error message may appear. This error might appear because SQL Distributed
Management Objects (SQL-DMO) is not installed with SQL Server 2008 by default.
Workaround: Before attempting the following workaround, check to make sure that you have properly entered
your SQL Server 2008 credentials. If your credentials are correct and the error message still appears, install
SQL-DMO.
To install SQL-DMO, run the SQL Server 2005 Backwards Compatibility installer:
1. On the SQL Server 2008 Installation Media, navigate to the \x64\Setup\x64\ folder on 64–bit applic-
ation servers and \x86\Setup\x86\ on 32–bit application servers.
2. Double-click SQLServer2005_BC.msi.
3. Follow the on-screen instructions.
After installing SQL-DMO, run the Host a SQL Server Database Wizard again. The wizard will complete
without error.
Issue: ASM attempts to create non-existent storage during discovery
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.
HP StorageWorks Automated Storage Manager 7

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.
Issue: HP StorageWorks X1000 Network Storage Systems allow installation of ASM agent
Workaround: The ASM agent is intended to be installed and run on application servers. Before installing the
ASM agent on a server, ensure that the server is not an HP X1000 Network Storage System. If the ASM agent
is installed on an HP X1000 Network Storage System, uninstall it.
ASM indicates that NFS Server is unavailable or turned off for a shared folder
Workaround: This is an intermittent issue. To work around the issue, restart the storage system.
Issue: Changing system time setting during ASM discovery causes ASM to fail
If system time settings such as time zone are modified while the ASM discovery process is taking place, the
ASM fails and logging stops.
Workaround: Close the ASM user interface if open and restart the ASM service after adjusting the time.
Data Protector Express
This section describes issues related to HP StorageWorks Data Protector Express (DPX), a service
required to enable data protection features on ASM. The following issues apply only to storage systems
with DPX installed and enabled.
Issue: Changes made to a backup using Data Protector Express are not always reflected in ASM
If you use Data Protector Express to change the rotation type associated with a backup to Custom rotation,
the change is not reflected in ASM.
Workaround: Data Protector Express can be used to change the rotation type of a backup to Custom rotation,
however, this change will not be reflected in ASM. If you need to use a custom rotation, HP recommends that
you continue to use Data Protector Express to make any further changes to the backup.
8

Issue: Data Protector Express may fail to start with "Service not found" error
When attempting to start Data Protector Express, the following error may be displayed:
Code: 59 (0x3b)
Message: Service not found
Description: The desired service was not found. Either the service is no longer
active, or the machine providing the service is unavailable at this time.
Workaround: Check the dpconfig.ini file at C:\Program Files\HP\Data Protector Express\
config. In particular, the isDatabaseServer setting should be Yes. Other entries may vary depending
on your configuration.
The file should have a [configuration] section similar to the following:
[configuration]
lastUser=ASMbackup
nodeGuid={00001001-44BF7770-0010D9E7-0018CAB0}
nodeName=STORAGEWORKSAIO
databaseServerAddress=localhost
isDatabaseServer=Yes
databaseServerName=Data Protector Express Storage Domain
disableNetwork=Yes
remoteAdmin=No
Issue: Backup job fails for Exchange storage groups that were manually migrated to the storage system
It is possible to manually create a virtual hard disk on the storage system using the Microsoft Software iSCSI
Target snap-in. This disk may then be assigned to a target, allowing an iSCSI initiator on the Exchange server
to access the disk as a local volume.
If the logs and database(s) of an Exchange storage group are then moved to this iSCSI volume, ASM (ASM)
will discover the Exchange Storage Group, and present it as an application in the ASM user interface. This
will allow you to configure data protection for the application and schedule a DPX backup; however, when
the backup job runs, it fails.
The job status in DPX will be operator canceled, and the following error is written to the Windows application
event log on the storage system:
Stopping backup job '<job name>' due to checksum verification failure.
The error occurs because ASM performs checksum verifications using the eseutil.exe utility on Exchange
databases and logs before backing up the files. Databases and logs are expected to be found in separate
volumes as a best practice method employed by ASM when a wizard is used to migrate an Exchange storage
group to the storage system. When the logs are not found, the checksum fails and ASM cancels the backup
job and notifies Exchange that the backup did not complete successfully.
Workaround: Manually create another iSCSI virtual hard disk and make it accessible to the Exchange server:
1. Use the Exchange Management Console to move the storage group path for the log files and system files
to the new volume, leaving the database at the original iSCSI volume.
2. After modifying the paths in Exchange, click Refresh in the ASM user interface to force a discovery.
3. The application area for log files will now show an alert. Right click on this area and select Remove from
view.
4. Another discovery will be performed and ASM will restore the log file area into the user interface with
corrected properties, such as the new location on the Exchange server.
For backup jobs from ASM to work properly, each database and the log files/system files must be on a
separate iSCSI volume. For example, if a storage group contains one mail store and one public folder store,
three iSCSI volumes should be used, one for each database, and one for the log and system files.
HP StorageWorks Automated Storage Manager 9

Issue: Performing a “Remove from View” on a Virtual Library causes the library to appear as a User-Defined
application
If a virtual library is deleted from Data Protector Express, and then the Remove from View option is used on
the virtual library in ASM, the virtual library is removed from the Data Protection view, but appears in the User
Defined view.
Workaround:
1. Use Data Protector Express to stop and then delete the Virtual Library Device.
a. In Data Protector Express, select the Devices icon from the Favorites pane on the left.
b. In the right pane, navigate until the desired device is displayed.
c. Right-click the Virtual Library device and select Stop.
d. After the device has been stopped, right-click again and select Delete.
2. Delete the storage folder used by Data Protector Express to store the backup data. The storage folder
path can be found by right-clicking on the virtual library in ASM, selecting Properties, and then selecting
the Storage tab.
3. Right-click on the virtual library in ASM and select Remove from view.
Issue: Removing a Virtual Tape Library (VTL) in Data Protector Express causes ASM to fail
If an application is being backed up to a Virtual Tape Library and the VTL is removed using Data Protector
Express, ASM will fail.
Workaround: In ASM. remove any backup jobs that use the VTL as a backup target before removing the VTL
device in Data Protector Express. After removing the VTL in Data Protector Express, remove the VTL in ASM
by right clicking on the VTL and selecting Remove From View.
Effective date
July 2009
10