toasters

toasters@lists.teaparty.net

13515 discussions

Re: Migrating from NetApp to new NetApp
by Sateesh Mucharla 25 May '00

25 May '00

Kelsey, Recently i migrated data (over 110GB) from F520 to F760. With a gig card insatlled in both the systems, we acheived 35GB per hour by using vol copy command. I am not sure about F230 taking a gig card. Alternately, you could use cpio for data transfer from any unix host. Its very efficient. I am acheiving 7GB per hour on regular network. Cheers Sateesh National Semiconductors > X-envelope-info: <kgc(a)sonic.net> > Date: Wed, 24 May 2000 14:50:25 -0700 > From: Kelsey Cummings <kgc(a)sonic.net> > X-Accept-Language: en > MIME-Version: 1.0 > To: toasters(a)mathworks.com > Subject: Migrating from NetApp to new NetApp > Content-Transfer-Encoding: 7bit > > I've got a f230 with 4 shelves of 4GB disks and its replacement, an > f740. I talked to netapp support and they recommended that the best > method to move the data from the f230 to the f740 would be to tapes with > dump and restore. I can't believe that there isn't a more efficient way > to do this. We are an ISP and all mail/ftp/http is served off of the > netapp, any downtime will be painfull so we'd like to minimize it as > best we can. > > What choices to migrate the data do we have? We've considered tar/cpio > over nfs but that's going to take some time even if we migrate one > service at a time. dump/restore seems clumsy. and plain ole 'cp' would > take forever. Apparently there are issues with volcopy going from SCSI > to FCAL, is that true? > > -- > Kelsey Cummings - kgc(a)sonic.net sonic.net > System Administrator 300 B Street, Ste 101 > 707.522.1000 (Voice) Santa Rosa, CA 95404 > 707.547.2199 (Fax) http://www.sonic.net/ > Fingerprint = 7F 59 43 1B 44 8A 0D 57 91 08 73 73 7A 48 90 C5

2 1

Re: software distribution with NDMPcopy/SnapMirror over WANs?
by Tor Lillqvist 25 May '00

25 May '00

> I believe "rsync" utility can help you out.... Definitely. FYI: Do not even consider rdist. In the common case of very small daily changes, rsync is one magnitude faster than rdist for replicating from one filer to another. (If lots of files change every day, the actual data transfer time will probably dominate, and the difference will not be that great.) Of course, SnapMirror is probably one magnitude faster than any replication using intermediate NFS clients such as rsync, as has other advantages as well... --tml

1 0

Oracle and NTAP.
by foo 25 May '00

25 May '00

Ok, so we've been contemplating using one of our 760's for Oracle storage. Discussions with Netapp people made me feel relatively warm and fuzzy about doing this but discussions with our DBA consultants didn't. Specifically they mentioned a situation they had experienced while testing a netapp/oracle environment which would cause total corruption and require restoration from backup. The specific situation is a case where the filer loses power but the DB server doesn't. Their claim is that if this occurs there is no method to recover the DB other than from backup. Anyone had any experience with Oracle/Netapp or this specific situation? We plan to test this in the next few days, but I wanted to get any insights you all might have. Thanks, -Brian

2 1

RE: Migrating from NetApp to new NetApp
by john.harechmak＠netapp.com 24 May '00

24 May '00

Hi, There is a whitepaper that might be interest on the netapp website: "Migrating Data Between NetApp Filers" http://www.netapp.com/tech_library/3018.html. Have you considered NDMPcopy? -- johnrh -----Original Message----- From: Kelsey Cummings [mailto:kgc@sonic.net] Sent: Wednesday, May 24, 2000 2:50 PM To: toasters(a)mathworks.com Subject: Migrating from NetApp to new NetApp I've got a f230 with 4 shelves of 4GB disks and its replacement, an f740. I talked to netapp support and they recommended that the best method to move the data from the f230 to the f740 would be to tapes with dump and restore. I can't believe that there isn't a more efficient way to do this. We are an ISP and all mail/ftp/http is served off of the netapp, any downtime will be painfull so we'd like to minimize it as best we can. What choices to migrate the data do we have? We've considered tar/cpio over nfs but that's going to take some time even if we migrate one service at a time. dump/restore seems clumsy. and plain ole 'cp' would take forever. Apparently there are issues with volcopy going from SCSI to FCAL, is that true? -- Kelsey Cummings - kgc(a)sonic.net sonic.net System Administrator 300 B Street, Ste 101 707.522.1000 (Voice) Santa Rosa, CA 95404 707.547.2199 (Fax) http://www.sonic.net/ Fingerprint = 7F 59 43 1B 44 8A 0D 57 91 08 73 73 7A 48 90 C5

