mirror of
https://we.phorge.it/source/phorge.git
synced 2024-12-23 05:50:55 +01:00
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
This commit is contained in:
parent
3770998c39
commit
117519f396
2 changed files with 11 additions and 5 deletions
|
@ -204,5 +204,6 @@ Continue by:
|
||||||
- configuring inbound mail with @{article:Configuring Inbound Email}; or
|
- configuring inbound mail with @{article:Configuring Inbound Email}; or
|
||||||
- importing repositories with @{article:Diffusion User Guide}; or
|
- importing repositories with @{article:Diffusion User Guide}; or
|
||||||
- learning about daemons with @{article:Managing Daemons with phd}; or
|
- learning about daemons with @{article:Managing Daemons with phd}; or
|
||||||
- configuring backups with @{article:Configuring Backups}; or
|
- configuring backups with
|
||||||
|
@{article:Configuring Backups and Performing Migrations}; or
|
||||||
- contributing to Phabricator with @{article:Contributor Introduction}.
|
- contributing to Phabricator with @{article:Contributor Introduction}.
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
@title Configuring Backups
|
@title Configuring Backups and Performing Migrations
|
||||||
@group config
|
@group config
|
||||||
|
|
||||||
Advice for backing up Phabricator.
|
Advice for backing up Phabricator, or migrating from one machine to another.
|
||||||
|
|
||||||
= Overview =
|
= Overview =
|
||||||
|
|
||||||
|
@ -16,12 +16,17 @@ which needs to be backed up are:
|
||||||
|
|
||||||
This document discusses approaches for backing up this data.
|
This document discusses approaches for backing up this data.
|
||||||
|
|
||||||
|
If you are migrating from one machine to another, you can generally follow the
|
||||||
|
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.
|
||||||
|
|
||||||
= Backup: MySQL Databases =
|
= Backup: MySQL Databases =
|
||||||
|
|
||||||
Most of Phabricator's data is stored in MySQL, and it's the most important thing
|
Most of Phabricator's data is stored in MySQL, and it's the most important thing
|
||||||
to back up. You can run `bin/storage dump` to get a dump of all the MySQL
|
to back up. You can run `bin/storage dump` to get a dump of all the MySQL
|
||||||
databases. This is a convenience script which just runs a normal `mysqldump`
|
databases. This is a convenience script which just runs a normal `mysqldump`,
|
||||||
of every database Phabricator owns.
|
but will only dump databases Phabricator owns.
|
||||||
|
|
||||||
Since most of this data is compressible, it may be helpful to run it through
|
Since most of this data is compressible, it may be helpful to run it through
|
||||||
gzip prior to storage. For example:
|
gzip prior to storage. For example:
|
||||||
|
|
Loading…
Reference in a new issue