HP XP7 Performance Advisor v6.1 Software Troubleshooting and FAQs Guide

1. Initiate a backup of the complete HP XP7 Performance Advisor database using the Backup
Utility.
2. Remove the current version of HP XP7 Performance Advisor.
3. Install the current version of HP XP7 Performance Advisor again.
4. Select a different drive location for the HP XP7 Performance Advisor database.
5. Restore all the data using the Backup Utility.
Can I copy the HP XP7 Performance Advisor database before removing the application, so that the
same database can be restored after the installation is complete? In addition, how can I ensure
that HP XP7 Performance Advisor restores data from the folder that I specify?
From v3.5 onwards, copying database and pasting it onto a management station is not valid and
does not result in restoring the database. To backup and restore the database, you can do the
following:
1. Archive performance data for the XP and XP7 disk arrays using the database archival
functionality and later import the data back onto the same management station or another
management station where HP XP7 Performance Advisor is newly installed.
2. Backup the data using the Backup Utility and later restore that data onto the same management
station or another management station where HP XP7 Performance Advisor is newly installed.
NOTE: Ensure that the HP XP7 Performance Advisor versions on both the source and target
management stations are the same.
For more information on archiving and importing data, or using the Backup utility, see the HP XP7
Performance Advisor Software User Guide.
After removing Performance Advisor v3.4.1 on the management station, I did not delete the HPSS
folder and started with the v4.5 installation. After the installation completed, I am not able to log
into Performance Advisor. Why?
As you did not delete the HPSS folder when you removed v3.4.1 and later installed v4.5, the
HPSS folder will contain both SOLID and Oracle files. Remove v4.5, delete the HPSS folder
manually, and reinstall v4.5 on the management station.
Configuration FAQs
Following are the configuration FAQs:
Table 5 Limiting the amount of disk array history records per transfer from the web server
...%HPSS_HOME%\pa\properties\
serverparameters.properties
File
This parameter is read the first time a request is sent to
scroll through a range of disk array data.
When Read
This limits the amount of records the web server can send
to the client and prevents a large amount of data from
Discussion
being dragged across the network at one time. To view a
large amount of records, manually adjust the begin and
end times on the web browser, and request the records
from the web server.
Use the following to keep an XML data request that covers
a large amount of time, data records from tying up a servlet
Entry
with a large transfer and causing out-of-memory errors.
The client can make requests for more data, because it has
a count of records that are available and can specify which
record to start with for the next transfer.
DiskArrayPerfHistoryMaxRecordTransfer=1000
Configuration FAQs 75