Re: amanda + debian woody problem
Make sure that amanda is enable in /etc/inet.d/amanda
--->snip<---
# default: off
# description: The client for the Amanda backup system.\
# This must be on for systems being backed up\
# by Amanda.
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
server = /usr/lib/amanda/amandad
disable = no
}
--->snip<---
Do the same for amandaidx and amandatape. Mine was by default disabled.
Remember to restart the inetd service.
Marcus Schopen wrote:
> Hi,
>
> running amcheck on my woody as user backup says:
>
> WARNING: localhost: selfcheck request timed out. Host down?
> Client check: 1 host checked in 29.997 seconds, 1 problem found
>
--
|-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-|
Bartho Saaiman
Cellphone * Work +27 72 341 8626 * +27 21 808 2497 ext 204
Stellenbosch Automotive Engineering http://www.cae.co.za
|-=-=-=-=-=-=-=< registered linux user 236001 >-=-=-=-=-=-=-=-=-|
amanda + debian woody problem
Hi, running amcheck on my woody as user backup says: WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 29.997 seconds, 1 problem found /tmp/amanda/amcheck.20020531031831.debug says: amcheck: debug 1 pid 668 ruid 34 euid 0 start time Fri May 31 03:18:31 2002 amcheck: dgram_bind: socket bound to 0.0.0.0.515 amcheck: pid 668 finish time Fri May 31 03:19:01 2002 iptraf says: ICMP dest unrch from 127.0.0.1 to 127.0.0.1 on lo while running amcheck lsof says this: # lsof | grep amanda inetd 209root 10u IPv4397 TCP *:amandaidx (LISTEN) amcheck 695root memREG 114,5 82852 354909 /usr/lib/libamanda-2.4.2p2.so amcheck 695root4u REG 114,8 030670 /tmp/amanda/amcheck.temp.695 amcheck 695root 10w REG 114,8 12530669 /tmp/amanda/amcheck.20020531032117.debug amcheck 697root cwdDIR 114,8409630657 /tmp/amanda amcheck 697root memREG 114,5 82852 354909 /usr/lib/libamanda-2.4.2p2.so amcheck 697root1u REG 114,8 030670 /tmp/amanda/amcheck.temp.695 amcheck 697root2u REG 114,8 030670 /tmp/amanda/amcheck.temp.695 amcheck 697root4u REG 114,8 030670 /tmp/amanda/amcheck.temp.695 amcheck 697root 10w REG 114,8 12530669 /tmp/amanda/amcheck.20020531032117.debug /etc/inetd.conf (debian package put it in there): amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped last thing: I'm wondering that I can't find a amandad in /usr/lib/amanda/ Any ideas would be more than great! Thanks Marcus -- Petition for a Software Patent Free Europe http://petition.eurolinux.org
RE: amrecover: No index records for disk for specified date
Toomas Aas wrote: > Actually, I meant the logfiles in the directory that is specified > as 'logdir' in amanda.conf. In my case it's /var/log/amanda/MyConfig/ in my case they are specified in amanda.conf as /var/log/amanda, and yes, they are indeed there and given permissions 700. Is there a way of putting amrecover into debug mode? > These files, in addition to index files, are also necessary for > amrecover. > An unrelated note, if I may. Top-posting and sending out entire > paragraphs as single long lines makes replying to your messages > somewhat cumbersome. Sorry. cheers, john.
unsubscribe
unsubscribe
unsubscribe
> unsubscribe >
MacOS X ??
Anyone attempt to compile this beast on MacOS X yet? ( client only ) - Michael Hogsett Sr. System Administrator SRI International Computer Science & System Design Laboratories
unsubscribe
unsubscribe
RE: amrecover: No index records for disk for specified date
Hi! > the log files in /tmp/amanda/amindexd-[date,etc.] do not really > say anything other than exhibit the following behavior: Actually, I meant the logfiles in the directory that is specified as 'logdir' in amanda.conf. In my case it's /var/log/amanda/MyConfig/ These files, in addition to index files, are also necessary for amrecover. An unrelated note, if I may. Top-posting and sending out entire paragraphs as single long lines makes replying to your messages somewhat cumbersome. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * How can i miss you if you won't go away?
RE: amrecover: No index records for disk for specified date
yes. the log files in /tmp/amanda/amindexd-[date,etc.] do not really say anything other than exhibit the following behavior: when using amrecover, i cd to the appropriate directory (meaning the directory which was backed up last night and which i want to test a restore on). the log file then says that the directory i tried to cd to was an invalid directory. Further info: if i look in the index directory for that host, i find the file which includes the directory in question. if i look in /tmp/amanda/amtrmidx, i see the host and the directory listed (although i don't know what this program does). thanks in advance for your help! cheers, john. Toomas Aas wrote: > Hi! > > > i am having the exact same problem. > > (the problem being that amrecover says "index records not present") > > > I have checked the following: > > > > 1. Version of tar is upgraded > > 2. The backups themselves are successfull > > 3. The index files are indeed present where they should be > > 4. the correct index directory is specified in amanda.conf > > 5. the amanidx/tcp service is specified in /etc/services on the client machine eg. >: > > 6. Are the log files present in Amanda's log directory? > > -- > Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ > * Mcmxlogist: An expert translator of Roman numerals.
Re: Zero Level Backups
or in your dumptype definition include "strategy noinc"
eg. In our "weekly" backup sets the global dumptype is defined as:
define dumptype global {
comment "Global definitions"
# This is quite useful for setting global parameters, so you don't have
# to type them everywhere. All dumptype definitions in this sample file
# do include these definitions, either directly or indirectly.
# There's nothing special about the name `global'; if you create any
# dumptype that does not contain the word `global' or the name of any
# other dumptype that contains it, these definitions won't apply.
# Note that these definitions may be overridden in other
# dumptypes, if the redefinitions appear *after* the `global'
# dumptype name.
# You may want to use this for globally enabling or disabling
# indexing, recording, etc. Some examples:
# index yes
# record no
index yes
record no
holdingdisk yes
strategy noinc
}
according to the amanda.conf file comments:
# strategy- set the dump strategy. Valid strategies are currently:
# "standard" - the standard one.
# "nofull" - do level 1 dumps every time. This can be used,
# for example, for small root filesystems that
# only change slightly relative to a site-wide
# prototype. Amanda then backs up just the
# changes.
# "noinc"- do level 0 dumps every time.
# "skip" - skip all dumps. Useful for sharing a single
# disklist in several configurations.
# Default: [strategy standard]
Wayne Richards
>
> In message <[EMAIL PROTECTED]>, Brook Hurd writes
> :
> > How do you force Amanda to do all Zero Level Backups?
>
> man amadmin
>
> amadmin configname force hostname [ disks ]
> Force the disks on hostname to do a full (level 0) backup during
> the next Amanda run.
>
>
>
RE: amrecover: No index records for disk for specified date
Hi! > i am having the exact same problem. (the problem being that amrecover says "index records not present") > I have checked the following: > > 1. Version of tar is upgraded > 2. The backups themselves are successfull > 3. The index files are indeed present where they should be > 4. the correct index directory is specified in amanda.conf > 5. the amanidx/tcp service is specified in /etc/services on the client machine eg. : 6. Are the log files present in Amanda's log directory? -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * Mcmxlogist: An expert translator of Roman numerals.
Re: Zero Level Backups
In message <[EMAIL PROTECTED]>, Brook Hurd writes : > How do you force Amanda to do all Zero Level Backups? man amadmin amadmin configname force hostname [ disks ] Force the disks on hostname to do a full (level 0) backup during the next Amanda run.
unsubscribe
unsubscribe
Re: AMANDATES file
--On Wednesday, May 29, 2002 12:18:42 -0400 Brook Hurd <[EMAIL PROTECTED]> wrote: > I have been trying to do some research regarding the AMANDATES file, but I was >unable to find any documentation on the purpose of this document. I would appreciate >peoples insights on this file. > > Thanks, > > Brook Its used as the functional equivalent to dump's /etc/dumpdates so that Amanda can keep track of what levels were done when on which filesystems. The file contains lines like these: / 0 1022467489 / 1 1022639983 / 2 1018233593 /mnt/srv/backups 0 1022467139 /mnt/srv/backups 1 1022639924 /mnt/srv/home/app 0 1022381269 /mnt/srv/home/app 1 1022639885 /mnt/srv/home/app 2 1018233460 Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
ME TOO RE: amrecover: No index records for disk for specified date: ME TOO
i'm getting the same problem too. Makes it impossible to use amrecover to
restore data
Michael Martinez
System Administrator (Contractor)
Information Systems and Technology Management
CSREES - United States Department of Agriculture
(202) 720-6223
-Original Message-
From: John D. Bickle [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 12:06 PM
To: Simas Cepaitis
Cc: 'Jon LaBadie'; '[EMAIL PROTECTED]'
Subject: RE: amrecover: No index records for disk for specified date
Hi folks.
i am having the exact same problem.
I have checked the following:
1. Version of tar is upgraded
2. The backups themselves are successfull
3. The index files are indeed present where they should be
4. the correct index directory is specified in amanda.conf
5. the amanidx/tcp service is specified in /etc/services on the client
machine eg. :
amanda 10080/udp # amanda added by jdb 2002-05-15
amandaidx 10082/tcp # amanda added by jdb 2002-05-15
amidxtape 10083/tcp # amanda added by jdb 2002-05-15
6. these services are available on the server machine (redhat 7.2) and in
addition being in /etc/services, are also correctly present in xinetd.
7. If it type the history command, the backup for that particular host is
listed correctly.
Can someone please point me in the right direction?
thanks,
john.
Here is the output from amrecover (domain names removed to protect the
innocent).
bash-2.05# amrecover -s serverhost..net
AMRECOVER Version 2.4.2p2. Contacting server on monitor.rvbs.net ...
220 monitor AMANDA index server (2.4.3b3) ready.
200 Access OK
Setting restore date to today (2002-05-29)
200 Working date set to 2002-05-29.
200 Config set to DailySet1.
501 No index records for host: www. Invalid?
Trying www.(client domain).com ...
200 Dump host set to www.(client domain).com.
$CWD '/usr/local/src' is on disk '/' mounted at '/'.
200 Disk set to /.
No index records for disk for specified date
If date correct, notify system administrator
Invalid directory - /usr/local/src
amrecover> quit
200 Good bye.
Simas Cepaitis wrote:
> Hello,
>
> > -Original Message-
> > From: Jon LaBadie [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, May 27, 2002 8:35 PM
> > To: Simas Cepaitis
> > Subject: Re: amrecover: No index records for disk for specified date
> >
> >
> >
> > Any chance your disklist uses localhost rather than a hostname?
>
> No, I use full hostname. For example,
>
> sunny.5ci.lt /usr {
>always-full
>exclude list "/usr/local/etc/amanda/test/.exclude"
>compress server fast
> } -1 local
>
> > If using tar, maybe a bad release of tar. gunzip one of the
> > indexs. See if each line begins with a long number. That is
> > one sign of a bad tar.
>
> I tried using both gnutar (version 1.13.25) and native FreeBSD tar.
>
> # pwd
> /usr/local/etc/amanda/test/index/sunny.5ci.lt/_usr
> #zmore 20020527_0.gz
> /
> /bin/
> /bin/cu
> /bin/uucp
> /bin/uulog
> /bin/uuname
> /bin/uupick
> /bin/uusched
> ...
> ...
>
> I don't think that is a tar problem. Somehow I believe that rather
> directory with indexes is not found. Is there any option to enable
> debug mode or something to see more in logs? Because now
> they aren't providing much use (amrecover for example)... :(
>
>
> Simas Cepaitis
> [EMAIL PROTECTED]
Re: Zero Level Backups
read the man page for amadmin amadmin force > How do you force Amanda to do all Zero Level Backups? > > Thanks, > > Brook
Re: changer script that works with mtx version 1.2.13
I am using mtx-changer from the 1.2.16 distro. Works great with solaris 8/DLT 7000/a2.4.2--once I had the scsi cables properly terminated! > Does anybody have a changer script that works with mtx version 1.2.13 . > I am now getting the error message: > /usr/local/libexec/chg-mtx: [: : integer expression expected > /usr/local/libexec/chg-mtx: [: -lt: unary operator expected > > It just suddenly happened. Just when I thought I had amanda working. > UGH! > > Thanks > > Andre >
RE: AMANDATES file
amandates serves the same function as /etc/dumpdates: to show when the system backups are being done Michael Martinez System Administrator (Contractor) Information Systems and Technology Management CSREES - United States Department of Agriculture (202) 720-6223 -Original Message- From: Brook Hurd [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 12:19 PM To: [EMAIL PROTECTED] Subject: AMANDATES file I have been trying to do some research regarding the AMANDATES file, but I was unable to find any documentation on the purpose of this document. I would appreciate peoples insights on this file. Thanks, Brook
Re: AMANDATES file
On Wed, 29 May 2002 at 12:18pm, Brook Hurd wrote > I have been trying to do some research regarding the AMANDATES file, but > I was unable to find any documentation on the purpose of this document. > I would appreciate peoples insights on this file. It's used by amanda to record dates and levels of backups using tar. The dump analog is /etc/dumpdates. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Zero Level Backups
On Wed, 29 May 2002 at 12:19pm, Brook Hurd wrote > How do you force Amanda to do all Zero Level Backups? All the time, or just that night? If you want to force a specific host for that night, you can do 'amadmin Config force host' -- look at the amadmin man page for all the details. If all you want is level 0s all the time, set dumpcycle to 0. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: changer script that works with mtx version 1.2.13
Andre Gauthier wrote: > Does anybody have a changer script that works with mtx version 1.2.13 . > I am now getting the error message: > /usr/local/libexec/chg-mtx: [: : integer expression expected > /usr/local/libexec/chg-mtx: [: -lt: unary operator expected I have had more luck with the chg-zd-mtx changer script. I believe it is in the libexec directory. -- Eric
RE: amrecover: No index records for disk for specified date
Hi folks.
i am having the exact same problem.
I have checked the following:
1. Version of tar is upgraded
2. The backups themselves are successfull
3. The index files are indeed present where they should be
4. the correct index directory is specified in amanda.conf
5. the amanidx/tcp service is specified in /etc/services on the client machine eg. :
amanda 10080/udp # amanda added by jdb 2002-05-15
amandaidx 10082/tcp # amanda added by jdb 2002-05-15
amidxtape 10083/tcp # amanda added by jdb 2002-05-15
6. these services are available on the server machine (redhat 7.2) and in addition
being in /etc/services, are also correctly present in xinetd.
7. If it type the history command, the backup for that particular host is listed
correctly.
Can someone please point me in the right direction?
thanks,
john.
Here is the output from amrecover (domain names removed to protect the innocent).
bash-2.05# amrecover -s serverhost..net
AMRECOVER Version 2.4.2p2. Contacting server on monitor.rvbs.net ...
220 monitor AMANDA index server (2.4.3b3) ready.
200 Access OK
Setting restore date to today (2002-05-29)
200 Working date set to 2002-05-29.
200 Config set to DailySet1.
501 No index records for host: www. Invalid?
Trying www.(client domain).com ...
200 Dump host set to www.(client domain).com.
$CWD '/usr/local/src' is on disk '/' mounted at '/'.
200 Disk set to /.
No index records for disk for specified date
If date correct, notify system administrator
Invalid directory - /usr/local/src
amrecover> quit
200 Good bye.
Simas Cepaitis wrote:
> Hello,
>
> > -Original Message-
> > From: Jon LaBadie [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, May 27, 2002 8:35 PM
> > To: Simas Cepaitis
> > Subject: Re: amrecover: No index records for disk for specified date
> >
> >
> >
> > Any chance your disklist uses localhost rather than a hostname?
>
> No, I use full hostname. For example,
>
> sunny.5ci.lt /usr {
>always-full
>exclude list "/usr/local/etc/amanda/test/.exclude"
>compress server fast
> } -1 local
>
> > If using tar, maybe a bad release of tar. gunzip one of the
> > indexs. See if each line begins with a long number. That is
> > one sign of a bad tar.
>
> I tried using both gnutar (version 1.13.25) and native FreeBSD tar.
>
> # pwd
> /usr/local/etc/amanda/test/index/sunny.5ci.lt/_usr
> #zmore 20020527_0.gz
> /
> /bin/
> /bin/cu
> /bin/uucp
> /bin/uulog
> /bin/uuname
> /bin/uupick
> /bin/uusched
> ...
> ...
>
> I don't think that is a tar problem. Somehow I believe that rather
> directory with indexes is not found. Is there any option to enable
> debug mode or something to see more in logs? Because now
> they aren't providing much use (amrecover for example)... :(
>
>
> Simas Cepaitis
> [EMAIL PROTECTED]
Zero Level Backups
How do you force Amanda to do all Zero Level Backups? Thanks, Brook
AMANDATES file
I have been trying to do some research regarding the AMANDATES file, but I was unable to find any documentation on the purpose of this document. I would appreciate peoples insights on this file. Thanks, Brook
changer script that works with mtx version 1.2.13
Does anybody have a changer script that works with mtx version 1.2.13 . I am now getting the error message: /usr/local/libexec/chg-mtx: [: : integer expression expected /usr/local/libexec/chg-mtx: [: -lt: unary operator expected It just suddenly happened. Just when I thought I had amanda working. UGH! Thanks Andre
unsubscribe
unsubscribe
Re: Getting My Data Back Off The Tape
On Wed, 29 May 2002, GIC MLs wrote: > I followed your advice and ran the command with the -tvf - flags, which > seemed to only give me a listing of directories.: Tar stores all the directories first, so if you are impatient, you might not wait around until the files start showing up :) Nick
Re: retain dump files on holding disk
On Wed, 29 May 2002, Jon LaBadie wrote:
> Skyblue thinking. Wouldn't this be just the level 0's you'd want retained?
> At least that is my antiquated impression of off-site archiving.
A level 0 from three days ago won't have a file I created two days
ago. A level 1 from one day ago will. So although level 0's are
necessary for restoring an entire directory, without the level n's,
you essentially have infrequent full backups. Therefore, I don't
see any reason to only store or retain level 0's.
By the way, since no one has piped up with an easy solution to
retaining dump images, here's my horrible hack, which has been
working very well for a week now. I call it from cron about an
hour after I start amdump.
#!/bin/sh
# I'd like to hold on to the dumped files, so that restores from the
# last 24 hours become very quick. I'll make hardlinks to the files
# in /packages/amanda/spool/*/*/ and I'll remove them before the next
# dump. (Maybe I can keep two days around, since I've got 80GB now.)
die() {
echo "$1"
exit $2
}
config=$1 # weekly or daily
config_dir=/packages/amanda/spool/$config
current=`ls -t $config_dir|egrep -v recent|head -1`
test -n "$current" || die "no current directory in $config_dir" 5
test -d $config_dir/recent || mkdir $config_dir/recent || die "couldn't
make $config_dir/recent" 6
test -d $config_dir/less_recent || mkdir $config_dir/less_recent || die
"couldn't make $config_dir/less_recent" 6
# poor-mans rotation:
rm -rf $config_dir/less_recent/*
mv $config_dir/recent/* $config_dir/less_recent/
while test -d $config_dir/$current
do
(cd $config_dir/$current && \
find . -type f \! -name '*.tmp' -exec ln {} $config_dir/recent/{} \;
2>/dev/null
)
sleep 1
done
echo "done capturing files from $config_dir/$current"
Re: Running out of tape due to full dumps
At 2002-05-29T00:27:52Z, Bradley Marshall <[EMAIL PROTECTED]> writes: > Its a DDS3 tape, and runs out when it tries to flush about 16G (30G > uncompressed). No offense, but how much data did you /want/ to fit on a 12G tape? -- Kirk Strauser The Strauser Group - http://www.strausergroup.com/
Re: retain dump files on holding disk
On Tue, May 28, 2002 at 11:11:11PM -0700, Don Wolski wrote: > At 11:58 AM 5/28/02 -0500, Nick Russo wrote: > >I'd like to keep all the dump images on disk even after they > >get written to tape. My reasoning is that a large percentage > >of the restore requests I get from my users could be satisfied > >by files from the last day or two. > > Another reason for retaining dump images would be to make a second backup > tape in case writing one of the tapes is to be it's last use before errors > occur, and so that one copy could be kept off-site (in case the disaster > that destroys your disks also destroys your tape copies kept on-site). Skyblue thinking. Wouldn't this be just the level 0's you'd want retained? At least that is my antiquated impression of off-site archiving. > So I would add to Nick's question, can the retained dump images be taped a > second time, hopefully in a way that allows amanda to record the fact that > the images exists on two different tapes. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: backup over the network
Also, as a note, I found that I would get "amanda timed out" errors until I chmod'ed .amandahosts to 400. So if you can't get it to work, and you think you've done it all right, make sure your .amandahosts is 400 -Michael -Original Message- From: Kevin Hancock [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 29, 2002 9:16 AM To: jean Cc: [EMAIL PROTECTED] Subject: Re: backup over the network > > I hope I don't have to re-install the program again. Thanx in advance. > > You'll need to compile, install, and configure amanda on the new machine You really only need to install amanda client you do not need the server. You are using Linux, if it is a RPM system just install amanda-common and amanda-client packages. Restart (x)inetd, add the amanda server to .amandahosts and the client is done. You may have to edit hosts.allow and any firewall scripts, depends how you do your security. Edit disklist on server and run amcheck I was amazed at how easy it is to add clients. Kevin
ERROR: escudo.nhh.no: [could not access da5c (da5c): No such file or directory] after upgrading from 2.4.1p1 go 2.4.2p2
I have just upgraded Amanda from 2.4.1p1 go 2.4.2p2, and now Amanda has started complaining about "could not access [...]" for two partitions on the Amanda-server. I have tried to add the advfs patch (ref. http://www.mail-archive.com/amanda-users@amanda.org/msg11876.html>), but that did not help. The system is running FreeBSD 4.5-RELEASE-p4. Here are more details: amanda@escudo:~$ amcheck nhh Amanda Tape Server Host Check - Holding disk /var/amanda/spool: 15616486 KB disk space available, using 15514086 KB NOTE: skipping tape-writable test Tape NHH220 label ok Server check took 5.505 seconds Amanda Backup Client Hosts Check ERROR: escudo.nhh.no: [could not access da5c (da5c): No such file or directory] ERROR: escudo.nhh.no: [could not access da4s1e (da4s1e): No such file or directory] Client check: 12 hosts checked in 0.446 seconds, 2 problems found (brought to you by Amanda 2.4.2p2) amanda@escudo:~$ mount /dev/da0s1a on / (ufs, local) /dev/da1s1e on /var (ufs, local) /dev/da1s1f on /var/log (ufs, local) /dev/da1s1g on /var/spool/mqueue (ufs, local) /dev/da0s1e on /usr (ufs, local) /dev/da5c on /usr/cyrus/spool/stab (ufs, local) /dev/da4s1e on /usr/cyrus/spool/stud (ufs, local) /dev/da1s1h on /home (ufs, local) /dev/da3s1e on /var/amanda/spool (ufs, local) /dev/da1s1a on /mnt/da1s1a (ufs, local) mfs:34 on /tmp (mfs, asynchronous, local) amanda@escudo:~$ grep escudo nhh/disklist escudo.nhh.no da0s1a nhh-nocomp-noinc# / escudo.nhh.no da0s1e nhh-comp# /usr escudo.nhh.no da1s1e nhh-comp# /var escudo.nhh.no da1s1f nhh-comp# /var/log escudo.nhh.no da1s1g nhh-comp# /var/spool/mqueue escudo.nhh.no da1s1h nhh-comp# /home escudo.nhh.no da4s1e nhh-comp# /usr/cyrus/spool/stud escudo.nhh.no da5cnhh-comp# /usr/cyrus/spool/stab amanda@escudo:~$ amadmin nhh version build: VERSION="Amanda-2.4.2p2" BUILT_DATE="Wed May 29 14:11:51 CEST 2002" BUILT_MACH="FreeBSD escudo.nhh.no 4.5-RELEASE-p4 FreeBSD 4.5-RELEASE-p4 #6: Tue Apr 23 12:40:34 CEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ESCUDO i386" CC="gcc" paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" libexecdir="/usr/local/libexec" mandir="/usr/local/man" AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/r" DUMP="/sbin/dump" RESTORE="/sbin/restore" GNUTAR="/usr/bin/tar" COMPRESS_PATH="/usr/bin/gzip" UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" listed_incr_dir="/usr/local/var/amanda/gnutar-lists" defs: DEFAULT_SERVER="escudo.nhh.no" DEFAULT_CONFIG="nhh" DEFAULT_TAPE_SERVER="escudo.nhh.no" DEFAULT_TAPE_DEVICE="/dev/nrsa0" HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amanda@escudo:~$ ~kas -- Knut A. Syéd NHH, IT-avdelingen
