Differences

This shows you the differences between two versions of the page.

--- vmware:troubleshooting [2021/01/07 11:03] – lunetikk
+++ vmware:troubleshooting [2021/09/16 17:17] – lunetikk
@@ Line 121: / Line 121: @@
 __Fix:__ \\
-Connect to your ESX host via ssh and restart the management agents
+Connect to your ESX host via SSH and restart the management agents
 <code>
 /etc/init.d/hostd restart
@@ Line 129: / Line 129: @@
 You should be able to create or remove the snapshot afterwards
-[[https://kb.vmware.com/s/article/1027707|https://kb.vmware.com/s/article/1027707]]
+[[https://kb.vmware.com/s/article/1027707|VMware KB 1027707 - Invalid state]]\\
+[[https://kb.vmware.com/s/article/1003490|VMware KB 1003490 - Restart management agents]]\\
+[[https://kb.vmware.com/s/article/2004746|VMware KB 2004746 - Activate SSH]]\\
 ==== No coredump target has been configured ====
@@ Line 229: / Line 231: @@
 To fix the logrotate/cron, check [[https://kb.vmware.com/s/article/2149278|VMware KB 2149278]]
+==== Restore from different datastore ====
+A VM is broken and needs to be restored. To do so you need to copy the VM from the backup datastore to your productive one \\
+__Reason:__ \\
+You dont want to run VMs from your backup datastore \\
+__Fix:__ \\
+Connect to your esx host via ssh and copy the files with "cp" or "vmkfstools"\\
+Make sure you either rename your old .vmdk + flatfile to .old or your restore to something different (rename flat in .vmdk)
+<code bash>
+cp -a myvm.vmdk /vmfs/volumes/prod_datastore/myvm/myvm.vmdk
+cp -a myvm-flat.vmdk /vmfs/volumes/prod_datastore/myvm/myvm-flat.vmdk
+</code>
+With vmkfstools you dont need to edit the flat name inside .vmdk, the tool does this for you if you choose another name
+<code bash>
+vmkfstools -i myvm.vmdk /vmfs/volumes/prod_datastore/myvm/myvm.vmdk
+</code>
+\\

Lunetikk's IT Wiki

User Tools

Site Tools

Differences

Page Tools