Hi There!
root@fileserver:/usr/local/sbin ./amrecover Daily
AMRECOVER Version 2.4.2-19991216-beta1. Contacting server on fileserver ...
220 fileserver AMANDA index server (2.4.2-19991216-beta1) ready.
200 Access OK
Setting restore date to today (2001-03-12)
200 Working date set to
Am Montag, 12. März 2001 09:25 schrieben Sie:
Hi!
Can't determine disk and mount point from $CWD
amrecover
What is wrong?
In short NOTHING. When you start amrecover it assumes that you want to
recover directly into your current working directory. You need to
sethost, then setdisk. So,
"Casey" == Casey Scott [EMAIL PROTECTED] writes:
Casey Hi all. I am new to Amanda, so please forgive the newbie question.
Casey How do I blank a tape? amlabel -f ? When I attempted my first real
Casey backup, it finished sucessfully but was a mix of Level 0 and 1.
Casey
Sorry, I should I have clearer in my description. Yes, it is very
possible, in fact probable that a full Level 0 was performed before
killing amanda. So I am correct in thinking that all should be Level 0?
I will check the FAQ to flush the database.
Thanks
Casey
On 12 Mar 2001 21:48:23 +1100,
Does doing amlabel -f reset the tape? I only have one tape right now,
and I have completed the procedure for flush out the database. I would
like the tape to be reset also
On 12 Mar 2001 21:48:23 +1100, Ben Elliston wrote:
"Casey" == Casey Scott [EMAIL PROTECTED] writes:
Casey Hi
Hello,
I had a look at the amanda readme and help files but I have no idea
about
1. how to set up my tape drive (/dev/hdb as seen by dmesg). I have a
hdb: OnStream DI-30, ATAPI TAPE drive
2. how to do tests to check whether the configuration is working?
3. how to make the first fullbackup
Setting up the tape drive is done in amanda.conf, as well the backup
types and amount of tapes. amcheck [conf] will check your configuration
without doing a backup. You can also try a back up with the tape drive
set to /dev/null, amanda will go through everything w/o actually writing
to the tape.
dumpcycle 0
in your amanda.conf dumptype definition for the appropriate dumptype being
used
Dave Stracher
-Original Message-
From: Dr Prabhakar Ganapathy [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 12, 2001 10:01 AM
To: Amanda Users
Subject: Level of backup
Folks ,
I am trying
amcheck-server: could not get changer info: badly formed result from
changer: ""amanda.conf", line 32: configuration keyword expected"
and in line 32 in amanda.conf there was exactly the following keyword:
dtimeout 3600
Maybe you have a newline problem.
Hi all,
I've downloaded, compiled and installed 2.4.2 on my linux 2.2.16 (RH 6.1).
I've then used the old configuration from 2.4.1 with mtx and chg-zd-mtx
support for my HP SureStore 24x6.
amcheck give me the following error:
amcheck-server: could not get changer info: badly formed result
"Casey" == Casey Scott [EMAIL PROTECTED] writes:
Casey Does doing amlabel -f reset the tape? I only have one tape right now,
Casey and I have completed the procedure for flush out the database. I would
Casey like the tape to be reset also
You can relabel the tape if you want. Just to be
Hello all:
I recently had a dump die for reasons unknown on one of my clients. Future
dumps of this hard drive have NOT been sucessful (Data timeout reported in
amanda reports).
I logged into the box and discovered a number of processes owned by amanda
attempting to backup that disk. I was
"Alain" == Alain Muls [EMAIL PROTECTED] writes:
Alain 2. how to do tests to check whether the configuration is
Alain working?
Once you've configured Amanda, you run `amcheck conf' to test the
configuration. This is documented in the `amcheck' manual page.
To *really* test the
I logged into the box and discovered a number of processes owned by amanda
attempting to backup that disk. I was able to kill all but two:
root 29202 0.0 2.2 2672 1700 ?DMar08 3:26 gtar ...
root 30706 0.0 2.2 2672 1700 ?DMar09 3:41 gtar ...
I tried
This is an issue with mtx, and with the chg-zd-mtx script or amanda.
On Mon, Mar 12, 2001 at 08:52:55PM +0100, Riccardo Cozzani wrote:
Hi all,
I've downloaded, compiled and installed 2.4.2 on my linux 2.2.16 (RH 6.1).
I've then used the old configuration from 2.4.1 with mtx and
Hi all,
I encounter following error from my CNCBACK in 192.168.0.83
[root@CNCBACK DailySet1]# su backup -c "amcheck DailySet1 -c"
Amanda Backup Client Hosts Check
ERROR: office: [addr 192.168.0.83: hostname lookup failed]
Client check: 1 host checked in 0.109
Charlie!
Amanda Backup Client Hosts Check
ERROR: office: [addr 192.168.0.83: hostname lookup failed]
Client check: 1 host checked in 0.109 seconds, 1 problem found
(brought to you by Amanda 2.4.2)
But 'office' is really pingable in fact,
What does:
*
On Mar 12, 2001, Alexander von Homeyer
[EMAIL PROTECTED] wrote:
amcheck-server: could not get changer info: badly formed result from
changer: ""amanda.conf", line 32: configuration keyword expected"
Looks like the changer program is from some older release of Amanda.
--
Alexandre Oliva
"David" == David Lloyd [EMAIL PROTECTED] writes:
David If that doesn't work, try dig 83.0.168.192.in-addr.arpa
dig -x 192.168.0.83 is less of a mouthful. :-)
Ben
But how can I disable it, I meaning not using reverse DNS lookup?
--Charlie
- Original Message -
From: "David Lloyd" [EMAIL PROTECTED]
To: "Charlie Zhu" [EMAIL PROTECTED]
Cc: "Amanda Users" [EMAIL PROTECTED]
Sent: Tuesday, March 13, 2001 1:56 PM
Subject: Re: hostname lookup failed
Hmmm..
To disable it completely, I think you'd need to hack the source.
DSL
Oops!
To disable it completely, I think you'd need to hack the source.
Obvously you don't need to but I wouldn't if I were you :-)
DSL
--
CWA - Chin Waggers Association
"Let's sit around and complain about something.
Our topic for today is: ADSL...h...that `L'
stands for Linux
22 matches
Mail list logo
