Takashi Kurakata wrote:
Hi all
Amanda-2.5.2p1 on both the server and client.
The backup devices are vtapes on the server.
I ran amdump on the server.
The backup would be "full dump (Lv0)".
After I ran amdump, I found the vtape directory not being correctly set.
I Thought that the backup was failure.
When I checked the log($logdir/DailySet1/log.yyyymmddhhmmss), I found
that the amanda creates incremental dumps.
----
ERROR taper no-tape [No writable valid tape found]
WARNING taper changer problem: Virtual-tape directory /var/vtapes does
not exist.
FINISH planner date 20080123192410 time 1.344
SUCCESS dumper ctamanda /var/test 20080123192410 1 [sec 0.455 kb 10 kps
22.0 orig-kb 10]
SUCCESS chunker ctamanda /var/test 20080123192410 1 [sec 0.219 kb 10 kps
191.1]
STATS driver estimate ctamanda /var/test 20080123192410 1 [sec 1 nkb 42
ckb 64 kps 10]
----
Would you please answer to my questions follow whether if they are
possible or not?
1) Why amanda creates incremental dumps to holding disk?
Amanda is supposed to redirect the dumps to a holding disk in the
follow case:
- No tape drive.
- The cable became disconnected.
or the wrong tape in the drive
or the tape was write protected
or ...
Why amanda doesn't fail backup and creates incremental dumps to holding
disk?
When there are tape errors, Amanda falls back to "plan B". In that
case it tries to proceed by making backup to holding disk, taking into
account the "reserve" parameter in amanda.conf:
reserve number
Default: 100. The part of holding-disk space that should be
reserved for incremental backups if no tape is available,
expressed as a percentage of the available holding-disk space
(0-100). By default, when there is no tape to write to, degraded
mode (incremental) backups will be performed to the holding disk.
If full backups should also be allowed in this case, the amount
of holding disk space reserved for incrementals should be lowered.
Note the default is to reserve 100% for incremental backups. If your
holdingdisk is very large, and you want level-0 backups as well,
lower the number (even "reserve 0" is allowed).
2) Do you judge that which module is it?
Do you know whether to judge that which module is "Lv1"?
Planner? Driver?
Planner decides the diferent levels for each DLE.
But planner also provides a "plan B" for driver, so that when
there suddenly are tape errors, driver can switch some full backups
to an incremental when the unreserved holdingdisk space is full.
3) Why amanda-2.5.0p2 isn't creates incremental dumps to holding disk?
Neither this time nor the same thing didn't intermited though did by
amanda-2.5.0p2 (amanda2.5.0p2-4) that the bundle was done with RHEL5.
Why amanda-2.5.0p2 isn't creates incremental dumps to holding disk?
I'm not sure I understand the question...
--
Paul Bijnens, xplanation Technology Services Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
