<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE doc SYSTEM "doc.dtd">
<doc title="{[project]} Command &amp; Configuration Reference">
    <!-- CONFIG -->
    <config title="{[project]} Configuration Reference">
        <description>The {[project]} Configuration Reference details all configuration options.</description>

        <text><backrest/> can be used entirely with command-line parameters but a configuration file is more practical for installations that are complex or set a lot of options. The default location for the configuration file is <file>/etc/pgbackrest/pgbackrest.conf</file>.  If no file exists in that location then the old default of <file>/etc/pgbackrest.conf</file> will be checked.</text>

        <config-section-list title="Settings">
            <!-- CONFIG - LOG -->
            <config-section id="log" name="Log">
                <text>The <setting>log</setting> section defines logging-related settings.<admonition type="caution">Trace-level logging may expose secrets such as keys and passwords.  Use with caution!</admonition></text>

                <!-- CONFIG - LOG SECTION - LOG-LEVEL-FILE KEY -->
                <config-key-list>
                    <config-key id="log-level-file" name="File Log Level">
                        <summary>Level for file logging.</summary>

                        <text>The following log levels are supported:
                        <ul>
                            <li><id>off</id> - No logging at all (not recommended)</li>
                            <li><id>error</id> - Log only errors</li>
                            <li><id>warn</id> - Log warnings and errors</li>
                            <li><id>info</id> - Log info, warnings, and errors</li>
                            <li><id>detail</id> - Log detail, info, warnings, and errors</li>
                            <li><id>debug</id> - Log debug, detail, info, warnings, and errors</li>
                            <li><id>trace</id> - Log trace (very verbose debugging), debug, info, warnings, and errors</li>
                        </ul></text>

                        <example>debug</example>
                    </config-key>

                    <!-- CONFIG - LOG SECTION - LOG-LEVEL-CONSOLE KEY -->
                    <config-key id="log-level-console" name="Console Log Level">
                        <summary>Level for console logging.</summary>

                        <text>The following log levels are supported:
                        <ul>
                            <li><id>off</id> - No logging at all (not recommended)</li>
                            <li><id>error</id> - Log only errors</li>
                            <li><id>warn</id> - Log warnings and errors</li>
                            <li><id>info</id> - Log info, warnings, and errors</li>
                            <li><id>detail</id> - Log detail, info, warnings, and errors</li>
                            <li><id>debug</id> - Log debug, detail, info, warnings, and errors</li>
                            <li><id>trace</id> - Log trace (very verbose debugging), debug, info, warnings, and errors</li>
                        </ul></text>

                        <example>error</example>
                    </config-key>

                    <!-- CONFIG - LOG SECTION - LOG-LEVEL-STDERR KEY -->
                    <config-key id="log-level-stderr" name="Std Error Log Level">
                        <summary>Level for stderr logging.</summary>

                        <text>Specifies which log levels will output to <id>stderr</id> rather than <id>stdout</id> (specified by <br-option>log-level-console</br-option>).  The timestamp and process will not be output to <id>stderr</id>.

                        The following log levels are supported:
                        <ul>
                            <li><id>off</id> - No logging at all (not recommended)</li>
                            <li><id>error</id> - Log only errors</li>
                            <li><id>warn</id> - Log warnings and errors</li>
                            <li><id>info</id> - Log info, warnings, and errors</li>
                            <li><id>detail</id> - Log detail, info, warnings, and errors</li>
                            <li><id>debug</id> - Log debug, detail, info, warnings, and errors</li>
                            <li><id>trace</id> - Log trace (very verbose debugging), debug, info, warnings, and errors</li>
                        </ul></text>

                        <example>error</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - LOG-PATH KEY -->
                    <config-key id="log-path" name="Log Path">
                        <summary>Path where log files are stored.</summary>

                        <text>The log path provides a location for <backrest/> to store log files.  Note that if <setting>log-level-file=off</setting> then no log path is required.</text>

                        <example>/backup/db/log</example>
                    </config-key>

                    <!-- CONFIG - LOG SECTION - LOG-TIMESTAMP KEY -->
                    <config-key id="log-timestamp" name="Log Timestamp">
                        <summary>Enable timestamp in logging.</summary>

                        <text>Enables the timestamp in console and file logging.  This option is disabled in special situations such as generating documentation.</text>

                        <example>n</example>
                    </config-key>

                    <!-- CONFIG - LOG SECTION - LOG-SUBPROCESS KEY -->
                    <config-key id="log-subprocess" name="Log Subprocesses">
                        <summary>Enable logging in subprocesses.</summary>

                        <text>Enable file logging for any subprocesses created by this process using the log level specified by <br-option>log-level-file</br-option>.</text>

                        <example>y</example>
                    </config-key>
                </config-key-list>
            </config-section>

            <!-- CONFIG - GENERAL -->
            <config-section id="general" name="General">
                <text>The <setting>general</setting> section defines options that are common for many commands.</text>

                <config-key-list>
                    <config-key id="buffer-size" name="Buffer Size">
                        <summary>Buffer size for file operations.</summary>

                        <text>Set the buffer size used for copy, compress, and uncompress functions.  A maximum of 3 buffers will be in use at a time per process.  An additional maximum of 256K per process may be used for zlib buffers.

                        Size can be entered in bytes (default) or KB, MB, GB, TB, or PB where the multiplier is a power of 1024. For example, the case-insensitive value 32k (or 32KB) can be used instead of 32768.

                        Allowed values, in bytes, are <id>16384</id>, <id>32768</id>, <id>65536</id>, <id>131072</id>, <id>262144</id>, <id>524288</id>, <id>1048576</id>, <id>2097152</id>, <id>4194304</id>, <id>8388608</id>, and <id>16777216</id>.</text>

                        <example>32K</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - CMD-SSH KEY -->
                    <config-key id="cmd-ssh" name="SSH client command">
                        <summary>Path to ssh client executable.</summary>

                        <text>Use a specific SSH client when an alternate is desired or the <file>ssh</file> executable is not in $PATH.</text>

                        <example>/usr/bin/ssh</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - COMPRESS -->
                    <config-key id="compress" name="Compress">
                        <summary>Use gzip file compression.</summary>

                        <text>Backup files are compatible with command-line gzip tools.</text>

                        <example>n</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - COMPRESS-LEVEL KEY -->
                    <config-key id="compress-level" name="Compress Level">
                        <summary>Compression level for stored files.</summary>

                        <text>Sets the zlib level to be used for file compression when <setting>compress=y</setting>.</text>

                        <allow>0-9</allow>
                        <example>9</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - COMPRESS-LEVEL-NETWORK KEY -->
                    <config-key id="compress-level-network" name="Network Compress Level">
                        <summary>Compression level for network transfer when <setting>compress=n</setting>.</summary>

                        <text>Sets the zlib level to be used for protocol compression when <setting>compress=n</setting> and the database cluster is not on the same host as the repository.  Protocol compression is used to reduce network traffic but can be disabled by setting <setting>compress-level-network=0</setting>.  When <setting>compress=y</setting> the <setting>compress-level-network</setting> setting is ignored and <setting>compress-level</setting> is used instead so that the file is only compressed once.  SSH compression is always disabled.</text>

                        <allow>0-9</allow>
                        <example>1</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - DB-TIMEOUT KEY -->
                    <config-key id="db-timeout" name="Database Timeout">
                        <summary>Database query timeout.</summary>

                        <text>Sets the timeout, in seconds, for queries against the database.  This includes the <code>pg_start_backup()</code> and <code>pg_stop_backup()</code> functions which can each take a substantial amount of time.  Because of this the timeout should be kept high unless you know that these functions will return quickly (i.e. if you have set <setting>startfast=y</setting> and you know that the database cluster will not generate many WAL segments during the backup).</text>

                        <example>600</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - DELTA OPTION -->
                    <config-key id="delta" name="Delta">
                        <summary>Restore or backup using checksums.</summary>

                        <text>During a restore, by default the <postgres/> data and tablespace directories are expected to be present but empty.  This option performs a delta restore using checksums.

                        During a backup, this option will use checksums instead of the timestamps to determine if files will be copied.</text>

                        <example>y</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - LOCK-PATH KEY -->
                    <config-key id="lock-path" name="Lock Path">
                        <summary>Path where lock files are stored.</summary>

                        <text>The lock path provides a location for <backrest/> to create lock files to prevent conflicting operations from being run concurrently.</text>

                        <example>/backup/db/lock</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - NEUTRAL-UMASK -->
                    <config-key id="neutral-umask" name="Neutral Umask">
                        <summary>Use a neutral umask.</summary>

                        <text>Sets the umask to 0000 so modes in the repository are created in a sensible way.  The default directory mode is 0750 and default file mode is 0640.  The lock and log directories set the directory and file mode to 0770 and 0660 respectively.

                        To use the executing user's umask instead specify <setting>neutral-umask=n</setting> in the config file or <setting>--no-neutral-umask</setting> on the command line.</text>

                        <example>n</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - LOG-PATH KEY -->
                    <config-key id="spool-path" name="Spool Path">
                        <summary>Path where transient data is stored.</summary>

                        <text>This path is used to store data for the asynchronous <cmd>archive-push</cmd> and <cmd>archive-get</cmd> command.

                        The asynchronous <cmd>archive-push</cmd> command writes acknowledgements into the spool path when it has successfully stored WAL in the archive (and errors on failure) so the foreground process can quickly notify <postgres/>. Acknowledgement files are very small (zero on success and a few hundred bytes on error).

                        The asynchronous <cmd>archive-push</cmd> process queues WAL in the spool path so it can be provided very quickly when <postgres/> requests it.  Moving files to <postgres/> is most efficient when the spool path is on the same filesystem as <path>pg_xlog</path>/<path>pg_wal</path>.

                        The data stored in the spool path is not strictly temporary since it can and should survive a reboot.  However, loss of the data in the spool path is not a problem.  <backrest/> will simply recheck each WAL segment to ensure it is safely archived for <cmd>archive-push</cmd> and rebuild the queue for <cmd>archive-get</cmd>.

                        The spool path is intended to be located on a local Posix-compatible filesystem, not a remote filesystem such as <proper>NFS</proper> or <proper>CIFS</proper>.</text>

                        <example>/backup/db/spool</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - PROCESS-MAX -->
                    <config-key id="process-max" name="Process Maximum">
                        <summary>Max processes to use for compress/transfer.</summary>

                        <text>Each process will perform compression and transfer to make the command run faster, but don't set <setting>process-max</setting> so high that it impacts database performance.</text>

                        <example>4</example>
                    </config-key>

                    <!-- CONFIG - GENERAL SECTION - PROTOCOL-TIMEOUT KEY -->
                    <config-key id="protocol-timeout" name="Protocol Timeout">
                        <summary>Protocol timeout.</summary>

                        <text>Sets the timeout, in seconds, that the local or remote process will wait for a new message to be received on the protocol layer.  This prevents processes from waiting indefinitely for a message.  The <br-option>protocol-timeout</br-option> option must be greater than the <br-option>db-timeout</br-option> option.</text>

                        <example>630</example>
                    </config-key>
                </config-key-list>
            </config-section>

            <!-- CONFIG - REPO -->
            <config-section id="repository" name="Repository">
                <text>The <setting>repository</setting> section defines options used to configure the repository.

                <b>Indexing</b>: All <setting>repo-</setting> options are indexed to allow for configuring multiple repositories, though only a single repository is currently supported. For example, the repository is configured with the <setting>repo1-path</setting>, <setting>repo1-host</setting>, etc. options.

                The <setting>repo-retention-*</setting> options define how long backups will be retained.  Expiration only occurs when the number of complete backups exceeds the allowed retention.  In other words, if retention-full is set to 2, then there must be 3 complete backups before the oldest will be expired.  Make sure you always have enough space for retention + 1 backups.</text>

                <config-key-list>
                    <!-- CONFIG - REPO SECTION - REPO-HOST KEY -->
                    <config-key id="repo-host" name="Repository Host">
                        <summary>Repository host when operating remotely via SSH.</summary>

                        <text>Make sure that trusted SSH authentication is configured between the <postgres/> host and the repository host.

                        When backing up and archiving to a locally mounted filesystem this setting is not required.</text>

                        <example>repo1.domain.com</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-HOST-CMD KEY -->
                    <config-key id="repo-host-cmd" name="Repository Host Command">
                        <summary><backrest/> exe path on the repository host.</summary>

                        <text>Required only if the path to <exe/> is different on the local and repository hosts.  If not defined, the repository host exe path will be set the same as the local exe path.</text>

                        <default>same as local</default>
                        <example>/usr/lib/backrest/bin/pgbackrest</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-HOST-CONFIG KEY -->
                    <config-key id="repo-host-config" name="Repository Host Configuration">
                        <summary><backrest/> repository host configuration file.</summary>

                        <text>Sets the location of the configuration file on the repository host.  This is only required if the repository host configuration file is in a different location than the local configuration file.</text>

                        <example>/conf/pgbackrest/pgbackrest.conf</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-HOST-CONFIG-INCLUDE-PATH KEY -->
                    <config-key id="repo-host-config-include-path" name="Repository Host Configuration Include Path">
                        <summary><backrest/> repository host configuration include path.</summary>

                        <text>Sets the location of the configuration include path on the repository host.  This is only required if the repository host configuration include path is in a different location than the local configuration include path.</text>

                        <example>/conf/pgbackrest/conf.d</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-HOST-CONFIG-PATH KEY -->
                    <config-key id="repo-host-config-path" name="Repository Host Configuration Path">
                        <summary><backrest/> repository host configuration path.</summary>

                        <text>Sets the location of the configuration path on the repository host.  This is only required if the repository host configuration path is in a different location than the local configuration path.</text>

                        <example>/conf/pgbackrest</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-HOST-USER KEY -->
                    <config-key id="repo-host-user" name="Repository Host User">
                        <summary>Repository host user when <setting>repo-host</setting> is set.</summary>

                        <text>Defines the user that will be used for operations on the repository host.  Preferably this is not the <id>postgres</id> user but rather some other user like <id>pgbackrest</id>.  If <postgres/> runs on the repository host the <id>postgres</id> user can be placed in the <id>pgbackrest</id> group so it has read permissions on the repository without being able to damage the contents accidentally.</text>

                        <example>repo-user</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-HOST-PORT KEY -->
                    <config-key id="repo-host-port" name="Repository Host Port">
                        <summary>Repository host port when <setting>repo-host</setting> is set.</summary>

                        <text>Use this option to specify a non-default port for the repository host protocol.  Currently only SSH is supported</text>

                        <example>25</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-HARDLINK -->
                    <config-key id="repo-hardlink" name="Repository Hardlink">
                        <summary>Hardlink files between backups in the repository.</summary>

                        <text>Enable hard-linking of files in differential and incremental backups to their full backups.  This gives the appearance that each backup is a full backup at the file-system level.  Be careful, though, because modifying files that are hard-linked can affect all the backups in the set.</text>

                        <example>y</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-PATH KEY -->
                    <config-key id="repo-path" name="Repository Path">
                        <summary>Path where backups and archive are stored.</summary>

                        <text>The repository is where <backrest/> stores backups and archives WAL segments.

                        It may be difficult to estimate in advance how much space you'll need.  The best thing to do is take some backups then record the size of different types of backups (full/incr/diff) and measure the amount of WAL generated per day.  This will give you a general idea of how much space you'll need, though of course requirements will likely change over time as your database evolves.</text>

                        <example>/backup/db/backrest</example>
                    </config-key>

                    <!-- CONFIG - RETENTION SECTION - REPO-FULL-RETENTION KEY -->
                    <config-key id="repo-retention-full" name="Full Retention">
                        <summary>Number of full backups to retain.</summary>

                        <text>When a full backup expires, all differential and incremental backups associated with the full backup will also expire.  When the option is not defined a warning will be issued.  If indefinite retention is desired then set the option to the max value.</text>

                        <example>2</example>
                    </config-key>

                    <!-- CONFIG - RETENTION SECTION - REPO-DIFFERENTIAL-RETENTION KEY -->
                    <config-key id="repo-retention-diff" name="Differential Retention">
                        <summary>Number of differential backups to retain.</summary>

                        <text>When a differential backup expires, all incremental backups associated with the differential backup will also expire.  When not defined all differential backups will be kept until the full backups they depend on expire.</text>

                        <example>3</example>
                    </config-key>

                    <!-- CONFIG - RETENTION SECTION - REPO-ARCHIVE-RETENTION-TYPE KEY -->
                    <config-key id="repo-retention-archive-type" name="Archive Retention Type">
                        <summary>Backup type for WAL retention.</summary>

                        <text>If set to <setting>full</setting> <backrest/> will keep archive logs for the number of full backups defined by <setting>repo-retention-archive</setting>.  If set to <setting>diff</setting> (differential) <backrest/> will keep archive logs for the number of full and differential backups defined by <setting>repo-retention-archive</setting>, meaning if the last backup taken was a full backup, it will be counted as a differential for the purpose of repo-retention.  If set to <setting>incr</setting> (incremental) <backrest/> will keep archive logs for the number of full, differential, and incremental backups defined by <setting>repo-retention-archive</setting>. It is recommended that this setting not be changed from the default which will only expire WAL in conjunction with expiring full backups.</text>

                        <example>diff</example>
                    </config-key>

                    <!-- CONFIG - RETENTION SECTION - REPO-ARCHIVE-RETENTION KEY -->
                    <config-key id="repo-retention-archive" name="Archive Retention">
                        <summary>Number of backups worth of continuous WAL to retain.</summary>

                        <text><admonition type="note">WAL segments required to make a backup consistent are always retained until the backup is expired regardless of how this option is configured.</admonition>If this value is not set, then the archive to expire will default to the <setting>repo-retention-full</setting> (or <setting>repo-retention-diff</setting>) value corresponding to the <setting>repo-retention-archive-type</setting> if set to <setting>full</setting> (or <setting>diff</setting>). This will ensure that WAL is only expired for backups that are already expired.

                        This option must be set if <setting>repo-retention-archive-type</setting> is set to <setting>incr</setting>.  If disk space is at a premium, then this setting, in conjunction with <setting>repo-retention-archive-type</setting>, can be used to aggressively expire WAL segments. However, doing so negates the ability to perform PITR from the backups with expired WAL and is therefore <b>not</b> recommended.</text>

                        <example>2</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-KEY KEY -->
                    <config-key id="repo-s3-key" name="S3 Repository Access Key">
                        <summary>S3 repository access key.</summary>

                        <text>AWS key used to access this bucket.</text>

                        <example>AKIAIOSFODNN7EXAMPLE</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-KEY-SECRET KEY -->
                    <config-key id="repo-s3-key-secret" name="S3 Repository Secret Access Key">
                        <summary>S3 repository secret access key.</summary>

                        <text>AWS secret key used to access this bucket.</text>

                        <example>wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-TOKEN KEY -->
                    <config-key id="repo-s3-token" name="S3 Repository Security Token">
                        <summary>S3 repository security token.</summary>

                        <text>AWS security token used with temporary credentials.</text>

                        <example>AQoDYXdzEPT//////////wEXAMPLEtc764bNrC9SAPBSM22 ...</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-BUCKET KEY -->
                    <config-key id="repo-s3-bucket" name="S3 Repository Bucket">
                        <summary>S3 repository bucket.</summary>

                        <text>S3 bucket used to store the repository.

                        <backrest/> repositories can be stored in the bucket root by setting <br-option>repo-path=/</br-option> but it is usually best to specify a prefix, such as <path>/repo</path>, so logs and other AWS generated content can also be stored in the bucket.</text>

                        <example>pg-backup</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-CA-FILE KEY -->
                    <config-key id="repo-s3-ca-file" name="S3 SSL CA File">
                        <summary>S3 SSL CA File.</summary>

                        <text>Use a CA file other than the system default.</text>

                        <example>/etc/pki/tls/certs/ca-bundle.crt</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-CA-PATH KEY -->
                    <config-key id="repo-s3-ca-path" name="S3 SSL CA Path">
                        <summary>S3 SSL CA Path.</summary>

                        <text>Use a CA path other than the system default.</text>

                        <example>/etc/pki/tls/certs</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-ENDPOINT KEY -->
                    <config-key id="repo-s3-endpoint" name="S3 Repository Endpoint">
                        <summary>S3 repository endpoint.</summary>

                        <text>The AWS end point should be valid for the selected region.</text>

                        <example>s3.amazonaws.com</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-HOST KEY -->
                    <config-key id="repo-s3-host" name="S3 Repository Host">
                        <summary>S3 repository host.</summary>

                        <text>Connect to a host other than the end point.  This is typically used for testing.</text>

                        <example>127.0.0.1</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-REGION KEY -->
                    <config-key id="repo-s3-region" name="S3 Repository Region">
                        <summary>S3 repository region.</summary>

                        <text>The AWS region where the bucket was created.</text>

                        <example>us-east-1</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-S3-VERIFY-SSL KEY -->
                    <config-key id="repo-s3-verify-ssl" name="S3 Repository Verify SSL">
                        <summary>Verify S3 server certificate.</summary>

                        <text>Disables verification of the S3 server certificate.  This should only be used for testing or other scenarios where a certificate has been self-signed.</text>

                        <example>n</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-TYPE KEY -->
                    <config-key id="repo-type" name="Repository Type">
                        <summary>Type of storage used for the repository.</summary>

                        <text>The following repository types are supported:
                        <ul>
                            <li><id>cifs</id> - Like <id>posix</id>, but disables links and directory fsyncs</li>
                            <li><id>posix</id> - Posix-compliant file systems</li>
                            <li><id>s3</id> - AWS Simple Storage Service</li>
                        </ul></text>

                        <example>cifs</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-CIPHER-TYPE KEY -->
                    <config-key id="repo-cipher-type" name="Repository Cipher Type">
                        <summary>Cipher used to encrypt the repository.</summary>

                        <text>The following repository types are supported:
                        <ul>
                            <li><id>none</id> - The repository is not encrypted</li>
                            <li><id>aes-256-cbc</id> - Advanced Encryption Standard with 256 bit key length</li>
                        </ul>Note that encryption is always performed client-side even if the repository type (e.g. S3) supports encryption.</text>

                        <default>none</default>
                        <example>aes-256-cbc</example>
                    </config-key>

                    <!-- CONFIG - REPO SECTION - REPO-CIPHER-PASS KEY -->
                    <config-key id="repo-cipher-pass" name="Repository Cipher Passphrase">
                        <summary>Repository cipher passphrase.</summary>

                        <text>Passphrase used to encrypt/decrypt files of the repository.</text>

                        <example>zWaf6XtpjIVZC5444yXB+cgFDFl7MxGlgkZSaoPvTGirhPygu4jOKOXf9LO4vjfO</example>
                    </config-key>
                </config-key-list>
            </config-section>

            <!-- CONFIG - BACKUP -->
            <config-section id="backup" name="Backup">
                <text>The <setting>backup</setting> section defines settings related to backup.</text>

                <config-key-list>
                    <!-- CONFIG - BACKUP SECTION - ARCHIVE-CHECK -->
                    <config-key id="archive-check" name="Check Archive">
                        <summary>Check that WAL segments are in the archive before backup completes.</summary>

                        <text>Checks that all WAL segments required to make the backup consistent are present in the WAL archive.  It's a good idea to leave this as the default unless you are using another method for archiving.

                        This option must be enabled if <br-option>archive-copy</br-option> is enabled.</text>

                        <example>n</example>
                    </config-key>

                    <!-- CONFIG - BACKUP SECTION - ARCHIVE-COPY -->
                    <config-key id="archive-copy" name="Copy Archive">
                        <summary>Copy WAL segments needed for consistency to the backup.</summary>

                        <text>This slightly paranoid option protects against corruption in the WAL segment archive by storing the WAL segments required for consistency directly in the backup.  WAL segments are still stored in the archive so this option will use additional space.

                        On restore, the WAL segments will be present in <path>pg_xlog/pg_wal</path> and <postgres/> will use them in preference to calling the <code>restore_command</code>.

                        The <br-option>archive-check</br-option> option must be enabled if <br-option>archive-copy</br-option> is enabled.</text>

                        <example>y</example>
                    </config-key>

                    <!-- CONFIG - BACKUP SECTION - BACKUP-STANDBY KEY -->
                    <config-key id="backup-standby" name="Backup from Standby">
                        <summary>Backup from the standby cluster.</summary>

                        <text>Enable backup from standby to reduce load on the primary cluster.  This option requires that both the <host>primary</host> and <host>standby</host> hosts be configured.</text>

                        <example>y</example>
                    </config-key>

                    <!-- CONFIG - BACKUP SECTION - CHECKSUM-PAGE KEY -->
                    <config-key id="checksum-page" name="Page Checksums">
                        <summary>Validate data page checksums.</summary>

                        <text>Directs <backrest/> to validate all data page checksums while backing up a cluster.  This option is automatically enabled when data page checksums are enabled on the cluster.

                        Failures in checksum validation will not abort a backup.  Rather, warnings will be emitted in the log (and to the console with default settings) and the list of invalid pages will be stored in the backup manifest.</text>

                        <example>n</example>
                    </config-key>

                    <!-- CONFIG - BACKUP SECTION - EXCLUDE KEY -->
                    <config-key id="exclude" name="Path/File Exclusions">
                        <summary>Exclude paths/files from the backup.</summary>

                        <text>All exclusions are relative to <path>$PGDATA</path>. If the exclusion ends with / then only files in the specified directory will be excluded, e.g. <br-option>--exclude=junk/</br-option> will exclude all files in the <path>$PGDATA/junk</path> directory but include the directory itself.  If the exclusion does not end with / then the file may match the exclusion exactly or match with / appended to the exclusion, e.g. <br-option>--exclude=junk</br-option> will exclude the <path>$PGDATA/junk</path> directory and all the files it contains.

                        <b>Be careful using this feature -- it is very easy to exclude something critical that will make the backup inconsistent.  Be sure to test your restores!</b>

                        All excluded files will be logged at <id>info</id> level along with the exclusion rule.  Be sure to audit the list of excluded files to ensure nothing unexpected is being excluded.<admonition type="note">Exclusions are not honored on delta restores.  Any files/directories that were excluded by the backup will be <i>removed</i> on delta restore.</admonition>This option should not be used to exclude <postgres/> logs from a backup.  Logs can be moved out of the <id>PGDATA</id> directory using the <postgres/> <setting>log_directory</setting> setting, which has the benefit of allowing logs to be preserved after a restore.

                        Multiple exclusions may be specified on the command-line or in a configuration file.</text>

                        <example>junk/</example>
                    </config-key>

                    <!-- CONFIG - BACKUP SECTION - MANIFEST-SAVE-THRESHOLD -->
                    <config-key id="manifest-save-threshold" name="Manifest Save Threshold">
                        <summary>Manifest save threshold during backup.</summary>

                        <text>Defines how often the manifest will be saved during a backup.  Saving the manifest is important because it stores the checksums and allows the resume function to work efficiently.  The actual threshold used is 1% of the backup size or <setting>manifest-save-threshold</setting>, whichever is greater.

                        Size can be entered in bytes (default) or KB, MB, GB, TB, or PB where the multiplier is a power of 1024.</text>

                        <example>5G</example>
                    </config-key>

                    <!-- CONFIG - BACKUP SECTION - RESUME -->
                    <config-key id="resume" name="Resume">
                        <summary>Allow resume of failed backup.</summary>

                        <text>Defines whether the resume feature is enabled.  Resume can greatly reduce the amount of time required to run a backup after a previous backup of the same type has failed.  It adds complexity, however, so it may be desirable to disable in environments that do not require the feature.</text>

                        <example>n</example>
                    </config-key>

                    <!-- CONFIG - BACKUP SECTION - START-FAST -->
                    <config-key id="start-fast" name="Start Fast">
                        <summary>Force a checkpoint to start backup quickly.</summary>

                        <text>Forces a checkpoint (by passing <id>y</id> to the <id>fast</id> parameter of <code>pg_start_backup()</code>) so the backup begins immediately.  Otherwise the backup will start after the next regular checkpoint.

                        This feature only works in <postgres/> &gt;= <id>8.4</id>.</text>

                        <example>y</example>
                    </config-key>

                    <!-- CONFIG - BACKUP SECTION - STOP-AUTO -->
                    <config-key id="stop-auto" name="Stop Auto">
                        <summary>Stop prior failed backup on new backup.</summary>

                        <text>This will only be done if an exclusive advisory lock can be acquired to demonstrate that the prior failed backup process has really stopped.

                        This feature relies on pg_is_in_backup() so only works on <postgres/> >= <id>9.3</id>.

                        The setting is disabled by default because it assumes that <backrest/> is the only process doing exclusive online backups.  It depends on an advisory lock that only <backrest/> sets so it may abort other processes that do exclusive online backups.  Note that <cmd>base_backup</cmd> and <cmd>pg_dump</cmd> are safe to use with this setting because they do not call <code>pg_start_backup()</code> so are not exclusive.</text>

                        <example>y</example>
                    </config-key>
                </config-key-list>
            </config-section>

            <!-- CONFIG - ARCHIVE -->
            <config-section id="archive" name="Archive">
                <text>The <setting>archive</setting> section defines options for the <cmd>archive-push</cmd> and <cmd>archive-get</cmd> commands.</text>

                <config-key-list>
                    <!-- CONFIG - ARCHIVE SECTION - ARCHIVE-ASYNC KEY -->
                    <config-key id="archive-async" name="Asynchronous Archiving">
                        <summary>Push/get WAL segments asynchronously.</summary>

                        <text>Enables asynchronous operation for the <cmd>archive-push</cmd> and <cmd>archive-get</cmd> commands.

                        Asynchronous operation is more efficient because it can reuse connections and take advantage of parallelism.  See the <br-option>spool-path</br-option>, <br-option>archive-get-queue-max</br-option>, and <br-option>archive-push-queue-max</br-option> options for more information.</text>

                        <example>y</example>
                    </config-key>

                    <!-- CONFIG - ARCHIVE SECTION - ARCHIVE-GET-QUEUE-MAX KEY -->
                    <config-key id="archive-get-queue-max" name="Maximum Archive Get Queue Size">
                        <summary>Maximum size of the <backrest/> archive-get queue.</summary>

                        <text>Specifies the maximum size of the <cmd>archive-get</cmd> queue when <br-option>archive-async</br-option> is enabled.  The queue is stored in the <br-option>spool-path</br-option> and is used to speed providing WAL to <postgres/>.

                        Size can be entered in bytes (default) or KB, MB, GB, TB, or PB where the multiplier is a power of 1024.</text>

                        <example>1073741824</example>
                    </config-key>

                    <!-- CONFIG - ARCHIVE SECTION - ARCHIVE-QUEUE-MAX KEY -->
                    <config-key id="archive-push-queue-max" name="Maximum Archive Push Queue Size">
                        <summary>Maximum size of the <postgres/> archive queue.</summary>

                        <text>After the limit is reached, the following will happen:
                        <ol>
                            <li><backrest/> will notify <postgres/> that the WAL was successfully archived, then <b>DROP IT</b>.</li>
                            <li>A warning will be output to the Postgres log.</li>

                        </ol>If this occurs then the archive log stream will be interrupted and PITR will not be possible past that point.  A new backup will be required to regain full restore capability.

                        In asynchronous mode the entire queue will be dropped to prevent spurts of WAL getting through before the queue limit is exceeded again.

                        The purpose of this feature is to prevent the log volume from filling up at which point Postgres will stop completely.  Better to lose the backup than have <postgres/> go down.

                        Size can be entered in bytes (default) or KB, MB, GB, TB, or PB where the multiplier is a power of 1024.</text>

                        <example>1GB</example>
                    </config-key>

                    <!-- ======================================================================================================= -->
                    <config-key id="archive-timeout" name="Archive Timeout">
                        <summary>Archive timeout.</summary>

                        <text>Set maximum time, in seconds, to wait for each WAL segment to reach the <backrest/> archive repository.  The timeout applies to the <cmd>check</cmd> and <cmd>backup</cmd> commands when waiting for WAL segments required for backup consistency to be archived.</text>

                        <example>30</example>
                    </config-key>
                </config-key-list>
            </config-section>

            <!-- CONFIG - RESTORE -->
            <config-section id="restore" name="Restore">
                <text>The <setting>restore</setting> section defines settings used for restoring backups.</text>

                <config-key-list>
                    <!-- CONFIG - RESTORE SECTION - DB-INCLUDE KEY -->
                    <config-key id="db-include" name="Include Database">
                        <summary>Restore only specified databases.</summary>

                        <text>This feature allows only selected databases to be restored.  Databases not specifically included will be restored as sparse, zeroed files to save space but still allow <postgres/> to perform recovery.  After recovery the databases that were not included will not be accessible but can be removed with the <id>drop database</id> command. <admonition type="note">built-in databases (<id>template0</id>, <id>template1</id>, and <id>postgres</id>) are always restored.</admonition>The <setting>{[dash]}-db-include</setting> option can be passed multiple times to specify more than one database to include.</text>

                        <example>db_main</example>
                    </config-key>

                    <!-- CONFIG - RESTORE SECTION - LINK-ALL KEY -->
                    <config-key id="link-all" name="Link All">
                        <summary>Restore all symlinks.</summary>

                        <text>By default symlinked directories and files are restored as normal directories and files in $PGDATA.  This is because it may not be safe to restore symlinks to their original destinations on a system other than where the original backup was performed.  This option restores all the symlinks just as they were on the original system where the backup was performed.</text>

                        <example>y</example>
                    </config-key>

                    <!-- CONFIG - RESTORE SECTION - LINK-MAP KEY -->
                    <config-key id="link-map" name="Link Map">
                        <summary>Modify the destination of a symlink.</summary>

                        <text>Allows the destination file or path of a symlink to be changed on restore.  This is useful for restoring to systems that have a different storage layout than the original system where the backup was generated.</text>

                        <example>pg_xlog=/data/xlog</example>
                    </config-key>

                    <!-- CONFIG - RESTORE SECTION - RECOVERY-OPTION KEY -->
                    <config-key id="recovery-option" name="Recovery Option">
                        <summary>Set an option in <file>recovery.conf</file>.</summary>

                        <text>See http://www.postgresql.org/docs/X.X/static/recovery-config.html for details on recovery.conf options (replace X.X with your <postgres/> version).  This option can be used multiple times.<admonition type="note">The <setting>restore_command</setting> option will be automatically generated but can be overridden with this option.  Be careful about specifying your own <setting>restore_command</setting> as <backrest/> is designed to handle this for you.  Target Recovery options (recovery_target_name, recovery_target_time, etc.) are generated automatically by <backrest/> and should not be set with this option.</admonition>Since <backrest/> does not start <postgres/> after writing the <file>recovery.conf</file> file, it is always possible to edit/check <file>recovery.conf</file> before manually restarting.</text>

                        <example>primary_conninfo=db.mydomain.com</example>
                    </config-key>

                    <!-- CONFIG - RESTORE SECTION - TABLESPACE-MAP KEY -->
                    <config-key id="tablespace-map" name="Tablespace Map">
                        <summary>Restore a tablespace into the specified directory.</summary>

                        <text>Moves a tablespace to a new location during the restore.  This is useful when tablespace locations are not the same on a replica, or an upgraded system has different mount points.

                        Since <postgres/> 9.2 tablespace locations are not stored in pg_tablespace so moving tablespaces can be done with impunity.  However, moving a tablespace to the <setting>data_directory</setting> is not recommended and may cause problems.  For more information on moving tablespaces http://www.databasesoup.com/2013/11/moving-tablespaces.html is a good resource.</text>

                        <example>ts_01=/db/ts_01</example>
                    </config-key>

                    <!-- CONFIG - RESTORE SECTION - TABLESPACE KEY -->
                    <config-key id="tablespace-map-all" name="Map All Tablespaces">
                        <summary>Restore all tablespaces into the specified directory.</summary>

                        <text>By default tablespaces are restored into their original locations and while this behavior can be modified by with the <setting>tablespace-map</setting> open it is sometime preferable to remap all tablespaces to a new directory all at once.  This is particularly useful for development or staging systems that may not have the same storage layout as the original system where the backup was generated.

                        The path specified will be the parent path used to create all the tablespaces in the backup.</text>

                        <example>/data/tablespace</example>
                    </config-key>
                </config-key-list>
            </config-section>

            <!-- CONFIG - STANZA -->
            <config-section id="stanza" name="Stanza">
                <text>A stanza defines the backup configuration for a specific <postgres/> database cluster.  The stanza section must define the database cluster path and host/user if the database cluster is remote.  Also, any global configuration sections can be overridden to define stanza-specific settings.

                <b>Indexing</b>: All <setting>pg-</setting> options are indexed to allow for configuring multiple <postgres/> hosts. For example, a single master is configured with the <setting>pg1-path</setting>, <setting>pg1-host</setting>, etc. options.  If a standby is configured then index the <setting>pg-</setting> options as <setting>pg2-</setting> (e.g. pg2-host, pg2-path, etc).</text>

                <config-key-list>
                    <!-- CONFIG - STANZA SECTION - PG-HOST-CMD KEY -->
                    <config-key id="pg-host-cmd" name="PostgreSQL Host Command">
                        <summary><backrest/> exe path on the <postgres/> host.</summary>

                        <text>Required only if the path to <exe/> is different on the local and <postgres/> hosts.  If not defined, the database host exe path will be set the same as the local exe path.</text>

                        <default>same as local</default>
                        <example>/usr/lib/backrest/bin/pgbackrest</example>
                    </config-key>

                    <!-- CONFIG - STANZA SECTION - PG-HOST-CONFIG KEY -->
                    <config-key id="pg-host-config" name="PostgreSQL Host Configuration">
                        <summary><backrest/> database host configuration file.</summary>

                        <text>Sets the location of the configuration file on the <postgres/> host.  This is only required if the <postgres/> host configuration file is in a different location than the local configuration file.</text>

                        <example>/conf/pgbackrest/pgbackrest.conf</example>
                    </config-key>

                    <!-- CONFIG - STANZA SECTION - PG-HOST-CONFIG-INCLUDE-PATH KEY -->
                    <config-key id="pg-host-config-include-path" name="PostgreSQL Host Configuration Include Path">
                        <summary><backrest/> database host configuration include path.</summary>

                        <text>Sets the location of the configuration include path on the <postgres/> host.  This is only required if the <postgres/> host configuration include path is in a different location than the local configuration include path.</text>

                        <example>/conf/pgbackrest/conf.d</example>
                    </config-key>

                    <!-- CONFIG - STANZA SECTION - PG-HOST-CONFIG-PATH KEY -->
                    <config-key id="pg-host-config-path" name="PostgreSQL Host Configuration Path">
                        <summary><backrest/> database host configuration path.</summary>

                        <text>Sets the location of the configuration path on the <postgres/> host.  This is only required if the <postgres/> host configuration path is in a different location than the local configuration path.</text>

                        <example>/conf/pgbackrest</example>
                    </config-key>

                    <!-- CONFIG - STANZA SECTION - PG-HOST KEY -->
                    <config-key id="pg-host" name="PostgreSQL Host">
                        <summary><postgres/> host for operating remotely via SSH.</summary>

                        <text>Used for backups where the <postgres/> host is different from the repository host.</text>

                        <example>db.domain.com</example>
                    </config-key>

                    <!-- CONFIG - STANZA SECTION - PG-HOST-USER KEY -->
                    <config-key id="pg-host-user" name="PostgreSQL Host User">
                        <summary><postgres/> host logon user when <setting>pg-host</setting> is set.</summary>

                        <text>This user will also own the remote <backrest/> process and will initiate connections to <postgres/>.  For this to work correctly the user should be the <postgres/> database cluster owner which is generally <id>postgres</id>, the default.</text>

                        <example>db_owner</example>
                    </config-key>

                    <!-- CONFIG - STANZA SECTION - PG-PATH KEY -->
                    <config-key id="pg-path" name="PostgreSQL Path">
                        <summary><postgres/> data directory.</summary>

                        <text>This should be the same as the <setting>data_directory</setting> setting in <file>postgresql.conf</file>.  Even though this value can be read from <file>postgresql.conf</file> or <postgres/> it is prudent to set it in case those resources are not available during a restore or offline backup scenario.

                        The <setting>pg-path</setting> option is tested against the value reported by <postgres/> on every online backup so it should always be current.</text>

                        <example>/data/db</example>
                    </config-key>

                    <!-- CONFIG - STANZA SECTION - PG-PORT KEY -->
                    <config-key id="pg-port" name="PostgreSQL Port">
                        <summary><postgres/> port.</summary>

                        <text>Port that <postgres/> is running on.  This usually does not need to be specified as most <postgres/> clusters run on the default port.</text>

                        <example>6543</example>
                    </config-key>

                    <!-- CONFIG - STANZA SECTION - PG-SOCKET-PATH KEY -->
                    <config-key id="pg-socket-path" name="PostgreSQL Socket Path">
                        <summary><postgres/> unix socket path.</summary>

                        <text>The unix socket directory that was specified when <postgres/> was started.  <backrest/> will automatically look in the standard location for your OS so there is usually no need to specify this setting unless the socket directory was explicitly modified with the <setting>unix_socket_directory</setting> setting in <file>postgresql.conf</file>.</text>

                        <example>/var/run/postgresql</example>
                    </config-key>

                    <!-- CONFIG - STANZA SECTION - PG-HOST-PORT KEY -->
                    <config-key id="pg-host-port" name="PostgreSQL Host Port">
                        <summary><postgres/> host port when <setting>pg-host</setting> is set.</summary>

                        <text>Use this option to specify a non-default port for the <postgres/> host protocol.  Currently only SSH is supported</text>

                        <example>25</example>
                    </config-key>
                </config-key-list>
            </config-section>
        </config-section-list>
    </config>

    <!-- COMMAND -->
    <operation title="{[project]} Command Reference">
        <description>The {[project]} Command Reference details all commands and options.</description>

        <text>Commands are used to execute the various <backrest/> functions.  Here the command options are listed exhaustively, that is, each option applicable to a command is listed with that command even if it applies to one or more other commands.  This includes all the options that may also configured in <file>pgbackrest.conf</file>.

        Non-boolean options configured in <file>pgbackrest.conf</file> can be reset to default on the command-line by using the <id>reset-</id> prefix.  This feature may be used to restore a backup directly on a repository host.  Normally, <backrest/> will error because it can see that the database host is remote and restores cannot be done remotely.  By adding <br-option>--reset-pg1-host</br-option> on the command-line, <backrest/> will ignore the remote database host and restore locally.  It may be necessary to pass a new <br-option>--pg-path</br-option> to force the restore to happen in a specific path, i.e. not the path used on the database host.

        The <id>no-</id> prefix may be used to set a boolean option to false on the command-line.

        Any option may be set in an environment variable using the <id>PGBACKREST_</id> prefix and the option name in all caps replacing <id>-</id> with <id>_</id>, e.g. <br-option>pg1-path</br-option> becomes <id>PGBACKREST_PG1_PATH</id> and <br-option>stanza</br-option> becomes <id>PGBACKREST_STANZA</id>.  Boolean options are represented as they would be in a configuration file, e.g. <id>PGBACKREST_COMPRESS="n"</id>, and <id>reset-*</id> variants are not allowed.  Options that that can be specified multiple times on the command-line or in a config file can be represented by separating the values with colons, e.g. <id>PGBACKREST_DB_INCLUDE="db1:db2"</id>.

        Command-line options override environment options which override config file options.</text>

        <operation-general title="General Options">
            <option-list>
                <!-- OPERATION - GENERAL - CONFIG OPTION -->
                <option id="config" name="Config">
                    <summary><backrest/> configuration file.</summary>

                    <text>Use this option to specify a different configuration file than the default.</text>

                    <example>/conf/pgbackrest/pgbackrest.conf</example>
                </option>

                <!-- OPERATION - GENERAL - CONFIG INCLUDE PATH OPTION -->
                <option id="config-include-path" name="Config Include Path">
                    <summary>Path to additional <backrest/> configuration files.</summary>

                    <text>Configuration files existing in the specified location with extension <file>.conf</file> will be concatenated with the <backrest/> configuration file, resulting in one configuration file.</text>

                    <example>/conf/pgbackrest/conf.d</example>
                </option>

                <!-- OPERATION - GENERAL - CONFIG PATH OPTION -->
                <option id="config-path" name="Config Path">
                    <summary>Base path of <backrest/> configuration files.</summary>

                    <text>This setting is used to override the default base path setting for the <br-option>--config</br-option> and <br-option>--config-include-path</br-option> options unless they are explicitly set on the command-line.

                    For example, passing only <code>--config-path=/conf/pgbackrest</code> results in the  <br-option>--config</br-option> default being set to <code>/conf/pgbackrest/pgbackrest.conf</code> and the <br-option>--config-include-path</br-option> default being set to  <code>/conf/pgbackrest/conf.d</code>.</text>

                    <example>/conf/pgbackrest</example>
                </option>

                <!-- OPERATION - GENERAL - STANZA OPTION -->
                <option id="stanza" name="Stanza">
                    <summary>Defines the stanza.</summary>

                    <text>A stanza is the configuration for a <postgres/> database cluster that defines where it is located, how it will be backed up, archiving options, etc.  Most db servers will only have one Postgres database cluster and therefore one stanza, whereas backup servers will have a stanza for every database cluster that needs to be backed up.

                    It is tempting to name the stanza after the primary cluster but a better name describes the databases contained in the cluster.  Because the stanza name will be used for the primary and all replicas it is more appropriate to choose a name that describes the actual function of the cluster, such as app or dw, rather than the local cluster name, such as main or prod.</text>

                    <example>main</example>
                </option>
            </option-list>
        </operation-general>

        <command-list title="Commands">
            <!-- OPERATION - BACKUP COMMAND -->
            <command id="backup" name="Backup">
                <summary>Backup a database cluster.</summary>

                <text><backrest/> does not have a built-in scheduler so it's best to run it from cron or some other scheduling mechanism.</text>

                <option-list>
                    <!-- OPERATION - BACKUP COMMAND - TYPE OPTION -->
                    <option id="type" name="Type">
                        <summary>Backup type.</summary>

                        <text>The following backup types are supported:
                            <ul>
                                <li><id>full</id> - all database cluster files will be copied and there will be no dependencies on previous backups.</li>
                                <li><id>incr</id> - incremental from the last successful backup.</li>
                                <li><id>diff</id> - like an incremental backup but always based on the last full backup.</li>
                            </ul></text>

                        <example>full</example>
                    </option>

                    <!-- OPERATION - BACKUP COMMAND - FORCE OPTION -->
                    <option id="force" name="Force">
                        <summary>Force an offline backup.</summary>

                        <text>When used with <br-option>--no-start-stop</br-option> a backup will be run even if <backrest/> thinks that <postgres/> is running.  <b>This option should be used with extreme care as it will likely result in a bad backup.</b>

                        There are some scenarios where a backup might still be desirable under these conditions.  For example, if a server crashes and the database cluster volume can only be mounted read-only, it would be a good idea to take a backup even if <file>postmaster.pid</file> is present.  In this case it would be better to revert to the prior backup and replay WAL, but possibly there is a very important transaction in a WAL segment that did not get archived.</text>

                        <example>y</example>
                    </option>

                    <!-- ======================================================================================================= -->
                    <option id="online" name="Online">
                        <summary>Perform an online backup.</summary>

                        <text>Specifying --no-online prevents <backrest/> from running <code>pg_start_backup()</code> and <code>pg_stop_backup()</code> on the database cluster.  In order for this to work <postgres/> should be shut down and <backrest/> will generate an error if it is not.

                        The purpose of this option is to allow offline backups.  The <path>pg_xlog</path>/<path>pg_wal</path> directory is copied as-is and <setting>archive-check</setting> is automatically disabled for the backup.</text>

                        <example>n</example>
                    </option>
                </option-list>

                <command-example-list>
                    <command-example title="Full Backup">
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=db --type=full backup
                        </code-block>
                        Run a <id>full</id> backup on the <id>db</id> stanza.  <br-option>--type</br-option> can also be set to <id>incr</id> or <id>diff</id> for incremental or differential backups.  However, if no <id>full</id> backup exists then a <id>full</id> backup will be forced even if <id>incr</id> or <id>diff</id> is requested.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - ARCHIVE-PUSH COMMAND -->
            <command id="archive-push" name="Archive Push">
                <summary>Push a WAL segment to the archive.</summary>

                <text>The WAL segment may be pushed immediately to the archive or stored locally depending on the value of <setting>archive-async</setting></text>

                <command-example-list>
                    <command-example>
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=db archive-push %p
                        </code-block>
                        Accepts a WAL segment from <postgres/> and archives it in the repository defined by <setting>repo-path</setting>.  <id>%p</id> is how <postgres/> specifies the location of the WAL segment to be archived.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - ARCHIVE-GET COMMAND -->
            <command id="archive-get" name="Archive Get">
                <summary>Get a WAL segment from the archive.</summary>

                <text>WAL segments are required for restoring a <postgres/> cluster or maintaining a replica.</text>

                <command-example-list>
                    <command-example>
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=db archive-get %f %p
                        </code-block>
                        Retrieves a WAL segment from the repository.  This command is used in <file>recovery.conf</file> to restore a backup, perform PITR, or as an alternative to streaming for keeping a replica up to date.  <id>%f</id> is how <postgres/> specifies the WAL segment it needs and <id>%p</id> is the location where it should be copied.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - CHECK COMMAND -->
            <command id="check" name="Check">
                <summary>Check the configuration.</summary>

                <text>The <cmd>check</cmd> command validates that <backrest/> and the <pg-setting>archive_command</pg-setting> setting are configured correctly for archiving and backups. It detects misconfigurations, particularly in archiving, that result in incomplete backups because required WAL segments did not reach the archive. The command can be run on the database or the repository host.  The command may also be run on the standby host, however, since <code>pg_switch_xlog()</code>/<code>pg_switch_wal()</code> cannot be performed on the standby, the command will only test the repository configuration.

                Note that <code>pg_create_restore_point('pgBackRest Archive Check')</code> and <code>pg_switch_xlog()</code>/<code>pg_switch_wal()</code> are called to force <postgres/> to archive a WAL segment.  Restore points are only supported in <postgres/> &gt;= 9.1 so for older versions the <cmd>check</cmd> command may fail if there has been no write activity since the last log rotation, therefore it is recommended that activity be generated by the user if there have been no writes since the last WAL switch before running the <cmd>check</cmd> command.</text>

                <command-example-list>
                    <command-example>
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=db check
                        </code-block>
                        </text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - EXPIRE COMMAND -->
            <command id="expire" name="Expire">
                <summary>Expire backups that exceed retention.</summary>

                <text><backrest/> does backup rotation but is not concerned with when the backups were created.  If two full backups are configured for retention, <backrest/> will keep two full backups no matter whether they occur two hours or two weeks apart.</text>

                <command-example-list>
                    <command-example>
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=db expire
                        </code-block>
                        Expire (rotate) any backups that exceed the defined retention.  Expiration is run automatically after every successful backup, so there is no need to run this command separately unless you have reduced retention, usually to free up some space.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - RESTORE COMMAND -->
            <command id="restore" name="Restore">
                <summary>Restore a database cluster.</summary>

                <text>This command is generally run manually, but there are instances where it might be automated.</text>

                <option-list>
                    <!-- OPERATION - RESTORE COMMAND - SET OPTION -->
                    <option id="set" name="Set">
                        <summary>Backup set to restore.</summary>

                        <text>The backup set to be restored.  <id>latest</id> will restore the latest backup, otherwise provide the name of the backup to restore.</text>
                        <example>20150131-153358F_20150131-153401I</example>
                    </option>

                    <!-- OPERATION - RESTORE COMMAND - FORCE OPTION -->
                    <option id="force" name="Force">
                        <summary>Force a restore.</summary>

                        <text>By itself this option forces the <postgres/> data and tablespace paths to be completely overwritten.  In combination with <br-option>--delta</br-option> a timestamp/size delta will be performed instead of using checksums.</text>

                        <example>y</example>
                    </option>

                    <!-- OPERATION - RESTORE COMMAND - TYPE OPTION -->
                    <option id="type" name="Type">
                        <summary>Recovery type.</summary>

                        <text>The following recovery types are supported:
                        <ul>
                            <li><id>default</id> - recover to the end of the archive stream.</li>
                            <li><id>immediate</id> - recover only until the database becomes consistent. This option is only supported on <postgres/> &gt;= 9.4.</li>
                            <li><id>name</id> - recover the restore point specified in <br-option>--target</br-option>.</li>
                            <li><id>xid</id> - recover to the transaction id specified in <br-option>--target</br-option>.</li>
                            <li><id>time</id> - recover to the time specified in <br-option>--target</br-option>.</li>
                            <li><id>preserve</id> - preserve the existing <file>recovery.conf</file> file.</li>
                            <li><id>none</id> - no <file>recovery.conf</file> file is written so <postgres/> will attempt to achieve consistency using WAL segments present in <path>pg_xlog</path>/<path>pg_wal</path>.  Provide the required WAL segments or use the <setting>archive-copy</setting> setting to include them with the backup.</li>
                        </ul></text>
                        <example>xid</example>
                    </option>

                    <!-- OPERATION - RESTORE COMMAND - TARGET OPTION -->
                    <option id="target" name="Target">
                        <summary>Recovery target.</summary>

                        <text>Defines the recovery target when <br-option>--type</br-option> is <id>name</id>, <id>xid</id>, or <id>time</id>.</text>
                        <example>2015-01-30 14:15:11 EST</example>
                    </option>

                    <!-- OPERATION - RESTORE COMMAND - TARGET-EXCLUSIVE OPTION -->
                    <option id="target-exclusive" name="Target Exclusive">
                        <summary>Stop just before the recovery target is reached.</summary>

                        <text>Defines whether recovery to the target would be exclusive (the default is inclusive) and is only valid when <br-option>--type</br-option> is <id>time</id> or <id>xid</id>.  For example, using <br-option>--target-exclusive</br-option> would exclude the contents of transaction <id>1007</id> when <br-option>--type=xid</br-option> and <br-option>--target=1007</br-option>.  See the <setting>recovery_target_inclusive</setting> option in the <postgres/> docs for more information.</text>

                        <example>n</example>
                    </option>

                    <!-- OPERATION - RESTORE COMMAND - TARGET-RESUME OPTION -->
                    <option id="target-action" name="Target Action">
                        <summary>Action to take when recovery target is reached.</summary>

                        <text>This option is effective when <setting>hot_standby=on</setting> is configured in <file>postgresql.conf</file>, otherwise the cluster will be promoted when the target is reached or there is no more WAL in the archive.

                            The following actions are supported:
                        <ul>
                            <li><id>pause</id> - pause when recovery target is reached. (<postgres/> &gt;= 9.1)</li>
                            <li><id>promote</id> - promote and switch timeline when recovery target is reached. (<postgres/> &gt;= 9.1)</li>
                            <li><id>shutdown</id> - shutdown server when recovery target is reached. (<postgres/> &gt;= 9.5)</li>
                        </ul></text>

                        <example>promote</example>
                    </option>

                    <!-- OPERATION - RESTORE COMMAND - TARGET-TIMELINE OPTION -->
                    <option id="target-timeline" name="Target Timeline">
                        <summary>Recover along a timeline.</summary>

                        <text>See <setting>recovery_target_timeline</setting> in the <postgres/> docs for more information.</text>

                        <example>3</example>
                    </option>
                </option-list>

                <command-example-list>
                    <command-example title="Restore Latest">
                        <text><code-block title="">
                                {[backrest-exe]} --stanza=db --type=name --target=release restore
                            </code-block>
                            Restores the latest database cluster backup and then recovers to the <id>release</id> restore point.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - INFO COMMAND -->
            <command id="info" name="Info">
                <summary>Retrieve information about backups.</summary>

                <text>The <cmd>info</cmd> command operates on a single stanza or all stanzas.  Text output is the default and gives a human-readable summary of backups for the stanza(s) requested.  This format is subject to change with any release.

                For machine-readable output use <setting>--output=json</setting>.  The JSON output contains far more information than the text output and is kept stable unless a bug is found.</text>

                <option-list>
                    <!-- OPERATION - INFO COMMAND - OUTPUT OPTION -->
                    <option id="output" name="Output">
                        <summary>Output format.</summary>

                        <text>The following output types are supported:
                        <ul>
                            <li><id>text</id> - Human-readable summary of backup information.</li>
                            <li><id>json</id> - Exhaustive machine-readable backup information in JSON format.</li>
                        </ul></text>

                        <example>json</example>
                    </option>
                </option-list>

                <command-example-list>
                    <command-example title="Information for a single stanza">
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=db --output=json info
                        </code-block>

                        Get information about backups in the <id>db</id> stanza.</text>
                    </command-example>

                    <command-example title="Information for all stanzas">
                        <text><code-block title="">
                            {[backrest-exe]} --output=json info
                        </code-block>

                        Get information about backups for all stanzas in the repository.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - HELP COMMAND -->
            <command id="help" name="Help">
                <summary>Get help.</summary>

                <text>Three levels of help are provided.  If no command is specified then general help will be displayed.  If a command is specified then a full description of the command will be displayed along with a list of valid options.  If an option is specified in addition to a command then the a full description of the option as it applies to the command will be displayed.</text>

                <command-example-list>
                    <command-example title="Help for the backup command">
                        <text><code-block title="">
                            {[backrest-exe]} help backup
                        </code-block>

                        Get help for the backup command.</text>
                    </command-example>

                    <command-example title="Help for backup command, --force option">
                        <text><code-block title="">
                            {[backrest-exe]} help backup force
                        </code-block>

                        Get help for the force option of the backup command.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - START COMMAND -->
            <command id="start" name="Start">
                <summary>Allow <backrest/> processes to run.</summary>

                <text>If the <backrest/> processes were previously stopped using the <cmd>stop</cmd> command then they can be started again using the <cmd>start</cmd> command.  Note that this will not immediately start up any <backrest/> processes but they are allowed to run.</text>

                <command-example-list>
                    <command-example title="Start processes for stanza main">
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=main start
                        </code-block>

                        Allows <backrest/> processes to run for the <id>main</id> stanza.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - STOP COMMAND -->
            <command id="stop" name="Stop">
                <summary>Stop <backrest/> processes from running.</summary>

                <text>Does not allow any new <backrest/> processes to run.  By default running processes will be allowed to complete successfully.  Use the <setting>--force</setting> option to terminate running processes.

                <backrest/> processes will return an error if they are run after the stop command completes.</text>

                <option-list>
                    <!-- OPERATION - STOP COMMAND - FORCE OPTION -->
                    <option id="force" name="Force">
                        <summary>Force all <backrest/> processes to stop.</summary>

                        <text>This option will send TERM signals to all running <backrest/> processes to effect a graceful but immediate shutdown.  Note that this will also shutdown processes that were initiated on another system but have remotes running on the current system.  For instance, if a backup was started on the backup server then running <cmd>stop --force</cmd> on the database server will shutdown the backup process on the backup server.</text>

                        <example>y</example>
                    </option>
                </option-list>

                <command-example-list>
                    <command-example title="Stop processes for all stanzas">
                        <text><code-block title="">
                            {[backrest-exe]} stop
                        </code-block>

                        Stop new <backrest/> processes for all stanzas but allow any current process to complete.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - VERSION COMMAND -->
            <command id="version" name="Version">
                <summary>Get version.</summary>

                <text>Displays installed <backrest/> version.</text>

                <command-example-list>
                    <command-example title="Get version">
                        <text><code-block title="">
                            {[backrest-exe]} version
                        </code-block>

                        Get <backrest/> version.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - STANZA-CREATE COMMAND -->
            <command id="stanza-create" name="Stanza Create">
                <summary>Create the required stanza data.</summary>

                <text>The <cmd>stanza-create</cmd> command must be run on the host where the repository is located after the stanza has been configured in <file>pgbackrest.conf</file>.</text>

                <option-list>
                    <!-- OPERATION - STANZA-CREATE COMMAND - FORCE OPTION -->
                    <option id="force" name="Force">
                        <summary>Force stanza creation.</summary>

                        <text><admonition type="caution">Use <br-option>--force</br-option> only as a last resort, when all else fails.  If data is missing from the repository then the recreated <file>.info</file> files will likely be corrupt.</admonition>If the required stanza <file>.info</file> files do not exist in the repository but backups or WAL segments do exist, then this option can be used to force the stanza to be created from the existing data in the repository.  This is most likely to be useful after corruption or an incomplete restore of the repository from elsewhere.</text>

                        <example>n</example>
                    </option>

                    <!-- ======================================================================================================= -->
                    <option id="online" name="Online">
                        <summary>Create on an online cluster.</summary>

                        <text>Specifying --no-online prevents <backrest/> from connecting to <postgres/> when creating the stanza.</text>

                        <example>n</example>
                    </option>
                </option-list>

                <command-example-list>
                    <command-example title="Create required stanza data">
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=db stanza-create
                        </code-block>

                        Create the required data for the <id>db</id> stanza.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - STANZA-UPGRADE COMMAND -->
            <command id="stanza-upgrade" name="Stanza Upgrade">
                <summary>Upgrade a stanza.</summary>

                <text>Immediately after upgrading <postgres/> to a newer major version, the <br-option>pg-path</br-option> for all <backrest/> configurations must be set to the new database location and the <cmd>stanza-upgrade</cmd> run on the repository host. If the database is offline use the <br-option>--no-online</br-option> option.</text>

                <option-list>
                    <!-- ======================================================================================================= -->
                    <option id="online" name="Online">
                        <summary>Update an online cluster.</summary>

                        <text>Specifying --no-online prevents <backrest/> from connecting to <postgres/> when upgrading the stanza.</text>

                        <example>n</example>
                    </option>
                </option-list>

                <command-example-list>
                    <command-example title="Upgrade a stanza">
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=db stanza-upgrade
                        </code-block>

                        Upgrade the <id>db</id> stanza to a new version of <postgres/>.</text>
                    </command-example>
                </command-example-list>
            </command>

            <!-- OPERATION - STANZA-DELETE COMMAND -->
            <command id="stanza-delete" name="Stanza Delete">
                <summary>Delete a stanza.</summary>

                <text>The <cmd>stanza-delete</cmd> command removes data in the repository associated with a stanza.<admonition type="warning">Use this command with caution &amp;mdash; it will permanently remove all backups and archives from the <backrest/> repository for the specified stanza.</admonition>
                To delete a stanza:
                <ul>
                    <li>Shut down the <postgres/> cluster associated with the stanza (or use --force to override).</li>
                    <li>Run the <cmd>stop</cmd> command on the repository host.</li>
                    <li>Run the <cmd>stanza-delete</cmd> command on the repository host.</li>
                </ul>Once the command successfully completes, it is the responsibility of the user to remove the stanza from all <backrest/> configuration files.</text>

                <option-list>
                    <!-- OPERATION - STANZA-CREATE COMMAND - FORCE OPTION -->
                    <option id="force" name="Force">
                        <summary>Force stanza delete.</summary>

                        <text>If <postgres/> is still running for the stanza, then this option can be used to force the stanza to be deleted from the repository.</text>

                        <example>n</example>
                    </option>
                </option-list>

                <command-example-list>
                    <command-example title="Delete a stanza">
                        <text><code-block title="">
                            {[backrest-exe]} --stanza=db stanza-delete
                        </code-block>

                        Delete the <id>db</id> stanza repository.</text>
                    </command-example>
                </command-example-list>
            </command>
        </command-list>
    </operation>
</doc>
