 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
13 messages in net.sourceforge.lists.courier-users[courier-users] RES: Courier Backup ...| From | Sent On | Attachments |
|---|---|---|
| Sam Varshavchik | Nov 24, 2007 7:15 am | |
| Ronie Gilberto Henrich | Nov 24, 2007 9:24 am | |
| Jay Lee | Nov 24, 2007 3:39 pm | |
| Jérôme Blion | Nov 24, 2007 7:11 pm | |
| Ronie Gilberto Henrich | Nov 25, 2007 9:36 am | |
| Jay Lee | Nov 25, 2007 10:37 am | |
| gor...@bobich.net | Nov 26, 2007 2:25 am | |
| Ronie Gilberto Henrich | Nov 26, 2007 7:12 am | |
| gor...@bobich.net | Nov 26, 2007 7:28 am | |
| Jay Lee | Nov 26, 2007 8:18 am | |
| gor...@bobich.net | Nov 26, 2007 8:27 am | |
| Ronie Gilberto Henrich | Nov 26, 2007 10:23 am | |
| gor...@bobich.net | Nov 27, 2007 1:40 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [courier-users] RES: Courier Backup / replication point | Actions... |
|---|---|---|
| From: | Ronie Gilberto Henrich (ron...@ronie.com.br) | |
| Date: | Nov 25, 2007 9:36:34 am | |
| List: | net.sourceforge.lists.courier-users | |
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.
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.
Maybe we could improve this idea...
Best regards,
Ronie
-----Mensagem original----- De: Jérôme Blion [mailto:jero...@free.fr] Enviada em: sábado, 24 de novembro de 2007 10:12 PM Para: Jay Lee Cc: ron...@ronie.com.br; cour...@lists.sourceforge.net; cour...@lists.sourceforge.net Assunto: Re: [courier-users] Courier Backup / replication point
Jay Lee a écrit : Sounds to me like something that should be (and has been) configured at the filesystem/block layers rather than at the Courier application layer. Take a look at projects like RedHat's GFS or Sun's ZFS. I don't know much about NetApps either but I know they do NFS very well (which Courier supports very well) and I'm pretty sure they can be configured redundantly.
Jay
On 11/24/07, Ronie Gilberto Henrich <ron...@ronie.com.br> wrote:
Is it any feature in courier that allows me to inform backup storage paths?
Today I use unison to maintain a replica of our email files, configurations, ..., in a second server to use as a fast recovery backup solution. The problem is that unison uses a lot of resources and IO_WAIT is always very high.
So, I was wondering if it is any feature to inform backup storage paths for courier to save all its files always into two different paths. Does something like this exist?
If it does not exist, don't you think it is a interesting feature to be implemented?
Thanks and regards,
Ronie
Hi,
If we work with a filer, an easier way to proceed would be to affect LUNS/filesystems to the "backup" server. This way, you don't have to copy anything... The rollback on the master server just follows the same process. After that, you have to secure your filer. (snapshot and so on)
HTH. Jerome Blion.