The Monitoring functions available in the Tivoli Storage Resource Manager function tree enable you to run regularly scheduled or ad-hoc data collection jobs. These jobs gather statistics about the storage assets and their usage within your enterprise.
The following lists the different kinds of data collection jobs that Tivoli Storage Resource Manager supports:
New Server Discovery - Discovery Jobs. Use Discovery jobs to collect information about the computers in your network. Discovery jobs will find new computers that have been introduced to your network and have not yet been detected by Tivoli Storage Resource Manager.
Availability Monitoring - Ping Jobs. Use Ping jobs to collect information about the availability of the storage assets in your enterprise.
Asset Collection - Probe Jobs. Use Probe jobs to collect statistics about the storage assets in your enterprise, such as computers, disk controllers, hard disks, and file systems.
Usage Monitoring - Scan Jobs. Use Scan jobs to collect statistics about the usage and trending of your actual storage consumption. Scan jobs perform the majority of the work for Tivoli Storage Resource Manager by providing all the data for usage reporting, as well as for quota and constraint analysis. They gather information at both the file and directory level. Profiles enable you to fine tune and control what files are scanned during a filesystem scan, as well as to specify exactly what statistical information is gathered.
Simplified Object Selection and Object Management - Groups. Create groups that represent a set of objects that you define, such as computers and users, to reuse within the different jobs that you run. Groups enable you to define a set of related objects one time and save these selections as a named group for future use in Scans, Probes, Pings or other entities within the Tivoli Storage Resource Manager. When you update the objects within a group, those updates are automatically picked up by the jobs that reference that group.
You can select the following sub nodes within the Monitoring node: