Time Machine not backing up my vmWare image file


Recommended Posts

So, I have a vmWare Fusion install and the image file is saved in "~/vmWare/Windows XP Professional SP3.vmwarevm". For some reason, Time Machine does not back up this file. Could it be due to the single 6GB size of the file? My Time Machine drive is formatted HFS like it should be for TM.

Thoughts?

It's a bugfix in a previous version of VMWare Fusion. Basically, because time machine backs up only files that have changed, if you boot up and do something on your virtual machine it's got to re-backup the entire Virtual Machine hard drive.

So if you say you're working on a virtual machine for six hours and time machine is setup to backup every hour, now lets say that the Virtual Disk is about 10GB, that means over six hours you've backed up 60GB of data.

Thats why it wont backup VMWare discs. Use VMWares built in Snapshots instead.

It's a bugfix in a previous version of VMWare Fusion. Basically, because time machine backs up only files that have changed, if you boot up and do something on your virtual machine it's got to re-backup the entire Virtual Machine hard drive.

So if you say you're working on a virtual machine for six hours and time machine is setup to backup every hour, now lets say that the Virtual Disk is about 10GB, that means over six hours you've backed up 60GB of data.

Thats why it wont backup VMWare discs. Use VMWares built in Snapshots instead.

bollocks, I theorized about that but I was hoping it wasn't the reason

Just make sure your Fusion is up to date; the fix for the problem Vegetunks describes has been resolved in version 1.1.2. The newest version at this time is 1.1.3. You could also run Fusion 2.0 rc1 but that's a work in progress so you might experience some stability issues (though Fusion beta's and rc's are very stable).

Release notes for 1.1, 1.1.1, 1.1.2 and 1.1.3 can be found here.

Also make sure the directory your vm's are in is not on the Time Machine exclusion list.

So, I updated to 1.1.3 and now it's backing up my image file. However, after reading Vegetunks' initial reply, I don't know if I want it to take a snapshot after every boot of the VM, as it will now create a big fat 8GB footprint over and over. For now, it's good to know that I can back it up if needed, for now I will put that directory in my exclude list.

Thanks for the help everyone, this is just another gentle reminder of why I love this forum.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I literally tried to install it on my PC today and it crashed upon every start up. I tried all the tricks, terminate and remove cache, uninstall, reinstall, reboot, install via winget.. in the end I had my call with Brad Wardell on Google Meet. Oh I also tried Teams on the web, and got no video or audio (yes I allowed mic and camera).
    • Microsoft explains how it made Teams so much faster in 2026 by Usama Jawad Microsoft Teams is Redmond's flagship online communication and collaboration tool, primarily used in enterprise, government, and school environments. It regularly receives updates, with Microsoft frequently revealing features currently in development as well, such as Efficiency Mode and a dedicated app for meeting recaps. Now, the company has shed some light on the backend enhancements it has made to its popular software in 2026. During the first half of 2026, switching between chats has become 20% faster on desktop and web, which is especially great for less powerful devices or hardware on weak networks. Microsoft explains that it tracks two types of chat switches. The first is a warm switch, which relates to returning to a recent chat, in which case it is most likely already present in memory and should load extremely fast. The other is a cold switch where a chat that hasn't been opened recently is now opened. Naturally, the second type of chat switch was causing the most notable latency spikes. Microsoft realized that this was happening because of three reasons. First, the query to fetch conversation data was being fired too late. Next, queries were being sent sequentially, increasing the overall round-trip time. Finally, there was no handling of response priority, which meant that non-critical responses would sometimes block the main thread. Microsoft solved all of these problems by firing the data query immediately, bundling queries to be sent together so that they wouldn't create a "waterfall" effect, and enabling faster painting of the frame. As a result, warm and cold switches now have almost the same latency, and the only distinguishable difference between them is due to the data layer response time. Next, Microsoft focused on reducing app hangs and freezes on macOS and iOS by 35%. On macOS, the company has a health monitor thread running in the background that does exactly what it says on the tin. The tech firm built a dedicated StackDecoder tool to analyze health monitor's output at scale. Through this combination, it decided to move several error reporting and monitoring threads either to the background or treated them as an asynchronous call so that they wouldn't block the main thread, causing Teams to freeze. On iOS, the same result was accomplished through optimization of computations, caching, offloading operations from the main thread, refactoring database access behaviors, deferring non-critical tasks, and more. On a related note, it also made people search 25% on iOS by optimizing the query pipeline, and efficient database task queuing and scheduling. However, Microsoft has emphasized that improving Teams' performance is an ongoing endeavor, and that it hopes that these efforts will continue to make the software a reliable partner in online communication scenarios. On a related note, Microsoft recently unveiled some upcoming performance upgrades for OneDrive on macOS too, and you can check those out here.
  • Recent Achievements

    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
    • First Post
      X-No-file earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      520
    2. 2
      PsYcHoKiLLa
      210
    3. 3
      +Edouard
      147
    4. 4
      Steven P.
      96
    5. 5
      ATLien_0
      84
  • Tell a friend

    Love Neowin? Tell a friend!