Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 5 of 5 total |
what is High Availability Solutions available for elevatedb? |
Sat, Oct 19 2013 11:22 PM | Permanent Link |
ae1080 | as subject .
is failover clustering available or planned? thanks ahmed |
Sun, Oct 20 2013 10:21 AM | Permanent Link |
Raul Team Elevate | Can't speak for future (you need Tim from Elevate Soft to comment on
that) but EDB in its current form provides lot of capability already. 1. There is replication allowing you to keep multiple separate EDB databases up to date. Very easy to do a warm standby and depending on your data and input patterns even hot standby might be doable. 2. if you have the infrastructure of good performance shared storage (san ideally) then multiple EDB servers running on multiple separate servers can share the same catalogue and databases hence giving you a EDB cluster. This would work in with NAS/file server but then you likely run into performance issues due to NAS file sharing protocols. In theory you can the latter solution with a load balancer or OS level failover cluster (like Windows one) but i don't know if anybody has done it. Raul On 10/19/2013 11:22 PM, ae1080 wrote: > as subject . > is failover clustering available or planned? > thanks > ahmed > |
Thu, Oct 24 2013 8:54 AM | Permanent Link |
Adam Brett Orixa Systems | Ahmed,
As Raul has said it is possible to imitate the behaviour you are requesting in EDB, EDB just uses different names for the processes. I use Amazon AWS to provide cloud-based servers hosting EDB. AWS will allow you to set up multiple servers in different Regions (Ireland, USA, Singapore etc.) so you can spread your availability around and be secure that all servers will not fall over at the same time ... unless a planet-wide apocalypse occurs ( It is then relatively easy in EDB to write procedures & jobs which "share the data around" between different servers. This is done by PUBLISHING all databases, then writing SAVE UPDATE and LOAD UPDATE scripts that run regularly to synchronize the data on each different server with the others. Your front-end application then just needs to be coded to try to connect to each server in turn. If one is down it will connect to the next one, or you can have a system to "take turns" connecting to different servers in order to simulate load-balancing. You have to think it through and write your own logic, which is more work than some other solutions, but at the same time you get more control over the process. |
Thu, Oct 24 2013 9:33 AM | Permanent Link |
Raul Team Elevate | On 10/24/2013 8:54 AM, Adam Brett wrote:
> > You have to think it through and write your own logic, which is more work than some other solutions, but at the same time you get more control over the process. > One thing i always forget to mention also is that feature set for the price can't be beat - one time payment and royalty free distribution of unlimited copies with your app. Raul |
Thu, Oct 24 2013 10:28 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Raul
And don't forget - almost unbeatable support. It would be unbeatable if only he would sort out all my problems, requests and suggestions and forget everyone else <vbg> Roy Lambert |
This web page was last updated on Monday, April 29, 2024 at 05:23 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |