Ask the Community
Groups
Backup skipped because backup was already running - Connect IT Community | Kaseya
<main> <article class="userContent"> <h3 data-id="problem"><strong>PROBLEM</strong></h3> <p>Backups keep getting skipped with warning "backup skipped because the backup was already running"</p> <h3 data-id="cause"><strong>CAUSE</strong></h3> <p>A backup or verify job was already running on the agent when the backup was scheduled to start. This may be because a previous job is taking longer than expected, or has "hung".</p> <h3 data-id="resolution"><strong>RESOLUTION</strong></h3> <p>1) Go to the Backup Status page and check if there is a long-running backup in progress. If it appears to be "hung" (stuck at 95% completion), refer to <a href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/88940698" rel="noopener nofollow">this article</a>.</p> <p>2) If "Verify Backup" option is selected in the Backup schedule for the agent, check if the <a href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/entries/88892998-Verify-Backup-task-hangs-after-scheduled-backup-job" rel="noopener nofollow">verify job has "hung"</a>.</p> <p>3) Check if the kaseyabackupcmd.exe process is running on agent machine - if so, kill it</p> <p>4) Start new backup and check if the problem persists<br><br></p> <h3 data-id="applies-to"><strong>APPLIES TO</strong></h3> <p>Kaseya Backup module - v6.5 and later</p> <p>Acronis Backup client v11.x</p> </article> </main>