toasters

toasters@lists.teaparty.net

13520 discussions

qtrees
by Deena Matarazzo 10 Aug '01

10 Aug '01

I have a qtree on a directory and would also like to set some limits on subdirectories within that directory. Is there anyway to do this?

2 1

RE: Direct attaching SCSI tape drives to 760's
by Parsons, Steve 10 Aug '01

10 Aug '01

Andrew, Network Appliance recommends against hot-plugging of SCSI tape and library devices. The 68-pin connector is not defined as a hot-plug connector and does not provide electrical safety for either the adapter or the device. Most of the time, a hot-plug won't hurt anything, but on occasion you'll blow a transceiver. The SCA connector used on disk drives is designed to assure a square connection with ground mating occurring first. The 68-pin connector on tape drives is not so designed. Steve -----Original Message----- From: Andrew Toon [mailto:andrew.toon@tracegroup.com] Sent: Thursday, August 09, 2001 3:58 AM To: 'Paul Letta' Cc: 'toasters(a)mathworks.com' Subject: RE: Direct attaching SCSI tape drives to 760's I have had to remove a d6irectly attached tape drive a few time on my F740. It hasn't caused any problems. However when I attach a new drive it will only recognise it if I do a reboot. I don't know if there's something similar to the Solaris "drvconfig" command but if not it would be a great feature to have. Andrew Toon Technical Services Manager Trace Computers Plc -----Original Message----- From: Paul Letta [ mailto:letta@jlab.org <mailto:letta@jlab.org> ] Sent: 07 August 2001 17:18 To: toasters(a)mathworks.com Subject: Direct attaching SCSI tape drives to 760's Does anybody have any comments in regard to direct attaching SCSI drives 760's ? My concern is what happens when the drives fail ? I seem to have a drive failure rate of 3 or 4 a year. Currently I do not direct attach, so replacing them is no problem. But what happens to the filers when you remove a SCSI tape device hot ? Can you reattach a new one without rebooting the filer ? I do not think my environment would stand for a filer reboot each time a tape drive fails, but I really do not want to live with the 4MB/Sec I get for backups over the network now. Any thoughts? Thanks, Paul Disclaimer This email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of Trace Computers PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this mail is strictly prohibited

1 0

jumbo frames
by Zekeriya Eskiocak 10 Aug '01

10 Aug '01

Hi All, Anybody has experience with using Jumbo Frames in Netapp F740-Oracle8.0&IBM AIX environment? Any recommendation is appreciated. Thanks Zekeriya Eskiocak System Engineer Prolink Services Kayisdagi Cad. No 105 Kucukbakkalkoy 81120 Istanbul-TURKIYE- Work:+90 216 573 73 00 (Ext.107) Mobile:+90 532 761 80 69

1 0

Re: vif's and failover
by mds＠gbnet.net 09 Aug '01

09 Aug '01

Sun's Cluster and the non-clustered IPMP use simple ICMP echo between the active and back-up interfaces to evaluate their health and decide when it's appropriate to fail over. In fact I believe they send an ICMP echo to the appropriate network broadcast address, so that, as long as the switch, a router or a client machine responds failover doesn't take place, and as soon as the network goes suspiciously quiet a failover is undertaken whether the ethernet link is still detected or not. As has been said, it's a fairly basic precaution in a clustered environment to trust as little as possible and to examine the actual service you care about as closely as possible. I also don't believe this is patented, or rocket science. On Thu 9 Aug, 2001, Sam Cramer <cramer(a)netapp.com> wrote: > > Does anyone have any experience with this? Can someone confirm or deny > > the failover in the event of loss of dataflow, but not loss of link? > > The vif code detects the loss of link status, not the loss of dataflow. > Only the loss of link status will cause a failover. > > Sam > >-- End of excerpt from Sam Cramer -- -Mark ... an Englishman in London ...

1 0

Re: vif's and failover
by Sam Cramer 09 Aug '01

09 Aug '01

> Does anyone have any experience with this? Can someone confirm or deny > the failover in the event of loss of dataflow, but not loss of link? The vif code detects the loss of link status, not the loss of dataflow. Only the loss of link status will cause a failover. Sam

2 1

vif's and failover
by Jordan Share 09 Aug '01

09 Aug '01

So, we had a switch fail today. It failed in such a way that link was maintained on the ports, it just didn't pass any packets. When this happened, the vif that I had created on our filer did not switch over to the backup link (on another switch). I initially thought it was because I hadn't set it to check to make sure that traffic was actually flowing out the interfaces. However, then I couldn't find anywhere to actually do that. What's the deal here? Did I totally miss something? How exactly does failover work, anyway? Thanks, Jordan

2 3

Networker backup using cifs
by David C Baumgardner 09 Aug '01

09 Aug '01

I have been using legato Networker 6.0.1 running on a Windows NT box to back up my NetApp 720. The tape drive is a DLT8000 attached to the NT box. I mapped the c$ share on the Filer and put it in the Networker client as "\\oineap01\c$". oineap01 being the name of the filer. Full backup was taking 4 hours for 40 gb of data. Now that has changed to 12 hours with the following error messages; 08/09/01 08:35:33 nsrexecd: failed to write NUL handshake on 232: errno 154, Connection reset by peer 08/09/01 08:35:55 savegrp: oipc4190.owens-ill.com:\\oineap01\c$ abandoned. 08/09/01 08:35:55 savegrp: oipc4190.owens-ill.com:\\oineap01\c$ will retry 0 more time(s) 08/09/01 08:38:31 nsrd: savegroup alert: Default completed, 1 client(s) (oipc4190.owens-ill.com Failed) * oipc4190.owens-ill.com:\\oineap01\c$ has been inactive for 35 minutes since Thu Aug 09 08:00:33 2001. * oipc4190.owens-ill.com:\\oineap01\c$ is being abandoned by nsrexec. 08/09/01 08:38:32 nsrd: runq: NSR group Default exited with return code 1. It still goes on and completes the backup and I can recover files from that backup with no problem. Has anyone ran into this and /or know what is going on? David Baumgardner CAD/CAM Administrator Container Engineering 419.247.8274

