Zen

Source string Source string

191/10000 · 191

The string is read only.

English Actions
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. Please read to the chapter :doc:`backup-restore-docker` for information about that case.
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.
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 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.
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``.
Adapt customer interface with corporate identity
In OTOBO it is very easy to adapt the customer area to your own corporate identity. Follow this tutorial step by step and OTOBO will shine in your own design in a short time.
Currently, it is not so easy to adapt the agent area to one's own CI. Changes in the OTOBO .css files would be necessary here. One exception is the logo on the agent login page and the agent header. The logos can be easily exchanged by copying the logos to the server and then adjusting the options ``AgentLoginLogo`` and ``AgentLogo`` under ``Admin -> System Configuration``.
Change colors in Customer Area
To change the colors for the OTOBO customer interface, please go to ``Admin -> System Configuration`` and change the following settings:
CustomerColorDefinitions
To change the colours on the Customer Dashboard, please go to `Admin -> System Configuration`` and search for CustomerDashboard. In the search result you will find all the options you need with colour definitions.
Change Logos and Pictures
In the first step please copy your Logos and Pictures to the OTOBO Server. Please use an SCP client (WinSCP) for this purpose. Often you do not have the permissions to copy the logos to the right place. In this case, it is best to use the folder /tmp/.
In the next step copy the Logo into the OTOBO Home directory:

Loading…

No matching activity found.
Browse all string changes

Glossary

English English
No related strings found in the glossary.

String information

Flags
read-only
Source string location
../../content/backup-restore-docker.rst:29
String age
4 years ago
Last updated
a year ago
Source string age
4 years ago
Translation file
locale/content.pot, string 14