redundant remote servers

[rmvg]

I have several domains lets say domain1.com and domain2.com these domains have seperate static ips, physical locations and even different isps. I have zimbra setup on one box already and am in the process of setting up the other box i wish to use these machines

1. as backup mx servers for each other
2. as completely redundant servers ie each user will be on both machines if one fails the other takes over. Is this possiable using zimbra or is there a better way to achive this?

Please forgive me if this is covered in the docs or on the lists somewhere if so just point me in the right direction.

[KevinH]

The *best* way to do this would be to use Red Hat cluster that we ship as part of our Network release. This gives you true real time cluster and redundant systems. So basically install a multi-node system and have eash clustered for failover.

In the OSS release you can create a multi-node install. Basically when installing the 2nd, 3rd, etc host point to the LDAP master. This will allow you to have each postfix instance be a backup of the other. Of course each user can only be on one mailbox server so you don't have a true cluster for the mail itself. For this you'd need to use the Network version.

Let me know if you have any other questions.

[rmvg]

where/how do i get the network version

The *best* way to do this would be to use Red Hat cluster that we ship as part of our Network release. This gives you true real time cluster and redundant systems. So basically install a multi-node system and have eash clustered for failover.

In the OSS release you can create a multi-node install. Basically when installing the 2nd, 3rd, etc host point to the LDAP master. This will allow you to have each postfix instance be a backup of the other. Of course each user can only be on one mailbox server so you don't have a true cluster for the mail itself. For this you'd need to use the Network version.

Let me know if you have any other questions.

[KevinH]

where/how do i get the network version

Send a email to sales _at_ zimbra.com They can set you up with the Network beta information.

[rmvg]

Contacted sales let my clients know the price they will be getting back to me but doubt they will be willing to shell out that kind of cash. Guess i will stick to OSS for now.

I have a couple of questions do u remeber this thread
http://www.zimbra.com/forums/showthr...=2428#post2428

have still not been able to fix this problem thinking a reinstall might be the easiest answer. However i have some users online and cannot risk losing there email. I have the /opt/zimbra directory backed up nightly to another server. Is there a right way to do this ie do i have to stop zimbra first? will /opt/zimbra be enough or do i need other directories too?

there is also the post about upgrading here should i follow this last time i did but the scripts seemed to corrupt my message store somehow and blow away my messages anyway.

"
To save existing users and data, you'll need to migrate the database schema prior to installing 3.0.M1. These steps will accomplish that.

su - zimbra
zmcontrol shutdown
mysql.server start
mkdir 30_M1_migrate
cd 30_M1_migrate
unzip zcs_3.0.M1.migrate.zip http://downloads.zimbra.com/3.0_M1/...M1a.migrate.zip
./migrate20050824a-Volume.pl
./migrate20050831-SecondaryMsgVolume.pl
mysql.server stop
3.0.M1/install.sh
"

Mostly i have be waiting for the next release so i can kill two birds with one stone.

As for the clustering or multi-node install as u call it. Is the master the server i already have setup do i have to make changes to it to use it as a master? and do i point zimbra at this server during install on the 2nd 3rd machines? Also during a reinstall can i change the domain name from ck.com to mail.ck.com or will that break things mysql lapd or perhaps certs?

The *best* way to do this would be to use Red Hat cluster that we ship as part of our Network release. This gives you true real time cluster and redundant systems. So basically install a multi-node system and have eash clustered for failover.

In the OSS release you can create a multi-node install. Basically when installing the 2nd, 3rd, etc host point to the LDAP master. This will allow you to have each postfix instance be a backup of the other. Of course each user can only be on one mailbox server so you don't have a true cluster for the mail itself. For this you'd need to use the Network version.

Let me know if you have any other questions.

[KevinH]

I have a couple of questions do u remeber this thread
http://www.zimbra.com/forums/showthr...=2428#post2428

Yes. Not sure why it's not working for you. Lots of other folks here have seemed to get it working.

However i have some users online and cannot risk losing there email. I have the /opt/zimbra directory backed up nightly to another server. Is there a right way to do this ie do i have to stop zimbra first? will /opt/zimbra be enough or do i need other directories too?

Well I'll remind you all again this is BETA code. So we've not commited to provide clean upgrades and data migration. It *should* work, but please we know there are still some bugs which is why we call it BETA. You should be able to just run the installer again and do an upgrade with the same release or a new release.

there is also the post about upgrading here should i follow this last time i did but the scripts seemed to corrupt my message store somehow and blow away my messages anyway.

Yes there was some problems with those scripts. We hope to have this cleaner for the next release.

As for the clustering or multi-node install as u call it. Is the master the server i already have setup do i have to make changes to it to use it as a master? and do i point zimbra at this server during install on the 2nd 3rd machines? Also during a reinstall can i change the domain name from ck.com to mail.ck.com or will that break things mysql lapd or perhaps certs?

Your server is a master. So the 2nd/3rd machines can just point to that. You can try to change the name but again it's listed in many places so might not work. We rather you get the domain right the first time or create a new domain and move user's to it.