Subject | FB 1.5.x SS Redundancy |
---|---|
Author | Daniel R. Jimenez |
Post date | 2005-06-01T02:01:29Z |
Hi,
I have had a look at Helen's book, but unfortunately I have not found a
answer, I was not expecting one, as I believe this is probably to far of
topic for the book.
I would like know if there is a build in facility on FB 1.5.x SS, which
allows for full live automated DB redundancy to a separate PC (the FDB on
PC-2 is identical to the FDB on PC-1 at all times, 24/7), so that if PC-1
was to go up in flames, PC-2 could take over transparently.
That is, the application will see that the connection to PC-1 is down, so it
would switch to PC-2, so with transparently, what I really mean, is that our
application(s) does not have to take responsibility for keeping the two FDB
in perfect sink at all times, etc.
If this is not part of FB 1.5.x SS what tools do the members of this group
recommend?
Thank you
daniel
I have had a look at Helen's book, but unfortunately I have not found a
answer, I was not expecting one, as I believe this is probably to far of
topic for the book.
I would like know if there is a build in facility on FB 1.5.x SS, which
allows for full live automated DB redundancy to a separate PC (the FDB on
PC-2 is identical to the FDB on PC-1 at all times, 24/7), so that if PC-1
was to go up in flames, PC-2 could take over transparently.
That is, the application will see that the connection to PC-1 is down, so it
would switch to PC-2, so with transparently, what I really mean, is that our
application(s) does not have to take responsibility for keeping the two FDB
in perfect sink at all times, etc.
If this is not part of FB 1.5.x SS what tools do the members of this group
recommend?
Thank you
daniel