Looks like feature is broken in 8.x 7-Mode. I got the same result on 8.2. Testing with "exportfs -c" succeeds, as well as mount request from client, but then client got error response when actually accessing volume. I also verified that client does send AUTH_NONE as expected. I then tested on 9.0RC1 (C-mode obviously) and it works as expected (setting sec=none as the only accepted authentication will effectively result in all_squash behavior). I do not have Data ONTAP 7.x to test right now, but I am fairly confident it was working in the past. I suggest you open case with NetApp support. May be there is some hidden option to do it, but I could not find one. If you get it working I appreciate if you share information (I found old post two years ago with the same question and the same problem with sec=none not working). Thank you!
... View more
If my understanding is correct, cDOT requires separate root aggrage and we can host data SVMs/volumes at root aggregate. Is this correct? Yes and no (unless you made a typo). cDOT requires separate root aggregate and it is highly discouraged to host SVM data on it. It is dedicated to root volume only. While we plan to have switchless cluster, it would take 2 interfaces (1 - 1G and 1 - 10G) Wrong. cDOT requires two dedicated 10G ports for cluster interconnect (switched or switchless does not matter). Everything else can in principle share the same remaining physical ports; it depends entirely on your network connectivity. Finally question about SVMs and volumes. At our current setup we have the same volume accessible from different network/purposes. How can I setup the volumes/SVM the same way? Well, if you want to avoid redesign - migrate each 7-Mode filer to own SVM keeping the same names and addresses. This will give you familiar management model where you have two independent servers with own resources. Clients won't notice anything. Finally - is there any document/note/report which would help me to understand differences between cDOT and 7-mode and make our transition painless? You could start with http://transition.netapp.com/. But judging by your question, I highly recommend to arrange for professional service, either from NetAp or from NetApp partner, to plan and implement such migration.
... View more
From Brocade documentation: "This command applicable only to 8G FC ports; it is not supported on Condor 3-based platforms." 6505 and 6510 are 16G platforms (even if you use 8G SFP) so they should not need it.
... View more
To free space you need to delete all snapshots that keep "copy" of deleted file(s). Whether it happens "next time snapshot schedule runs" depends on which snapshots have these files and whether these snapshots are deleted when "snapshot schedule runs".
... View more
Indocators are described in Platform Monitoring Guide (https://library.netapp.com/ecm/ecm_download_file/ECMP1112529). Not sure what you mean under "controls" but usually there is none - it starts on power on without any manual intervention. Connections are outlined in System Installation and Setup - you should have it if you downloaded the whole documents set for FAS2040. All of them do assume that you are familiar with basic concepts (controller, shelf etc). I think you would get better responses if you asked more precise questions. Are you NetApp partner by any chance or do you have some training units for NetApp University? Web based trainings for platforms are good and provide exactly what you ask, at least those that deal with servicing them.
... View more
I am not aware of any protocol related limit on number of files in a volume. There is max directory size and theoretical limit on number of files in a volume. The latter is derived from the minimal file size of 4K; and max directory size can be increased in principle (although not recommended).
... View more
I am not aware of any way doing it with NFS (with CIFS it may be possible to define share with this path). If you have FlexClone license, you can clone snapshot and mount resulting FlexClone volume to get access to it.
... View more
As a rule of thumb, to preserve 7-Mode identity NAS workloads need two SVM and SAN - one. This is due to single-image SAN configuration which allows you to consolidate LUNs while NAS identity is tied to controller.
... View more
Yes, you should be able to do full baseline restore to different volume (actually different qtree, so may be on the same volume), but this will transfer the same amount of data over WAN an your main issue was available WAN bandwidth. My idea was to perform incremental restore, which may transfer less data. Actually your method may be faster because it moves just one VM, instead of full volume (i.e. full datastore).
... View more
There may be more efficient ways to restore snapshots back to production, but I am not sure you really want it. It depends on how data is distributed over volumes. I.e. you can restore only full snapshots, which means - everything on a volume (or qtree). If it is datastore shared by multiple VMs doing it would also revert state of everything on this datastore. ... what may work is break snapmirror perform incremental restore (snapvault restore -r) from vault copy needed data to production system resync snapmirror This should transfer only incremental changes over WAN, but leaves your mirror unprotected for duration of restore. I would recommend testing it in lab environment though.
... View more
Did you try "snapmirror update -source-snapshot"? It should work for vaulting. Or you could try modify these snapshots and assign suitable snapmirror name.
... View more
I also would like to know if this is available now. Workgroup mode is available starting with ONTAP 9.0RC1 which is available for download.
... View more
What are you going to do with output of this command? If you are requested to run it by support, then support is the best place to ask for detailed explanation how to run it.
... View more
In general you can replace any head with any head as long as you are able to attach old shelves to new head and resulting configuration is supported according to HWU (shelf types, storage limits etc). The steps in most cases are the same, except here you need to decide whether you want root on - presumably, existing - internal disks in 2552 or want to keep root on shelves from 3210.
... View more
Snapshot "size" is the amount of data that was changed (i.e. overwritten) or deleted since snapshot had been taken. Usually the older is snapshot, the more data was changed so it is shown as "bigger".
... View more