Clustermode mroot destroyed

HA-PAIR.

Logged into the systemshell and completely emptied mroot on both nodes.
rebooted.

During boot, an mroot.tgz is extracted from /tmp and the new mroot is
regenerated.

You will have to set a new root password (boot menu) and diag password (security login password).

Please leave your comments for me to improve

clustermode recovery mroot (only use if you know what you are doing)

the backups are in /mroot/etc/backups/config

the rdb environment is in /mroot/etc/cluster_config/
I tarred the db’s in /mroot/etc/cluster_config/tarred
on the surviving node, and copied that to a third location.
The db’s were not restored by the backup and the directories
remain empty.
I copy the tar file from the third location to the cluster_config
directory and untarred. Reboot and node functions properly again.

1. on surviving node:
cd /mroot/etc/cluster_config/rdb
tar cf tarred .
scp tarred root@192.168.1.159:/tmp/

2. on broken node:
boot system and login…
kp-01::system configuration*> backup showNode Backup Tarball Time Size
——— —————————————– —————— —–
kp-01 kp-01.daily.2015-04-06.00_10_00.7z 04/06 00:10:00 4.66MB
kp-01 kp-01.daily.2015-04-07.00_10_01.7z 04/07 00:10:01 4.18MB
kp-01 kp-02.daily.2015-04-06.00_10_00.7z 04/06 00:10:00 3.27MB
kp-01 kp-02.daily.2015-04-07.00_10_01.7z 04/07 00:10:01 3.21MB
kp-01 kp.8hour.2015-04-06.18_15_00.7z 04/06 18:15:00 7.35MB
kp-01 kp.8hour.2015-04-07.02_15_04.7z 04/07 02:15:04 7.68MB
kp-01 kp.8hour.2015-04-07.10_15_00.7z 04/07 10:15:00 7.97MB
kp-01 kp.daily.2015-04-05.00_10_00.7z 04/05 00:10:00 7.21MB
kp-01 kp.daily.2015-04-06.00_10_00.7z 04/06 00:10:00 8.11MB
kp-01 kp.daily.2015-04-07.00_10_01.7z 04/07 00:10:01 7.56MB
kp-01 kp.weekly.2015-03-11.10_08_12.7z 03/11 10:08:12 3.26MB
kp-01 kp.weekly.2015-03-17.00_15_00.7z 03/17 00:15:00 6.06MB
kp-01 kp.weekly.2015-04-07.00_15_06.7z 04/07 00:15:06 7.57MB

kp-01::system*> configuration recovery node restore -backup kp.8hour.2013-04-07.02_15_04.7z

3. on broken node
cd /mroot/etc/cluster_config/rdb
scp root@192.168.1.159:/tmp/tarred .
tar xf tarred
sudo reboot

Cluster mode Snapmirror

Source Volume and Destination Volume should have the same Language!

Source Volume is RW type. Destination Volume is DP type.

1. create a schedule (to be used for the updates of the vault relationship)
job schedule cron create -name midday -hour 11 -minute 0
2. create a policy for source vserver to keep snapshots of the volume
snapshot policy create -vserver vs1 -policy vault -enabled true -schedule1 daily -count1 6 -prefix1 daily -snapmirror-label1 daily
3. create a policy for destination vserver
snapmirror policy create -vserver vs2 -policy vs2-vault-policy

4. add a rule to the destination policy to specify the retention
snapmirror policy add-rule -vserver vs2 -policy vs2-vault-policy -snapmirror-label daily -keep 20

5. create peer relationship
vserver peer create -vserver vs1 -peer-vserver vs2 -applications snapmirror

6. create a snapmirror relation of type XDP
snapmirror create -source-path vs1:vol1 -destination-path vs2:vol12 -type XDP -policy vs2-vault-policy -schedule midday

7. initialize
snapmirror initialize -destination-path vs2:vol12

8. run show
snapmirror show

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