HP AK373A - StorageWorks All-in-One Storage System 1200r 5.4TB SAS Model NAS... Anleitung zur Verwendung

HP StorageWorks Automated Storage

Manager

release notes

Part number: 5697-0194

First edition: January 2010

Legal and notice information

Version: HP StorageWorks Automated Storage Manager (ASM) version 3.9.0

Description

These release notes cover HP StorageWorks Automated Storage Manager as of January 2010.

Update recommendation Recommended

Supersedes HP StorageWorks Automated Storage Manager release notes, part number

5697–8166, First edition, June 2009

Product models

The HP StorageWorks Automated Storage Manager 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 (on X1000 Network Storage

Systems)

Languages

The following languages are available:

•French

•Italian

•German

•Japanese

HP StorageWorks Automated Storage Manager 3

•Simplified Chinese

•Spanish

•Russian

Enhancements

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.

NOTE:

HP Automated Storage Manager is preinstalled on all HP StorageWorks X1000 Network Storage

Systems. HP ASM is not supported on HP X3000 Network Storage Systems.

The following enhancements are included in ASM version 3.9.0:

•In order to update the ASM agent, run ASMUpdate_3.9.0.exe on application servers.

•StorageWorks Storage Manager and HP Data Protector Express updates are no longer installed

as of the ASM 3.9.0 update.

•.NET 3.0 is a prerequisite for the ASM 3.9.0 update and is not bundled with ASM 3.9.0 update.

HP StorageWorks Storage Mirroring Software update

An evaluation version of the HP StorageWorks Storage Mirroring Software version 5.1 is available

for all HP StorageWorks X1000 and X3000 Network Storage Systems. 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.

Server Manager includes a link to install HP StorageWorks Storage Mirroring Software (SWSM)

version 5.1.

Fixes

The following defects were fixed in ASM 3.9.0:

•Fixed a scenario where removing a Virtual Tape Library in Data Protector Express caused the ASM

MMC to fail

•Fixed an application credential error that was occurring after replication with StorageWorks

Storage Mirroring (SWSM)

•Fixed a virtual library creation error

•Fixed a replication credentials update error

•Fixed a SWSM replication license error after ASM Update

•Fixed a snapshot creation failure error

•Fixed an ASM discovery failure error on AiO400 systems

Issues and workarounds

Automated Storage Manager (ASM)

This section describes issues related to HP Automated Storage Manager (HP ASM) version 3.9.0.

Issue: ASM backup of iSCSI based application server data fails on X1000 Network Storage Systems running

Windows Storage Server 2008 SP2.

ASM provides integrated backup of iSCSI LUNs that are presented as volumes to application servers. The

ASM agent installed on the application server initiates a VSS snapshot of the iSCSI volumes. This results in an

application-consistent snapshot on the storage server that is temporarily mounted on the storage server, giving

backup software access to the files; however, the attempt to mount the snapshot on the storage server fails,

which causes the backup job to fail.

Workaround: This problem is currently under investigation. Until a solution is implemented, one of the following

workarounds is required to back up application data held in iSCSI volumes.

Option 1: Back up data from the application server. From the application server, the iSCSI storage appears

as normal Windows volumes mounted at drive letters or mount paths. Use normal procedures for backing up

these volumes. Depending on the backup software used, there may be a conflict with the VSS Hardware

Provider on the application server. If there are backup errors, try disabling the VSS Hardware Provider: click

Start >Administrative Tools > Services. Double-click Microsoft iSCSI Software Target VSS Hardware Provider.

Stop the service if it is running, and set the Startup Type to Disabled.

Option 2: Schedule or manually create snapshots of iSCSI LUNs (virtual disks) on the storage server using

Microsoft iSCSI Software Target. These snapshots can then be mounted locally on the storage server giving

backup software access to the files. Refer to Microsoft iSCSI Software Target help for more detail on automating

this process. Go to Start > Administrative Tools > Microsoft iSCSI Software Target. Select Help Topics from the

Help menu and navigate to the Managing Backup and Recovery for Virtual Disks topic.

