Obsolete and instant VMDK file

Similar Questions

• Snapshot deletion failed, remove the instant vmdk files?

  We have a 2 TB data store that became close to completely full. I tried to delete a snapshot that got to 95% the data store completely filled and then pretty much killed the server.

  There are 2 drives on a data store. The disk system (Server.vmdk) is 50 GB and the second disc (Server_1.vmdk) is 1.95 GB

  I managed to get the operational return server to convert the system disk to a new virtual machine (Server_New.vmdk) on another data store, removal of the original vmdk in the data store complete and then adding a second drive that points to Server_1.vmdk

  As far as I can tell everything is everything works fine and it's not like there are any missing files so I am happy with that. One thing I couldn't confirm if I can delete the snapshot files. I'm pretty confident that I can remove them without causing problems, but I'd love to get confirmation from someone who knows what they are doing.

  I've looked through the vmware.log file and don't see any mention of server_1 - 000001.vmdk or 000002.vmdk - server_1. Also in browser data store, the modification date and time is 20 minutes before server_new.vmdk and server_1.vmdk and these times coincide fairly well with when I converted to the virtual machine.

  If anyone can confirm that these files from snapshots can be deleted safely, it would be greatly appreciated.

  If the snapshot is attached to a VM voltage you will not be able to delete in file locking in the data store Navigator. If ca you remove it, then it is not attached and I guess it's safe. Another way is I rename and then see if there is any impact, otherwise it is then safe to remove

• Instant VMDK files do not delete after deleting snapshots

  Hi - I have a server SLES/OES2 with two discs - 75 and 750 GB.  I deleted a few shots after that test app and I'm back to instant No.  The data store always shows two files VMDK - server_1 - 000001.vmdk (17 GB) and server_1 - 000002.vmdk (56 GB).  The second is still active in this sound change timestamp.

  This is the last section of the VMX file:

  debugStub.linuxOffsets = "0x2d1ac, 0xffffffff, 0 x 0 0 x 0, 0xc58223b, 0x0, 0xc582254, 0x0, 0x2d1a8, 0 x 0 0 x 0 0 x 0, 0xc58226c, 0 x 0"

  scsi0:1.filename = "SSS-SLES-TEST_1 - 000002.vmdk.

  scsi0:1.mode = "persistent".

  scsi0:1.ctkEnabled = "FALSE".

  scsi0:1.DeviceType = "scsi-disk" hard

  scsi0:1.present = 'TRUE '.

  scsi0:1.redo = «»

  I got 32 GB free in the data store until I deleted snapshots, then he went to 0 GB free!  I deleted ISO files, and now it's up to 3.7 GB free. The total data store is 1.36 TB

  There were not errors when deleting sanpshot - although it took awhile.

  All this started because I had forgotten that this VM had snapshots and I started to copy the data to the server and got a warning that server_1 - 000001.vmdk was full and remove the space.

  I don't think that the virtual machine is healthy!  Any suggestions?

  Thank you

  You can try to power down the virtual machine, taking another cliché and with a bit of luck the entire tree of the snapshot will be detected. After that, keep the VM down and try to delete all snapshots.

  http://KB.VMware.com/kb/1002310 also have relevant information and instructions, you can follow.

  Marcelo Soares

  VMWare Certified Professional 310/410

  Technical Support Engineer

  Globant Argentina

  Review the allocation of points for "useful" or "right" answers.

