1 of 1 people found this helpful
You are right that the scenario you are talking about probably occurs only because you are suspending your VM.
To overcome this, I think I would try to configure a scheduled task or whatever script to stop the PI Analysis Service when you suspend you VM, same for when restoring it.
Depending of your virtualization engine this may be possible or not... worse case would be to add two bat files on your desktop:
net stop PIAnalysisManager
net start PIAnalysisManager
By Defaut, PI Asset Based Analytics will perform historical recovery.
What type of VM do you use?
Hope this helps
I use VMware Server, but could switch to VirtualBox.
Forgot to mention that i did switch off AutoBackfilling, so it does not make sense to me yet. I suspended yesterday at 17:30, resumed today at 9:00, analysis is scheduled to run at midnight, But still i got new events.
Ah, wait, i did not restart the Analytics engine after the config changes... Let me try that.
The question on how on a functional level i can make the difference between connection issues and no data, is the reason why ACE is currently much better suited for more complex recalculation scenarios than Abacus. Because, rethinking this, this would require being able to postpone the calculation of a result until all requirements are fullfilled (like we have data...)
The simple fix for me is to change the logic in the rule to count the number of events. If only PtCreated or no events, then init the value, and on badval, just skip the output.
After a restart of the Analytics engine, no more auto backfilling, problem solved!
It might be a good idea to at least note this in the PSE GUI that when changing the settings, a restart of the engine is required.
We'll do that. Thanks Roger.
I am glad that you could solve your problem Roger and thanks for participating at products improvements.
Now i'm mainly really glad that no one told me to read the manual ('cos i didn't...)
Software should be so easy that manuals are not needed....