2. A Save as action has been added to the options for user-created reports and dashboards. [18898, 18852]

3. For tabular reports, you now can select up to 16 fields to filter the rows in a report. Prior to this change, only 4 row filters were supported. [11091]

4. The Portal Explorer was updated to fix an issue where when deleting a copied report template with report instance, only the template was deleted, leaving an orphan instance behind. [18243]

5. The SQL Template Designer now has a new Custom Number Formatter. During the upgrade process, the Number Formatter will be replaced with this new formatter; the formatter pattern will remain the same. Also, the Date Formatter has been deprecated. Note that if you import a template that was created prior to 9.1, the formatting will need to be manually modified. [14843]

6. In certain cases, where a Portal originated with pre-8.x software versions, the upgrade failed because a legacy portalproperties.xml file was found in the portalconf directory. The upgrade process has been updated to ensure that the file is deleted prior to the upgrade. [18599]

7. Advanced report filtering for tabular reports now supports greater than, less than, greater than or equal to, and less than or equal to. The field type can be. Number, String, Date, Duration, and File Size. The match is case insensitive. [19422]

8. The Data Collector Logs report now correctly sorts by request date. [18839]

9. The Portal Installation Guide for Linux was updated to include a step to ensure that prior to installing the license key, the Portal services are started. [19008]

10. Prior to this release, certain drilldown tabular reports, such as the Array Utilization Summary, had issues with report filtering. Report filtering for tabular reports now works as expected. [18286]

11. To enable advanced drilldown configuration in the SQL Template Designer, the Report Statistics functionality (CTRL+ALT+T) was updated to support two types of system names that can be referenced in a drilldown URL: System Name for factory-shipped reports that cannot be customized and Dynamic Template Instance ID for report templates created with the Dynamic Template Designer. The Portal upgrade and also the template import processes convert the drilldown configurations in existing report templates that were created with the SQL Template Designer prior to APTARE StorageConsole 9.x. [17375, 19122]

12. The Dynamic Template Designer was updated to fix an issue with he Configure Charts option. The error occurred when the input unit is chosen, but the related fields were left blank. [18537]

13. During an upgrade of Capacity Manager, the install script would detect that Capacity Manager database tables were already installed and exit out of the installation. The script now recognizes the presence of these database tables and provides a message “Capacity database tables already exist. Proceeding with the remaining processing...".[17211]

14. Prior to this release, on the Host Group Administration window, dragging and dropping had stopped working on Internet Explorer 10. This has been resolved and works on all supported browsers. [18476]

16. During the Portal upgrade, the new aptare.jar files were not automatically upgraded. This issue is fixed with this aptare.jar release. [19092, 18975]

17. Certain reports that show % values were updated to display correct percentage values, rather than decimals in the percentage. This issue was found in reports such as the VM Performance Summary where performance statistics are listed as percentages. [19463, 19487]

18. The Linux Portal upgrader was updated to fix an upgrade configuration issue that occurred only under very unique circumstances when upgrading to 9.x. The upgrader now considers both the operating system and the type of installer, portal or database. [18726]

19. Two issues occurring during tabular report exports have been corrected. The unit in the column header did not honor the user profile (KB or KiB) settings. The values in the columns were revised to be numeric. This enables a .csv file to be used to populate an external system. [19219]

20. The Portal and Database Installation has additional file systems and revised minimum disk space recommendations. [18791]

2. Increased the line length limit in the Attribute Load Utility to 32767, which is the maximum allowed. [18293]

3. The upgrade process no longer overwrites the system parameters that define database purging intervals. An issue in the previous release caused customer-defined revisions to these intervals to be reset to the default settings. [18713]

4. Several default database purging intervals have been updated in the system parameters: KEEP_FILE_SYSTEM_LOG_MONTHS, KEEP_HOST_PROCESS_LOG_DAYS, KEEP_HDS_LOG_MONTHS, and KEEP_VMW_LOG_MONTHS. See the APTARE StorageConsole System Administrator’s Guide for details. [18985]

2. Occasionally on busy systems, the Data Receiver would time out when returning a system ID. Collection now ceases when this occurs. [18026]

3. Two new fields have been added to all Data Collector policies: Collector Domain and Policy Domain. The read-only Collector Domain identifies the domain of the collector to which the policy is being added. The Policy Domain must match the Collector Domain to ensure that collected hosts appear in the correct host group. [19194].

4. To improve virtual memory usage, a parameter was changed in the startup.sh script. [18998]

5. Improvements to watchdog logging make the log more readable for troubleshooting. [19173]

6. Prior to this release, if data collection was interrupted, some uncollected objects were marked for deletion and were therefore not visible in the Portal. Exception handling now handles this use case. [19175]

7. Updates to data collection ensure that port 6002 does not get used by any StorageConsole processes. This was particularly an issue for Windows Data Collectors. [18575]

8. Under certain circumstances on Windows servers, the upgrade process would hang due to full buffers. This issue has been corrected in this release. [18909]

2. Host Resources collection was updated accommodate new command and output formats in HP-UX 11.3.31. This fixes an issue where file systems made with agile disks did not get collected. [18260]

3. Linux multipathed disk file systems are now collected successfully. A change in the output format of several Linux commands caused a parsing error. [19048, 18999]

4. SUSE multipath for host data collection has been fixed in this release. [19049, 18882]

5. Host data collection no longer queries the Win32_Product WMI class, which frequently triggered Microsoft installer re-configuration events and filled log files. [19098, 19172]

6. Host data collection was updated to fix an issue where, when saving host virtual volume data, a “maximum cursors exceeded” exception occurred. [18663, 18622]

7. Host data collection was incorrectly reporting LUNs as allocated and unused. This was due to data collection command failures in “tcsh shell” and “sudo with tty” environments. [18885, 18843]

8. Host database processing was enhanced to accommodate environments using HP VCM technology, where the WWN may not be truly unique. [19171, 18776]

9. For collection of certain file systems, a permission denied error occurred when a new advanced parameter was specified and data collection used the disk free (df) command. The fix uses sudo for the command and requires the advanced parameter: FILESYSTEMS_STRICT_CHECKING set to 'Y'. When adding this advanced parameter, set the default value to 'N' and then change it to 'Y'. [19044, 18772]

10. The SQL Server host probe was updated to fix an issue where data was not collected from hosts. [19404]

1. The following database published view has been added for use in the SQL Template Designer. [18341, SC-425]

2. The following database published view has been updated for use in the SQL Template Designer. [18675]

3. For HP 3PAR data collection, the SSH connection to the remote hosts is now closed when the processing is complete. [18689]

4. For HP 3PAR data collection, LUN mapping was fixed to ensure that data for all LUNs is collected. This fix takes into account hosts with multiple paths to the same LUN. [18656]

5. HP 3PAR data collection of physical disks and cage drives now handles a temperature value of N/A and also drive numbers that start in position 0. [18578]

6. HP 3PAR data collection now correctly captures and saves raw capacity values as KiB instead of bytes. Prior to this fix, when collection was halted prematurely, capacity values were saved as bytes. [17660]

7. HP 3PAR data collection was updated to ensure that snap_space_allocation_warning values are captured as absolute capacity values rather than percentages. [19398]

8. HP 3PAR Common Provisioning Group (CPG) data collection to fix an issue with collection of the device type and logical disks. These fixes impacted the data shown in the HP 3PAR Common Provisioning Group (CPG) Summary report. [18738, 18795]

9. For HP 3PAR, the Array Capacity Utilization now correctly displays the percentage values for the Raw Usage and LD Usage tooltips. [15534]

10. For IBM SVC data collection, arrays virtualized by the SVC were not appearing in the Array Utilization Summary report. This issue has been fixed in this release. [18710]

11. For IBM SVC data collection, a database update was made to accommodate larger values for the host interface state. [18696]

12. For IBM SVC data collection, exceptions occurred while saving host interface information. The root cause of these errors was fixed in this release. [18895]

13. IBM SVC data collection was updated to fix an issue where array performance data was not collected [18749, 18863]

14. An update to the Host Utilization Detail report fixes an issue where, under certain circumstances, the report did not render correctly. [18707, SC-1482]

15. The Mission Control Performance Analysis report was updated to fix an issue where the report did not render when the selected scope was less than 24 hours. [19050, 19046]

16. The sort order for the Hitachi Disk Summary report now includes the drive role column. [18367]

17. The Hitachi Data System Data Collector is now named Hitachi Block Storage. [18461]

18. A NetApp collection message was changed from an error to a warning: “Exception while getting netAppLunPerfInstanceList.” This message occurs when the NetApp filer doesn’t have LUNs assigned. [19093]

19. The Array Capacity Forecast report was updated to fix an issue where the total capacity did not display correctly. [19130]

20. The Array Performance by RAID Group report was updated to fix an issue where the drilldown to the Array Performance by LUNs did not render the report. This error occurred when the RAID type value included a plus (+) sign, such as RAID-5(7+1). [19019]

21. The Port Throughput by Array report was revised to correct an issue with the Show Chart option. This issue was specific to the Internet Explorer browser, which did not recognize the selected checkbox. [18971]

22. For NetApp data, the Array Utilization Summary report was updated to fix an issue where the # RAID Groups hyperlink drilled down to the List Array Groups report instead of the correct report, the NetApp Aggregate Summary. [19282]

23. The following updates were made to the Array Capacity and Utilization report:

24. The Host Capacity Forecast By Host displayed incorrect values for average and maximum capacity for the hosts displayed in the report. The values are now correct. [19157]

25. The Hitachi Block Storage Data Collector Policy dialog contained an extra scheduling field. This has been removed. [18298]

26. Various total capacity and used capacity values were stored in bytes instead of kilobytes and were incorrectly converted (using powers of 10 instead of powers of 2) from GB, MB, and so on to bytes. This caused erroneous capacity reports for Avamar nodes and partition. Powers of 2 are now used to convert the values. [19027]

27. The checkinstall process now lists the IBM VIO product name as appropriate. [18911]

28. Reports that display LUN numbers, such as the LUN Utilization Summary, have been reformatted to remove commas from the LUN numbers. [18832]

29. For EMC VNX (Celerra) data collection was updated to fix the configurations for Active Directory authentication. [18648]

30. Prior to this release, during data collection for EMC VNX, StorageConsole was unable to display error logs in the application if collection failed. This has been resolved. [18447]

31. For EMC VNX (CLARiiON) data collection, warning messages have been added for number format exceptions. During checkinstall, messages for parsing errors in log files indicated issues for fields that are not persisted in the database. [18779]

32. A problem persisting EMC VNX (CLARiiON) data was resolved in this release. This issue occurred only in certain circumstances, where the device number in the array was reused. [18778, 18758]

33. EMC VNX (CLARiiON) data collection was modified to accommodate N/A as a valid value for consumed capacity. This is relevant for virtual provisioning environments. [18816, 18810]

34. Checkinstall for Dell Compellent data collection now logs connection failure exceptions with tips on how to proceed. [19400]

1. Data collection was updated to persist guest snapshot history and the following database published views have been added or updated for use in the Report Template Designer. [18527, 12625]

2. The VM Performance Over Time and the VM Details reports were updated to correct the values displayed for CPU% and Memory%. [19228]

3. Several reports had missing tooltip help: VM Files Summary, VM Summary, and Physical Disk Performance Summary. These reports have been fixed. [18565]

4. The Virtualization Manager documentation was updated to reflect the requirement for port 443 for HTTPS connectivity. Data collection uses HTTPS without certificates for secure connections. [16598]

5. The Virtualization Manager performance database tables were updated to increase the size of the columns, allowing for larger values: number_of_disks_read and number_of_disks_write. [18302]

6. Virtualization Manager data collection was updated to handle exception cases where datastores do not have any files. [18928]

7. The Virtualization Manager Data Collector Policy dialog window was modified to fix an issue where the checkbox selection for the active probe for performance was not persisted correctly in the database. This issue prevented performance data collection from being disabled. [18364]

8. The VM Summary report now displays the legend for the colored icons that represent the state of the VM. [12592, SC-189]

9. A Virtualization Manager database update fixes an issue where the scope selector encountered errors when modifying the scope. [19179,19170]

10. A change to Virtualization Manager data collection fixes an issue where collection would fail when an ESX server did not have a VM. [18466]

11. The VM Performance Over Time and VM Detail reports were updated to fix percentage values, which were incorrectly being divided by 100. [19036]

12. A Virtualization Manager cloud report, VM Guest True Size, was modified to accommodate a change that was made in Oracle version 11.2.0.4. [19474]

13. The apt_v_vmw_vmguest_disk_log view was updated to add the disk_path column. This missing column caused erroneous values to be displayed in reports. [19375]

14. The apt_v_vmw_perform_disk_log view was updated to support queue length with the following columns. [7715, SC-591]

1. For Symantec NetBackup data collection, the client’s software patch level is now collected. The apt_v_nbu_client_detail database published view was updated to include the patch_level column. [18334, SC-627]

2. NetBackup data collection was modified to make a separate processing thread for collecting client software versions. This enhancements provides scheduling flexibility, enabling collection to be scheduled less frequently during off hours. This new probe can be configured in the NetBackup Data Collector Policy. [SC-194, SC-598, 16822]

3. The Capture File Details option is no longer supported for NetBackup jobs. [18491]

4. The NetBackup Data Collector Policy window was modified to clarify the dependencies for collecting SLP Job Details. [18727]

5. Collection of NetBackup SLP Job Details was updated to fix an issue where images were skipped. This occurred if the SLP was set up at the schedule level rather than the policy level. [18641, 18615]

6. The NetBackup Data Collector Policy was updated to change the default start time for the Client Details probe. The new default schedule is set to Tuesday at 9:00 a.m. [18894]

7. For NetBackup and Avamar, a database fix corrects an issue where certain clients had nulls or incorrect data saved for the make, model, and OS version. This occurred in cases where the hosts/clients did not have aliases defined. [15374]

8. Prior to this release, NetBackup collection (Disk Pool and Storage Server) failed due to a PL/SQL numeric error. The size of the IP address database field was updated to accommodate larger values, because this field could contain a host name that has a length that is greater than an IP address. [18571, 18557]

9. If you have custom report templates for NetBackup restore jobs, this change may require updates to those templates. Certain information for NetBackup restore jobs is stored differently in the database. Prior to this release, apt_v_nbu_job.client_id contained the media server ID. Starting with version 9.1, the media server ID for restore jobs is saved in apt_v_nbu_job.restore_media_server_id. And, the apt_v_job.client_id will contain the target_client_id. [16782]

10. The NetBackup database processing was updated to omit schedules with a name of “Dup.” This schedule type is a temporary placeholder that is created during a duplication job and should not be included in the final save to the database. [19416]

11. Collection of NetBackup AIR was updated to store the correct job type for incremental jobs. [18550, 18458]

12. Several NetBackup database columns were increased in size to accommodate larger values. Prior to this fix, an exception log message indicated a numeric or value error when saving client information. [19388]

13. The apt_v_nbu_policy_client database published view was updated to add columns for the interface name and IP address. [18683]

14. When upgrading to version 9.x, the NetBackup backup job completed event poll has been removed from the poll log, as it is no longer a valid poll. [19169]

15. NetBackup collection was updated to include additional skipped file types, such as Skipping too long path name.” Prior to this release, the only skipped file messages that were parsed were “open file” and “failure reading file.” [18484]

16. The NetBackup job database table was updated to increase the size of the backup ID column, from 64 to 128, to accommodate larger backup IDs. [19062]

17. NetBackup data collection was updated to fix the following issue: The Schedule storage unit values were overwritten by the Backup Policy storage unit if the Schedule storage unit did not have a value. This did not reflect the correct Policy details. [18630]

18. In support of NetBackup SLP data collection, several new job types are now collected and persisted in the database: 22=backup From Snapshot, 23=Replication (snap), 24=Import (snap), 25=application state capture, 26=indexing, 27=index cleanup, 28=Snapshot, 29=SnapIndex, 30=ActivateInstantRecovery, 31=DeactivateInstantRecovery, 32=ReactivateInstantRecovery, 33=StopInstantRecovery, 34=InstantRecovery. [18570, 18548]

19. Collection of NetBackup SLP job details from Windows servers was updated to fix an issue where the required target directories for stdout and stderr were not created, if they did not already exist. Certain directories are required for collection via the WMI proxy. [18734]

20. Improvements were made to labels and green help text on the Symantec NetBackup Data Collector Policy dialog to provide additional clarity. [19128]

21. Prior to this release, collection of NetBackup 7.6 policies did not persist/update associated clients. This issue has been fixed in this release. [18708]

22. During the NetBackup database purge process, a constraint violation occurred for certain servers that had disk pools. The disk pool mount data is now purged when the associated server data is deleted. [18496, 18494]

23. The NetBackup tape drive log database table now has the time stamp included in the poll time column. This enables more data points to be reported in tape usage reports. Prior to this release, only the date was recorded. [19417]

24. EMC Avamar data collection was modified to correct an issue where the amount of data protected was incorrect. The collected values were in MB, but they needed to be converted to KiB before saving to the database. [19024]

25. The EMC Avamar database was updated to increase the length of the event_data column to 2048. If data exceeds this length, it will be truncated. [19410]

26. The Programmer’s Reference Guide was updated to include columns and descriptions that had been missing from the following Avamar published view: apt_v_avm_activities. [18897, 18988]

27. For CommVault Simpana collection, the skipped files collection now is turned off by default. [18406]

28. An update to CommVault Simpana data collection and database persistence fixes an issue where parallel processing threads inserted duplicate CommVault servers. [18642]

29. For CommVault Simpana collection, additional processing has been introduced to collect the CommServe database version. In certain environments, the database version may not be available in the expected location. [18918]

30. The CommVault Simpana database tables and data dictionary were updated to fix an issue that caused certain reports to fail. [19427]

