<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Command Reference on PIG.CENTER</title><link>https://pig.center/docs/pgbackrest/command/</link><description>Recent content in Command Reference on PIG.CENTER</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 08 Sep 2026 21:29:01 +0800</lastBuildDate><atom:link href="https://pig.center/docs/pgbackrest/command/index.xml" rel="self" type="application/rss+xml"/><item><title>Annotate Command (annotate)</title><link>https://pig.center/docs/pgbackrest/command/annotate/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/annotate/</guid><description>&lt;p&gt;Annotations included with the &lt;code&gt;backup&lt;/code&gt; command can be added, modified, or removed afterwards using the &lt;code&gt;annotate&lt;/code&gt; command.&lt;/p&gt;&#10;&lt;h2 id="command-options"&gt;Command Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="backup-annotation-option---annotation"&gt;Backup Annotation Option (&lt;code&gt;--annotation&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;Annotate backup with user-defined key/value pairs.&lt;/p&gt;&#10;&lt;p&gt;Users can attach informative key/value pairs to the backup. This option may be used multiple times to attach multiple annotations.&lt;/p&gt;&#10;&lt;p&gt;Annotations are output by the &lt;code&gt;info&lt;/code&gt; command text output when a backup is specified with &lt;code&gt;--set&lt;/code&gt; and always appear in the JSON output.&lt;/p&gt;</description></item><item><title>Archive Get Command (archive-get)</title><link>https://pig.center/docs/pgbackrest/command/archive-get/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/archive-get/</guid><description>&lt;p&gt;This command is used by PostgreSQL to restore a backup, perform PITR, or as an alternative to streaming for keeping a replica up to date. WAL segments are required for PostgreSQL recovery or to maintain a replica.&lt;/p&gt;&#10;&lt;p&gt;When multiple repositories are configured, WAL will be fetched from the repositories in priority order (e.g. &lt;code&gt;repo1&lt;/code&gt;, &lt;code&gt;repo2&lt;/code&gt;, etc.). In general it is better if faster/cheaper storage has higher priority. If a repository is specified with the &lt;code&gt;--repo&lt;/code&gt; option then only that repository will be searched.&lt;/p&gt;</description></item><item><title>Archive Push Command (archive-push)</title><link>https://pig.center/docs/pgbackrest/command/archive-push/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/archive-push/</guid><description>&lt;p&gt;Accepts a WAL segment from PostgreSQL and archives it in each repository defined by the indexed &lt;code&gt;repo-path&lt;/code&gt; option (see the &lt;a href="https://pig.center/docs/pgbackrest/configuration/#repository-options"&gt;Repository&lt;/a&gt;&#10; section for information on configuring repositories). The WAL segment may be pushed immediately to the archive or stored locally depending on the value of &lt;code&gt;archive-async&lt;/code&gt;. With multiple repositories configured, &lt;code&gt;archive-push&lt;/code&gt; will attempt to push to as many repositories as possible.&lt;/p&gt;&#10;&lt;p&gt;The &lt;code&gt;archive-push&lt;/code&gt; is intended to be configured and called by PostgreSQL. See &lt;a href="https://pig.center/docs/pgbackrest/user-guide/#configure-archiving"&gt;Configure Archiving&lt;/a&gt;&#10; for an example.&lt;/p&gt;</description></item><item><title>Backup Command (backup)</title><link>https://pig.center/docs/pgbackrest/command/backup/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/backup/</guid><description>&lt;p&gt;When multiple repositories are configured, pgBackRest will backup to the highest priority repository (e.g. &lt;code&gt;repo1&lt;/code&gt;) unless the &lt;code&gt;--repo&lt;/code&gt; option is specified.&lt;/p&gt;&#10;&lt;p&gt;pgBackRest does not have a built-in scheduler so it&amp;rsquo;s best to run it from cron or some other scheduling mechanism.&lt;/p&gt;&#10;&lt;p&gt;See &lt;a href="https://pig.center/docs/pgbackrest/user-guide/#perform-a-backup"&gt;Perform a Backup&lt;/a&gt;&#10; for more details and examples.&lt;/p&gt;&#10;&lt;h2 id="command-options"&gt;Command Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="backup-annotation-option---annotation"&gt;Backup Annotation Option (&lt;code&gt;--annotation&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;Annotate backup with user-defined key/value pairs.&lt;/p&gt;</description></item><item><title>Check Command (check)</title><link>https://pig.center/docs/pgbackrest/command/check/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/check/</guid><description>&lt;p&gt;The &lt;code&gt;check&lt;/code&gt; command validates that pgBackRest and the archive_command setting are configured correctly for archiving and backups for the specified stanza. It will attempt to check all repositories and databases that are configured for the host on which the command is run. 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 PostgreSQL or repository host. The command may also be run on the standby host, however, since &lt;code&gt;pg_switch_xlog()&lt;/code&gt;/&lt;code&gt;pg_switch_wal()&lt;/code&gt; cannot be performed on the standby, the command will only test the repository configuration.&lt;/p&gt;</description></item><item><title>Expire Command (expire)</title><link>https://pig.center/docs/pgbackrest/command/expire/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/expire/</guid><description>&lt;p&gt;pgBackRest does full backup rotation based on the retention type which can be a count or a time period. When a count is specified, then expiration is not concerned with when the backups were created but with how many must be retained. Differential backups are count-based but will always be expired when the full backup they depend on is expired. Incremental backups are not expired by retention independently — they are always expired with their related full or differential backup. See sections &lt;a href="https://pig.center/docs/pgbackrest/user-guide/#full-backup-retention"&gt;Full Backup Retention&lt;/a&gt;&#10; and &lt;a href="https://pig.center/docs/pgbackrest/user-guide/#differential-backup-retention"&gt;Differential Backup Retention&lt;/a&gt;&#10; for details and examples.&lt;/p&gt;</description></item><item><title>Help Command (help)</title><link>https://pig.center/docs/pgbackrest/command/help/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/help/</guid><description>&lt;p&gt;Three levels of help are provided. If no command is specified then general help will be displayed. If a command is specified (e.g. &lt;code&gt;pgbackrest help backup&lt;/code&gt;) 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 (e.g. &lt;code&gt;pgbackrest help backup type&lt;/code&gt;) then a full description of the option as it applies to the command will be displayed.&lt;/p&gt;</description></item><item><title>Info Command (info)</title><link>https://pig.center/docs/pgbackrest/command/info/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/info/</guid><description>&lt;p&gt;The &lt;code&gt;info&lt;/code&gt; 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.&lt;/p&gt;&#10;&lt;p&gt;For machine-readable output use &lt;code&gt;--output=json&lt;/code&gt;. The JSON output contains far more information than the text output and is kept stable unless a bug is found.&lt;/p&gt;&#10;&lt;p&gt;To speed up execution, limit the output to only progress information by specifying &lt;code&gt;--detail-level=progress&lt;/code&gt;. Note that this skips all checks except for availability of the stanza.&lt;/p&gt;</description></item><item><title>Repository Get Command (repo-get)</title><link>https://pig.center/docs/pgbackrest/command/repo-get/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/repo-get/</guid><description>&lt;p&gt;Similar to the unix &lt;code&gt;cat&lt;/code&gt; command but works on any supported repository type. This command requires a fully qualified file name and is primarily for administration, investigation, and testing. It is not a required part of a normal pgBackRest setup.&lt;/p&gt;&#10;&lt;p&gt;If the repository is encrypted then &lt;code&gt;repo-get&lt;/code&gt; will automatically decrypt the file. Files are not automatically decompressed but the output can be piped through the appropriate decompression command, e.g. &lt;code&gt;gzip -d&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Repository List Command (repo-ls)</title><link>https://pig.center/docs/pgbackrest/command/repo-ls/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/repo-ls/</guid><description>&lt;p&gt;Similar to the unix &lt;code&gt;ls&lt;/code&gt; command but works on any supported repository type. This command accepts a path, absolute or relative to the repository path defined by the &lt;code&gt;--repo-path&lt;/code&gt; option, and is primarily for administration, investigation, and testing. It is not a required part of a normal pgBackRest setup.&lt;/p&gt;&#10;&lt;p&gt;The default text output prints one file name per line. JSON output is available by specifying &lt;code&gt;--output=json&lt;/code&gt;.&lt;/p&gt;&#10;&lt;p&gt;If more than one repository is configured, the command will default to the highest priority repository (e.g. &lt;code&gt;repo1&lt;/code&gt;) unless the &lt;code&gt;--repo&lt;/code&gt; option is specified.&lt;/p&gt;</description></item><item><title>Restore Command (restore)</title><link>https://pig.center/docs/pgbackrest/command/restore/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/restore/</guid><description>&lt;p&gt;The restore command automatically defaults to selecting the latest backup from the first repository where backups exist (see &lt;a href="https://pig.center/docs/pgbackrest/user-guide/#restore-a-backup"&gt;Quick Start - Restore a Backup&lt;/a&gt;&#10;). The order in which the repositories are checked is dictated by the &lt;code&gt;pgbackrest.conf&lt;/code&gt; (e.g. repo1 will be checked before repo2). To select from a specific repository, the &lt;code&gt;--repo&lt;/code&gt; option can be passed (e.g. &lt;code&gt;--repo=1&lt;/code&gt;). The &lt;code&gt;--set&lt;/code&gt; option can be passed if a backup other than the latest is desired.&lt;/p&gt;</description></item><item><title>Server Command (server)</title><link>https://pig.center/docs/pgbackrest/command/server/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/server/</guid><description>&lt;p&gt;The pgBackRest server allows access to remote hosts without using the SSH protocol.&lt;/p&gt;&#10;&lt;h2 id="command-options"&gt;Command Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="tls-server-address-option---tls-server-address"&gt;TLS Server Address Option (&lt;code&gt;--tls-server-address&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;TLS server address.&lt;/p&gt;&#10;&lt;p&gt;IP address the server will listen on for client requests.&lt;/p&gt;&#10;&lt;div class="td-code td-code--untitled" id="td-code-4bb5b1e0-fence-0" data-td-code data-td-code-auto-id&#10; data-td-language="yaml" data-td-line-count="2"&gt;&#10; &lt;div class="td-code__viewport" id="td-code-4bb5b1e0-fence-0-viewport" data-td-code-viewport&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-yaml" data-lang="yaml"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;default&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="l"&gt;localhost&lt;/span&gt;&lt;span class="w"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;example&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;--&lt;span class="l"&gt;tls-server-address=*&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;h3 id="tls-server-authorized-clients-option---tls-server-auth"&gt;TLS Server Authorized Clients Option (&lt;code&gt;--tls-server-auth&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;TLS server authorized clients.&lt;/p&gt;&#10;&lt;p&gt;Clients are authorized on the server by verifying their certificate and checking their certificate CN (Common Name) against a list on the server configured with the &lt;code&gt;tls-server-auth&lt;/code&gt; option.&lt;/p&gt;</description></item><item><title>Server Ping Command (server-ping)</title><link>https://pig.center/docs/pgbackrest/command/server-ping/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/server-ping/</guid><description>&lt;p&gt;Ping a pgBackRest TLS server to ensure it is accepting connections. This serves as an aliveness check only since no authentication is attempted.&lt;/p&gt;&#10;&lt;p&gt;If no host is specified on the command-line then the &lt;code&gt;tls-server-host&lt;/code&gt; option will be used.&lt;/p&gt;&#10;&lt;h2 id="command-options"&gt;Command Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="tls-server-address-option---tls-server-address"&gt;TLS Server Address Option (&lt;code&gt;--tls-server-address&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;TLS server address.&lt;/p&gt;&#10;&lt;p&gt;IP address the server will listen on for client requests.&lt;/p&gt;&#10;&lt;div class="td-code td-code--untitled" id="td-code-528d8710-fence-0" data-td-code data-td-code-auto-id&#10; data-td-language="yaml" data-td-line-count="2"&gt;&#10; &lt;div class="td-code__viewport" id="td-code-528d8710-fence-0-viewport" data-td-code-viewport&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-yaml" data-lang="yaml"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;default&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="l"&gt;localhost&lt;/span&gt;&lt;span class="w"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;example&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;--&lt;span class="l"&gt;tls-server-address=*&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;h3 id="tls-server-port-option---tls-server-port"&gt;TLS Server Port Option (&lt;code&gt;--tls-server-port&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;TLS server port.&lt;/p&gt;</description></item><item><title>Stanza Create Command (stanza-create)</title><link>https://pig.center/docs/pgbackrest/command/stanza-create/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/stanza-create/</guid><description>&lt;p&gt;The &lt;code&gt;stanza-create&lt;/code&gt; command must be run after the stanza has been configured in &lt;code&gt;pgbackrest.conf&lt;/code&gt;. If there is more than one repository configured, the stanza will be created on each. Stanzas that have already been created will be skipped so it is always safe to run &lt;code&gt;stanza-create&lt;/code&gt;, even when a new repository has been configured.&lt;/p&gt;&#10;&lt;p&gt;See &lt;a href="https://pig.center/docs/pgbackrest/user-guide/#create-the-stanza"&gt;Create the Stanza&lt;/a&gt;&#10; for more information and an example.&lt;/p&gt;&#10;&lt;h2 id="command-options"&gt;Command Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="online-option---online"&gt;Online Option (&lt;code&gt;--online&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;Create on an online cluster.&lt;/p&gt;</description></item><item><title>Stanza Delete Command (stanza-delete)</title><link>https://pig.center/docs/pgbackrest/command/stanza-delete/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/stanza-delete/</guid><description>&lt;p&gt;The &lt;code&gt;stanza-delete&lt;/code&gt; command removes data in the repository associated with a stanza.&lt;/p&gt;&#10;&lt;p&gt;WARNING:&lt;/p&gt;&#10;&lt;p&gt;Use this command with caution — it will permanently remove all backups and archives from the pgBackRest repository for the specified stanza.&lt;/p&gt;&#10;&lt;p&gt;To delete a stanza:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Shut down the PostgreSQL cluster associated with the stanza (or use &amp;ndash;force to override).&lt;/li&gt;&#10;&lt;li&gt;Run the &lt;code&gt;stop&lt;/code&gt; command on the host where the &lt;code&gt;stanza-delete&lt;/code&gt; command will be run.&lt;/li&gt;&#10;&lt;li&gt;Run the &lt;code&gt;stanza-delete&lt;/code&gt; command.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Once the command successfully completes, it is the responsibility of the user to remove the stanza from all pgBackRest configuration files and/or environment variables.&lt;/p&gt;</description></item><item><title>Stanza Upgrade Command (stanza-upgrade)</title><link>https://pig.center/docs/pgbackrest/command/stanza-upgrade/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/stanza-upgrade/</guid><description>&lt;p&gt;Immediately after upgrading PostgreSQL to a newer major version, the &lt;code&gt;pg-path&lt;/code&gt; for all pgBackRest configurations must be set to the new database location and the &lt;code&gt;stanza-upgrade&lt;/code&gt; command run. If there is more than one repository configured on the host, the stanza will be upgraded on each. If the database is offline use the &lt;code&gt;--no-online&lt;/code&gt; option.&lt;/p&gt;&#10;&lt;h2 id="command-options"&gt;Command Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="online-option---online"&gt;Online Option (&lt;code&gt;--online&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;Update an online cluster.&lt;/p&gt;</description></item><item><title>Start Command (start)</title><link>https://pig.center/docs/pgbackrest/command/start/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/start/</guid><description>&lt;p&gt;If the pgBackRest processes were previously stopped using the &lt;code&gt;stop&lt;/code&gt; command then they can be started again using the &lt;code&gt;start&lt;/code&gt; command. Note that this will not immediately start up any pgBackRest processes but they are allowed to run. See &lt;a href="https://pig.center/docs/pgbackrest/user-guide/#starting-and-stopping"&gt;Starting and Stopping&lt;/a&gt;&#10; for more information and examples.&lt;/p&gt;&#10;&lt;h2 id="general-options"&gt;General Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="allow-run-as-root-option---allow-root"&gt;Allow Run as Root Option (&lt;code&gt;--allow-root&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;Allow the command to run as the root user.&lt;/p&gt;</description></item><item><title>Stop Command (stop)</title><link>https://pig.center/docs/pgbackrest/command/stop/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/stop/</guid><description>&lt;p&gt;Does not allow any new pgBackRest processes to run. By default running processes will be allowed to complete successfully. Use the &lt;code&gt;--force&lt;/code&gt; option to terminate running processes.&lt;/p&gt;&#10;&lt;p&gt;pgBackRest processes will return an error if they are run after the stop command completes. See &lt;a href="https://pig.center/docs/pgbackrest/user-guide/#starting-and-stopping"&gt;Starting and Stopping&lt;/a&gt;&#10; for more information and examples.&lt;/p&gt;&#10;&lt;h2 id="command-options"&gt;Command Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="force-option---force"&gt;Force Option (&lt;code&gt;--force&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;Force all pgBackRest processes to stop.&lt;/p&gt;</description></item><item><title>Verify Command (verify)</title><link>https://pig.center/docs/pgbackrest/command/verify/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/verify/</guid><description>&lt;p&gt;Verify determines if the backups and archives in a repository are valid.&lt;/p&gt;&#10;&lt;h2 id="command-options"&gt;Command Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="output-option---output"&gt;Output Option (&lt;code&gt;--output&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;Output type.&lt;/p&gt;&#10;&lt;p&gt;The following output types are supported:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;code&gt;none&lt;/code&gt; - No verify output.&lt;/li&gt;&#10;&lt;li&gt;&lt;code&gt;text&lt;/code&gt; - Output verify information to stdout.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;div class="td-code td-code--untitled" id="td-code-0b746fb1-fence-0" data-td-code data-td-code-auto-id&#10; data-td-language="yaml" data-td-line-count="2"&gt;&#10; &lt;div class="td-code__viewport" id="td-code-0b746fb1-fence-0-viewport" data-td-code-viewport&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-yaml" data-lang="yaml"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;default&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="l"&gt;none&lt;/span&gt;&lt;span class="w"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;example&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;--&lt;span class="l"&gt;output=text&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;h3 id="set-option---set"&gt;Set Option (&lt;code&gt;--set&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;Backup set to verify.&lt;/p&gt;&#10;&lt;p&gt;Verify all database and archive files associated with the specified backup set.&lt;/p&gt;</description></item><item><title>Version Command (version)</title><link>https://pig.center/docs/pgbackrest/command/version/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://pig.center/docs/pgbackrest/command/version/</guid><description>&lt;p&gt;Displays installed pgBackRest version.&lt;/p&gt;&#10;&lt;h2 id="command-options"&gt;Command Options&#10;&lt;/h2&gt;&#10;&lt;h3 id="output-option---output"&gt;Output Option (&lt;code&gt;--output&lt;/code&gt;)&#10;&lt;/h3&gt;&#10;&lt;p&gt;Output type.&lt;/p&gt;&#10;&lt;p&gt;The following output types are supported:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;code&gt;text&lt;/code&gt; - Display the installed pgBackRest version as text.&lt;/li&gt;&#10;&lt;li&gt;&lt;code&gt;num&lt;/code&gt; - Display the installed pgBackRest version as an integer.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;div class="td-code td-code--untitled" id="td-code-6fab8499-fence-0" data-td-code data-td-code-auto-id&#10; data-td-language="yaml" data-td-line-count="2"&gt;&#10; &lt;div class="td-code__viewport" id="td-code-6fab8499-fence-0-viewport" data-td-code-viewport&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-yaml" data-lang="yaml"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;default&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="l"&gt;text&lt;/span&gt;&lt;span class="w"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;example&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;--&lt;span class="l"&gt;output=num&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;&#10;&lt;/div&gt;</description></item></channel></rss>