Ask the Community
Groups
The appliance may erroneously attempt an incremental backup following VM configuration change - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>The appliance may erroneously attempt an incremental backup following VM configuration change.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>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. <br>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. </p> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p>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. </p> <h2 data-id="notes"><strong>NOTES</strong></h2> <p>This defect was found by James B. </p> </article> </main>