1 0

RE: Direct attaching SCSI tape drives to 760's
by Andrew Toon 09 Aug '01

09 Aug '01

I have had to remove a d6irectly attached tape drive a few time on my F740. It hasn't caused any problems. However when I attach a new drive it will only recognise it if I do a reboot. I don't know if there's something similar to the Solaris "drvconfig" command but if not it would be a great feature to have. Andrew Toon Technical Services Manager Trace Computers Plc -----Original Message----- From: Paul Letta [mailto:letta@jlab.org] Sent: 07 August 2001 17:18 To: toasters(a)mathworks.com Subject: Direct attaching SCSI tape drives to 760's Does anybody have any comments in regard to direct attaching SCSI drives 760's ? My concern is what happens when the drives fail ? I seem to have a drive failure rate of 3 or 4 a year. Currently I do not direct attach, so replacing them is no problem. But what happens to the filers when you remove a SCSI tape device hot ? Can you reattach a new one without rebooting the filer ? I do not think my environment would stand for a filer reboot each time a tape drive fails, but I really do not want to live with the 4MB/Sec I get for backups over the network now. Any thoughts? Thanks, Paul Disclaimer This email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of Trace Computers PLC. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this mail is strictly prohibited

1 0

Configuring Veritas Business Server with NDMP option on a HP9000/ J6000 part II
by Schepers, Jan 09 Aug '01

09 Aug '01

Hello all, Of course my description is not complete witnessing the fact that I received a number of questions wrt the configuration. I have problems configuring 0 Veritas Netbackup Business Server 3.4GA with an 0 NDMP option running on a 0 HP9000/J6000 (HPUX 11.00) as management server to backup a 0 F850 running Ontap 6.0.1 that has a 0 HP C7145-8000 DLT8K library connected to it. When I try to do a "robot inventory", I get the error message "robot inventory failed: Unable to open robotic path (201)" At the same time the filer console shows the following messages: Wed Aug 8 18:20:09 CES [Java Thread:warning]: Ndmpd25: Top level IOException Wed Aug 8 18:20:09 CES [Java Thread:warning]: Ndmpd25: IO exception: Socket closed. What simple thing did I do wrong ? regards, YS Output of some commands: root# telnet waal Trying... Connected to waal. Escape character is '^]'. Local flow control off Password: waal> version NetApp Release 6.0.1: Sat Dec 2 00:46:34 PST 2000 waal> Connection closed by foreign host. waal> ndmpd status ndmpd ON. No ndmpd sessions active. waal> sysconfig -m Media changer (5b.0) HP C7145-8000 mc0 - media changer device waal> sysconfig -t Tape drive (5b.1) Quantum DLT8000 rst0l - rewind device, format is: 81633 bpi 40 GB (w/comp) nrst0l - no rewind device, format is: 81633 bpi 40 GB (w/comp) urst0l - unload/reload device, format is: 81633 bpi 40 GB (w/comp) rst0m - rewind device, format is: 85937 bpi 35 GB nrst0m - no rewind device, format is: 85937 bpi 35 GB urst0m - unload/reload device, format is: 85937 bpi 35 GB rst0h - rewind device, format is: 85937 bpi 50 GB (w/comp) nrst0h - no rewind device, format is: 85937 bpi 50 GB (w/comp) urst0h - unload/reload device, format is: 85937 bpi 50 GB (w/comp) rst0a - rewind device, format is: 85937 bpi 70 GB (w/comp) nrst0a - no rewind device, format is: 85937 bpi 70 GB (w/comp) urst0a - unload/reload device, format is: 85937 bpi 70 GB (w/comp) root# /usr/openv/volmgr/bin/set_ndmp_attr -verify waal Connecting to host "waal" as user "root"... Waiting for connect notification message... Opening session with NDMP protocol version 2... Host info is: host name "waal" os type "NetApp" os version "NetApp Release 6.0.1" host id "0033590107" host supports TEXT authentication host supports MD5 authentication Getting MD5 challenge from host... Logging in using MD5 method... Login was successful Opening SCSI device "mc0"... Setting SCSI target controller 0 id 0 lun 0... Inquiry result is "HP C7145-8000 2260c060p.04" Opening SCSI device "spt0"... Setting SCSI target controller 4 id 0 lun 0... Inquiry result is "HP C7145-8000 2260c060p.04"

1 0

Re: restore is very expensive
by Steve Losen 08 Aug '01

08 Aug '01

Thanks to Emmett Hogan, who I think was too shy to post to the whole list. Emmett suggested that I try smbclient, which just so happens to be installed on the unix NFS client where I create the accounts. With smbclient I can make a CIFS connection and get a command line prompt. At the prompt I can type "setmode filename +h" and this turns on the DOS hidden bit for filename. I can feed a file of commands to smbclient, so I think I will modify my bulk account script to use tar, which will be much faster than restore. As I build the accounts I will create a file of smbclient commands to run to set the DOS hidden bits. The file will look like this: setmode a/ab/abc9d/.forward +h setmode a/ab/abc9d/.pinerc +h setmode d/de/def8g/.forward +h ... etc. Then I can run smbclient like this: smbclient //filer/home -U root < command-file I get prompted for the password once and then smbclient sets all the DOS hidden bits. For the curious, we are authenticating CIFS users with a unix NIS database, so all of our volumes have unix permissions. You must authenticate with a domain controller if you want NT or mixed style permissions. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

1 0

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