19711

The data dictionary for Storage Viewer for Backup was updated to include descriptions for the possible values of the backup policy type.

19879

Database process now prevents duplicates when saving host aliases. Prior to this release, the following error was logged: exact fetch returns more than requested number of rows.

19899

For the Generic Backup Data Collector, the length of the Pathname database field was increased to accommodate larger names.

19914

The Tape Media Summary report was updated to fix an issue where, under certain circumstances, the report was empty.

20053

The Error Log Summary report now correctly displays the error codes along with the error descriptions. This error was introduced in the upgrade to versions 9.0 (and higher) and has now been fixed in this release.

20548

The size of several Avamar database columns was increased to accommodate larger values: apt_avm_event_catalog.event_catalog_id and apt_avm_event modify.event_catalog_id.

19905

Due to a database limitation on error code length, EMC Avamar jobs with codes exceeding the length were failing. The column length has been increased from 6 to 12.

20334

In Object Maintenance, when attempting to delete an Avamar server that is a master server, a message now explains why the server cannot be deleted.

SC-3516

The Generic Backup Data Collector has been updated to include the Schedule Name in the CSV file that is used to import backup data. The comma-separated file contains 15 data elements from the backup/restore jobs (prior releases supported 14 data elements). Note that each field must have an entry, even if it is a null entry within the commas. Field values cannot contain embedded commas. All string fields must be enclosed within single straight quotes.

20454

20573

20568

19301

Avamar data collection was updated to fix an issue where the Avamar UID was appended to the client name.

19470

During Dell Compellent data collection, the following error was identified in a log: “Failed to save due to unexpected error:: SQL Error(-2291) ORA-02291:integrity constraint (PORTAL.APS_CPL_ISCSI_PORT_C1) violated - parent key not found.” A database change has fixed the logic that caused this error.

20612

The Data Domain System Performance report no longer ignores the end date from the scope selection. Prior to this fix, the report graphed data that was outside the scope’s time range.

20646

When adding a Data Domain collection policy, if the set of server addresses contained a new line and a comma as separators, the addresses were not separated correctly. A combination of commas and white space separators is now allowed.

20666

For Data Domain collection, in some cases the virtual tape library name was null. This issue has been fixed in this release.

20583

Logic was fixed that caused the following error in the scon.err log:

19948

For NetBackup data collection, support has been added for the Image Cleanup job type.

18894

In the NetBackup Data Collector policy, the default schedule for client details collection has been changed to Tuesday at 9:00 a.m.

20474

19442

Fixed the deadlock errors displaying during Symantec NetBackup collection.

20251

When two or more media servers with tape libraries were attached to a NetBackup 7.5+ Master Server, only a single media server’s drives would be collected. With this fix, drive name is being used as the unique identifier when collecting tapes from multiple media servers.

19512

When processing NetBackup Synthetic Full Backup jobs that have an SLP as a destination, data collection now collects the correct start time and date for the job. Prior to this fix, jobs appeared to be running longer than the actual runtime.

19546

The data receiver was updated to fix an issue where NetBackup 6.5 disk volume collection failed to be stored in the database when null values were encountered in the read/write streams.

19740

Database logic was modified to correct an issue where the NetBackup duplicate job status for parent and child jobs did not match.

19749

The Hitachi Storage Viewer Data Collector Installation Guide for Backup was updated to correct the Windows directory paths for the NetBackup load script, load_nbu_backups.

19795

The Hitachi Storage Viewer Data Collector Installation Guide for Backup was updated to include configuration details for collection of NetBackup Master Servers that belong to a cluster.

19529

The size of the CLIENT_RESOURCE_ID column was increased to 10 in the following NetWorker database tables: APT_LEG_CLIENT_RESOURCE, APT_LEG_CR_GROUP, APT_LEG_CR_MEDIA_SERVER, APT_LEG_JOB.

19812

For TSM, the length of the Schedule ID field was increased in several database tables to accommodate larger values.

20395, 20396

20773

To accommodate a smaller set of data results, three reports were updated to include KB as a unit of measure. Previously, the measurement was in MiB. The following reports were updated: LUN Performance, Array Performance by LUN and Array Performance by RAID Group.

20609

The LUN Details report displayed an erroneous error about the Group by value. This has been fixed.

20557

The method used to handle the time period value was not being correctly used by the LUN Performance drill down report when changing the scope. The time range is now revisable.

20455

When a capacity collection policy is updated with a new schedule, the change is now reflected immediately, rather than waiting for the next collection cycle.

19991, 19986

The criteria for determining licensing limits for Storage Viewer for Capacity licensing has been revised. The new criteria is as follows: When licensing Hitachi Storage Viewer for Capacity, the license is based on the raw amount of SAN storage in your environment. Hitachi Storage Viewer only includes arrays that have been polled within the last 30 days.

20549

The chargeback log database table has been added to the Array Enterprise Object, making it available for custom reports created with the Dynamic Template Designer.

19639

User-selected values for capacity chargeback policies would randomly change when editing the policy. This has been resolved and the correct values are displaying.

19873

An error occurred when creating LUN mapping records for multi-path disks. LUN mapping is now handled correctly.

20827

During a Portal upgrade, duplicate records in the LUN performance log table caused the upgrade to fail. This special case is now handled during the Portal upgrade.

20773

After rendering the Array Performance by RAID Group report for last 24 hours, and drilling down on some of the # LUNs numerics, not all reports rendered.

20553

The Array Performance by RAID Group report and the associated LUN Detail Report were rendering response times of zero in most intervals. This has been fixed in this release.

19982

Due to a data collection issue, after an upgrade, the Array Utilization Summary reported zero LUNs for arrays. The drilldown to Array Capacity and Utilization no longer displays zeroes under the LUN Summary.

20443

Logging of capacity performance collection has been improved by changing certain events from errors to warnings, thereby reducing the clutter in the scon.err log file. In some cases, this logging activity came from transient files during disaster recovery replication operations.

20254

Performance improvements have been made for the following database published views: aps_v_lun_stats_day_log, aps_v_lun_stats_log, and aps_v_lun_perform_log.

SC-3732, 19893

For collected array LUN performance data, default retention periods (raw, hourly, and daily) control the retention of the data, as shown in the following list. At each data collection cycle, Hitachi Storage Viewer determines which data needs to be aggregated and moved to the next period. When the daily performance data ages out, it gets deleted. See the Hitachi Storage Viewer System Administrator’s Guide for instructions on how to modify the following defaults. These defaults represent contiguous interval periods.

A new LUN performance database published view (aps_v_lun_perform_log) contains raw, hourly, and daily LUN performance history data. This new view replaces the previous LUN performance views (aps_v_lun_stats_day_log and aps_v_lun_stats_log). These previous views can continue to be used, with the following understanding, based on the default interval settings shown above:

20535

The LUN Performance report was modified to remove the “Show Capacity in” scope selector component.

SC-2213, 20253, 19726

The aps_v_storage_array database published view was enhanced with additional columns. Also, a hot_spare column was added to the aps_v_pdev view.

20259

Prior to this release, an error occurred while adding a capacity chargeback policy.

19582

After the creation of capacity chargeback policies for DAS, the Storage Viewer for Virtual Servers collection status showed errors. These errors occurred because the hosts subscribing to the policies did not have associated LUNs or arrays. This issue has been fixed in this release.

19587

Performance improvements have been made for host-to-LUN mapping logic when the data is collected and saved to the database.

19602

The Host Capacity & Utilization reports were updated to fix an issue where the host type selection was not filtering the results correctly. If no host types are selected, the report will display results for VM Servers, VIO Servers, and Other host types.

SC-3018

Support for Dell Compellent Enterprise Manager 14.2.2.6 is included in this release.

20673

The following prerequisite has been added to the documentation for the EMC VNX (CLARiiON) data collector:

A low security level for certificates is required. Ensure this setting by using the following command:

SC-325

Support for EMC Isilon performance reporting was added to this release. The following new reports are now available:

Several EMC Isilon performance database published views were updated to include an isi_protocol_id column. See the Hitachi Storage Viewer Database Programmer’s Reference Guide: aps_v_isi_protocol_prf_log_min, aps_v_isi_protocol_prf_log_hr, aps_v_isi_protocol_prf_log_day, aps_v_isi_protocol_performance.

