2 Replies Latest reply on Jun 20, 2018 1:48 PM by lmalone

    AF backup restoration and custom data references


      Hello All,

      We are planning to restore the AF server on to a new machine, with the SQL backup of PIFD database.

      We have noticed that there are few custom data references available, and used by some AF attributes in the existing AF server. I would like to know if these Custom Data References (CDR's) will be restored from the SQL backup or we would need to additionally copy and register the dll's manually on the new machine.


      Also, if these dll's need to be registered manually, please let us know if there is a way to identify the dll name associated with the CDR. This is because, these CDR's in the existing server are legacy ones developed years back and we don't have any documents/resources to help us in identifying the dll names or the source code.


      Kindly help us on this.




        • Re: AF backup restoration and custom data references
          Dan Fishman

          From what I understand you should be fine.  When you register the custom data reference with the AF Server, you are actually storing it within the SQL database.  When clients connect, they are able to obtain a copy of the dll.  It might be worthwhile to either retire the custom data references, rewrite them or to at least know what is out there.  To obtain the registered plugins run ..Program Files\Pipc\AF>regplugin64 /list and Program Files(x86)\PIPC\AF> Regplungin /list.


          If they plugins are old, their might only be 32 bit assemblies. 


          Also from PI System Explorer> Server Properties > Plug-Ins and then look for Data Reference Plugins.

          • Re: AF backup restoration and custom data references

            Hi Nandhini,


            Dan nailed this question-- custom data references are registered and stored in the AF server, and are automatically retrieved by clients and stored in the '%programdata%osisoft\af\plugins' directory. Therefore, when you restore your SQL database, there shouldn't be anything further you need to do in terms of distributing custom data references. In fact, the custom data references are likely still stored on client machines and won't need to be re-fetched until a newer version of the assembly is registered on the AF server.


            Hope this helps!