cancel
Showing results for 
Search instead for 
Did you mean: 

Job did not run, but no error

TandyBrands
Level 4

Hey Folks,

Ok, got a new one here.  I have a policy defined called "Exch-TBEX02-DB".  Within this policy, I have three schedules defined.

Differential-Inc   - 2 Week retention (occurs nightly)

Full - 1 month Retention (Occurs weekly)

Full-Offsite - Infinity (retention) (Occurs end-of-month)  These get pulled and off-sited.

So the diffs run, the Full runs, but of hte three policies I have set up like this, two of them ran, the third did not.  No error, it's like it is not even scheduled (It is, btw to occur Midnight to 6 AM).  Now, on the date I have the FULL-OFFSITE occuring (this last one 10/219/11 for example), I have EXCLUDED that date as a run date in the FULL schedule (so not to conflict with FULL-OFFSITE)

Is there a log file I can look at or something?

Thanks,

James

1 ACCEPTED SOLUTION

Accepted Solutions

Mark_Solutions
Level 6
Partner Accredited Certified

Can i confirm that it is the Full off site one that did not?

29th October was a Saturday - your window is on a Sunday

I am thinking that you have a 7 day frequency for the Full Schedule that is an issue anyway - if it ran well over time or got run manually in the week it would not be ready - i would reduce this to 4 or 5 days, if it only has an open window once a week it will always be ready on that day.

View solution in original post

6 REPLIES 6

Mark_Solutions
Level 6
Partner Accredited Certified

Could you do the policy listing for the problem policy and one of the other please:

bppllist policyname -L

Just in case we can spot something

nbpemreq -predict and -due - date shows what is expected to run when but lets start with the full listing

Thanks

TandyBrands
Level 4

Policy Name:       Exch-TBEX02-DB
Options:           0x0
template:          FALSE
c_unused1:         ?
Names:             (none)
Policy Type:       MS-Exchange-Server (16)
Active:            yes
Effective date:    11/11/2009 11:40:12
Mult. Data Stream: no
Perform Snapshot Backup:   no
Snapshot Method:           (none)
Snapshot Method Arguments: (none)
Perform Offhost Backup:    no
Backup Copy:               0
Use Data Mover:            no
Data Mover Type:           2
Use Alternate Client:      no
Alternate Client Name:     (none)
Use Virtual Machine:      0
Hyper-V Server Name:     (none)
Enable Instant Recovery:   no
Policy Priority:   0
Max Jobs/Policy:   Unlimited
Disaster Recovery: 0
Collect BMR Info:  no
Keyword:           (none specified)
Data Classification:       -
Residence is Storage Lifecycle Policy:    no
Client Encrypt:    no
Checkpoint:        no
Residence:         tbbackup01-hcart3-robot-tld-0
Volume Pool:       NetBackup
Server Group:      *ANY*
Granular Restore Info:  no
Generation:      49
Client/HW/OS/Pri:  tbex02 PC-x64 Windows2008 1952796252 0 0 0 ?
Include:           Microsoft Information Store:\First Storage Group
Include:           Microsoft Information Store:\Second Storage Group
Include:           Microsoft Information Store:\Third Storage Group
Schedule:          Full-Offsite
  Type:            FULL SExchange (0)
  Calendar sched: Enabled
    SPECIFIC DATE 0 - 10/01/2011
    SPECIFIC DATE 1 - 10/29/2011
    SPECIFIC DATE 2 - 11/26/2011
    SPECIFIC DATE 3 - 12/31/2011
  Maximum MPX:     1
  Synthetic:       0
  PFI Recovery:    0
  Retention Level: 9 (infinity)
  u-wind/o/d:      0 0
  Incr Type:       DELTA (0)
  Alt Read Host:   (none defined)
  Max Frag Size:   0 MB
  Number Copies:   1
  Fail on Error:   0
  Residence:       (specific storage unit not required)
  Volume Pool:     Offsite-EXCH
  Server Group:    (same as specified for policy)
  Residence is Storage Lifecycle Policy:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  006:00:00   000:00:00  006:00:00 
   Monday      000:00:00  000:00:00
   Tuesday     000:00:00  000:00:00
   Wednesday   000:00:00  000:00:00
   Thursday    000:00:00  000:00:00
   Friday      000:00:00  000:00:00
   Saturday    000:00:00  000:00:00
