Re: [Veritas-bu] whats wrong with my calendar based backup
Which run days did you have checked. The one for the start of the start windows, The end day of the start window or both. Were you trying to get more than one full per week? I am using Solaris 9 just like you. I have tried both the windows and the java gui's. I also had no rerun after run date. I only saw the issue when I only had one run day checked. At first the run day was always the end of the start window but the other 2 variations gave me the same issues. I am using a binary from mp3 to fix vault/duplicate issues as well. (nbrb for Solaris) That issue did not exist in 6.0 or mp1. I would be happy to send it to you for additional testing if you still can not duplicate the problem. After a bit of work Support was able to duplicate the issue and once they did it was difficult to clear it up for them. Thanks for your effort I understand if you are satisfied with your findings. Here is a bppllist -byclient aivas -L For a working policy. This policy does not work when I change the window to span from Friday to all day Saturday. Policy Name: aivas Options: 0x0 template: FALSE c_unused1: ? Names: (none) Policy Type: MS-Windows-NT (13) Active:yes Effective date:05/24/2004 00:00:00 Backup netwrk drvs:no Collect TIR info: no Mult. Data Stream: no Perform Snapshot Backup: no Snapshot Method: (none) Snapshot Method Arguments: (none) Perform Offhost Backup:no Backup Copy: 0 Use Data Mover:no Data Mover Type: 0 Use Alternate Client: no Alternate Client Name: (none) Enable Instant Recovery: no Policy Priority: 0 Max Jobs/Policy: Unlimited Disaster Recovery: 0 Collect BMR Info: no Keyword: BMR Test Windows 2003 Box Client Encrypt:no Checkpoint:no Residence: whitedragon_LTO2 Volume Pool: Full_Library_WIN Client/HW/OS/Pri: aivas PC WindowsNET 0 0 0 0 ? Include: C:\ECC\* Include: C:\FabricManager\* Include: C:\Program Files\ECC\* Include: C:\Program Files\EMC\* Exclude: (none defined) Schedule: Full_Library Type:FULL (0) Calendar sched: Enabled Friday, Week 1 Friday, Week 2 Friday, Week 3 Friday, Week 4 Friday, Week 5 Maximum MPX: 1 Synthetic: 0 PFI Recovery:0 Retention Level: 4 (2 months) u-wind/o/d: 0 0 Incr Type: DELTA (0) Alt Read Host: (none defined) Max Frag Size: 0 MB Number Copies: 1 Fail on Error: 0 Residence: (specific storage unit not required) Volume Pool: (same as policy volume pool) Daily Windows: Day Open Close W-Open W-Close Sunday 000:00:00 000:00:00 Monday 000:00:00 000:00:00 Tuesday 000:00:00 000:00:00 Wednesday 000:00:00 000:00:00 Thursday000:00:00 000:00:00 Friday 017:00:00 024:00:00 137:00:00 144:00:00 Saturday000:00:00 000:00:00 Schedule: Cumulative_Inc Type:CINC (4) Calendar sched: Enabled Monday, Week 1 Tuesday, Week 1 Wednesday, Week 1 Thursday, Week 1 Monday, Week 2 Tuesday, Week 2 Wednesday, Week 2 Thursday, Week 2 Monday, Week 3 Tuesday, Week 3 Wednesday, Week 3 Thursday, Week 3Monday, Week 4 Tuesday, Week 4 Wednesday, Week 4 Thursday, Week 4 Monday, Week 5 Tuesday, Week 5 Wednesday, Week 5 Thursday, Week 5 Maximum MPX: 1 Synthetic: 0 PFI Recovery:0 Retention Level: 1 (2 weeks) u-wind/o/d: 0 0 Incr Type: DELTA (0) Alt Read Host: (none defined) Max Frag Size: 0 MB Number Copies: 1 Fail on Error: 0 Residence: (specific storage unit not required) Volume Pool: (same as policy volume pool) Daily Windows: Day Open Close W-Open W-Close Sunday 000:00:00 000:00:00 Monday 004:00:00 010:00:00 028:00:00 034:00:00 Tuesday 004:00:00 010:00:00 052:00:00 058:00:00 Wednesday 004:00:00 010:00:00 076:00:00 082:00:00 Thursday004:00:00 010:00:00 100:00:00 106:00:00 Friday 000:00:00 000:00:00 Saturday000:00:00 000:00:00 -Jonathan Marks (970)295-5362 -Original Message- From: bob944 [mailto:[EMAIL PROTECTED] Sent: Thursday, June 15, 2006 1:40 AM To: Marks, Jonathan - Fort Collins, CO; 'Tristan Ball'; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] whats wrong with my calendar based backup > Support had me stop Netbackup and remove the file and then start > Netbackup. I was told it would recreate that "pempersist" > file. It did > recreate the file but did not help get my fulls to run. I was using > nbpemreq -predict -date XX/XX/ XX:XX:XX with different dates and > times to try and forecast what would run. I was very care
Re: [Veritas-bu] whats wrong with my calendar based backup
Support had me stop Netbackup and remove the file and then start Netbackup. I was told it would recreate that "pempersist" file. It did recreate the file but did not help get my fulls to run. I was using nbpemreq -predict -date XX/XX/ XX:XX:XX with different dates and times to try and forecast what would run. I was very careful to use the -updatepolicies after any changes I made. This is important to note since there is a small possibility that some of the errors I saw after the initial failure was from the nbpemreq command. I tried to wait and see if the fulls ran at all, but after making a few changes such as the pempersist and waiting a week and then trying something else, I had to change my policies in order to have data backed up. I was always able to manually run the policy. Which I did for all affected policies when I discovered the issue. -Jonathan Marks -Original Message- From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 13, 2006 6:33 PM To: Marks, Jonathan - Fort Collins, CO; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] whats wrong with my calendar based backup I've had similar experiences with 6.0mp2, both calender and frequency based schedules. It seems that the PEM gets confused about which schedules are running/have run. For us, the fix has been to shut down netbackup, then edit the bin/bpshed.d/pempersist file, removing the entries (and subsequent blank lines) for the schedules that were miss-behaving. T. --- Tristan Ball System Administrator Vision Systems +61-3-9211-7064 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marks, Jonathan - Fort Collins, CO Sent: Wednesday, 14 June 2006 9:52 AM To: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] whats wrong with my calendar based backup I do not have documentation for my specific error. I called in Case 280-593-264 to Veritas support for help with my issue. I have used calendar based scheduling for 3 years now and have used it on 5.0 mpX, 5.1 mp2-3 and now 6.0mp2. When I upgraded from version 5.1mp3 to 6.0mp2 all of my Full_library backups that crossed midnight stopped spawning jobs. There were no errors, but policies that met the Full spanning midnight criteria just did not run. I had a cumulative policy start windows Mon-Fri 4:00-10:00 and the calendar settings checked for re-occurring Mon-Fri. I also had a full policy with start window Fri 20:00 - Sat 23:59 and the calendar settings checked for Sat. I dropped the Fri start window and removed the Friday calendar schedule from the cumulative. I then added the Friday check boxes to the calendar schedule for full. I stopped everything and restarted but I could not get any fulls to run. It seems to me and according to eh SAG vol1 that I should have had two fulls running one on Friday late and one sometime on Saturday. Neither occurred. I tried just about everything to get at least one full backup to work with the start windows set to span midnight. Support had me try many things too. If I checked the full's calendar schedule for all days things would run in the window I had set. Is that the way it is supposed to work? Should you need to check all the days to get a full just because you have the midnight start window crossed. That was not my understanding. I then modified the schedule and set the full start window to Fri 20:00-23:59 and removed the Saturday Check boxes from the re-occurring schedule, bing things started to work. I discussed this with support and was told to change everything to not cross the midnight boundary. This boundary issue for lack of a better description was affecting 26 policies here. It always seemed like the policy thought that the other day Fri or Saturday what ever day it was not was the one who owned the start window. It did not create two jobs as one may expect. It created none. The SAG vol1 says that if you want a policy to cross midnight on a single backup attempt you should use Frequency based scheduling with a frequency of 1 day instead. I was unable to get 6.0mp2 calendar configured with fulls crossing the boundary line. I tried new policies but still ran into the same problems. Support was able to duplicate the problem. I asked for a document or something that would state the condition that caused the fulls not to run but received a "We will continue looking at this, do you mind if we close the call" Any suggestion on things to try I am still game. I think the midnight issue must be some strange thing I missed and would be over joyed the figure out what was wrong. I responded since the issue sounded the same as mine and the user may have made what ever strange checks I did. I for lack of time only provided the solution and the go away response I was given from Symantec. -Jonathan Marks -Original Message- From: bob944 [mailto:[
Re: [Veritas-bu] whats wrong with my calendar based backup
I do not have documentation for my specific error. I called in Case 280-593-264 to Veritas support for help with my issue. I have used calendar based scheduling for 3 years now and have used it on 5.0 mpX, 5.1 mp2-3 and now 6.0mp2. When I upgraded from version 5.1mp3 to 6.0mp2 all of my Full_library backups that crossed midnight stopped spawning jobs. There were no errors, but policies that met the Full spanning midnight criteria just did not run. I had a cumulative policy start windows Mon-Fri 4:00-10:00 and the calendar settings checked for re-occurring Mon-Fri. I also had a full policy with start window Fri 20:00 - Sat 23:59 and the calendar settings checked for Sat. I dropped the Fri start window and removed the Friday calendar schedule from the cumulative. I then added the Friday check boxes to the calendar schedule for full. I stopped everything and restarted but I could not get any fulls to run. It seems to me and according to eh SAG vol1 that I should have had two fulls running one on Friday late and one sometime on Saturday. Neither occurred. I tried just about everything to get at least one full backup to work with the start windows set to span midnight. Support had me try many things too. If I checked the full's calendar schedule for all days things would run in the window I had set. Is that the way it is supposed to work? Should you need to check all the days to get a full just because you have the midnight start window crossed. That was not my understanding. I then modified the schedule and set the full start window to Fri 20:00-23:59 and removed the Saturday Check boxes from the re-occurring schedule, bing things started to work. I discussed this with support and was told to change everything to not cross the midnight boundary. This boundary issue for lack of a better description was affecting 26 policies here. It always seemed like the policy thought that the other day Fri or Saturday what ever day it was not was the one who owned the start window. It did not create two jobs as one may expect. It created none. The SAG vol1 says that if you want a policy to cross midnight on a single backup attempt you should use Frequency based scheduling with a frequency of 1 day instead. I was unable to get 6.0mp2 calendar configured with fulls crossing the boundary line. I tried new policies but still ran into the same problems. Support was able to duplicate the problem. I asked for a document or something that would state the condition that caused the fulls not to run but received a "We will continue looking at this, do you mind if we close the call" Any suggestion on things to try I am still game. I think the midnight issue must be some strange thing I missed and would be over joyed the figure out what was wrong. I responded since the issue sounded the same as mine and the user may have made what ever strange checks I did. I for lack of time only provided the solution and the go away response I was given from Symantec. -Jonathan Marks -Original Message- From: bob944 [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 13, 2006 12:54 PM To: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] whats wrong with my calendar based backup > 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. And your documentation is what, exactly? If this is fact, _I_ want to know about it; please provide a pointer to your documentation and I'll apologize for the next sentence. If this extraordinary claim is an area of NetBackup you don't yet understand, but you are happy to spread it as fact on a world-wide mailing list without knowing if it's true or not, do you think that's useful? Backup windows can span any number of midnights. (Ref: SAG Volume I.) If you don't thoroughly understand calendar-based scheduling, the behavior of calendar-based-schedule backup windows spanning midnight may surprise you. Since that behavior usually isn't what users intend, best practice for many is not to span midnight when using calendar-based, in which case calendar-based works as the user expects. (Ref: every person I ever knew who tried moving from freq to cal schedules.) ___ 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 backupschedule.bppllist included.
I am not sure allow is the correct word. If I scheduled a full backup to run across midnight and checked both days in the calendar schedule then I had an issue where the backup job never ran. I did not fail or anything it just did not run. The interface would allow me to configure the policy and recreating the policy did not change the effects. I spoke with Netbackup and the fix the gave me (work around) was not to cross the midnight boundary. -Jonathan Marks -Original Message- From: Steve Beuttel [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 13, 2006 10:31 AM To: Marks, Jonathan - Fort Collins, CO Cc: Bob Stump; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] whats wrong with my calendar based backupschedule.bppllist included. I'm sorry ... did I read correctly that you have verified that NBU 6.0 will not allow a start window to cross midnight? And someone actually told you that was a feature because to do so is a "bad practice"? Is this common experience? Thanks, -Steve- Bob Stump wrote: > goofy isn't the word I was thinking ofbad prcatice to do backups > from 6PM to 6AM > > anyhow. I should have included that I am using NB5.1_MP4 > > > > > > >>> "Marks, Jonathan - Fort Collins, CO" <[EMAIL PROTECTED]> > 6/13/2006 12:02 PM >>> > 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 > > > *From:* Bob Stump [mailto:[EMAIL PROTECTED] > *Sent:* Monday, June 12, 2006 4:02 PM > *To:* veritas-bu@mailman.eng.auburn.edu > *Subject:* [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 problem > The 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 strategy > 1. 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 monday 3. > 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: NovellNetWare gw01 > NovellNetWare gw02 > NovellNetWare gw03 > NovellNetWare gw04 > NovellNetWare gw05 > NovellNetWare gw06 > NovellNetWare gw07 > NovellNetWare gw08 > NovellNetWare 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 --> Tuesday04:00:00 > Tuesday17:30:00 --> Wednesday 04:00:00 > > Schedule: 17.30_mon_full > Type:Full Backup > Frequency: every 5 days >
Re: [Veritas-bu] whats wrong with my calendar based backupschedule.bppllist included.
I did not have any problems with Pre 6.0 crossing the midnight boundary. -Jonathan Marks (970)295-5362 From: Bob Stump [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 13, 2006 10:21 AMTo: Marks, Jonathan - Fort Collins, CO; veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] whats wrong with my calendar based backupschedule.bppllist included. goofy isn't the word I was thinking ofbad prcatice to do backups from 6PM to 6AM anyhow. I should have included that I am using NB5.1_MP4 >>> "Marks, Jonathan - Fort Collins, CO" <[EMAIL PROTECTED]> 6/13/2006 12:02 PM >>> 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 Thu
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] policies not running
Title: Message I have had this problem since going to 6.0. On my systems I found it occurs when I have a start time that crosses midnight. I rebalanced my jobs so they do not cross midnight and all work well. -Jonathan Marks (970)295-5362 I knew there was something I forgot! and if this still does not work... try creating a new Policy. I have definetely seen a corrupt policy where nothing would run, but re-creating has solved it! Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Wilkinson, Tim [mailto:[EMAIL PROTECTED] Sent: 13 June 2006 06:54To: Lewick, Taylor; veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] policies not running Taylor, We had this in NBU6 but it turned out we were using frequency with the frequency set too high. For weeklies, we had it set to a frequency of 1 week, which was falling outside of the start window; we set it to 3 days and it runs fine now. Cheers, Tim From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lewick, TaylorSent: Tuesday, 13 June 2006 6:35 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] policies not running In NetBackup 5.1 MP 4, we are experiencing a recent issue where some policies are not starting. Schedules are set well, policies are active, clients are correct, these jobs don't error, they just never start. Anyone else seeing this, and any idea what to check for? Thanks, Taylor This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of EADS Astrium Limited.Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.EADS Astrium Limited, Registered in England and Wales No. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
