ONTAP Discussions
ONTAP Discussions
Can anyone tell me the current instructions for NetApp Release 9.6P2
for pre-mounting the destination NAS volumes
Here are the older version instructions but the whole section for namespace is missing in 9.6p2
If a SnapMirror source volume becomes unavailable and you want to access the data from the SnapMirror destination volume, you must break the SnapMirror relationship. Access to the destination volume is changed from data protection (DP) to read/write (RW).
You can use the destination volume to serve data while you repair or replace the source, until you can reestablish the original SnapMirror relationship configuration.
SnapMirror relationships are listed and managed from the Vserver that contains the destination volume.
The best practice is to pre-mount the destination NAS volumes into the destination Vserver namespace as part of your disaster recovery configuration. If this was not done, you need to mount the volumes after breaking the SnapMirror relationship, to ensure that the volumes are accessible on the destination. You mount them into the namespace using the same junction path that the source volume was mounted to in the source Vserver. For details, see the task for mounting FlexVol volumes in the System Manager online Help.
https://library.netapp.com/ecmdocs/ECMP1287556/html/GUID-8A3F828F-CD3D-48E8-A171-393581FEB2ED.html
Solved! See The Solution
Storage -> Junction Paths
Select vserver from the 'SVM drop box.'
Click: Mount link.
A new window will appear;
Select the destination snapmirror volume from drop down.
Edit the Junction Name (if needed)
Change the Junction Path (if needed)
Click: Mount
Every SVM has a unique namespace. The SVM root volume is the entry point to the namespace hierarchy.
I don't have the GUI instructions as I spend very little time using it.
If you are willing to drop to the CLI you can 'pre' mount the snapmirror'ed volumes after they finish their initialization step.
::> volume mount -vserver [vserver_name] -volume [volume_name] -junction-path [juntion_path_name]
Additionally you should make sure the export policy for the snapmirror'ed volume(s) is defined on the destination cluster for the proper subnets.
GUI instructions preferred...
the mirrors are already setup... i created a nic for nfs but not sure how to get the namespace when that's no longer an option.
Storage -> Junction Paths
Select vserver from the 'SVM drop box.'
Click: Mount link.
A new window will appear;
Select the destination snapmirror volume from drop down.
Edit the Junction Name (if needed)
Change the Junction Path (if needed)
Click: Mount
Every SVM has a unique namespace. The SVM root volume is the entry point to the namespace hierarchy.
1.) network interfaces -- added ip associated with nfs
2.) turned on NFS for the SVM
3.) added export policy to SVM for the IP address
4.) added junction path to a specific volume
on attempting to add that new ip as a datastore -- fails.
what am i missing?
in junction paths the security style is set to unix... how do i set that to ntfs?
Got it... the trick was under SVM / Export Policies the client ip address was a subnet mask and not the ip address.
But without the junction path it wouldn't have worked..
thank you