01-20-2016 03:55 AM
Jobs run twice on the same scheduled;
Could you please help me solve this problem?
Solved! Go to Solution.
01-20-2016 07:46 AM
Hi Heron,
Could you confirm that you are running the schedule "Full_Diario" only on Sunday to friday not on saturday.
If its so, then you should remove selection on saturday on the Calendar.( select only sunday to friday)
As you have selected the saturday in calendar for "Full_Diario" schedule it will look for the open window for that day, so the backup will start run before 9.00 as there was open window selected on saturday from 00:00 hrs to 9:00 as per calendar schedule.
This is the reason you might have two backup on friday night & saturday morning since the friday backup completed with in backup window and there was open window for saturday schedule, but you might thought you have selected backup Daily Windows only for friday and not for saturday,
01-20-2016 04:04 AM
Please show us the policy config.
On the master, run this command from cmd:
bppllist <policy-name> -U
Please copy the text output and post here.
01-20-2016 04:15 AM
Hi Marianne,
thanks for answering.
I have many clients in this policy. Two schedules of daily backup, one goes to the backup tape and the other in a SLP (disk, tape after)
Policy Name: C_LNX_DB_LOGICO
Policy Type: Standard
Active: yes
Effective date: 02/03/1991 17:26:47
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: 60
Policy Priority: 120
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: SLP_LNX_DUPLICA_P_DB
Volume Pool: Pool_FS_BD
Server Group: PRODEMGE
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: yes
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 RedHat2.6 dl12061_mysql_fhemig
Linux RedHat2.6 it11338_ses_mysql
Linux RedHat2.6.18 dl16093_alertdbadw01
Linux RedHat2.6.18 dl16104_alertdbadw02
Linux RedHat2.6.18 dl16421_alertdbehr01
Linux RedHat2.6.18 dl16437_alertdbehr02
Linux RedHat2.6.18 vm16380_alerttapp01
Linux RedHat2.6.18 vm16373_alertppdb01
Linux RedHat2.6.18 vm16396_alerteleapp01
Linux RedHat2.6.18 vm16407_alertsupapp01
Linux RedHat2.6.18 vm19016_cedecdb01
Linux RedHat2.6.18 vm_bd_postgres_seej
Linux RedHat2.6.18 vm_bd_mysql_seej
Linux RedHat2.6.18 vm02aps01b
Linux Debian2.6.18 vm_sysgalapl
Linux RedHat2.6.18 vm09aps01b
Linux RedHat2.6 sn09744-sigafbd
Linux RedHat2.6.18 sn03502_mysqlseep01
Linux RedHat2.6.18 vm15671_mysqlfjp01
Linux RedHat2.6 vm_pgsqlp01_ima
Linux Debian2.6.18 vm19aps01b
Linux RedHat2.6.18 vm05aps03b
Linux RedHat2.6.18 vm05aps09b
Linux RedHat2.6.18 vm05aps04b
Linux RedHat2.6.18 vm02aps02b
Linux RedHat2.6.18 vm05aps02b
Linux SuSE2.6.16 sn07378_oraipemsgi
Linux RedHat2.6.18 vm10aps02b
Linux RedHat2.6.18 vm10aps01b
Linux Debian2.6.18 vm_galbanco
Linux RedHat2.6.18 vm22aps01b
Linux RedHat2.6.18 vm22aps03b
Linux RedHat2.6.18 vm05aps07b
Linux RedHat2.6.18 vm07aps03b
Linux RedHat2.6.18 vm21aps02b
Linux RedHat2.6.18 vm04aps02b
Linux RedHat2.6.18 vm04aps01b
Linux RedHat2.6.18 vm05aps08b
Linux RedHat2.6.18 vm05aps01b
Linux Debian2.6.18 vm06aps03b
Linux RedHat2.6.18 vm06aps05b
Linux RedHat2.6.18 vm06aps06b
Linux RedHat2.6.18 vm22aps02b
Linux RedHat2.6.18 vm20aps01b
Linux RedHat2.6.18 vm_adm_fhemig
Linux RedHat2.6.18 vm07aps01b
Linux RedHat2.6.18 vm17aps01b
Linux RedHat2.6.18 gmgpidevb
Linux RedHat2.6.18 gmgportaldevb
Linux RedHat2.6.18 vmsaphcm-devb
Linux RedHat2.6.18 gmgsolmandevb
Linux RedHat2.6.18 gmgsolmanprdb
Linux RedHat2.6.18 gmgerecfedevb
Linux RedHat2.6.18 gmgbwdevb
Linux RedHat2.6.18 vmcrm-dev_gmgcrmdev
Linux RedHat2.6.18 vm10aps03b
Linux RedHat2.6.18 vm16aps01b
Linux RedHat2.6.18 vm_webuemg
Include: ALL_LOCAL_DRIVES
Schedule: Full
Type: Full Backup
Calendar sched: Enabled
Included Dates-----------
Sunday, Week 1
Monday, Week 1
Tuesday, Week 1
Wednesday, Week 1
Thursday, Week 1
Friday, Week 1
Saturday, Week 1
Sunday, Week 2
Monday, Week 2
Tuesday, Week 2
Wednesday, Week 2
Thursday, Week 2
Friday, Week 2
Saturday, Week 2
Sunday, Week 3
Monday, Week 3
Tuesday, Week 3
Wednesday, Week 3
Thursday, Week 3
Friday, Week 3
Saturday, Week 3
Sunday, Week 4
Monday, Week 4
Tuesday, Week 4
Wednesday, Week 4
Thursday, Week 4
Friday, Week 4
Saturday, Week 4
Sunday, Week 5
Monday, Week 5
Tuesday, Week 5
Wednesday, Week 5
Thursday, Week 5
Friday, Week 5
Saturday, Week 5
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: 10 (45 days)
Number Copies: 1
Fail on Error: 0
Residence: Midias_Server_Lnx
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Saturday 22:00:00 --> Sunday 21:50:00
Schedule: Full_Diario
Type: Full Backup
Calendar sched: Enabled
Included Dates-----------
Sunday, Week 1
Monday, Week 1
Tuesday, Week 1
Wednesday, Week 1
Thursday, Week 1
Friday, Week 1
Saturday, Week 1
Sunday, Week 2
Monday, Week 2
Tuesday, Week 2
Wednesday, Week 2
Thursday, Week 2
Friday, Week 2
Saturday, Week 2
Sunday, Week 3
Monday, Week 3
Tuesday, Week 3
Wednesday, Week 3
Thursday, Week 3
Friday, Week 3
Saturday, Week 3
Sunday, Week 4
Monday, Week 4
Tuesday, Week 4
Wednesday, Week 4
Thursday, Week 4
Friday, Week 4
Saturday, Week 4
Sunday, Week 5
Monday, Week 5
Tuesday, Week 5
Wednesday, Week 5
Thursday, Week 5
Friday, Week 5
Saturday, Week 5
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: (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 22:00:00 --> Monday 09:00:00
Monday 22:00:00 --> Tuesday 09:00:00
Tuesday 22:00:00 --> Wednesday 09:00:00
Wednesday 22:00:00 --> Thursday 09:00:00
Thursday 22:00:00 --> Friday 09:00:00
Friday 22:00:00 --> Saturday 09:00:00
01-20-2016 04:26 AM
see the active monitor,
selected jobs are in the same window;
01-20-2016 04:37 AM
Which Schedule ran twice? And When?
You have 2 schedules in this policy :
Both schedules are Calendar based that cross midnight.
There used to be warnings in NBU Admin Guide (have not checked recent versions) about Calendar backups that cross midnight and Rundays selected for both days (before and after midnight). This would cause the backup to run before midnight and after midnight again.
Not sure if this is still the same in NBU 7.7.
If you tell us which schedule and when, it will help to troubleshoot.
Also tell us if this was a 'once off' or every day?
01-20-2016 05:02 AM
I note that is run jobs up in duplicate in the same window/schedule.
Usually it happened between Friday and Saturday.
see the Active Monitor figure in the post above. Sorry for the default setting Portuguese in Brazil.
01-20-2016 05:21 AM
Apologies - you posted the screenshot while I was typing up the post above.
Yes - it seems that the Calendar schedules crossing midnight are running before midnight and again after midnight because in reality the backups run on different days.
I am 'old school' and prefer to use Frequency schedules for Daily and Weekly backups.
I only ever use Calendar for schedules such as Monthly or Yearly that is difficult/impossible to schedule with Frequency.
One possible solution might be to change backup windows to either before or after midnight.
Hopefully other Calendar users have better advice on how to fix this.
01-20-2016 07:46 AM
Hi Heron,
Could you confirm that you are running the schedule "Full_Diario" only on Sunday to friday not on saturday.
If its so, then you should remove selection on saturday on the Calendar.( select only sunday to friday)
As you have selected the saturday in calendar for "Full_Diario" schedule it will look for the open window for that day, so the backup will start run before 9.00 as there was open window selected on saturday from 00:00 hrs to 9:00 as per calendar schedule.
This is the reason you might have two backup on friday night & saturday morning since the friday backup completed with in backup window and there was open window for saturday schedule, but you might thought you have selected backup Daily Windows only for friday and not for saturday,
01-21-2016 05:16 AM
Hi Sankar_28,
Thank you tip, I never thought it !!!
I made the settings you specified, but now I ask you:
Why not place the problems on other days of the week ???
Why only from Friday to Saturday ???
01-21-2016 05:35 AM
Hi Sankar_28,
Thank you tip, I never thought it !!!
I made the settings you specified, but now I ask you:
Why not place the problems on other days of the week ???
Why only from Friday to Saturday ???
01-21-2016 05:52 AM
Hi,
As per my observation the calendar schedule will look for start time of open window each day which is 22:00 for the days from sunay to friday, but for saturday if the calendar schedule looks the open window there was open window present on 00:00 to 09:00 hours.
so for saturday the backup start time of open window will be consider as 00:00 hours as open window present for that day is from 00:00 to 09:00 hours, as there was no start time as 22:00 as like other days.
Kindly let me know if its works for this week.
01-28-2016 07:04 AM
Ok!! everything working!!
thank you.