From 4bca12e28c787a0615480e3fdc889368fcbb2fec Mon Sep 17 00:00:00 2001 From: Steve Manuel Date: Mon, 26 Jun 2017 17:50:28 -0700 Subject: docs sync - search index backups --- docs/build/Running-Backups/Backups/index.html | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) (limited to 'docs/build/Running-Backups/Backups') diff --git a/docs/build/Running-Backups/Backups/index.html b/docs/build/Running-Backups/Backups/index.html index aabe029..04d1ffe 100644 --- a/docs/build/Running-Backups/Backups/index.html +++ b/docs/build/Running-Backups/Backups/index.html @@ -655,6 +655,13 @@ +
  • + + Search Indexes + + +
    • + @@ -785,6 +792,13 @@ +
  • + + Search Indexes + + +
    • + @@ -814,12 +828,21 @@

    Uploads

    -

    The /uploads directory is gzip compressed and archived as a tar file, stored in the temporary directory (typically /tmp on Linux) on your origin server with a timestamp in the file name.

    +

    The uploads directory is gzip compressed and archived as a tar file, stored in the temporary directory (typically /tmp on Linux) on your origin server with a timestamp in the file name. It is removed after the HTTP response for the backup has been written.

    An example backup request for the /uploads directory would look like:

    $ curl --user user:pass "https://example.com/admin/backup?source=uploads" > uploads.tar.gz
 # unarchive the tarball with gzip 
 $ tar xzf uploads.tar.gz
    + + +

    Search Indexes

    +

    The search directory, which is created to store the various search indexes for your content types (only if they implement search.Searchable), is backed up in the same fashion as Uploads.

    +

    An example backup request for the /search directory would look like:

    +
    $ curl --user user:pass "https://example.com/admin/backup?source=search" > search.tar.gz
+# unarchive the tarball with gzip 
+$ tar xzf search.tar.gz
+
    -- cgit v1.2.3