HP StorageWorks All-in-One Storage System release notes (5697-7584, September 2008)

All-in-One Storage M anager
Description
On Windows Server 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
installation will 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 ba ckup) are applied to a
remote user-defined storage area, a nd 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 discover y 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 s ingle iSCSI LUN results in
extra space utilization on the replication target
Description
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 t
he iSCSI LUN. If the iSCSI LUN was created on the AiO as a user-defined
app
lication, ASM will discover that the database files a re now in the volume and it
wi
ll promote the user-defined application to a SQL Server or Exchange application
instance. If the SQL Server or Exchange application instance is replicated to
an
other system, the iSCSI LUN i s replicated to the target system twice: once for the
database file a n d again for the log file.
I
n general, the amount of space used o n the replication target is equal to the size
of each iSCSI LUN that contains multi ple components multiplied by the number
of components in that iSCSI LUN. If multiple components exist in multiple iSCSCI
LU Ns, the sum of the product of the sizes is the total consumed space. Snapshot
space usage is similar.
For example, a sing le iSCSI LUN of 200MB that contains a volume that has
both the database file and the log filewouldconsume400MBofspaceonthe
replication target (200MB x 2 = 400MB). Likewise, a n 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 2000M B of
space on the replication target (500MB x 3 + 250MB x 2).
All-in-One Storage System
7