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_01C2E1DB.8B1C4B90
Content-Type: text/plain
Based on your note, I checked my L700 & found that three drives are not
marked for tape_alert enabled. Do you know the process to enable it?
-M
-----Original Message-----
From: Tim Hoke [mailto:thoke AT northpeak DOT com]
Sent: Monday, March 03, 2003 3:19 PM
To: Paul Bleimeyer
Cc: veritas-bu AT mailman.eng.auburn DOT edu; 'vidit kohli'
Subject: Re: [Veritas-bu] RE: Veritas-bu digest, Vol 1 #1990 - 3 msgs
Hmmm...
Well, NBU does work in SSO with TapeAlert, as long as the drives support
it.
tpautoconf -t will show if they do or not.
Frequency based cleaning doesn't (as noted) work in SSO.
IF however, you are going to use Library based (Since tapealert might not
work), then make sure to disable tape alert within NetBackup....
On each media server:
touch /usr/openv/volmgr/database/NO_TAPEALERT
Then restart the daemons.
And make sure you are at 3.4_4 or 4.5_1
-Tim
thoke AT northpeak DOT com
On Mon, 3 Mar 2003, Paul Bleimeyer wrote:
> > From: "vidit kohli" <vidit_k AT hotmail DOT com>
> > Subject: [Veritas-bu] 9840 drive cleaning in L700
>
> > I have setup Netbackup 3.4 to control 9840 drive cleaning in
> > L700, but
> > problem is that it don't work as required.
> > [my understanding was that when ever any drive needs cleaning
> > , netbackup
> > will perform before next backup starts for that 9840 drive]
> >
> > I have two cleaning media in the slots detected by media manager,
> > also tpclean -c option does manual clean fine
> >
> > Please advise if I'm missing any settings?
> >
>
>
> Vidit,
>
> I am going to reply here since I faced the same thing as you about a year
> ago
> and this might help someone else out as well if they read the archives
later
> on.
>
> You mentioned in an email to me that you had SSO enabled on your media and
> master
> servers. The reason I asked this is because we did the same thing. Same
> problems too!
>
> In an SSO environment with an L700 you want the library to clean the tape
> drives and not have veritas handle it. The reason is that frequency base
> tape cleaning and tape alert fails under environments using SSO with
> veritas. The library should be made responsible for cleaning the drives.
> This is not totally clear in the Veritas documentation when referencing
SSO
> environments. At least the last time I looked it was a little sparse.
>
> So what the heck is going on then? Why does it fail under SSO and not
> others?
> Here is why. It has to do with the tape cleaning and usage counter getting
> reset.
> When you first media server mounts the tape and starts using the drive,
then
> the counter on usage in the drive starts running. For example, you run
about
> 10 tapes through this same drive via the
> same media server all weekend long during a full. The last tape unmounts
and
> the veritas
> media server notifies your master that it is done with the drive and the
> drive is released.
> At this point your tape drive has a usage counter for the amount of time
> this drive
> has been in use. Now veritas is currently setup to detect this and will
> attempt to clean
> the drives. Everything looks great right?
>
> Here is where SSO gets in the mix. Now along comes media server number 2.
>
> It has a number of policies/classes it is supposed to run as
> well and starts allocating drives. Including the one your first media
server
> just got done
> using. As soon as it connects to the tape drive that media server 1 was
just
> using, it
> resets the tape usage/cleaning counter on the drive and the veritas job
for
> cleaning
> never fires. Not good.
>
> So how do we fix this behavior? With SSO in the mix you want to make sure
> that the library itself handles this process for you. Now this gets a
little
> bit interesting as well, since some of the prior releases of firmware on
the
> L700 didn't always handle this properly as well.
>
> Here is a link from support about the version issues:
> http://seer.support.veritas.com/docs/240940.htm
>
> So once you get the veritas jobs disabled, now you want to go to the front
> panel of your l700 or
> you can do this remotely if you have the horizon code installed for remote
> support as well.
> You want to select the menu button and then find the main library portion
> and enable library
> cleaning. This way when the "clean drive" light comes on, your library
will
> pull a cleaning tape
> and insert it into the drive for cleaning at the next available interval.
> You also want to keep
> at least a couple tapes in your normal silo space for running a manual
> cleaning at times.
> Every once in a while you may get a tape that ends up being frozen and
> veritas decides to freeze
> it since it looks like a bad tape. Go ahead and manually clean the drive
and
> reload the tape again
> with it unfrozen. In some cases, this is just a drive that is very close
to
> needing a cleaning
> and has not tripped the clean drive light. Just a suggestion.
>
> I can tell you that we are running with horizon load level 3.01.02 and
> 130.112E on our drives
> and its working like a champ. I would also recommend you consider
upgrading
> to the 341_4A patch
> if you can, since it also has some corrections in it for releasing the
> drives properly. Just
> a suggestion. As always, check your fabric rev levels, tape drivers, drive
> firmware, library firmware,
> and switch rev levels into account before changing anything in your SAN.
>
> Here is the readme on 4a.
> http://seer.support.veritas.com/docs/240940.htm
>
>
> Hope this helps you out.
>
> Regards,
>
> Paul Bleimeyer
> Research Computing Facility
> Mayo Foundation, Rochester MN
>
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C2E1DB.8B1C4B90
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.2653.12">
<TITLE>RE: [Veritas-bu] RE: Veritas-bu digest, Vol 1 #1990 - 3 =
msgs</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Based on your note, I checked my L700 & found =
that three drives are not marked for tape_alert enabled. Do you =
know the process to enable it?</FONT></P>
<P><FONT SIZE=3D2>-M</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Tim Hoke [<A =
HREF=3D"mailto:thoke AT northpeak DOT com">mailto:thoke AT northpeak DOT
com</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: Monday, March 03, 2003 3:19 PM</FONT>
<BR><FONT SIZE=3D2>To: Paul Bleimeyer</FONT>
<BR><FONT SIZE=3D2>Cc: veritas-bu AT mailman.eng.auburn DOT edu; 'vidit =
kohli'</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Veritas-bu] RE: Veritas-bu digest, Vol =
1 #1990 - 3 msgs</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Hmmm...</FONT>
</P>
<P><FONT SIZE=3D2>Well, NBU does work in SSO with TapeAlert, as long as =
the drives support</FONT>
<BR><FONT SIZE=3D2>it.</FONT>
</P>
<P><FONT SIZE=3D2>tpautoconf -t will show if they do or not.</FONT>
</P>
<P><FONT SIZE=3D2>Frequency based cleaning doesn't (as noted) work in =
SSO.</FONT>
</P>
<P><FONT SIZE=3D2>IF however, you are going to use Library based (Since =
tapealert might not</FONT>
<BR><FONT SIZE=3D2>work), then make sure to disable tape alert within =
NetBackup....</FONT>
</P>
<P><FONT SIZE=3D2>On each media server:</FONT>
</P>
<P><FONT SIZE=3D2>touch /usr/openv/volmgr/database/NO_TAPEALERT</FONT>
</P>
<P><FONT SIZE=3D2>Then restart the daemons.</FONT>
</P>
<P><FONT SIZE=3D2>And make sure you are at 3.4_4 or 4.5_1</FONT>
</P>
<P><FONT SIZE=3D2>-Tim</FONT>
<BR><FONT SIZE=3D2>thoke AT northpeak DOT com</FONT>
</P>
<P><FONT SIZE=3D2>On Mon, 3 Mar 2003, Paul Bleimeyer wrote:</FONT>
</P>
<P><FONT SIZE=3D2>> > From: "vidit kohli" =
<vidit_k AT hotmail DOT com></FONT>
<BR><FONT SIZE=3D2>> > Subject: [Veritas-bu] 9840 drive cleaning =
in L700</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> > I have setup Netbackup 3.4 to control 9840 =
drive cleaning in</FONT>
<BR><FONT SIZE=3D2>> > L700, but</FONT>
<BR><FONT SIZE=3D2>> > problem is that it don't work as =
required.</FONT>
<BR><FONT SIZE=3D2>> > [my understanding was that when ever any =
drive needs cleaning</FONT>
<BR><FONT SIZE=3D2>> > , netbackup</FONT>
<BR><FONT SIZE=3D2>> > will perform before next backup starts for =
that 9840 drive]</FONT>
<BR><FONT SIZE=3D2>> ></FONT>
<BR><FONT SIZE=3D2>> > I have two cleaning media in the slots =
detected by media manager,</FONT>
<BR><FONT SIZE=3D2>> > also tpclean -c option does manual clean =
fine</FONT>
<BR><FONT SIZE=3D2>> ></FONT>
<BR><FONT SIZE=3D2>> > Please advise if I'm missing any =
settings?</FONT>
<BR><FONT SIZE=3D2>> ></FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Vidit,</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> I am going to reply here since I faced the same =
thing as you about a year</FONT>
<BR><FONT SIZE=3D2>> ago</FONT>
<BR><FONT SIZE=3D2>> and this might help someone else out as well if =
they read the archives later</FONT>
<BR><FONT SIZE=3D2>> on.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> You mentioned in an email to me that you had =
SSO enabled on your media and</FONT>
<BR><FONT SIZE=3D2>> master</FONT>
<BR><FONT SIZE=3D2>> servers. The reason I asked this is because we =
did the same thing. Same</FONT>
<BR><FONT SIZE=3D2>> problems too!</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> In an SSO environment with an L700 you want the =
library to clean the tape</FONT>
<BR><FONT SIZE=3D2>> drives and not have veritas handle it. The =
reason is that frequency base</FONT>
<BR><FONT SIZE=3D2>> tape cleaning and tape alert fails under =
environments using SSO with</FONT>
<BR><FONT SIZE=3D2>> veritas. The library should be made responsible =
for cleaning the drives.</FONT>
<BR><FONT SIZE=3D2>> This is not totally clear in the Veritas =
documentation when referencing SSO</FONT>
<BR><FONT SIZE=3D2>> environments. At least the last time I looked =
it was a little sparse.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> So what the heck is going on then? Why does it =
fail under SSO and not</FONT>
<BR><FONT SIZE=3D2>> others?</FONT>
<BR><FONT SIZE=3D2>> Here is why. It has to do with the tape =
cleaning and usage counter getting</FONT>
<BR><FONT SIZE=3D2>> reset.</FONT>
<BR><FONT SIZE=3D2>> When you first media server mounts the tape and =
starts using the drive, then</FONT>
<BR><FONT SIZE=3D2>> the counter on usage in the drive starts =
running. For example, you run about</FONT>
<BR><FONT SIZE=3D2>> 10 tapes through this same drive via the</FONT>
<BR><FONT SIZE=3D2>> same media server all weekend long during a =
full. The last tape unmounts and</FONT>
<BR><FONT SIZE=3D2>> the veritas</FONT>
<BR><FONT SIZE=3D2>> media server notifies your master that it is =
done with the drive and the</FONT>
<BR><FONT SIZE=3D2>> drive is released.</FONT>
<BR><FONT SIZE=3D2>> At this point your tape drive has a usage =
counter for the amount of time</FONT>
<BR><FONT SIZE=3D2>> this drive</FONT>
<BR><FONT SIZE=3D2>> has been in use. Now veritas is currently setup =
to detect this and will</FONT>
<BR><FONT SIZE=3D2>> attempt to clean</FONT>
<BR><FONT SIZE=3D2>> the drives. Everything looks great =
right?</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Here is where SSO gets in the mix. Now along =
comes media server number 2.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> It has a number of policies/classes it is =
supposed to run as</FONT>
<BR><FONT SIZE=3D2>> well and starts allocating drives. Including =
the one your first media server</FONT>
<BR><FONT SIZE=3D2>> just got done</FONT>
<BR><FONT SIZE=3D2>> using. As soon as it connects to the tape drive =
that media server 1 was just</FONT>
<BR><FONT SIZE=3D2>> using, it</FONT>
<BR><FONT SIZE=3D2>> resets the tape usage/cleaning counter on the =
drive and the veritas job for</FONT>
<BR><FONT SIZE=3D2>> cleaning</FONT>
<BR><FONT SIZE=3D2>> never fires. Not good.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> So how do we fix this behavior? With SSO in the =
mix you want to make sure</FONT>
<BR><FONT SIZE=3D2>> that the library itself handles this process =
for you. Now this gets a little</FONT>
<BR><FONT SIZE=3D2>> bit interesting as well, since some of the =
prior releases of firmware on the</FONT>
<BR><FONT SIZE=3D2>> L700 didn't always handle this properly as =
well.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Here is a link from support about the version =
issues:</FONT>
<BR><FONT SIZE=3D2>> <A =
HREF=3D"http://seer.support.veritas.com/docs/240940.htm"; =
TARGET=3D"_blank">http://seer.support.veritas.com/docs/240940.htm</A></F=
ONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> So once you get the veritas jobs disabled, now =
you want to go to the front</FONT>
<BR><FONT SIZE=3D2>> panel of your l700 or</FONT>
<BR><FONT SIZE=3D2>> you can do this remotely if you have the =
horizon code installed for remote</FONT>
<BR><FONT SIZE=3D2>> support as well.</FONT>
<BR><FONT SIZE=3D2>> You want to select the menu button and then =
find the main library portion</FONT>
<BR><FONT SIZE=3D2>> and enable library</FONT>
<BR><FONT SIZE=3D2>> cleaning. This way when the "clean =
drive" light comes on, your library will</FONT>
<BR><FONT SIZE=3D2>> pull a cleaning tape</FONT>
<BR><FONT SIZE=3D2>> and insert it into the drive for cleaning at =
the next available interval.</FONT>
<BR><FONT SIZE=3D2>> You also want to keep</FONT>
<BR><FONT SIZE=3D2>> at least a couple tapes in your normal silo =
space for running a manual</FONT>
<BR><FONT SIZE=3D2>> cleaning at times.</FONT>
<BR><FONT SIZE=3D2>> Every once in a while you may get a tape that =
ends up being frozen and</FONT>
<BR><FONT SIZE=3D2>> veritas decides to freeze</FONT>
<BR><FONT SIZE=3D2>> it since it looks like a bad tape. Go ahead and =
manually clean the drive and</FONT>
<BR><FONT SIZE=3D2>> reload the tape again</FONT>
<BR><FONT SIZE=3D2>> with it unfrozen. In some cases, this is just a =
drive that is very close to</FONT>
<BR><FONT SIZE=3D2>> needing a cleaning</FONT>
<BR><FONT SIZE=3D2>> and has not tripped the clean drive light. Just =
a suggestion.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> I can tell you that we are running with horizon =
load level 3.01.02 and</FONT>
<BR><FONT SIZE=3D2>> 130.112E on our drives</FONT>
<BR><FONT SIZE=3D2>> and its working like a champ. I would also =
recommend you consider upgrading</FONT>
<BR><FONT SIZE=3D2>> to the 341_4A patch</FONT>
<BR><FONT SIZE=3D2>> if you can, since it also has some corrections =
in it for releasing the</FONT>
<BR><FONT SIZE=3D2>> drives properly. Just</FONT>
<BR><FONT SIZE=3D2>> a suggestion. As always, check your fabric rev =
levels, tape drivers, drive</FONT>
<BR><FONT SIZE=3D2>> firmware, library firmware,</FONT>
<BR><FONT SIZE=3D2>> and switch rev levels into account before =
changing anything in your SAN.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Here is the readme on 4a.</FONT>
<BR><FONT SIZE=3D2>> <A =
HREF=3D"http://seer.support.veritas.com/docs/240940.htm"; =
TARGET=3D"_blank">http://seer.support.veritas.com/docs/240940.htm</A></F=
ONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Hope this helps you out.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Regards,</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Paul Bleimeyer</FONT>
<BR><FONT SIZE=3D2>> Research Computing Facility</FONT>
<BR><FONT SIZE=3D2>> Mayo Foundation, Rochester MN</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>> Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>> <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>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><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>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C2E1DB.8B1C4B90--
|
