Clone your live system, then test, time and document the upgrade procedure, then if everything goes OK in the cloned system it should work as expected in live (and should in theory take less time as you will have documented all the commands etc.). Going from 2.4 has a number of changes to the GUI interface aswell, so remember your users who will probably be on the phone to you asking where everything is, if you have a cloned system you could give them something to play with for a short period of time before the live is upgraded. Steve On 7 May 2012 21:20, Steve Clark wrote:

** Hello List,

I am concerned with the down time that appears to be involved when upgrading from 2.4.x to 3.0.x when following the procedures outlined in the UPGRADING document. Especially if after the upgrade we find some showstopper and have to revert.

Anybody have any suggestions to mitigate the risks?

-- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark@netwolves.com http://www.netwolves.com

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs