After I have upgraded amanda in server side to 2.4.5p1-2 version it
stoped backup.
In log file of amdump I see:
dumper: FATAL must be run setuid root to communicate correctly
Which permission should be installed?
In server side permissions is:
-rwxr-xr--1 root disk30628 Dec 29 21:00 d
Leonid Shulov wrote:
After I have upgraded amanda in server side to 2.4.5p1-2 version it
stoped backup.
How did you upgrade?
If compiling from source, you must "make install" as root.
If not, the install process cannot set the permissions correct,
and Amanda will not work.
If it were rpms, whi
1. I upgraded amanda from amanda from Debian package
2. I changed prmission to:
/usr/lib/amanda/# chmod u+s dumper killpgrp planner rundump runtar
and now its work.
Thanks for help
Leonid
Paul Bijnens wrote:
Leonid Shulov wrote:
After I have upgraded amanda in server side to 2.4.5p1-2 v
sorry I should have mentioned, I'm using Solaris 9. My etimeout is set to -8000 (which has been ok for months) but i still think its way to much. I didnt change it as this is the error i'm getting now: FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR Estimate timeout from host01 host01
Dear list,
I've installed an amanda server and client on an alpha machine running
NetBSD in these versions:
# pkg_info -a | grep amanda
amanda-common-2.4.4p4nb2 Common libraries and binaries for Amanda
amanda-server-2.4.4p4nb2 Server part of Amanda, a network backup system
amanda-client-2.4.4p
On Monday 30 January 2006 03:08, Leonid Shulov wrote:
>After I have upgraded amanda in server side to 2.4.5p1-2 version it
>stoped backup.
>In log file of amdump I see:
>
> dumper: FATAL must be run setuid root to communicate correctly
>
What means did you use to install it, rpms, debs, tarballs b
Torsten Harenberg wrote:
Dear list,
I've installed an amanda server and client on an alpha machine running
NetBSD in these versions:
# pkg_info -a | grep amanda
amanda-common-2.4.4p4nb2 Common libraries and binaries for Amanda
amanda-server-2.4.4p4nb2 Server part of Amanda, a network backup s
Paul Bijnens wrote:
Amanda uses /etc/(v)fstab to map devices to directories and vice versa.
Is there some mapping there that results in /home being mapped to /afs?
Hi Paul,
thanks a lot for your quick reply.
Okay:
our fstab looks like this:
/dev/sd0a / ffs rw 1 1
/dev/wd0a /usr ffs rw
Has anyone migrated from BRU to Amanda? I did google, but no significant hits.
We are using a Quantum SDLT320 tape drive with autoloader with 8 slots.
slots 1 + 2 backup job 1 incremental daily / differential weekly
slots 3 + 4 backup job 2 incremental daily / differential weekly
slots 5 + 6 ba
Hi List
I have beening looking into a external storage capacity problem whereby
my Organisation have three Linux Suse 9 Enterprise servers with DAT tap
drives that use 20GB native thus the server have a 80GB hard drive
capacity So anyway I am about to push for a 80GB DLT drive with a
Dedicated tow
On Mon, 2006-01-30 at 18:05 +, Chuck Amadi Systems Administrator
wrote:
> I was wandering would it be possible to have the 80GB File/Document
> server backup up to DLT cartridges but on the DLE (disk list entries)
> have the two other servers which are also 80GB hard drives backuped to
> the n
On Mon, 30 Jan 2006 at 11:48am, Salvatore Enrico Indiogine wrote
Has anyone migrated from BRU to Amanda? I did google, but no significant hits.
We are using a Quantum SDLT320 tape drive with autoloader with 8 slots.
slots 1 + 2 backup job 1 incremental daily / differential weekly
slots 3 + 4
On Mon, 30 Jan 2006 at 6:05pm, Chuck Amadi Systems Administrator wrote
I have beening looking into a external storage capacity problem whereby
my Organisation have three Linux Suse 9 Enterprise servers with DAT tap
drives that use 20GB native thus the server have a 80GB hard drive
capacity So an
Hi there,
BRU and other backup vendors use proprietary tape format and there are no
utilities for tape format conversion. For migration from one backup solution
(BU1) to another (BU2) there are two options:
- Keep your BU1 in place for recovers only until retention policy for all
old data expires.
2006/1/30, Dmitri Joukovski <[EMAIL PROTECTED]>:
>
> BTW, why do you migrate from BRU in the first place?
1. We have the strange SCSI error: "Medium destination full" I have
a feeling that it is related to the fact that the change from one tape
to the other of the same b/u pool is not really bug
hi,
i have been experimenting with 2.4.5 with the split/span patch.
it would be nice to be able to simply upgrade from our current
2.4.2p1 to 2.4.5 + split/span 7.2, using the same curinfo database.
is it the case that the split/span changes use exactly the same
database format, or are they d
Hi all,
Environment:
- server
- Debian Sarge, amanda-server 2.4.4p3-3;
- client
- Debian Sarge, amanda-client 2.4.4p3-3;
- Debian Woody, amanda-client 2.4.4p3-3 (I made it myself
backport).
The clients' full backup is succesful with the following config
(typicall
Salvatore Enrico Indiogine schrieb:
2006/1/30, Dmitri Joukovski <[EMAIL PROTECTED]>:
BTW, why do you migrate from BRU in the first place?
1. We have the strange SCSI error: "Medium destination full" I have
a feeling that it is related to the fact that the change from one tape
to the other of
Gene Heskett schrieb:
On Monday 30 January 2006 03:08, Leonid Shulov wrote:
After I have upgraded amanda in server side to 2.4.5p1-2 version it
stoped backup.
In log file of amdump I see:
dumper: FATAL must be run setuid root to communicate correctly
What means did you use to install it, rpm
On Mon, Jan 30, 2006 at 10:00:45PM +0100, Kosa Attila wrote:
> Hi all,
>
> Environment:
> - server
> - Debian Sarge, amanda-server 2.4.4p3-3;
> - client
> - Debian Sarge, amanda-client 2.4.4p3-3;
> - Debian Woody, amanda-client 2.4.4p3-3 (I made it myself
> backport).
>
Stefan G. Weichinger wrote:
To all users of AMANDA on Debian:
Are these packages problematic in general?
I've had very few problems with them. The only complaints I've had are
with segfaults on a couple of the admin utilities. I've had an offer by
one of the developers to help resolve those
Stefan G. Weichinger wrote:
>
> To all users of AMANDA on Debian:
> Are these packages problematic in general?
>
> Thanks, Stefan
>
I run the Debian Sarge packages of Amanda (2.4.4p3-3) without any
problems (other than I don't particularly care for the default
locations it uses, but that's proba
Jon LaBadie wrote:
> On Mon, Jan 30, 2006 at 10:00:45PM +0100, Kosa Attila wrote:
>> Hi all,
>>
>> Environment:
>> - server
>> - Debian Sarge, amanda-server 2.4.4p3-3;
>> - client
>> - Debian Sarge, amanda-client 2.4.4p3-3;
>> - Debian Woody, amanda-client 2.4.4p3-3 (I made it myself
Hi,
i have a Problem with amanda.
I try to backup 1 Directory from a Server. The Directoy has a size of round
about 80 GB.
Every Morning i get the status mail:
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape DailySet166.
The next tape Amanda expects to use is: a new tape.
The
24 matches
Mail list logo
