Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

PI Powershell

GetPIBufferedServer Class

  • Last UpdatedDec 15, 2025
  • 3 minute read
GetPIBufferedServer Class

Get a PI Buffered Server

The Get-PIBufferedServer cmdlet gets buffered server information for a specified logical server or specified physical server that is part of a logical server.

This cmdlet can be run against remote PI Buffer Subsystems by leveraging PowerShell Remoting.

Inheritance Hierarchy

SystemObject
  InternalCommand
    Cmdlet
      PSCmdlet
        OSIsoft.PowerShellOSICmdletBase
          OSIsoft.PowerShellGetPIBufferedServer

Namespace:  OSIsoft.PowerShell
Assembly:  OSIsoft.PowerShell (in OSIsoft.PowerShell.dll) Version: 3.1.1.0 (3.1.1.466)

Syntax

[CmdletAttribute("Get", "PIBufferedServer", SupportsShouldProcess = true)]
public class GetPIBufferedServer : OSICmdletBase
<CmdletAttribute("Get", "PIBufferedServer", SupportsShouldProcess := true)>
Public Class GetPIBufferedServer
	Inherits OSICmdletBase

Dim instance As GetPIBufferedServer
[CmdletAttribute(L"Get", L"PIBufferedServer", SupportsShouldProcess = true)]
public ref class GetPIBufferedServer : public OSICmdletBase
[<CmdletAttribute("Get", "PIBufferedServer", SupportsShouldProcess = true)>]
type GetPIBufferedServer =  
    class
        inherit OSICmdletBase
    end

The GetPIBufferedServer type exposes the following members.

Constructors

  NameDescription
Public method
GetPIBufferedServer

Properties

  NameDescription
Public property
Details

Return all buffered server details

Public property
LogicalServerName

Logical server name. This is the PI Collective name for collectives, or the server name for standalone PI Data Archive servers

Public property
PhysicalServerName

Physical server name. This is the member node name for PI Collectives, or the server name for standalone PI Data Archive servers. If not specified for a PI Collective, all member sessions will be included. This parameter is not required for a standalone PI Data Archive server.

Examples

Get-PIBufferedServer -LogicalServerName PISRV-Collective -PhysicalServerName PISRV-1

Gets the PI buffered server information object from the local instance of PI Buffer Subsystem for the PISRV-1 machine, which is a member of the PISRV-Collective PI Data Archive HA Collective.

Examples

(Get-PIBufferedServer -LogicalServerName PISRV-Collective -PhysicalServerName PISRV-1 -Details).LogicalServers.Values.PhysicalServersBufferConfiguration.Values.GUID

Outputs the PI buffered server GUID from the local instance of PI Buffer Subsystem for the PISRV-1 machine, which is a member of the PISRV-Collective PI Data Archive HA Collective. This can be used to identity PIBufSS queues belonging to this buffered server.

Examples

Invoke-Command -ComputerName PIINT1 -ScriptBlock { Get-PIBufferedServer -LogicalServerName PISRV-Collective -PhysicalServerName PISRV-1 }

Gets the PI buffered server information object from the PIINT1 instance of PI Buffer Subsystem for the PISRV-1 machine, which is a member of the PISRV-Collective PI Data Archive HA Collective.

Note the use of Invoke-Command. Failure of this example to execute properly is likely not an issue with Get-PIBufferedServer, but with the network or PS connection to the remote computer. Note that the OSIsoft.PowerShell module must be installed on the remote computer as well for this to work.

See Also

TitleResults for “How to create a CRG?”Also Available in