Article ID: 5157 Reviewed: 17/05/2016 Product Version: AhsayACB / AhsayOBM: 18.104.22.168 or above OS: Windows
This article offers a guideline on how to troubleshoot on case where scheduled backup job is not running.
Below are the steps to follow for troubleshooting problem with missed schedule backup:
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).
Ensure that the AhsayCBS server and AhsayOBM / ACB client application are running on the latest stable release, to prevent issues that are already resolved.
Refer to the following KB article for instruction on how to patch the server and client application:
Ensure that the Ahsay Online Backup Manager Service are started or can be started properly:
Check if the scheduler service is running by inspecting the client side scheduler debug log.
Refer to the following KB article for location of the Scheduler Debug Logs (debug.log):
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:
# /etc/init.d/obmscheduler stop # /etc/init.d/obmscheduler start
$ SystemStarter stop AhsayOBM $ SystemStarter start AhsayOBM * For client installation on Mac OS X 10.10 or above, enter the following command in Terminal: <code> $ sudo launchctl unload /Library/LaunchDaemons/com.AhsayOBM.scheduler.plist $ sudo launchctl load -w /Library/LaunchDaemons/com.AhsayOBM.scheduler.plist
Ensure that the 'Run scheduled backup for this backup set' setting is enabled on the corresponding client computer.
Check on the AhsayCBS web console to determine if the schedule is configured for the correct client computer.
In the scheduler debug log, check if entries similar to the following example can be found:
[YYYY/MM/DD hh:mm:ss][info][BackupSet (Backup_ID)] Next backup will run in 0 hr 1 min 0 sec [YYYY/MM/DD hh:mm:ss][info][BackupSet (Backup_ID)] Skipping scheduled backup on this computer. Schedule should run on ComputerName_A, current computer name: ComputerName_B
For each backup set, the scheduler service will verify if the computer name (of the machine where the scheduler service is running) is the same as the computer name specified in the backup set setting.
If the computer name of the client computer had changed, the scheduled backup job will be skipped by the scheduler service, because of the mis-match.
To resolve the issue, ensure that the scheduled backups on the corresponding machine is configured properly, make sure that the correct computer name has been set in the AhsayCBS web console for the relevant backup set.
Under [Users, Groups & Policies] > [Backup User] > [username] > [Backup Set] > [Backup Schedule]:
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.
Login to the AhsayCBS web console, under [Users, Groups and Policies] > [Backup User] > [username] > [User Profile] > [General], check on the Timezone setting.
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 AhsayOBM / ACB installation folder, except for installation on WIndows, the home.txt file is located at: C:\ProgramData\AhsayOBM\home.txt
Within the file, you should see at least one entry pointing to a .obm / .acb 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.
For AhsayOBM installation on Linux, you must configure the client login setting by running the RunConfigurator.sh script at least once:
Login Menu (No configuration files found) ----------------------------------------- (1). Login (2). Free Trial (3). Quit ----------------------------------------- Your Choice: 1
For AhsayOBM / ACB 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).
Resolve the issue, please follow the instructions as follow:
9.1 Enter the following command in terminal:
$ sudo vi /etc/hostconfig
9.2 Edit the file by adding the following entry into the hostconfig file:
9.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.
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 KB article:
Check if 'Mirrored Folders' is enabled for Desktop:
In some cases, scheduled backup may not run with this option enabled, please disable the option to resolve the issue.
**Important** 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 clocks of the client machine and that of AhsayCBS are off.