Hi,
Please clarify the TCP socket connection between the
dumper and amandad. Let me know which one is acting as
a server and client. If we specify the entry in the
DLE like this 222.222.222.222 /home root-tar.
chunker: stream_accept: connection from
127.0.0.1.45601
dumper: stream_client:
Hi,
Please clarify the TCP socket connection between the
dumper and amandad. Let me know which one is acting as
a server and client. If we specify the entry in the
DLE like this 222.222.222.222 /home root-tar.
chunker: stream_accept: connection from
127.0.0.1.45601
dumper: stream_client:
Yes, it will do a read of the entire tape. There is a config file option
called amrecover_do_fsf that if set to true will fsf your tape to the
correct spot if your drive supports it, which is much faster than a linear
read.
I do have that set, and the drive finished up in about 1 hour. It
Contention on the disk, especially if it is also
used for other
tasks, and compounded if inparallel is set very high. RAID5
is often
not high-performance. I've seen some that do well on a
single read
or write, but seriously degrade with a few simultaneous operations.
Either way, if
Hello,
Ok, I have increased tapebufs to 80, I'm not really sure how high to
increase it though. I do have plenty of free ram.
I've increased it to 1024 on my PowerEdge 2850 with 8GB RAM.
Ok wow that's a huge increase. I'll keep trying smaller increments until I
get the error and then
On 2006-07-11 14:13, Jerlique Bahn wrote:
Just a thought: Were you sitting next to the tape drive while running the
above test? Did you see it stopping and re-starting over and over...?
Yes it is starting and stopping at frequent intervals. I recompiled amanda
with --with-buffered-dump to
I would like to use amverify to make
sure that data written to tape is also readable.
Could anybody clarify the following
issues:
1) What kind of errors can amverify
detect?
2) What kind of errors *cannot* amverify
detect?
3) Does it make sense to schedule amverify
after amdump every day?
4)
Nicola Mauri wrote:
1) What kind of errors
can amverify
detect?
2) What kind of errors *cannot*
amverify
detect?
3) Does it make sense to schedule
amverify
after amdump every day?
4) Should we trust amverify results?
Should we continue to check backup by periodically restoring
On Tue, Jul 11, 2006 at 09:07:32PM +0930, Jerlique Bahn wrote:
Yes, it will do a read of the entire tape. There is a config file option
called amrecover_do_fsf that if set to true will fsf your tape to the
correct spot if your drive supports it, which is much faster than a linear
read.
On Tue, Jul 11, 2006 at 08:14:19AM -0600, Graeme Humphries wrote:
Nicola Mauri wrote:
1) What kind of errors can amverify detect?
2) What kind of errors *cannot* amverify detect?
3) Does it make sense to schedule amverify after amdump every day?
4) Should we trust amverify results? Should
I'm a first-time amanda user, trying to backup a linux machine and a few
windows shares. I went through the tutorial at
amanda.zmanda.com/quick-backup-setup.html, modifying things to fit my
setup. The linux machine seems to be ok, but I'm getting some errors
with the SMB share.
The windows
On Tue, Jul 11, 2006 at 11:30:23AM -0400, Nathan Weston enlightened us:
I'm a first-time amanda user, trying to backup a linux machine and a few
windows shares. I went through the tutorial at
amanda.zmanda.com/quick-backup-setup.html, modifying things to fit my
setup. The linux machine
Example configuration (all of the files below need to be owned by user
amanda):
The AMANDA client software and Samba is installed on host
amanda_server_host. A share to be backed up called share is on PC
my-laptop. The share will be accessed via PC user testing and
password testing and using
On Tue, Jul 11, 2006 at 11:30:23AM -0400, Nathan Weston wrote:
I'm a first-time amanda user, trying to backup a linux machine and a few
windows shares. I went through the tutorial at
amanda.zmanda.com/quick-backup-setup.html, modifying things to fit my
setup. The linux machine seems to be
On Tue, Jul 11, 2006 at 08:46:12AM -0700, Pavel Pragin wrote:
Example configuration (all of the files below need to be owned by user
amanda):
The AMANDA client software and Samba is installed on host
amanda_server_host. A share to be backed up called share is on PC
my-laptop. The share
Matt Hyclak wrote:
Yes, you need to create an /etc/amandapass file with the appropriate
username/password combinations. man amanda for the details.
As for the second problem, I don't see anything in the .debug files that
gives me a clue. The permissions for /etc/amandates look like this:
On Tue, Jul 11, 2006 at 12:08:27PM -0400, Nathan Weston enlightened us:
Matt Hyclak wrote:
Yes, you need to create an /etc/amandapass file with the appropriate
username/password combinations. man amanda for the details.
As for the second problem, I don't see anything in the .debug files
On Tue, Jul 11, 2006 at 12:08:27PM -0400, Nathan Weston wrote:
But, I seem to have found the source of the problem -- I'm running
Fedora Core 4 which has SELinux enabled by default. When I turn that
off, amcheck runs with no errors.
Is there an easy way to make amanda play nice with
(expecting tape emcpd-007 or a new tape)
If I have the old tape loaded in the drive, I get an error about
the wrong tape loaded in the drive, but again I get nothing from
amcheck -sm.
read label `emcpd-006', date `20060711
Hi,
I am planning to develop the GUI for Amanda using Java
swings. I have two options . Please suggest me which
one is best.
1.Develop the new application for java and invoke the
planner and driver executable.Amanda code need not be
touched.
2.Convert the entire server code to Java and adding
* Jon LaBadie [EMAIL PROTECTED] [2006:07:11:11:59:30-0400] scribed:
On Tue, Jul 11, 2006 at 11:30:23AM -0400, Nathan Weston wrote:
snip /
As for the second problem, I don't see anything in the .debug files that
gives me a clue. The permissions for /etc/amandates look like this:
-rw-r-
Amanda Group
I ran the amtapetype from Amanda 2.5.0p2 last night, took about 6 hours to
complete the estimate:
Model: Quantum Superload 3 LTO-3 16 Tape Library.
define tapetype QS3LTO-3 {
comment Quantum Super Loader 3 LTO-3 16 tape library
length 448369 mbytes
filemark 6403 kbytes
speed
22 matches
Mail list logo
