1. Please help support our sponsors by considering their products and services.
    Our sponsors enable us to maintain high-speed Internet connection and fast webservers.
    They support this free information and knowledge exchange forum service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions

Client sched vs Admin sched

Discussion in 'TSM Server' started by TaSMania, Nov 13, 2017.

  1. TaSMania

    TaSMania ADSM.ORG Member

    Joined:
    Nov 17, 2015
    Messages:
    52
    Likes Received:
    1
    First of all, I hope it's under correct topic, configuration. Sorry if not and please move to correct topic.

    So I know we schedule Client's backup with DEFINE ASSOCIATION.
    How does Admin Schedule works or scheduled?

    Example: FULL database backup @ 5PM

    in ACTLOG I see:
    ANR2750I Starting scheduled command PROD_DB_BACKUP -" assuming this name was created for schedule"

    and then
    ANR2017I Administrator Admin001 issued command: RUN PROD_DB_BACKUP (SESSION: 1600554)

    and....
    ANR2017I Administrator Admin001 issued command: BACKUP DB DEVC=DBBACK_FILEDEV TYPE=full NUMSTREAMS=4 WAIT=yes (SESSION: 1600554)

    Noticed PROD_DB_BACKUP appear when I :
    Q SCRIPT F=D and Q SCHED * Type=admin f=d

    So I'm thinking, DEFINE ASSOC is not what I want because it requires domain parameter.
    My guess would be DEFINE SCHEDULE for admin command? admin ref 7.1.4 page 332

    so was it setup like this?
    DEF SCH PROD_DB_BACKUP Type=admin starttime=17:00 "the rest is default?"
    or
    RUN SCRIPT?
     
  2.  
  3. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,849
    Likes Received:
    363
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    See help define schedule - HELP is your friend.

    In newer TSM server versions, there will be 2 help entries: one for client and one for admin schedules.

    Define association is ONLY for client schedules.

    DB backups are defines under admin schedules. So, to define a DB backup schedule as an example:

    define schedule DB_backup type=admin cmd="backup db devclass=<DEVCLASS_Name> type=full numstreams=2 wait=<yes_or_no>" starttime=06:00 active=yes

    OR, with a script:

    define schedule DB_backup type=admin cmd="run BACKUP_SCRIPT_name" starttime=06:00 active=yes
     
  4. TaSMania

    TaSMania ADSM.ORG Member

    Joined:
    Nov 17, 2015
    Messages:
    52
    Likes Received:
    1
    I was already there. That's why I added Reference 7.1.4. page 332.
    Since you pointed me to where I was. I assumed I'm at the right spot.
    DEFINE SCH - is that just creating the sch or execute it.
    Hope I word my question correctly.

    for client backup.
    1. define sch - creating schedule
    2. define assoc - creating schedule to the node

    so for admin sch, don't I have to assoc the schedule to something, in this case not node.
    I'm thinking there's a run command I have to set up.
     
  5. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,849
    Likes Received:
    363
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    define association (see help define association) associates nodes to a client schedule.

    I repeat, there is NO DEFINE ASSOCIATION for admin schedules. If you want an admin schedule to run script, see my example or see help define schedule for admin.
     
  6. TaSMania

    TaSMania ADSM.ORG Member

    Joined:
    Nov 17, 2015
    Messages:
    52
    Likes Received:
    1
    Yes I know there's NO define association for admin sch.
    I think I understand it now. Just one command setup the the admin sched.
    Thank you much.
     

Share This Page