See, e.g.,
http://archives.zmanda.com/amanda-archives/viewtopic.php?t=6913&sid=91e3c881079ae117012208432adf30cb
I've had that running for years. A simple shell script that does weekly fulls and daily incrementals
of the amanda directory to an archive directory on the same machine, then tars up the whole archive
directory and shoots it over to another Amanda server. There it gets backed up by the regular Amanda
run. I have several Amanda servers in different departments that reciprocate this shared service,
backing up each others configurations. If you are interested, I could send the script.
There are other Amanda admins who have similar or related approaches.
On 4/14/16 5:09 AM, David Simpson wrote:
Hi all,
Just wondered what your method to backup Amanda itself was?
I was thinking about a cron job to tar the Amanda dirs before the amdump run starts – it would be
placed in a directory local to the backup server (on itself) and then put onto VTAPE or TAPE using
tar. If it had to be restored it could be restored from a dump using OS tools (tar etc).
Another question is, what does everyone do about data growth? Are you using scripts/monitoring
system or something like Robin Hood?
regards
David
----------------------
David Simpson - Computing Support Officer
Institute of Biomedical Engineering – IBME
Old Road Campus Research Building
Oxford, OX3 7DQ
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 317 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[email protected]>
---------------
Erdös 4
