I have tried all sorts of wierd and wonderfull combinations of things as the
diskdev.

I have tried 

        paperbark       /dev/hda8       dumptype
        paperbark       /home           dumptype
        paperbark       /mnt/c-drive dumptype
        paperbark       /               dumptype        

You name it and I have probably tried it :) ( i think? )
And I still recieve the same error message

The following message is same for them all except the diskdev section
changes. ( below )

I did have another look at the Amanda FAQamatic and found an article on
there saying that the UDP packets may not be large enough, but it also says
that this should no longer occurr since they increased the packet size from
1 kB to 64 kb. 

I am using Redhat 7.0 on a PII 400 with 192 MB ram, surely I needed worry
about the UDP packet size... ??????

Thanks everyone for their help so far... I just hope that we can nut this
one out.


------- ERROR MESSAGE STARTS HERE. ----------

*** THE DUMPS DID NOT FINISH PROPERLY!

*** A TAPE ERROR OCCURRED: [cannot overwrite active tape DailySet100].
*** PERFORMED ALL DUMPS TO HOLDING DISK.

THESE DUMPS WERE TO DISK.  Flush them onto a new tape.
Tonight's dumps should go onto 1 tape: a new tape.

FAILURE AND STRANGE DUMP SUMMARY:
  paperbark  /home lev 0 FAILED [missing result for /home in paperbark
response]


STATISTICS:
                          Total       Full      Daily
                        --------   --------   --------
Dump Time (hrs:min)        0:00       0:00       0:00   (0:00 start)
Output Size (meg)           0.0        0.0        0.0
Original Size (meg)         0.0        0.0        0.0
Avg Compressed Size (%)     --         --         -- 
Tape Used (%)               0.0        0.0        0.0
Filesystems Dumped            0          0          0
Avg Dump Rate (k/s)         --         --         -- 
Avg Tp Write Rate (k/s)     --         --         -- 


NOTES:
  planner: Adding new disk paperbark:/home.
  driver: WARNING: got empty schedule from planner


DUMP SUMMARY:
                                      DUMPER STATS                  TAPER
STATS
HOSTNAME  DISK           L  ORIG-KB   OUT-KB COMP%  MMM:SS   KB/s  MMM:SS
KB/s
-------------------------- --------------------------------------
--------------
paperbark /home          0   FAILED
--------------------------------------------

(brought to you by Amanda version 2.4.1p1)

--------- END ERROR MESSAGE -----------

Thanks again

Nathan


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Peter Schaffrath
Sent: Tuesday, 7 November 2000 9:55 AM
To: Nathan Bird
Cc: '[EMAIL PROTECTED]'; 'Amanda user's group'
Subject: RE: AMDump Reporting Results Missing 


On Tue, 7 Nov 2000, Nathan Bird wrote:
> In disklist I was under the impression that you had to write the
following.
> 
> hostname diskdev dumptype [spindle [interface]]
> 
> The diskdev that it is referring to is the tape device isn't it?

Nice idea :-)

No, "diskdev" is the harddisk (sig!) on the client that you want to
backup. Ex. if you have 2 disks on client1 there are 2 entries:
client1 /mountpoint1/of/disk1 dumptype
client1 /mountpoint2/of/disk2 dumptype

And possibly lots more for other clients.
The tape device is set in your amanda.conf file and that's the only place
where it is needed.

Peter

Reply via email to