toasters

toasters@lists.teaparty.net

13523 discussions

Filer Backup w/Networker
by dmaloy＠atomaintl.com 17 Oct '00

17 Oct '00

I have two 740's which I would like to backup. We are currently using Legato Networker for our backup solution and the backup server is a UNIX machine with a locally connected DLT tape library. Within Networker, I have to specify which filesystems to backup and when I specify the volume on the filers, my backup log reports that the backup size was almost triple the size of what the actual data size was, reported by using the "df" command. I have a feeling that it is also backing up the .snapshot directories for ea. vol but not sure. Is there a way to ensure that these directories are not included in the save set? Will a "-.snapshot" line in the client setup fix it? Don Maloy Sr. CAD Administrator Atoma Latching Systems 19888 Haggerty Rd Livonia, MI 48152

2 1

RE: Filer Backup w/Networker
by White, Lance 17 Oct '00

17 Oct '00

Why not backup JUST the snapshot directory? (i.e. .snapshot/nightly.0/) -----Original Message----- From: dmaloy(a)atomaintl.com [mailto:dmaloy@atomaintl.com] Sent: Monday, October 16, 2000 4:41 PM To: toasters(a)mathworks.com Subject: Filer Backup w/Networker I have two 740's which I would like to backup. We are currently using Legato Networker for our backup solution and the backup server is a UNIX machine with a locally connected DLT tape library. Within Networker, I have to specify which filesystems to backup and when I specify the volume on the filers, my backup log reports that the backup size was almost triple the size of what the actual data size was, reported by using the "df" command. I have a feeling that it is also backing up the .snapshot directories for ea. vol but not sure. Is there a way to ensure that these directories are not included in the save set? Will a "-.snapshot" line in the client setup fix it? Don Maloy Sr. CAD Administrator Atoma Latching Systems 19888 Haggerty Rd Livonia, MI 48152

1 0

Re: Backup solution.
by Graydon Dodson 16 Oct '00

16 Oct '00

A word of advice on the Spectra Logic Gator. We have had one for about two months now and it is not yet a mature product. (but it is making progress) In that time I have had to upgrade S/W in the unit at least four times. One upgrade (done at the recommendation of Spectra Logic) turned out to not be compatible with the EC level of my H/W requiring a couple of RMAs. Today it is still possible to confuse the unit if care is not taken. (what else can you expect from a product running Windoes CE?) Having said the above. I like the idea behind the gator and believe that in time Spectra Logic will get the kinks worked out. The ability to logically partition the unit as well as the future possibility of backing a netapp over FC-AL makes it very appealing. But you might want to give the unit a little time to mature first. In my experience the fastest way to back up a filler today is direct attach SCSI. FC-AL is not supported till OnTap 6.x which is still only early access. (I will not run early access code on production fillers) Gig ethernet may look appealing but I cannot see how placing an ethernet layer between the NetApp and the tape drive is going to speed anything up. There are two fundamental bottlenecks for backups, the speed of the tape drive and the load on the filler. Adding more stuff in the middle cannot speed things up. While we are on the subject, I have an upgrade the "ndmputil" package that supports large tape libraries and includes a tool to retrieve drive & tape stats from AIT tape drives. I hope to get the upgrade to NetApp for posting on NOW as soon as I get the documentation updated. Graydon Dodson grdodson(a)lexmark.com Lexmark International Inc. ------------- Begin Forwarded Message ------------- From: Jeff Bryer <bryer%sfu.ca(a)interlock.lexmark.com> Subject: Re: Backup solution. To: foo%eek.org(a)interlock.lexmark.com (foo) Date: Mon, 16 Oct 2000 14:28:27 -0700 (PDT) Cc: toasters%mathworks.com(a)interlock.lexmark.com > The questions are: > > 1.) Which tape library to buy (leaning towards SpectraLogic Bullfrog with 4 drives/40 tapes). > We were looking at the Gator 12000 from SpectraLogic ourselves. Then decided on the 64000 for it's ability to scale up. We haven't got it hooked up yet, so I can't give you a performance report just yet. > 2.) To connect the library to the network via gig-e or to the netapp's via FCAL. > We're going with direct attach SCSI to a pair of F740s and a pair of SUN E450s. May direct attach to a 3rd F740 (if we buy a third). In a year or so, I may want to switch over to a SAN environment (swap out our S-QIPS with F-QIPS in the Gator), but I'm not comfortable enough with technology currently to consider that for the immediate future. > 3.) Which software to buy and what to make it do (eh NDMP blah). > We're evaluating Time Navigator (Quadratec), Backup Express (SyncSort), and Quick Restore (Workstation Solutions). Legato's NDMP support currently is not worth considering, and Veritas hasn't been forthcoming in working with us. We're looking to handle 1 - 1 1/2TBs in the short term, and scale up if we start backing up servers across campus. -- Jeff Bryer bryer(a)sfu.ca Systems Administrator (604) 291-4935 Academic Computing, Simon Fraser University ------------- End Forwarded Message -------------

1 0

Re: Backup solution.
by mehlel001＠hawaii.rr.com 16 Oct '00

16 Oct '00

