1 Reply Latest reply on Jul 16, 2018 10:46 PM by jengler

    Archive alignment post processing or merging

    JF.URBIETA

      Hi all,

      I've a tricky question about PI archives... My client has a PI Data archive since a while and has decided to migrate to the latest version on a new server (such work has been already done on other locations) but the worst part is the following : In order to adopt a new tag naming rule, most of acquired tags will be renamed (not a bad idea), but in fact the two servers will be supposed to have parallel activities till the first one is decommissioned.

       

      So the problem is that in order to recover correctly data from archives for a dedicated tag, the only way is to preserve the initial tag Id. But as only 10% of previous tags will be re-used, how to handle Ids which are no more required...

       

      Is there anyway to recover an existing tag Id in order to re-use it in the new database, so archives will be correctly aligned between both bases and tag representation?

       

      To summarize:

      • Now :
        • Tag "ABCD" corresponding to sensor "A" from equipment "B" with tag unique Id "1234" is declared in PI Data Archive Server "OLD" and has archives since a while
      • Near Future:
        • Tag "ABCD" corresponding to sensor "A" from equipment "B" with tag unique Id "1234" is declared in PI Data Archive Server "OLD" and has archives since a while
        • Tag "DCBA" corresponding to sensor "A" from equipment "B" has to be declared in PI Data Archive Server "NEW" with tag unique Id "1234" and shares archives from "OLD" server
      • Far future:
        • Tag "DCBA" corresponding to sensor "A" from equipment "B" with tag unique Id "1234" is declared in PI Data Archive Server "NEW" and has archives merged with existing ones

       

      So any feedback on similar issues or tips will be welcome as usual.

       

      Regards,

        • Re: Archive alignment post processing or merging
          jengler

          Hello Jean,

           

          In my opinion, you have two options.

           

          Option 1: Migrate the PI Server as you normally would. Re-point all of the old interfaces to the new servers maintaining the old naming convention. THEN, once all that is done, use PI Builder functionality to rename the tags to the new naming convention that you want. This will retain the same point IDs.

           

          Otherwise...

           

          Option 2: Create the new PI Server with new tag names. Those new tag names will likely have different point IDs. Then you may need to use a binary conversion file described in KB 2785OSI8 to map the new tags to the old point IDs.