Useful options

[sintaqx]

While discussing the immenent move to using nwnx on a rather large PW (http://www.alandfaraway.org) a couple of items were brought up that would be useful. The ability to define backup databases, a test for the primary database existance/response, and the ability to fail over to a backup database.

[DarkstarsDad]

I just have the db do it for me auto backup and restore from the db itself. i run 2 db and have them cross check between themselves.

[sintaqx]

The big thing that we were looking at is the fail-over to another database. the backup/mirroring is no problem.

[DarkstarsDad]

Sorry misuderstood the question. That would need the ability to access multiple db at same time. Interesting concept. Switch in the ini file perhaps? you could modify the source and add redundant check for primary and then log in secondary if needed. Kinda like the port switch.

[NoMercy]

If your on linux using seperate servers or user-mode linux it is a possibility that you can do IP address takeover, so when the first server dies, server 2 asumes server 1's IP address to process it's requests, more details at: http://www.linux-ha.org/.

Only works if the odbc2 plugin auto-reconects when a connection fails, but I would imagine it does, and coding in a backup might be easier than building a server cluster :)

[sintaqx]

We were thinking the easiest thing would be to simply add in some .ini options
BACKUP1=xxx.xxx.xxx.xxx
BACKUP2=xxx.xxx.xxx.xxx
etc.

We may end up writing this into the code anyway, figured others might see some use in it, so it would be nice to have in the 'real thing'. Also, putting it in the code makes it platform independant, a very big thing right now.