Hello Joshua,
Monday, December 03, 2001, 8:23:33 PM, you wrote:
JBL On Mon, 3 Dec 2001 at 9:56am, Stefan G. Weichinger wrote
1) Not all hosts to be backed up have 100M-NICs inside, so while
dumping them it slows down the connection to 100M-hosts.
(Getting about 10kB/s right now on the
Hallo Joshua,
Monday, December 03, 2001, 8:23:33 PM, you wrote:
JBL What is your runspercycle? Tapecycle *must* be = (preferebably )
JBL runspercycle. Otherwise, you may be overwriting the *only* full dump of a
JBL filesystem you have on tape. If that happens, you're SOL at restore time.
Perhaps it would help if I used the correct address, no?
Anyways, I found the problem. In the amanda home directory there is a .rhosts
file. I set that to be the same as the .amandahosts settings. I have CLI now.
Thanks again to all who replied!
Ross
-Original Message-
From:
1332.502 inparallel 4 bandwidth 600 diskspace 12167192 dir OBSOLETE
datestamp 20011204 driver: drain-ends tapeq
LFFO big-dumpers 1
driver: result time 1332.502 from taper: TAPER-OK
driver: send-cmd time 1332.517 to dumper0: FILE-DUMP 00-1
/mnt/SCSI4/am_hold/20011204/ra._etc.1 ra /etc 1 2001:11:28
On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote
06573011000/./security/dev/audio
06573011000/./security/dev/fd0
06573011000/./security/dev/sr0
06573011000/./security/dev/st0
06573011000/./security/dev/st1
(these are just the contents of /etc on each host). The version of tar on
the
On Mon, 3 Dec 2001 at 4:53pm, José Vicente Núñez Zuleta wrote
I upgraded the dump version but then i got the
following problem:
lnxsrv0001:/dev/hdc1 1 [/sbin/dump
returned 3] (17:48:39)
lnxsrv0001:/dev/hdc6 1 [/sbin/dump
returned 3] (17:48:23)
On Mon, 3 Dec 2001 at 11:56am, Rafe Thayer wrote
Hi Folks,
Another question for ya. After I did an amdump to test out dumping our
disks to tape, I tried to do an amrecover to see if restoring the data
would work. It seems to work for our linux machines, but the solaris box
has some
Hi,
On Mon, Dec 03, 2001 at 07:47:25AM -0900, Jennifer Peterson wrote:
Good morning,
I've been trying for the past week to install stctl on my Sun 2.8
system. This has included installing the Sun compiler and following
every piece of advice that I could find on this list and through
Hallo Joshua,
Tuesday, December 04, 2001, 2:59:03 PM, you wrote:
JBL I'm wondering if you're seeing lots of collisions when the 10M clients
JBL start dumping.
I don´t know how to use netstat correctly. How should I look for the
collisions ?
JBL I believe (taking into account your next mail)
Hello,
--- Joshua Baker-LePain [EMAIL PROTECTED] escribió:
On Mon, 3 Dec 2001 at 4:53pm, José Vicente Núñez
Zuleta wrote
I upgraded the dump version but then i got the
following problem:
lnxsrv0001:/dev/hdc1 1
[/sbin/dump
returned 3] (17:48:39)
A moment of introduction:
I'm the UNIX administrator for a branch of Science Applications
International Corporation. I've been using amanda quite happily now for ~6
months to feed an HP SureStore Ultrium 1/20 ( that's 2TB native ) backing up
a data center of RH7.1 and HPUX 10.20 boxen.
The
Hello,
I am seeing some strang behavior with my amanda setup. I have an dump
that has a dumpcycle of 7 days, yet seven days has passed and I have not
see a full dump. In fact my last full dump was on Nov 20. I have had a
successful incremental dump every day since, but no full. Below are the
On Tue, 4 Dec 2001 at 3:14pm, Stefan G. Weichinger wrote
Tuesday, December 04, 2001, 2:59:03 PM, you wrote:
JBL I'm wondering if you're seeing lots of collisions when the 10M clients
JBL start dumping.
I don´t know how to use netstat correctly. How should I look for the
collisions ?
On Tue, 4 Dec 2001 at 10:51am, [EMAIL PROTECTED] wrote
I am seeing some strang behavior with my amanda setup. I have an dump
that has a dumpcycle of 7 days, yet seven days has passed and I have not
see a full dump. In fact my last full dump was on Nov 20. I have had a
successful
Redhat 7.0 w/tar 1.13.17
Solaris 8 w/tar 1.13.19
amanda 2.4.2p2
I have an exclude list that looks like:
/proc
/devices
/tmp
/temp
/var/lock
/var/spool/postfix/private
/spool/postfix/private
/var/tmp
/lost+found
*..LCK
But amrecover tells me that amanda is still backing up these
directories.
I was running dump on 7.1, and had nothing but problems. I was told that
Linus himself came out on the list and claimed that people should stop
expecting reliable behavior from dump, as there were things being changed
in the kernel that might make it unreliable. I switched to GNUtar, and
have
Amrecover must be run as the root user (after all, the amanda user can't
write those files!). In the amanda user's home directory there will be (or
you can create) a .amandahosts file. Make sure that the root user is
listed there instead of the amanda user for purposes of the amrecover. And
Hello,
Just a follow up to the email I sent out earlier. I determined that I was using the
wrong dumptype in my disklist file. Now, instead of not being able to read a header,
amrestore gives me the following:
amrestore: 0: skipping start of tape: date 20011204 label Eatoni-01
amrestore: 1
I do not have anything defined for runspercycle. What messages are
your refering to? I have the mails for each day.
Andrew
On Tue, 4 Dec 2001, Joshua Baker-LePain wrote:
On Tue, 4 Dec 2001 at 10:51am, [EMAIL PROTECTED] wrote
I am seeing some strang behavior with my amanda setup. I have
On Tue, 4 Dec 2001 at 2:42pm, [EMAIL PROTECTED] wrote
I do not have anything defined for runspercycle. What messages are
your refering to? I have the mails for each day.
OK, runspercycle defaults to be the same as dumpcycle. Are you running
amdump every night?
Are there any messages in
On Tue, 4 Dec 2001 at 10:10am, Stephen Carville wrote
I have an exclude list that looks like:
/proc
/devices
/tmp
/temp
/var/lock
/var/spool/postfix/private
/spool/postfix/private
/var/tmp
/lost+found
*..LCK
But amrecover tells me that amanda is still backing up these
Indicates
Hello!
I'm using amanda for tapeless operation (using file: types) and write
the data created on DVD. When I try to resore directly from DVD using
amrestore, it complains that the DVD is mounted read-only. I've seen
that it tries to open the info file in read-write mode, is this really
needed?
At 01:41 PM 12/4/2001 -0500, Christopher S. Dahn wrote:
I was running dump on 7.1, and had nothing but problems. I was told that
Linus himself came out on the list and claimed that people should stop
expecting reliable behavior from dump, as there were things being changed
in the kernel that
Hello!
I'm using amanda for tapeless operation (using file: types) and write
the data created on DVD. When I try to resore directly from DVD using
amrestore, it complains that the DVD is mounted read-only. I've seen
that it tries to open the info file in read-write mode, is this really
needed?
On Tue, 4 Dec 2001 at 4:40pm, Dan Swartzendruber wrote
At 01:41 PM 12/4/2001 -0500, Christopher S. Dahn wrote:
I was running dump on 7.1, and had nothing but problems. I was told that
Linus himself came out on the list and claimed that people should stop
expecting reliable behavior from
Hi
At first I thought tar failed as given below because the files were changing.
But apparently, only one directory (/grove1) keeps failing. Its always the same
message - the only difference are the levels. It seems to me to be too much of a
coincidence that this directory is the only one to
unsubscribe [EMAIL PROTECTED]
I'm running Amanda-2.4.1p1, with a 32 day tape cycle, tapes
labeled daily01 to daily32 (config name is daily)
Recently, my drive ate daily32. I continued to run without
problems until today when I did what I thought would be the
Right Thing:
$ amrmtape daily daily32
And then with a new tape:
$
28 matches
Mail list logo
