toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

Netapp blog
by Patrick van Helden 10 Dec '09

10 Dec '09

For some time now I have been adding items regarding issues and fixes with Netapp systems into a blog type format for myself. I have posted this blog online so everyone can enjoy! http://netappfas.blogspot.com/ netappfas.blogspot.com For now I have only migrated the old articles but am planning to add new ones regularly. -- View this message in context: http://old.nabble.com/Netapp-blog-tp26727926p26727926.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

1 0

Re: migrating a volume with snapmirror
by Joel Krajden 09 Dec '09

09 Dec '09

Wonder if you can put the source volume into restricted mode first and migrate will the open read or write simply continue if the FSID are identical. It should but I have never tried it. Joel Ed Wilts wrote: > On Wed, Dec 9, 2009 at 7:56 AM, Joel Krajden <joelk(a)encs.concordia.ca > <mailto:joelk@encs.concordia.ca>> wrote: > > You might want to look at > > Solution ID: kb40272 > Last updated: 30 SEP 2009 > > Sample procedure using ' snapmirror migrate ' that avoids remounting > in a NFS environment > > > Unfortunately, it only works if all NFS access has stopped. If you > have just one host out there that you forgot about that is doing I/O to > the volume, it's remount time and users grumbling about stale handles. > > .../Ed > > Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE > ewilts(a)ewilts.org <mailto:ewilts@ewilts.org> > Contact Me Linkedin <http://www.linkedin.com/in/ewilts> > > -- | Joel Krajden | Rm: EV-7105, Tel: 514 848-2424 3052 | | Core Technologies Mgr | | | Engineering & | Email: joelk(a)encs.concordia.ca | | Computer Science | | | Concordia University | In a circus, the clowns are supposed | | Montreal, Canada | to make you laugh, not cry. |

2 1

Redoing snapmirror to a destination
by John Stoffel 09 Dec '09

09 Dec '09

Guys, Do to stupidity on my part, I managed to accidently delete a snapshot on the source side of a snapmirror pair, so that snapmirror can't continue. It's not critical, it's just our tools area, which isn't updated frequently. So now I want to re-snapmirror, but I want to limit the downtime of the clients on the destination side as much as possible when I switch them to the new re-snapmirrored volume. Currently, my clients mount east:/vol/tools, so what I'd like to do is: west> snapmirror store tools rst0a,rst1a east> vol create tools .... east> vol restrict tools east> snapmirror retrieve tools_new rst0a,rst1a Now for the tricky part: east> nfs off east> vol rename tools tools_old east> vol rename tools_new tools east> nfs on east> exportfs -a -v so that all my clients see (on a read-only volume) is a quick outage or pause in NFS traffic, then they just continue on using tools and such as usual. Or will I be forced to reboot all of my client machines one by one? Which will be truly truly truly painful... The general snapmirror update and cleanup of the old volume is trivial. It's limiting the outage to my clients that I worry about. Thanks, John John Stoffel - Senior Staff Systems Administrator - System LSI Group Toshiba America Electronic Components, Inc. - http://www.toshiba.com/taec john.stoffel(a)taec.toshiba.com - 508-486-1087

7 7

Filers and anti virus software benefit
by Joel Krajden 09 Dec '09

09 Dec '09

Most of our clients (1000) accessing the filers for home directory shares are protected with an anti virus tool that scans a file on opening. There are unmanaged clients which have access to the filers and they may or may not be protected with an anti virus that is up to date, but they only risk infecting their own files in general. Is there any real benefit to having virus checking implemented on the filer as well. Given that zero day infections will not be stopped, the additional cost of dedicated virus scanners and software licensing is significant, the performance hit with thousands of users will be high; what have other filer administrators used as arguments for or against using these products. Any experience from administrators where the product has been of value? Joel

3 2

Covert IBM N Series to NetApp Solution
by ifstat 08 Dec '09

08 Dec '09

Ok, I'm sure this has been covered somewhere during the years, and I'm well aware that this is taboo in terms of the NetApp IBM partnership, but I would like to attempt or rather investigate the following: 1. Reconfigure an IBM N3700 to FAS270, initializing the disks and deploying NetApp Data ONTAP, does anyone know if the underlying hardware (firmware) will accept this. 2. Add NetApp disks and shelves to the system, ie grow with NetApp directly and not neccessarily IBM. Anyone attempted this your info would be helpful. We are not concerned about the support agreements, financially NetApp is cheaper and easier, so in this day and age it all about the MONEY:). -- View this message in context: http://old.nabble.com/Covert-IBM-N-Series-to-NetApp-Solution-tp26690019p266… Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