NOTE:

Backups created in this manner are crash consistent, meaning that the application is not given the

opportunity to acquire its data for the backup. If the backup is used for recovery, extra steps such as

replaying logs may be required. For an application consistent backup, use option 1 above and use

VSS-aware backup software.

Issue: When updating older versions of ASM to ASM version 3.9.0, some initiated tasks are not always shown

in the ASM Task Viewer.

Workaround: Restart the storage system. After the restart, all tasks are visible in the ASM Task Viewer.

Issue: Adding a storage system from ASM fails with a Cannot contact server error.

When attempting to add a storage system to ASM using the Add HP Storage System function in the ASM

Actions pane, the action sometimes fails with the following error message: The server could not be contacted.

Please verify that the HP Automated Storage Manager server is running.

Workaround:

1. Ensure that the ASM server and client are both running the same version of ASM.

2. Configure the ASM server and client firewall for exceptions on ports 12550 and 12551.

HP StorageWorks Automated Storage Manager 5

Issue: When provisioning storage, ASM fails to grow the logical disk capacity to the requested capacity, even

though the ASM user interface indicates adequate capacity. This is an intermittent issue.

Workaround: Retry the operation after the discovery process is complete.

Issue: Replication operation in ASM may fail on non-English systems.

A non-ASCII path may be created by ASM on non-English systems; however, HP StorageWorks Storage

Mirroring does not properly handle non-ASCII paths. As the result, replication may fail during the Replicate

component subtask.

Workaround: Change the system account language to English:

1. Log on to the storage system with the local Administrator account.

2. Change the System and Administrator account to English:

a. In Control Panel, double-click Region and Language Options.

b. On the Formats tab, select English (United States) under Current format.

c. On the Location tab, select United States under Current location.

d. On the Keyboards and Languages tab, select English under Choose a display language.

e. On the Administrative tab, click Copy to reserved accounts.

f. Check System accounts (local system, local service, and network service), and then click OK.

g. On the Administrative tab, click OK.

h. Restart the storage system.

3. Log on to the storage system with the local Administrator account.

4. Change the Administrator account back to your preferred language:

a. In Control Panel, double-click Region and Language Options.

b. Select your preferred options on each tab, but do not copy the settings to System account.

c. Log off and then log back into the storage system.

Issue: When updating older versions of ASM to ASM version 3.9.0, some existing virtual libraries are moved

to Remote Virtual Libraries area of ASM.

Workaround: Not applicable. There is no impact to data or applications.

Issue: The ASM Grow/Extend Volume command fails intermittently.

The Grow/Extend Volume command sometimes returns a failure even though the operation completes successfully

and the volume capacity matches the requested size.

Workaround: Retry the operation after completing the Discovery process.

Issue: NFS share folder creation fails when the NFS share folder name contains spaces.

Spaces are not allowed in NFS share names. If a space is included in an NFS share folder name, it is

automatically replaced by Windows with the underscore symbol (_). If an NFS share folder exists with the

same name (including the underscore symbol), a Windows prompt appears requesting a new NFS share

folder name. ASM, however, cannot check for or replace spaces in NFS share folder names during task

execution because CIFS share names do allow spaces.

Workaround: Do not include spaces in NFS share names. This issue will be addressed in a future release.

Issue: In rare cases, snapshot time stamps generated by the Operating System may not be parsed correctly.

Workaround: When a snapshot time stamp cannot be parsed, the current time on the storage system is used

in place of the timestamp. If the application server on which the snapshot is taken is in a different time zone,

it is important to note that the time stamp displayed in the ASM snapshot management dialog box reflects the

time zone of the storage system.

Issue: When updating ASM version 3.7.0 to ASM version 3.9.0, the Disk and Volume Management MMC

snap-in is not visible on HP ProLiant Storage Servers running Windows Storage Server 2003 x64 Standard

Edition.

Workaround: All features formerly listed under Disk and Volume Management are now available in the Share

and Storage Management MMC snap-in.

Issue: After updating storage servers running AiO version 1.3.1 to ASM version 3.9.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.

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.

