Recover a VMDK Snapshoted file

Similar Questions

• Not able to add the snapshot file to the virtual machine

  We have Win 2003 virtual machine running on ESXi 4.0.0 261974. The virtual machine has two vmdk files. We had taken the snapshot a few days back and today by mistake, we have removed one of the vmdk (DB - srv - 000001.vmdk - snapshot file). Now, we are not able to add the snapshot file to the virtual machine. When tried to add the existing vmdk, it displays only the source disk (DB - srv.vmdk). Please, help us to solve this problem.

  The GUI allows only adding the base vmdk. To add the Flash disk, you must manually change the vmx file. Registrations for the formerly removed virtual disk could still exist in the vmx file with... .present = "FALSE". After changing the vmx file you must reload the configuration. To do this, remove the VM of the inventory and add it back again (right-click on the vmx file).

  André

• standby of the comments file system create two snapshot files

  Why would or should suspend the comments file system create two snapshot files.

  In our environment, we have the following VMDK.

  Syntest.VMDK

  Syntest_1.VMDK

  Syntest_2.VMDK

  Syntest_3.VMDK

  Syntest_4.VMDK

  When I create a snapshot that suspends the comments file system it creates two syntest_1 - 000001.vmdk and syntest_1.000002.vmdk (as well as all of the files for snapshots).  Here is a screenshot.

  

  Why and is at - it something wrong?   I can find a ton of articles on stereotypes, but nothing that speaks.

  We are currently on ESXi 5.1.0,1157734.

  Thank you

  Mike

  Out of curiosity. Are two snapshots created even when you create the snapshot manually?

  With backup applications, this behavior is not uncommon. The first snapshot is created for the virtual machine write them changed data, while the current is/instant backup, and the second snapshot is created by the backup software to attach the virtual disk basic to the host/proxy backup as "independent - not persistent. Once the virtual disk is disconnected from the proxy the second snapshot will be discarded and then the first snapshot will be validated for the basic disk.

  CBT information should not be reset somehow, but updated as changed during the backup data.

  André

• Error: snapshot file < uspecified filename > is greater than th emaximum size supported by the data store

  I get the following error.

  File & lt; uspecified filename & gt; is superior to th emaximum supported by the data store

  My vm is 1024 GB, my block size is 4 MB and I 5.05 TB of free space.  The navigation data store, I see that there is a snapshot file incomplete 2gigs in size. I made snapshots to create in a different location from http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1002929 but still the same problem. Thanks for any help

  The virtual disk is too large to create a snapshot on a 4MB block size data store. The maximum size of VMDK is 1,016 Go.

  See "calculation time system required by the snapshot files" in http://kb.vmware.com/kb/1012384

  André

• The snapshot files exist on the data store, but not in the Snapshot Manager

  I searched for a question of space on one of our virtual machines throughout the morning.  I finally found that the virtual machine has two snapshot files (total of 120 GB) on the data store.

  The problem is that these pictures are not in the snapshot

  Manager. How can I get rid of these files from snapshots, recover the 120 GB drive

  space and keep everything in tact?

  Thank you all.

  -Dave Claussen

  [email protected]

  Try to create the new snapshot, and then remove all the...

  vcbMC - 1.0.6 Beta

  Lite vcbMC - 1.0.7

  http://www.no-x.org

• How to move the snapshot file

  Is there a way to move the snapshot files to some other hard disk partition?

  I'm running out of space on my hard drive partition wherer my VM resides, only option I have available is to remove my shot, I don't want to.

  Any suggestion?

  You must edit the vmdk and vmx - if it works by simply changing the vmx you do something I don't understand ;-)

  ___________________________________

  VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

