toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

ender: owner-toasters@mathworks.com
by Darren Dunham 13 Mar '01

13 Mar '01

> > Please correct me. > > When ipv4 networik interfaces are initialized by /etc/init.d/network thru > /etc/hostname.xyz, First of all, we have to be sure that we're talking about Solaris 8 here. It appears the startup scripts have had some name changes... > 1. if /etc/hostname.zyz has more than one lines, each line will be > configured for that interface with > /sbin/ifconfig xyz inet param-string > with param-string is the content of the corresponding line. This leads to > the interface is not up, except param-string has the correct format & > contains the keyword "up" > ( for example, the line contains "some-valid-host-name up" ) Sure.. > 2. If /etc/hostname.xyz.has only one line, the interface will be init as > /sbin/ifconfig xyz inet param-string netmask + broadcast + up. > In this case, the param-string is often the hostname. > --- > > So if /etc/hostname.xyz has 3 lines, we will have > /sbin/ifconfig xyz inet line1 > /sbin/ifconfig xyz inet line2 > /sbin/ifconfig xyz inet line3 Actually, it would be... /sbin/ifconfig xyz inet line1 /sbin/ifconfig xyz inet line2 /sbin/ifconfig xyz inet line3 netmask + broadcast + up *unless* the last line is blank. If the last line is blank then it becomes... /sbin/ifconfig xyz inet line1 /sbin/ifconfig xyz inet line2 Line 3 is dropped entirely.. > Why do we need this multi-line process like this ? Good question. I couldn't find a particular bug or patch in sunsolve that mentioned this... Also, this multi-line stuff appears to be new in Solaris 8. -- Darren Dunham ddunham(a)taos.com Unix System Administrator Taos - The SysAdmin Company Got some Dr Pepper? San Francisco, CA bay area < How are you gentlemen!! Take off every '.SIG'!! >

1 0

RE: LTO support?
by Stringer, Douglas 12 Mar '01

12 Mar '01

Don't let the LTO manufactures hear you say that. With different driver support, media, ISV certification requirements and specifications that are anything but similar to DLT, the only common item these formats share is that they are 'linear' tape formats. NetApp will be supporting LTO in the late summer/early fall timeframe. Regards, Doug Stringer -----Original Message----- From: ryanb [mailto:ryanb@enteract.com] Sent: Monday, March 12, 2001 12:58 PM To: Moshe Linzer Cc: toasters(a)mathworks.com Subject: Re: LTO support? On Mon, Mar 12, 2001 at 09:17:57PM +0200, Moshe Linzer wrote: > Does anyone know when LTO will be supported on the filer? I have two > 760's, and we are shopping around for a backup library. I am hesitant > to go with LTO at this point, but management likes the numbers. Can > anyone share experience or opinions on LTO drives or libraries? Most LTO equipment is identical to DLT equipment, only with a different tape drive. In this respect, the LTO drives will perform identically, or so I'd like to think. ;) Please let me know if I'm wrong here. - ryan

2 1

Re: getting dump messages into messages file
by Steve Kappel 12 Mar '01

12 Mar '01

Jeffrey Krueger wrote: >Moshe: You can create the directory "ndmp" in your netbackup logs directory >(ours is /usr/openv/netbackup/logs, not sure about yours) on the NBU server >to cause it to create the debug logs Steve mentioned. Be forewarned that >they get big fast, and that simultaneous dump processes output is >intermixed forcing you to match the PID on each line to the bptm process >for the backup you are interested in. NBU NDMP debug info is also >intermixed, so you'll want to look for lines that match this: > ><date> <time> [<bptm PID>]-Log:<dump/restore output from filer> By default the ndmp logs should only have error messages. But avrd polls all UP and free devices every 15 seconds or so and not having a NDMP tape mounted results in NDMP_IO_ERR for that. To get more info in there you need a numeric value in the file /usr/openv/volmgr/database/ndmp_debug If you use 65535 it will fill your disk quickly with lots of stuff you aren't interested in. (Not to mention slow things down.) The value is actually a mask constructed of the bits defined in the ndmp.org SDK. I have never tried it but you might get a value of 8192 to put log entries in there without adding a lot of other stuff. If it doesn't do that... like I said, this is an undocumented/unsupported log :) __________________________________________________________________________ Steve Kappel steve.kappel(a)veritas.com VERITAS Software steve.kappel(a)iname.com (Personal)

2 1

RE: LTO support?
by Collie, Michael 12 Mar '01

12 Mar '01

Moshe, The LTO technology promises performance of up to 30Mb/s with 2:1 compression. This performance far exceeds DLTs, SDLT, ATI-2 and 9840s. The form factor for LTO (Ultrium) is different for today's tape drives. It may be some time before library vendors integrate the LTO technology into their products. NetApp support for LTO is slated for 4th quarter of 2001. ---Original Message----- From: ryanb [mailto:ryanb@enteract.com] Sent: Monday, March 12, 2001 12:58 PM To: Moshe Linzer Cc: toasters(a)mathworks.com Subject: Re: LTO support? On Mon, Mar 12, 2001 at 09:17:57PM +0200, Moshe Linzer wrote: > Does anyone know when LTO will be supported on the filer? I have two > 760's, and we are shopping around for a backup library. I am hesitant > to go with LTO at this point, but management likes the numbers. Can > anyone share experience or opinions on LTO drives or libraries? Most LTO equipment is identical to DLT equipment, only with a different tape drive. In this respect, the LTO drives will perform identically, or so I'd like to think. ;) Please let me know if I'm wrong here. - ryan

