Re: newbie problems

2003-07-23 Thread Jason P.Pickering
Hi Yogish. It would seem that the permissions on you holding disk are not
correct. Did you try chown amanda:amanda /home/tmp to give amanda
permission to write to the disk?
Regards..JPP



On Wed, 23 Jul 2003, Yogish wrote:

 Hi
 I am a newbie with amanda,  I have configured amanda according to a book, However 
 when I try to amdump it gives me following error.I have also attached the 
 amanada.conf and disklist files.Can anyone please help me
 This was the error I ran into when I checked the log files
 START planner date 20030722
 INFO planner Adding new disk localhost:/home/.
 START driver date 20030722
 WARNING driver WARNING: ignoring holding disk /home/tmp: Permission denied
 FINISH planner date 20030722
 STATS driver startup time 14.803
 ERROR taper no-tape [not an amanda tape]
 FAIL driver localhost /home/ 0 [can't switch to incremental dump]
 FINISH driver date 20030722 time 28.470


 Regards
 Yogish
 --
 Yogish.G.K
 American Healthcare Solutions Inc
 405, South Lincoln
 Steamboat Springs CO-80487
 Ph-970-870-6232 ( EXT 106) (office)
 Email: [EMAIL PROTECTED]
 


Dumps way too big...

2003-07-09 Thread Jason P.Pickering
I recently added a directory to be backed up and this is the message that
I get..

I have a holding disk with 15GB space (reserving 30% for degraded mode
dumps) and I am using a Surestore DAT 24 tape drive with DDS-3 tapes.

I saw the work around in the FAQ, but google turned up this
http://groups.yahoo.com/group/amanda-users/message/30947

which said that it may have something to do with the tape definition which
is...


define tapetype HP-DAT24 {
comment HP SureStore DAT 24 #disabled compression
length 12288 mbytes
filemark 0 kbytes
speed 1024 kbytes
}


So, it would seem that even if the Level 1 dump is 5.8 gigs (according to
the planner) I shuold be able to handle it.

Does anyone know how to correct this?

Thanks and best regards,
Jason Pickering

Here is the report...


FAILURE AND STRANGE DUMP SUMMARY:
jtlinux.SI //yinling/MyDocuments lev 1 FAILED [dumps way too big, must skip
incremental dumps]


STATISTICS:
  Total   Full  Daily
      
