Setting up a schedule on the client machine NodeA1

Use this procedure to define a schedule on the client machine with the client node NodeA1.

update node NodeA1 passexp=0

To set up a schedule on the client with client node NodeA1:

1. Create a dsm.sys file in the /usr/tivoli/tsm/client/ba/bin directory if one does not exist. Add the following servername stanzas:
   1. Add a servername stanza for the file system backups that are associated with your Tivoli Storage Manager backup archive client. For example:

      servername   TSMbackup
         commmethod   tcpip
         tcpserveraddress    site.xyzinc.com
         tcpport    1500
         nodename   client
         passwordaccess    generate

      The servername TSMbackup setting must be specified in the dsm.opt file that is associated with the Tivoli Storage Manager backup archive client. The default directory location is /usr/tivoli/tsm/client/ba/bin.

   2. Add a servername stanza for the backups that are associated with Data Protection for Oracle. For example:

      servername   TSMOracle
         commmethod   tcpip
         tcpserveraddress     site.xyzinc.com
         tcpport    1500
         nodename   NodeA1
         passwordaccess    generate
         passworddir       /home/oracle user 

      Replace oracle user with the Oracle user ID of the target Oracle database instance.

      The servername TSMOracle setting must be specified in the dsm.opt file associated with Data Protection for Oracle. The default directory location is /usr/tivoli/tsm/client/oracle/bin64. This dsm.opt file can have a unique name, such as dsmoracle.opt. Make sure that the dsmi_orc_config option specifies the user options file, dsmoracle.opt in Step 1b, associated with Data Protection for Oracle. For example:

      dsmi_orc_config /usr/tivoli/tsm/client/oracle/bin64/dsmoracle.opt

   3. Add a servername stanza for the scheduled backups associated with Data Protection for Oracle. For example:

      servername   DPSched
         commmethod   tcpip
         tcpserveraddress    site.xyzinc.com
         tcpport    1500
         nodename   NodeA1
         passwordaccess    generate
         passworddir       /home/oracle user

      Replace oracle user with the Oracle user ID of the target Oracle database instance.

2. Make sure that there is a symbolic link to this dsm.sys file so that the file is available to the Tivoli Storage Manager API directory, /usr/tivoli/tsm/client/api/bin64.
3. Create the scheduler backup script, schedbkdb.scr, in the /usr/tivoli/tsm/client/oracle/sched/ directory. This script is the scheduler backup script that was defined for the scheduler in Setting up a schedule on the Tivoli Storage Manager server. The scheduler backup script runs the command script mysched.scr, which runs the RMAN backup script bkdb.scr. This example shows the scheduler backup script schedbkdb.scr:

   #!/bin/ksh
   su - OracleUser -c /home/oracle/sched/mysched.scr

4. Create the command script mysched.scr in the /home/oracle/sched/ directory. A sample of the command script mysched.scris provided: in the following example:

   #!/bin/ksh
   export ORACLE_HOME=/orc11g/app/oracle/product/11.2.0
   export PATH=$ORACLE_HOME/bin:$PATH
   rman target agnttest/agnttest@target rcvcat rman/rman@rman
   cmdfile /home/oracle/sched/bkdb.scr msglog /home/oracle/sched/bkdb.log

   You must place the command text, rman target agnttest/agnttest@target rcvcat rman/rman@rman and cmdfile /home/oracle/sched/bkdb.scr msglog /home/oracle/sched/bkdb.log, on the same line in this command script. The command text is placed on two lines in this example to accommodate page formatting.

5. Create the RMAN backup script bkdb.scr in the /home/oracle/sched/ directory. An example of the RMAN backup script bkdb.scr:

   run {
   allocate channel t1 type 'sbt_tape' parms 
   'ENV=(TDPO_OPTFILE=/home/oracle/sched/tdpo.opt)';
   allocate channel t2 type 'sbt_tape' parms 
   'ENV=(TDPO_OPTFILE=/home/oracle/sched/tdpo.opt)';
   
   backup
   format 'df_%t_%s_%p_%u_%c'
   (database); }

6. Log in as the root user to the system where Data Protection for Oracle is installed as node name NodeA1.
7. Start the scheduler in the inittab. Use the servername parameter to specify the correct stanza to use in the dsm.sys file:

     dsmc sched -servername=DPSched

   Data Protection for Oracle is now enabled for scheduled backups.

INCLUDE /adsmorc/.../DB* mgmtclassnameforDBs 
INCLUDE /adsmorc/.../LOG* mgmtclassnameforLogs 
enablelanfree yes 
lanfreecommmethod sharedmem 
* errorlogname /home/oracle/dsierror__NodeA1.log 

schedmode prompted 
tcpclientport 1502 
schedlogname /home/root/dsmsched_NodeA1.log 
* commmethod tcpip <- unnecessary because it's default. 
errorlogname /home/root/dsmerror_NodeA1.log