Nathan_probst wrote:

>
> Now this is interesting...how might FB's "shadow database" facility
> factor into this? We were talking about this issue yesterday and I
> wondered to myself about keeping the "master" database on the host and
> configuring a "shadow" on the USB HDD. Any tips about managing a
> shadow db that is intermittently available? Does FB have some sort of
> commit logging to "catch up" the shadow when it comes available again?
>

Cute idea, but it won't work for the current style of shadowing.
There's no way to separate and reattach a shadow. The idea behind
shadowing was to have a hot copy of the database that could be
started if the primary disk failed. Replication might work better.


Regards,


Ann