Background archive transfer for edge server submits

The P4V user on the edge server no longer needs to wait for both the submitted archive files and the metadata to be transferred to the commit server. It is possible for an administrator to configure the replication environment so that:

  1. The edge server sends the metadata to the commit server.
  2. The P4V 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.

To enable background archive transfer

If the Server is not configured for this feature, the P4V user on the edge server must wait for both the submitted archive files and the metadata to be transferred to the commit server.

Prerequisites

  • Ensure a service user is defined for the commit server and that this service user is logged into the ExternalAddress field of the server specification for all edge servers that will participate in background transfers.
  • If any of the participating edge servers are enabled for SSL/TSL security, ensure the service user on the commit server has established trust to the ExternalAddress field for those edge servers.

Steps

  1. Set the submit.allowbgtransfer configurable to 1 on the EDGE servers that you want to participate in background archive transfer.
  2. Set the lbr.autocompress configurable to 1 on ALL the servers.

  3. Set the submit.autobgtransferconfigurable to 1 on the EDGE servers that you want to participate in background archive transfer.