You can add and delete nodes from schedules by associating and disassociating the nodes with the schedules. TSM nodes can be associated with more than one schedule.
You can perform the following activities when managing client node
associations with schedules.
Task | Required Privilege Class |
---|---|
Adding new nodes to existing schedules | System or restricted policy over the domain to which the node is assigned |
Moving nodes to existing schedules | System or restricted policy over the domain to which the node is assigned |
Deleting nodes associated with a schedule | System or restricted policy over the domain to which the node is assigned |
Displaying nodes associated with a specific schedule | Any administrator |
You can add new nodes to existing schedules by associating the node to the schedule. To associate client nodes with a schedule, you can use the administrative Web interface or you can issue the DEFINE ASSOCIATION command from the command line interface. For information, see Associating Client Nodes with Schedules.
You can move a node from one schedule to another schedule by:
You can display information about which nodes are associated with a specific schedule. For example, you should query an association before deleting a client schedule.
Figure 49 shows the report that is displayed after you enter:
query association engpoldom
Figure 49. Query Association output
+--------------------------------------------------------------------------------+ |Policy Domain Name: ENGPOLDOM | | Schedule Name: MONTHLY_BACKUP | | Associated Nodes: MAB SSTEINER | | | |Policy Domain Name: ENGPOLDOM | | Schedule Name: WEEKLY_BACKUP | | Associated Nodes: MAB SSTEINER | | | +--------------------------------------------------------------------------------+
When you remove the association of a node to a client schedule, the client data is no longer managed according to the schedule. However, the remaining client nodes still use the schedule.
To delete the association of the ENGNOD client with the ENGWEEKLY schedule, in the policy domain named ENGPOLDOM, enter:
delete association engpoldom engweekly engnod
Rather than delete a schedule, you may want to delete all associations to it and save the schedule for possible use in the future.