nssbackup-team team mailing list archive

[Jean-Peer Lorenz <peer.loz@xxxxxxx>]

Some more questions from me to triage this issue:

* Were the snapshots removed physically from the disk or aren't they not
visible in the restoration gui but still reside on the disk?

* What version of sbackup did you use? From where did you installed it
(source/Ubuntu repository/PPA)?

* What exact version of nssbackup did you use? From where did you
installed nssbackup (source/PPA)?

I recognized a problem with your installation of nssbackup. It does not
seem to be proper. A resource file is not found though this one is
created during the installation process. Did you install from source
code or did you just copied the files?

here is the log entry:
2009-03-01 13:21:34,731 - WARNING - nssbackupd.py:__onError(233) - [Errno 2] Nessun file o directory: '/usr/lib/python2.5/site-packages/nssbackup/ressources'


Here you can see how invalid snapshots are handled by NSsbackup. The snapshot is renamed:

2009-03-01 13:04:38,821 - WARNING - SnapshotManager.py:_read_snps_from_disk_allformats(176) - Got a non valid snapshot '2008-06-20_11.05.33.326694.enzanita.ful' , removing : The mandatory 'ver' file doesn't exist in [2008-06-20_11.05.33.326694.enzanita.ful] 
2009-03-01 13:04:38,822 - INFO - SnapshotManager.py:_read_snps_from_disk_allformats(178) - Invalid snapshot '/home/backup/2008-06-20_11.05.33.326694.enzanita.ful' is going to be renamed!

As you can see, the `ver` file was missing in that snapshot? Why? I guess the backups were never finished by sbackup and because of that no `ver` file was written.
Can you check this in the currently created sbackup backups

* Please post your `/etc/sbackup.conf` and `/etc/nssbackup.conf`.

A final remark: since some releases (don't know exactly RC3 or 4)
NSsbackup does not delete invalid backups and does not upgrade backups
in old formats.

Hopefully, we can firgure out what was going on there.

Best regards. Jean-Peer

-- 
deletes incremental backups left by sbackup
https://bugs.launchpad.net/bugs/337269
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.