[Borgbackup] tag A or U when files are updated ?

[Thorsten Schöning]

Guten Tag Ernest Chiarello,
am Donnerstag, 2. September 2021 um 11:59 schrieben Sie:

> I then restart the same backup, in the same warehouse but with a
> different archive name (trial5). all the xml and bimg files are
> tagged U, like "updatedb", but the qcow2 image is still tagged A,
> even though it hasn't moved ... the VM has been shut down since April.

Sounds like the following, so carefully look at file time stamps:

> The files cache is used to determine whether Borg already “knows” /
> has backed up a file and if so, to skip the file from chunking. It
> intentionally excludes files that have a timestamp which is the same
> as the newest timestamp in the created archive.

You can make sure by creating an additional, small file in the backup
source folder:

> If you want to avoid unnecessary chunking, just create or touch a
> small or empty file in your backup source file set (so that one has
> the latest timestamp, not your 50GB VM disk image) and, if you do
> snapshots, do the snapshot after that.

https://borgbackup.readthedocs.io/en/stable/faq.html#i-am-seeing-a-added-status-for-an-unchanged-file

Mit freundlichen Grüßen

Thorsten Schöning

-- 
AM-SoFT IT-Service - Bitstore Hameln GmbH
Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK

E-Mail: Thorsten.Schoening at AM-SoFT.de
Web:    http://www.AM-SoFT.de/

Tel:   05151-  9468- 0
Tel:   05151-  9468-55
Fax:   05151-  9468-88
Mobil:  0178-8 9468-04

AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 221853 - Geschäftsführer: Janine Galonska