How about backing up to another filer? You could use "Snap Mirror". The main reson I suggest this is because to restore that much data off of tape would take days! We have over 40 filers are are looking to backup directly to a "Backup Filer" using Snap Mirror and MAYBE have a tape robot off of the "backup filer" that would go to tape maybe once a month and be used as a DR device ofr offsite storeage etc. Anybody do anything simular to this? Thanks in advance, Lance >Ok, so I've been trying to figure out the "optimal" backup solution for my environment for awhile and haven't had much luck. I >know this topic gets beaten to death, but if you can indulge me for a moment that'd be great. > >I have 2 760's with a 1/2 TB each (in a cluster). We'll be adding a 720 with ~1/2 TB very soon, and expect our overall storage >to at least double in the next 6-12 months. We have approximately 25 servers (sparcs of various flavors) using the storage. >We'd like to have a unified solution for backing up the netapp's as well as all of the servers. > >The questions are: > >1.) Which tape library to buy (leaning towards SpectraLogic Bullfrog with 4 drives/40 tapes). > >2.) To connect the library to the network via gig-e or to the netapp's via FCAL. > >3.) Which software to buy and what to make it do (eh NDMP blah). > >Did I miss anything? > >So if you had this environment today what kind of solution would your propose? > >-Brian >

1 0

RE: NIS groups not showing up
by mehlel001＠hawaii.rr.com 16 Oct '00

16 Oct '00

Thanks to all for your help. As it turns out the problem is if a group line on your NIS+ server exceeds 1024 chars the filer will stop processing the NIS entry once it sees that line. So all groups after that are non-existant! I understand this is fixed in 6.0 but don't know for sure. If not there should atleast be a warning in the log file that says you may have exceeded the 1024 char limit in a particular NIS map. >Hi Lance, > > When the group cache is created, if there are duplicate entries, a message will >be logged. Are there any such messages logged? > >Thanks, >-Devi > > > >-----Original Message----- >From: Lance R. Mehle [mailto:mehlel001@hawaii.rr.com] >Sent: Saturday, October 14, 2000 3:13 PM >To: Toasters (E-mail) >Subject: NIS groups not showing up > > >Hi all, > >I have a problem that I was wondering if any of you have seen. > >We have a little over 2000 groups in our NIS+ environment. When I check the >nis_cache file on the filer about 399 are missing. A ypgroup also shows the >group(s) missing from the filer although a ypmatch can find the group(s). >It also appears that the same groups are effected all the time. > >The groups are fine on the UNIX side. > >Help! > >Lance >

1 0

Backup solution.
by foo 16 Oct '00

16 Oct '00

Ok, so I've been trying to figure out the "optimal" backup solution for my environment for awhile and haven't had much luck. I know this topic gets beaten to death, but if you can indulge me for a moment that'd be great. I have 2 760's with a 1/2 TB each (in a cluster). We'll be adding a 720 with ~1/2 TB very soon, and expect our overall storage to at least double in the next 6-12 months. We have approximately 25 servers (sparcs of various flavors) using the storage. We'd like to have a unified solution for backing up the netapp's as well as all of the servers. The questions are: 1.) Which tape library to buy (leaning towards SpectraLogic Bullfrog with 4 drives/40 tapes). 2.) To connect the library to the network via gig-e or to the netapp's via FCAL. 3.) Which software to buy and what to make it do (eh NDMP blah). Did I miss anything? So if you had this environment today what kind of solution would your propose? -Brian

2 1

RE: cifs.home_dir values
by Louis Brune 16 Oct '00

16 Oct '00

If I may submit a summary: From paul.benn(a)netapp.com: options cifs.home_dir vol\vol0\homes,vol\vol1\more_homes Data ONTAP 6.0 has another new option as well called "cifs.home_dir_namestyle." This option allows you to change how a username is used for mapping the home directory. Here are the three options with descriptions: ntname (or nothing): This is the same as with ONTAP 5.x. The user's home directory name must match the user's NT domain account name. mapped: The user's home directory name must match the user's mapped UNIX user name. domain: Under the root home directory (set with the cifs.home_dir option), you need to create one subdirectory for each domain that the filer trusts. Each user's directory is then created under their respective domain directory. The user's home directory name must match the user's NT domain account name and the domain directory must match the user's domain. and from Anissa.Mohler(a)netapp.com: Actually the syntax will be: options cifs.home_dir /vol/vol0/homes,/vol/vol1/more_homes If you type it wrong you will get a friendly error message :) There are many different ways of using home directories in ONTAP 6.x like Paul mentioned. It is one of the cooler new features from a CIFS point of view. Meanwhile, back in 5.3.x-land, there was from Eli.Lopez(a)netapp.com, jkrueger(a)qualcomm.com, and Moshel.Linzer(a)nsc.com: > > > On Wed, Sep 20, 2000 at 09:23:04AM +0200, Eli Lopez wrote: > > > > BTW, you can create a soft link on the filer called QTREE1 pointing to > > > > /vol/vol1/QTREE1 and mount using the link name. > > > > > > Cool! I didn't know the NetApp could internally resolve symlinks for > > > NFS/CIFS exports/shares and still give us the "right stuff" from rquotad > > > and what not. > > > > Yeah, the same trick allows us to share our CIFS homedirs under a single root, > > without actually moving the user's home directory. > > Whoa. What's this? I knew symlinks if resolved on the same > filesystem on a filer work correctly under CIFS, but this seems > different. You can symlink across *volumes* on the same filer and it is > transparent to NFS and CIFS clients??? > Yes, the difference is that you are SHARING THE SYMLINK, not putting a symlink inside a share. So without quoting all of Chris' email, you can set your cifs homedir to a directory full of symlinks (userid -> /path/to/homedir), and each user will get a share to his own homedir upon login! Cool undocumented feature. And it appears to be true that some 6.X release will have multiple homedir paths, but this is still more versatile! So we ask: Will support for that most excellent symlink trick persist into ONTAP >=6? -- Moderation in all things, except love. Louis

