 | This user documentation was written for BMC Capacity Optimization v9.5.00. The procedures described may therefore slightly differ if you are using BMC Capacity Optimization v9.0.03. |
What's New
| • | Storage Capacity Views and Reports for BCO now supports BMC Capacity Optimization v9.5.00. |
| • | Host information is now available in the Storage Capacity view under the Host Mapping and Reconciled Host Mapping tabs. |
| • | The new column Updated was added to all the tabs of the Storage Capacity view to display the date and time of the latest update for all the metrics. |
Changes and Improvements
| • | The Saturation Risk column now indicates "No risk" when the number of days before saturation is greater than 30 days instead of displaying the actual number of remaining days. |
Fixed issue
| • | On rare occasions, the value 0 could appear in the capacity metrics columns due to an incorrect data mart calculation. |
Known Limitation
| ▪ | By design and in order to properly and automatically represent unique hosts, the Reconciled Host Mapping tab groups together hosts and WWN addresses of hosts that are mapped to the same volumes and combines the capacity metrics of these interconnected volumes. This may result in a too simplified report that does not represent the actual configuration of your datacenter. For example, the storage volumes belonging to a cluster will typically be grouped under one entity representing the cluster, with no difference between the nodes of this cluster. |
| • | The capacity of FAST VP volumes (dynamic tiering) is reported as fully subscribed in each of the underlying storage pools. If, for example, a 1TB volume consumes 100GB of an SSD pool and 500GB of a SATA pool, both pools will be considered as subscribed for 1TB. While not false, this will cause the subscription of a pool and of the entire storage system to be greater than what has been actually subscribed by the hosts. |
|
