On Tue, Aug 24, 2021 at 07:06:44PM +, Debra S Baddorf wrote:
Wasn’t there, at some point, a parameter in addition to the chunksize param?
I’m using chunking, but yes, the whole set of chunks is always re-taped.
But I’m using real tapes so that’s what I want.
Wasn’t there another
Wasn’t there, at some point, a parameter in addition to the chunksize param?
I’m using chunking, but yes, the whole set of chunks is always re-taped.
But I’m using real tapes so that’s what I want.
Wasn’t there another parameter, besides chunking onto the holding disk,
which actually allowed
On Mon, Aug 23, 2021 at 06:30:24PM +0100, Jose M Calhariz wrote:
Hi,
What you describe is what I see when I do not use chunks. The last
backup to the last vtape will be transfered again to vtape on next
amdump or amflush.
Kind regards
Jose M Calhariz
Yes, that is the historically desired
Hi,
What you describe is what I see when I do not use chunks. The last
backup to the last vtape will be transfered again to vtape on next
amdump or amflush.
Kind regards
Jose M Calhariz
On Sun, Aug 22, 2021 at 02:40:52PM -0400, Jon LaBadie wrote:
> I have one large DLE that gets broken into
I have one large DLE that gets broken into about
45 chunks for taping. My vtapes hold 20 of these
chunks and I allow up to 3 tapes to be used nightly.
Two evening back another large DLE was in the same
dump so only about 30 of the 45 chunks fit on the
three tapes.
Today I ran amflush thinking
Hi,
I just upload a new package of amanda 3.5.1-8 to Debian. The NEWS is:
* That I have updated the README.Debian with instructions for
auth=ssh and more simple examples.
* Added to a patch to build amanda with a new libc6, this patch came
from Fedora and maybe interesting to merge
,
+ rc-hostname, xamandad_path, -auth=ssh, amdump, amindexd,
+ amidxtaped);
+}
+else {
+ g_debug(exec: %s %s %s %s %s %s %s %s %s %s %s %s %s %s,
+ SSH, SSH_OPTIONS, -l, xclient_username, -p, client_port,
+ -i, xssh_keys, rc-hostname, xamandad_path, -auth=ssh,
+ amdump, amindexd
Thanks so much for this information.
+--
|This was sent by k.anderson3...@yahoo.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
On Sat, Dec 11, 2010 at 11:32:39AM -0800, Lyndon Nerenberg (VE6BBM/VE7TFX)
wrote:
In the case, what does the ssh daemon on the clinet machhine
do when it recies the requst from the Amanda server ?
The server essentially does 'ssh client /usr/local/libexec/amandad ...'
How does it know
stan wrote:
On Sat, Dec 11, 2010 at 11:32:39AM -0800, Lyndon Nerenberg (VE6BBM/VE7TFX)
wrote:
In the case, what does the ssh daemon on the clinet machhine
do when it recies the requst from the Amanda server ?
The server essentially does 'ssh client /usr/local/libexec/amandad ...'
We have just set up our first client using ssh auth. This machine is
behind firewall, and has a non routbale address (192.168,x,x). The firewall
is set up such that ssh from outside for this machine goes to port 1026,
and is port fwarded via the firewall to the clinet.
I set this up following
In the case, what does the ssh daemon on the clinet machhine
do when it recies the requst from the Amanda server ?
The server essentially does 'ssh client /usr/local/libexec/amandad ...'
Hi,
We are trying to setup Amanda for 1 client behind a firewall with Auth SSH for
the first time. The machines behind the firewall are all NATed. The firewall
will not allow us to port redirect port 22. As a result, all the machines
behind
the firewall have non-standard SSH port numbers
Debbie O Connell wrote:
Hi,
We are trying to setup Amanda for 1 client behind a firewall with Auth SSH for
the first time. The machines behind the firewall are all NATed. The firewall
will not allow us to port redirect port 22. As a result, all the machines behind
the firewall have non
, December 10, 2010 4:32:56 PM
Subject: Re: Configuring Auth SSH for a client behind a firewall
Debbie O Connell wrote:
Hi,
We are trying to setup Amanda for 1 client behind a firewall with Auth SSH
for
the first time. The machines behind the firewall are all NATed. The firewall
will not allow us
My amanda server is 2.6.1p2 my clients are 2.5
Presently I am just using bsd security because that is what I have always been
using.
I am told that it would be best to go to bstcp as this is more up to date.
I want to install the amanda for window and it says that I have to use bsdtcp
for
On Mon, Jun 14, 2010 at 10:54 AM, McGraw, Robert P rmcg...@purdue.edu wrote:
If I compile with --with-bsdtcp-security and bsd, can my 2.6.1p2 server use
bsd security for some clients and bsdtcp for other clients and would I set
this in the define dumptype?
Absolutely.
Dustin
--
Open
\
--enable-manpage-build \
--enable-static-binary \
--disable-s3-device \
QUESTIONS:
In my amanda-2.5.2p1 I have only been using with-bsd-security and auth=bsd.
For amanda-2.6.1p1:
1) Is it ok to have multiple with-bsd*-security lines?
2) is auth=bsd valid
3) do I
this problem is distracting me from
my _real_ work...
For those possessed of godlike depth-of-knowledge, here's the executive
summary: SSH auth works, amcheck seems happy, amdump produces planner: ERROR
Request to zoe.x.noiseplant.com failed: EOF on read from zoe.x.noiseplant.com,
planner plans
the keytab. It doesnt seem to be doing that.
Also, What keytab on the client needs to be read as root?
--Chad
On Jun 25, 2008, at 5:29 PM, Jean-Louis Martineau wrote:
xinetd must be configured to run amandad as root.
Jean-Louis
Chad Kotil wrote:
I am trying to setup krb5 auth on amanda 2.6.0p1. I
Yah, A little background might help.
UVWX.YZ.EDU is the realm of my secondary KDC for these two hosts (the
clients) which I am trying to configure krb auth on. YZ.EDU is the
primary KDC on these hosts. These two hosts are my bastion servers ,
i.e. hop off boxes to protect my local
If your realm is YZ.EDU, then that's what you use. If UVWX.YZ.EDU is
a host name and not a realm name, then it doesn't belong in your
principal names.
Can you explain why you want to auth against the secondary rather than
the primary? I can't think of any reason that should matter.
-Mitch
, What keytab on the client needs to be read as root?
--Chad
On Jun 25, 2008, at 5:29 PM, Jean-Louis Martineau wrote:
xinetd must be configured to run amandad as root.
Jean-Louis
Chad Kotil wrote:
I am trying to setup krb5 auth on amanda 2.6.0p1. I built the
server and client --with-krb5
:
xinetd must be configured to run amandad as root.
Jean-Louis
Chad Kotil wrote:
I am trying to setup krb5 auth on amanda 2.6.0p1. I built the server
and client --with-krb5-security, added a new principal to my KDC
([EMAIL PROTECTED] REALM), and wrote a keytab file and placed it
on the server
that.
Also, What keytab on the client needs to be read as root?
--Chad
On Jun 25, 2008, at 5:29 PM, Jean-Louis Martineau wrote:
xinetd must be configured to run amandad as root.
Jean-Louis
Chad Kotil wrote:
I am trying to setup krb5 auth on amanda 2.6.0p1. I built the
server and client
() == 0) {
if (strcasecmp(auth, krb5) != 0) {
error(_('%s' auth require amandad to be run as '%s'),
auth,
CLIENT_LOGIN);
}
} else {
if (strcasecmp(auth, krb5) == 0) {
error(_('krb5' auth require amandad to be run as root
seem to be doing that.
Also, What keytab on the client needs to be read as root?
--Chad
On Jun 25, 2008, at 5:29 PM, Jean-Louis Martineau wrote:
xinetd must be configured to run amandad as root.
Jean-Louis
Chad Kotil wrote:
I am trying to setup krb5 auth on amanda 2.6.0p1. I built the
server
I am trying to setup krb5 auth on amanda 2.6.0p1. I built the server
and client --with-krb5-security, added a new principal to my KDC
([EMAIL PROTECTED] REALM), and wrote a keytab file and placed it
on the server. It is locked down so only amandabackup (the user that
runs amanda) can read
= /usr/libexec/amandad
server_args = -auth=krb5
disable = no
}
HTH,
---
AlanP
On 25 Jun 2008, at 21:45, Chad Kotil wrote:
I am trying to setup krb5 auth on amanda 2.6.0p1. I built the server
and client --with-krb5-security, added a new principal to my KDC
([EMAIL PROTECTED] REALM), and wrote
xinetd must be configured to run amandad as root.
Jean-Louis
Chad Kotil wrote:
I am trying to setup krb5 auth on amanda 2.6.0p1. I built the server
and client --with-krb5-security, added a new principal to my KDC
([EMAIL PROTECTED] REALM), and wrote a keytab file and placed it
on the server
Hello,
I have an amanda setup using auth-ssh, but I'm running into a bit of a
problem. I've compiled amanda by hand on most of the boxes I'm backing
up (including the server), but I'd like to use the rpm's from zmanda.org
on my servers that have packages available. The problem is that I can't
man amanda.conf
DUMPTYPE SECTION
client_username string
Default: CLIENT_LOGIN. Specify the username to connect on
the client, only use with rsh/ssh authentification.
Cameron Matheson wrote:
Hello,
I have an amanda setup using auth-ssh, but I'm running into a bit
On Thu, Oct 04, 2007 at 12:28:03PM -0400, Jean-Louis Martineau wrote:
man amanda.conf
DUMPTYPE SECTION
client_username string
Default: CLIENT_LOGIN. Specify the username to connect on
the client, only use with rsh/ssh authentification.
Don't know how I missed
On Sat, Aug 04, 2007 at 09:30:55PM +0200, Ralf Auer wrote:
I am running Ubuntu 7.04 on i386 on the server host. Tried gcc-4.1 and
gcc-3.3. Downloaded 2.5.2p1 from Amanda website.
This is how I configured 2.5.2p1 sources:
./configure
--prefix=/opt/amanda
--with-user=amanda
Hi Dustin,
the 2.5.2p1 that produce this error were not from Ubuntu but from
the Amanda download page! Only the 2.5.1p1 sources have been downloaded
from Ubuntu. On some machines the Ubuntu sources compile only, when
libreadline5-dev is installed, on some machines they don't need
Hi Dustin,
it's working now! Still kinda strange for me. What I did was the
following:
I purged the 'flex', 'bison' and 'libreadline5-dev' Ubuntu packages from
my office machine. (Those packages are not installed on my laptop, where
the sources cleanly compiled yesterday).
After this
Perhaps, as the testing process gets started in the
community version (no, folks, I haven't forgotten!),
you can help us out with Ubuntu testing.
Just let me know...
By the way, maybe you could also answer this question: I need a
completely statically linked Amanda for some hosts. Is it
Hi all,
I am just upgrading my Amanda from 2.4.5 to 2.5.1p1 (2.5.2p1 does not
compile at all). I am very happy about the new 'ssh-auth' feature in
2.5. It works now in my test setup (only 2 DLEs).
The question I have now, is, wether ssh is used ONLY for authentication,
or if ALL dumps
I've been using ssh-auth since the earliest days of 2.5. Yes, the
dumps themselves go through the ssh tunnel. I have not noticed any
appreciable increase in backup time, at least on our system, which has
over 400 DLEs. (I'm not sure why the number of DLEs would be
relevant, really.)
Ralf Auer
Ralf Auer wrote:
Hi all,
I am just upgrading my Amanda from 2.4.5 to 2.5.1p1 (2.5.2p1 does not
compile at all). I am very happy about the new 'ssh-auth' feature in
2.5. It works now in my test setup (only 2 DLEs).
The question I have now, is, wether ssh is used ONLY
On Sat, Aug 04, 2007 at 02:59:12PM +0200, Ralf Auer wrote:
I am just upgrading my Amanda from 2.4.5 to 2.5.1p1 (2.5.2p1 does not
compile at all). I am very happy about the new 'ssh-auth' feature in
2.5. It works now in my test setup (only 2 DLEs).
Do you mind expounding
meant.
Thanks again,
Ralf
Ralf Auer schrieb:
Hi all,
I am just upgrading my Amanda from 2.4.5 to 2.5.1p1 (2.5.2p1 does not
compile at all). I am very happy about the new 'ssh-auth' feature in
2.5. It works now in my test setup (only 2 DLEs).
The question I have now
to 2.5.1p1 (2.5.2p1 does not
compile at all). I am very happy about the new 'ssh-auth' feature in
2.5. It works now in my test setup (only 2 DLEs).
Do you mind expounding on the compilation problems with 2.5.2p1? What
OS/architecture? What error(s) did you see?
Thanks!
Dustin
--
Ralf
'ssh-auth' feature in
2.5. It works now in my test setup (only 2 DLEs).
Do you mind expounding on the compilation problems with 2.5.2p1? What
OS/architecture? What error(s) did you see?
Thanks!
Dustin
--
Ralf Auer
Physics Institute IVOffice: 2.137
University
schrieb:
On Sat, Aug 04, 2007 at 02:59:12PM +0200, Ralf Auer wrote:
I am just upgrading my Amanda from 2.4.5 to 2.5.1p1 (2.5.2p1 does not
compile at all). I am very happy about the new 'ssh-auth' feature in
2.5. It works now in my test setup (only 2 DLEs).
Do you mind expounding
Jean-Louis Martineau schrieb:
Because the host key is not known.
Try: ssh ng.oops.intern -i /root/.ssh/id_rsa -l amanda
and accept the host key.
Yup, that was it, thanks. I had contacted as user root, as it seems,
importing the key there.
ssh doesn't use xinetd.
Does that mean I can
This doesn't work for me since I tried it first with 2.5.1p2 on client
and server :
Followed the zmanda-howto
(http://wiki.zmanda.com/index.php/Configuring_SSH_authentication), could
be a bit more explicit in some points IMO ...
-- Can't use amrecover via ssh-auth here.
I always get
(http://wiki.zmanda.com/index.php/Configuring_SSH_authentication), could
be a bit more explicit in some points IMO ...
-- Can't use amrecover via ssh-auth here.
I always get:
# amrecover dds -s ng -t ng
Host key verification failed.
AMRECOVER Version 2.5.2b1. Contacting server on ng ...
[request
What kind of configuration do I need, now that I've upgraded my
server to 2.5.1p2? Most of the clients are 2.4.something
and are no longer able to connect to do a recover, although dumps
work fine.
The server is itself a client. It can do a recover now, but if we change
something I'll
Since you are using the old amindexd/amidxtaped protocol, you must
configure them in your server xinetd the same way you did for your
amanda 2.4.5 server.
Deb Baddorf wrote:
What kind of configuration do I need, now that I've upgraded my
server to 2.5.1p2? Most of the clients are
\
--with-testing=conf10 \
-with-tcpportrange=20482,20993 \
--with-udpportrange=955,978 \
Under the bsdtcp auth scheme which amanda ports
should I define in /etc/services? Right now I have
the following:
amanda-conf10 10116
\
Under the bsdtcp auth scheme which amanda ports
should I define in /etc/services? Right now I have
the following:
amanda-conf10 10116/tcp
amanda-conf10 10116/udp
kamanda-conf10 10117/udp
amandaidx-conf10 10118/tcp
amidxtape-conf10 10119/tcp
and inetd.conf looks
Jean-Francois Malouin wrote:
Looking at the selfcheck debug files for the client (server is the
only client at the moment) there is a warning about amanda-client.conf
not being in the (wrong) place I assume but then it proceed to find
it at the right place. I'm not sure if it's the normal
Hi list,
Maybe I missed something in the documentation, wiki, faq, forum, or in
the list archives, but besides adding ssh authentication in the dumptype
what steps does one take to use it?
I assume its using keys and the amanda backup user then runs a command
via ssh. Does it only use amandad
Jason Castonguay wrote:
Hi list,
Maybe I missed something in the documentation, wiki, faq, forum, or in
the list archives, but besides adding ssh authentication in the dumptype
what steps does one take to use it?
1. set auth ssh in the dumptype
2. both server and client must be configured
/~jcastonguay/
They still need a bit of polish, but work for me.
one more thing, needs to configure Amanda with --with-ssh-security.
It will install dumper/amcheck non-suid.
--Kevin
1. set auth ssh in the dumptype
2. both server and client must be configured exactly the same
a. username
* Gene Heskett [EMAIL PROTECTED] [2004-02-09 22:02]:
Hi!
I'm a newbee on amanda and haven't yet managed to get amanda to
work. The problem in this thread is similar to the one I have. I've
tried the solution sugested by Gene Haskett.
I have made the changes you sugested in the files amanda,
Hi, Sören,
on Dienstag, 10. Februar 2004 at 10:41 you wrote to amanda-users:
SE I have the following in
SE [amanda home]/.amandahosts(indented here only for visability):
SE localhost amanda
SE [EMAIL PROTECTED] amanda
SE [EMAIL PROTECTED] root
SE [EMAIL PROTECTED]root
SE
On Tuesday 10 February 2004 04:41, Sören Edzen wrote:
* Gene Heskett [EMAIL PROTECTED] [2004-02-09 22:02]:
Hi!
I'm a newbee on amanda and haven't yet managed to get amanda to
work. The problem in this thread is similar to the one I have. I've
tried the solution sugested by Gene Haskett.
I have
Hello list
I have a backupserver with two partitions on it that need to be backup'd
+ 2 clients.
I have a .amandahosts in the amanda user's $HOME. It has this in it:
[cut]
hostname.eduline.be amanda
[/cut]
To make backups, this works fine. But when I want to amrecover files, I
get that
You are actually supposed to run amrecover as root...which makes sense
being that would be the account that would be doing a restore or a
recover typically.
Don
Tom Van de Wiele wrote:
Hello list
I have a backupserver with two partitions on it that need to be backup'd
+ 2 clients.
I have a
On Wed, 3 Apr 2002 at 6:25pm, Tom Van de Wiele wrote
Hello list
I have a backupserver with two partitions on it that need to be backup'd
+ 2 clients.
I have a .amandahosts in the amanda user's $HOME. It has this in it:
[cut]
hostname.eduline.be amanda
[/cut]
To make backups,
auth 373720fd subscribe amanda-users [EMAIL PROTECTED]
63 matches
Mail list logo
