Hi Alan, I have recently been in the details of arranging a maintenance contract with Openerp, I suggest you take your question directly your Openerp account manager for commercial aspects, they will be able to clarify things so you are not in "no contracts land". As it's the same db and code it shouldn't be problematic from a pricing perspective.
I am surprised however, with your technical approach as you could loose up to one day of data in case of server crash with this setup. Why didn't you consider clustering db at postgres level ? ( note: we recently had a server power supply crash and got caught by surprise as we have availability penalties in some of our contracts). We started looking into postgres clustering to achieve a 5 min downtime or less in case of server crash, but we are only at the beginning.... I would be happy to hear anyone else views on how to achieve high availability with openerp. Kind regards, Christian Sprauer Railnova CEO, Belgium On 9 nov. 2011, at 18:19, "Alan Lord (Gmail)" <[email protected]> wrote: > Hi all, > > We want to provide a "hot standby" backup for one of our customers > (effectively a copy of the system on a different host). > > Our idea is to (basically) take a dump of the database each night and copy it > to their standby server (physically different location, different IP/MAC > etc.) so if their main server dies they can still access their services. > > They will will have the Enterprise Warranty. Is this likely to break anything? > > TIA > > Al > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
