By Super User on Monday, 16 November 2026
Category: Backup Tools for OTOBO

How to Back Up OTOBO Helpdesk: Admin Panel Walkthrough

If your OTOBO helpdesk vanished tomorrow, how quickly could you get it back? For most teams the honest answer involves a command line, a half-remembered script and a lot of hoping. This walkthrough shows how to set up automated, encrypted off-site backups entirely from the OTOBO Admin panel — no SSH, no cron, no scripts.

In a nutshell
✓Backup Tools for OTOBO installs like any other add-on via Admin → Package Manager, with the licence verified locally.
✓You can configure local disk, FTP, FTPS, SFTP, OneDrive, Dropbox, Google Drive and Backblaze B2 from the Destinations tab — and use several at once.
✓Scheduling runs on OTOBO's own daemon scheduler, so backups sit alongside your other OTOBO tasks rather than in a separate cron job.
✓Your master encryption key is shown only once and is never saved in OTOBO or included in config exports — store it offline.

Why manual OTOBO backups let teams down

OTOBO ships with command-line scripts — scripts/backup.pl and scripts/restore.pl — that create a backup archive of your database and OTOBO home directory. They work. The problem is everything around them: someone has to remember to run them, someone has to set up cron, and the archive usually lands in a local directory on the same server.

That last point matters most. A backup stored on the same server disappears with the server. Your helpdesk holds tickets, SLAs, customer history and configuration — losing it costs time, trust and revenue. And a backup nobody checks is a backup nobody can rely on.

Our product, Backup Tools for OTOBO, is a native OTOBO plugin that replaces that manual effort with automation, encryption, notifications and one-click recovery — all managed from inside the Admin panel. This guide walks through setting it up from scratch.

Step 1: Install the package

Start in Admin → Package Manager. Upload the .opm file exactly as you would for any other OTOBO add-on. There is no SSH, no terminal and no server access required for this step.

Once installed, the plugin's settings appear in your Admin panel, ready for configuration.

Common mistake: installing on a version outside the supported range. The plugin is built for OTOBO 10.0.x — 11.0.x, so check your version before you begin.

💡 Pro tip: Generate your encryption key, write it down and store it somewhere offline before your first backup. It is shown once and never saved in OTOBO.

Step 2: Activate your licence

Paste your licence key into the Licence box. Verification happens locally — no external calls are needed, which keeps setup simple on locked-down networks.

Licence keys are locked to the domain they are issued for, so enter just the hostname when you request one — no https://, slashes or port numbers. If you later move OTOBO to a new domain, get in touch and the key can be reissued at no charge.

Worth knowing what each edition covers, because it affects the steps that follow:

If a licence lapses or you downgrade, existing cloud and SFTP destinations stay saved but stop receiving new backups — nothing is deleted, and they show as locked. Upgrading reactivates everything as configured.

See What Backup Tools Covers

Full instance backups, multiple destinations, scheduling and one-click restore — all managed from the OTOBO Admin panel. See the full feature list.

Explore Backup Tools for OTOBO → Ask us a question →

Step 3: Add your destinations

Open the Destinations tab. Every destination — FTP, FTPS, SFTP, OneDrive, Dropbox, Google Drive and Backblaze B2 — is configured entirely from here in the Admin panel. No command line, no terminal, no SSH.

The key decision is redundancy. You can sync the same backup to several destinations at once — for example local disk, a cloud drive and an SFTP server together — so a single point of failure never leaves you without a copy. A sensible pattern for many teams is one local copy for fast restores plus one off-site copy for disaster recovery.

Docker users, read this twice: backups assemble in a staging directory outside your OTOBO installation. If you run OTOBO in Docker, both the local backup path and the staging path must be properly bind-mounted from the host — otherwise local copies vanish when the container is rebuilt.

Step 4: Turn on encryption (and store the key properly)

Encryption is toggled per destination before upload, using one master key for all destinations. It protects your data even if your cloud storage is compromised.

Here is the part people get wrong. Your master encryption key is shown exactly once when generated. It is never saved inside OTOBO and never included in configuration exports. Store it offline, separately from everything else. A lost key means permanently unreadable backups — by you and by us.

This is also why the Import / Export Settings feature, which saves destinations, schedule and retention rules to a single JSON file, deliberately excludes passwords, private keys, OAuth secrets and your encryption key. Back those up separately.

Step 5: Set the schedule and retention rules

Scheduling is built on OTOBO's own daemon scheduler, so you can set any time and any frequency, and backups run reliably alongside your other OTOBO tasks. There is no separate cron job to maintain and no second system to monitor.

Retention is where you decide how much history to keep. You can keep backups for a set number of days, or keep only the last N copies. On paid plans you can override the global policy per destination — for example, keep 30 days locally but only 7 days on cloud storage. Free licences follow the global retention policy everywhere.

Two practical additions while you are here:

Stuck on a Destination?

Having trouble configuring a destination or testing your schedule? Our technical team and community are on hand to help.

Explore the CogSnug support forum → Ask us a question →

Step 6: Run your first backup and check it

With destinations, encryption, schedule and retention in place, run a backup and watch it through. The dashboard lists every backup, sorted newest-first, so you can see exactly what happened.

Then do three checks:

If a backup is ever interrupted unexpectedly — a server restart mid-run, for example — the dashboard detects it and lets you safely clear the stuck status with one click. No SSH or manual file edits.

Restoring is a one-click action from the dashboard, bringing your entire helpdesk, tickets, agents and settings back as they were. It is worth testing a restore on a non-production instance before you need it in anger.

A quick setup checklist

Run through this before you close the Admin panel:

For the full feature list and edition comparison, see the Backup Tools for OTOBO product page. If you get stuck configuring destinations or testing a schedule, the CogSnug support forum is the place to ask.

Protect Your OTOBO Helpdesk

Set up automated, encrypted off-site backups from your Admin panel in minutes. Start with the Free Edition for local and FTP, or try every premium feature for 14 days.

Explore Backup Tools for OTOBO → Ask us a question →

Related: Backup Tools for OTOBO · the CogSnug support forum · Backup Tools for OTOBO

Related Posts

Leave Comments