Re: [Veritas-bu] bpcd notification on Solaris client

[George Drew]

The messages are being logged by inetd. If you don't want inetd to  
log connections, then turn off inetd tracing (remove '-t' from inetd  
startup).


I wouldn't recommend turning off daemon.notice in syslog.conf. Makes  
it difficult to troubleshoot actual problems.


George

On Mar 28, 2007, at 8:58 AM, Evsyukov, Sergey wrote:


Thank you for hint.
Is connecting to bpcd by server every minute - correct behaviour of  
NB ?


C.


From: GAURAV RAKHEJA /SSTG/INFOTECH/BKC [mailto:[EMAIL PROTECTED] 
infotech.com]

Sent: Wednesday, March 28, 2007 4:42 PM
To: Evsyukov, Sergey
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] bpcd notification on Solaris client

Hi,

Try using the following commands:

cd /usr/openv/netbackup/bin
./bpcd -standalone

Hope things will work fine now.

Thanks & Regards,
Gaurav Rakheja,
Shared Services Technology Group,
ICICI Bank Ltd,
Netbackup Admin Team,
Zenith House, Mahalaxmi
Mumbai
+91-22-2490 6087
<>
<>


From: [EMAIL PROTECTED] [mailto:veritas-bu- 
[EMAIL PROTECTED] On Behalf Of Evsyukov, Sergey

Sent: Wednesday, March 28, 2007 3:26 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] bpcd notification on Solaris client

Hello,
is it possible to turn off  "notice" bpcd notifications on Solaris  
client (see below), or i need to exclude all daemon.notice  
notifications from syslogd.conf?


Thank you very much for help, Sergey

Mar 28 12:09:04 host1 inetd[5505]: [ID 317013 daemon.notice] bpcd 
[16763] from host2
Mar 28 12:11:05 host1 inetd[5505]: [ID 317013 daemon.notice] bpcd 
[18578] from host2
Mar 28 12:12:42 host1 inetd[5505]: [ID 317013 daemon.notice] bpcd 
[19853] from host2
Mar 28 12:14:23 host1 inetd[5505]: [ID 317013 daemon.notice] bpcd 
[24148] from host2
Mar 28 12:15:24 host1 inetd[5505]: [ID 317013 daemon.notice] bpcd 
[26436] from host2
Mar 28 12:17:00 host1 inetd[5505]: [ID 317013 daemon.notice] bpcd 
[27778] from host2
Mar 28 12:18:46 host1 inetd[5505]: [ID 317013 daemon.notice] bpcd 
[29438] from host2


