Incremental scheduls not kicking in with TIR enabled/synthetic schedules

[Spartacus81]

Friends,

Policy

Daily_incremental

Weekly_Full (synthetic)

all of my incrementals on other policies are working but the synthetic. any suggestions would be appreciated?

[Andy_Welburn]

Has this ever worked or just started failing?

In the first instance, can we see how this policy is set up:

bppllist POLICY_NAME -U

[Spartacus81]

as far as i know it never worked. here is the policy i created as a test - manual full ran as expected but no incremental?

E:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist.exe xDCG -U
------------------------------------------------------------

Policy Name:       xDCG

  Policy Type:         MS-Windows
  Active:              yes
  Effective date:      12/16/2013 10:16:33
  Backup network drvs: no
  Collect TIR info:    yes, with move detection
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          yes
       Interval:       15
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           diskstage-basic1
  Volume Pool:         Daily
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows2008   sukcw-pwl-bak01

  Include:  C:\Temp\DCG-Temp

  Schedule:              Manual_Full
    Type:                Full Backup
    Frequency:           every 7 days
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (6 days)
    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
    Schedule indexing:     0
    Daily Windows:
          Monday     10:30:00  -->  Monday     11:30:00

  Schedule:              Weekly_Synthetic
    Type:                Full Backup
    Frequency:           every 7 days
    Maximum MPX:         1
    Synthetic:           1
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     1 (6 days)
    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
    Schedule indexing:     0
    Daily Windows:
          Monday     13:00:00  -->  Monday     14:00:00

  Schedule:              Daily_Incremental
    Type:                Differential Incremental Backup
    Frequency:           every 1 hour
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     0 (2 days)
    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
    Schedule indexing:     0
    Daily Windows:
          Monday     11:00:00  -->  Monday     13:10:00

E:\Program Files\Veritas\NetBackup\bin\admincmd>

[Andy_Welburn · Accepted solution]

Just set-up & ran my own test policy - thought I'd found an issue but it was 'user error' (apparently if your window is set to open/close on a Sunday it won't run on a Monday!! ).

Once that 'error' was rectified my incremental ran as expected & would expect the synthetic to also (we *do* actually run synthetics on a weekly basis).

Does the incremental appear in the output of nbpemreq?

If syntax is the same (still running an unsupported version here):

nbpemreq -predict -date 12/24/2013 -due

(use nbpemreq -updatepolicies following any policy changes - esp. for immediate tests - if that's still a valid command ;) )

[Spartacus81]

thanks Andy... have tested few backups and it was a user error. mis configuration of frequency/calender plus my customer wanted to run synthetic using full as synthetic plus cumulative as synthetic too. i have gone back to basics and tested full, inc and synth and all ran and worked fine. yes that command syntex is still good. ;) i will mark your post as a solution to give you some points. ;)