Hi, > 2) Assuming we get the clustering architecture right (which we > should), it should be possible to start a new read-only node to an > existing cluster, wait for it to synchronize all existing content from > the rest of the cluster, and finally stop this backup node. The result > should be a complete, runnable copy of the repository.
this however also assumes that each cluster node has a complete copy of the repository. I'd rather be in favor of a cluster solution that distributes the repository across multiple machines for improved scalability. regards marcel
