Ask the Community
Groups
Resolving “orphaned” offsite synthetic full backups - Connect IT Community | Kaseya
<main> <article class="userContent"> <h3 data-id="problem">Problem</h3> <p>One or more O<em>ffsite Synthetic Full Backups</em> (OSFB) is queued but never gets marked as “<em>ready to go</em>”.</p> <p>The prior dependent backup set has been completely or partially deleted.</p> <p> </p> <h3 data-id="cause">Cause</h3> <p>Every OSFB is dependent on the last <em>Backup Set</em>. If a <em>Backup Set</em>, or any of its files, are deleted before the OSFB for the next set is completed, the OSFB for the next set (and any later dependent sets) will be “orphaned”.</p> <p> </p> <h3 data-id="resolution">Resolution</h3> <p>In this case it is necessary to start a new chain by forcing a <em>non-synthetic Full Backup</em>.</p> <p>This can be done using the following steps: -</p> <p><br>1) force a new non-synthetic full backup by re-submitting the <em>Image Password</em> on the affected backup agent</p> <p>- go to <em>Backup > Configure > Image Password</em> page</p> <p>- select the agent</p> <p>- re-enter the <em>same password</em> in the "create" and "confirm" boxes, and click the <strong><em>Change</em> </strong>button (password does not need to be changed, just re-submitting the same password again will force the next backup to be non-synthetic full backup)</p> <p>- the existing schedule will not be affected (for example if full backups normally run on Fridays and you do this on a Tuesday, you will get a non-synthetic full backup on Tuesday and then a synthetic full again on the Friday)</p> <p> </p> <p>2) if there is not enough bandwidth to replicate the new full backup: -<br>- suspend replication using <em>Schedule Transfer</em> function</p> <p>- copy the file to the offsite server manually (for example using a removable disk)</p> <p>- enable replication again</p> <p> </p> <p>3) manually delete or move the sets prior to the new full backup from the image location - they will be removed from Kaseya database the next time a full (or synthetic full) runs, at this point any queued offsite synthetic full backups for those sets will be removed</p> <p> </p> <h3 data-id="related-articles">Related articles</h3> <p><a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/103171266">Offsite synthetic full backups stuck in queue (not running)</a></p> <p><a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/103170436">Manually seeding offsite replication data</a></p> <p> </p> <h3 data-id="applies-to">Applies to</h3> <p>Kaseya VSA (Backup module)</p> </article> </main>