nssbackup-team team mailing list archive

[cando <701916@xxxxxxxxxxxxxxxxxx>]

I use it on 2 different machines:

One server with Ubuntu Lucid 10.04 x64, SBackup fresh installed from ppa
One workstation Ubunty Maverick 10.10 x64, SBackup installed / upgraded 
directly from the distro package

On both machines the same error. incremental backups contain always full 
file set (ver.1.5) as stamp in file ver in backup set.

Older backups (from ver stamp1.4) were all correct, full backup set 
contains all files, incremental only changed content.

The bug is reproduceable, it happens all the time since the installation 
of the new version on both machines.

I assume Sbackup runs as root (file permissions are set to owner root).
The UI is called via: gksu sbackup-config-gtk - so it is an elevated 
user account. (after the upgrade the management UI
has completely disappeared from the System -> Administration Menus and I 
have manually add the entries for
sbackup-config-gtk and sbackup-restore-gtk with elevated rights via gksu.)

related to your request: I have set up now a new profile (manual backup) 
and tried on the same disk (different directories).
It seems to work, the first set contains all files, the subsequent sets 
contain only the complete empty folder structures
(changed vs. ver. 1.4 - there were no empty folders) I have tried 
immediately following 3 backups with this configuration
and the backup seems to work.

What are the criteria how sbackup decides that one file was modified and 
needs to be backed up incrementaly?

I will  do the test tomorrow again to see, if it still works after 
reboots and clam av virus scans and I will mail you the results.

I have some questions regarding sbackup:

What happens if two sbackup jobs access the same folder / file from 
different machines (e.g. for redundancy)?
Does sbackup modify the file system on backup somehow so the two jobs 
bite each other if a user decides
to back up / copy the shared data himselve in the meantime?

Is it somewhere documented, how sbackup works and on what information it 
relies and what changes it makes to the file system?


Many thanks


cando


On 01/12/2011 05:29 PM, Jean-Peer Lorenz wrote:
> Thank you for using SBackup and for taking the time reporting this bug.
>
> In order to track down the cause of the problem some more information
> are required. Please answer the following questions:
>
> * what distribution do you use?
> I've understood correctly 10.04 Lucid and 10.10 Maverick, right?
>
> * from where was it installed (PPA, from source)?
> * Is the bug reproducible; does it happen every time?
> * do you run sbackup as superuser (root) or as regular user?
> * Do backups (incremental) work for you, when running a backup stored on local drive?
> * If you set up a minimal profile (maybe just a single directory) and run a manual backup (1st full, 2nd incr.), does it work as expected?
>
> At first glance, your specific error looks like an underlying problem to
> me (e.g. modified time stamps) not directly caused by SBackup.
>
> Many thanks for your help.
>

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.
https://bugs.launchpad.net/bugs/701916

Title:
  Incremental Backup not working in ver. 0.11.3