Hello,
-Original Message-
From: Jon LaBadie [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 27, 2002 8:35 PM
To: Simas Cepaitis
Subject: Re: amrecover: No index records for disk for specified date
Any chance your disklist uses localhost rather than a hostname?
No, I use full
Hi all,
I've got amanda running successfully here for some time, but
periodically I have a problem where the tape runs out of space.
This generally happens when 2 of the larger partitions I have have
a full dump run on them at the same time. Is there any way to tell
Amanda to try not to do a
If I change tapetypes (ie, from a 30G config to a 20G one), can I expect
Catastrophy to occur?
--
Rob KeareyWebsite: http://apac.redhat.com
Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer
+61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Please not again this discussion...
it has been discussed in depth (if i remember right) last fall,
so please have a lock at the archives of that time.
Christoph
Uncle George wrote:
Ya, but didnt someone post that DUMP on linux can fail - if the
conditions are right? I think is was
Hi,
As i read the original message of Andre i would say he isn't
using tar for his backup, and his linux-dump does not like
the ext3-fs.
For using tar you have to put the line
programm GNUTAR
in your dumptype.
If this line is missing amanda defaults to dump to do the
backups.
And AFAIK there is
dear all,
i install amanda 2.4.3p3(both rpm and source have been tried) in a redhat
7.3 system. i have used amanda in other systems without and problem for 3
years. however, amanda seems do not work probably this time. amanda is able
to store all the data in the temp. disk space. however, when
I have a problem where my dumper is slow and the taper seems to be faster:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min)11:21
Dump Time (hrs:min)9:42
does this mean that there was a definitive conclusion?
Christoph Scheeder wrote:
Please not again this discussion...
On Tue, 28 May 2002 at 5:01pm, Robert Kearey wrote
If I change tapetypes (ie, from a 30G config to a 20G one), can I expect
Catastrophy to occur?
No. You may get some delayed level 0s, but it will work itself out.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke
On Tue, 28 May 2002 at 6:34am, Uncle George wrote
does this mean that there was a definitive conclusion?
Yup -- use what you are comfortable with and what your testing proves
works.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
On Tue, 28 May 2002 at 11:09am, Bartho Saaiman wrote
I have a problem where my dumper is slow and the taper seems to be faster:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run
On Tue, 28 May 2002 at 4:29pm, Bradley Marshall wrote
I've got amanda running successfully here for some time, but
periodically I have a problem where the tape runs out of space.
This generally happens when 2 of the larger partitions I have have
a full dump run on them at the same time. Is
Hi Joshua
I am using a dump disk and these backups are all local. I am using the
following compressions to ensure that the data actually fits on a disk.
define dumptype tgz-best {
program GNUTAR
options compress-best, index
priority high
dumpcycle 0
}
define dumptype
On Tue, 28 May 2002 at 2:47pm, Bartho Saaiman wrote
I am using a dump disk and these backups are all local. I am using the
following compressions to ensure that the data actually fits on a disk.
What's your hardware? What OS?
--
Joshua Baker-LePain
Department of Biomedical Engineering
Sorry, thats a general conclusion to most things in life.
Is there a situation(s) where DUMP can fail. If yes, why are there no
warning labels ( ie the probability of failure is 1 in 1billion ). If
NO, than can I see the proof that absolutely refutes Mr. Torvolds
statement.
/gat
Its
I am using:
[bartho@caepdc amanda]$ uname -a
Linux caepdc.cae.sun.ac.za 2.4.18-6mdk #1 Fri Mar 15 02:59:08 CET 2002
i686 unknown
[bartho@caepdc amanda]$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: DDYS-T36950M Rev: S96H
Type:
On Tue, 28 May 2002 at 2:59pm, Bartho Saaiman wrote
I am using:
Are you doing any sort of software RAID over all those disks? What's your
CPU speed?
Basically, I would run some tar tests (with gzip -- you can see the exact
command amanda runs in /tmp/amanda/sendbackup*debug) and see what
On Tue, 28 May 2002, Joshua Baker-LePain wrote:
On Tue, 28 May 2002 at 11:09am, Bartho Saaiman wrote
...
Filesystems Dumped1 1 0
The first thing to do, if at all possible, is to use a holding disk.
Given that your run time=dump time+tape time, it appears you
On Tue, 28 May 2002 at 3:14pm, Ulrik Sandberg wrote
On Tue, 28 May 2002, Joshua Baker-LePain wrote:
On Tue, 28 May 2002 at 11:09am, Bartho Saaiman wrote
...
Filesystems Dumped1 1 0
The first thing to do, if at all possible, is to use a holding disk.
no conlusion all people on this list agree to.
you can melt down the discusssion to the following:
1.)linux-ext2-dump is guaranteed to work correct if you have an
completely inactive and sync'ed filesystem. in other words:
if your fs is not mount at all or at least mounted read-only.
in all other
I think the warnings about dump are well documented in the man pages. The
man page for Solaris ufsdump, for example, recommends running dump in
single-user mode or on unmounted disks. I believe a similar warning is
provided for other versions of dump.
DavidM
-Original Message-
From:
A two-fold newbie (Amanda, Solaris) asks:
I am having some problems making amanda happy as a client on a Solaris 8
box. In a nutshell, I am seeing the inetd looping error discussed on
the list back in February. Basically, the problem is this:
1.) I have a Solaris 8 box configured as the tape
It was a quiet weekend -- Glad to see this list popping again.
A set-up problem that I sent last week is still with me, i.e amcheck
reports permission denied for the disks in disklist (client and server
are the same). Since last posting, I've tried changing disklist to specify local disk
access:
This linux-kernel mailing list posting has a short summary and
interesting update on the issue (that I had not seen before, anyway).
http://www.cs.helsinki.fi/linux/linux-kernel/2001-40/1002.htmlhttp://www.cs.helsinki.fi/linux/linux-kernel/2001-40/1002.html
Summary: kernels later than 2.4.11
Hi James -
I had the same problem back in June on a FreeBSD box -- the problem turned
out to be the tcp wrapper file (hosts.allow). I forgot to add the entry
for amandad.
Also check here:
http://amanda.sourceforge.net/fom-serve/cache/140.html
HTH!
-doug
--
Couldn't find this anywhere in the FAQ-O-Matic, but I'd welcome
a pointer if an answer is already floating around somewhere.
I'd like to keep all the dump images on disk even after they
get written to tape. My reasoning is that a large percentage
of the restore requests I get from my users could
Also Sprach Anthony A. D. Talltree:
Its interesting that I was unaware of this dilema ( the possible failure
of DUMP ) until it was posted on this list
It's mentioned in the second paragraph of Sun's ufsdump man page.
Despite all the FUD that's been parroted about dump over the years, by
Hi,
reffering to the mentioned Advisories I would like to know what
the latest stable version of Amanda is, that is not affected.
I thought that 2.4.2p2 is the latest, as mentioned a week or
so ago on this list. Below, only 2.3.0.4 is mentioned. But this
wasn't shipped with FreeBSD 4.5.
To follow up on my eariler problem, the checklist Doug pointed me to at
http://amanda.sourceforge.net/fom-serve/cache/140.html
was most helpful. It turns out that libreadline was not seen by the
amanda user on the client, and thus the amandad daemon was croaking. I
simply made sure
Removing their 2.3.0.4 port was the right thing for FreeBSD to do.
That version is what, 4 years old or more? I'd challenge the
often used assertion in the announcement. If it's often used
it's only because folks like FreeBSD have been shipping it long
after it should have been replaced with a
Hi thanks for your reply, yes I tried taring and untaring and it works.
Chris Marble wrote:
Andre Gauthier wrote:
I have recently installed Amanda on Red Hat 7.2 with ext3 fS. I am using
tar-1.13.25-4. I complied with group=backup. Ran amcheck and it did not
report any errors, but
Hi,
I am very new to amanda and this group. I have read the faq-o-matic list
but couldn't find the answer so I think I will ask here.
We have amanda 2.4.1 running on a Linux system. It is working fine so
far. Currently it only backs up the server that it sits on to a tape
On Tue, May 28, 2002 at 08:11:27AM -0400, Joshua Baker-LePain wrote:
Why not define a slightly smaller tapelength? That way amanda won't try
to put too much on the tape.
Are you using hardware compression? You may be assuming too much
compression.
I'm actually using software
On Wed, 29 May 2002 at 9:02am, Bradley Marshall wrote
On Tue, May 28, 2002 at 08:11:27AM -0400, Joshua Baker-LePain wrote:
Why not define a slightly smaller tapelength? That way amanda won't try
to put too much on the tape.
Are you using hardware compression? You may be assuming too
On Tue, 28 May 2002 at 3:45pm, jean wrote
but couldn't find the answer so I think I will ask here.
We have amanda 2.4.1 running on a Linux system. It is working fine so
far. Currently it only backs up the server that it sits on to a tape
everyday. Now we like to add one more
Hi,
Ok, so I have finally got Amanda to write a partition to tape.
Now I want to grab a file off of the tape.
I'm using Amanda-2.4.2p2 on FreeBSD.
After a successful amcheck and amdump, I run
# mt rewind
# mt fsf 001
to position the tape at the beginning of where I wrote daily001.
I'm
36 matches
Mail list logo
