Vimalin Changelog

What's new in Vimalin 2.6.560

Nov 18, 2021
  • New:
  • Support for VMware Fusion 12.2.x
  • General fixes:
  • Fixed an issue with backup of a running VM and restoring it in running state. In Fusion 12.2 there are some small changes to the .vmx that caused this process to misbehave. Fusion would report that the .vmx file is corrupted when trying to open the restored VM. This is now fixed.
  • We're now adding an embedded info.plist to the vimalinWorker binary in an attempt to resolve the security issues requiring Full Disk Access requirements for vimalinWorker. Sadly this does not make any difference, the issue on this is exactly as it was. Our resolve for the moment is an extension to the error message that points to the FAQ section at our website.
  • Backup Archive:
  • Context menu option "Add Notes..." now changes the text into "Edit Notes..." once you have added some notes.
  • 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.

New in Vimalin 2.6.542 (May 7, 2021)

  • This release has a few bug fixes, several improvements on the user interface and improves the ability to look over the logs made by Vimalin.

New in Vimalin 2.6.517 (Jan 8, 2021)

  • General fixes:
  • Fixed a bug where a backup would fail because the previous backup of that same VM was interrupted.
  • The interrupted backup ended up leaving a backup snapshot. On start of the new backup the old snapshot backup is removed before creating a new backup snapshot, but the filelist was not refreshed. This would cause the 2nd backup to fail as well.
  • If your backup failed due to lack of free disk space, it would still create an empty folder at the backup target. Deleting the failed backup did not remove the empty folder. Fixed.
  • In the last version we already changed file checking logic about specific log files as it triggered false warnings, because the log files still change while they are being copied (which is fine for log files). Turns out there are more log files (d'oh), so this changed logic now applies for all .log files thereby curing a lot of failed backups due to the "could not copy all files" error.
  • Backup Archive:
  • Defined the Delete key as short cut key for deleting a VM.
  • Introduced search logic. You can search the list of VMs for patterns in VM name and back target. The search is case insensitive.
  • Any column is now sortable by clicking on the header. You can sort ascending or descending and the rest of the list will adjust to the selected sort.
  • Backup Archive Details:
  • The list of files is now sorted by file name.
  • Activity Log:
  • Fixed an optimisation that caused the log not to reload on opening the screen the 2nd time. You had to change from normal view to detailed view to force a reload.
  • Improved logging details by quite a bit, by providing more exact details on why something went wrong. Eg. if not enough space, then tell how much free space was actually needed. Another example would be that if file size of the copied file is different then state the details. Basically the logging logic has been overhauled, so that you less often have to go down to the text only logs in order to figure out the reason for a problem.

New in Vimalin 2.5.481 (Sep 29, 2020)

  • This update adds support for the most recent versions of VMware Fusion, VMware Workstation & VMware Player.

New in Vimalin 2.5.474 (Sep 14, 2020)

  • General changes:
  • All the main screens of Vimalin can now be resized by the user. The size set by the user is remembered for the next time you run the application.
  • Backup Target:
  • Trying to import a VM that was deleted from the Backup Archive without the backup target attached did not work. In other words, the backup was deleted from the database, but not on disk.
  • When importing VMs it now also import the duration for how long it took to make the backup.
  • Backup Archive:
  • The archive grid now also has a size column.
  • Backup Archive Details:
  • Shows TotalSize correctly when the VM is imported.

New in Vimalin 2.5.459 (Sep 9, 2020)

  • General changes:
  • Update to latest OpenSSL library 1.0.2u
  • VM's that have a non local disk now also log the details about what disk was non local to aide with troubleshooting.
  • Added new guest OS support for:
  • 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" in order to find out why the backup did not run.
  • Backup Target:
  • 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.