Re: dar_manager - incremental backups and removed file

On Monday, 15 April 2024 22:56:58 CEST Denis Corbin wrote:
> On 15/04/2024 07:04, J. Roeleveld via Dar-support wrote:
> 
> >> No warning showed. I just realize that dates are evaluated a the
> >> nanosecond accuracy, but the display has only the second as precision,
> >> thus this may be the reason of the warning while you see no difference.
> >> Unfortunately there is no way to get this information except restoring
> >> files.
> > 
> > 
> > The backups I register into the database are taken at a daily interval and
> > the files are unlikely to be touched.
> 
> thus, the removal date should not be the same as the creation date as 3 
> days passed in between...
> 
> [...]
> 
> > As you mention the directory:
> > $ dar_manager -B zdata_os_services_binhost_root.dmd -f usr/share/fonts/
> > liberation-fonts
> > 
> >          1       Thu Jun  3 15:32:10 2021  saved
> > 
> > absent
> > 
> >          2       Thu Jun  3 15:32:10 2021  present
> > 
> > absent
> > 
> >          3       Thu Jun  3 15:32:10 2021  present
> > 
> > absent
> > 
> >          4       Mon Apr  8 08:13:39 2024  present
> > 
> > absent
> > 
> > $ dar_manager -B zdata_os_services_binhost_root.dmd -f usr/share/fonts/
> > liberation-fonts/.uuid
> > 
> >          1       Thu Jun  3 15:32:10 2021  saved
> > 
> > absent
> > 
> >          2       Thu Jun  3 15:32:10 2021  present
> > 
> > absent
> > 
> >          3       Thu Jun  3 15:32:10 2021  present
> > 
> > absent
> > 
> >          4       Thu Jun  3 15:32:10 2021  removed
> > 
> > absent
> > 
> > The directory did get a new date, but the file has not been marked as
> > changed (if I read the output correctly)
> 
> yes, you do.
> 
> And this sounds really really weird! Though it does not explain the 
> original problem with dar_manager, it looks like an unexpected behavior 
> of dar, here, unless you make use of  -< -> -= options?

No, I don't, the commands I use are:

* full:
 /usr/bin/sudo /usr/bin/dar -m 256 -zbzip2:5 -s <slizesize> -D -R <backuproot> 
-c <dartarget> --user-comment <usercomment>
   --min-digits <zeropadding>,0,<zeropadding> -K <passphrase>
   -Z *.zip -Z *.gz -Z *.bz2 -Z *.cz -Z *.jar -Z *.rar -Z *.tgz -Z *.war -Z 
*.ear -Z *.rar -Z *.7z -Z *.tgz -Z *.tbz2 -Z *.avi -Z *.mkv -Z *.mp3
   -E "/opt/backups/etc/dar_par_create.duc %p %b %n %e %c 2"

* incremental:
/usr/bin/sudo /usr/bin/dar -m 256 -zbzip2:5 -s <slizesize> -D -R <backuproot> 
-c <dartarget> --user-comment <usercomment>
    --min-digits <zeropadding>,0,<zeropadding> -A <parent_catalogue> -K 
<passphrase>
    -Z *.zip -Z *.gz -Z *.bz2 -Z *.cz -Z *.jar -Z *.rar -Z *.tgz -Z *.war -Z 
*.ear -Z *.rar -Z *.7z -Z *.tgz -Z *.tbz2 -Z *.avi -Z *.mkv -Z *.mp3
    -E "/opt/backups/etc/dar_par_create.duc %p %b %n %e %c 2"

* create catalogue:
/usr/bin/sudo /usr/bin/dar --min-digits <zeropadding>,0,<zeropadding> -C 
<new_catalogue> -A <dartarget>

> Which dar and dar_manager version are used?

I use version 2.7.13.
Am planning on upgrading to 2.7.14 later this month.

> > As this particular partition and system is not too critical, I can share
> > the catalogues and database with you directly?
> 
> yes, you can, I'll have a look with the -x option just added to 
> dar_manager (git / master branch)
>
> >> what filesystem is used? Which option have been used to mount it?
> > 
> > 
> > The filesystem:
> > # mount
> > /dev/xvda1 on / type ext4 (rw,noatime,discard,stripe=2)
> 
> OK, the noatime does not explain the directory behavior it should not 
> concern mtime (which dar/dar_manager look at) but only atime, and ext4 
> is not known to have any limitation regarding mtime behavior AFAIK.

I haven't heard of any limitation there either.

> > I have several systems using the same distribution, but only this
> > particular one is showing the problem.
> 
> are they all using the same dar and dar_manager versions?

Yes, they all use the same dar and dar_manager versions.

--
Joost