'RE: Kolab-users Digest, Vol 86, Issue 10'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-users
Subject:    RE: Kolab-users Digest, Vol 86, Issue 10
From:       kiser Caesar <kcaesar () hotmail ! com>
Date:       2011-04-18 21:23:08
Message-ID: DUB104-w6D1ABC8998707A9C10C1DA3910 () phx ! gbl
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

--Pièce jointe du message transmise--
Subject: Re: Question about kolab 2.3.0
Date: Mon, 18 Apr 2011 10:35:40 +0200
To: kolab-users@kolab.org
From: wickert@kolabsys.com

Am Montag, 18. April 2011, 08:32:08 schrieb kiser Caesar:
> I think now the best choice is to migrate directly to kolab 2.3.0 (debian
> 6.0). I will create a fresh xen vm.

If this is a production system, I suggest you wait for 2.3.1 which will happen 
next week.

> But after who can help me to migrate my user's data and ldap to the new
> server ?

There are detailed upgrade instructions for each release in 1st.README. If you 
miss something don't hesitate to ask again.

Regards,
Christoph

-- 
Christoph Wickert
Senior Engineer

Kolab Systems AG
Zürich, Switzerland

e: wickert@kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert

Hello Christoph,

Yes it's for a production server. So I will waiting for 2.3.1 release.
Moreover I think I was not very clear on my last email.

Currently my kolab server (kolab 2.2.2, debian 4.0) runs on a physical server and I \
want to migrate to a vm (xen). I hope to find a way to jump "directly" from 2.2.2 to \
2.3.1... For this I planned to install a fresh vm (kolab 2.3.1, debian 6.0) and today \
I need to know how I can migrate my ldap to the new server (with slapcat, \
modification and slapadd as show in tutorial?). And next to finish how I can sync my \
"/kolab/var/imapd/spool/..." to the new server ? With rsync ? Or maybe with another \
process ?

Please help,

Best regards,

[Attachment #5 (text/html)]

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
<br>--Pièce jointe du message transmise--<br>Subject: Re: Question about kolab \
2.3.0<br>Date: Mon, 18 Apr 2011 10:35:40 +0200<br>To: kolab-users@kolab.org<br>From: \
wickert@kolabsys.com<br><br><pre>Am Montag, 18. April 2011, 08:32:08 schrieb kiser \
Caesar:<br>&gt; I think now the best choice is to migrate directly to kolab 2.3.0 \
(debian<br>&gt; 6.0). I will create a fresh xen vm.<br> <br>If this is a production \
system, I suggest you wait for 2.3.1 which will happen <br>next week.<br> <br>&gt; \
But after who can help me to migrate my user's data and ldap to the new<br>&gt; \
server ?<br> <br>There are detailed upgrade instructions for each release in \
1st.README. If you <br>miss something don't hesitate to ask again.<br> \
<br>Regards,<br>Christoph<br> <br>-- <br>Christoph Wickert<br>Senior Engineer<br> \
<br>Kolab Systems AG<br>Zürich, Switzerland<br> <br>e: wickert@kolabsys.com<br>t: +49 \
251 871 369 77<br>w: <a href="http://kolabsys.com" \
target="_blank">http://kolabsys.com</a><br> <br>pgp: 85DACC63 Christoph \
Wickert<br></pre><br>Hello Christoph,<br><br>Yes it's for a production server. So I \
will waiting for 2.3.1 release.<br>Moreover I think I was not very clear on my last \
email.<br><br>Currently my kolab server (kolab 2.2.2, debian 4.0) runs on a physical \
server and I want to migrate to a vm (xen).<br>I hope to find a way to jump \
"directly" from 2.2.2 to 2.3.1...<br>For this I planned to install a fresh vm (kolab \
2.3.1, debian 6.0) and today I need to know how I can migrate my ldap to the new \
server (with slapcat, modification and slapadd as show in tutorial?).<br>And next to \
finish how I can sync my "/kolab/var/imapd/spool/..." to the new server ? With rsync \
? Or maybe with another process ?<br><br>Please help,<br><br><br>Best \
regards,<br><br><br> 		 	   		  </body> </html>

_______________________________________________
Kolab-users mailing list
Kolab-users@kolab.org
https://kolab.org/mailman/listinfo/kolab-users

[prev in list] [next in list] [prev in thread] [next in thread] 