SVM-DR MDV (Meta Data Volume) SVM-DR updates are failing with error: Metadata volume is not available on cluster "source". Run "snapmirror config-replication status show" for more details.” Source::*>...SVM-DR MDV (Meta Data Volume) SVM-DR updates are failing with error: Metadata volume is not available on cluster "source". Run "snapmirror config-replication status show" for more details.” Source::*> snapmirror config-replication status show Storage Status: warning Storage In Use: Unavailable Storage Remarks: Unable to free resources Source::*> debug cps storage-area-group show Abandoned Volumes: MDV_CRS_2104458f258d11e454cd123478563456_A Standby Recreate Retry Count: 0
MDV_CRS volumes should not be deleted for any reason MDV_CRS volumes are holding metadata used in SVM-DR and MetroCluster It is possible to move the MDV_CRS volumes to other data aggregates using the ...MDV_CRS volumes should not be deleted for any reason MDV_CRS volumes are holding metadata used in SVM-DR and MetroCluster It is possible to move the MDV_CRS volumes to other data aggregates using the volume move command under advanced privilege level The best practice is that each MDV_CRS volume should reside on a different aggregate Theoretically, move MDV_CRS volume has no effect. How are MDV volumes supposed to be located over aggregates?
Volume move of the MDV_CRS volume from an SnapLock aggregate fails: Warning: You are about to modify the system volume "MDV_CRS_xxx". This might cause severe performance or stability problems. Error: ...Volume move of the MDV_CRS volume from an SnapLock aggregate fails: Warning: You are about to modify the system volume "MDV_CRS_xxx". This might cause severe performance or stability problems. Error: command failed: Unable to move volume "MDV_CRS_xxx" in Vserver "cluster". Audit log volume must be configured for the Vserver Customer does not want to provision a SnapLock audit volume for the cluster admin vserver
