Hi,
I think I have a planner/estimate problem.
I'm trying to create an amanda configuration that makes DVD-sized backup images
on disk of an 80GB file system. Once the images are made, I plan to burn them
to DVD-RW. Since a 4.7GB DVD can't hold 80GB of data, I made a largish number
of DLEs,
Ok, my problem was a low value of dtimeout. I bumped it to 3600 and now my
dumps are working correctly.
-Adam
Hi,
I have a problem with amverify. Or more correctly, I don't quite see why I
get the output I do:
[EMAIL PROTECTED] tmp]$ amverify bertha-us
No tape changer...
Tape device is /dev/nst0...
Verify summary to amanda
Defects file is /tmp/amanda/amverify.28777/defects
amverify bertha-us
Wed Jun
Joshua Baker-LePain writes:
Is this from a package, or did you compile amanda yourself? What
does your ipchains/tables setup look like?
My mistake --- local rebuild (that's the host):
build: VERSION=Amanda-2.4.2p2
BUILT_DATE=Sat Mar 9 17:43:45 PST 2002
BUILT_MACH=Linux
Problem solved, as determined by one dump having the client disks indexed so far.
The issue appeared to be that the client had two IP addresses (because
of a solution to another, temporary problem). Getting back to one IP
address returned the indexing.
Thanks for all the help, and I'll still
John R. Jackson writes:
Looking at the sendbackup.*.log files, I can see where the index
program is invoked. I don't see anything to indicate _why_ the
index files are so small.
Could you post one of those files? The symptoms seem to imply indexing
is enabled but the client just
John R. Jackson writes:
Certainly; I've attached one to the end of this message. (A gzip'd
original.)
Nothing was attached to your E-mail.
I _hate_ it when I have a brain fade like that. This time, it's
attached.
... Is it a good idea to go back and rebuild amanda? Could there
be
Adam Lins writes:
Are your backup images OK? If you pick some client/disk that is
having an index problem, what happens if you try something like
this:
mt -f /dev/whatever rewind
amrestore -p /dev/whatever client disk | gtar tf -
Here's what I tried:
[root@bertha
Joshua Baker-LePain writes:
On Thu, 4 Apr 2002 at 5:15pm, Adam Lins wrote
I have a problem with my index files. Each run, a gzip'd index
file is created. Each run, this file is about 20 bytes long. I
doubt gzip is compressing the information on 20+GB of files into
20 bytes
Joshua Baker-LePain writes:
Is this from a package, or did you compile amanda yourself? What
does your ipchains/tables setup look like?
My mistake --- local rebuild (that's the host):
build: VERSION=Amanda-2.4.2p2
BUILT_DATE=Sat Mar 9 17:43:45 PST 2002
BUILT_MACH=Linux
--- is that the right version?
GNU tar is v1.13.19; what else should I look for/at to diagnose this?
I'd like to know how to restore index files from tape, if anyone knows
how to do that...
Any help appreciated.
-Adam
--
Adam Lins www.bdti.com
Engineering Manager Ph
Someone mentioned before that it's possible to rebuild amanda indices,
if you have a good tar program.
Can someone please share the steps to do that? Our indices are
hosed... :-(
Thanks,
-Adam
I had this problem recently, and it turned out to be a bum network
interface. (Although your dump rate seems OK.)
Try doing an FTP of a large file between two of the servers that
failed; if a large (say, 10 MB) file takes more than a second or two
to transfer, you should consider if your network
13 matches
Mail list logo
