On 2011-02-07 08:56 +0100, Xavier Bestel wrote:
> Package: backup-manager
> Version: 0.7.9-3
> Severity: important
>
>
> Hi,
>
> backups on my system are quite big (some are half a Tb), so they are quite
> long to do. Today I received the mail for the backup started on Feb 1st. The
> problem is that while the master backup isn't finished, bm already started to
> do the corresponding incremental backups:
> -rwxrwxrwx 1 501 501 460G 2 févr. 19:50 awak-home.20110201.master.tar.gz*
> -rwxrwxrwx 1 501 501 460G 3 févr. 20:16 awak-home.20110202.tar.gz*
> -rwxrwxrwx 1 501 501 981M 3 févr. 06:35 awak-home.20110203.tar.gz*
> -rwxrwxrwx 1 501 501 983M 4 févr. 06:33 awak-home.20110204.tar.gz*
> -rwxrwxrwx 1 501 501 978M 5 févr. 06:33 awak-home.20110205.tar.gz*
> -rwxrwxrwx 1 501 501 980M 6 févr. 06:33 awak-home.20110206.tar.gz*
> -rwxrwxrwx 1 501 501 947M 7 févr. 06:33 awak-home.20110207.tar.gz*
> -rwxrwxrwx 1 501 501 14M 7 févr. 06:33 awak-home.incremental.bin*
>
> bm should somehow check that it isn't already doing a tarball (some
> kind of lock) and don't do it twice.
It does this already, the second instance should have refused to start.
Unless you're using a different configuration file for it, that is.
> Or maybe it does, but it doesn't work.
Possibly. If you would like to debug this, please set
BM_LOGGER_LEVEL="debug" in /etc/backup-manager.conf and send the syslog
output (grep backup-manager /var/log/user.log) if/when the problem
reoccurs.
Regards,
Sven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