"This e-mail message may contain confidential, proprietary or  
legally privileged information. It should not be used by anyone who  
is not the original intended recipient. If you have erroneously  
received this message, please delete it immediately and notify the  
sender. The recipient acknowledges that ICICI Bank or its  
subsidiaries and associated companies, (collectively "ICICI  
Group"), are unable to exercise control or ensure or guarantee the  
integrity of/over the contents of the information contained in e- 
mail transmissions and further acknowledges that any views  
expressed in this message are those of the individual sender and no  
binding nature of the message shall be implied or assumed unless  
the sender does so expressly with due authority of ICICI  
Group.Before opening any attachments please check them for viruses  
and defects."


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


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

Re: [Veritas-bu] Strange errors in netapp messages log after upgrade of nbu from 5.1 to 60MP2 -- diag gear

[George Drew]

Len,

This message means that you have some device in the path to your
tape drive that isn't happy with 16-byte CDBs (some scsi-3 commands).
This one in particular is the scsi-3 "WRITE ATTRIBUTE" command.

(Reference: http://t10.org/ftp/t10/drafts/spc4/spc4r04.pdf)

George

On Sat, 13 May 2006, Len Boyle wrote:


Good Day,

We upgraded a netbackup master running on solaris 9 from 5.1mp3 to 60MP2. This 
master runs ndmp backups on 6 R200's with fibre direct attached IBM LTO-2 tape 
drives. After the netbackup upgrade, with no changes with the tape drives, tape 
library or netapps we started to see the following messages in the 
/etc/messages file on the netapp. We are being told by netapp and symantec that 
this is a problem with scsi commands, but they report that they can not tell us 
what the offending scsi commands are, unless we hook up a sniffer.
So my question to this group, is Any hints on what one should  use to act as a 
sniffer for this scsi connection?

That is what company makes good sniffers, and what are the different features  
one should look for?

Thanks for any info you guys can throw this way.

Fri May 12 07:54:31 EDT [scsi.cmd.contingentAllegiance:error]: Device 3a.51: 
Contingent allegiance: cdb 0x8d.
Fri May 12 08:00:01 EDT [kern.uptime.filer:info]:   8:00am up 57 days, 18:59 
427592 NFS ops, 3947850238 CIFS ops, 9 HTTP ops, 0 DAFS ops, 0 FCP
ops, 0 iSCSI ops
Fri May 12 08:03:16 EDT [scsi.cmd.contingentAllegiance:error]: Device 3b.52: 
Contingent allegiance: cdb 0x8d.

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


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

RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1 MP3

[George Drew]

Well, frequency-based cleaning is up to you. Not recommended in an SSO
environment, as drive-in-use time is tracked on each media server, and
you will end up attempting to over-clean your drives. You'd have
to check with your drive vendor, but I know that a lot of drives will
ignore a cleaning tape if it doesn't think it needs cleaning, or if
it's too soon.

As I said before though, don't worry about those lights. Netbackup
checks tapealert on mount and dismount, and as long as you have a
cleaning tape configured that still has cleanings left, netbackup
will take of cleaning with no hassle. If you start seeing a lot of
media errors you might be having some problems with drive cleaning,
but mostly it just works.

George

On Fri, 3 Mar 2006, Greenberg, Brian wrote:


That's fantastic.  So I should probably do frequency based cleaning then
until I go to NBU 6.0?  The drives seem to need cleaning after about 500
or 600 hours of use.

Regards,
  Brian

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of George
Drew
Sent: Thursday, March 02, 2006 6:14 PM
To: Paul Keating
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1
MP3

The best thing to do (for nbu versions < 6.0) is to ignore those
lights. Those versions of netbackup only recognize two of the 48 or
so possible flags set on the tapealert log page, clean now and clean
periodic. The light on the front of the drive could get set for who
knows how many of the other possibilities (ask ADIC or IBM). Also,
the tapealert log page is a 'read and clear' log page, meaning if
something (the library) reads it before netbackup then netbackup will
never see that the flag was set, and take no action.

Netbackup 6.x will tell you which flag was set, and take action on
many of them.

George


On Mar 2, 2006, at 10:01 AM, Paul Keating wrote:


In the 18 months since my two L700's have been in production, for the
first 6 months, one library was doing nightly backups and daily
vaulting, then both libraries in use with Inline tape copy for the
last
12 months, I've used 1 tape in the first library (25 cleanings) and
maybe a dozen cleans in the second library.

Paul


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Greenberg, Brian
Sent: March 2, 2006 10:42 AM
To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and
NBU 5.1 MP3


Ahhh, I misread your message.  So you were essentially doing
frequency
based cleaning.  Yes, that's my other option.  Fortunately, the
lights
on our drives only come on about after 800 hours of use,
approximately.

I still have a ticket open with Veritas.  We're trying to see if the
cleaning count decrements at all on the tapes since tpconfig's report
isn't telling me if the drive gets cleaned when it looks like
from time
to time it does, so I'm looking at that report every day too.

So what libraries are you using?

Regards,
   Brian

-Original Message-
From: WEAVER, Simon [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 9:36 AM
To: Greenberg, Brian; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1
MP3


Hi Brian
No, I never waited for the lights, because as mentioned, the
lights seem
to
come on almost after EVERY backup.

What I done, was within 3.4, checked how many times the drive was
used
and
approx once per month used TPClean.

ADIC support was totally useless, blaming the Netbackup
Software But
how
could it be the software if the drive is telling me it needs
cleaning??

I had a schedule to run TPCLEAN every month Brian - when I
say "manual",
what I meant was "not controlled by Netbackup".

Most of my Netbackup implementation is all automated - I only
ever look
at
the product or drives if I get an alert.

Thankfully, I no longer use ADIC :-)

Simon Weaver
Technical Support
Windows Domain Administrator

EADS Astrium
Tel: 02392-708598

Email: [EMAIL PROTECTED]



-Original Message-
From: Greenberg, Brian [mailto:[EMAIL PROTECTED]
Sent: 02 March 2006 15:33
To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1
MP3


So your cleaning process is completely manual?  You waited to see
cleaning
lights on the drives and then cleaned them?

That's what I've been doing, but for us, that's only a
temporary fix. My
motto, automate everything and then put the checks in place
to make sure
it's running properly.

Regards,
   Brian

-Original Message-
From: WEAVER, Simon [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 9:25 AM
To: Greenberg, Brian; 'veritas-bu@mailman.eng.auburn.edu'
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2

Re: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1 MP3

[George Drew]

The best thing to do (for nbu versions < 6.0) is to ignore those  
lights. Those versions of netbackup only recognize two of the 48 or  
so possible flags set on the tapealert log page, clean now and clean  
periodic. The light on the front of the drive could get set for who  
knows how many of the other possibilities (ask ADIC or IBM). Also,  
the tapealert log page is a 'read and clear' log page, meaning if  
something (the library) reads it before netbackup then netbackup will  
never see that the flag was set, and take no action.


Netbackup 6.x will tell you which flag was set, and take action on  
many of them.


George


On Mar 2, 2006, at 10:01 AM, Paul Keating wrote:


In the 18 months since my two L700's have been in production, for the
first 6 months, one library was doing nightly backups and daily
vaulting, then both libraries in use with Inline tape copy for the  
last

12 months, I've used 1 tape in the first library (25 cleanings) and
maybe a dozen cleans in the second library.

Paul


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Greenberg, Brian
Sent: March 2, 2006 10:42 AM
To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and
NBU 5.1 MP3


Ahhh, I misread your message.  So you were essentially doing  
frequency
based cleaning.  Yes, that's my other option.  Fortunately, the  
lights

on our drives only come on about after 800 hours of use,
approximately.

I still have a ticket open with Veritas.  We're trying to see if the
cleaning count decrements at all on the tapes since tpconfig's report
isn't telling me if the drive gets cleaned when it looks like
from time
to time it does, so I'm looking at that report every day too.

So what libraries are you using?

Regards,
   Brian

-Original Message-
From: WEAVER, Simon [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 9:36 AM
To: Greenberg, Brian; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1
MP3


Hi Brian
No, I never waited for the lights, because as mentioned, the
lights seem
to
come on almost after EVERY backup.

What I done, was within 3.4, checked how many times the drive was  
used

and
approx once per month used TPClean.

ADIC support was totally useless, blaming the Netbackup
Software But
how
could it be the software if the drive is telling me it needs
cleaning??

I had a schedule to run TPCLEAN every month Brian - when I
say "manual",
what I meant was "not controlled by Netbackup".

Most of my Netbackup implementation is all automated - I only
ever look
at
the product or drives if I get an alert.

Thankfully, I no longer use ADIC :-)

Simon Weaver
Technical Support
Windows Domain Administrator

EADS Astrium
Tel: 02392-708598

Email: [EMAIL PROTECTED]



-Original Message-
From: Greenberg, Brian [mailto:[EMAIL PROTECTED]
Sent: 02 March 2006 15:33
To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1
MP3


So your cleaning process is completely manual?  You waited to see
cleaning
lights on the drives and then cleaned them?

That's what I've been doing, but for us, that's only a
temporary fix. My
motto, automate everything and then put the checks in place
to make sure
it's running properly.

Regards,
   Brian

-Original Message-
From: WEAVER, Simon [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 9:25 AM
To: Greenberg, Brian; 'veritas-bu@mailman.eng.auburn.edu'
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1
MP3


Brian
My ADIC would not communicate with Netbackup - manual intervention  
was

the
only way. I had a rule that NBU recognised the cleaning tape and was
able to
use TPCLEAN - but it was no big deal.

Simon Weaver
Technical Support
Windows Domain Administrator

EADS Astrium
Tel: 02392-708598

Email: [EMAIL PROTECTED]



-Original Message-
From: Greenberg, Brian [mailto:[EMAIL PROTECTED]
Sent: 02 March 2006 14:56
To: WEAVER, Simon
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1
MP3


Fair guess but no.  Actually, ADIC has nothing to do with it.
 It's the
tape
alert that comes from the drive itself.  I have hardware/library
frequency
based cleaning off so that NBU can clean when it gets the request  
from

the
drive.  Barcode rules also wouldn't have anything to do with it  
either

because they are only for importing media/inventorying media in the
library.

Regards,
   Brian

-Original Message-
From: WEAVER, Simon [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 1:44 AM
To: Greenberg, Brian; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Cleaning issues: LTO-3/ADIC i2k and NBU 5.1
MP3


Hi Brian
I had an LTO1 ADIC, and to be very truthful, I ended up doing it
manually,
because the tape request simply did not interact with Netbackup

RE: [Veritas-bu] recommended LTO2 drive fragment size?

[George Drew]

I would recommend that 2Gb is probably not a large enough fragment size, as 
that's barely
long enough for the drive to get up to speed. Figure 70MB/sec transfer rate 
(optimally),
and your drive is stopping every 4 minutes (roughly). Add multi-plexing and that
could be even more often, not to mention that it makes very little difference 
any more.
For single-stream backups nbu knows where to go to get a file for a 
single-file-restore,
and for multi-plexed images nbu needs to read the entire image anyway.

Admittedly it's unlikely that you're going to see 70MB/sec, but it's still not 
very much
time.

George


On Wed, 25 Jan 2006, Casoli Marco wrote:


Hello

Look at the Veritas-Document #262724 (How to optimally performance-tune
systems with IBM Linear Tape-Open 2 drives)
Notice: You must have enough physical und shared memory on your system.

And your question: We use the follow fragmentsize (2000 MB)

Marco Casoli
IT-Systemspezialist
Storage/Backup


Genossenschaft Migros Ostschweiz
Finanzen/Informatik
Industriestrasse 47
CH-9201 Gossau


 _

Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Barber,
Layne (Contractor)
Gesendet: Mittwoch, 25. Januar 2006 14:45
An: veritas-bu@mailman.eng.auburn.edu
Betreff: [Veritas-bu] recommended LTO2 drive fragment size?


Any recommendations for the fragment size when using LTO2 drives? Any
other tuning tips for a 5.1 setup using LTO2.



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