Ask the Community
Groups
Offsite synthetic full backups stuck in queue (not running) - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>SYMPTOMS</strong></p> <p>Synthetic full backups have completed on backup agent, but have not yet been executed on the offsite server.</p> <p>Backup Status page may show a backlog of queued offsite synthetic full backups.</p> <p> </p> <p><strong>CAUSE</strong></p> <p>When a <em>synthetic full backup</em> completes on a <em>backup agent</em>, an offsite synthetic full backup (OSFB) is queued on the <em>offsite server</em> that the client’s backups are replicated to. The status can be monitored from the <em>Offsite Status</em> page (Offsite/Local Server status sections).</p> <p><img src="/attachments/token/E1wCYxl3DRu2paFmapBuqUFfq/?name=offsitestatus.png" alt="offsitestatus.png" width="878" height="376" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p>The OSFB can only be processed when the <em>Backup Set</em> its being created <strong>from</strong> (i.e. the previous backup set) is complete on the offsite server. If the job shows in the queue as <em>“ready to go”</em>, it means all required files are present.</p> <p>If a job is not <em>“ready to go”</em> it may be because: -</p> <ul><li> <p>incremental or differential backups from the previous set have not completed replication</p> </li> <li> <p>the OSFB from the previous set has not completed yet</p> </li> <li> <p>a dependent backup set has been deleted by a user from the backup agent’s<em> Image Location</em></p> </li> </ul><p>Once marked as <em>“ready to go”</em>, OSFB’s are processed sequentially in order of when they were queued. If a job is <em>“ready to go”</em> but not yet <em>“in process”</em>, it may be queued behind other jobs on the offsite server.</p> <p> </p> <p><strong>SOLUTION</strong></p> <p>Use these steps to determine why an offsite synthetic full backup (OSFB) has not completed yet: -</p> <p>1) go to <em>Backup Status</em> page and check the <em>synthetic full backup queue</em> for the offsite server that the backups are being replicated to. If there are several jobs queued for the backup agent in question, locate the oldest by <em>“New set name”</em></p> <p>2) if the job is <em>“ready to go”</em> and <em>“in process”</em>, it is currently running. If it appears to be “stuck” (it has been running for much longer than expected), click <a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/71506486">here </a>for further troubleshooting steps</p> <p>3) if the job is<em> “ready to go”</em> but is <strong>not</strong> <em>“in process”</em>, it is queued behind other jobs. Sort the queue by <em>“ready to go”</em> column to view all jobs which are ready and waiting to be processed.</p> <p>- if there are always multiple <em>“ready to go”</em> jobs waiting to be processed, <em>the offsite server may be overloaded</em><br>- if a job for another backup agent appears to be “stuck” (it has been running for much longer than expected), click <a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/71506486">here </a>for further troubleshooting steps</p> <p>4) if the job is not <em>“ready to go”</em>: -</p> <p>- from <em>Backup Status</em> page, review replication status for the offsite server</p> <p><img src="/attachments/token/d6O0oTT7dqPQkFA5CcN8Hmwa5/?name=offsiterepstatus.png" alt="offsiterepstatus.png" width="910" height="414" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p>- check that the <em>Backup Set</em> <strong>prior to the queued OSFB</strong> is complete (full backup and all incremental backups must be present)<br>- if any files have not yet completed replication, <em>OSFB will remain in the queue until they are complete. </em>If there is insufficient bandwidth available to complete replication, <a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/103170436">seed the replication data manually</a><br>- if the previous backup set is no longer present, <a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/102008793">the OSFB is “orphaned”</a>. <strong>In this case it will never run, and neither will any later dependent jobs.</strong></p> <p> </p> <p><strong>FURTHER INVESTIGATION</strong></p> <p>If the problem cannot be resolved using the above steps, please provide Kaseya Support with the following information: -</p> <p>1) screenshot of <em>Synthetic Backups Queued</em><br>2) screenshot of <em>replication status</em> showing oldest queued job and the previous backup set<br>3) agent names of affected backup agent, local and offsite servers<br>4) offsite replication logs from local and offsite servers - these are located in the agent “working directory” (usually c:\kworking) and named offsite*.txt</p> <p> </p> <p><strong>RELATED ARTICLES</strong></p> <p><a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/71506486">Synthetic full backups appear to be "hung" or stuck at 95% estimated completion</a></p> <p><a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/102008793">Resolving “orphaned” offsite synthetic full backups</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> <p><strong>APPLIES TO</strong></p> <p>Kaseya VSA (Backup module)</p> </article> </main>