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. :-) -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
