On Mon, 27 Dec 1999 [EMAIL PROTECTED] wrote:
> Saving the UBIK databases requires an
>administrator to shut down the database servers on a single database
>machine (preferably one that is not the sync site), copy the raw
>database files on that machine "/usr/afs/db/*.DB0", start the database
>servers, and then store/save (tar) the copied databases along with the
>"/usr/afs/etc/" directory to tape.
Is it really necessary to shut down the servers on one machine? For example,
our standard non-AFS backup system always tests each file it backs up to
make sure it doesn't change while being backed up. If it did, it retries
(up to four times). If it fails after four retries, it just gives up.
I would think that such a system would work fine, under the assumption that
the databases don't change all that often in our site, and that there is no
relationship BETWEEN databases (e.g., between kaserver and prdb) that needs
to be preserved.
Is this a fairly accurate picture?
Thanks for any help you (or anyone else) can provide -- and for your timely
reminder!
