hey VM-Guys,
yesterday night, i get an error with my one vm in my infrastructure.
The vcb backup was made trouble..
The VM was creating a snapshot and than going down (hard power off). The Vm consists of one vmdk and one rdm!
If i tried to start the vm manually i get the following error:
"Cannot open the disk '/vmfs/volumes/..../MyVM/MyVM-01-000045.vmdk' or one of the snapshot disks it depends on.Reason: Too many levels of redo logs."
Try to apply Snapshot´s --> but in VC does not show any snapshot!
On the cli tried it with vcbSnapshot .... but this shows no snapshots, too.
The workaround to create a new snapshot and remove all, does not!
after some "googeling" i found a solution to get the machine on again..
1.) export MyVM 2.) cd /vmfs/volumes/.../ mv MyVM MyVM.old mkdir MyVM cd MyVM 3.) # vcbExport -M 1 -F 1 -d ${VMNAME}_1.vmdk -s ../${VMNAME}.old/${VMNAME}_1.vmdk 4.) connect the RDM to the MyVM 5.) start MyVM --> machine is running with RAW Device
Now my problem:
i miss files from one day! i got all *delta* file and die copy of the original vm folder.
is ther any possibility to restore the missing files, from the delta files?
I had not very clear with your issue. Let me explain how I can solve this. If you use the RDM in your storage, even you VM is corrupted, you will still able to get the content in the storage by assigning the Physical LUN to another VM or reattach should work. you can even do a zoning for that particular LUN to another physical server, the content in the storage will still around. If file system corrupted, that will be operating system related, and you should recover by Operating System recovery method.
Post a listing of all the files you have (including file sizes)
the raw device on san was not touched
That was a wise decision!
Zip up all the descriptor files (the short VMDK files), the log files, the VMSD file and the VMX and post it.
got a private message!
stony,
What is the backup software you're using for what seems like vm image level backups? I just had the exact same issue with the snapshot creation and the issue was 1) The snap resulted in depleting my LUN space during the process and 2) I had to repoint the .vmx file to reflect the correct path to the .vmdk files. I can give you more info and specifics if you're still having the issue.