This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| vmware:troubleshooting [2021/01/07 11:04] – lunetikk | vmware:troubleshooting [2022/09/03 16:27] (current) – lunetikk | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== VMware Troubleshooting ===== | + | ====== VMware Troubleshooting |
| ==== Cant apply or remediate a host profile ==== | ==== Cant apply or remediate a host profile ==== | ||
| Line 231: | Line 231: | ||
| To fix the logrotate/ | To fix the logrotate/ | ||
| + | ==== 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 " | ||
| + | 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 / | ||
| + | cp -a myvm-flat.vmdk / | ||
| + | </ | ||
| + | |||
| + | 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 / | ||
| + | </ | ||
| + | |||
| + | \\ | ||