Upgrading and getting mails ported

[protik]

Frankly only one user, that's me.
I started kolab 2 as experimental, was not sure I'll actually be making it
primary mail server.
Few of my friends are interested but I don't wanna create accounts before I
upgrade it.

Thanks
On Mar 31, 2013 12:13 PM, "Paul Klos" <kolab at klos2day.nl> wrote:

> **
>
> Op zondag 31 maart 2013 10:00:50 schreef protik:
>
> Thanks,
>
>  How about Migration of LDAP (it says not yet authored)
>
>  And I'm assuming to start with this guide I need to have both kolab2  and
> kolab3 setup and running.
>
> Regards
>
>
>
> On Sun, Mar 31, 2013 at 6:08 AM, Paul Klos <kolab at klos2day.nl> wrote:
>
> Op zaterdag 30 maart 2013 22:08:03 schreef protik:
>
> Hi,
>
>  I currently have version 2.4 and wanted to upgrade to 3.0.
>
>  However I don't wanna loose current settings / mails or users.
>
>  My current setup is with openpkg.
>
>  Kolab 3.0 doesn't support openpkg upgrade, so I'm looking for guide /
> tutorial link to move from one setup to the other and way to test new setup.
>
> Thanks
>
>
>
>
>
> Hi,
>
>
>
> This should be your starting point:
>
>
>
>
> http://docs.kolab.org/en-US/Kolab_Groupware/3.0/html/Administrator_Guide/chap-Administrator_Guide-Upgrading_from_Kolab_2_on_OpenPKG.html
>
>
>
> Cheers,
>
>
>
> Paul
>
>
>
> PGP: 8FE6E0BD
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://www.intevation.de/mailman/listinfo/kolab-users
>
>
> The section on LDAP migration has indeed not been authored. Just out of
> curiosity, hoe many users are we talking about?
>
>
>
> As to your other question, yes, you do need to setup a new Kolab 3
> instance and keep the Kolab2 running. The migration as described requires
> both the old and the new server to be up and running.
>
>
>
> Cheers,
>
>
>
> Paul
>
>
> PGP: 8FE6E0BD
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20130331/cd3d83c6/attachment.html>