02-14-2016 09:17 PM
Hi All,
Could you please help me in answering the below query.
I have created a policy and the schedule type is calender and the window is opened for 24 hours for the whole week and the start time of the policy is 10AM . Eventhough start time of the policy is 10AM backup is triggering at 00:00. Is it due to backup window is opened for 24 hours
For another policy schedule type is calender and the window is opened for 17 hours from 10:00 AM to 3:00 PM for the whole week and the start time of the policy is 10AM . Eventhough start time of the policy is 10AM backup is triggering at 10 AM. In the first case why the backup is triggering at 00:00 eventhough scheduled at 10 AM.
Thanks in advance
Solved! Go to Solution.
02-16-2016 10:48 AM
02-14-2016 09:40 PM
I must be missing something. If backup window is open 24 hours then it means from 00:00 to 24:00.
Where do you see start time of 10:00?
Bear in mind that in calendar scheduling before and after midnight means two different days.
If backups are scheduled for every day, then after midnight means backup can be run again.
Are you aware of the fact that backup window is a 'start' window, not backup duration window?
So, a start window of 24 hours means the backup can start any time during the window.
Please show us your policy config for a better understanding:
bppllist <policy-name> -U
02-16-2016 02:29 AM
Hi Marianne,
Please find the output
Policy Name: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Policy Type: Standard
Active: yes
Effective date: 01/01/1970 01:00:00
Client Compress: no
Follow NFS Mounts: yes
Cross Mount Points: no
Collect TIR info: no
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: Backupserver-bup1-hcart-robot-tld-0
Volume Pool: ENIQ_STATS_Pool
Server Group: *ANY*
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
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: no
HW/OS/Client: Solaris Solaris_x86_1 xxxxxxxx
Include: NEW_STREAM
Filesystem_1
Filesystem_2
Filesystem_3
Schedule: Full_Backup
Type: Full Backup
Calendar sched: Enabled
Allowed to retry after run day
Included Dates-----------
Sunday, Week 1
Wednesday, Week 1
Friday, Week 1
Sunday, Week 2
Wednesday, Week 2
Friday, Week 2
Sunday, Week 3
Wednesday, Week 3
Friday, Week 3
Sunday, Week 4
Wednesday, Week 4
Friday, Week 4
Sunday, Week 5
Wednesday, Week 5
Friday, 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: 3 (1 month)
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:
Sunday 10:00:00 --> Monday 03:00:00
Monday 10:00:00 --> Tuesday 03:00:00
Tuesday 10:00:00 --> Wednesday 03:00:00
Wednesday 10:00:00 --> Thursday 03:00:00
Thursday 10:00:00 --> Friday 03:00:00
Friday 10:00:00 --> Saturday 03:00:00
Saturday 10:00:00 --> Sunday 03:00:00
02-16-2016 02:45 AM
So, the window is NOT opened for 24 hours for the whole week as per your opening post.
Calendar backups simply don't play well with windows crossing midnight as the 2 days in start and end times are 2 different days plus you have selected 'Allowed to retry after run day'.
Please help us understand :
a) why the backup window is open for so many hours?
b) when you are expecting backups to run - which days and when?
Why have you selected Sunday, Wednesday, Friday but open windows every day of the week?
If we have a clear understanding of your schedule requirements, we may be able to help you reconfigure the schedules.
02-16-2016 06:18 AM
Hi Marianne,
Please find my inputs.
For the policy I have posted the backupwindow is opened for 17 hours bu please see the output for another policy where the window is opened for 24 hours
Policy Name: xxxxxxxxxxxxxxxxxxxx
Policy Type: Standard
Active: yes
Effective date: 01/01/1970 01:00:00
Client Compress: no
Follow NFS Mounts: yes
Cross Mount Points: no
Collect TIR info: no
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: -bup1-hcart-robot-tld-0
Volume Pool: ENIQ_STATS_Pool
Server Group: *ANY*
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
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: no
HW/OS/Client: Solaris Solaris_x86_1
Include:
Schedule: Full_Backup
Type: Full Backup
Calendar sched: Enabled
Allowed to retry after run day
Included Dates-----------
Sunday, Week 1
Wednesday, Week 1
Friday, Week 1
Sunday, Week 2
Wednesday, Week 2
Friday, Week 2
Sunday, Week 3
Wednesday, Week 3
Friday, Week 3
Sunday, Week 4
Wednesday, Week 4
Friday, Week 4
Sunday, Week 5
Wednesday, Week 5
Friday, 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: 3 (1 month)
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:
Sunday 10:00:00 --> Monday 10:00:00
Monday 10:00:00 --> Tuesday 10:00:00
Tuesday 10:00:00 --> Wednesday 10:00:00
Wednesday 10:00:00 --> Thursday 10:00:00
Thursday 10:00:00 --> Friday 10:00:00
Friday 10:00:00 --> Saturday 10:00:00
Saturday 10:00:00 --> Sunday 10:00:00
a) why the backup window is open for so many hours?
Backup window is opened for many hours because we are taking raw luns backup which will take 1 day for the completion of backup. if the backup is not completed within the window it migh fail. Sometimes we are unable to predict whether backup will be completed within the window.
b) when you are expecting backups to run - which days and when?
Why have you selected Sunday, Wednesday, Friday but open windows every day of the week?
We are expecting the backup to run on sun, wed, fri but if if the backup is not completed on sun it will extend till monday and if the window is closed backup might fail.
Please let us know in case of any queries
02-16-2016 07:02 AM
simple one for to get backup on wed/fri/sun is select wed/fri/sun in calander and create backup window only for wed/fri/sun(10-10/10-3) and remove the backup window for other days, which might help your backup run only on these 3 days not on other days.
02-16-2016 07:06 AM
The "run window" is a "start opportunity window".
A backup job is not cancelled if it does not finish by the time the "run window" closes.
It is perfectly valid to have a "run window" of a few hours for a backup job that may run for many hours or days.
You only get a status 196 if the backup job is still "queued" and has not yet gone "active" by the time the "run window" closes.
02-16-2016 10:48 AM