1 of 1 people found this helpful
I doubt that the data update delay is related to making the PI Network Manager service dependent on the Microsoft iSCSI. Service dependencies will only affect service start up and service shut down and shouldn't affect the proper functioning of the service. I think to troubleshoot your data update issue, the next best step is to consult the SDK logs. Here is a KB for reference: https://techsupport.osisoft.com/Troubleshooting/KB/3248OSI8/
I'm not sure what our official recommendations are for this type of situation. I'll try to get you an answer and post back to this thread.
1 of 2 people found this helpful
Why do you have to do a weekly reboot? We try to keep our PI systems running 24/7/365. Do you have an unresolved issue which is only solved by doing a reboot? If that's the case then get the root cause fixed and that will negate the issue with network manager you are seeing now.
2 of 2 people found this helpful
Why would you host core application directory on a SAN disk? I am curious about the reasoning behind this.
You could set up PI Services (incl. pinetgmr) to a Delayed startup, so the services would start 2 minutes after reboot (this can be changed - see discussion here), which should be enough time for the SAN disk to be available.