[EMAIL PROTECTED] wrote:
Hello,
I have used amtapetype to get the LTO4 constants, it was very long
from 13:00 until 21:30 . but here is it :
define tapetype LTO4 {
comment Dell LTO4 800Go - Compression Off
length 802816 mbytes
filemark 0 kbytes
speed 52616 kps
}
Guy Dallaire wrote:
I finally found the right FM in order to RTFM and proceeded to create the
RAID-0 holding disk with 2 250Gb SATA drives in order to try to fix the
trhroughput problem with the tape drive. The raidtools have been replaced by
the mdadm command.
I'm back to square one.
Jon LaBadie wrote:
On Thu, Oct 27, 2005 at 10:25:43AM -0700, Chris Marble wrote:
Jon LaBadie wrote:
On Wed, Oct 26, 2005 at 11:53:16AM -0700, Chris Marble wrote:
the /dev/sdb2 is mounted on / partition
but instead of using /dev/sdb2 it uses /dev/root for backup
Jon LaBadie wrote:
On Wed, Oct 26, 2005 at 11:53:16AM -0700, Chris Marble wrote:
the /dev/sdb2 is mounted on / partition
but instead of using /dev/sdb2 it uses /dev/root for backup
here is the right of the two devices
brw--- 1 root root 8, 18 avr 1 16:48 /dev/root
Eric Doutreleau wrote:
i cannot backup / partition with dump on my FC3 machine.
I'm using
amanda-2.4.4p3-1 on both server and client
Steps to Reproduce:
i have configured my amanda server to backup a / partition on my FC3
computer. I use the mountpoint / in my disklist file
i
I'm tring to build amanda client on a new Mac 10.4.1 box.
./configure --prefix=/usr/local/amanda-2.4.5 --with-user=amanda
--with-group=wheel --with-config=hmcis --without-server
--host=powerpc-apple-darwin
Then a simple make which ends with:
/bin/sh ../libtool --mode=link gcc -g -O2 -o
Server is Linux 2.4.20, Amanda 2.4.4b1 Troublesome client is
Linux 2.4.18, Amanda 2.4.4b1. 108 other DLEs on other systems are
working fine. I'm using dump for my backups.
/-- Odin /home lev 1 STRANGE
sendbackup: start [Odin:/home level 1]
sendbackup: info BACKUP=/sbin/dump
sendbackup:
Jean-Louis Martineau wrote:
Could you send a backtrace?
In gdb, type 'where' after the Segmentation fault.
Could you also try to run amcheck with the MALLOC_CHECK_ variable set.
For more details on it, see the man page for malloc.
export MALLOC_CHECK_=2
[9:23am] operator@Chris (~):
I've been using Amanda 2.4.2p2 for several years. Server is Linux
2.4.20 and clients are Linux, Solaris, HP-UX, IRIX and Tru-64.
Had a DLE that was too large so it was time for gnu tar and an exclude list.
Installed Amanda 2.4.4b1 on the troublesome client, Linux 2.4.18, and it's
fine there.
Joshua Baker-LePain wrote:
On Wed, 19 Feb 2003 at 2:46pm, Chris Marble wrote
I've been using Amanda 2.4.2p2 for several years. Server is Linux
2.4.20 and clients are Linux, Solaris, HP-UX, IRIX and Tru-64.
Had a DLE that was too large so it was time for gnu tar and an exclude list
stan wrote:
I'm in the process of upgrading my Amanda machine from an older HP-UX
machine to a new faster FreebSD machine. Lot's of machines that used to
back up fine ae now failing with the following:
sendbackup: spawning /usr/sbin/dump in pipeline
sendbackup: argument list: dump 0usf
Jon LaBadie wrote:
chg-multi?
I thought that was generally used for multiple drives.
Not for multiple tapes in a changer.
I've been using chg-multi for several years with a changer.
Started using it with a gravity-feed DDS stacker and stayed with
it when I moved to an AIT-2 4-tape changer.
Orion Poplawski wrote:
Just started testing with using software compression on the server
(trying not to impact the clients too much), and got the following result:
Advantageto doing some compression on the clients is that it saves you
network bandwidth.
A lot of file systems were not
Robert wrote:
Please advice me which type IDE-Tape drive will be better to buy for
15 Gb storage.
Doing a quick look at Pricewatch says that a Travan TR5 10/20Gb drive
would be a good match: About $200
Seagate Hornet
10/20Gb Travan 5 Int
IDE Tape backup
drive p/n stt22a
With the cost
Owain Pritchard wrote:
I have added a new client into the disklist and it's access password
in the amandapass file.
When I run amcheck on the new configuration, amcheck throws up
the following error appears:-
ERROR: info file
=?iso-8859-1?B?SOlsaW8gRHViZXV4?= wrote:
Can i use Amanda without holdingdisk??? I want to backup from a share
directly do a tape device.
Sure, no problem. Just don't specify any holding disk in amanda.conf
--
[EMAIL PROTECTED] - HMC UNIX Systems Manager
Nicolas Cartron wrote:
I want to install Amanda on a production environment,
backup server on FreeBSD and clients running Linux, Solaris or FreeBSD.
I read in the section dedicated to Amanda (in the 'Unix backup recovery',
O'reilly) the following lines :
AMANDA currently starts a new
Du-Wayne Rood wrote:
I was wondering if someone can tel me how to configure amanda to run
more than one dump per server?
Do you want Amanda to run multiple data streams from a client to the
tape server? Then increase
maxdumps 4 # Max number of concurrent dumps to run on the
Wayne Byarlay wrote:
Greetings, quick easy question: My amanda machine was down for 2 consecutive
backup days. What can I expect when I bring it back online? Will Amanda
automatically compensate? or do I need to manually do the last 2 tapes?
Amanda will whine but everything will be fine
Chris Marble wrote:
Jean-Louis Martineau wrote:
Amanda-2.4.3b4 on client is broken and will not talk correctly with
older server, upgrade your client to 2.4.3
Okay, upgrade done. I'll find out tonight.
Dumps appear to have gone sucessfully. If only I'd asked before spending
as much
Jean-Louis Martineau wrote:
Amanda-2.4.3b4 on client is broken and will not talk correctly with
older server, upgrade your client to 2.4.3
Okay, upgrade done. I'll find out tonight.
--
[EMAIL PROTECTED] - HMC UNIX Systems Manager
John R. Jackson wrote:
2 of the strace files ended with:
--- SIGXCPU (CPU time limit exceeded) ---
+++ killed by SIGXCPU +++
Well, *that* would certainly do it :-).
Not sure how we got from XCPU to signal 24, but whatever.
I've been using Amanda for several years and usually
John R. Jackson wrote:
Okay, script gzip.test put in place and amanda run with a disklist
just for the one troublesome client. 5 partitions. 3 work, 2 fail.
The gzip.log files don't give me any great hints:
There's a bit more information there. The two that failed returned a
status of
Martin Oehler wrote:
I use amanda on a solaris 7 box with a DTL drive (20 GB)
attached. My dumpcyle is 4 weeks with 20 runs per cycle.
Because the size of one incremental backup is only
between 2-4 GB I don't want to change the tape each day.
You could crank your dumpcycle down to 3 (or
Chris Marble wrote:
John R. Jackson wrote:
That may be what it says (--with-user=backup), but it's not what's built
into the runtar binary. The binary is running as though you had said
--with-user=operator.
You're right. After make distclean, reconfig and reinstall the gnutar
Brook Hurd wrote:
We currently use 20 8 gig tapes for our backup in
amanda. We have obtained some 20 gig tapes and we
would like to add these to the backup schedule. Do we
need to replace the 8 gig tapes with the 20's or can
we intermix them?
You could set up a seperate configuration to
Joshua Hamor wrote:
Amanda Tape Server Host Check
-
Holding disk /dumps/amanda: 14044688 KB disk space available, that's plenty
amcheck-server: slot 2: date 20020318 label C5102 (active tape)
amcheck-server: slot error: no tape online
amcheck-server: fatal slot
Brad Tilley wrote:
But I was wondering if I should have just tried to run amlabel on the
tape (in hopes that a new label would fix the problem) instead of
removing the tape first.
IIRC (If I Recall Correctly) an amlabel makes whatever data was on
the tape unavailable. You could have
Jeffery Smith wrote:
Can any one tell me if there is a way to set a stop time for backups? I
am not thrilled about this idea, but some of my backups do run a bit
long and I am getting complaints some mornings when there are many level
0 dumps.
No way that I can think of. You could start
Carl Wilhelm Soderstrom wrote:
I've got an AIT-2 tape drive, which supposedly will hold 50-100GB.
the tapetype that I found, seems to say that it's 43GB:
define tapetype AIT2 {
comment AIT-2 with 230m tapes
length 43778 mbytes
filemark 3120 kbytes
speed 5371 kps
}
Here's what I'm
Martin Oehler wrote:
Chris Marble wrote:
Martin Oehler wrote:
I use amanda on a solaris 7 box with a DTL drive (20 GB)
attached. My dumpcyle is 4 weeks with 20 runs per cycle.
Because the size of one incremental backup is only
between 2-4 GB I don't want to change
Brandon Moro wrote:
It seems to be expecting an entry in the gnutar-lists file, and didn't find
it.
Can someone give me a better explanation concerning what exactly
the gnutar-lists do? (what function it serves?)
See if those files get created once you've got the backups running. I may
Martin Oehler wrote:
I use amanda on a solaris 7 box with a DTL drive (20 GB)
attached. My dumpcyle is 4 weeks with 20 runs per cycle.
Because the size of one incremental backup is only
between 2-4 GB I don't want to change the tape each day.
You could crank your dumpcycle down to 3 (or
Don Potter wrote:
I'm trying this outI have more than enough holding are and network
bandwidth..so I was wondering how many users actually adjust this
value.I have been up to 8 but I have usually become involved with
spindle contention.
I run mine at 20. I max out a pair of
[EMAIL PROTECTED] wrote:
I have 17 ~50G tapes...
I also have approximately 50G to backup.
If it's going to be 50Gb after compression then you can run full
backups every day with dumpcycle=0. If it won't fit you could set
dumpcycle=2. Set your weekly backups to no-reuse until they're a
Juanjo wrote:
After doing some checks, I'm gonna let amanda do a first backup, about 180
Gigs of data.
Well, after those checks, the pointer is at tape 3, how can I tell amanda
to start with tape 1?
I've tried launching:
amrmtape confname tapelabel
but it says something about
Stephen Carville wrote:
One of my tapes did not come back from offsite in time for today's
backup (Some winidiot sent if off for four weeks instead of one) so
today's backup failed. How can I get amanda to just skip that tape
and go on to the next one in the sequence? When I try amcheck,
John R. Jackson wrote:
Okay, script gzip.test put in place and amanda run with a disklist
just for the one troublesome client. 5 partitions. 3 work, 2 fail.
The gzip.log files don't give me any great hints:
There's a bit more information there. The two that failed returned a
status of
John R. Jackson wrote:
/sbin/dump 0sf 1048576 - /dev/sda5 | /bin/gzip -dc | cat /dev/null
That command fails with
gzip: stdin: not in gzip format
Sorry. You're right that the 'd' should not have been there.
... At least I can run backups with compression once again.
So,
John R. Jackson wrote:
Yeah, still have a problem. ...
Nuts! I was hoping your problem would just go away on its own :-).
It did go away by itself when the same thing happened 6-8 months ago.
Each time it showed up when I cranked down dumpcycle and amanda had
to start delaying things.
Wayne Richards wrote:
We have been experiencing a lot of failures on full backup with a large dump
disk.
Our dump disk devices are:
/dev/dsk/c0t13d0s0 83143932708 8145398 1%/usr13
/dev/dsk/c2t1d0s317413250 10 17239108 1%/usr14
The holdingdisk
Ben Elliston wrote:
On Friday, amdump wrote my dump images to a tape successfully, but a
subsequent amverify showed that the tape is defective. Now, my dumps have
been removed from the holding disk, but I don't think the images on the
tape are usable.
Is there any way to re-do this
Albert Hopkins wrote:
Testing a new amanda server install (RH Linux 7.2, amanda 2.4.2p2, DLT
7000). I first ran a successful backup and then attempted to recover one
(small) file. The first time I extract I get
amrecover: Can't read file header
extract_list - child returned
Davidson, Brian wrote:
I have Amanda 2.4.3b1 installed on a intel computer running BSDI 4.1. I
have amanda in the /etc/services file and in the /etc/inetd.conf file.
amandad does not start when the computer is rebooted but no error messages
are reported in /var/log/messages. I can run
Jon LaBadie wrote:
Last night I realized I had forgotten to change cartridges
when the dump was about 1/2 way through. Some disklist entries
done, others in progress, others not started.
What would happen IF I put in the correct cartridge at that time?
Amanda already knows that there
John R. Jackson wrote:
This would be a more accurate test:
dump 0sf 1048576 - /dev/sda5 | (restore -tvf - ; cat /dev/null)
Suprisingly that ran fine:
Not terribly surprising, but it shows the dump - restore pipeline is
not the problem. Now try this:
/sbin/dump 0sf 1048576
Robert Kearey wrote:
It seems that the setup I've inherited has no indexing enabled, and
I'm at a loss to understand why given the advantages. Is there some
compelling reason to have indexing off? Can I just turn it on?
I have indexing enabled but I never make use of it. I'm either
Joshua Baker-LePain wrote:
On Wed, 16 Jan 2002 at 9:40pm, Chris Marble wrote
? sendbackup: index tee cannot write [Broken pipe]
| DUMP: Broken pipe
| DUMP: The ENTIRE dump is aborted.
? index returned 1
sendbackup: error [/sbin/dump returned 3, compress got signal 24]
Hmmm
John R. Jackson wrote:
This would be a more accurate test:
dump 0sf 1048576 - /dev/sda5 | (restore -tvf - ; cat /dev/null)
Suprisingly that ran fine:
dir 478497 ./kerberos/sbin
leaf478498 ./kerberos/sbin/sserver
leaf 176 ./tmp
DUMP: 81.09% done at 8174 kB/s,
I've been a proponent of dump for years but I'm looking to move to
gnu tar for one disk. Amanda fails with dump on just this disk when
it tries to do a level 0 backup.
/-- Odin /home lev 1 FAILED [/sbin/dump returned 3, compress got signal 24]
sendbackup: start [Odin:/home level 1]
Malcolm Herbert wrote:
The first question is how to easily stagger 0-level dumps across a
dump cycle where some disks need to be backed up at different frequency
to others.
You can use different dump types for different disks. In these special
dumptypes set the desired dumpcycle for that
Eric Nelson wrote:
Does anyone know how to 'tell' amanda to stop gathering estimates of a PC if it goes
off-line/crashes? Overall, I would like for amanda to bypass the particular PC if
the
estimates are taking too long and continue with the rest of the dump.
You could shorten etimeout in
[EMAIL PROTECTED] wrote:
have a
Quantum DLT8000-40 which holds ten tapes for which I found the description
with length, filemark, and speed. My question is do I use chg-multi for the
tpchanger parameter, and do I need to use the changerfile parameter? Also
do you need a changer.conf file?
=?iso-8859-1?q?Jos=E9=20Vicente=20N=FA=F1ez=20Zuleta?= wrote:
Error #1: I ran amrecover on the tape server:
# /home/amanda/sbin/amrecover NEWBREAK
AMRECOVER Version 2.4.2. Contacting server on
lenbkx0001 ...
220 lenbkx0001 AMANDA index server (2.4.2) ready.
200 Access OK
Setting restore
Thomas Beer wrote:
during boot the following errors occure:
Should I place every service started place in an
extra file?
That's what works for me (seperate files).
My amanda file just has:
service amanda
{
socket_type = dgram
protocol= udp
Ross George wrote:
When I run amdump, the following message appears (presumably due to the
hard drive being too big):
The system is FreeBSD 4.0, with Amanda 2.4.2p2.
FAILED AND STRANGE DUMP DETAILS:
/-- xxx /exports/mail lev 0 FAILED [/sbin/dump returned 3]
sendbackup: start
=?iso-8859-1?q?Jos=E9=20Vicente=20N=FA=F1ez=20Zuleta?= wrote:
Also another of my problems was using Linux dump. Is
simply useless with amanda, stick with tar (not very
usefull if you have to backup time sensitive files as
Rational Clearcase VOB's).
I'm doing my backups with Linux dump,
Joerg Klaas wrote:
So, does someone have a set of working conf-files for me, to be able to
start an backup using:
Linux Kernel 2.2x
SONY TSL-11000 DAT Tapechanger (8Tapes)
I already found 3 devicefiles which seem to be ok, for me side here.
They are
/dev/sg0
/dev/sg1
/dev/nst0
Damith Coomasaru wrote:
I am new to amanda. I tried to restore but I occured following error:
amanda:~# /usr/sbin/amrestore /dev/st0
amrestore: 0: skipping start of tape: date 2002 label HISS0
amrestore: 1: restoring amanda.ruh.ac.lk._var_backups.2002.0
...
amrestore:
Michael Sobik wrote:
amrestore correctly lists all the dump images on the tape. However, if I
try and restore with:
amrestore -p /dev/device real hostname real disk name /dev/null
I get:
amrestore: 3: restoring realhostname.diskimage.0
Why not try a more real restoration
Dan Smith wrote:
I've got a machine that is trying to backup a directory that is about
4GB. I've got the dumptype set with server fast compression. It's
been going for at least 8 hours (on this one disklist entry). The
machine is very fast, so it's not just lagging. Other disklist
Stan Brown wrote:
I'm backing up 99 filesystems. I am using one of the postscript forms
(forget which one) to print out a report at the end of the run. Clearly 99
won't fit in one page.
I'm using example/3hole.ps and my 81 filesystems fit on 2 sides of a single
piece of paper. I don't
=?iso-8859-1?Q?gloria_era=F1a?= wrote:
I've been noticing that our amanda backup fails every 10 days and stop to
backup our main server. Can someone point me why I'm getting this? I'm not
very familiar with amanda and we rely on someone's script for our backup
which makes it more
peanut butter wrote:
Hi, I'm using version 2.4.2p2 of Amanda. For a particular client on
which I use tar with Amanda to back up a single directory, this entry
has worked fine until I aborted an amdump several days ago (at least I
think these are connected). The next amdump (or one very
Denise Ives wrote:
I still get access Errors on the partitions for my newly
added clients. I have tried using both hdg1 and /dev/hdg1 in the disk
list.
Amanda Backup Client Hosts Check
ERROR: sunny3.neptune.com: [can not access /dev/hdg1
(/dev/hdg1):
[EMAIL PROTECTED] wrote:
This morning I needed to overwrite an old tape. I looked in the tapelist
file and my tape is listed as reuse. If I try to flush data to that tape
I get the error cannot overwrite active tape. Must I run an amrmtape
before I can reuse a tape? I feel I am missing
Tal Ovadia wrote:
Server Linux RH6.2 Client Sun E450 Solaris 2.7
I get a strange error from amcheck on the non system disks on this
specific machine:
ERROR: myserver.mydomain.com: [can not access /disc2 (/disc2): No such
file or directory]
ERROR: myserver.mydomain.com: [can not access
Patrick Presto wrote:
Is this the only way to do it you think? I was hoping I could use the tapes
and just append to the last backup taken (somehow??). I would prefer not to
use the holding disk if possible.
By design Amanda will not append to a tape.
If I did backup five days to the
Randy Gibson wrote:
We have one system on our LAN that seldom get's all partitions backed up.
FAILURE AND STRANGE DUMP SUMMARY:
kazoo /u1 lev 1 FAILED [could not connect to kazoo]
Where another partition on the same machine does make it. I seen this on
other nodes on the LAN
radar wrote:
i have a (hp c1537a dds3 125m 4mm) tapedrive
that can hold 12 gig uncompressed and says that it can
compress up to 24. i think you know it all.
my thougts was, hey, let the hardware do the compression
so your system is not under such a heavy load.
I was going that way for a
Gerhard den Hollander wrote:
Since it's a linux box , you may want to look into using reiserFS.
I found that file access with Reiser is faster than ext2 (although nothing
shocking) esp. when going through a lot of smaller files in one swoop.
I formatted up the holding disk with a large
Ben Elliston wrote:
I have a couple of machines that are slow and poorly connected to my
tape server. In every instance, I happen to *know* that if these
machines were to appear first in the backup schedule, the backup would
finish more quickly.
Can you put in a delay time for all the
Wilkerson, Scott wrote:
greener pastures a few months ago. Since then, each time our remaining
system manager has upgraded a sun system to Solaris 8 it has begun failing
out of the backup set. I have made sure that I can rsh from our backup
amcheck gives this error:
WARNING:
Tanniel Simonian wrote:
Currently, I am running Amanda 2.4.2, with the Exabyte Mammoth 2 EZ17
loader, on a Dell Poweredge 2300, etc..
My exact configuration is as follows.
In my amanda.conf file i have:
snip
tpchanger "/usr/amanda/libexec/chg-zd-mtx"
tapedev "/dev/nst0"
changerdev
John R. Jackson wrote:
I've been running an `amdump' for about 16 hours now -- the following dump
(a level 0, as it happens) keeps happening over and over again. When I
reach 100%, it starts again!
Is this 2.4.2? If so, there's a known bug that we think is fixed in the
latest CVS
Denise Ives wrote:
the mail to: on the amanda.conf file-
Is there a command besides amdump - to test this?
org "daily" # your organization name for reports
mailto "[EMAIL PROTECTED]" #space separated list of operators at your site
amcheck will send e-mail on a failure if
Henning Sprang wrote:
I have a problem with amandas tapes.
5 days ago i got the last mail with a successful backup message:
--- snip ---
These dumps were to tape net-daily4.
Tonight's dumps should go onto 1 tape: a new tape.
--- snap ---
the day after that, the tape was changed to
77 matches
Mail list logo
