3 Replies Latest reply on Dec 11, 2018 8:21 AM by lngueko

    PI Server Back Up Issue

    ReyWong

      Hello everyone, I am having some problems when configuring PI Server now. Please can give some advice.

      We have two PI Servers, one as the primary server and the other as the Secondary server. By configuring the PI SDK and PI Collective to make the two servers a group, the data of the primary server will be transferred to the secondary server. Our server will automatically open the backup every day at 3 am. In the current problem, the Secondary server will always fail the backup, and it will not be able to search the Current Value after a few days and show the error code [-10727]:RPC is  Non-Existent And the Backup error code is [-16915] backup was aborted.

      I try to delete the secondary server and try to connect it again , some time successfully, but most time failed.

        • Re: PI Server Back Up Issue
          lngueko

          This error [-10727] PINET: RPC is Non-Existent can happen under a variety of conditions such as:

          • In the PI Message Log when the PI Server was starting up
          • Connecting to the PI Data Archive
          • Running a query on the PI Data Archive

          There are many more possibilities than what are listed above, but those are the most common scenarios.

           

          In almost all cases, this problem is caused by one or more PI Data Archive subsystems not running. Starting those subsystems will solve the issue. You can locate the subsystem(s) that is(are) not running from the Windows Service applet and start them manually. All of the subsystem names start with PI (which makes them easy to find). Pay attention to any errors that occur when you try to start the subsystems. If the subsystems failed to start the first time, then they are likely to fail again for the same reason.

           

          In some cases, the subsystem is started, but it is busy, so it has not yet sent its list of RPCs to pinetmgr. These cases are rare because subsystems should publish their RPCs to pinetmgr's table fairly soon after startup. Two notable exceptions include the PI Snapshot Subsystem (pisnapss) and the PI Archive Subsystem (piarchss) during deep queue recovery.

           

          16915 backup was aborted may be due to disk space.

           

          KB00639 - PI Backup fails with Error [-16915] "Backup was aborted, Backup operation shutdown with errors"

          2 of 2 people found this helpful