In PI Collective randomly archives getting corrupted in primary & secondary PI server. What is the best solution to sync or merge the good data from primary & secondary PI server to ensure all data is available?
Hi Abu,Archive reprocessing is recommended to repair a corrupt archive so that you can access its data. Make sure that if you're reprocessing the primary archive, you first perform an archive shift. I don't believe you can merge two archives with overlapping time stamps, but you can fill in missing archive gaps as KB 3108OSI8 illustrates.
If you need any assistance with this process, contact OSIsoft Tech Support.
Hope this helps!
In addition to Emily Mendelsohn's comments, can you explain a bit more detail about the situation? Do you mean archives are repeatedly becoming corrupted? I would be interested to know what PI Data Archive you are using on both servers, and how are you determining that the archives are corrupt? Could you include specific error messages you are seeing? Additionally, are the archives experiencing the issue the primary archive? Or historical archives?
If you are seeing archives repeatedly becoming corrupted, it may be beneficial to dig deeper into understanding what is causing this to happen.
- Adam Fink
You would want to investigate the root cause of the corruption if it is frequent:
Retrieving data ...