19347

Prior to this release, during EMC VNX (Celerra) data collection, an error was reported: vnx_adaptor_pkg.saveVnxFileSystem: base volume ID not found. This occurred when loading the file system data. This issue has been fixed in this release.

20100

The EMC VNX (Celerra) Data Mover Summary report was modified to fix an issue where the time period component was no longer in the scope selector after upgrading to Storage Viewer 9.x.

19385

Processing of EMC Symmetrix storage group and LUN mapping details was modified to fix an issue that caused an integrity constraint error message.

19434

Collection of EMC Symmetrix arrays without ports now logs this as an informational message rather than a warning in the scon.log file.

19508

NetApp database tables were updated to accommodate larger values for several columns: nbr_scsi_ops, nbr_read_blocks, nbr_read_ops, nbr_write_blocks, nbr_write_ops.

20482

The aps_v_nap_quota_log database published view was enhanced with the following additional columns: nap_group_id, nap_user_id, and nap_volumne_id.

20655

Portal logging no longer reports an error when running the Array Capacity & Utilization report for NetApp systems. This occurred when the number of LUNs was null, which is actually a valid value.

19728

The Port Throughput by Array report was updated to fix an issue with the IO/sec values displayed for NetApp storage systems.

20405

NetApp data collection now succeeds when the policy contains a comma-separated or new-line-separated list of server names.

20462

NetApp performance data collection was updated to improve the scheduling of processing threads.

20731

Performance improvements for NetApp Cluster-Mode data collection ensure that ONTAP API resource limits are not exceeded.

20720, 20721

An update ensures that the Data Collection Status page displays the correct finish status for NFS exports and also the correct finish transactions for CIFS and aggregates.

20722

For collection from NetApp 7 arrays, when the normal http connection does not work, the Data Collector tries to connect to the arrays via https. Prior to this patch release, an authentication exception could occur when attempting the https connection because the user name and password were not configured correctly for the secure connection.

19387

Processing of HP 3PAR logical and physical device mapping details was modified to fix an issue that caused an integrity constraint error message.

20342

Collection with a CLI from the newest HP 3PAR 7000 series arrays had the values for total capacity incorrect because the chunklet calculation defaulted to 256MB when it found an unknown array model. The Chunklet Size is now used to calculate the value.

20644

Documentation was updated to reflect support of HP Command View Advanced Edition for HP StorageWorks XP arrays. Configure an Hitachi Block Storage data collector policy to collect from these systems.

20275

In an effort to make the Array Capacity and Utilization report more accurate for HP 3PAR, certain labels have been changed in the report. Those fields that referred to VLUNs have been changed to Virtual Volumes (VV).

20192

For Hitachi block array collection, the default Hitachi Data Systems version was updated in the database collector configuration. Because the default version was set to 6.3, the collection was failing. The default version is now 5.x.

SC-3179, 19739

For Hitachi array data collection, an update fixes an issue that caused an exception while parsing and saving journal pool and storage array details. In support of this fix, the Journal Pool Name has been added to the following published views: aps_v_hds_journal_pool_log and aps_v_hds_journal_pool. These are documented in the Hitachi Storage Viewer Database Programmer’s Reference Guide.

19828

The aps_v_hds_array_group database published view was enhanced with the following additional column: journal_pool_id.

20318

A database update fixes an issue that caused a numeric or value error: character to number conversion error that occurred during Hitachi array collection.

19415

A database change was made to handle the condition that caused this error: “array group not found for arrayGroupNbr: -1.” This was specific to Hitachi array data collection.

20724

For Hitachi arrays, the database logic has been modified to ensure that the array family capacity chargeback policy works as expected.

19831

For Hitachi arrays, the logic for determining which LUNs are open reserved LUNs was modified. This fixes an issue where allocated LUNs are listed in the unallocated LUNs list.

19881

The database was updated to fix an issue that caused the following error message: “ SQL Error(-1400) ORA-01400:cannot insert NULL into ("PORTAL"."APS_HBA_PORT"."IS_ACTIVE").” This occurred when the Port WWN was null.

19882

The logic for determining when file system data is deleted fixes an issue that caused an integrity constraint error message.

20547, 20689

