toasters

toasters@lists.teaparty.net

13531 discussions

comments on netapp filers cifs performance
by neil lehrer 12 Sep '00

12 Sep '00

hi, i'd appreciate hearing what you think of the cifs performance on netapp filers. i am considering a f760, our wkstations are primarily nt 4.0 sp5. thanks --

2 2

RE: AIT libraries
by Premanshu Jain 12 Sep '00

12 Sep '00

Yes Qualstar's are really good. We are implementing them now. We could dump 105 GB (Unix format data) on a AIT2 tape. This compression depends on the type of data you are backing up. The CIFS data blocks dumped only upto 60-70 GB per tape. -----Original Message----- From: Larry Goodman [mailto:Larry.Goodman@Intense3D.com] Sent: Tuesday, September 12, 2000 6:45 AM To: toasters(a)mathworks.com Subject: AIT libraries If any of you kind toaster'ites have experience with AIT2 tape libraries, I'd like to here your advice about the different brands available. I've been researching these devices and they all seem to claim pretty much the same specs (duh, they're all using the same Sony drive!). I'm particularly interested in the durability of the robotics. I've been looking at libraries from Spectra Logic, Qualstar, Adic and Overland Data, usually providing from 12 to 24 slots (single drive). The Qualstar folks claim that they're the only supplier that uses a "lead-screw" design instead of belts for better reliability. Any comments? Thanks, Larry.Goodman(a)Intense3d.com

1 0

RE: 2 volumes or 1
by Walters, Mike 11 Sep '00

11 Sep '00

You don't mention what size drives they are (9/18/36GB). As a rule, however, I would suggest that you are correct in thinking you would be better off combining disks to make a single volume. You can use qtrees to segragate data (& give more control if some is NFS & some CIFS, for example). I believe that your 'heavy reads & writes' will benefit from the larger raid group. You would obviously need to destroy vol1 before adding disks to vol0. Just one minor point - I presume you do have a spare disk as well - if not, & you have a disk fail, the filer will squawk at hourly intervals complaining, then if you don't add a drive, shutdown after 24 hours (options raid.timeout defaults to 24 [hours] to configure this) on the basis that you don't want to run degraded for any significant time. Cheers Mike UK SE -----Original Message----- From: Pesce, Nicholas (FUSA) [mailto:Nicholaspesce@firstusa.com] Sent: 11 September 2000 21:30 To: 'toasters(a)mathworks.com' Subject: 2 volumes or 1 Gentlemen, I need your opinion on a creation I am about to unleash on our unsuspecting production site where I work. I currently have a 740 filer with 2 shelves and 7 disks. 3 disks are in the first shelf and configured for volume 0 root volume 4 disks are inthe second shelf and configured for volume 1 Now, since I didn't put this box together. I was wondering if it is better to make all of these disks one volume. There are heavy reads and writes to the volume1, but I don't know if having a heavily used volume combined with root functions will kill my performance. Besides this will make a larger volume for more distributed writes (8 total disks versus 4). Also I will be saving 1 disk of data space because I won't need the second parity disk. Addition information is that they are fibre channel shelves (of course). And that the data is not important (washed away daily). Assuming that the root volume functions do not critically affect my box (and I don't believe that they do, as most of it is running from memory) I believe my choice is correct. Just wondering if you guys agree with this hypothesis or not. Nicholas Pesce Internet Production Services Phone: 847 488-6384 Pager: 888 785 3455 Fax: 847 488 3434

1 0

RE: Restricting CIFS
by Hawley, Rob 11 Sep '00

11 Sep '00

The WINS server must be able to ping each interface on the filer that you want to register with WINS. In situations like you describe where you have a private network that should not be registered with WINS, then you need to turn off WINS registration on that interface. You do that by adding a -wins parameter to the ifconfig for the interface. ~~~~~~~~~~~~~~~~~ mailto: hawleyr(a)netapp.com US Mail: Network Appliance Inc. Windows Networking Engineering 495 E Java Dr Phone/pager: 408-822-6661 Sunnyvale, CA 94089 http://www.netapp.com -----Original Message----- From: Graydon Dodson [mailto:grdodson@lexmark.com] Sent: Monday, September 11, 2000 1:09 PM To: toasters(a)mathworks.com Subject: Restricting CIFS Anyone know of a way to restrict CIFS on a filer to certain network interfaces. Specificaly we need to turn it off on one interface. This interface is to a private net and we keep getting: No WINS servers are responding; still trying warnings clogging up the log. We want CIFS on the other interfaces and it can easily contact the wins servers on those nets. Thanks. Graydon Dodson grdodson(a)lexmark.com Lexmark International Inc.

1 0

RE: Restricting CIFS
by Benn, Paul 11 Sep '00

11 Sep '00

you can disable wins on just that interface by entering: filer> ifconfig <interface> -wins -----Original Message----- From: Graydon Dodson [mailto:grdodson@lexmark.com] Sent: Monday, September 11, 2000 1:09 PM To: toasters(a)mathworks.com Subject: Restricting CIFS Anyone know of a way to restrict CIFS on a filer to certain network interfaces. Specificaly we need to turn it off on one interface. This interface is to a private net and we keep getting: No WINS servers are responding; still trying warnings clogging up the log. We want CIFS on the other interfaces and it can easily contact the wins servers on those nets. Thanks. Graydon Dodson grdodson(a)lexmark.com Lexmark International Inc.

1 0

Restricting CIFS
by Graydon Dodson 11 Sep '00

11 Sep '00

Anyone know of a way to restrict CIFS on a filer to certain network interfaces. Specificaly we need to turn it off on one interface. This interface is to a private net and we keep getting: No WINS servers are responding; still trying warnings clogging up the log. We want CIFS on the other interfaces and it can easily contact the wins servers on those nets. Thanks. Graydon Dodson grdodson(a)lexmark.com Lexmark International Inc.

2 1

RE: Restricting CIFS
by Krause, Oliver 11 Sep '00

11 Sep '00

You cannot restrict CIFS to an interface. you get rid of the error message if you configure the private interface with the "-wins" option. Then the filer doesn't try to register this ip on the wins server. Oliver > -----Original Message----- > From: Graydon Dodson [mailto:grdodson@lexmark.com] > Sent: Montag, 11. September 2000 22:09 > To: toasters(a)mathworks.com > Subject: Restricting CIFS > > > > Anyone know of a way to restrict CIFS on a filer to certain > network interfaces. > Specificaly we need to turn it off on one interface. This > interface is to > a private net and we keep getting: > > No WINS servers are responding; still trying > > warnings clogging up the log. We want CIFS on the other > interfaces and it can > easily contact the wins servers on those nets. > > > Thanks. > > Graydon Dodson > grdodson(a)lexmark.com > Lexmark International Inc. >

1 0

RE: creating a share with vba on a filer
by Uren, Jim 11 Sep '00

11 Sep '00

Hi Ulrich, from a DOS prompt, typing net helpmsg 2116 reveals this-- The device or directory does not exist. EXPLANATION You specified an unknown device or directory. ACTION Check the spelling of the device or directory name. so checking the pathname as suggested below seems like a good idea. as I recall, if you wish to use the "vol" form of the filename, you will want to put C$ in the pathname, such as: \\filer\c$\vol\vol0\sharename\directory but the \\filer\share\directory format should work just fine. check to see if c:\> dir \\cobfile01\users$ succeeds or not for example. Jim U > -----Original Message----- > From: Hawley, Rob [mailto:rob.hawley@netapp.com] > Sent: Monday, September 11, 2000 7:31 AM > To: 'Ulrich Neumann'; toasters(a)mathworks.com > Subject: RE: creating a share with vba on a filer > > > Your program looks correct. We do support using level 502 to > add a share. > Please confirm a couple of points that could be the source of > the problem: > > 1. The user running the script is a member of either the > filer's Administrators > group or is a member of Power Users. That is required for NT > compatible > security. > 2. That the path vol\nt01\users is the correct physical path > to where the user's > directory should be created. That is there are no other > directories in the path. > > If neither of these resolve your problem, then please contact > NetApp customer > support. They will need a packet trace of this exchange and a > cifs sessions -s > of the user attempting to execute the script. CS can help you > if you are > unfamiliar with how to get a packet trace. > > ~~~~~~~~~~~~~~~~~~~ > mailto: hawleyr(a)netapp.com US Mail: Network Appliance Inc. > Windows Networking Engineering 495 E Java Dr > Phone/pager: 408-822-6661 Sunnyvale, CA 94089 > http://www.netapp.com > > > -----Original Message----- > From: Ulrich Neumann [mailto:ulrich.neumann@brose.de] > Sent: Monday, September 11, 2000 2:01 AM > To: toasters(a)mathworks.com > Subject: creating a share with vba on a filer > > << File: ShareErr2116Filer.txt >> we just turned our > user-home-shares from a > nt-server to a filer. > for creating new user-shares, we use a selfmade program in vb. > unfortunately this program woun't work now with the filer. > > neither "c:\vol\nt01\users\username" nor "\\cobfile01\users$\username" is working. there's always the error 2116.(see sub makeshare in attached code) is there anybody out there who has a good idea to solve this problem? greetings from brose GmbH & Co KG Client-Server-Technologien Ulrich Neumann

1 0

Re: Deleting snapshot
by Steve Kappel 11 Sep '00

11 Sep '00

Hi Stephen, Thanks for jumping in here and ending this thread. >It definitely does not seem appropriate to blame >the NDMP client. It is a filer specific issue. >Apologies to Steve Kappel. But I bet his >blood pressure wasn't high enough. ;) Naw, if I let a little thing like this bother me I'd be dead already ;) I'd rather not see this list turn into a blame game of any kind. We all have our good days and our not so good days. I would urge readers who have problems like this to use the support organizations of both NetApp and VERITAS. For at least the VERITAS side, if you are unhappy with an answer you get from the support organization please ask the support engineer to escalate the problem - use my name if you have to :) __________________________________________________________________________ Steve Kappel steve.kappel(a)veritas.com VERITAS Software steve.kappel(a)iname.com (Personal)

1 0

RE: creating a share with vba on a filer
by Hawley, Rob 11 Sep '00

11 Sep '00

Your program looks correct. We do support using level 502 to add a share. Please confirm a couple of points that could be the source of the problem: 1. The user running the script is a member of either the filer's Administrators group or is a member of Power Users. That is required for NT compatible security. 2. That the path vol\nt01\users is the correct physical path to where the user's directory should be created. That is there are no other directories in the path. If neither of these resolve your problem, then please contact NetApp customer support. They will need a packet trace of this exchange and a cifs sessions -s of the user attempting to execute the script. CS can help you if you are unfamiliar with how to get a packet trace. ~~~~~~~~~~~~~~~~~~~ mailto: hawleyr(a)netapp.com US Mail: Network Appliance Inc. Windows Networking Engineering 495 E Java Dr Phone/pager: 408-822-6661 Sunnyvale, CA 94089 http://www.netapp.com -----Original Message----- From: Ulrich Neumann [mailto:ulrich.neumann@brose.de] Sent: Monday, September 11, 2000 2:01 AM To: toasters(a)mathworks.com Subject: creating a share with vba on a filer << File: ShareErr2116Filer.txt >> we just turned our user-home-shares from a nt-server to a filer. for creating new user-shares, we use a selfmade program in vb. unfortunately this program woun't work now with the filer. neither "c:\vol\nt01\users\username" nor "\\cobfile01\users$\username" is working. there's always the error 2116.(see sub makeshare in attached code) is there anybody out there who has a good idea to solve this problem? greetings from brose GmbH & Co KG Client-Server-Technologien Ulrich Neumann

1 0

Jump to page:

2026

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