Veritas-bu

Re: [Veritas-bu] Policy kicking off again after a successful backupandgetting 196 errors.

2010-09-22 08:36:04
Subject: Re: [Veritas-bu] Policy kicking off again after a successful backupandgetting 196 errors.
From: David Stanaway <david AT stanaway DOT net>
To: veritas-bu AT mailman.eng.auburn DOT edu
Date: Wed, 22 Sep 2010 07:31:16 -0500
Try unchecking the allow retry after calendar day (Not sure how it is worded exactly).

Why do you have a calendar based schedule for your daily? Looks like you just need it for the weekly/monthly.


On 9/21/2010 4:02 PM, THELEN, ROBERT M (ATTSI) wrote:

I have seen Calendar based backups do this when the backup window is open for a long time.  The Window is really to be used for frequency based backups – The backup will happen sometime during that window, based on the frequency.  However, for calendar based backups, the start of the backup window is when the backup is set to run.  If the backup runs and completes during the window, and it is still the same calendar day, then the backup will run again, until the backup window closes, with some respect for the frequency (but not much).

 

I solved this in the past by either shrinking the backup window or inflating the frequency.

 

With your backup windows starting at 7am and running all day through 10pm, I would guess that some of these backups might even run more than once per day.

 

-Rob Thelen.

 

From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of BeDour, Wayne
Sent: Tuesday, September 21, 2010 7:39 AM
To: WEAVER, Simon (external); veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Policy kicking off again after a successful backupandgetting 196 errors.

 

It’s calendar based, daily is a Cumulative Incremental that runs Monday through Saturday, backup window 07:00:00 à 22:00:00.  The weekly / monthly is a Full, runs on Sunday with the same window.  It has happened on the weekly and daily runs.

 

Wayne BeDour
Unix System Administrator
PH: 248-447-1739
Internet: wbedour AT lear DOT com


From: WEAVER, Simon (external) [mailto:simon.weaver AT astrium.eads DOT net]
Sent: Tuesday, September 21, 2010 8:28 AM
To: BeDour, Wayne; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Policy kicking off again after a successful backup andgetting 196 errors.

 

Wayne

What is the frequency set for in this policy (within the schedule).

 

Simon

 


From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of BeDour, Wayne
Sent: Tuesday, September 21, 2010 1:07 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Policy kicking off again after a successful backup andgetting 196 errors.

Our environment, HP-UX 11-31 currently running one master and media server running NetBackup 6.5.2.  Running mostly unix / Linus backups and a couple windows b/u’s thrown in for good measure.

I’ve been modifying a few policies, splitting out mount points, changing the volume pool etc.  On a couple of the policies that I’ve modified, they successfully run to completion and then they kick off again and error out with a 196.  When they attempt to run after the successful run, they are still in the backup window even though they shouldn’t have kicked off again.  Doesn’t make much sense to me, anyone ever see this before?

Thanks in advance….

Wayne BeDour

Unix System Administrator

PH: 248-447-1739

Internet: wbedour AT lear DOT com



_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu