Re: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included.
Title: Message retry after runday means "anytime after" the defined runday...not just the next day. so when you create a new policy, or add a client to an existing policy, the first time tha backup runs, it hits all schedules to see which takes precidence.if your monthly/quarterly exists, then it is probably the highest priority, unless you've got a yearly, so it tries to run..you wouldn't expect it to, since you configured it for the last of the month, but since "allow tries after run day" is selected, it assumes today is after run day, since there is no existsing image for this schedule in the last month/quarter, or whatever. I think this is "by design", rather than a bug. Paul -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mansell, RichardSent: June 12, 2006 6:23 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included. Hi Bob We had a similar problem with our quarterly backup. It should only run 4 times a year but tried to run instead of the weekly backup for any new servers added to a policy. Removing 'Allowed to retry after run day' seemed to cure the problem. Regards Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob StumpSent: Tuesday, 13 June 2006 10:02 amTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included. I have years of experience with frequency based scheduling but I have always shied away from calendar based. Today I made my first attempt and I cannot see where I made a mistake. Please review this and help me if you can. Thanks. ...**This electronic email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. The views expressed in this message are those of the individual sender and may not necessarily reflect the views of the ChristchurchCity Council.If you are not the correct recipient of this email please advise thesender and delete.Christchurch City Councilhttp://www.ccc.govt.nz** La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included.
What version of NBU ... the early Calendar based jobs (4.5ish) had some bugs with the logic. As far as having Calendar based schedules crossing midnight you should not do that. I don't think its goofy, it just defats the purpose of Calendar based Schedules. You told NBU that you want it to run on a certain day, well after Midnight it is no longer that day. Also you should read up on the setting "allow Retry after Run day" Its hard to say exactly what happened without more detail but it maybe that the backup that kicked off right away was from the Freq based Schedule: 17.30_mon_full or 17.30_mon_inc since they are open each day. Hope that helpsSteve On 6/13/06, Marks, Jonathan - Fort Collins, CO <[EMAIL PROTECTED]> wrote: If you are using Netbackup 6.0 you can not have your start window cross midnight. I was told that it is bad practice. I think Netbackup has gone goofy. -Jonathan Marks (970)295-5362 From: Bob Stump [mailto:[EMAIL PROTECTED]] Sent: Monday, June 12, 2006 4:02 PM To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included. I have years of experience with frequency based scheduling but I have always shied away from calendar based. Today I made my first attempt and I cannot see where I made a mistake. Please review this and help me if you can. Thanks. Here is the problemThe calendar based backup started on the first day that I made this policy active even though it is not suppose to be active until the last Monday of the month. Here is the strategy1. full backup every monday night excluding last monday of the month with 1 month retention allow tuesday full for any failures that may occur on monday3. last monday of each month run a calendar full backup with 3 month retention retries allowed after runday which would be tuesday night.2. incremental backup every night except monday nights with 1 month retention Here is the bppllist:Policy Name: groupwise01-09 Policy Type: Standard Active: yes Effective date: 06/12/2006 08:00:00 Client Compress: no Follow NFS Mounts: no Cross Mount Points: no Collect TIR info: no Block Incremental: no Mult. Data Streams: yes Client Encrypt: no Checkpoint: no Policy Priority: 25 Max Jobs/Policy: Unlimited Disaster Recovery: 0 Residence: dssu_grp Volume Pool: Novell Keyword: (none specified) HW/OS/Client: Novell NetWare gw01 Novell NetWare gw02 Novell NetWare gw03 Novell NetWare gw04 Novell NetWare gw05 Novell NetWare gw06 Novell NetWare gw07 Novell NetWare gw08 Novell NetWare gw09 Include: /FS Schedule: 17.30_mon_calendar Type: Full Backup Maximum MPX: 10 Synthetic: 0 PFI Recovery: 0 Retention Level: 5 (3 months) Number Copies: 1 Fail on Error: 0 Residence: dssu04 Volume Pool: (same as policy volume pool) Calendar sched: Enabled Allowed to retry after run day SPECIFIC DATE 0 - 06/26/2006 SPECIFIC DATE 1 - 07/31/2006 SPECIFIC DATE 2 - 08/28/2006 SPECIFIC DATE 3 - 09/25/2006 SPECIFIC DATE 4 - 10/30/2006 SPECIFIC DATE 5 - 11/27/2006 SPECIFIC DATE 6 - 12/25/2006 Monday, Week 5 Daily Windows: Monday 18:30:00 --> Tuesday 04:00:00 Tuesday 17:30:00 --> Wednesday 04:00:00 Schedule: 17.30_mon_full Type: Full Backup Frequency: every 5 days Maximum MPX: 10 Synthetic: 0 PFI Recovery: 0 Retention Level: 3 (1 month) Number Copies: 1 Fail on Error: 0 Residence: dssu04 Volume Pool: (same as policy volume pool) EXCLUDE DATE 0 - 06/26/2006 EXCLUDE DATE 1 - 07/31/2006 EXCLUDE DATE 2 - 08/28/2006 EXCLUDE DATE 3 - 09/25/2006 EXCLUDE DATE 4 - 10/30/2006 EXCLUDE DATE 5 - 11/27/2006 EXCLUDE DATE 6 - 12/25/2006 Daily Windows: Monday 17:20:00 --> Tuesday 04:00:00 Tuesday 17:30:00 --> Wednesday 04:00:00 Schedule: 17.30_mon_inc Type: Differential Incremental Backup Frequency: every 12 hours Maximum MPX: 10 Synthetic: 0 PFI Recovery: 0 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) Daily Windows: Sunday 17:30:00 --> Monday 04:00:00 Tuesday 17:30:00 --> Wednesday 04:00:00 Wednesday 17:30:00 --> Thursday 04:00:00 Thursday 17:30:00 --> Friday 04:00:00
Re: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included.
If you are using Netbackup 6.0 you can not have your start window cross midnight. I was told that it is bad practice. I think Netbackup has gone goofy. -Jonathan Marks (970)295-5362 From: Bob Stump [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 4:02 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included. I have years of experience with frequency based scheduling but I have always shied away from calendar based. Today I made my first attempt and I cannot see where I made a mistake. Please review this and help me if you can. Thanks. Here is the problemThe calendar based backup started on the first day that I made this policy active even though it is not suppose to be active until the last Monday of the month. Here is the strategy1. full backup every monday night excluding last monday of the month with 1 month retention allow tuesday full for any failures that may occur on monday3. last monday of each month run a calendar full backup with 3 month retention retries allowed after runday which would be tuesday night.2. incremental backup every night except monday nights with 1 month retention Here is the bppllist:Policy Name: groupwise01-09 Policy Type: Standard Active: yes Effective date: 06/12/2006 08:00:00 Client Compress: no Follow NFS Mounts: no Cross Mount Points: no Collect TIR info: no Block Incremental: no Mult. Data Streams: yes Client Encrypt: no Checkpoint: no Policy Priority: 25 Max Jobs/Policy: Unlimited Disaster Recovery: 0 Residence: dssu_grp Volume Pool: Novell Keyword: (none specified) HW/OS/Client: Novell NetWare gw01 Novell NetWare gw02 Novell NetWare gw03 Novell NetWare gw04 Novell NetWare gw05 Novell NetWare gw06 Novell NetWare gw07 Novell NetWare gw08 Novell NetWare gw09 Include: /FS Schedule: 17.30_mon_calendar Type: Full Backup Maximum MPX: 10 Synthetic: 0 PFI Recovery: 0 Retention Level: 5 (3 months) Number Copies: 1 Fail on Error: 0 Residence: dssu04 Volume Pool: (same as policy volume pool) Calendar sched: Enabled Allowed to retry after run day SPECIFIC DATE 0 - 06/26/2006 SPECIFIC DATE 1 - 07/31/2006 SPECIFIC DATE 2 - 08/28/2006 SPECIFIC DATE 3 - 09/25/2006 SPECIFIC DATE 4 - 10/30/2006 SPECIFIC DATE 5 - 11/27/2006 SPECIFIC DATE 6 - 12/25/2006 Monday, Week 5 Daily Windows: Monday 18:30:00 --> Tuesday 04:00:00 Tuesday 17:30:00 --> Wednesday 04:00:00 Schedule: 17.30_mon_full Type: Full Backup Frequency: every 5 days Maximum MPX: 10 Synthetic: 0 PFI Recovery: 0 Retention Level: 3 (1 month) Number Copies: 1 Fail on Error: 0 Residence: dssu04 Volume Pool: (same as policy volume pool) EXCLUDE DATE 0 - 06/26/2006 EXCLUDE DATE 1 - 07/31/2006 EXCLUDE DATE 2 - 08/28/2006 EXCLUDE DATE 3 - 09/25/2006 EXCLUDE DATE 4 - 10/30/2006 EXCLUDE DATE 5 - 11/27/2006 EXCLUDE DATE 6 - 12/25/2006 Daily Windows: Monday 17:20:00 --> Tuesday 04:00:00 Tuesday 17:30:00 --> Wednesday 04:00:00 Schedule: 17.30_mon_inc Type: Differential Incremental Backup Frequency: every 12 hours Maximum MPX: 10 Synthetic: 0 PFI Recovery: 0 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) Daily Windows: Sunday 17:30:00 --> Monday 04:00:00 Tuesday 17:30:00 --> Wednesday 04:00:00 Wednesday 17:30:00 --> Thursday 04:00:00 Thursday 17:30:00 --> Friday 04:00:00 Friday 17:30:00 --> Saturday 04:00:00 Saturday 17:30:00 --> Sunday 04:00:00 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included.
Perhaps the calendar schedule has to be in its own policy?>>> "Bob Stump" <[EMAIL PROTECTED]> 6/12/2006 6:01 PM >>> I have years of experience with frequency based scheduling but I have always shied away from calendar based. Today I made my first attempt and I cannot see where I made a mistake. Please review this and help me if you can. Thanks. Here is the problemThe calendar based backup started on the first day that I made this policy active even though it is not suppose to be active until the last Monday of the month. Here is the strategy1. full backup every monday night excluding last monday of the month with 1 month retention allow tuesday full for any failures that may occur on monday3. last monday of each month run a calendar full backup with 3 month retention retries allowed after runday which would be tuesday night.2. incremental backup every night except monday nights with 1 month retention Here is the bppllist:Policy Name: groupwise01-09 Policy Type: Standard Active: yes Effective date: 06/12/2006 08:00:00 Client Compress: no Follow NFS Mounts: no Cross Mount Points: no Collect TIR info: no Block Incremental: no Mult. Data Streams: yes Client Encrypt: no Checkpoint: no Policy Priority: 25 Max Jobs/Policy: Unlimited Disaster Recovery: 0 Residence: dssu_grp Volume Pool: Novell Keyword: (none specified) HW/OS/Client: Novell NetWare gw01 Novell NetWare gw02 Novell NetWare gw03 Novell NetWare gw04 Novell NetWare gw05 Novell NetWare gw06 Novell NetWare gw07 Novell NetWare gw08 Novell NetWare gw09 Include: /FS Schedule: 17.30_mon_calendar Type: Full Backup Maximum MPX: 10 Synthetic: 0 PFI Recovery: 0 Retention Level: 5 (3 months) Number Copies: 1 Fail on Error: 0 Residence: dssu04 Volume Pool: (same as policy volume pool) Calendar sched: Enabled Allowed to retry after run day SPECIFIC DATE 0 - 06/26/2006 SPECIFIC DATE 1 - 07/31/2006 SPECIFIC DATE 2 - 08/28/2006 SPECIFIC DATE 3 - 09/25/2006 SPECIFIC DATE 4 - 10/30/2006 SPECIFIC DATE 5 - 11/27/2006 SPECIFIC DATE 6 - 12/25/2006 Monday, Week 5 Daily Windows: Monday 18:30:00 --> Tuesday 04:00:00 Tuesday 17:30:00 --> Wednesday 04:00:00 Schedule: 17.30_mon_full Type: Full Backup Frequency: every 5 days Maximum MPX: 10 Synthetic: 0 PFI Recovery: 0 Retention Level: 3 (1 month) Number Copies: 1 Fail on Error: 0 Residence: dssu04 Volume Pool: (same as policy volume pool) EXCLUDE DATE 0 - 06/26/2006 EXCLUDE DATE 1 - 07/31/2006 EXCLUDE DATE 2 - 08/28/2006 EXCLUDE DATE 3 - 09/25/2006 EXCLUDE DATE 4 - 10/30/2006 EXCLUDE DATE 5 - 11/27/2006 EXCLUDE DATE 6 - 12/25/2006 Daily Windows: Monday 17:20:00 --> Tuesday 04:00:00 Tuesday 17:30:00 --> Wednesday 04:00:00 Schedule: 17.30_mon_inc Type: Differential Incremental Backup Frequency: every 12 hours Maximum MPX: 10 Synthetic: 0 PFI Recovery: 0 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) Daily Windows: Sunday 17:30:00 --> Monday 04:00:00 Tuesday 17:30:00 --> Wednesday 04:00:00 Wednesday 17:30:00 --> Thursday 04:00:00 Thursday 17:30:00 --> Friday 04:00:00 Friday 17:30:00 --> Saturday 04:00:00 Saturday 17:30:00 --> Sunday 04:00:00 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included.
Hi Bob We had a similar problem with our quarterly backup. It should only run 4 times a year but tried to run instead of the weekly backup for any new servers added to a policy. Removing 'Allowed to retry after run day' seemed to cure the problem. Regards Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob StumpSent: Tuesday, 13 June 2006 10:02 amTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] whats wrong with my calendar based backup schedule.bppllist included. I have years of experience with frequency based scheduling but I have always shied away from calendar based. Today I made my first attempt and I cannot see where I made a mistake. Please review this and help me if you can. Thanks. ... ** This electronic email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. The views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Christchurch City Council. If you are not the correct recipient of this email please advise the sender and delete. Christchurch City Council http://www.ccc.govt.nz ** ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
