Systems and methods for compacting a virtual machine file
View Patent ↗Systems and methods for compacting a virtual machine file are presented. In one example, the system accesses a source virtual machine file associated with a guest file system. The system creates a destination virtual machine file based on the guest file system and initializes a block allocation table of the destination virtual machine file. The system accesses a block allocation table of the source virtual machine file and, for each block of the source virtual machine file, determines whether the block is in use. If so, the system copies the block to the destination virtual machine file and updates the block allocation table of the destination virtual machine file. If not, the system does not copy the block or update the block allocation table of the destination virtual machine file, thereby reducing the destination virtual machine file's size compared to the source virtual machine file's size.
1. A method performed by a physical computer system for compacting a virtual machine file, the method comprising:
under control of a physical computer system configured for use with virtual machines associated with virtual machine files:
accessing a source virtual machine file associated with a guest file system;
determining the guest file system associated with the source virtual machine file;
creating a destination virtual machine file based on the guest file system;
initializing a block allocation table of the destination virtual machine file;
accessing a block allocation table of the source virtual machine file and for each block of the source virtual machine file identified in the block allocation table of the source virtual machine file:
determining whether the block includes data that is not marked for deletion from the source virtual machine file;
in response to determining that the block includes data that is not marked for deletion from the source virtual machine file, copying the block to the destination virtual machine file and updating the block allocation table of the destination virtual machine file; and
in response to determining either that the block does not include data or that the block includes data which is marked for deletion from the source virtual machine file, not copying the block and not updating the block allocation table of the destination virtual machine file, thereby reducing a size of the destination virtual machine file compared to a size of the source virtual machine file.
2. The method of claim 1 , further comprising copying a file header of the source virtual machine file to the destination virtual machine file.
3. The method of claim 1 , further comprising copying a file footer of the source virtual machine file to the destination virtual machine file.
4. The method of claim 1 , wherein determining whether the block is in use comprises:
accessing a logical cluster number bitmap of the source virtual machine file;
identifying one or more clusters associated with the block; and
using the logical cluster number bitmap to determine whether at least one of the one or more clusters is in use.
5. The method of claim 1 , further comprising copying metadata associated with the source virtual machine file to the destination virtual machine file.
6. The method of claim 5 , further comprising updating the metadata associated with the destination virtual machine file based on the blocks copied from the source virtual machine file to the destination virtual machine file.
7. The method of claim 1 , further comprising:
determining the size of the source virtual machine file prior to creating the destination virtual machine file; and
in response to determining that the size of the source virtual machine file satisfies a threshold, creating the destination virtual machine file.
8. The method of claim 7 , wherein determining that the size of the source virtual machine file satisfies the threshold further comprises determining that the size of the source virtual machine file exceeds a threshold size.
9. The method of claim 1 , further comprising:
determining a percentage of blocks not in use prior to creating the destination virtual machine file; and
in response to determining that the percentage of blocks not in use satisfies a threshold, creating the destination virtual machine file.
10. The method of claim 9 , wherein determining that the percentage of blocks not in use satisfies the threshold further comprises determining that the percentage of blocks not in use exceeds a threshold percentage.
11. The method of claim 1 , wherein an initial size of the destination virtual machine file is less than the size of the source virtual machine file.
12. The method of claim 1 , wherein the source virtual machine file comprises a dynamic virtual machine file.
13. The method of claim 1 , wherein the destination virtual machine file comprises a dynamic virtual machine file.
14. The method of claim 1 , wherein determining whether the block is in use comprises determining whether the block is in use based, at least in part, on the block allocation table.
15. The method of claim 1 , further comprising deactivating a source virtual machine associated with the source virtual machine file prior to accessing the source virtual machine file.
16. A system for compacting a virtual machine file, the system comprising a physical computing system configured to:
access a source virtual machine file associated with a guest file system;
create a destination virtual machine file based on the guest file system;
initialize a block allocation table of the destination virtual machine file;
access a block allocation table of the source virtual machine file and for each block of the source virtual machine file identified in the block allocation table of the source virtual machine file:
determine whether the block includes data that is not marked for deletion from the source virtual machine file;
in response to determining that the block includes data that is not marked for deletion from the source virtual machine file, copy the block to the destination virtual machine file and update the block allocation table of the destination virtual machine file; and
in response to determining either that the block does not include data or that the block includes data which is marked for deletion from the source virtual machine file, refrain from copying the block and refrain from updating the block allocation table of the destination virtual machine file, thereby reducing a size of the destination virtual machine file compared to a size of the source virtual machine file.
17. The system of claim 16 , wherein the physical computing system is further configured to determine the guest file system associated with the source virtual machine file.
18. The system of claim 16 , wherein the physical computing system is further configured to copy a file header of the source virtual machine file to the destination virtual machine file.
19. The system of claim 16 , wherein the physical computing system is further configured to copy a file footer of the source virtual machine file to the destination virtual machine file.
20. The system of claim 16 , wherein determining whether the block is in use comprises:
accessing a logical cluster number bitmap of the source virtual machine file;
identifying one or more clusters associated with the block; and
using the logical cluster number bitmap to determine whether at least one of the one or more clusters is in use.
21. The system of claim 16 , wherein the physical computing system is further configured to copy metadata associated with the source virtual machine file to the destination virtual machine file.
22. The system of claim 21 , wherein the physical computing system is further configured to update the metadata associated with the destination virtual machine file based on the blocks copied from the source virtual machine file to the destination virtual machine file.
23. The system of claim 16 , wherein the physical computing system is further configured to:
determine the size of the source virtual machine file prior to creating the destination virtual machine file; and
in response to determining that the size of the source virtual machine file satisfies a threshold, create the destination virtual machine file.
24. The system of claim 16 , wherein the physical computing system is further configured to:
determine a percentage of blocks not in use prior to creating the destination virtual machine file; and
in response to determining that the percentage of blocks not in use satisfies a threshold, create the destination virtual machine file.
25. A system for compacting a virtual machine file, the system comprising:
a physical host server comprising a virtualization layer configured to support a parent partition and one or more child partitions, the parent partition comprising a virtual machine management system and a compactor, the one or more child partitions each comprising a virtual machine associated with a guest operating system and one or more applications;
a data store comprising one or more virtual machine files configured to be accessed by the one or more child partitions; and
the compactor configured to:
access, from the data store, a source virtual machine file comprising a dynamic virtual machine file and a guest file system;
create a destination virtual machine file based, at least in part, on the guest file system, the destination virtual machine file comprising a dynamic virtual machine file;
initialize a block allocation table of the destination virtual machine file;
access a block allocation table of the source virtual machine file and for each block of the source virtual machine file identified in the block allocation table of the source virtual machine file:
determining whether the block includes data that is not marked for deletion from the source virtual machine file;
in response to determining that the block includes data that is not marked for deletion from the source virtual machine file, causing the block to be copied to the destination virtual machine file and updating the block allocation table of the destination virtual machine file; and
in response to determining either that the block does not include data or that the block includes data which is marked for deletion from the source virtual machine file, not causing the block to be copied and not updating the block allocation table of the destination virtual machine file thereby reducing a size of the destination virtual machine file compared to a size of the source virtual machine file.
26. The system of claim 25 , wherein the compactor is further configured to determine the guest file system associated with the source virtual machine file.
27. The system of claim 25 , further comprising a duplicator configured to copy a block to the destination virtual machine file in response to the compactor determining that the block is in use.
28. The system of claim 25 , wherein each of the one or more applications access resources of the host server via a hypervisor.
29. The system of claim 25 , wherein each of the one or more applications access resources of the host server via a virtual machine management system.
30. Non-transitory computer storage configured to store executable instructions that when executed by a processor cause the processor to:
access a source virtual machine file comprising a dynamic virtual machine file associated with a guest file system;
determine the guest file system associated with the source virtual machine file;
create a destination virtual machine file based on the guest file system, the destination virtual machine file comprising a dynamic virtual machine file;
initialize a block allocation table of the destination virtual machine file;
access a block allocation table of the source virtual machine file and for each block of the source virtual machine file identified in the block allocation table of the source virtual machine file:
determine whether the block includes data that is not marked for deletion from the source virtual machine file;
in response to determining that the block includes data that is not marked for deletion from the source virtual machine file, copy the block to the destination virtual machine file and update the block allocation table of the destination virtual machine file; and
in response to determining either that the block does not include data or that the block includes data which is marked for deletion from the source virtual machine file, not copy the block and not update the block allocation table of the destination virtual machine file thereby reducing a size of the destination virtual machine file compared to a size of the source virtual machine file.