FAS2554 root data partition configuration

[PedroOrt]

Hello all,

Is it possible to configure a cluster with root data partition, where all data partitions belong to one aggregate but the root partitions are split between the  two root aggregates?

Example: FAS2554 with 20 disks, 10 root partitions for root_aggr_01, 10 root partitions for root_aggr_02, 20 data partitions for data_aggr_01.

Assuming this is possible, what would be the best way to achieve this, starting with the typical root data partition configuration:

-10 root partitions for root_aggr_01 + 10 data partitions for  data_aggr_01.

-10 root partitions for root_aggr_02 + 10 data partitions for data_aggr_02.

Can I delete the "data_aggr_02" and the add these data partitions to  "data_aggr_01" ?

Thanks for your help,

Pedro

[SpindleNinja · Accepted solution]

Yep.   You need to remove the owner of the data part of the partition and the assign it to the partner.   

set adv 

disk removeowner -disk x.x.x -data true
disk assign -disk x.x.x -data true -owner NODEx
disk show -fields data-owner, root-owner

[PedroOrt]

Thank you, I've sucessfully completed the change.

BTW, does it matter which node owns the "container" ? 

[SpindleNinja]

With ADP R-D and R-D-D, generally the root part and the container have the same owner by default.     After the initial ADP config on controller initlization I don't think it matters though.    I've always tried to keep them balanced though.  

Check out here:   

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-psmg%2FGUID-6BCE9E33-D9FD-4250-B7FA-88761158D4DD.html&cp=2_8_6_4_0 

with R-D "The container disk and the two partitions do not all need to be owned by the same node in the HA pair as long as they are all owned by one of the nodes in the HA pair. However, when you use a partition in an aggregate, it must be owned by the same node that owns the aggregate" 

[paul_stejskal]

Make sure you reallocate after you do so, otherwise you might experience less performance (depending on # of disks added). https://kb.netapp.com/app/answers/answer_view/a_id/1001574/loc/en_US

https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-cmpr-970%2FTOC__volume__reallocation.html&lang=en

I usually recommend to customers to do a "reallocation start -f true -p true -path /vol/volumename" and do one volume in the aggregate at a time. Usually that is enough to balance it out. Start from your busiest volume that may be the smallest and work your way to more idle volumes.