2 1

LTO support?
by Moshe Linzer 12 Mar '01

12 Mar '01

Does anyone know when LTO will be supported on the filer? I have two 760's, and we are shopping around for a backup library. I am hesitant to go with LTO at this point, but management likes the numbers. Can anyone share experience or opinions on LTO drives or libraries? Thanks, Moshe

3 2

RE: getting dump messages into messages file
by Traitel, Eyal 12 Mar '01

12 Mar '01

You can turn on our own NDMP logging using: ndmpd debug 50 You can control logging only to a file by turning off logging to console ndmpd debug screen This will create files called /etc/ndmplog*, which contains much more than the dump messages, but you can obviously grep it by "dump"... I do not know if it has any performance issues on the dump itself though. Hope it helps, Eyal. ---------------------------------------------------------------------- eTraitel - I'm the new eBuzzword around !!! ---------------------------------------------------------------------- Eyal Traitel - Filer Escalation Engineer CNA, MCSE, CSA, NetApp CA Network Appliance BV Holland Office Center Kruisweg 799b 2132 NG, Hoofddorp The Netherlands Office: +31 23 567 9685 Cellular: +31 6 5497 2568 Email: eyal(a)netapp.com ---------------------------------------------------------------------- Get answers NOW! - NetApp On the Web - http://now.netapp.com ---------------------------------------------------------------------- -----Original Message----- From: Moshe Linzer [mailto:Moshe.Linzer@nsc.com] Sent: Monday, March 12, 2001 11:40 AM To: Stephen Manley Cc: toasters(a)mathworks.com Subject: Re: getting dump messages into messages file Stephen Manley wrote: > For now, you either want to capture dump logs by running > via rsh, or if you use an NDMP client, they generally > capture the dump messages in their logs. Does anyone know how to see the NDMP dump output messages from within Legato or Veritas? We have tested both products, but neither allowed us to view the NDMP dump messages like we do in Budtool. We checked all the logs, but maybe there is a logging option that needs to be turned on? Moshe -- ---------------------------------------------------------------------------- - Moshe Linzer | On the Internet, Unix Systems Manager | National Semiconductor, Israel | nobody knows you're a moron. Phone: 972-9-970-2247 | Fax: 972-9-970-2001 | - Network Magazine Email: moshel(a)nsc.com | ---------------------------------------------------------------------------- -

2 1

logging cifs deletes on F760
by nick.mayrath＠webmd.net 12 Mar '01

12 Mar '01

Is it possible to log what user is deleting what files on an F760 running 5.3.6r2 and CIFS only? Nick Mayrath ExpressBill, Inc. 800-453-8439 ext. 216

1 0

Re: getting dump messages into messages file
by Steve Kappel 12 Mar '01

12 Mar '01

Moshe Linzer wrote: >Stephen Manley wrote: > >> For now, you either want to capture dump logs by running >> via rsh, or if you use an NDMP client, they generally >> capture the dump messages in their logs. > >Does anyone know how to see the NDMP dump output messages from within Legato or >Veritas? We have tested both products, but neither allowed us to view the >NDMP dump messages like we do in Budtool. We checked all the logs, but maybe >there is a logging option that needs to be turned on? Current releases of NetBackup NDMP put these messages into the NDMP debugging log which isn't externally supported. Starting with the next major release (fall) they will go into the bptm log and possibly the user log. __________________________________________________________________________ Steve Kappel steve.kappel(a)veritas.com VERITAS Software steve.kappel(a)iname.com (Personal)

1 0

getting dump messages into messages file
by neil lehrer 12 Mar '01

12 Mar '01

hi, i noticed that dump messages were not being recorded in the messages file. i did not have a syslog.conf file so i created one like this: *.* /etc/messages *.* /dev/console no change. am i doing something wrong? f760 ontap 5.36r2. thanks. -- regards

6 8

How are NDMP incrementals so fast?
by Tom "Mad Dog" Yergeau 10 Mar '01

10 Mar '01

Obviously from all the NDMP messages I'm sending this week, we just started using NDMP. :-) I just saw the results of our first incremental NDMP backups and I was flabbergasted at how fast they ran. I even double-checked the logs to make sure it actually was backing stuff up. When doing an incremental backup over CIFS, it would take about three hours to go through about 200 GB of stuff (1.8 million inodes). Doing it with NDMP, it takes 20-30 minutes. That's quite an improvement. It's obvious that when doing an incremental NDMP backup, there is something going on that allows the filer to determine extremely quickly which files have changed since the full backup. Can someone tell us what's going on? Does the filer keep a log of stuff that's changed? Is this just something WAFL is really good at? Thanks! MD

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters