> (*) Dump may work fine for you a thousand times. But it _will_ fail under
> the right circumstances. And there is nothing you can do about it.
Let's generalise:
[any program and anything] may work for you a thousand times. Bit it
_will_ fail under the right circumstances. And there is nothi
Why not? Have you seen/had problems with recent versions of gnu tar, or
Sun's bundled tar? I have seen problems with versions of tars
interacting with each other, but not when using the same version/vendor.
I do find it a bit strange that you would trust dump over tar regardless
of the comme
On Fri, 27 Apr 2001, John R. Jackson wrote:
:>Or you could just use gtar
:
:As long as you don't mind altering the last access time of every file
:that is backed up.
That and tar of any flavor is not something I would willingly entrust
backups to.
Jamie Bowden
--
"It was half way to Riven
>As long as you don't mind altering the last access time of every file
>that is backed up.
... and as long as you don't mind waiting twice as long.
I would take that over the possibility of data getting munged. Plus,
you could run Fcheck after a backup to help out on filesystem
intrusion detection. At the very least I would use gtar on the
data you really need to keep safe until some better utility
comes out that's better under >2.4 ker
>Or you could just use gtar
As long as you don't mind altering the last access time of every file
that is backed up.
>-Dan
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Or you could just use gtar
-Dan
On Fri, 27 Apr 2001, Ben Hyatt wrote:
> Lately he's been making some interesting comments...
>
> mach kernel is crap, dump is stupid blah blah blah
>
> Seems to me that if he didn't create it, er steal it it's
> automatically 'crap' or 'stupid'.
>
> Ma
Lately he's been making some interesting comments...
mach kernel is crap, dump is stupid blah blah blah
Seems to me that if he didn't create it, er steal it it's
automatically 'crap' or 'stupid'.
Maybe he's still upset at Andrew S. Tanenbaum for
giving him 2 f's on operating system design way
Anyone read from the kernel.org newsgroup a message from Linus Torvald
about dump?
here is his message:
"Note that dump simply won't work reliably at all even in 2.4.x: the
buffer cache and the page cache (where all the actual data is) are not
coherent. This is only going to get even worse in 2.
>... My question is,
>how will I be notified that this is occuring? Increasing numbers of 'full
>dump of xxx delayed' messages followed by appearances of 'last full dump of
>xxx overwritten in y days' ? ...
I think that's correct.
> On a related note, if it all fits on one tape now and I ch
Assuming a stable configuration that is configured to use a single tape per
run, what happens as either more disks are added or the size of the data
grows? It seems to do a good job of delaying or promoting dumps to accomodate
fluctuations in the size of the disks, but if the total size is increa
On Fri, Apr 27, 2001 at 12:53:08PM -0500, John R. Jackson wrote:
> I'm not sure what this has to do with "Readline" as in your Subject:,
> but be that as it may.
Oopps... that was my original question, but I solved the problem with
(readline -> amrecover history functionality) on my own. For some
On Fri, Apr 27, 2001 at 02:15:47PM -0500, John R. Jackson wrote:
>I think this is saying that on host samba2 it could not take IP address
>10.0.1.2 and convert that back to a host name. That IP address should
>be the IP address of the machine that connected to samba2, i.e. your
>tape server (wher
> ERROR: samba2: [addr 10.0.1.2: hostname lookup failed]
I think this is saying that on host samba2 it could not take IP address
10.0.1.2 and convert that back to a host name. That IP address should
be the IP address of the machine that connected to samba2, i.e. your
tape server (where you ran a
This one has me a bit confused. Here are the hostnames
samba2 = 10.0.2.201
samba = 10.0.1.3
homer = 10.0.1.2
and this is the error I receive:
Amanda Backup Client Hosts Check
ERROR: samba2: [addr 10.0.1.2: hostname lookup failed]
^--
>... I would like to know whether the size of the "tapebufs"
>variable makes a big difference in performance. ...
I'm not sure what this has to do with "Readline" as in your Subject:,
but be that as it may.
I'm sure cranking up tapebufs makes a big difference on some systems.
I thought I'd give
>When i run amrecover on the client it returns:
>
>'AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
>amrecover: Unexpected server end of file'
Do you have amindexd and amidxtaped configured in inetd.conf or xinetd?
If you run "netstat -a | grep amandaidx" is something listening? W
First, thanks to Bart-Jan Vrielink for filling in the "where to look"
pieces of this. I knew they had to be there somewhere :-).
The only thing I would add to his comments is to make sure you have a
tape in the drive before trying the "mt" commands.
>Yes, because i read that the first scsi devi
In a message dated: Fri, 27 Apr 2001 11:09:12 EDT
Joshua Baker-LePain said:
>One of the reasons for the move to 2.2.19 is NFSv3 support (finally).
Well, IMO, the only and best reason for moving to 2.2.19 is to get
rid of the ptrace root exploit which exists in all kernels < 2.2.18,
and, AFAIK
I have a couple of questions regarding /etc/amandates.
1) What is the current purpose of /etc/amandates? I know that it is
updated on the client on every run. But are the contents actually
used? Or is it just information for the sysadm?
2) Why is amandates in /etc? My guess is because
>
> Please give the following patch a try and let me know if it solves the
> problem so I can update the sources. Note that except for making sure
> it compiles, it is untested as I don't have the hardware needed to easily
> do much else.
>
Cool. Thanks. Will do.
Carey
I just upgraded one of my RedHat 6.2 clients to 2.2.19 earlier this week
with no problems at all. I'm using AMANDA 2.4.1p1 (an oldie but a goodie),
with dump 0.4b19. The only other thing I see different is that I don't use
NFS. Is it possible that there are NFS packages that have to be updated whe
On Fri, 27 Apr 2001 at 9:28am, Albert Hopkins wrote
> I recently upgraded an amanda client (just the client, not the server)
> RedHat's recent kernel release for version 6.2 of their OS. The version is
> something like 2.2.19-enterprise... Anyway, one problem I had with the new
> kernel was loc
On Fri, 27 Apr 2001 at 10:51am, John Evans wrote
> When I upgraded my 6.2 box to 2.2.19 (with standard kernel, not
> enterprise), I recompiled the kernel with the only differing options being
> the enabling of NFS Version 3.0 filesystem support and server support.
I thought RedHat's 2.2.19 had N
When I upgraded my 6.2 box to 2.2.19 (with standard kernel, not
enterprise), I recompiled the kernel with the only differing options being
the enabling of NFS Version 3.0 filesystem support and server support.
Amanda hasn't complained about it...
On Fri, 27 Apr 2001, Albert Hopkins wrote:
>
>I
I recently upgraded an amanda client (just the client, not the server)
RedHat's recent kernel release for version 6.2 of their OS. The version is
something like 2.2.19-enterprise... Anyway, one problem I had with the new
kernel was lockd not working with NFS mounts, but I was able to resolve th
Greetings!
We are using Amanda to backup an NFS-server with roughly 100GB of data
and a DLT IV tape drive. We are now in the process of installing a
dedicated backup server to do the job running Debian Linux. We built
the latest stable Amanda (amanda-2.4.2p2) on it, which seems to be
working fin
On Fri, 27 Apr 2001, Juergen Knott wrote:
> But the /dev/nst0 device don't work, and i don't know why.
> I can put in a tape from hand in the tapedrive and can start ./amcheck Daily,
> and it's all ok.
> The second start of ./amcheck Daily is runningand running...and running.
> No messages
Hi, i think this is a typical question, but i can't use amrecover.
When i run amrecover on the client it returns:
'AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
amrecover: Unexpected server end of file'
There is an article in the FAQ-O-Matic but it doesn't help me.
Can you?
Than
29 matches
Mail list logo