The appliance may erroneously attempt an incremental backup following VM configuration change.
After changes are made to a protected VM (e.g. adding a new disk or VM hardware version change) normally the next incremental backup to run would fail, and promote the following backup to a full backup automatically.
This is not happening properly in all cases, resulting in incremental backups failures noting a full is required to resolve in backup summary messages, but the full doesn't automatically happen resulting in a chain of failing backups requiring user manual intervention.
This issue is resolved with Unitrends ROS 10.1. If a VM backup determines changes to the VM that require a new backup, only 1 failed incremental should be encountered and the next backup should automatically perform a full backup to self-resolve without further customer action.
This defect was found by James B.