From the Edit Historian Connection window you can select Tunnel (Push).
The Tunnel (Push) historian type allows you to configure the DataHub instance as a tunnel slave to forward data from a local external historian to a remote external historian, by connecting to a DataHub tunnel master running on the remote machine. Please see External Historian 4 - Tunnel (Push) for more details.

A unique text string used to identify this connection. This
label is used to identify the connection when configuring store
and forward, and to create the database name or retention policy
in some historians. The label can contain only letters, numbers
and the underscore ( _ ) character.
The connection name of the tunnel you have configured to push data to the remote DataHub instance. See Tunnel (Push) in the the tutorial for more information.
The Label configured for the external historian on the remote side.
The number of milliseconds that the DataHub instance will buffer data in memory before pushing it across the tunnel. Leaving this field blank means that no accumulation time will be enforced. If both this value and Maximum # of buffered values (below) are specified, then the DataHub instance will send all buffered values across the tunnel whenever the first of these two limits is reached.
The maximum number of values that the DataHub instance will buffer in memory before pushing them across the tunnel. Leaving this field blank means that no values will be buffered.
Checking this option causes messages regarding successful writes to the database to be logged at the level in the DataHub Event Log. If this is not checked then these messages are logged at the level and are therefore normally hidden from the user.
Please see Modify Point Names, Data Sampling or Forwarding in Connection Configuration for how to configure these options.
Once you have completed the Tunnel (Push)-specific configuration, you can return to Picking Points in General Configuration to continue.