Vimalin & Vimarun Community Forums

Vimalin - automated Virtual Machine backups for VMware Fusion, Workstation and Player

Vimarun - run VMware Virtual Machines automatically

You are not logged in.

#1 2020-08-10 15:19:51

wila
Administrator
Registered: 2016-10-14
Posts: 82

Vimalin for Fusion 2.5.459 update

Vimalin for Fusion 2.5.459 update

You can download the update from the following url:

https://www.vimalin.com/download/Vimalin-2.5.459.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.5.459

Here's the list of changes since version 2.5.432:

General changes

  • Support for macOS Big Sur as host OS has been added.

  • Vimalin now uses the  hardened runtime and application entitlements as requested by macOS notarization requirements.

  • Replaced old context menu logic with more natural functioning context menu's.

  • VM's that have a non local disk now also log the details about what disk was non local to aide with troubleshooting.

  • Uninstaller, remove the GUI logs when running a complete uninstall via the uninstall application ("~/Library/Logs/Vimalin") and remove a few other empty folders (contents was already removed)

Added new guest OS support for:

  • macOS Big Sur,

  • CentOS 8

New screen: "Process Queue"
This allows you to see each task that still is in the process queue. You can also delete tasks if needed.

Backup Jobs:

  • When using the "Backup Now" button, the backup job immediately gets validated and if it cannot run then you will get a message about that in the user interface. Previously the error would only show up in the log and you would have to go "hunt and peck" for why the backup did not run.

Backup Target:

  • There was a parsing issue with shares using a particular naming scheme (containing parenthesis in the volume name "()"). As a result the file system of this kind of disk was not correctly detected and you could not set it as a backup target. This has been fixed.

  • Setting a backup target to an existing backup target will offer to import existing VMs. Not all of the existing VMs would be detected, this has now been fixed.

Backup Archive:

  • The "Get Info" screen was displaying the actual VM bundle size for "Total Size" instead of Processed Size. This means that for incomplete backups it would show the wrong total count. Fixed.

Register License:

  • When registering a license it would display a nice checkmark for when you correctly enter a new license, but it wouldn't replace the "demo license nn days" with "registered", so it could be confusing to see if the license registered correctly or not. Fixed.

Offline

Board footer

Powered by FluxBB