amanda 3.3beta: amrecover fails because of decompression?
Hello, after updating yesterday to 3.3beta amrecover shows: on linuxhost dumped with tar Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00070 now Continue [?/Y/n/s/d]? Y tar: Archive is compressed. Use -z option tar: Error is not recoverable: exiting now Extractor child exited with status 2 and solarishost dumped with star: Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00059 now Continue [?/Y/n/s/d]? Y Restoring files into directory /tmp All existing files in /tmp can be deleted Continue [?/Y/n]? Y /opt/csw/bin/star: Archive is 'gzip' compressed, try to use the -z option. Extractor child exited with status -1 Is there an option on client to enable decompression? Regards, Dennis -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Re: amanda 3.3beta: amrecover fails because of decompression?
Do the dump are compressed on client or server? Post the amrecover and amidxtaped debug files. As a workaround, you can do the following in amrecover before the extract: set property command-options -z Jean-Louis Dennis Benndorf wrote: Hello, after updating yesterday to 3.3beta amrecover shows: on linuxhost dumped with tar Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00070 now Continue [?/Y/n/s/d]? Y tar: Archive is compressed. Use -z option tar: Error is not recoverable: exiting now Extractor child exited with status 2 and solarishost dumped with star: Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00059 now Continue [?/Y/n/s/d]? Y Restoring files into directory /tmp All existing files in /tmp can be deleted Continue [?/Y/n]? Y /opt/csw/bin/star: Archive is 'gzip' compressed, try to use the -z option. Extractor child exited with status -1 Is there an option on client to enable decompression? Regards, Dennis
Re: amanda 3.3beta: amrecover fails because of decompression?
amrecover is 3.1.1, this is a compatibility issue.
Try the attached patch, You can manually patch the installed amidxtaped
script.
Jean-Louis
Dennis Benndorf wrote:
Hello Jean-Louis,
dumps are normally compressed on client-side (but there are a few exceptions).
See attached files.
Regards,
Dennis
Original-Nachricht
Datum: Tue, 19 Apr 2011 08:00:45 -0400
Von: Jean-Louis Martineau martin...@zmanda.com
An: Dennis Benndorf dennis.bennd...@gmx.de
CC: amanda-users@amanda.org
Betreff: Re: amanda 3.3beta: amrecover fails because of decompression?
Do the dump are compressed on client or server?
Post the amrecover and amidxtaped debug files.
As a workaround, you can do the following in amrecover before the extract:
set property command-options -z
Jean-Louis
Dennis Benndorf wrote:
Hello,
after updating yesterday to 3.3beta amrecover shows:
on linuxhost dumped with tar
Extracting files using tape drive changer on host dl380-54.gbv.de.
Load tape D00070 now
Continue [?/Y/n/s/d]? Y
tar: Archive is compressed. Use -z option
tar: Error is not recoverable: exiting now
Extractor child exited with status 2
and solarishost dumped with star:
Extracting files using tape drive changer on host dl380-54.gbv.de.
Load tape D00059 now
Continue [?/Y/n/s/d]? Y
Restoring files into directory /tmp
All existing files in /tmp can be deleted
Continue [?/Y/n]? Y
/opt/csw/bin/star: Archive is 'gzip' compressed, try to use the -z
option.
Extractor child exited with status -1
Is there an option on client to enable decompression?
Regards,
Dennis
diff --git a/server-src/amidxtaped.pl b/server-src/amidxtaped.pl
index dfbea94..c156a00 100644
--- a/server-src/amidxtaped.pl
+++ b/server-src/amidxtaped.pl
@@ -570,7 +570,8 @@ sub xfer_src_cb {
$header-{'clntcompprog'} = '';
}
} else {
- if ($dle-{'compress'} == $Amanda::Config::COMP_SERVER_FAST ||
+ if (!$self-{'their_features'}-has($Amanda::Feature::fe_amrecover_receive_unfiltered) ||
+ $dle-{'compress'} == $Amanda::Config::COMP_SERVER_FAST ||
$dle-{'compress'} == $Amanda::Config::COMP_SERVER_BEST) {
push @filters,
Amanda::Xfer::Filter::Process-new(
Re: amanda 3.3beta: amrecover fails because of decompression?
Hello Jean-Louis, thanks for the patch, seems to work now! Regards, Dennis Original-Nachricht Datum: Tue, 19 Apr 2011 09:39:08 -0400 Von: Jean-Louis Martineau martin...@zmanda.com An: Dennis Benndorf dennis.bennd...@gmx.de CC: amanda-users@amanda.org Betreff: Re: amanda 3.3beta: amrecover fails because of decompression? amrecover is 3.1.1, this is a compatibility issue. Try the attached patch, You can manually patch the installed amidxtaped script. Jean-Louis Dennis Benndorf wrote: Hello Jean-Louis, dumps are normally compressed on client-side (but there are a few exceptions). See attached files. Regards, Dennis Original-Nachricht Datum: Tue, 19 Apr 2011 08:00:45 -0400 Von: Jean-Louis Martineau martin...@zmanda.com An: Dennis Benndorf dennis.bennd...@gmx.de CC: amanda-users@amanda.org Betreff: Re: amanda 3.3beta: amrecover fails because of decompression? Do the dump are compressed on client or server? Post the amrecover and amidxtaped debug files. As a workaround, you can do the following in amrecover before the extract: set property command-options -z Jean-Louis Dennis Benndorf wrote: Hello, after updating yesterday to 3.3beta amrecover shows: on linuxhost dumped with tar Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00070 now Continue [?/Y/n/s/d]? Y tar: Archive is compressed. Use -z option tar: Error is not recoverable: exiting now Extractor child exited with status 2 and solarishost dumped with star: Extracting files using tape drive changer on host dl380-54.gbv.de. Load tape D00059 now Continue [?/Y/n/s/d]? Y Restoring files into directory /tmp All existing files in /tmp can be deleted Continue [?/Y/n]? Y /opt/csw/bin/star: Archive is 'gzip' compressed, try to use the -z option. Extractor child exited with status -1 Is there an option on client to enable decompression? Regards, Dennis -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone
amgtar set_euid Fixed Bug Broken Again
Please reference: http://old.nabble.com/Re%3A-amgtar-getting-Permission-denied-td28223185.html With Amanda 3.2.2 I am getting the symptom described in the web page above. I also notice that estimate, backup and restore code paths all are missing the appropriate seteuid(0)/setuid(0) code. Would someone with commit access on the community edition please commit the appropriate fix? Thank you, Trever Adams signature.asc Description: OpenPGP digital signature
Re: amgtar set_euid Fixed Bug Broken Again
The fix is already committed. If you have a similar problem, then make a new bug report with all relevant information including the amgtar debug file. Jean-Louis Trever L. Adams wrote: Please reference: http://old.nabble.com/Re%3A-amgtar-getting-Permission-denied-td28223185.html With Amanda 3.2.2 I am getting the symptom described in the web page above. I also notice that estimate, backup and restore code paths all are missing the appropriate seteuid(0)/setuid(0) code. Would someone with commit access on the community edition please commit the appropriate fix? Thank you, Trever Adams
Balancing dumps automatically?
Hello folks, Is there a way to get Amanda to balance automatically the full dumps for a given configuration? I'm using version 3.1.3 and here's a 'amadmin config balance' output: due-date #fsorig kB out kB balance -- 4/19 Tue 25 232452650 232452650 +107.4% 4/20 Wed 21 90997530 90997530-18.8% 4/21 Thu 20 39760030 39760030-64.5% 4/22 Fri 21 135107180 135107180+20.5% 4/23 Sat 20 39760030 39760030-64.5% 4/24 Sun 20 39760030 39760030-64.5% 4/25 Mon 20 39760030 39760030-64.5% 4/26 Tue 21 67242650 67242650-40.0% 4/27 Wed 21 298396590 298396590 +166.2% 4/28 Thu 22 109601030 109601030 -2.2% 4/29 Fri 22 65933810 65933810-41.2% 4/30 Sat 21 50985370 50985370-54.5% 5/01 Sun 28 78124620 78124620-30.3% 5/02 Mon 29 281192170 281192170 +150.9% -- TOTAL 311 1569073720 1569073720 112076694 DISTINCT51 1052193330 1052193330 (estimated 14 runs per dumpcycle) (20 filesystems overdue. The most being overdue 1 day.) Here's the pertinent section of my 'amanda.conf': inparallel 10 netusage 100 mbps maxdumps 2 dumpcycle 2 weeks runspercycle 14 tapecycle 16 tapes bumpsize 20 Mb bumpdays 1 bumpmult 4 I suppose that I could manually force a full dump on days were none or not many full dumps are scheduled... But I thought that I'd ask the question if there was a way of getting amanda do that automatically. Thanks! -- Luc Lalonde, analyste - Département de génie informatique: École polytechnique de Montréal (514) 340-4711 x5049 luc.lalo...@polymtl.ca -
Re: Balancing dumps automatically?
Luc Lalonde wrote: Hello folks, Is there a way to get Amanda to balance automatically the full dumps for a given configuration? Amanda do it by default. I'm using version 3.1.3 and here's a 'amadmin config balance' output: due-date #fsorig kB out kB balance -- 4/19 Tue 25 232452650 232452650 +107.4% 4/20 Wed 21 90997530 90997530-18.8% 4/21 Thu 20 39760030 39760030-64.5% 4/22 Fri 21 135107180 135107180+20.5% 4/23 Sat 20 39760030 39760030-64.5% 4/24 Sun 20 39760030 39760030-64.5% 4/25 Mon 20 39760030 39760030-64.5% 4/26 Tue 21 67242650 67242650-40.0% 4/27 Wed 21 298396590 298396590 +166.2% 4/28 Thu 22 109601030 109601030 -2.2% 4/29 Fri 22 65933810 65933810-41.2% 4/30 Sat 21 50985370 50985370-54.5% 5/01 Sun 28 78124620 78124620-30.3% 5/02 Mon 29 281192170 281192170 +150.9% -- TOTAL 311 1569073720 1569073720 112076694 DISTINCT51 1052193330 1052193330 (estimated 14 runs per dumpcycle) (20 filesystems overdue. The most being overdue 1 day.) amanda can't balance if the tape size is too small, you could increase runtapes. amanda can't balance if maxpromoteday is set to a small value. amanda might have some problem balancing the bigger dle, manual force can help. You have 51 dles and amanda plan 311 full in the next dumpcycle days!!! Do you have dles that you force full more often? Jean-Louis
Re: Balancing dumps automatically?
Hello Jean-Louis, I've not done a 'force' in a long time... However, I've added some new DLE's recently. So by default they've entered the cycle with a 'level 0'. Maybe that's why the backups are not balanced... It still strange that Amanda plans to do 311 full dumps during the cycle! Any ideas why I'm getting this? And 'maxpromoteday' is not specified in my configuration. So it must be using the default value of '1000'. Bye. - Original Message - From: Jean-Louis Martineau martin...@zmanda.com To: Luc Lalonde luc.lalo...@polymtl.ca Cc: amanda-users@amanda.org Sent: Tuesday, April 19, 2011 4:15:50 PM GMT -05:00 US/Canada Eastern Subject: Re: Balancing dumps automatically? Luc Lalonde wrote: Hello folks, Is there a way to get Amanda to balance automatically the full dumps for a given configuration? Amanda do it by default. I'm using version 3.1.3 and here's a 'amadmin config balance' output: due-date #fsorig kB out kB balance -- 4/19 Tue 25 232452650 232452650 +107.4% 4/20 Wed 21 90997530 90997530-18.8% 4/21 Thu 20 39760030 39760030-64.5% 4/22 Fri 21 135107180 135107180+20.5% 4/23 Sat 20 39760030 39760030-64.5% 4/24 Sun 20 39760030 39760030-64.5% 4/25 Mon 20 39760030 39760030-64.5% 4/26 Tue 21 67242650 67242650-40.0% 4/27 Wed 21 298396590 298396590 +166.2% 4/28 Thu 22 109601030 109601030 -2.2% 4/29 Fri 22 65933810 65933810-41.2% 4/30 Sat 21 50985370 50985370-54.5% 5/01 Sun 28 78124620 78124620-30.3% 5/02 Mon 29 281192170 281192170 +150.9% -- TOTAL 311 1569073720 1569073720 112076694 DISTINCT51 1052193330 1052193330 (estimated 14 runs per dumpcycle) (20 filesystems overdue. The most being overdue 1 day.) amanda can't balance if the tape size is too small, you could increase runtapes. amanda can't balance if maxpromoteday is set to a small value. amanda might have some problem balancing the bigger dle, manual force can help. You have 51 dles and amanda plan 311 full in the next dumpcycle days!!! Do you have dles that you force full more often? Jean-Louis -- Luc Lalonde, analyste - Département de génie informatique: École polytechnique de Montréal (514) 340-4711 x5049 luc.lalo...@polymtl.ca -
Re: Balancing dumps automatically?
Luc Lalonde wrote: Hello Jean-Louis, I've not done a 'force' in a long time... However, I've added some new DLE's recently. So by default they've entered the cycle with a 'level 0'. Maybe that's why the backups are not balanced... It still strange that Amanda plans to do 311 full dumps during the cycle! Any ideas why I'm getting this? Do you have dle with 'strategy noinc' or with a smaller dumpcycle? 'amadmin CONF disklist' print it. Jean-Louis