• Instant capture files increase in size after copy

  I have recently setup a u1 ESXi 4.1 installation. One of the virtual machines has two (vmdk) disks running w2k3 and there a snapshot taken while the virtual machine is suspended. Before making some major changes to w2k3, I decided to save this VM by copying (while he was still suspended) all the files to another folder in the data store using the datastore browser in vSphere.

  It worked well except that I am intrigued and frightened by a sharp increase in the size of the two snapshot vmdk files. The original shots have been respectively 508 MB and 82 MB and base vmdk files are 20 GB and 10 GB respectively. After copying all the files from the virtual computer to another folder for backup in the data store, the snapshot vmdk files had increased in size to 10.2 and 5.5 GB respectively. Base vmdk files have the same size as the originals.

  Could someone please explain the increased size. Clearly after a dozen shots if this behavior has been reproduced for each snapshot then any copy would fill the entire data store.

  I have found no documentation why this would happen, but this behavior is what to expect when Instant copying VMDK. I did a few tests some time ago (I think it's with ESX 4.0 GA) and the only way - if I remember correctly - to copy the snapshot files without increasing the size had to vacate the snapshot by first transfer to a new vacuum/folder on the same data store (far enough from the base vmdk) and copy it.

  André

• Recreate .vmx and vmdk file and merging instant discriptor

  Hi all

  I'm under ESXi 5.0 and miss me the vmx file descriptor of a particular virtual machine.

  The machine works fine until I stopped him. Off, I will not be able to restart it before I recreated the descriptor file and created a new .vmx.

  The only files that are located in the folder of the virtual machine are:

  -rw - 1 root root 23152713728 Sep 19 22:43 TS1-000001 - delta.vmdk

  -rw - 1 root root 0 Sep 19 22:14 TS1 - b4014f27.vswp

  -rw - 1 root root 80530636800 Sep 19 22:38 TS1 - flat hard

  -rw - 1 root root 20166422528 Sep 19 22:14 TS1_1-000001 - delta.vmdk

  -rw - 1 root root 107374182400 Sep 19 23:03 TS1_1 - flat hard

  -rw - 1 root root 0 Sep 19 22:09 vmx-TS1-3019984679 - 2.vswp

  I was able to recreate the disk descriptor file and attach it to a new VM created with the same characteristics as the former.

  It will start, the only problem is that the disc does not contain the latest data from the snapshot. So it is pretty useless now.

  So my question is: what steps should I follow (and when) to merge the Flash disk with a parent?

  I have a backup of the vmdk unmodified and the snapshot files listed above.

  I hope someone can point me in the right direction.

  Thanks in advance.

  Sources: lack vmx and vmware.log file and VMware KB: Re-create a missing virtual machine disk descriptor file

  Welcome to the community,

  snapshots are used in channels, i.e. you must re-create the instant string for each of the two virtual drives (see attached hard files) and make sure the .vmx file points to the latest snapshots.

  An easy way to recover would be to create a new virtual machine with the VM current name "TS1" and two virtual disks (virtual disks size doesn't really count) and create a snapshot. Then replace the hard the new virtual machine with the file descriptor files in the attachment of this post and the hard delta/flat files.

  If you want to do differently - that is with manually editing the virtual machine's .vmx file - make sure you relaod the configuration after editing the file (seehttp://kb.vmware.com/kb/1026043)

  André

• You press on delete all selected items by browsing the data store and accidentally deleted a vmdk file which has the OS on it

  I accidentally deleted the vmdk file that has my OS on it by pressing the "Delete selected items" button in the window of browser data store. Is there anyway to recover? I have a snapshot that doesn't seem to work. There is still the VMDK file in there, but it has now 'delta' be added at the end. Now I get an error message when I try to turn on my VM saying that he doesn't get the vmdk file, of course.

  

  

  From the screen shots looks you have deleted only the descriptor hard files that can be recreated. To ensure this is the case, please provide a complete list of the files in the folder of the virtual machine and attach the last file.log of vmware(from the virtual work computer) to a post response to view required details.

  André

• Rename a vmdk file and move it

  situation: a guest VM o/s is corrupt.  The virtual machine has a second VMDK file that contains the data.   Need to build a new virtual machine with the same naming convention.   Power off the VM origin with disk virtual corrupt system.  Removed from the inventory.   Then I recreated another virtual machine with a good guest o/s.   Now, I need set the data disk, but the label for this VMDK is exactly the same as the original system disk.   So the question is: can I rename the original data VMDK file and move it to the virtual machine created as a second virtual disk without problems?   Thank you.

  Each virtual disk consists of two files, the file hard small header/descriptor and the file data (flat file or delta). For the rename command, you provide the name of file descriptor only.

  André

• the VMDK files are more and more and more...

  I have vmware 8.01 with two virtual machines. OS Win7 64 bit ultimate host, guests are win7 ultimate 32-bit. The first VM was created by workstation, with 80 GB of HARD drive and this virtual machine works very well, the vmdk file size is constant.

  The second was created by the virtualization of a physical machine. It has 298 GB of HARD drive. I created it three months ago, and now the size of this virtual machine is 505 Gb in the host file system. This virtual machine, called 'Prospero' has ten vmdk files:

  Prospero.VMDK 240 GB

  Prospero - 000001.vmdk 19 GB

  Prospero - 000002.vmdk Gb 116

  Prospero - 000003.vmdk 40 GB

  Prospero - 000004.vmdk 56 GB

  Prospero - 000005.vmdk 12 GB

  Prospero - 000006.vmdk 3.3 GB

  Prospero - 000007.vmdk 4.3 GB

  Prospero - 000008.vmdk 13 GB

  Prospero - 000009.vmdk 14 GB

  Yesterday, the size of the last file vmdk file was only 500 MB. It is now 14 GB.

  Initially, I set the snapshot generation and later I switch, but the growth of the size of the vmdk files continues day after day.

  Said VMWare tools: 'the fret is disabled for this virtual machine.

  What can I do to stop this more and return to the normal size of 298 GB?

  I've attached the vmx file.

  Welcome to the community,

  Initially I set the snapshot generation, and later I turned off...

  It seems that you have the "characteristic" Autoprotect is always enabled. The .vmx file still contains many entries of "RollingTier". You will need to disable Autoprotect for the virtual machine and then remove snapshots using the Snapshot Manager.

  André

• I - delta.vmdk files, non - .vmsn files. How to restore the instant guest operating system?

  Hello

  Coincidentally, using the browser data store, I've deleted almost all the files in one of the guest OS. Only files vmdk (dish and delta) have survived. So far I've managed to run (using this link http://tinyurl.com/yda5f8d ( ) the guest using OS his - flat.vmdk file and it works very well. The problem is, it's an operating system in the former State, and I would go back to the last snapshot (I have two actually).

  I have ESXi 3.5 and the use of the Mode of Tech support. So I base (flat) file and not visible (from vClient) snapshot two working files. Browser data store using I can see them under delta.vmdk - 000001-xxx and xxx-000002 - delta.vmdk. Should what kind of magic I type in the console to restore my operating system in the lates snapshot? It's ok to merge these snapshots in a main flat file if it would be faster or easier.

  Concerning

  Piotr

  OK, let's give it a try.

  Attached you will find a collection of files that are generated, assuming that the snapshot 000002 was the last. I'll give you the steps to make sure that the current data files will not be affected where 000001 was the last snapshot.

  1. delete the virtual machine of the inventory
  2. Download files attached to the virtual machine file
  3. Delete the w2003r2.vmsd file if it exists.
  4. Right-click on the vmx file and select "add to the inventory.
  5. Open the virtual machine settings and uncheck the box "connect to power on" for the network card (only to make sure that the virtual machine does not connect to the network, where the snapshots are not in the right order)
  6. Important: Create a new snapshot, and to ensure that the new vmdk file is referenced in the disk of the virtual machine settings

  Now you can try it without risk of turning the virtual computer and check if everything seems OK. I suggest that you take a look at the Windows event logs and check if the last entries are from the scheduled date. Because you have turned on on the VM from the file (flat) base, run 'chkdsk /f' for all readers to solve possible problems.

  If this doesn't seem to be the right order, please report and I will edit the files to make snapshot 000001 the current.

  Once everything is ok you should really consider deleting snapshots. To ensure that this does no new issues, please provide the build number of your hosts ESXi and the amount of free disk space on the data store!

  André

• SRM and VMDK files on separate LUNS

  Generally, all General all virtual machines requiring SRM are on a pair of LUN (i.e. all content VM). In the case of DR all LUNS are toggled together so that the entire virtual machine is in static mode for recovery.

  However, we have a new requirement for a certain virtual machines that have a certain number of VMDK files, even if the virtual machines are SRM, they all have a single VMDK on separate LUNS which are not necessary for the failover. The question I have is if in the case of DR VM works on another site without the missing VMDK file? and the virtual machine becomes corrupted if all files are not present?

  I did some tests in my environment. This works.

  I have a VM that resides on the data store ' *-SRM02 '. I added the second vmdk residing on non-replicated data store "LabManager02".

  Now when I try to protect this virtual machine with MRS, I get an error:

  A virtual machine has one or more devices that do not have file on Lun being replicated backings.

  and the Wizard "To configure Protection" opens.

  On the "Storage devices" screen, you can see that the second vmdk has a yellow warning mark:

  

  When you press the "Detach" button, the unreplicated vmdk turns to "Not attached":

  

  I ran the resumption of the trial, and he succeeded.

  Once, make sure data residing on the partitions that you want to detach is not needed for the server and applications to run normally.

  Michael.

• the vmdk files are compatible with ESXi 4.1 and Vmware server 2.0?

  I would like the two 4.1 ESXi and Vmware server 2.0 use the same vmdk file, of course, not at the same time just to the emergency plan. Is this possible?

  Hi Spitzmann,

  Welcome to the forum.

  Yes, they use the machine material virtual version 7. Take a look at this kb .

  Useful another link .

  Concerning

  Franck

• Windows 7 vmdk file not found, but it's really there...

  Had a running instance of MAX OS 10.9.2 Fusion 6 and a VM Windows 7, everything worked fine.  Had to reinstall the operating system using the procedure of restoration of Mac (alt - R during startup) to remove stuff JAMF Casper and re - take control of my machine after leaving a company. After recovery / re-install of OS X... I tried to use the original VM file and the merger could not find the vmdk files. So I restored a "Windows 7.vmwarevm" VM file Time machine. Same exact results... Fusion is up fine, recognizes the Windows 7 VM, but is not able to find the file "Windows 7.vmdk". When I try to start the virtual machine, I get the error message "could not open the file" / users/brucekreis/Documents/Virtual Machines.localized / 7.vmwarevm/Windows 7.vmdk Windows ":"the system cannot find the specified file". ".

  
  

  I can see it in a terminal window, checked that I am the owner of all files and directories in the tree, and they have at least the permissions for the owner, RW read only for all the rest... I changed the permissions to all access for files and dir (chmod-r 777 < dir >) tree and even reset the ACL (r n < dir > chmod). I can change the configuration files using the console VMware fusion library and check that it changes through the terminal window.  I tried to delete the .lck files and catch instant and re-did the file .vxm to the 7.vmdk Windows, without any change in the error message.

  
  

  I always suspect permissions, ACL, or something dealing with the recovery changed. I restored the original file .vmwarevm yet once, so you can see it of original state before I started to make changes and ran the util to collect information of technical support. I attached the zip file.

  FWIW... I tried to import the virtual machine and create a new virtual machine from this instance, but it is gray in molten selection windows, as if it is not recognized as a valid VM.

  Thank you in advance...

  You are missing two scopes binary "twoGbMaxExtentSparse', a basic disk, and the other from the first snapshot disk.

  Windows 7 - s009.vmdk

  Windows 7-000001 - s008.vmdk

  It is a workaround solution mainly for the express purpose of recovering data from the user, which is stored in the virtual hard disk, not necessarily get working 100% again.

  Copy Windows 7 - s040.vmdk for Windows 7 - s009.vmdk and Windows 7-000001 - s039.vmdk for Windows 7-000001 - s008.vmdk.

  This replaces the missing binary extensions with empty extents.  This allows VMware Fusion a string of competition and makes it look like a complete set of files hard.

  The problem is the two missing bodies, look at the size of each before and after, there will be some lack of content.  How the mission critical, can not say.

  You can try to start normally or start first with an ISO Image live and make recovering data first, and then try to run normally.  I can't say exactly what will be broken/missing except however backups clean* you don't have much choice.

  ==========

  * It is a known fact that Time Machine is not 100% reliable backing up/restoring VMS in all circumstances/conditions.  Also back up Virtual Machines via Time Machine of disk/time intensive and wastes a lot of space for something that may be corrupted and worthless time to restore it.  At least I would exclude the Virtual Machines with virtual machines and Time Machine shutdown, not suspended and VMware Fusion closed and then manually copy the VMS to another location, preferably on a different physical hard drive.  So keep the user data stored in the virtual machine saved out of the Virtual Machine on a regular basis in order to always have a backup of the current user data.  If you need to restore a properly saved by VM is not as common at least you will have a virtual working Machine and data user to go forward with when you find out your Time Machine backup of the virtual machine fails.

  Also take a look at: best practices for backup of virtual machine (programs and data) in VMware Fusion (1013628)

• Instant orphaned files - need to recover data on the basic disk

  Hello

  I'm sure this has been asked several times before, but how merge content from an instant orphan to the basic disk?

  Reading over there seem to be several different methods to do so.

  I have a virtual machine with three RDM, the virtual machine is running at the wide base VMDK disks but there is a single snapshot file associated with each base VMDK, snapshots do not appear in the Snapshot Manager.

  I tried to change the snapshot. The VMDK files and change the parent CIDs for the basic disk, but still not instant show in the Snapshot Manager.

  Is the best way to stop the virtual machine, remove the inventory and then add it to the inventory, I don't see the shots if the parent CID is correct?

  What is a better method?

  2. turn off then turn off the virtual machine (if it is not already off). Stop the current virtual machine with any Active snapshots.

  3. once the virtual machine is completely turned off, create a unique snapshot of the virtual machine and do not feed upward after this step.

  4 browse your data store for the virtual machine and look for the numbers you hard files. Instant latest should only be a few megabytes, and you want one that is just before that.

  5. go to the command line console and edit the .vmx for your virtual machine in the container for data store. Looking for a similar article to the following for each of your virtual disks.
  
scsi0:0.present = "true"
scsi0:0.fileName = "???-00002.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"

  You want to change the "scsi0:0.fileName =" section under the same file name that you found in step 4. You will need to repeat this in the file for each virtual disk on your VM.
  Save the .vmx file, overwriting the original.

  6. now, it will be a long process, if the hard files are large (more than 20 concerts) and can last several hours. During this process, you may lose connectivity to your ESX Server on the client of the infrastructure. What you need to do is run the below command from within the container to store the virtual machine data.
  
vmware-cmd <your .vmx file> removesnapshots


  7. once the previous step is complete, check your VM settings in client infrastructure and check that your virtual disks are now pointing to the original hard file (does not contain de-00001 etc.). If everything was successful, you should be able to power to the top of your VM.

  8. once the virtual machine is running and check the operation, you can remove the last numbered - 0000x.vmdk that was created from your snapshot in the third stage (should only be a few megabytes). This file must have been ignored by the instant withdrawal because you have changed the .vmx file.

  Question I have is if the basic disk has been changed today I lose all changes today when merging the snapshots (which have not been written to since 18:00 yesterday)- or will be the basic disk back to 18:00 yesterday and lose all changes today?

  If you need to extract data from instant orphans, you know that you can NOT do without altering the current state
  new files from today will still be there - but they are not referenced in the MFT and other pieces are replaced by old data of the orphan snapshot
  If you must do this with a backup...

  or - possibly use a snashot of the RDM, as it is now...

  in any case – which gives good advice is almost impossible without sitting in front of the case

• Thin provision NFS works only for instant VMDK

  Hi guys,.

  We have a host of ESXi 4.1 using NFS as a storage device. NFS is provided by the platform, Bluearc Mercury.

  Whenever I create a new virtual machine, for Thin Provisioning option is checked but also gray outside. There is a line saying:

  "Actual allocation policy will be determined by the NFS server.

  I'll check the newly created VMDK and it's a thick disk, it consumes as much disk space I put for the disc size.

  So, it makes me believe that the Bluearc Mercury does not support provisioning.

  The strange thing happens after that I did a snapshot, another VMDK as server - 0001.vmdk was created, and it's the thin disk.

  Someone at - it the similar problem?

  Kind regards

  Derrick

  Showmanlkz,

  On the BlueArc server, file systems are provisioned files, thin as VMDK files are created as "fragmented files".  Just a slight difference in terminology, but the effect is what you're looking for in what concerns the commissioning only the disk blocks that are actually used (thin provisioning).

  If you have created a 10 GB VMDK file, but have only 5 GB of data on the inside, only pointers to these 5 GB of data blocks will be created.  Us will not pointers to blocks of empty data.  Standard orders will make reference to the metadata VMDK structure and will report on the 10 GB file.  In order for a command 'df' to show the use of real drive (5 GB), rather than the allocated size (10 GB), you must enable the "true fragmented file" mode.  Contact the BlueArc TAC for the real run command.

  Snapshots are a completely different beast.  By default, they are only pointers to a point static instant copy.  However, if you use our new feature JetClone to create clones in entry level file, these files will be also thin provisioned, only as the clone diverges in content data from the original VM has been created between more and more.

  Julie HG

  Product Manager, BlueArc

• How to retrieve a large vmdk file in ESXi?

  Hello

  I desperately need help. I have a server with ESXi. One of the virtual machines in this server had a top serving our customers mail server. We had to move this mail server to a different location. When I tried to re - create the virtual machine with the same e-mail server (for testing purposes) all of a sudden, the big vmdk file disappeared. Of course, when I try to load the machine now, it gives an error "file not found".

  I read on other pages on how to recreate the vmdk file, but they were all on ESX and has not worked for me. The best method was present.

  Please can someone help me on how I can get the big vmdk file?

  Thanks in advance.

  Kind regards

  seedeg

  OK... explaining:

  A VMDK file is the union between a VMNAME.vmdk header file and a file VMNAME - flat hard. The datastore browser, when you have both, they appear as one, as on the second screenshot.

  The virtual machine always point to the VMNAME.vmdk file, which points to the VMNAME - flat hard, which really contains the data. You will never see the dish once that these two files are located on the data store, but sometimes people delete it and I was suggesting that it may have happened to you.

  Hard 00000files are instant. They are the changes on the original flat file logs, but if you don't have it you can't rebuild since the change to connect because you do not have the original data map.

  You may need to call a company to recover files from disks, or look for some tools which does this in VMFS volumes - I don't know everything, since VMFS is too simple and not to keep track of deleted files unless you take a snapshot of the file system in some time.

  If you do not have backups and can produce the VMDK or the flar. VMDK no matter where, there is nothing more I can do to help you. Sorry about that

  Marcelo Soares

  VMWare Certified Professional 310/410

  Master virtualization technology

  Globant Argentina

  Review the allocation of points for "useful" or "right" answers.