You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation.md
+10-2Lines changed: 10 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -582,6 +582,12 @@ The typical workflow is as follows:
582
582
583
583
- Run [backup](#backup) or [restore](#restore) commands with [remote options](#remote-mode-options)**on backup host**. 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.
584
584
585
+
For example, to create archive full backup using remote mode via ssh, run:
586
+
587
+
pg_probackup backup -B backup_dir --instance instance_name -b FULL --remote-host=192.168.0.2 --remote-user=postgres
588
+
589
+
For example, to restore backup on remote system using ssh, run:
590
+
585
591
>NOTE: The remote backup mode is currently unavailable for Windows systems.
586
592
587
593
### Running pg_probackup on Parallel Threads
@@ -953,8 +959,10 @@ Specifies the backup mode to use. Possible values are:
953
959
- PAGE — creates an incremental PAGE backup based on the WAL files that have changed since the previous full or incremental backup was taken.
954
960
- PTRACK — creates an incremental PTRACK backup tracking page changes on the fly.
955
961
956
-
-C
957
-
--smooth-checkpoint
962
+
```
963
+
-C
964
+
--smooth-checkpoint
965
+
```
958
966
Spreads out the checkpoint over a period of time. By default, pg_probackup tries to complete the checkpoint as soon as possible.
0 commit comments