Vmware server consolidating disks

The first thing was to find the host where the machine was located and that was doing the removal of the snapshot, so I logged in to the ESXi host using SSH, and running th following command: ~ # vim-cmd vimsvc/task_list (Managed Object Reference) [ 'vim. * I would strongly advise against using snapshot for more then 1-3 days and that grows to this size.

vmware server consolidating disks-73

When you take a snapshot of a hard drive a new set of files are created.

The new file holds any new or changed blocks and the old descriptor file is updated No Snapshot Before a snapshot is created, the VM configuration file (“name”.vmx) contains (among many other things) a line referencing the hard drive descriptor file:ide0:0Name = “Kyle A.vmdk”At this point the “name”is essentially blank The original “name”hard drive descriptor file contains (among other things) two lines referencing the ID of the drive (note the ID is unique only for snapshots – all master disks are fffffffe) as well as a line referencing the binary “-flat” file for this drive.

To monitor the VMDK snapshot and base disks which are currently being updated, run this watch command: Note: sesparse disks will be present from ESXi 5.5 if the size of the Virtual Disk is more than 2 TB. By default, the watch command is updated every 2 seconds.

where: -d highlights the differences between successive updates. l shows a long listing which displays additional file information. Now, the above watch command that we saw is the most commonly used method.

You see the read and the delta files touch time, but the time stamps of the RDM pointer file are not updated. Navigate to the Virtual Machine directory containing the virtual disks associated with the Virtual Machine that is being consolidated.

If you have any VM_NAME-00000#or VM_NAME-00000#files within the directory, that means that the Virtual Machine has snapshots associated with it at this time.They had shutdown a Virtual Machine because it had a huge snapshot ~1.7 TB, and afterwards they had initiated the remove snapshot task. So quick calculation says that this will take 20 hours, and they could not wait that long too power on the machine again, so we had to do something. Host System.acquire Cim Services Ticket-268543629' An error was received from the ESX host while powering on VM SERVER01. The system cannot find the file specified /vmfs/volumes//Datastore1/SERVER01/SERVER01_1-rw——- 1 root root 494 Dec 17 2013 /vmfs/volumes//Datastore1/SERVER01/SERVER01_1-rw——- 1 root root 1000.0G Dec 17 /vmfs/volumes//Datastore1/SERVER01/SERVER01_1-000001-rw——- 1 root root 494 Nov 22 /vmfs/volumes//Datastore1/SERVER01/SERVER01_1-000001-rw——- 1 root root 522.1G Dec 17 /vmfs/volumes//Datastore1/SERVER01/SERVER01_2-rw——- 1 root root 494 Dec 17 2013 /vmfs/volumes//Datastore1/SERVER01/SERVER01_2-rw——- 1 root root 617.8G Dec 17 /vmfs/volumes//Datastore1/SERVER01/SERVER01_1-000001-rw——- 1 root root 494 Nov 22 /vmfs/volumes//Datastore1/SERVER01/SERVER01_1-000001-rw——- 1 root root 1000.0G Dec 17 /vmfs/volumes//Datastore1/SERVER01/SERVER01_3-rw——- 1 root root 494 Dec 17 2013 /vmfs/volumes//Datastore1/SERVER01/SERVER01_3-rw——- 1 root root 567.3G Dec 17 /vmfs/volumes//Datastore1/SERVER01/SERVER01_1-000001-rw——- 1 root root 494 Nov 22 /vmfs/volumes//Datastore1/SERVER01/SERVER01_1-000001Afterward I could power on the machine without any problems, and then initiate a Consolidate Snapshots, to delete the remaining snapshot, will the machine is running.But you can't cancel the task from the v Sphere Client. This procedure can de diffent if there is multiple snapshots on the Virtual Machine.Snap descriptor .vmdk: CID=fffffffe parent CID=fffffffe parent File Name Hint=”Kyle A.vmdk” # Extent description RW 41943040 VMFSSPARSE “Kyle A-000001-delta.vmdk”The end result is the points to the descriptor file of the VMDK to be written to.If that is a snapshot then it in turn references the next file “up” the snapshot tree.CID=fffffffe parent CID=ffffffff # Extent description RW 41943040 VMFS “Kyle A-flat.vmdk”One snapshot When a snapshot is taken, the configuration file (“name”.vmx) gets updated with the name of the current snapshotide0:0Name = “Kyle A-000001.vmdk”The snapshot descriptor file gets updated with (among other things) the name of the associated file which includes the state of RAM, CPU and VMX.snapshot0.filename = “Kyle A-Snapshot2.vmsn”The original “name”is left unchanged (see above)A snapshot binary is created as “name”-000001(note the name change from “-flat”) The descriptor file “name”-000001is created with a line referencing the “delta” binary file plus a new ID.

Tags: , ,