RE: RedHat, amanda, and permission denied
The Redhat 7.2 distribution contained an RPM that was only the client and not the complete package. Needless to say that didn't work for me. I had the best luck doing the compile. Just an FYI Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 25, 2002 12:50 PM To: [EMAIL PROTECTED] Subject: Re: RedHat, amanda, and permission denied In message [EMAIL PROTECTED], Martin Hepworth writes: Ok so when you compiled did to specify the user and group or not give theses params to configure ?? I don't remember now. I'll have to check. If you didn't you'll need to rerun configure with them in (I recommend and makle clean before hand). Thanks, if I can't easily find the Amanda RPM's, I'll do that. -s
RE: amrecover - I have obviously overlooked something
.amandahosts contains the following: schroeder root hosts.allow contains the following lines for schroeder: ALL: 127.0.0.1 ALL: 192.168.4.98 I am assuming that it is amidxtape. The closest reference I can find is amidxtaped. I do not show a service running by this name though. Is amidxtaped called or is is supposed to be a service? Doug -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Friday, April 05, 2002 10:35 AM To: Doug Johnson Cc: Amanda-Users (E-mail) Subject: Re: amrecover - I have obviously overlooked something On Fri, 5 Apr 2002 at 10:23am, Doug Johnson wrote ** AMRECOVER EXAMPLE * [root@schroeder amanda]# amrecover AMRECOVER Version 2.4.2p2. Contacting server on schroeder ... amrecover: cannot connect to schroeder: Connection refused Do you have root listed in the .amandahosts on schroeder? Is amidxtape (or is it amandaidx) from schroeder allowed in hosts.allow? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
New message output in log.
another cup of coffee this morning will be welcomed. Doug Johnson Systems Administrator Vifan USA, Inc.
RE: Amanda and xinetd
I don't know if it means anything or not but I have a disable statement in
all of my xinetd files. I am using RH 7.2 and each config is located in the
xinetd.d directory under etc. Mine look like this:
[root@schroeder xinetd.d]# cat amandad
# default: off
#
# description: Part of the Amanda server package
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
[root@schroeder xinetd.d]# cat amandaidx
# default: off
#
# description: Part of the Amanda server package
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
groups = yes
server = /usr/local/libexec/amindexd
}
[root@schroeder xinetd.d]# cat amidxtape
# default: off
#
# description: Part of the Amanda server package
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
groups = yes
server = /usr/local/libexec/amidxtaped
server_args = amidxtaped
}
Doug
-Original Message-
From: Cory Visi [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 11, 2002 10:33 AM
To: [EMAIL PROTECTED]
Subject: Amanda and xinetd
Well all my problems are basically due to the fact that Amanda refuses to
work with xinetd. This was suggested by someone on the list and I finally
decided to try it. Why doesn't Amanda work with xinetd? There is no good
debugging log that would help in figuring out this problem. Amandad clearly
does not recognize the IPv4 unicast bindings that it needs to with xinetd.
Here is my inetd.conf:
amanda dgram udp wait backup /usr/local/libexec/amandad amandad
Here is my relevant xinetd.conf:
service amanda
{
id = amanda-udp
log_on_success += USERID
log_on_failure += USERID
socket_type = dgram
protocol = udp
wait = yes
user = backup
server = /usr/local/libexec/amandad
}
This really looks like a bug in the program as xinetd and inetd are
designed to operate as identical as possible.
Thanks,
Cory Visi
RE: Backup NT share with amanda
Do you by chance have a /tmp/amanda/sendsize*debug file from the client? Looking where the failure comes from it may be when planner sends the sendsize request and the result was not what it was expecting to see. This may be one option to look at. Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 7:37 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Backup NT share with amanda Two forms its successfully, but I cant backup the files. The error is the same. Thanks. From: Ulrik Sandberg [EMAIL PROTECTED] To: Doug Johnson [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: RE: Backup NT share with amanda Date: Tue, 7 May 2002 00:56:48 +0200 (Västeuropa, sommartid) you may want to test the SAMBA connection: smbclient nt-server\\share (The extra slashes are not a mistake. They are used to escape the backslashes under unix.) Just to save you guys some keystrokes, forward slash works equally well: smbclient //nt-server/share -- Ulrik Sandberg _ Envíe y reciba su correo de Hotmail desde el móvil: http://mobile.msn.com
RE: Backup NT share with amanda
I may be wrong, but this is the way I have mine setup. I believe that you must use the tar option when backing up a SAMBA share. I am assuming here that you are using SAMBA to be able to connect to the NT Share. If so then you may want to test the SAMBA connection: smbclient nt-server\\share (The extra slashes are not a mistake. They are used to escape the backslashes under unix.) Using this command you should get a password prompt. Running this as amanda and using amanda's password should get you access to the share (assuming you have given amanda a backup operaotr's account under NT). Give that a try and if I am off base about your setup let me know. Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 1:31 PM To: [EMAIL PROTECTED] Subject: Backup NT share with amanda Hello, I am a new amanda-user, and I have a problem whith NT share. I have this configuration RH 7.2 Amanda 2.4.2p2 disklist linux-server //nt-server/share always-full amandapass //nt-server/share user%passwd WORKGROUP when I run amcheck MyConf all its ok, but when I run amdump with the new tape this is the error in the mail. FAILURE AND STRANGRE SUMMARY linux-server //nt-server/share RESULTS MISSING NOTES planer Adding new disk linux-server//nt-server/share. HOSTNAME DISKORIG-KB OUT-KB COMP% MMMSS KB/S MMSS KN/S linux-server nt-server/share MISSING - DO YOU HAVE ANY IDEA? Thanks. _ Envíe y reciba su correo de Hotmail desde el móvil: http://mobile.msn.com
RE: Backup NT share with amanda
I have included my examples on the disklist and the dumptype. Don't forget
the amandapass file in etc that must be created by hand which I believe that
you had earlier. I cannot recall why I did not use the example of the
dumptype in the docs. But I do recall that when I compiled the program it
was using GNUTAR as my installation. I am using RedHat 7.2 and the only
problem that I had were extended characters which I resolved with the new
version of SAMBA.
My disklist for the NT shares looks like this:
schroeder //ntusa2/c$ user-tar
schroeder //ntusa1/c$ user-tar
schroeder //ntusa1/d$ user-tar
schroeder //ntusa1/e$ user-tar
My dumptype looks like this:
define dumptype user-tar {
root-tar
comment user partitions dumped with tar
priority medium
}
I found an article about Results Missing in the archive. It said the
following:
Strictly speaking it means when amreport ran to generate the E-mail
after planner and driver had done all the work, it could not find those
clients/disks in the log file.
Look at the corresponding log.MMDD.NN file. First, make sure it
ends properly with a FINISH driver ... line. Then find all the lines
related to one of the clients/disks that worked so you see what a normal
run should look like. Then look for one of the RESULTS MISSING ones
and see what's different.
Next, look at the corresponding amdump.NN file for the RESULTS MISSING
clients/disks. If planner says it got estimates from them, look for
driver FILE-DUMP or PORT-DUMP commands to a dumper. Then track that
particular dumper and see what it had to say after that.
So take a look at the logs and see what it may not like in that area.
Doug
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 06, 2002 3:07 PM
To: [EMAIL PROTECTED]
Subject: RE: Backup NT share with amanda
I read the page http://www.fnal.gov/docs/products/amanda/docs/SAMBA
I run smbclient and I see the directories and amanda is a backup operaotr's
account under NT.
The dump type is
global
program ´´GNUTAR´´
comment ´´Full dum always´´
compress client fast
dumpcycle 0
From: Doug Johnson [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: Backup NT share with amanda
Date: Mon, 6 May 2002 14:18:04 -0400
I may be wrong, but this is the way I have mine setup. I believe that you
must use the tar option when backing up a SAMBA share. I am assuming here
that you are using SAMBA to be able to connect to the NT Share. If so then
you may want to test the SAMBA connection:
smbclient nt-server\\share
(The extra slashes are not a mistake. They are used to escape the
backslashes under unix.)
Using this command you should get a password prompt. Running this as amanda
and using amanda's password should get you access to the share (assuming
you
have given amanda a backup operaotr's account under NT).
Give that a try and if I am off base about your setup let me know.
Doug
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 06, 2002 1:31 PM
To: [EMAIL PROTECTED]
Subject: Backup NT share with amanda
Hello,
I am a new amanda-user, and I have a problem whith NT share.
I have this configuration
RH 7.2
Amanda 2.4.2p2
disklist
linux-server //nt-server/share always-full
amandapass
//nt-server/share user%passwd WORKGROUP
when I run amcheck MyConf all its ok, but when I run amdump with the new
tape this is the error in the mail.
FAILURE AND STRANGRE SUMMARY
linux-server //nt-server/share RESULTS MISSING
NOTES
planer Adding new disk linux-server//nt-server/share.
HOSTNAME DISKORIG-KB OUT-KB COMP% MMMSS KB/S MMSS KN/S
linux-server nt-server/share MISSING -
DO YOU HAVE ANY IDEA?
Thanks.
_
Envíe y reciba su correo de Hotmail desde el móvil: http://mobile.msn.com
_
Hable con sus amigos en línea, pruebe MSN Messenger: http://messenger.msn.es
Which nst0 or st0 in post amdump functions is desireable?
After I do my amdump in the crontab I was thinking about ejecting the tape. And since I am not using a changer in the config the only way I have found so far is to use the mt command. It seems that in the archives that there are two different methods used in the following situation: 0 3 * * 1-5 /usr/local/sbin/amdump DailySet1 mt -f /dev/nst0 rewoffl 0 3 * * 1-5 /usr/local/sbin/amdump DailySet1 mt -f /dev/st0 rewoffl The difference being how the device is called (nst0 vs. st0). Since I am now using the magnetic tape command from the system do I still need to reference the nst0 device which is used in the amdump. What problems or issues would it cause in either method? Thanks in advance, Doug Johnson Systems Administrator Vifan USA, Inc. 1 Vifan Drive Morristown, TN 37814 423-581-6990 x207
RE: another amrecover problem.
No, everything was right on target. Even though the index files were there the operator service couldn't read them. Everything is runnig as amanda:disk and works smooth. Thanks again. doug -Original Message- From: John R. Jackson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 09, 2002 5:46 PM To: Doug Johnson Cc: Amanda-Users (E-mail) Subject: Re: another amrecover problem. Worked like a charm. ... Did you have to do anything I didn't remember in my list? If not, then I'll take your advice and get this posted to the FAQ. Doug John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amrecover - I have obviously overlooked something
Running Linux Redhat 7.2 with amanda-2.4.2p2 with advfx.diff patch applied. Amcheck works great: AMCHECK EXAMPLE *** [root@schroeder amanda]# amcheck disklist Amanda Tape Server Host Check - Holding disk /dumps/amanda: 3098380 KB disk space available, that's plenty ERROR: cannot overwrite active tape DailySet100 (expecting a new tape) No problem here, I have the last tape in the machine I ran amdump with NOTE: skipping tape-writable test Server check took 1.937 seconds Amanda Backup Client Hosts Check Client check: 4 hosts checked in 0.069 seconds, 0 problems found (brought to you by Amanda 2.4.2p2) ** END EXAMPLE *** Amdump works with no errors as well. When I run amrecover here is what I get: ** AMRECOVER EXAMPLE * [root@schroeder amanda]# amrecover AMRECOVER Version 2.4.2p2. Contacting server on schroeder ... amrecover: cannot connect to schroeder: Connection refused ***END EXAMPLE ** Any help in pointing me in the right direction would be great. Thanks, Doug
RE: amrecover - I have obviously overlooked something
.amandahosts contains the following: schroeder root hosts.allow contains the following lines for schroeder: ALL: 127.0.0.1 ALL: 192.168.4.98 I am assuming that it is amidxtape. The closest reference I can find is amidxtaped. I do not show a service running by this name though. Is amidxtaped called or is is supposed to be a service? Doug -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Friday, April 05, 2002 10:35 AM To: Doug Johnson Cc: Amanda-Users (E-mail) Subject: Re: amrecover - I have obviously overlooked something On Fri, 5 Apr 2002 at 10:23am, Doug Johnson wrote ** AMRECOVER EXAMPLE * [root@schroeder amanda]# amrecover AMRECOVER Version 2.4.2p2. Contacting server on schroeder ... amrecover: cannot connect to schroeder: Connection refused Do you have root listed in the .amandahosts on schroeder? Is amidxtape (or is it amandaidx) from schroeder allowed in hosts.allow? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: amrecover - I have obviously overlooked something
Those two services were the key. Thanks to all who helped!
Doug
-Original Message-
From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 12:01 PM
To: Doug Johnson
Cc: Amanda-Users (E-mail)
Subject: RE: amrecover - I have obviously overlooked something
On Fri, 5 Apr 2002 at 11:48am, Doug Johnson wrote
I am assuming that I need one of these files for amandaidx and amidxtape.
Is
this correct?
Yep. Mine look like:
[jlb@chaos jlb]$ cat /etc/xinetd.d/amandaidx
# default: off
#
# description: Part of the Amanda server package
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
server = /usr/local/libexec/amindexd
}
[jlb@chaos jlb]$ cat /etc/xinetd.d/amidxtape
# default: off
#
# description: Part of the amanda server package
#
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
server = /usr/local/libexec/amidxtaped
}
Also note that xinetd needs more than just a HUP to restart itself. Just
do '/etc/init.d/xinetd restart' after adding those files, and you'll be
ready to go.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
dumpdates causing amdump to fail.
I am wanting to dump /etc which contains the dumpdates file. Is there a way to ignore or exclude in a non-compression dump this file in etc. The error I recieve is /-- linus /etc lev 0 FAILED [/sbin/dump returned 1] sendbackup: start [linus:/etc level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f... - sendbackup: info end | DUMP: You can't update the dumpdates file when dumping a subdirectory | DUMP: The ENTIRE dump is aborted. sendbackup: error [/sbin/dump returned 1] \ Any suggestions would be greatly appreciated. Thanks, Doug Johnson Systems Administrator Vifan USA, Inc. 1 Vifan Drive Morristown, TN 37814 423-581-6990 x207
RE: dumpdates causing amdump to fail.
Thanks Joshua. R'ing every manual I can find I was trying to come up with a solution to a problem that I am having. When I choose the root file system (/) called sda5 and put it in the disklist as follows: schroeder sda5 nocomp-root I receive the following error when I do an amcheck: ERROR: schroeder: [could not access sda5 (sda5): No such file or directory] I though that maybe it didn't like the fact that it was a / filesystem so I was trying to just use the directories that I specify. If I exclude that filesystem everything works ok. Whats up with /? And what page did you find that information on? : Doug -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 04, 2002 2:50 PM To: Doug Johnson Cc: [EMAIL PROTECTED] Subject: Re: dumpdates causing amdump to fail. On Thu, 4 Apr 2002 at 2:05pm, Doug Johnson wrote | DUMP: You can't update the dumpdates file when dumping a subdirectory RTEM. :) You're trying to back up a subdirectory, not a filesystem. dump won't let you do this. Either back up filesystems only or use tar. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
LTO Drive
Has anyone had experience with an LTO drive with amanda? After setting my config file which is included below I run amcheck and get the following message. [root@schroeder disklist]#amcheck disklist Amanda Tape Server Host Check - Holding disk /dumps/amanda: 3224648 KB disk space available, that's plenty amcheck-server: slot 0: not an amanda tape insert tape into slot 1 and press return### Problem here also. I believe I have specified no changer in config Understanding that I need to label the tape I run amlabel and get the following result: [root@schroeder disklist]# amlabel disklist DailySet101 labeling tape in slot 0 (/dev/st0): rewinding, reading label, not an amanda tape rewinding, writing label DailySet101, checking label amlabel: no label found, are you sure /dev/st0 is non-rewinding? How do I change it to a rewinding or what would you believe I would need to do in this case. Any help would be appreciated. Config provided below: [root@schroeder disklist]# cat amanda.conf ### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ### ### ### ### This file is not meant to be installed as is, and in fact, it ### ### WILL NOT WORK! You must go through it and make changes appropriate ### ### to your own situation. See the documentation in this file, in the ### ### man amanda man page, in the docs directory and at the Amanda### ### web page (www.amanda.org). ### ### ### ### !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! !!! WARNING !!! ### # # amanda.conf - sample Amanda configuration file. This started off life as # the actual config file in use at CS.UMD.EDU. # # If your configuration is called, say, csd, then this file normally goes # in /usr/local/etc/amanda/csd/amanda.conf. # org DailySet1 # your organization name for reports mailto amanda root# space separated list of operators at your site dumpuser root # the user to run dumps under inparallel 4# maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec dumpcycle 0 # the number of days in the normal dump cycle runspercycle 0 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 5 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle ### ### ### # WARNING: don't use `inf' for tapecycle, it's broken! ### ### ### bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300# number of seconds per filesystem for estimates. #etimeout -600 # total number of seconds for estimates. # a positive number will be multiplied by the number of filesystems on # each host; a negative number will be taken as an absolute total time-out. # The default is 5 minutes per filesystem. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 20 # A positive integer telling taper how many 32k buffers to allocate. # WARNING! If this is set too high, taper will not be able to allocate # the memory and will die. The default is 20 (640k). # Specify tape device and/or tape changer. If you don't have a tape # changer, and you don't want to use more than one tape per run of # amdump, just comment out the definition of tpchanger. # Some tape changers require tapedev to be defined; others will use # their own tape device selection mechanism. Some use a separate tape # changer device (changerdev), others will simply ignore this # parameter. Some rely on a configuration file (changerfile) to # obtain more information about tape devices, number of slots, etc; # others just need to store some data in files, whose names will start # with changerfile. For more information about individual tape # changers, read docs/TAPE.CHANGERS. # At most one changerfile entry must be defined; select the most # appropriate one for your configuration. If you select man-changer, # keep the first one; if you decide not to use a tape changer, you may # comment
