Snapshots "grow" when data contained in these snapshots changes. So after snapshot was taken some host activity resulted in large amount of changed data. You have to check what your hosts do - there is nothing NetApp can do about it.
... View more
I'm not exactly sure what do you mean under "data store is changed", but as a general rule - volume name is relevant only during initial mount request. When request is completed client gets back opaque handle that is now used to access data. Renaming volume does not change this handle, so any client that had volume mounted under old name continues to access the same volume, even though it now has new name. That's probably what you observe. You need to remount data store to actually access new volume. There is no way to switch it on the fly.
... View more
Strictly speaking it says “You must be running a minimum OS version of Data ONTAP 8.1.y”, but you are right, it is not 8.2 - was answering from memory. Sorry.
... View more
Well, KB article mentioned says "do no attempt this procedure unless you are running 8.2". I do not have enough background to question it, although I recently installed 8.2.1 C-Mod on 3170 running 7G without any apparent issues.
... View more
The only reason to use e0M is when you absolutely need separate physical management network and do not want to waste 1GbE (or 10G) for it.
... View more
Do not be confused. You do not need to use e0M - any interface can be used to manage filer. You can add mezzanine card with 2 x 10G. You can't add more 1GbE to 2240.
... View more
SVM sees only those volumes that had been allocated to it. It is cluster administrator who sees all aggregates. If you want to restrict it - assign aggregates exclusively to SVM and let vserver (not cluster) admin to do it. Makes sense in multitenant environment anyway.
... View more
You will need to at least install SnapMirror license and configure networking. You can also SnapMirror root volume, this will duplicate as much of configuration as possible. You will still need to reconfigure networking and reinstall licenses to remain compliant (licenses are filer specific).
... View more
This means replacement disk was marked as failed in previous system. It is possible to unfail it in advanced mode, but there must be a reason why it was marked as failed in the first place.
... View more
1. so this is just detaching the shelf from a local SAS port and attaching it to the ATTO bridge? this should even work online, Could you provide link to NetApp document that confirms it? Hot shelf relocation was never supported. From Storage Subsystem Technical FAQ: Nondisruptive relocation or removal of storage shelves is a process referred to as single-shelf removal (SSR) and is not currently supported by NetApp.
... View more
Why is it not hot add scenario? It was always possible to hot add shelves. Make sure that option disk.auto_assign (and disk.auto_assign_shelf if applicable to your version) is disabled and manually assign disks to required controller and pool. Then re-enable options if required.
... View more