In the example disks to move are identified by the numbers 1, 4, 5 > Log, TempDB and Data. Since SQL Server on VMware best practices suggest to create dedicated LUNs for Data, Transaction Log and TempDB creating VMDK files with Thick Provision Eager Zeroed format, the process needs to move some virtual disks to different datastores.īefore moving the disks, look at the current SQL Server configuration through Server Manager > Disks (Windows 2012 in this example) because the disk number is not the same as assigned by VMware. To improve its performance, moving the VMDk files in dedicated LUNs it's a possible configuration to consider.
So even though restoring a VM from a -flat.vmdk file is pretty easy it isn’t my recommended method, you’re far better protected with good, reliable backups, then on hoping that the -flat.vmdk file is still laying around somewhere.With VMware vSphere 5.5 it’s possible to move VMDK files to different datastores leaving the VM powered on with no service interruption using the Storage vMotion feature.Ī scenario where disks location has to be reconfigured occurs when a SQL Server is configured with Data, Logs and TempDB stored on same LUN with Lazy Zeroed VMDK format. You can also go back and delete the Recovery-flat.vmdk.Finally, power up the new Recovery VM and your old VM (Win2012) should be back online good as new!.Now just copy the Win2012-flat.vmdk file from the Win2012 folder over to the Recovery folder (Note: This step could take several minutes):Ĭp /vmfs/volumes/vmNFS02/Win2012/Win2012-flat.vmdk Recovery-flat.vmdk.Rename the original Recovery-flat.vmdk file to.Then navigate to the Recovery VM folder.Enable SSH on the host and logged in via PuTTy (or WinSCP) and verified the contents of Win2012 folder:.I created a new VM called Recovery with the same specs as my Win2012 server (2vCPU, 4GB RAM, 40GB HHD).How to Recover a VM using a vm-flat.vmdk file Ok, now on to how to restore a VM with a missing. I then deleted all the files associated with that VM with the exception of the Win2012-flat.vmdk file, as seen in the image at top.Īfter the files had been deleted I tried to power up the VM knowing it would not and received this error. That’s when I remembered a method to recover a VM using the vm-flat.vmdk file that I had actually done 2-3 years ago.įor this example I’ve created a Server 2012 virtual machine (called Win2012) and placed a text file on the desktop called “Important Info”. I believe in backups, I like to have my VM’s backed up so that I can depend on them for events just like this very issue. A couple days ago I was asked the question “ An admin deleted the vmdk file associated with a VM, there are no snapshots or backups of the VM.
0 kommentar(er)
