Remove an aggregate from MCC

[Jeff_Cai]

Hi All,

IHAC is running a MCC in 8.3.1P1 with 2 aggregates at each site, now they want to remove one aggregate at site A. What's the best practices to do this?

Do we need to follow the KB 1015185 to move the MDV_CSR volume, then remove the aggregate? Or just run the following command:

metrocluster configure -allow-with-one-aggregate true, and then remove the aggregate?

Thanks,

Jeff Cai

[niels]

Hi Jeff,

you need to follow the KB.

The parameter "-allow-with-one-aggregate true" is only valid and working during initial MCC setup.

Kind regards, Niels

[Jeff_Cai]

Hi Niels,

Thanks for your reply.

Can we remove the aggregate when "-allow-with-one-aggregate" is false? Because there are just two aggregates.

Best Regards,

Jeff

[niels · Accepted solution]

Yes, you can. As said, this option is only valid during initial MCC setup.

It just skips the check that both MDVs need to reside on different aggregates for redundancy purposes.

After the MCC has been configured, this option is of no use anymore. The MetroCluster as of today does not check where the MDVs reside after MCC has been configured.

There is a BURT open though for a future improvement to have ONTAP relocate one of the MDVs automatically, once a second aggregate is created.

Kind regards, Niels

[PUKKA_XUJIE]

Hi Niels,

"There is a BURT open though for a future improvement to have ONTAP relocate one of the MDVs automatically, once a second aggregate is created."

What do you mean ？

[niels]

"BURT" is the NetApp internal bug and new feature tracking tool.

Once a bug is hit and reported to NetApp support or a new feature is requested a new BURT is opened internally to track it.

There is a tool on the NetApp support site where you can look for public BURTS:

https://mysupport.netapp.com/NOW/cgi-bin/bol/

With the comment I just wanted to point out that engineering is working on improving the automated MDV placement to make it even more resilient and flexible.

regards, Niels