• After a hard drive crash and recover most of my files on an external hard drive but who eventually became my only internal, because I live on an island in South America and there is virtually nobody on the island I live it can he

  After a hard drive crash and recover most of my files on an external hard drive which eventually became my only internal, but because I live on an island in South America and there's hardly anyone on the island I live who can help other that a friend, I took a trip to Miami to visit the genius bar and they did a new install of Capitan which I don't really like by the way.  In any case, I though I had lost all my iPhoto library, but I managed to find my photos. Only now I have two libraries... the iPhoto with images from my Photos on Capitan and 8 years.  Is it possible to consolidate them in a library?  And can I still use RAW to be able to edit photos? aIso, y at - it a tutorial for the Photos?

  In the future more facts and less editorial help here

  SO now, we know all about how you feel but nothing on your system or your problem

  What version of El Captain do you have (10.11.3 is the current version with Photos 1.3)

  You cannot merge libraries without third party software - Photos of power can merge pictures libraries

  You can migrate iPhoto libraries to libraries of Photos by dragging Photos icon in the Dock

  When you first launched the Photos it has migrated the last used for Photos iPhoto library

  I hope this will help, but to get specific answers, you need to provide real information and not feelings

  LN

• Is there a way to recover the EFS encrypted files stored on an external drive without the origianl certificate?

  Is there a way to recover the EFS encrypted files stored on an external drive without the original of the certificate?

  I had photos/files stored on an external drive and have been encrypted with EFS in XP. The main drive crashed, all keys have been lost. Got a new main drive, installed the new OS and now can't access encrypted files.

  Unless you can retrieve parts of your old drive or have a backup of your encryption certificate, you have probably lost all of your encrypted data.  Recovery agents work only if they are in place when the file/folder is initially encrypted.  A program like AEFSDR might be able to resurrect your old certificate from your old drive if it is readable at all.  If you plan to use EFS in the future, make sure you read the following article the court - particularly paragraph entitled "why you should back up your certificates.

  "Best practices for EFS file system.
    <>http://support.Microsoft.com/kb/223316 >

  HTH,
  JW

• Delete the snapshot files

  I have a Windows 7 VM running on an Intel Mac computer. The size of the VM folder is about 280 GB. A large part of this weight belongs to the snapshot files. I copied the Windows 7 VM on a real Windows 7 machine and its opening perfectly using the VM player and everything works fine.

  All I want to do is the snapshot of the files detected, because it takes a lot of space on my disk. I can do by the player, or what I need to do this on the Mac where it all started?

  Thank you in advance for your help!

  Chaz

  After going through the Menus you see snapshot commands?, no!

  While you can run a Virtual Machine that has Snapshots in VMware Player you can only manipulate them with Instances of the ACE.

  Otherwise, some options are...

  Add a second virtual hard drive and clone the existing to the new and then swap the VHD on.

  Use VMware vCenter Converter Standalone and create a new Virtual Machine from the existing.

  Install VMware Workstation and use it to delete snapshots.

  Install the SDK for the VMware virtual disk and vmware-vdiskmanager allows to create a new hard to replace existing ones.

  Back to VMware Fusion and delete snapshots.

• HOWTO delete a VMDK to a virtual machine without actually deleting the vmdk disk file?

  How to remove a file VMDK to a virtual machine without actually deleting the vmdk disk file?

  Details:

  My perl script, I need to temporarily remove a vmdk to a virtual machine file. However I do not want the vmdk file should be removed from the virtual machine. For example, the gui vsphere provides this option to delete a virtual disk without deleting the virtual disk from the disk files.

  In my script, I use the ReconfigVM_Task to do this. This does the job, but also removes the vmdk file. How can ensure me that the vmdk file will not delete the disk?

  The code snippet is something are:

  My $devspec = VirtualDeviceConfigSpec-> new)

  device = > $device,

  #device to delete above:

  operation = > VirtualDeviceConfigSpecOperation-> new ('remove'));

  Push (@$ devspec_list, $devspec);

  My $config_spec = VirtualMachineConfigSpec-> new)

  deviceChange = > $devspec_list

  );

  my $task = $template_view-> ReconfigVM_Task (spec = > $config_spec);

  would really appreciate your help

  s

  Take a look at this script: vmdkManagement.pl

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  VMware developer community

  If you find this information useful, please give points to "correct" or "useful".

