In this blog post I am going to show you how to make a read-writeable snapshot-clone of an NFS export on an Everpure Flash Array. This approach would allow you to make an almost instant “snapshot” clone of, for example, a large Oracle database that uses NFS on an Everpure Flash Array.
In my previous blog post Moving a Purity File System into a Pod, I observed that:
However, unlike block volume snapshots which may be instantly copied to new volumes providing for a nearly instant method to clone large databases, NFS snapshots work somewhat differently.
I then showed how you can move NFS exported file systems into a Pod. In this blog post we will clone that pod and all of the NFS exported file systems contained therein. Note that this process and these screen shots were taken on Purity 6.10.6. Releases of Purity that are older or newer may exhibit different behaviour.
The pod cloning process is extremely easy. From the Purity interface select the Pods tab and then use the dialog box to search for the pod that holds your NFS exported file systems.
Click on the required pod, and then use the 3-dot button on the left of the panel, and select Clone…. Provide a unique and descriptive name for the cloned pod, and then select Clone

The cloned pod will now exist, but it will not yet have any policies or exported directories. Use the Purity interface to locate the cloned pod, and then click the + symbol in the Policies panel to create a policy for our cloned pod.

NOTE: We could also add this cloned pod to an existing policy by editing that policy and adding the cloned file systems to it. In this example however, we will create a new and distinct policy, allowing us to change the export rules for our cloned database.
Once the new policy has been created, we can click on it to add the cloned file systems.

When we cloned the pod, Purity also cloned the underlying file systems and directories. These are thin-clones, the only capacity they require are any deltas that occur between the original source pod and the cloned one.
In the Policy attribute screen, click the + symbol on the right of the Members panel. When you click the — Select a Directory — button, Purity will list the available directories to add to the new policy. Use the filter option to find the new directory or directories that were created when the pod was cloned. They will be prefixed with the name of the new pod you selected earlier.

When you select a directory to add to the policy, Purity will prompt you for a new export name. This is the name NFS clients will mount. When the directories have been added it should look something like this:

We still need to recreate the NFS export rules. Click on the + symbol on the right hand side of the Rules panel and then specify the NFS export rules for the cloned pod. In this example we have set the client to “*” allowing any NFS client to mount the exported file system. This is a lab system and our database contains no real data. In an real environment the Client should be limited to only those servers authorized to mount the exported NFS clone.

Now our cloned pod and the directories held therein have been exported as new NFS exports. You should now be able to mount these new exports from your Linux client.
