Feature request : distributed architecture

alain_mig

Feature request : distributed polling, able to withstand link failures between sites.

Lets say you have 2 sites with a slow connection between those, instead of having a remote poller one one side and a full ORION install on the other, you would have a master install and a secondary install (I guess each one would have to be installed as such primary secondary etc..).

What I mean is that the secondary DB would probe on its lan and store data in its local DB this way behaving as a regular ORION install, but the feature we would like to see would be to be able to pack the DB and manually transfer it, and import the database into the primary site each week or so (that part could be manual), the interest is that you can publish reports of the entire network from one DB only, and the remote poller function could this time be able to poll on its lan even if the link with the main site is down.

I guess technically we would have to choose the type of DB install from the configuration wizzard, the type secondary would have interfaceId volumeID and nodeID set to some high number so to avoid overwriting data in the primary database. The other part would be to have some merging function available from the database manager.

Of course such setup would not allow a high number of secondary DB, and would not allow for realtime collection from distant databases.

Please let me know if I'm not clear enough.
Regards,
Alain

Don331

Alian,
Check out some of the new options for Orion. Most of what you're asking for is already available in the Hot Standby pack!

Don Barry
Aegis Mortgage Corp
Houston, TX