• Recover a file VMDK Snapshoted / consolidate a snapshot

  Hello

  I have a very big problem and I don't know how to deal with in the right way, I had a few old server that was set up with the weekly snapshots.

  and we have some hardware problem with the server that cause some files to capture instant adeleted the data store ccidentally.

  We can recover some of the vmdk files.

  image attached with files you can find on the server.

  We tried a few steps in order to recover the machine (change on vm vmdk configure / create a new snapshot, and delete everything in the Snapshot Manager)-I was able to turn it on with the flat vmdk, but the data is less 6 months ago.

  I found a few articles on consolidate an instant snapshot and difficulty of string but I did not really understand how to go about it.

  What should I do? Is it possible to merge these files or extract files from them?

  

  Okay, so what I found in the files and file sizes I rebuilt an instant string possible.

  The string is: 5-> 4-> 1->->->-> db1.vmdk 6 2 14

  I had to modify two files hard (see attachment). The first fix was on no. 14 that indicated a snapshot does not exist n13. The (next) one parent that makes sense here is no. 2, so I went no. 14, no. 2. The second challenge was to change the parrentCID No. 6 to match the basic disk CID. The reason for this shift is more likely, because you have turned on on the virtual machine with db1. vmdk used as virtual virtual machine disk.

  What I recommend you do now, is to replace the two .. the VMDK (12 and 6) files with those that I have attached to this post and then clone the virtual disk from the command line by running vmkfstools-i db1 - 000005.vmdk db1 - clone.vmdk

  The next step is to attach the newly created clone as an additional virtual disk with a help of VM, or - if you want to see if the VM is able to start - fix it db1 - clone.vmdk directly on the virtual machine from db1. In the second case, please create a new snapshot before you turn the virtual machine with the cloned virtual disk. In this way that the db1 - clone.vmdk will not be changed.

  In no case be prepared there could be corruption in the file system of the client!

  André

• Help on the snapshot files and delta

  Hello

  Last night, does not have an ArcServe backup on a single virtual machine.  Not the end of the world, that has happened before.

  This morning, received an alert from a script that I coded to look for * delta * files on our data store.  A delta file has been abandoned here. We have to drive on this machine and the file only delta remained for one of these discs. Usually, all I have to do is create a new snapshot, delete all snapshots and everything returns to normal.  This time, the Delta stayed there.

  So I tried to create another snapshot option (with suspend it), as mentioned in the vmware.  He failed (Timed out).  Damn now I stuck out there for all of our disc delta files.  Tried again with the options suspend like 10 minutes after.  Works.  Delete all snapshots, works, but still stuck with these delta files.

  OK, the thing is all these 00000?-files delta does not appear to be used, as the modification date remained at the time of the snapshot.

  And also, the .vmx file doesn't seem to point to the delta files.  Then maybe I could safely remove?

  Here is some info.

  -------------------------------------

  LS - Flatr (sorted by modification date)

  / vmfs/volumes/5277f3fe-dc1ba57b-C0E6-1cc1de225128/Apps-Server1_4vtl6 # ls - Flatr

  -rw - 1 root root 602 2 December 2013 APPS - Server1_4vtl6_4.vmdk

  -rw - 1 root root 602 2 December 2013 APPS - Server1_4vtl6_3.vmdk

  -rw - 1 root root 602 2 December 2013 APPS - Server1_4vtl6_1.vmdk

  -rw - 1 root root 599 2 December 2013 APPS - Server1_4vtl6.vmdk

  drwxr-xr-t 1 root root 1400 December 2, 2013... /

  -rw - r - r - 1 root root 267858 December 2, 2013 vmware - 1.log

  -rw - r - r - 1 root root 367566 December 2, 2013 vmware - 2.log

  -rw - r - r - 1 root root 539395 Jan 14 14:58 vmware - 3.log

  -rw - 1 root root 8684 May 22 11:59 APPS - Server1_4vtl6.nvram

  -rw - r - r - 1 root root 3279104 30 mai 18:23 4.log - vmware

  -rw - 1 root root 602 30 mai 18:24 APPS - Server1_4vtl6_2.vmdk

  -rw - 1 root root 3865051136 30 mai 18:24 APPS-Server1_4vtl6 - e9c5721a.vswp

  -rw - r - r - 1 root root 273 30 mai 18:25 APPS - Server1_4vtl6.vmxf

  -rw - 1 root root 288 3 Jun 06:21 APPS-Server1_4vtl6_4 - 000002.vmdk

  -rw - 1 root root 45056 3 Jun 06:21 APPS-Server1_4vtl6_4-000002 - delta.vmdk

  -rw - 1 root root 422 3 Jun 12:00 APPS-Server1_4vtl6_3 - 000002.vmdk

  -rw - 1 root root 16822272 on 3 June 12:00 APPS-Server1_4vtl6_3-000002 - delta.vmdk

  -rw - 1 root root 422 3 Jun 12:00 APPS-Server1_4vtl6_2 - 000002.vmdk

  -rw - 1 root root 16850944 on 3 June 12:00 APPS-Server1_4vtl6_2-000002 - delta.vmdk

  -rw - 1 root root 422 3 Jun 12:00 APPS-Server1_4vtl6_1 - 000002.vmdk

  -rw - 1 root root 16822272 on 3 June 12:00 APPS-Server1_4vtl6_1-000002 - delta.vmdk

  -rw - 1 root root 417 3 Jun 12:00 APPS-Server1_4vtl6 - 000002.vmdk

  -rw - 1 root root 422 3 Jun 12:00 APPS-Server1_4vtl6_4 - 000003.vmdk

  -rw - 1 root root 16822272 on 3 June 12:00 APPS-Server1_4vtl6_4-000003 - delta.vmdk

  -rw - 1 root root 16904192 on 3 June 12:01 APPS-Server1_4vtl6-000002 - delta.vmdk

  -rw - 1 root root 3932672 on 3 June 12:01 APPS-Server1_4vtl6-000002 - ctk.vmdk

  -rw - r - r - 1 root root 13 on 3 June 13:59 APPS-Server1_4vtl6 - to the .xml

  -rw - r - r - 1 root root 45 3 Jun 14:00 APPS - Server1_4vtl6.vmsd

  -rw - 1 root root 1311232 on 3 June 14:00 APPS-Server1_4vtl6_1 - ctk.vmdk

  -rw - 1 root root 3932672 on 3 June 14:00 APPS-Server1_4vtl6 - ctk.vmdk

  -rw - 1 root root 1311232 on 3 June 14:00 APPS-Server1_4vtl6_4 - ctk.vmdk

  -rw - 1 root root 1311232 on 3 June 14:00 APPS-Server1_4vtl6_3 - ctk.vmdk

  -rw - 1 root root 2294272 on 3 June 14:00 APPS-Server1_4vtl6_2 - ctk.vmdk

  drwxr-xr-x 1 root root 5740 3 Jun 14:00. /

  -rwxr-xr-x 1 root root 3923 3 Jun 14:06 APPS - Server1_4vtl6.vmx *.

  -rw - r - r - 1 root root 2004374 3 Jun 17:53 vmware.log

  -rw - 1 root root 21474836480 3 Jun 17:54 APPS-Server1_4vtl6_3 - flat hard

  -rw - 1 root root 64424509440 3 Jun 17:55 APPS-Server1_4vtl6 - flat hard

  -rw - 1 root root 37580963840 3 Jun 17:56 APPS-Server1_4vtl6_2 - flat hard

  -rw - 1 root root 21474836480 3 Jun 17:56 APPS-Server1_4vtl6_1 - flat hard

  -rw - 1 root root 21474836480 3 Jun 17:56 APPS-Server1_4vtl6_4 - flat hard

  ---------------

  # cat APPS - Server1_4vtl6.vmx

  . Encoding = 'UTF-8 '.

  config.version = '8 '.

  virtualHW.version = "7".

  pciBridge0.present = 'TRUE '.

  pciBridge4.present = 'TRUE '.

  pciBridge4.virtualDev = "pcieRootPort"

  pciBridge4.functions = '8 '.

  pciBridge5.present = 'TRUE '.

  pciBridge5.virtualDev = "pcieRootPort"

  pciBridge5.functions = '8 '.

  pciBridge6.present = 'TRUE '.

  pciBridge6.virtualDev = "pcieRootPort"

  pciBridge6.functions = '8 '.

  pciBridge7.present = 'TRUE '.

  pciBridge7.virtualDev = "pcieRootPort"

  pciBridge7.functions = '8 '.

  vmci0. Present = 'TRUE '.

  NVRAM = "APPS - Server1_4vtl6.nvram.

  virtualHW.productCompatibility = "hosted".

  powerType.powerOff = 'soft '.

  powerType.powerOn = "hard."

  powerType.suspend = "hard."

  powerType.reset = 'soft '.

  displayName = "D-APP-Server1 - 2 k 8".

  extendedConfigFile = "APPS - Server1_4vtl6.vmxf.

  numvcpus = '2 '.

  scsi0. Present = 'TRUE '.

  scsi0.sharedBus = 'none '.

  scsi0.virtualDev = "lsisas1068".

  memsize = "4096".

  scsi0:0. Present = 'TRUE '.

  scsi0:0. FileName = "APPS - Server1_4vtl6.vmdk.

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

  scsi0:1.present = 'TRUE '.

  scsi0:1.filename = "APPS - Server1_4vtl6_1.vmdk.

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

  scsi0:2.present = 'TRUE '.

  scsi0:2.filename = "APPS - Server1_4vtl6_2.vmdk.

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

  scsi0:3.present = 'TRUE '.

  scsi0:3.filename = "APPS - Server1_4vtl6_3.vmdk.

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

  scsi0:4.present = 'TRUE '.

  scsi0:4.filename = "APPS - Server1_4vtl6_4.vmdk.

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

  IDE1:0. Present = 'TRUE '.

  IDE1:0. FileName = "".

  IDE1:0. DeviceType = "atapi cdrom.

  IDE1:0.startConnected = "FALSE".

  ethernet0. Present = 'TRUE '.

  ethernet0.virtualDev = "e1000".

  ethernet0.wakeOnPcktRcv = "FALSE".

  ethernet0.networkName = 'network of the Virtual Machine.

  ethernet0. AddressType = 'vpx.

  ethernet0.generatedAddress = "00:50:56:a9:6 has: 33»

  disc. EnableUUID = 'TRUE '.

  guestOS = "windows7srv-64.

  annotation = "Base of OMF Windows 2008 R2 EE server. | 0 a 4 cpu, 8 GB Mem"

  UUID. BIOS = ' 42 29 04 07 e8 52 5f - f5 02 ba da f1 78 cc e5 c5.

  VC. UUID = "50 29 4 c 34 2f fa 27 79 - 56 06 4 34 27 97 c6 a1.

  SCHED. CPU.min = '0 '.

  SCHED. CPU. Units = "mhz".

  SCHED. CPU.shares = 'normal '.

  sched.mem.MinSize = "410".

  SCHED.mem.shares = 'normal '.

  svga.vramSize = "33554432.

  vmci0.ID = "2026228965".

  tools.syncTime = "FALSE".

  UUID. Location = "56 4 d b5 3rd 5A d9 bc 70-65 30 52 f f2 1 d 2d 20.

  cleanShutdown = "FALSE".

  Replay.Supported = "FALSE".

  unity.wasCapable = "FALSE".

  sched.swap.derivedName = ' / vmfs/volumes/5277f3fe-dc1ba57b-c0e6-1cc1de225128/APPS-Server1_4vtl6/APPS-Server1_4vtl6-e9c5721a.vswp '.

  Replay.FileName = «»

  scsi0:0. Redo = «»

  scsi0:1.redo = «»

  scsi0:2.redo = «»

  scsi0:3.redo = «»

  scsi0:4.redo = «»

  pciBridge0.pciSlotNumber = "17".

  pciBridge4.pciSlotNumber = "21".

  pciBridge5.pciSlotNumber = "22".

  pciBridge6.pciSlotNumber = "23".

  pciBridge7.pciSlotNumber = "24".

  scsi0.pciSlotNumber = "160".

  ethernet0.pciSlotNumber = "32".

  vmci0.pciSlotNumber = "33".

  scsi0.sasWWID = "50 05 05 67 ba 52 50 e8.

  vmotion.checkpointFBSize = "33554432.

  hostCPUID.0 = "0000000b756e65476c65746e49656e69".

  hostCPUID.1 = "000206c200200800029ee3ffbfebfbff".

  hostCPUID.80000001 = "0000000000000000000000012c 100800.

  guestCPUID.0 = "0000000b756e65476c65746e49656e69".

  guestCPUID.1 = "000206c200010800829822030febfbff".

  guestCPUID.80000001 = "00000000000000000000000128100800".

  userCPUID.0 = "0000000b756e65476c65746e49656e69".

  userCPUID.1 = "000206c200200800029822030febfbff".

  userCPUID.80000001 = "00000000000000000000000128100800".

  evcCompatibilityMode = "FALSE".

  IDE1:0.clientDevice = 'TRUE '.

  scsi0:0.ctkEnabled = 'TRUE '.

  scsi0:1.ctkEnabled = 'TRUE '.

  scsi0:2.ctkEnabled = 'TRUE '.

  scsi0:3.ctkEnabled = 'TRUE '.

  scsi0:4.ctkEnabled = 'TRUE '.

  ctkEnabled = 'TRUE '.

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

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

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

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

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

  guest.commands.sharedSecretLogin.hostd - quiescedsnap = ""

  SCHED.scsi0:2.shares = 'normal '.

  SCHED.scsi0:2.throughputCap = 'off '.

  floppy0. Present = "FALSE".

  Thank you!!!

  Indeed, it looks like some files are orphans. If it is possible to turn off the virtual machine for a short period, I would say that you do this, then move the hard orphaned directory and power on the virtual machine again. If everything works, delete the subdirectory, including files. What I found useful is RVTools that reports these files as "Zombies".

  André

