I actually do something very similar to that on all my Amanda servers. My crontab entries for amdump
look like:
45 22 * * 1-5 su - amandabackup -c "/usr/local/sbin/amdump daily" > /dev/null;
/usr/local/bin/amchanger daily unload; /usr/local/adm/backup/daily-amanda-con
fig
45 0 * * 0-1 su - amandabackup -c "/usr/local/sbin/amdump --no-taper daily" > /dev/null;
/usr/local/adm/backup/daily-amanda-config
The script daily-amanda-config backs up all the configuration directories into a set of day name
directories on a different drive that get cycled weekly. The script then tars up that day name
directory and ships it over to another server. So, it is doubly backed up in case a drive fails or
in case the whole server goes belly up. I think that script is in the amanda users list archives.
That intermediate script is a simple one I wrote to unload the tape so that it is not sitting in the
drive all day. We had some serious power outages one summer, and if the library lost power with a
tape in the drive, there was a good chance it would jam the tape and ruin it. That also required
taking out the drive and manually winding out the tape. Unloading the tape significantly reduced the
risk of that occurring.
----
However, in this situation, what I'm trying to cope with is a *merge*. The transition from one
server to the other was not an abrupt total switchover. Both servers were running. I got Amanda
3.3.3 installed and working for the server itself. Then I moved a couple of clients as a test. Then
I moved the tape library and the remaining clients. So, the Amanda database on the new server has
some unique data that it has created, and the Amanda database on the old server has the longer
history. I'm trying to figure out how to merge the longer history from the old server onto the new
server without stepping on the new information that is unique to the backups that have been done on
the new server.
Chris
On 5/22/13 1:40 PM, Charles Curley wrote:
Forward to the list because I didn't check the "to:" line when I
replied.
Begin forwarded message:
Date: Wed, 22 May 2013 10:58:48 -0600
From: Charles Curley <[email protected]>
To: Chris Hoogendyk <[email protected]>
Subject: Re: transferring Amanda database from one server to another
On Wed, 22 May 2013 12:08:08 -0400
Chris Hoogendyk <[email protected]> wrote:
Is there a simple clean way of transferring that information from the
E250 without stepping on the Amanda database entries that have been
accumulated already on the SuperMicro?
I faced a similar problem in making offsite backups of my Amanda data.
See
http://charlescurley.com/blog/articles/backing_up_amanda_metadata/index.html
I doubt you need the scripts, but that should tell you everything you
need to preserve. I believe most (all?) of the directories you need to
preserve are specified in amanda.conf.
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[email protected]>
---------------
Erdös 4
