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

All-in-One Storage Manager
Workaround
As a best practice, when configuring storage for SQL Server and Exchange
databases, create the database files on o ne iSCSI LUN and create the associated
log and system filesonaseparateiSCSILUN.Thisway,whenstorageareasare
replicated, there will be one component per iSCSI LUN and space will be utilized
on the replication target more efficiently .
Issue:
Data volumes are not remounted after Quick Restore
Description
Mounted data
volumes are not remounted after performing an AiO Quick Restore.
These data vo
lumes are not damaged or destroyed but they are not visible in the
ASM user interface after a Quick Restore operation.
Workaround
In order to restore the mount points to their original loc ations, you must record
them prior to running Quick Restore.
1. Using Windows Disk Manager, record the m ount points of the volumes within
the root directory of each volume.
2. After running Quick Restore, scan the system to find data volumes that are not
assigned drive letters.
3. Temporarily mount the volumes that are not assigned drive let ters.
4. Locate the recorded list of mount points and remount the temporarily mounted
volumes to the correct locations according to the record.
Issue:
All-in-One Storage Manager does not recognize a change of disk type between SAS and SATA
Description
On AiO systems that allow a mix of SAS and SATA drives on the same storage
controller, a user may replace an unallocated disk with a disk of a different bus
type. For example an unallocated SAS disk could be replaced with a SATA disk.
ASM will discover any size difference i n the disks, but it d o es not detect the
difference in bus type. This may result in incorrect best practice decisions made
by ASM on the Storage Allocation page of its wizards. For example, if a disk
replacement resulted in only 2 remaining SAS disks, the wizard may still propose a
RAID 5 logical drive. The attempt to create the logical drive would then fail.
Workaround
1. Sto
ptheHP All-in-One Storage Manager Server Windows service.
2. Delete or rename the file C:\Program Files\HP\HP All-in-One
Storage Manager\hpkas-sandbox.bin.
3. Restart the HP All-in-One Storage Manager Server Windows service.
AS
M will now have a correct accounting of the SAS and SATA drives present.
Data Protector Express
This section describes issues related to HP StorageWorks Data Protector Express running on All-in-One
Storage Systems.
NOTE:
Changes made using Data Protector Express are not always reflected in All-in-One Storage M anager.
Data Protector Express
I
ssue:
Changes made to a backup using Data Protector Express are not always reflected in All-in-One
Storage Manager
Description
If you use Data Protector Express to change the rotation type associated with a
backup to Custom rotation, the change is not reflected in All-in-One Storage
Manager.
8