HP StorageWorks XP Performance Advisor Software release notes Database Migration Utility 1.1.
Legal and notice information © Copyright 1999, 2009 Hewlett-Packard Development Company, L.P.
Description HP StorageWorks XP Performance Advisor Software (Performance Advisor, PA) collects, monitors, and displays the performance of your HP StorageWorks XP disk arrays. Performance Advisor collects in-depth performance data so you can study performance at the level of components such as LDEV, CHIP or CHA, ACP or DKA, and DKC. Performance Advisor also includes XPWatch, a real-time troubleshooting tool to help you identify the root cause of performance issues.
NOTE: If the upgrade is from Performance Advisor v2.2B or later versions (prior to v3.2), you must first upgrade PA to v3.2. Then, using the new database migration utility, you can upgrade PA and also migrate the data to v3.5 through v3.5.2 (as per your requirement). For more information on upgrading to PA v3.2, see the HP StorageWorks XP Performance Advisor Software Installation guide provided in the PA v3.2 CD media.
NOTE: To run an application or a batch file on Windows Vista system, you need to right click on that particular application or batch file, and select Run as Administrator from the pop-up menu. Installing Performance Advisor v3.5 through v3.5.2 To install Performance Advisor, complete the following steps: 1. Log in to the Performance Advisor management station with administrative permissions. 2. Insert Performance Advisor installation CD 1 in the CD drive. 3. 4. 5. 6. 7. 8.
batch script ensures that the remaining performance data points are converted to the new database format. 5. 6. Stop Solid.exe. Right click the Solid Embedded Engine application icon on the Task bar and click Close in the pop-up menu. A dialog box appears confirming that the services have stopped. Start Performance Advisor services (go to Start -> Programs -> HP Storage Works -> XP Performance Advisor -> Start services).
Known issues and limitations Following are the known issues and limitations: Known issues None. Limitations If the database migration happens from v3.2 to v3.5 through v3.5.2, after the migration is complete, you need to perform a fresh configuration data collection for all the XP arrays. It is for accessing the previous performance data.