HP StorageWorks Automated Storage Manager 7

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 iSCSI 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.

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.

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.

StorageWorks Storage Mirroring (SWSM)

Issue: Errors are reported when attempting to use SWSM 5.2 with ASM.

The following errors are reported when attempting to configure replication credentials for SWSM: Could not

get replication license state. Check replication credentials and for valid license key. and object reference not

set to an instance of an object.

Workaround: These errors are reported because SWSM version 5.2 is not supported with ASM. Uninstall

SWSM 5.2 and install SWSM 5.1. SWSM 5.1 is available at http://www.hp.com/go/storageworks/

storagemirroring.

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.

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.

HP StorageWorks Automated Storage Manager 9

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.

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.

Effective date

January 2010

Andere Handbücher für AK373A - StorageWorks All-in-One Storage System 1200r 5.4TB SAS Model NAS...

Dieses Handbuch passt für folgende Modelle

Inhaltsverzeichnis

Andere HP Software Handbücher

HP Data Protector IDB Purge Bedienungsanleitung

HP Designjet T1300 Bedienungsanleitung

HP C7791C - DesignJet 130 Color Inkjet Printer Konfigurationshandbuch

HP ProCurve 3500yl Series Anleitung zur Verwendung

HP Integrity Superdome 2 Bedienungsanleitung

HP HP LaserJet 2605, 2605dn, 2605dtn Service-Handbuch

HP Quality Center Synchronizer 1.2 Bedienungsanleitung

HP D6030A - NetServer - E50 Bedienungsanleitung

HP dc5700 - Microtower PC Bedienungsanleitung

HP t5630 - Thin Client Montage- und Bedienungsanleitung

HP Xw25p - ProLiant - Blade Workstation Bedienungsanleitung

HP AB500A - Integrated Lights-Out Advanced Bedienungsanleitung

HP T5700 - compaq thin client Bedienungsanleitung

HP Pavilion w1000 - Desktop PC Betriebsanleitung

HP LASERJET ENTERPRISE 500 Service-Handbuch

HP StorageWorks 1606 - Extension SAN Switch Bedienungsanleitung

HP Integrity BL860c Programmierhandbuch

HP BladeSystem bc2000 - Blade PC Service-Handbuch

HP Integrity BL860c Bedienungsanleitung

HP NonStop RDF J-series RVUs Programmierhandbuch

HP HSG80 - StorageWorks RAID Array Controller Bedienungsanleitung

HP Pavilion t700 - Desktop PC Betriebsanleitung

HP AA-RTDRB-TE Bedienungsanleitung

HP Integrity BL860c Bedienungsanleitung

Beliebte Software Handbücher anderer Marken

COMPRO

COMPRO COMPROFM Bedienungsanleitung

Muratec

Muratec OFFICEBRIDGE ONLINE Bedienungsanleitung

Oracle

Oracle Contact Center Anywhere 8.1 Bedienungsanleitung

Adobe

Adobe 65007312 - Photoshop Lightroom Handbuch

Avaya

Avaya NULL One-X for RIM Blackberry Bedienungsanleitung

PS Audio

PS Audio PowerPlay Betriebsanleitung

Brady

Brady LOCKOUT PRO 3.0 Service-Handbuch

Avaya

Avaya Interaction Center Bedienungsanleitung

Texas Instruments

Texas Instruments TI-83 Plus Silver Edition Handbuch

Novell

Novell GROUPWISE 8 - INTERNET AGENT Bedienungsanleitung

Oracle

Oracle Application 9i Bedienungsanleitung

Acer

Acer RDM Bedienungsanleitung

Canon

Canon Vixia HF21 Bedienungsanleitung

Canon

Canon ZR950 Bedienungsanleitung

Samsung

Samsung Auto Backup Bedienungsanleitung

Polycom

Polycom Vortex EF2201 Montage- und Bedienungsanleitung

Brocade Communications Systems

Brocade Communications Systems Brocade 8/12c Bedienungsanleitung

Novell

Novell SP2 - S Bedienungsanleitung