nvironment. This fact made the problem a not trivial one.
What I did was to use:
0 0 * * * env LANG=en_US /usr/local/amanda/sbin/amdump ISR1
in the crontab.
Cheers,
On Apr 2, 2008, at 3:36 PM, Rodrigo Ventura wrote:
Hello,
from some time now amanda has refused to send me mails. Acco
and failed: /usr/bin/Mail -s "ISR1 AMANDA MAIL
REPORT FOR April 2, 2008" sysadmin
@isr.ist.utl.pt
0
0
0
[...]
However, the command "amreport ISR1 -l log.2008040202.0",
launched from a shell, user amanda obviuously, works fine!
Any clues?
In the shell, LANG=en_US.
...
Cheers,
Rodrigo Ventura
Institute for Systems and Robotics
(www.isr.ist.utl.pt)
Instituto Superior Técnico
Lisbon, Portugal
tar (GNU tar) 1.16.1
Did you upgraded something on the system?
Yeah. Some packages from slackware and amanda itself.
Thank you all for the provided help,
Cheers,
Rodrigo Ventura
Institute for Systems and Robotics
(www.isr.ist.utl.pt)
Instituto Superior Técnico
Lisbon, Portugal
Hello,
I'm getting sporadically errors like this:
FAILURE AND STRANGE DUMP SUMMARY:
omni/ lev 1 FAILED [dump (30447) /usr/bin/tar
returned 2]
and I don't have a clue on what's going on. I grepped /tmp/amanda and
found no reference to this. Any clues?
C
/dev/nst0
$ amtape ISR current
changer: got exit: 0 str: 3 6 1
changer_query: changer return was 6 1
changer_query: searchable = 0
amtape: scanning current slot in tape-changer rack:
changer: got exit: 0 str: 3 /dev/nst0
slot 3: date 20060806 label ISR003
Any clues?
Cheers,
Rodrigo
--
Rodrigo Ventura
ISR/IST
On Friday 28 July 2006 15:42, Jon LaBadie wrote:
> No it is not "wrong". "some ... may" also includes zero dumps are left.
You are right, I overlooked the writting...
> I'd guess your DLE "omni:/home/mn" was dumping direct to tape,
> bypassing the holding disk.
Right, but I can't figure how why
tape?
--
Now, the tape entry on amanda.conf contains:
--
define tapetype HP-DAT-72x6-nc {
comment "HP autoloader DAT 72x6 (compression off)"
# data provided by Rodrigo Ventura <[EMAIL PROT
On Friday 21 July 2006 17:18, Jon LaBadie wrote:
> I hesitate to say they are better. But perhaps more popular
> are the scripts based on using the mtx command, either chg-mtx
> or more commonly the newer chg-zd-mtx.
Thanks. I switched to chg-zd-mtx. Doing a couple of amtape tests, however the
o
On Friday 21 July 2006 16:29, Jon LaBadie wrote:
> From the low volume of comments about chg-scsi on this list
> it seems few sites are using that changer. Thus our unfamiliarity
> with its config and log files. Sorry.
>
> Of course, as few people post to the list except with problems,
> maybe th
On Friday 21 July 2006 15:58, Gene Heskett wrote:
> I'm just as puzzled, I now have the latest 2.5.1p1-20060719 installed
> and I have no such file either.
>
> Would the OP please supply the full path to this file?
The filename is tapestatus and is created in the config directory (e.g., where
ama
More details; the head of the tapestatus:
$ head -n 30 tapestatus
20060720 ISR003
Write Error Counters Page
Total Errors Corrected = 0
Total Times E. Processed = 0
Total Bytes Processed = 0
Total Unrecoverable Errors = 0
Read Error Counter
Today the server disk went out of space because the tapestatus file grew over
several GiGs. It seems to be related with upgrading amanda to 2.5.0p2. The
contents are lines like "tape status = ...". Any clues?
Cheers,
Rodrigo
--
*** Rodrigo Martins de Matos Ventura <[EMAIL PROTECTED]>
*** W
Hi. I'm forwarding this mail that ought to go to amanda-users in the first
place.
-- Forwarded Message --
Subject: Re: upgrading amanda to 2.5.0
Date: Thursday 20 July 2006 16:27
From: Rodrigo Ventura <[EMAIL PROTECTED]>
To: Jean-Louis Martineau <[EMAIL P
Hi all,
regarding upgrading amanda to 2.5.0 (from 2.4.4) I have a couple of questions:
1- is there any upgrade issue between 2.4.4 and 2.5.0? Since there is an
UPGRADE file, can I assume there is none?
2- I'm a bit confused about the patch levels; the amanda web page announces
2.5.0-p1 as the
Hello,
I have a simple question: does amanda support dumping/restoring over IPv6?
I have a server behind a NATbox that I need to backup periodically. IPv6 would
be the neat solution. Otherwise, are there IPv4 solutions?
I read somewhere about iptables having a module for amanda. How does it w
Hello again,
I'm trying to make sure there is no shoe-shinning effect on my tapes. Examining
amdump report I get:
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s
M
Hi all,
Occasionaly I get the following errors after amdump:
*** A TAPE ERROR OCCURRED: [label ISR006 or new tape not found in rack].
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: ISR006.
which is simply not true, si
I noticed that my tape drive (HP DAT autoloader) requires a "mt
compression 0" prior to tape access. It seems that even after reading
the tape label in a non-compressed tape, when it writes, it uses
hardware compression. I noticed it comparing the tapeer data transfer
rates in several amdumps afte
I have the same problem over here. I'm well aware that I could never
restore, at least easly, a windows system partition using backups
based on samba, but at least better than having no backup at all.
By the way, are there off-the-shelf howto to guide setting up a
reliable backup of a NT server u
My 5 cent to this discussion:
Depending on the level of abstraction, the client and server names can
be ascribed in reverse order. It is true that it is the machine with
the tape and running amdump that initiates the transactions with the
amandad's spread across the netword, and that the latter p
This is off-topic. I haven't been using amverify, but I guess it is a
good idea, if one wannt to be sure the backup was properly
performed. So I liked the script in the original post very
interesting:
Yan> /usr/local/bin/vxaTool /dev/st0 -C 1 //turns on compression
Yan> /usr/sbin/amd
Why don't you split your disk among several directories (aka DLE,
disklist entry). I guess that's common practice in amanda, and indeed
a powerful mechanism. I'm using 36GB tapes for a pool of several
hundred GB across a server farm. I split the pool into a bunch of DLE,
dividing among filesystems
This just happened this night amdump:
(/tmp/amanda/sendbackup.20051128003448.debug)
[...]
sendbackup: time 3.133: index created successfully
sendbackup: time 3.134: error [/bin/tar got signal 11]
sendbackup: time 3.134: pid 13222 finish time Mon Nov 28 00:34:51 2005
Signal 11 is SIGSEGV. My tar
> "Inaki" == Inaki Sanchez <[EMAIL PROTECTED]> writes:
Inaki> No problem doing amlabel ISR006 right now, amanda will let
Inaki> you do the backup in ISR005 or ISR006, it is up to you.
But how can I choose which?? Amanda handles the autoloader
automatically, I have no control on what t
last one was done circa 2003, so it's a bit old... (I
guess I wasn't using amanda back then yet...)
Cheers,
Rodrigo Ventura
--
*** Rodrigo Martins de Matos Ventura <[EMAIL PROTECTED]>
*** Web page: http://www.isr.ist.utl.pt/~yoda
*** Teaching Assistant and PhD Student
. Mails sharing the same message-id are hardlinked. The problem
happens whenever I recover a single mailbox, containing mails
hardlinked to other mailboxes.
Thanks,
Rodrigo Ventura
--
*** Rodrigo Martins de Matos Ventura <[EMAIL PROTECTED]>
*** Web page: http://www.isr.ist.utl.pt
rresponding to the compression switched on and off:
define tapetype HP-DAT-72x6-c {
comment "HP autoloader DAT 72x6 (compression on)"
# data provided by Rodrigo Ventura <[EMAIL PROTECTED]>
length 31255 mby
But are all tapes operations non-blocking? The most efficient way
seems to be to perform all operations in blocking mode, meaning that
the next operation is performed after finnishing the current one.
Either (1) amtape does everything non-blocking, meaning that the sleep
time must be an upper bou
What exactlty means the "sleep" configuration parameter in the
changer.conf file? I notice some lag in the tape commands (it seems
the tape is doing nothing, and the amtape is just sleeping...), so
maybe the default value of 90 is too conservative for my system. How
can I safely tune it?
And BTW,
Hi. There are a couple of parameters on amanda.conf that I can't
figure out exactly their meaning, even after reading the man pages a
thousand times:
- dumpcycle, in days
- runspercycle, in number of amdumps
- tapecycle, in number of tapes
tapecycle is the total number of tapes; only these tapes
Hum, I'm a bit confused here... I read somewhere that it was not
trivial to disable hardware compression. I have an autoloader with a
DAT 72 drive, connected to a linux server. The command mt
datcompression 0 Compression off does not seem to work.
I read that the hardware compression flag was wri
That's an interesting configuration. I think I'll adopt something like
that here. The only problem is that someone (i.e., me) will have to
change the magazine at the right times. Hum, since each magazine has 6
slots, can't use one per day, unless I skip a day, maybe sunday. I
also like the swappin
Another quick question: hitting end-of-tape error does not mean that
the tape length setting in tapetype is wrong?
I have:
define tapetype HP-DAT-72x6 {
comment "HP autoloader DAT 72x6"
# data provided by Rodrigo Ventura <[EMAIL PROTECTED]>
length 31255 mbytes
Oops, I just read on amanda.conf:
autoflush no #
# if autoflush is set to yes, then amdump will schedule all dump on
# holding disks to be flush to tape during the run.
I misunderstood your mails, sorry, I'll set this to "yes" and wait for
the next normal dump. Tomorrow let's see the results.
C
Thank you all for the valuable tips (might be a good idea to put some
of those Q&A in a FAQ).
> "Alexander" == Alexander Jolk <[EMAIL PROTECTED]> writes:
Alexander> Since you seem to have 30GB tapes, splitting up those
Alexander> dumps above 3GB might be a good idea anyway, of course.
tape ISR005" and
"The next tape Amanda expects to use is: ISR001" which seems ok (I
only have ISR001-ISR005). So can I conclude that amanda *only* used
one tape? The dumps that did not fit are on holding disk?
Thank you,
Cheers,
Rodrigo Ventura
--
*** Rodrigo Martins de
Hi.
Meanwhile I sent a mail to amanda-users re-reporting the problem. Here
goes the data relative to that: I have 14 filesystems to dump on
localhost, so that total timeout should be 300*14=4200 seconds, right?
Doing a grep on sensize log, I get:
$ grep "estimate time" sendsize.20050904195400.de
but these
timeouts are not visible in the logs.
What do you suggest me to do next to trackdown the problem?
Cheers,
Rodrigo Ventura
--
*** Rodrigo Martins de Matos Ventura <[EMAIL PROTECTED]>
*** Web page: http://www.isr.ist.utl.pt/~yoda
*** Teaching Assistant and PhD Student at IS
It happened again. This time the timeout was on localhost! There is no
firewall involved, both in this case as well as in the last (mail from
July 12th).
FAILURE AND STRANGE DUMP SUMMARY:
omni //new/E$ lev 0 FAILED [Estimate timeout from omni]
omni //new/C$ lev 0 FAILED [Estimate
Hello. My backup system has been running smoothly for the last few
months. However today I got this FAILED dumps:
FAILURE AND STRANGE DUMP SUMMARY:
gtisr /usr lev 0 FAILED [Estimate timeout from gtisr]
gtisr /boot lev 0 FAILED [Estimate timeout from gtisr]
gtisr / lev 0 FAIL
Hi. I'm using a HP DAT 72x6, which has 6 slots. The unit came with 5
DAT's 36/72 GB and a clean tape, all inserted in the cartidge.
What is the common procedure with regard with cleaning tapes? I
suppose I'll have to check the unit regularly to see whether it needs
cleaning. Is there anyone using
The problem was that gtisr is a firewall (iptables), and I had to open
ports >1024 with source on amanda server. An alternative was to use
the amanda conntrack module, but I think it's simpler to open those
ports, provided that the source IP (and the physical iface) restrict
its use to the amanda
I'm adding a remote (gtisr) DLE to my disklist. The amcheck -c say
it's all ok, but when I run amdump it fails:
FAILURE AND STRANGE DUMP SUMMARY:
gtisr /boot lev 0 FAILED 20050517[could not connect to gtisr]
gtisr /usr lev 0 FAILED 20050517[could not connect to gtisr]
omni /
My amdump has just finished, and the report looks good:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
omni /
The amdump I'm doing right now is looking good: the sendsize.*.include
files for the var/spool/imap/user is non-zero (and its contents make
sense). I guess the problem was that the directory var/spool/imap/user
was not readable by amanda. Although gnutar is performed as root, and
therefore there a
> "Jon" == Jon LaBadie <[EMAIL PROTECTED]> writes:
Jon> Is your runtar (and several other amanda programs) set-uid'ed
Jon> root?
-rwsr-x---1 root backup 50972 Feb 19 16:57 runtar
among others. It seems amanda is properly installed, as far as
setuid's are concerned.
Alexander Jolk wrote:
Ahm, sorry, I don't quite follow you there. Your sendbackup.* files are
empty, zero bytes? That shouldn't be the case already. (Don't get
caught by the fact that they are readable only to your amanda user, and
root!) And which files are the include files? Could you ela
Alexander Jolk wrote:
Once again, your syntax seems right to all of us, but nobody really
seems to be actively using `include' right now. I know for certain that
using `exclude' works, for example.
I see. My problem is that I have a /home full of users (34G used) and a
/var/spool/imap/users ful
The man page has this suspicious paragraph:
diskdevice
Default: same as diskname. The name of the disk device to be
backed up. It may be a
full device name, a device name without the /dev/ prefix, e.g.
sd0a, or a mount point
such as /usr.
They
> "Alexander" == Alexander Jolk <[EMAIL PROTECTED]> writes:
Alexander> I'm pretty sure there's an error somewhere in your
Alexander> disklist config since your index files are empty. I
Alexander> don't remember whether you showed us already your
Alexander> relevant /tmp/amanda
> "Jon" == Jon LaBadie <[EMAIL PROTECTED]> writes:
Jon> Does 'amadmin disklist omni /var/spool/... ' show
Jon> indexing turned on?
Yes.
Jon> Are there index files for those DLE's under your index dir?
Yes, all gzipped; decompress to an empty file.
Jon> Was there ever a suc
> "Jon" == Jon LaBadie <[EMAIL PROTECTED]> writes:
Jon> These are level 1 dumps. Maybe no changes? Did you get the
Jon> same results on the last level 0? If I recall, these are
Jon> mail dirs, is there stuff there?
Last dump summary:
DUMPER
> "Jon" == Jon LaBadie <[EMAIL PROTECTED]> writes:
Jon> So far your DLE's seem ok to me. The one part I question is
Jon> "global". What is your global definition? Is it even
Jon> specifying GNUTAR as the dump program?
My global is:
define dumptype global {
comment "Global
Thank you for the answers.
I have one more question/problem: I have several partitions that are
not being dumped. The device/directory/include specifications in DLE
is not yet very clear to me. I have a root partition (/) where the OS
is installed, as well as IMAP accounts at /var/spool/imap/user
ata provided by Rodrigo Ventura <[EMAIL PROTECTED]>
length 31255 mbytes
filemark 527 kbytes
speed 1580 kps
}
How can I setup amanda to be less conservative, i.e. assume it can
record a little bit more than 31GB per tape? Is there a parameter
where I can specify the assumed c
56 matches
Mail list logo
