Guidance on configuring a master server and replica to share the storage for archive files is now included. Shared archive storage can be part of a high-availability configuration for a Perforce service.

See “Configuring a replica with shared archives”.

New in this release is the ability to promote a shelved changedlist to the commit server in a distributed configuration. Once promoted, a shelved changelist is available to any edge server.

See “Promoting shelved changelists”.

Added coverage of the proxy's -S flag, which disables cache fault coordination.

See “P4P flags”.

A synopsis of the steps to run the broker as a Windows service is now included.

See “Running the Broker”.

The commands used to display broker connection information are now described.

See “Broker information”.

Guidance on how protections work with replicas and brokers has been included, in addition to the coverage for proxies, describing how the dm.proxy.protects configurable influences protection table entries.

See “Replication and protections”, or “Broker and protections”, or “P4P and protections”.

Previously, the conversion steps instructed users to remove the replica's state file, both when using a checkpoint or replication. This step is only applicable when using a checkpoint.

The checkpoint approach also recommends using a filtered checkpoint. A cross reference to the Perforce System Administrator's Guide is provided for details on the flags required to produce a filtered journal dump file.

See “Converting a forwarding replica to an edge server”.

Clarified which servers the commands should be executed against, and corrected the description of the -p flag in the p4 reload command.

See “Migrating a workspace from a commit server or remote edge server to the local edge server”.

An admonition has been included to emphasize the importance of this administrative step.

See “Tickets and timeouts for service users”.

Replication can see a notable performance improvement when the rpl.compress configurable is set. A note to this effect has been added to “Warnings, Notes and Limitations”.

The example describing how to apply protections table entries to proxy connections included incorrect line number references. These have been revised and now include IPV6 examples, and a description of how the dm.proxy.protects influences evaluation of protection table entries.

See “P4P and protections”.

When configuring a broker to use an SSL connection to the target server, P4TARGET cannot be specified in the broker's configuration file. A clarification has been added to this effect.

See “Enabling SSL support”.

Several descriptions of broker flags were updated to accurately indicate the expected behavior. The most notable change is the addition of ", and exit".

In addition, the description of the -v flag now includes discussion of the available server= trace values.

See “P4Broker flags”.

The description of the debug-level option now properly indicates that it overrides both the -v flag and P4DEBUG.

The description of the service-user options has been expanded to cover acquiring a ticket, using P4TICKET, and setting an unlimited timeout.

A description of the altserver option has been included.

See “Global settings”.

The RESPOND action was missing from the broker command handler specification, and is now included.

The example command handler was missing the curly braces, and these are now included.

A synopsis of the regular expression syntax available to command handlers is now included.

See “Command handler specifications”.

When a broker filter program is invoked, additional details are provided, including ClientHost, proxyLevel, and brokerLevel.

See “Filter Programs”.

Clarification has been added that alternate servers for a broker must be a replica, broker, or proxy.

See “Alternate server definitions”.

A note has been added that when using a centralized authorization server, all outer servers must be running the same (or newer) release level as the central server.

Also, the example outer server configuration for Windows has replaced the incorrect use of P4CHANGE with P4AUTH.

See “Centralized authorization server (P4AUTH)”.

Descriptions throughout this guide of how to specify target servers, such as replicas, edge servers, brokers, or proxies, now include the optional protocol element to specify how connections to target servers should be established. This is required for encrypting connections via SSL.

protocol is described in detail in “P4TARGET”, and “Specifying hosts”.