Tivoli Storage Manager has an advance feature where you can automatically define TSM Client schedules for one or more clients and also make the schedules inactive after particular period of time. This feature should be monitored carefully or else it would initiate unnecessary backups which leads to other TSM server process. This can be achieved by using DEFINE CLIENTACTION command.
You can use the DEFINE CLIENTACTION command to specify that one or more client nodes perform a one-time action if the client schedulers are active. If the scheduling mode is set to prompted, the client performs the action within 3 to 10 minutes. If the scheduling mode is set to polling, the client processes the command at its prescribed time interval. The time interval is set by the QUERYSCHEDPERIOD client option.
Also Read: How to configure TSM Client Backup & Archive Schedules ?
One Time backup Scheduling
The DEFINE CLIENTACTION command causes Tivoli Storage Manager to automatically define a schedule and associate client nodes with that schedule. With the schedule name provided, you can later query or delete the schedule and associated nodes. The names of one-time client action schedules can be identified by a special character followed by numerals, for example @1. Remember that this is also dangerous command if you forget to mention nodename in the command, it will run schedule for all the nodes which might result in big havoc.You can use the DEFINE CLIENTACTION command to specify that one or more client nodes perform a one-time action if the client schedulers are active. If the scheduling mode is set to prompted, the client performs the action within 3 to 10 minutes. If the scheduling mode is set to polling, the client processes the command at its prescribed time interval. The time interval is set by the QUERYSCHEDPERIOD client option.
Also Read: How to configure TSM Client Backup & Archive Schedules ?
The schedule name and association information is returned to the server console or the administrative client with messages ANR2500I and ANR2510I. For example, you can issue a DEFINE CLIENTACTION command that specifies an incremental backup command for client node PROD in domain SAPDOM.
define clientaction PROD domain=SAPDOM action=incremental
Tivoli Storage Manager defines a schedule and associates client node PROD with the schedule. The server assigns the schedule priority 1, sets the period units (PERUNITS) to ONETIME, and determines the number of days to keep the schedule active based on the value set with SET CLIENTACTDURATION command.
Syntax
.-*-----------------.
>>-DEFine CLIENTAction--+-------------------+------------------->
| .-,-------------. |
| V (1) | |
'---node_name-----+-'
.-DOmain--=--*---------------.
>--+----------------------------+------------------------------->
| .-,-----------. |
| V | |
'-DOmain--=----domain_name-+-'
.-ACTion--=--Incremental------.
>--+-----------------------------+------------------------------>
'-ACTion--=--+-Incremental--+-'
+-Selective----+
+-Archive------+
+-REStore------+
+-RETrieve-----+
+-IMAGEBACkup--+
+-IMAGEREStore-+
+-Command------+
'-Macro--------'
>--+---------------------------+-------------------------------->
'-OPTions--=--option_string-'
.-Wait--=--No------.
>--+---------------------------+--+------------------+---------><
'-OBJects--=--object_string-' '-Wait--=--+-No--+-'
'-Yes-'
You can also determine how long these schedules that were defined via DEFINE CLIENTACTION commands remain active by using the SET CLIENTACTDURATION command. This SET CLIENTACTDURATION command allows you to specify the number of days that schedules that were created with the DEFINE CLIENTACTION command are active.
Also Read: Different types of Incremental Backups
These schedules are automatically removed from the database whether the associated nodes have processed the schedule or not, after the specified number of days. The following example specifies that schedules for client actions be active for 3 days
Also Read: Different types of Incremental Backups
These schedules are automatically removed from the database whether the associated nodes have processed the schedule or not, after the specified number of days. The following example specifies that schedules for client actions be active for 3 days
set clientactduration 3
If the duration of client actions is set to zero, the server sets the DURUNITS parameter (duration units) as indefinite for schedules defined with DEFINE CLIENTACTION command. The indefinite setting for DURUNITS means that the schedules are not deleted from the database.
0 Comment to "Use this TSM command to define backup schedule for only one time"
Post a Comment