To accommodate larger values, database update for IBM SVC increased the size of over_allocation_pct and counts columns in the SVC mirror extent database table.

16254

Database performance improvements have been implemented to ensure optimal performance for certain database table queries and saves; for example, when saving the host chargeback log.

19502

During an upgrade, two data collector tables/logs were inadvertently being deleted from the database. This has been revised to retain the tables when upgrading from one version to another.

19709

A database update was made to accommodate large attribute values (increased from 350 to 4,000 characters).

19920

The load_package.loadGroupMemberFile utility was modified to recover when encountering excessively long input lines.

19990

For the Dynamic Template Designer, the Filesystem Summary method was modified to handle an Oracle function 4000 character limitation.

20171

The contents of the database scon.log file will now rotate every week on a Tuesday morning at 7:00 a.m. This should prevent this file from getting too big. The existing scon.log will be copied to scon1.log and the scon.log file will be emptied. A week later, the job will run again and scon1.log will be overwritten.

20191

Improvements to database published views ensures that only data relevant to the report scope is displayed.

20488

Changes to the database improve how errors appear in the Database Error Summary report. Prior to this revision, module names included input parameters, which cluttered the report.

20502

Database changes were made to correct erroneous error messages in the scon.err log.

20634

The database now handles large messages, such as trace logs greater than 4,000 characters. Prior to this fix, errors appeared in the database scon.err log file.

20732

Database logic was modified to correct an issue that, under certain circumstances, caused a “Function created with compilation errors” error during a Portal upgrade.

18654

For an IBM VIO data collector, the known hosts and privacy key files are now encrypted.

19241

A number of data collector screens did not display green help text for some fields. This has been correct and now all fields display green help text.

20304

Data Receiver logs were filling and rotating very quickly because all data envelopes were being logged at log level INFO. This is all data collected by 9.x collectors. This has been resolved by only logging data at the log level DEBUG and envelope metadata at level INFO.

20675

The listcollectors.sh|bat utility, which is used to identify data collector configurations, was updated to clarify details. The Server ID label has been changed to: Sub-system/Server Instance/Device Manager Id.

20335, 20727

Prior to this release, when a Data Collector policy was modified, for example, with a new server name, multiple processing threads started and collection ran in parallel for the same server. Likewise, in some cases, if a Data Collector was disabled and then enabled, multiple threads were initiated. This patch release ensures that these additional processes are not started.

18444, 18465

The Hitachi Storage Viewer Data Collector Installation Guide for Backup has been updated to clarify the overview steps for NetBackup Distributed Data Collection.

19118

Additional customization settings (managed in the portal.properties file) have been documented in the Hitachi Storage Viewer System Administrator’s Guide.

19394

The Hitachi Storage Viewer Data Collector Installation Guide for Backup has been updated to include the standard WMI proxy port in the CommVault Simpana architecture diagram.

19551

The Load NetBackup Events instructions in the Hitachi Storage Viewer Data Collector Installation Guide for Backup were corrected to include all the necessary command parameters.

19598

The SSL configuration instructions in the Hitachi Storage Viewer System Administrator’s Guide were updated to accurately reflect details for configuring virtual hosts.

19657

The Hitachi Storage Viewer Data Collector Installation Guide for Backup has been updated to provide additional information for Windows installation for NetBackup.

19747

The Hitachi Storage Viewer Database Programmer’s Reference Guide was updated to include the vault_sent_date column in the view: apt_v_nbu_job_tape_media. Prior to this release, this column was only exposed in the apt_v_nbu_tape_media published view.

19798

The Hitachi Storage Viewer System Administrator’s Guide was updated to include additional details in “Loading Host and WWN Relationship.”

19817

The Hitachi Storage Viewer System Administrator’s Guide was updated to include a procedure for enabling/disabling capacity chargeback logging.

19818

The Hitachi Storage Viewer User’s Guide Dynamic Template Designer section was updated to include a note about the Boolean operators used when defining static filters.

19892

The Hitachi Storage Viewer User’s Guide was updated to include a note in the Selecting Report Scope section: Report scope time period must include the 12 am midnight boundary when choosing a scope of less than 24 hours.

19910, 19606

