First you can not downgrade from 8.3 (C-Mode only) to 7-Mode - you need to perform new installation of 7-Mode. Also disk lables in 8.3 are not recognized (or, better, accepted) by 8.2 which explains panic - it does not see any disk. So to install new 8.2 version you would need to downgrade to 8.2.x C-Mode. Follow standard documentation, if it is new system it should be easy. You do not care about preserving data anyway. This will downgrade disk labels. Follow https://kb.netapp.com/support/index?page=content&id=1014786 to reinstall 7-Mode. PS Sorry, had to edit reply as critical "not" was missing - you cannot downgrade (or upgrade) between C-Mode and 7-Mode.
... View more
@scottgelb wrote: TR 4100 covers this really well.. a really nice reference. See page 6. Page 7 is more interesting as it details conditions when LIF migration is really non-disruptive. It seems that SMB 2 or 3 alone does not gurantee it; there are situations when session may be lost. I wonder if Windows is using durable handles by default (and in which versions). I could not find any explanation, but then I am not really Windows guy.
... View more
Any chance those disks are already partitioned (probably, during installation)? You cannot use SSDs that have been partitioned for root-data partitioning in a storage pool
... View more
Scott beat me, but note that it may be confused by local users that won't be present on DR filer. So replicating configuration is more involved. You may look at vfiler DR which relocates complete filer with all configuration.
... View more
If you have no data, simply re initialize it (special boot menu, menu 4). It will create single aggregate with 3 disks and root volume on it; all other disks become spare.
... View more
You must reinstall each node to use ADP. On your model when you go to Special Boot menu and select 4, in Data ONTAP 8.3 it will automatically partition all disks assigned to the controller into root and data parts and create root aggreate from root partitions. It makes sense to do "set-defaults" in loader prompt before. Root partition size is computed automatically based on number of disks, so be sure to perform assignment as need in maintenance mode before starting installation.
... View more
Yes. In cDOT each node must have root volume on dedicated aggregate. 8.3 introduced Advanced Disk Partitioning, where small part of each disk is used for root aggregate and the rest - for data. This leaves you with almost full disk capacity for data. Actually, this should be default on new installation - I am surprised you did not get it.
... View more
I do not think there is any load balancing in root volume access; and even if it were, root volume should be used for junction points only, so benefit is marginal. For real disaster recovery you should probably look at SVM replication. It is always possible to replace root volume with another one and manually mount everything - it just takes time (and proper documentation). So LS mirrors saves it for you. Having root mirrored to another cluster does not help, because to restore it you need running SVM and it cannot run without root volume - catch 22.
... View more
LS mirror is recommended for disaster recovery. If root volume is lost, you can promote LS copy to root volume. This is not transparent and requires manual administrator intervention. Of course, as long as root volume is not available clients cannot access data.
... View more
I'm afraid I still cannot parse your question (assuming, it *is* a question, as it completely lacks any question marks); so guessing what you mean - when you connect to cluster management address you connect to the node where LIF is currently active. When LIF is migrated to another node (for any reasons) current connection is terminated and you need to reconnect. How many pings are lost is irrelevant here. Does it answer your question?
... View more
In 8.3 I would expect something like 1.22 (<stack>.<shelf>). In any case, this is of course not correct. Did you read documentation? Assuming your system is actually using node names for whatever reason, this would be node1:3b.22.* for all disks in shelf 22. Or you can simply run storage disk assign -all if all disks should be assigned to the same node. You can see shelf information using - surprise - "storage shelf show" command.
... View more
You must specify to which node they will be assigned. In 7-Mode default is the node where you run command, but in C-Mode cluster shell you can sit anywhere. You need to only run it once, and being on C-Mode you should do it from cluster shell if this is possible.
... View more
You need to assign disks using "storage disk assign". You can see them in cluster shell with "storage disk show -container-type unassigned". In principle you should be able to use "disk assign" in node shell as well.
... View more