toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

End-of-Year backup plans...
by Don Glascock 11 May '99

11 May '99

Hi -- As we prepare for the potential purchase of a relatively large toaster in six months or so, we are also considering the options for backing it up. We're happy with our little F230, traditional "14 Gbyte" 8mm tapes, and Networker, but it would appear that lights-out backups of a much larger toaster would do better with bigger-capacity tapes. The AIT/DLT discussions & documents have been very useful. So the big questions we will need to have answered in the next six months are: 1. Will Legato's Networker backup software speak NDMP by Q1 2000? It is said that this is the reason why they bought BudTool from Intelliguard. Do representatives of Legato read this list? 2. Does Network Appliance plan to support AIT jukeboxes (not just autoloaders) in native mode (not just "dds mode") by Q1 2000? 3. Will Legato (or Veritas) take advantage of the memory chips on AIT tapes? If so, exactly how? 4. What do you think of the statement made in one of the AIT/DLT documents that said that AIT tape drives only clean the head, and not the tape path as well? I realize this is only May, but planning is everything. Thanks! Don Glascock -- Donald S. Glascock Mailstop GU-1016 Special Purpose Processor Development Group Mayo Foundation Rochester, MN 55905 Glascock.Donald(a)Mayo.EDU +1.507.284.1850 +1.507.284.9171 (fax) http://www.mayo.edu/sppdg/sppdg_home_page.html "No matter where you go, there you are."

1 0

rsh from NT
by Jason Middlebrooks 11 May '99

11 May '99

Now that I have been corrected about rsh working from NT how do I do it. I have the NT host name in the hosts.equiv file on the filer but everytime I try to rsh I get a permission denied. Any ideas?

2 1

Solaris/NIS/shadow-passwords
by David Lee 11 May '99

11 May '99

We are considering getting a NetApp Filer to become the major fileserver in our established cluster of Solaris 2.6 machines, with a user population of some 15,000 administered using NIS with shadow passwords for authentication. We understand that filer can do NIS, and that it can use its own shadow password file, but can use a Solaris/NIS/shadow combination? Network Appliance haven't yet been able to give us a definitive answer, nor a reference site we could contact. -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : Phone: +44 191 374 2882 (ddi) South Road : : Fax: +44 191 374 7759 Durham : : Internet: T.D.Lee(a)durham.ac.uk U.K. :

4 3

Re: Solaris/NIS/shadow-passwords
by sirbruce＠ix.netcom.com 11 May '99

11 May '99

On 05/10/99 14:25:10 you wrote: >However, if you are in a Unix only environment, then this doesn't >matter. The filer does no allow login, so the password portion is not >used. The only thing the filer uses the password file for is to do >username->UID mapping, so you only really need to worry about having a >password at all if you have an /etc/quotas file with usernames in it. Jerry, You're forgetting PC-NFS. Some people still use that. It would be nice if PC-NFS supported Solaris shadow passwords as well as the old SunOS 4.x NIS shadow passwords. >If you are using Unix password authentication with CIFS, however, you >have to copy the shadow file onto the filer itself. (Note that this does >not apply if you have domain authentication.) But what he wants is for the filer to support this via NIS, so he doesn't have to copy the shadow file onto the filer itself. (That is one of the main points of NIS, you know.) Bruce

2 1

Dual power on F760
by Aaron M. Sims 11 May '99

11 May '99

I've scanned the docs and the now.netapp.com site for an answer to this... no luck. How do I determine the status of either power supply in a F760 filer. If a power supply is off or failed, I'd like to run a command that will tell me just that. Thanks, Aaron -- Aaron M. Sims | "The reason why bad things happen to you is BellSouth.net | because you're a dumbass!" Systems Engineer | - Red Foreman, That 70s Show aaron.sims(a)bellsouth.net|

3 4

Re: rsh into the filer from NT
by Matt Day 10 May '99

10 May '99

