Subscribe

System manager 2.0R1 not following Netapp recommendation on MetroCluster Aggregates

I just created my first 64-bit aggregate with System Manager 2.0R1 on our Ontap 8.0.1 system.

It failed partialy, among things it said was that it could not set snap schedule.

Unfortunately, it did succeed but Ontap CLI immediatly complained that it is not recommended.

I ended up with a 64-bit aggregate, with a default aggregate snap schedule set, aggregate option nosnap=off

I researched some and found following Netapp KB and followed it:

https://kb.netapp.com/support/index?page=content&id=2011977

Unfortunately I didn't set the aggregate nosnap option so Ontap continued complaining despite setting the "off schedule"

One more thing I noticed is that system manager didn't seem to take care of how many spares would be left after creating the aggregate.

I came to the last "continue" wizard page and there I stopped as I didn't have time to test if the last click would bring out any kind of warning/error about not having any spares left after creating the aggregate.

With Ontap (long missing) dissability to remove disks from an aggregate I view the spare question as very serious as it might not be noticed until too late when the aggregate already is in production.

And there seems to be some serious bug related to aggregate snapshots on syncmirrored aggregates:

http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=162634

Then again, it might have given an error at the last step when trying to create the aggregate.....

Re: System manager 2.0R1 not following Netapp recommendation on MetroCluster Aggregates

Hi,

Since you have not gotten an answer, you may want to ask this question in the NetApp Support Community.  The current customers, partners and internal Subject Matter Experts are addressing technical product questions there.

Mike