asterisk users - Dec 2005 - Asterisk Realtime Database Redundancy

In short, does Asterisk have any database redundancy???

Is there any way to specific more than one db host in res_mysql.conf? If you
specify dbhost with a hostname, and use round-robin dns, does Asterisk read this
file only on startup or on every db connect attempt? If it fails to get a
connection, is it start enough to try the next host?

What about with the MySQL application? Is there any way to incorporate
redundancy into this, such that it can try multiple db servers when one is
unavailable? Is there any way around the limitation where Asterisk reads
extensions.conf on startup, and if that db goes down, Asterisk has already
loaded the IP address into memory... and your screwed?

And what about Realtime extensions? Is there any database redundancy there at
all? What happens when this happens:

*CLI> [Dec 27 06:18:15] ERROR[3007]: res_config_mysql.c:615 mysql_reconnect:
MySQL RealTime: Failed to connect database server vox180 on 192.168.10.15. Check
debug for more info.
[Dec 27 06:18:15] ERROR[3007]: res_config_mysql.c:615 mysql_reconnect: MySQL
RealTime: Failed to connect database server vox180 on 192.168.10.15. Check debug
for more info.
[Dec 27 06:18:15] ERROR[3007]: res_config_mysql.c:615 mysql_reconnect: MySQL
RealTime: Failed to connect database server vox180 on 192.168.10.15. Check debug
for more info.
[Dec 27 06:18:15] ERROR[3007]: res_config_mysql.c:615 mysql_reconnect: MySQL
RealTime: Failed to connect database server vox180 on 192.168.10.15. Check debug
for more info.

Is Asterisk smart enough to be able to try another database? It looks like even
when there are following contexts with a number, Asterisk immediately fails the
call at this point.

Thanks,
Douglas.