HP StorageWorks All-in-One Storage System Release Notes (434690-006, June 2008)

All-in-One Storage Manager
Workaround
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 AiO. If this o ccurs, running
the wizard again will result in another iSCSI LUN (vhd file) being created on the
AiO 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 AiO white
paper Reclaiming storage on the HP StorageWorks All-in-One Storage System at
h
ttp://h7 1028.www7.hp.com/ERC/downloads/4AA1-1026ENW.pdf.
Issue:
HP All-in-One Storage Manager Agent fails to install
Description
On Windows S
erver 2008 systems, the installation of the HP All-in-One Storage
Manager Agent may fail with an Install failed error message. Support
for the ASM
Agent on a Windows Server 2008 system requires Microsoft .NET
Framework 3.0. If Microsoft .NET Framework 3.0 is not installed, the ASM Agent
installat
ion w ill fail.
Workaround
To install Microsoft .NET Framework 3.0 on Windows Server 2008:
1. If the Initial Configuration Tasks window is not open on the Windows Server
2008 system, open it by entering the oobe command at the Run prompt.
2. Click Add a Role.
The Add Roles Wizard opens.
3. Click Next.
4. On the Server Roles page, check the Application Server box and then click
Next.
5. Complete the wizard.
Microsoft .NET Framework 3.0 is installed. The ASM Agent can now be installed.
Issue:
Data protection settings are not modified for storage areas that ae promoted by ASM
Description
If data protection settings (replication, snapshots, and b ackup) are applied to a
remote user-defined storage area, and then a SQL Server database or Exchange
database is manually migrated to th is 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
Whe
n SQL Server or Exchange databases that are part of user-defined storage
are
as 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:
Re
plicating a storage component whose application data exists in a single iSCSI LUN results in
ex
tra space utilization on the replication target
All-in-One Storage System
7