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

2010-09-22 Thread David Stanaway
 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-boun...@mailman.eng.auburn.edu
 [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of
 *BeDour, Wayne
 *Sent:* Tuesday, September 21, 2010 7:39 AM
 *To:* WEAVER, Simon (external); veritas-bu@mailman.eng.auburn.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: wbed...@lear.com mailto:wbed...@lear.com

 

 *From:* WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net]
 *Sent:* Tuesday, September 21, 2010 8:28 AM
 *To:* BeDour, Wayne; veritas-bu@mailman.eng.auburn.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-boun...@mailman.eng.auburn.edu
 [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of
 *BeDour, Wayne
 *Sent:* Tuesday, September 21, 2010 1:07 PM
 *To:* veritas-bu@mailman.eng.auburn.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: wbed...@lear.com mailto:wbed...@lear.com



___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


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

2010-09-21 Thread WEAVER, Simon (external)
I was going to suggest to update to .6 as well
 
Used to see this on SAP systems, but not to the same degree as this.
S.



From: judy_hinchcli...@administaff.com
[mailto:judy_hinchcli...@administaff.com] 
Sent: Tuesday, September 21, 2010 3:27 PM
To: WEAVER, Simon (external); wbed...@lear.com;
veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Policy kicking off again after a successful
backupandgetting 196 errors.



I use to have that, can't remember if it was a bug or not.

if you can bounce nb, or disable and re enable the policy.  Or just
bounce the scheduler on the master.

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WEAVER,
Simon (external)
Sent: Tuesday, September 21, 2010 7:28 AM
To: BeDour, Wayne; veritas-bu@mailman.eng.auburn.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-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of BeDour,
Wayne
Sent: Tuesday, September 21, 2010 1:07 PM
To: veritas-bu@mailman.eng.auburn.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: wbed...@lear.com

**
** LEGAL DISCLAIMER **
**
 
This E-mail message and any attachments may contain 
legally privileged, confidential or proprietary 
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of 
this message to the intended recipient(s), you are 
hereby notified that any dissemination, distribution 
or copying of this E-mail message is strictly 
prohibited. If you have received this message in 
error, please immediately notify the sender and 
delete this E-mail message from your computer.
This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England

 


This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered 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


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

2010-09-21 Thread Rusty.Major
I would agree to try to patch as there were some issues with the early 
releases and calendar based scheds. Calendar scheduling is the bane of 
NetBackup engineering. 

Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard 
Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 
281-584-4693
Keeping People and Information Connected® ▪ 
http://availability.sungard.com/ 
P Think before you print 
CONFIDENTIALITY:  This e-mail (including any attachments) may contain 
confidential, proprietary and privileged information, and unauthorized 
disclosure or use is prohibited.  If you received this e-mail in error, 
please notify the sender and delete this e-mail from your system. 



WEAVER, Simon (external) simon.wea...@astrium.eads.net 
Sent by: veritas-bu-boun...@mailman.eng.auburn.edu
09/21/2010 09:42 AM

To
judy_hinchcli...@administaff.com, wbed...@lear.com, 
veritas-bu@mailman.eng.auburn.edu
cc

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






I was going to suggest to update to .6 as well
 
Used to see this on SAP systems, but not to the same degree as this.
S.

From: judy_hinchcli...@administaff.com 
[mailto:judy_hinchcli...@administaff.com] 
Sent: Tuesday, September 21, 2010 3:27 PM
To: WEAVER, Simon (external); wbed...@lear.com; 
veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Policy kicking off again after a successful 
backupandgetting 196 errors.

I use to have that, can’t remember if it was a bug or not.
if you can bounce nb, or disable and re enable the policy.  Or just bounce 
the scheduler on the master.
 
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WEAVER, 
Simon (external)
Sent: Tuesday, September 21, 2010 7:28 AM
To: BeDour, Wayne; veritas-bu@mailman.eng.auburn.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-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of BeDour, 
Wayne
Sent: Tuesday, September 21, 2010 1:07 PM
To: veritas-bu@mailman.eng.auburn.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: wbed...@lear.com

**
** LEGAL DISCLAIMER **
**
 
This E-mail message and any attachments may contain 
legally privileged, confidential or proprietary 
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of 
this message to the intended recipient(s), you are 
hereby notified that any dissemination, distribution 
or copying of this E-mail message is strictly 
prohibited. If you have received this message in 
error, please immediately notify the sender and 
delete this E-mail message from your computer.

This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
 

This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England

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

2010-09-21 Thread THELEN, ROBERT M (ATTSI)
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-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of BeDour, Wayne
Sent: Tuesday, September 21, 2010 7:39 AM
To: WEAVER, Simon (external); veritas-bu@mailman.eng.auburn.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: wbed...@lear.com 



From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] 
Sent: Tuesday, September 21, 2010 8:28 AM
To: BeDour, Wayne; veritas-bu@mailman.eng.auburn.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-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of BeDour, Wayne
Sent: Tuesday, September 21, 2010 1:07 PM
To: veritas-bu@mailman.eng.auburn.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: wbed...@lear.com

**
** LEGAL DISCLAIMER **
**
 
This E-mail message and any attachments may contain 
legally privileged, confidential or proprietary 
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of 
this message to the intended recipient(s), you are 
hereby notified that any dissemination, distribution 
or copying of this E-mail message is strictly 
prohibited. If you have received this message in 
error, please immediately notify the sender and 
delete this E-mail message from your computer.

 

This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England

 

**
** LEGAL DISCLAIMER **
**
 
This E-mail message and any attachments may contain 
legally privileged, confidential or proprietary 
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of 
this message to the intended recipient(s), you are 
hereby notified that any dissemination, distribution 
or copying of this E-mail message is strictly 
prohibited. If you have received this message in 
error, please immediately notify the sender and 
delete this E-mail message from your computer.

 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu