Re: holding disk not used?
It appears that you are telling amanda to use -50GB of space for your holding
diskwhy would you want a negative number?
Mine us configured as:
use 17 Mb
Anyone on this?
Right now this is a show stopper for me :(
jf
* Jean-Francois Malouin jean-francois.malo...@bic.mni.mcgill.ca [20110815
13:26]:
Hi,
I've have this seemingly simple problem but I can't put my finger on
it :)
I just installed amanda-3.3.0 on a new server and amanda doesn't seem
to use the holding disk: it port-dumps directly to tape and if I
specify 'holdingdisk required' in the dumptype the run simply fails:
define holdingdisk holddisk {
directory /holddisk/charm
use -50Gb
chunksize 0
}
define dumptype app-amgtar-span {
global
program APPLICATION
application app-amgtar
priority high
allow-split
holdingdisk required
compress none
}
Permissions are ok for /holddisk/charm.
I've attached the amdump log file. I can provide more debug upon
request.
amdump log has this:
driver: flush size 0
find diskspace: not enough diskspace. Left with 1277107616 K
driver: state time 1642.093 free kps: 1024000 space: 0 taper: idle
idle-dumpers: 12 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle:
no-diskspace
The tapetype definition is:
define tapetype tape-lto5 {
comment Created by amtapetype; compression disabled
length 1480900608 kbytes
filemark 3413 kbytes
speed 107063 kps
blocksize 2048 kbytes
part-size 100gb
part-cache-max-size 100gb
}
and the DLE is
gaspar /raid/ipl {
app-amgtar-span
record no
}
??
thanks in advance,
jf
amdump: start at Fri Aug 12 20:59:45 EDT 2011
amdump: datestamp 20110812
amdump: starttime 20110812205945
amdump: starttime-locale-independent 2011-08-12 20:59:45 EDT
driver: pid 5120 executable /opt/amanda-3.3.0/libexec/amanda/driver version
3.3.0
planner: pid 5119 executable /opt/amanda-3.3.0/libexec/amanda/planner version
3.3.0
planner: build: VERSION=Amanda-3.3.0
planner:BUILT_DATE=Wed Aug 10 13:24:08 EDT 2011 BUILT_MACH=
planner:BUILT_REV=4084 BUILT_BRANCH=3_3 CC=gcc
planner: paths: bindir=/opt/amanda-3.3.0/bin
planner:sbindir=/opt/amanda-3.3.0/sbin
planner:libexecdir=/opt/amanda-3.3.0/libexec
planner:amlibexecdir=/opt/amanda-3.3.0/libexec/amanda
planner:mandir=/opt/man AMANDA_TMPDIR=/var/tmp/amanda
planner:AMANDA_DBGDIR=/var/tmp/amanda
planner:CONFIG_DIR=/opt/amanda-3.3.0/etc/amanda
planner:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump
planner:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
planner:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF
planner:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar
planner:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip
planner: LPRCMD=UNDEF MAILER=UNDEF
planner:listed_incr_dir=/opt/amanda-3.3.0/var/amanda/gnutar-lists
planner: defs: DEFAULT_SERVER=edgar DEFAULT_CONFIG=charm
planner:DEFAULT_TAPE_SERVER=edgar
planner:DEFAULT_TAPE_DEVICE=tape:/dev/nst0 NEED_STRSTR
planner:AMFLOCK_POSIX AMFLOCK_FLOCK AMFLOCK_LOCKF AMFLOCK_LNLOCK
planner:SETPGRP_VOID AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
planner:CLIENT_LOGIN=amanda CHECK_USERID HAVE_GZIP
planner:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
planner:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
READING CONF INFO...
planner: timestamp 20110812205945
planner: tape_length is set from tape length (1480900608 KB) * runtapes (3)
==
4442701824 KB
planner: time 0.000: startup took 0.000 secs
SENDING FLUSHES...
ENDFLUSH
SETTING UP FOR ESTIMATES...
planner: time 0.000: setting up estimates for gaspar:/raid/ipl
gaspar:/raid/ipl overdue 15199 days for level 0
setup_estimate: gaspar:/raid/ipl: command 0, options: nonelast_level -1
next_level0 -15199 level_days 0getting estimates 0 (-3) -1 (-3) -1 (-3)
driver: tape size 1480900608
planner: time 0.000: setting up estimates took 0.000 secs
GETTING ESTIMATES...
reserving 0 out of 0 for degraded-mode dumps
driver: started dumper0 pid 5122
driver: send-cmd time 0.001 to dumper0: START 20110812205945
driver: started dumper1 pid 5123
driver: send-cmd time 0.001 to dumper1: START 20110812205945
driver: started dumper2 pid 5124
driver: send-cmd time 0.002 to dumper2: START 20110812205945
driver: started dumper3 pid 5125
driver: send-cmd time 0.002 to dumper3: START 20110812205945
driver: started dumper4 pid 5126
driver: send-cmd time 0.002 to dumper4: START 20110812205945
driver: started dumper5 pid 5127
driver: send-cmd time 0.002 to dumper5: START 20110812205945
driver: started dumper6 pid 5128
driver: send-cmd time 0.002 to dumper6: START 20110812205945
driver: started dumper7 pid 5129
driver: send-cmd time 0.003 to dumper7: START 20110812205945
driver: started dumper8 pid 5130
Re: preventing dump on (host) as directed??
On Mon, 3 Aug 2009, Dustin J. Mitchell wrote: On Mon, Aug 3, 2009 at 10:36 AM, u...@3.am wrote: However, one of the filesystems still failed to back up. Furthermore, it used 3 different virtual tapes for this run, even though I set: It looks like it only used one tape -- what makes you think it used three? How large are your tapes? It wrote ~1.8G of data, then stopped. Did that filesystem run out of space? No, the file system has some 300GB of available space, and the total backup would have been kess than 20GB. However, I had the tapetypes set to be 50GB and between this and other configs, may have had more 50GB tapes defined this way than there is space for. I never actually backed up anywhere near that much data or used that much space. Does that matter? Also, can I assume that there is no good reason to use a holding disk on the backup server if you're doing disk based virtual tapes? TIA! James Smallacombe PlantageNet, Inc. CEO and Janitor u...@3.am http://3.am =
preventing dump on (host) as directed??
Hi:
I have amanda 2.5.1p3 running on a server and amanda 2.6.1p1 on the client
in this case. I set up 3 virtual tapes on disk with a 3 week
dumpcycle and a 3 tape tapecycle. I then saw somewhere that you
should have one more tape in your tapecycle than in your dumpcycle, so I
added one.
I am doing level 0 full backups only, but not yet on a regular basis for
these hosts. Because I had a failure the first time, I added this to my
amanda.conf:
usetimestamps yes # allow more than one run per day
However, one of the filesystems still failed to back up. Furthermore, it
used 3 different virtual tapes for this run, even though I set:
runtapes 1# number of tapes to be used in a single run
Here was the report:
These dumps were to tape NS3_4.
The next tape Amanda expects to use is: NS3_1.
FAILURE AND STRANGE DUMP SUMMARY:
ns3.pil.net /dev/mirror/gm0s1g lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 1:20
Dump Time (hrs:min)1:12 1:12 0:00
Output Size (meg)1830.7 1830.70.0
Original Size (meg) 4943.6 4943.60.0
Avg Compressed Size (%)37.0 37.0--
Filesystems Dumped3 3 0
Avg Dump Rate (k/s) 436.8 436.8--
Tape Time (hrs:min)1:18 1:18 0:00
Tape Size (meg) 1830.7 1830.70.0
Tape Used (%) 3.13.10.0
Filesystems Taped 5 5 0
Chunks Taped 0 0 0
Avg Tp Write Rate (k/s) 402.7 402.7--
USAGE BY TAPE:
Label Time Size %NbNc
NS3_4 1:18 1874624k3.1 5 0
NOTES:
planner: tapecycle (4) = runspercycle (21)
planner: Last full dump of ns3.pil.net:/dev/mirror/gm0s1a on tape NS3_0
overwritten in 4 runs.
planner: Last full dump of ns3.pil.net:/dev/mirror/gm0s1g on tape NS3_3
overwritten in 2 runs.
planner: Preventing bump of ns3.pil.net:/dev/mirror/gm0s1g as directed.
planner: Last full dump of ns3.pil.net:/dev/mirror/gm0s1e on tape NS3_0
overwritten in 4 runs.
planner: Last full dump of ns3.pil.net:/dev/mirror/gm0s1f on tape NS3_2
overwritten in 3 runs.
driver: ns3.pil.net /dev/mirror/gm0s1g 0 [dump to tape failed, will try
again]
taper: tape NS3_4 kb 1874720 fm 5 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS
KB/s
-- -
-
ns3.pil.net -ror/gm0s1a 0 2478757 923072 37.2 34:31 445.7 34:32
445.5
ns3.pil.net -ror/gm0s1e 0 2436963 907008 37.2 35:06 430.7 35:07
430.5
ns3.pil.net -ror/gm0s1f 0 146506 44544 30.41:55 388.1 1:56
385.2
ns3.pil.net -ror/gm0s1g 0 FAILED
(brought to you by Amanda version 2.5.1p3)
-
What's the best way to straighten out this mess, and have each backup dump
to one tape and back up everything?
Thanks,
James Smallacombe PlantageNet, Inc. CEO and Janitor
u...@3.am http://3.am
=
Restoring from virtual tapes
I've restored amanda file systems in the past from tape using amrestore. However, I switched from tapes to vtapes several months ago and am trying to restore a file system. According to the FAQs and posts I saw searching various archives, one wants to use amrecover intead of amrestore for vtapes. Trying to run as user amanda, I am told it has to be run as root. When I run it as root, I get this error: su-2.05b# amrecover -C colos AMRECOVER Version 2.5.0p2. Contacting server on ns1.pil.net ... amrecover: cannot connect to server.mydomain.net: Connection refused I then add the user root to ~amanda/.amandahosts, but it doesn't make a difference: (Partial) cat ~amanda/.amandahosts localhost.mydomain.net amanda server.mydomain.net amanda server.mydomain.net root localhost.mydomain.net root I also tried adding to this config's amanda.conf the following: amrecover_changer file:/path/to/tapedev And it didn't help. What am I missing? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: Restoring from virtual tapes
Um, never mind...I was able to use amrestore with no problems, and for what I was doing, it was probably better than amrecover anyway. On Mon, 23 Jul 2007 [EMAIL PROTECTED] wrote: OMG, I had those two commented out, because at one time, the amanda server was a client only. It's now the server, and it's been backing up fine with just amandad in there. I just uncommented restarted inetd, but now I get the following: AMRECOVER Version 2.5.0p2. Contacting server on ns1.pil.net ... 220 ns1 AMANDA index server (2.5.0p2) ready. 200 Access OK Setting restore date to today (2007-07-23) 200 Working date set to 2007-07-23. 501 Index directory /var/adm/amanda/colos/index does not exist I assume this is because amandixd never ran on that config. The question now is, can this FS be restored, and if nos, how? Thanks! On Mon, 23 Jul 2007, Jean-Louis Martineau wrote: What is your xinetd configure on ns1.pil.net for the amandaidx and amidxtaped services? Jean-Louis [EMAIL PROTECTED] wrote: I've restored amanda file systems in the past from tape using amrestore. However, I switched from tapes to vtapes several months ago and am trying to restore a file system. According to the FAQs and posts I saw searching various archives, one wants to use amrecover intead of amrestore for vtapes. Trying to run as user amanda, I am told it has to be run as root. When I run it as root, I get this error: su-2.05b# amrecover -C colos AMRECOVER Version 2.5.0p2. Contacting server on ns1.pil.net ... amrecover: cannot connect to server.mydomain.net: Connection refused I then add the user root to ~amanda/.amandahosts, but it doesn't make a difference: (Partial) cat ~amanda/.amandahosts localhost.mydomain.net amanda server.mydomain.net amanda server.mydomain.net root localhost.mydomain.net root I also tried adding to this config's amanda.conf the following: amrecover_changer file:/path/to/tapedev And it didn't help. What am I missing? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: Amanda file driver questions
On Tue, 19 Dec 2006, Paul Bijnens wrote:
Also have a look at the updated version:
http://wiki.zmanda.com/index.php/File_driver
ok, thanks for that pointer
and was able to get the first backup, but I seem confused about how to do
a virtual tape rotation. I never used a changer before, so perhaps I
don't get the distinction between the slot number and the tape number. I
basically want to have a 4 week level 0 rotation, where after the 4th
week, the first week gets overwritten, etc, just like a tape would.
I created a directory on a usb drive like this:
/mnt/usb/dumps
I put this in my amanda.conf:
dumpcycle 4 weeks # the number of days in the normal dump cycle
tapecycle 4 tapes # the number of tapes in rotation
tapetype HARD-DISK # what kind of tape it is (see tapetypes
labelstr ^FULL[0-9][0-9]*$# label constraint regex: all tapes must
tpchanger chg-disk
changerfile /usr/local/etc/amanda/weekly/changer.conf
define tapetype HARD-DISK {
comment Hard disk backup storage instead of tape
length 30 mbytes
}
Then in my changer.conf, this:
For chg-disk, you don't need a changer.conf.
The number of tapes is taken from the dumpcycle paramater.
And the changerfile parameter is the prefix of a set of
files.
Sorry, I'm still confused about that changerfile...is it a file, or just a
text string to be used as the prefix for...what? Tape names? In the
wiki above, they show this example:
changerfile /home/amanda/test/chg-disk-status# status files prefix
But no example contents for that file.
Also, chg-disk needs a tapedev which points to the root
of a directory tree, containing slotN (N = 1... up-to-tapecycle)
subdirectories.
I used:
tapedev file:/mnt/usb/dumps
The example page for chg-disk uses:
tapedev file:/amandatapes/test/slots
I assume either should work fine, but still find the distinction between
the slot name and the (virtual) tape name a little confusing. Is there
any point in using:
labelstr ^FULL[0-9][0-9]*$
Like I did for real tapes, when amanda is going ahead and using slotN
for the names of each dmp directory anyway?
Alternatively, you can use chg-multi instead of chg-disk, and
have a detail changer.conf containing the layout of your
vtapes.
There is an example in the wiki.
According to that wiki, I would think chg-disk (simpler) would be better
for me)
multieject 0
gravity 0
needeject 0
ejectdelay 0
firstslot 1
lastslot 2
you probably mean lastslot 4
For chg-disk, this parameter is moot, since the file is, correct?
Thanks again, sorry for my density...
James Smallacombe PlantageNet, Inc. CEO and Janitor
[EMAIL PROTECTED]
http://3.am
=
Amanda file driver questions
I'm switching from a DLT backup system to a disk-based backup system with
occasional tapes for offsite backups. I followed the instructions at:
http://www.amanda.org/docs/howto-filedriver.html
and was able to get the first backup, but I seem confused about how to do
a virtual tape rotation. I never used a changer before, so perhaps I
don't get the distinction between the slot number and the tape number. I
basically want to have a 4 week level 0 rotation, where after the 4th
week, the first week gets overwritten, etc, just like a tape would.
I created a directory on a usb drive like this:
/mnt/usb/dumps
I put this in my amanda.conf:
dumpcycle 4 weeks # the number of days in the normal dump cycle
tapecycle 4 tapes # the number of tapes in rotation
tapetype HARD-DISK # what kind of tape it is (see tapetypes
labelstr ^FULL[0-9][0-9]*$# label constraint regex: all tapes must
tpchanger chg-disk
changerfile /usr/local/etc/amanda/weekly/changer.conf
define tapetype HARD-DISK {
comment Hard disk backup storage instead of tape
length 30 mbytes
}
Then in my changer.conf, this:
multieject 0
gravity 0
needeject 0
ejectdelay 0
firstslot 1
lastslot 2
slot 1 file:/mnt/usb/dumps/FULL0
slot 2 file:/mnt/usb/dumps/FULL1
slot 3 file:/mnt/usb/dumps/FULL2
slot 4 file:/mnt/usb/dumps/FULL3
I figured the slots would correspond to the tape names and create files or
directories named FULL0-3. It didn't
In the dumps directory, it just created:
lrwx-- 1 amanda wheel20 Dec 19 16:55 data -
/mnt/usb/dumps/slot3
-rw-r--r-- 1 amanda wheel11 Dec 19 16:55 info
drwxr-xr-x 2 amanda wheel 1024 Dec 16 13:14 slot1
With the slot1 directory containing the backups. The data symlink rotates
every time I run amcheck (slot1, slot2, etc), which completely confuses
me. Is this whole slot business neccessary? Can we just have amanda look
for the appropriate tape name (ie, FULL0) when that tape is required for
that week's dump?
TIA!
James Smallacombe PlantageNet, Inc. CEO and Janitor
[EMAIL PROTECTED]
http://3.am
=
Re: changes to amanda.conf for amanda 2.5.1?
On Thu, 14 Sep 2006, Frank Smith wrote:
Chan, Victor wrote:
To all,
I've changed up to Amanda 2.5.1. For some reason, these three
parameters that used to work in Amanda.conf didn't work anymore.
What version were you using?
diskdir var/tmp:
I don't see that in my 2.4.5 or my 2.5 configs. I vaguely recall that
was what the 'holdingdisk' parameter used to be called. Also, you're
missing the closing quote so the parser would choke anyway.
disksize 25000 MB
Same issue as above. You need something like:
holdingdisk name {
use 200 Gb
...
}
He can also have:
directory /var/tmp # where the holding disk is
But I've never seen diskdir and I've been running amanda for some 9
years...
James Smallacombe PlantageNet, Inc. CEO and Janitor
[EMAIL PROTECTED]
http://3.am
=
amflush NO FILE TO FLUSH
I make a special amanda config with a one tape tapelist to just dump this one large filesystem on a remote network that didn't make the last backup due to an interuption. After nearly 24 hours, it made it to the local holding disk on the server, but had a tape error trying to get it to tape. The DLT drive complained about needing to be cleaned, so I did that, amlabeled another tape (not a new one, but one that should be fine) and attempted to amflush thusly: su-2.05b$ amflush ns1 ns1_0 Scanning/home/amanda/dumps... 20060914210742: found Amanda directory. Today is: 20060915 Flushing dumps in 20060914210742 to tape drive /dev/nsa0. Expecting a new tape. (The last dumps were to tape ns1_0) Are you sure you want to do this [yN]? y Running in background, you can log off now. You'll get mail when amflush is finished. --- The tape drive starts to spin, but a few seconds later, I get the amanda report saying: NOTES: taper: tape ns1_0 kb 0 fm 0 [OK] ? DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s -- - host.name.net /dev/da0s1f NO FILE TO FLUSH --- (brought to you by Amanda version 2.4.5) With all the stats at zero. There are definitely several ~1GB files in the under ~amanda/dumps/20060914210742/ and it seemed to find the directory fine... Any ideas? James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: amflush NO FILE TO FLUSH
Responding to my own post...is it possible that this dump taking place over 2 different dates be an issue? Does it matter what date is in the tapelist when you flush it? If so, I could rename files or the folder... On Fri, 15 Sep 2006 [EMAIL PROTECTED] wrote: I make a special amanda config with a one tape tapelist to just dump this one large filesystem on a remote network that didn't make the last backup due to an interuption. After nearly 24 hours, it made it to the local holding disk on the server, but had a tape error trying to get it to tape. The DLT drive complained about needing to be cleaned, so I did that, amlabeled another tape (not a new one, but one that should be fine) and attempted to amflush thusly: su-2.05b$ amflush ns1 ns1_0 Scanning/home/amanda/dumps... 20060914210742: found Amanda directory. Today is: 20060915 Flushing dumps in 20060914210742 to tape drive /dev/nsa0. Expecting a new tape. (The last dumps were to tape ns1_0) Are you sure you want to do this [yN]? y Running in background, you can log off now. You'll get mail when amflush is finished. --- The tape drive starts to spin, but a few seconds later, I get the amanda report saying: NOTES: taper: tape ns1_0 kb 0 fm 0 [OK] ? DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s -- - host.name.net /dev/da0s1f NO FILE TO FLUSH --- (brought to you by Amanda version 2.4.5) With all the stats at zero. There are definitely several ~1GB files in the under ~amanda/dumps/20060914210742/ and it seemed to find the directory fine... Any ideas? James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Resuming interupted dumps
Is there a way to resume a level0 dump wheree it left off, rather than starting all over again, in the even of a client reboot during the dump? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: selfcheck request timed out WAS Re: Running amanda client only
Replying to my own post (sorry, but I'm getting desperate here), I took the advice of the FAQ-O-Matic and installed lsof and ran this command: su-2.05b# lsof -uamanda There was no output. Should there have been? Does this mean that amandad is not running? This is what I have in my /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad inetd.conf has beek killed and restarted, the client even rebooted...anything? On Wed, 13 Sep 2006 [EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Toomas Aas wrote: [EMAIL PROTECTED] wrote: The server is reporting that client down, so I checked and noticed that the FBSD port for the amanda-client did not install amindexd or amidxtaped, although it did install amandad. Are all 3 needed for a client? No, for client only amandad is needed. Then I cannot figure out why I'm getting selfcheck request timed out from that client. The path in inetd.conf is correct, as is the user (amanda) and /tmp/amanda is owned by amanda and has debug files there (just config info). .amandaclients has localhost.fqdn as well as hostname.fqdn. That client IS running alot of IP addresses on it, but I've done that before with no trouble. Here is amcheck -c output: su-2.05b$ amcheck -c weekly Amanda Backup Client Hosts Check ERROR: old.amanda.client: [host someIP.comcastbiz.net: hostname lookup failed] WARNING: new.amanda.client: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.153 seconds, 2 problems found I understand the first error from the old client...there is no forward DNS on that IP (BTW, is there a way around that? Just have it look at IP address?). I can't figure out the cause of the second one...I went through everything on the FAQ-O-Matic about it... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: selfcheck request timed out WAS Re: Running amanda client only
On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: Replying to my own post (sorry, but I'm getting desperate here), I took the advice of the FAQ-O-Matic and installed lsof and ran this command: su-2.05b# lsof -uamanda There was no output. Should there have been? Does this mean that amandad is not running? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. This is what I have in my /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad inetd.conf has beek killed and restarted, the client even rebooted...anything? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Thanks for your reply. I did run it from the command line and it eventually times out, although it does not exit immediately if I type something. debug files are created in /tmp/amanda, but not with any useful info...just how it was compiled. There is absolutely nothing in /var/log/messages about amanda(d). I thought ldconfig was run upon boot...in any case, if I'm missing some kind of lib, wouldn't amanda complain about it when trying to build it? Thanks again for any help... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: selfcheck request timed out WAS Re: Running amanda client only
On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: Replying to my own post (sorry, but I'm getting desperate here), I took the advice of the FAQ-O-Matic and installed lsof and ran this command: su-2.05b# lsof -uamanda There was no output. Should there have been? Does this mean that amandad is not running? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. This is what I have in my /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad inetd.conf has beek killed and restarted, the client even rebooted...anything? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Thanks for your reply. I did run it from the command line and it eventually times out, although it does not exit immediately if I type something. 2.4.5 will exit if you hit enter, 2.5 doesn't. The client is 2.5.0p2, the server is 2.4.5. Could that be an issue? If so, which one do you recommend? debug files are created in /tmp/amanda, but not with any useful info...just how it was compiled. There is absolutely nothing in /var/log/messages about amanda(d). Inetd doesn't normally log unless you start it with a debug option. In your case, since a debug file is created then inetd is working so you may not need to check further on that. Post the debug file on the client and maybe we can see at what stage of the connection it stops. Are you running a firewall on or between the client? No firewall that I've configured...I did just hook up via comcast business though...nmap from the client back to the server looks ok...I can ssh back, as well. the debug files had what looked like nothing but a config.log, until I just looked now and noticed this huge (48MB) debug file with 670 thousand lines of this: amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Fixed amcheck, one more question (or two)
Sorry for all the whining...it turned out the host down was the same reverse DNS problem that the other amanda client was returning, but since the error message was totally different, it baffled. I hooked the server back up to the old network and it worked fine. 2 more minor issues: I'm getting this: ERROR: label FULL0 match labelstr but it not listed in the tapelist file. (expecting a new tape) I thought that amanda would simply create a new tapelist...I deleted the old one because it was years old. Do I need to manually create a new one? If so, which dates do I use...I simply created an empty file figuring amanda would take care of the rest. Lastly (I hope), is there a way to get amanda to not do host lookups and simply use IP addresses in .amandahosts? For security, I think IP addresses would be better. Thanks again! James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Running amanda client only
Hi: I've been using amanda for years, but I just reconfigured and updated some servers using the latest everything and updated the disklists for the newer format (integer/spindle). From FreeBSD ports, I just installed amanda-2.4.5 on the amanda server and amanda-2.5.0p2 on the client (the ports defaulted to those). The server is reporting that client down, so I checked and noticed that the FBSD port for the amanda-client did not install amindexd or amidxtaped, although it did install amandad. Are all 3 needed for a client? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: Failed dumps with new amanda client
On Wed, 21 Jun 2006, Jon LaBadie wrote:
On Wed, Jun 21, 2006 at 08:23:57AM -0400, Joshua Baker-LePain wrote:
On Tue, 20 Jun 2006 at 10:59pm, [EMAIL PROTECTED] wrote
Here's the complete report, now that it finally finished:
su-2.05a$ amtapetype -f /dev/nrsa0
Writing 256 Mbyte compresseable data: 92 sec
Writing 256 Mbyte uncompresseable data: 90 sec
Estimated time to write 2 * 1024 Mbyte: 720 sec = 0 h 12 min
wrote 763218 32Kb blocks in 2334 files in 13153 seconds (short write)
wrote 757298 32Kb blocks in 4646 files in 20125 seconds (short write)
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 24034 mbytes
filemark 81 kbytes
speed 1530 kps
}
Does this mean that this 35GB uncompressed tape is only yeilding 24GB?
Yep, which means it's not an amanda issue. And I have no idea why it's
doing that. Good luck with it. ;)
24GB, that is just about where it ran out during amdump too.
I've no idea either; just a possible coincidence.
In my tapechart DLT IV tape is shown as 1800 inches long
while DLT III tape is 1200 inches long.
That ratio , 1200/1800 is pretty close to the
24GB (observed)/35GB (expected) ratio.
Any chance these are just short tapes?
If so, I've been defrauded...they are clearly stamped FujiFilm DLT IV
For all I know about DLT, the physical cartridge may have
changed between DLT III and DLT IV so my question is silly.
I note your speed is pretty low compared to my chart listing,
1.5 vs 5.0 MB/sec. Is DLT capacity affected by slow feed?
Not sure...I noticed the speed as well. I had raised the conf parameter:
From: netusage 1600 Kbps
To:netusage 7200 Kbps
I can't recall if that's bits or bytes (small b should be bits, right?).
But I'll try raising it alot more, since all dumps are over 100mbit
ethernet.
James Smallacombe PlantageNet, Inc. CEO and Janitor
[EMAIL PROTECTED]
http://3.am
=
Re: Failed dumps with new amanda client
On Tue, 20 Jun 2006, Joshua Baker-LePain wrote: On Tue, 20 Jun 2006 at 10:35am, [EMAIL PROTECTED] wrote On Mon, 19 Jun 2006, Joshua Baker-LePain wrote: I'd be awfully suspicious that you're running with hardware compression enabled (quite possibly unbeknownest to you). That doesn't really make sense to me...if that were the case, wouldn't it affect all of the clients? In any case, I manually turn off the hardware compression before every backup. One thing that has me curious is this: Yes, it would affect all the clients. All the (already) compressed data going to tape would be hardware compressed by the drive, making it expand and take up more tape space. Therefore, even though amanda only saw ~25GB go to tape, on tape it took up the whole 35GB. The error you got (short write) typically means you hit EOT. That happened on one particular client, and so that particular client failed. I don't have any experience with DLT, but I've heard tell that with some drives turning off hardware compression isn't always easy. Avg Dump Rate (k/s) 1491.9 1491.9-- Tape Time (hrs:min)4:00 4:00 0:00 That speed looks a bit slow for a DLT7000...closer to what you'd expect from a DLT4000. Is there some kind of timeout at 4 hours? Not that I'm aware of, and you didn't hit any timeout anyway -- you got a short write. Regarding the speed, since you're not running with a holding disk, there are all sorts of things that can affect the dump/tape rate -- speed from the client disks, network congestion, etc. I'd start by using amtapetype to test your new drive, both for hardware compression and native speed. I'd also look at adding a holding disk to your config, if at all possible. Thanks for the response. Here's what I get with amtapetype: su-2.05a$ amtapetype -f /dev/nrsa0 Writing 256 Mbyte compresseable data: 92 sec Writing 256 Mbyte uncompresseable data: 90 sec Estimated time to write 2 * 1024 Mbyte: 720 sec = 0 h 12 min wrote 763218 32Kb blocks in 2334 files in 13153 seconds (short write) It's going through another write at the moment, but I assume short write means it isn't getting full capacity from the tape? Not sure what those compression stats mean, either... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: Failed dumps with new amanda client
On Tue, 20 Jun 2006, Joshua Baker-LePain wrote:
On Tue, 20 Jun 2006 at 4:27pm, [EMAIL PROTECTED] wrote
On Tue, 20 Jun 2006, Joshua Baker-LePain wrote:
I'd start by using amtapetype to test your new drive, both for hardware
compression and native speed. I'd also look at adding a holding disk to
your config, if at all possible.
Thanks for the response. Here's what I get with amtapetype:
su-2.05a$ amtapetype -f /dev/nrsa0
amtapetype runs better when given an estimate of the tapelength.
Writing 256 Mbyte compresseable data: 92 sec
Writing 256 Mbyte uncompresseable data: 90 sec
That's a check to see if hardware compression is enabled -- it isn't.
That's good.
Estimated time to write 2 * 1024 Mbyte: 720 sec = 0 h 12 min
wrote 763218 32Kb blocks in 2334 files in 13153 seconds (short write)
763218*32KiB = 23.3GiB, /13153s = 1857 KiB/s. Those are pretty similar to
what your network dumps were getting. So it's your tape drive and/or
tapes that are the issue. Again, I have no experience with DLT, but check
your tapes to make sure they're really 35GB capacity. Any problems with
the SCSI chain? Does the drive simply need to be cleaned?
It's going through another write at the moment, but I assume short write
means it isn't getting full capacity from the tape? Not sure what those
short write simply means that it tried to write another 32KB block, and
there wasn't room on the tape for it. That's what happens when you hit
EOT.
Here's the complete report, now that it finally finished:
su-2.05a$ amtapetype -f /dev/nrsa0
Writing 256 Mbyte compresseable data: 92 sec
Writing 256 Mbyte uncompresseable data: 90 sec
Estimated time to write 2 * 1024 Mbyte: 720 sec = 0 h 12 min
wrote 763218 32Kb blocks in 2334 files in 13153 seconds (short write)
wrote 757298 32Kb blocks in 4646 files in 20125 seconds (short write)
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 24034 mbytes
filemark 81 kbytes
speed 1530 kps
}
Does this mean that this 35GB uncompressed tape is only yeilding 24GB?
The mt program recognises it as a 35GB tape:
su-2.05a$ mt status
Mode Density Blocksize bpi Compression
Current: 0x1b:DLTapeIV(35GB)variable 85937IDRC
-available modes-
0:0x1b:DLTapeIV(35GB)variable 85937IDRC
1:0x1b:DLTapeIV(35GB)variable 85937IDRC
2:0x1b:DLTapeIV(35GB)variable 85937IDRC
3:0x1b:DLTapeIV(35GB)variable 85937IDRC
-
Current Driver State: at rest.
-
File Number: 0 Record Number: 0Residual Count 0
BTW, with DLT, the 2000, 4000 and 7000 all use the same actual media, DLT
IV.
James Smallacombe PlantageNet, Inc. CEO and Janitor
[EMAIL PROTECTED]
http://3.am
=
Failed dumps with new amanda client
Hi:
It's been many years since I needed help with Amanda, but I'm stuck on
this one. I've had a client+server and a client only box set up for
years, backing up no problem (running amanda-2.4.4). I switched from a
DLT4000 to a DLT7000 several months ago, as the former was wearing out and
I needed more space.
A colo customer requested that I backup his FreeBSD box, which was built
with only on file system, which is using around 8GB of space. I built and
installed amanda-2.4.5 without a hitch and amchecks look fine. However,
I've attempted full dumps 3 times using two different tapes (the last
time, I reconfigured and reinstalled amanda duplicating my other client's
config) and all have failed exactly like this:
These dumps were to tape FULL0.
*** A TAPE ERROR OCCURRED: [[writing file: short write]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: FULL1.
FAILURE AND STRANGE DUMP SUMMARY:
main.heart /dev/da0s1a lev 0 FAILED [data write: Broken pipe]
main.heart /dev/da0s1a lev 0 FAILED [dump to tape failed]
main.heart /dev/da0s1a lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:09
Run Time (hrs:min) 4:34
Dump Time (hrs:min)4:00 4:00 0:00
Output Size (meg) 20978.420978.40.0
Original Size (meg) 38216.538216.50.0
Avg Compressed Size (%)54.9 54.9--
Filesystems Dumped8 8 0
Avg Dump Rate (k/s) 1491.9 1491.9--
Dump Time (hrs:min)4:00 4:00 0:00
Output Size (meg) 20978.420978.40.0
Original Size (meg) 38216.538216.50.0
Avg Compressed Size (%)54.9 54.9--
Filesystems Dumped8 8 0
Avg Dump Rate (k/s) 1491.9 1491.9--
Tape Time (hrs:min)4:00 4:00 0:00
Tape Size (meg) 20978.520978.50.0
Tape Used (%) 59.9 59.90.0
Filesystems Taped 8 8 0
Avg Tp Write Rate (k/s) 1491.8 1491.8--
USAGE BY TAPE:
Label Time Size %Nb
FULL0 4:00 20978.5 59.9 8
?
FAILED AND STRANGE DUMP DETAILS:
/-- main.heart /dev/da0s1a lev 0 FAILED [data write: Broken pipe]
sendbackup: start [main.hearth.com:/dev/da0s1a level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/sbin/restore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Date of this level 0 dump: Mon Jun 19 15:33:29 2006
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/da0s1a (/) to standard output
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 8092024 tape blocks.
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 12.34% done, finished in 0:35
| DUMP: 30.07% done, finished in 0:23
| DUMP: 45.62% done, finished in 0:17
| DUMP: 62.13% done, finished in 0:12
\
?
NOTES:
planner: Last full dump of ns1.pil.net:/dev/da0s1a on tape FULL0
overwritten on this run.
planner: Last full dump of ns1.pil.net:/dev/da0s1g on tape FULL0
overwritten on this run.
planner: Last full dump of ns1.pil.net:/dev/da0s1e on tape FULL0
overwritten on this run.
planner: Last full dump of ns1.pil.net:/dev/da0s1f on tape FULL0
overwritten on this run.
planner: Last full dump of mail.pil.net:/dev/aacd0s1a on tape FULL0
overwritten on this
run.
planner: Last full dump of mail.pil.net:/dev/aacd0s1g on tape FULL0
overwritten on this
run.
planner: Last full dump of mail.pil.net:/dev/aacd0s1e on tape FULL0
overwritten on this
run.
planner: Last full dump of mail.pil.net:/dev/aacd0s1f on tape FULL0
overwritten on this
run.
planner: Last full dump of main.hearth.com:/dev/da0s1a on tape
overwritten in 1 run.
taper: tape FULL0 kb 24499968 fm 9 writing file: short write
?
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
mail.pil.net -v/aacd0s1a 0 117614 42944 36.5 0:361184.0 0:361183.7
mail.pil.net -v/aacd0s1e 0 2494624 865536 34.7 10:301373.8 10:301373.7
mail.pil.net -v/aacd0s1f 0 1808993 407328 22.5 6:421012.6 6:421012.5
mail.pil.net -v/aacd0s1g 0 160671519237184 57.5 95:261613.2 95:261613.2
main.hearth. /dev/da0s1a 0 FAILED ---
ns1.pil.net /dev/da0s1a 0 127749 74624 58.4 0:471579.3 0:471577.8
ns1.pil.net /dev/da0s1e 0 2505458 770528 30.8 18:29 694.7 18:29 694.7
ns1.pil.net /dev/da0s1f 0 700444 126752 18.1 3:11 663.6 3:11 663.6
ns1.pil.net /dev/da0s1g 0