Instructions for disabling the cloud service to the portal have been added to the System Administrator Guide. These instructions cover modifying the portal.properties file.

19918

Several additional portal.properties configurations have been documented in the Hitachi Storage Viewer System Administrator’s Guide to aid in customizing the following: Maximum lines for exported reports, default report export path, host management page size, path for the Hitachi Storage Viewer for File Analytics database, and disabling the cloud.

19938

The Hitachi Storage Viewer System Administrator’s Guide was updated to include a the steps for stopping and starting the reporting database on a Windows Portal server.

20073

All Data Collector Installation Guides have been updated with an appendix that contains a table of default firewall ports. This same information has been added been to a tech note titled: Firewall Configuration: Default Ports.

20246

The Hitachi Storage Viewer License Installation and Guidelines contains updated information about how IBM Tivoli Storage Manager (TSM) licenses are counted.

20353, 19424

The Hitachi Storage Viewer Installation and Upgrade Guide for Linux was updated to include the required configuration (mod_status enabled) to view the apache server status page. In addition, instructions have been added to update to Apache and Tomcat versions 2.4.6 and 7.0.42 respectively.

19488

The Hitachi Storage Viewer Certified Configurations Guide was updated to include support for CMCNE (Connectrix Manager Converged Network Edition).

19506

Fixed a database exception for SAN Fabric Cisco switch data, where the size of the VSAN identifier database column needed to be increased to accommodate larger data values.

20119

Added and revised columns in the Host to Storage Summary report:

20401, 20418

Certain database events that were logged as errors are now logged as warnings:

20621, 20619

During collection of switch performance data, database messages were logged as errors in scon.err when there was an anomaly in the sequence of data collector threads (for example, the physical switch was not yet collected, but other metadata was ready for database persistence). These messages are now logged as warnings in scon.log.

19006

Additional prerequisite details for the Host Inventory probe have been documented in the Hitachi Storage Viewer Data Collector Installation Guide for File Analytics.

20090

A script to retrieve drive folder sizes was fixed to account for gaps in the folder hierarchy and to also include the last folder in the stack, which was missed in the previous version of the script.

20311

Additional Storage Viewer for File Analytics privileges have been documented, to be referenced if api-* does not meet your security requirements for data collection from NetApp-7 systems.

20311

Additional api permissions have been documented for Storage Viewer for File Analytics data collection. See the Hitachi Storage Viewer Data Collector Installation Guide for File Analytics for details on configuring a user with these privileges.

20382

The Duplicate Files report no longer fails to load if there is no data to display.

19348

When collecting host data, if a duplicate host is found, an informational message is logged in the scon.err log file. This is treated as information rather than an error, as there may be a legitimate reason for the duplicate.

19957

Prior to this release, if a Data Collector passcode contained a pipe character, the collector failed to validate in the Host Inventory view. This issue has been fixed.

SC-3295, SC-3486, SCP-110

As of 9.2, host resources data collection no longer supports collection from the Windows 2000 Server, Advanced Server operating system.

20623

The Host Utilization Detail report no longer displays the word, Null, as a value in the report’s table.

20540

A fix to AIX host data collection now ensures that the CPU collection data is populated when the Processor probe is enabled.

20531

The import process for a report template created with the Dynamic Template Designer in version 9.1 has been enhanced with better error handling for version 9.2. A new error message is displayed when appropriate explaining the why an import failed.

20640

When adding a host group that already existed, the Portal did not return a proper message because the error code number had been changed. The operation now refers to the new error code and displays the correct message.

20615

The Method Designer in the Dynamic Template Designer was inadvertently deleting queries you edited. This has been corrected and queries can again be revised without issues.

20835

The Dynamic Template Designer scope selector components have been alphabetized.

SC-3936

The upgrader script has been enhanced to detect and explicitly show a patch release version when it is applied as an upgrade to an installed version of Hitachi Storage Viewer.

16473

Online help was available from a hyperlink without requiring authentication. Authentication is now required.

18991

Column headers became misaligned in some reports when using Internet Explorer 9. This browser issue has been resolved.

19031

The Mission Control Performance report column headers are now static.

19075

In a previous version, report templates that were copied into the same folder as the original caused the copy to be listed as the original template. This issue has been resolved, as copied items can no longer be pasted into the same folder as the original.

