13 messages in net.sourceforge.lists.courier-usersRe: [courier-users] RES: Courier Back...
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] RES: Courier Backup / replication pointActions...
From:gor...@bobich.net (gor@bobich.net)
Date:Nov 26, 2007 8:27:24 am
List:net.sourceforge.lists.courier-users

On Mon, 26 Nov 2007, Jay Lee wrote:

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

1) Price (it is a very expensive solution);

No not really, you can use OSS solutions like GFS or ZFS to achieve this. you're already talking about having redundant storage, why should it cost any more at the filesystem or block level than it would at the app level?

AFAIK, ZFS doesn't (yet) support clustering.

Jay, about the NFS solution, how does it work regarding syncronism?

I mean, will the files in the 2 servers be always the same?

Example, courier saves a file on server 1, at the same time will that file be updated in server 2?

Yes I believe so with GFS or ZFS, why don't you spend some time researching their merits?

Indeed, you can NFS export shares from a GFS file system.

Gordan