Cluster mode Netapp systemshell

Cluster mode runs on Bash shell.. which means we have the bash shell on that we have the next generation shell ngsh (NetApp calls it like that)

• Log in to system shell.
• Run sudo bash
• Then type ngsh
• you would launch the cluster shell.
• to confirm, do an exit.
• You would be routed back to system shell.

cluster600::*> systemshell
  (system node systemshell)

Data ONTAP/amd64 (cluster600-01) (pts/2)

login: diag
Password:
Last login: Wed Feb 10 13:51:44 from localhost


Warning:  The system shell provides access to low-level
diagnostic tools that can cause irreparable damage to
the system if not used properly.  Use this environment
only when directed to do so by support personnel.

cluster600-01%
cluster600-01%
cluster600-01% sudo bash
bash-3.2#
bash-3.2# now we are in the system shell
bash-3.2#
bash-3.2#
bash-3.2# ngsh
cluster600::> exit
Goodbye


bash-3.2# exit
exit
cluster600-01% exit
logout

cluster600::*>

Please leave your comments.. and if there is anything I can add, feel free to ask.

Cluster Mode NetApp Snapvault example

. create vserverA and vserverB
cl1::> vserver create vserverA -rootvolume roota -aggregate aggr1_n1 -ns-switch file -nm-switch file -rootvolume-security-style unix

cl1::> vserver create vserverB -rootvolume rootb -aggregate aggr1_n2 -ns-switch file -nm-switch file -rootvolume-security-style unix

for vserverA
2. create a source datavolume in vserverA
cl1::> vol create -vserver vserverA -volume datasource -aggregate aggr1_n1 -size 100m -state online

3. create a destination datavolume in vserverB with type DP
1::> vol create -vserver vserverB -volume datadest -aggregate aggr1_n2 -size 100m -type DP

Using the 5min schedule for snapshots on the source

Create new snapshot-policy for vserverA with the 5min schedule and a count of 2.
Also specify the snapmirror-label for the snapshots.
4. cl1::> volume snapshot policy create -vserver vserverA -policy 5minpol -enabled true -schedule1 5min -count1 2 -prefix1 5min -snapmirror-label1 vserverA-vault-5min

Connect snapshot-policy to the vserverA datasource volume.
5. cl1::> volume modify -vserver vserverA -volume datasource -snapshot-policy 5minpol

for vserverB.
Create snapmirror policy and rule
6. cl1::> snapmirror policy create -vserver vserverB -policy vserverA-vault
7. cl1::> snapmirror policy add-rule -vserver vserverB -policy vserverA-vault -snapmirror-label vserverA-vault-5min -keep 40

Setup a peer relationship
8. cl1::> vserver peer create -vserver vserverA -peer-vserver vserverB -applications snapmirror

Create the snapmirror relation
9. cl1::> snapmirror create -source-path vserverA:datasource -destination-path vserverB:datadest -type XDP -policy vserverA-vault -schedule 5min

Initialize.
10. cl1::> snapmirror initialize -destination-path vserverB:datadest

Monitor:
View the lag time.
cl1::> snapmirror show -destination-path vserverB:datadest -field lag

View the relationship
cl1::> snapmirror show

View the snapshots
cl1::> snapshot show -vserver vserverA -volume datasource -instance
cl1::> snapshot show -vserver vserverB -volume datadest


Please leave your comments.. that would be helpful, Thanks for reading.

C-dot NetApp Metrocluster switchback

Make sure to run these commands:

metrocluster heal -phase aggregates
metrocluster heal -phase root-aggregates
metrocluster switchback