<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
to my point of view, you should simply virtualize kolab server. i you
correctly backup your vm you will have your fully redondant system with
day -1.<br>
i think upg<br>
rading the VM to 2.2.4 will be a more secure way to upgrade as it's
easy to go back in case of bad issues.<br>
regards.<br>
Le 17/12/2010 13:14, kiser Caesar a écrit :
<blockquote cite="mid:DUB104-w7F6DF0577DE1A3A2421FEA3160@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>Hello,<br>
<br>
Actually I'm running a kolab server 2.2.2 on a physical server (debian
4.0), but for more security I plan to duplicate it as a virtual image.
My goal is to have backup/redundant service.<br>
Now to have a sync with my two servers, I will make a rsync from my two
"/kolab"each evening. I think I will have with this way a fully
redondant system with day -1.<br>
<br>
But before I want to know your eventual feedback on my idea ? <br>
<br>
Moreover, I think I must upgrade to kolab 2.2.4 before doing my virtual
server ?<br>
<br>
Then to finish, someone have already upgrade his sytem (debian 4.0 >
debian 5.0) ? I need some feedback,<br>
<br>
<br>
Best regards,<br>
<br>
<br>
</blockquote>
<br><br>
<br> <br>************************************************************************************<br>This footnote confirms that this email message has been scanned by<br>PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.<br>************************************************************************************<br><br>
</body>
</html>