>To: Jim Harmon <[EMAIL PROTECTED]>
>cc: [EMAIL PROTECTED]
>Subject: Re: NFS mounted holding disk
>Date: Fri, 13 Apr 2001 12:11:29 -0500
>From: "John R. Jackson" <[EMAIL PROTECTED]>
>X-Scanner: exiscan *14o7BR-Mv-00*QV3l7VyiBh2*
http://duncanthrax.net/exiscan/
>
>>Using a NFS mounted holdin
John,
Thanks for your comments.
>>... I will try upgrading to 2.4.2.
>
>Note that the current release is 2.4.2p2, and there is a patch beyond
>that on the patches web page which may or may not apply to your
site.
Thanks. Yes I have upgraded to 2.4.2p2 (the advfs.patch is not
applicable).
>>.
In a message dated: Tue, 17 Apr 2001 10:42:13 BST
Anthony Worrall said:
>One reason would be the NFS server has a 1Gb interface and the clients and
>tape server have only 100Mb.
Okay, so now you're saturating the 100Mb interface on the tape server
twice? I still don't see the advantage in thi
On Monday 16 April 2001 23:55, you wrote:
> ...
> > obsd.athome:wd1a 0 28128k writing to tape
> > obsd.athome:wd1d 0 92416k dump done, wait
> > for writing to tape
>
> If it says it's writing to tape, and the tape leds aren't flashing, I
> suppos
>In fact I would like it if the clients could dump directly to the NFS mounted
>holding disk rather than via the tape server.
Seems to me a better plan would be to run amdump on the NFS server and
make taper the remote piece. This keeps the single driver controlling
all the pieces (and not floo
>Thanks. Yes I have upgraded to 2.4.2p2 (the advfs.patch is not
>applicable).
The advfs.patch does more than just fix problems with advfs. It also
deals with some Linux LABEL= issues in /etc/fstab. It may still not
apply to your setup, but just in case.
>My reading of the amanda man page for
>But I can write tar archives to the tape drive as well as dd and dump
>to it too.
But you can't do that as fast as Amanda with intermittent file mark
ioctl's mixed in. The dd test is just a first estimate at what Amanda
does.
If taper is stuck and you can't kill it, that's a kernel driver iss
Anthony Worrall <[EMAIL PROTECTED]> writes:
> >From: "John R. Jackson" <[EMAIL PROTECTED]>
> >
> >>Using a NFS mounted holding disk doesn't seem possible ...
> >
> >I would consider that a feature :-). Why in the world would you drag
> >a bunch of dump images across the network to an Amanda serv
Right now I reference all my disks by device name (e.g. 'hda1'). If
possible, I'd like to change this to mount point references (e.g. '/').
The kicker is, of course, that I'd like to do this without losing my index
and curinfo data. Can I simply:
1) Change the references in the disklist, and
2
How can I do a full dump on all file systems, everyday?. currently I use the
>following in the amanda.conf file. But it does not seem to be working.
define dumptype global {
Command 'define' not recognized.
comment "Global definition
>Right now I reference all my disks by device name (e.g. 'hda1'). If
>possible, I'd like to change this to mount point references (e.g. '/').
>The kicker is, of course, that I'd like to do this without losing my index
>and curinfo data. Can I simply:
>
>1) Change the references in the disklist,
On Tue, 17 Apr 2001 at 2:48pm, John R. Jackson wrote
> I don't think this is sufficient (sigh). As I recall, amrecover runs
> the equivalent of an "amadmin find" and that looks in the
> log.MMDD.NN files for information. So you would also need to change
> them (I'd use Perl :-).
I just kn
>Can anybody tell me what I am doing wrong?.
Not without you telling us why you think it's not working.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Any compatibility between p2 and p1? I want to upgrade our server to p2
(well, we got a new backup server and I'm getting amanda going on it) and
I don't want to have to rebuild all the clients.
Mark
--
http://www.mchang.org/
http://decss.zoy.org/
>Any compatibility between p2 and p1? ...
There should not be any compatibility problems between the two.
>Mark
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Running Amanda 2.4.2pl1, I'm seeing the following message while its trying
to get the estimate for one machine:
error result for host hub.org disk da1s1a: Request to hub.org timed out.
error result for host hub.org disk da4s1a: Request to hub.org timed out.
error result for host hub.org disk da3
On Apr 18, 2001, The Hermit Hacker <[EMAIL PROTECTED]> wrote:
> error result for host hub.org disk da1s1a: Request to hub.org timed out.
[snip]
> error result for host hub.org disk da0s1a: Request to hub.org timed out.
See how long it took in /tmp/amanda/sendsize.debug, and compare it
with the d
17 matches
Mail list logo
