I have not posted blogs for a while. In last a few weeks, I was heads down configuring NetApp FlexPod with XenDesktop. I would like to share some best practices on NetApp cluster OnTAP storage configuration in my next a few blogs.
One best practice with NetApp Cluster OnTAP is using load sharing SnapMirror for virtual storage server’s root volumes.
In Cluster-Mode, NAS clients can use a single NFS mount point or CIFS share to access a namespace of potentially thousands of volumes. The root volume for a Vserver namespace contains the paths where the data volumes are junctioned into the namespace. NAS clients cannot access data if the root volume is unavailable.
Every Vserver has a root volume that serves as the entry point to the namespace provided by that Vserver. The root volume of a Vserver is a FlexVol volume that resides at the top level of the namespace hierarchy and contains the directories that are used as mount points, the paths where data volumes are junctioned into the namespace.
In the unlikely event that the root volume of a Vserver namespace is unavailable, NAS clients cannot access the namespace hierarchy and therefore cannot access data in the namespace. For this reason, it is a NetApp best practice to create a load-sharing mirror for the root volume on each node of the cluster so that the namespace directory information remains available in the event of a node outage or failover.
The procedure is also stated in NetApp FlexPod Animal CVD.