we turn off all aggregate snap reserve on all of our filers without any issues since we do not use any of the aggregate snapshots or copy features. we have had no issues with coredumps during failovers etc.

-- Daniel Leeds Senior Systems Administrator Edmunds.com

-----Original Message----- From: owner-toasters@mathworks.com on behalf of Glenn Walker Sent: Mon 12/18/2006 3:41 PM To: Michael Schipp; toasters@mathworks.com Subject: RE: Aggregrate snap reserve (again)

I'm pretty sure that the aggr snap reserve is not needed for core dump - this is written to the 10% overhead space (or to spare drives, depending on how you've configured your filer), then when the filer comes back up and the 'savecore' is performed, it is written to the /etc/crash directory.

As for the aggr copy command, that is news to me (you see how often I've used it).

The one thing you did overlook: restoring an aggregate - not individual volume, mind you. This is the same concept as vol snap restore.

Glenn

________________________________

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Michael Schipp Sent: Monday, December 18, 2006 5:54 PM To: toasters@mathworks.com Subject: Aggregrate snap reserve (again)

Hi all,

We have had a lot of talk since DOT 7 of this but just to clear it up some (I hope).

aggregate snapshots are required if you use (default 5%);

* RAID SyncMirror and/or MetroCluster configurations.

* Aggr copy command

* Core dump

IS the core dump in on aggr0 snap space only?

So if a Filer/FAS has two aggregates and not using or needing SyncMirror and the aggrcopy command is it safe to turn off the aggregate snap reserve for aggr1 (still leaving snap reserve on for aggr0 for core dumps)?

NetApp - are aggregates snap reserve used for any other purpose?

Thanks

Michael