toasters

toasters@lists.teaparty.net

2 participants
13514 discussions

manual nightly snapshot rollover, or 'snap redo'
by Todd C. Merrill 24 Mar '99

24 Mar '99

Is there a way to *manually* rollover snapshots retaining the .number sequence? That is, without doing this in a script: rsh filer snap delete vol0 nightly.N rsh filer snap rename vol0 nightly.N-1 nightly.N ... rsh filer snap rename vol0 nightly.0 nightly.1 rsh filer snap create vol0 nightly.0 Reason is, I need to do a few things just before midnight and then a few things after midnight, but the things before midnight might not finish exactly before midnight when the filer makes the nightly snapshot, and I need them to be included in the read-only snapshot. So, I'd like to do something like: 1. do my pre-midnight commands 2. rsh filer snap nightly 3. do my post-midnight commands ("commands" are things done from an NFS mount to manipulate the data/files on the filer, not commands executed on the filer itself) and have step 2 do all the numbering bookkeeping for me, according to the snap schedule. Probably not, since that would mean some other switch to tell the filer *not* to the automagic snapshots. But, I'd thought I'd ask anyway, in case anyone has any better ideas. Orrrrr, how about a resnap? I could let the filer make its nightly.0 snapshot as usual, and then a few minutes after midnight, execute something like: rsh filer snap redo vol0 nightly.0 Oooo, I like that better. That helps with other snapshot manipulations we use, instead of: rsh filer snap create new rsh filer snap rename image old rsh filer snap rename new image rsh filer snap delete old Would this be useful enough to more than just me for an RFE? Until next time... Todd C. Merrill The Mathworks, Inc. 508-647-7792 24 Prime Park Way, Natick, MA 01760-1500 508-647-7012 FAX tmerrill(a)mathworks.com http://www.mathworks.com ---

1 0

RE: NetApp/Auspex killer?
by Adams, Christian 24 Mar '99

24 Mar '99

Hey Tom - If you propate over an IP network on the front end of the head, then yes there is a performance penalty. If you have the disk shelves handle the propagation, then you can do some interesting things which do not create a performance penalty. But then you're talking about putting intelligence down into the disk shelves themselves. /Christian Adams > -----Original Message----- > From: tkaczma(a)gryf.net [SMTP:tkaczma@gryf.net] > Sent: Monday, March 22, 1999 4:47 PM > To: toasters(a)mathworks.com > Subject: RE: NetApp/Auspex killer? > > > > On Mon, 22 Mar 1999, Mohler, Jeff wrote: > > > Your DR solution should PUSH data out constantly, not request it > > remotely every 60 seconds, then if a snapcopy fails for that period, it > gets > > thrown away on the remote side...two lost minutes of data. > > That's true for your application, but I don't want to mirror my disks > across the country even every 60 seconds. Once every couple of minutes > or hours is perfect for me. If you truly mirror your disks the latency > associated with data propagation will kill the performance. > > Tom

3 2

Re: One tape *drive* supported on 5.1.2???
by mds＠gbnet.net 24 Mar '99

24 Mar '99

On Tue 23 Mar, 1999, Kelly Wyatt <saskww(a)wnt.sas.com> wrote: > We have just been informed by Network Appliance that only *one* tape *drive* > per adapter is supported on 5.1.2. (We have been running with 1 adapter/2 > drives since August on 4.3 and then 5.0 and now on 5.1.2 since we upgraded.) Not true. Or, if it is then we've been breaking the rules for a while. Well actually we were breaking the rulees for a while, but now we've got a really weird, really unique buggette. But when we squich that, we'll be back to breaking the rules. 8) > > Was anyone else aware of this? This came about due to a call we placed when > removing a stuck tape rebooted the filer... > ------- > > Kelly Wyatt, saskww(a)wnt.sas.com <mailto:saskww@wnt.sas.com> > Integrated Solutions Consulting > SAS Institute Inc. / SAS Campus Drive / Cary, NC 27513 > (919) 677-8000 X4279 (Voice) / (919) 677-4444 (FAX) > http://www.sas.com <http://www.sas.com> >-- End of excerpt from Kelly Wyatt

1 0

RE: One tape *drive* supported on 5.1.2???
by Melvin, Grant 24 Mar '99

24 Mar '99