Schedule:          Full
  Type:            FULL SExchange (0)
  Frequency:       7 day(s) (604800 seconds)
    EXCLUDE DATE 0 - 10/01/2011
    EXCLUDE DATE 1 - 10/29/2011
    EXCLUDE DATE 2 - 11/26/2011
    EXCLUDE DATE 3 - 12/31/2011
  Maximum MPX:     1
  Synthetic:       0
  PFI Recovery:    0
  Retention Level: 3 (1 month)
  u-wind/o/d:      0 0
  Incr Type:       DELTA (0)
  Alt Read Host:   (none defined)
  Max Frag Size:   0 MB
  Number Copies:   1
  Fail on Error:   0
  Residence:       (specific storage unit not required)
  Volume Pool:     (same as policy volume pool)
  Server Group:    (same as specified for policy)
  Residence is Storage Lifecycle Policy:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  006:00:00   000:00:00  006:00:00 
   Monday      000:00:00  000:00:00
   Tuesday     000:00:00  000:00:00
   Wednesday   000:00:00  000:00:00
   Thursday    000:00:00  000:00:00
   Friday      000:00:00  000:00:00
   Saturday    000:00:00  000:00:00
Schedule:          Differential-Inc
  Type:            INCR (1)
  Frequency:       1 day(s) (86400 seconds)
  Maximum MPX:     1
  Synthetic:       0
  PFI Recovery:    0
  Retention Level: 1 (2 weeks)
  u-wind/o/d:      0 0
  Incr Type:       DELTA (0)
  Alt Read Host:   (none defined)
  Max Frag Size:   0 MB
  Number Copies:   1
  Fail on Error:   0
  Residence:       (specific storage unit not required)
  Volume Pool:     (same as policy volume pool)
  Server Group:    (same as specified for policy)
  Residence is Storage Lifecycle Policy:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  000:00:00
   Monday      000:00:00  000:30:00   024:00:00  024:30:00 
   Tuesday     000:00:00  000:30:00   048:00:00  048:30:00 
   Wednesday   000:00:00  000:30:00   072:00:00  072:30:00 
   Thursday    000:00:00  000:30:00   096:00:00  096:30:00 
   Friday      000:00:00  000:30:00   120:00:00  120:30:00 
   Saturday    000:00:00  000:30:00   144:00:00  144:30:00 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

In addition to policy config as per Mark's request, please also post the following for the client name (or one of the clients) in the problematic policy:

bpimagelist -client <client-name> -policy <policy_name> -d 10/21/2011 -U

Mark_Solutions
Level 6
Partner Accredited Certified

Can i confirm that it is the Full off site one that did not?

29th October was a Saturday - your window is on a Sunday

I am thinking that you have a 7 day frequency for the Full Schedule that is an issue anyway - if it ran well over time or got run manually in the week it would not be ready - i would reduce this to 4 or 5 days, if it only has an open window once a week it will always be ready on that day.

TandyBrands
Level 4

 

C:\Program Files\Veritas\NetBackup\bin\admincmd>bpimagelist -client TBEX02 -policy Exch-TBEX02-DB -d 10/21/2011 -U
Backed Up         Expires       Files       KB  C  Sched Type   Policy
----------------  ---------- -------- --------  -  ------------ ------------
11/01/2011 00:00  11/14/2011        7  3910686  N  Differential Exch-TBEX02-DB
10/31/2011 00:00  11/13/2011        7  1181232  N  Differential Exch-TBEX02-DB
10/30/2011 00:00  11/29/2011       16 607305176  N  Full Backup  Exch-TBEX02-DB
10/29/2011 00:00  11/11/2011        7  3137427  N  Differential Exch-TBEX02-DB
10/28/2011 00:00  11/10/2011        7  3565536  N  Differential Exch-TBEX02-DB
10/27/2011 00:00  11/09/2011        7  3519450  N  Differential Exch-TBEX02-DB
10/26/2011 00:00  11/08/2011        7  3395522  N  Differential Exch-TBEX02-DB
10/25/2011 00:00  11/07/2011        7  3605477  N  Differential Exch-TBEX02-DB
10/24/2011 00:03  11/06/2011        7   567744  N  Differential Exch-TBEX02-DB
10/23/2011 00:00  11/22/2011       16 604333402  N  Full Backup  Exch-TBEX02-DB
10/22/2011 00:09  11/05/2011        7  3527638  N  Differential Exch-TBEX02-DB
10/21/2011 00:00  11/04/2011        7  2676543  N  Differential Exch-TBEX02-DB

Mark, You are correct.  So my problem was my Policy scheduled on a Saturday, but the time window was on Sunday.  As for the rest of your suggestion, I don't think I understand your suggestion.  The FULL is a 7-day frequency, I include an exclusion date at the end ofhte month when the offsite should run so there is no overlap. I will need to re-work my window to make sure it runs when I want it to. Thanks! 

Mark_Solutions
Level 6
Partner Accredited Certified
Using a 7 day frequency actually cuts it fine if say it was queued until 5.50am then 7 days after that doesn't leave much room for error Also, if it failed and you ran it manually on Monday morning it may not be ready to run again by Saturday By making it 4 days, it can still only run on Saturday when the window is open but it will always be ready Hope this explains it better