I'm running amanda 3.3.9 with vtapes and trying to enable writing to
multiple volumes with:
taper-parallel-write2
Sometimes, but not always, I'll get an error like this during the dump:
dump to tape failed: taper: Slot 5, containing 'daily-5', is already in
use by drive
of starting a discussion, and also “bump”.
Deb Baddorf
Fermilab
On Mar 12, 2015, at 5:21 PM, Oscar Ricardo Silva osi...@utexas.edu wrote:
I've been testing encrypted storage of backups but am confused as to how to restore
files. In my setup, I run the backup server with other sysadmins running
I've been testing encrypted storage of backups but am confused as to how
to restore files. In my setup, I run the backup server with other
sysadmins running the individual servers being backed up and ideally I'd
like for these sysadmins to restore files from the client systems
without
On 04/27/2011 04:10 PM, gene heskett wrote:
On Wednesday, April 27, 2011 05:00:34 PM Oscar Ricardo Silva did opine:
I've been using amanda for awhile but because of some index not found
issues decided to try 3.2.2 (currently using 2.6.1p2). Right now
backups on the new version work fine
On 04/27/2011 03:58 PM, Jean-Louis Martineau wrote:
Oscar Ricardo Silva wrote:
[amanda@amanda tmp]$ cat
./amanda/server/newbktest/amidxtaped.20110427135604.debug
1303930564.513325: amidxtaped: pid 933 ruid 511 euid 511 version
2.6.1p2: start at Wed Apr 27 13:56:04 2011
1303930564.513380
This has come up in the past but so far I haven't seen an actual
solution ... does anybody have client side encryption working on
FreeBSD? I have it working fine with my linux clients and for now I'm
using server side encryption for the freebsd clients but it puts too
high a load on the
Since I've been this deep (holds hand above head) in trying to get encryption to
work, I've been reading and re-reading documentation and man pages. I noticed a
small typo in the amanda.conf page for the section detailing encryption in
dumptypes. Basically, for encrypt client it says to look
With all the problems I've had doing client side encryption on FreeBSD I wanted
to make sure amanda worked without any fancy options. I tried two
variations on backups:
1. No compression, no encryption, ssh authentication
2. No compression, SERVER-side encryption, ssh authentication
I'm
: Not found in archive
tar: ./boot/boot1: Not found in archive
tar: Error exit delayed from previous errors
Extractor child exited with status 2
(by the way, two backups were run, one with tar 1.13.25 and the second having
configured amanda to use 1.14)
Any suggestions/ideas?
Oscar Ricardo Silva
Dustin J. Mitchell wrote:
On Thu, Apr 3, 2008 at 9:40 PM, Oscar Ricardo Silva
[EMAIL PROTECTED] wrote:
I think I'm getting closer to getting this working on FreeBSD and my past
errors were a combination of hardheadedness and incorrect documentation.
Some of the encryption documentation points
Sorry for the multiple recent posts but as I work my way through enabling
encrypted backups I keep running into different issues. In our last episode, I
had enabled encrypted backups and corrected an issue with ipv6 and key placement
on the amanda server.
My current issue is that while backups
Dustin J. Mitchell wrote:
On Fri, Mar 28, 2008 at 5:57 PM, Oscar Ricardo Silva
[EMAIL PROTECTED] wrote:
/usr/local/amanda25/sbin/amrecover -C dailytoo
AMRECOVER Version 2.5.2p1. Contacting server on amanda.tn.utexas.edu ...
[request failed: amanda.tn.utexas.edu: ssh could not resolve
I've been recently moving to doing encrypted backups with ssh authentication.
After some hiccups with random numbers and cryptic messages about Error:
Password must be at least 20 characters, I am now successfully encrypting my
backups. Now I just need to test the ability to restore files ...
Eric Schnoebelen wrote:
Oscar Ricardo Silva writes:
- I'm attempting to compile the client version of amanda on a Dell
- PowerEdge server running FreeBSD 6.3 but keep running into an
- ssh related error. I use the following configure statement:
Use the port from /usr/ports.. It has patches
I'm attempting to compile the client version of amanda on a Dell PowerEdge
server running FreeBSD 6.3 but keep running into an ssh related error. I use
the following configure statement:
./configure --prefix=/usr/local/amanda25 --infodir=/usr/share/info
--mandir=/usr/share/man
I've setup encrypted backups per http://wiki.zmanda.com/index.php/Encryption
and it's working. Unfortunately, I have two clients that have configured the
ssh daemon to listen on port 23 instead of 22. I thought I could get by this by
creating an ssh config file on the amanda server dictating
of how amanda actually launches the
encrypted portion of the backup, I can't quite follow it.
As always, any help would be appreciated.
Oscar
Oscar Ricardo Silva wrote:
I hadn't thought to do that and I would like to have said that fixed it
... unfortunately, no, that didn't fix it. Same
I'm pretty sure this isn't necessarily a problem with amanda but more of one
with the utilities used to encrypt the backups. I'm using amanda 2.5.1p3 and
attempting to encrypt the transmission and storage of backups. I've done this
on a few machines, and this one is running FreeBSD 4.11 along
like aespipe is not really getting the passphrase that's stored
in /home/amanda/.am_passphrase ... H ...
[EMAIL PROTECTED] wrote:
Can you make the content of .am_passphrase to be 20 chars long?
It's a requirement by aespipe on some platform, I guess.
Oscar Ricardo Silva [EMAIL PROTECTED
(Not sure if my messages are reaching the list so apologies if you're received
this twice)
I've been attempting to compile amanda 2.5.1 on FreeBSD 4.11 but run into this
error on the make:
amandad.c:826: warning: zero-length format string
amandad.c:882: warning: zero-length format string
We're moving away from tape based backups and have purchased a large
disk array that directly attaches to my amanda server. I'm aware of the
file driver for mimicking tape drives but should I even go that route?
Why not just leave the backups on the holding disk?
Any suggestions/information
Ian Turner wrote:
On Thursday 28 September 2006 11:54, Geert Uytterhoeven wrote:
Amanda only keeps track of what was written to `tape'. You cannot restore
from the holding disk without resorting to a manual restore.
This was true a long time ago, but no more. Today you can restore from the
I'm currently using 2.4.5 but would like to upgrade to 2.5.1. I'm on
unclear on what I need to do as far as authentication is
concerned. I don't control all my clients and can't really ask them
(long story) to make changes to their amanda configs. If I used bsd
authentication, is it
slink off to the corner now ... and excuse the top-posting ...
Oscar
At 07:52 PM 7/6/2005, Paul Bijnens wrote:
Oscar Ricardo Silva wrote:
I have a few hosts where some filesystems fail to be backed up. I
thought it might be firewall/iptables issues but the fact that at least
one filesystem
I have a few hosts where some filesystems fail to be backed up. I thought
it might be firewall/iptables issues but the fact that at least one
filesystem on the host is successful seems to ruin that idea. Also, on the
amanda server one of the hosts having problems is completely trusted on all
I've been banging my head against a wall trying to figure out why I
couldn't backup a few clients even though all the checks seemed to run
OK. Sure enough, turned out to be a firewall/iptables issue ... my
amanda server was allowed in on ports 10080, 10082, 10083 but NOT on any
other ports
I thought I would respond to the various suggestions in one message and
included my original message at the end for reference. I also realized
that I wasn't clear when I displayed the permissions
on /dev/mapper/VolGroup00-LogVol00 device. When the machine boots,
permissions are:
I know this isn't necessarily an amanda question, but I have a user who's
setup two RedHat Enterprise 4 machines and used lvm. Unfortunately, the
devices:
/dev/mapper/VolGroup00-LogVol00
has permissions:
drwxr-xr-x 2 root root 100 Jun 6 03:58 /dev/mapper
brw-r- 1 root disk 253, 0
I recently replaced my amanda server with a new machine but managed to move
all indices and databases with it. I did go from FreeBSD to Linux but all
changer scripts and tape devices are configured properly and working. The
problem I'm having is that I'm getting
... FAILED [Estimate
I have setup encrypted backups using the script found at:
http://security.uchicago.edu/tools/gpg-amanda/
and backups appear to work. The problem comes when I attempt to restore
files using amrecover. Once the restore starts I get a message saying that
what's found is not a tar archive
Load
At 12:22 PM 12/5/2002 -0500, Mark Stosberg, you wrote:
Hello,
I'm curious how some you have dealt with the catch-22 of backing up
Amanda's configuration files. Ideally during the restore process Amanda
is available with all it's configuration files intact. However, if the
Amanda server needs to
At 03:32 PM 4/26/2002 -0500, Terry McCoy, you wrote:
I have a file system on a client that I want to exclude directories
from being backed. Every time the client runs the excluded directories
are backed up anyway.
I have a dump type that has exclude list specified as shown
below:
define
If you really, really want to do this, use the -f flag:
amlabel -f DailyConfig LABEL
Oscar
At 03:24 PM 3/18/2002 +0800, Robert SHEN, you wrote:
I tried to relabel the tape used previous by another config, and I got the
following error:
...
rewinding, reading label Monthly-03, tape
At 11:50 AM 6/13/2002 -0400, Martinez, Michael - CSREES/ISTM, you wrote:
Tried excluding the entire directory --- no go.
Another question for ya: if I use the exclude list option, does my list
file need to be in an amanda directory (var/amanda) or can it be anywhere?
My Sco Unix installation has
At 11:32 AM 6/12/2002 -0400, Martinez, Michael - CSREES/ISTM, you wrote:
I had posted this msg before, but I had given the wrong info.
I'm backing up / on one of my clients. I would like to exclude
/var/adm/syslog from the backup.
On my server:amanda.conf, I have defined a disklist entry with
At 03:32 PM 4/26/2002 -0500, Terry McCoy, you wrote:
I have a file system on a client that I want to exclude directories
from being backed. Every time the client runs the excluded directories
are backed up anyway.
I have a dump type that has exclude list specified as shown
below:
define
I decided to start using tar for a particular machine but received the
following for one of the file systems (the rest of the machine backed up
without problems):
FAILURE AND STRANGE DUMP SUMMARY:
utnetdb.gw /usr lev 0 FAILED [/usr/local/bin/tar returned 2]
/-- utnetdb.gw /usr lev 0 FAILED
If you really, really want to do this, use the -f flag:
amlabel -f DailyConfig LABEL
Oscar
At 03:24 PM 3/18/2002 +0800, Robert SHEN, you wrote:
I tried to relabel the tape used previous by another config, and I got the
following error:
...
rewinding, reading label Monthly-03, tape
I've been trying to backup a large filesystem on a client with no
success. I am now trying to back it up with GNU tar, exclude lists and the
use of two tapes per run. The filesystem is about 30GB and I have a DLT
7000 drive with DLT IV tapes which natively do 35GB. The message I
received
Is the amanda user part of the group that can read /dev/rdsk/c0t0d0s7 ?
At 11:44 AM 2/1/2002 -0500, gene, you wrote:
I made a little more progress. Now I'm getting a permissions problem on
/export/home (this is all I'm trying to backup until I get it working).
{datadev:root}# su - amanda -c
I've been successfully using amanda for my backups, starting with 2.4.1 and
now up to 2.4.2p2. I have a filesystem on one machine that I want to
backup using tar (yes, I have GNU tar 1.13.19 installed). The problem is
that although the backup goes through it's paces, it appears something is
At 04:35 PM 1/31/2002 -0500, John R. Jackson, you wrote:
I've been successfully using amanda for my backups, starting with 2.4.1 and
now up to 2.4.2p2. ...
Ooooh. An old-timer :-).
Oooohhh, ouch ... the sting ...
sendsize-gnutar: error opening
At 02:48 PM 8/23/2001 -0500, Rebecca Pakish, you wrote:
Let me apologize in advance for my lack of knowledge and experience.
Being thrown into the world of Unix/Linux (willingly) and my first task is
amanda.
I'm running RH 7.1 on an old Dell 333 with an IDE drive and an external
12/24 SCSI
I noticed that 2.4.2p1 had a problem on some Linux machines (associating
/dev/root with /) and saw that this had been fixed in 2.4.2p2. I upgraded
the client portion of Amanda on all my backup targets so as to have on
consistent version. Unfortunately, right after I did that, I got the
I've been having trouble backing up one client, where I changed the
dumptype to use tar on one of its filesystems (and I'm using tar 1.13.17 on
the client). All other clients use dump, and while I left the etimeout
setting to the default of 600, the backup ran fine except for the client
I sent the message below yesterday. After having read some other seemingly
unrelated messages, I realized that I did change one of the disks on the
client "client.foo.com" from using dump to tar (see dumptypes below). It
was after this change that the entire client started coming back as
Yes, this was all that was in the file and I now see that it was
incomplete. I didn't see the process running so it was either killed or it
crashed. I'll stay with tar and the increased timeout for tonight and see
if the process does complete.
Oscar
At 05:20 PM 1/30/01 -0500, John R.
47 matches
Mail list logo
