APTARE IT Analytics Release Notes
- Patch Releases for Version 10.4.00
- Patch Releases: APTARE IT Analytics
- 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)
10.4.00P6 Patch Release Notes
The 10.400P6 release includes all patch fixes up to and including 10.3.00P13. The following software changes are included in this release.
Resolves an issue where the free physical memory was not being collected for Linux Hosts.
Resolves an issue that was causing the Storage Pool probe on the IBM Spectrum Protect Data Collector policy to throw an error. Updates have been made to APT_TSM_STORAGE_POOL.device_class_id.
Resolves an issue where NetBackup hosts from a VIP backup were getting removed from host groups as they were not collected by the Backup Policy probe. They are now being collected.
Resolves an issue with NetApp E-series by increasing the size of the database table column aps_storage_array.array_type to 64 bytes.
Resolves an issue by improving the response time for Policy REST APIs.
Cohesity collection now handles Protection Policies of type kAWS without errors. Protection policy of type kRPO is no longer collected as it is no longer supported by Cohesity.
Resolves an issue where IBM Enterprise array logging was not going to array-specific logfiles.
Resolves an issue where File Analytics Collection/Aggregation operates when owner name is not available.
The requirement for a password has been removed from deleting hosts. A warning and confirmation dialog is still displayed to prevent accidental deletion.
Resolves an issue with the report Data Collection Status for VMware by increasing the length of column resource_name in the VMWare resource table.
With this fix, in VMware data collection, when datastores are found that are not used by any ESX server, the Collection Status by Policy will display an "INFO" message and list collection status as successful.
Retains the User Type if a user exists prior to SSO configuration. Users logging in for the first-time after an SSO configuration, will be assigned the User Type, End User.
Removes the requirement of phone numbers being mandatory entries during user creation. Also solves the issue of changes in their values.
Resolves an issue with the Chargeback Policy Capacity report not filtering on the scope of Storage Array Vendor.