Old vmdk files

Hello

I have some data stores that have a few folders with a few old VM names, we used earlier in our infrastructure, but do not exist today. These files contain nothing more than hard files that are attached to other virtual machines, and they are still in use (the date of modification to files hard comes this week). File hard names are always based on the old virtual machines that were used previously. My question is:

Is it possible to know which virtual machines using these hard currently files?

Elodie

Maybe this PowerCLI help script: http://vniklas.djungeln.se/2011/12/05/virtual-machine-vmdk-file-report-with-powercli/

If you prefer an additional tool, RVTools might help.

Tags: VMware

Similar Questions

  • My vmdk files not visible from vpshere but visible from ssh console

    Hello

    I would use my dataontap virtual appliance of Netapp communities tar file.

    Their installation guide, they show just to put this on the data store tar file.

    This tar file contains the following files:

    DataONTAP.vmdk

    DataONTAP.vmx

    DataONTAP - flat hard

    DataONTAP - nvram.vmdk

    DataONTAP-nvram - flat hard

    DataONTAP - s001.vmdk by DataONTAP - s126.vmdk (126 disk files)

    DataONTAP - sim.vmdk

    DataONTAP - var.vmdk

    DataONTAP-var - flat hard

    I put this vsphere on the data store file and extract it to ssh connection on esxi with the command "tar".

    All files are now visible to PuTTY connection on esxi

    1 / but when I browse datastore, I see not all vmdk files. (missing 126 files on disk)

    2 / when I turn, this virtual machine, I have this error "DataONTAP - sim.vmdk file not found on /vmfs/volumes.../.

    But this file exist on the path specified error.

    Configuration:

    ESXi 5.1, NFS datastore.

    Stand-alone node (without cluster)

    No vcenter

    Spatial data store are free and available.

    Checksum for this tar file are OK.

    Thank you very much

    Concerning

    The files in the archive are the data files, and not the descriptor. I guess DataONTAP - sim.vmdk is the file descriptor for these files DataONTAP - sXXX.vmdk . To ensure that this is the case, please attach the DataONTAP - sim.vmdk.

    If this is the case, here are the steps that should make the usable virtual machine:

    1. load the muliextent module
      vmkload_mod multiextent
    2. Rename the virtual disk file to a temporary file name
      vmkfstools EI DataONTAP - sim.vmdk DataONTAP-sim - old.vmdk
    3. clone the virtual disk in a format supported the original file name
      vmkfstools-i DataONTAP-sim - old.vmdk DataONTAP - sim.vmdk - d thin - an ide
    4. unload the module multiextent
      multiextent vmkload_mod-u

    At this point, you should be able to turn on the virtual machine. If everything works as expected, you can delete all the temporary files of DataONTAP-sim-old * hard .

    André

  • flying over the vmdk files after storage vmotion

    People,

    I finished a few vmotions storage and I see that there are some vmdk files left belonging to a virtual machine by flying over in the source data store.

    Storage vmotion however was very good. Time last modified files are several months old.

    If the vmdk files are old players was dismantled some time back?

    There are also a few - zdump.000 left side files in source data warehouses. should you be worried about those?

    Rahul-

    Although I suppose the files are orphans, I always double-check for use before deleting. Virtual disk file (hard) can be changed only in case Active snapshots exist for them. What you can do is run RVTools, to see if these files appear as 'Zombies' and if so, I would say you first create a subdirectory and move the "orphans" files above and - if everything continues to work as expected - delete at a later date. Alternatively you can check the vmware.log of the virtual machine file to see if the files appear here.

    Zdump files are created if something unexpected occurs. However, it is difficult to say what the brought to be created and if they are old and have any problems, you can delete just them.

    André

  • Storage vMotion + vmdk files in different folders

    Hello

    Storage vMotion will spend the vmdk files [in 2 different folders on the same data store for the moment] in the same folder while that migrated to the different data store?

    Why the vmdk files are in 2 different folders:

    Windows 2008r2 was misconfigured evil so anything by rebooting, it went to the system recovery. Was not able to recover the system.

    The system was rebuilt, and 2 D: and E: drives were attached ["use an existing virtual disk"] as of the existing vmdk disks to the new virtual machine.

    So drive C: [rebuilt VM] vmdk file is located in files vmdk D: & E new-vm-folder & readers are old-vm-folder.

    So "storage vMotion will pass the vmdk files [in 2 different folders on the same data store for the moment] in the same folder while that migrated to the different data store? I know that storage vMotion and change of name of the files/folders works well.

    If this is not the case, what would be the best practice to get is sorted?

    Thank you very much

    Pawel

    Welcome to the community - Yes it will be. The other option would be to turn off the cold and virtual machine migrate the virtual machine to the correct data store.

  • Clean the VMDK files

    I was watching our store data this morning and noticed that some of the virtual machines have multiple VMDK files. They are labeled as Servername.vmdk, Servername_1.vmdk, etc. We had played around with VM data recovery in the past, but no longer use it and I wonder if that's what they are. Is there a way to know if one of these files is allowed to delete? Some of them take a lot of space.

    Logs (old) we can see that the virtual machine has two virtual disks in the annex:

    scsi0:0. FileName = WSBWINSBS.vmdk
    SCSI1:0. FileName = WSBWINSBS_1.vmdk

    The other two... ctk.vmdk files are used to track modified block, which I think was activated with backup of tests.

    André

  • VMDK file name

    one of our virtual machines has been renamed, but the label in the data store for the vmdk file is always the old name.  I know that I can VM V2V and rename it but was told that if I sVmotion the disk to another location of data store that it renames automatically.  is that correct?

    That is right.  A storage vMotion will solve your problem as well.

  • Ways to convert VMDK files

    Hello

    We recently had a server crash, and I decided to rebuild the server and put ESXi 4 on it.

    However, backups, I have old machines are on disks formatted in NTFS (not USB, they are in our backup machine) which means that they are unable to be mounted (AFAIK) under ESXi.

    The problem I have is that the VMDK files I have are the old version so not compatible with the curernt ESXi. I know I can convert them using vmkfstools (with i - pass memory) but I have two problems with this. First of all I have to bring to the ESXi server initially, and since we look at about 5 TB of data it will take FOREVER (been running for 2 days - even far complete) and the second is even if I get them on the server, I'll need another 5 TB of disk space to convert them to , which I did not.

    So my question (s)

    1 - is really not in any case to mount a NTFS (not USB) under ESXi drive - like that I could simply convert from the backup to store data (and easy) drive

    2. is there a converter of the VMDK files offline?

    3. is there a way to change the NTFS drive into a format readable by ESXi (ext3/resierfs/something) without losing data

    4. is there a way to optimize network transfers maybe?

    5. is there another solution that I could look at

    Thanks in advance

    Bob

    Whoa Whoa Whoa, back up the truck.

    You can use VMware Converter to do this and save yourself a TON of headaches.

    First of all, what version of VMware did you use ALREADY in the VM host? VMware Server? VMware GSX? VMware ESX 3.5 - 2? VMware Workstation?

    Second, do you have JUST the VMDK files? or are you support VMX files as well? If you do not the VMX, you have headaches on several levels. Converter needs the VMX file to know how many processors the virtual machine was, he had what hard drive controller, etc. to perform a proper conversion. If you do not have the VMX (and just the VMDK) files AND running ESX 3.x, you can redo the VMX file by doing a NEW VM on the ESXi 4.x server and attaching the VMDK file to it. You need these VMs as VM hardware version 4 (NOT 7), and 'best' guess as to what kind of equipment they had for the network card, card scsi, etc. This could put you in the right direction very fast and would be easy to test it on one of the smallest virtual machine if you had all tiny.

    Thirdly, what you used to get backups of virtual machines before?

    This might be easier to do offline, do not hesitate to email me at jonmkohler AT gmail DOT com and I would be happy to give you a hand with that. If not, put the answers here.

    Jonathan Kohler

    VCAP4-DCA / DCD

  • a VMDK file is not recognized as vmdk file in esxi

    For some reason strange esxi is not recognizing my vmdk format vmdk file. He sees it only as a normal file. And when I try to turn on the virtual machine, I get an error indicating that the vmdk file is not a valid file.

    It seems that you (or someone else) changed the header vmdk file manually. Otherwise it would not exist a file 'vmdk.old '.

    Go to the command line (on the console or ssh) and check that the content of the header vmdk file is correct. If you need help, please send the header as well as the file ".old" file to see what has changed.

    André

  • deleted all vm outside the flat vmdk files - recovery?

    In a moment of madness I accidentally tried to remove a virtual machine from a data store. All updated files other than the flat vmdk file then deleted... It is not a critical system, but I still prefer to retrieve by using the existing if possible vmdk file. Since it is a flat file without descriptor I can not simply use it as basis for a new virtual machine, then how would you go to get it? In my view, a provisioning was not used, so should I just copy on a linux machine, it mount it and copy the relevant files or I can pick it up in esx - i?

    Edit: I should probably add that I know the exact size of the disc, but when I try to create new disks I can't manage to get split into flat vmdk / basic (with an idea of just using the new disks for the old descriptor)

    Take a look at sanbarrow.com for some details on this kind of issue, but basically, you can follow this process

    (1) create a new virtual machine with the same disc than the old size.

    (2) copy the file descriptor on file with just the file flat.vmdk left.

    (3) change the descriptor file (hard) and update to point to the old file flat.vmdk.

    (4) allowing the VM.

    (5) change the new virtual machine and delete the virtual HD.

    (6) copy the old file to the new folder VM with vmkfstools.

    (7) to change the new virtual machine and add a file of existing (using the new copy) drive.

    (8) to turn on the virtual machine.

    But before that, you can you

    1) check for us if the virtual machine still works

    (2) post a list of the folder where the virtual computer files were (with the-l option to show the size of the file).

    (3) can you tell me what VMware product and version are you using?  I guess ESXi 3.5 but it would be preferable to confirm.

    Dave

    VMware communities user moderator

    Now available - vSphere Quick Start Guide

    You have a system or a PCI with VMDirectPath?  Submit your specifications to Officieux VMDirectPath HCL.

  • Reduce the VMDK files

    I have a W2003 server, with multiple partitions (all VMDK individual files within a data store), I want to shrink one of the partitions (not o/s) and use space to push another two, - is this possible?

    Thank you

    Another solution is to add a smaller vmdk, copy all data (with the guest operating system) and remove the old vmdk.

    Or you can use vmkftools and copy the vmdk into a thin disk.

    André

  • Problem VMDK file large cluster in a box

    So I've been running a flavor of vmware server 2.x since its release with little or no problems. Not that it matters but my host server is a Dell Poweredge 1900 with 32 GB of RAM, running windows server 2003 x 64.  I have also 2 Windows VM that I run as a cluster in a box, and they worked very well in this way for more than 3-4 years at the time of vmware 1.x. Both virtual machines have been set up exactly as such:

    SCSI 0:0 16GB & lt; - c drive

    1:0 500 MB & lt; - quorum SCSI cluster

    SCSI 1:1 12GB & lt; - the app cluster disk

    1:2 950 GB SCSI & lt; - storage of cluster disk

    SCSI 1:3) 12 GB & lt;-the sql cluster disk

    1:4 250 GB & lt; - disk SCSI storage of additional cluster

    What I did recently to set up a new file 2 TB since vmware server 2.x vmdk will now allow you to make files vmdk bigger than the old limit of 950 GB. This new 2 TB file was supposed to replace my 2 readers of old SCSI 1:2 and 1:4 SCSI cluster storage. After making the swap and copy all data to a vmdk file again, I noticed a problem at any moment I'm going to and move the resource cluster VMDK new 2 TB to the other server. Basically the two servers stop responding and it seems that vmware server choke on the 2 TB for some reason vmdk file any. Here's what I see in my logs any time that this happens.

    01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

    01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

    01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

    01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

    01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

    01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

    01:21:47.953 02 Dec: vmx | scsi0:0: READ command (10) took 23,142 seconds (ok)

    01:21:47.968 02 Dec: vmx | SCSI1:2: READ command (10) took 45,504 seconds (ok)

    01:22:46.062 02 Dec: vmx | SCSI1:2: RELEASE (6) command took 5,235 seconds (ok)

    01:22:46.093 02 Dec: vcpu-0 | DISC: Resync'ing disc scsi1:2.

    01:23:08.593 02 Dec: vcpu-0 | DISKLIB-DSCPTR: open : 'storage3.vmdk' (0x6a)

    01:23:08.593 02 Dec: vcpu-0 | DISKLIB-LINK: opened 'e:\virtual_machines\storage\storage3.vmdk' (0x6a): monolithicSparse, 4194304000 sectors / 2.0 TB.

    01:23:08.593 02 Dec: vcpu-0 | DISKLIB-LIB: open "e:\virtual_machines\storage\storage3.vmdk" (flags 0x6a).

    01:23:08.609 02 Dec: vmx | SCSI1:2: READ command (10) took 22,527 seconds (ok)

    01:24:15.640 02 Dec: 1 vcpu. DISC: Resync'ing disc scsi1:0.

    Has anyone ever ran across this or has anyone ever used a file vmdk of this size as a cluster resource? As I said before that I had 0 problems with my cluster before I added this new 2 TB vmdk file...

    I'm not at all surprised that you get this problems.

    You use monolithicSparse vmdk type!

    For cluster in a box, I highly recommend flat VMDK.

    I wonder that it worked for you all with the drive more sharing

    ___________________________________

    VMX-settings- VMware-liveCD - VM-infirmary

  • Removal of the old update files

    I moved from Vista to Windows 7 (downloaded myself).  I am concerned about all the old backup files I have on my computer.  How can I determine what I have and how to remove them.  I did a deletion of hotfix files Backup on my XP, such as recommended by someone in this forum, and it worked.  Should I delete the old files of backup for Vista and Windows 7?

    Thank you.  Pat patricia Bern Bern

    Hello, once again. If you have upgraded to Win7, a lot depends on how you did the upgrade. Your best bet would be to repost your question here, Pat: http://social.answers.microsoft.com/Forums/en-US/w7install/threads

    Happy New Year! ~ Robear Dyer (PA Bear) ~ MS MVP (that is to say, mail, security, Windows & Update Services) since 2002 ~ WARNING: MS MVPs represent or work for Microsoft

  • Threats of virus after a clean install... where is the 'old machine' file?

    My PC has a virus; My anti virus would not repair it... After doing a clean install of Windows XP, I remember reading that I can delete a file named 'old machine' if the new installation worked. I installed Microsoft Security Essentials... For 3 days, everything worked was great until this evening...

    Tonight, I ran an update of virus definitions and then run the 'full' scan Microsoft Security Essentials has notified me that I had a few threats. There was also a warning on a temporary file and asked if I wanted to send it to Microsoft I did...
    I am trying to be proactive and prevention viruses take over this machine again... I remembered reading after installation 'own' that I should remove the file 'old Machine' if the computer works well after the clean install? .. .also had a warning on a temporary file.
    Any idea where I can find the 'old machine' file; (I thought the clean install would remove all)... I did a search on my computer and come with nothing
    Help, please!...

    Hello

    Step 1: You can remove it in c:/Windows. With the help of old cleaning disc.

    In the disk cleanup, select the previous installation of windows. Put a check mark to remove it.

    Note: this section, method, or task contains steps that tell you how to modify the registry. However, serious problems can occur if you modify the registry incorrectly. Therefore, make sure that you proceed with caution. For added protection, back up the registry before you edit it. Then you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click on the number below to view the article in the Microsoft Knowledge Base:

    322756 (http://support.microsoft.com/kb/322756/ )

    How to back up and restore the registry in Windows

    Description of the tool in Windows XP disk cleanup

    http://support.Microsoft.com/kb/310312

    Step 2: Run a virus scan to make sure that the computer is Virus-free:

    Microsoft safety scanner

    http://www.Microsoft.com/security/scanner/en-us/default.aspx

    Note: If infections are detected during the scan, there is a risk of data loss because infected files will be deleted.

    For more information:

    The disk cleanup tool stops responding while it is compressing old files on a Windows XP-based computer

    http://support.Microsoft.com/kb/812248

    It will be useful.

  • What is old compressed files. can I delete them and any danger ot my PC

    I have the old windows files compressed in my pc. I want to delete them. Is it safe to do so.

    Hello

    What exactly do you mean by the old compressed Windows files?

    If there is no concern for data or if it is not a Windows system file you can go ahead and delete the file.

  • How to remove the old compressed files? I have over 200,000.

    After being run-up disk cleanup, I show more than 200,000 old compressed files.  How can I remove them?

    You delete a file compressed just the way that you remove any other file, BUT...

    You can't really delete these 'compressed old files.  By default, in Windows XP Disk Cleanup tool will compress files that have not been used for 50 days.  Well, you can keep the files to which you have not accessed in the past two months.

    You can change the disk cleanup period is used to determine if a file is 'old'--> http://www.howtogeek.com/howto/windows/make-disk-cleanup-compress-olderor-newer-files-on-xp/

    However, many people (including me) just disable the analysis of "old files" because it is run much faster disk cleanup: see, for example,--> http://www.pctools.com/forum/showthread.php?49060-Disable-Compress-Old-Files-in-Disk-cleanup or http://www.kellys-korner-xp.com/xp_tweaks.htm straight line 48 (notice that there are two links, one to turn off "compress old files" and the other for him re - allow to) those reg files also change how Disk Cleanup deals by default temporary files - temporary files accessed during the 7 days are not deleted; the first files reg Kelly happening in 0 days and the file "undo" restores the default value of 7 days).

Maybe you are looking for