Skip to content

Commit 7b6b3d7

Browse files
author
epriestley
committedJul 5, 2017
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
1 parent a6f0182 commit 7b6b3d7

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed
 

‎src/docs/user/configuration/configuring_backups.diviner

+6
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,12 @@ same steps you would if you were creating a backup and then restoring it, you
2424
will just backup the old machine and then restore the data onto the new
2525
machine.
2626

27+
WARNING: You need to restart Phabricator after restoring data.
28+
29+
Restarting Phabricator after performing a restore makes sure that caches are
30+
flushed properly. For complete instructions, see
31+
@{article:Restarting Phabricator}.
32+
2733

2834
Backup: MySQL Databases
2935
=======================

0 commit comments

Comments
 (0)
Failed to load comments.