By Super User on Wednesday, 18 November 2026
Category: Backup Tools for OTOBO

OTOBO Backup Script vs Plugin: A Practical Guide

If you run OTOBO, you already have backup scripts: backup.pl and restore.pl. They work, but they were built for manual command-line use, not as a managed backup system. This guide walks through the practical limitations and shows how the Backup Tools plugin replaces them with scheduled, encrypted, multi-destination backups and one-click restore.

Quick summary
✓backup.pl and restore.pl are manual CLI tools: local-only archives, no encryption, no notifications, and you must set up cron yourself.
✓The Backup Tools plugin adds scheduled backups, multiple destinations (including cloud), AES encryption, retention policies and email failure alerts.
✓Restore moves from a multi-step CLI workflow to one-click from the OTOBO Admin panel.
✓Setup is browser-only via Package Manager — no SSH required — and a free tier covers local disk and FTP.

1What OTOBO's backup.pl and restore.pl actually do

OTOBO ships with two command-line scripts: scripts/backup.pl and scripts/restore.pl. Together they create a backup archive of your database and OTOBO home directory, and restore it. They are the standard starting point, and they do the core job.

But they were built for manual CLI use. That means you run them by hand, or you write your own cron job to run them on a schedule. There is no dashboard, no notification, and no built-in off-site sync. If you want your backup somewhere other than the local disk, you handle that yourself.

For a small, static installation this might be enough. For a busy helpdesk with SLAs and customer history, the manual approach leaves gaps that are easy to overlook until you need a restore.

2The manual CLI limitations in plain English

Here is what the built-in scripts do not do, based on the comparison in our Backup Tools for OTOBO documentation:

None of these are bugs. They are simply the boundaries of a script built for manual use. The problem is that manual backups depend on memory and discipline — and both are in short supply on a busy IT team.

💡 Pro tip: Test a restore before you need it. A backup you have never restored is only a hypothesis — verify the process on a non-production instance first.

3Common mistakes when relying on backup.pl alone

These are the practical traps we see readers run into:

If any of these sound familiar, it is worth reviewing your setup today. A short checklist at the end of this post will help.

Tired of remembering to run backup.pl?

Backup Tools for OTOBO schedules backups for you and sends email alerts if a sync fails. Set it up from the Admin panel in minutes.

Explore Backup Tools for OTOBO → Ask us a question →

4How the Backup Tools plugin changes the picture

Backup Tools for OTOBO is a native Admin plugin that does the same core job as the scripts — packaging your database, configuration and filesystem into one archive — then goes further. It is our product, built for OTOBO 10.0.x – 11.0.x.

From the OTOBO Admin panel you can:

Setup is browser-only: upload the .opm file in Admin → Package Manager, activate your licence, configure destinations and schedule. No SSH, no cron jobs.

5Side-by-side: script vs plugin

The table below summarises the differences from the source documentation.

The data protected is the same — your database and OTOBO home. The plugin simply replaces CLI work with automation, encryption, notifications and one-click recovery.

6A practical migration path (without breaking anything)

You do not have to choose one or the other forever. A safe approach is to run both in parallel for a short period:

  • ✓Keep your existing backup.pl cron job running. Do not remove it yet.
  • ✓Install the plugin via Package Manager and activate the free licence.
  • ✓Configure a local destination and a schedule that matches or improves on your current cadence.
  • ✓Run a manual backup from the dashboard and confirm the archive appears.
  • ✓Add a second destination (for example, an FTP or cloud destination) so you have an off-site copy.
  • ✓Test a restore on a non-production instance if possible. The plugin offers one-click restore, but you should still verify the process.
  • ✓Once you are confident, disable the old cron job and rely on the plugin.
  • If you get stuck, our support forum is a good place to ask. For a broader walkthrough of the Admin panel, see our earlier post on how to back up OTOBO helpdesk.

    Need a hand with your first restore?

    Our support forum is a good place to ask questions about destinations, schedules and restore testing before you go live.

    Explore the CogSnug support forum → Ask us a question →

    7Encryption and key management: the one thing not to get wrong

    The plugin supports AES backup encryption. One master key is used for all destinations, and you can toggle encryption per destination before upload. That protects data even if your cloud storage is compromised.

    But there is an important safeguard: 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. A lost key means permanently unreadable backups — by you and by us.

    This is not a reason to avoid encryption. It is a reason to treat the key like any other critical secret: document where it is, who has it, and how it is recovered.

    8Your pre-flight checklist

    Before you change anything, run through this list:

    If you answer “no” or “not sure” to more than one, the plugin is worth a look. The free tier covers local disk and FTP forever, and a 14-day trial unlocks all destinations, encryption and alerts — no card required.

    Ready to move beyond manual scripts?

    Try Backup Tools for OTOBO free: local disk and FTP forever, plus a 14-day trial of all destinations, encryption and alerts. No card needed.

    Explore Backup Tools for OTOBO → Ask us a question →

    Related: Backup Tools for OTOBO · OTOBO Backup Failed to Sync Offsite? Fix It Today · How to Back Up OTOBO Helpdesk: Admin Panel Walkthrough

    Related Posts

    Leave Comments