Cron job not running

backintime-{common,kde} version 0.9.26-3 installed on sidux (Debian/sid).

Is computer always on? It could happen that you missed the backup point. BiT
logs into the syslog. So you can check that one to see if it did run or not.

2009/11/22 Kap4Lin <email address hidden>

> Question #91217 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/91217
>
> Kap4Lin gave more information on the question:
> backintime-{common,kde} version 0.9.26-3 installed on sidux
> (Debian/sid).
>
> --
> You received this question notification because you are an answer
> contact for Back In Time.
>

On Sun, Nov 22, 2009 at 5:09 AM, Bart de Koning
<email address hidden> wrote:
> Bart de Koning proposed the following answer:
> Is computer always on? It could happen that you missed the backup point. BiT
> logs into the syslog. So you can check that one to see if it did run or not.

Yes, the computer is on. I can see the following in syslog:

Nov 22 00:00:01 nebu /USR/SBIN/CRON[18747]: (apoc) CMD (nice -n 19
/usr/bin/backintime --backup-job >/dev/null 2>&1)
Nov 22 00:00:02 nebu backintime (apoc): INFO: Lock
Nov 22 00:00:02 nebu backintime (apoc): INFO: Include folders: [...long list..]
Nov 22 00:00:02 nebu backintime (apoc): INFO: Ignore folders: []
Nov 22 00:00:02 nebu backintime (apoc): INFO: Last snapshots: {}
Nov 22 00:00:02 nebu backintime (apoc): INFO: [KDE4Plugin.Systray.run]
Nov 22 00:00:03 nebu backintime (apoc): INFO: Compare with old
snapshot: 20091107-023119
Nov 22 00:00:03 nebu backintime (apoc): INFO: [KDE4Plugin.Systray.run]
begin loop

Nothing after that. Exactly similar thing was found in logs from two
weeks earlier too. So, it seems to run, but I do not see any new
snapshots being created on the backup hard disk!

So, here is the question: with the above said setup, is a new
directory (yyyymmdd-hhMMss) supposed to be created every week?

> 2009/11/22 Kap4Lin <email address hidden>
>
>> Question #91217 on Back In Time changed:
>> https://answers.launchpad.net/backintime/+question/91217
>>
>> Kap4Lin gave more information on the question:
>> backintime-{common,kde} version 0.9.26-3 installed on sidux
>> (Debian/sid).
>>

--
Regards
PK
--------------------------------------
http://counter.li.org #402424

Ai you bumped into a misterious bug that we are trying to solve, but we
cannot get grip into it.
https://bugs.launchpad.net/backintime/+bug/441628
In the meanwhile you can at least make manual backups by running "backintime
-b", or using hte KDE-GUI

Can you post your log also in that bugreport + some additional information
like how often you have it scheduled?

And it is supposed to make a new folder every time it is scheduled!
Cheers,
Bart

2009/11/23 Kap4Lin <email address hidden>

> Question #91217 on Back In Time changed:
> https://answers.launchpad.net/backintime/+question/91217
>
> Status: Answered => Open
>
> Kap4Lin is still having a problem:
> On Sun, Nov 22, 2009 at 5:09 AM, Bart de Koning
> <email address hidden> wrote:
> > Bart de Koning proposed the following answer:
> > Is computer always on? It could happen that you missed the backup point.
> BiT
> > logs into the syslog. So you can check that one to see if it did run or
> not.
>
> Yes, the computer is on. I can see the following in syslog:
>
> Nov 22 00:00:01 nebu /USR/SBIN/CRON[18747]: (apoc) CMD (nice -n 19
> /usr/bin/backintime --backup-job >/dev/null 2>&1)
> Nov 22 00:00:02 nebu backintime (apoc): INFO: Lock
> Nov 22 00:00:02 nebu backintime (apoc): INFO: Include folders: [...long
> list..]
> Nov 22 00:00:02 nebu backintime (apoc): INFO: Ignore folders: []
> Nov 22 00:00:02 nebu backintime (apoc): INFO: Last snapshots: {}
> Nov 22 00:00:02 nebu backintime (apoc): INFO: [KDE4Plugin.Systray.run]
> Nov 22 00:00:03 nebu backintime (apoc): INFO: Compare with old
> snapshot: 20091107-023119
> Nov 22 00:00:03 nebu backintime (apoc): INFO: [KDE4Plugin.Systray.run]
> begin loop
>
> Nothing after that. Exactly similar thing was found in logs from two
> weeks earlier too. So, it seems to run, but I do not see any new
> snapshots being created on the backup hard disk!
>
> So, here is the question: with the above said setup, is a new
> directory (yyyymmdd-hhMMss) supposed to be created every week?
>
>
> > 2009/11/22 Kap4Lin <email address hidden>
> >
> >> Question #91217 on Back In Time changed:
> >> https://answers.launchpad.net/backintime/+question/91217
> >>
> >> Kap4Lin gave more information on the question:
> >> backintime-{common,kde} version 0.9.26-3 installed on sidux
> >> (Debian/sid).
> >>
>
> --
> Regards
> PK
> --------------------------------------
> http://counter.li.org #402424
>
> You received this question notification because you are an answer
> contact for Back In Time.
>

This really needs to be fixed. Otherwise, a backup program which does not do any backup is kind of useless!! I've posted my logs at the above bug. Hopefully you guys can get around and have a solution...

Geez guys, how my 500 GB backup disk is spitting out all kinds of missing inode/Exception Emask/BMDMA/DRDY ERR/.. errors.. I'm running an fsck on it now... Looks like a lot of previous backup data (the ones done by backintime) is corrupted...

You could've just written a frontend to rsnapshot in Qt, rather than trying smart things!

No more of backintime... I'll have to fall back to the proven rsnapshot utility!!!

Geez guys, how my 500 GB backup disk is spitting out all kinds of missing inode/Exception Emask/BMDMA/DRDY ERR/.. errors.. I'm running an fsck on it now... Looks like a lot of previous backup data (the ones done by backintime) is corrupted...

You could've just written a frontend to rsnapshot in Qt, rather than trying smart things!

No more of backintime... I'll have to fall back to the proven rsnapshot utility!!!

This question was expired because it remained in the 'Open' state without activity for the last 15 days.