Ask the Community
Groups
Incremental Backup Results in a Failure When No Data Changes - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Incremental Backup Results in a Failure When No Data Changes, when System State is Included</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="purpose">Purpose</h3> <p>This article provides a workaround to show failed incremental backups jobs when no data changes as successful.</p> <h3 data-id="applies-to">Applies To</h3> <p>Unitrends appliance software version 6.0 and later</p> <p>All Windows versions.</p> <h3 data-id="symptoms">Symptoms</h3> <p>Incremental backup jobs fail when non system volumes were included in backup, no data changes on the client and System State option included. This is typical of backup schedules where the only data being backed is a non-system disk such as the secondary drive(s) on file server where data seldom changes and system state excluded during a backup.</p> <p>When viewing the event from a backup or failures report, the end of the output will contain the following:</p> <blockquote class="blockquote"> <p><span style="font-family: courier;">----- Summary Messages -----<br>System state is excluded from backup, it requires include volume 'C:/'.<br>----- End Summary Messages -----<br><br>FATAL: No backup data received from client.<br>The database update was successful.</span></p> </blockquote> <p>Fix: Exclude a System State from backup where only data volumes are included.</p> </article> </main>