Estimate Time (hrs:min)0:05
Run Time (hrs:min) 3:51
Dump Time (hrs:min)1:47   0:37   1:09
Output Size (meg)   10908.0 4595.9 6312.1
Original Size (meg) 13242.7 6705.8 6536.9
Avg Compressed Size (%)66.6   68.5   20.4   (level:#disks ...)
Filesystems Dumped6  1  5   (1:5)
Avg Dump Rate (k/s)  1743.9 2104.8 1550.4

Tape Time (hrs:min)3:07   1:19   1:48
Tape Size (meg) 10908.2 4595.9 6312.3
Tape Used (%)  88.8   37.4   51.4   (level:#disks ...)
Filesystems Taped 6  1  5   (1:5)
Avg Tp Write Rate (k/s)   996.8  995.8  997.5

DUMP SUMMARY:
 DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
-- - 
jtlinux.SIMT -ble/jasonp 1  590240 590272   --   10:18 955.1   9:52 996.4
jtlinux.SIMT -design/rct 0 FAILED ---
jtlinux.SIMT -yDocuments 1 58145205814560   --   56:271716.9  96:55 999.8
jtlinux.SIMT -yDocuments 1 FAILED ---
jtlinux.SIMT /etc1 690128  18.6   0:21   3.7   0:06  21.2
jtlinux.SIMT /home   0 68667004706208  68.5  37:162104.8  78:46 995.8
jtlinux.SIMT /var1  287750  58688  20.4   2:19 422.9   1:00 976.8
jtlinux.SIMT hda61 580128  22.1   0:04  22.1   0:06  20.9

(brought to you by Amanda version 2.4.3)



Re: Problems with amrecover

2003-06-16 Thread Jason P.Pickering

First of all, thanks for your help Jon. 

On Mon, 16 Jun 2003, Jon LaBadie wrote:

 Hi, the body of you message refers to dumping and flushing.
 Why a subject about amrecover???

Oops..this was before my first cup of coffee this morning. ;-) Indeed, the 
title of my mail should be Problems with amflush!. Sorry about that.

 Here is why I guessed nothing to dump.  This suggests that
 during your dump, 100% (the default) of the holding disk was 
 reserved for degraded mode dumps.  Everything had to go direct
 to tape.  As there was no tape and no holding disk, there would
 not have been any dumps available for amflush.
 
 If my guess is correct,
 rethink the setting of your reserve parameter.


Indeed, this enabled me to flush those degraded dumps to tape. I had this 
line commented out in my original configuration file. 

Thanks so much for the speedy and accurate response!

Best regards,
Jason Pickering




Problems with amrecover

2003-06-15 Thread Jason P.Pickering
Hello amanda users...


This problem has happened several time to me, and I
have trawled through the archives here, but haven't found any
solution really. I forgot to put the correct tape in last night, and 
unfortunately, amflush won't dump my backup to tape.
Here is what i get (see below). 

Can anybody tell me how to get those backups onto tape and have my 
database be correctly updated?

Thanks in advance,
Jason Pickering

[EMAIL PROTECTED] amanda-2.4.3]$ driver: pid 3882
executable driver 
version 2.4.3
driver: send-cmd time 0.002 to taper: START-TAPER
20030606
taper: pid 3883 executable taper version 2.4.3
taper: page size is 4096
taper: buffer size is 32768
driver: adding holding disk 0 dir /mnt/home2/backups
size 3008448
reserving 3008448 out of 3008448 for degraded-mode
dumps
driver: start time 0.009 inparallel 4 bandwidth 70600
diskspace 
3008448 dir OBSOLETE datestamp 20030606 driver:
drain-ends tapeq LFFO 
big-dumpers ttt
taper: buffer[00] at 0x40218000
taper: buffer[01] at 0x4022
taper: buffer[02] at 0x40228000
taper: buffer[03] at 0x4023
taper: buffer[04] at 0x40238000
taper: buffer[05] at 0x4024
taper: buffer[06] at 0x40248000
taper: buffer[07] at 0x4025
taper: buffer[08] at 0x40258000
taper: buffer[09] at 0x4026
taper: buffer[10] at 0x40268000
taper: buffer[11] at 0x4027
taper: buffer[12] at 0x40278000
taper: buffer[13] at 0x4028
taper: buffer[14] at 0x40288000
taper: buffer[15] at 0x4029
taper: buffer[16] at 0x40298000
taper: buffer[17] at 0x402a
taper: buffer[18] at 0x402a8000
taper: buffer[19] at 0x402b
taper: buffer structures at 0x402b8000 for 240 bytes
taper: read label `Backup1' date `20030417'
taper: wrote label `Backup1' date `20030606'
driver: result time 73.680 from taper: TAPER-OK
driver: state time 73.680 free kps: 70600 space:
3008448 taper: idle 
idle-dumpers: 4 qlen tapeq: 0 runq: 0 roomq: 0 wakeup:
86400 driver-
idle: not-idle
driver: interface-state time 73.680 if : free 600 if
ETH0: free 4 
if LOCAL: free 3
driver: hdisk-state time 73.680 hdisk 0: free 3008448
dumpers 0
driver: QUITTING time 73.680 telling children to quit
driver: send-cmd time 73.680 to taper: QUIT
taper: DONE [idle wait: 0.000 secs]
taper: writing end marker. [Backup1 OK kb 0 fm 0]
driver: FINISHED time 95.582
[EMAIL PROTECTED] amanda-2.4.3]$