Hello Ludwig, from the docker docs:
"This is indicated by the fact that the Data loop file and a Metadata loop file are on files under /var/lib/docker/devicemapper. These are loopback-mounted sparse files." Sparse files are really a problem to backup and restore. Regards Stefan Am 23.10.2017 um 21:03 schrieb Ludwig Waigel: > Hello Stefan, > > the machine has only one partition so it is hard to choose the wrong one. > > Meanwhile I found the issue systematically excluding certain directories from > the restoring process until it ran through. > > The server in question is using docker which some time ago has been migrated > to the latest version. However, the old version was using devicemapper as a > storage driver whereas the new version is using overlays. > > Long story short, within the backup the file > "/var/lib/docker/devicemapper/devicemapper/data" had a size about 160GB. The > original file that has been backuped had some 5GB. > > What is beyond me is the fact that the original 5GB file got backuped up > being 160GB in total and being restored as such. > > Cheers, > Ludwig > -- *CaC, Computer and Communication* Inhaber Stefan Klatt End-2-End Senior Network Consultant Triftstrasse 9 60528 Frankfurt Germany USt-IdNr.: DE260461592 Tel.: +49-(0)172-6807809 Tel.: +49-(0)69-67808-900 Fax: +49-(0)69-67808-837 Email: [email protected] Profil: http://www.cac-netzwerk.de/profil -- 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.
smime.p7s
Description: S/MIME Cryptographic Signature
