From 1eeb39c87b434f06672e41a1bd6dbfd363ab42cb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20B=C3=B6hmer?= Date: Thu, 9 Feb 2023 00:03:08 +0100 Subject: [PATCH] Destroyed Backup & Restore Data (markdown) --- Backup-&-Restore-Data.md | 48 ---------------------------------------- 1 file changed, 48 deletions(-) delete mode 100644 Backup-&-Restore-Data.md diff --git a/Backup-&-Restore-Data.md b/Backup-&-Restore-Data.md deleted file mode 100644 index 81a9f9d..0000000 --- a/Backup-&-Restore-Data.md +++ /dev/null @@ -1,48 +0,0 @@ -# Backup and Restore Data - -When working productively you should backup the data and configuration of Part-DB regularly to prevent data loss. This is also useful, if you want to migrate your Part-DB instance from one server to another. In that case you just have to backup the data on server 1, move the backup to server 2, install Part-DB on server 2 and restore the backup. - -## Backup (automatic / Part-DB supported) -Part-DB includes a command `php bin/console partdb:backup` which automatically collects all the needed data (described below) and saves them to a ZIP file. - -If you are using a MySQL/MariaDB database you need to have `mysqldump` installed and added to your `$PATH` env. - -### Usage -To backup all possible data, run the following command: `php bin/console partdb:backup --full /path/to/backup/partdb_backup.zip`. - -It is possible to do only partial backups (config, attachments, or database). See `php bin/console partdb:backup --help` for more infos about these options. - -## Backup (manual) -There are 3 parts which have to be backup-ed: The configuration files, which contains the instance specific options, the uploaded files of attachments, and the database containing the most data of Part-DB. -Everything else like thumbnails and cache files, are recreated automatically when needed. - -### Configuration files -You have to copy the `.env.local` file and (if you have changed it) the `config/parameters.yaml` and `config/banner.md` to your backup location. - -### Attachment files -You have to recursively copy the `uploads/` folder and the `public/media` folder to your backup location. - -### Database -#### Sqlite -If you are using sqlite, it is sufficient to just copy your `app.db` from your database location (normally `var/app.db`) to your backup location. - -#### MySQL / MariaDB -For MySQL / MariaDB you have to dump the database to an SQL file. You can do this manually with phpmyadmin, or you use [`mysqldump`](https://mariadb.com/kb/en/mariadb-dumpmysqldump/) to dump the database to an SQL file via command line interface (`mysqldump -uBACKUP -pPASSWORD DATABASE`) - -## Restore -Install Part-DB as usual as described in the installation section, with the exception of the database creation / migration part. You have to use the same database type (sqlite or mysql) as on the back-uped server instance. - -### Restore configuration -Copy configuration files `.env.local`, (and if existing) `config/parameters.yaml` and `config/banner.md` from the backup to your new Part-DB instance and overwrite the existing files there. - -### Restore attachment files -Copy the `uploads/` and the `public/media/` folder from your backup into your new Part-DB folder. - -### Restore database -#### Sqlite -Copy the backup-ed `app.db` into the database folder normally `var/app.db` in Part-DB root folder. - -#### MySQL / MariaDB -Recreate a database and user with the same credentials as before (or update the database credentials in the `.env.local` file). -Import the dumped SQL file from the backup into your new database. -