toasters

toasters@lists.teaparty.net

1 participants
13515 discussions

volume, qtree snapmirror resync question
by Steve Losen 20 Jun '11

20 Jun '11

Hi Toasters, We have recently upgraded to ONTAP 8.0.1 and are migrating to 64 bit aggrs/vols. Quick question: Say I have 32 bit volume A on primary storage being volume snapmirrored to 32 bit volume B on secondary storage. A has one qtree, then entire volume itself. I create 64 bit volume C on secondary storage and use qtree snapmirror to copy /vol/B/- to /vol/C/qtree Is there any way to resync C and A now? Will this work on secondary? snapmirror resync -S primary:/vol/A/- /vol/C/qtree I suppose I must snapmirror break the B, C relationship first. If this will work then we can migrate a lot of our secondary storage to 64 bit without heavily impacting primary storage. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

1 0

Truncated SSH ouptut on 8.x?
by A Darren Dunham 07 Jun '11

07 Jun '11

Anyone seen differences with SSH command output on 8.x filers? I've encountered this a few times lately, and as best I can tell it's always been on 8.x machines. It appears to be more likely to happen on the first command to a filer in a while. I'll run something like "ssh <filer> exportfs" and either get a line or two or just a normal prompt returned with no output. Never an error. Then I'll just repeat the last command and get full output. In fact I can repeat it multiple times and never see the error again. There is a KB article that seems similar (https://kb.netapp.com/support/index?page=content&id=2013198), but it's not really the same, affects 7.x, and the variable that is mentioned to resolve doesn't seem appropriate. I don't have a lot of hard data on this, I'm not prepared to open a ticket on just yet. But I'm wondering if others have seen it. Thanks, -- Darren

1 0

RE: Hot remove disk shelves?
by Steiner, Jeffrey 02 Jun '11

02 Jun '11

I've heard that asked before, and the answer was no. The issue was something about internal device maps. The filers build maps of which devices are where on the loops, and that includes the shelf itself as well as the drives. Both controllers are aware of the shelves at all times, even if they aren't actually using disks inside them. The only safe way to remove the shelf is at a time when neither controller is aware of it, and that means when both are off. >-----Original Message----- >From: Borzenkov, Andrey [mailto:andrey.borzenkov@ts.fujitsu.com] >Sent: Thursday, June 02, 2011 4:06 PM >To: Steiner, Jeffrey; Blake Golliher; Steve Losen >Cc: toasters(a)mathworks.com >Subject: RE: Hot remove disk shelves? > >Would it be possible via takeover/giveback? I.e. - takeover node2, >unplug shelf on node2 side then do the same with node1? Would it still >lead to problem mentioned? > > >--- >With best regards > >Andrey Borzenkov >Senior system engineer >Service operations > >-----Original Message----- >From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] >On Behalf Of Steiner, Jeffrey >Sent: Thursday, June 02, 2011 6:45 PM >To: Blake Golliher; Steve Losen >Cc: toasters(a)mathworks.com >Subject: RE: Hot remove disk shelves? > >It may appear to work at first, but you'll have a panic and crash >eventually. It might last a week or two, but you'll eventually have >problems. > >If you move quick and you have your FC/NFS timeouts set right, you can >shut down, decable the shelves, and turn it back on before hosts will >notice. I've done that myself more than a few times. > > >>-----Original Message----- >>From: Blake Golliher [mailto:thelastman@gmail.com] >>Sent: Thursday, June 02, 2011 3:07 PM >>To: Steve Losen >>Cc: toasters(a)mathworks.com >>Subject: Re: Hot remove disk shelves? >> >>I've seen people do this without problems, but I've not had to do it >>yet myself. Having the disks unassigned is a good idea since you'll >>want them unowned when you add them to other heads. If you can afford >>to do it while in takeover mode that probably couldn't hurt. >> >>Let us know how it goes. I'm under the impression this works, but is >>unsupported from netapp eng still. >> >>-Blake >> >>On Thu, Jun 2, 2011 at 6:03 AM, Steve Losen ><scl(a)sasha.acc.virginia.edu> >>wrote: >>> >>> Hello Toasters, >>> >>> We have a FAS3170 HA pair with some SATA disk shelves (AT-FCX) >>> attached to the end of a chain where none of the disks are in use >>> (all are spares, all have ownership assigned). We are running >>> ONTAP 8.0.1. >>> >>> The chain is singly attached to both controllers, i.e., the >>> shelf "A" modules are chained to a single FC adapter on one >>> controller and the shelf "B" modules are chained to a single >>> FC adapter on the other controller. >>> >>> The shelves we want to remove are at the far end of the chain. >>> Essentially we want to undo the result of a hot shelf add without >>> downtime. >>> >>> Is it possible to hot remove these shelves? Would it help to >>> "un-own" the disks first? >>> >>> I suppose this could be done using CF takeover/giveback >>> but that might be too disruptive. >>> >>> Steve Losen scl(a)virginia.edu phone: 434-924-0640 >>> >>> University of Virginia ITC Unix Support >>> >>> >>> >

2 1

Hot remove disk shelves?
by Steve Losen 02 Jun '11

02 Jun '11

Hello Toasters, We have a FAS3170 HA pair with some SATA disk shelves (AT-FCX) attached to the end of a chain where none of the disks are in use (all are spares, all have ownership assigned). We are running ONTAP 8.0.1. The chain is singly attached to both controllers, i.e., the shelf "A" modules are chained to a single FC adapter on one controller and the shelf "B" modules are chained to a single FC adapter on the other controller. The shelves we want to remove are at the far end of the chain. Essentially we want to undo the result of a hot shelf add without downtime. Is it possible to hot remove these shelves? Would it help to "un-own" the disks first? I suppose this could be done using CF takeover/giveback but that might be too disruptive. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

5 4

Moving disks to another controller (head)
by Steve Losen 18 May '11

18 May '11

Hi Toasters, I need to physically move some disks/aggregates to another controller. Do you see anything wrong with this procedure? 1) upgrade DOT to the same version on both heads (7.3.3) 2) shut down and power off both heads 3) physically move the disk shelves 4) boot the destination head in maintenance mode and use "disk assign" to take ownership of the moved disks 5) boot the destination head normally 6) aggr online the foreign aggregates I am concerned about step 4 above. Will it work or do I need to boot the source filer in maintenance mode and change the disk ownership to the destination head before moving the disks? In step 5 some of the foreign aggregates will have names that conflict with native aggregates. I presume that when ONTAP boots it will automatically rename the foreign aggrs as necessary. Or must I rename them on the source filer beforehand? I know that some of you do this routinely, so I appreciate any words of advice. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

4 3

Partner WWNN must match local WWNN to start FCP under Single Image
by Chaim Rieger 13 May '11

13 May '11

getting this error when trying ti start fcp cf is disabled and not licensed any ideas ?

1 0

Re: Snapmirror to Tape - crazy idea
by John Stoffel 11 May '11

11 May '11

Mike> The only thing to be aware of with LREP is that it is Qtree Mike> level replication. If you want volume Snapmirror (so your Mike> snapshots are also mirrored), LREP will not be too helpful. I'm volume snapmirror. And from all I've read and seen, there's no way to do incremental volume snapmirrors to tape (or LREP). Oh well, no real surprise. John

1 0

Snapmirror to Tape - crazy idea
by John Stoffel 10 May '11

10 May '11

Guys, Has anyone ever tried to do a snapmirror to tape of a volume, then you retrieve it onto the destination. Then can you do the next snapmirror update for the volume to tape as well? The idea is that it takes so much time to write and read 10Tb of tape, not even counting the FedEx across country time, that it might make sense to also write the next snapmirror update to tape as well. God knows I'm tempted to try this... John

3 2

Secure Share Access program on W2K8 server issue
by Paul Letta 28 Apr '11

28 Apr '11

Hi, Is there any one out there using Secure Share Access to view/set file properties in a volume with unix style permissions from a Windows client ? We've used this for years with no issue. But installing the latest Secure Share (3.3) onto Win2K8 server machines doesn't work like it used to. The software installs fine, but when I right click on a file and go to properties, I do not see the SecureShare tab. Any suggestions ? Thanks, Paul

2 2

Procedure for moving volumes on nearstore
by Steve Losen 15 Apr '11

15 Apr '11

Hello Toasters, This is just a little procedure that I figured out by trial and error. I needed to migrate some snapmirror destination volumes on a nearstore to other aggregates on the same nearstore. With a few modifications, this procedure will also work when moving a volume to a different nearstore filer. To avoid load on the primary storage filer I ran the full snapmirror copy (snapmirror initialize) locally on the nearstore filer. However, this left me with a snapmirror snapshot that was not deleted automatically and required deletion by hand. Here is the procedure. Assume oldvol on a nearstore filer is being snapmirrored from a primary storage filer. You want to move oldvol to a different aggregate on the nearstore. On the nearstore (destination) filer do this: vol create newvol newaggr XXXXg vol restrict newvol Now do the full snapmirror locally: snapmirror initialize -S oldvol newvol You may want to comment out your snapmirror.conf line for oldvol to avoid numerous logged errors if a scheduled snapmirror (from primary) of oldvol fails due to oldvol being busy. When the full copy is done, replace oldvol with newvol. vol offline oldvol vol destroy oldvol vol rename newvol oldvol Un-comment your snapmirror.conf line for oldvol and wait a bit for the filer to notice the change. Then snapmirror update from primary storage: snapmirror update oldvol Yes, this actually works. You want to update so that another snapmirror snapshot is created in oldvol. In addition to this snapshot you have a previous snapmirror snapshot that is locked and will not be deleted automatically. snap list -n oldvol The locked snapshot is marked "(snapmirror)". You need to delete it by hand, but you cannot do this without breaking the mirror: snapmirror break oldvol snap delete oldvol lockedsnapshotname Also delete this same snapshot from the source volume. Run this on the primary filer: snap delete oldvol lockedsnapshotname Now re-establish the mirror on the nearstore: snapmirror resync oldvol And you're done. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

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