Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UTM VM's not backed up by Time Machine #6474

Closed
romlu2024 opened this issue Jul 13, 2024 · 6 comments
Closed

UTM VM's not backed up by Time Machine #6474

romlu2024 opened this issue Jul 13, 2024 · 6 comments

Comments

@romlu2024
Copy link

romlu2024 commented Jul 13, 2024

Describe the issue
I rely on Apple's built-in Time Machine for my backups and recently noticed due to a VM corruption that I was not able to recover the VM from the backups. Instead of having a recent backup, I only had the backup of the initial VM setup. In fact, when running a VM in UTM and closing it, UTM does not modify the time stamp and therefore Time machine does not backup the changed VM.

This happens for VM's stored in the default location and for VM's moved in a custom location.

Configuration

  • UTM Version: 4.5.3
  • macOS Version: macOS Sonoma 14.5
  • Mac Chip (Intel, M1, ...): Apple Silicon M1
@osy
Copy link
Contributor

osy commented Jul 14, 2024

I think this is an issue with Time Machine. Did you exclude ~/Library or anything by chance?

@romlu2024
Copy link
Author

romlu2024 commented Jul 14, 2024

No, nothing is excluded.

As I mentioned in the initial post, even the VM's that are moved through the "Move" feature in UTM to a custom location are not backed up.

When I modify files and folders in the VM and then shutdown Wndows and stop UTM, the date of the VM bundle is not changed and the modification date of the qcow2 files are not changed as well.

image

@osy
Copy link
Contributor

osy commented Aug 21, 2024

I just tested this and indeed the bundle modified date did not change but the qcow2 file did change modified date. Can you post the output of https://eclecticlight.co/2018/05/31/new-version-of-the-time-machine-mechanic-t2m2/

@romlu2024
Copy link
Author

Hi osy, please find attached the log files.

I think I was confused about the time stamp of the bundle while creating the bug report. I now took a test VM, backup the VM with TM and restored the whole VM.

In fact, it gets restored but the time stamp of the bundle is still showing a very old date (date of creation of VM). When you browse the TM history, you always see the same date (when the VM was created). You never see an updated date and time.

Maybe this confused me.

In TM history, the date should change each time the VM gets backup'ed up when powered on previously.

TM-Logs.txt

@osy
Copy link
Contributor

osy commented Aug 22, 2024

I think the bundle timestamp doesn't change but the files inside of it does. And that does get backed up right?

@romlu2024
Copy link
Author

romlu2024 commented Aug 22, 2024

Yes, during my latest test, the modified files inside the bundle got backup'ed and I could restore the changed VM. As I mentioned in my previous post, the VM date shown in the TM history does not change and shows always the date of the VM creation. This is something that you should fix so that the bundle date is the date of the last powered on date and time (VMware Fusion does the same)

@osy osy closed this as completed in 14c2494 Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants