Decommissioning a MetroCluster system when disk sanitization is required
Applies to
- ONTAP 9
- MetroCluster FC and MetroCluster IP
- Decommissioning a MetroCluster when disk sanitization is also required
Description
-
This procedure applies to both MetroCluster FC and MetroCluster IP.
-
Complete the steps in order. Unconfigure MetroCluster before you delete any aggregates or use boot menu options that clear disks.
-
Boot menu option 9a (unpartition all disks and remove their ownership) and the wipe/re-initialize steps don't sanitize data. They only remove partitions, metadata and ownership. You still need to sanitize the disks if data has to be wiped.
Prerequisites
-
Confirm all workloads have been migrated. From the destination clusters, delete any SnapMirror or SVM-DR relationships, and any cluster or vserver peers, that point to the old clusters.
-
Check whether the drives are self-encrypting (NSE/SED/FIPS) with
storage encryption disk show(cluster shell) ordisk encrypt show(Maintenance Mode). -
Confirm the customer's data-wiping requirements, such as the number of overwrite passes or whether they need proof of sanitization.
-
Collect console logs (SP/BMC) for all nodes during the activity.
