Backup policy firing Multiple time

[shans]

Dear All

we are facing an problem in our enironment . We are having totally 900+ policy . Some 10 policies are firing repeatedly within  the backup windows .sue to this our tape utilization goes high .

For example we can say a single policy is firing more than 25 times with in the backup windows . Can any one please help me on this .

Master server : Hp Unix 11.23

Netbackup Version : 6.5.4

Policy Details

Policy Type:         Standard
  Active:              no
  Effective date:      12/01/2009 15:28:05
  Client Compress:     no
  Follow NFS Mounts:   no
  Cross Mount Points:  no
  Collect TIR info:    yes, with move detection
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    yes
  Residence:           clonesvr_stu_NEWDISK
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       Gold
  Residence is Storage Lifecycle Policy:    no

Granular Restore Info:  no
  HW/OS/Client:  HP9000-800    HP-UX11.23    
 
  Schedule:          4_PM
    Type:            Differential Incremental Backup
    Frequency:       every 7 days
    Maximum MPX:     15
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 12 (15 years)
    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:
          Sunday     16:00:00  -->  Sunday     17:00:00
          Monday     16:00:00  -->  Monday     17:00:00
          Tuesday    16:00:00  -->  Tuesday    17:00:00
          Wednesday  16:00:00  -->  Wednesday  17:00:00
          Thursday   16:00:00  -->  Thursday   17:00:00
          Friday     16:00:00  -->  Friday     17:00:00
          Saturday   16:00:00  -->  Saturday   17:00:00

Waiting for your reply

[Venkatesh_K]

Hi,

is schedule Calander based or frequency based ?
are all clints affected under same policy or diffrent policy ?
use the command nbpemreq to determine what jobs are due in next hours.
you can refer http://seer.entsupport.symantec.com/docs/279299.htm for commands on NB 6.0

nbpemreq (1M)
NAME
nbpemreq – NetBackup Policy Execution Manager Requisition, schedules jobs when jobs
are due.
SYNOPSIS
/usr/openv/netbackup/bin/admincmd/nbpemreq -predict -date
mm/dd/yyyy HH:MM:SS
/usr/openv/netbackup/bin/admincmd/nbpemreq -predict -dateu
unixtime
/usr/openv/netbackup/bin/admincmd/nbpemreq -updatepolicies
DESCRIPTION
The nbpemreq command enables a user to determine which jobs are coming due in the
near future, and to read in all policy updates that have been entered and are in a pending
state.
OPTIONS
-predict -date mm/dd/yyyy HH:MM:SS
This option provides feedback by showing what jobs are scheduled to run
in the near future. The -date command specifies the time more accurately.
-predict -dateu unixtime
This option provides feedback by showing what jobs are scheduled to run
in the near future. The -dateu command specifies the time in UNIX time
(seconds).
-updatepolicies
This option tells the NetBackup policy execution manager to read in all
policy updates that are pending.

[shans]

Hi Venkatesh

Thanks for your mail . Its frquency based schedule .All the clients are covered under different policy .I have also tried nbpemreq -updatepolicy as suggested by symantec but not helpfull .

Note : Inside  a single policy we have defined 8 schedules with 3 hours frequency

[Venkatesh_K]

Hi,

Use nbpemreq with -predict option and determine what are the backups that are due in next 24hrs may be. and check if the backup of the clients are listed repetedly with in 24hrs.
 
you can also try creating new backup policy with same properties (COPY to New policy) and one with diffrent properties (CREATE new policy ) for any one client that is having problem and wait for next scheduled backup to run and check if you are still experiencing the same problem.

Im just wondering why do you have 8 schedules with 3 hrs frequency ???

[shans]

Hi Venky

Tried creating an new policy by copy to new & policy Wizard .But nothing helpfull .

We are taking backup of the data Base Archives . So we have 8 schedules with one full backup & Remaining Incremental backup .

Regards

Sundar

[Venkatesh_K]

Are these the scheduled backups or the User backup (RMAN backups ), ?

if they are scheduled than wait for the next schedule backup to run, as you said its 3hrs frequency, once you have the new policy created run

/usr/openv/netbackup/bin/admincmd/nbpemreq -updatepolicies.


what does -predict option tell does it show many babackups due for same cliend and does same number of backups run with in next given time in command

[stu52]

The policy listed in your original post is not active, please give us a list of the active policy or policies with the problem.

Also, you said:  "Note : Inside  a single policy we have defined 8 schedules with 3 hours frequency"

depending on the backup window for each schedule, it's possible to have a schedule run multiple times.  For example, if you have the following schedule and a 3 hr frequency, it's possible to run more than once:

Daily Windows:
          Sunday     16:00:00  -->  Sunday     23:00:00

here the backup window is 7 hours, with a 3 hour frequency it is possible for the job to run at the following times:  16:00, 19:00 & 22:00.

