Hi Rachel, On 10/19/2011 12:00 PM, Rachel Hollis wrote:
Greetings colleagues, I've got a new 64bit server to replace the 32bit production server. What would be the best way to go about this?
At a guess, I'd think that the same version of Koha (production server has 3.03) should be loaded on the new server, then a backup from the production server loaded (this would have our preferences, saved SQLs, calendar, etc. as well as patrons and biblios, circulations, etc.) and finally we'd upgrade/update the new server to the new version of Koha.
This sounds like a good plan, since a new server means that you'll be testing the new hardware, the operating system updates you'll be applying, then finally the Koha upgrade. Of course, if you allow enough time for testing and do a dry run or two, from your patron's point of view, absolutely nothing would appear to change until you're ready to unveil the shiny new Koha upgrade. Regards, Galen -- Galen Charlton Director of Support and Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org