RedmineBackupRestore » History » Version 2
Go MAEDA, 2018-01-11 01:11
Reviewed parameters of mysqldump and pg_dump
| 1 | 1 | Go MAEDA | h1. Backing up and restoring Redmine |
|---|---|---|---|
| 2 | 1 | Go MAEDA | |
| 3 | 1 | Go MAEDA | {{>toc}} |
| 4 | 1 | Go MAEDA | |
| 5 | 1 | Go MAEDA | h2. Backup |
| 6 | 1 | Go MAEDA | |
| 7 | 1 | Go MAEDA | Redmine backups should include: |
| 8 | 1 | Go MAEDA | * Database |
| 9 | 1 | Go MAEDA | * Attachments (stored in the @files@ directory of your Redmine install) |
| 10 | 1 | Go MAEDA | |
| 11 | 1 | Go MAEDA | h3. Backing up database |
| 12 | 1 | Go MAEDA | |
| 13 | 1 | Go MAEDA | h4. MySQL |
| 14 | 1 | Go MAEDA | |
| 15 | 1 | Go MAEDA | The @mysqldump@ command can be used to backup the contents of your MySQL database to a text file. For example: |
| 16 | 1 | Go MAEDA | <pre> |
| 17 | 2 | Go MAEDA | /usr/bin/mysqldump -u <username> -p<password> -h<hostname> <redmine_database> > /path/to/backup/db/redmine.sql |
| 18 | 1 | Go MAEDA | </pre> |
| 19 | 1 | Go MAEDA | |
| 20 | 2 | Go MAEDA | You can find @<username>@, @<password>@, @<hostname>@, and @<redmine_database>@ in the file @config/database.yml@. @<host_name>@ may not be required depending on your installation of the database. |
| 21 | 2 | Go MAEDA | |
| 22 | 1 | Go MAEDA | h4. PostgreSQL |
| 23 | 1 | Go MAEDA | |
| 24 | 1 | Go MAEDA | The @pg_dump@ command can be used to backup the contents of a PostgreSQL database to a text file. Here is an example: |
| 25 | 1 | Go MAEDA | <pre> |
| 26 | 2 | Go MAEDA | /usr/bin/pg_dump -U <username> -h <hostname> -Fc --file=redmine.sqlc <redmine_database> |
| 27 | 1 | Go MAEDA | </pre> |
| 28 | 1 | Go MAEDA | |
| 29 | 2 | Go MAEDA | You can find @<username>@, @<hostname>@, and @<redmine_database>@ in the file @config/database.yml@. @<hostname>@ may not be required depending on your installation of the database. The @pg_dump@ command will prompt you to enter the password when necessary. |
| 30 | 2 | Go MAEDA | |
| 31 | 1 | Go MAEDA | h4. SQLite |
| 32 | 1 | Go MAEDA | |
| 33 | 1 | Go MAEDA | SQLite databases are all contained in a single file, so you can back them up by copying the file to another location. |
| 34 | 2 | Go MAEDA | |
| 35 | 2 | Go MAEDA | You can determine the file name of SQLite database by looking at @config/database.yml@. |
| 36 | 1 | Go MAEDA | |
| 37 | 1 | Go MAEDA | h3. Backing up attachments |
| 38 | 1 | Go MAEDA | |
| 39 | 1 | Go MAEDA | All file uploads are stored in the @files/@ directory. You can copy the contents of this directory to another location to easily back it up. |
| 40 | 1 | Go MAEDA | |
| 41 | 1 | Go MAEDA | h3. Sample backup script |
| 42 | 1 | Go MAEDA | |
| 43 | 1 | Go MAEDA | Here is a simple shell script that can be used for daily backups (assuming you're using a MySQL database): |
| 44 | 1 | Go MAEDA | |
| 45 | 1 | Go MAEDA | <pre> |
| 46 | 1 | Go MAEDA | # Database |
| 47 | 1 | Go MAEDA | /usr/bin/mysqldump -u <username> -p<password> <redmine_database> | gzip > /path/to/backup/db/redmine_`date +%Y-%m-%d`.gz |
| 48 | 1 | Go MAEDA | |
| 49 | 1 | Go MAEDA | # Attachments |
| 50 | 1 | Go MAEDA | rsync -a /path/to/redmine/files /path/to/backup/files |
| 51 | 1 | Go MAEDA | </pre> |
| 52 | 1 | Go MAEDA | |
| 53 | 1 | Go MAEDA | |
| 54 | 1 | Go MAEDA | h2. Restore |
| 55 | 1 | Go MAEDA | |
| 56 | 1 | Go MAEDA | TODO |