This is part 6 of this 8 part series. Questions around managing VMFS snapshots have been cropping up a lot lately and I realized I didn’t have a lot of specific Pure Storage and VMware resignaturing information out there. Especially around scripting all of this and the various options to do this. So I put a long series out here about how to do all of this.
The series being:
- Mounting an unresolved VMFS
- Why not force mount?
- Why might a VMFS resignature operation fail?
- How to correlate a VMFS and a FlashArray volume
- How to snapshot a VMFS on the FlashArray
- How to mount a VMFS FlashArray snapshot
- Restoring a single VM from a FlashArray snapshot
Using vCenter and our Web Client plugin, recovering a snapshot is a pretty straight forward process. So the pre-requisite here is having our Web Client plugin installed and configured. Info on that here. If you want to know the manual steps, scroll down further and the whole process is described in detail that does not use the plugin–just our GUI and vCenter.
So, in this case, I have a few VMs on a datastore called “ProdVMFS”:
Something goes wrong on my VM called “AppServer” so I need to bring up a copy of the datastore it sits on.
Mounting a Snapshot with the FlashArray Web Client Plugin
When the datastore object is selected in the vCenter inventory, I can choose the FlashArray Snapshot tab (this is under “Related Objects” in vCenter versions prior to 6.5) and see the available snapshots.
There are a variety of options here, but what I want is to choose “Copy to New Datastore”. This will follow this procedure:
- Copy the snapshot to a new volume
- Connect the new volume to host group on the FlashArray that corresponds to the cluster chosen.
- Rescan the cluster
- Resignature the VMFS
- Rename the resignatured name to whatever was entered
Confirm then populate the wizard. All you really need to enter is a new name and then a cluster to mount it to.
Now let it finish. The snapshot is now recovered!
If you want to follow the manual process (whether to build a script etc.) or don’t use the plugin for some reason, here is the detailed process.
First identify the underlying FlashArray volume, you can do this with one of the methods described in this post here.
Once done click on the volume in the GUI and identify the snapshot you want. The choose the option “Copy Snapshot”.
Enter in a new volume name. This name will be assigned to the new volume that is created from the snapshot image. I am using my original volume name plus the suffix of “Copy”.
Next, click on the new volume and then connect it to the proper host group or host that you want to recover it to. If you are using it to restore a VM or entire datastore or a single virtual disk, attach it to the same host group as the source volume.
Then choose the host group(s) (or hosts).
Now back to vCenter and rescan your cluster.
Make sure you choose the default options to scan for new devices and VMFS volumes.
Lastly, in the same menu, choose “New Datastore”.
Choose VMFS and the next.
Find the proper device in the next screen, match the NAA to the FlashArray volume, you will also see the original VMFS name in the “Snapshot Volume” header. Don’t bother entering a new name, as the datastore will always just get the resignature name of (snap-<identifier><original VMFS name>.
The last part is to choose the resignature option. It is NOT the default selection, so make sure to choose “Assign a new signature”.
The process will complete and the datastore will be ready for use/recovery: