From 7b6b3d722ad7109a768104ddb875df228318cf87 Mon Sep 17 00:00:00 2001 From: epriestley Date: Mon, 3 Jul 2017 10:25:37 -0700 Subject: [PATCH] Document the need to restart Phabricator after performing a restore Summary: Depending on how you perform a restore, APC (or, e.g., running daemon processes) might be poisoned with out-of-date caches. Add a note to advise installs to restart after restoring data. See also lengthy fishing expedition support thread. Test Plan: Read the text. Reviewers: chad, amckinley Reviewed By: amckinley Differential Revision: https://secure.phabricator.com/D18180 --- src/docs/user/configuration/configuring_backups.diviner | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/docs/user/configuration/configuring_backups.diviner b/src/docs/user/configuration/configuring_backups.diviner index 1f13e0e17f..9776448216 100644 --- a/src/docs/user/configuration/configuring_backups.diviner +++ b/src/docs/user/configuration/configuring_backups.diviner @@ -24,6 +24,12 @@ same steps you would if you were creating a backup and then restoring it, you will just backup the old machine and then restore the data onto the new machine. +WARNING: You need to restart Phabricator after restoring data. + +Restarting Phabricator after performing a restore makes sure that caches are +flushed properly. For complete instructions, see +@{article:Restarting Phabricator}. + Backup: MySQL Databases =======================