We have 2 IS in a cluster connecting to a broker. Version 6.5. During the usual restart on last weekend the broker did not come up. The error message was: brokerdata.qs file corrupted, once we replaced the corrupted files (a few others under default dir of Broker) from the back up it came up. After that one of the interfaces started failing to publish its canonical. The error was “Document type is not defined in the Broker.” but this interface is in production and it was working fine before the .qs file corruption incident. So I synced the document from developer pushed to Broker but what I failed to notice at that time was the Trigger subscribing this document has also lost its subscription. By the time I realized this it was too late and the interface published a few records before I could disable/re-enable the trigger to bring back the subscription. The trigger re-established it subscription but it did not pick up those docs published earlier. It looks like a data loss.:o
Since this document’s properties are StorageType=Guaranteed and never Discard, it should be stored somewhere on the disk.
Now is there any way we can pull these docs out and resubmit them? Question may sound a little lame but since it is production data and I’m working on other possibilities to get the data re-send it would be great if some one can throw some light here and any help on this is highly appreciated.
If any one has any idea of the other two issues of .qs file corruption and docuemnt disappearing from broker, please let me know, that would be also helpful in investigating this issues further.