Knowledgebase: Tips and tricks
Backup2Go and Virtual Machine Image Files
Posted by Sven Koester, Last modified by Andre Kuehnemund on 10 May 2011 11:10
When Backup2Go is used to save workstations which hold virtual machines like VMWare to run a second operating system, care must be taken when saving the guest image.

These images are often big files, representing the guest operating system including its memory. These big files change when the guest is running.
As a result, file based backup mechanisms like Backup2Go will save that file again.

Assuming this is a 40 GB file saved twice a day, this will result in one week in 2 * 7 * 40 GB = 560 GB space in the Backup2Go repository only to save the instances of this one file. This may unexpectedly fill up the limited capacity of a disk storage. 

To avoid that, several virtual machine implementation allow for storing the guest image in a disk structure consisting of several smaller files/chunks. As only a few of the chunks change when the guest OS is executed, this dramatically reduces the effect.

In case that is not possible, it may make sense to exclude that container file from the backup.


(16 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name:
CAPTCHA Verification 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).