Exit Zen
1
../../content/backup-restore.rst:12
English
Backup and Restore
0/180 · 18
2
../../content/backup-restore.rst:14
English
OTOBO has built in scripts for backup and restore. Execute the scripts with the option ``-h`` for more information.
0/1150 · 115
3
../../content/backup-restore.rst:17
English
Backup
0/100 · 6
4
../../content/backup-restore.rst:21
English
To create a new backup, write permission for the destination directory is needed for the user ``otobo``.
0/1040 · 104
5
../../content/backup-restore.rst:27 • ../../content/backup-restore.rst:80
English
The output of the script:
0/250 · 25
6
../../content/backup-restore.rst:70
English
Restore
0/100 · 7
7
../../content/backup-restore.rst:74 • ../../content/backup-restore-docker.rst:65
English
To restore the database make sure that the database ``otobo`` exists and contains no tables.
0/920 · 92
8
../../content/backup-restore.rst:96 • ../../content/backup-restore-docker.rst:17
English
Considerations for running OTOBO under Docker
0/450 · 45
9
../../content/backup-restore.rst:98
English
The same scripts can be used with OTOBO running under Docker. However some Docker specific limitation must be considered. Please read to the chapter :doc:`backup-restore-docker` for information about that case.
0/2100 · 210
10
../../content/backup-restore-docker.rst:12
English
Backup and Restore using Docker
0/310 · 31
11
../../content/backup-restore-docker.rst:14
English
Please read to the chapter :doc:`backup-restore` for basic information about the backup and restore scripts.
0/1080 · 108
12
../../content/backup-restore-docker.rst:19
English
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.
0/1670 · 167
13
../../content/backup-restore-docker.rst:22
English
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.
0/6170 · 617
14
../../content/backup-restore-docker.rst:29
English
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.
0/1910 · 191
15
../../content/backup-restore-docker.rst:32
English
First we need to create the volume.
0/350 · 35
16
../../content/backup-restore-docker.rst:48
English
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.
0/1950 · 195
17
../../content/backup-restore-docker.rst:67
English
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.
0/1580 · 158
18
../../content/backup-restore-docker.rst:75
English
As soon as you are connected to the MySQL server, you can drop and recreate the `otobo` database.
0/970 · 97
19
../../content/backup-restore-docker.rst:83
English
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``.
0/1530 · 153
20
../../content/customer-interface-ci.rst:12
English
Adapt customer interface with corporate identity
0/480 · 48