31. The Job Status Summary report was modified to fix an issue that was specific to CommVault Simpana. When generating this report with a scope that included CommVault Simpana jobs, the drilldown to the Job Summary report did not render, leaving only a blank screen. This drilldown link has been fixed in this release. [18748, 19890, 18786]

32. A NetWorker database column for the client resource comment was increased to 512 characters to accommodate larger comments. [18850]

33. The NetWorker published database view, apt_v_leg_saveset_group, had a new is_active column so that groups that were deleted do not appear in reports. [18944]

34. EMC NetWorker data collection was updated to fix an issue where no drive performance data was captured if NetWorker 7.5 or 7.6 was on a Unix server. [18888]

35. The following database published view has been added for use in the SQL Template Designer. [18224]

36. Database logic for EMC NetWorker for the Tape Media Summary report now filters out the media type cleaning tapes, as they are not associated with backup jobs. [18068]

37. For EMC NetWorker, increased the size of the database field apt_leg_schedule.schedule_name from (32) to (128). [18649]

38. A database update for the TSM tape media table fixes an issue where certain date fields were empty after data collection. [18377]

39. TSM skipped files collection was updated to ensure that additional common skipped file messages are captured. [18485]

40. TSM tape collection was updated to fix an issue where some TSM tapes incorrectly have the last write date also set as the last read date. [18765]

41. The database logic for saving TSM library types was modified to recognize the VTL type. [18796]

42. TSM data collection now captures the TSM instance version number. [18817]

43. TSM database logic was modified to correctly capture the library manager type. Prior to this fix, the library type received from a client was updating the type field; the type now is only updated when the value comes from the library manager. [18610]

44. Prior to this release, when attempting to purge obsolete TSM data, an error occurred that indicated that a value exceeded system limits. This issue has been fixed. [18676]

45. Transaction processing for collected TSM tape drives was updated to ensure that the number of tape drives in the tape library is correct when tapes have been removed from a library. [18385]

46. An issue with TSM data collection resulted in TSM client nodes not being collected for TSM 5.2 servers. This resulted in errors when checkinstall was run. [19038]

47. TSM data collection now saves host alias data correctly in the database. Prior to this fix, a flag was incorrectly set to indicate that the alias was manually added via CSV load. [19108]

48. The deletion of IBM Tivoli Storage Manager orphan servers was causing errors in the database tables. This has been resolved. [19102]

49. TSM data collection was updated to correctly capture the ACS drive ID of a TSM drive. Prior to this fix, a number format exception occurred during data collection. [18601]

50. For TSM data collection, when attempting to collect from a new, unsupported version of TSM, the latest supported driver is used. [18813, 18783]

51. The filespace_name column in the TSM filespace database table was increased to 2048 characters. [19413]

52. TSM Job Summary Details collection thread would not complete if it was interrupted when inserting data. [19414]

53. The Running and Queued Job Summary was updated to fix an issue that caused the report to not render. [18921, 18762]

54. For HP Data Protector collection, when saving the tape library, the host name of the library path could not be found, causing an exception message. The host record is now created properly in the database. [18228]

55. The HP Data Protector database purge routine for the message log was configured to purge the data every 90 days. [18248]

56. Generic Backup database tables are now always created automatically during the Portal installation and schema creation. [18831]

57. An issue with the retention of Data Domain file system historical data was fixed in this release. Prior to this fix, if there was a problem with data collection, the historical data was deleted. [19234, 19233]

58. A database purge routine for Data Domain storage unit data was revised to accommodate the use case where the disk volume associated with the storage unit is not associated with the disk pool on the same management server. [16942]

59. The database purge utility, purgeOrphanServerDetail, was fixed to ensure successful completion of the database purge. [18728, 18884]

60. Several Backup Manager reports, such as Job Summary, now have a scope selector where only the relevant backup products are listed in the Advanced scope list. Prior to this release, products that did not exist in an enterprise were incorrectly available in the list that results from clicking the Advanced button in the scope selector. [18833]

61. The documentation incorrectly stated that the bar chart on the Tape Library and Drive Utilization report allows users to drill down to a backup event report. This functionality is not available, and the Report Reference Guide has been updated. [18857]

62. The Tape Library and Drive Utilization report has been revised to allow the user to drill down on the Media Count instead of Number of Slots.[18064]

63. Data Domain data collection was improved to handle exceptions that may occur on busy systems. These exceptions would cause the data receiver to time out. [18026]

64. The Job Status Summary report was updated to fix the following issue: A bar chart used an incorrect color in the rendition. The colors in the chart have been revised to be consistent with the rest of the application, blue for success, red for failure. [18518]