Article ID: 8007
Product Version: CloudBacko Go 8.5 or above
Operating System: Windows, Linux/FreeBSD, macOS
Scheduled backup are not running (missed backup).
This article offers a guideline on how to troubleshoot for missed scheduled backup.
Below are the steps to follow for troubleshooting problem with missed schedule backup:
Computer shutdown or hibernated
Was the affected computer switched off, hibernated or in standby mode?
Check if the affected computer was switched off, hibernated or in standby mode when the scheduled backup is due to run (e.g. computer shutdown after office hour, but backup schedule configured to a time after office hour).
Patch the CloudBacko Go client application to the latest stable release
Are you using the latest version of CloudBacko Go?
Ensure that the CloudBacko Go client application is running on the latest stable release to rule out issues that are already resolved.
Refer to the following article for instruction on how to patch the client application:
FAQ: How to install the latest patch set for CloudBacko Go?
CloudBacko Go Services
Was the CloudBacko Go Services started?
Check if the scheduler service is running by inspecting the client side scheduler debug log.
Refer to the following article for location of the Scheduler Debug Logs (debug.log):
FAQ: Where are the backup client application logs stored at?
The scheduler debug log contain every details of the scheduler service. If the schedule is running properly, the log will contain entries similar to the following example:
| [YYYY/MM/DD hh:mm:ss][info][Thread][Reloader] Loading profile from server …
[YYYY/MM/DD hh:mm:ss][info] Loading profile…
[YYYY/MM/DD hh:mm:ss][info] Loading profile from server …
[YYYY/MM/DD hh:mm:ss][info] Loading profile from server … Completed
[YYYY/MM/DD hh:mm:ss][info] Loading profile… Completed
[YYYY/MM/DD hh:mm:ss][info] Profile is reloaded from server. Reloading scheduler …
[YYYY/MM/DD hh:mm:ss][info] [BackupSet (Backup_ID)] Next backup will run in x hr x min x sec.
[YYYY/MM/DD hh:mm:ss][info] Profile is reloaded from server. Reloading scheduler … Completed
If no log entry is written to the debug log, try to restart the service with the following procedure:
For client installation on Windows, in Control Panel:
[ Administrative Tools ] > [ Services ] > [ CloudBacko Go Services ]
For client installation on Linux, enter the following command:
| # /etc/init.d/obmscheduler stop
# /etc/init.d/obmscheduler start
For client installation on Mac OS X 10.7 to 10.9, enter the following command in Terminal:
| $ SystemStarter stop AhsayOBM
$ SystemStarter start AhsayOBM
For client installation on Mac OS X 10.10 or above, enter the following command in Terminal:
| $ sudo launchctl unload /Library/LaunchDaemons/com.AhsayOBM.scheduler.plist
$ sudo launchctl load /Library/LaunchDaemons/com.AhsayOBM.scheduler.plist
Run scheduled backup on this computer setting
Was the backup schedule setting configured properly?
Ensure that the 'Run scheduled backup for this backup set' setting is enabled on the corresponding client computer.
Is the timezone setting configured properly?
Ensure that the timezone setting of the corresponding backup account is correctly configured.
In some cases, a missed backup job alert is received for backup job that was actually performed at the scheduled time (but at an incorrect time).
For these cases, check if the timezone setting of the corresponding backup account is correctly setup.
Operating system profile
Check if the scheduler service is looking at the correct operating system account profile.
Check if the home.txt has been populated correctly, the home.txt is located at the CloudBacko Go installation folder, except for installation on Windows, the home.txt file is located at:
Within the file, you should see at least one entry pointing to a .obm directory that is accessible by the local scheduler service, for example “C:\Users\administrator\.obm”. Modify the home.txt file by adding the directory path to the .obm folder, if the file is empty.
CloudBacko Go installation on Linux
Did you run the RunConfiguator.sh script on the affected client computer?
CloudBacko Go installation on Mac OS X (10.7 to 10.9)
For CloudBacko Go installation on Mac OS X, if the hostname of the affected client computer is constantly changing due to different DHCP server assignment (e.g. user who travel often with MacBook).
To resolve the issue, refer to the following steps:
1. Enter the following command in terminal:
|$ sudo vi /etc/hostconfig|
2. Edit the file by adding the following entry into the hostconfig file:
3. Restart the computer.
Once the computer is restarted, check on the scheduler debug log to confirm if the correct hostname is picked up by the scheduler service.
Java heap size setting
Did the client application ran out of memory?
Ensure that there are sufficient free memory available on the client computer for the backup to begin.
Check if entries similar to the following example can be found at the scheduler debug log:
| [YYYY/MM/DD hh:mm:ss][info][AhsayOBM.OutputStream][Backup Set] Error occurred during initialization of VM
[YYYY/MM/DD hh:mm:ss][info][AhsayOBM.OutputStream][Backup Set] Could not reserve enough space for object heap
Increase the memory allocation setting with the instructions provided in the following article:
FAQ: How do I modify the Java heap size setting of CloudBacko Go?
Backup client installation on guest virtual machine hosted by VMware Fusion
Is the Mirrored Folders option enabled?
We would just like to clarify that missed backup may not necessarily be a software problem.
End-users may have their PC / server switched off, hibernated or in standby mode when the schedule is due to run, or network can be unavailable or being cut off during the scheduled backup time.
We have also seen cases where the system clock of the client machine is off.
schedule, missed, miss, backup, missing, not, running