Am Freitag, den 21.07.2017, 13:50 -0700 schrieb Tomas Martišius:
>
> 2017 m. liepa 18 d., antradienis 13:09:57 UTC+3, Tom Weber rašė:
> >
> >
> > Hi there,
> >
> > I have a nice working bareos setup with bareos 15.2.2 on the backup
> > server side (debian 8 based). 20 filedaemons as clients (debian 7 /
> > 8 /
> > windows 2008) all working fine for months.
> >
> > A couple of weeks ago I upgraded a fileserver to debian 9 with the
> > included filedaemon 16.2.4-3.
> >
> > All appeared to be working fine without changes in the config
> > needed.
> >
> > Today I had to figure that after a restore of the debian 9 (bareos
> > 16.2.4 filedaemon) client all restored files are corrupt!
> >
> > This seems to happen during backup, since restores to a 15.2.2
> > filedaemon gives me the same broken files (verified by checksum).
> > The filesize is the same as the orignial.
> >
> > # ls -la /etc/mime.types /var/tmp/bareos-restores/etc/mime.types
> > -rw-r--r-- 1 root root 24301 Mai 1 2016 /etc/mime.types
> > -rw-r--r-- 1 root root 24301 Mai 1 2016 /var/tmp/bareos-
> > restores/etc/mime.types
> >
> > # md5sum /etc/mime.types /var/tmp/bareos-restores/etc/mime.types
> > 4561fade4c4fc48e526e72871c470eec /etc/mime.types
> > c42310a18b08a91f41590c157f6caa3c /var/tmp/bareos-
> > restores/etc/mime.types
> >
> > # head /etc/mime.types | hd
> > 00000000 23 23 23 23 23 23 23 23 23 23 23 23 23 23 23
> > 23 |################|
> > *
> > 00000040 23 23 23 23 23 23 23 23 23 23 23 23 23 23 23
> > 0a |###############.|
> > 00000050 23 0a 23 20 20 4d 49 4d 45 20 6d 65 64 69 61
> > 20 |#.# MIME media |
> > 00000060 74 79 70 65 73 20 61 6e 64 20 74 68 65 20 65 78 |types
> > and the ex|
> > 00000070 74 65 6e 73 69 6f 6e 73 20 74 68 61 74 20 72
> > 65 |tensions that re|
> > 00000080 70 72 65 73 65 6e 74 20 74 68 65 6d 2e 0a 23
> > 0a |present them..#.|
> > ....
> >
> > # head /var/tmp/bareos-restores/etc/mime.types | hd
> > 00000000 23 23 23 23 23 23 23 23 23 23 23 23 23 23 23
> > 23 |################|
> > *
> > 00000040 47 4a 3e aa d7 0d b3 09 df 22 40 10 39 1e 28
> > 7b |GJ>......"@.9.({|
> > 00000050 dc 25 f3 31 ea d7 04 f2 cb 43 46 f0 be f2 ad
> > 1d |.%.1.....CF.....|
> > 00000060 54 ad 85 41 1d 93 cb 96 23 72 eb 3f 9a 55 ae
> > f1 |T..A....#r.?.U..|
> > 00000070 05 da 93 71 f1 97 ad 87 06 88 a6 78 a6 2f 41
> > a9 |...q.......x./A.|
> > 00000080 b2 7d be a1 2d 4e 8e 1d 66 0a 41 ed 90 3d 37 dc |.}..-
> > N..f.A..=7.|
> > ....
> >
> > I've got TLS enabled on all communication.
> >
> > Is this a known problem?
> > Let me know if I can provide more info.
> >
> > Regards,
> > Tom
> We have the some problem in our backup. For now we don't find
> solution for this. I think there is similar problem as some time ago
> was reported and fixed in 14.2 bareos version:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788543
> https://bugs.bareos.org/view.php?id=437
> For some reason it become actual again.
That bug sounds different. My "system" backup with /etc/mime.types was
single volume and filesizes after restore don't differ, just corrupted
content.
Does this also happen for you if you use debian9 provided bareos on
server AND client? Might save me some testing on a friday night because
i need a working backup again asap :(
Tom
--
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.
