This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C3EA91.119C5944
Content-Type: text/plain
Make sure you have in your bp.conf file:
ALLOW_MEDIA_OVERWRITE = DBR
ALLOW_MEDIA_OVERWRITE = TAR
ALLOW_MEDIA_OVERWRITE = CPIO
ALLOW_MEDIA_OVERWRITE = ANSI
ALLOW_MEDIA_OVERWRITE = AOS/VS
ALLOW_MEDIA_OVERWRITE = MTF1
Make sure NBU re-reads the bp.conf file after updating it.
If NBU sees a tape label format it does not recognize, it will FREEZE the
tape. The parameters shown above, when placed into bp.conf file, will force
NBU to overwrite the label and use the tape normally.
Paul Griese
System Management
713-331-6454
-----Original Message-----
From: Ashok Kumar [mailto:ldapsk AT yahoo DOT com]
Sent: Monday, February 02, 2004 8:08 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Frozen
Hi
I am using Netbackup DataCentre4.5GA on solaris 8
There where some tapes in frozen state.
I used bpmedia -unfreeze -m xxxxxx,
then moved them to scratch pool.
But when these tapes where taken by some volume pool
these tapes went back into Frozen state.
What might be the problem? Are these tapes are BAD?
Regards
Ashok
--- "Stump, Robert (Contractor) (DRMS)"
<Robert.Stump AT dla DOT mil> wrote:
> Or
> In the same class (policy) have two FULL backup
> schedules with the window of
> opportunity set to exactly the same timeframe.
> The only difference is retention and frequency. If
> both schedules have met
> the frequency requirement then,
> only the one with the longest retention will be
> scheduled to run.
> This works for me.
>
> -----Original Message-----
> From: dave-bu AT graniteweb DOT com
> [mailto:dave-bu AT graniteweb DOT com]
> Sent: Thursday, January 29, 2004 11:16 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Scheduling?
>
>
>
> * Daryl Katauskas <DKatauskas AT nst-inc DOT com>
> [2004-01-29 16:36]:
> > Hello All:
> >
> > I have a requirement to schedule full backups for
> a group of client
> machines each Friday. So far so good. I also have
> an additional
> requirement to perform a full backup of the same
> machines on the LAST Friday
> of each month for long term archiving.
>
> >
> > Can anyone offer any suggestions on how to
> accomplish this second type of
> schedule? (Other than by specifically excluding the
> first backups?
>
> Actually, this depends on what your requirements
> are. Do you need an
> ADDITIONAL full on the last Friday, or can you use
> one of the other
> fulls for this?
>
> set up a weekly schedule and a monthly schedule that
> have no times
> defined in the window. this way it will run only if
> you tell it to.
> having different schedules allows you to set up
> different retentions. Then
> try using a wrapper script that is scheduled through
> cron to run every
> Friday and test if it is the last Friday of the
> month. If it is, run the
> monthly schedule, if not run the weekly schedule
> using bpbackup with a
> -i switch.
>
> This is just one variation of the problem, geared
> toward 3.4 and
> earlier. If you are using 4.5, It's simple to add a
> monthly
> calendar-based schedule instead of a frequency-based
> one.
>
> --
> David Rock
> david at graniteweb dot com
>
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
____________________________________________________________________________
_
(c) 2003 TeleCheck International, Inc. THIS DOCUMENT, AND ANY ATTACHED
INFORMATION: 1) IS PROPRIETARY, PRIVILEGED AND CONFIDENTIAL PROPERTY OF
TELECHECK UNDER APPLICABLE LAW, AND 2) IS INTENDED EXCLUSIVELY FOR INTERNAL
USE BY TELECHECK EMPLOYEES AND INTENDED RECIPIENTS WITH A LEGITIMATE
TELECHECK BUSINESS NEED THEREFORE. ITS REPRODUCTION, DISSEMINATION,
DISTRIBUTION AND/OR DISCLOSURE, EXCEPT TO SUCH TELECHECK EMPLOYEES AND
INTENDED RECIPIENTS, IS STRICTLY PROHIBITED . IF YOU ARE NOT SUCH A
TELECHECK EMPLOYEE OR INTENDED RECIPIENT, OR THE EMPLOYEE OR AGENT
RESPONSIBLE FOR DELIVERING THIS MESSAGE TO THE INTENDED RECIPIENT, YOU ARE
HEREBY NOTIFIED THAT ANY REPRODUCTION, DISSEMINATION, DISTRIBUTION AND/OR
DISCLOSURE OF THIS DOCUMENT, OR ANY ATTACHMENTS, IS STRICTLY PROHIBITED.
------_=_NextPart_001_01C3EA91.119C5944
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2657.73">
<TITLE>RE: [Veritas-bu] Frozen</TITLE>
</HEAD>
<BODY>
<BR>
<P><FONT SIZE=3D2>Make sure you have in your bp.conf file:</FONT>
</P>
<P><FONT SIZE=3D2>ALLOW_MEDIA_OVERWRITE =3D DBR</FONT>
<BR><FONT SIZE=3D2>ALLOW_MEDIA_OVERWRITE =3D TAR</FONT>
<BR><FONT SIZE=3D2>ALLOW_MEDIA_OVERWRITE =3D CPIO</FONT>
<BR><FONT SIZE=3D2>ALLOW_MEDIA_OVERWRITE =3D ANSI</FONT>
<BR><FONT SIZE=3D2>ALLOW_MEDIA_OVERWRITE =3D AOS/VS</FONT>
<BR><FONT SIZE=3D2>ALLOW_MEDIA_OVERWRITE =3D MTF1</FONT>
</P>
<P><FONT SIZE=3D2>Make sure NBU re-reads the bp.conf file after =
updating it.</FONT>
</P>
<P><FONT SIZE=3D2>If NBU sees a tape label format it does not =
recognize, it will FREEZE the tape. The parameters shown above, when =
placed into bp.conf file, will force NBU to overwrite the label and use =
the tape normally. </FONT></P>
<P><FONT SIZE=3D2>Paul Griese</FONT>
<BR><FONT SIZE=3D2>System Management</FONT>
<BR><FONT SIZE=3D2>713-331-6454</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Ashok Kumar [<A =
HREF=3D"mailto:ldapsk AT yahoo DOT com">mailto:ldapsk AT yahoo DOT com</A>]
</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, February 02, 2004 8:08 AM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Frozen</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Hi</FONT>
</P>
<P><FONT SIZE=3D2>I am using Netbackup DataCentre4.5GA on solaris =
8</FONT>
<BR><FONT SIZE=3D2>There where some tapes in frozen state.</FONT>
<BR><FONT SIZE=3D2>I used bpmedia -unfreeze -m xxxxxx,</FONT>
<BR><FONT SIZE=3D2>then moved them to scratch pool.</FONT>
<BR><FONT SIZE=3D2>But when these tapes where taken by some volume =
pool</FONT>
<BR><FONT SIZE=3D2>these tapes went back into Frozen state.</FONT>
<BR><FONT SIZE=3D2>What might be the problem? Are these tapes are =
BAD?</FONT>
</P>
<P><FONT SIZE=3D2>Regards</FONT>
<BR><FONT SIZE=3D2>Ashok</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>
<P><FONT SIZE=3D2>--- "Stump, Robert (Contractor) =
(DRMS)"</FONT>
<BR><FONT SIZE=3D2><Robert.Stump AT dla DOT mil> wrote:</FONT>
<BR><FONT SIZE=3D2>> Or</FONT>
<BR><FONT SIZE=3D2>> In the same class (policy) have two FULL =
backup</FONT>
<BR><FONT SIZE=3D2>> schedules with the window of</FONT>
<BR><FONT SIZE=3D2>> opportunity set to exactly the same =
timeframe.</FONT>
<BR><FONT SIZE=3D2>> The only difference is retention and frequency. =
If</FONT>
<BR><FONT SIZE=3D2>> both schedules have met</FONT>
<BR><FONT SIZE=3D2>> the frequency requirement then, </FONT>
<BR><FONT SIZE=3D2>> only the one with the longest retention will =
be</FONT>
<BR><FONT SIZE=3D2>> scheduled to run.</FONT>
<BR><FONT SIZE=3D2>> This works for me.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>> From: dave-bu AT graniteweb DOT com</FONT>
<BR><FONT SIZE=3D2>> [<A =
HREF=3D"mailto:dave-bu AT graniteweb DOT com">mailto:dave-bu AT graniteweb DOT
com</A>=
]</FONT>
<BR><FONT SIZE=3D2>> Sent: Thursday, January 29, 2004 11:16 =
PM</FONT>
<BR><FONT SIZE=3D2>> To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>> Subject: Re: [Veritas-bu] Scheduling?</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> * Daryl Katauskas =
<DKatauskas AT nst-inc DOT com></FONT>
<BR><FONT SIZE=3D2>> [2004-01-29 16:36]:</FONT>
<BR><FONT SIZE=3D2>> > Hello All:</FONT>
<BR><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> > I have a requirement to schedule full =
backups for</FONT>
<BR><FONT SIZE=3D2>> a group of client</FONT>
<BR><FONT SIZE=3D2>> machines each Friday. So far so =
good. I also have</FONT>
<BR><FONT SIZE=3D2>> an additional</FONT>
<BR><FONT SIZE=3D2>> requirement to perform a full backup of the =
same</FONT>
<BR><FONT SIZE=3D2>> machines on the LAST Friday</FONT>
<BR><FONT SIZE=3D2>> of each month for long term archiving.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> > </FONT>
<BR><FONT SIZE=3D2>> > Can anyone offer any suggestions on how =
to</FONT>
<BR><FONT SIZE=3D2>> accomplish this second type of</FONT>
<BR><FONT SIZE=3D2>> schedule? (Other than by specifically =
excluding the</FONT>
<BR><FONT SIZE=3D2>> first backups?</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Actually, this depends on what your =
requirements</FONT>
<BR><FONT SIZE=3D2>> are. Do you need an</FONT>
<BR><FONT SIZE=3D2>> ADDITIONAL full on the last Friday, or can you =
use</FONT>
<BR><FONT SIZE=3D2>> one of the other </FONT>
<BR><FONT SIZE=3D2>> fulls for this? </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> set up a weekly schedule and a monthly schedule =
that</FONT>
<BR><FONT SIZE=3D2>> have no times</FONT>
<BR><FONT SIZE=3D2>> defined in the window. this way it will run =
only if</FONT>
<BR><FONT SIZE=3D2>> you tell it to. </FONT>
<BR><FONT SIZE=3D2>> having different schedules allows you to set =
up</FONT>
<BR><FONT SIZE=3D2>> different retentions. Then </FONT>
<BR><FONT SIZE=3D2>> try using a wrapper script that is scheduled =
through</FONT>
<BR><FONT SIZE=3D2>> cron to run every </FONT>
<BR><FONT SIZE=3D2>> Friday and test if it is the last Friday of =
the</FONT>
<BR><FONT SIZE=3D2>> month. If it is, run the </FONT>
<BR><FONT SIZE=3D2>> monthly schedule, if not run the weekly =
schedule</FONT>
<BR><FONT SIZE=3D2>> using bpbackup with a </FONT>
<BR><FONT SIZE=3D2>> -i switch. </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> This is just one variation of the problem, =
geared</FONT>
<BR><FONT SIZE=3D2>> toward 3.4 and</FONT>
<BR><FONT SIZE=3D2>> earlier. If you are using 4.5, It's simple to =
add a</FONT>
<BR><FONT SIZE=3D2>> monthly </FONT>
<BR><FONT SIZE=3D2>> calendar-based schedule instead of a =
frequency-based</FONT>
<BR><FONT SIZE=3D2>> one. </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> --</FONT>
<BR><FONT SIZE=3D2>> David Rock </FONT>
<BR><FONT SIZE=3D2>> david at graniteweb dot com </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
</P>
<BR>
<P><FONT SIZE=3D2>__________________________________</FONT>
<BR><FONT SIZE=3D2>Do you Yahoo!?</FONT>
<BR><FONT SIZE=3D2>Yahoo! SiteBuilder - Free web site building tool. =
Try it! <A HREF=3D"http://webhosting.yahoo.com/ps/sb/"; =
TARGET=3D"_blank">http://webhosting.yahoo.com/ps/sb/</A></FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu <A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________________________=
______________</FONT>
</P>
<P><FONT SIZE=3D2>(c) 2003 TeleCheck International, Inc. THIS DOCUMENT, =
AND ANY ATTACHED INFORMATION: 1) IS PROPRIETARY, PRIVILEGED AND =
CONFIDENTIAL PROPERTY OF TELECHECK UNDER APPLICABLE LAW, AND 2) =
IS INTENDED EXCLUSIVELY FOR INTERNAL USE BY TELECHECK EMPLOYEES AND =
INTENDED RECIPIENTS WITH A LEGITIMATE TELECHECK BUSINESS NEED =
THEREFORE. ITS REPRODUCTION, DISSEMINATION, DISTRIBUTION =
AND/OR DISCLOSURE, EXCEPT TO SUCH TELECHECK EMPLOYEES AND =
INTENDED RECIPIENTS, IS STRICTLY PROHIBITED . IF YOU ARE =
NOT SUCH A TELECHECK EMPLOYEE OR INTENDED RECIPIENT, OR THE EMPLOYEE OR =
AGENT RESPONSIBLE FOR DELIVERING THIS MESSAGE TO THE INTENDED =
RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REPRODUCTION, =
DISSEMINATION, DISTRIBUTION AND/OR DISCLOSURE OF THIS DOCUMENT, OR ANY =
ATTACHMENTS, IS STRICTLY PROHIBITED.</FONT></P>
<BR>
<BR>
</BODY>
</HTML>
------_=_NextPart_001_01C3EA91.119C5944--
|
