Helix Core Server Administrator Guide: Multi-Site Deployment (2019.1)

Background archive transfer for edge server submits

Users on edge servers might want to spend less time waiting for their submits to complete. Starting with 2019.1, it is possible to configure the replication environment so that:

  1. The edge server sends the metadata to the commit server.
  2. The user on the edge server sees the submit is complete and can resume work.
  3. In the background, the commit server pulls the archive files from the edge server.

Prior to 2019.1, the user on the edge server would need to wait for both the submitted archive files and the metadata to be transferred to the commit server.

To enable background archive transfer:

  1. Set the submit.allowbgtransfer configurable to 1 on ALL the servers in your replication environment.
  2. Tell your users to issue p4 submit -b, where the -b option causes background transfer of the archive files.

Alternatively, to enable background archive transfer with the added convenience of p4 submit automatically functioning as p4 submit -b:

  1. Set the submit.allowbgtransfer configurable to 1 on ALL the servers in your replication environment.
  2. Set the submit.autobgtransfer configurable to 1 on ALL the servers in your replication environment.

Note

To recover a failed archive transfer, restart the transfer by using the p4 pull -t target command, where target represents the commit server.