archive/phabricator
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Document the need to restart Phabricator after performing a restore

Browse Source 
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
This commit is contained in:
epriestley
2017-07-03 10:25:37 -07:00
parent a6f0182104
commit 7b6b3d722a
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/docs/user/configuration/configuring_backups.diviner
View File

@@ -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 will just backup the old machine and then restore the data onto the new
machine. 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 Backup: MySQL Databases
======================= =======================