Hi, Am 12.03.2012 um 12:05 schrieb Marcel Reutegger:
> 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. But: However the repository implements sharding etc. The user of the JCR API does not have to care about this implementation detail... As such a backup solution, should well be possible on-top of the JCR API regardless of how the internal implementation distributes data etc., right ? Regards Felix
