Skip to main content

VMware Workstation pro 16.1

Thread solved

Hi Echantech

I have VMware Workstation 16.1 pro installed on my laptop and also saved the VMs (working directory) on C:, so that the virtual machines are backed up when I create an image of the system.

But now someone warned me that this would not work with True Image.

Is that true? Do you have any experience with it?

With the request for help and with best regards,
wisch

0 Users found this helpful

Wisch, I use VMware Player 16 on my own laptop and have multiple different VM's that I use but after initially using ATI to backup my VM's, I quickly came to the conclusion that this was wasting a lot of my time!

I store my VM's on a second disk in a separate partition well away from my C: drive so that it has no impact on my regular OS backup tasks.  My VM's currently add up to around 530GB in size, so having them on C: would either require that I exclude the files / folders or else cause my OS backups to be increased by this size!

The approach I use is to use a synchronisation program to mirror any changes to my D:\VMware folder where all my VM's are stored to an external USB 3.0 HDD drive, and run the program after each time I have been using a VM, when I am happy that all was good!  If I have had any issues with the VM, I keep the option to delete the local copy and copy back the VM data from the external drive.

Using the sync program saves Acronis from trying to compress the VM files and store them in .tib file format.

Hi Steve

Ok, then I'll do it that way, thank you very much!
It actually seems that TI is struggling with the already compressed VMs.

Best regards,
wisch

Wisch,

I can echo Steve's comments.  I also store VM on locations that away from C:.  I prefer to maintain a very lean OS installation therefore, I keep most data on disks other than C:.

Attempting to use TI to backup already compressed data will bog down the app as it attempts to further compress such data but rarely can and because compressed data is usually large in size this ends up being a slow futile process as it appears you have found out.

I take the same approach - VMs on a separate 1TB M.2 drive.

Ian