Hello I've read (and believe I understand) the upgrade notes at http://www.dspacedev2.org/1_6_0Documentation/ch04.html#N10F06 however, I'm concerned that my upgrade won't be as smooth as it might be. Mainly because I suspect that changes have been applied outside the approved update mechanism and I don't want to loose those changes. I'm planning a more conservative upgrade path (outlined below), which I hope will allow me to catch any problems before I take our production instance off line. I'd greatly appreciate feedback as to whether my approach is flawed, and/or whether there are significant classes of issues that I won't catch in this manner.
My approach relies on the fact that I have a smaller dev machine that I can use for my purposes (alas it is too small to hold the entire assets directory). My work is also complicated by the fact that I'm running a dual-instance server. Both servers are running the redhat family of linux operating systems. My plan: 0) Do a full backup of live 1) Using a database snapshot and file copy of [dspace-source] and [dspace], duplicate both dspace on the dev machine (with the exception of the assets directory). Leaving the live server running. 2) Upgrade the dev server and see what issues fall out of the woodwork. 3) Fix those issues in the dev server. 4) Do a full backup of live 5) Stop the live server. 6) Upgrade the live server 7) Transfer any necessary fixes from the dev server to the live server 8) Restart live server Does that sound like a sane approach? Is there anything I can't test / debug / fix in this way? I'm already aware that: * handles will be broken (because they'll point to the live server rather than the dev site) * search will be broken (because i'll not have the assets directory) cheers stuart -- Stuart Yeates http://www.nzetc.org/ New Zealand Electronic Text Centre http://researcharchive.vuw.ac.nz/ Institutional Repository ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