Since you have shown us an inactive policy as an example, I have no way of knowing if you are having that problem or not.  The policy you listed has a frequency of 7 days and, yet, it has a daily schedule for each day of the week with a one-hour window....this schedule will only run once a week!  If you want it to run every day, then you should set it for a frequency of 1 day.

[shans]

Hi

Please find the active policy info .

  Policy Type:         Standard
  Active:              yes
  Effective date:      08/16/2008 21:00:00
  Client Compress:     no
  Follow NFS Mounts:   no
  Cross Mount Points:  no
  Collect TIR info:    no
  Block Incremental:   no
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          yes
       Interval:       10
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           clonesvr_stu_NEWDISK
  Volume Pool:         Unix_DR_Pool
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no

Granular Restore Info:  no
  HW/OS/Client:  HP-UX-IA64    HP-UX11.23   

  Include: 
           

  Schedule:          10_PM
    Type:            Full Backup
    Frequency:       every 3 hours
    Maximum MPX:     32
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 10 (7 years) 10 (7 years)
    Number Copies:   2
    Fail on Error:   1 1
    Residence:       clonesvr_stu_ESL clonesvr_stu_ESL
    Volume Pool:     TCS_Chennai_Daily TCS_Thane_Daily
    Server Group:    *ANY* *ANY*
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     22:00:00  -->  Sunday     23:00:00
          Monday     22:00:00  -->  Monday     23:00:00
          Tuesday    22:00:00  -->  Tuesday    23:00:00
          Wednesday  22:00:00  -->  Wednesday  23:00:00
          Thursday   22:00:00  -->  Thursday   23:00:00
          Friday     22:00:00  -->  Friday     23:00:00
          Saturday   22:00:00  -->  Saturday   23:00:00

  Schedule:          1_PM
    Type:            Differential Incremental Backup
    Frequency:       every 3 hours
    Maximum MPX:     32
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 5 (3 months) 5 (3 months)
    Number Copies:   2
    Fail on Error:   0 0
    Residence:       clonesvr_stu_ESL clonesvr_stu_ESL
    Volume Pool:     TCS_Thane_Daily TCS_Chennai_Daily
    Server Group:    *ANY* *ANY*
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     13:00:00  -->  Sunday     13:30:00
          Monday     13:00:00  -->  Monday     13:30:00
          Tuesday    13:00:00  -->  Tuesday    13:30:00
          Wednesday  13:00:00  -->  Wednesday  13:30:00
          Thursday   13:00:00  -->  Thursday   13:30:00
          Friday     13:00:00  -->  Friday     13:30:00
          Saturday   13:00:00  -->  Saturday   13:30:00

  Schedule:          4_PM
    Type:            Differential Incremental Backup
    Frequency:       every 3 hours
    Maximum MPX:     32
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 5 (3 months) 5 (3 months)
    Number Copies:   2
    Fail on Error:   1 1
    Residence:       clonesvr_stu_ESL clonesvr_stu_ESL
    Volume Pool:     TCS_Thane_Daily TCS_Chennai_Daily
    Server Group:    *ANY* *ANY*
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     16:00:00  -->  Sunday     17:00:00
          Monday     16:00:00  -->  Monday     17:00:00
          Tuesday    16:00:00  -->  Tuesday    17:00:00
          Wednesday  16:00:00  -->  Wednesday  17:00:00
          Thursday   16:00:00  -->  Thursday   17:00:00
          Friday     16:00:00  -->  Friday     17:00:00
          Saturday   16:00:00  -->  Saturday   17:00:00

  Schedule:          7_PM
    Type:            Differential Incremental Backup
    Frequency:       every 3 hours
    Maximum MPX:     32
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 5 (3 months) 5 (3 months)
    Number Copies:   2
    Fail on Error:   0 0
    Residence:       clonesvr_stu_ESL clonesvr_stu_ESL
    Volume Pool:     TCS_Thane_Daily TCS_Chennai_Daily
    Server Group:    *ANY* *ANY*
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     19:00:00  -->  Sunday     20:00:00
          Monday     19:00:00  -->  Monday     20:00:00
          Tuesday    19:00:00  -->  Tuesday    20:00:00
          Wednesday  19:00:00  -->  Wednesday  20:00:00
          Thursday   19:00:00  -->  Thursday   20:00:00
          Friday     19:00:00  -->  Friday     20:00:00
          Saturday   19:00:00  -->  Saturday   20:00:00

Thanks & Regards

Sundar

[Marianne · Accepted solution]

Remove client STREAMS* files under /usr/openv/netbackup/db/images/<client-name> before next full backup is due.  I've had similar experience where cleanup of STREAMS files file force them to be recreated when next schedule was due and solved the problem. If you delete them prior to Inc backup, your backups will be full.