cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Triggered a frequency based backup for one client out of its window after this getting 196 error

I manually triggered a frequency based backup for one client out of its window after this I'm getting 196 client backup was not attempted because backup window closed error everyday.

 

How shall i fix this?

 

 

 

3 Replies
Highlighted

Re: Triggered a frequency based backup for one client out of its window after this getting 196 error

Starting a frequency backup will disturb backup start-time. If the frequency is one a day, then the scheduler will check for the last successful backup. If enough time has not elapsed (24 hours), then the backup will not be started. Only when 24 hours has passed will the backup be submitted - if the backup window is still open. 
For this reason we shorten the frequency to be slightly bigger than the backup window. 
If the window is 8 hours for example, we change the backup window to +- 12 hours. The backup will not kick off outside backup window, but will then be submitted as soon as the backup window opens.
Please see David Chapa's excellent article about Frequency scheduling: 
NetBackup Frequency Based Scheduling

Please show us the policy (bppllist <policy-name> -U) and last successful backup for the client (bpimagelist -hoursago 72 -client <name>). Adjust hoursago to match include the start time of the backup.

Please also open Job Details for a status 196 failure - you will see that the job was queued for a reason.
Please copy the text and post here?

Highlighted

Re: Triggered a frequency based backup for one client out of its window after this getting 196 error

Thanks for sharing the article on Frequency based scheduling

The backups started to run fine as per schedule now, i believe its because i triggered the backup before the backup window closes and then it calculated 12hours from last successful backup so it fall in the actual backup window which runs in the evening.

 

[root@NBUmaster ~]# bppllist Linux_Servers_OTA -U
------------------------------------------------------------

Policy Name:       Linux_Servers_OTA

  Policy Type:         Standard
  Active:              yes
  Effective date:      08/09/2012 10:57:21
  Client Compress:     no
  Follow NFS Mounts:   no
  Cross Mount Points:  no
  Collect TIR info:    yes
  Block Incremental:   no
  Mult. Data Streams:  yes
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           stu_dedup_appliance1
  Volume Pool:         NetBackup
  Server Group:        *NONE*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      0 seconds
  ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
  Use Accelerator:  no
  HW/OS/Client:  Linux-IA64    RedHat2.6     hq03092
                 Linux-IA64    RedHat2.6     hq03093
                 Linux-IA64    RedHat2.6     hq03094
                 Linux-IA64    RedHat2.6     hq03095
                 Linux-IA64    RedHat2.6     hq03096

  Include:  ALL_LOCAL_DRIVES

  Schedule:              MonthlyBackup
    Type:                Full Backup
    Frequency:           every 26 days
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 week)
    Number Copies:       1
    Fail on Error:       0
    Residence:           slp_files_dc1_monthly
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         1
    Daily Windows:
          Saturday   18:00:00  -->  Sunday     16:00:00

  Schedule:              WeeklyBackup
    Type:                Cumulative Incremental Backup
    Frequency:           every 4 days
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    Synthetic:           0
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 week)
    Number Copies:       1
    Fail on Error:       0
    Residence:           slp_files_dc1_weekly
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         1
    Daily Windows:
          Saturday   18:00:00  -->  Sunday     16:00:00

  Schedule:              DailyBackup
    Type:                Differential Incremental Backup
    Frequency:           every 12 hours
     Excluded Dates----------
        No specific exclude dates entered
        No exclude days of week entered
    PFI Recovery:        0
    Maximum MPX:         1
    Retention Level:     0 (1 week)
    Number Copies:       1
    Fail on Error:       0
    Residence:           slp_files_dc1_daily
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         1
    Daily Windows:
          Sunday     18:00:00  -->  Monday     06:00:00
          Monday     18:00:00  -->  Tuesday    06:00:00
          Tuesday    18:00:00  -->  Wednesday  06:00:00
          Wednesday  18:00:00  -->  Thursday   06:00:00
          Thursday   18:00:00  -->  Friday     06:00:00
          Friday     18:00:00  -->  Saturday   06:00:00
[root@NBUmaster ~]#

Highlighted

Re: Triggered a frequency based backup for one client out of its window after this getting 196 error

The recommendation is to make the frequency slightly bigger than the backup window.

So, for Daily backup window of 12 hours, I would make the frequency 13 hours.