Radu Filip [EMAIL PROTECTED] writes:
Hello, Johanness!
Thank you very much for your answer.
On 27 Feb 2001, Johannes Niess wrote:
1) Amanda sets options for gnutar to stop at partition boundaries.
From the logs I see that it's not this one...
2) If your holding disk is on the
hello,
this question was already posted yesterday, but I
got no answer! ;)
1/
When I try to run 'amrecover' to check file index
recovery, here's what it says:
bash$ /usr/local/amanda/sbin/amrecover -C daily1
AMRECOVER Version 2.4.2. Contacting server on *
amrecover: Unexpected
* Alexandre Oliva [EMAIL PROTECTED] (Tue, Feb 27, 2001 at 10:36:20PM -0300)
On Feb 27, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote:
What is the easiest way to debug sendsize ?
Get the request from amandad.debug and feed it to sendsize's stdin.
OK, full output of the amandad.debug is
* Alexandre Oliva [EMAIL PROTECTED] (Wed, Feb 28, 2001 at 09:22:10AM -0300)
On Feb 28, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote:
GNUTAR sda6 0 1970:1:1:0:0:0 -1 exclude-list=/usr/local/lib/amanda/exclude.gtar
GNUTAR sda6 0 1970:1:1:0:0:0 -1
On Feb 28, 2001, Gerhard den Hollander [EMAIL PROTECTED] wrote:
* Alexandre Oliva [EMAIL PROTECTED] (Wed, Feb 28, 2001 at 09:22:10AM -0300)
I did ^C a test amdump for this config during the estimate phase.
Could it be that amandates is corrupt ?
Well, it might be, but it certainly wouldn't
did you check /tmp/amanda/amrecover.*.debug ?
amrecover.debug shows only 1 line:
amrecover: debug 1 pid 16190 ruid 0 euid 0 start time Wed Feb 28
12:13:55 2001
And are you running this on the server ?
if not, you have to specify the server
amrecover -C daily1 -s mytapeserver
I am getting a results missing message from amanda as well as the date
is being reported to be "BogusMonth 0, 0". I ran amcheck and it went
through fine. I am including the report amdump generates in the hopes
someone might suggest a way to troubleshoot. Thanks in advance...
*** THE DUMPS DID
* Aleksandr Vladimirskiy [EMAIL PROTECTED] (Wed, Feb 28, 2001 at 09:36:12AM -0500)
I am getting a results missing message from amanda as well as the date
is being reported to be "BogusMonth 0, 0". I ran amcheck and it went
through fine. I am including the report amdump generates in the hopes
they aren't really duplicate entries - they are different hosts with the
same disk designation being backed-up. Thank you for the help, but
amreport says it can't open disklist... what do I do?
Alex
Gerhard den Hollander wrote:
* Aleksandr Vladimirskiy [EMAIL PROTECTED] (Wed, Feb 28, 2001 at
I'm trying to get my first tape changer working, and I'm a little confused.
It appears that I need to use the chg-zd-mtx scriptm but the version of mtx
that I have is used like this:
mtx -f /dev/sg0 next
for instance. Now it appears to me that chg-zd-mtx just runs mtx like this:
mtx next
my xinetd.conf for amandaidx amidxtape is:
service amandaidx
{
...
server = /usr/local/amanda/libexec/amindexd
server_args = amindexd
}
I don't think you want any server_args. Note:
xinetd state-dump gives:
Service = amandaidx
...
I saw this in my report output:
NOTES:
planner: Incremental of pds:/usr bumped to level 3.
taper: tape DailyBackup-009 kb 2986656 fm 4 [OK]
Yet I saw that /usr was dumped as level 0:
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISK
Jean-Louis Martineau wrote:
backup server. I ran the restore on a Linux box with the 2.4 kernel, hoping that
this
would alleviate the 2GB file size limitation, but so far the output/errors
continue.
Once again, thanks for your help.
Each chunk contains the absolute path of the
On Feb 28, 2001, "Paul D. Schmidt" [EMAIL PROTECTED] wrote:
planner: Incremental of pds:/usr bumped to level 3.
taper: tape DailyBackup-009 kb 2986656 fm 4 [OK]
Yet I saw that /usr was dumped as level 0:
If pds:/usr had got an incremental, it would be a level 3. But
planner ended up
On Feb 28, 2001, Eric Helms [EMAIL PROTECTED] wrote:
follows: /sbin/restore -ivf /data/hope
Verify tape and initialize maps
/data/sbin/restore: /data/hope: File too large
try
cat /data/hope | /sbin/restore -ivf -
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Inside the chg-zd-mtx, it sets the TAPE environment variable, which
works the same as the CHANGER that's listed in the mtx docs.
On Wed, 28 Feb 2001, Stan Brown wrote:
I'm trying to get my first tape changer working, and I'm a little confused.
It appears that I need to use the chg-zd-mtx
but amreport says it can't open disklist... what do I do?
How did you try to run amreport? From what directory? Are the log.*
files zero length? Any chance your Amanda user is running into a quota
problem?
Alex
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
ERROR: /dev/nst0: rewinding tape: No medium found.
...
Tape drive is OnStream ADR50. The problem is the server is far away from
me and I even don't know if any tape there is in, but I assume it is.
Why would you assume it has a tape in it when the OS specifically told
Amanda it didn't?
Also, I
I use amanda 2.4.2p1
I just applied some changes to the CVS sources last night that do a
better job of logging what is going on. If you can at least temporarily
upgrade to them, it will be a whole lot easier to debug.
the critical programs:
-rwsr-x--- 1 root disk 367198 Feb 27
Where must i start the recovery? On the Server or on the client?
Typically on the client.
On the fileserver (Tapeserver) amrecover give me no output ...
Huh? No output at all???
and on the client (king) an amrecover gives me:
root@King:/usr/local/sbin ./amrecover -C Daily -s fileserver -t
I posted earlier about a sendsize problem.
sendsize.debug has a line in it that say:
could not lock /etc/amandates: Invalid argument
The owner and group was amanda and disk respectively. The amanda services is
setup to run as user amanda and as group disk in xinetd.d/amanda. When I
chown
21 matches
Mail list logo
