Wonderful. Questions answered. Thank you all for your time and help.
SOGo 3.1 … (With a 2.3 tailback!) … Here we go! ~ Laz Peterson Paravis, LLC Ph: 951.319.3240 x201 > On May 23, 2016, at 9:17 AM, Christian Mack ([email protected]) > <[email protected]> wrote: > > Hello > > Am 23.05.2016 um 16:00 schrieb "Laz C. Peterson" ([email protected]): >> Hi there, >> >> We are looking to upgrade, and I am curious to know if it is possible to run >> both 2.3 and 3.1 at the same time (testing, etc.)? >> > > Yes this is possible. > You have to install 3.x on another server than 2.x and use the same DB. > > Beware: > The database location is stored in the DB itself. > Therefore if you used "localhost", this will not work from the second > machine. > If you used an DNS Alias (e.g. defined in /etc/hosts) > >> I would imagine I need to run the database schema update to 3.0.0 (via >> sql-update-3.0.0-to-combined-mysql.sh), > > No, not at all. > That script is only needed, if you want to change to the new db schema > with only a few tables for all users, instead of 6 tables per user. > Then you have to change the SOGo configuration too. > >> but will this make any changes to the database that would be incompatible >> with 2.3? > > Yes, 2.3 is not capable of using the new schema (yet?). > >> And also, does 3.1 store data any differently in any existing tables that >> would cause a problem? >> > > If you keep the existing db schema, it will work without problems. > > > Kind regards, > Christian Mack > > -- > Christian Mack > Universität Konstanz > Kommunikations-, Informations-, Medienzentrum (KIM) > Abteilung Basisdienste > 78457 Konstanz > +49 7531 88-4416 > -- [email protected] https://inverse.ca/sogo/lists
