This discussion is archived
5 Replies Latest reply: Feb 6, 2013 4:47 PM by user228125 RSS

Schduled job not running

user228125 Newbie
Currently Being Moderated
Hi there,

We're new to OSB but have successfully created datasets and can run adhoc jobs on-demand successfully.
The next step was to schedule these jobs and we've created a scheduled job with a daily trigger. Trouble is, OSB isn't running the job at all.
And there's no mention of it on the Home page as either a successful or failed job. Its almost as if the schedule is invisible to OSB..

We're read the docs and can't find anything we're missing, but clearly something isn't working.

Any pointers would be most appreciated!

Thanks
  • 1. Re: Schduled job not running
    rdoogan Journeyer
    Currently Being Moderated
    What OS are you running?

    Post the output of "obtool lssched -l" and "obtool lsj"

    Thanks

    Rich
  • 2. Re: Schduled job not running
    user228125 Newbie
    Currently Being Moderated
    We're running Solaris 10 Update 10 (SPARC). OSB 10.4.0.2.0

    # ./obtool lssched -l
    DUPLICATION_SCAN:
    Type: duplication scan
    State: enabled
    Location: Changer
    Priority: 100
    UUID: 62236aa8-511d-1030-92e5-d036966cd519
    Trigger 1:
    Day/date: daily
    At: 07:05
    KKVolDupSch:
    Type: duplication scan
    State: enabled
    Location: Changer
    Priority: 100
    Comment: KK Volume Duplication Schedule
    UUID: 2a555a76-4d05-1030-92e5-d036966cd519
    Trigger 1:
    Day/date: daily
    At: 13:40
    OSB-CATALOG-SCHED:
    Type: backup
    State: enabled
    Dataset: OSB-CATALOG-DS
    Priority: 50
    Encryption: no
    Comment: OSB catalog backup schedule
    UUID: 4992a584-4223-1030-a6ee-c98e22e97dfc
    Trigger 1:
    Day/date: (none)
    At: 00:00
    Backup level: full
    Media family: OSB-CATALOG-MF
    OSB-DAILY-AM:
    Type: backup
    State: enabled
    Dataset: database/aclys10_fcrepla.ds
    Priority: 100
    Encryption: no
    UUID: e7eead18-51be-1030-92e5-d036966cd519
    Trigger 1:
    Day/date: daily
    At: 05:00
    Backup level: full
    Media family: OSB-DAILY-AM
    VAULTING_SCAN:
    Type: vaulting scan
    State: enabled
    Priority: 100
    UUID: d031bf3c-511c-1030-92e5-d036966cd519
    Trigger 1:
    Day/date: daily
    At: 07:00
    Trigger 2:
    Day/date: daily
    At: 20:00


    # ./obtool lsj
    Job ID Sched time Contents State
    ---------------- ----------- ------------------------------ ---------------------------------------
    19 02/07.13:40 volume duplication scan future work
    20 02/07.20:00 volume vaulting scan future work
    21 02/07.08:31 dataset database/aclys10_fcrepla.ds ready to run
  • 3. Re: Schduled job not running
    rdoogan Journeyer
    Currently Being Moderated
    So your job is "ready to run", so it's being held. An "obtool lsj -l" on it would maybe tell you why it is waiting.

    What is your backup window set to "obtool lsbw"

    Since your backup job is scheduled for 5am your backup window might need to be adjusted. Personally I have mine set to a 24 hour period as I always want my backups to run.

    Thanks

    Rich
  • 4. Re: Schduled job not running
    user228125 Newbie
    Currently Being Moderated
    Hi Rich

    Thanks very much for your help with this. We extended the window and the job started immediately.

    I think we might have actually had two issues: one: the backup window expiring for the 8:31 job, and problem two, in the Trigger for the schedule we hadn't set the "Expire after" option.
    We actually had the same job scheduled for 5am when the backup windows was actually valid, but it didn't run. However when we set the "Expire after" to "10 years", this second attempt at 08:31 ran (after also extending the backup window).

    We'll give it another go to be sure, but it looks good. TYVM!
  • 5. Re: Schduled job not running
    user228125 Newbie
    Currently Being Moderated
    All works beautifully second time around. Thanks again.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points