HP StorageWorks Automated Storage Manager 4.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Version: HP StorageWorks Automated Storage Manager (HP ASM) version 4.3 Description Update recommendation Recommended Supersedes HP StorageWorks Automated Storage Manager (HP ASM) version 4.
Languages The following languages are available: • English • French • Italian • German • Japanese • Simplified Chinese • Spanish • Russian Enhancements HP StorageWorks ASM 4.3 includes support for Exchange Server 2010. Prerequisites If you are running a version of HP StorageWorks ASM released prior to version 4.0, first upgrade to version 4.0 and then upgrade to version 4.3.
Workarounds The following workarounds apply to HP ASM version 4.3. • The Expose snapshot step of the Run virtual library backup job fails with the following error message: Could not find the volume exception. All Run virtual library backup jobs for the same application area skip the Expose snapshot step and instead run the Unexpose snapshot and Delete snapshot steps. This error occurs in both ASM 4.1 and ASM 4.2. Workaround: 1. 2. Upgrade to ASM 4.3. Restart the application server.
• Extending storage space to the maximum allowed size fails and displays an error message. After storage is created in ASM, a size range is displayed that indicates the minimum and maximum size that the storage space can be extended (for example, 15MB - 272GB). When using the Allocate Space function to extend storage to the displayed maximum space allowed, the operation fails and an error message is displayed.
• When a restore job restores a folder that was previously shared via CIFS, the folder may no longer be shared and therefore will not be discovered in ASM. Workaround: Manually assign the appropriate permissions to the folder in order to share it, which allows the folder to be discovered in the ASM client UI.
• A restore operation could cause data loss if the mount point of the volume on the application server is deleted. If you configure a restore operation on a SQL Server or Exchange application using Data Protection Manager and the mount path of the application volume is deleted from the server, the operation could potentially cause a data loss. You might also see the error Attempting to mount to an unavailable location in the Unmount for restore task when the restore job is run.
The following items are additions to the “Troubleshooting Automated Storage Manager” section in the user guide. • HP ASM attempts to grow a volume when no space is available. The software might produce the following error message during storage provisioning of application/share storage: Unable to grow volume Workaround: The System Recovery process preconfigures a DON'T ERASE volume that is used for the installation and configuration of system recovery.
• 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.
