KB2000: Another backup job is still running. Backup skipped

Allow the in-progress backup job to be complete before starting another backup for the same backup set (scheduled or manually).

If there is no previous backup job running, the previous job started for the backup set may have ended abruptly (e.g. server crash, client application crash).  Refer to the following steps to clear all obsoleted file(s):

1. Confirm if there is any 'running' within the ipc folder under the CloudBacko configuration folder at:

CloudBacko Go: ${User_Profile}\.obm\ipc\BackupSet\Backupset_id

CloudBacko Pro: ${User_Profile}\.cbp\ipc\BackupSet\Backupset_id

CloudBacko Lite: ${User_Profile}\.cbl\ipc\BackupSet\Backupset_id

CloudBacko Home: ${User_Profile}\.cbh\ipc\BackupSet\Backupset_id

2. Remove all files under the ipc directory.

3. Restart the CloudBacko service afterwards.

Note:
When a backup job is started manually or automatically at the scheduled time, a 'running' file will be created within the ipc directory to indicate that a backup job is in-progress. Under normal circumstances, the file will be removed automatically when the backup job is completed.

However, for cases where the previous backup job was ended abruptly (e.g. server crash, client application crash), the 'running' file may not be properly cleared. When the next backup job is started, the client agent will detect that the 'running' file exists, misinterpreting that a previous backup job is still in progress.