Jean-Louis Martineau wrote:
Brian Cuttler wrote:
On Thu, Mar 04, 2010 at 06:28:08AM -0500, Jean-Louis Martineau wrote:
I never like using two configs. Recovery is complex.
Why not use one config? amanda don't allow it, but you can cheat.
Edit amanda.conf every days to change the tpchanger and strategy, if
could be done by a simple script, or more easily, put the difference
in separate file and use 'includefile', that way you just needs a
'cp' before each run.
The only problem is with autoflush, if some dump are left on holding
after a run, they can be flushed to the wrong tpchanger on the next
run.
I'd thought those settings where available as -o options on
the amdump command. Single config with different lines in
cron so nothing is edited or copied ? Maybe an amadmin force
command once per week as well, just before the tape based run ?
You can change the tpchanger with -otpchanger=.... , but changing a
dumptype from command lines doesn't works with dumptype inheritance,
it works only if it is used from the disklist, it is fix in SVN.
But you can do the force full; and, if you have a holding disk of
sufficient capacity, you can use -o to specify a non-existent tape
device so that Amanda drops back and does incrementals only to conserve
holding disk space. If you then flushed those out to a device, you could
achieve what is being requested, I think.
One objection to the original idea of having two separate
configurations, is that to be running incrementals only, you have to
have a full to reference. Within the context of that configuration, you
wouldn't.
I use a couple of different arrangements in different departments. In
one department, their budget for tapes (or anything for that matter) is
very limited. They also have less data to back up in the first place. I
use -o on the cron line to define a non-existent tape drive and tape
library during the week. Then, on Saturday evening, the cron let's it go
to the tape library. Everything gets flushed to tape and the Amanda
scheduler catches up on full backups. I'm not sure I even bother with
the force full. The amanda.conf definitions are such that it wants at
least one full every week and ends up doing them when it is finally
given a chance.
In most of my other departments, I run an ordinary backup every night of
the week, and the Amanda scheduler distributes full backups through the
week. Then, on the weekend I use -o in the cron to define a non-existent
tape drive and library. So, on the weekends, I get incrementals only and
they are all saved on the holding disk. On Monday night, those all get
flushed out to tape with the regular backups. With this set up, my
rotation of 35 tapes lasts 7 weeks instead of the 5 weeks I would get if
I let it use a tape every night of the week.
I believe this technique is documented on the wiki.
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[email protected]>
---------------
Erdös 4
