Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
28d150d8
Commit
28d150d8
authored
Mar 17, 2005
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update file system snapshot docs.
parent
57fdb2b0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
9 deletions
+12
-9
doc/src/sgml/backup.sgml
doc/src/sgml/backup.sgml
+12
-9
No files found.
doc/src/sgml/backup.sgml
View file @
28d150d8
<!--
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.5
8 2005/03/17 05:10:11
momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.5
9 2005/03/17 15:38:46
momjian Exp $
-->
<chapter id="backup">
<title>Backup and Restore</title>
...
...
@@ -364,9 +364,11 @@ tar -cf backup.tar /usr/local/pgsql/data
</para>
<para>
If your database is spread across multiple volumes (for example,
if you are using tablespaces) there may not be any way
to obtain exactly-simultaneous frozen snapshots of all the volumes.
If your database is spread across multiple file systems there may not
be any way to obtain exactly-simultaneous frozen snapshots of all
the volumes. For example, if your data files and WAL log on different
file disks, or if tablespaces are on different file systems, it might
not be possible to use snapshots because the snapshots must be simultaneous.
Read your file system documentation very carefully before trusting
to the consistent-snapshot technique in such situations. The safest
approach is to shut down the database server for long enough to
...
...
@@ -375,11 +377,12 @@ tar -cf backup.tar /usr/local/pgsql/data
<para>
Another option is to use <application>rsync</> to perform a file
system backup. First, while the database server is running,
run <application>rsync</>, then shut down the database
server and perform a second <application>rsync</>, then
restart the database server. This allows a file system backup to be
performed with minimal downtime.
system backup. This is done by first running <application>rsync</>
while the database server is running, then shutting down the database
server just long enough to do a second <application>rsync</>. The
second <application>rsync</> will be much quicker than the first,
but will be consistent because the server was down. This method
allows a file system backup to be performed with minimal downtime.
</para>
<para>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment