Quick Overview ** Allocate 4 hours, but this *should* only take about a 1-2 hours **
Shutdown Diagnostics Server
Copy the [Drive]:\path\Diagnostics\Server directory as a backup
Un-install the current Diagnostics server, and say NO TO ALL when asked to remove configs. This will leave the etc and storage directories behind (a second copy, in addition to your backup).
Install the new Server.
This will automatically name the etc folder left from step 3, as etc.old - giving you a well to dip from for change migration (step 7 below).
Stop the new Server asap - it will start immediately as part of the installation.
** Remove the new storage directory and copy the entire directory over from your backup (may take a long time and be many, many gigabytes)
** ONLY necessary if you did not follow step 3's direction to leave the configs in place.
The installer should adopt the old storage directory and make this step unnecessary.
Check the size of storage with windows explorer properties - in both this folder and your backup of the diagnostics server. IF they are close/same, you are okay.
NOTE: storage contains ALL UI customizations for the server and users; custom fields, alerts, custom displays, permissions, etc
Go through the etc directory and merge all of the configurations - be thorough, check every file. These are the big ones:
Check the nanny config file: [PATH]\Server\nanny\windows\dat\nanny\server.nanny - this is where the server heap size is set.
Check the bin directory for the wget subdirectory - if that is there, migrate it over to the new bin directory.
Restart the Diagnostics Server.
General Note, immediately following the upgrade:
It will take some time for the Diag server to get the web interface up - perhaps as long as 5 minutes, it's going to be very busy setting things up, so be patient. *NOTE: Sometimes IE caches the page and will not refresh it correctly, and sometimes bouncing between ports 35000 and 2006 will net a result when a plain refresh will not. Your mileage may vary.
Configurations such as applications and probe groups may take a little time (sometimes a couple hours) to fill-out and display as expected in the UI.
Historic data is stored in near-line backups in the storage directory and are unpacked as-needed, and *should* display normally, immediately - if not just a little slow during the initial start-up of this freshly upgraded server, as it cooks all the changes.
Watch server.log, deletions.log, changes.log - these are were >90% of the action is when you re-start the server and it starts pouring over all the old data and integrating it into the new server configuration.
BAC integration SHOULD be automatic, and does not normally require intervention. If the customer is using BAC and Diagnostics is integrated with it, just check it through BAC and make sure the integration is still working. If not, consult the BAC admin guide on integrating Diagnostics.
7.5x probes and collectors WILL work with an 8.x commander.
7.5x mediators will NOT work with an 8.x commander.
You MUST upgrade all your mediators when you upgrade your commander.
Get hold of wdiff.exe from the HP Virtual User bin directory. Wdiff can show you differences at the directory as well as the file level. Use it to compare the configuration files. Yellow lines are differences. Press TAB to move to the next difference. Generally speaking, do not worry about additions to the new file, which do not exist in the old files.
Get baretail.exe from box.net. It will allow you to watch multiple diagnostics log files in real time, and filter for key problematic words like WARN, SEVERE and memory.
NOT RECOMMENDED UPGRADE PATH:
8.00 - generally accepted as being a really bad and unusable version
8.01 - unstable
8.02 - memory leaks
8.03 - not entirely healed
RECOMMENDED UPGRADE PATH:
8.04 - generally stable and installable
8.05 - stable. Build 220.127.116.11 has some scalability issues with large numbers of mediators, fixed in build 18.104.22.168.