On 07/15/16 12:16 PM, Robert N wrote: > Hi, > > I tried to restore a current state, which involves a Full backup from 09.07 > and subsequent Incrementals from 11.07, 12.07, 13.07, 14.07, 15.07. some > hardlinks changed on 13.07 and bareos reports errors for the old files, the > ones before 13.07 which shouldn't be restored anyway. > > ex. > > on 09.07 ( jobid 616 ) backup contained: > > > [root@backup-1 bareos-restore]# echo list files jobid=616 | bconsole | egrep > "8c6213dcfe55982fec72226d3fd4b62b5829e0d6|6b55f578ead1fc8044dfba12758c3285bab6df5a" > /var/lib/yum/yumdb/i/8c6213dcfe55982fec72226d3fd4b62b5829e0d6-initscripts-9.03.53-1.el6.centos-x86_64/releasever > > on 14.07 ( jobid 774 ) the file is already gone, and there's another file ( > notice the difference in the checksum before initscripts ), hardlink to the > same as the old one > > [root@backup-1 bareos-restore]# echo list files jobid=774 | bconsole | egrep > "8c6213dcfe55982fec72226d3fd4b62b5829e0d6|6b55f578ead1fc8044dfba12758c3285bab6df5a" > > /var/lib/yum/yumdb/i/6b55f578ead1fc8044dfba12758c3285bab6df5a-initscripts-9.03.53-1.el6.centos.1-x86_64/releasever > > on 15.07 try to restore the current state to /data/bareos-restore/20160715, > and get the following error for all gone hardlinks: > > 15-Jul 10:06 muc1pro-backup-1-fd JobId 862: Error: create_file.c:341 Could > not hard link > /data2/bareos-restore/20160715/var/lib/yum/yumdb/i/8c6213dcfe55982fec72226d3fd4b62b5829e0d6-initscripts-9.03.53-1.el6.centos-x86_64/releasever > -> > /data2/bareos-restore/20160715/var/lib/yum/yumdb/l/7053e34722803b2f52096d231ccd5050d2341ecf-libxml2-python-2.7.6-20.el6_7.1-x86_64/releasever: > ERR=No such file or directory > > [root@backup-1 bareos-storage]# ll > /data2/bareos-restore/20160715/var/lib/yum/yumdb/l/7053e34722803b2f52096d231ccd5050d2341ecf-libxml2-python-2.7.6-20.el6_7.1-x86_64/releasever > -rw-r--r-- 177 root root 1 Jul 27 2015 > /data2/bareos-restore/20160715/var/lib/yum/yumdb/l/7053e34722803b2f52096d231ccd5050d2341ecf-libxml2-python-2.7.6-20.el6_7.1-x86_64/releasever > > > [root@backup-1 bareos-storage]# ll > /data2/bareos-restore/20160715/var/lib/yum/yumdb/i/8c6213dcfe55982fec72226d3fd4b62b5829e0d6-initscripts-9.03.53-1.el6.centos-x86_64/releasever > ls: cannot access > /data2/bareos-restore/20160715/var/lib/yum/yumdb/i/8c6213dcfe55982fec72226d3fd4b62b5829e0d6-initscripts-9.03.53-1.el6.centos-x86_64/releasever: > No such file or directory > > > the file in question has 177 hardlinks on the client: > > > [root@client ~]# stat > /var/lib/yum/yumdb/i/6b55f578ead1fc8044dfba12758c3285bab6df5a-initscripts-9.03.53-1.el6.centos.1-x86_64/releasever > File: > `/var/lib/yum/yumdb/i/6b55f578ead1fc8044dfba12758c3285bab6df5a-initscripts-9.03.53-1.el6.centos.1-x86_64/releasever' > Size: 1 Blocks: 8 IO Block: 4096 regular file > Device: fc03h/64515d Inode: 132164 Links: 177 > Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) > Access: 2016-07-15 10:21:58.136351385 +0200 > Modify: 2015-07-27 11:30:20.340459782 +0200 > Change: 2016-07-13 21:09:10.742323401 +0200 > > Why does Bareos try to create the hardlink if it was in the meantime deleted? > In the end the behavior is correct, becuase it doesn't create the hardlink, > but throws errors during restore, which leads to concerns.... >
Because that is how it work without the accurate mode. Try reading the docs on accurate. So it works exactly as it should and so do most other backup products e.g. replaying full, diff, incr backups. I'm pretty sure its even documented behavior. -- Marco van Wieringen [email protected] Bareos GmbH & Co. KG Phone: +49-221-63069389 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz, M. v. Wieringen -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
