#Whole MetroCluster recover from configuration backup

1 messages · Page 1 of 1 (latest)

onyx elk
#

Hello,
Our Business Continuity Manager is asking us to provide the procedure to recover our whole 4 nodes MetroCluster from backup (including configuration, …)
We already have configured the configuration backup of both ha-pair to upload backups to an external ftps server
We also have SnapVault replications of data volumes to a SnapLock target.

The considered procedure could be :

  1. Recreate clusters from configuration backup (system configuration recovery cluster recreate) and rejoining the second node of each ha-pair to the cluster
    https://docs.netapp.com/us-en/ontap/system-admin/restore-cluster-config-from-existing-task.html
  2. Re-create all SnapMirror peer relationships
  3. Restore data from Vault (snapmirror restore)

My question is : what is exactly restored through step one ?
There is a mention that SVM informations is included in the configuration backup (https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Is_SVM_information_included_in_the_configuration_backup_file)
Do we need to recreate something else ? (what about aggregate, volumes, shares, exports, …)

Is there a NetApp procedure that describe the whole recover in case of a wiper and related backup best practices ?

Best Regards,
Didier

compact blaze
#

I would probably re-create the MCC from scratch and restore from backup... you have more than enough time to rebuild the config while the snapmirror (or restore) runs 😉

#

I mean in such a scenario (2 separate sites both destroyed) you will need to get new hardware anyway... with probably new disks, new aggr layout, new controller with different IO cards, etc.

#

I mean I realize you got asked this question probably by your boss or something, but what these people usually don't realize is that in such a situation, the MetroCluster is almost certainly the least of their problems

jolly surge
#

Internally we refer to Metrocluster's two failure scenarios as "backhoe" and "smoking crater". Backhoe is simple - sites are partitioned, tiebreaker/mediator decides one survives and STONITH's the other... smoking crater, you might be lucky and be able to get another identical system, but realistically you're probably building a new MCC and migrating data.

compact blaze
#

Doesn't "Smoking Crater" refer to only one site being destroyed, i.e. wegen you just do a switchover?

jolly surge
#

Yes, sorry, I misread the initial question..

#

So original question is - how do you setup a metrocluster from scratch? Follow the metrocluster configuration guide is the answer I guess