Subscription server database should contain all information needed also
to run publication server, so in case of publication server fault on of the
subscription servers could become publication server with a help from
heartbeat (www.linux-ha.org) resource handling.
As I understand there is just a few tables that are missing in subscription
server and vice versa, e.g. after recovery failed publication server could
act as subscription server.
With such a feature Daffodil replicator will be very usefull in a cluster
environment.
Feel free to contact if some comments are needed, or You can point me
on where contribution could be made.
Thank You!