Академический Документы
Профессиональный Документы
Культура Документы
3 Release Notes
NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 463-8277 Web: www.netapp.com Feedback: doccomments@netapp.com Part number: 215-06647_A0 March 2012
Contents
OnCommand Insight 6.3 updates.............................................................................................................. 2 Data sources updates in 6.3 ...................................................................................................................... 2 Special instructions.................................................................................................................................... 2 Reporting updates ..................................................................................................................................... 3 Corrected defects ...................................................................................................................................... 4 Known problems ........................................................................................................................................ 4 OnCommand Insight Data Warehouse schema and table changes ......................................................... 5 Service pack additions............................................................................................................................... 6 How to send your comments ..................................................................................................................... 6
These changes were made to all of the OnCommand Insight products and to OnCommand Insight Data Warehouse.
Special instructions
Before upgrading to 6.3 with storage array using Automated Storage Tiering
Before upgrading to OnCommand Insight 6.3, you should remove any manual tier annotations made on volumes assigned from EMC FAST VP storage pools. Otherwise, OnCommand Insight cannot set default annotations for AST, and the tier utilization reports on AST volumes might not reflect correct data.
Reporting updates
OnCommand Insight reporting in Query Studio now includes online Help that describes the data elements you can use in the drag-and-drop reports. The following changes were made to the pre-defined reports.
New reports
Chargeback > Historical Capacity Accountability by Application report Inventory > DR Replicas report. Displays information on replica target volumes along with their sources Storage and Storage Pool Capacity > Storage Capacity by Tier Storage and Storage Pool Capacity > Storage Pool Capacity Trend
Renamed reports
File System Utilization > Storage Utilization by Host was renamed to Storage Utilization by Application and then Host. Storage Efficiency > Storage Capacity Efficiency Rating report was renamed to NetApp Storage Capacity Efficiency Rating report.
Corrected defects
The 6.3 release corrects these defects. Defect number 22452 Resolution Response time for EMC Symmetrix was incorrectly reported as zero. Response time is now reported as zero only when it is the result of data from the device. Otherwise, no response time is shown. The Port Name field was added to the Port Capacity data model. The Performance Distribution detail view was not generated when a VM was selected in the Topology view. This problem has been corrected. An error was generated when the Analyze Missing Path option was selected for an iSCSI path. This problem has been corrected. The Client did not run from https://localhost. This problem was corrected. Data Warehouse (DWH) data sources in Framework Manager on 64-bit Windows OS could not be accessed. This problem prevented customers from creating a new project or opening an existing reporting model. This problem has been corrected. For NetApp storage, a negative value was reported in the "Unused Raw Capacity (GB)" column of the Storage Pools view. This problem was corrected. The rounding methodology was inconsistent in the consumed capacity and raw capacity columns of the Internal Volume Performance detail view. The same method is used for all capacity rounding now. The link to the VM Storage utilization report did not produce the report. The URL for this report was corrected in the VMware plugin. The installation of JAVA VM for Windows from the Insight server did not work and has been corrected. OnCommand Insight builds a dictionary of keywords from the database to be used primarily when scrubbing XML queries and creating a database backup file for ASUP. Previously, this build failed when it encountered a keyword of more than 255 characters. Now, when a keyword of more than 255 characters is encountered, the build program uses the first 255 characters of that word as the keyword and continues processing.
23744 23890
Known problems
Data Warehouse Build from History and Annotations
If storage resources include automated tiering annotations and those annotations did not exist in the past, then when you choose to the Data Warehouse Build from History option, current annotations might be applied to volumes in the past, even if the annotations did not exist. The OnCommand Insight Server does not retain annotation history. So, when you use the Data Warehouse Build from History option, Data Warehouse applies the current annotations to historical objects. For example, if a volume has an automated tiering annotation and you choose to build the Data Warehouse from history, the automated tiering annotation will be applied to the volume even if the tier did not exist in the past. Workaround: This should not apply in most cases because OnCommand Insight did not support AST before version 6.3. However, to avoid this, disregard tiering information in reports before the date of the upgrade to version 6.3.
Capacity by tier reports incorrect when AST and non-AST volumes included
When you run capacity reports by tier on Automated Storage Tiering (AST) supporting storage pools that have non-AST volumes, the reports show more capacity in AST volumes and less capacity in the tiers that were assigned to these volumes. This is because any volume allocated on a storage pool that supports AST is also considered to be participating in AST and is associated with the AST-assigned tier. Workaround: Run the reports separately for these two types of objects.
Added columns
Schema Name dwh_inventory Table Name storage_pool Columns Added vendorTier autoTiering usesFlashPools Id storageId identifier name Id autoTieringPolicyId storageId vendorTier limitPercent autoTieringPolicyId autoTiering flashPoolEligibility lastKnownAccessTime
auto_tiering_policy
auto_tiering_policy_constraint
volume internal_volume
Schema Name
dwh_dimensions
storage_pool_dimension date_dimension