13 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier Backup / ...
FromSent OnAttachments
Sam VarshavchikNov 24, 2007 7:15 am 
Ronie Gilberto HenrichNov 24, 2007 9:24 am 
Jay LeeNov 24, 2007 3:39 pm 
Jérôme BlionNov 24, 2007 7:11 pm 
Ronie Gilberto HenrichNov 25, 2007 9:36 am 
Jay LeeNov 25, 2007 10:37 am 
gor...@bobich.netNov 26, 2007 2:25 am 
Ronie Gilberto HenrichNov 26, 2007 7:12 am 
gor...@bobich.netNov 26, 2007 7:28 am 
Jay LeeNov 26, 2007 8:18 am 
gor...@bobich.netNov 26, 2007 8:27 am 
Ronie Gilberto HenrichNov 26, 2007 10:23 am 
gor...@bobich.netNov 27, 2007 1:40 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Courier Backup / replication pointActions...
From:Jay Lee (jl@pbu.edu)
Date:Nov 25, 2007 10:37:24 am
List:net.sourceforge.lists.courier-users

On 11/25/07, Ronie Gilberto Henrich <ron@ronie.com.br> wrote:

Hi Jérôme, Hi Jay,

The disadvantages in using something at the filesystem/block is specially regarding load balancing. We have two servers, with different IP addresses inside our network, where courier is running. At the front, we have the firewalls and LVS doing a load balancing. They will redirect to the active courier server. So, if we replicate at the filesystem/block layers, we have to take out several files from the replication proccess, because the different IP addresses, different server names, and so on.

There is no need to replicate the entire filesystem, just your data. So have a RAID1 root filesystem in each of your two servers and then have them NFS mount the shared Maildirs.

As a solution for that situation, I think that a "replication point" feature

in courier will be a nice solution.

We have a software develop team, so we can do that contribution to the courier project.

-- Jay Lee Network / Systems Administrator Information Technology Dept. Philadelphia Biblical University