Source string Read only

7/100
Context English State
Backup and Restore
OTOBO has built in scripts for backup and restore. Execute the scripts with the option ``-h`` for more information.
Backup
To create a new backup, write permission for the destination directory is needed for the user ``otobo``.
The output of the script:
Restore
To restore the database make sure that the database ``otobo`` exists and contains no tables.
Considerations for running OTOBO under Docker
The same scripts can be used with OTOBO running under Docker. However some Docker specific limitation must be considered.
First we need to make sure that the backup files are not created in the file system that is internal to the container. Because in that case all data would be lost when the container is stopped. Therefore the backup directory must be in a volume. For now we only consider the most simple case, where the backup dir is a local dir on the Docker host. The location of the backup dir in the container can be arbitrarily chosen. In this example we choose the local dir ``otobo_backup`` as the location on the host, and ``/otobo_backup`` as the location in the container.
First we need to create the volume.
For creating the backup we need a running database and the volumes ``otobo_opt_otobo`` and ``otobo_backup``. This means that the webserver and the Daemon may, but don't have to, be stopped.
For restoring the backup we also need to specify which backup should be restored. The placeholder ``<TIMESTAMP>`` is something like ``2020-09-07_09-38``.
Backup and Restore using Docker
Please read to the chapter :doc:`backup-restore` for basic information about the backup and restore scripts.
The standard scripts ``backup.pl`` and ``restore.pl`` can also be used with OTOBO running under Docker. However some Docker specific limitations have to be considered.
First, we need to make sure that the backup files are not created in the file system that is internal to a Docker container. Because in that case the created files would be lost when the container is stopped. This means that the backup directory must located within in a volume. For this manual we only consider the most simple case, where the backup directory is a local directory on the Docker host. The location of the backup dir in the container can be arbitrarily chosen. In this example we choose the local dir ``otobo_backup`` as the location on the host and ``/otobo_backup`` as the location in the container.
Secondly, commands in the Docker container usually run as the user `otobo` with the user id 1000 and the group id 1000. It must be made sure, that this user can write in the backup directory.
For creating the backup we need a running database and the volumes ``otobo_opt_otobo`` and ``otobo_backup``. This means that the webserver and the OTOBO daemon may, but don't have to, be stopped.
To drop an existing otobo database and create a new one you can use the following commands. First, you have to connect to the MySQL CLI of the `db` container.
As soon as you are connected to the MySQL server, you can drop and recreate the `otobo` database.
Component Translation Difference to current string
This translation Propagated Translated OTOBO 10/Installation Manual
The following string has the same context and source.
Propagated Translated OTOBO 10/OTOBO

Loading…

User avatar None

New source string

OTOBO 10 / Installation Manual — English

New source string 3 years ago
Browse all component changes

Things to check

Multiple failing checks

The translations in several languages have failing checks

Reset

Glossary

English English
No related strings found in the glossary.

Source information

Flags
read-only
Source string location
../../content/backup-restore.rst:70
String age
3 years ago
Source string age
3 years ago
Translation file
locale/content.pot, string 6