I have to set up a DSpace instance and want to make it highly avalable. Its
not that the load is gonna be that heavy to start with, but I want to have
some redundancy such that if a machine goes bad, the system will still
function while I look about changing it out. So I'm planning on using LVS on
Centos.
I will have two routers which will keep traffic going to two webservers on
the backend which have duplicate DSpace instances. Now to have duplicate
instances I will use a common NFS store for the assest store, but for the
database I will point each of the DSpace instances to a common database on
the network. I know this will be a single point of failure, but I can either
restore the database quickly if I need, or I can get synchronisation across
postgres databases dynamically if I want (slony, etc).
My question is: can anyone give me a simpler or better way to achieve high
availability, and is DSpace code able to manage different web applications
writing to the database across different instances.
John
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
