1. This is normal case of mixing drives of different sizes in a single aggregate. You cannot add them to existing raid group that consists of disks of larger size (same non-partitioned disks are of lager usable size). You can add them as separate raid group. 2. Same as 1 - best practive is to not use different disk kinds in single aggregate. YOu can of course create separate aggregate. 3. Spare will be auto-partitioned as needed. See also https://kb.netapp.com/support/s/article/why-is-a-newly-added-disk-not-auto-partitioned-on-hdd-and-aff-adp-systems?language=en_US
... View more
7-Mode supports takeover on network link failure; this is called "negotiated failover" and is enabled per-interface. Downside is that it monitors only link failures and cannot handle situations where link is physically present but packets are not delivered. C-Mode lets host MPIO stack handle it.
... View more
Break mirrors, setup in reverse direction, resync from C to B and then from B to A. As long as there is commmon snapshot resync will transfer only changes relative to it.
... View more
@illllm wrote: If your production environment ends up with issues, this will be the first issue you will need to fix with NetApp support. Create a new Aggr. Come on, really. Do you have any evidence to prove this statement?
... View more
No, NetApp does not support automatic tiering. FlashPool is cache - SSD disks do not increase available space. Sort of manual tiering is possible using volume/LUN move, but no better granularity.
... View more
If you use CLI often, I would consider using PowerShell, assuming you are on Windows. It is much more convinient than automating CLI directly.
... View more
Did you even try to search? https://kb.netapp.com/support/s/article/how-to-convert-a-clustered-data-ontap-8-x-node-to-a-7-mode-node?language=en_US
... View more
Procedure to manually collect logs is described in knowledge base: https://kb.netapp.com/support/s/article/how-to-manually-collect-logs-and-copy-files-from-a-clustered-data-ontap-storage-system?language=en_US Knowledge base also has articles explaining how to move root volume. Just do a search.
... View more
@Manikandan291 wrote: But customer need to take data from this storage.How to take data from old storage. I already told you - change FAS8020 setup to 7-Mode, connect shelves, backup data. @Manikandan291 wrote: Can you confirm without existing controller we will do the head swap I cannot parse this question, sorry. @Manikandan291 wrote: As per best practices for initializing cDOT we need the minimum of 3 disks from the shelf. but we not aware of how to do choose particular three disk during fresh initialization. They are allocated automatically during initialization.
... View more
It is not possible to do head swap from 7-Mode to C-Mode. It is possible to connect existing shelves to FAS8020 in 7-Mode! and get access to data and configuration. To preserve data you will need to either migrate it to another FAS in C-Mode or do backup to external media, reinitialize shelves in C-Mode and restore data. It may be possible to use one controller in dual head FAS8020 as 7-Mode and second - in C-Mode to perform migration, but I am sure it is not officially supported and requires quite a bit of experience to complete. Migration from 7-Mode to C-Mode is complex task that far exceeds forum format. I strongly suggest you contact your partner or NetApp and ask for professional service to plan and implement it.
... View more
You cannot upgrade 7-Mode to C-Mode. You need to wipe clean and reinstall in C-Mode. Existing data is lost. If you want to preseve it, you need to migrate data to another C-Mode filer or backup and restore.
... View more
There are no reserve ports. There are recommended ports for cluster interconnect that are offered by default during setup, but even these ports can be changed. And e0M port has limited functionality and usually is used as node/cluster management. So assuming you completed initial cluster setup any other port usage is completely up to you.
... View more
1. 8020 only supports single chassis HA pair (with exception of MetroCluster configuration where you use extra FC-VI adapter), so it communicates over backplane. If you have MetroCluster I strongly suggest to not do it on your own if you are new to NetApp. 2, 3. Cluster expects and sets up by default 1 common cluster management IP and one management IP for each node. You can have as many ports connected to management network as you deem necessary and IP will failover between them as needed. Whether management and data networks are separate is entirely up to you and your requirements.
... View more
@yaoguang wrote: in general procedure for 7mode ... 5. go to maintennance mode to assign the disks to new node 6. boot it up normally ... 5.5 - restore /var from old disks, otherwise some configuration is lost or incorrect (takes some time to notice). But OP tagged question with both C-Mode and 7-Mode which makes it rather hard to answer ...
... View more
Not that I'm aware of. It is possible to perform SnapMirror to tape (connection can be FC or SAS) or store SnapMirror stream to a file on the filer. The latter may be alternative if you have enough space; file can be then copied off filer. To use it for restore you would need to SnapMirror from it to a volume first, which again requires additional space. Not sure how much single tape drive costs, but that can be alternative.
... View more
You do not need HA Pair to establish cluster peering. The only requirement is full mesh - each node of one cluster must be able to speak with each node of other cluster. Two ports aer recommended from redundancy considreations, but this is not required.
... View more
Why do you need access to root volume? What do you want to do? You find detailed step by step description of update procedure in the same place where you download firmware.
... View more