TIME command with BMC AMI Storage views
Exceptions when using TIME with BMC AMI Storage
BMC AMI Storage historical views make complete use of the TIME command and all of its settings, with the following exceptions:
- When you select a resource (such as a pool or volume) from a historical view, the date and time associated with that resource override the TIME command values in subsequent views. This feature allows you to remain in the time frame of the selected item as you drill down to more detail data.
- Within many BMC AMI Storage historical views, a single resource can be trended, showing multiple intervals of that resource over time. However, a duration of only one interval cannot display a trend. Therefore, if the specified duration is one interval (1I) and trending is in effect, BMC AMI Storage overrides the 1I value and uses a duration of 7 days.
- The cache statistics within the Tape Reporting facility report on data collected at 15-minute intervals. A duration value of 1I is translated to 7. If you do want to see one 15-minute interval you can specify a duration value of 15M, for 15 minutes.
- Within all HSM Activity views, using the HSM DAYS field overrides the TIME command's duration value.
- When using the TIME command with a duration value of interval, you cannot advance the view forward or backward with the NEXT and PREV commands. However, these commands do function for all other duration values.
Intervals and data collection
The TIME command's Duration field tells BMC AMI Storage historical views how many intervals of data to include when reporting data. If you specify 4I for this field, historical views will display four intervals of data. However the time periods represented by these intervals can vary depending on how often the component is set up to collect data.
For example, the Space Collector can collect data for pools and volume at different intervals. Pools and volumes are assigned to a policy, and the policy defines the time interval at which data is collected. Each policy can specify different interval times, causing different pools and volumes to be collected at different intervals. Assume that the TIME command specifies two intervals (2I) as the duration for a pool or volume view. In that case, the Space Collector will display two intervals of data for each policy, regardless of the time frame represented by the intervals. The intervals might represent a day for some pools or volumes, and a week for others.
Similarly, the Space Collector can also collect application data at different intervals, as determined by the relevant APPLMON commands. Each APPLMON command specifies the applications to be collected. Multiple APPLMON commands can be used to collect application data at different intervals. Assume that the TIME command specifies two intervals (2I) as the duration for an application view. In that case, the Space Collector will display two intervals of data for each application, regardless of the time frame represented by the intervals. The intervals might represent a day for some applications, or a week for others.
Some components have no concept of an interval. These components log data as activity occurs and not at a predefined interval. If an interval-based duration is specified, these components interpret one interval to mean either 7 days or 2 days, as follows:
- For HSM Activity views, 2 days
- For Audit Log views, 7 days
- For Event Log views, 7 days