On Thu, Mar 21, 2002 at 02:42:54PM +0800, Robert SHEN wrote:
I got the following error when I tried to test the amrecover command
After executed amrecover, it showed
Can't determine disk and mount point fr om $CWD
Normal,
CWD = current working dir
CWD is not one of the dirs in your disk
On Wed, Mar 20, 2002 at 04:56:00PM -0800, Anthony A. D. Talltree wrote:
Thank you all for the advice, I got through make successfully after setting
LD_LIBRARY_PATH.
However, after I've installed Amanda, there's a new problem. When I try
to run any amanda executables, I get the following
Help!
It seems that no matter what I set tapetype's length to (i.e., no matter
how small I say the tape is) amanda hits end-of-tape.
Please correct me if I am wrong but...
I thought that if I set the tapetype length to a conservative value,
then amanda would schedule only enough file-systems
On 21 Mar 2002 at 9:19am, [EMAIL PROTECTED] wrote
It seems that no matter what I set tapetype's length to (i.e., no matter
how small I say the tape is) amanda hits end-of-tape.
Please correct me if I am wrong but...
I thought that if I set the tapetype length to a conservative value,
Hi! I just started using amanda on Monday night. That night, something caused
my backup server to go off the network about halfway through the night, leaving
several disks unbacked up. On Tuesday night, however, this didn't happen. Yet
still, three disks didn't get backed up -- the dump
I can only advise you from Solaris side.
you can issue `ldd amanda_binary_name` on solaris, and see which library
it's linking. Then check and make sure all the library files exist in the
location it specifies.
Mark
- Original Message -
From: Mary Tan [EMAIL PROTECTED]
To: [EMAIL
Joshua Baker-LePain wrote:
On 21 Mar 2002 at 9:19am, [EMAIL PROTECTED] wrote
It seems that no matter what I set tapetype's length to (i.e., no matter
how small I say the tape is) amanda hits end-of-tape.
Please correct me if I am wrong but...
I thought that if I set the
Hello,
Two things;
On one hand, I have been thinking about running amanda once a week for
totals directly to tape, and the rest of weekdays without tapes so
incrementals are sent to holding disk, and then before next total on
friday with tapes, I do amflush...
Would that work nicely? I ask
Hi,
I successfuly backup files to my DLT (thanks the FAQ ;-)
When I want to restore, i got an problem :
amrecover: error reading tape: Connection reset by peer
extract_list - child returned non-zero status: 1
PS : I use Sparc/Solaris8 + Amanda version 2.4.2p2 + gtar1.13.19
Can
I did a reboot on the MP-RAS box to start with a clean slate and here is
what I've found so far.
amcheck results from tape server (relay):
relay# su amanda -c /usr/local/sbin/amcheck tig
Amanda Tape Server Host Check
-
Holding disk /amanda/hold: 17953520 KB disk
On Thu, 21 Mar 2002, Jon LaBadie wrote:
You won't. After running a while amanda will spread the level 0's over
all the dump days. So if your once a week tape now gets 40GB and your
daily incrementals now get 2, each will average about 8 GB daily.
Actually it's even better than that. Each
I'd like your insight into why I'm getting this error message
when dumping various disks:
/-- ahab /var/spool/mail lev 0 FAILED [/sbin/dump returned 1]
sendbackup: start [ahab:/var/spool/mail level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc
On Thu, 21 Mar 2002 at 10:22am, [EMAIL PROTECTED] wrote
I'd like your insight into why I'm getting this error message
when dumping various disks:
| DUMP: You can't update the dumpdates file when dumping a subdirectory
That's why. You're using dump, and trying to dump something that
Thanks for Reading!!
I am having some difficulties on understanding dumps. I'm coming
from an Arkeia and ArcServe background and some of the terminology is
confusing me. My question is, how do I configure the disklist file so I
don't hit EOT?? Am I on the right track here, or totally
On Thu, 21 Mar 2002 at 10:53am, Mark Schoonover wrote
RH 7.2 with approx 180 GB of disk space available, with about 25 GB used.
Two Exabyte Eliant 820s tape drives that are 8 GB native. ( I know, get
bigger drives!! I will... )
7GB native using 160mXL tapes -- that's what I use. 25GB used
On Thu, Mar 21, 2002 at 12:16:10PM -0600, Brandon D. Valentine wrote:
On Thu, 21 Mar 2002, Jon LaBadie wrote:
You won't. After running a while amanda will spread the level 0's over
all the dump days. So if your once a week tape now gets 40GB and your
daily incrementals now get 2, each
On Mon, Mar 18, 2002 at 04:21:22PM -0500, Don Potter wrote:
Thanks Jean...your idea works great..why hasn't this been
incorporated previously by chance
Because nobody reported this problem :-)
Jean-Louis
Jean-Louis Martineau wrote:
Hi Don,
Try this patch on the client, it
It depends on how often you require full backups. I was getting really low
tape utilization and big swings in amadmin 'balance' results, so I cut my
dumpcycle and runspercycle in half, and now I get more consistent tape
usage, and level 0 backups twice as often as a side benefit. Amanda's tape
Josh, Jenn Paul,
Thanks for the quick replies! I have found the error of my ways,
which leads me to a few more questions! The way I understand it is a 'dump'
is one cron job of amdump running. OK no problem there. Now, how do I
estimate how many filesystems I can backup to a single
On Thu, 21 Mar 2002 at 12:50pm, Mark Schoonover wrote
Thanks for the quick replies! I have found the error of my ways,
which leads me to a few more questions! The way I understand it is a 'dump'
is one cron job of amdump running. OK no problem there. Now, how do I
estimate how many
Sometimes 'dump' is one run of amdump, sometimes it is the 'dump' utility
that makes a backup of a filesystem. The number of filesystems that fit on a
tape will vary by their size and compressability. Your bump factors in
amanda.conf will also affect it.
Levels are degrees of incremental-ness
Excellent! Thanks. Can't see the forest for the trees.
On Thu, 21 Mar 2002, Joshua Baker-LePain wrote:
On Thu, 21 Mar 2002 at 10:22am, [EMAIL PROTECTED] wrote
I'd like your insight into why I'm getting this error message
when dumping various disks:
| DUMP: You can't update the
On one hand, I have been thinking about running amanda once a week for
totals directly to tape, and the rest of weekdays without tapes so
incrementals are sent to holding disk, and then before next total on
friday with tapes, I do amflush...
FYI, 2.4.3 (now in beta testing) has an autoflush
- i have to launch /usr/local/sbin/amrecover -d /dev/rmt/0 instead of
/usr/local/sbin/amrecover DailySet1
One point -- you should use a non-rewinding device name for anything
you do with Amanda. So that should be -d /dev/rmt/0n.
Also, I'm guessing, based on the device name, that you're running
This is why linking with -R is the better answer. ...
Absolutely. LD_LIBRARY_PATH has a lot of really evil side effects and
should be an absolute last resort.
And, of course, most or all instances of 'configure' that I encounter
fail completely ...
That's interesting.
Not long ago I
But now that you mention it, I suspect that
for Solaris we should add -R$dir in addition to -L$dir. Right?
Yep. I *think* a space is necessary after the R, but could be wrong.
Not long ago I discovered Amanda had a --with-libraries option that
took a list of directories and stuck them on the
I did a reboot on the MP-RAS box to start with a clean slate and here is
what I've found so far.
...
WARNING: edaf6.irs.sat: selfcheck request timed out. Host down?
...
(brought to you by Amanda 2.4.3b1)
...
SERVICE selfcheck
OPTIONS ;
GNUTAR /home/tp 0 OPTIONS
27 matches
Mail list logo
