2,187
edits
Difference between revisions of "Installation (ESX)"
Jump to navigation
Jump to search
→Storage: Added disk and VM recovery
(→HBA and SAN Operations: Added "QLogic") |
(→Storage: Added disk and VM recovery) |
||
| Line 484: | Line 484: | ||
Latency occurs when the hypervisor or physical storage cannot keep pace with the demand for IO | Latency occurs when the hypervisor or physical storage cannot keep pace with the demand for IO | ||
=== Storage Monitor Log Entries === | === Storage Monitor Log Entries === | ||
How to decode the following type of entries... | How to decode the following type of entries... | ||
Sep 3 15:15:14 tfukesxent1 vmkernel: 85:01:23:01.532 cpu4:2264)StorageMonitor: 196: vmhba1:2:0:0 status = 2/0 0x6 0x2a 0x1 | Sep 3 15:15:14 tfukesxent1 vmkernel: 85:01:23:01.532 cpu4:2264)StorageMonitor: 196: vmhba1:2:0:0 status = 2/0 0x6 0x2a 0x1 | ||
| Line 578: | Line 576: | ||
|} | |} | ||
=== Recovering VM's from failed storage === | |||
Procedure generated from an occasion where the ESX software was installed on top of the shared SAN VMFS storage, where the VM files still existed so the VM’s continued to run, but as the file system index no longer existed, the vmdk’s etc were orphaned and would be lost if the VM’s were to be restarted. Though it could be adapted to suit any situation where the ESX datastore is corrupted, cannot power on VM’s, and rebooting a VM would lose it. However, its well worth calling VMware support before carrying this out, they may be able to provide an easier solution. | |||
# On each VM | |||
## Shut-down running applications | |||
## Install VMware Converter (Typical install, all default options) | |||
## Hot migrate local VM to a new VM on new storage | |||
### As VMware converter starts, select '''Continue in Starter Mode''' | |||
### Select '''Import Machine''' from the bottom of the initial screen | |||
### Select source as '''Physical Machine''', then on next screen '''This local machine''' | |||
### Select default options for source disk | |||
### Select '''VMware ESX server...''' as your destination | |||
### Enter ESX hostname, and root user/pass | |||
### Enter new VM name, e.g. ''myserver''-recov (not the same as the existing, it will let you do it, but the VC isn’t happy later on) | |||
### Select host | |||
### Select datastore | |||
### Select network and uncheck '''Connect at power on...''' | |||
### Don’t select power on after creation, and let the migration run | |||
## Reconfig the new VM, edit its settings as follows | |||
##* Floppy Drive 1 --> Client Device | |||
##* CD/DVD Drive 1 --> Client Device | |||
##* Parallel Port 1 --> Remove | |||
##* Serial Port 1 --> Remove | |||
##* Serial Port 2 --> Remove | |||
##* USB Controller --> Remove | |||
## Power up the new VM and check it over | |||
## Power off the old VM (you will lose it forever, be very sure the new VM is good) | |||
## Connect the network of the new VM | |||
## Delete the old VM | |||
# Delete the knackered SAN datastore and refresh on all other ESX’s that share it (deletes the name but doesn’t free up any space) | |||
# Create a new SAN datastore (this formats the old space) | |||
# Refresh on all other ESX’s that share the datastore | |||
# Shutdown all the new VM’s | |||
# Clone them to the new SAN datastore using the original name (e.g. ''myserver'') | |||
# Power up new new VM’s on SAN datastore, confirm OK, then delete ''myserver''-recov servers | |||
=== Recover lost SAN VMFS partition === | |||
EG After a powerdown, ESX's can see the SAN storage, but the VMFS cannot be found in the Storage part of the ESX config, even after Refresh. To fix, the VMFS needs to be resignatured... | |||
'''Do not attempt to ''Add Storage'' to recover the VMFS, this will format the partition''' | |||
# On one of the ESX's, in Advanced Settings, change LVM.EnableResignature to 1 | |||
# '''Refresh''' Storage, the VMFS should be found with a new name, something like snap-000000002-''OriginalName''. | |||
# '''Remove from Inventory''' all VM's from the old storage, the old storage should disappear from the list of datastores | |||
# Rename the found storage to the original name | |||
# '''Refresh''' Storage on all other ESX's, they should see the VMFS again | |||
# Revert LVM.EnableResignature on the appropriate ESX | |||
# Via the ESX, browse the datastore and re-add the VM's to the inventory (right-click over the .vmx file) | |||
#* For a Virtual Machine Question about what to do about a UUID, select Keep | |||
[[Category:VMware]] | [[Category:VMware]] | ||