Re: Problem backing up: "no backup size line"
hi, > Now I get the following error: "no backup size line", in the log it looks > like this > > FAIL dumper 192.168.0.1 /boot 20171024230002 1 [no backup size line] >sendbackup: start [192.168.0.1:/boot level 1] >sendbackup: info BACKUP=/bin/tar >sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ... >sendbackup: info end >sendbackup: error [no backup size line] > PARTIAL chunker 192.168.0.1 /boot 20171024230002 1 [sec 0.174 kb 11 kps > 246.4] > > But I also do not know how to check this: GNU tar state file > /var/lib/amanda/gnutar-lists/XYZSOMETHING.new is corrupted. did you solve that problem by now? I’m not sure, but deleting the .new-file in /var/lib/amanda/gnutar-lists/ could help you with that. greets, Michael — Michael Müskens Cologne, Germany signature.asc Description: Message signed with OpenPGP using GPGMail
Re: amanda and pigz
Am 03.02.2014 um 15:35 schrieb Jean-Louis Martineau: Newer version have a '-a' option that do not needs human interaction. ah, I see that now, but I still have to move the data-Link to the needed tape? How can I then restore while a backup is running when not using multitape? which is rather fine in running automatically, unattended and with no need of an amanda-Database. As I understand, amrestore so far only has been a wrapper for dd if=file bs=32k skip=1? Why has this simple functionality been changed? It is a lot more that a simple dd. I'm sure it does, detecting in which way it was zipped and so on. As I wrote: No offense :) After having build 3.3.5, I'm still experiencing problems. I'm sorry, maybe I'm just blind :/ /michael -- BOFH excuse #283: Lawn mower blade in your fan need sharpening
Re: amanda and pigz
You can't use amrestore to directly read the dump from a vtape, use something like: amrestore -r file:/backup/tapepools/DailySet/DailySet-69 For that I would have to point the data-link to the needed tape? That is something I actually wanted to avoid :) or : amtape CONF label DailySet-69 amrestore -r file:/backup/tapepools/DailySet It is a lot easier to use amfetchdump: amfetchdump CONF tobak012.intern.backup.muessi.de /etc 20140128003001 That command obviously needs human interaction and has to be run as user backup? backup@tobak012:~/hoehoe$ amfetchdump DailySet tobak012.intern.backup.muessi.de /etc 20140128 1 volume(s) needed for restoration The following volumes are needed: DailySet-69 Press enter when ready I want to avoid that too. So far running amanda-2.6.1 I used to autorestore via amrestore -p tobak012.intern.backup.muessi.de |tar [option] - ./ which is rather fine in running automatically, unattended and with no need of an amanda-Database. As I understand, amrestore so far only has been a wrapper for dd if=file bs=32k skip=1? Why has this simple functionality been changed? No offense, just wondering :) /mm -- BOFH excuse #244: Your cat tried to eat the mouse.
Re: amanda and pigz
Hi guys, Use the '-r' argument of amrestore and manually uncompress the file with pigz or gzip I have a similar Problem with amanda-3.3.1 and with argument -r I get: root@tobak012:~/manual_restore/dussel# amrestore -r /backup/tapepools/DailySet/DailySet-69/3.tobak012.intern.backup.muessi.de._etc.0 Reading from '/backup/tapepools/DailySet/DailySet-69/3.tobak012.intern.backup.muessi.de._etc.0' split dumpfile: date 20140128003001 host tobak012.intern.backup.muessi.de disk /etc part 1/UNKNOWN lev 0 comp .gz program /bin/tar ERROR: unexpected header type 5 in holding file '/backup/tapepools/DailySet/DailySet-69/3.tobak012.intern.backup.muessi.de._etc.0' Extracting the dump via dd is working fine... Any suggestions? TIA Michael -- If you can put an axe through it, it's hardware; if you *want* to put an axe through it, it's software.
Re: holding disk not used?
Am 17.08.2011 um 18:00 schrieb Jean-Francois Malouin: * u...@3.am u...@3.am [20110817 11:54]: It appears that you are telling amanda to use -50GB of space for your holding diskwhy would you want a negative number? driver: pid 9802 ruid 111 euid 111 version 3.3.0: start at Wed Aug 17 11:36:39 2011 driver: pid 9802 ruid 111 euid 111 version 3.3.0: rename at Wed Aug 17 11:36:39 2011 driver: find_diskspace: want 1277107616 K driver: pid 9802 finish time Wed Aug 17 11:52:43 2011 hello, what does amcheck -l say? You usually get output like this: backup@tobak012:~$ amcheck DailySet -l Amanda Tape Server Host Check - Holding disk /backup/tapes/raid001/holdingdisk_DailySet: 43416 MB disk space available, using 17816 MB NOTE: skipping tape checks Server check took 0.001 seconds (brought to you by Amanda 3.3.0) If something is wrong with the holdingdisk, it should appear right there. /Michael -- Michael Müskens Rule #18: It's better to seek forgiveness than ask permission.
Problems with amanda-3.3.0 and amrestore
Hello everybody, since some time I've been testing amanda-3.3.0 but I'm still experiencing some troubles with using amrestore. First of all: Backups to virtual tapes do run fine and extracting backups via dd if=/backup/tapepools/DailySet/DailySet-15/00010.MYCLIENT._var_lib_amanda.0 bs=32k skip=1 |gzip -dc |tar xvf - ./ as specified in the header of the tapefile brings the correct and expected result. However, when I try to use amrestore the way I used to run in amanda-version 3.0.0, the command ends with some error messages I do not understand. For example: backup@MYSERVER:/backup/tapes/raid001/test$ amrestore -p /backup/tapepools/DailySet/DailySet-15/1.MYCLiENT._etc_amanda.0 | tar xvf - ./ Reading from '/backup/tapepools/DailySet/DailySet-15/1.MYCLIENT._etc_amanda.0' split dumpfile: date 20110801003001 host MYCLIENT disk /etc/amanda part 1/UNKNOWN lev 0 comp .gz program /bin/tar filter stderr: filter stderr: gzip: stdin: unexpected end of file ERROR: /bin/gzip exited with status 1 tar: This does not look like a tar archive tar: .: Not found in archive tar: Exiting with failure status due to previous errors The tar-errors are follow-ups of the original gzip error, I guess, after googling some, I did not really find some threads or solutions to solve this problem, maybe I'm missing something? Do I have to use some other options? I tried -h and some other stuff, but it didn't work :/ Testing the tapefile on a system with the old c-based amrestore, restoring works just fine, so I don't think the reason is the tapefile. I know that I can still use dd but actually I was quite happy with amrestore, so I'd like to keep for my automated restores :) If you need some more information please feel free to ask /Michael -- Michael Müskens Rule #18: It's better to seek forgiveness than ask permission.
Re: No Joy with 3.3.0
Am 03.06.2011 um 21:14 schrieb Steven Backus: I installed 3.3.0 and can't connect to any of my clients: WARNING: whimsy.med.utah.edu: selfcheck request failed: Connection refused WARNING: genepi.med.utah.edu: selfcheck request failed: Connection refused WARNING: episun7.med.utah.edu: selfcheck request failed: Connection refused WARNING: eclectic.med.utah.edu: selfcheck request failed: Connection refused WARNING: grandeur.med.utah.edu: selfcheck request failed: Connection refused WARNING: balance.med.utah.edu: selfcheck request failed: Connection refused WARNING: harmony.med.utah.edu: selfcheck request failed: Connection refused WARNING: clarity.med.utah.edu: selfcheck request failed: Connection refused WARNING: symmetry.med.utah.edu: selfcheck request failed: Connection refused WARNING: serendipity.med.utah.edu: selfcheck request failed: Connection refused WARNING: genepi.hci.utah.edu: selfcheck request failed: Connection refused WARNING: episun8.med.utah.edu: selfcheck request failed: Connection refused Client check: 13 hosts checked in 10.440 seconds. 12 problems found. hello, i figure it's this one: The default auth is changed to bsdtcp, if you are using the default bsd then you must add it to your configuration. /michael -- Michael Müskens Rule #18: It's better to seek forgiveness than ask permission.
