Email notifications
I recently did and upgrade/move of our mail server and now I no longer get the email notifications from Amanda. I didn't think there was a setting to specify your email server in amanda. Is it caching it somewhere? Any help is appreciated.
Re: RE amanda in domU
Thanks for the reply. I will look into this. Cyrille Bollu wrote: At home, I'm trying to move my USB printer in a domU xen domain. According to my reading, it's possible but I have to use a kernel command line argument like pciback.hide=(00:11.0) in dom0 and add something like pci = ['00,11,00'] to my guest configuration. (Didn't succeed yet though). Maybe, you should do the same for a tape drive? I have find http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module that might well help you. That was my 5cents help, Cyrille *James Wilson [EMAIL PROTECTED]* Envoyé par : [EMAIL PROTECTED] 10/10/2007 18:02 Veuillez répondre à [EMAIL PROTECTED] A amanda-users@amanda.org cc Objet amanda in domU I was wondering if amanda could run in a xen instance. And if so does the dom0 automatically pass the tape scsi adapter to the xen instance? Also if I move amanda to this xen instance will it be able to open my old tapes? Any help is appreciated.
Tapes not reusing
Amanda is not reusing tapes in my library. I have them setup to overwrite when it reaches the last tape but now I am getting this tape error. Any ideas? Thanks in advance. *** A TAPE ERROR OCCURRED: [No writable valid tape found]. Some dumps may have been left in the holding disk. Run amflush again to flush them to tape. The next 3 tapes Amanda expects to use are: a new tape, a new tape, DailyTape-21. The next new tape already labelled is: WeeklyTape-14.
Re: Tapes not reusing
Sorry, I will post my configs this time. I have them split up into 2
separate backups. DailyTapes run from Monday-Saturday and WeeklyTapes
run on Sunday which are always full backups. I meant the conf files by
Them.
Here is my amanda.conf from DailyTape only.
dumpcycle 7 # the number of days in the normal dump cycle
runspercycle 7 # the number of amdump runs in dumpcycle days
# (4 weeks * 5 amdump runs per week -- just
weekdays)
tapecycle 15 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
runtapes 3 # number of tapes to be used in a single run of
amdump
tpchanger chg-zd-mtx # the tape-changer glue script
tapedev /dev/nst0 # the no-rewind tape device to be used
changerfile /etc/amanda/tape/changer
changerdev /dev/sg0
tapetype IBM-LTO2# what kind of tape it is (see
tapetypes below)
holdingdisk hd2 {
directory /home/amandahold
use 5Mb
}
labelstr ^DailyTape-[0-9][0-9]*$ # label constraint regex: all
tapes must match
dtimeout 1800 # number of idle seconds before a dump is aborted.
ctimeout 30 # maximum number of seconds that amcheck waits
# for each client host
etimeout 300# number of seconds per filesystem for estimates.
includefile /etc/amanda/tape/advanced.conf
includefile /etc/amanda/tape/dumptypes
includefile /etc/amanda/tape/tapetypes
Jon LaBadie wrote:
On Fri, May 25, 2007 at 04:26:46PM -0500, James Wilson wrote:
Amanda is not reusing tapes in my library. I have them setup to overwrite
when it reaches the last tape but now I am getting this tape error. Any
ideas? Thanks in advance.
*** A TAPE ERROR OCCURRED: [No writable valid tape found].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next 3 tapes Amanda expects to use are: a new tape, a new tape,
DailyTape-21.
The next new tape already labelled is: WeeklyTape-14.
Amanda doesn't seem to agree with you.
When you say I have them setup, what is them, the library or
the amanda config. What is your amanda config, particularly the
value of tapecycle? How many tapes are in the library? Why does
it think some of your tapes for the same config are called DailyTape...
and others are called WeeklyTape...? Is the tape WeeklyTape-14 in
the library?
Re: Amanda Client
The reason I use amandabackup is because that is the user I created on
the server with the rpm packages. I have changed all the permissions on
the files to read amandabackup disk. I also copied what you posted below
and changed the host to amandabackup. From what you posted below the
only_from field should that be the client name or the amanda server
name? I can't test right because amanda is doing a backup but I will
test as soon as the backups are done.
Gene Heskett wrote:
On Monday 23 April 2007, James Wilson wrote:
Are you talking about the /etc/xinetd.d/amanda file? in my case it is
amandabackup.
That is not the usual name for that file. What distro are you running?
OTOH, the actual name of that file isn't terribly important, but the contents
are, and should generally resemble this, although the server locations could
change depending on your packaging system, and of course the FQDN too:
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons such it needs
service amanda
{
only_from = coyote.coyote.den
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
server_args = -auth=bsd amdump amindexd amidxtaped
}
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
===
which will result in those 3 'service's being registered with xinetd for ready
availability in the event they are called upon. As far as xinetd is
concerned there is zero difference in how it works if the file was broken up
into 3 pieces at the service keyword, and named jimbo, bubba and teri-sue, or
this all in one file was named after a BC comic strip character. Its what is
in the file(s) that that count. :-)
Pavel Pragin wrote:
James Wilson wrote:
Hey All,
I have amanda version 2.5.0p2 I have installed version 2.5.0p2-4
for the amanda client. I have added the amanda server and the amanda
user in the .amandahost file on the client I checked the
/etc/services and all the amanda ports are there. But when I try to
do an amcheck tape this is what I get. It's been awhile since I have
added a client, am I missing something?
WARNING: ifx-se-02.transolutions.net: selfcheck request failed:
timeout waiting for ACK
Client check: 1 host checked in 30.036 seconds, 1 problem found
Hello,
It sound like you are trying to use bsd authentication to connect to
a client that is using bsdtcp. You either need to upgrade to the
2.5.1 server or change the client to run bsd. These changes need to
be made in the xientd service for amanda.
Thank You
Amanda Client
Hey All, I have amanda version 2.5.0p2 I have installed version 2.5.0p2-4 for the amanda client. I have added the amanda server and the amanda user in the .amandahost file on the client I checked the /etc/services and all the amanda ports are there. But when I try to do an amcheck tape this is what I get. It's been awhile since I have added a client, am I missing something? WARNING: ifx-se-02.transolutions.net: selfcheck request failed: timeout waiting for ACK Client check: 1 host checked in 30.036 seconds, 1 problem found
Re: amanda-2.5.0p2-1.src.rpm
I got the source bilt and changed the path to amandad in the /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. Put when I run amcheck on the server for this host it still times out. Any ideas? Paddy Sreenivasan wrote: James, libamclient-2.5.0p2.so should be installed in /usr/lib directory and is part of the binary rpm. Source rpm (amanda-2.5.0p2-1.src.rpm) will not contain the libamclient library. You have to build the source rpm to get the libamclient library. Thanks, Paddy On 11/8/06, James Wilson [EMAIL PROTECTED] wrote: Hey All, I am installing this on RedHat version 9 and was wondering if there were additional steps needed for the source rpm? When I try to manually run ./selfcheck I get this error error while loading shared libraries: libamclient-2.5.0p2.so: cannot open shared object file: No such file or directory. Do I need to pull libamclient-2.5.0p2.so down from zmandas website? And if so do I need anything additional to this? Thanks
Re: amanda-2.5.0p2-1.src.rpm
I changed the permissions on the /tmp/amanda directory and now I get this. ERROR: NAK apexdev.transolutions.net: getpwnam(amandabacup) fails Stefan G. Weichinger wrote: James Wilson wrote: I got the source bilt and changed the path to amandad in the /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. Put when I run amcheck on the server for this host it still times out. Any ideas? faq/doc: restart xinetd, look for /tmp/amanda, permissions, Stefan
Re: amanda-2.5.0p2-1.src.rpm
I did a make uninstall and ran ./configure again but it still comes up with the user amandabacup instead of amandabackup. How can I totally remove the configuration? Stefan G. Weichinger wrote: James Wilson wrote: I got the source bilt and changed the path to amandad in the /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. Put when I run amcheck on the server for this host it still times out. Any ideas? faq/doc: restart xinetd, look for /tmp/amanda, permissions, Stefan
Re: amanda-2.5.0p2-1.src.rpm
Yes I ran ./configure --with-user=amandabackup --with-group=disk. Is there a way to remove the ./configure like make uninstall is there a similar command? Paddy Sreenivasan wrote: Did you run ./configure --with-user=amandabackup other configure options ? Please provide output of amadmin XX config command? Thanks, Paddy On 11/9/06, James Wilson [EMAIL PROTECTED] wrote: I did a make uninstall and ran ./configure again but it still comes up with the user amandabacup instead of amandabackup. How can I totally remove the configuration? Stefan G. Weichinger wrote: James Wilson wrote: I got the source bilt and changed the path to amandad in the /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. Put when I run amcheck on the server for this host it still times out. Any ideas? faq/doc: restart xinetd, look for /tmp/amanda, permissions, Stefan
Re: amanda-2.5.0p2-1.src.rpm
I apologize it seems that I was using the 2.5.0p2.tar.gz file not the sourc rpm. Does this make a difference? Paddy Sreenivasan wrote: Did you run ./configure --with-user=amandabackup other configure options ? Please provide output of amadmin XX config command? Thanks, Paddy On 11/9/06, James Wilson [EMAIL PROTECTED] wrote: I did a make uninstall and ran ./configure again but it still comes up with the user amandabacup instead of amandabackup. How can I totally remove the configuration? Stefan G. Weichinger wrote: James Wilson wrote: I got the source bilt and changed the path to amandad in the /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. Put when I run amcheck on the server for this host it still times out. Any ideas? faq/doc: restart xinetd, look for /tmp/amanda, permissions, Stefan
Re: amanda-2.5.0p2-1.src.rpm
Can you point me to some examples on building from source rpm? Paddy Sreenivasan wrote: James, libamclient-2.5.0p2.so should be installed in /usr/lib directory and is part of the binary rpm. Source rpm (amanda-2.5.0p2-1.src.rpm) will not contain the libamclient library. You have to build the source rpm to get the libamclient library. Thanks, Paddy On 11/8/06, James Wilson [EMAIL PROTECTED] wrote: Hey All, I am installing this on RedHat version 9 and was wondering if there were additional steps needed for the source rpm? When I try to manually run ./selfcheck I get this error error while loading shared libraries: libamclient-2.5.0p2.so: cannot open shared object file: No such file or directory. Do I need to pull libamclient-2.5.0p2.so down from zmandas website? And if so do I need anything additional to this? Thanks
selfcheck not running
Hey All, Any ideas on why selfcheck would not run on a client. I have a rhel4 server that I just installed the client on and I always get the selfcheck error. When I look in the /tmp/amanda directory there is no logs for selfcheck but there are logs for amandad. The logs for amandad say, any help is appreciated. amandad: time 0.001: creating new service: /usr/lib/amanda/noop OPTIONS features=feff9ffe07; amandad: time 0.003: sending ACK pkt: amandad: time 0.003: sending REP pkt: OPTIONS features=feff9ffe07; amandad: time 10.002: timeout amandad: time 10.002: sending REP pkt: OPTIONS features=feff9ffe07; amandad: time 10.003: received REQ pkt: SERVICE noop OPTIONS features=feff9ffe07; amandad: time 10.003: received unexpected REQ packet SERVICE noop OPTIONS features=feff9ffe07; amandad: time 10.003: sending NAK pkt: ERROR unexpected packet type REQ amandad: time 20.005: accept recv REQ pkt: SERVICE noop OPTIONS features=feff9ffe07; amandad: time 20.005: /usr/lib/amanda/noop OPTIONS features=feff9ffe07; : already running, acking req amandad: time 20.005: sending ACK pkt:
Timeout
Hey All,
I keep getting this error for one of my hosts.
selfcheck request failed: timeout waiting for ACK
Client check: 4 hosts checked in 30.153 seconds, 1 problem found
I have added this in my amandaclient file in the xinetd.d directory.
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
}
And I have this added to the .amandahosts file.
localhost amandabackup
localhost.localdomain amandabackup
amanda.transolutions.net amandabackup
amanda.transolutions.net root
Am I missing something? I have restarted the xinetd.d service. It is
hard to restart the service because this is a heavily used production
server. The server is running RHE4.
Re: Timeout
I am using version 2.5.0p2-1
Paddy Sreenivasan wrote:
If you are running 2.5.1 or 2.5.1p1, these xinetd and .amandahosts
entries
require changes. See
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication
For troubleshooting this problem, you can also see troubleshooting
wiki page:
http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_failed
Paddy
On 11/6/06, James Wilson [EMAIL PROTECTED] wrote:
Hey All,
I keep getting this error for one of my hosts.
selfcheck request failed: timeout waiting for ACK
Client check: 4 hosts checked in 30.153 seconds, 1 problem found
I have added this in my amandaclient file in the xinetd.d directory.
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
}
And I have this added to the .amandahosts file.
localhost amandabackup
localhost.localdomain amandabackup
amanda.transolutions.net amandabackup
amanda.transolutions.net root
Am I missing something? I have restarted the xinetd.d service. It is
hard to restart the service because this is a heavily used production
server. The server is running RHE4.
Selfcheck not running
The file selfcheck is there and it is owned by amandabackup and group
disk. However I have no log files from selfcheck. I installed the RPM
for rhel4 version 2.5.0p2-1
Paddy Sreenivasan wrote:
Check if selfcheck is installed in the machine. It must be in
/usr/lib/amanda/ directory. It should be owned by amanda user.
How did you install amanda client?
Paddy
On 11/6/06, James Wilson [EMAIL PROTECTED] wrote:
I have not selfcheck debug files in the /tmp/amanda directory. How ever
I do have this files on my other servers that are running amanda client.
Paddy Sreenivasan wrote:
It should be in client: /tmp/amanda directory in 2.5.0 and in
/tmp/amanda/client/config name/ directory in 2.5.1 It will called
selfcheck.datestamp.debug
Paddy
On 11/6/06, James Wilson [EMAIL PROTECTED] wrote:
Sorry for my ignorance but where are the selfcheck logs located?
Paddy Sreenivasan wrote:
This could be a problem. Is there information on selfcheck logs? It
appears selfcheck is not starting
Paddy
On 11/6/06, James Wilson [EMAIL PROTECTED] wrote:
Here is the file I do see the requests and replies but then I see
an one
line that says received unexpected REQ packet. Could this be the
problem?
Paddy Sreenivasan wrote:
Usually the problem is with the DNS on the client. Is there any
information on
amandad, selfcheck logs in /tmp/amanda directory?
Thanks,
Paddy
On 11/6/06, James Wilson [EMAIL PROTECTED] wrote:
I have done the pings and trace route and everything is
resolving.
Paddy Sreenivasan wrote:
Presence of virtual IPs should not matter.
Check if it is a name resolution issue.
Paddy
On 11/6/06, James Wilson [EMAIL PROTECTED] wrote:
I have tried the trouble shooting. The config files look
right,
does it
matter if their are virtual ip addresses on the client?
I'm not
trying
to connect to one of the virtual IP's but just wondering if
this
would
confuse amanda at all.
Paddy Sreenivasan wrote:
If you are running 2.5.1 or 2.5.1p1, these xinetd and
.amandahosts
entries
require changes. See
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication
For troubleshooting this problem, you can also see
troubleshooting
wiki page:
http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_failed
Paddy
On 11/6/06, James Wilson [EMAIL PROTECTED]
wrote:
Hey All,
I keep getting this error for one of my hosts.
selfcheck request failed: timeout waiting for ACK
Client check: 4 hosts checked in 30.153 seconds, 1
problem
found
I have added this in my amandaclient file in the xinetd.d
directory.
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
}
And I have this added to the .amandahosts file.
localhost amandabackup
localhost.localdomain amandabackup
amanda.transolutions.net amandabackup
amanda.transolutions.net root
Am I missing something? I have restarted the xinetd.d
service.
It is
hard to restart the service because this is a heavily
used
production
server. The server is running RHE4.
amandad: debug 1 pid 27487 ruid 6002 euid 6002: start at Mon
Nov 6
13:22:10 2006
amandad: version 2.5.0p2
amandad: build: VERSION=Amanda-2.5.0p2
amandad:BUILT_DATE=Fri May 12 11:52:52 PDT 2006
amandad:BUILT_MACH=Linux rocky.zmanda.com
2.6.9-22.0.2.ELsmp
#1 SMP Thu Jan 5 17:13:01 EST 2006 i686 i686 i386 GNU/Linux
amandad:CC=gcc
amandad:CONFIGURE_COMMAND='./configure'
'--build=i386-redhat-linux' '--prefix=/usr' '--bindir=/usr/bin'
'--sbindir=/usr/sbin' '--libexecdir=/usr/lib/amanda'
'--datadir=/usr/share' '--sysconfdir=/etc'
'--sharedstatedir=/var/lib/amanda'
'--localstatedir=/var/lib/amanda'
'--libdir=/usr/lib' '--includedir=/usr/include'
'--infodir=/usr/info'
'--mandir=/usr/share/man'
'--with-gnutar-listdir=/var/lib/amanda/gnutar-lists'
'--with-dumperdir=/usr/lib/amanda' '--with-index-server=localhost'
'--with-tape-server=localhost' '--with-user=amandabackup'
'--with-group=disk' '--with-owner=paddy' '--with-fqdn'
amandad: paths: bindir=/usr/bin sbindir=/usr/sbin
amandad:libexecdir=/usr/lib/amanda
mandir=/usr/share/man
amandad:AMANDA_TMPDIR=/tmp/amanda
AMANDA_DBGDIR=/tmp/amanda
amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/
amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump
amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF
Re: IP address change
The server and client are installed on the same box. This was working fine before I split my network up into vlans and changed the ip of the amanda server along with the subnetmask. All the ip's are correct and they all resolve to the server the are supposed to. All the servers with the amanda client work fine the ones that are using samba do not work. Jon LaBadie wrote: I didn't follow the earlier thread, so if this is way off base, sorry. I picked this out of your HTML posting: On Wed, Nov 01, 2006 at 08:52:15AM -0600, James Wilson wrote: ... . The servers that have amanda client installed backup fine. The amanda server and the other servers are in the same vlan.br br Sounds like amanda client and server software are being installed separately to each host as needed. Just to be sure you are aware, the server needs the client software to back up itself and to be able to backup indirect clients (samba shares or nfs mounts).
Re: Monthly backup
Well I have a folder lets say its called voice and in voice I have a bunch of folders in there labeled by date. Starting with todays date all the way back to 10-01-2005. I want to backup everything till may of 2006 for the. Then I'm going to delete all those files because I have them on tape. Then every month I just want to back up the next month so in this case the next month would be June then July etc. Steven Kurylo wrote: 1. Have a backup run once a month on the 1st. We have a config which only does full backups and cron schedules it to run at the start of the month. 2. Only backup data 7 months prior to todays date based on -mm format. Do you mean only keep 7 months worth of data? Then only put 7 tapes in the rotation.
Re: Monthly backup
the folder name doesn't change. for example if I have folders 2006-01 2006-02 2006-03 2006-04 And I only want to back up folders 2006-01 and 2006-02. Is this possible? To back up certain folders and not others in a particular directory. Steven Kurylo wrote: James Wilson wrote: Well I have a folder lets say its called voice and in voice I have a bunch of folders in there labeled by date. Starting with todays date all the way back to 10-01-2005. I want to backup everything till may of 2006 for the. Then I'm going to delete all those files because I have them on tape. Then every month I just want to back up the next month so in this case the next month would be June then July etc. So you don't want a full backup, just a specific folder whose name changes each month. I would create a symlink /path/to/link, pointing to /path/to/2006-04. Tell the backup to backup /path/to/link. When the backup is done, have a script which deletes /path/to/2006-04, then changes /path/to/link to point at 2006-05. Or you could have amanda backup everything, but use an exclude to block the most recent folders. Then you'd have to rewrite the exclude file regularly. I'm sure there might be a few other ways.
Re: Monthly backup
This is a good idea. Thanks for your reply. Jon LaBadie wrote: On Wed, Nov 01, 2006 at 11:17:09AM -0800, Steven Kurylo wrote: James Wilson wrote: Well I have a folder lets say its called voice and in voice I have a bunch of folders in there labeled by date. Starting with todays date all the way back to 10-01-2005. I want to backup everything till may of 2006 for the. Then I'm going to delete all those files because I have them on tape. Then every month I just want to back up the next month so in this case the next month would be June then July etc. So you don't want a full backup, just a specific folder whose name changes each month. I would create a symlink /path/to/link, pointing to /path/to/2006-04. snip I'm sure there might be a few other ways. Here is another ;) Have amanda totally exclude your voice directory tree. Outside of amanda create a monthly cronjob to make an archive (gnutar or zip or ???) of the voice directory you want to backup. The archive should be created somewhere amanda will backup. Perhaps an empty directory just for this purpose so it will be easy to find on recovery. Once the archive is made, and you are sure amanda has backed it up, delete the archive and the voice directory it contained. This could also be a cronjob that runs a day or several after the archive was made. It could even run daily, check the if an archive is in the directory, if so, check the amanda index files to see if it has been backed up, and only do the deletions if all conditions are met.
Re: IP address change
But there is only one server that is not in the same subnet the other 2 are. Aaron Taylor wrote: You stated that once you split your LAN up into multiple VLANs the Samba clients stopped working. Are you aware that the SMB protocol doesn't work across subnets by default without additional configuration? Thanks, -Aaron Taylor On 11/1/06, *James Wilson* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: The server and client are installed on the same box. This was working fine before I split my network up into vlans and changed the ip of the amanda server along with the subnetmask. All the ip's are correct and they all resolve to the server the are supposed to. All the servers with the amanda client work fine the ones that are using samba do not work. Jon LaBadie wrote: I didn't follow the earlier thread, so if this is way off base, sorry. I picked this out of your HTML posting: On Wed, Nov 01, 2006 at 08:52:15AM -0600, James Wilson wrote: ... . The servers that have amanda client installed backup fine. The amanda server and the other servers are in the same vlan.br br Sounds like amanda client and server software are being installed separately to each host as needed. Just to be sure you are aware, the server needs the client software to back up itself and to be able to backup indirect clients (samba shares or nfs mounts). -- Thanks, -Aaron Taylor
IP address change
Hey All, We just did a big network over haul at my job and every since the change amanda does not back up some machines. I looked in the latest log file and it states. Error planner request to amanda.transolutions.net failed: timeout waiting for ACK. amanda.transolutions.net //192.168.1.38/etc RESULTS MISSING amanda.transolutions.net //192.168.1.38/opt RESULTS MISSING amanda.transolutions.net //192.168.1.38/var RESULTS MISSING amanda.transolutions.net //192.168.1.10/Sessions RESULTS MISSING amanda.transolutions.net //192.168.1.10/Scripts RESULTS MISSING amanda.transolutions.net //192.168.1.7/interfix RESULTS MISSING amanda.transolutions.net //192.168.1.7/automate RESULTS MISSING amanda.transolutions.net //192.168.9.2/Crescendo RESULTS MISSING amanda.transolutions.net //192.168.9.2/BK RESULTS MISSING amanda.transolutions.net /usr RESULTS MISSING amanda.transolutions.net /etc RESULTS MISSING amanda.transolutions.net /opt RESULTS MISSING I did change the IP address of the amanda server would this have an effect on the backups for some reason?
No more holding disk space
Hey All, Lately I've been gettting the Failed [no more holding disk space] for this one client. Is there something I can do to fix this? It has been backing up fine until Sunday night and Monday night. FAILURE AND STRANGE DUMP SUMMARY: amanda.transolutions.net //192.168.1.38/etc lev 1 STRANGE amanda.transolutions.net //192.168.1.38/var lev 1 STRANGE vikings.transolutions.net /opt lev 1 STRANGE amanda.transolutions.net //192.168.1.38/opt lev 1 STRANGE amanda.transolutions.net //192.168.1.202/interfix lev 1 STRANGE amanda.transolutions.net //192.168.1.26/Sessions lev 1 STRANGE amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE amanda.transolutions.net //192.168.1.23/Crescendo lev 1 STRANGE amanda.transolutions.net //192.168.1.23/BKlev 4 FAILED [no more holding disk space]
Re: No more holding disk space
I have a server with 60 GB of disk space left after installing everything. I thought I gave amanda the whole 60 gigs. Should it need more that that? Jon LaBadie wrote: On Tue, Sep 26, 2006 at 08:42:58AM -0500, James Wilson wrote: Hey All, Lately I've been gettting the Failed [no more holding disk space] for this one client. Is there something I can do to fix this? It has been backing up fine until Sunday night and Monday night. FAILURE AND STRANGE DUMP SUMMARY: amanda.transolutions.net //192.168.1.38/etc lev 1 STRANGE amanda.transolutions.net //192.168.1.38/var lev 1 STRANGE vikings.transolutions.net /opt lev 1 STRANGE amanda.transolutions.net //192.168.1.38/opt lev 1 STRANGE amanda.transolutions.net //192.168.1.202/interfix lev 1 STRANGE amanda.transolutions.net //192.168.1.26/Sessions lev 1 STRANGE amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE amanda.transolutions.net //192.168.1.23/Crescendo lev 1 STRANGE amanda.transolutions.net //192.168.1.23/BKlev 4 FAILED [no more holding disk space] At the risk of sounding pedantic, increase the amount of holding disk space. It doesn't have to be a single space, I'm currently using two and my previous installation had four holding disks (HDs). Just empty directories on different file systems that I let amanda use all the available space except one or two GB. And I set the chunk size to one or two GB so it is easy to split a DLE among the various HDs. You might also see if some junk is still in the HD. You might also split up the DLE so it doesn't require so much HD. It also sounds as if the estimate is incorrect as I don't think amanda will write to the HD if it expects the size to be bigger than the available space. Instead it would send that DLE direct to tape.
Re: No more holding disk space
Thanks for the reply Jon. I thought I had 60 gig specified but infact I only had 10gig specified. Sorry for the inconvience. Jon LaBadie wrote: On Tue, Sep 26, 2006 at 08:42:58AM -0500, James Wilson wrote: Hey All, Lately I've been gettting the Failed [no more holding disk space] for this one client. Is there something I can do to fix this? It has been backing up fine until Sunday night and Monday night. FAILURE AND STRANGE DUMP SUMMARY: amanda.transolutions.net //192.168.1.38/etc lev 1 STRANGE amanda.transolutions.net //192.168.1.38/var lev 1 STRANGE vikings.transolutions.net /opt lev 1 STRANGE amanda.transolutions.net //192.168.1.38/opt lev 1 STRANGE amanda.transolutions.net //192.168.1.202/interfix lev 1 STRANGE amanda.transolutions.net //192.168.1.26/Sessions lev 1 STRANGE amanda.transolutions.net //192.168.1.133/ifxsessions lev 1 STRANGE amanda.transolutions.net //192.168.1.23/Crescendo lev 1 STRANGE amanda.transolutions.net //192.168.1.23/BKlev 4 FAILED [no more holding disk space] At the risk of sounding pedantic, increase the amount of holding disk space. It doesn't have to be a single space, I'm currently using two and my previous installation had four holding disks (HDs). Just empty directories on different file systems that I let amanda use all the available space except one or two GB. And I set the chunk size to one or two GB so it is easy to split a DLE among the various HDs. You might also see if some junk is still in the HD. You might also split up the DLE so it doesn't require so much HD. It also sounds as if the estimate is incorrect as I don't think amanda will write to the HD if it expects the size to be bigger than the available space. Instead it would send that DLE direct to tape.
Re: AMRESTORE
Never mind I found the -C option and that worked fine. Thanks for any replies. James Wilson wrote: I am trying to do a test restore from amanda and I get this error Could not read config file /etc/amanda/DailySet1/amanda.conf! I don't have a DailySet1 directory. Where do I change the path for this?
Compression
How can I tell what compression I am using? Also how do I make sure hardware compression is off?
Amanda, Novell
I was wondering if amanda was capable of backing up an older version of novell. 5.0, 3.12?
Re: Partial backup
\* ? Call timed out: server did not respond after 2 milliseconds listing \T\* | tar: dumped 178 files and directories | Total bytes written: 11032576 sendbackup: size 10774 sendbackup: end \ Jon LaBadie wrote: On Thu, Jul 13, 2006 at 05:34:50PM -0500, James Wilson wrote: Here is an amstatus before and after the backup. Before it estimated 1231m but after it only backed up 171m. Howcome amanda isn't backing up everything? amstatus is not the tool to use. After a dump you should receive a report via email. If you don't are not getting them, they can be regenerated with amreport. It looks to me like these are status reports from two different runs of amdump. Note, if you run it without an amdump actively running, amstatus reports on the previous run. You say the first was "before" the backup. That would suggest it is the status of the previous backup. It does not report the status of the file system in preparation for a future run of amdump. amanda.transolutions.net://192.168.1.133/ifxsessions 0 1231m partial estimate done SUMMARY part real estimated size size partition : 1 estimated : 1 1231m flush : 0 0m failed : 00m ( 0.00%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 0 0m 0m ( 0.00%) ( 0.00%) Nothing was dumped on this run. wait for writing: 0 0m 0m ( 0.00%) ( 0.00%) wait to flush : 0 0m 0m (100.00%) ( 0.00%) writing to tape : 0 0m 0m ( 0.00%) ( 0.00%) failed to tape : 0 0m 0m ( 0.00%) ( 0.00%) taped : 0 0m 0m ( 0.00%) ( 0.00%) 32 dumpers idle : not-idle taper idle network free kps: 1001400 holding space : 1m (100.00%) 0 dumpers busy : 0:00:00 ( 0.00%) sh-3.1$ amstatus tape Using /etc/amanda/tape/amdump.1 from Thu Jul 13 16:29:51 CDT 2006 amanda.transolutions.net://192.168.1.133/ifxsessions 05m finished (17:08:58) SUMMARY part real estimated size size partition : 1 estimated : 1 171m flush : 0 0m failed : 00m ( 0.00%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 1 5m 171m ( 3.40%) ( 3.40%) It was not 171 mb that was dumped, the estimate was 171. What was dumped was 5 mb. wait for writing: 0 0m 0m ( 0.00%) ( 0.00%) wait to flush : 0 0m 0m (100.00%) ( 0.00%) writing to tape : 0 0m 0m ( 0.00%) ( 0.00%) failed to tape : 0 0m 0m ( 0.00%) ( 0.00%) taped : 1 5m 171m ( 3.40%) ( 3.40%) 32 dumpers idle : no-dumpers taper idle network free kps: 1001400 holding space : 1m (100.00%) chunker0 busy : 0:00:00 ( 0.00%) dumper0 busy : 0:08:59 ( 23.00%) taper busy : 0:00:06 ( 0.27%) 0 dumpers busy : 0:35:36 ( 91.02%)not-idle: 0:35:30 ( 99.70%) no-dumpers: 0:00:06 ( 0.30%) 1 dumper busy : 0:00:00 ( 0.00%) Much more detail would be available from amreport.
Partial backup
Here is an amstatus before and after the backup. Before it estimated 1231m but after it only backed up 171m. Howcome amanda isn't backing up everything? amanda.transolutions.net://192.168.1.133/ifxsessions 0 1231m partial estimate done SUMMARY part real estimated size size partition : 1 estimated : 1 1231m flush : 0 0m failed : 00m ( 0.00%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 0 0m 0m ( 0.00%) ( 0.00%) wait for writing: 0 0m 0m ( 0.00%) ( 0.00%) wait to flush : 0 0m 0m (100.00%) ( 0.00%) writing to tape : 0 0m 0m ( 0.00%) ( 0.00%) failed to tape : 0 0m 0m ( 0.00%) ( 0.00%) taped : 0 0m 0m ( 0.00%) ( 0.00%) 32 dumpers idle : not-idle taper idle network free kps: 1001400 holding space : 1m (100.00%) 0 dumpers busy : 0:00:00 ( 0.00%) sh-3.1$ amstatus tape Using /etc/amanda/tape/amdump.1 from Thu Jul 13 16:29:51 CDT 2006 amanda.transolutions.net://192.168.1.133/ifxsessions 05m finished (17:08:58) SUMMARY part real estimated size size partition : 1 estimated : 1 171m flush : 0 0m failed : 00m ( 0.00%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 1 5m 171m ( 3.40%) ( 3.40%) wait for writing: 0 0m 0m ( 0.00%) ( 0.00%) wait to flush : 0 0m 0m (100.00%) ( 0.00%) writing to tape : 0 0m 0m ( 0.00%) ( 0.00%) failed to tape : 0 0m 0m ( 0.00%) ( 0.00%) taped : 1 5m 171m ( 3.40%) ( 3.40%) 32 dumpers idle : no-dumpers taper idle network free kps: 1001400 holding space : 1m (100.00%) chunker0 busy : 0:00:00 ( 0.00%) dumper0 busy : 0:08:59 ( 23.00%) taper busy : 0:00:06 ( 0.27%) 0 dumpers busy : 0:35:36 ( 91.02%)not-idle: 0:35:30 ( 99.70%) no-dumpers: 0:00:06 ( 0.30%) 1 dumper busy : 0:00:00 ( 0.00%)
Amanda
This is the 2 errors I get when I run amlabel. Does anyone know why?
I've attached my amanda.conf file and changer file. Thanks for any advice.
cannot determine first slot
amlabel: could not load slot current: line 31: Product: command not found
#! /bin/sh
###
# AMANDA Tape Changer script for use with the MTX tape changer program
# Version 1.0 - Tue Feb 20 13:59:39 CST 2001
#
# Based on 'stc-changer' by Eric Berggren ([EMAIL PROTECTED])
# Updated by Tim Skirvin ([EMAIL PROTECTED])
#
# Given that there's no license...let's make this the Perl Artistic License.
# Just make sure you give me and Eric credit if you modify this.
###
### USER CONFIGURATION
# Name of the tape drive (takes place of tapedev option in amanda.conf)
# and default driver number in library (usu 0) that DRIVE_NAME points to
DRIVE_NAME=/dev/nst0
DRIVE_NUM=0
# Location of STC command and control device
MTX_CMD=/usr/local/sbin/mtx;
MTX_CONTROL=/dev/sg0;
# Whether tape drive must eject tape before changer retrieves
# (ie, EXB-2x0). Usually okay if set while not necessary, bad if
# required but not set.
DRIVE_MUST_EJECT=1
# How long to check drive readiness (in seconds) after mounting (or
# ejecting) a volume (on some libraries, the motion or eject command may
# complete before the drive has the volume fully mounted and online,
# or ready for retrieval, resulting in Drive not ready/Media not
# ready errors). Do an mt status command every 5 seconds upto this
# time.
DRIVE_READY_TIME_MAX=120
# tape mt command location...
MT_CMD=/usr/bin/mt # called via MT_CMD -f DRIVE_NAME rewind
# MT_CMD -f DRIVE_NAME offline to eject
# and MT_CMD -f DRIVE_NAME status to get ready info
##
#
NumDrives=-2
NumSlots=-23
LastSlot=-23
LoadedTape=-1
#
# Usage information
#
usage()
{
echo
echo Usage: $Progname command [arg...]
echo -info reports capability and loaded tape
echo -slot slot loads specified tape into drive
echo current reports current mounted tape
echo next loads logically next tape (loops to top)
echo prev loads logically previous tape (loops to bot)
echo firstloads first tape
echo last loads last tape
echo 0..99loads tape from specified slot#
echo -eject uloads current mounted tape
echo -reset resets changer (and drive); loads first tape
echo
exit 5
}
#
# Perform stc changer command ( handle the fatal errors)
# else, set 'CommandResStr' and 'CommandRawResStr' to the result string
# and 'CommandResCode' to the exit code
#
dotapecmd()
{
cmd=$1
arg=$2
CommandResStr=`$MTX_CMD $MTX_CONTROL $cmd $arg 21`
CommandRawResStr=$CommandResStr
CommandResCode=$?
CommandResStr=`echo $CommandResStr | head -1 | sed 's/^[^:]*: //'`
if [ $CommandResCode -gt 1 ]; then
echo 0 $Progname: returned $CommandResStr
exit 2
fi
}
#
# Unload tape from drive (a drive command; ejecttape is a changer command
# to actually retrieve the tape). Needed by some changers (controlled by
# setting DRIVE_MUST_EJECT)
#
ejectdrive()
{
# Tell drive to eject tape before changer retrieves; req'd by some
# drives (ie, EXB-2x0). Not needed by QDLT-4x00. Do a rewind
# command first, then offline to eject (instead of rewoffl)
#
if [ $DRIVE_MUST_EJECT -ne 0 ]; then
mtresstr=`$MT_CMD -f $DRIVE_NAME rewind 21`
mtrescode=$?
if [ $mtrescode -ne 0 ]; then
if echo $mtresstr | egrep -s 'no tape'; then
:; # no tape mounted; assume okay...
else
# can't eject tape, bad; output: tape# reason
echo 0 $mtresstr
exit 1
fi
else
mtresstr=`$MT_CMD -f $DRIVE_NAME offline 21`
mtrescode=$?
checkdrive 1
fi
fi
}
#
# Check drive readiness after (un)mounting a volume (which may take a while
# after the volume change command completes)
#
checkdrive()
{
unmounting=$1
if [ $DRIVE_READY_TIME_MAX -gt 0 ]; then
# sleep time between checks
pausetime=5
# number of interations to check
numchecks=`expr $DRIVE_READY_TIME_MAX / $pausetime`
if [ $numchecks -eq 0 ]; then
numchecks=1
fi
# check until success, or out of attempts...
while [ $numchecks -gt 0 ]; do
mtresstr=`$MT_CMD -f $DRIVE_NAME status 21`
mtrescode=$?
if [ $mtrescode -eq 0 ]; then
# Success ?
return 0
else
# pause, before trying again
if [ $numchecks -gt 1
Amanda
Here is the full error I am getting now. amlabel: could not load slot current: cannot determine first slot
Amanda
Hi, I am new to Amanda and I was just wondering if anyone here has configured a Dell powervault 132T with 2 drives and 23 slots or anything close to this. When I run amtapetype I get an unknow-tapetype is the right for the powervault? Also wondering if Amanda can backup directories or does it just backup the whole hard drive? Can I write more than one dump to a tape? Any config examples or pointers are appreciated, right now I only have the basics completed like the client setup the hosts, directories, etc. Thanks, James
