To protect the Storage Virtual Machine (SVM) namespace root volume, you can create a load-sharing mirror volume on every node in the cluster, including the node in which the root volume is located. Then you create a mirror relationship to each load-sharing mirror volume and initialize the set of load-sharing mirror volumes. As you add new nodes to the cluster, you may choose to add a new load-sharing mirror to a set of existing load-sharing mirrors.
New-NcVol
PS>New-NcVol -Name root_vs01_m3 -Aggregate sas_aggr1 -JunctionPath $null -Type dp -Size 1g -VserverContext vs01
Name State TotalSize Used Available Dedupe Aggregate Vserver
---- ----- --------- ---- --------- ------ --------- -------
root_vs01_m3 online 1.0 GB 0% 1023.9 MB False sas_aggr1 vs01
Create the destination load-sharing mirror volume by using the New-NcVol cmdlet with the -type parameter set to DP (data-protection volume). The destination volume that you create must be the same size or greater than the SVM root volume.
New-NcSnapmirror
PS>New-NcSnapmirror //vs01/root_vs01_m3 //vs01/root_vs01 -Type ls
SourceLocation DestinationLocation Status MirrorState
-------------- ------------------- ------ -----------
ntap-clus01://vs01/root_vs01 ntap-clus01://vs01/root_vs01_m3 idle uninitialized
Use the New-NcSnapmirror cmdlet with the -type LS parameter to create a load-sharing mirror relationship between the source volume and a destination volume.
Note: The -Schedule parameter does not need to be used, because Data ONTAP automatically applies the same schedule to the set of all load-sharing mirrors that share the same source volume.
Get-NcSnapmirror
PS>Get-NcSnapmirror | Select sourcelocation, destinationlocation, relationshipstatus, relationshipType, ishealthy, schedule | ft -a
SourceLocation DestinationLocation RelationshipStatus RelationshipType IsHealthy Schedule
-------------- ------------------- ------------------ ---------------- --------- --------
ntap-clus01://vs01/root_vs01 ntap-clus01://vs01/root_vs01_m1 idle load_sharing True 5min
ntap-clus01://vs01/root_vs01 ntap-clus01://vs01/root_vs01_m2 idle load_sharing True 5min
ntap-clus01://vs01/root_vs01 ntap-clus01://vs01/root_vs01_m3 load_sharing 5min
Use the Get-NcSnapmirror cmdlet with the parameters listed to confirm the relationship has been created, as well as the health of the relationship.
Invoke-NcSnapmirrorInitialize
PS> Invoke-NcSnapmirrorInitialize -DestinationVolume root_vs01_m3 -DestinationVserver vs01 | Get-NcJob
JobId JobName JobPriority JobState JobVserver JobCompletion
----- ------- ----------- -------- ---------- -------------
70 SnapMirror initialize exclusive queued vs01
PS> Get-NcJob 70
JobId JobName JobPriority JobState JobVserver JobCompletion
----- ------- ----------- -------- ---------- -------------
70 SnapMirror initialize exclusive success vs01 SnapMirror: done
Use the Invoke-NcSnapmirrorInitialize cmdlet specifying the DestinationVolume and DestinationVserver to perform the initial update of a SnapMirror relationship.
Note: Do not use the Invoke-NcSnapmirrorLsInitialize cmdlet. The Invoke-NcSnapmirrorLsInitialize cmdlet is for initializing volumes for an entire set of load-sharing mirrors, not for initializing an individual volume.
Invoke-NcSnapmirrorLsUpdate
PS> Invoke-NcSnapmirrorLsUpdate ntap-clus01://vs01/root_vs01 | Get-NcJob
JobId JobName JobPriority JobState JobVserver JobCompletion
----- ------- ----------- -------- ---------- -------------
87 SnapMirror Loadshare update exclusive queued vs01
PS> Get-NcJob 87
JobId JobName JobPriority JobState JobVserver JobCompletion
----- ------- ----------- -------- ---------- -------------
87 SnapMirror Loadshare update exclusive success vs01 SnapMirror: done
Upon job completion, update the LS set by using the Invoke-NcSnapmirrorLsUpdate cmdlet specifying the source endpoint to update destination volumes of the set of load-sharing mirrors. The cmdlet makes destination volumes in the group of load-sharing mirrors up-to-date mirrors of the source volume. Separate SnapMirror transfers are performed from the source volume to each of the up-to-date destination volumes in the set of load-sharing mirrors.
Use the Get-NcSnapmirror cmdlet once more to confirm the health of the relationship.
PS> Get-NcSnapmirror | Select sourcelocation, destinationlocation, relationshipstatus, relationshipType, ishealthy, schedule | ft -a
SourceLocation DestinationLocation RelationshipStatus RelationshipType IsHealthy Schedule
-------------- ------------------- ------------------ ---------------- --------- --------
ntap-clus01://vs01/root_vs01 ntap-clus01://vs01/root_vs01_m1 idle load_sharing True 5min
ntap-clus01://vs01/root_vs01 ntap-clus01://vs01/root_vs01_m2 idle load_sharing True 5min
ntap-clus01://vs01/root_vs01 ntap-clus01://vs01/root_vs01_m3 idle load_sharing True 5min
Further reading:
