I set up Amanda on Friday to do an almost real backup job. I thought this
would be the final test before putting it into operation.
When I arrived at work this morning, I was somewhat surprised to see that
the Amanda run doesn't seem to have finished. amstatus daily gives me some
information, b
Looking with my newbie's eyes it seems that
Amanda is running well. Just very slowly.
And Amanda's log seems to indicate that the
problem is on the tape drive side.
The only thing strange that I see is the
following line which say that your drive is busy only 0,41% of the time:
> taper busy
Good point - and that is why I need help unravelling what it all means. My
question now would be: 0.41% of what? What would 100% of that something
represent? Constant streaming of data to tape from holding disk?
I've just left it alone to see if I get different results when subsequently
runni
[EMAIL PROTECTED] a écrit sur 17/07/2006
11:36:21 :
>
> Good point - and that is why I need help unravelling what it all means.
My
> question now would be: 0.41% of what? What would 100%
of that something
> represent? Constant streaming of data to tape from holding disk?
AFAIK, 100% would
On 2006-07-17 11:36, Joe Donner (sent by Nabble.com) wrote:
Good point - and that is why I need help unravelling what it all means. My
question now would be: 0.41% of what? What would 100% of that something
represent? Constant streaming of data to tape from holding disk?
of the total elapse
Well, one thing I've noticed is that the DLEs in question are the ones with
largest overall size:
+/- 8GB
+/- 9GB
+/- 32GB
All the other DLEs (except for the two I mentioned, which are in fact hidden
files) have successfully been written to tape and are less than
approximately 2GB in size...
When I execute the top command (Red Hat Enterprise 3) for user Amanda, I get:
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
2136 amanda15 0 948 948 836 S 0.0 0.0 0:00 1 amdump
2145 amanda15 0 1072 1072 844 S 0.0 0.1 0:02 1 driver
On 2006-07-17 13:32, Joe Donner (sent by Nabble.com) wrote:
and ps -fu amanda outputs:
UIDPID PPID C STIME TTY TIME CMD
amanda2136 2135 0 Jul14 ?00:00:00 /bin/sh /usr/sbin/amdump
daily
amanda2145 2136 0 Jul14 ?00:00:02 /usr/lib/amanda/driver daily
a
I thought I'll run amflush and see what happens. It outputs this:
Scanning /mnt/hdb1...
20060714: found Amanda directory.
Today is: 20060717
Flushing dumps in 20060714 to tape drive "/dev/nst0".
Expecting tape daily-1 or a new tape. (The last dumps were to tape daily-3)
Are yo
HI,
I need some clarification. I worked on amrestore ,
which we can retrieve the backup image from holding
disk or tape.
amrestore /dev/nst0
amrestore holdingdiskname
But I didn't understand the amrecover. I feel
amrecover is also developed for the same purpose.
Why we need two commands for the
ext I thought I'll run amflush and see what happens. It outputs this:
>
> Scanning /mnt/hdb1...
> 20060714: found Amanda directory.
>
> Today is: 20060717
> Flushing dumps in 20060714 to tape drive "/dev/nst0".
> Expecting tape daily-1 or a new tape. (The la
On Mon, Jul 17, 2006 at 05:57:45AM -0700, silpa kala enlightened us:
> I need some clarification. I worked on amrestore ,
> which we can retrieve the backup image from holding
> disk or tape.
> amrestore /dev/nst0
> amrestore holdingdiskname
>
> But I didn't understand the amrecover. I feel
> amre
Joe Donner (sent by Nabble.com) wrote:
FAILURE AND STRANGE DUMP SUMMARY:
minerva/usr/local/clients lev 0 FAILED [input: Can't read data: :
Input/output error]
And the holding disk still contains a folder with Friday's date and a 30GB
file for the DLE mentioned above.
Can you try cat'ting
Sorry, I've already went and deleted that file...
Alexander Jolk wrote:
>
> Joe Donner (sent by Nabble.com) wrote:
>> FAILURE AND STRANGE DUMP SUMMARY:
>> minerva/usr/local/clients lev 0 FAILED [input: Can't read data: :
>> Input/output error]
>>
>> And the holding disk still contains a
Kevin Till wrote:
Mike Allen wrote:
After some helpful email from Frank Smith off-list I have decided to
try a different approach to
slve my problem:
Here is an excerpt from my tape-server /etc/services file.
amanda 20080/udp #Dump server control
amandaidx 20082/tcp #Amanda i
I'm using the 3-hole label template.
Amanda version is 2.5.0p2 from zmanda on Fedora 4.
I'm taping to vtapes and tape spanning is turned on.
Though I seldom exceed one tape the dumps are still
split into tape_splitsize chunks.
It appears to me that the "File #" column in the report
is meaningless
Mike Allen wrote:
try configure with "--with-tcpportrange=5,50100
--with-udpportrange=512,1023 ..." and recompile.
Open the corresponding ports in the firewall setup.
The reason udp port 34932 was tried because Amanda cannot find a
reserved udp port that it can use.
The followin
Hi all,
If you plan attending upcoming LinuxWorld in San Francisco on August 14-17
or if you live in SF/Bay area, please stop by at Amanda Birds-of-a-Feather
session on:
Tuesday August 15, 2006, 6 - 7 p.m.
BOF1: Open Source Backup and Recovery Software Amanda
Room 301
The Amanda sessio
On Mon, Jul 17, 2006 at 09:32:01AM -0700, Mike Allen wrote:
> >
> The following occurred while compiling with the values you suggested:
>
>
> make install-data-hook
> chown operator /usr/local/man/man8/amanda.8
> chgrp operator /usr/local/man/man8/amanda.8
> chown operator /usr/local/man/man8/am
Kevin Till wrote:
Mike Allen wrote:
try configure with "--with-tcpportrange=5,50100
--with-udpportrange=512,1023 ..." and recompile.
Open the corresponding ports in the firewall setup.
The reason udp port 34932 was tried because Amanda cannot find a
reserved udp port that it can use
Mike Allen wrote:
Kevin Till wrote:
Mike Allen wrote:
try configure with "--with-tcpportrange=5,50100
--with-udpportrange=512,1023 ..." and recompile.
Open the corresponding ports in the firewall setup.
The reason udp port 34932 was tried because Amanda cannot find a
reserved udp
On Mon, Jul 17, 2006 at 03:58:17PM -0700, Mike Allen wrote:
> Kevin Till wrote:
> >Mike Allen wrote:
> >
> >>>
> >>>
> >>>try configure with "--with-tcpportrange=5,50100
> >>>--with-udpportrange=512,1023 ..." and recompile.
> >>>
> >>>Open the corresponding ports in the firewall setup.
> >>>
>
Kevin Till wrote:
Mike Allen wrote:
Kevin Till wrote:
Mike Allen wrote:
try configure with "--with-tcpportrange=5,50100
--with-udpportrange=512,1023 ..." and recompile.
Open the corresponding ports in the firewall setup.
The reason udp port 34932 was tried because Amanda cannot fi
RPMs and source tar ball are available for following platforms at
http://www.zmanda.com/downloads.html
- Red Hat Enterprise server 4,
- Red Hat Enterprise server 3
- Suse Linux Enterprise 9,
- Suse Linux Enterprise 10,
- Open Suse 10.0,
- Fedora Core 3,
- Fedora Core 4,
- Fedora Core 5 and
- Sourc
Je serai absent(e) du 18/07/2006 au 01/08/2006.
Je répondrai à votre message dès mon retour.
Hi,
I have put together the following srcipt
http://www.cs.ait.ac.th/~on/testgtar to help testing exclude patterns
in GNU tar.
This is a simple Perl script, that should run on any installation; but
I'd like to receive comments about the way I could improve it (this
not working being first candida
26 matches
Mail list logo
