mirror of
https://we.phorge.it/source/phorge.git
synced 2025-01-05 12:21:02 +01:00
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
This commit is contained in:
parent
a6f0182104
commit
7b6b3d722a
1 changed files with 6 additions and 0 deletions
|
@ -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
|
||||||
=======================
|
=======================
|
||||||
|
|
Loading…
Reference in a new issue