2022-10-19, 22:21:05
Vimalin for Fusion 2.6.587 update
This is an update release that also has a few important bug fixes for Fusion 12.2
https://www.vimalin.com/download/Vimalin-2.6.587.dmg
(or use the Vimalin -> "Check for Updates" menu option)
Please note that the update recommendation is to first uninstall your existing Vimalin application by dragging it to the Trash (or for our English users, drag it to the Bin).
Only after the old Vimalin is uninstalled run the installer to update to Vimalin 2.6.587.
Here's the list of changes since version 2.6.560:
General fixes
Known Issues
More information about Vimalin is available at the main website: https://www.vimalin.com
This is an update release that also has a few important bug fixes for Fusion 12.2
https://www.vimalin.com/download/Vimalin-2.6.587.dmg
(or use the Vimalin -> "Check for Updates" menu option)
Please note that the update recommendation is to first uninstall your existing Vimalin application by dragging it to the Trash (or for our English users, drag it to the Bin).
Only after the old Vimalin is uninstalled run the installer to update to Vimalin 2.6.587.
Here's the list of changes since version 2.6.560:
General fixes
- Tweak on vmsd lock file cleanup to wait 3 seconds after creating a snapshot. This helps when you have a very fast disk. Also added an exception handler in case an error happens during the delete, so we don't get a crash, but a nice report instead.
- Improved error logging and exception handling when hashing files and copying them.
- If a scheduled VM backup has been missed by more than 3 hours then the scheduler logic will check if that the machine has been recently sleeping / was shut down. In that case it will sleep for 90 seconds before doing anything else. That should be plenty of time for the network to be ready and not automatically fail the backup attempt, because it could not contact the network backup location.
- If you have 2 VM backups scheduled at the same time and they run after one another then there’s a 21 second delay between them. This is to anticipate with network connections where Vimalin uses the autoconnect logic. IOW, when the network connection is not yet setup, it will connect before the backup and disconnect after the backup. A disconnect can take up to 20 seconds or so and we’ve seen logs where the next backup was under the impression that the disk was connected, but it was still disconnecting. Delaying that should give the machine enough chance to complete the disconnect and run another autoconnect.
- Improved exception handling around sending emails.
- Improved text on Full Disk Access popup to provide better guidance for configuring these settings.
- Added guest OS's from the Fusion Tech Preview, such as Windows 11. However this also includes all the new guest OS's on Apple Silicon.
- If you compress and then decompress a VM, the file ownership ends up being set to root. This then causes problems during restore. On restore we now set the user ownership of each individual file.
- Deleting a VM from the library would leave an empty folder if the VM was running during the backup as the snapshot folder was not correctly removed. This has been fixed.
- When the demo expires the "demo expired" message would overflow the text area. The text has been shortened and the rest of the info has moved to a tooltip.
Known Issues
- If you use Windows 11 with vTPM (or normally encrypted) you cannot make backups when the VM is running. See here for more information.
- No official Apple Silicon support, although it has been reported to work fine.
More information about Vimalin is available at the main website: https://www.vimalin.com