BUS Backups not running on schedule

From SWCP Support Wiki
(Redirected from BUS not running on a Mac)
Jump to navigationJump to search

Version 8

Missed backups can happen for several reasons, incuding

  • Computer being in standby (sleep or hibernation) at the time of the scheduled backup
    Solutions:
    • Extend your computer's sleep/wake timer to ensure the computer is awake at the correct time
    • Choose a different time for the scheduled backups via the Backup Sets => => [Backup Set Name] => Backup Schedule menu of the client, or on https://backup.swcp.com
    • Disable sleep timers entirely on the computer (not advisable on computers with battery power, like laptops), or set your power options to disable sleep when the computer is plugged in
    • Set a scheduled task to wake the computer at the scheduled backup time
  • Problem with the BUS Client's scheduler service
    Solutions:
    • Restarting the computer will usually correct this issue
    • If rebooting is not possible/advisable, you can also restart the scheduler service by going (on Windows) with the following steps:
      • Open a "Run" window (Windows key + R), type "services.msc" and click "Run"
      • In the services menu, locate "SWCP BUS Client Services" then right-click and choose "Restart"
  • The scheduler is not configured to run on the correct system
    Solution:
    • Open the BUS Client, then go to Backup Sets => [Backup Set Name] => Backup Schedule, enable the schedule with the slider button and click "OK" when prompted to run backups on your new computer.
How do I know it's working?

The scheduler has a log file that will contain information on whether the scheduler has a heartbeat. If the scheduler is not running, the log file will not have any current information, or may contain errors that will clue us into hte problem. It is located in the bus client's profile folder, which is called .obm on the server version and .acb on the desktop version. Here's how to find it:

On Windows:

  • In File Explorer, browse to C:\Users\Your username\.obm or .acb\log\Scheduler, and open the file debug.log.
    (note that .obm/.acb are hidden folders, so File Explorer will need to have the "View Hidden Files and Folders" checkbox ticked. That is in the View menu tab of File Explorer on Windows 8 and later.)

On MacOS:

  • Open Terminal (or your preferred terminal app), then type in the following commands:
cd ~/.acb/log/Scheduler (replace .acb with .obm if you are using the Server version)
tail debug.log (this will show you the last 10 lines of debug.log)

On Linux:

  • In a terminal, type in the following
sudo tail /root/.obm/logs/.obm/debug.log

If the scheduler is running properly the last few lines of the log file will look like this, with current timestamps: 

[2020/05/07 10:22:24][info] Profile is reloaded from server. Reloading scheduler ...
[2020/05/07 10:22:24][info] [Backup (1576276018881)]  Next backup will run in 8 hr 37 min 35 sec.
[2020/05/07 10:22:24][info] Profile is reloaded from server. Reloading scheduler ... Completed
[2020/05/07 10:27:24][info] Loading profile...
[2020/05/07 10:27:24][info] Loading profile from server ...
[2020/05/07 10:27:26][info] Loading profile from server ... Completed
[2020/05/07 10:27:26][info] Loading profile... Completed
[2020/05/07 10:27:26][info] Profile is reloaded from server. Reloading scheduler ...
[2020/05/07 10:27:26][info] [Backup (1576276018881)]  Next backup will run in 8 hr 32 min 33 sec.
[2020/05/07 10:27:26][info] Profile is reloaded from server. Reloading scheduler ... Completed

If any errors are listed, or the timestamps aren't current, please let us know.

Version 6

This affects both Mac and Windows clients. Especially after moving to a new computer, and sometimes after upgrading a Mac to Snow Leopard, the SWCP Backup client may fail to run on schedule.

The notes below tell how to inspect the log file on a Mac -- substitute similar for Windows, or skip down to "The Fix" below.

To find out what's going on, first check the scheduler logs. Run the Terminal program. This will put you in your home directory. From there 

  cd .obm/log/Scheduler

The log file for today is named debug.log. Yesterday's log is debug.log.1, etc. 

  tail debug.log

will show you the last ten lines of the log file. The error message of interest will look like: 

  Ignore scheduled / server initiated backup on this computer, Macintosh. 
  Should run on computer named 'Sayuri.local'.

The computer's name in this example is "Sayuri", but for some reason the BUS client believes it to be named "Macintosh".

The Fix

To get the scheduler working again, log into the BUS web interface at https://bus.swcp.com using your BUS client account name and password. From there select "Backup Set" from the top right side menu.

Scroll down to the "Backup Schedule" section to this item: 

 "Run scheduled backup on computers named "

The text box should have the name of your computer. If this doesn't machine the current name of your computer, edit it to match (in this example "Macintosh").

Scroll down to the "Update" button and click it. That should fix it -- your computer do the right thing at the next scheduled backup time.

Retrieved from "https://wiki.swcp.com/w/index.php?title=BUS_Backups_not_running_on_schedule&oldid=2067"