Known Issues in Backup

Major Issues (these are going to be addressed with high priority)
  • Fixed - to the best of my knowledge! Restore of an entire disk was not always working. For a backup application this is a major issue of course. So far I tested a restore with a Windows 8.1 Pro system and did not succeed, and with a Windows 10 Pro system where it took the system two reboots and after that the system was working. At present I do not recommend to use the restore functionality without doing your own tests. However the backup part is definitely working as tests indicate (see also Restoring files, Verification & Validation). As described there, you can also mount the images and run virtual machines with that. Or in other words: your files are safe, but you may have to reinstall the system by other means if the system really crashes.

Lindenberg Software Backup limitations on Windows 7 / Windows Server 2008 / Windows Home Server

  • On these operating systems the Virtual Disk API does not support all the features required by the backup service and thus the option to run a backup service is not available in the configuration UI. On the same operating systems and also because of limited operating system support for virtual disks plus lack of support of Server Message Block 3.0 encryption, the "Mount" button is not supported. Otherwise they are supported as clients.

Minor Issues (these are likely to be addressed depending on user's needs. Some are just noteworthy and not really bugs)

  • Systems using Instant Go (formerly known as Connected Standby, and also called Modern Standby in Microsofts documentation) may go to sleep state during backups, especially when running on battery. I am looking into this issue in order to find a resolution.
  • Occassionally Windows Task Scheduler may not start the backup at the configured point in time but later. The exact situations are probably only known to Microsoft, but usually it happens on battery if the battery is already low and there is a great risk that backup would not succeed anyway.
  • There is no support for multiple configurations on the client, e.g. for different disks or different servers
  • There is no integrated means to pause a backup schedule during e.g. vaccation
  • Backup remembers the sector size of your disk only if you use .vhdx as the backup image format. It also does not yet verify the target disk on restore is using the same sector size. Fortunately most disks and in particular SSDs are sector size 512 bytes even though some of them use 4KB sectors physically, but unfortunately the sector size does matter. If you backup a 4KB sector size disk to .vhd, you will not be able to mount the image or start a virtual disk. This is a limitation inherited from the .vhd file format which just does not have any means to store the sector size.
  • There is no user interface to change the configuration of virtual machines, virtual machines may become broken as backups are merged, and virtual machines created by Backup are not cleaned up automatically.

Bug Bounty Program

I am very serious about quality and specifically security of my products and services. Thus in line with other (see https://en.wikipedia.org/wiki/Bug_bounty_program) I am willing to give away free or reduced cost licenses to users who report serious issues. Eligibles have to be the first ones to report the issue (in other words, everything listed at Known Issues does of course not qualify, as does anything that is documented on this site), the issue must be serious (with respect to the purpose of the application), and the reporter must provide sufficient information to make it reproducible and fixable. If multiple users report the same issue, it is up to my discretion who will be honored, considering who was first and who was providing the most useful information.

Reports shall be sent to support@lindenberg.one or submitted via support.lindenberg.one.