- Product Version:
- Problem Description:
- Cause:
- Verify if a file called "running" exist in the ipc directory:
- (ServosityPro) \.obm\ipc\BackupSet\%backupset_ID%\
- (ServosityStandard) \.acb\ipc\BackupSet\%backupset_ID%\
- If there is, please remove the file
- If the backup set in concern is a MS Exchange server backup, please also remove all data within the temporary database directory
- Restart the Online Backup Scheduler service on the machine in concern
ServosityStandard: All
ServosityPro: Post-5.1
ServosityOBS: All
OS: All platforms
ServosityPro: Post-5.1
ServosityOBS: All
OS: All platforms
After an ServosityOBS server stoppage, a backup set that was performing on a ServosityPro/ServosityStandard client machine seems to have stopped. Furthermore, new backup job that is performed by the scheduler or that is performed manually cannot be started. What can be the problem?
Outlined below are some guidelines on how to troubleshoot the issue:
Notes:
When a backup set is performed, a file called "running" will be generated inside the ipc directory (e.g. \.obm\ipc\BackupSet\%backupset_ID%\). This is to indicate that a backup job is currently running. Under most circumstance, the file "running" will be removed after the backup job is completed.
However, in the case where the ServosityOBS service was stopped unexpectedly. Backup job(s) that was running will be interrupted, and the file "running", in some cases may not be removed.
When the next backup job is set to be performed, ServosityPro/ServosityStandard detects that the file "running" still exist in the ipc directory, which indicates that a backup job is still in progress. And thus, no backup job can be started.
Notes:
When a backup set is performed, a file called "running" will be generated inside the ipc directory (e.g. \.obm\ipc\BackupSet\%backupset_ID%\). This is to indicate that a backup job is currently running. Under most circumstance, the file "running" will be removed after the backup job is completed.
However, in the case where the ServosityOBS service was stopped unexpectedly. Backup job(s) that was running will be interrupted, and the file "running", in some cases may not be removed.
When the next backup job is set to be performed, ServosityPro/ServosityStandard detects that the file "running" still exist in the ipc directory, which indicates that a backup job is still in progress. And thus, no backup job can be started.