1) State of the machine
Please verify if the affected machine is not switched off, hibernated or in standby mode when the scheduled backup is due to run.

2) Scheduling Name
Please ensure that the “Run scheduled backup on computers named” for the backup set has been populated properly, through the webinterface http://onlinebackup.nucleus.be.

3) Info.log analysis
Please verify the info.log file, for any additional error messages.
The info.log is located in:
Business Back-up
(Windows) C:/Program Files/Nucleus Business Backup/ipc/Scheduler
(Linux) /usr/local/obm/ipc/Scheduler
(Mac OS X) /Applications/Nucleus Business Backup/ipc/Scheduler

Home Back-up
(Windows) C:/Program Files/Nucleus Home Backup/ipc/Scheduler
(Mac OS X) /Applications/Nucleus Home Backup/ipc/Scheduler

Verify if there are entries similar to the example below:

[YYYY/MM/DD hh:mm:ss] Scheduler Version=x.x.x.x
[YYYY/MM/DD hh:mm:ss] Java Vendor=Sun Microsystems Inc. Version=1.4.2_10
[YYYY/MM/DD hh:mm:ss] [info] Starting Scheduler, User:’Username’, Home:’C:/Documents and Settings/Username/.obm’
[YYYY/MM/DD hh:mm:ss] Another Scheduler is running! This Scheduler will not start!

To get the scheduler running again, you need to remove a file called “running” which reside in the folder ${Install-Home}/ipcScheduler and then restart the [Online Backup Scheduler] service.

4) Home.txt analysis
Verify if the home.txt has been populated correctly. The home.txt is located in:
Business Back-up
(Windows) C:/Program Files/Nucleus Business Backup/
(Linux) /usr/local/obm
(Mac OS X) /Applications/Nucleus Business Backup/

Home Back-up
(Windows) C:/Program Files/Nucleus Home Backup/
(Mac OS X) /Applications/Nucleus Home Backup/

You should see at least one entry pointing to a .obm (or .acb) folder that is accessible by the local scheduler service, for example “C:/Documents and Settings/administrator/.obm”. Please modify the home.txt file if this is not the case.

5) Scheduling Service analysis
Check if the scheduler service is running by inspecting the client side scheduler log. The scheduler debug log is located in:

Business Back-up
(Windows) C:/Documents and Settings/administrator/.obm/log/Scheduler/debug.log
(Linux) ~/.obm/log/Scheduler/debug.log
(Mac OS X) ~/.obm/log/Scheduler/debug.log

Home Back-up
(Windows) C:/Documents and Settings/administrator/.acb/log/Scheduler/debug.log
(Mac OS X) ~/.acb/log/Scheduler/debug.log

This log contain every details on the scheduler service.

If the schedule is working fine, the client side scheduler log should 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][LocalProfile.loadFromServer] Loading profile from server …
[YYYY/MM/DD hh:mm:ss][info][LocalProfile.loadFromServer] Loaded profile from server.
[YYYY/MM/DD hh:mm:ss][info][BackupSet (Backup_ID)] Next backup will run in 0 hr 36 min 37 sec
[YYYY/MM/DD hh:mm:ss][info][BackupSet (Backup_ID)] Next backup will run in 80 hr 16 min 37 sec
[YYYY/MM/DD hh:mm:ss][info][Thread][Reloader] Loaded profile from server.

Otherwise, please restart the scheduler service. If the problem persist, please consider re-installing the Nucleus Home/Business Back-up software or the scheduler service.

If the Nucleus Home/Business Back-up software is installed on a Windows 2000 machine, the scheduler service can stall at times due to the instability of Windows 2000’s Services. A workaround is to write a batch job that restart the scheduler service periodically.

Please also check whether entries similar to the following example can be found at the scheduled backup time:

[YYYY/MM/DD hh:mm:ss][info][BackupSet (Backup_ID)] Wake Up …
[YYYY/MM/DD hh:mm:ss][info][BackupSet (Backup_ID)] This backup job will run to its completion.
[YYYY/MM/DD hh:mm:ss][info][BackupSet (Backup_ID)] Start running backup

If additional error messages are found, please contact us through support@nucleus.be with the log files.

6) Linux: username + password
If the Nucleus Back-up software is installed on a Linux machine, please try running the Configurator.sh script to set appropriate backup account and password.

7) Still experiencing problems?
If you are still experiencing problems after the abovementioned steps, please contact our support department at support@nucleus.be

Notes:
We would just like to clarify that missed backup may not necessarily be 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 Online Back-up server are off, causing problems.

Kunnen we je nog ergens anders mee helpen?

Bel of mail ons. We helpen je snel met een antwoord.

Contacteer ons