Community

Subscribe
Highlighted
Accepted Solution

aggregate snap reserve size

Hello guys,

I would like to know what is the minimal aggregate snap reserve size i may left on the system?

Re: aggregate snap reserve size

Hi,

I've reduced this to 2% before, but be very careful with reducing aggr snap reserve as it gets used for a few different things.  One example is semi-sync SnapMirror where it is used as a buffer.

Re: aggregate snap reserve size

Thank you Yeoman,

In my case there are no any snapmirror at all.

Slava Chubar

Professional Services Engineer

NetApp

972.3.9205538 Direct

972.52.3120538 Mobile

slava@netapp.com

www.netapp.com

Re: aggregate snap reserve size

If you don't have RAID syncmirror and / or a metrocluster configuration and you don't expect to use aggregate snap restores (has anyone ever used this???), you don't need snapshots on aggregate level and therefore can set the aggregate snap reserve to 0%. If you use aggregate snapshots set the snap reserve to such a level that you normally don't run of reserve space.

We are running on all our non metrocluster configurations with 0% aggregate snap reserve and no aggregate snapshots (snap sched -A <aggregate> 0) ever since we migrated to ontap 7.0.

Re: aggregate snap reserve size

Thank you Dukers,

As I know, you need to save some space for some maintenance processes like block reallocation or in case of aggr inconsistence when you need to run wafl_check.

Slava Chubar

Professional Services Engineer

NetApp

972.3.9205538 Direct

972.52.3120538 Mobile

slava@netapp.com

www.netapp.com

Re: aggregate snap reserve size

I wouldn't go below 3% aggregate snap reserve (that does let you get back 2% from the default at least) as doing otherwise can cause data corruption issues (as well as cause issues upgrading to 7.3.x).

See this bug report as well....

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

There was also a general warning in the 7.3.x upgrade docs about this as well giving 3% as a minimum.

I would stay away from 0% aggregate snap reserve as I have personally had data corruption issues with this (a volume with "file" space guarantee got set to "none" silently and subsequently had some corrupted files which we didn't notice for a couple months due to some odd circumstances).

Re: aggregate snap reserve size

The bug is not about snap reserve size for the aggregate, but about free space in the aggregate. Using a snap reserve of more than 0% is only a tool to make sure nothing can ever take up all the space in an aggregate.

I always have at least 10% free in the aggregate, therefore for me this will never be an issue. But if I am wrong I would really like to know about it.

Re: aggregate snap reserve size

This thread is a top Google result for "aggregate snap reserve"

  Have you come across any contrary information?

Re: aggregate snap reserve size

Hi, we always leave default 5%.

And disabling aggr snap reserve only with metrocluster configuration or when extra space needed (not best practice but...).

http://now.netapp.com/NOW/knowledge/docs/ontap/rel727_vs/html/ontap/sysadmin/provisioning/concept/c_oc_prov_sys-maintenance-aggr-snapshot-copy-managin...

Best practice for us is at least 10% free space in aggregate.

Re: aggregate snap reserve size

There is no right or wrong here, just do what makes you comfortable.

If you don't use aggregate snapshots, there is no need to to reserve space in the aggregate. But some use the snap reserve as a tool to make sure there is always (enough) free space in the aggregate.