To: Anthony Worrall [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: NFS mounted holding disk
Date: Tue, 17 Apr 2001 10:51:17 -0400
From: Paul Lussier [EMAIL PROTECTED]
X-Scanner: exiscan *14pWpZ-BM-00*1pxFlM.Ffuc*
http://duncanthrax.net/exiscan/
John,
Thanks for your further comments.
Thanks. Yes I have upgraded to 2.4.2p2 (the advfs.patch is not
applicable).
The advfs.patch does more than just fix problems with advfs. It also
deals with some Linux LABEL= issues in /etc/fstab. It may still not
apply to your setup, but just in case.
Hi,
I've looked at the man pages, the Faq-o-matic, etc and find very little describibg the
output of amstatus. Could someone give me some insight into the output?
...SUMMARY part real estimated
size size
partition : 49
estimated : 48
On 18 Apr 2001, Alexandre Oliva wrote:
On Apr 18, 2001, The Hermit Hacker [EMAIL PROTECTED] wrote:
error result for host hub.org disk da1s1a: Request to hub.org timed out.
[snip]
error result for host hub.org disk da0s1a: Request to hub.org timed out.
See how long it took in
Hi,
Throughout the dump schedule we can see the distribution of full
backups.
I use : dumpcycle 5 days
runspercycle 5
tapecycle 6 tapes
But I get the "unbalanced" backups over 6 tapes. One tapes is full,
and other tapes is just half full.
How to balance the
Here's a bad idea for you: Install Amanda server on both the NFS server and
the tape server; Run amdump on the NFS server using whatever configuration
you'd like, but don't let it dump to tape; use the tape server to back up
the NFS server at level 0 every time; after the tape server is done,
Hi
Unfortunately the NFS server is a NAS device on which I can not run amanda :-(.
Now if amanda could talk NDMP I could use the tape device on the NAS
server, but I would still need another box to run amanda and the data
would be going in and out of this box. Still that would be better than
Hi,
I am running Amanda-2.4.2p1 the server is Linux RH6.2 Client Sun E450,
Solaris 2.7
I have setup amanda, and it is backing up the system disk (I am using
tar, dump failed), but Amanda can not recognize the non system disks.
ERROR: myserver.mydomain.com: [can not access /dev/dsk/c0t1d0s6
Hi All!
Amanda, Version 2.4.2-19991216-beta1, runs a lot of time very well.
Now i have installed a new SCSI Hard Drive, and than i want to start amanda.
But amanda don't run.
Amanda Tape Server Host Check
-
Holding disk /dumps/amanda: 2095692 KB disk space
Juergen Knott wrote:
Hi All!
Amanda, Version 2.4.2-19991216-beta1, runs a lot of time very well.
Now i have installed a new SCSI Hard Drive, and than i want to start amanda.
But amanda don't run.
Amanda Tape Server Host Check
-
Holding disk /dumps/amanda:
Hello,
Just wanted to double check my configuration here.
What I want to do aside from my production backups is to have
a separate config for archival purposes.
I've checked the list archives and have done the following:
a)Made a separate config for archive
b)edited amanda.conf
I've looked at the man pages, the Faq-o-matic, etc and find very little descri
bibg the output of amstatus. ...
Does "etc" include "the chapter" at www.backupcentral.com/amanda.html?
I tried to describe some of it in there.
SUMMARY part real estimated
On Apr 18, 2001, "Ben Hyatt" [EMAIL PROTECTED] wrote:
I've checked the list archives and have done the following:
It looks ok to me.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student
3hrs, and 46min???
Right. Note that you did estimates of 11 separate disks, and the default
etimeout is 5 minutes per disk, which is 55 minutes, hence the timeout
errors. You need to crank that way up, or it might indicate there is
a problem with that client (bad disk, etc) that needs to be
Throughout the dump schedule we can see the distribution of full
backups.
I use : dumpcycle 5 days
runspercycle 5
tapecycle 6 tapes
But I get the "unbalanced" backups over 6 tapes. One tapes is full,
and other tapes is just half full.
How many times have you run
I have setup amanda, and it is backing up the system disk (I am using
tar, dump failed) ...
What do you mean by "dump failed"?
, but Amanda can not recognize the non system disks.
ERROR: myserver.mydomain.com: [can not access /dev/dsk/c0t1d0s6
(/dev/dsk/c0t1d0s6): No such file or directory]
I have an HP SureStore 12000E ...
how about the tapetype? The
default is HP-DAT, should this be modified? ...
That depends. Does the 12000E have DAT tape drives? More specifically,
what kind of tape drives does it have? Once you figure that out, go
to the FAQ at www.amanda.org and look for
Hi everybody,
I am backing up 3 systems using amanda. My /etc/dumpdates on 3 systems ( total 12
files)shows that al the files were backed up. But the amverify shows less file systems
than what /etc/dumpdates indicate( only 4 files).
I'd appreciate if anybody can tell what is happening.
Dear Sirs.
I already set up a HP SureStore 6x40i changer based tape device
backing up our main server, now I tried to install on a secondary
machine with a simple HP DAT drive a second piece of amanda, but
without success.
I followed the steps described in the really confusing manuals and
other
"John R. Jackson" wrote:
I have setup amanda, and it is backing up the system disk (I am using
tar, dump failed) ...
What do you mean by "dump failed"?
amcheck give an error, so does amdump
, but Amanda can not recognize the non system disks.
ERROR: myserver.mydomain.com: [can not
The config stuff looks OK to me, I would suggest leaving off the slot part
of the amlabel command. When I label tapes through chg-manual, I always just
`amlabel Config2 NextTapeName`, and if it asks me to put a tape in a
specific slot, I just re-insert the tape in the drive, wait for it to settle
DUMP: (This should not happen)bread from /dev/rdsk/c2t4d0 [block
-402651472]: count=-1216308224, got=-1.
This message typically indicates an active file system, i.e. the data
changed from underneath dump while it was running. You may have to change
the timing of when that data is hitting the
amcheck give an error, so does amdump
I figured that. Sheesh!
The question is, what was the error message, i.e. what **exactly** did
it say? Without that information, nobody is going to be able to guess
what was wrong.
/dev/dsk/c0t1d0s6 is /disc1
OK, then what do you get for these commands:
Hi,
I've been trying unsuccesfully to label a exabyte
160mXL tape on a EXB-8500 drive. I run amlable
as amanda user. backup server is solaris 2.6
with Amanda 2.4.2.
$ id
uid=301(amanda) gid=301(backup)
$ /usr/local/sbin/amlabel DailySet1 DailySet1-000
rewinding, reading label, not an amanda
On Wed, 18 Apr 2001, Bort, Paul wrote:
Hello.
Thanks for responding.
Our systems are all based on FreeBSD 4.3-RC3, I forgot to mention that.
well, the backup operator is 'operator' and this user has full read/write
permissions to the tape device (/dev/nsa0, /dev/nrsa0).
whenever I put any line
"John R. Jackson" wrote:
amcheck give an error, so does amdump
I figured that. Sheesh!
The question is, what was the error message, i.e. what **exactly** did
it say? Without that information, nobody is going to be able to guess
what was wrong.
That was the exact error msg from
Usually if AMANDA kicks out a tape during amcheck it is either because the
tape isn't labeled or isn't the labeled tape she was expecting (for example,
if you forgot to change the tape.)
With no offense intended, have you already amlabel'ed the tape you are
inserting during amcheck?
Could you
On Wed, 18 Apr 2001, John R. Jackson wrote:
3hrs, and 46min???
Right. Note that you did estimates of 11 separate disks, and the default
etimeout is 5 minutes per disk, which is 55 minutes, hence the timeout
errors. You need to crank that way up, or it might indicate there is
a problem
Hello all-
I'm new to list, having subscribed myself today because I'm having problems
with an Amanda backup system I'm administering for a co-worker while he's on
vacation. Here's the situation:
The system has been running fine for about a month. On monday, we added a
new machine to the
Hello Brian,
You are using an old version, tell your co-worker to upgrade :-)
In this old release, amanda will use all space on the holding disk
if the dump size is larger than the estimate. You can temporarily
create a dumptype for this disk with "holdingdisk no".
Jean-Louis
On Wed, Apr 18,
I'll tell him to upgrade when he gets back; I'm sure he'll be thrilled (it
worked FINE when I left...) ;-)
In the meanwhile, do you think setting the comprate to something like 95%
would help it estimate better, thus solving this problem? Or is there
another way to get it to make more accurate
Am Mittwoch, 18. April 2001 19:10 schrieben Sie:
Holding disk /dumps/amanda: 2095692 KB disk space available, that's
plenty amcheck-server: could not get changer info: error could not read
result from "/usr/local/libexec/chg-scsi" (got signal 11)
Odds are excellent that you have set the
32 matches
Mail list logo