• Deleting a snapshot file # .vmsn

  I was looking through the data from one of my servers store and there's a snapshot # .vmsn file 27,36 KB in size. There is no snapshots in the Snapshot Manager. Is it save to delete this file? I'm under vCenter 5.0 with ESX 4.1.

  Thank you

  The files that you see with the-# extension are files capture instant delta. This means that this virtual machine is instant, if not nesessarily that they are running out of them. You can check by going on the settings of the virtual machine, choose the hard drive and see what VMDK he works out. In theory, he is likely to point to 00002, indicating that it is the active snapshot.

  If you are running on the snapshot, and you don't see the snapshots in snapshot Manager, a tip would be to create a new snapshot and then remove all the snapshots, once it's done. Just back up your Virtual Machine first, so you don't lose any data when it goes bad.

  It is important to clean these plates so that they do not start to fill in your data store. You can read more details here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1027887

• Do not take a snapshot - file already exists

  I'm taking a snapshot on a virtual computer and receive a "file already exists question."

  If I look at the structure of the computers folder virtual there are non - 0000.vmdk which I guess means there are no snapshots.

  However, I see a lot of vmsn files, probably 20 of them.

  NetBackup fails this virtual machine every night, that's how I picked up the snapshot cannot be created

  Help, please

  In my view, only the Delta file is the question. Durning an instant creation, that this file is created, after deleting this file should be gone.

  Then when it tries to create this file when snapshot, he sees already exist and so give the error "the file exists."

  Somehow this file gave me, but you can delete this file and all the files of vmsn.

  concerning

  Please allow points if you find this useful/correct

