Iulian Topliceanu wrote:
How do I use the --numeric-owner flag which makes tar not lookup uid/gid
numbers with amanda?
What does amanda use while estimating a volume? I have /var/spool/mail
55 GB big (EXT3) with 1944656 inodes used and it lasts an eternity for
amanda to do the volume
Hi Gene,
Gene Heskett wrote:
First, the normal amanda install is to configure and make it as an
unpriviledged user, like 'amanda'. This user 'amanda' should be made
a member of the group 'disk' or some similar high ranking operator.
When that make is done, then become root to do the install,
Hi Paul,
Paul Bijnens wrote:
I believe, LVM2, or lvm special files has nothing to do with using
gnutar to backup. (The other way around: using dump with a non
accessible lvm-special file would be a problem.)
And gnutar actually *does* run with root-priviledges, at least, if
installed correctly
Hans van Zijst wrote:
I checked runtar and
it indeed runs as root. Well, at least it's got the suid bit set. How do
I configure Amanda to use runtar? The configuration has the option
--with-rundump but I couldn't find anything about runtar. I checked
amanda.conf, but no runtar either...
By
On Thu, 20 Jan 2005 at 11:39pm, David Newman wrote
An amanda server on Box A backs up partitions from amanda clients on Box A
and Box B. The dumptype is gnutar for both boxes. Backups on Box B work
fine. Backups on Box A fail with an all estimate failed error.
Both boxes run GNU tar
Hmm, that messages wasn't supposed to be sent yet...
Hans van Zijst wrote:
I did, months ago. So it should be using the setuid runtar binary, but
still it can't read stuff. Maybe the problem arises in an earlier stage,
before the actual backup is done. When I run amcheck, it complains it
can't
Hello,
does anybody have a clue what's going on here at my system:
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -f... -
sendbackup: info end
? sendbackup: index tee cannot write [Connection timed out]
? index returned 1
sendbackup: error [/bin/tar got signal
Hans van Zijst wrote:
Hmm, that messages wasn't supposed to be sent yet...
Hans van Zijst wrote:
I did, months ago. So it should be using the setuid runtar binary, but
still it can't read stuff. Maybe the problem arises in an earlier
stage, before the actual backup is done. When I run amcheck,
[EMAIL PROTECTED] wrote:
does anybody have a clue what's going on here at my system:
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -f... -
sendbackup: info end
? sendbackup: index tee cannot write [Connection timed out]
? index returned 1
sendbackup: error
On Friday 21 January 2005 03:55, Hans van Zijst wrote:
Hi Gene,
Gene Heskett wrote:
First, the normal amanda install is to configure and make it as an
unpriviledged user, like 'amanda'. This user 'amanda' should be
made a member of the group 'disk' or some similar high ranking
operator.
On Friday 21 January 2005 08:23, [EMAIL PROTECTED] wrote:
Hello,
does anybody have a clue what's going on here at my system:
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/tar -f... -
sendbackup: info end
? sendbackup: index tee cannot write [Connection timed out]
?
Amanda 2.4.2p2
Solaris 8
SDLT 220
We recently make a couple of changes to our amanda conf (well, one
of our amanda server configs).
1) changed the config name
2) changed from SW to HW compression, increased tape length
in config file by 50 %, we where seeing nearly that in SW
compression.
Stefan,
On Wed, Jan 19, 2005 at 10:48:54PM +0100, Stefan G. Weichinger wrote:
BC Major imporvement though still below the acceptable threshold.
BC Definitely looking like it was never an amanda issue, this looks to
BC be an underlying architecture problem.
I hope that you spot the issue
On Fri, Jan 21, 2005 at 11:30:02AM -0500, Brian Cuttler wrote:
Amanda 2.4.2p2
Solaris 8
SDLT 220
We recently make a couple of changes to our amanda conf (well, one
of our amanda server configs).
1) changed the config name
2) changed from SW to HW compression, increased tape length
...
On Friday 21 January 2005 11:37, Brian Cuttler wrote:
Stefan,
On Wed, Jan 19, 2005 at 10:48:54PM +0100, Stefan G. Weichinger wrote:
BC Major imporvement though still below the acceptable threshold.
BC Definitely looking like it was never an amanda issue, this
looks to BC be an underlying
On Fri, Jan 21, 2005 at 11:30:02AM -0500, Brian Cuttler wrote:
4) We did also change the crontab for bin to force level 0 dumps on
Fridays. This change reflecting the changes made when we renamed
notes_dlt to wcnotes.
Are you perchance seeing these level-2 dumps disproportionally
often
On Fri, Jan 21, 2005 at 11:08:57AM -0500, Gene Heskett wrote:
? sendbackup: index tee cannot write [Connection timed out]
Try increasing the etimeout value in your amanda.conf
dtimeout, no? (I have no idea whether that'd help, but it's more
likely to than is etimeout)
--
| | /\
|-_|/
Eric,
I think Jon LaBadie hit it when he suggested that amanda wasn't
examining the threshold as data to tape rather than data to dump
and the change from SW to HW compression was bringing us over this
limit.
Since this is Lotus Notes and the databases are little more than
large text files, any
I tried to compile and configure Amanda 2.4.4 for the first
time on Compaq Tru64 version 5.1b but Im having problems configuring the
changer (Compaq StorageWorks MSL 5026 Library).
I have included outputs of Amanda.conf, chg-multi.conf, disklist,
and tapelist (empty file). I ran HP
Scheuerman, James wrote:
I tried to compile and configure Amanda 2.4.4 for the first time on
Compaq Tru64 version 5.1b but Im having problems configuring the
changer (Compaq StorageWorks MSL 5026 Library).
I have included outputs of Amanda.conf, chg-multi.conf, disklist, and
tapelist
On Fri, Jan 21, 2005 at 03:29:16PM -0500, Brian Cuttler wrote:
I think Jon LaBadie hit it
Cool. I was speaking in ignorance of what the data looked like.
There is a word that I like to use for this type of design. Hidious
Yup, that's a technical term :-)
So a one block file would
have a
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger wrote:
- configure and make as $AMANDAUSER
I don't believe this is necessary. One should avoid building
Amanda as root, but that's not because it'll cause problems for
Amanda; it's for the same reason one should avoid building
--On Friday, January 21, 2005 18:18:52 -0500 Eric Siegerman [EMAIL PROTECTED]
wrote:
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger wrote:
- configure and make as $AMANDAUSER
I don't believe this is necessary. One should avoid building
Amanda as root, but that's not
On Fri, Jan 21, 2005 at 06:15:28PM -0600, Frank Smith wrote:
--On Friday, January 21, 2005 18:18:52 -0500 Eric Siegerman [EMAIL
PROTECTED] wrote:
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger wrote:
- configure and make as $AMANDAUSER
I don't believe this is
On Friday 21 January 2005 18:18, Eric Siegerman wrote:
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger wrote:
- configure and make as $AMANDAUSER
I don't believe this is necessary. One should avoid building
Amanda as root, but that's not because it'll cause problems for
Amanda;
On Friday 21 January 2005 19:15, Frank Smith wrote:
--On Friday, January 21, 2005 18:18:52 -0500 Eric Siegerman
[EMAIL PROTECTED] wrote:
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger
wrote:
- configure and make as $AMANDAUSER
I don't believe this is necessary. One should
26 matches
Mail list logo
