Known Issues and Optimizations
Version 10.2.00P7
Known Issues and Optimizations
The following known issues are present in the APTARE StorageConsole 10.xx release.
Issue Number
The Portal un-install process on a Windows platform may not remove all the files in the StorageConsole package.
The File Analytics File List Export feature has an issue where the number of files exported does not match the number of files shown in the File Categories report. This occurs only if the File Categories have been modified and the user running the report belongs to more than one Domain.
Occasionally, tabular reports will display mis-aligned column headings. To avoid this issue, wait for the report to finish rendering before clicking on another tab.
A report template exported from an earlier StorageConsole version can be imported into a later Portal software version, but the template may experience some loss of formatting when imported.
When running checkinstall for VMware collection, error messages may not accurately reflect the cause of the error. Inspect the collector logs for the actual cause of the error.
For SAN Fabric collection, in certain cases, the database may contain aliases that actually do not exist, but they appear to be associated with a zone.
For very large Datastores, VMware Datastore and Performance collection may encounter an out-of-memory condition, causing incomplete data collection. Choose one of the following workarounds:
Disable the Datastores probe (preferred)
Collect each vCenter in a separate Data Collector and configure the memory usage appropriately.
Due to browser caching, there may be times when the data in a drilldown report is out of synch with the data reflected in its parent report. To ensure synchronized data, refresh the parent report and click the drilldown link as soon as the parent report fully renders.
VMware performance collection may fail with an error: specified parameter was not correct. querySpec.size. A workaround can be found in this VMware KB article:
Some versions of vCenter (e.g., 5.5.0) have a hard-coded limit of 25,000 files and directories that can be listed for a directory in a Datastore. This limit may be different for different versions of vCenter. If any directory in a Datastore collected via vCenter has >25,000 files/subdirectories, the contents of that directory (and subdirectories) will not be collected and will be classified as Unknown in the Datastore Usage Breakdown report. Collecting directly from an ESX host does not appear to suffer from this issue, but that may also be version-dependent.
In the Inventory for Backup Servers, in the Backup Master Server Overview, the mouse-over tooltips in the Job Status SLA report display job counts that do not match the underlying data shown in the Job Summary report.
In the Inventory for VM Servers, the VM Cluster Summary report does not list any data. To view this report with data, search the reports and generate the report from the report template in the search results.
EMC Isilon SMB shares in access zones are not being collected and reported in the EMC Isilon SMB Share Summary report.
Reduces the occurrence frequency of an issue with a Microsoft Azure billing data collector probe failure. This error is raised by Microsoft Azure when the data being requested is not ready to be consumed by the Data Collector, as it is still being processed by Microsoft Azure.
When a failure occurs, the data will be collected during the next scheduled collection time.
Certain environments may require optimizations to improve performance or to accommodate a large number of data collection policies.
Customize the Linux File Handle Setting for Large Collections
In Linux, a portion of memory is designated for file handles, which is the mechanism used to determine the number of files that can be open at one time. The default value is 1024. For large collection policy environments, this number may need to be increased to 8192 so that the collector does not exceed the open file handle limit. A large environment is characterized as any collector that is collecting from 20 or more subsystems, such as 20+ TSM instances or 20+ unique arrays.
To change the number of file handles, take the following steps.
1. On the Linux Data Collector server, edit /etc/security/limits.conf and at the end of the file, add these lines.
root soft nofile 8192
root hard nofile 8192
2. Log out and log back in as root to execute the following commands to validate all values have been set to 8192.
ulimit –n
ulimit –Hn
ulimit –Sn
3. Restart the Data Collector.