I have sometimes done this with Linux VM's that I use for local development.
Usually, the VM disk images are some where between the need to backup Applications and configuration files, and not as important my work and data files.
The problem with VM's is not just the quantity of data that needs to be backed up, but the overall size of the data that needs to be evaluated. I think that CrashPlan does a pretty good job of just coping the changed data of the disk image, but it has to do a HUGE amount of processing with every backup. Therefore VM's are hard to fit in with the remote versioned backups of CrashPlan and Arq.
I do backup these up via Carbon Copy Clone when I mirror the entire drive.
Usually, the VM disk images are some where between the need to backup Applications and configuration files, and not as important my work and data files.
The problem with VM's is not just the quantity of data that needs to be backed up, but the overall size of the data that needs to be evaluated. I think that CrashPlan does a pretty good job of just coping the changed data of the disk image, but it has to do a HUGE amount of processing with every backup. Therefore VM's are hard to fit in with the remote versioned backups of CrashPlan and Arq.
I do backup these up via Carbon Copy Clone when I mirror the entire drive.