• help with the snapshot files orphans and ghettovcb on esxi3.5

  I'm trying to back up a single vm on my box esxi3.5 but ghettovcb guard complain that there is already a snashop

  
  

  None of them appear in the snashot Manager.

  I tried creating and deleting a snapshop using snapshot Manager, but these files persist and prevent the backup of this virtual ghettovcb machine.

  any help out there?

  should I remove?

  I'm under esxi3.5

  / vmfs/volumes/4af43c5b-3edb7050-7ec1-000e7feef085/SiteServer # ls-l
  -rw - 1 root root 16820736 29 August 08:13 siteserver-000001 - delta.vmdk
  -rw - 1 root root 229 29 August at 08:05 siteserver - 000001.vmdk
  -rw - 1 root root 16820736 29 August at 08:17 siteserver-000002 - delta.vmdk
  -rw - 1 root root 236 29 August 08:13 siteserver - 000002.vmdk
  -rw - 1 root root 16820736 29 August at 08:17 siteserver-000003 - delta.vmdk
  -rw - 1 root root 236 29 August at 08:17 siteserver - 000003.vmdk
  -rw - 1 root root 16820736 29 August at 08:20 siteserver-000004 - delta.vmdk
  -rw - 1 root root 262 29 August at 08:19 siteserver - 000004.vmdk
  -rw - 1 root root 419473920 29 August at 09:03 siteserver-000005 - delta.vmdk
  -rw - 1 root root 236 29 August at 08:59 siteserver - 000005.vmdk
  -rw - 1 root root 83929600 29 August at 09:24 siteserver-000006 - delta.vmdk
  -rw - 1 root root 262 29 August at 09:06 siteserver - 000006.vmdk
  -rw - 1 root root 16820736 29 August at 09:27 siteserver-000007 - delta.vmdk
  -rw - 1 root root 236 29 August at 09:24 siteserver - 000007.vmdk
  -rw - 1 root root 18915 29 August at 09:24 siteserver - Snapshot672.vmsn
  -rw - 1 root root 402653184 29 August at 08:59 siteserver - f7f25df0.vswp
  -rw - 1 root root 21484431360 29 August at 08:05 siteserver - flat hard
  -rw - 1 root root 8704 29 August at 08:59 siteserver.nvram
  -rw - 1 root root 403 29 August to 01:23 siteserver.vmdk
  -rw - 1 root root 847 29 August at 09:24 siteserver.vmsd
  -rwxr-xr-x 1 root root 1894-29 August at 09:24 siteserver.vmx
  -rw - 1 root root 265 June 3, 2010 siteserver.vmxf
  -rw - r - r - 1 root root 136146 29 August at 08:47 vmware - 0.log
  -rw - r - r - 1 root root 22071 Aug 4 12:54 vmware - 1.log
  -rw - r - r - 1 root root 17245 25 July 00:54 vmware - 2.log
  -rw - r - r - 1 root root 16997 25 July 00:49 vmware - 3.log
  -rw - r - r - 1 root root 0 25 July 00:45 vmware - 4.log

  
  -rw - r - r - 1 root root 16712 25 July 00:42 vmware - 5.log
  -rw - r - r - 1 root root 58064 29 August at 09:25 vmware.log

  Yes. The reason why you need to take another cliché is only in order to activate the clear all"" button. Because we don't need the memory, you can take the snapshot without it.

  André