04-25-2014 03:31 AM
Hi
i am using Netbackup
when ever any weekly backup ran at its time , week 01 and week02 backups also ran
for example this week, week04 backup ran and with it week 01 and week 02 backups also ran
i have scheduled in calender properly in Calender > Recurring Week Days and then CHECKED 4th week in week04 schedule properties and checked 1ST Week in Week01 schedule
So whats the problem?
Solved! Go to Solution.
04-25-2014 04:13 AM
That actually looks OK apart from a couple of things:
1. week5 having no days set to actually run
2. seems very complex to me
Sounds like there may be some corruption that has crept in so you may need to re-create the schedules
As verything looks the same to me at first glance you really only need 3 schedules - a daily incremental (frequency based would be fine), a weekly full (calendar based) monthly full (calendar based)
It you must use 1st of month it makes it difficult - would be easier to use 1st Saturday of the month.
You could try running nbpemreq -updatepolicies first and also see what a predict gives you - but if they all keep running there is something wrong with the schedules
Do they all run for all clients?
04-25-2014 03:41 AM
Could we see bppllist policyname -U please
You may have retries allowed after runday and if you get failures they could all run .. but need to really see the output to analyse first
04-25-2014 03:44 AM
Post the policy configuration for us
# bppllist POLICYNAME -U
Update: Too late ....
04-25-2014 04:01 AM
C:\Program Files\VERITAS\NetBackup\bin\admincmd>
C:\Program Files\VERITAS\NetBackup\bin\admincmd>bppllist Lin_Laptop_User -U
------------------------------------------------------------
Policy Name: Lin_Laptop_User
Policy Type: Standard
Active: yes
Effective date: 03/20/2007 16:57:43
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: yes
Interval: 15
Policy Priority: 99999
Max Jobs/Policy: 5
Disaster Recovery: 0
Collect BMR info: no
Residence: (specific storage unit not required)
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: User_Backup
Data Classification: -
Residence is Storage Lifecycle Policy: no
Granular Restore Info: no
HW/OS/Client: Linux SuSE2.6 cccaudl001
Linux SuSE2.6 cccisdl002
Linux RedHat2.4 ccccrdl001
Linux SuSE2.6 cccisdl003
Linux RedHat2.4 cccinvl001
Linux SuSE2.6 ccctfil001
Linux SuSE2.6 cccisdl001
Linux SuSE2.6 cccopsl001
Linux RedHat2.4 cccconl009
Linux RedHat2.4 ccccrdl002
Linux SuSE2.6 ccctrdl001
Linux SuSE2.6 ccccmpl001
Linux SuSE2.6 cccisdl007
Linux SuSE2.6 cccaudl002
Linux SuSE2.6 cccaudl003
Linux RedHat2.4 ccchrdl001
Linux SuSE2.6 cccadml001
Linux SuSE2.6 cccconl008
Linux SuSE2.6 cccadml002
Linux SuSE2.6 ccchrdl003
Linux SuSE2.6 ccchrdl004
Linux SuSE2.6 ccchrdl005
Linux SuSE2.6 cccceol003
Linux SuSE2.6 cccpdsl002
Linux SuSE2.6 ccccmpl002
Linux SuSE2.6 cccisdl020
Linux SuSE2.6 cccprdl001
Linux SuSE2.6 cccprdl002
Linux SuSE2.6 cccconl002
Linux SuSE2.6 cccisdl015
Linux SuSE2.6 cccisdl014
Linux SuSE2.6 cccaudl000
Linux SuSE2.6 cccaudl012
Linux SuSE2.6 cccaudl013
Linux SuSE2.6 cccaudl009
Linux SuSE2.6 ccccadl004
Linux SuSE2.6 cccaudl010
Linux SuSE2.6 ccctest123
Include: /home
Schedule: FULL_MONTHLY
Type: Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
Number Copies: 1
Fail on Error: 0
Residence: USERS_MONTHLY
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Day 1 of month
EXCLUDE DATE 0 - 06/01/2013
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Sunday 09:00:00 --> Sunday 18:00:00
Monday 09:00:00 --> Monday 18:00:00
Tuesday 09:00:00 --> Tuesday 18:00:00
Wednesday 09:00:00 --> Wednesday 18:00:00
Thursday 09:00:00 --> Thursday 18:00:00
Friday 09:00:00 --> Friday 18:00:00
Saturday 09:00:00 --> Saturday 18:00:00
Schedule: USERS_WEEK1
Type: Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: USERS_WEEK1
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Friday, Week 1
EXCLUDE DATE 0 - 03/01/2013
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Friday 09:00:00 --> Friday 18:00:00
Schedule: USERS_WEEK2
Type: Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: USERS_WEEK2
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Friday, Week 2
EXCLUDE DATE 0 - 08/09/2013
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Friday 09:00:00 --> Friday 18:00:00
Schedule: USERS_WEEK3
Type: Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: USERS_WEEK3
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Friday, Week 3
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Friday 09:00:00 --> Friday 18:00:00
Schedule: USERS_WEEK4
Type: Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: USERS_WEEK4
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Friday, Week 4
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Friday 09:00:00 --> Friday 18:00:00
Schedule: USERS_WEEK5
Type: Full Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: USERS_WEEK5
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Allowed to retry after run day
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Friday 09:00:00 --> Friday 18:00:00
Schedule: MONDAY_INCRM
Type: Differential Incremental Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: USERS_MON
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Monday, Week 1
Monday, Week 2
Monday, Week 3
Monday, Week 4
Monday, Week 5
EXCLUDE DATE 0 - 08/20/2012
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Monday 09:00:00 --> Monday 18:00:00
Schedule: THURSDAY_INCRM
Type: Differential Incremental Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: USERS_THR
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Thursday, Week 1
Thursday, Week 2
Thursday, Week 3
Thursday, Week 4
Thursday, Week 5
EXCLUDE DATE 0 - 08/08/2013
EXCLUDE DATE 1 - 10/17/2013
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Thursday 09:00:00 --> Thursday 18:00:00
Schedule: TUESDAY_INCRM
Type: Differential Incremental Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: USERS_TUE
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Tuesday, Week 1
Tuesday, Week 2
Tuesday, Week 3
Tuesday, Week 4
Tuesday, Week 5
EXCLUDE DATE 0 - 08/21/2012
EXCLUDE DATE 1 - 10/15/2013
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Tuesday 09:00:00 --> Tuesday 18:00:00
Schedule: WEDNESDAY_INCRM
Type: Differential Incremental Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 0 (1 week)
Number Copies: 1
Fail on Error: 0
Residence: USERS_WED
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Calendar sched: Enabled
Wednesday, Week 1
Wednesday, Week 2
Wednesday, Week 3
Wednesday, Week 4
Wednesday, Week 5
EXCLUDE DATE 0 - 08/22/2012
EXCLUDE DATE 1 - 10/16/2013
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Wednesday 09:00:00 --> Wednesday 18:00:00
C:\Program Files\VERITAS\NetBackup\bin\admincmd>
04-25-2014 04:10 AM
You may have retries allowed after runday and if you get failures they could all run .. but need to really see the output to analyse first
i donot understand this sentence.
u mean to say if week04 backup will fail then other weekly backups will run?
04-25-2014 04:13 AM
That actually looks OK apart from a couple of things:
1. week5 having no days set to actually run
2. seems very complex to me
Sounds like there may be some corruption that has crept in so you may need to re-create the schedules
As verything looks the same to me at first glance you really only need 3 schedules - a daily incremental (frequency based would be fine), a weekly full (calendar based) monthly full (calendar based)
It you must use 1st of month it makes it difficult - would be easier to use 1st Saturday of the month.
You could try running nbpemreq -updatepolicies first and also see what a predict gives you - but if they all keep running there is something wrong with the schedules
Do they all run for all clients?
04-25-2014 04:15 AM
Ian - i mean that if one fails it can run the following week when there is an open window regardless of the date - and the normally scheduled ones could run too - happens if there are failures and retries after run day are allowed
04-25-2014 04:37 AM
1.ok i will set week5 date , as week5 we ran manually
2.u said
nly need 3 schedules - a daily incremental (frequency based would be fine), a weekly full (calendar based) monthly full (calendar based)
so we have already done like this, but daily incremental is also calnder based
nbpemreq -updatepolicies it gives output Corba Exception:TRANSIENT (what happens with this command)?
3.yes all clientsrun with week01 and week02
04-25-2014 04:43 AM
If the updatepolicies command fails with a corba error then you do have a problem as it indicates an issue somewhere with communications and so updates of the timers may not be happening
How long since your Master had a reboot? Well worth doing it regularly to keep processes cleaned up
04-25-2014 04:56 AM
If the updatepolicies command fails with a corba error then you do have a problem as it indicates an issue somewhere with communications and so updates of the timers may not be happening
so whats the solution of it? give me step which i will practicaly do
We have bpdown and bpup today but not rebooted th NB Server since long , i think one month
04-25-2014 06:03 AM
As a start i would reboot the Master Server and then try the nbpemreq command again to see if it is then happy
If so you can run it with the predict swicch to see if it then shows just one due to run tonight rather than more than one
Double check your anti virus for exclusions etc. but this may have just been a glitch unless it has always run all of the jobs at the same time?
04-28-2014 12:02 AM
Sorry for late answer,
our office was closed and two days holiday
i will reboot today and check again the nbpemreq command but what do u mean by this
If so you can run it with the predict swicch to see if it then shows just one due to run tonight rather than more than one
04-28-2014 02:01 AM
also when we manually ran the weekly jobs ,there is no issue, but when weekly jobs ran automatically this issue came that for example with wwek04 jobs week1 and week2 jobs also ran for each client
04-28-2014 10:38 PM
Please help me
04-29-2014 01:53 AM
Once you have done the reboot see if the nbpemreq -updatepolicies works
If so (and hopefully it does!) you can run using the predict to see if only one job is due to run on Friday:
nbpemreq -predict -date 05/03/2014 09:00:00
To see what it says is due to run on at that time and date