Jason Middlebrooks <Jason_Middlebrooks(a)datalink.com> wrote: >I was told by someone that you can not rsh into a filer from the builtin >rsh utility NT has to offer. Am I correct on this one and is there a third >party rsh utility that will allow me to do this? I know it works great in >the UNIX evironment. No, that's not true. NT's builtin rsh works fine with the filer. Matt

1 0

RE: rsh into the filer from NT
by Benn, Paul 10 May '99

10 May '99

Hi Jason, Yes, rsh CAN be used on an NT box to issue commands to a filer. I recently released a white paper that has a section on using rsh. Check out Section 5.2 of: http://www.netapp.com/technology/level3/3052.html Hope this helps. Regards, Paul -----Original Message----- From: Jason Middlebrooks [mailto:Jason_Middlebrooks@datalink.com] Sent: Monday, May 10, 1999 2:46 PM To: toasters(a)mathworks.com Subject: rsh into the filer from NT I was told by someone that you can not rsh into a filer from the builtin rsh utility NT has to offer. Am I correct on this one and is there a third party rsh utility that will allow me to do this? I know it works great in the UNIX evironment.

1 0

rsh into the filer from NT
by Jason Middlebrooks 10 May '99

10 May '99

I was told by someone that you can not rsh into a filer from the builtin rsh utility NT has to offer. Am I correct on this one and is there a third party rsh utility that will allow me to do this? I know it works great in the UNIX evironment.

1 0

RE: Ontap P* relase mess.
by sirbruce＠ix.netcom.com 07 May '99

07 May '99

On 05/07/99 12:09:23 you wrote: >[process details snipped] >We are just beginning to move to this new model. There is likely to be some >overlap between P releases and maintenance releases in the near term. I hope you >can bear with us as we work through this transition. Well, the new process looks more efficient and sensible, but basically it amounts to eliminating P releases and putting out regular maintence releases. This is fine, but it doesn't really eliminate the problem this particular custoemr had. In the new scheme, CS would have given this customer a 5.2.1Dx patch which they'd be using when 5.2.2 came out. Due to the timing constraints you mention, the D patch might not have made it into the 5.2.2 release. The new customer, seeing 5.2.2 (either on a new filer or on NOW) assumes 5.2.2 would include 5.2.1Dx, and so downloads it and gets bitten. This was what prompted me to suggest what I did before. In the new scheme you describe, since CS can spin a D release quickly to address a customer problem, when 5.2.2 is ready for release it can be delayed only a day or two for CS to spin any Ds it needs from 5.2.1 to go with 5.2.2 that didn't make it into 5.2.2. Then when the customer running 5.2.1Dx goes to NOW, they'll not only see 5.2.2, but 5.2.2Dx with a note only to download this version if they're running 5.2.1Dx. Of course, if CS really can't spin a release that fast, then okay. But I suspect this might be what will wind up happening anyway. A customer experiences one bug, which CS fixes in 5.2.1Dx, then another bug which is fixed in 5.2.2. CS will have to spin a 5.2.2Dx release before 5.2.3 (which hopefully finally contains the 5.2.1Dx patch missing in 5.2.2) >I also agree with Paul regarding the rfe's. We need to do a better job of >documenting the changes that go into these releases. Customers need accurate >information about the content of these releases in order to make informed >decisions in managing their filers. You should expect to see change here as >well. Yes, barring any other corrective action at least this will provide another way an otherwise confused customer can learn not to install a certain version because the patch they want isn't in it. Bruce

1 0

Re: Dual power on F760
by sirbruce＠ix.netcom.com 07 May '99

07 May '99

On 05/07/99 16:02:32 you wrote: > >Well, here's my delima. The filer is isolated (network wise) and >has no default route to the rest of the world. SNMP won't help. > >The filer is in a remote location (800 miles away), so looking >at the LED is not a viable option. I think that even when one power supply fails and the other takes over, it will log a message in the messages file (and on the console). This may be one of those "log once every hour" messages so the customer can't miss it. So if you don't have those, I think the power supplies are OK. The message may not tell you which power supply is bad, but that's what the LED is for, since you have to have someone there in person to replace it. Bruce

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