Controlling the space collector
The space collector provides historical space information about pools, volumes, boxes, physical disks, systems, and applications. Policies, scheduled services, and console commands are used to initiate space collection and logging to historical databases. Reporting from these databases is then provided within the
BMC AMI Ops
Interface and the
BMC AMI Storage
batch reporting facility.
Two databases are provided to store space collector data, a detail database to contain very granular data over the recent past, and a capacity planning database to contain less granular data over a much longer time period. These databases are referred to as the space collector and capacity planning databases respectively throughout BMC AMI Storage. Defining and maintaining these databases is discussed later in this section.
The space collector provides detail historical logging and reporting of space information. Information is maintained for the following resources:
- Groups and pools
- Volumes
- System summary
- Boxes
- Physical disks
- Applications
The logging facility is controlled with BMC AMI Storage policies and command requests. Policies and commands determine the frequency at which snapshots are logged to the database and which resources are included in the process.
Policies define how often space information is logged for pools and volumes. Each policy specifies an interval or intervals at which space information is logged for the owned pools and volumes. Different policies can specify different intervals at which to log space data. This process allows historical logging to take place frequently for critical pools and volumes, and less frequently for pools and volumes that do not need to be monitored as closely. Less frequent monitoring saves space in the historical database and allows longer data retention periods on the database.
After pool and volume space information is logged, the SPSUM command can be used to create space information by box, physical disk, and system summary. The SPSUM command causes the most recent snapshot of each volume on the database to be summarized to the system, box and physical disk level. These records are then logged to the space database. Each time the SPSUM command is issued, summarization and logging take place. This process allows box, physical disk, and system summary data to be logged at a different interval than pool and volume data, according to the importance of the data and the space required on the space database.
The APPLMON command with the LOG=Y keyword causes historical logging of application data. Like the SPSUM command, the APPLMON command controls the granularity of historical application reporting. The application collector database (SGCDB) is read and snapshots of application space data are logged to the space database.
For more information, see: