PI Ancillary Server?

Does anyone use or know details about the PI Ancillary Server?

"Ancillary Server: an ancillary server is a PI server that serves a supporting role to a corresponding properly licensed production server for testing or network architecture reasons.  It can be used in production or non-production environments.  The ancillary server has no technical limitations.When do I use it?

Examples of use include a production + pre-production pair for validation purposes, or a production + production pair where one server is inside a firewall and another is outside for a data diode. "

Parents
  • I'd like to know a little bit more about it, such as:

    - How does it works along side the production PI Data Arquive server in the production + production exemple given.

    - How is it licensed? Is it a stand alone licence, like PI Test, or is it bond to other PI, like an HA Node.

  • Hi Halen,

     

    1. It works along side a production server as a pre-production server for validation and testing purposes. The advantage of this server over something like a development server is that it does not have technical limitations which means it it compatible with much more of our software, specifically interfaces. And of course there is the example you gave above with the firewall.
    2. I believe it is licensed separately like a development server and unlike an HA setup. However, for more detailed information regarding licensing, your best research is your OSIsoft Account Manager.
  • We bought the Ancillary server license. However, we are skeptical of doing PIFD production backup/restores to the new Archive/AF node due to config changes that come with it. How do other clients handle this issue? To make sure the Dev is up to date but does not over-write configs such as node names, analysis, and notification startups?

Reply
  • We bought the Ancillary server license. However, we are skeptical of doing PIFD production backup/restores to the new Archive/AF node due to config changes that come with it. How do other clients handle this issue? To make sure the Dev is up to date but does not over-write configs such as node names, analysis, and notification startups?

Children
No Data