On 2008-06-25 14:48, Johan Booysen wrote:
Well, that seems to work beautifully. I've forced a full dump of about
180GB, and amdump successfully spanned across the two tape drives. I'm
doing a test restore now, but can already see that it works just fine.
I'm still not 100% sure on how to perform restores if a disklist entry
is spanned across two tapes, but one of the tape drives have died.
Would I need to use amrestore instead of amrecover, and then manually
untar all the restored chunks?
In the parameters for the config that I added, a single DLE does not
span two tapes, so you do not encounter that problem.
You need to configure a dumptype for that having a parameter "tape_splitsize"
and then only those DLE's having that dumptype will be split into chunks.
See:
http://wiki.zmanda.com/index.php/How_To:Split_Dumps_Across_Tapes
I try to avoid that option if possible.
Instead I try to fill my tapes using a technique that I explained here:
http://wiki.zmanda.com/index.php/How_To:Fill_tapes_to_100%25
and, if you're using Amanda 2.6 or later, you can even add the newer
parameters "flush-threshold-dumped" to achieve a better result.
Thanks.
Johan
-----Original Message-----
From: owner-amanda-users AT amanda DOT org
[mailto:owner-amanda-users AT amanda DOT org] On Behalf Of Johan Booysen
Sent: 24 June 2008 13:39
To: amanda List
Subject: RE: Amanda 2.6.0 spanning
Hmm, that's weird. My tapecycle specifies 25 tapes.
What I'm trying to do is to "bring over" the old server's
index/log/tapelist/disklist files etc to the config on the new server,
to test that I can do restores from tapes written by the old server.
What I've done in the meantime is to create a second config to do a test
amdump, so as not to affect the production config, so to speak. And
I've labelled some spare tapes for the second config for this purpose so
I don't mess with the production set of tapes.
I must have missed something out regarding the existing tapes from the
old server - will double-check it all again.
Thanks!
-----Original Message-----
From: Paul Bijnens [mailto:Paul.Bijnens AT xplanation DOT com]
Sent: 24 June 2008 13:27
To: Johan Booysen
Cc: amanda List
Subject: Re: Amanda 2.6.0 spanning
On 2008-06-24 13:49, Johan Booysen wrote:
Hi,
Looks like I'm getting somewhere this time. The server is happy with
the two tape drives emulating a changer with 2 slots, and all amtape
commands seem to complete ok.
Just one question before I do a test run:
Can I ignore the following warning about the second tape being "still
active and cannot be overwritten" when doing an amcheck?
No, you can't ignore that.
slot 1:read label `daily-5', date `20080508'.
..
..
slot 2:read label `daily-6', date `20080509'.
Tape with label daily-6 is still active and cannot be overwriten.
I'm assuming I can, since I double-checked that daily-6 is marked as
"reuse" in the tapelist.
The tapes are used by Amanda in an ordered rotation.
The tapecycle parameter defines the size of that rotation.
Amanda needs to be given the number specified in tapecycle
before she accepts to overwrite that tape again.
See "man amanda.conf", "tapecycle" for a more detailed explanation.
When you REALLY are sure you want Amanda to overwrite it,
you can "amrmtape" followed by "amlabel -f" (specifying
correct configs and labels).
Or you can (temporarily) lower the count given by
tapecycle in amanda.conf
--
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 *
***********************************************************************
|
