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/src/Running-Backups/Backups.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to 'docs/src') diff --git a/docs/src/Running-Backups/Backups.md b/docs/src/Running-Backups/Backups.md index 15632a0..fde0cab 100644 --- a/docs/src/Running-Backups/Backups.md +++ b/docs/src/Running-Backups/Backups.md @@ -16,11 +16,21 @@ $ curl --user user:pass "https://example.com/admin/backup?source=system" > syste ``` ## 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: ```bash $ 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](/Running-Backups/Backups/#uploads). + +An example backup request for the `/search` directory would look like: +```bash +$ curl --user user:pass "https://example.com/admin/backup?source=search" > search.tar.gz +# unarchive the tarball with gzip +$ tar xzf search.tar.gz ``` \ No newline at end of file -- cgit v1.2.3