Votes - 0, Average rating: 0
(
)
)
|
Other manuals for this model:
manual abstract
assigned to it, the text on this tab is incorrect. The text should indicate that a file system quota should be applied
to the shared folder.
2. The Allocate space action will incorrectly display a size of 0 MB for the shared folder and continuing with the
Allocate space action will grow the volume by unexpected amounts.
3. If a file system previously existed (for example, when the shared folder was created with ASM) and is removed,
ASM will continue to display the original quota information.
Workaround: To resolve issues 1 and 2, applying a file system quota to the shared folder. To resolve issue 3, select
the Remove from view action for the shared folder in the ASM user interface.
ASM may fail to run the correct operations on storage recently modified with non-ASM tools.
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.
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.
Data Protector Express workarounds
This section describes workarounds related to Data Protector Express
Issue: ASM may not recognize Data Protector Express immediately after Data Protector Express installation and before
the first discovery is run.
Upon installing Data Protector Express and immediately after installing Data Protector Express, clicking on the Create
a virtual library ..." action in ASM displays the following warning: Virtual Library cannot be created
This warning will display after starting ASM any time after installing Data Protector Express, but before discovery runs
(which could be up to an hour), when starting the user interface and selecting Create a virtual library. This is because
ASM does not recognize Data Protector Express until Data Protector Express has been installed and the first discovery
has been run.
This is because ASM does not recognize Data Protector Express until it has been installed and the first discovery has
been run.
Workaround: After installing Data Protector Express, refresh ASM to initiate the discovery process and try creating
virtual library once the discovery is finished.
Issue: Data Protector Express 5.0 functionality is not available through ASM if Data Protector Express is installed in
Chinese, Japanese, or Korean
A problem with Data Protector Express installations in languages with multi-byte character sets disables the integration
of Data Protector Express and ASM. This only affects the use of Data Protector Express functionality through the ASM
user interface; there are no problems when using the Data Protector Express user interface directly. There is also no
problem with ASM integration if Data Protector Express is installed in a language other than Chinese, Japanese, or
Korean. The issue occurs with Data Protector Express 5.0 builds earlier than 60459. To determine the Data Protector
Express version and build, select Help > About in the Data Protector Express user interface. The problem occurs when
the ASM Create a Virtual Library wizard is used. It displays the error message Error executing GetVLDinfo.pl, HP Data
Protector Express Software is required for Data Protector Express scripts to run. If any of the other ASM wizards are
used, on the Data Protection page the option for Tape or Other Device Backup will be disabled, and the message No
devices found is displayed.
Workaround: This issue has been resolved in Data Protector Express 5.0 build 60459 or greater. You can download
the latest version of Data Protector Express from http://www.hp.com/go/dataprotectorexpress. When installing the
newer Data Protector Express build, select Upgrade the existing installation when prompted.
8
Release Notes
...Other models in this manual:
Media Storage - HP StorageWorks X1500 Network Storage System (151.4 kb)
Media Storage - HP StorageWorks X1600 Network Storage System (151.4 kb)
Media Storage - HP StorageWorks X1800 Network Storage System (151.4 kb)
Media Storage - HP X1000 Network Storage Systems (151.4 kb)