Hi Kelly, I'm sorry to say that you were given the wrong response from NetApp today, so let me clear this up and apologize for any inconvenience caused. When engineering looked at the config on your site a *wrong* assumption was made and it was thought that there were 2 tape devices each on separate cards, which is not a supported config. The good news is that your configuration *IS* supported since you have 2 tape devices on a single SCSI tape adapter. In our next Data ONTAP release 5.3 we will be supporting 2 SCSI tape adapters on the F760 & F630 platforms. And since we support 2 tape drives per SCSI adapter this will allow upto 4 tape drives to be supported on these filers or 2 tape devices each on separate cards. Cheers, Grant -----Original Message----- From: Kelly Wyatt [mailto:saskww@wnt.sas.com] Sent: Tuesday, March 23, 1999 1:08 PM To: toasters(a)mathworks.com Subject: One tape *drive* supported on 5.1.2??? We have just been informed by Network Appliance that only *one* tape *drive* per adapter is supported on 5.1.2. (We have been running with 1 adapter/2 drives since August on 4.3 and then 5.0 and now on 5.1.2 since we upgraded.) Was anyone else aware of this? This came about due to a call we placed when removing a stuck tape rebooted the filer... ------- Kelly Wyatt, saskww(a)wnt.sas.com <mailto:saskww@wnt.sas.com> Integrated Solutions Consulting SAS Institute Inc. / SAS Campus Drive / Cary, NC 27513 (919) 677-8000 X4279 (Voice) / (919) 677-4444 (FAX) http://www.sas.com <http://www.sas.com>

1 0

RE: name lookup debugging?
by Mohler, Jeff 23 Mar '99

23 Mar '99

Ive had this problem before too..and my only solution was a reboot. BIND on the box has done some really funky things for me..occasionally. ...maybe twice in a year. But the Filer will be the only device out of dozens/hundreds reporting any problems. > -----Original Message----- > From: Jim Davis [SMTP:jdavis@CS.Arizona.EDU] > Sent: Tuesday, March 23, 1999 2:06 PM > To: toasters(a)mathworks.com > Subject: name lookup debugging? > > I'm getting some odd messages from one of our filers > > [mountd]: DNS server for domain "CS.Arizona.EDU" not responding: > Connection timed out. > > The nameserver it's trying to contact as per /etc/resolv.conf seems to be > up and happy. No obvious network problems between here and there, though > our campus router people were playing permute-the-configuration earlier. > > Is there something that can be turned on on the netapp side to get more > details about what the filer is doing, name-lookup-wise?

1 0

One tape *drive* supported on 5.1.2???
by Kelly Wyatt 23 Mar '99

23 Mar '99

We have just been informed by Network Appliance that only *one* tape *drive* per adapter is supported on 5.1.2. (We have been running with 1 adapter/2 drives since August on 4.3 and then 5.0 and now on 5.1.2 since we upgraded.) Was anyone else aware of this? This came about due to a call we placed when removing a stuck tape rebooted the filer... ------- Kelly Wyatt, saskww(a)wnt.sas.com <mailto:saskww@wnt.sas.com> Integrated Solutions Consulting SAS Institute Inc. / SAS Campus Drive / Cary, NC 27513 (919) 677-8000 X4279 (Voice) / (919) 677-4444 (FAX) http://www.sas.com <http://www.sas.com>

1 0

NVRAM PCI cards
by Daniel Quinlan 23 Mar '99

23 Mar '99

Does anyone know who makes the NVRAM cards used by NetApp (for F630 and earlier)? No, I'm not looking to put this into one of my NetApps, but I am looking for a PCI card with some sort of non-volatile RAM that I can purchase. Ideally, some sort of battery-backed RAM -- not flash. - Dan

5 4

Re: NVRAM PCI cards
by mds＠gbnet.net 23 Mar '99

23 Mar '99

You could always give solid state disk a try - fibre channel or SCSI connection and capacities from jsut over a hundred MB to about 17GB are available. A 17GB battery backed solid state RAM drive would cost about 250,000 USD though.. 8)

1 0

RE: NVRAM PCI cards
by Packer, Gary 23 Mar '99

23 Mar '99

I believe the NVRAM card used in the EISA system was designed by a company called PEP, I don't know if they offer a PCI version. Since the F330 series, we have used our own proprietary design of NVRAM. -----Original Message----- From: guy(a)netapp.com [mailto:guy@netapp.com] Sent: Monday, March 22, 1999 7:02 PM To: quinlan(a)transmeta.com Cc: toasters(a)mathworks.com Subject: Re: NVRAM PCI cards > Does anyone know who makes the NVRAM cards used by NetApp (for F630 > and earlier)? Network Appliance, Inc.. (Well, they're probably actually *manufactured* by Solectron or some other contract manufacturer, but they're *not* an off-the-shelf part we buy from somebody else.) The NVRAM card used on the EISA filers came, as I was told, from a company that had an ISA NVRAM card - we had them design an EISA version. If they're still around, they may have a PCI card; I don't remember the name of the company, but I can ask around....

1 0

Re: NetApp/Auspex killer?
by Arvind K Aggarwal 23 Mar '99

23 Mar '99

> > > It all boils down to the words "disaster" and "recovery" being > > subjective.... > > > > And the "official" meanings change between the time you show > > management a price tag and when the data center catches on fire. :) > > > > > > jason > --- > > *laugh* > > Good one! > Until the data center catches fire and the same folks wanna know why *YOU* did not tell them the whole truth. I agree with jason, I just like to put in every caveat possible to cma. Arvind

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