toasters

toasters@lists.teaparty.net

13513 discussions

RE: Snapshots/no snapshots on the same volume
by Norman, Paul 21 Jan '99

21 Jan '99

> -----Original Message----- > From: Bob Collie [mailto:bob.collie@telalink.net] > Sent: Wednesday, January 20, 1999 1:01 PM > To: toasters(a)mathworks.com > Subject: Snapshots/no snapshots on the same volume > > > Can you designate a certain area of the same volume to not snapshot > where you designate the rest of it to do so? > > It is my current understanding that I have to create an entirely > new volume in order to try and do this, but I'm hoping that is > not the case. I hate to be the one to dash your hopes, but your understanding is correct. You need to create additional volume. Snapshots are indeed done on a per volume basis. > > NetApp Release 5.1.2: Sat Sep 26 05:05:59 PDT 1998 > > Thanks, > -Bob > > -- > Bob Collie, VP/Chief Technical Officer, Telalink Corporation > mailto:bob.collie@telalink.net >

1 0

RE: Clustered failover product roadmap
by Norman, Paul 21 Jan '99

21 Jan '99

> -----Original Message----- > From: Brian Tao [mailto:taob@risc.org] > Sent: Wednesday, January 20, 1999 12:26 PM > To: toasters(a)mathworks.com > Subject: Clustered failover product roadmap > > > I've got two conflicting pieces of information that I'd like > to have sorted out. I initially thought that clustered failover was > available on the F760 late last year, and that it was coming to the > F740 sometime this quarter. I was then told by a Netapp vendor that > last year saw the rollout of clustering on the F630's, and that I > should only expect clustering on the F760's this quarter. Clustering > on the F740's was not in the plans. F630 Clusters starting shipping October 10th of last year. F760 and F740 Clusters started shipping January 11th of this year. > > I'm pretty sure I heard right the first time, and I'm told Netapp > demonstrated an F740 cluster at LISA'98. I bought a pair of F740's on > the assumption that I could get clustering on them for 1999Q1, and I'm > about to buy another pair on the same assumption. We did demonstrate an F740 cluster at LISA'98 last December. > -- > Brian Tao (BT300, taob(a)risc.org) > "Though this be madness, yet there is method in't" >

1 0

Re: Snapshots/no snapshots on the same volume
by Keith Brown 21 Jan '99

21 Jan '99

>Can you designate a certain area of the same volume to not snapshot >where you designate the rest of it to do so? No. Sorry. Keith

3 2

Clustered failover product roadmap
by Brian Tao 20 Jan '99

20 Jan '99

I've got two conflicting pieces of information that I'd like to have sorted out. I initially thought that clustered failover was available on the F760 late last year, and that it was coming to the F740 sometime this quarter. I was then told by a Netapp vendor that last year saw the rollout of clustering on the F630's, and that I should only expect clustering on the F760's this quarter. Clustering on the F740's was not in the plans. I'm pretty sure I heard right the first time, and I'm told Netapp demonstrated an F740 cluster at LISA'98. I bought a pair of F740's on the assumption that I could get clustering on them for 1999Q1, and I'm about to buy another pair on the same assumption. -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

4 3

Snapshots/no snapshots on the same volume
by Bob Collie 20 Jan '99

20 Jan '99

Can you designate a certain area of the same volume to not snapshot where you designate the rest of it to do so? It is my current understanding that I have to create an entirely new volume in order to try and do this, but I'm hoping that is not the case. NetApp Release 5.1.2: Sat Sep 26 05:05:59 PDT 1998 Thanks, -Bob -- Bob Collie, VP/Chief Technical Officer, Telalink Corporation mailto:bob.collie@telalink.net

1 0

RE: Clustered failover product roadmap
by Gegenheimer, Bill 20 Jan '99

20 Jan '99

You may get multiple responses on this one. Clustering on the 760's and the 740's is supported now, as of release 5.2.1, which has just come out (last week). Bill > -----Original Message----- > From: Brian Tao [mailto:taob@risc.org] > Sent: Wednesday, January 20, 1999 12:26 PM > To: toasters(a)mathworks.com > Subject: Clustered failover product roadmap > > > I've got two conflicting pieces of information that I'd like > to have sorted out. I initially thought that clustered failover was > available on the F760 late last year, and that it was coming to the > F740 sometime this quarter. I was then told by a Netapp vendor that > last year saw the rollout of clustering on the F630's, and that I > should only expect clustering on the F760's this quarter. Clustering > on the F740's was not in the plans. > > I'm pretty sure I heard right the first time, and I'm told Netapp > demonstrated an F740 cluster at LISA'98. I bought a pair of F740's on > the assumption that I could get clustering on them for 1999Q1, and I'm > about to buy another pair on the same assumption. > -- > Brian Tao (BT300, taob(a)risc.org) > "Though this be madness, yet there is method in't" >

