Peter.Learmonth at netapp
May 18, 2011, 7:38 AM
Post #3 of 5
RE: Moving disks to another controller (head)
[In reply to]
I'm pretty sure you do need to take care of ownership of disks. I would do a modified version of step 4 and "disk remove_ownership" in maint mode on the source heads. Then do disk assign after adding to the destination. You don't have to type in the sysid or worry about which one goes where.
Also, in step 1, make sure FW of both disks and shelves is up to date before moving stuff. Should happen automagically as part of upgrading DOT.
Nuking old vols/aggrs and zeroing can be done at destination. As Jeff said, any foreign aggrs will be listed as such, and any dupe names get (number) appended to their name.
From: Jeff Bryer [mailto:bryer [at] sfu]
Sent: Wednesday, May 18, 2011 7:14 AM
To: Steve Losen
Cc: toasters [at] mathworks
Subject: Re: Moving disks to another controller (head)
If you are just adding the shelves to another system you can choose to hot add them.
Otherwise what you've outlined is similar to a head swap (docs for that are on NOW).
No you don't need to unown the disks on the source filer.
The foreign aggregates will be renamed, used to add (1) to the name, but it's been awhile since
I've done that.
And of course, make sure you keep track of anything for those volumes that could be lost (LUN mappings,
CIFS shares, maybe snapshot schedules, etc).
----- Original Message -----
From: "Steve Losen" <scl [at] sasha>
To: toasters [at] mathworks
Sent: Wednesday, May 18, 2011 4:28:52 AM
Subject: Moving disks to another controller (head)
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 [at] virginia phone: 434-924-0640
University of Virginia ITC Unix Support
Jeff Bryer bryer [at] sfu
Systems Administrator (778) 782-1016
IT Infrastructure, Simon Fraser University