I'm looking for information about how best to manage Amanda clients upon which
are Devs are running docker containers. Some of the production hosts are also
running containers. Does anyone have suggestions regarding best practices for
backing up docker containers in an Amanda environment? (I
I've just built a new mysql server and have Amanda client installed and running
on it. Dumps worked fine until I installed sssd and hooked the machine into
our Active Direcotry domain (not my idea.)
Now, this link into Active Directory has bloated the /var/log/lastlog file up
to something
Would a combination of 'admin no-reuse' and 'amvault' do what you want?
> -Original Message-
> From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org]
> On Behalf Of Marcin Stolarek
> Sent: Friday, March 25, 2016 06:29 AM
> To: amanda-users@amanda.org
> Subject: Backup
If your server or client is using the UFW firewall, verify that a recent
package update didn't remove some of your accept rules. I had this happen on
one of my Ubuntu 14 clients just recently, but it broke SSH rather than amanda.
I'd double-check (lsmod) that the *_conntrack_amanda module is
As long as all of your clients are new enough to support it. I have some
ancient (2008-era!) machines hanging around that can't be upgraded and their
clients don't support amanda applications. For those you're stuck with naked
gnutar.
> -Original Message-
> From:
I was just skimming through this week's list messages, and I'm seeing queries
regarding things recently broken, and all of them seem to include ssh, ssl, or
other encryptions.
In mid-December, the Debian/Ubuntu distros pushed out a new openssl library
package that seems to have simply deleted
It sounds like your new empty client is trying to talk to itself instead of
your amanda server. You run amrecover on the client, not the server, and the
client needs to know who the server is. Also, the server needs to know who the
client host is, and who the user is running amrecover.
> > >
[snip]
>
> Which is sort of what I did Joi.
>
> amrecover bothers me because that is no apparent way to strip the leading
> part of the path from what you want to recover, and from the messages it
> presents, if you don't just give up and use a scratch directory, then move
> what it recovers,
r 24, 2015 06:35 PM
> To: Debra S Baddorf <badd...@fnal.gov>; Joi L. Ellis
> <jlel...@pavlovmedia.com>
> Cc: amanda-users@amanda.org
> Subject: Re: Upgrade woes and eternal hanging of dumps
>
> On 9/21/2015 11:36 AM, Debra S Baddorf wrote:
> > YES!I agree with t
I've just read through the long thread prompted by this particular post. I'd
like to offer a few points I didn't see mentioned before...
Idea one: You upgraded from 2.5 to 3.3. 2.5 amdump only spoke UDP with a 'bsd'
auth protocol, so that was the only action available. Thus, inetd.conf
My amanda server has a massive SAN with a virtual tape library defined on it.
The SAN is itself duplicated to a colo of ours over our high-speed backbone.
So, Amanda doesn't have to worry about any offsite action, it happens for me
behind the scenes. No one takes any tapes or hard drives
How to identify setgid/setuid stuff:
root@Macropus:/# ls -la /usr/sbin/am* /usr/lib/amanda/* | grep rws
-rwsr-xr-- 1 root backup 18880 Jan 7 2014 /usr/lib/amanda/calcsize
-rwsr-xr-- 1 root backup 48288 Jan 7 2014 /usr/lib/amanda/dumper
-rwsr-xr-- 1 root backup 10528 Jan 7 2014
Amcheck is a compiled binary, not a script.
With bash, if the path to a script's interpreter is invalid, it says so with
-bash: ./jj: /bash: bad interpreter: No such file or directory
But if it can't find the command you asked for, you get:
-bash: ./jjj: No such file or
I find mixing su and sudo leads to bad juju.
I just use something like:
$ sudo -u amanda amcheck blah blah
You can also just do:
$ sudo -u amanda /bin/bash -l
.. to give yourself a login shell for the amanda account. Whether or not this
will work on your platform varies with
I just had a vaguely similar issue on my network. My Amanda server stopped
processing, and everything failed with 'RESULTS MISSING'. Nothing I tested on
the Amanda server worked, and I had several zombie amandad processes stuck in
it. I rebooted the Amanda server and got to checking the
A rather general-purpose way to check for *nix is to cat /etc/issue.net, which
is the login-banner for a remote shell connection. These usually default to a
line with the OS version and hostname, printed before the login prompt.
-Original Message-
From: owner-amanda-us...@amanda.org
With the NIS change… did that involve changing the hostname or IPs the server
appears to be using as seen from the client? Is your xinetd using tcpwrappers?
Do you need to update /etc/hosts.allow, hosts.deny, and/or
~amanda/.amandahosts? Is the new Amanda UID reflected properly in
https://en.opensuse.org/Archive:Package_list_11.3 lists Amanda-2.6.1 as an
available package. If that version is new enough, you can install it with the
usual package manager.
-Original Message-
From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On
Behalf Of
What does /etc/fstab contain for the two partitions with the holding disks?
I've never used a zfs filesystem; does the amanda account have sufficient
permissions to create files/directories on the new holding disk directory?
Could the mount permissions be incorrect? (IE it's mounted for
Message-
From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On
Behalf Of Jon LaBadie
Sent: Monday, September 29, 2014 8:17 PM
To: amanda users
Subject: Re: Question about backing up a MS-Windows VM (NFTS file system)
On Mon, Sep 29, 2014 at 03:51:43PM +, Joi L
It sounds to me like you need to tell the system to update its ldconfig cache.
Ldconfig --help.
This is something you usually do as root after installing/building new
libraries.
--
Joi Owen
System Administrator
Pavlov Media, Inc
-Original Message-
From: owner-amanda-us...@amanda.org
We have several SANS here. I'm not their manager so I'm not able to really be
specific as to brand or whatnot, but I know one of them is setup to replicate
itself off-site to a backup SAN, so any hosts storing files on it get those
backed up for free without Amanda.
Another SAN we have is
I've got some systems in a similar situation, and I usually don't bother
backing up from the guest's filesystem directly. I have a cron job that makes
an LVM snapshot of the disk image and uses 'dd' to do make a bit image of the
entire filesystem into a .img file, and then I have Amanda back
One server can support them all. I have a single 3.3.3 on Ubuntu 14.04
supporting DLES from clients on Ubuntu 14.04, 12.04, 10.04, Debian 7, 6, 5,
Cent OS 6 (.2 and.3) and Cent OS 5.X (.2,3,4,5,6,7,8,10)
For all of these, I installed the amanda-client package with the platform’s
package
I'm using bsd auth everywhere in my environment, and I'm successfully backing
up machines on public IPs from my amanda server inside our NAT firewall.
I put the name/ip of the NAT firewall itself into my client's .amandahosts
file, not the name of the Amanda server. Theoretically, anyone
I've been doing some googling, and the rpc_pipefs is a feature/function/product
of nfs4. It's used for communicating between nfs4 servers and clients and
doesn't contain anything you need to back up, it's all dynamically generated as
part of client/server interactions. I'd just put that
...@wdtv.com]
Sent: Monday, July 28, 2014 12:29 PM
To: Joi L. Ellis
Cc: r.vick...@rhul.ac.uk; amanda-users@amanda.org; bug-...@gnu.org
Subject: Re: [BULK] Re: Question on the one-filesystem option
On Monday 28 July 2014 11:00:25 Joi L. Ellis did opine And Gene did reply:
I've been doing some googling
I've been installing Amanda on our network for the past few months and on a
number of the machines, I noticed that the machine had an /etc/xinetd.d/Amanda
file, but the xinetd service wasn't installed, openbsd-inetd was, and that one
reads /etc/inetd.conf. Amanda-client package installs the
I think you have a more basic network connectivity issue. If it were a simple
.amandahosts issue, you'd get an error message to that affect, not 'connection
reset by peer', which is a network thing.
Don't forget to check the logs on the server and the client, see
/var/log/Amanda/*, find the
29 matches
Mail list logo
