HA - Assign Disks to One Node Failover Issues?

Dshrout311

This may be a basic question, and I am pretty sure I already know the answer, but I wanted to verify.

A client of mine has a FAS2520 with HA Controllers running 12 - 2.42TB disks (6 per node). Due to the need to increase the capacity of their system they've purchased a new DS4243 (typo) DS4246 shelf with 12 - 3.63TB disks.

The shelf has been connected to the the controllers with HA in mind. 

I was hoping to accomplish two things for them. Increase the storage size for them as well as add disks to the current aggregates to increase overall speed. I know I can add the new disks to their current aggregates, but because of the size difference that is generally not recommended and overtime it may slow things down.

So my question - is it possible to assign all the new disks to one of the nodes, create a single aggregate using all the disks, migrate the volumes on the old aggregate to the newly created one, then wipe out the old aggregate, assign the disks to a single node, and create a new aggregate using all the 2.42 disks. Will this configuration break HA? If a node goes down will it make the aggregate that was created on that node using all the disks unavailable? Is a better option to replace the drives in the 2520 with the same size drives as the new shelf?

Sorry if this is pretty basic, I'm relatively new to NetApp and am trying to make the best decision for the client.

Thanks,

SpindleNinja

Thanks for posting.  Looks like they are ADPed!  and yes I would read up on it.  it's a great feature.    

 Also note that the aggrs will be 11 drives each,  you need spares.   

Here's what you can do though: 

First off, disable disk autoassign. 

->storage disk option modify -node * -autoassign off

1. Reassign all the disks in shelf 01 to controller 2 and create an aggr. 

-> storage disk removeowner -disk 1.1.x 

-> storage disk assign -owner node2

create your new aggr on node 2 (either GUI or CLI) 

2. move all volumes off aggr2 if they're any left.

3. delete aggr2  (the partitions will now show as spares)  

4. You can re-assign the data partitions to controller 1 by the following: 

-> set advanced 

-> disk removeowner -disk x.x.x -data true
-> disk assign -disk x.x.x -data true -owner NODE1
-> disk show -fields data-owner, root-owner     (to verify that everything is moved over correctly) 

5. zero all the spare 

-> storage disk zerospares

After the drives are zeroed, feel free to grow the aggr on node1.   

Re-enable disk autoassign 

->storage disk option modify -node * -autoassign on