3 2

Re: Redoing snapmirror to a destination
by John.Stoffel＠taec.toshiba.com 07 Dec '09

07 Dec '09

I just double checked and I don't have any common snapshots unfortunately. Time to file a req with netapp to make 'snap delete ...' Be less permissive in deleting snapshots used for any snap* relationships without a force switch of some sort... Thanks, John stoffel ----- Original Message ----- From: Michael Barrow [michael(a)barrow.me] Sent: 12/07/2009 03:02 PM PST To: John Stoffel Cc: <toasters(a)mathworks.com> Subject: Re: Redoing snapmirror to a destination Do you not have *any* Snapshots in common between the source and destination? If you have common Snapshots, you can issue a 'snapmirror resync' on the destination and the relationship will be established. This is better than swapping the volume because you'll likely get stale file handles. -- Michael Barrow michael at barrow dot me On Dec 7, 2009, at 2:50 PM, John Stoffel wrote: > > Guys, > > Do to stupidity on my part, I managed to accidently delete a snapshot > on the source side of a snapmirror pair, so that snapmirror can't > continue. It's not critical, it's just our tools area, which isn't > updated frequently. > > So now I want to re-snapmirror, but I want to limit the downtime of > the clients on the destination side as much as possible when I switch > them to the new re-snapmirrored volume. > > Currently, my clients mount east:/vol/tools, so what I'd like to do > is: > > west> snapmirror store tools rst0a,rst1a > > east> vol create tools .... > east> vol restrict tools > east> snapmirror retrieve tools_new rst0a,rst1a > > Now for the tricky part: > > east> nfs off > east> vol rename tools tools_old > east> vol rename tools_new tools > east> nfs on > east> exportfs -a -v > > so that all my clients see (on a read-only volume) is a quick outage > or pause in NFS traffic, then they just continue on using tools and > such as usual. > > Or will I be forced to reboot all of my client machines one by one? > Which will be truly truly truly painful... > > The general snapmirror update and cleanup of the old volume is > trivial. It's limiting the outage to my clients that I worry about. > > Thanks, > John > John Stoffel - Senior Staff Systems Administrator - System LSI Group > Toshiba America Electronic Components, Inc. - http://www.toshiba.com/taec > john.stoffel(a)taec.toshiba.com - 508-486-1087 > > > >

1 0

Re: Redoing snapmirror to a destination
by John.Stoffel＠taec.toshiba.com 07 Dec '09

07 Dec '09

Hmmm fsid is something to keep in mind. I can do a couple of tests vols later to see what happens. Thanks for the feedback all! Thanks, John stoffel ----- Original Message ----- From: Bert Kiers [kiersb(a)xs4all.net] Sent: 12/08/2009 12:34 AM CET To: John Stoffel Cc: toasters(a)mathworks.com Subject: Re: Redoing snapmirror to a destination On Mon, Dec 07, 2009 at 05:50:20PM -0500, John Stoffel wrote: Hi, > so that all my clients see (on a read-only volume) is a quick outage > or pause in NFS traffic, then they just continue on using tools and > such as usual. > Or will I be forced to reboot all of my client machines one by one? > Which will be truly truly truly painful... The trick is to keep the fsid the same. I doubt the steps you outline will do that. Is it possible to tell a filer to use a particular fsid for a volume? (I guess snapmirror does not change inodes, what is also needed here.) Grtnx, -- Bert Kiers XS4ALL UNIX systeembeheerder, suspected terrorist 1984 was not meant as a manual

1 0

Re: Redoing snapmirror to a destination
by John.Stoffel＠taec.toshiba.com 07 Dec '09

07 Dec '09

