HP StorageWorks Automated Storage Manager 4.3 Release Notes (5697-0826, May 2011)

• Backup job fails with error 4067: Storage pool is full or not enough disk space.
When using ASM to create backup jobs, there is a Schedule backups to a local virtual library
option. The dialog box proposes a virtual library size. The proposed size is based on the allocated
storage for the data to be backed up, and the media rotation type selected. You can select a
smaller size for the virtual library, but if the size is not sufficient, backup jobs may fail with error
4067. This can happen even when the capacity of the virtual library is much larger than the data
to be backed up. For example, you have a shared folder holding 100 MB of files and you specified
a virtual library capacity of 2 GB. The first time the backup job runs, it succeeds. But later backup
jobs fail with error 4067. This occurs because Data Protector Express reserves a minimum of 1
GB for each slot in the virtual library device. Each media rotation set will occupy one slot in the
device. For example, a media rotation type of Simple 4 has 4 sets: Monthly, Weekly, Daily 1,
and Daily 2. This means that the minimum capacity of the virtual library has to be 4 GB. In
addition, if you run the backup job manually, some versions of Data Protector Express use an
additional slot rather than overwriting a media rotation slot. So the minimum capacity of a virtual
library that uses a Simple 4 rotation type would be 5 GB.
Workaround: Ensure that the minimum required virtual library capacity is set. The minimum
required capacity in GB of a virtual library is Number of sets used in the rotation type + 1. In
ASM, the tooltip on each rotation type provides the number of sets.
• 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.
10 Workarounds