Hi.
You wrote in the Amanda FAQ:
``This can be wasteful, specially if you have a small amount of data to back
up, but expensive large-capacity tapes. One possible approach is to run
amdump with tapes only, say once a week, to perform full backups, and run it
without tape on the other days, so
Hmm,
Favor #1: can the reply to adress on the digests be set to @amanda.org ;)
* [EMAIL PROTECTED] [EMAIL PROTECTED] (Fri, Jan 19, 2001 at 06:34:02AM
-)
First off, thanks to all who answered my priorities question. ;)
Second.
I noticed when looking through the logs that the *dumper*
Hi!
Iam just beginning to work with amanda!
At the last days there were no problems, but this mail of the daily
amanda backup just shows me a lot of failures which I have never seen!
beethoven /home lev 1 FAILED [dumps way too big, must skip incremental dumps]
zeus /home1 lev 1
Hi people,
How can I check which levels of Amanda will made in backup
tape? (what kind of command i can use to do that? exist any?)
Thanks in advanced,
Diogo Batista Salgueiro
Curitiba - Paran - Brasil
Could it be that the firewall gets stricter rules at night? I doubt
the problem was an actual time-out, since three minutes is just too
short a time for an estimate time-out.
The firewall does not change rules. I, again, had the same exact
problem last night. Can I turn on some debugging
At 07:23 AM 1/19/01 +0100, Jens Bech Madsen wrote:
Ben Elliston [EMAIL PROTECTED] writes:
Is there a way for Amanda to eject the tape at the end of a run so that I
can simply remove it each day (and to indicate that the tape run has
actually completed)?
Or should I just run `mt
On Fri, Jan 19, 2001 at 08:53:49AM -0600, Andrew Robinson wrote:
At 07:23 AM 1/19/01 +0100, Jens Bech Madsen wrote:
Ben Elliston [EMAIL PROTECTED] writes:
Is there a way for Amanda to eject the tape at the end of a run so that I
can simply remove it each day (and to indicate that the
Ben Elliston wrote:
Hi.
You wrote in the Amanda FAQ:
``This can be wasteful, specially if you have a small amount of data to back
up, but expensive large-capacity tapes. One possible approach is to run
amdump with tapes only, say once a week, to perform full backups, and run it
without
On Fri, Jan 19, 2001 at 09:59:57AM +0100, Gerhard den Hollander wrote:
Hmm,
Favor #1: can the reply to adress on the digests be set to @amanda.org ;)
* [EMAIL PROTECTED] [EMAIL PROTECTED] (Fri, Jan 19, 2001 at
06:34:02AM -)
unsubscribe from [EMAIL PROTECTED] and
subscribe to [EMAIL
Hello all ,
I have been trying to get amanda to work for the last week , to no
avail. I am sure it is something simple.
I worked out all of the installation and configuration issues , however
here is the problem.
I am backing up from a centralized backup server , all of the clients
"sync"
More on the same story .. Im getting there :)
Seems that the bottleneck indeed was the gzip process ..
I've changed my disklist/amanda.conf to no longer compress the images, and
instead rely on the hardware compression in the LTO drive
(trading tape space for speed ;) ), and the results are
On Tue, 16 Jan 2001, Bruce Ferrell wrote:
Looks like the network dropped out
No, that's not the case. The same behaviour happens consistantly all
the time, only with that computer (not the other 5 which are on the
same hub which can access the network fine (it's running a mail
server, httpd,
Some people would consider fitting 30Gb on a 20Gb tape optimistic. Here's
quick list of things to check that might help:
1. Are you using either software or hardware compression? If you are using
both, you could wind up with backups taking more tape than expected.
2. Is/was the tape drive in
I want to set up amanda on a solaris 7 system. the problem that I am
having is that I can't figure out how to reference the disk drives. In
SunOS you could use sd3g or sd1a or whatever. with Solaris, they are
reference like c0t0d0s1
Amanda doesn't seem to like this.
I have also tried giving
Hello!
Thank you to those who responded to me so quickly!
After having it confirmed that either notation (c0t0d0s6 or /usr) *should*
work, I went back and did some experimentation and found that amanda refused
to work because I had blank lines after the lines that specified the disk!
Anyway,
We've been using amanda to backup 2 FreeBSD boxes and 5 PeeCee's for about
two years now. But it was time to upgrade our Unix boxes as well as the
Operating Systems. I managed to upgrade the two FreeBSD boxes to
FreeBSD-4.1.1 Release and FreeBSD 4.2 Release, and have the main "amanda"
box
In addition to what Paul Bort said ...
I am backing up from a centralized backup server , all of the clients
"sync" content to the server , and the backups are performed from a dump
directory on the server. ...
Is there some reason you're not letting Amanda run directly on the
clients? What
How can I check which levels of Amanda will made in backup
tape? (what kind of command i can use to do that? exist any?)
It's difficult to know what level Amanda will use in the next run.
That depends on how much data there is to be backed up.
If you want to know what levels it did on an
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!
dublin:sda4 0 1878319k dumping 1679872k (89.43%)
(8:08:27)
This file system is too large
... this mail of the daily
amanda backup just shows me a lot of failures which I have never seen!
beethoven /home lev 1 FAILED [dumps way too big, must skip incremental du
mps]
This says that after Amanda had gathered all the dump size estimates,
and kept reducing the size as much as it
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 sources. If you can't or don't want
I will do some more debugging... In the meanwhile, if nobody
can figure out what it is, I would also appreciate advice on what info
to gather, so that you can better help debug.
Attach a debugger to the sendbackup process and use "where" to get a
call stack. Ditto for the dumper it is
I've found that when gzip is running on my own, and clients systems it's
usually using 95+% of one cpu, which isn't a problem for us or them because
the machines either have a spare cpu, or aren't doing anything at the time.
more of a problem for bigger sites where your server will always be
Hi there,
I using amanda to backup several servers, but now some of my disks
started signaling the following error. Those are vx filesystems of
an HP 10.20, I have done fbackup on those filesystems and I worked.
I also tried to switch from compressed to noncompressed but with no
luck. Has
I've got a 2.4.2 amanda server using samba to backup the C:\ drive
of an NT workstation. That user's machine has C:\ set as one 8gig
partition, and it's 6gig full. My tapes have just over 4 gig
capacity compressed. (Of course there are many other partitions in this
backup set, but those
On Thu, 18 Jan 2001, Hurf Sheldon wrote:
Our amanda was set up by set up by someone who has moved on.
Well now that would be me...
1: When we move the Overland to the FreeBSD PC and run amlabel, we get
errors in the system log file and the DLT goes out to lunch - we setup
an HP
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
cmarble wrote:
Is this 2.4.2? If so, there's a known bug that we think is fixed in the
latest CVS sources. If you can't or don't want to get them, there will
be a 2.4.2p1 shortly, or ask me offline and I'll send you the patch.
Will I only have to update my 2.4.2 installation on
Ben Elliston wrote:
Is there a way for Amanda to eject the tape at the end of a run so that I
can simply remove it each day (and to indicate that the tape run has
actually completed)?
Or should I just run `mt offline' myself?
Don't run "amdump ..." directly. Instead, write a script that
29 matches
Mail list logo