No common snaps that I know of, but its a good idea. John Thanks, John stoffel ----- Original Message ----- From: "Page, Jeremy" [jeremy.page(a)gilbarco.com] Sent: 12/07/2009 03:04 PM PST To: John Stoffel; <toasters(a)mathworks.com> Subject: RE: Redoing snapmirror to a destination I think you can resynch if there are any common snapshots, did you call Netapp? -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of John Stoffel Sent: Monday, December 07, 2009 5:50 PM To: toasters(a)mathworks.com Subject: Redoing snapmirror to a destination Guys, Do to stupidity on my part, I managed to accidently delete a snapshot on the source side of a snapmirror pair, so that snapmirror can't continue. It's not critical, it's just our tools area, which isn't updated frequently. So now I want to re-snapmirror, but I want to limit the downtime of the clients on the destination side as much as possible when I switch them to the new re-snapmirrored volume. Currently, my clients mount east:/vol/tools, so what I'd like to do is: west> snapmirror store tools rst0a,rst1a east> vol create tools .... east> vol restrict tools east> snapmirror retrieve tools_new rst0a,rst1a Now for the tricky part: east> nfs off east> vol rename tools tools_old east> vol rename tools_new tools east> nfs on east> exportfs -a -v so that all my clients see (on a read-only volume) is a quick outage or pause in NFS traffic, then they just continue on using tools and such as usual. Or will I be forced to reboot all of my client machines one by one? Which will be truly truly truly painful... The general snapmirror update and cleanup of the old volume is trivial. It's limiting the outage to my clients that I worry about. Thanks, John John Stoffel - Senior Staff Systems Administrator - System LSI Group Toshiba America Electronic Components, Inc. - http://www.toshiba.com/taec john.stoffel(a)taec.toshiba.com - 508-486-1087 Please be advised that this email may contain confidential information. If you are not the intended recipient, please do not read, copy or re-transmit this email. If you have received this email in error, please notify us by email by replying to the sender and by telephone (call us collect at +1 202-828-0850) and delete this message and any attachments. Thank you in advance for your cooperation and assistance. In addition, Danaher and its subsidiaries disclaim that the content of this email constitutes an offer to enter into, or the acceptance of, any contract or agreement or any amendment thereto; provided that the foregoing disclaimer does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment to this email.

1 0

Does anyone know if the dedup is across the entire aggr or just the volume in 7.3.x?
by Page, Jeremy 07 Dec '09

07 Dec '09

Does anyone know if the dedup is across the entire aggr or just the volume in 7.3.x? I'd like to break up my VMware environment so we have a volume per service (so SQL Warehouse volume, Call Center etc). This would be nice because we could delegate the rights to them, move them around if specific apps required more IO and aid in troubleshooting. The question I have is will this kill our dedup percentages? Please be advised that this email may contain confidential information. If you are not the intended recipient, please do not read, copy or re-transmit this email. If you have received this email in error, please notify us by email by replying to the sender and by telephone (call us collect at +1 202-828-0850) and delete this message and any attachments. Thank you in advance for your cooperation and assistance. In addition, Danaher and its subsidiaries disclaim that the content of this email constitutes an offer to enter into, or the acceptance of, any contract or agreement or any amendment thereto; provided that the foregoing disclaimer does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment to this email.

2 1

SMVI 2.0 problem
by steve klise 02 Dec '09

02 Dec '09

ok, scratching my head here... I just upgraded the new SMVI 2.0 with file level restore.. HURAYY.. Its only been a year, but I guess you cant rush perfection. I was previously running 1.2 and have the typical wait time errors, but for the most part is successful. Specs: ESX vshpere 4.0 (non 4i flavor) SMIV 2.0 (installed on VMWare VIC physical server) 6040's DOT 7.3.11 FC HP DL380s G5(for now) problem: When I try and do a single file restore via self service option, (to and from the same VM guest), I go to select the vm in the restore agent from the guest OS, I press OK. Then I get an error: Failed to retrieve backupList fro the source guest. And I only have an OK button. i have tried from multiple guest os'es. Same result. I looked in the log, and this is just before the popup I get: at RestoreAgentWCFSvc.RestoreAgent.GetBackupsAndDisks(GuestIdentifier guest, List`1& backupRootedHierarchy, List`1& diskRootedHierarchy, Exception& exFromHyperVisor) then the error in the log.. 11/23/2009 01:31:48:154 (PID:01684 ,TID:00006): Failed to retrieve backupList for the source guest Any help is appreciated.. -- View this message in context: http://old.nabble.com/SMVI-2.0-problem-tp26486178p26486178.html Sent from the Network Appliance - Toasters mailing list archive at Nabble.com.

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