>Okay, so we decide to restore the data from tape from last night. That's always fun. Afterwards, I'm contrasting the backup copy that I made of the corrupt data against the restored data, and here's the strange part: the last good record in the corrupt table corresponded to the last record after the restore (ie. all the corrupt records in the "Policy" table were the records that were added today!). I don't understand how only today's data could be affected by whatever happened.

Nirav,

From my own experience and reports from others, a thing like this "just can happen". If only you are on a Novell server ... (4x, 5x, 6 I never heard of this problem ... yet).

To my findings there is some bug in Novell's cache (= resides in main memory of the server), implying that data is not written to disk properly (no dirty cache blocks shown). This is not a problem (reading data throughout the day) , until you pull the plug out (etc.). I reasoned that overnight all is forced to disk because the backup (FIFO) filling the cache (the backup data read later but then from disk).

OT : This bug in Novell's cache can also cause corruption without a server crash (hi Jim! no, I still didn't solve that ...).

Peter