update

Author: gsmolk

pg_probackup/index.html

@@ -361,9 +361,11 @@ <h4 id="page-validation">Page validation</h4>
 <p>Page is considered corrupted if checksumm comparison failed more than 100 times, in this case backup is aborted.</p>
 <p>Redardless of data checksums been enabled or not, pg_probackup always check page header “sanity”.</p>
 <h4 id="external-directories">External directories</h4>
-<p>To back up a directory located outside of the data directory, use the optional <code>--external-dirs</code> parameter that specifies the path to this directory. If you would like to add more than one external directory, provide several paths separated by colons.</p>
+<p>To back up a directory located outside of the data directory, use the optional <code>--external-dirs</code> parameter that specifies the path to this directory. If you would like to add more than one external directory, provide several paths separated by colons, on Windows system paths must be separated by semicolon instead.</p>
 <p>For example, to include ‘/etc/dir1/’ and ‘/etc/dir2/’ directories into the full backup of your <em>instance_name</em> instance that will be stored under the <em>backup_dir</em> directory, run:</p>
 <pre><code>pg_probackup backup -B backup_dir --instance instance_name -b FULL --external-dirs=/etc/dir1:/etc/dir2</code></pre>
+<p>For example, to include ‘C:1’ and ‘C:2’ directories into the full backup of your <em>instance_name</em> instance that will be stored under the <em>backup_dir</em> directory on Windows system, run:</p>
+<pre><code>pg_probackup backup -B backup_dir --instance instance_name -b FULL --external-dirs=C:\dir1;C:\dir2</code></pre>
 <p>pg_probackup creates a separate subdirectory in the backup directory for each external directory. Since external directories included into different backups do not have to be the same, when you are restoring the cluster from an incremental backup, only those directories that belong to this particular backup will be restored. Any external directories stored in the previous backups will be ignored.</p>
 <p>To include the same directories into each backup of your instance, you can specify them in the pg_probackup.conf configuration file using the <a href="#set-config">set-config</a> command with the <code>--external-dirs</code> option.</p>
 <h3 id="verifying-a-cluster">Verifying a Cluster</h3>
@@ -437,9 +439,10 @@ <h3 id="using-pg_probackup-in-the-remote-mode">Using pg_probackup in the Remote
 <li><p>If you would like to take remote backup in <a href="#creating-a-backup">PAGE</a> mode, or rely on <a href="#archive-mode">ARCHIVE</a> WAL delivery mode, or use <a href="#performing-point-in-time-pitr-recovery">PITR</a>, then configure continuous WAL archiving from database host to the backup host as explained in the section <a href="#setting-up-continuous-wal-archiving">Setting up continuous WAL archiving</a>. For the <a href="#archive-push">archive-push</a> and <a href="#archive-get">archive-get</a> commands, you must specify the <a href="#remote-mode-options">remote options</a> that point to backup host with backup catalog.</p></li>
 <li><p>Run <a href="#backup">backup</a> or <a href="#restore">restore</a> commands with <a href="#remote-mode-options">remote options</a> <strong>on backup host</strong>. pg_probackup connects to the remote system via SSH and creates a backup locally or restores the previously taken backup on the remote system, respectively.</p></li>
 </ul>
-<p>For example, to create archive full backup using remote mode via ssh, run:</p>
-<pre><code>pg_probackup backup -B backup_dir --instance instance_name -b FULL --remote-host=192.168.0.2 --remote-user=postgres</code></pre>
-<p>For example, to restore backup on remote system using ssh, run:</p>
+<p>For example, to create archive full backup using remote mode through SSH connection to user <code>postgres</code> on host with address <code>192.168.0.2</code> via port <code>2302</code>, run:</p>
+<pre><code>pg_probackup backup -B backup_dir --instance instance_name -b FULL --remote-user=postgres --remote-host=192.168.0.2 --remote-port=2302</code></pre>
+<p>For example, to restore latest backup on remote system using remote mode through SSH connection to user <code>postgres</code> on host with address <code>192.168.0.2</code> via port <code>2302</code>, run:</p>
+<pre><code>pg_probackup restore -B backup_dir --instance instance_name --remote-user=postgres --remote-host=192.168.0.2 --remote-port=2302</code></pre>
 <blockquote>
 <p>NOTE: The remote backup mode is currently unavailable for Windows systems.</p>
 </blockquote>