19078

The Explorer was unable to distinguish between Dynamic and SQL templates. This caused it to incorrectly display the type. The Explorer now correctly identifies the template types.

19293

Prior to this release, when a user stopped sharing a report template, report or dashboard that had a shortcut copied by the shared user, the operation failed. This has been fixed in this release.

19340

Prior to this release, when importing a Dynamic Template that contained a stand-alone method, an error occurred when a large amount of data was returned from the template query. Template validation has been implemented to prevent this error.

19367

Prior to this release, if user folders contained any reports or shortcuts, they could not be deleted. You are now prompted to confirm the deletion and then allowed to delete the folder.

19389

The Portal Explorer now refreshes the display when a copy/paste operation completes.

19467

During an upgrade, if the Tomcat home directory was set to something other than the default directory of /home/tomcat, the upgrade would silently fail. The upgrader now explicitly checks if the directory exists and provides an error message if it does not.

19563

Previously, the Capacity License Usage Detail report displayed license capacity using incorrect units. The report now shows the correct units, GB.

19581

The maximum length for a dashboard name has been increased to 80 characters.

19617

The Explorer now retains the sorted order when switching to another tabbed view and returning to the Explorer list.

19618

Changing the scheduled time of an Export Scheduled Report resulted in the report not being exported and an error was displayed. Now, the scheduled time is honored and exporting is occurring properly.

19620

Issues with exporting a Dynamic Template that has a method have been fixed in this release.

19622

Improvements to the host inventory search ensure that the paging information (page number, page size, or results count) is displayed in the results.

19624

When adding a new host group, if you pressed Enter instead of clicking OK on the dialog, you were logged out of Hitachi Storage Viewer. This has been fixed and the Enter key disabled.

19694

When exporting a report such as Mission Control, the indicator icons, such as blue, red, green, were not displaying for some customers. This was caused by the customer’s network configuration and the way the images were handled in the code. The indicator icons are now displayed properly for all exported reports.

19697

New server types have been added to the Portal so that when searching host administration errors do not occur: Symantec NetBackup Storage Server and Generic Media.

19698

A Portal update fixes an issue where when the OS type of a host is changed (for example, from Unix to Windows), the database is updated to reflect the change.

19699, 20085, 20096

When exporting or emailing a report as a text format, you now have the option to have the text file use a delimiter of your choice and quotation marks.

19729

An update to the Portal corrects an issue in the SQL Template Designer, where setting the cascade to sub-groups option in the scope selector caused the report template to become corrupt.

19746

Prior to version 9.2.00, headers were not displaying on report portlets when added to a dashboard. The code has been revised to always show the headers in a portlet view.

19786

The Dynamic Template Designer dialog window now includes a Cancel button to enable canceling an add/insert operation.

19820

The SQL Template Designer was updated to fix an issue where, for bar charts, the formatting tab did not retain the value set for the caption.

19840, 20071, 19596

The export path for scheduled reports has been enhanced to ensure that exported output is saved to writable directories.

19871

Report scope selectors were enhanced so that a larger number of hosts can be included in the scope.

19907

In the Host Management Administration panel, after selecting a host that is associated with Storage Viewer for Virtual Servers and getting more details via the details button to the Host Details Report, in some cases the detail report was blank. This issue occurred only in certain environments where a host was obsolete. This specific case is now handled appropriately.

19931

The Recent section of the Explorer had stopped allowing sorting on the columns. This has been fixed.

19942

The full search didn’t filter correctly when selecting the name or description when no keyword text is provided. The search returned no results. This has been resolved. If a keyword is not provided, now all results are displayed.

20007

The Dynamic Template Designer Field Configuration window now closes as expected when the Esc key is pressed.

20036

Filtering of tabular reports now processes regular expressions correctly.

20083

Bar charts with drilldowns on a bar that go to a bar or a line chart report now display data only for the date range relevant for the selected bar. Prior to this fix, the data in the drilldown report contained more data that was not constrained to the bar’s date.

20118

The Cloud section on the Explorer is now completely removed if a user does not have the Cloud privilege enabled. The section is not displayed on the Explorer until the privilege is selected.

20144

