Hi Alexander,

> I think a shadow could reside on a NFS share.
>
> But what I can think to be a more robust approach will be replication.
>
> You set-up the server 1 to replicate everything to server 2
>
> Then when connection goes down, your app connects to the second server.
>
> A one way replication like this should be easy to implement.
>
> Maybe others could give other ideas.
>

If the db app has knowledge regarding the primary FDB and the secondary FDB
(so it would normally connect to PC-1, but if it becomes un-available it
will connect to PC-2), and we decide that replication is the way to go, how
do you deal with the following scenario?

If PC-1 is the main FDB and it became unavailable due to network problems
and 72 hours later if came back on line (the db app will now see PC-1 as
available and it will connect to it, as it is the main/primary DB), how
would you setup the replication so that PC-1 would be updated from PC-2,
since PC-2 has the latest most recent set of data? And normally the
replication would take place from PC-1 to PC-2? Please remember that this is
to be transparent, so minimal user interaction.


daniel