I am using an Iomega disk for virtual pc. There was an error (windows file corrupted) and i can’t lunch aplications on virtual pc. Does anyone knowing how can i get data from that disk?

ESX Snapshot Recovery

Snapshot Recovery on local side using snapshots on local filer which run every 6 hours by script integrating Netapp snapshots with quiesced VMware snapshots (without memory)

1. Identify Snapshot to be recovered. In most cases this will be “vmware_recent”
2. Identify a target Volume on Netapp to accommodate the new LUN that will be created based on the snapshot. If necessary, expand volume to accommodate the new LUN.
3. Command Line on filer
a. Lun clone create /vol/ESX7/ESX7/esx7clone.lun –b /vol/ESX7/ESX7/esx7.lun vmware_recent
b. LUNs – Manage –
i. Verify that LUN was successfully created and exists.
ii. Go to the new LUN and click on “No Maps”
iii. Add the ESX hosts to the initiator group by selecting “Add Group to Map”
iv. Add all ESX host(s) in the cluster to the initiator group.

NOTE: If you do not add all hosts to the initiator group, than when you register the VM, you will experience a failure to register because all hosts cannot see the same LUN.

4. From VirtualCenter Client locate the ESX Recovery host
a. From the “Configuration” – “Storage Adapters” - under“iSCSI Software Adapter”, right click “vmhba40” and select Rescan to recognize the new cloned LUN presented. SS
b. Find the problematic (failed) Virtual Machine and right click and select “Remove from Inventory” SS
c. Browse the datastore of the new Snapshot Clone LUN which should be labeled (snap-00000002-Store7) and find the configuration file (vmname.vmx). Right click and select “Add to Inventory” SS
NOTE: Do NOT delete from Disk as a precaution if additional information is needed from the failed Virtual Machine
d. Select the Virtual Machine and from “Snapshot Manager” select “Delete All” to revert the the “Quiesce” Snapshot.
e. Power on the Virtual Machine
f. Answer the uuid question by selecting “Keep” Note: This step may be eliminated on the local side. Will definitely be eliminated on the DR side by adding a parameter to the configuration file. See Ionic Capital documentation.
g. Verify network and virtual machine functionality.
5. When all functionality is verified and during scheduled maintenance window) you can do a “cold migration” of the recovered VM back to the original LUN which in this case is “Store7” and power on the virtual machine.

There are conflicting stories about NetApp’s work on “SnapManager for VMware”. Some people say that there is one under development, but others say that there isn’t. I honestly can’t tell you one way or another, but I agree that it would be extremely helpful and would definitely strengthen their value proposition as a storage vendor for VMware deployments.

Do you have any information if NetApp is working on or planning to release a ‘SnapManager for VMware’. That would be fantastic if they did. It would greatly simplifiy things and take the scripting out of the picture to ensure consistency.

Thanks!

I would assume that you have already modified the ESX hosts to allow the cloned LUNs to be seen (enabled resignaturing). When you rescan, be sure to rescan for new storage devices as well as new VMFS datastores. If that doesn’t work, post back or e-mail me here (my e-mail is scott dot lowe at scottlowe dot org) or at work (you probably already have that address).

Good luck!

Certainly, ensuring the integrity/consistency/validity of a snapshot is a critical task, and this technique isn’t the best to use in all instances. But as you point out, it comes in mighty handy at times!