Schedule set for once daily -- but is not happening.

The Systemback uses a reference file in the storage directories (.sbschedule). If the last modification time and current time difference is bigger than scheduler time, then the sbscheduler daemon try to start to create a new restore point.
The scheduler may not work because the following reasons:
- The sbscheduler daemon is not running. Check with the "pgrep sbscheduler" command (you will get the process id or nothing).
- The storage directory is not available (because the partition is not mounted, ...).
- The scheduler ON/OFF switch resets the reference time, so if you turned on the scheduler, then the scheduled restore point creation does not start before tomorrow. Check the .sbschedule file last modification time. You can change this time with the following command:
touch -d "36 hours ago" /home/Systemback/.sbschedule
But reboot the computer and wait 5 minutes.
- The sbscheduler daemon try to open the Systemback window (if you not set the silent mode), but failed (because Xauthority, or the dpkg or the Systemback locking is not possible because another process). Close all package manager and the Systemback.

Please check these things and report back.

The scheduler may not work because the following reasons:
- The sbscheduler daemon is not running. Check with the "pgrep sbscheduler" command (you will get the process id or nothing).
I get nothing -- a blank line, no process ID -- and in Systemback, scheduled backups are 'Enabled'.

- The storage directory is not available (because the partition is not mounted, ...).
A manually-triggered backup works fine, so the storage partition seems to be 'there'.

I think I should get sbscheduler running, before going any further? What is the next step in troubleshooting this?

So the sbscheduler does not started. The autostart is carried out by the following files (after login in the GUI):
/etc/xdg/autostart/sbschedule.desktop
/etc/xdg/autostart/sbschedule-kde.desktop
with the following command:
/usr/lib/systemback/sbsustart scheduler
I do not know this Bodhi Linux, but it seems that this solution does not work with it. So please check the /etc/xdg/autostart directory, is it empty (apart from the Systemback files)?

We have the two files described above in /etc/xdg/autostart, and sbsustart plus
sbscheduler in the other directory, as you described.
Bodhi Linux is a light-weight Ubuntu distro with an Enlightenment 16 or 17 environment.

Ok, I will download this distribution and I will check it.

The Enlightenment does not start applications from /etc/xdg/autostart by default. So the sbscheduler daemon does not start automatically.
You need to enable the scheduler daemon auto starting via the menu -> Settings -> All -> Apps -> Startup Applications (or edit manually the ~/.e/e/applications/startup/.order file).
This is a manual workaround, I cannot fix this problem in the Systemback, because there is no global configuration file.

Thanks Kendek, for going to the trouble of doing all that.
Just to make certain, since you've just looked at it, and know all the details ...
could you please write for me exactly the words that I will add to the .order file?

And if I go through Startup Applications, what will be the word I see there, of what I am to select?

I thought it would be easier if I ask while it is fresh in your mind, instead of making a mistake and then asking in a few days ...

I will make a post on the Bodhi form after that, to alert other users that some programs may not install as expected because of what you have discovered.

The main reason I asked, in case you are wondering, is there something that's been left out of this line?
/usr/lib/systemback/sbsustart scheduler

When there is a parameter following an executable, often there has to be some punctuation there, such as a '<space> -' or if it's all the executable's name, then would be a '_' because Unix doesn't like spaces.

So if you could please write it out, whatever it should be, then I will not make a mistake.

Thanks for your patience, in explaining the details. I will post a link to this thread on the Bodhi Linux forum, so other Bodhi users will be aware of it. I'm sure the response from the Bodhi developers will be that it has to be corrected by the Enlightenment developers. But at least Bodhi users will know of the work-around necessary for Systemback and other software that uses a similar technique.

Thanks Kendek, that solved my question.

Kendek's solution posted on Bodhi Linux forum, E17 section:
http://forums.bodhilinux.com/index.php?/topic/12609-some-software-needs-manual-work-around-for-automatic-startups/#entry94076

... along with a recommendation for other Bodhi usesrs to try Systemback.

Ok, thanks.