2 1

Re: Stale File Handles -Reply
by Guy Harris 24 May '00

24 May '00

> is this perchance a problem with entries in the sm file? Unlikely - that's only for lock manager stuff, nor for NFS stuff.

1 0

Stale File Handles -Reply
by Timothy Cook 24 May '00

24 May '00

is this perchance a problem with entries in the sm file? >>> Jay Orr <orrjl(a)stl.nexen.com> 05/24/00 12:03pm >>> AARRRGGHH!!! Ok, so I queried the list about this a year ago (early May '99) but am dealing with it again. Guy Harris was kind enough to help, and if you're out there I could use your help again. We had a power outage a week ago that shut down all our desktop systems - but not our filers and servers. Now, we have at random times during the day a large majority of systems griping : NFS write error on host hardrock: Stale NFS file handle. (file handle: 2ae0500 51356400 20000000 aa5c8 54417810 5c140000 2ae0500 51356400) They all have the same File handle, and the toaster has no error messages in its etc/messages files. I tried rebooting a few systems, but they still generate these error messages. I was trying to figure out what file it is by extracting an INODE number, but what Guy said before doesn't match : >In 5.0, we had to add a file system ID; file handles in 5.0 and later >consist of: > > 32-bit file ID for mount point > 32-bit generation count for mount point > 8-bit snapshot ID in which file resides > 8-bit unused byte > 32-bit file ID for file > 32-bit generation count for file > 32-bit volume ID for file > 32-bit file ID for export point > 32-bit combined snapshot ID and generation number for export > point; > the upper 8 bits of that 32-bit quantity are the snapshot ID > and the lower 24 bits are the generation number. > >The file's file ID (but not the mount point's or export point's file ID) >is *big-endian*; So, any ideas as to how to figure this out? Thanks! ----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO

1 0

Time Navigator for NDMP backup
by Jeff Bryer 24 May '00

24 May '00

Does anyone have any experience with Time Navigator for backing up NetApps? I only just heard about the software yesterday, but they appear to support NDMP (clients for Solaris, AIX, Linux and NetApps). The company, Quadratec (www.quadratec-software.com), is only just entering into the North American market but they've been in the European market for awhile now. I will be getting an 30-day eval package to play with over June, but curious to hear from anyone who has already tried the software. -- Jeff Bryer bryer(a)sfu.ca Systems Administrator (604) 291-4935 Academic Computing, Simon Fraser University

1 0

RE: Stale File Handles
by Jenkinson, John P (SAIC) 24 May '00

24 May '00

OnTAP version?? this is what we got from netapp that helped us Take the 4th hex number and convert it to decimal. Then do ls -lid on the all the directories on which directory was mounted from the server in question, looking for one with an imunber equal to the mount point file ID from the file handle. you can of course do a find -inum instead -------------------- John Jenkinson BP Exploration (Alaska) > ---------- > From: Jay Orr[SMTP:orrjl@stl.nexen.com] > Sent: Wednesday, May 24, 2000 8:03 AM > To: toasters(a)mathworks.com > Cc: guy(a)netapp.com > Subject: Stale File Handles > > AARRRGGHH!!! > > Ok, so I queried the list about this a year ago (early May '99) but am > dealing with it again. Guy Harris was kind enough to help, and if you're > out there I could use your help again. > > We had a power outage a week ago that shut down all our desktop systems - > but not our filers and servers. Now, we have at random times during the > day a large majority of systems griping : > > NFS write error on host hardrock: Stale NFS file handle. > (file handle: 2ae0500 51356400 20000000 aa5c8 54417810 5c140000 2ae0500 > 51356400) > > They all have the same File handle, and the toaster has no error messages > in its etc/messages files. I tried rebooting a few systems, but they still > generate these error messages. I was trying to figure out what file it is > by extracting an INODE number, but what Guy said before doesn't match : > > >In 5.0, we had to add a file system ID; file handles in 5.0 and later > >consist of: > > > > 32-bit file ID for mount point > > 32-bit generation count for mount point > > 8-bit snapshot ID in which file resides > > 8-bit unused byte > > 32-bit file ID for file > > 32-bit generation count for file > > 32-bit volume ID for file > > 32-bit file ID for export point > > 32-bit combined snapshot ID and generation number for export > > point; > > the upper 8 bits of that 32-bit quantity are the snapshot ID > > and the lower 24 bits are the generation number. > > > >The file's file ID (but not the mount point's or export point's file ID) > >is *big-endian*; > > So, any ideas as to how to figure this out? > > > Thanks! > > ----------- > Jay Orr > Systems Administrator > Fujitsu Nexion Inc. > St. Louis, MO > >

1 0

F720 & AIT-2 tape drive
by Amy B. Caldwell 24 May '00

24 May '00

For all of you who graciously helped me with suggestions, I thought I'd write back with the results of our problem with our new F720 and the AIT-2 (Sony SDX-510C) tape drive so that everyone could benefit from our experience. The final justification from a NetApp engineer for why the AIT-2 drive would not work with our filer was due to insufficient cache on the F720's processor. Although we actually got a few complete backups using that tape drive, subsequent dumps would always fail until we got to the point (months later) that the filer itself would time out while talking to the tape drive at the beginning of a dump. We bought the filer February 2 and we got a DLT7000 tape drive on Monday, May 22, and now our problem is (supposedly) solved. We have had no problems with the DLT7000 so far (although it has less capacity -- and it's only been two days :-) ). We never tried the AIT-2 tape drive with any third party backup software. Thanks for your help! Amy Caldwell Texas A&M Nuclear Engineering

1 0

Re: File-specific NDMP backups?
by Dave Toal 23 May '00

23 May '00

> Bill, Thanks for the assistance. > The netapp returns this: > > smith> dump 0uf rst0a /vol/brs1/argus/brs-data1/prod/alr2 > DUMP: creating "/vol/brs1/../snapshot_for_backup.98" snapshot. > DUMP: Using Partial Volume Dump > DUMP: Date of this level 0 dump: Tue May 23 22:24:22 2000. > DUMP: Date of last level 0 dump: the epoch. > DUMP: Dumping /vol/brs1/argus/brs-data1/prod/alr2 to rst0a > DUMP: mapping (Pass I)[regular files] > DUMP: mapping (Pass II)[directories] > DUMP: estimated 95116 tape blocks. > DUMP: dumping (Pass III) [directories] > DUMP: dumping (Pass IV) [regular files] > DUMP: dumping (Pass V) [ACLs] > DUMP: 97906 tape blocks > DUMP: DUMP IS DONE > DUMP: Deleting "/vol/brs1/../snapshot_for_backup.98" snapshot. > Tue May 23 22:25:04 GMT [smith: ndmp_session_0]: ../common/ndmpd/tape.c:788 ndmpdTapeRead: read error. > smith> > > NetBackup returned "media write error". > > <sigh> I've just discovered that the tape won't unload from the > netapp's DLT: it's rewound but the mechanism (storagetek 9714) is jammed. > Which means I get to drive through Boston to go play with it. > > I don't want to attribute this to the read error. Generally I > don't have problems with this sort of thing, though. Also, the netapp apparently wasn't happy with being poked at: > Subject: > Cluster Alert from smith > Date: > Tue, 23 May 2000 22:44:41 +0000 > From: > unixgroup(a)t-t.com > To: > unixgroup(a)t-t.com > > > > > REBOOT on smith at Tue May 23 22:44:41 GMT 2000 > Most annoying. No downtime, though. Dave > >

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