APTARE IT Analytics Release Notes
- Patch Releases for Version 10.4.00
- What's New: Version 10.4 Highlights
- Supported Systems
- Installation and Upgrades
- Enhancements and Resolved Issues by Category
- Known Issues, Optimizations, and End of Life (EOL)
Before You Upgrade
The Portal must be running a minimum of version 10.2.01 to upgrade to 10.4.00.
Ensure that the aptare.jar is upgraded successfully.
Verify the rpm fontconfig is installed. Fontconfig is a library designed to provide system-wide font configuration, customization and application access. If the rpm fontconfig is not installed, the installer will not be able to load User Interface Mode. This is a prerequisite for a Linux Portal upgrade and a new Data Collector installation. (SC-18363)
If upgrading in a Shared Services environment, review the section Upgrading a Shared Service Environment in your OS-specific Portal Upgrade and Installation documentation for pre-install steps. (SC-18767)
Release 10.2.01 introduced two new backup vendors, Veeam Backup & Replication and Oracle RMAN. For customers upgrading to 10.2.01, and have Backup Manager reports saved, you must explicitly select these new Job Types and save reports for them to be included in your report output. (SC-15697)
Release 10.2.01 introduced a new behavior in the upgrader. APTARE IT Analytics, does not ship any database views for the user aptare_ro. During an upgrade, if aptare_ro user is found to have created database views, the upgrade process will stop with a warning message: (28686)
"WARNING. Found conflicting database views. These conflicts will cause the upgrade to fail. A list of database views are in upgrade_pre.log. Contact Support. Upgrade terminated..."
Release 10.2.01P4 introduced support for Microsoft Hyper-V, which changes the folder structure in the Inventory for VM Guests and VM Servers. For customers who are upgrading and with Microsoft Hyper-V installed, unpin your reports from VM Guests and VM Servers. Before this release, these reports were specific to VMware and would not correctly reflect all VM objects in the Inventory after the upgrade. (SC-16870)
For performance reasons, only new and revised reports are loaded during an upgrade. (SC-17912)