2 1

Re: can't control access over CIFS
by Keith Brown 20 Jan '99

20 Jan '99

>Clearly, there is some cacheing going on, but I don't know where, why, >or when. Yes there is some "cacheing" going on, and this is probably what's causing your confusion. When a Windows client first establishes a CIFS session to the filer, either by mapping a network drive to a filer share or by accessing our file system using a UNC pathname, the Windows user is normally mapped to a valid UNIX identity so that the UNIX permissions in the file system can be enforced on that user. This is done by looking up the Windows username in the filer's /etc/passwd file (or the equivalent passwd.byname NIS map) and associating the users UNIX UID, primary GID and secondary GIDs with the established CIFS session (the secondary GIDs, if any, come from an /etc/group lookup, just like on UNIX). This mapping only occurs at session establishment time. If you subsequently add the user to another group by editing the /etc/group file, or change their UID or primary GID by editing the /etc/passwd file, the new values and/or group memberships will not be associated with the Windows user until they disconnect their session from the filer and then reconnect. Forcing a Windows client to disconnect a CIFS session from a server is actually something of an art form. The CIFS redirector on Windows manages sessions largely independently of direct user actions, and this may also be causing some confusion. For example, a: NET USE Q: \\FILER\SHARE will establish a CIFS session to the filer (unless there is one established already), but a: NET USE Q: /D will not disconnect the session. It will disconnect the network drive from the CIFS session (you won't have a Q: anymore), but the CIFS session itself will normally remain established, even if you have no other drives mapped to the filer. Only if you don't try and access the filer via *any* method (UNC or mapped drive) for a period of time (10 minutes is the default, but it can be changed in the registry) will the CIFS redirector quietly disconnect the session from the filer. This is just how Windows networking works, whether you're dealing with a filer or a Windows NT server. So, if you mess with a Windows user's group memberships by editing the passwd and group databases, the easiest way to make *certain* that a new mapping is done immediately is to force a disconnect from the filer side using the "cifs terminate <workstation-name>" console command. I'm fairly certain that logging the user out of the Windows client and then logging them back in again will force a client side disconnect, but I haven't watched that one with my own eyes and I don't want to mislead you. The Windows redirector's session management policies can be a little esoteric. :-) Whatever you do, you can use the "cifs sessions" command to make sure that the client's session has gone before you try accessing the filer again from said client after making the changes. As a final note, this mapping-Windows-users-to-equivalent-UNIX-users stuff is actually unnecessary if you are using the filer in a Windows-only context. If you enable NTFS security within our file system, Windows users do not have to be associated with unique UIDs and GIDs etc... in order for security to be enforced. In other words, Windows-centric folk should not be "scared" by any of the above. If you don't care about UNIX, none of this is necessary or directly applicable. If you just have a mass of humble Windows users, we don't "force" you to mess with passwd files, group files, UIDs, GIDs, UNIX perms etc, etc... to administer these users. It can all be done using regular domain accounts and NTFS permissions, all managed and administered from the standard User Manager for Domains and Server Manager NT tools, as well as the Explorer UI (file properties -> security -> permissions etc...). Keith

1 0

Frequency of "recovered error" messages
by sthaug＠nethelp.no 20 Jan '99

20 Jan '99

We have an F330 running 4.3.3D2 where one of the disks is now generating 30 - 40 "READ sector xxxxxxx recovered error" messages per day. At what frequency of such messages should I start worrying about the disk? Steinar Haug, Nethelp consulting, sthaug(a)nethelp.no

3 2

Sybase or Oracle on NetApp?
by Adam Moskowitz 20 Jan '99

20 Jan '99

Is anyone out there running Sybase or Oracle on top of your filers? Are you satisfied with the performance? Have you had any problems? Any tips. We're considering doing this for our Sybase applications (which are closer to data warehousing than OLTP, if that matters). Please respond to me and I'll summarize to the list. Thanx, AdamM

1 0

Problem restoring files
by charles＠applix.com 19 Jan '99

19 Jan '99

This question probably has an obvious answer, but here goes: We are trying to restore a particular sub-directory from a single tape backup. Since I have never done this, I ran the command "restore tf nrst0a fran" to make sure that the syntax was right. This listed all of the files in the target directory (/user/fran). But when I went to do the actual restore ("restore rvf nrst0a fran"), I started getting messages like "Warning: cannot create directory /user/miller/blah/blah/blah: file exists", which they do. In fact /user/fran does not currently exist on the filer (thus the restore), and /user/miller does. My question is: why is the restore touching anything but /user/fran in the first place? Any info on the proper syntax would be greatly appreciated. Regards, /charles Charles Homan System & Network Opertions Group Applix, Inc.

2 2

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