All, How is the recommended way to move to the upcoming 3.4? We were thinking of having two instances. One with our current 3.02.02.003 and one with 3.4. Is that a good way to do it or should we upgrade to 3.2.7 and go from there? Can we move our data or is it better to do a fresh load? How different is the database in 3.4? Your advice to this newbie is greatly appreciated. -- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
Le 19/04/2011 15:01, Linda Culberson a écrit : > All, Hi Linda, > How is the recommended way to move to the upcoming 3.4? First of all the recommended way is to wait until 3.4 is officially here ;-) > We were thinking of having two instances. One with our current > 3.02.02.003 and one with 3.4. Is that a good way to do it or should > we upgrade to 3.2.7 and go from there? I think it doesn't matter. The database update will take care of this smoothly. (For reader under 3.0, I think it should work too, but I suggest to switch to 3.2 before anyway. For readers running 2.x, wow, upgrade to 3.0, then 3.2 then 3.4) > Can we move our data or is it better to do a fresh load? How > different is the database in 3.4? the DB is quite different but the upgrade takes care of DB upgrade. However, depending on your size & how critical it is to have things live working smoothly, it's always wise to have a test/integration server before upgrading... > Your advice to this newbie is greatly appreciated. Another question you could ask yourself is: * what's important for me in the 3.4 ? (which killer feature I'm waiting for impatiently) * which risk do I accept (ie: if there is a problem that prevents me to work, how long/critical can it be ?) * which ressources do I have to solve a problem Depending on the answers to the previous questions, it may be better/wise to wait for 3.4.1 or 3.4.2, or even 3.4.4 ! To summarize: "if it works, don't fix it" ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
This is wonderful advice, Paul, and all just what I needed to hear. Thank you! On 4/19/2011 8:19 AM, Paul Poulain wrote: > Le 19/04/2011 15:01, Linda Culberson a écrit : >> All, > Hi Linda, >> How is the recommended way to move to the upcoming 3.4? > First of all the recommended way is to wait until 3.4 is officially here ;-) >> We were thinking of having two instances. One with our current >> 3.02.02.003 and one with 3.4. Is that a good way to do it or should >> we upgrade to 3.2.7 and go from there? > I think it doesn't matter. The database update will take care of this > smoothly. > (For reader under 3.0, I think it should work too, but I suggest to > switch to 3.2 before anyway. For readers running 2.x, wow, upgrade to > 3.0, then 3.2 then 3.4) >> Can we move our data or is it better to do a fresh load? How >> different is the database in 3.4? > the DB is quite different but the upgrade takes care of DB upgrade. > However, depending on your size& how critical it is to have things live > working smoothly, it's always wise to have a test/integration server > before upgrading... >> Your advice to this newbie is greatly appreciated. > Another question you could ask yourself is: > * what's important for me in the 3.4 ? (which killer feature I'm waiting > for impatiently) > * which risk do I accept (ie: if there is a problem that prevents me to > work, how long/critical can it be ?) > * which ressources do I have to solve a problem > > Depending on the answers to the previous questions, it may be > better/wise to wait for 3.4.1 or 3.4.2, or even 3.4.4 ! > To summarize: "if it works, don't fix it" ;-) > -- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
Hi, On Apr 19, 2011, at 9:01 AM, Linda Culberson wrote:
How is the recommended way to move to the upcoming 3.4? We were thinking of having two instances. One with our current 3.02.02.003 and one with 3.4. Is that a good way to do it or should we upgrade to 3.2.7 and go from there?
Having two instances (production and test) is always a good idea. I don't think it is necessary per se to upgrade your test database to 3.2.7 first, you should be able to just upgrade from 3.2.2 to 3.4.
Can we move our data or is it better to do a fresh load? How different is the database in 3.4?
It will not be necessary to reload your data. You can just set up your test instance with a full copy of your exiting production database, upgrade the test instance to 3.4, then test. Once you're happy with the results and have resolved any glitches, you can then run the upgrade process in your production database. Regards, Galen -- Galen Charlton VP, Data Services Equinox Software, Inc. / Your Library's Guide to Open Source email: gmc@esilibrary.com direct: +1 352-215-7548 skype: gmcharlt web: http://www.esilibrary.com/
participants (3)
-
Galen Charlton -
Linda Culberson -
Paul Poulain