Thanks, Brian. So, basically, the upgrade in general is pretty straightforward.
The key point, though, is that I am promoting an important Amanda client to be the new Amanda server. During that process, there may be a period of time when the old server (running 2.5.1p3) will be talking to this important client that has been updated to 3.3.0, but not yet taken over as server. I don't want to miss backing it up during that time.
So, briefly, will a 2.5.1p3 server have trouble with a 3.3.0 client (just until I get things completely swapped around)?
On 7/15/11 3:03 PM, Brian Cuttler wrote:
Chris, We followed a very similar path for our E250s, to T2000 upgrades. The E250 eventually not having the bandwidth to backup the servers. I have now installed 3.3.0 on several of my systems, a Sparc and several x86, though they where all Solaris 10. I don't know how many E250s you have, but I think I'd upgrade the amanda version on the new server first, that way I'd potentially put backups off-line for a single system, where as a server upgrade might off-line backups for multiple clients. The 3.3.0, up from 3.1.2 on the x86 and from 2.4.x (I think, it was all of two weeks ago you know) on the Sparc, but in all cases the update was simple. I did need to tweak the amanda.conf on the Sparc but it was badly out of date and the tweaks where minor and easy to find. The only difficulty I had was with a Solaris 10/x86 amanda server that was running 3.1.2, but had a wide variety of clients, from Windows to old Solaris boxes. That difficulty was rooted in the change to default BSDAUTH. The steps to deal with that should be pretty simple, I just haven't had time and choose to pick the low hanging fruit from among my other amanda servers. I am still running about a dozen servers because of 1) data volume 2) bandwidth between various physical campuses 3) physical network separation for security. On Thu, Jul 14, 2011 at 02:05:19PM -0400, Chris Hoogendyk wrote:I'm in the process of doing an upgrade and thought I should check with the list before plunging forward to see if anyone else has done it quite like this or has any comments or suggestions. Original set up: Amanda 2.5.1p3 on a collection of E250's running Solaris 9. Spare E250 set up as a backup server with a tape library and extra holding disk space. Actual user data storage scattered around on a couple of systems, but the bulk by far is on the main departmental server. Changes since then: Several servers upgraded to T5220's and storage continuing to increase. We now have many TB on the departmental server. The network is almost entirely GigE. It's reached the point where I think Amanda would be better off directly on the departmental server. The T5220 has more than enough scalability to add Amanda, and that would eliminate the majority of the network transfer volume during backups. It would also allow me to fairly easily do the occasional archive directly to tape. I have a spare tape library and have set it up on the departmental server. I have downloaded Amanda 3.3.0 and am about to install it. I thought I would get that checked out, move all the history, configuration, and tapes from the dedicated backup server to the departmental server, and then stop running Amanda on the backup server. The general recommendation has always been to update the Amanda server and get it running before updating clients. In this case, I will be converting one of the clients to be the server and upgrading it in the process. However, there will be a transition phase from the point at which I do the `make install` to point where it has been debugged/configured/put-in-service during which the original Amanda server (2.5.1p3) will be backing up the departmental server on which the binaries will have been upgraded to 3.3.0. Is that going to result in a period of broken backups during which my main departmental server won't get backed up? Does anyone have a recommendation for the best way to approach this? Should I instead install the server components of 2.5.1p3 on the departmental server and switch Amanda servers before beginning the upgrade process? (The original install was client only.) TIA -- --------------- Chris Hoogendyk - O__ ---- Systems Administrator c/ /'_ --- Biology& Geology Departments (*) \(*) -- 140 Morrill Science Center ~~~~~~~~~~ - University of Massachusetts, Amherst <hoogen...@bio.umass.edu> --------------- Erd�s 4--- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support (v) 518 486-1697 Wadsworth Center (f) 518 473-6384 NYS Department of Health Help Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
-- --------------- Chris Hoogendyk - O__ ---- Systems Administrator c/ /'_ --- Biology& Geology Departments (*) \(*) -- 140 Morrill Science Center ~~~~~~~~~~ - University of Massachusetts, Amherst <hoogen...@bio.umass.edu> --------------- Erdös 4
