@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
Make migrations more clear in backup documentation
Summary: Not sure this would have avoided the issue, but I remember a couple of other people asking about migrations, so try to make it more clear/obvious that the backup tools are also useful for migrations. Although this is reasonably obvious when you think about it, it's not very obvious when you're trying to do a migration, and maybe making it more explicit will help.
Test Plan: Read new documentation.
Reviewers: chad, btrahan
Reviewed By: chad
CC: aran
Differential Revision: https://secure.phabricator.com/D7992
+11
-5
+2
-1
src/docs/user/configuration/configuration_guide.diviner
+2
-1
src/docs/user/configuration/configuration_guide.diviner
···
204
204
- configuring inbound mail with @{article:Configuring Inbound Email}; or
205
205
- importing repositories with @{article:Diffusion User Guide}; or
206
206
- learning about daemons with @{article:Managing Daemons with phd}; or
207
-
- configuring backups with @{article:Configuring Backups}; or
207
+
- configuring backups with
208
+
@{article:Configuring Backups and Performing Migrations}; or
208
209
- contributing to Phabricator with @{article:Contributor Introduction}.
+9
-4
src/docs/user/configuration/configuring_backups.diviner
+9
-4
src/docs/user/configuration/configuring_backups.diviner
···
1
-
@title Configuring Backups
1
+
@title Configuring Backups and Performing Migrations
2
2
@group config
3
3
4
-
Advice for backing up Phabricator.
4
+
Advice for backing up Phabricator, or migrating from one machine to another.
5
5
6
6
= Overview =
7
7
···
16
16
17
17
This document discusses approaches for backing up this data.
18
18
19
+
If you are migrating from one machine to another, you can generally follow the
20
+
same steps you would if you were creating a backup and then restoring it, you
21
+
will just backup the old machine and then restore the data onto the new
22
+
machine.
23
+
19
24
= Backup: MySQL Databases =
20
25
21
26
Most of Phabricator's data is stored in MySQL, and it's the most important thing
22
27
to back up. You can run `bin/storage dump` to get a dump of all the MySQL
23
-
databases. This is a convenience script which just runs a normal `mysqldump`
24
-
of every database Phabricator owns.
28
+
databases. This is a convenience script which just runs a normal `mysqldump`,
29
+
but will only dump databases Phabricator owns.
25
30
26
31
Since most of this data is compressible, it may be helpful to run it through
27
32
gzip prior to storage. For example: