VMware & HP 3PAR – RDM disks and HP 3PAR snapshot
I will show you how you can take a cold snapshot via the HP 3PAR of a VMware RDM disk in physical compatibility mode. You can also do the snapshot while the guest host is running.
Check the guest hard disk and make a note of the vml file as seen in the screenshot as this will be needed to make sure all your RDM disks pointing to the correct vml file alter.
Here you will see that there are some files and folders in the RDM disk before the snapshot. Take a look at the date and time stamp of the files/folder.
Just check LUN is showing up on the ESX hosts, pay attention to the LUN ID and the naa (Network Addressing Authority) number to make sure you get the same one back from the SAN when you roll back the snapshot.
Now shutdown the guest machine.
Now go to you InForm Manager console and take the snapshot. Give the destination volume a name, leave the ID ticked and then choose your snapshot option RO – Read Only or RW – Read/Write.
I took a RO snapshot as shown below.
Now you can power up your guest machine and make any modification to the RDM disk, I decided to delete all the files and folder.
If you try to go into the InForm manager console and try to “promote” the RO snapshot you will see that the “promote” is grayed out. This is because the base volume is still exported to the ESXi hosts.
So you don’t cause any issue with disk activity; shutdown the guest machine.
As an engineer I will do the following to avoid any issues with guest disk, ESX pointers, 3PAR ID allocation.
I would remove the disk from guest machine but not delete them, then I will detach the LUN’s from the hosts and then finally unexport the LUN’s in 3PAR.
To tell you the truth I took the risk and unexported the LUN in 3PAR.
Now you will see that the RO snapshot is “promote” is not grayed out. Now “promote” the snapshot back into the base volume.
You will notice that the ESX hosts have lost connection to the LUNS, don’t worry about that.
Once the snapshot has been committed back to the base volume it’s time to “export” the LUN back again to the ESX hosts. When you right click on the volume and go promote the default settings will be selected for you.
Click next and choose “host set” if you have that set up, select the host set from the list and then don’t forget to untick the “auto” and put in the correct LUN ID, otherwise 3PAR will allocate any number which in my case it would of been “0”. Because 3PAR is not intelligent enough to take the LUN ID automatically. Click “finish” at the next dialog window.
You will have to wait until all the ESX hosts see the LUN again under Storage Adapters settings.
For sanity I will allow all the ESX hosts to see the LUN again before you attempt to power up the guest machine.
The roll back of the snapshot has worked as you can see the files and folders are back to their original state.
Posted on January 19, 2013, in 3PAR, ESXi 4x & 5x, HP, VMware and tagged 3par, compatibility mode, ESXi, HP 3PAR, HP 3PAR ESXI LUN detached, HP 3PAR R/W error, snapshot, VMware. Bookmark the permalink. Leave a comment.