As Kate said, this is probably a bad idea.

There are a few ways of mirroring content. The first and "easiest" is to just use a network filesystem on a third server. However, in our experience, UBB.classic and most NFS implementations do not get along well. One customer recently implemented an eight server load balanced cluster using NFS alone on Linux, however we can not support this configuration officially.

Another option would be running something like rsync every few minutes. Unfortunately, this would lead to the possibility of catching the data files in the middle of a write, and thus could lead to the backup copy containing corrupted data.

So, basically... Don't do this. <img src="https://www.ubbcentral.com/boards/images/graemlins/smile.gif" alt="" />

If you need a proper failover solution, then you should indeed look at UBB.threads. It's safe to run the code itself on NFS, and you can use MySQL's failover/mirrors/slaves. Do note that you'll probably need to alter the configuration of the UBB.threads board(s) if you need to suddenly redirect to another MySQL server. You could also consider the MySQL Cluster software, currently in beta. We haven't tested UBB.threads with it, but we don't anticipate problems. (Assuming you also want database failover and not just web server failover.)

This thread for sale. Click here! [Linked Image from navaho.infopop.cc]