On 5/22/13 2:57 PM, Charles Curley wrote:
On Wed, 22 May 2013 14:21:31 -0400
Chris Hoogendyk <[email protected]> wrote:
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.
Ah, sorry, I wasn't clear.
I figured you could do your metadata backup, using your script or mine.
Then you could have two configurations, one of which points to the new
and ongoing data/metadata, the other of which points to the old
data/metadata.
This is not as elegant as doing a complete merge, which is what you
asked for. On the other tentacle, it's probably a lot less work. And,
Murphy willing, you won't need it.
Once gotcha is that the metadata format may have changed from 2.5.1p3
to 3.3.3.
I suspect other people may be interested in your results. Debian 7
(Wheezy [*Where* do the get these code names?]) was released early in
May, with Amanda 3.3.1-4 on it. This replaces 6, (Squeeze), with Amanda
2.6.1p2-3. Debian admins tend to be a cautious lot, but I expect we'll
see migrations over the next few months. I'm already running a 2.6.1p2
server with several 3.3.1 clients, and no problems so far. I should do
some test restores, though. :-)
I've typically done my Amanda builds from source rather than use what is packaged with the
distribution. Partly that is coming from Solaris. But, my first Ubuntu systems were clients, and I
didn't want to try backing up a client with a newer Amanda than the server. So I just took the
source tar.gz from the server and built it on the Ubuntu client. Mostly, on Ubuntu, I have been
sticking with the packages and aptitude. What's fun is dealing with custom configurations with
upstart and apparmor (e.g. multiple instances of MySQL). Same order of fun as dealing with Solaris
SMF. And then jumping back and forth between them.
Recently, I jumped to Amanda 3.3.3 on my primary T5220 Solaris 10 servers. That worked nicely with
the 2.5.1p3 clients. When I made the switch in another department from the E250 Amanda server to the
SuperMicro Amanda server, I also jumped to Amanda 3.3.3. It again worked nicely with the 2.5.1p3
clients. Then I bumped a test client to 3.3.3 (also SuperMicro with Ubuntu). That went smoothly as
well. So, I'll probably work towards building 3.3.3 for all the clients and then my other Amanda
installations as well.
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[email protected]>
---------------
Erdös 4
