Maybe, but I have another machine with the exact same inetadm output
and that one works fine so it's not the cause of this specific problem
Abilio
On May 19, 2009, at 5:31 AM, Frank Smith wrote:
Abilio Carvalho wrote:
Anyone? I'm kinda lost at a problem that seems so basic, and I could
the prefix with no argument is how the config.log interprets
prefix='', which I did to install amanda in the default directories
rather than inside a specific subdir. Again, like frank's attempt I
have another machine with the same config options and that one works
fine.
Cheers
Abilio
Hi,
does any has experiences with amanda and sun(storagetek) sl24 or better
sl48 with 2 lto4 tape drives?
the tape drives are normal lto4 tape drive from HP.
Or can I simply take the configuration from the Arcvault 48 - HP LTO4-800
tape?
best regards,
Uwe
2009/5/18 Paul Bijnens
Do you think I have to split as much as possible the big diskset into
multiple little diskset for amanda to be able to restore as fast as
possible without having to scan a complete librairy ?
Franck
Dustin J. Mitchell a écrit :
On Mon, May 18, 2009 at 11:41 AM, Franck GANACHAUD
Done further tests, still no explanation.
Amandahosts on the client is:
BACKUPHOST.bbp.ch amandabackup amdump
BACKUPHOST amandabackup amdump
inetadm -l svc:/network/amanda/tcp on the client returns:
SCOPENAME=VALUE
name=amanda
endpoint_type=stream
proto=tcp
Abilio Carvalho wrote:
the log directory on the client only has the following:
r...@backupclient:/tmp/amanda/amandad# cat amandad.20090519111556.debug
1242724556.328466: amandad: pid 18933 ruid 0 euid 0 version 2.6.1:
start at Tue May 19 11:15:56 2009
ruid 0 euid 0
That's root user
Do you
Yes, the user amandabackup exists, as you can see it owns all the
amanda-related files. I've checked nsswitch.conf and it's checking
files before nisplus on passwd, so that's not it.
I'm unsure what you mean by inetd log, but from what I've searched
it's enabling tcp_trace and tcp_wrappers
follow-up:
I was wrong, it wasn't syslog, it was messages. There I now see a
couple lines like:
May 19 13:58:23 galadhrim inetd[24015]: [ID 317013 daemon.notice]
amanda[27116] from 172.22.0.23 44223
May 19 13:58:31 galadhrim inetd[24015]: [ID 317013 daemon.notice]
amanda[27214] from
I have defined an exclude list in a dumptype using
exclude list /etc/amanda/DailySet1/exclude-list
with entries like
$ cat /etc/amanda/DailySet1/exclude-list
./dumps
./opt/dell/srvadmin/shared/.ipc
I have a couple of questions about the entries. Based on the
documentation I've read
m == martin...@zmanda.com writes:
m The '.' is required, all excludes are relative to the dle you back up.
m Brandon Metcalf wrote:
m I have defined an exclude list in a dumptype using
m
mexclude list /etc/amanda/DailySet1/exclude-list
m
m with entries like
m
m$ cat
owner is amandabackup:disk
I can log in to the account just fine, I don't think any more logging
is possible though I'll check. I checked the manifest for the service
and it confirms that it is SUPPOSED to start as amandabackup.
If I do what you say, and log into amandabackup and run that, I
Brandon Metcalf wrote:
m First, am I correct in thinking the '.' are required? If so, how can
m Amanda be told to exclude, for example, /dumps on sda1 but still
m backup /dumps on sda2 other than defining different dumps types with
m their own exclude list?
m
m You can't.
Seems
The '.' is required, all excludes are relative to the dle you back up.
Brandon Metcalf wrote:
I have defined an exclude list in a dumptype using
exclude list /etc/amanda/DailySet1/exclude-list
with entries like
$ cat /etc/amanda/DailySet1/exclude-list
./dumps
m == martin...@zmanda.com writes:
m Brandon Metcalf wrote:
m m First, am I correct in thinking the '.' are required? If so, how
can
m m Amanda be told to exclude, for example, /dumps on sda1 but still
m m backup /dumps on sda2 other than defining different dumps types with
m m
Brandon Metcalf wrote:
m == martin...@zmanda.com writes:
m Brandon Metcalf wrote:
m m First, am I correct in thinking the '.' are required? If so, how
can
m m Amanda be told to exclude, for example, /dumps on sda1 but still
m m backup /dumps on sda2 other than defining different
On 2009-05-19 15:35, Brandon Metcalf wrote:
m == martin...@zmanda.com writes:
m
m
m Seems like a nice feature would be to allow the DLE to be specified in
m the exclude list.
m
m The 'exclude list' can be a relative path to the dle.
So, you're saying I can specify one dumptype
On Tue, May 19, 2009 at 3:36 AM, Franck GANACHAUD
franck.ganach...@altran.com wrote:
Do you think I have to split as much as possible the big diskset into
multiple little diskset for amanda to be able to restore as fast as possible
without having to scan a complete librairy ?
Yes, that's the
Splitting up your DLE is what I would recommend for a variety of
reasons. I'm working with someone now who is configuring the backup of a
3TB raid array to LTO4. Initially they were saying that it needed to be
one large DLE. Finally, they agreed to break it up into a bunch of
DLE's. They now
I use a lot of Sun equipment, but I haven't splurged on Sun tape drives
(they haven't come up on the education deals for one thing). However, as
you say, the tape drive itself is a standard lto4 from HP. The old
internal DAT drives on some of my Sun servers are also standard HP.
You could use
P == paul.bijn...@xplanation.com writes:
P On 2009-05-19 15:35, Brandon Metcalf wrote:
P m == martin...@zmanda.com writes:
P
P m
P m
P m Seems like a nice feature would be to allow the DLE to be specified
in
P m the exclude list.
P m
P
P m The 'exclude list' can be
I didn't specify these.
Original diskset is 250Gb to save to DLT4 35GB tapes using a 8 slots
autoloader.
I'm going to split this diskset going down one level in the filesystem
which will give me a little less than 150 diskset.
I just have to think about a mechanism to upgrade the diskset list
On 2009-05-19 16:52, Franck GANACHAUD wrote:
I didn't specify these.
Original diskset is 250Gb to save to DLT4 35GB tapes using a 8 slots
autoloader.
I'm going to split this diskset going down one level in the filesystem
which will give me a little less than 150 diskset.
I just have to think
I have Amanda 2.6.1p1. Darin Perusich mentioned a patch
FSF_AFTER_FILEMARK that needs to be added for Solaris hosts.
Where or how do I get this patch or a patched source.
Thanks
Robert
_
Robert P. McGraw, Jr.
Manager,
On Tue, May 19, 2009 at 12:33 PM, McGraw, Robert P rmcg...@purdue.edu wrote:
I have Amanda 2.6.1p1. Darin Perusich mentioned a patch
FSF_AFTER_FILEMARK that needs to be added for Solaris hosts.
Where or how do I get this patch or a patched source.
On Tuesday 19 May 2009, McGraw, Robert P wrote:
FSF_AFTER_FILEMARK
According to the ChangeLog for the 2.6.2 snapshot I'm running, that was added
on 4-21. Whether its in 2.6.1p1 I do not know. For space reasons I rarely
keep more than about 10 of the previous snapshots here.
Did you get your
Hi,
Is there any gross imcompatability that would prevent a 2.6.1p1 client
from being backed up by a 2.4.3b3 server?
I've got it to the point where they are at least talking with each
other, using auth bsd.
amcheck -c is happy.
estimates worked ok.
But amstatus is showing this:
client-a:/a
I try to keep them compatible, but I don't test with release before 2.4.5.
index_server is used only by amrecover.
Can you post the amandad.*.debug file from the client?
Jean-Louis
Mitch Collinsworth wrote:
Hi,
Is there any gross imcompatability that would prevent a 2.6.1p1 client
from
At 3:01 PM +0200 5/19/09, Abilio Carvalho wrote:
owner is amandabackup:disk
I can log in to the account just fine, I don't think any more logging
is possible though I'll check. I checked the manifest for the service
and it confirms that it is SUPPOSED to start as amandabackup.
If I do what
On Tue, 19 May 2009, Jean-Louis Martineau wrote:
I try to keep them compatible, but I don't test with release before 2.4.5.
index_server is used only by amrecover.
Can you post the amandad.*.debug file from the client?
Jean-Louis
Yup, here's a sample below.
-Mitch
1242745188.258722:
Thanks those were all things I'd tried already. I've managed to fix it
though. For some reason, completely purging the service from
everywhere and recreating it from the exact same manifest did the
trick, where before that I'd tried changing the user parameter on the
service without
amanda client 2.6.1p1 is compatible with server 2.4.3b4 and up. But it
is not with 2.4.3b3 and previous.
Try the attached patch.
Jean-Louis
Mitch Collinsworth wrote:
Hi,
Is there any gross imcompatability that would prevent a 2.6.1p1 client
from being backed up by a 2.4.3b3 server?
I've
On Tuesday 19 May 2009, Abilio Carvalho wrote:
the prefix with no argument is how the config.log interprets
prefix='', which I did to install amanda in the default directories
rather than inside a specific subdir. Again, like frank's attempt I
have another machine with the same config options and
32 matches
Mail list logo
