[foxboro] Very strabge incident on legacy historian

Yesterday we took an AW-51B down for yearly vbackups. When it was rebooted,
the operators complaind that "ternding did not work". Investigation
revealse that it actually did work, but only for about 243 of the ~800
points that should have been in the historian.

The historian data display revealed that the histrian thouht that only 243
points were configured! The only thing thta looked unusual (that we found)
was that Informix's tbchek -pe showed to physical extents overlaping.

The history of this machine is that the historian wa upgraded from 500
points to 100 a whil back when we brought in another process unit to it's
sphere of control.

We resored a tape from Septemnber to a unit in the lab, and it alos showed
only 243 points in the historian, but it did not display the Inromix
extenrs error.

We woulnd up doing a dbitint, and alod from some older data, and got back
most of the points.

My question is, has anyone else seen this behavior? And can anyone explain
what might have hapend?

I think I will also add a historian database dump to my routine bi-weekly
automated backups. Is anyone else doing this?


-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
                                                -- Benjamin Franklin
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: