You can automate client operations, such as backup and archive. Figure 3 shows the TSM objects that may be involved in automated client operations. They are listed below:
Figure 3. Automating Client Operations
The client can specify a management class for a file or set of files, or can use the default management class for the policy domain. The client specifies a management class by using an INCLUDE option in the client's include-exclude list or file. See (A) in Figure 3.
The management class contains information that determines how TSM handles files that clients backup, archive, or migrate. For example, the management class contains the backup copy group and the archive copy group. Each copy group points to a destination, which is a storage pool where files are stored when they are backed up or archived. See (E) in Figure 3.
Clients are assigned to a policy domain when they are registered. Schedules that can automate client operations are also associated with a policy domain. See (C) in Figure 3. To automate client operations, you define schedules for a domain. You then define associations between schedules and clients in the same domain. See (B) in Figure 3.
For a schedule to work on a particular client, the client machine must be turned on and the client scheduler must be running.
The scheduled client operations are called events, and information about events are stored in the TSM database. See (D) in Figure 3. For example, you can query the server to determine which scheduled events completed successfully and which failed.