Re: still problems with manual tape changer using tapespan
On 02/20/2013 07:07 AM, Jean-Louis Martineau wrote: On 02/20/2013 06:59 AM, Karsten Fuhrmann wrote: Hello Jean-Louis, should i apply the path on trunk or release 3.3.3? The patch apply to trunk and the 3-3 branch, I haven't tested if apply cleanly on the release 3.3.3 but I think it should. Karsten, Let me know if the patch works for you. Jean-Louis
Re: includefile in disklist
On 02/25/2013 06:55 AM, Nuno Dias wrote:
Hi,
In amanda-3.3.2 if I use includefile directive in disklist, that
directive must be the first thing in the file, and only one includefile
is allowed, this is a feature or a bug?
Cheers,
Nuno
It is a bug, the attached patch fix it.
Jean-Louis
diff --git a/server-src/diskfile.c b/server-src/diskfile.c
index d8e11dc..91e27db 100644
--- a/server-src/diskfile.c
+++ b/server-src/diskfile.c
@@ -38,7 +38,7 @@
#include util.h
#include amxml.h
-static am_host_t *hostlist;
+static am_host_t *hostlist = NULL;
static netif_t *all_netifs;
/* local functions */
@@ -58,8 +58,9 @@ read_diskfile(
char *line = NULL;
/* initialize */
-hostlist = NULL;
-lst-head = lst-tail = NULL;
+if (hostlist == NULL) {
+ lst-head = lst-tail = NULL;
+}
line_num = 0;
/* if we already have config errors, then don't bother */
Re: Is this possible with Amanda 3.3?
On 03/02/2013 01:01 PM, Joseph Cheng wrote: I have been looking at mailing list archives but I am not sure if this is possible or not. please advise. 1. Specify only certain directories per host to be backed up. Not global list of directories configured on server and then excludes on clients. 2. From client use amrecover to fetch any host's last full, sucessful backup in an automatted way without browsing with the ftp like client or answering questions. All from vtape and no physical tape devices. Example amrecover -h restorehost.domain.com http://restorehost.domain.com DailySet1 /restore/path amrecover is an interactive program. A patch that allow all command to be set on the command line will be accepted. To automate it, you can create a small file (/tmp/recover-cmd): sethost HOST setdisk DLE add . extract y y y y y y quit and run: cd /path/where/to/recover ; amrecover CONF /tmp/recover-cmd Be sure to be on the right directory before running amrecover, it can remove everything in it. Jean-Louis #2 is critical in virtual machine envrionment. Old virtual machine is gone, new one created, then automation tool runs the amrecover command to download the last full backup for the virtual machine that is being replaced. Is this possible?
Re: Is this possible with Amanda 3.3?
On 03/03/2013 03:17 PM, Jon LaBadie wrote: On Sun, Mar 03, 2013 at 02:32:24PM -0500, Joseph Cheng wrote: 2. From client use amrecover to fetch any host's last full, sucessful backup in an automatted way without browsing with the ftp like client or answering questions. All from vtape and no physical tape devices. Example amrecover -h restorehost.domain.com DailySet1 /restore/path amrestore might be more appropriate FRom what I see amrestore and amfetchdump run on Amanda server and not on the VM that is remotely requesting backup data. correct? This would be difficulet to make work in a setting where different VM need backups on demand without manual work on the backup server to assemble the data :( Someone will correct me if I'm wrong, but I believe amrestore and amfetchdump can be run from the linux client. They can't, they must be run on the amanda server. Jean-Louis
Re: Tape drive problem?
Leslie, chg-zd-mtx is deprecated, try to use the 'robot' changer instead. taper: FATAL TypeError in method 'log_add', argument 2 of type 'char *' A fix for this bug was already posted, or you can try to upgrade to 3.3.3 Jean-Louis On 03/07/2013 01:58 PM, Leslie(Pete) Boyd wrote: Hello, Amanda version is 3.3.0. OS is CentOS release 5.9 (Final) Tape device is a SL500 with 3 LT05 drives Amanda report is attached. All dumps are level 0, rsync to disk is used for level 9s. After using /dev/nst2 for 4 complete tapes, the process aborts with: USAGE BY TAPE: Label Time Size % DLEs Parts AMADSet13a-572 7:48 1471706336K 99.4 136 AMADSet13a-560 6:47 1458516864K 98.5 035 AMADSet13a-561 7:08 1480924640K 100.0 036 AMADSet13a-562 7:48 1443092096K 97.5 035 FAILED DUMP DETAILS: /-- node35bk.rtpnc.epa.gov /13w lev 0 FAILED [data write: Broken pipe] sendbackup: start [node35bk.rtpnc.epa.gov:/13w level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ... sendbackup: info end \ NOTES: planner: Adding new disk node35bk.rtpnc.epa.gov:/13w. driver: Taper protocol error driver: going into degraded mode because of taper component error. taper: Slot 41 with label AMADSet13a-572 is usable taper: tape AMADSet13a-572 kb 1471706336 fm 36 [OK] taper: Slot 29 with label AMADSet13a-560 is usable taper: tape AMADSet13a-560 kb 1458516864 fm 35 [OK] taper: Slot 30 with label AMADSet13a-561 is usable taper: tape AMADSet13a-561 kb 1480924640 fm 36 [OK] taper: Slot 31 with label AMADSet13a-562 is usable taper: tape AMADSet13a-562 kb 1443092096 fm 35 [OK] taper: could not determine current slot, are you sure your drive slot is 2 I suspect that my configuration is not supporting the tape changer properly. Anytime multiple requests are made to the changer, one of the amanda jobs will fail with: node35bk.rtpnc.epa.gov /13w lev 0 FAILED [data write: Broken pipe] Any suggestions on getting this problem resolved would be greatly appreciated. Thanks in advance...have a nice day! ** Leslie(Pete) Boyd Contractor: The rich man isn't the one who has the most, Vision Technoligies but the one who needs the least. Senior Systems Engineer US EPA Rm. E460--- IN GOD WE TRUST -- 919/541-1438 **
Re: Upgraded from 3.3.0 to 3.3.3
Which mtx operation failed? Post the taper debug file.
Jean-Louis
On 03/12/2013 05:13 PM, Leslie(Pete) Boyd wrote:
Hello,
Can anyone suggest a solution to this problem?
I upgraded from 3.3.0 to 3.3.3 in order to use the
hp-robot changer.
Amcheck does not report any problems.
Amanda fails with:
Date: March 12, 2013
These dumps were to tape AMADSet13a-563.
The next 15 tapes Amanda expects to use are: 14 new tapes, AMADSet13a-563.
The next 14 new tapes already labelled are: AMADSet13a-560, AMADSet13a-561,
AMADSet13a-562, AMADSet13a-564, AMADSet13a-565, AMADSet13a-566, AMADSet13a-567,
AMADSet13a-568, AMADSet13a-569, AMADSet13a-570, AMADSet13a-571, AMADSet13a-572,
AMADSet13a-573, AMADSet13a-574
FAILURE DUMP SUMMARY:
node35bk.rtpnc.epa.gov /13w lev 0 FAILED [can't dump 'holdingdisk never' dle
in degraded mode]
node35bk.rtpnc.epa.gov /13w lev 0 FAILED [data write: Connection reset by
peer]
node35bk.rtpnc.epa.gov /13w lev 0 partial taper: error from mtx: destination
Element Address 500 is Already Full
STATISTICS:
Total Full Incr. Level:#
Estimate Time (hrs:min) 0:01
Run Time (hrs:min) 0:27
Dump Time (hrs:min) 0:00 0:00 0:00
Output Size (meg)0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
DLEs Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min) 0:25 0:25 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%)0.00.00.0
DLEs Taped 1 1 0
Parts Taped1 1 0
Avg Tp Write Rate (k/s) 0.00.0--
USAGE BY TAPE:
Label Time Size % DLEs Parts
AMADSet13a-563 0:0717550496K1.2 1 1
FAILED DUMP DETAILS:
/-- node35bk.rtpnc.epa.gov /13w lev 0 FAILED [data write: Connection reset by
peer]
sendbackup: start [node35bk.rtpnc.epa.gov:/13w level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -xpGf - ...
sendbackup: info end
\
NOTES:
planner: Adding new disk node35bk.rtpnc.epa.gov:/13w.
taper: Slot 4 with label AMADSet13a-563 is usable
taper: Will request retry of failed split part.
taper: tape AMADSet13a-563 kb 0 fm 1 [OK]
taper: error from mtx: destination Element Address 500 is Already Full
taper: error from mtx: destination Element Address 500 is Already Full
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s
MMM:SS KB/s
-
-
node35bk.rtpnc.epa.gov /13w0 --PARTIAL
25:190.0 PARTIAL
(brought to you by Amanda version 3.3.3)
Thanks in advance...have a nice day!
**
Leslie(Pete) Boyd
Contractor: The rich man isn't the one who has the most,
Vision Technoligies but the one who needs the least.
Senior Systems Engineer
US EPA Rm. E460--- IN GOD WE TRUST --
919/541-1438
**
Re: Upgraded from 3.3.0 to 3.3.3
Amanda think the tape is unloaded when it is not, uncomment the
load-poll property and increase some of the time.
You can also try to set the EJECT-BEFORE-UNLOAD and EJECT-DELAY properties.
uncomment your tape-device properties and amanda should use the 3 drives.
Set 'taper-parallel-write 3' if you want amanda to use them in parallel.
man amanda-changers
man amanda.conf
Jean-Louis
On 03/13/2013 10:44 AM, Leslie(Pete) Boyd wrote:
Hello,
Thanks for the prompt response.
Made changes to the amanda.conf file this AM and ran the job
again.
Taper log file is attached.
Output of the amreport is attached.
The amanda.conf file is attached. Please have a look at the
changer section of this file and let me know how it should be
coded for my 3 tape system.
FYI: OS is CentOS 5.9.
Tape drive is SUN Sl500 with 3 LT05 drives.
Thanks again for your assistance...have a nice day!
X-Authentication-Warning: guinness.omniscient.com: majordom set sender to
owner-amanda-us...@amanda.org using -f
X-Virus-Scanned: clamav-milter 0.97.3-exp at guinness.omniscient.com
Date: Wed, 13 Mar 2013 07:58:13 -0400
From: Jean-Louis Martineau martin...@zmanda.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110
Thunderbird/17.0.2
MIME-Version: 1.0
To: Leslie(Pete) Boyd l...@hpcc.epa.gov
CC: amanda-users@amanda.org, hpcc_supp...@hpcc.epa.gov
Subject: Re: Upgraded from 3.3.0 to 3.3.3
Content-Transfer-Encoding: 7bit
X-Virus-Status: Clean
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7
(guinness.omniscient.com [127.0.0.1]); Wed, 13 Mar 2013 08:07:02 -0400 (EDT)
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7
(guinness.omniscient.com [127.0.0.1]); Wed, 13 Mar 2013 07:58:23 -0400 (EDT)
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7
(guinness.omniscient.com [205.129.9.5]); Wed, 13 Mar 2013 07:58:22 -0400 (EDT)
List-Id: amanda-users.amanda.org
List-Id: amanda-users.amanda.org
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data:
2013.3.13.115715
X-PerlMx-Spam: Gauge=, Probability=8%, Report=' MULTIPLE_RCPTS 0.1,
HTML_00_01 0.05, HTML_00_10 0.05, BODY_SIZE_3000_3999 0, BODY_SIZE_5000_LESS 0,
BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0,
__BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG
0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __LINES_OF_YELLING 0,
__MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __MOZILLA_USER_AGENT 0,
__MULTIPLE_RCPTS_CC_X2 0, __RUS_OBFU_PHONE 0, __SANE_MSGID 0,
__SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_NO_MAILTO 0, __URI_NO_PATH 0,
__URI_NO_WWW 0, __URI_NS , __USER_AGENT 0, __cbl.abuseat.org_ERROR '
Which mtx operation failed? Post the taper debug file.
Jean-Louis
On 03/12/2013 05:13 PM, Leslie(Pete) Boyd wrote:
Hello,
Can anyone suggest a solution to this problem?
I upgraded from 3.3.0 to 3.3.3 in order to use the
hp-robot changer.
Amcheck does not report any problems.
Amanda fails with:
Date: March 12, 2013
These dumps were to tape AMADSet13a-563.
The next 15 tapes Amanda expects to use are: 14 new tapes, AMADSet13a-563.
The next 14 new tapes already labelled are: AMADSet13a-560, AMADSet13a-561,
AMADSet13a-562, AMADSet13a-564, AMADSet13a-565, AMADSet13a-566,
AMADSet13a-567,
AMADSet13a-568, AMADSet13a-569, AMADSet13a-570, AMADSet13a-571,
AMADSet13a-572,
AMADSet13a-573, AMADSet13a-574
FAILURE DUMP SUMMARY:
node35bk.rtpnc.epa.gov /13w lev 0 FAILED [can't dump 'holdingdisk never'
dle
in degraded mode]
node35bk.rtpnc.epa.gov /13w lev 0 FAILED [data write: Connection reset
by
peer]
node35bk.rtpnc.epa.gov /13w lev 0 partial taper: error from mtx:
destination
Element Address 500 is Already Full
STATISTICS:
Total Full Incr. Level:#
Estimate Time (hrs:min) 0:01
Run Time (hrs:min) 0:27
Dump Time (hrs:min) 0:00 0:00 0:00
Output Size (meg)0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
DLEs Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min) 0:25 0:25 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%)0.00.00.0
DLEs Taped 1 1 0
Parts Taped1 1 0
Avg Tp Write Rate (k/s) 0.00.0--
USAGE BY TAPE:
Label Time Size % DLEs Parts
AMADSet13a-563 0:0717550496K1.2 1 1
FAILED DUMP DETAILS:
/-- node35bk.rtpnc.epa.gov
Re: Amanda Performance
Compression is often a CPU bottleneck, did you check for cpu usage? You can try to use pigz instead of gzip if you have available core. How many dump are you doing in parallel? You can try to increase inparallel, netusage and/or maxdumps. You can use amplot and amstatus to check amanda performance. Jean-Louis On 03/13/2013 10:44 PM, Amit Karpe wrote: Hi all, I am using Amanda to take backup weekly monthly. For monthly backup which is 2.5 to 2.7TB in size after backup with compression, it take 4-5 days. (Total size is around 6-7 TB, and there 52 entries DLEs, from 10 different host in network. I am backuping on NAS, where I have 19T total space.) Off course there are various parameter we have to consider to claim whether it is slow process or not. Could you please let me know how should I check and compare whether my backup process is slow or not ? Which are main parameter which affect Amanda Performance ? Which tool I should use to check Amanda Performance ? Currently I am using following steps: 1. I have started monthly backup. 2. Using bandwidth monitoring tools i.e. ntop, bmon I am checking Backup Server to NAS bandwidth usage trafic status. 3. Using iotop I am checking status / speed of io operation. 4. There are other few tools, which may help to understand io, had disk usage. But as my backup directory is not a local device, (I have mounted as nfs directory) I can't run hdparm or iostat directly. 5. Monitoring NAS's admin interface for its bandwidth usage. 6. Currently I am checking for some spastics, which help to compare with my current setup. Still I can't understand whether I going right way or not ! It will be if you help me here. -- Regards Amit Karpe. http://www.amitkarpe.com/ http://news.karpe.net.in/
Re: timeout of amrecover
There is no timeout in amrecover, it can wait for days. Amrecover detect the error when the system return the error. Jean-Louis On 03/22/2013 05:25 AM, Nagai Megumu wrote: Hello I want you to teach about timeout of amrecover. Execution a restore using the amrecover,time out network disconnected later.But, it takes about 2 hours of time before it times out. Work procedure 1.Run the extract in amrecover 2.While restoring files, the backup server and backup client Unplug the LAN cable that connects 3.Check time out. Usage environment 【backup server】 - os Ubuntu 12.04 LTS - architecture x86_64 - hdd Disk /dev/sda: 160.0 GB, 160041885696 bytes - cpu model name: AMD Athlon(tm) 64 Processor 3500+ processor: 0 - mem MemTotal: 3083604 kB - amanda 3.3.1 【backup client】 - os Ubuntu 12.04.2 LTS - architecture i386 - hdd Disk /dev/sda: 160.0 GB, 160041885696 bytes - cpu model name: Intel(R) Pentium(R) 4 CPU 3.20GHz processor: 0〜1 - mem MemTotal: 1018236 kB - amanda 3.3.1 amrecover.MMDDhhmmss.debug(some excerpt) - Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: tar Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: --ignore-zeros Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: --numeric-owner Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: -xpGvf Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: - Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-1 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-10 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-11 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-12 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-13 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-14 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-15 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-16 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-17 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-18 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-19 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-2 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-20 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-3 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-4 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-5 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-6 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-7 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-8 Thu Mar 21 23:11:45 2013: thd-0x88a2c00: amrecover: ./data-9 Thu Mar 21 23:11:53 2013: thd-0x88a2c00: amrecover: stream_read_callback: data is still flowing Thu Mar 21 23:12:04 2013: thd-0x88a2c00: amrecover: stream_read_callback: data is still flowing *2 hours time out Fri Mar 22 01:23:27 2013: thd-0x88a2c00: amrecover: stream_read_callback: data is still flowing Fri Mar 22 01:23:27 2013: thd-0x88a2c00: amrecover: security_stream_seterr(0x88e0800, recv error: Connection timed out) gzip: stdin: unexpected end of file
Re: S3 backups stalling
Stefan, Add device-property verbose yes re-run a backup and post the taper debug file. Jean-Louis On 03/25/2013 10:00 AM, Stefan G. Weichinger wrote: Do I miss something? I got my amazon-AWS-account and try to run amanda with S3-backend as mentioned at http://wiki.zmanda.com/index.php/How_To:Backup_to_Amazon_S3#New_chg-multi_.28Amanda_3.1_and_later.29 I can amcheck and amlabel correctly ... but amdump and amflush seem to get stuck somehow. $ amstatus s3 Using /usr/adm/amanda/s3/amflush mythtv.oops.intern:/etc 0 4m flushing to tape (1m done (37.54%)) sits there for long time ... nothing else happens. I retried with S3_SSL set to No to check things, no difference. This is amanda-3.3.3 on gentoo linux ... see the following logs. Thanks for any help, Stefan -- $ cat log INFO amflush amflush pid 24200 DISK amflush mythtv.oops.intern /etc DISK amflush mythtv.oops.intern /etc DISK amflush mythtv.oops.intern /etc DISK amflush mythtv.oops.intern /etc START amflush date 20130325144427 INFO driver driver pid 24202 START driver date 20130325144427 STATS driver hostname amanda STATS driver startup time 0.024 INFO taper taper pid 24203 INFO taper Slot 6 with label s3-6 is not reusable INFO taper Slot 7 with label s3-7 is usable START taper datestamp 20130325144427 label s3-7 tape 1 $ cat amflush amflush: start at Mon Mar 25 14:44:29 CET 2013 amflush: datestamp 20130325144427 amflush: starttime 20130325144427 amflush: starttime-locale-independent 2013-03-25 14:44:29 CET FLUSH mythtv.oops.intern /etc 20130325102147 0 /mnt/amhold/s3/20130325102147/mythtv.oops.intern._etc.0 FLUSH mythtv.oops.intern /etc 20130325114341 1 /mnt/amhold/s3/20130325114341/mythtv.oops.intern._etc.1 FLUSH mythtv.oops.intern /etc 20130325115229 1 /mnt/amhold/s3/20130325115229/mythtv.oops.intern._etc.1 FLUSH mythtv.oops.intern /etc 20130325124222 0 /mnt/amhold/s3/20130325124222/mythtv.oops.intern._etc.0 ENDFLUSH driver: pid 24202 executable driver version 3.3.3 driver: tape size 10485760 driver: adding holding disk 0 dir /mnt/amhold/s3 size 64786432 chunksize 10485760 reserving 0 out of 64786432 for degraded-mode dumps driver: send-cmd time 0.024 to taper: START-TAPER worker0 20130325144427 driver: start time 0.024 inparallel 8 bandwidth 1002600 diskspace 64786432 dir OBSOLETE datestamp 20130325144427 driver: drain-ends tapeq LARGESTFIT big-dumpers driver: state time 0.024 free kps: 1002600 space: 64786432 taper: idle idle-dumpers: 8 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: not-idle driver: interface-state time 0.024 if default: free 8 if eth0: free 921600 if local: free 1000 driver: hdisk-state time 0.024 hdisk 0: free 64786432 dumpers 0 driver: state time 2.243 free kps: 1002600 space: 64786432 taper: idle idle-dumpers: 8 qlen tapeq: 4 runq: 0 roomq: 0 wakeup: 0 driver-idle: not-idle driver: interface-state time 2.243 if default: free 8 if eth0: free 921600 if local: free 1000 driver: hdisk-state time 2.243 hdisk 0: free 64786432 dumpers 0 driver: result time 2.243 from taper: TAPER-OK worker0 driver: send-cmd time 2.244 to taper: FILE-WRITE worker0 00-1 /mnt/amhold/s3/20130325102147/mythtv.oops.intern._etc.0 mythtv.oops.intern /etc 0 20130325102147 14320 driver: startaflush: LARGESTFIT mythtv.oops.intern /etc 4423 0 driver: state time 2.244 free kps: 1002600 space: 64786432 taper: writing idle-dumpers: 8 qlen tapeq: 3 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers driver: interface-state time 2.244 if default: free 8 if eth0: free 921600 if local: free 1000 driver: hdisk-state time 2.244 hdisk 0: free 64786432 dumpers 0 taper: status file mythtv.oops.intern /etc:/var/tmp/amanda/taper_status_file_NAGqED driver: state time 2.264 free kps: 1002600 space: 64786432 taper: writing idle-dumpers: 8 qlen tapeq: 3 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers driver: interface-state time 2.264 if default: free 8 if eth0: free 921600 if local: free 1000 driver: hdisk-state time 2.264 hdisk 0: free 64786432 dumpers 0 driver: result time 2.264 from taper: REQUEST-NEW-TAPE 00-1 driver: send-cmd time 2.264 to taper: START-SCAN worker0 00-1 driver: send-cmd time 2.264 to taper: NEW-TAPE worker0 00-1 taper: wrote label 's3-7' driver: state time 3.219 free kps: 1002600 space: 64786432 taper: writing idle-dumpers: 8 qlen tapeq: 3 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers driver: interface-state time 3.219 if default: free 8 if eth0: free 921600 if local: free 1000 driver: hdisk-state time 3.219 hdisk 0: free 64786432 dumpers 0 driver: result time 3.220 from taper: NEW-TAPE 00-1 s3-7
Re: flush-threshold-* parameters - some clarification needed.
On 03/27/2013 06:39 AM, Kamil Jońca wrote: (This is duplicate mail, previously sent, but I weren't subscribed) In some sites there is suggestion, that config: --8---cut here---start-8--- #flush-threshold-dumped 100 # (or more) #flush-threshold-scheduled 100 # (or more) #taperflush 100 #autoflush yes --8---cut here---end---8--- helps to do better tape utilization. But how behave amanda in my configuration (+ these four lines above): I have defined 1gb vtapes, placed onto four hard disks rotated (ie. first flush go to disk 1, second to 2, third to 3, fourth to 4, fifth to 1, and so on) say on first disk are tapes: alfa-1-1 to alfa-1-10 on second: alfa-2-1 to alfa-2-10 on third: alfa-3-1 to alfa-3-10 on fourth: alfa-4-1 to alfa-4-10 One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially) alfa-1-2. Amanda should not write to alfa-1-2 if the above setting are commented out. Are you using a holding a disk? It must be larger than a vtape (1gb). Jean-Louis
Re: flush-threshold-* parameters - some clarification needed.
On 03/27/2013 08:58 AM, Kamil Jońca wrote: Jean-Louis Martineau martin...@zmanda.com writes: On 03/27/2013 06:39 AM, Kamil Jońca wrote: (This is duplicate mail, previously sent, but I weren't subscribed) In some sites there is suggestion, that config: --8---cut here---start-8--- #flush-threshold-dumped 100 # (or more) #flush-threshold-scheduled 100 # (or more) #taperflush 100 #autoflush yes --8---cut here---end---8--- helps to do better tape utilization. But how behave amanda in my configuration (+ these four lines above): I have defined 1gb vtapes, placed onto four hard disks rotated (ie. first flush go to disk 1, second to 2, third to 3, fourth to 4, fifth to 1, and so on) say on first disk are tapes: alfa-1-1 to alfa-1-10 on second: alfa-2-1 to alfa-2-10 on third: alfa-3-1 to alfa-3-10 on fourth: alfa-4-1 to alfa-4-10 One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially) alfa-1-2. Amanda should not write to alfa-1-2 if the above setting are commented out. Are you using a holding a disk? It must be larger than a vtape (1gb). My bad. I forgot to say that I have runtapes greater than 1. And my question is what amanda do if above flush settings are not commmented. Amanda should not write to alfa-1-2, the backup should stay in the holding disk. They should be written to vtape on the next run or when you have more than 1GB (100% of 1gb) of dump on holding disk. Uncommenting the above setting is useless if you do not use a holding disk. Did you read the documentation? Did you tried it? Jean-Louis
Re: flush-threshold-* parameters - some clarification needed.
On 03/27/2013 11:41 AM, Kamil Jońca wrote: Jean-Louis Martineau martin...@zmanda.com writes: On 03/27/2013 08:58 AM, Kamil Jońca wrote: Jean-Louis Martineau martin...@zmanda.com writes: On 03/27/2013 06:39 AM, Kamil Jońca wrote: (This is duplicate mail, previously sent, but I weren't subscribed) In some sites there is suggestion, that config: --8---cut here---start-8--- #flush-threshold-dumped 100 # (or more) #flush-threshold-scheduled 100 # (or more) #taperflush 100 #autoflush yes --8---cut here---end---8--- helps to do better tape utilization. But how behave amanda in my configuration (+ these four lines above): I have defined 1gb vtapes, placed onto four hard disks rotated (ie. first flush go to disk 1, second to 2, third to 3, fourth to 4, fifth to 1, and so on) say on first disk are tapes: alfa-1-1 to alfa-1-10 on second: alfa-2-1 to alfa-2-10 on third: alfa-3-1 to alfa-3-10 on fourth: alfa-4-1 to alfa-4-10 One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially) alfa-1-2. Amanda should not write to alfa-1-2 if the above setting are commented out. Are you using a holding a disk? It must be larger than a vtape (1gb). My bad. I forgot to say that I have runtapes greater than 1. And my question is what amanda do if above flush settings are not commmented. Amanda should not write to alfa-1-2, the backup should stay in the holding disk. Yes, I use holding disk. So far I do not have these lines and amanda writes backup to disk (for example today backup below): --8---cut here---start-8--- -rw-r- 1 backup backup243 Mar 27 16:27 /var/spool/amanda/vtapes/state -rw--- 1 backup backup 39436 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/8.localhost._srv_samba_kopie.2 -rw--- 1 backup backup 33328 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/9.localhost._var_lib_samba.1 -rw--- 1 backup backup 25797104 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/00010.localhost._var_spool_news_archive.1 -rw--- 1 backup backup 58407680 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/3.localhost._home_kjonca_Mail.6 -rw--- 1 backup backup 63076 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/4.localhost._home_kjonca_Muzyka.1 -rw--- 1 backup backup 16056464 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/5.localhost._home_kjonca_archiwum.2 -rw--- 1 backup backup 48955192 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/6.localhost._srv_archiwa.2 -rw--- 1 backup backup 43736 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/7.localhost._srv_samba.1 -rw--- 1 backup backup 34024 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/2.localhost._home_kjonca_Drivers.1 -rw--- 1 backup backup 133441876 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/1.localhost._home_kjonca_Downloads.2 -rw--- 1 backup backup 32768 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/0.alfa-2-8 -rw--- 1 backup backup 965672960 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/8.localhost._home_kjonca_Downloads.2 -rw--- 1 backup backup 53746648 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/6.localhost._home_kjonca.3 -rw--- 1 backup backup 81132 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/7.localhost._home_kjonca_CalibreLibrary.1 -rw--- 1 backup backup 34692104 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/2.bambus.kjonca._home.2 -rw--- 1 backup backup 59360 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/3.localhost._etc.1 -rw--- 1 backup backup 164232 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/4.localhost._home.1 -rw--- 1 backup backup 19114828 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/5.localhost._home_f4y.1 -rw--- 1 backup backup 52240 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/1.bambus.kjonca._etc.1 -rw--- 1 backup backup 32768 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/0.alfa-2-7 --8---cut here---end---8--- As we can see amanda fills two vtapes (slot7 and slot8). And my experience shows that (WITHOUT flush-* settings mentioned above) at next run (with this disk) amanda will use next slot. Right? right What amanda do when these flush-* will be set to 100? man amanda.conf: search for flush-threshold-dumped and flush-threshold-scheduled. It will not write to the second vtape, it will keep the backup in the holding disk. It will write to the next available vtape on the following run. They should be written to vtape on the next run or when you have more than 1GB (100% of 1gb) of dump on holding disk. Uncommenting the above setting is useless if you do not use a holding disk. Yes, of course. Did you read the documentation? Yes. But I do not know which vtape amanda use at some of next run. The one available when it try to write to a vtape. (Because tomorrow I will put disk
Re: flush-threshold-* parameters - some clarification needed.
Kamil, The flush-threshold-* are useful for tape device, there is no advantage to use them with vtape. With a tape, if you don't fill it, there is unused space on it. With vtape, if you write 500MB to a 1GB vtape, then the vtape use 500MB nothing more, the space is not lost, it can be use by another slot. I do not understand what you want to do. Jean-Louis On 03/27/2013 11:41 AM, Kamil Jońca wrote: Jean-Louis Martineau martin...@zmanda.com writes: On 03/27/2013 08:58 AM, Kamil Jońca wrote: Jean-Louis Martineau martin...@zmanda.com writes: On 03/27/2013 06:39 AM, Kamil Jońca wrote: (This is duplicate mail, previously sent, but I weren't subscribed) In some sites there is suggestion, that config: --8---cut here---start-8--- #flush-threshold-dumped 100 # (or more) #flush-threshold-scheduled 100 # (or more) #taperflush 100 #autoflush yes --8---cut here---end---8--- helps to do better tape utilization. But how behave amanda in my configuration (+ these four lines above): I have defined 1gb vtapes, placed onto four hard disks rotated (ie. first flush go to disk 1, second to 2, third to 3, fourth to 4, fifth to 1, and so on) say on first disk are tapes: alfa-1-1 to alfa-1-10 on second: alfa-2-1 to alfa-2-10 on third: alfa-3-1 to alfa-3-10 on fourth: alfa-4-1 to alfa-4-10 One day dumps takes 1,5GB and goes to tape alfa-1-1 and (partially) alfa-1-2. Amanda should not write to alfa-1-2 if the above setting are commented out. Are you using a holding a disk? It must be larger than a vtape (1gb). My bad. I forgot to say that I have runtapes greater than 1. And my question is what amanda do if above flush settings are not commmented. Amanda should not write to alfa-1-2, the backup should stay in the holding disk. Yes, I use holding disk. So far I do not have these lines and amanda writes backup to disk (for example today backup below): --8---cut here---start-8--- -rw-r- 1 backup backup243 Mar 27 16:27 /var/spool/amanda/vtapes/state -rw--- 1 backup backup 39436 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/8.localhost._srv_samba_kopie.2 -rw--- 1 backup backup 33328 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/9.localhost._var_lib_samba.1 -rw--- 1 backup backup 25797104 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/00010.localhost._var_spool_news_archive.1 -rw--- 1 backup backup 58407680 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/3.localhost._home_kjonca_Mail.6 -rw--- 1 backup backup 63076 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/4.localhost._home_kjonca_Muzyka.1 -rw--- 1 backup backup 16056464 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/5.localhost._home_kjonca_archiwum.2 -rw--- 1 backup backup 48955192 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/6.localhost._srv_archiwa.2 -rw--- 1 backup backup 43736 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/7.localhost._srv_samba.1 -rw--- 1 backup backup 34024 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/2.localhost._home_kjonca_Drivers.1 -rw--- 1 backup backup 133441876 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/1.localhost._home_kjonca_Downloads.2 -rw--- 1 backup backup 32768 Mar 27 16:23 /var/spool/amanda/vtapes/slot8/0.alfa-2-8 -rw--- 1 backup backup 965672960 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/8.localhost._home_kjonca_Downloads.2 -rw--- 1 backup backup 53746648 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/6.localhost._home_kjonca.3 -rw--- 1 backup backup 81132 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/7.localhost._home_kjonca_CalibreLibrary.1 -rw--- 1 backup backup 34692104 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/2.bambus.kjonca._home.2 -rw--- 1 backup backup 59360 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/3.localhost._etc.1 -rw--- 1 backup backup 164232 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/4.localhost._home.1 -rw--- 1 backup backup 19114828 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/5.localhost._home_f4y.1 -rw--- 1 backup backup 52240 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/1.bambus.kjonca._etc.1 -rw--- 1 backup backup 32768 Mar 27 16:23 /var/spool/amanda/vtapes/slot7/0.alfa-2-7 --8---cut here---end---8--- As we can see amanda fills two vtapes (slot7 and slot8). And my experience shows that (WITHOUT flush-* settings mentioned above) at next run (with this disk) amanda will use next slot. Right? What amanda do when these flush-* will be set to 100? They should be written to vtape on the next run or when you have more than 1GB (100% of 1gb) of dump on holding disk. Uncommenting the above setting is useless if you do not use a holding disk. Yes, of course. Did you read the documentation? Yes. But I do not know which vtape
Re: flush-threshold-* parameters - some clarification needed.
On 03/28/2013 12:55 AM, Kamil Jońca wrote: Jean-Louis Martineau martin...@zmanda.com writes: On 03/27/2013 01:02 PM, Kamil Jońca wrote: Simple: Say, I have 1 TB disk for vtapes. I can create 900 vtapes on this disk. But all of dumps have ~500MB, so only half of disk are used. And only 900 days are remebered. And I'm curious if I have better utilization for disk, so I can have longer period of dumps. Create 1800 vtapes. The number of slots should not directly depend on the length of the tapetype but on the used size of each slots. But in this case there is a risk to get no space left on device when, in turn, dumps get larger later. What then? You monitor the free space and delete older slot if it become close to full. Jean-Louis
Re: all estimate timed out
On 04/04/2013 02:48 PM, Chris Hoogendyk wrote:
I may just quietly go nuts. I'm trying to run the command directly. In
the debug file, one example is:
Mon Apr 1 08:05:49 2013: thd-32a58: sendsize: Spawning
/usr/local/libexec/amanda/runtar runtar daily
/usr/local/etc/amanda/tools/gtar --create --file /dev/null
--numeric-owner --directory /export/herbarium --one-file-system
--listed-incremental
/usr/local/var/amanda/gnutar-lists/localhost_export_herbarium_1.new
--sparse --ignore-failed-read --totals . in pipeline
So, I created a script working off that and adding verbose:
#!/bin/ksh
OPTIONS= --create --file /dev/null --numeric-owner --directory
/export/herbarium
--one-file-system --listed-incremental;
OPTIONS=${OPTIONS}
/usr/local/var/amanda/gnutar-lists/localhost_export_herbarium_1.new
--sparse
--ignore-failed-read --totals --verbose .;
COMMAND=/usr/local/libexec/amanda/runtar runtar daily
/usr/local/etc/amanda/tools/gtar ${OPTIONS};
#COMMAND=/usr/sfw/bin/gtar ${OPTIONS};
remove the 'runtar' argument
exec ${COMMAND};
If I run that as user amanda, I get:
runtar: Can only be used to create tar archives
If I exchange the two commands so that I'm using gtar directly rather
than runtar, then I get:
/usr/sfw/bin/gtar: Cowardly refusing to create an empty archive
Try `/usr/sfw/bin/gtar --help' or `/usr/sfw/bin/gtar --usage' for more
information.
Re: all estimate timed out
On 04/05/2013 12:09 PM, Chris Hoogendyk wrote: OK, folks, it is the --sparse option that Amanda is putting on the gtar. This is /usr/sfw/bin/tar version 1.23 on Solaris 10. I have a test script that runs the runtar and a test directory with just 10 of the tif files in it. Without the --sparse option, time tells me that it takes 0m0.57s to run the script. With the --sparse option, time tells me that it takes 3m14.91s to run the script. Scale that from 10 to 1300 tif files, and I have serious issues. Now what? Can I tell Amanda not to do that? What difference will it make? Is this a bug in gtar? Use the amgtar application instead of the GNUTAR program, it allow to disable the sparse option. tar can't know where are the holes, it must read them. You WANT the sparse option, otherwise your backup will be large because tar fill the holes with 0. Your best option is to use the calcsize or server estimate. Jean-Louis
Re: DLE splitting problem
On 04/11/2013 08:04 AM, Vytas-JWRL wrote:
Hi,
I am trying to split a large directory into separate DLEs
unfortunately it does not appear to be working. Amanda version is
2.6.1p2 installed using apt-get on a debian server.
The following line is from the currently running amdump showing that
the estimated dump size is 162gigs, however I thought I had excluded
the Line_xx directories which contain the bulk of the image data. The
DLE should only be about 500megs in size. Can anyone point me to what
I am doing wrong?
Try to remove the / at the end of the exclude.
eg. exclude file optional ./Source_Files
Jean-Louis
Thanks,
Vytas
hopper:/mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06 0 162g
dumping 223g (137.76%) (20:28:02)
hopper /mnt/raid2/projects/Alberta/PLVI {
comp-user-tar
exclude file optional ./Source_Files/
}
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files {
comp-user-tar
exclude file optional ./1210h06/
}
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_10
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_11
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_12
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_13
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_14
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_15
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_16
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_17
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_18
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_19
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_20
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_21
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_22
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06/Line_23
comp-user-tar
hopper /mnt/raid2/projects/Alberta/PLVI/Source_Files/1210h06 {
comp-user-tar
exclude file optional ./Line_10/
exclude file append ./Line_11/
exclude file append ./Line_12/
exclude file append ./Line_13/
exclude file append ./Line_14/
exclude file append ./Line_15/
exclude file append ./Line_16/
exclude file append ./Line_17/
exclude file append ./Line_18/
exclude file append ./Line_19/
exclude file append ./Line_20/
exclude file append ./Line_21/
exclude file append ./Line_22/
exclude file append ./Line_23/
}
Re: stream 0 accept failed: bad SECURITY line: ''
On 04/12/2013 11:52 AM, Brian Cuttler wrote: amandad: try_socksize: send buffer size is 65536 amandad: try_socksize: receive buffer size is 65536 amandad: time 3.128: bind_portrange2: trying port=831 amandad: time 3.129: stream_server: waiting for connection: 0.0.0.0.36507 amandad: try_socksize: send buffer size is 65536 amandad: try_socksize: receive buffer size is 65536 amandad: time 3.136: bind_portrange2: trying port=831 amandad: time 3.136: stream_server: waiting for connection: 0.0.0.0.38560 amandad: try_socksize: send buffer size is 65536 amandad: try_socksize: receive buffer size is 65536 amandad: time 3.143: bind_portrange2: trying port=831 amandad: time 3.144: stream_server: waiting for connection: 0.0.0.0.49357 amandad: time 3.144: sending REP pkt: CONNECT DATA 36507 MESG 38560 INDEX 49357 OPTIONS features=feff9ffe07; The server should connect to these ports, check the server dumper debug files, try to disable firewall and selinux. Jean-Louis
Re: diskname length
Hi Nuno, The length is limited to 254 characters. Can you post the amdump file amstatus is using? Which amanda version are you using? Jean-Louis On 04/15/2013 02:41 AM, Nuno Dias wrote: Hi, Is there a limit in the length of a diskname in the disklist file? I have a directory with 198 caracteres and when the backup is running, when I run amstatus the command stops at listing this directory and eats all the memory of the machine, what seems a nasty bug. Cheers, Nuno
Re: problem with port range
On 04/23/2013 11:45 AM, Brian Cuttler wrote: Amanda users, Server is Solaris x86, with amanda 3.1.2, locally built Client is CentOS 5.9 with amanda 2.5.0p2, package 2.5.0p2 do not use an amanda-client.conf file, the port can only be configure at configure time. Jean-Louis I know I must have restricted port ranges on the server because I pass through a firewall and have ipf.conf settings on a client on the far side set to (edited for line length) pass proto tcp from 'server' port 1008310101 to any port 1008310101 pass proto udp from 'server' port 931949 to any port = amanda I'm having trouble figuring out how to set the port range on the new client, which was a pre-build package. (and is back rev, yet that was what was found in the repository). Amdump of the client has these errors in its report and backups are not happening. Amcheck runs cleanly, I see daemons start, but I do not see any data exchange. stemcell-stage /usr/share lev 1 FAILED [too many dumper retry: [could not connect DATA stream: can't connect stream to stema.wadsworth.org port 51058: Connection timed out]] stemcell-stage /etc lev 1 FAILED [too many dumper retry: [request failed: timeout waiting for ACK]] stemcell-stage /var lev 0 FAILED [too many dumper retry: [could not connect DATA stream: can't connect stream to stema.wadsworth.org port 54800: Connection timed out]] stemcell-stage /export/bak lev 1 FAILED [too many dumper retry: [request failed: timeout waiting for ACK]] I have created an amanda-client.conf on the client. Based on the client's amanda debug file I see '--with-config=DailySet1' CONFIG_DIR=/etc/amanda I created /etc/amanda/DailySet1/amanda-client.conf and attempted to add port information unreserved-tcp-port 1083,10101 reserved-udp-port 931,949 but this is clearly not working. Do I need a better kit? Do I need to build it locally? Do I have the wrong directory? Am I using the wrong options or values? Not sure what I'm doing wrong, any help appreciated. thank you, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: can't connect the stream
On 04/25/2013 10:39 AM, Brian Cuttler wrote: Already, _now_ I'm ready to solve the real problem... Server is Solaris 10 x86, Amanda server 3.1.2. Client, a CentOS 5x box has had amanda 2.5 removed in favor of 3.3.0-1. I've finally figured out the dumptype/auth/protocal, amcheck is running properly. From the amanda debug file, I find the config directory to be /etc/amanda, and the default config name DailySet1, so I have copied the amanda.conf from the server to /etc/amanda/DailySet1/amanda-client.conf (on the client). amandad process do not read the per-config amanda-client.conf. Put it in /etc/amanda/amanda-client.conf Btw. The bsdtcp auth, it is a lot easier to configure, that's why it is the default auth in 3.3 I still see port issues in the amdump report. The next 2 tapes Amanda expects to use are: Curie504, Curie505. FAILURE DUMP SUMMARY: stemcell-stage /usr/share lev 1 FAILED [too many dumper retry: [could not connect DATA stream: can't connect stream to stema.wadsworth.org port 48982: Connection timed out]] stemcell-stage /etc lev 1 FAILED [too many dumper retry: [could not connect DATA stream: can't connect stream to stema.wadsworth.org port 48985: Connection timed out]] I'd thought the solution was adding the following to the amanda-client.conf unreserved-tcp-port 1083,10101 reserved-udp-port 931,949 Those values choosen as they where the ranged used when I build the amanda server. I know I'm close, but I'm just not getting it. Note - I had expected to see the amandad debug file tell me that I was or was not including the config file, I do NOT see that though I was sure I'd seen it in debug files on other amanda clients. Perhaps I'm looking in the wrong debug file? Perhaps my amanda-client.conf is in the wrong directory? thank you, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: Cryptic Error with 2 different versions of amanda
On 04/29/2013 11:01 AM, Brendon Martino wrote: non-working fc5 CLIENT (64-bit): amanda-2.4.5p1-3.2.fc5.i686 2.4.5p1 can't use the bsdtcp auth, you must use the bsd auth. Add the auth in the dumptype (only for the 2.4.5p1 client). Set the xinetd file: socket_type = dgram protocol= udp wait= yes Jean-Louis
Re: Cryptic Error with 2 different versions of amanda
On 04/29/2013 01:54 PM, Brendon Martino wrote: Hi Jean-Louis, I tried that (set it and restarted the xinetd service): netstat -a | grep amanda udp0 0 *:amanda*:* However, there is a different error from the server: WARNING: fc5client.analogic.com: selfcheck request failed: Connection refused Client check: 1 host checked in 10.299 seconds. 1 problem found. tail /var/log/amanda/server/DailySet1/amcheck.20130429135313.debug Mon Apr 29 13:53:23 2013: amcheck-clients: connect_port: Skip port 570: owned by meter. Mon Apr 29 13:53:23 2013: amcheck-clients: make_socket opening socket with family 2 Mon Apr 29 13:53:23 2013: amcheck-clients: connect_port: Try port 571: available - Success Mon Apr 29 13:53:23 2013: amcheck-clients: connect_portrange: Connect from 0.0.0.0:571 failed: Connection refused Mon Apr 29 13:53:23 2013: amcheck-clients: connect_portrange: connect to 10.112.110.215:10080 failed: Connection refused Mon Apr 29 13:53:23 2013: amcheck-clients: stream_client: Could not bind to port in range 512-1023. Mon Apr 29 13:53:23 2013: amcheck-clients: security_seterror(handle=0xb7a05500, driver=0xb765a320 (BSDTCP) error=Connection refused) Mon Apr 29 13:53:23 2013: amcheck-clients: security_close(handle=0xb7a05500, driver=0xb765a320 (BSDTCP)) Mon Apr 29 13:53:23 2013: amcheck-clients: security_stream_close(0xb7a0e370) Mon Apr 29 13:53:23 2013: amcheck: pid 1806 finish time Mon Apr 29 13:53:23 2013 Looks like it doesn't want to connect because it is still trying to use BSDTCP? Is that right? Thanks --Brendon Martino On 04/29/2013 01:46 PM, Jean-Louis Martineau wrote: On 04/29/2013 11:01 AM, Brendon Martino wrote: non-working fc5 CLIENT (64-bit): amanda-2.4.5p1-3.2.fc5.i686 2.4.5p1 can't use the bsdtcp auth, you must use the bsd auth. Add the auth in the dumptype (only for the 2.4.5p1 client). Set the xinetd file: socket_type = dgram protocol= udp wait= yes run: amadmin CONF disklist All DLEs of the host must have the BSD auth. Jean-Louis
Re: Cryptic Error with 2 different versions of amanda
On 04/29/2013 02:05 PM, Brendon Martino wrote: Ok, here is the result: sudo -u amandabackup /sbin/amadmin DailySet1 disklist line 63: host fc5client.analogic.com: interface default disk /usr/local/bin: program GNUTAR data-path AMANDA priority 2 dumpcycle 7 maxdumps 1 maxpromoteday 1 bumpsize 20480 bumpdays 1 bumpmult 4.00 strategy STANDARD ignore NO estimate CLIENT compress CLIENT FAST comprate 0.50 0.50 encrypt NONE auth BSDTCP Set it to BSD kencrypt NO amandad-path client-username client-port ssh-keys holdingdisk NEVER record YES index YES starttime fallback-splitsize 10Mb skip-incr NO skip-full NO allow-split YES spindle -1 What's missing here?
Re: ZFS Compression Oddities with Amanda
Guy, Are you also using amanda software compression? Using compression on the holding disk is probably just a waste of CPU as the data is compressed once and decompressed once, but if it the only way it can fit in the holding disk. If you use amanda software compression, then the data is compressed on holding disk and on tape. Jean-Louis On 05/01/2013 01:10 PM, Guy Sisalli wrote: I'm attempting to commit 7 TB of text to tape. It's presently stored in a natively gzip-9 compressed zvol, weighing in at 1.7 TB. My holding area is 5 TB, and is set to a native gzip-5 compression. The functional difference between gzip-5 and gzip-9 is not very much: Level 9 compression has a 4-8% advantage over level 5. The entire DLE (taken as files, not a snapshot) should fit quite comfortably in my holding area. It didn't! I watched my holding area balloon to 4 TB and keep right on going, as if it wasn't compressing at all. Is there any scenario in which this might happen? Would you recommend against a setup like the one I've described? I'm happy to offer any details needed, but this is probably a good start: Source: NAMEPROPERTY VALUE SOURCE zulu01/keyRepo type filesystem - zulu01/keyRepo creation Tue Jan 8 13:48 2013 - zulu01/keyRepo used 1.74T - zulu01/keyRepo available 6.60T - zulu01/keyRepo referenced1.74T - zulu01/keyRepo compressratio 4.65x - zulu01/keyRepo mounted yes- zulu01/keyRepo quota none default zulu01/keyRepo reservation none default zulu01/keyRepo recordsize128K default zulu01/keyRepo mountpoint/tank/datastoredefault zulu01/keyRepo sharenfs offdefault zulu01/keyRepo checksum on default zulu01/keyRepo compression gzip-9 local Hold: NAME PROPERTY VALUE SOURCE hold type filesystem - hold creation Fri Dec 7 10:34 2012 - hold used 257M - hold available 5.35T - hold referenced243M - hold compressratio 1.00x - hold mounted no - hold quota none default hold reservation none default hold recordsize128K default hold mountpoint/hold default hold sharenfs offdefault hold checksum on default hold compression gzip-5 local
Re: ampgsql - some questions
On 05/06/2013 03:16 PM, Kamil Jońca wrote:
I tried to use ampgsql to backup mu personal database cluster (over a
dozen GBs) finally I think, I did it, but there is some ambiguity for
me.
I used
http://wiki.zmanda.com/man/ampgsql.8.html
http://wiki.zmanda.com/index.php/How_To:Use_Amanda_to_Back_Up_PostgreSQL
as a reference. (I used debian's 1:3.3.3-1 version)
My first config (excerpts)
[...]
amanda.conf
--8---cut here---start-8---
define dumptype gnutar {
program GNUTAR
}
define dumptype gnutar-local {
gnutar
auth local
}
define application-tool app-ampgsql {
comment ampgsql
plugin ampgsql
property ARCHIVEDIR /var/lib/postgresql/archive
property TMPDIR /tmp/ampgsql
property DIRECTORY /tmp/amanda-pgsql/
property HOST /var/run/postgresql/
property USER backup
}
define dumptype ampgsql-local {
gnutar-local # You might need this if you're setting 'auth
bsdtcp' in your global dumptype settings, for example
program APPLICATION
application app-ampgsql
property PG-ARCHIVEDIR /var/lib/postgresql/archive
property PG-DATADIR /var/lib/postgresql/9.1/main
}
--8---cut here---end---8---
This create two properties of the dumptype, you want application properties:
It is a bug to use the 'PG-' prefix on the application properties.
The 'PG-' prefix must be use only if you define the properties in
amanda-client.conf, don't do it, it is deprecated.
define dumptype ampgsql-local {
gnutar-local # You might need this if you're setting 'auth
bsdtcp' in your global dumptype settings, for example
program APPLICATION
application {
app-ampgsql
property ARCHIVEDIR /var/lib/postgresql/archive # not required, it
is set in app-ampgsql
property DATADIR /var/lib/postgresql/9.1/main# you could set it
in app-ampgsql
}
}
disklist
--8---cut here---start-8---
localhost postgres ampgsql-local
--8---cut here---end---8---
(example from howto was foo.example.com bar dt_ampgsql)
But this did not work :(
After read some debug and log files I found that tar called from ampgsql
tries to backup postrgresql dir which was clearly wrong.
then I changed disklist to
--8---cut here---start-8---
localhost postgres /var/lib/postgresql/9.1/main ampgsql-local
--8---cut here---end---8---
And this seems to work. (At least dump contents looks reasonable)
But
1. Am I misssed something about cluster data dir in dikslist?
2. If I have to use diskdevice in disklist entry - what for is PG-DATADIR?
Either the diskdevice in disklist or the DATADIR application property.
Jean-Louis
Re: ampgsql - some questions
On 05/07/2013 08:47 AM, Kamil Jońca wrote: Yes, I know it's deprecated (as written http://wiki.zmanda.com/man/ampgsql.8.html), but I think, that manual is not clear here about PG- prefix, moreover I can't see DATADIR property for application. You are right, there is no DATADIR application property, you must set the diskdevice in disklist. Jean-Louis
Re: seemingly random pattern of dump failures
Chris, look in the amandad debug files on the client and the dumper debug file on the server. Jean-Louis On 05/09/2013 03:06 PM, Chris Hoogendyk wrote: On one of my older setups that is running Amanda 2.5.1p3, I'm getting patterns of failures that I can't make sense of. Some days everything works just fine. Other days I get everything from a couple of DLEs failing to a half dozen. They are typically the same three servers, which are in another building. However, there is a server that has the largest DLEs in that same building that does not exhibit failures. There are also several servers in the same building as the Amanda backup server that don't show any failures. I even made a spreadsheet that shows a 0, 1 or 2 for backup levels of successes and a red x for failures. Can't see any pattern. I've looked at a bunch of things and pored over the log files to no avail. The errors show up in the Amanda reports as: anise.nsm.umass.edu/home lev 1 FAILED [cannot read header: got 0 instead of 32768] metzi1.physics.umass.edu /data lev 1 FAILED [cannot read header: got 0 instead of 32768] anise.nsm.umass.edu/home lev 1 FAILED [cannot read header: got 0 instead of 32768] anise.nsm.umass.edu/home lev 1 FAILED [too many dumper retry: [request failed: timeout waiting for ACK]] metzi1.physics.umass.edu /data lev 1 FAILED [too many dumper retry: [request failed: timeout waiting for ACK]] metzi1.physics.umass.edu /data lev 1 FAILED [cannot read header: got 0 instead of 32768] The interesting thing is that if I go to metzi1, into /tmp/amanda/client/daily/ and do an `ls *0508*` I can see the debug logs from last night. If I do a `grep '/data' *0508*` I can see any entries that mention the DLE /data. I see no instances of sendbackup. I see only those runtar debug files that correspond to the size estimates for 0, 1 and 2 level backups. There is no runtar that would correspond to an actual dump. If I do the same thing with `grep '/home' *0508*` (the DLE /home was successfully backed up), then I see all the runtar debug files for the estimates as well as a runtar debug file for the actual backup. I also see several lines in the sendbackup debug file for /home. I've also looked through /var/log/syslog, /var/log/auth.log, etc. on the client (which is Ubuntu 12.04 LTS), and I've looked through Amanda debug logs, /var/adm/messages, /var/adm/authlog, etc. on the server (which is Solaris 10). I don't see any logged errors for dropped connections or failures of any sort. The Amanda logs just don't mention /data on metzi1. A couple of the other servers that are being backed up are Ubuntu 12.04 and several are Ubuntu 10.04. None of them have been tweeked for sshd_config. All have tcpkeepalive turned on. I tried bumping up the timeouts in amanda.conf (by a factor of 5). That seems a bit much, and it didn't seem to make any difference. What should I be looking for? Where would Amanda log what is going on? (Or, why would it not be logging it?) Thank you,
Re: amcheckdump(8) failure and other issues
On 05/14/2013 02:22 AM, Jukka Salmi wrote: critical (fatal): Can't locate object method new via package Amanda::Xfer::Dest::Taper::Splitter (perhaps you forgot to load Amanda::Xfer::Dest::Taper::Splitter?) at /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Taper/Scribe.pm line 731. Hmm, looks similar to the problem mentioned above... Any hints? It looks like your installation is not complete, or you have multiple version installed? Do you have the following file: /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/XferServer.pm What's the output of the following command: grep AMANDA_COMPONENTS /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm Another potential issue I noticed is with amstatus(8): [...] It seems that this problem was caused by reading an amdump output file created by 2.5.2p1 amdump with 3.3.1 amdump; amstatus(8) now seems to work fine. This is normal, amstatus can only read amdump.* from it own version. Jean-Louis
Re: Anyone have any ideas on this dump?
Leslie, Amanda failed with 'No cache for previous failed part' and retried the dump and failed after it use 13 tapes. I never saw a failure with 'No cache for previous failed part', can you post the amdump.X file and the taper debug file. Jean-Louis On 05/13/2013 04:01 PM, Leslie(Pete) Boyd wrote: Hi All, Amanda version: (brought to you by Amanda version 3.3.3) OS:CentOS release 5.9 (Final) Anyone have any idea what happened to this dump? The complete filesystem is 13TB with only 9TBs used and there are 13 tapes allocated to this set. Report is attached. Thanks in advance...have a nice day! ** Leslie(Pete) Boyd Contractor: The rich man isn't the one who has the most, Vision Technoligies but the one who needs the least. Senior Systems Engineer US EPA Rm. E460--- IN GOD WE TRUST -- 919/541-1438 **
Re: amcheckdump(8) failure and other issues
On 05/14/2013 12:01 PM, Jukka Salmi wrote: $ grep AMANDA_COMPONENTS /usr/pkg/lib/perl5/vendor_perl/5.16.0/Amanda/Constants.pm $AMANDA_COMPONENTS = ndmp; That's the problem, it should be like: $AMANDA_COMPONENTS = server restore client amrecover ndmp Xfer.pm load XferServer only if server is included in $AMANDA_COMPONENTS. Jean-Louis
Re: amflush doesn't run. at all
Not creating the debug files is strange as it is one of the first thing it do. Use strace or a debugger (gdb) to find where it hang. Jean-Louis On 05/16/2013 05:16 AM, Abilio Carvalho wrote: Hi. still slowly trying to get my backup system to work, it's going OK but for some reason, whenever I get some dumps stuck in holding, I can't get those to tape at all. amflush just seems to hang immediately after I run it. amflush -fs also gives me exactly nothing to work with. Nothing in any logs anywhere that I can see. Similarly, amadmin holding list hangs in exactly the same way. I'm definitely not good enough yet to debug this by myself, can anyone help? with no logs or error messages or whatever I wouldn't even know where to start. Cheers Abilio ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by Clearswift for the presence of computer viruses. www.clearswift.com **
Re: amanda 3.3.3 sellfcheck request failed
Brian,
Do a: telnet grifserv.wadsworth.org amanda
create an amandad debug file on grifserv?
Jean-Louis
On 05/16/2013 02:06 PM, Brian Cuttler wrote:
Hello amanda users,
And the great wheel turns again... I've been here before, but
apparently fell back to 2.6.1 and upd from a failed 3.3.0 install.
I am running amanda 3.1.2 on Solaris 10/x86 as a server and
am in the process of upgrading the amanda client on solaris 10/Sparc
from 2.6.1 to 3.3.3.
Built seems to have gone fine.
Problme is the amcheck is failing.
I have updated the xinetd.conf on the client, it now reads.
amanda stream tcp nowait amanda /usr/local/libexec/amanda/amandad
amandad -auth=bsdtcp amdump
I disabled the prior instance of amanda (udp) in SMF services and
removed the config file both from the SMF manifest directory and from
the compiled database and then imported the new inetd config.
I updated the disklist, rather than using
define dumptype zfs-snapshot {
index
program APPLICATION
application app_amgtar
script script_zfs_snapshot
# auth bsdtcp
estimate server
}
We use
define dumptype zfs-snapshot-bsdtcp {
index
program APPLICATION
application app_amgtar
script script_zfs_snapshot
auth bsdtcp
estimate server
}
I have a note that says the auto param should be in the script and
not the dumptype, but that produces an immediate error when I invoke
amcheck.
I have updated exactly one DLE in the disklist for this client
and I have commented out all other references to this host in
the disklist, this is to prevent any confusion as to which protocal
should be used.
I am not seeing any errors in /var/adm/mesasges, nor are we producing
any debug files in the /tmp/amanda directory.
Amcheck on the server does this.
amcheck -c curie grifserv
Amanda Backup Client Hosts Check
WARNING: grifserv.wadsworth.org: selfcheck request failed: EOF on read from
grifserv.wadsworth.org
Client check: 1 host checked in 0.077 seconds. 1 problem found.
(brought to you by Amanda 3.1.2)
Snoop between the server and the client produces this
curie.wadsworth.org - grifserv.wadsworth.org TCP D=10080 S=516 Syn Seq=3583579017
Len=0 Win=49640 Options=mss 1460,nop,wscale 0,nop,nop,sackOK
grifserv.wadsworth.org - curie.wadsworth.org TCP D=516 S=10080 Syn Ack=3583579018
Seq=144367203 Len=0 Win=49640 Options=mss 1460,nop,wscale 0,nop,nop,sackOK
curie.wadsworth.org - grifserv.wadsworth.org TCP D=10080 S=516 Ack=144367204
Seq=3583579018 Len=0 Win=49640
curie.wadsworth.org - grifserv.wadsworth.org TCP D=10080 S=516 Push
Ack=144367204 Seq=3583579018 Len=89 Win=64240
grifserv.wadsworth.org - curie.wadsworth.org TCP D=516 S=10080 Ack=3583579107
Seq=144367204 Len=0 Win=49640
grifserv.wadsworth.org - curie.wadsworth.org TCP D=516 S=10080 Fin
Ack=3583579107 Seq=144367204 Len=0 Win=49640
curie.wadsworth.org - grifserv.wadsworth.org TCP D=10080 S=516 Ack=144367205
Seq=3583579107 Len=0 Win=64240
curie.wadsworth.org - grifserv.wadsworth.org TCP D=10080 S=516 Fin
Ack=144367205 Seq=3583579107 Len=0 Win=64240
grifserv.wadsworth.org - curie.wadsworth.org TCP D=516 S=10080 Ack=3583579108
Seq=144367205 Len=0 Win=49640
grifserv.wadsworth.org - curie.wadsworth.org TCP D=9997 S=51483 Push
Ack=97669462 Seq=1337171445 Len=396 Win=49640
grifserv.wadsworth.org - curie.wadsworth.org TCP D=9997 S=65528 Syn Seq=3928298379
Len=0 Win=49640 Options=mss 1460,nop,wscale 0,nop,nop,sackOK
curie.wadsworth.org - grifserv.wadsworth.org TCP D=65528 S=9997 Syn Ack=3928298380
Seq=3586269716 Len=0 Win=49640 Options=mss 1460,nop,wscale 0,nop,nop,sackOK
grifserv.wadsworth.org - curie.wadsworth.org TCP D=9997 S=65528 Ack=3586269717
Seq=3928298380 Len=0 Win=49640
grifserv.wadsworth.org - curie.wadsworth.org TCP D=9997 S=65528 Fin
Ack=3586269717 Seq=3928298380 Len=0 Win=49640
curie.wadsworth.org - grifserv.wadsworth.org TCP D=65528 S=9997 Ack=3928298381
Seq=3586269717 Len=0 Win=49640
curie.wadsworth.org - grifserv.wadsworth.org TCP D=65528 S=9997 Fin
Ack=3928298381 Seq=3586269717 Len=0 Win=49640
grifserv.wadsworth.org - curie.wadsworth.org TCP D=9997 S=65528 Ack=3586269718
Seq=3928298381 Len=0 Win=49640
curie.wadsworth.org - grifserv.wadsworth.org TCP D=51483 S=9997 Ack=1337171841
Seq=97669462 Len=0 Win=48419
grifserv.wadsworth.org - curie.wadsworth.org TCP D=9997 S=51483 Push
Ack=97669462 Seq=1337171841 Len=396 Win=49640
grifserv.wadsworth.org - curie.wadsworth.org TCP D=9997 S=32768 Syn Seq=342358183
Len=0 Win=49640 Options=mss 1460,nop,wscale 0,nop,nop,sackOK
curie.wadsworth.org - grifserv.wadsworth.org TCP D=32768 S=9997 Syn Ack=342358184
Seq=3599432777 Len=0 Win=49640 Options=mss 1460,nop,wscale 0,nop,nop,sackOK
grifserv.wadsworth.org - curie.wadsworth.org TCP D=9997 S=32768 Ack=3599432778
Seq=342358184 Len=0 Win=49640
grifserv.wadsworth.org - curie.wadsworth.org TCP D=9997 S=32768 Fin
Ack=3599432778 Seq=342358184 Len=0 Win=49640
curie.wadsworth.org - grifserv.wadsworth.org TCP D=32768 S=9997
Re: amanda 3.3.3 sellfcheck request failed
On 05/16/2013 02:46 PM, Brian Cuttler wrote: But I'm not seeing, perhaps, looking in the wrong directory, any debug files. In: `amgetconf build.amanda_dbgdir`/amandad Jean-Louis
Re: amanda 3.3.3 sellfcheck request failed
On 05/16/2013 02:53 PM, Brian Cuttler wrote: /tmp/amanda/amandad - which was created by the manual run of amandad, no new files. If telnet do not create a new debug file it is because amandad is not executed, which means SMF is misconfigured. I can't help with SMF. Jean-Louis
Re: zfs-snapshot errors
On 05/21/2013 09:47 AM, Brian Cuttler wrote: Hello Amanda users, Yesterday I upgraded an client on Solaris 10/Sparc from 2.4.2p2, which working great (except perhaps for not being built with GTAR in mind, in, I think 2001!) with amanda 3.3.3. Found the following in the client side debug file. Mon May 20 18:36:42 2013: thd-2a4b8: amgtar: NORMAL : File .* shrunk by [0-9][0-9]* bytes, padding with zeros Mon May 20 18:36:42 2013: thd-2a4b8: amgtar: NORMAL : Cannot add file .*: No such file or directory$ Mon May 20 18:36:42 2013: thd-2a4b8: amgtar: NORMAL : Error exit delayed from previous errors Mon May 20 18:36:42 2013: thd-2a4b8: amgtar: amgtar: error opening /usr/local/var/amanda/gnutar-lists/wcapp_appp_db_0: No such file or directory Mon May 20 18:36:42 2013: thd-2a4b8: amgtar: Spawning /usr/sfw/bin/gtar /usr/sfw/bin/gtar -x --no-check-device -f - in pipeline Mon May 20 18:36:42 2013: thd-2a4b8: amgtar: Spawning /usr/sfw/bin/gtar /usr/sfw/bin/gtar --create --verbose --file - --directory /appp/db/.zfs/snapshot/amanda-_appp_db-current --one-file-system --no-check-device --listed-incremental /usr/local/var/amanda/gnutar-lists/wcapp_appp_db_1.new --sparse --ignore-failed-read --totals . in pipeline Mon May 20 18:36:42 2013: thd-2a4b8: amgtar: 0: strange(?): /usr/sfw/bin/gtar: unrecognized option `--no-check-device' Ignoring the NORMAL errors. The error Mon May 20 18:36:42 2013: thd-2a4b8: amgtar: amgtar: error opening /usr/local/var/amanda/gnutar-lists/wcapp_appp_db_0: No such file or directory is I think inconsequentail since in the file system I find. # pwd /appp/export/home/local/var/amanda/gnutar-lists # ls -l total 6 -rw--- 1 amanda sys0 May 14 21:43 wcapp_appp_db2_0.new -rw--- 1 amanda sys0 May 20 18:39 wcapp_appp_db2_1.new -rw--- 1 amanda sys0 May 15 20:49 wcapp_appp_db_0.new -rw--- 1 amanda sys0 May 20 18:40 wcapp_appp_db_1.new -rw--- 1 amanda sys0 May 20 20:17 wcapp_appp_export_0.new -rw--- 1 amanda sys0 May 17 18:33 wcapp_appp_export_1.new The error is from /usr/local/var/amanda/gnutar-lists, but you list /appp/export/home/local/var/amanda/gnutar-lists. I think we choked on the --no-check-device error. Mon May 20 18:36:42 2013: thd-2a4b8: amgtar: 0: strange(?): /usr/sfw/bin/gtar: unrecognized option `--no-check-device' # /usr/sfw/bin/gtar --version tar (GNU tar) 1.17 Copyright (C) 2007 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by John Gilmore and Jay Fenlason. Simple issue of having an updated gtar? Or do I have something more complex to worry about? Upgrade gtar to a newer version of do not set the CHECK-DEVICE property. Jean-Louis
Re: transferring Amanda database from one server to another
On 05/22/2013 01:08 PM, Chris Hoogendyk wrote: The index doesn't seem to be all that is needed. I looked at one of the index files, and it contained all the items in that backup for that dle, but it didn't indicate what tape it went to. That seems to be in the logs. I think I can see how to merge the index directories, because the indexes are all date/time/dle stamped. So, if I switched a client from the old server to the new server on, say May 16, then it's older indexes would be on the old server and it's newer ones would be on the new server. I could copy the old indexes over to the new server without stepping on anything. However, the log files don't seem to be so neatly segmented, and I'm not sure how I would merge them. Copy them all. I would love to do a complete merge for another reason. While I moved all the clients to the new server yesterday, I commented out many of the dle's to avoid having a complete set of full backups done all at once. I expected to add a portion of the dle's each day through the end of this week. However, if I could do a complete merge of the Amanda databases from the old server to the new server, then the planner would have that information and would take care of everything for me. You kind of get spoiled using Amanda and end up expecting that sort of thing. ;-) You should have copied the infodir (amgetconf CONFIG infofile). Some application use statefile on the client (gnutar-listdir), you should moved them if you changed the path. I think that's all you need: tapelist log files index directories info directories client state file Jean-Louis On 5/22/13 12:47 PM, Brian Cuttler wrote: Chris, You saved the index files? Just copy them to a separate directory and search them manually if necessary, or copy the entire amanda structure but give it a config name that is different than the functional one on the new server. On Wed, May 22, 2013 at 12:08:08PM -0400, Chris Hoogendyk wrote: With luck I won't need this, but one doesn't assume luck when planning backup systems. ;-) I've just successfully transferred a tape library from an old Sun E250 running Solaris 9 and Amanda 2.5.1p3 to a new SuperMicro running Ubuntu 12.04 LTS and Amanda 3.3.3. This has been a somewhat slow transition. We have moved that departments web services to the new server and set up Amanda on it. It was backing itself up, and then I moved a few other servers to it late last week. This was being held on a sizable pair of holding disks. The original E250 was still backing up a few other servers and itself. Then yesterday, after the Monday night backups flushed the weekend backups out to tape on the E250, we moved the tape library and switched all the servers to being backed up by the new server. That ran last night, and the tape library is working just fine. After transferring the tape library, I copied over /usr/local/amanda/etc/daily/tapelist so that the new server would continue with the correct tape sequence. That seems to have worked just fine. After this has been running for 6 weeks, all the tapes will have been cycled around and the Amanda database will reflect only what has been backed up on the new server. However, between now and then, if I need to recover something that was backed up on the E250, I have the tape library and tapes on the SuperMicro, but the Amanda database is on the E250 for part of the backups. Is there a simple clean way of transferring that information from the E250 without stepping on the Amanda database entries that have been accumulated already on the SuperMicro? TIA
Re: tape size question
Robert,
Do amanda report a tape error?
What it doesn't put on tape? dump from the current run or from previous run?
You give us nothing to look at it, can you post the amdump.? log file?.
Jean-Louis
On 05/23/2013 09:59 AM, McGraw, Robert P wrote:
Amanda Server Info:
Thu May 23 05:36:00 2013: amandad: build: VERSION=Amanda-3.2.3
Thu May 23 05:36:00 2013: amandad:BUILT_DATE=Tue Feb 5
17:10:59 EST 2013 BUILT_MACH=
Thu May 23 05:36:00 2013: amandad:BUILT_REV=3994
BUILT_BRANCH=3_2_3
Thu May 23 05:36:00 2013: amandad:
CC=/opt/SunStudio/sunstudio12.1/bin/cc
Amanda.conf snippet:
define changer sl24 {
tpchanger chg-robot:/dev/changer/0
changerfile chg-zd-mtx-state
property tape-device 0=tape:/dev/rmt/0cbn
property eject-before-unload true
property eject-delay 10
property unload-delay 10
property use-slots 1-20
property load-poll 0s poll 5s until 120s
device-property BLOCK_SIZE 2 mbytes
device-property LEOM true
define tapetype LTO4-HWC {
comment LTO4-Hardware Compression on.
length 1500 gbytes
filemark 0 kbytes
speed 102216 kps
part_size 40GB
}
holdingdisk hd1 {
comment holding disk
directory /zexport/planck/holdingdisk/daily
use 3000GB
chunksize 10GB
}
I use hardware compression to max the size of the tape. Uncompressed
the tape is 800GB compressed the theoretical max size is 1.6TB. I know
that I will not get the 1.6TB.
In the amanda.conf file I tell amanda that my tape is length 1500
gbytes and that my tape drive uses LEOM.
Why does amanda stop at %52 when I still have 1.5TB of data in the
holding disk to write to the tape? It is hard to believe that the LTO4
compression is so bad that I am not getting any compression at all.
Does anyone else have a similar setup if so do my parameters look OK.
Thanks
USAGE BY TAPE:
Label Time Size % DLEs Parts
D02006 2:24 806117M 52.57793
_
Robert P. McGraw, Jr.
Manager, Computer SystemEMAIL: rmcg...@purdue.edu
mailto:rmcg...@purdue.edu
Purdue UniversityROOM: MATH-807
Department of Mathematics PHONE: (765) 494-6055
150 N. University Street
West Lafayette, IN 47907-2067
_
Robert P. McGraw, Jr.
Manager, Computer SystemEMAIL: rmcg...@purdue.edu
mailto:rmcg...@purdue.edu
Purdue UniversityROOM: MATH-807
Department of Mathematics PHONE: (765) 494-6055
150 N. University Street
West Lafayette, IN 47907-2067
Re: amanda 3.3.3 too many files
Brian, Can you increase the number of open files at the system level? amcheck check all DLEs in parallel, you can try to add spindle (in the disklist) to reduce parallelism but that can have a bad impact on dump performance, so it is not a good workaround. You would like a maxcheck setting similar to maxdump, I put it in my TODO list. Jean-Louis On 06/05/2013 11:05 AM, Brian Cuttler wrote: Hello amanda users, I just updates amanda 3.3.0 to 3.3.0 on a Solaris 10/x86 system. The system is both the server and the client, there are no other clients of this system. We have ~265 DLEs on this system (large zfs arrays and all samba shares are their own file systems and DLE, thank goodness I was able to talk my manager out of making all user directories their own DLE as well, though they are their own zfs file systems). The following errors are -not- new with 3.3.3, we've had them for a while, I'd hoped the upgrade would take are of it. Also the amcheck leaves an amanda-check file around for one of the zfs file systems (yes, configured to use zfs snapshot). [I'm pretty sure these two errors are related to one another] The filesystem amanda-*-check file left is for the same filesystem each night, unless we add/remove DLE/filesystems. So I think it is the nth filesystem and at the limit of the open file counter, rather than something in the file system itself. I was hoping there was an easy fix for this. Last I recall on the topic it had to do with the fillm being a 32 bit rather than 64 bit value (I could be wrong about this). Otherwise all # amcheck tests run successfully. Will run # amdump this evening but do not anticipate any issues there. thank you, Brian amcheck -c finsen Amanda Backup Client Hosts Check ERROR: finsen: service selfcheck: selfcheck: Error opening pipe to child: Too many open files ERROR: finsen: service /usr/local/libexec/amanda/selfcheck failed: pid 8590 exited with code 1 Client check: 1 host checked in 83.304 seconds. 2 problems found. (brought to you by Amanda 3.3.3) from /var/log/conlog Jun 5 10:55:04 finsen amandad[8583]: [ID 927837 daemon.info] connect from finsen.wadsworth.org Jun 5 10:56:27 finsen selfcheck[8590]: [ID 702911 daemon.error] Error opening pipe to child: Too many open files --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: amanda 3.3.3 too many files
On 06/05/2013 01:41 PM, Brian Cuttler wrote:
Jean-Louis,
Yes, I did find some information on a run time mechanism to
increase the 256 file limit (file limit stored in unsigned character).
The work-around employes requires the exection of /usr/lib/extendedFILE.so.1
prior to the binary being executed.
Following up on your maxcheck and Spindle number, I wonder if I
couldn't automatically build an alternate disklist file with
spindle number and swap it in and out. It would have to be done
dynamically (since my disklist changes and making changes in
multiple locations is error prone), but that can be scripted and
called from cron.
/* I need something that will handle both formats of DLE
*
finsen /export2 zfs-snapshot2
finsen /export/home-AZ /export/home {
user-tar2
include ./[A-Z]*
}
*
*/
Since this is an amanda-client issue, rather than an amanda server
issue, I need to ask you, how to execute this on the client-side
before attempting to check the DLE list. Is there a way to invoke
this from the amanda daemon?
It must be done on the server before amcheck is executed.
./script-add-spindle disklist disklist.spindle
./amcheck CONF -odiskfile=disklist.spindle
Jean-Louis
Re: amanda 3.3.3 too many files
On 06/05/2013 03:56 PM, Brian Cuttler wrote:
Jean-Louis,
Thank you, I'm sorry I was unclear. Yes, of course the disklist
needs to be in place when I invoke amcheck on the server.
I'd meant that I need to find out how to up the file limit on
the client, which is a more difficult proposition since its
SMF/INET and not simply something I can script in cron on the
server. The fact that the client and the server are the same
box doesn't help much in this case.
It can help. use the 'local' auth, which is a fork of amandad instead of
connecting to it.
If you increase the limit for amcheck, then that amandad will get the
same limit.
Jean-Louis
thank you,
Brian
On Wed, Jun 05, 2013 at 03:08:45PM -0400, Jean-Louis Martineau wrote:
On 06/05/2013 01:41 PM, Brian Cuttler wrote:
Jean-Louis,
Yes, I did find some information on a run time mechanism to
increase the 256 file limit (file limit stored in unsigned character).
The work-around employes requires the exection of
/usr/lib/extendedFILE.so.1
prior to the binary being executed.
Following up on your maxcheck and Spindle number, I wonder if I
couldn't automatically build an alternate disklist file with
spindle number and swap it in and out. It would have to be done
dynamically (since my disklist changes and making changes in
multiple locations is error prone), but that can be scripted and
called from cron.
/* I need something that will handle both formats of DLE
*
finsen /export2 zfs-snapshot2
finsen /export/home-AZ /export/home {
user-tar2
include ./[A-Z]*
}
*
*/
Since this is an amanda-client issue, rather than an amanda server
issue, I need to ask you, how to execute this on the client-side
before attempting to check the DLE list. Is there a way to invoke
this from the amanda daemon?
It must be done on the server before amcheck is executed.
./script-add-spindle disklist disklist.spindle
./amcheck CONF -odiskfile=disklist.spindle
Jean-Louis
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
Re: amanda 3.3.3 too many files
On 06/05/2013 11:54 AM, Jean-Louis Martineau wrote: Brian, Can you increase the number of open files at the system level? amcheck check all DLEs in parallel, you can try to add spindle (in the disklist) to reduce parallelism but that can have a bad impact on dump performance, so it is not a good workaround. Forget that idea, adding spindle will not help. I think the problem is a file descriptor leak (files not closed), but it can be in any process. Can you monitor all opened file for all amanda processes? I don't know how to do it with Solaris, but you 'ls /proc/PID/fd' on linux. It will help to find which process leak. Jean-Louis
Re: amflush doesn't run. at all
On 06/07/2013 11:02 AM, Abilio Carvalho wrote:
Does this look familiar at all? The strace of amflush BBPTape at one point
just becomes an endless (literally. I think it cycles endlessly, but I can't info the
pattern, it's too large) series of these. Not only this machine, mind, every single DLE
that's configured will show up in the log like this:
stat(/amanda/holding/20130417171040/.bbp.ch._dev_mapper_igtgrp-igtlv.0.17120,
{st_mode=S_IFREG|0600, st_size=1048576, ...}) = 0
stat(/amanda/holding/20130417171040/.bbp.ch._dev_mapper_igtgrp-igtlv.0.17120,
{st_mode=S_IFREG|0600, st_size=1048576, ...}) = 0
open(/amanda/holding/20130417171040/.bbp.ch._dev_mapper_igtgrp-igtlv.0.17120,
O_RDONLY) = 5
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
read(5, AMANDA: CONT_FILE 20130417171040..., 32768) = 32768
close(5^C)= 0
Can you print a little more so I can see what repeat, do the number
(17120) increase?
You have a lot of file in the holding disk, you should use a larger
chunksize.
Lot of files == slow, slower, ...
Jean-Louis
Thanks. This issue is driving me mad, and the point is fast approaching where
my boss just nixes amanda. (not its fault, really, I'm just bad at this)
Cheers
Abilio
On May 16, 2013, at 2:00 PM, Jean-Louis Martineau martin...@zmanda.com wrote:
Not creating the debug files is strange as it is one of the first thing it do.
Use strace or a debugger (gdb) to find where it hang.
Jean-Louis
On 05/16/2013 05:16 AM, Abilio Carvalho wrote:
Hi. still slowly trying to get my backup system to work, it's going OK but for
some reason, whenever I get some dumps stuck in holding, I can't get those to
tape at all. amflush just seems to hang immediately after I run it. amflush -fs
also gives me exactly nothing to work with. Nothing in any logs anywhere that I
can see.
Similarly, amadmin holding list hangs in exactly the same way.
I'm definitely not good enough yet to debug this by myself, can anyone help?
with no logs or error messages or whatever I wouldn't even know where to start.
Cheers
Abilio
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
Clearswift for the presence of computer viruses.
www.clearswift.com
**
Re: amrecover asking for tape drive on old server
The default index and tape server are set when amanda is compiled, at the configure step. You can overwrite the default different ways: amrecover -s ... -t ...(man amrecover) add them to amanda-client.conf (man amanda-client.conf) you can also change the tape server inside amrecover: setdevice [[-h tape-server] tapedev] (help command inside amrecover) You can't change the index server inside amrecover. jean-Louis On 06/17/2013 01:47 PM, Chris Hoogendyk wrote: puzzle. If you recall, I switched from Amanda 2.5.1p3 on a Solaris 9 server on an E250 to Amanda 3.3.3 on an Ubuntu 12.04 server on SuperMicro around May 22. The transition seemed to run smoothly. The old E250 is still running mail services, and the new Amanda server is still backing that up. So, now someone wants their mail files recovered from May 26. Cool. Tapes were written by the new server on that date. But, when I run amrecover, I ran into the situation below. It seems to be searching for a tape drive on the old server rather than on the new server. Weird. I've been running Amanda on the new server with the tape library and tape drive on the new server for several weeks and it has been working just fine as far as the Amanda email reports go. I went through the amanda.conf, changer.conf, etc. and find no references to any server. It should just be looking for the devices on the Amanda server that I am running this on. Any idea what's up with this? And how I can fix it? I know I can just read the tape using native facilities, but I really don't want to fall back on that if I don't have to. This should all just work, as it always has in the past. -- attempted amrecover session --- chrisho@supereclogite:/usr/local/adm$ cd /amanda1 chrisho@supereclogite:/amanda1$ sudo amrecover daily [sudo] password for chrisho: AMRECOVER Version 3.3.3. Contacting server on eclogite.geo.umass.edu ... 220 eclogite AMANDA index server (2.5.1p3) ready. Setting restore date to today (2013-06-17) 200 Working date set to 2013-06-17. 200 Config set to daily. 501 Host supereclogite is not in your disklist. Trying host supereclogite.geo.umass.edu ... 200 Dump host set to supereclogite.geo.umass.edu. Use the setdisk command to choose dump disk to recover amrecover sethost eclogite.geo.umass.edu 200 Dump host set to eclogite.geo.umass.edu. amrecover setdisk /var/mail 200 Disk set to /var/mail. amrecover setdate --05-26 200 Working date set to 2013-05-26. amrecover add cooke Added file /cooke amrecover extract Extracting files using tape drive LIB-162A5 on host eclogite.geo.umass.edu. The following tapes are needed: geo-daily-13 Extracting files using tape drive LIB-162A5 on host eclogite.geo.umass.edu. Load tape geo-daily-13 now Continue [?/Y/n/s/d]? y could not stat 'LIB-162A5': No such file or directory Load tape geo-daily-13 now Continue [?/Y/n/d]? ? Enter yes to continue, no to stop or d to change to a new device Continue [?/Y/n/d]? d New device name [?]: /dev/nst0 Using tape /dev/nst0 from server eclogite.geo.umass.edu. Continue [?/Y/n/d]? y could not stat '/dev/nst0': No such file or directory could not stat '/dev/nst0': No such file or directory Load tape geo-daily-13 now Continue [?/Y/n/d]? d New device name [?]: ? Enter a new device name or default New device name [?]: default Using default tape from server eclogite.geo.umass.edu. Continue [?/Y/n/d]? y Got no header and data from server, check in amidxtaped.*.debug and amandad.*.debug files on server amrecover exit 200 Good bye.
Re: Unknown S3 error with Swift S3 (Openstack)
Stratos,
S3 compatibility of OpenStack is not tested, you must use the SWIFT-2.0 api.
You must specify 3 of USERNAME. PASSWORD, TENANT_NAME or TENANT_ID.
define changer openstack {
tpchanger
chg-multi:s3:xxx-backups/DailySet/slot-{01,02,03,04,05,06,07,08,09,10}
device_property S3_SUBDOMAIN no
device_property S3_SSL ON
device_property S3_STORAGE_CLASS STANDARD
device-property SSL_CA_INFO /etc/amanda/x.ca-bundle
device-property S3_HOST x:443
device-property VERBOSE YES
device-property S3_SERVICE_PATH /v2.0/tokens
device_property LEOM on
device-property STORAGE_API SWIFT-2.0
device_property USERNAME ???
device_property PASSWORD
device_property TENANT_NAME ???
device_property TENANT_ID ???
}
tpchanger openstack
Jean-Louis
On 06/19/2013 12:56 PM, Stratos Zolotas wrote:
Hi, it is my first post and just a few days with amanda.
I'm trying to configure backups on Openstack's Swift using S3. I have
the following error:
$ amlabel DailySet1 DailySet1-1 slot 1
Reading label...
Error reading volume label: While trying to read tapestart header:
Unknown S3 error (None) (HTTP 403)
Not writing label.
amlabel.log has this:
Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: pid 23948 ruid 63998
euid 63998 version 3.3.3: start at Fri Jun 14 21:57:33 2013
Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: Arguments: DailySet1
DailySet1-1 slot 1
Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: pid 23948 ruid 63998
euid 63998 version 3.3.3: rename at Fri Jun 14 21:57:33 2013
Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: Using state file:
/etc/amanda/DailySet1/s3-statefile
Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: S3 driver using
bucket '-backups', prefix 'DailySet1/slot-01'
Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: Create 1 threads
Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: GET
https://xxx.com:443/xxx-backups/DailySet1%2Fslot-01special-tapestart
failed with 403/None
Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: Device
s3:xx-backups/DailySet1/slot-01 error = 'While
trying to read tapestart header: Unknown S3 error (None) (HTTP 403)'
Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: Device
s3:x-backups/DailySet1/slot-01 setting
status flag(s): DEVICE_STATUS_DEVICE_ERROR, and
DEVICE_STATUS_VOLUME_ERROR
Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: pid 23948 finish
time Fri Jun 14 21:57:35 2013
My amanda.conf is:
org DailySet1
infofile /srv/amanda/state/curinfo
logdir /srv/amanda/state/log
indexdir /srv/amanda/state/index
dumpuser amandabackup
mailto operati...@xx.com
define tapetype S3 {
comment S3 Bucket
length 100 gigabytes # Bucket size
}
device_property S3_ACCESS_KEY xxx#
Your S3 Access Key
device_property S3_SECRET_KEY xxx#
Your S3 Secret Key
device_property S3_SSL ON#
Curl needs to have S3 Certification Authority (Verisign today)
# in its CA list. If connection fails, try setting this no NO
device-property SSL_CA_INFO /etc/amanda/x.ca-bundle
device-property S3_HOST x:443
tpchanger
chg-multi:s3:xxx-backups/DailySet1/slot-{01,02,03,04,05,06,07,08,09,10}
# Number of tapes in your tapecycle
changerfile s3-statefile
tapetype S3
define dumptype simple-gnutar-remote {
auth ssh
ssh_keys /etc/amanda/MyConfig/ssh-key
compress none
program GNUTAR
}
Using s3cmd and the same access/secret i have full permissions on the
S3 storage, so i cannot figure out why i'm getting a 403 error.
Thank you.
Re: Unknown S3 error with Swift S3 (Openstack)
On 06/20/2013 07:27 AM, Stratos Zolotas wrote: It seems that something is confusing the authentication. My setup has the Swift proxy and the Keystone authentication service on different servers. Do you tried to set S3-HOST to the keystone server? and/or set the PROXY device-property? man amanda-devices Jean-Louis
Re: 7zip instead of tar?
On 06/19/2013 10:37 PM, Schlacta, Christ wrote: Is it possible, or even better, supported to use .7z instead of .tar for the backup archive format? I know .7z gets incredible compression rates and provides the archive layer functionality as well, and includes an encryption mechanism as well. 7zip is not supported, but it should not be difficult to write a wrapper for it, that's why we have the application-api. Jean-Louis
Re: amanda, fresh startup, wrong printer for report
On 06/21/2013 01:01 PM, Gene Heskett wrote: Greetings; A fresh startup for amanda, after nearly a years hiatus, but when I ran a test backup a few hours ago, and the final report came out on a MFP that I keep around for its scanner, but has had dried up and plugged up nozzles in the printhead for near a year. So obviously I got a blank sheet of paper. Where does amanda keep its printer selection where there are 2 or more available so I can fix this by sending it to a BW laser, the systems default printer? Thanks. Cheers, Gene $ man amanda.conf printer string Printer to use when doing tape labels. See the lbl-templ tapetype option. Jean-Louis
Re: amanda, fresh startup, wrong printer for report
Gene, Steve, What is the values of LPRFLAG in /Amanda/Constants.pm Set it to -P if you are using lpr and set it to -d if you are using lp (see LPR in the same file). $LPRFLAG = -P; or $LPRFLAG = -d; Jean-Louis On 06/25/2013 12:18 PM, Steven Backus wrote: Gene writes: root@coyote:/home/amanda # amgetconf Daily printer Yet another me too post: amgetconf gen printer SteveLaser yet it comes out on ColorLaser. Steve
Re: amanda, fresh startup, wrong printer for report
On 06/26/2013 10:32 AM, Gene Heskett wrote: On Wednesday 26 June 2013 10:25:44 Jean-Louis Martineau did opine: Gene, Steve, What is the values of LPRFLAG in /Amanda/Constants.pm $LPR is /usr/bin/lpr $LPRFLAG is an empty here, but is now -PBROTHEHL2140 which is how cups knows it, as does lpr. I think my email was clear, set it to -P Amanda append the PRINTER setting. Reinstall in progress. But how do I make this part of my .configure driver? The bug is that LPRFLAG is not correctly set, if you confirm it works then I will make a patch. Jean-Louis And where have the 'alpha' downloads been moved to? Set it to -P if you are using lpr and set it to -d if you are using lp (see LPR in the same file). $LPRFLAG = -P; or $LPRFLAG = -d; Jean-Louis On 06/25/2013 12:18 PM, Steven Backus wrote: Gene writes: root@coyote:/home/amanda # amgetconf Daily printer Yet another me too post: amgetconf gen printer SteveLaser yet it comes out on ColorLaser. Steve Cheers, Gene
Re: amanda, fresh startup, wrong printer for report
What is in the 'invoking printer' line in the amreport debug file? Do you checked that LPRFLAG is set to -P in the installed Constants.pm file, A recompilation can reinstall the broken one. Jean-Louis On 06/26/2013 10:41 PM, Gene Heskett wrote: On Wednesday 26 June 2013 22:40:09 Gene Heskett did opine: On Wednesday 26 June 2013 12:26:02 Jean-Louis Martineau did opine: On 06/26/2013 10:32 AM, Gene Heskett wrote: On Wednesday 26 June 2013 10:25:44 Jean-Louis Martineau did opine: Gene, Steve, What is the values of LPRFLAG in /Amanda/Constants.pm $LPR is /usr/bin/lpr $LPRFLAG is an empty here, but is now -PBROTHEHL2140 which is how cups knows it, as does lpr. I think my email was clear, set it to -P I did, now the epson has 4 jobs queued. IOW no diff. Amanda append the PRINTER setting. Reinstall in progress. But how do I make this part of my .configure driver? The bug is that LPRFLAG is not correctly set, if you confirm it works then I will make a patch. Ok, reset and reinstalled, but not reconfigured first. How about my other question? Where have the alpha's been moved to? Jean-Louis And where have the 'alpha' downloads been moved to? Set it to -P if you are using lpr and set it to -d if you are using lp (see LPR in the same file). $LPRFLAG = -P; or $LPRFLAG = -d; Jean-Louis On 06/25/2013 12:18 PM, Steven Backus wrote: Gene writes: root@coyote:/home/amanda # amgetconf Daily printer Yet another me too post: amgetconf gen printer SteveLaser yet it comes out on ColorLaser. Steve Cheers, Gene Cheers, Gene Cheers, Gene
Re: error whith amlabel and chg-rait
chg-rait and chg-robot do not use meta label, don't try to set it.
Only chg-disk use meta-label.
The barcode is the combination of all barcodes, as the inventory told
you, the barcode is '{D00225,D00225}'
amlabel -f --barcode '{D00225,D00225}' mirror
The same is true for the slot number, you could do:
amlabel -f mirror slot '{225,225}'
It is not required to put the same barcode on both tape, it is generally
a bad idea to do so, a barcode must be unique.
Jean-Louis
On 06/27/2013 07:37 AM, Dennis Benndorf wrote:
Hello,
I am trying to set up a mirror of too robots using chg-rait. Tapes in
both robots have the same barcodes. Now I want to label them with the
name of their barcodes, but the following happens:
amanda@dl380-54:~$ amlabel -f --meta META225 --barcode D00225 mirror
Reading label...
No volume with barcode 'D00225' available
amanda@dl380-54:~$ amtape mirror inventory |grep 225
slot {225,225}: label D00225 barcode {D00225,D00225} (in drive {1,1})
amanda@dl380-54:~$ amlabel -f --meta META225 --barcode D00225 mirror
Reading label...
No volume with barcode 'D00225' available
amanda@dl380-54:~$ amlabel -f --barcode D00225 mirror
Reading label...
No volume with barcode 'D00225' available
amanda@dl380-54:~$ amlabel -f mirror^C
amanda@dl380-54:~$ man amanda.conf
amanda@dl380-54:~$ amlabel -f -o meta-autolabel=META%%% --barcode
D00225 mirror
Reading label...
No volume with barcode 'D00225' available
amanda@dl380-54:~$ amlabel -f -o meta-autolabel=META%%% mirror slot 225
Reading label...
Found Amanda volume 'D00225'.
amlabel: Can't call method make_new_meta_label on an undefined value
at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.
What I really want to do is to force both sites to label ( one site
has a different label as you can see )
amanda@dl380-54:~$ amlabel -f -o meta-autolabel=META%%% mirror slot 457
Reading label...
Error reading volume label: Inconsistent volume labels/datestamps: Got
D00457/20130408180904 on tape:/dev/L700/MRO-LW-1 against
D10068/20130508071050 on tape:/dev/L700/OPELHAUS-LW-1.
amlabel: Can't call method make_new_meta_label on an undefined value
at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.
--
Regards
Dennis
Re: amanda, fresh startup, wrong printer for report
HI, I committed the attached patch. Jean-Louis On 06/27/2013 07:40 AM, Jean-Louis Martineau wrote: What is in the 'invoking printer' line in the amreport debug file? Do you checked that LPRFLAG is set to -P in the installed Constants.pm file, A recompilation can reinstall the broken one. Jean-Louis On 06/26/2013 10:41 PM, Gene Heskett wrote: On Wednesday 26 June 2013 22:40:09 Gene Heskett did opine: On Wednesday 26 June 2013 12:26:02 Jean-Louis Martineau did opine: On 06/26/2013 10:32 AM, Gene Heskett wrote: On Wednesday 26 June 2013 10:25:44 Jean-Louis Martineau did opine: Gene, Steve, What is the values of LPRFLAG in /Amanda/Constants.pm $LPR is /usr/bin/lpr $LPRFLAG is an empty here, but is now -PBROTHEHL2140 which is how cups knows it, as does lpr. I think my email was clear, set it to -P I did, now the epson has 4 jobs queued. IOW no diff. Amanda append the PRINTER setting. Reinstall in progress. But how do I make this part of my .configure driver? The bug is that LPRFLAG is not correctly set, if you confirm it works then I will make a patch. Ok, reset and reinstalled, but not reconfigured first. How about my other question? Where have the alpha's been moved to? Jean-Louis And where have the 'alpha' downloads been moved to? Set it to -P if you are using lpr and set it to -d if you are using lp (see LPR in the same file). $LPRFLAG = -P; or $LPRFLAG = -d; Jean-Louis On 06/25/2013 12:18 PM, Steven Backus wrote: Gene writes: root@coyote:/home/amanda # amgetconf Daily printer Yet another me too post: amgetconf gen printer SteveLaser yet it comes out on ColorLaser. Steve Cheers, Gene Cheers, Gene Cheers, Gene diff --git a/config/amanda/progs.m4 b/config/amanda/progs.m4 index 31e7007..40c9ef1 100644 --- a/config/amanda/progs.m4 +++ b/config/amanda/progs.m4 @@ -150,7 +150,9 @@ AC_DEFUN([AMANDA_PROG_LPR], lp|*/lp) amanda_cv_printer_flag=-d;; esac ]) - if test -z $amanda_cv_printer_flag; then + if test ! -z $amanda_cv_printer_flag; then + LPRFLAG=$amanda_cv_printer_flag + else AMANDA_MSG_WARN([WARNING: amanda will always print to the default printer]) fi fi
Re: error whith amlabel and chg-rait
Dennis,
Try the attached patch.
You can patch the installed Amanda/Changer/rait.pm file.
Jean-Louis
On 06/27/2013 08:41 AM, Dennis Benndorf wrote:
grep meta-autolabel /etc/amanda/mirror/amanda.conf show nothing.
--
Regards
Dennis Benndorf
Am Donnerstag, 27. Juni 2013, 08:39:11 schrieb Jean-Louis Martineau:
Dennis,
Do you have 'meta-autolabel' set in your amanda.conf? unset it.
Jean-Louis
On 06/27/2013 08:33 AM, Dennis Benndorf wrote:
Ok I understand but why does it tell me those messages:
amanda@dl380-54:~$ amlabel -f mirror slot '{225,225}'
Reading label...
Found Amanda volume 'D00225'.
amlabel: Can't call method make_new_meta_label on an undefined value
at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.
amanda@dl380-54:~$ amlabel -f --barcode '{D00225,D00225}' mirror
Reading label...
Found Amanda volume 'D00225'.
amlabel: Can't call method make_new_meta_label on an undefined value
at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.
Regards Dennis
Am Donnerstag, 27. Juni 2013, 07:58:19 schrieb Jean-Louis Martineau:
chg-rait and chg-robot do not use meta label, don't try to set it.
Only chg-disk use meta-label.
The barcode is the combination of all barcodes, as the inventory
told
you, the barcode is '{D00225,D00225}'
amlabel -f --barcode '{D00225,D00225}' mirror
The same is true for the slot number, you could do:
amlabel -f mirror slot '{225,225}'
It is not required to put the same barcode on both tape, it is
generally
a bad idea to do so, a barcode must be unique.
Jean-Louis
diff --git a/perl/Amanda/Changer/rait.pm b/perl/Amanda/Changer/rait.pm
index e0ef276..d6ba1dd 100644
--- a/perl/Amanda/Changer/rait.pm
+++ b/perl/Amanda/Changer/rait.pm
@@ -268,6 +268,7 @@ sub _make_res {
}
my $combined_res = Amanda::Changer::rait::Reservation-new(
+ $self,
$kid_reservations, $rait_device);
$rait_device-read_label();
@@ -676,9 +677,11 @@ sub errmap (@) {
sub new {
my $class = shift;
-my ($child_reservations, $rait_device) = @_;
+my ($chg, $child_reservations, $rait_device) = @_;
my $self = Amanda::Changer::Reservation::new($class);
+$self-{'chg'} = $chg;
+
# note that $child_reservations may contain ERROR in place of a reservation
$self-{'child_reservations'} = $child_reservations;
Re: amanda, fresh startup, wrong printer for report
Gene,
Do the following command works to send an email:
/usr/bin/Mail -s 'The Coyote Den STRANGE: AMANDA MAIL REPORT FOR June 27,
2013' g...@coyote.coyote.den
type the body of the email on stdin followed by ctrl-D.
Can you send me the log.dataestamp.0 file so I can reproduce the
warning you get?
Jean-Louis
On 06/27/2013 09:42 AM, Gene Heskett wrote:
On Thursday 27 June 2013 09:29:23 Jean-Louis Martineau did opine:
HI,
I committed the attached patch.
Jean-Louis
Thank you, added to my build script and a full clean install of 4.-svn-4761
is underway.
And I did find the amreport.debug file, which is pasted here, last nights
version:
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: pid 2954 ruid 1001 euid
1001 version 4.0.0alpha.svn.4761: start at Thu Jun 27 02:29:11 2013
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: Arguments: Daily --from-
amdump
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: pid 2954 ruid 1001 euid
1001 version 4.0.0alpha.svn.4761: rename at Thu Jun 27 02:29:11 2013
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: using logfile:
/usr/local/var/amanda/Daily/log
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: operating in script mode
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: planned output: human
mail g...@coyote.coyote.den
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: planned output:
postscript /usr/local/etc/amanda/Daily/3hole.ps printer HL3170CDW
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: invoking mail app:
/usr/bin/Mail -s The Coyote Den STRANGE: AMANDA MAIL REPORT FOR June 27,
2013 g...@coyote.coyote.den
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: warning: Use of
uninitialized value in addition (+) at
/usr/local/share/perl/5.10.1/Amanda/Report/human.pm line 797.
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: waiting for child
process to finish..
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: invoking printer:
/usr/bin/lpr -P HL3170CDW
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: waiting for child
process to finish..
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: pid 2954 finish time Thu
[...date string EOF]
The perl line context from that human.pm file is:
my $nb_incr_dle = 0;
my @incr_dle = @{$self-{tapedisks}};
foreach my $level (1 .. $#incr_dle) {
$nb_incr_dle += $incr_dle[$level]; --line 797
}
print $fh swrite(
$st_format,
DLEs Taped,
$self-{tapedisks}[0] + $nb_incr_dle,
$self-{tapedisks}[0],
$nb_incr_dle,
(
(has_incrementals($self-{tapedisks}))
? by_level_count($self-{tapedisks})
:
)
);
I have zero perl experience. So I've no clue if that is stopping the email
or not.
Thanks.
Cheers, Gene
Re: error whith amlabel and chg-rait
Dennis,
Try the attached patch.
The barcode for the rait is '{D00225,D00225}', You must adjust the labelstr.
Jean-Louis
On 06/27/2013 10:30 AM, Dennis Benndorf wrote:
Hi,
amanda@dl380-54:~$ amlabel -f mirror slot '{225,225}'
Reading label...
Found Amanda volume 'D00225'.
Newly-generated label '' does not match labelstr '^D0[0-9]*$'
Dont know why this happend, because labelstr is set to ^D0[0-9]*$
and autolabel to $b any .
but if I set it by hand it works as expected:
amanda@dl380-54:~$ amlabel -f mirror D00225 slot '{225,225}'
Reading label...
Found Amanda volume 'D00225'.
Writing label 'D00225'...
Checking label...
Success!
amanda@dl380-54:~$ cat /etc/amanda/mirror/tapelist
0 D00225 reuse BLOCKSIZE:32
--
Big thanks,
Dennis
Am Donnerstag, 27. Juni 2013, 10:10:09 schrieb Jean-Louis Martineau:
Dennis,
Try the attached patch.
You can patch the installed Amanda/Changer/rait.pm file.
Jean-Louis
diff --git a/perl/Amanda/Changer/rait.pm b/perl/Amanda/Changer/rait.pm
index d6ba1dd..2234a2e 100644
--- a/perl/Amanda/Changer/rait.pm
+++ b/perl/Amanda/Changer/rait.pm
@@ -687,6 +687,8 @@ sub new {
$self-{'child_reservations'} = $child_reservations;
$self-{'device'} = $rait_device;
+my @barcodes = errmap { . $_-{'barcode'} } @$child_reservations;
+$self-{'barcode'} = collapse_braced_alternates(\@barcodes);
my @slot_names;
@slot_names = errmap { . $_-{'this_slot'} } @$child_reservations;
Re: amanda, fresh startup, wrong printer for report
amanda use the Mail command to send email.
You must fix your system so that Mail works.
Jean-Louis
On 06/27/2013 11:03 AM, Gene Heskett wrote:
On Thursday 27 June 2013 10:49:14 Jean-Louis Martineau did opine:
Gene,
Do the following command works to send an email:
/usr/bin/Mail -s 'The Coyote Den STRANGE: AMANDA MAIL REPORT FOR June
27, 2013' g...@coyote.coyote.den
No, and the first ctrl-D gets me a Cc: prompt, the next one seems to have
killed the terminal tab where I was sudo -i in, then issued the above
command with an su - amanda -c your command as quoted above
Not exactly the reaction I expected. And the content of
/var/spool/mail/amanda, which is owned by amanda, is still at 0 length,
dated the date/time I touched it to create it.
type the body of the email on stdin followed by ctrl-D.
Can you send me the log.dataestamp.0 file so I can reproduce the
warning you get?
That above did not generate a new log file, and the one from nominally 2am
this morning contains zero references to mail. Its also about 25k.
Does Mail keep its own log?
Jean-Louis
On 06/27/2013 09:42 AM, Gene Heskett wrote:
On Thursday 27 June 2013 09:29:23 Jean-Louis Martineau did opine:
HI,
I committed the attached patch.
Jean-Louis
Thank you, added to my build script and a full clean install of
4.-svn-4761 is underway.
And I did find the amreport.debug file, which is pasted here, last
nights version:
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: pid 2954 ruid 1001
euid 1001 version 4.0.0alpha.svn.4761: start at Thu Jun 27 02:29:11
2013 Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: Arguments:
Daily --from- amdump
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: pid 2954 ruid 1001
euid 1001 version 4.0.0alpha.svn.4761: rename at Thu Jun 27 02:29:11
2013 Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: using
logfile: /usr/local/var/amanda/Daily/log
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: operating in script
mode Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: planned
output: human mail g...@coyote.coyote.den
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: planned output:
postscript /usr/local/etc/amanda/Daily/3hole.ps printer HL3170CDW
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: invoking mail app:
/usr/bin/Mail -s The Coyote Den STRANGE: AMANDA MAIL REPORT FOR June
27, 2013 g...@coyote.coyote.den
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: warning: Use of
uninitialized value in addition (+) at
/usr/local/share/perl/5.10.1/Amanda/Report/human.pm line 797.
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: waiting for child
process to finish..
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: invoking printer:
/usr/bin/lpr -P HL3170CDW
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: waiting for child
process to finish..
Thu Jun 27 02:29:11 2013: thd-0x8a16d00: amreport: pid 2954 finish
time Thu [...date string EOF]
The perl line context from that human.pm file is:
my $nb_incr_dle = 0;
my @incr_dle = @{$self-{tapedisks}};
foreach my $level (1 .. $#incr_dle) {
$nb_incr_dle += $incr_dle[$level]; --line 797
}
print $fh swrite(
$st_format,
DLEs Taped,
$self-{tapedisks}[0] + $nb_incr_dle,
$self-{tapedisks}[0],
$nb_incr_dle,
(
(has_incrementals($self-{tapedisks}))
? by_level_count($self-{tapedisks})
:
)
);
I have zero perl experience. So I've no clue if that is stopping the
email or not.
Thanks.
Cheers, Gene
Cheers, Gene
Re: amflush problem
Jean-Francois,
There a is bug with overwrite with name with '-' (flush-threshold-dumped
and flush-threshold-scheduled).
This bug already fixed.
From ChangeLog:
2013-04-18 Jean-Louis Martineau martin...@zmanda.com
* common-src/conffile.c: Fix parsing command overwrite with '-'.
Fix small --print-source bug.
The only workaround is to set them in amanda.conf.
Jean-Louis
btw. 3.3.4 will be out very soon.
Jean-Louis
On 07/03/2013 12:03 PM, Jean-Francois Malouin wrote:
Replying to myself...
* Jean-Francois Malouin jean-francois.malo...@bic.mni.mcgill.ca [20130627
12:08]:
Hi,
It's been a while since I had to flush a dump from the holddisk to
tape. I use a bash script that contains:
amflush -f -b -oflush-threshold-dumped=0 -oflush-threshold-scheduled=0
-otaperflush=0 $conf
Whwn invoked as the amanda user I get the error:
/opt/amanda-3.3.2/etc/amanda/top/disklist, line 79: disk device name expected
amflush: errors processing config file
Line 79 is the 'app-amgtar' below:
edgar /opt/amanda {
#tar-calc
app-amgtar
estimate server
record no
index no
strategy noinc
}
When invoked without any option overrides amflush runs ok.
Any hint? It used to work prior to 3.x
Regards,
jf
I had time to investigate a little further this morning. Still no go.
Here is an example using only 1 DLE in the disklist.
~# su amanda -c ~amanda/sbin/flush-and-log.sh down
/opt/amanda-3.3.2/etc/amanda/down/disklist, line 1: disk dumptype
'app-amgtar-span' not found
amflush: errors processing config file
Use of uninitialized value $OF in ref-to-glob cast at /opt/amanda/sbin/amtoc line 48,
IF line 157.
ERROR: while ejecting volume: Tape device /dev/nst0 is not ready or is empty
(btw, /opt/amanda-3.3.2 points to /opt/amanda, the homedir of the user 'amanda'.
The little flush script and other info follows∵
~# cat ~amanda/sbin/flush-and-log.sh
#!/bin/sh
conf=$1
if [ $conf = ]; then
echo you must provide a config name as an argument!
exit 1
else
/opt/amanda/sbin/amflush -f -b -oflush-threshold-dumped=0
-oflush-threshold-scheduled=0 -otaperflush=0 $conf
logdir=`/opt/amanda/sbin/amgetconf $conf logdir`
log=`ls -1t $logdir/log.*.[0-9] | head -1`
/opt/amanda/sbin/amtoc -t -a $log
/opt/amanda/sbin/amtape $conf eject
fi
The disklist ~amanda/etc/amanda/down/disklist: (edited to include only one DLE)
tutor /raid/data8 app-amgtar-span
The dumptype 'app-amgtar-span' is defined in the files included in amanda.conf:
includefile /opt/amanda/common/applications.conf
includefile /opt/amanda/common/dumptype.conf
/opt/amanda/common/applications.conf:
define application-tool app-amgtar {
plugin amgtar
property CHECK-DEVICE NO
property IGNORE : Directory is new$
property append IGNORE : Directory has been renamed
property append IGNORE : file changed as we read it$
property append IGNORE : socket ignored$
property append IGNORE : Cannot stat: No such file or directory$
}
/opt/amanda/common/dumptype.conf:
define dumptype app-amgtar-span {
global
program APPLICATION
application app-amgtar
priority high
allow-split
holdingdisk required
compress none
comment tape-spanning user partitions dumped with amgtar
}
In the end it boils down to:
~# su amanda -c ~amanda/sbin/amadmin down disklist
line 1 (/opt/amanda/etc/amanda/down/disklist):
host tutor:
interface default
disk /raid/data8:
program APPLICATION
application app-amgtar
COMMENT tape-spanning user partitions dumped with amgtar
PROGRAM APPLICATION
SERVER-CUSTOM-COMPRESS
CLIENT-CUSTOM-COMPRESS
SERVER-ENCRYPT
CLIENT-ENCRYPT
AMANDAD-PATH
CLIENT-USERNAME
SSH-KEYS
AUTHBSDTCP
EXCLUDE LIST
EXCLUDE FILE
INCLUDE LIST
INCLUDE FILE
PRIORITYHIGH
DUMPCYCLE 10
MAXDUMPS6
MAXPROMOTEDAY 1
BUMPPERCENT 10
BUMPSIZE10240K
BUMPDAYS2
BUMPMULT2.0
STARTTIME000
STRATEGYSTANDARD
ESTIMATECLIENT
COMPRESSNONE
ENCRYPT NONE
SERVER-DECRYPT-OPTION -d
CLIENT-DECRYPT-OPTION -d
COMPRATE0.5 0.5
TAPE-SPLITSIZE 0K
FALLBACK-SPLITSIZE 10240K
SPLIT-DISKBUFFER
RECORD yes
SKIP-INCR no
SKIP-FULL no
HOLDINGDISK REQUIRED
KENCRYPTno
IGNORE no
INDEX yes
APPLICATION app-amgtar
Re: how to use runtapes 1 with single lto drive setup
Karsten,
see: man amanda-interactivity
tpchanger chg-single:tape:/dev/nst0
define interactivity email {
plugin email
property mailto m...@me.me
}
interactivity email
runtapes 2
Jean-Louis
On 07/02/2013 11:04 AM, Karsten Fuhrmann wrote:
Hello,
i am trying to get this working for ages, but i seem to miss something
all the time.
So i just want to use runtapes 1 because some of my filesystems are
bigger than my tapesize. I dont have a robot changer, just a lto
drive, so i have to change tapes by hand. I would like to get an email
when i need to change the tape. Can someone just post my the relevant
lines of amanda.conf to do that?
Greetings,
Karsten Fuhrmann
System Administrator
Rothkirch Cartoon-Film GmbH
Hasenheide. 54
D-10967 Berlin
phone +49 30 698084-109
fax +49 30 698084-29
mobile +49 176 49118462
skype: parceval3000
AIM: in...@mac.com mailto:in...@mac.com
Jabber: parce...@jabber.org mailto:parce...@jabber.org
Release of Amanda-3.3.3
Hello, The Amanda core team is pleased to announce the release of Amanda 3.3.4. Source tarballs are available from * http://www.amanda.org * https://sourceforge.net/project/showfiles.php?group_id=120 Binaries for many systems are available from * http://www.zmanda.com/download-amanda.php Documentation can be found at * http://wiki.zmanda.com Here's a list of the changes for release 3.3.4 (from the NEWS file): Look at the ReleaseNotes and ChangeLog file for more details. * amreport o new --format argument o new 'json' and 'json_raw' format. * amanda.conf o new REPORT-FORMAT option. * amtape o new 'verify' command. * amadmin o new 'force-level-1' command. * ampgslq o Add VERBOSE property. * S3 device o handle DURABLE_REDUCED_AVAILABILITY for google storage. * Many bugs fix. Jean-Louis
Re: Release of Amanda-3.3.4
Sorry for the wrong subject, it is 3.3.4 On 07/04/2013 07:32 AM, Jean-Louis Martineau wrote: Hello, The Amanda core team is pleased to announce the release of Amanda 3.3.4. Source tarballs are available from * http://www.amanda.org * https://sourceforge.net/project/showfiles.php?group_id=120 Binaries for many systems are available from * http://www.zmanda.com/download-amanda.php Documentation can be found at * http://wiki.zmanda.com Here's a list of the changes for release 3.3.4 (from the NEWS file): Look at the ReleaseNotes and ChangeLog file for more details. * amreport o new --format argument o new 'json' and 'json_raw' format. * amanda.conf o new REPORT-FORMAT option. * amtape o new 'verify' command. * amadmin o new 'force-level-1' command. * ampgslq o Add VERBOSE property. * S3 device o handle DURABLE_REDUCED_AVAILABILITY for google storage. * Many bugs fix. Jean-Louis
Re: amreport regex problem
On 07/04/2013 08:16 AM, Dennis Benndorf wrote:
Hi,
amreport seems to have a problem with my labelstring while amcheck
does not:
amanda@dl380-54:~$ amreport mirror
Hostname: dl380-54
Org : Tagesbackup
Config : mirror
Date : July 3, 2013
These dumps were to tapes {D00224,D00224}, {D00231,D00231},
{D00249,D00249}.
There are 734565M of dumps left in the holding disk.
They will be flushed on the next run.
amreport: regex ^{D0[0-9]*,D0[0-9]*}$: Invalid preceding regular
expression
'{' is a special character in a regex, but you want a real '{', it must
be escaped, and as amanda use escaped string, you must escape it twice:
labelstr ^\\{D0[0-9]*,D0[0-9]*\\}$
Jean-Louis
P.S. amanda 3.3.4 is already installed.
--
Regards
Dennis
Re: strange error in logfile
On 07/04/2013 09:33 AM, Karsten Fuhrmann wrote:
Hello,
using Amanda 3.3.3 on FreeBSD 9.1-RELEASE i got this strange message in the
system of the system which should be backuped via amzfs_sendrecv,
and the backup of this filesystem failed.
Jul 3 16:55:26 trac Amzfs_sendrecv[303]: Argument 1.00x isn't numeric in
multiplication (*) at /usr/local/libexec/amanda/application/amzfs-sendrecv line 292.
Greetings,
Karsten Fuhrmann
Amanda expect numerical value but your command append a 'x'.
Apply the attached patch and retry a backup, post the resulting
amzfs-snapshot debug file.
The patch add more debugging so I can see which command append the 'x'.
Jean-Louis
diff --git a/application-src/amzfs-sendrecv.pl b/application-src/amzfs-sendrecv.pl
index 44b91cf..37bc1a0 100644
--- a/application-src/amzfs-sendrecv.pl
+++ b/application-src/amzfs-sendrecv.pl
@@ -291,6 +291,7 @@ sub estimate_snapshot
$self-print_to_server_and_die(cannot estimate snapshot '$self-{snapshot}\@$self-{snapshot}': unknown reason, $Amanda::Script_App::ERROR);
}
}
+Amanda::Debug::debug(estimate_snapshot: $msg);
if ($level == 0) {
my $compratio = $self-get_compratio();
chop($compratio);
@@ -327,7 +328,8 @@ sub get_compratio
$self-print_to_server_and_die(cannot read compression ratio '$self-{snapshot}\@$self-{snapshot}': unknown reason, $Amanda::Script_App::ERROR);
}
}
-return $msg
+Amanda::Debug::debug(get_compratio: $msg);
+return $msg;
}
sub command_index_from_output {
Re: amreport regex problem
On 07/05/2013 04:21 AM, Dennis Benndorf wrote: It seems to me that it broke tonight, but amstatus shows me that some dles were flushed. Attached the taper debug file. Some dles where flushed. Amanda wrote to a tape and failed to unload it. It looks like your library is slower than the default amanda delay, can you try to set some of the following properties for both robot changers: property EJECT-BEFORE-UNLOAD yes property EJECT-DELAY 120 property UNLOAD-DELAY 120 property LOAD-POLL 60s poll 5s until 5m I'm not sure which one is required and I'm not sure if the number are large enough in the example. see: man amanda-changers Jean-Louis
Re: amanda, fresh startup, WAS wrong printer for report NOW mail
Amanda run a command to send an email, it the command works, then amanda works. What is the command amanda is running? you can find it in the amreport debug file. Run the same command on the command line, did it works? Jean-Louis On 07/05/2013 07:46 AM, Gene Heskett wrote: On Friday 05 July 2013 07:11:47 Jean-Louis Martineau did opine: amanda use the Mail command to send email. You must fix your system so that Mail works. Jean-Louis I've done quite a bit of fooling around, ripping out the bsd-mail stuff and installing the GNU mailutils and sendmail. I have successfully su'd to amanda and sent gene an email. But despite the mailto: g...@coyote.coyote.den line at the top of my working amanda.conf, the mail itself from amanda is sent to amanda. From the /var/log/mail.log, using grep sendmail mail.log|grep amanda: Jul 3 16:20:37 coyote sendmail[18397]: r63KKbV2018397: from=amanda, size=184, class=0, nrcpts=1, msgid=201307032020.r63kkbv2018...@coyote.coyote.den, relay=amanda@localhost Jul 3 16:20:37 coyote sendmail[18397]: r63KKbV2018397: to=g...@coyote.coyote.den, ctladdr=amanda (1001/1002), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30184, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (r63KKbmW018398 Message accepted for delivery) = my test mail that worked above = Jul 4 02:02:46 coyote sendmail[16012]: r645K1Np016012: from=amanda, size=711, class=0, nrcpts=1, msgid=201307040520.r645k1np016...@coyote.coyote.den, relay=amanda@localhost Jul 4 02:02:46 coyote sendmail[16012]: r645K1Np016012: to=amanda, ctladdr=amanda (1001/1002), delay=00:42:45, xdelay=00:00:00, mailer=relay, pri=30711, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (r6462kMf019315 Message accepted for delivery) Jul 5 02:08:34 coyote sendmail[3977]: r655K16f003977: from=amanda, size=711, class=0, nrcpts=1, msgid=201307050520.r655k16f003...@coyote.coyote.den, relay=amanda@localhost Jul 5 02:08:34 coyote sendmail[3977]: r655K16f003977: to=amanda, ctladdr=amanda (1001/1002), delay=00:48:33, xdelay=00:00:00, mailer=relay, pri=30711, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (r6568YNX007277 Message accepted for delivery) And at the time it writes to /var/spool/mail/amanda, it helpfully resets the perms to 0600, and kmail, running as me, cannot touch it. So, where is that mailto: line in amanda.conf getting lost? My wrapper scripts do not touch this AFAIK. And I just did su - amanda, and sent me another email, getting this in the mail.log: Jul 5 07:34:35 coyote sendmail[23789]: r65BYZEm023789: from=amanda, size=172, class=0, nrcpts=1, msgid=201307051134.r65byzem023...@coyote.coyote.den, relay=amanda@localhost Jul 5 07:34:35 coyote sendmail[23789]: r65BYZEm023789: to=g...@coyote.coyote.den, ctladdr=amanda (1001/1002), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30172, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (r65BYZPf023792 Message accepted for delivery) So it works, amd kmail got the msg. Why amanda itself cannot follow orders here? Is there something wrong with my mailto:;? I see in the example/amanda.conf, the FQDN isn't used, so I'll remove that for SG. I just tested it by hand as amanda, and it worked, but it did add the missing FQDN in the sendmail log. I'm snookered here. Out of ideas IOW. Cheers, Gene
Re: how to use runtapes 1 with single lto drive setup
0g 0g ( 0.00%) ( 0.00%)
taped : 2 933g 933g (100.00%) ( 61.35%)
tape 1: 2 933g 933g (109.84%) cf-daily-lto23 (20 chunks)
4 dumpers idle : no-dumpers
taper status: Idle
taper qlen: 19
network free kps: 8
holding space : 1168g (403.56%)
taper busy : 8:41:00 ( 99.46%)
0 dumpers busy : 8:43:49 (100.00%) no-dumpers: 8:43:41 ( 99.97%)
not-idle: 0:00:08 ( 0.03%)
The last lines of amflush.1 show this:
driver: result time 31429.525 from taper: REQUEST-NEW-TAPE 00-2
driver: send-cmd time 31429.525 to taper: START-SCAN worker0 00-2
driver: send-cmd time 31429.525 to taper: NEW-TAPE worker0 00-2
driver: state time 31429.527 free kps: 8 space: 1225029868 taper: writing
idle-dumpers: 4 qlen tapeq: 18 runq: 0 roomq: 0 wakeup: 0 driver-idle:
no-dumpers
driver: interface-state time 31429.527 if default: free 8
driver: hdisk-state time 31429.527 hdisk 0: free 1225029868 dumpers 0 hdisk 1:
free 0 dumpers 0
driver: result time 31429.527 from taper: NO-NEW-TAPE 00-2
dump of driver schedule before start degraded mode:
dump of driver schedule after start degraded mode:
driver: state time 31429.528 free kps: 8 space: 1225029868 taper: DOWN
idle-dumpers: 4 qlen tapeq: 18 runq: 0 roomq: 0 wakeup: 0 driver-idle:
no-dumpers
driver: interface-state time 31429.528 if default: free 8
driver: hdisk-state time 31429.528 hdisk 0: free 1225029868 dumpers 0 hdisk 1:
free 0 dumpers 0
driver: result time 31429.528 from taper: PARTIAL 00-2 INPUT-GOOD TAPE-ERROR [sec 1851.00 bytes
58870693888 kps 31059.379795 orig-kb 1024768320] No acceptable volumes found
driver: finished-cmd time 31429.528 taper wrote
framestore.cartoon-film.de:/tank/koh/user/./p-t
driver: taper failed framestore.cartoon-film.de /tank/koh/user/./p-t with tape
error: No acceptable volumes found
driver: taper will retry framestore.cartoon-film.de /tank/koh/user/./p-t
driver: state time 31429.528 free kps: 8 space: 1225029868 taper: DOWN
idle-dumpers: 4 qlen tapeq: 19 runq: 0 roomq: 0 wakeup: 0 driver-idle:
no-dumpers
driver: interface-state time 31429.528 if default: free 8
driver: hdisk-state time 31429.528 hdisk 0: free 1225029868 dumpers 0 hdisk 1:
free 0 dumpers 0
driver: QUITTING time 31429.528 telling children to quit
driver: send-cmd time 31429.528 to taper: QUIT
driver: FINISHED time 31430.762
On 03.07.2013, at 19:43, Jean-Louis Martineau wrote:
Karsten,
see: man amanda-interactivity
tpchanger chg-single:tape:/dev/nst0
define interactivity email {
plugin email
property mailto m...@me.me
}
interactivity email
runtapes 2
Jean-Louis
On 07/02/2013 11:04 AM, Karsten Fuhrmann wrote:
Hello,
i am trying to get this working for ages, but i seem to miss something all the
time.
So i just want to use runtapes 1 because some of my filesystems are bigger
than my tapesize. I dont have a robot changer, just a lto drive, so i have to
change tapes by hand. I would like to get an email when i need to change the tape.
Can someone just post my the relevant lines of amanda.conf to do that?
Greetings,
Karsten Fuhrmann
System Administrator
Rothkirch Cartoon-Film GmbH
Hasenheide. 54
D-10967 Berlin
phone +49 30 698084-109
fax +49 30 698084-29
mobile +49 176 49118462
skype: parceval3000
AIM: in...@mac.com mailto:in...@mac.com
Jabber: parce...@jabber.org mailto:parce...@jabber.org
Greetings,
Karsten Fuhrmann
System Administrator
Greetings,
Karsten Fuhrmann
System Administrator
Rothkirch Cartoon-Film GmbH
Hasenheide. 54
D-10967 Berlin
phone +49 30 698084-109
fax +49 30 698084-29
mobile +49 176 49118462
skype: parceval3000
AIM: in...@mac.com
Jabber: parce...@jabber.org
Re: Splitting a DLE with regex
Mike,
include must be a glob expression, not a regex, so ./[a-c]* is the
correct syntax,
Do /home and /home/aaronson are on the same filesystem?
df /home
df /home/aaronson
Are you using the application 'amgtar' or the program 'GNUTAR'?
Jean-Louis
On 07/31/2013 12:56 PM, Mike Neimoyer wrote:
Replying to multiple folks with this message Thanks for your kind
responses! :)
Starting with this disklist entry which returned an error:
localhost /home/a-c /home {
vhost2-user-tar
include ./[a-c]*
} 1 local
Jon was good enough to respond:
Might /home be a symbolic link to another
location, eg. /export/home? I don't know
if it matters, but I've always used the
actual storage dir.
BTW the second parameter (/home/a-c) is
just a DLE name, not a pathname. Omitting
the slashes might avoid future confusion.
Ex. HOME:a-c
I double-checked that /home was not symbolically linked to anywhere
else. Then I edited the diskname parameter in the DLE:
localhost HOME:a-c /home {
vhost2-user-tar
include ./[a-c]*
} 1 local
and an amcheck Daily returned, after the usualy info dir and index dir
not existing and being created on the next run:
ERROR: localhost: [Nothing found to include for disk HOME:a-c]
Client check: 1 host checked in 1.303 seconds. 1 problem found.
No love with that, I reverted the DLE to it's original (above) because
Chris' suggestion had rolled in:
Try:
localhost /home/./a-c /home {
vhost2-user-tar
include ./[a-c]*
} 1 local
That is, put in an intervening ./ in the
name on the first line.
I have a couple of examples like that in my
disklist, and it all seems to work just fine.
Sounds interesting! So I tried that.
localhost /home/./a-c /home {
vhost2-user-tar
include ./[a-c]*
} 1 local
Unfortunately, an amcheck Daily returned a by-now-familiar message:
ERROR: localhost: [Nothing found to include for disk /home/./a-c]
Client check: 1 host checked in 1.223 seconds. 1 problem found.
Reverting the DLE to original, I then took a crack at it again, based
on Christ's suggestion that the regex was invalid:
Your regex is invalid. It says the letters
a, b, or c repeated any number of times and
would match a, aa, cab, but not bad or aaron.
Try ./[a-c].*
Ahh, okay, this makes sense (sorta, since I thought the regex would
catch ANY directories starting with a*, b* c*) I'll give this new
method a go, however! I fix up the original DLE with the new regex:
localhost /home/a-c /home {
vhost2-user-tar
include ./[a-c].*
} 1 local
AND THE SURVEY SAAAYS:
ERROR: localhost: [Nothing found to include for disk /home/a-c]
Client check: 1 host checked in 1.241 seconds. 1 problem found.
I then tried mixing John's diskname label with Christ's regex: same
results. I tried Chris' suggestion for the diskname with Christ's
regex: no love.
By all that I've read and all that I've searched, this SHOULD be
working. I'm at wit's end, and I'd really like to get this working
before I'm laid-off on Friday. :)
Anyone have ANY other ideas? Can it be a problem with Amanda 3.3.1
(under Centos 6, with tar 1.26) passing include directives to tar?
Could it be a permission issue with tar? Beuller? Beuller? Anyone?
:)
~~Mike
Re: Splitting a DLE with regex
On 07/31/2013 04:00 PM, Mike Neimoyer wrote:
However, as the amandabackup user, when I cd /home and then ls -lah I
get a permission denied. This could be the reason the glob directive
is failing, since it cannot scan the contents of that directory to put
together an accurate include list for tar.
Unfortunately, each /home/username is owned by username:username as
the UID:GID. It now looks like I need to figure out a way to get the
amandabackup user access via a groupID.
Try the amgtar application, it should do the glob expansion as root.
Put the following in the dumptype:
program APPLICATION
application {
plugin amgtar
}
Jean-Louis
Re: amfetchdump problem in 3.3.3 and 3.3.4
Marcus, Replace the line: my $dle = $p1-XMLin($dle_str); by my $dle = $p1-XMLin($dle_str) if defined $dle_str; Jean-Louis On 09/04/2013 02:57 PM, Marcus Pless wrote: I recently switched to the 3.3.3 version of amanda and now I can't extract files from tape using amfetchdump. I get the same error with 3.3.4. The XML::Simple perl module is installed. Has anyone else seen this error? $ amfetchdump Daily hostname / 1 volume(s) needed for restoration The following volumes are needed: DLY009 Press enter when ready amfetchdump: Could not find amfetchdump.xml in /usr/local/amanda/sbin/ at /usr/local/amanda/sbin/amfetchdump line 507 From the end of the debug log: Wed Sep 4 11:08:31 2013: thd-0x9d6f348: amfetchdump: SL-500-LTO4: updating state Wed Sep 4 11:08:31 2013: thd-0x9d6f348: amfetchdump: parse_inventory: load slot 23 with label 'DLY009' Wed Sep 4 11:08:31 2013: thd-0x9d6f348: amfetchdump: SL-500-LTO4: too early for another 'status' invocation Wed Sep 4 11:08:31 2013: thd-0x9d6f348: amfetchdump: SL-500-LTO4: loading slot '23' Wed Sep 4 11:08:31 2013: thd-0x9d6f348: amfetchdump: SL-500-LTO4: requested volume is already in drive 1 Wed Sep 4 11:08:31 2013: thd-0x9d6f348: amfetchdump: SL-500-LTO4: polling 'tape:/dev/nst1' to see if it's ready Wed Sep 4 11:11:45 2013: thd-0x9d6f348: amfetchdump: Amanda::Recovery::Clerk: successfully located first part for recovery Wed Sep 4 11:11:45 2013: thd-0x9d6f348: amfetchdump: critical (fatal): Could not find amfetchdump.xml in /usr/local/amanda/sbin/ at /usr/local/amanda/sbin/amfetchdump line 507 /usr/local/amanda/lib/libamanda-3.3.3.so[0xa333b4] /lib/libglib-2.0.so.0(g_logv+0x337)[0x76a997] /lib/libglib-2.0.so.0(g_log+0x29)[0x76ab69] /usr/local/amanda/lib/perl/auto/Amanda/MainLoop/libMainLoop.so[0x6b63f2] /lib/libglib-2.0.so.0[0x762776] /lib/libglib-2.0.so.0(g_main_context_dispatch+0x182)[0x7621a2] /lib/libglib-2.0.so.0[0x765196] /lib/libglib-2.0.so.0(g_main_loop_run+0x1b7)[0x765557] /usr/local/amanda/lib/perl/auto/Amanda/MainLoop/libMainLoop.so(run_c+0x1f)[0x6b555f] /usr/local/amanda/lib/perl/auto/Amanda/MainLoop/libMainLoop.so(_wrap_run_c+0x94)[0x6b5604] /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_pp_entersub+0x40d)[0x1b651d] /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_runops_standard+0x1f)[0x1af98f] /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(perl_run+0x2ee)[0x15520e] /usr/bin/perl(main+0x13e)[0x804921e] /lib/libc.so.6(__libc_start_main+0xdc)[0x2d9e9c] /usr/bin/perl[0x8049021] Thanks in advance! --Marcus
Re: amfetchdump problem in 3.3.3 and 3.3.4
Marcus, What was your version before 3.3.3? The backup you try to restore was made with which version of amanda? Jean-Louis On 09/04/2013 02:57 PM, Marcus Pless wrote: I recently switched to the 3.3.3 version of amanda and now I can't extract files from tape using amfetchdump. I get the same error with 3.3.4. The XML::Simple perl module is installed. Has anyone else seen this error? $ amfetchdump Daily hostname / 1 volume(s) needed for restoration The following volumes are needed: DLY009 Press enter when ready amfetchdump: Could not find amfetchdump.xml in /usr/local/amanda/sbin/ at /usr/local/amanda/sbin/amfetchdump line 507 From the end of the debug log:
Re: amfetchdump problem in 3.3.3 and 3.3.4
Marcus, Can you tell me more about your random ssh failures? What errors do you get? What is in the debug files? Jean-Louis On 09/04/2013 04:11 PM, Marcus Pless wrote: Jean-Louis, Previously I was running 3.2.1 on this server. This version was great except it wouldn't reliably swap tapes on multiple tape backups. I upgraded to 3.3.4 which fixed the tape swapping problem but introduced a lot of random ssh failures. I haven't seen the tape swapping issue or the ssh issue in 3.3.3 but today I ran into the amfetchdump problem with 3.3.3. The error messages below are from last night's backup, written using 3.3.3. I was trying to verify the backup of a newly added host.
Re: building amanda 3.3.3
Petr is right, I added this dependencies to the Makefile: genversion.$(OBJEXT): $(genversion_SOURCES) genversion.h Jean-Louis On 10/22/2013 08:39 AM, Jens Berg wrote: Hi Petr, I've never taken a deeper look into amanda's makefiles so the following is just a guess. It looks like there is a dependency missing or not recognized and you are using the make utility with parallel job execution enabled (option -j), so make resolves to start gcc in parallel with the generation of genversion.h. Depending on your system load the generation of that header file finishes before or after gcc needs it, which results in a kind of unreproducible behavior. Maybe this is a result of passing --disable-dependency-tracking to ./configure ?? Best Jens On Tue Oct 22 2013 11:45:20 GMT+0200 phra...@redhat.com (Petr Hracek) wrote: Hi folks, I would like to build amanda under s390x environment but it is failing with Making all in common-src make[2]: Entering directory `/builddir/build/BUILD/amanda-3.3.3/common-src' rm -f genversion.h genversion.h.new gcc -DHAVE_CONFIG_H -I. -I../config -I../gnulib -fno-strict-aliasing -D_GNU_SOURCE -I/usr/include -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include-Wall -Wextra -Wparentheses -Wdeclaration-after-statement -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wformat-security -Wsign-compare -Wfloat-equal -Wold-style-definition -Wno-strict-aliasing -Wno-unknown-pragmas -Wno-deprecated-declarations -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -march=z10 -mtune=zEC12 -fPIE -fno-strict-aliasing -c genversion.c echo '#define CC gcc' genversion.h.new echo '#define BUILT_DATE '`date`'' genversion.h.new genversion.c:38:24: fatal error: genversion.h: No such file or directory #include genversion.h ^ compilation terminated. echo '#define BUILT_MACH ' genversion.h.new mv genversion.h.new genversion.h The bug is not reproducible, so it is likely a hardware or OS problem. make[2]: Leaving directory `/builddir/build/BUILD/amanda-3.3.3/common-src' Did you observed this behaviour? configure script is called with these parameters ./configure --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/lib64 --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --disable-rpath --disable-static --disable-dependency-tracking --disable-installperms --with-amdatadir=/var/lib/amanda --with-amlibdir=/usr/lib64 --with-amperldir=/usr/lib64/perl5/vendor_perl --with-index-server=amandahost --with-tape-server=amandahost --with-config=DailySet1 --with-gnutar-listdir=/var/lib/amanda/gnutar-lists --with-smbclient=/usr/bin/smbclient --with-amandates=/var/lib/amanda/amandates --with-amandahosts --with-user=amandabackup --with-group=disk --with-tmpdir=/var/log/amanda --with-gnutar=/bin/tar --with-ssh-security --with-rsh-security --with-bsdtcp-security --with-bsdudp-security --with-krb5-security Thank you in advance. diff --git a/common-src/Makefile.am b/common-src/Makefile.am index d7000a3..40dacb5 100644 --- a/common-src/Makefile.am +++ b/common-src/Makefile.am @@ -143,6 +143,8 @@ genversion_SOURCES = genversion.c svn-info.h genversion_LDADD = $(libamanda_la_LIBADD) \ ../gnulib/libgnu.la +genversion.$(OBJEXT): $(genversion_SOURCES) genversion.h + genversion.h: $(top_builddir)/config.status -rm -f $@ $@.new echo '#define CC $(CC)' $@.new
Re: virtual tape size (take #3)
man amanda-devices MAX_VOLUME_USAGE (read-write) On devices that support it, this property will limit the total amount of data written to a volume; attempts to write beyond this point will cause the device to simulate out of space. Zero means no limit. The tapetype parameter length sets this property. ENFORCE_MAX_VOLUME_USAGE (read-write) If this property is false, limit set by MAX_VOLUME_USAGE property (and thus the tapetype LENGTH parameter) will not be verified while writing to device, allowing the volume to expand without limit. If this property is true, then MAX_VOLUME_USAGE will be enforced, limiting the total size of the volume. This property is not available on all devices; see below. Set the ENFORCE_MAX_VOLUME_USAGE The tapetype length is use in the estimate phase, so it must be the same as the MAX_VOLUME_USAGE. Jean-Louis On 10/25/2013 09:50 AM, John G. Heim wrote: Last week I asked a few questions about virtual tape size. Well, I wouldn't say I resolved them but I think I have one clue. One of the things I asked about is the meaning of the length parameter for a tape definition. I had set it to 25G for my virtual tapes but amanda was writing 38G to each vtape. This was going to be a problem because I have a quota on my virtual tape file system of 2Tb and I had therefore calculated that I could create 80 25Gb tapes. Here is what the amanda.conf man page has to say about the tape length parameter: length int Default: 2000 kbytes. How much data will fit on a tape, expressed in kbytes. Note that this value is only used by Amanda to schedule which backupswill be run. Once the backups start, Amanda will continue to write to a tape until it gets an error, regardless of what value is entered for length (but see amanda-devices(7) for exceptions). The device for virtual tapes is vfs-disk or something like that. But I couldn't find anything in the docs for how it determines how much to write to a vtape. If it keeps writing until it got an error, in my case, it would write over 2Tb until it hit the hard quota on the filesystem. So that couldn't be. Then it occured to me that 25 * 150% = 38G. . Coincidence? I recreated the vtapes with a size of 16Gb. Now amanda is writing 25Gb to each tape. My first backup wrote to 11 tapes. Slots 1-10 have 25Gb on them with 19G on the last. The amount of stuff on tapes 1-10 is not exactly the same on each tape but it's a little over 24G each. IMO, this borders on a bug. The wiki strongly implies that you can take your disk file system size and divide by the number of tapes to get the tape size. While the amanda developers aren't responsibe for the wiki being misleading, it is natural to assume the length parameter for a virtual tape is the actual size of the tape. I'm not the only one who made that assumption, so did whoever wrote the wiki entry on virtual tapes. Anyway, I'd still like to know how amanda determines when to stop writing to a vtape. I can put comments in my amanda.conf to say that the tape length is set to 16G so amanda writes 24G to 25G to each tape. But that's hardly an ideal solution.
Re: virtual tape size (take #3)
Hi John, It always works for me. I found a bug, it randomly (not that random) take the value of the tapetype length or the device max-volume-usage property. In my case, it always use the value of the tapetype length, in your case it always take the value of the device max-volume-usage property. Sine your max-volume-usage is 0, it have no limit. Can you retry by setting the tapetype length and the device max-volume-usage property to the same value (max-volume-usage is in bytes). The attached path fix the bug. Jean-Louis On 10/25/2013 12:49 PM, John G. Heim wrote: But that same man page also says, that for the vfs device, This device supports the ENFORCE_MAX_VOLUME_USAGE property. Default value is true. Furthermore, the man page says that if ENFORCE_MAX_VOLUME_USAGE is false, the volumes expand without limit. But that's not what is happening. They are consistently expanding to 150% of the tape length parameter. Like I said, I even predicted that if I set the tape length parameter to 16386 megabypes, it would end up writing 25G to each volume. That was based on the fact that when I set it to 25600 megabypes, it wrote 38G to each volume. That same man page also says, Device properties specified outside of any device definition apply to all devices. Maybe I'll try setting MAX_VOLUME_USAGE and ENFORCE_MAX_VOLUME_USAGE in my amanda.conf and see what happens. I will bet that setting ENFORCE_MAX_VOLUME_USAGE to true will have no effect. One thing that does strike me as odd is that I'm not seeing other questions of this nature while searching the list archives. Maybe it is something weird abut my set up. I'm running debian wheezy and whatever amanda is in debian wheezy. The machine was running debian squeeze last week. Amanda exhibited the same behaviour in squeeze as it is doing in wheezy. I finally upgraded from squeeze to wheezy partly because of this problem. But maybe some misconfiguration got dragged along. But how would the vfs device have gotten misconfigured. I sure didn't do that. On 10/25/13 10:02, Jean-Louis Martineau wrote: man amanda-devices MAX_VOLUME_USAGE (read-write) On devices that support it, this property will limit the total amount of data written to a volume; attempts to write beyond this point will cause the device to simulate out of space. Zero means no limit. The tapetype parameter length sets this property. ENFORCE_MAX_VOLUME_USAGE (read-write) If this property is false, limit set by MAX_VOLUME_USAGE property (and thus the tapetype LENGTH parameter) will not be verified while writing to device, allowing the volume to expand without limit. If this property is true, then MAX_VOLUME_USAGE will be enforced, limiting the total size of the volume. This property is not available on all devices; see below. Set the ENFORCE_MAX_VOLUME_USAGE The tapetype length is use in the estimate phase, so it must be the same as the MAX_VOLUME_USAGE. Jean-Louis On 10/25/2013 09:50 AM, John G. Heim wrote: Last week I asked a few questions about virtual tape size. Well, I wouldn't say I resolved them but I think I have one clue. One of the things I asked about is the meaning of the length parameter for a tape definition. I had set it to 25G for my virtual tapes but amanda was writing 38G to each vtape. This was going to be a problem because I have a quota on my virtual tape file system of 2Tb and I had therefore calculated that I could create 80 25Gb tapes. Here is what the amanda.conf man page has to say about the tape length parameter: length int Default: 2000 kbytes. How much data will fit on a tape, expressed in kbytes. Note that this value is only used by Amanda to schedule which backupswill be run. Once the backups start, Amanda will continue to write to a tape until it gets an error, regardless of what value is entered for length (but see amanda-devices(7) for exceptions). The device for virtual tapes is vfs-disk or something like that. But I couldn't find anything in the docs for how it determines how much to write to a vtape. If it keeps writing until it got an error, in my case, it would write over 2Tb until it hit the hard quota on the filesystem. So that couldn't be. Then it occured to me that 25 * 150% = 38G. . Coincidence? I recreated the vtapes with a size of 16Gb. Now amanda is writing 25Gb to each tape. My first backup wrote to 11 tapes. Slots 1-10 have 25Gb on them with 19G on the last. The amount of stuff on tapes 1-10 is not exactly the same on each tape but it's a little over 24G each. IMO, this borders on a bug. The wiki strongly implies that you can take your disk file system size and divide by the number of tapes to get the tape size. While the amanda developers aren't responsibe for the wiki being misleading, it is natural to assume the length parameter
Re: virtual tape size (take #3)
On 10/30/2013 09:32 AM, John G. Heim wrote: Did you mean to tell me to set max_volume_usage or max-volume-usage? I don't see any docs on max-volume-usage (with dashes). But I do find docs on max_volume_usage (with underscores). On the other hand, this does not seem to work: device-property max_volume_usage 26214400 $man amanda-devices PROPERTIES Both the property name and the property value are always quoted. Property names, like Amanda configuration parameters, are not case-sensitive, and - (dash) and _ (underscore) may be used interchangeably. max-volume-usage, max_volume_usage and MAX-VOLUME_USAGE are the same property name. That appears to have no effect. Amanda still wrote 38G to my virtual tapes. Try to apply the patch I sent, it is just three lines to change in the Changer.pm file. If it doesn't works, post the complete output of 'amadmin CONF config' and the complete taper debug file. Jean-Louis On 10/25/13 13:19, Jean-Louis Martineau wrote: Hi John, It always works for me. I found a bug, it randomly (not that random) take the value of the tapetype length or the device max-volume-usage property. In my case, it always use the value of the tapetype length, in your case it always take the value of the device max-volume-usage property. Sine your max-volume-usage is 0, it have no limit. Can you retry by setting the tapetype length and the device max-volume-usage property to the same value (max-volume-usage is in bytes). The attached path fix the bug. Jean-Louis On 10/25/2013 12:49 PM, John G. Heim wrote: But that same man page also says, that for the vfs device, This device supports the ENFORCE_MAX_VOLUME_USAGE property. Default value is true. Furthermore, the man page says that if ENFORCE_MAX_VOLUME_USAGE is false, the volumes expand without limit. But that's not what is happening. They are consistently expanding to 150% of the tape length parameter. Like I said, I even predicted that if I set the tape length parameter to 16386 megabypes, it would end up writing 25G to each volume. That was based on the fact that when I set it to 25600 megabypes, it wrote 38G to each volume. That same man page also says, Device properties specified outside of any device definition apply to all devices. Maybe I'll try setting MAX_VOLUME_USAGE and ENFORCE_MAX_VOLUME_USAGE in my amanda.conf and see what happens. I will bet that setting ENFORCE_MAX_VOLUME_USAGE to true will have no effect. One thing that does strike me as odd is that I'm not seeing other questions of this nature while searching the list archives. Maybe it is something weird abut my set up. I'm running debian wheezy and whatever amanda is in debian wheezy. The machine was running debian squeeze last week. Amanda exhibited the same behaviour in squeeze as it is doing in wheezy. I finally upgraded from squeeze to wheezy partly because of this problem. But maybe some misconfiguration got dragged along. But how would the vfs device have gotten misconfigured. I sure didn't do that. On 10/25/13 10:02, Jean-Louis Martineau wrote: man amanda-devices MAX_VOLUME_USAGE (read-write) On devices that support it, this property will limit the total amount of data written to a volume; attempts to write beyond this point will cause the device to simulate out of space. Zero means no limit. The tapetype parameter length sets this property. ENFORCE_MAX_VOLUME_USAGE (read-write) If this property is false, limit set by MAX_VOLUME_USAGE property (and thus the tapetype LENGTH parameter) will not be verified while writing to device, allowing the volume to expand without limit. If this property is true, then MAX_VOLUME_USAGE will be enforced, limiting the total size of the volume. This property is not available on all devices; see below. Set the ENFORCE_MAX_VOLUME_USAGE The tapetype length is use in the estimate phase, so it must be the same as the MAX_VOLUME_USAGE. Jean-Louis On 10/25/2013 09:50 AM, John G. Heim wrote: Last week I asked a few questions about virtual tape size. Well, I wouldn't say I resolved them but I think I have one clue. One of the things I asked about is the meaning of the length parameter for a tape definition. I had set it to 25G for my virtual tapes but amanda was writing 38G to each vtape. This was going to be a problem because I have a quota on my virtual tape file system of 2Tb and I had therefore calculated that I could create 80 25Gb tapes. Here is what the amanda.conf man page has to say about the tape length parameter: length int Default: 2000 kbytes. How much data will fit on a tape, expressed in kbytes. Note that this value is only used by Amanda to schedule which backupswill be run. Once the backups start, Amanda will continue to write to a tape until it gets an error, regardless of what
Re: virtual tape size (take #3)
On 10/30/2013 10:44 AM, John G. Heim wrote: How do I apply the patch? I installed amanda from the package in debian wheezy. Use the patch command, or a simple text editor (vi). Look at the patch file, Edit the Changer.pm file, replace the line that start with a '-' by the line that start with a '+' Read the documentation for the diff and patch utilities. Jean-Louis On 10/30/13 09:07, Jean-Louis Martineau wrote: On 10/30/2013 09:32 AM, John G. Heim wrote: Did you mean to tell me to set max_volume_usage or max-volume-usage? I don't see any docs on max-volume-usage (with dashes). But I do find docs on max_volume_usage (with underscores). On the other hand, this does not seem to work: device-property max_volume_usage 26214400 $man amanda-devices PROPERTIES Both the property name and the property value are always quoted. Property names, like Amanda configuration parameters, are not case-sensitive, and - (dash) and _ (underscore) may be used interchangeably. max-volume-usage, max_volume_usage and MAX-VOLUME_USAGE are the same property name. That appears to have no effect. Amanda still wrote 38G to my virtual tapes. Try to apply the patch I sent, it is just three lines to change in the Changer.pm file. If it doesn't works, post the complete output of 'amadmin CONF config' and the complete taper debug file. Jean-Louis On 10/25/13 13:19, Jean-Louis Martineau wrote: Hi John, It always works for me. I found a bug, it randomly (not that random) take the value of the tapetype length or the device max-volume-usage property. In my case, it always use the value of the tapetype length, in your case it always take the value of the device max-volume-usage property. Sine your max-volume-usage is 0, it have no limit. Can you retry by setting the tapetype length and the device max-volume-usage property to the same value (max-volume-usage is in bytes). The attached path fix the bug. Jean-Louis On 10/25/2013 12:49 PM, John G. Heim wrote: But that same man page also says, that for the vfs device, This device supports the ENFORCE_MAX_VOLUME_USAGE property. Default value is true. Furthermore, the man page says that if ENFORCE_MAX_VOLUME_USAGE is false, the volumes expand without limit. But that's not what is happening. They are consistently expanding to 150% of the tape length parameter. Like I said, I even predicted that if I set the tape length parameter to 16386 megabypes, it would end up writing 25G to each volume. That was based on the fact that when I set it to 25600 megabypes, it wrote 38G to each volume. That same man page also says, Device properties specified outside of any device definition apply to all devices. Maybe I'll try setting MAX_VOLUME_USAGE and ENFORCE_MAX_VOLUME_USAGE in my amanda.conf and see what happens. I will bet that setting ENFORCE_MAX_VOLUME_USAGE to true will have no effect. One thing that does strike me as odd is that I'm not seeing other questions of this nature while searching the list archives. Maybe it is something weird abut my set up. I'm running debian wheezy and whatever amanda is in debian wheezy. The machine was running debian squeeze last week. Amanda exhibited the same behaviour in squeeze as it is doing in wheezy. I finally upgraded from squeeze to wheezy partly because of this problem. But maybe some misconfiguration got dragged along. But how would the vfs device have gotten misconfigured. I sure didn't do that. On 10/25/13 10:02, Jean-Louis Martineau wrote: man amanda-devices MAX_VOLUME_USAGE (read-write) On devices that support it, this property will limit the total amount of data written to a volume; attempts to write beyond this point will cause the device to simulate out of space. Zero means no limit. The tapetype parameter length sets this property. ENFORCE_MAX_VOLUME_USAGE (read-write) If this property is false, limit set by MAX_VOLUME_USAGE property (and thus the tapetype LENGTH parameter) will not be verified while writing to device, allowing the volume to expand without limit. If this property is true, then MAX_VOLUME_USAGE will be enforced, limiting the total size of the volume. This property is not available on all devices; see below. Set the ENFORCE_MAX_VOLUME_USAGE The tapetype length is use in the estimate phase, so it must be the same as the MAX_VOLUME_USAGE. Jean-Louis On 10/25/2013 09:50 AM, John G. Heim wrote: Last week I asked a few questions about virtual tape size. Well, I wouldn't say I resolved them but I think I have one clue. One of the things I asked about is the meaning of the length parameter for a tape definition. I had set it to 25G for my virtual tapes but amanda was writing 38G to each vtape. This was going to be a problem because I have a quota on my virtual tape file system of 2Tb and I
Re: setuid bits on some binaries
On 10/31/2013 06:15 AM, Petr Hracek wrote: Hi amanda users, I have just a tricky question: I observed that in Fedora we are delivering amanda where some binaries have setuid bits. Are the suid bits really needed for amanda working properly? List of affected binaries is (mode 104750): /usr/lib/amanda/application/amstar /usr/lib/amanda/calcsize /usr/lib/amanda/rundump /usr/lib/amanda/runtar /usr/lib/amanda/dumper /usr/lib/amanda/planner Yes, they are needed, some files are missing: /usr/lib/amanda/application/amgtar /usr/sbin/amcheck /usr/sbin/amservice They needs root because they either read the filesystem or open a privileged port (1024) Is it necessary to have setgid bit on the directory /var/log/amanda? I think no, my logdir is 700. Jean-Louis
Re: Amanda consumes all the memory
Nuno, Which process consume a lot of memory? Can you run strace on the process? and gdb to get a few stacktrace? I want to find want the process is doing. Posting the debug file of the process can be useful too. Jean-Louis On 11/06/2013 07:30 AM, Nuno Dias wrote: Hi all, I'm using amanda-3.3.3 and right now, when I run amdump in the fase of planner all the memory of the machine is consumed by amanda and eventually the amdump is killed. The machine has 24 Giga of memory, so is not a problema of low memory. I need help to debug this problem. Thanks, Nuno
How does Amanda reassemble partials of a full backup?
I don't know what you the mean by portion or partials: - portion of the specified level0 backup for every runcycle - series of partial level0 backups created at different dates - partials from different dates I think you clearly understand that amanda do full of the dles on different days. I think what you call 'partial level0' is that only a few dle get the full on the same day. eg some dle have a full and some have a level 1. Each dle are independant, you don't restore all dle at the same time, you restore a single dle at at time. Each dle have the date for the full and level 1,2,3, ..., amrecover restore from them. You must do the restore for each dle independently. Jean-Louis Hello, I am evaluating zmanda for deployment and have the following question regarding recovery and behavior: It would appear that Amanda does a portion of the specified level0 backup for every runcycle. Ie, for every run it does size of disklist/runcycle to complete a full backup for the dumpcycle. Let's presume that the incremental backups for a dump cycle do not exist or are destroyed (perhaps by running every run with noinc?) It would appear that for a dumpcycle you have a series of partial level0 backups created at different dates. How does amrecover explain what the state of the data if it is made up of partials from different dates? http://www.backupcentral.com/wiki/index.php/AMANDA In this example it happens that the total size of the disklist is split for each run by directory. However, it would appear that in reality Amanda generates the partial level0 based on the entire size of the disklist, so presumably a partial level0 is in fact a partial set of files comprising total size/runcycle.
Release of Amanda-3.3.5
Hello, The Amanda core team is pleased to announce the release of Amanda 3.3.5. Source tarballs are available from * http://www.amanda.org * https://sourceforge.net/project/showfiles.php?group_id=120 Binaries for many systems are available from * http://www.zmanda.com/download-amanda.php Documentation can be found at * http://wiki.zmanda.com Here's a list of the changes for release 3.3.5 (from the NEWS file): Look at the ReleaseNotes and ChangeLog file for more details. * amtape o faster 'verify' command. * fix parsing of config override arguments. * amsamba o Add REGEX-MATCH property. * amvault o Print progress status. * ndmp device o INDIRECT property default to yes. * Many bugs fix. Jean-Louis
Re: Which blocksize do I need to set and where?
Tom,
You can define the block size as the BLOCK-SIZE device property in the
changer section or in the tapetype, the device-property is used if it is
set.
You can define the read_block_size as the READ-BLOCK-SIZE device
property in the changer section or in the tapetype, the device-property
is used if it is set.
The problem is the tape is already written with a block larger than 2048k.
dd if=/dev/rmt/0bn bs=512m count=1 of=/dev/null
should print the size of the block (if = 512m)
You can increase the value of the READ-BLOCK-SIZE device property, the
readblocksize tapetype setting or simply use the '-f' flag of amlabel:
amlabel -f weekly weekly00 slot 1
Jean-Louis
On 12/16/2013 08:01 PM, Tom Robinson wrote:
Amanda 3.3.3
OmniOS (OpenSolaris derivative)
Hi,
I've got an IBM TS3200 robot working with mtx. The raw mtx command sees the
robot and tapes OK but
when I use amtape I get a 'block size too small' error.
The amlabel command also fails with:
$ amlabel weekly weekly00 slot 1
Reading label...
Error reading volume label: Error reading Amanda header: block size too small
Not writing label.
In amanda.conf I adjusted the blocksize and readblocksize but amanda is still
not satisfied.
Which blocksize is amanda unhappy about and where can I successfully adjust the
settings?
Kind regards,
Tom
in amanda.conf:
define changer robot {
tpchanger chg-robot:/dev/scsi/changer/c1t5000E11156304003d1
property tape-device 0=tape:/dev/rmt/0bn
#property eject-before-unload yes
property use-slots 1-23
device-property BLOCK_SIZE 2048k
}
tapedev robot
tapetype ULT3580-TD5
define tapetype global {
part_size 3G
part_cache_type none
}
define tapetype ULT3580-TD5 {
global
comment Created by amtapetype; compression enabled
length 1483907072 kbytes
filemark 1820 kbytes
speed 86133 kps
blocksize 2048 kbytes
readblocksize 2048 kbytes
}
$ mtx status
Storage Changer /dev/scsi/changer/c1t5000E11156304003d1:1 Drives, 24 Slots (
1 Import/Export )
Data Transfer Element 0:Full (Storage Element 3 Loaded):VolumeTag = 050CHOL5
Storage Element 1:Full :VolumeTag=WEEK00L5
Storage Element 2:Full :VolumeTag=WEEK01L5
Storage Element 3:Empty
Storage Element 4:Full :VolumeTag=051CHOL5
Storage Element 5:Full :VolumeTag=052CHOL5
Storage Element 6:Full :VolumeTag=053CHOL5
Storage Element 7:Full :VolumeTag=054CHOL5
Storage Element 8:Empty
Storage Element 9:Empty
Storage Element 10:Empty
Storage Element 11:Empty
Storage Element 12:Empty
Storage Element 13:Empty
Storage Element 14:Empty
Storage Element 15:Empty
Storage Element 16:Empty
Storage Element 17:Empty
Storage Element 18:Empty
Storage Element 19:Empty
Storage Element 20:Empty
Storage Element 21:Empty
Storage Element 22:Empty
Storage Element 23:Empty
Storage Element 24 IMPORT/EXPORT:Empty
$ amtape weekly inventory
slot 1: Error reading Amanda header: block size too small barcode WEEK00L5
slot 2: Error reading Amanda header: block size too small barcode WEEK01L5
slot 3: label amtapetype-1255848847 barcode 050CHOL5 (in drive 0)
slot 4: Error reading Amanda header: block size too small barcode 051CHOL5
slot 5: Error reading Amanda header: block size too small barcode 052CHOL5
slot 6: Error reading Amanda header: block size too small barcode 053CHOL5
slot 7: Error reading Amanda header: block size too small barcode 054CHOL5
(current)
slot 8: unknown state
slot 9: unknown state
slot 10: unknown state
slot 11: unknown state
slot 12: unknown state
slot 13: unknown state
slot 14: unknown state
slot 15: unknown state
slot 16: unknown state
slot 17: unknown state
slot 18: unknown state
slot 19: unknown state
slot 20: unknown state
slot 21: unknown state
slot 22: unknown state
slot 23: unknown state
amtape.20131217113945.debug:
Tue Dec 17 11:49:45 2013: thd-85d2400: amtape: pid 3379 ruid 33 euid 33 version
3.3.3: start at Tue
Dec 17 11:49:45 2013
Tue Dec 17 11:49:45 2013: thd-85d2400: amtape: Arguments: weekly inventory
Tue Dec 17 11:49:45 2013: thd-85d2400: amtape: pid 3379 ruid 33 euid 33 version
3.3.3: rename at Tue
Dec 17 11:49:45 2013
Tue Dec 17 11:49:45 2013: thd-85d2400: amtape: chg-robot: using statefile
'/var/opt/csw/amanda/chg-robot-dev-scsi-changer-c1t5000E11156304003d1'
Tue Dec 17 11:49:45 2013: thd-85d2400: amtape: invoking /opt/csw/sbin/mtx -f
/dev/scsi/changer/c1t5000E11156304003d1 status
Tue Dec 17 11:49:46 2013: thd-85d2400: amtape: mtx: Storage Changer
/dev/scsi/changer/c1t5000E11156304003d1:1 Drives, 24 Slots ( 1 Import/Export )
Tue Dec 17 11:49:46 2013: thd-85d2400: amtape: mtx: Data Transfer Element
0:Full (Storage Element 3
Loaded):VolumeTag = 050CHOL5
Tue Dec 17 11:49:46 2013: thd-85d2400: amtape: mtx: Storage Element 1:Full
:VolumeTag=WEEK00L5
Tue Dec 17 11:49:46 2013: thd-85d2400: amtape:
Re: trouble with test restore
Michael,
On the server, the global tpchanger and tapedev are now synonymous, all
setting must be put in the changer section.
On the client, only tapedev can be set, but you should set it to the
name of the changer:
tapedev my_vtapes
Jean-Louis
On 12/16/2013 06:21 PM, Michael Stauffer wrote:
Hi Everyone,
I've gotten my focus back to this and sorted out my problems.
1) 'amrecover' on clients was unable to connect to server.
Turns out the server's firewall was blocking amanda's ports. Easy fix.
Should have thought of this when the tutorial said to check the
firewall on the clients which I did, but I forgot about the server.
2) 'amrecover' hangs as it tries to load a tape after 'extract' command:
I looked at the amidxtaped log on the server, and saw that the tape
device name/file was not recognized/found. Turns out I had a different
name defined for 'tpchanger' on the server set configuration, than for
the clients' configuration. Changing the clients' configuration fixed
this. I'm curious about the parameter naming - in the
server's /etc/amanda/DailySet1/amanda.conf file, I define
...
define changer my_vtapes {
tpchanger chg-disk:/amandatest/vtape/DailySet1
property num-slot 10
property auto-create-slot yes
}
tpchanger my_vtapes
...
And in the clients' /etc/amanda/amanda-client.conf, it's
tapedev chg-disk://amandatest/vtape/DailySet1 # your tape
device
Just curious where 'tapedev' gets mapped to 'tpchanger'.
-M
On Tue, Nov 26, 2013 at 9:04 AM, Debra S Baddorf badd...@fnal.gov
mailto:badd...@fnal.gov wrote:
Recovery from server would work if it's the same type node as the
client (has to be able to run same version of system dump able
to read the saved file). It would place the recovered files in
your current directory on the server, not on the client.
As for your client's new problem, I'm adding the Amanda-users back
into this reply cuz I can diagnose that from home. Hope someone
else can step in here.
Deb (from phone)
On Nov 25, 2013, at 9:08 PM, Michael Stauffer
mgsta...@gmail.com mailto:mgsta...@gmail.com wrote:
Thanks Deb. I found an amrecover log but first this:
I realized I've been trying to recover from the server (i.e. run
amrecover on the server), and not the client as directed in the
tutorial (but shouldn't recovery from the server work too?).
Running amrecover on the client, I get this:
[root@cslim ~]# amrecover DailySet1
AMRECOVER Version 3.3.4. Contacting server on
cback.uphs.upenn.edu http://cback.uphs.upenn.edu ...
[request failed: No route to host]
From the client (cslim) I can ping and ssh to the server (even
passwordless ssh now). I'm using bsdtcp for auth - is there some
other setup for that?
Thanks.
-M
On Mon, Nov 25, 2013 at 6:16 PM, Debra S Baddorf
badd...@fnal.gov mailto:badd...@fnal.gov wrote:
xtracting files using tape drive
cback://amandatest/vtape/DailySet1 on host localhost.
Load tape DailySet1-3 now
Continue [?/Y/n/s/d]? y
[this is where it just hangs up]
--
Other info:
/var/log/amanda/log.error/ is empty
(As an aside, there are a large multitude of various log
files - is there an amanda command that parses them all to
look for errors and reports them?)
Have you tried
$ grep -ir DailySet1-3 /tmp/amanda/
(substitute if your logs aren't being sent to that directory)
There should also be a file *amrecover*mmdd* though
the hangup might be in a *taper* file or something else like
that.
Those are some first steps, in case better info doesn't come
soon!
Deb Baddorf
Fermilab
Re: Transient data-path errors when running amcheck
On 12/30/2013 10:46 AM, Steven Backus wrote: The problem I'm having with both chg-zd-mtx and chg-robot is the drive doesn't become ready in time. The first amcheck alwayws fails but the 2nd one succeeds. I've tried various delay settings to both without success. It' an Ultrium robot, any ideas on how I can avoid this problem? There is a lot of properties that can be set with chg-robot: EJECT-BEFORE-UNLOAD EJECT-DELAY LOAD-POLL UNLOAD-DELAY See the amanda-changers man page. Increase all delay to insane large value, provide moe information if it still fail. Jean-Louis
Re: amlabel segmentation fault
Kevin,
run amlabel under gdb:
$ gdb perl
(gdb) run /usr/local/sbin/amlabel --version
(gdb) bt
(gdb) list
Jean-Louis
On 01/04/2014 11:01 PM, Kervin L. Pierre wrote:
Hi,
This Segfault seems to occur occasionally and for different reasons. It's possible that
amlabel do not handle unknown devices gracefully. But I'm still looking. My tapedevice
is S3.
But I just built 3.3.5 on a Ubuntu desktop and now I get a segfault whenever I
run amlabel...
$ perl -d /usr/local/sbin/amlabel --version
Loading DB routines from perl5db.pl version 1.33
Editor support available.
Enter h or `h h' for help, or `man perldebug' for more help.
Signal SEGV at /usr/local/share/perl/5.14.2/Amanda/Device.pm line 12
require Amanda/Device.pm called at /usr/local/sbin/amlabel line 29
main::BEGIN() called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
line 0
eval {...} called at /usr/local/share/perl/5.14.2/Amanda/Device.pm line 0
Device.pm looks like
# This file was automatically generated by SWIG (http://www.swig.org).
# Version 2.0.4
#
# Do not make changes to this file unless you know what you are doing--modify
# the SWIG interface file instead.
package Amanda::Device;
use base qw(Exporter);
use base qw(DynaLoader);
require Amanda::Header;
package Amanda::Devicec;
bootstrap Amanda::Device;
package Amanda::Device;
@EXPORT = qw();
With the bootstrap Amanda line being line 12.
Should that line read package Amanda::Devicec;?
Any idea what the issue could be?
Best regards,
Kervin
Web Services Design, Development and Maintenance
http://adevsoft.com/
Re: amlabel segmentation fault
Kervin,
Looks like there is a bug if libcurl use GNUTLS.
Can you try the attached patch?
Jean-Louis
On 01/05/2014 12:10 PM, Kervin L. Pierre wrote:
Hi Jean-Louis,
Thanks for the response. Is there a way to rebuild with '-g' for debugging
support and to avoid stripping symbols? Would that help?
Here is the gdb output...
$ gdb --args perl /usr/local/sbin/amlabel --version
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/perl...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/perl /usr/local/sbin/amlabel --version
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Program received signal SIGSEGV, Segmentation fault.
0x7489876d in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
(gdb) backtrace
#0 0x7489876d in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
#1 0x748925ae in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
#2 0x7489004c in gcry_control () from
/lib/x86_64-linux-gnu/libgcrypt.so.11
#3 0x70c75259 in device_api_init () at device.c:64
#4 0x70ebc1f2 in boot_Amanda__Device (my_perl=optimized out,
cv=optimized out) at Amanda/Device.c:4676
#5 0x77b10591 in Perl_pp_entersub () from /usr/lib/libperl.so.5.14
#6 0x77b07d36 in Perl_runops_standard () from /usr/lib/libperl.so.5.14
#7 0x77aa43c0 in Perl_call_sv () from /usr/lib/libperl.so.5.14
#8 0x77aa51cc in Perl_call_list () from /usr/lib/libperl.so.5.14
#9 0x77a8faf1 in ?? () from /usr/lib/libperl.so.5.14
#10 0x77a9b7b3 in Perl_newATTRSUB () from /usr/lib/libperl.so.5.14
#11 0x77a9bfa2 in Perl_utilize () from /usr/lib/libperl.so.5.14
#12 0x77ac989e in Perl_yyparse () from /usr/lib/libperl.so.5.14
#13 0x77aa9b76 in perl_parse () from /usr/lib/libperl.so.5.14
#14 0x00400dae in main ()
(gdb) list
1 built-in: No such file or directory.
Best regards,
Kervin
Web Services Design, Development and Maintenance
http://adevsoft.com/
-Original Message-
From: Jean-Louis Martineau [mailto:martin...@zmanda.com]
Sent: Sunday, January 5, 2014 9:19 AM
To: Kervin L. Pierre
Cc: amanda-users@amanda.org
Subject: Re: amlabel segmentation fault
Kevin,
run amlabel under gdb:
$ gdb perl
(gdb) run /usr/local/sbin/amlabel --version
(gdb) bt
(gdb) list
Jean-Louis
On 01/04/2014 11:01 PM, Kervin L. Pierre wrote:
Hi,
This Segfault seems to occur occasionally and for different reasons. It's possible that
amlabel do not handle unknown devices gracefully. But I'm still looking. My tapedevice
is S3.
But I just built 3.3.5 on a Ubuntu desktop and now I get a segfault whenever I
run amlabel...
$ perl -d /usr/local/sbin/amlabel --version
Loading DB routines from perl5db.pl version 1.33 Editor support
available.
Enter h or `h h' for help, or `man perldebug' for more help.
Signal SEGV at /usr/local/share/perl/5.14.2/Amanda/Device.pm line 12
require Amanda/Device.pm called at /usr/local/sbin/amlabel line 29
main::BEGIN() called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
line 0
eval {...} called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
line 0
Device.pm looks like
# This file was automatically generated by SWIG (http://www.swig.org).
# Version 2.0.4
#
# Do not make changes to this file unless you know what you are
doing--modify # the SWIG interface file instead.
package Amanda::Device;
use base qw(Exporter);
use base qw(DynaLoader);
require Amanda::Header;
package Amanda::Devicec;
bootstrap Amanda::Device;
package Amanda::Device;
@EXPORT = qw();
With the bootstrap Amanda line being line 12.
Should that line read package Amanda::Devicec;?
Any idea what the issue could be?
Best regards,
Kervin
Web Services Design, Development and Maintenance http://adevsoft.com/
diff --git a/common-src/glib-util.c b/common-src/glib-util.c
index 713f0fc..905d518 100644
--- a/common-src/glib-util.c
+++ b/common-src/glib-util.c
@@ -27,6 +27,7 @@
#include amanda.h
#include glib-util.h
+#include pthread.h
#include conffile.h /* For find_multiplier. */
#ifdef HAVE_LIBCURL
@@ -71,7 +72,13 @@ GCRY_THREAD_OPTION_PTHREAD_IMPL;
static void
init_ssl(void)
{
-gcry_control(GCRYCTL_SET_THREAD_CBS);
+gcry_control(GCRYCTL_SET_THREAD_CBS, gcry_threads_pthread);
+
+if (!gcry_check_version (GCRYPT_VERSION)) {
+ g_critical(libgcrypt version mismatch);
+}
+
+gcry_control (GCRYCTL_INITIALIZATION_FINISHED, 0);
}
#else /* LIBCURL_USE_GNUTLS */
Re: Transient data-path errors when running amcheck
Steven, The complete output of mtx is not logged, run it on the command line to get the complete output: /usr/sbin/mtx -f /dev/changer nobarcode status 'it always works the 2nd time', Did it always works the 3rd and 4th time? When is the first time? Jean-Louis On 01/06/2014 12:27 PM, Steven Backus wrote: Amanda can't fix bug in the scsi hardware/firmware. It's possible there's a scsi bug but since it always works the 2nd time hopefully more of a timing issue. Post the amtape debug file when it fail. amtape.20140106091626.debug: Mon Jan 6 09:16:26 2014: thd-0xe1ff960: amtape: pid 12109 ruid 0 euid 0 version 3.3.5: start at Mon Jan 6 09:16:26 2014 Mon Jan 6 09:16:26 2014: thd-0xe1ff960: amtape: Arguments: gen slot 1 Mon Jan 6 09:16:26 2014: thd-0xe1ff960: amtape: pid 12109 ruid 0 euid 0 version 3.3.5: rename at Mon Jan 6 09:16:26 2014 Mon Jan 6 09:16:26 2014: thd-0xe1ff960: amtape: chg-robot: using statefile '/local/etc/amanda/gen/changer-state' Mon Jan 6 09:16:26 2014: thd-0xe1ff960: amtape: invoking /usr/sbin/mtx -f /dev/changer nobarcode status Mon Jan 6 09:16:26 2014: thd-0xe1ff960: amtape: new Amanda::Changer::Error: type='fatal', message='error from mtx: SCSI error; Sense Key=No Sense' Mon Jan 6 09:16:26 2014: thd-0xe1ff960: amtape: pid 12109 finish time Mon Jan 6 09:16:26 2014 Steve
Re: Transient data-path errors when running amcheck
Try this patch, chg-robot retry the mtx command if it failed with 'No
Sense'.
Jean-Louis
On 01/06/2014 01:04 PM, Steven Backus wrote:
The complete output of mtx is not logged, run it on the command line to
get the complete output:
/usr/sbin/mtx -f /dev/changer nobarcode status
Storage Changer /dev/sg6:1 Drives, 7 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded)
Storage Element 1:Empty
Storage Element 2:Full
Storage Element 3:Full
Storage Element 4:Full
Storage Element 5:Full
Storage Element 6:Full
Storage Element 7:Full
'it always works the 2nd time', Did it always works the 3rd and 4th
time?
Yes, after the first fail, it always works. Then several days
later I try switching tapes and it fails again the first time and
always works again after that.
When is the first time?
The first time is Monday morning after I've done a dump to the
holding disk. I do 6 amdumps during the week:
M degraded
T flush to tape
W degraded
Th degraded
F flush to tape
S degraded
Steve
diff --git a/perl/Amanda/Changer/robot.pm b/perl/Amanda/Changer/robot.pm
index 9dbf8e1..0cafec0 100644
--- a/perl/Amanda/Changer/robot.pm
+++ b/perl/Amanda/Changer/robot.pm
@@ -2266,12 +2266,15 @@ sub status {
my ($exitstatus, $output) = @_;
if ($exitstatus != 0) {
my $err = $output;
+ for my $line (split '\n', $output) {
+ debug(mtx: $line);
+ }
# if it's a regular SCSI error, just show the sense key
my ($sensekey) = ($err =~ /mtx: Request Sense: Sense Key=(.*)\n/);
$err = SCSI error; Sense Key=$sensekey if $sensekey;
$counter--;
- if ($sensekey eq Not Ready and $counter 0) {
- debug($output);
+ if (($sensekey eq Not Ready and $counter 0) ||
+ ($sensekey eq No Sense and $counter 0)) {
return Amanda::MainLoop::call_after(1000, $run_mtx);
}
return $status_cb-(error from mtx: . $err, {});
Re: amdump output, tape usage
Brian, Maybe you defined the tape larger than it is? Are you sure the tape can hold 80M of data? Are you using hardware compression? Jean-Louis On 01/08/2014 09:13 AM, Brian Cuttler wrote: I'm not sure I understand this tape usage... 18% plus 75% 100%, isn't it? Amanda 3.3.0 Solaris 10x86 tapes are DLT IV This, using a second tape, is new behaivor. I did try a newer amanda but the dump clients wouldn't die when they needed two, amanda never completed and required a lot of daily manual cleanup. I haven't tried the latest... FAILURE DUMP SUMMARY: finsen / lev 0 partial taper: No space left on device, splitting not enabled finsen / lev 0 was successfully re-flushed USAGE BY TAPE: Label Time Size % DLEs Parts Finsen322:57 603197M 75.11717 Finsen330:48 145593M 18.1 259 259
Re: amdump output, tape usage
On 01/08/2014 10:47 AM, Brian Cuttler wrote:
Jean-Louis,
Good question, especially as I badly misspoke.
The tape is not DLT IV, it is LTO IV, I used the standard
tape type definition, provided, as I would not have used
such a specific number.
define tapetype LTO4 {
comment Dell LTO4 800Gb - Compression Off
length 802816 mbytes
filemark 0 kbytes
speed 52616 kps
}
I am not using HW compression.
I am using compress client fast for the dumptypes.
All file systems are local to the host, we have a large 255
DLE that are ZFS file systems.
That being said - I think you are correct, I am using the
wrong tape length.
If they are LTO IV tapes, they hold 400 Gig, up to 800 G with
HW compression, which we are not using...
Q - Would it be correct to reset the tape length to 400 Gig ?
no, you can write at least 603197M on a tape.
Jean-Louis
thank you/rookie mistake,
Brian
On Wed, Jan 08, 2014 at 10:06:54AM -0500, Jean-Louis Martineau wrote:
Brian,
Maybe you defined the tape larger than it is?
Are you sure the tape can hold 80M of data?
Are you using hardware compression?
Jean-Louis
On 01/08/2014 09:13 AM, Brian Cuttler wrote:
I'm not sure I understand this tape usage... 18% plus 75% 100%, isn't it?
Amanda 3.3.0
Solaris 10x86
tapes are DLT IV
This, using a second tape, is new behaivor.
I did try a newer amanda but the dump clients wouldn't die when
they needed two, amanda never completed and required a lot of
daily manual cleanup. I haven't tried the latest...
FAILURE DUMP SUMMARY:
finsen / lev 0 partial taper: No space left on device, splitting not
enabled finsen / lev 0 was successfully re-flushed
USAGE BY TAPE:
Label Time Size % DLEs Parts
Finsen322:57 603197M 75.11717
Finsen330:48 145593M 18.1 259 259
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
Re: Amanda integrity and erc
amanda 3.3 and before do not have crc check. crc check is already in the development tree and will be included in the next major release. Restoring from a corrupted archive depend of the tool used. gtar can generally restore corrupted archive, some manual intervention can be required. software compressed dump are not recoverable. Jean-Louis On 01/08/2014 08:57 PM, Schlacta, Christ wrote: What mechanisms does amanda provide to guarantee the following: 1) what was on the original drive is what is sent to the backup server 2) what was sent to the backup server is what's written to the archive 3) what's written to the archive is what's rerouted from backup 4) that any errors encountered at any of the above, or any other step in the backup process can be recovered from, at least up to a certain level of resiliency I've scoured the faq and manuals and don't recall seeing answers to any of this.
Re: 'labelstr' param in amanda.conf
On 01/09/2014 01:47 PM, Michael Stauffer wrote: Hi, I'm setting up amanda 3.3.4. Regarding 'labelstr' in amanda.conf: The documentation says: If multiple configurations are run from the same tape server host, it is helpful to set their labels to different strings (for example, DAILY[0-9][0-9]* vs. ARCHIVE[0-9][0-9]*) to avoid overwriting each other's tapes. Does this mean that if I have multiple configurations in order to break up a large 30TB data set into managable chunks, each configuration will have to have a particular set of tapes assigned to it? That seems very awkward if so. yes Why do you have multiple configurations? You should do it with one configuration and multiple dle. Jean-Louis
Re: 'changerfile' param for tape robots
The global changerfile is is a configuration file for the old changer API The changer changerfile is used as a state file by some of the new changer. Jean-Louis On 01/09/2014 01:48 PM, Michael Stauffer wrote: Hi, I'm working on setting up a robot tape changer. The docs for chg-robot:DEVICE say this:the changerfile parameter can be used to specify a filename at which it should store its state. Ordinarily, this state is stored in a file named after the changer device under $localstatedir/amanda, e.g., /var/amanda/chg-robot-dev-sg0. There should be a single such statefile for each distinct tape library attached to the Amanda server, even if multiple Amanda configurations reference that library. Is this saying I have to define 'changerfile', or that it will default to placing it in $localstatedir/amanda? Also, some other refs to this param on the web say that it's for a configuration file, not a state file. Can I ignore those? Thanks. -M
Re: querying device-side compression setting
On 01/09/2014 01:44 PM, Michael Stauffer wrote: Hi, I'm setting up amanda 3.3.4 with a Quantum Scalar i500 tape library. Regrading compression options, I'll go with the recommendation in the documentation to let Amanda do the compression client-side. How can I determine if hardware compression is enabled on my tape library? I can't find anything about it in the library. Is this option controlled by amanda or other mtx settings? Thanks. Amanda do not set/unset hardware compression, it could be a feature to add to amanda. The hardware compression is controlled by mt. Jean-Louis
Re: amlabel segmentation fault
Kervin,
Did you try the patch?
Jean-Louis
On 01/06/2014 09:13 AM, Jean-Louis Martineau wrote:
Kervin,
Looks like there is a bug if libcurl use GNUTLS.
Can you try the attached patch?
Jean-Louis
On 01/05/2014 12:10 PM, Kervin L. Pierre wrote:
Hi Jean-Louis,
Thanks for the response. Is there a way to rebuild with '-g' for
debugging support and to avoid stripping symbols? Would that help?
Here is the gdb output...
$ gdb --args perl /usr/local/sbin/amlabel --version
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show
copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/perl...(no debugging symbols
found)...done.
(gdb) run
Starting program: /usr/bin/perl /usr/local/sbin/amlabel --version
[Thread debugging using libthread_db enabled]
Using host libthread_db library
/lib/x86_64-linux-gnu/libthread_db.so.1.
Program received signal SIGSEGV, Segmentation fault.
0x7489876d in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
(gdb) backtrace
#0 0x7489876d in ?? () from
/lib/x86_64-linux-gnu/libgcrypt.so.11
#1 0x748925ae in ?? () from
/lib/x86_64-linux-gnu/libgcrypt.so.11
#2 0x7489004c in gcry_control () from
/lib/x86_64-linux-gnu/libgcrypt.so.11
#3 0x70c75259 in device_api_init () at device.c:64
#4 0x70ebc1f2 in boot_Amanda__Device (my_perl=optimized
out, cv=optimized out) at Amanda/Device.c:4676
#5 0x77b10591 in Perl_pp_entersub () from
/usr/lib/libperl.so.5.14
#6 0x77b07d36 in Perl_runops_standard () from
/usr/lib/libperl.so.5.14
#7 0x77aa43c0 in Perl_call_sv () from /usr/lib/libperl.so.5.14
#8 0x77aa51cc in Perl_call_list () from
/usr/lib/libperl.so.5.14
#9 0x77a8faf1 in ?? () from /usr/lib/libperl.so.5.14
#10 0x77a9b7b3 in Perl_newATTRSUB () from
/usr/lib/libperl.so.5.14
#11 0x77a9bfa2 in Perl_utilize () from /usr/lib/libperl.so.5.14
#12 0x77ac989e in Perl_yyparse () from /usr/lib/libperl.so.5.14
#13 0x77aa9b76 in perl_parse () from /usr/lib/libperl.so.5.14
#14 0x00400dae in main ()
(gdb) list
1built-in: No such file or directory.
Best regards,
Kervin
Web Services Design, Development and Maintenance
http://adevsoft.com/
-Original Message-
From: Jean-Louis Martineau [mailto:martin...@zmanda.com]
Sent: Sunday, January 5, 2014 9:19 AM
To: Kervin L. Pierre
Cc: amanda-users@amanda.org
Subject: Re: amlabel segmentation fault
Kevin,
run amlabel under gdb:
$ gdb perl
(gdb) run /usr/local/sbin/amlabel --version
(gdb) bt
(gdb) list
Jean-Louis
On 01/04/2014 11:01 PM, Kervin L. Pierre wrote:
Hi,
This Segfault seems to occur occasionally and for different
reasons. It's possible that amlabel do not handle unknown devices
gracefully. But I'm still looking. My tapedevice is S3.
But I just built 3.3.5 on a Ubuntu desktop and now I get a segfault
whenever I run amlabel...
$ perl -d /usr/local/sbin/amlabel --version
Loading DB routines from perl5db.pl version 1.33 Editor support
available.
Enter h or `h h' for help, or `man perldebug' for more help.
Signal SEGV at /usr/local/share/perl/5.14.2/Amanda/Device.pm line 12
require Amanda/Device.pm called at /usr/local/sbin/amlabel line 29
main::BEGIN() called at
/usr/local/share/perl/5.14.2/Amanda/Device.pm line 0
eval {...} called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
line 0
Device.pm looks like
# This file was automatically generated by SWIG (http://www.swig.org).
# Version 2.0.4
#
# Do not make changes to this file unless you know what you are
doing--modify # the SWIG interface file instead.
package Amanda::Device;
use base qw(Exporter);
use base qw(DynaLoader);
require Amanda::Header;
package Amanda::Devicec;
bootstrap Amanda::Device;
package Amanda::Device;
@EXPORT = qw();
With the bootstrap Amanda line being line 12.
Should that line read package Amanda::Devicec;?
Any idea what the issue could be?
Best regards,
Kervin
Web Services Design, Development and Maintenance http://adevsoft.com/
Re: Transient data-path errors when running amcheck
Steven, Let me know if the patch works or not. Jean-Louis On 01/06/2014 01:13 PM, Jean-Louis Martineau wrote: Try this patch, chg-robot retry the mtx command if it failed with 'No Sense'. Jean-Louis On 01/06/2014 01:04 PM, Steven Backus wrote: The complete output of mtx is not logged, run it on the command line to get the complete output: /usr/sbin/mtx -f /dev/changer nobarcode status Storage Changer /dev/sg6:1 Drives, 7 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Full Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full Storage Element 7:Full 'it always works the 2nd time', Did it always works the 3rd and 4th time? Yes, after the first fail, it always works. Then several days later I try switching tapes and it fails again the first time and always works again after that. When is the first time? The first time is Monday morning after I've done a dump to the holding disk. I do 6 amdumps during the week: M degraded T flush to tape W degraded Th degraded F flush to tape S degraded Steve
Re: Transient data-path errors when running amcheck
Patch 1 2 are already committed. I committed the third path. Thanks for reporting the bug and testing the patch. Jean-Louis On 01/10/2014 11:43 AM, Steven Backus wrote: Jean-Louis writes: Let me know if the patch works or not. There were 3 patches: 1. Transient data-path errors when running amcheck 2. amtape-shows-slot-empty-but-mtx-doesn-t 3. chg-robot retry the mtx command if it failed with 'No Sense' -- All the patches worked great, I'm all fixed up now. Thanks Jean-Louis. Steve
Re: Provide list of files changed to avoid the crawl
Varun, You could add a pre-dle-estimate/pre-dle-backup script that put the list of files in a file and configure an 'exclude list' for amgtar to use that file. If you backup only files (no directory) then amanda will never notice when files are removed, so a restore will also restore removed files. Jean-Louis On 01/24/2014 09:09 AM, Varun Shastry wrote: Hi experts, I came to know that amanda client/agent crawls the file system under the given path to get the list of files that have changed since the previous backup. But in my use case because of the file system size (in several TBs using any of the clustered file system) I can't afford crawl every time. But there is a utility I use, which gives me list of files changed for any given two points in time. My main question here is that, Is there any method I could use to provide the list of files changed to the amanda client so that I can avoid amanda from crawling? If its there can I have some pointers to go through it? Thanks Varun Shastry PS: I agree, for full fledged backup crawling suggested, but with the above method I can at least avoid crawling for differential/incremental backups.
Re: amanda and pigz
Use the '-r' argument of amrestore and manually uncompress the file with pigz or gzip Jean-Louis On 01/27/2014 01:35 PM, Stefan G. Weichinger wrote: Do I have to use a specific version of amanda (newer than release X) to make use of pigz? I use it for compressing on a new client but the amrestore on the server has problems to unpack the stuff: amanda@backup /mnt/md4/restore/verify $ amrestore /dev/nst0 Restoring from tape daily03 starting with file 1. amrestore: 1: restoring split dumpfile: date 20140123220010 host main disk virt-backup-IKW_SQL part 1/UNKNOWN lev 2 comp N program /bin/tar amrestore: 2: restoring split dumpfile: date 20140123220010 host main disk 2013 part 1/UNKNOWN lev 0 comp cust program /bin/tar client_custom_compress /usr/bin/pigz ERROR: /usr/bin/pigz exited with status 2 amanda-3.2.1 on the server (we had to keep it on that version because of several dependencies ... app, glibc, kernel) ... pigz installed long after amanda ... in the correct path. So far I haven't found out what status 2 means here. I assume I should re-install amanda with debug on and read the logs, right? Thanks, Stefan
Re: amanda and pigz
On 01/28/2014 09:00 AM, Michael Müskens wrote: 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 You can't use amrestore to directly read the dump from a vtape, use something like: amrestore -r file:/backup/tapepools/DailySet/DailySet-69 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 Jean-Louis 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.
