On Tue, Jul 17, 2001 at 12:49:49PM -0500, John R. Jackson wrote:
* Did you set the TAPE environment variable before doing the rewind
and fsf commands? If so, what to? For instance, if it's set to
a rewinding device name (e.g. /dev/rmt/0b), the fsf would advance
out several
I keep getting reports like the attached running amanda on aix 4.3.3. I've setup a
samll (3 gig) holding disk, and configured amanda to use a 1gig chunk size (the
filesystem is not large file enabled, which means a 2-gig limit on aix). The
filesystems on fasttrans are using aix backup, but
Hi John,
thank You for the patch. Looks like it helped. At least amrecover works as
expected. I'll do more detailed test tomorrow.
reg's
Oleg
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of John R. Jackson
Sent: Tuesday, July 17, 2001 8:44 PM
To:
This is different from .rhosts: If you leave off the username, it will
accept any user.
Thanks for pointing that out. I didn't read the .rhosts man page
well enough.
I've updated the .amandahosts description in amanda(8) as follows:
.amandahosts
This is essentially the same as
I keep getting reports like the attached running amanda on aix 4.3.3. ...
fasttrans /egate lev 1 FAILED [data write: File too large]
...
EFBIG (File too large) can also be returned if the write exceeds
the process' file size limit. I'm not real conversant with AIX, but
I think the command
HI John:
I tried to use the patch that you sent to me and this the message that
i got
tanguy% patch /Local/Users/sandra/stream_client.diff
can't find file to patch at input line 8
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
[ XFS mailing list removed from Cc list. --JJ ]
I've patched amverify (2.4.2p2) to do the trick. It cds to /tmp/amanda
(on XFS) prior to start xfsrestore being fed by the xfsdump image: ...
Ok, it's not the nice, general, amverify.in,
testing-for-OS-and-xfsrestore solution but it works for me.
What version of Amanda?
Pretty much the latest, 242p2, I think.
The netusage would not affect planner. And I don't think inparallel is
involved, either. I'm pretty sure planner ships a sendsize request to
all the clients at the same time and doesn't pay any attention to either
of
Hi:
I ran amrecover using amanda-2.4.2p2 without any udp or tcp ranges and
was fine (i guess). I tried to recover a directory database . I
used the directory that i created in my area
/Local/Users/sandra/restore. From there I ran
/usr/local/sbin/amrecover -C miro_daily -s
Some tars are returning with an error (sort of).
---
? gtar: ./dsmith/.xsession-errors: file changed as we read it
| Total bytes written: 163194880
? gtar: Error exit delayed from previous errors
sendbackup: error [/opt/gnome/bin/gtar returned 2]
---
Also:
? gtar: ./net/freeware: Cannot
... I load the tape manually
and amanda started to read from the tape. After many hours ...
You might be able to speed up the restore by pre-positioning the tape.
Use amadmin config find host disk (or amtoc, etc) to find out
what file on the tape has the image. Then after mounting the tape,
Some tars are returning with an error (sort of).
---
? gtar: ./dsmith/.xsession-errors: file changed as we read it
| Total bytes written: 163194880
? gtar: Error exit delayed from previous errors
sendbackup: error [/opt/gnome/bin/gtar returned 2]
I *think* (but am not positive) that the
Can I change disklist entries in the middle of a dump cycle without
invalidating information?
No, don't do that. You shouldn't even change disklist if there are files
left on the holdingdisk to flush.
Hi,
I have recently installed amanda and have not as yet managed to successfully
obtain a backup to my satisfaction. I have a backup server (Helios) which
also has an amanda client and a remote amanda client (Apollo). The tape
device is a SUN L9 (DLT8000 with autochanger) 40GB (/dev/rmt/1n).
14 matches
Mail list logo