Prior to this release, when exporting a filtered report to a PDF, the action failed silently. This has been corrected and now PDFs can be created when exporting a report.

20174

On the Admin tab in the Explorer, the section Users and Groups has been renamed to User Groups.

20177

If save password was enabled for the browser, auto complete was also enabled in Manage Credentials dialog. The Password field was automatically populated. Auto-complete has been disabled for the dialog. The Password field now displays as empty.

20187

A database change fixes an issue where deleting a Data Collector that had advanced parameters caused the deletion to fail.

20213

When emailing a saved report, the email address and subject line were lost when clicking the Schedule button. This has been fixed and the dialog now retains the address and subject of the email.

20320

This bug resolves an issue with exporting a report to a PDF and mailing it.

20517, 20519

Improvements to Portal error logging include a simplified log message when the Portal encounters connection issues: 1) when updating the aptare.jar data collection file; 2) when connecting to the cloud. Prior to this change, the portal.log file included unnecessary stack traces.

20635

Portal logging now includes the report name when an out-of-memory error occurs while rendering a report with a large amount of data.

20521

The Portal now handles an connection error that occurred while executing a SQL template, which caused the following message to appear in the portal.log file: “Exception while closing connection Already closed.”

20483

Due to an issue with the scope selector, the VM Size Forecast report was not showing future dates. The scope selector now allows for a selection of future dates.

20123

Because of a database restriction, the VMware physical disk collection was failing. This has been corrected by increasing the column length for APT_VMW_PHYSICAL_DISK.PATH_POLICY to 32.

19384

Updates to the processing of datastore usage details fixes an integrity constraint issue.

19640

The logging level for certain reports (such as VM server detail) was modified to minimize unnecessary “field not found” messages.

19763

A database change fixes an issue where duplicate ESX servers were being saved to the database.

20011

The calculations for VM disk capacity have been revised to include the provisioned size of the base disk if it had been thin provisioned. This impacted the VM Disk fields in the VM Summary and Datastore Utilization Summary reports.

20012

The VM Detail report now displays the correct capacity values in the Disks section. The logic has been changed to account for virtual disk-to-LUN multipathing, where some paths may be associated with a LUN, while other paths do not have a LUN association.

20039

The Datastore Usage Breakdown report now includes an “Unknown” column.

20065

The apt_v_virtual_system published database view as been updated to include the vmw_cluster_id column. See the Hitachi Storage Viewer Database Programmer’s Reference Guide.

20093

A database update fixes the logic that caused the following error: “vmw_common_pkg.FcAdaptorExists: exact fetch returns more than requested number of rows.”

19865

The following reports neglected to display results for all Hitachi Storage Viewer products: VM Detail, Host Detail, VM Server Detail, Host Utilization Detail. With this fix, all source data for the host is displayed.

19921

The default number of hours to hard delete VM data has be revised to 96 hours.

20135

Due to column length errors during VMWare data collection, the column size was increased to 1024 with an ellipses if the content was truncated.

20217

The VM Files Summary now displays N/A for the maximum file size, if that data is not available.

20219

VMware collection for multi-host datastores was updated to apply the sizes calculated from the VM files, each time the datastore is requested. Prior to 9.2, the VMDK file size may have been inconsistent.

20237

Several Advanced Parameters have been made available to support Storage Viewer for Virtual Servers optimization. These are documented in the Hitachi Storage Viewer User’s Guide.

20286

Logic was modified to handle fields that may be null.

20409

VMware data collection now filters out negative performance values. These negative values occur when vCenter has not collected data from the ESX servers for the requested time period.

20457

When permanently deleting an ESX server via Object Maintenance, the associated data is remove as well. Prior to this release, the VM Summary report continued to display data for the deleted server.

20506

When collecting from a multi-host datastore, Could not find Extent errors were reported in log files. This message has been downgraded from an error to a warning because no data loss occurs. All data is ultimately persisted.

20575

The data collector was modified to fix an issue that caused a ClosedByInterruptException error when the collector ran the same processing thread a second time.

8047

During data collection, intermittent errors were logged to the database scon.err file if the host name was not available when the network data was being saved to the database. These events are now listed as warnings in the scon.log file since this is simply a processing sequence anomaly.