Tim Bradshaw wrote:
> On 2007-02-27 17:38:40 +0000, Dave Miner <dave.miner@sun.com> said:
>
>> You do need to provide some level of coherency, which could be as
>> simple as exporting out the configuration every so often (dhcpconfig
>> -X <some file> -a ALL -m ALL -o ALL) and copying it to the backup
>> server so that you can import it (dhcpconfig -I <some file>) when
>> needed. Or you place the data stores on some HA NFS service and share
>> them (which we do support) or in a SAN that's dual-ported and can be
>> failed over.
>
> Thanks! So if I put the store on a netapp (if we lose that then it's
> basically game over since it serves filespace to all the PCs anyway),
> then I should be OK? I'd assumed that the usual NFS locking issues
> would mean I'd just be immediately doomed if I did that, but things are
> probably better than they once were in that respect. So that's a good,
> cheap answer.
>

Yes, that's what the shared data store concept is intended to allow, and
part of the reason why we've never pursued implementing the failover
protocol draft that the ISC server has.

Dave