1 0

Re: FILERS IN A HIGH-TRANSACTION SYBASE APP ENVIRONMENT
by Rick Hulsey 16 Oct '00

16 Oct '00

We did some performance testing on HP K class boxes running HP-UX 10.20 and 11.0. We found that the Netapp over Gig-E was on average about 30% faster than the HP Mod-20 disk arrays (AKA CLARiiON 20 slot) configured in RAID 5 for our application queries. We are planning to wait for more testing on Sybase 12.5 to make the move to the filer because the move to 12.5 will be a dump and load of our existing databases anyway. Rick Hulsey Southwest Airlines 2425 Wyman Mail Stop 4DC Dallas, Tx., 75235 rick.hulsey(a)wnco.com (214) 792-7188 Office (972) 880-6882 Cell (800) 915-3747 Pager >>> Joe Luchtenberg <joe.luchtenberg(a)data-line.com> 10/13/00 03:40PM >>> Is anybody using NetApp filers for backend storage in a high-transaction Sybase app environment? I have a customer considering this configuration and would appreciate any insight/lessons learned from the field. Thanks. Joe Joe Luchtenberg Dataline, Inc. New number and email, please update: 757.858.0600 858.0606 fax joe.luchtenberg(a)data-line.com

1 0

Top 5 Web Sites
by mmcdonald＠123go.com 16 Oct '00

16 Oct '00

1 0

RE: cifs.home_dir values
by Muhlestein, Mark 15 Oct '00

15 Oct '00

And if you aren't ready to upgrade to 6.0, you can still create symbolic links which point across volumes. Mark -----Original Message----- From: Mohler, Anissa [mailto:Anissa.Mohler@netapp.com] Sent: Saturday, October 14, 2000 9:56 AM To: Benn, Paul; 'Coder, James (STP)'; 'toasters(a)mathworks.com' Subject: RE: cifs.home_dir values Actually the syntax will be: options cifs.home_dir /vol/vol0/homes,/vol/vol1/more_homes If you type it wrong you will get a friendly error message :) There are many different ways of using home directories in ONTAP 6.x like Paul mentioned. It is one of the cooler new features from a CIFS point of view. They are covered extensively in the ONTAP 6.0 Web Based Training (shameless plug) ... or you can always read the System Administrators Guide for ONTAP 6 on the NOW site ;) Enjoy! :-----Original Message----- :From: Benn, Paul [mailto:paul.benn@netapp.com] :Sent: Friday, October 13, 2000 10:48 PM :To: 'Coder, James (STP)'; 'toasters(a)mathworks.com' :Subject: RE: cifs.home_dir values : : :Hello James, : :If you're using Data ONTAP 6.0 or later you can specify :multiple directories on :one filer. The option you need to set is called :"cifs.home_dir" and you can use :a comma separated list with a maximum of 255 characters. :Here's a sample :command: : :options cifs.home_dir vol\vol0\homes,vol\vol1\more_homes : :Data ONTAP 6.0 has another new option as well called :"cifs.home_dir_namestyle." :This option allows you to change how a username is used for :mapping the home :directory. Here are the three options with descriptions: : :ntname (or nothing): :This is the same as with ONTAP 5.x. The user's home directory :name must match :the user's NT domain account name. : :mapped: :The user's home directory name must match the user's mapped :UNIX user name. : :domain: :Under the root home directory (set with the cifs.home_dir :option), you need to :create one subdirectory for each domain that the filer trusts. :Each user's :directory is then created under their respective domain :directory. The user's :home directory name must match the user's NT domain account :name and the domain :directory must match the user's domain. : : :Best Regards, : :Paul Benn :Network Appliance : : :-----Original Message----- :From: Coder, James (STP) [mailto:james.coder@guidant.com] :Sent: Friday, October 13, 2000 7:53 PM :To: 'toasters(a)mathworks.com' :Subject: cifs.home_dir values : : :I have a 760 being used for home file server in Solaris / windows :environment. This is replacing my e3500 filer server running :samba. Can :you have more than one volume listed in for cifs.home_dir? If :so, how do :you set it up? : :thx in advance - jcc : : :James C. Coder :UNIX Administrator :Guidant Corporation :Phone: 651-582-4797 :Email: james.coder(a)guidant.com : :

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