Gfi backup scheduler service not running6/18/2023 ![]() In some cases, a missed backup job alert is received for a backup job that was actually performed at the scheduled time (but at an incorrect time).įor these cases, check if the timezone setting of the corresponding backup account is correctly setup. Is the timezone setting configured properly?Įnsure that the timezone setting of the corresponding backup account is correctly configured. ![]() To resolve the issue, ensure that the scheduled backups on the corresponding machine are configured properly, make sure that the correct computer name has been set in the Ahsa圜BS web console for the relevant backup set. 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. Schedule should run on ComputerName_A, current computer name: ComputerName_Bįor 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. Skipping scheduled backup on this computer. Next backup will run in 0 hr 1 min 0 sec In the scheduler debug log, check if entries similar to the following example can be found: Is the schedule configured for another computer?Ĭheck on the Ahsa圜BS web console to determine if the schedule is configured for the correct client computer. Login to the AhsayOBM user interface, select Backup Sets, then the corresponding backup set, and Backup Schedule to confirm: Was the backup schedule setting configured properly?Įnsure that the 'Run scheduled backup for this backup set' setting is enabled on the corresponding client computer. Run scheduled backup on this computer setting $ sudo launchctl load -w /Library/LaunchDaemons/ $ sudo launchctl unload /Library/LaunchDaemons/ > įor client installation on Linux, enter the following command:įor client installation on Mac OS X 10.7 to 10.9, enter the following command in Terminal:įor client installation on Mac OS X 10.10 or above, enter the following command in Terminal: If no log entry is written to the debug log, try to restart the service with the following procedure:įor client installation on Windows, in Control Panel: Next backup will run in x hr x min x sec. If the schedule is running properly, the log will contain entries similar to the following example: The scheduler debug log contain every details of the scheduler service. Refer to the following KB article for location of the Scheduler Debug Logs (debug.log):įAQ: Where are the backup client application logs stored at? Was the Ahsay Online Backup Manager Service started?Įnsure that the Ahsay Online Backup Manager Service are started or can be started properly:Ĭheck if the scheduler service is running by inspecting the client side scheduler debug log. Refer to the following KB article for instruction on how to patch the server and client application:įAQ: How to install the latest patch set for Ahsa圜BS? FAQ: How to install the latest patch set for AhsayOBM / AhsayACB? Patch the Ahsa圜BS server and AhsayOBM / ACB client application to the latest stable releaseĪre you using the latest version of AhsayOBM / ACB?Įnsure that the Ahsa圜BS server and AhsayOBM / ACB client application are running on the latest stable release, to rule out issues that are already resolved. computer shutdown after office hour, but backup schedule configured to a time after office hour). Was the affected computer switched off, hibernated or in standby mode?Ĭheck if the affected computer was switched off, hibernated or in standby mode when the scheduled backup is due to run (e.g. Below are the steps to follow for troubleshooting problem with missed schedule backup:
0 Comments
Leave a Reply. |