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.
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:
- ✓Local directory only. The archive is saved locally. If the server fails, the backup fails with it.
- ✓No encryption. Transfers are unencrypted, and the archive itself is not encrypted before it leaves the server.
- ✓No notifications. If a backup fails, nobody is told. You find out when you try to restore.
- ✓Manual run or custom cron. Scheduling is your responsibility. You must remember to set it up and maintain it.
- ✓Multi-step restore. Restoring is a CLI workflow, not a single click.
- ✓Manual cleanup only. Retention is a manual flag, not an enforced policy.
- ✓SSH and CLI access required. Setup and operation need terminal access.
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.
3Common mistakes when relying on backup.pl alone
These are the practical traps we see readers run into:
- ✓Assuming cron is running. A cron entry can be lost after a server migration or container rebuild. Without alerts, you may not notice for weeks.
- ✓Keeping backups on the same server. A local archive does not protect you from disk failure, ransomware or a host outage.
- ✓Forgetting the restore step. A backup you have never restored is a hope, not a plan. The CLI restore workflow is easy to get wrong under pressure.
- ✓No retention policy. Old archives pile up until the disk fills, or someone deletes the wrong one.
- ✓Docker surprises. If you run OTOBO in Docker, local paths can vanish on container rebuild unless they are properly bind-mounted.
If any of these sound familiar, it is worth reviewing your setup today. A short checklist at the end of this post will help.
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:
- ✓Schedule backups using OTOBO's own daemon scheduler — any time, any frequency.
- ✓Send backups to multiple destinations: local disk, standard FTP, FTPS (explicit TLS), SFTP, OneDrive, Dropbox, Google Drive and Backblaze B2.
- ✓Encrypt backups with AES before upload, with a per-destination toggle.
- ✓Apply retention policies — keep for a set number of days or keep only the last N copies. Paid plans add per-destination rules.
- ✓Restore with one click from the dashboard, or delete old backups directly.
- ✓Get email alerts if a backup completes locally but fails to sync to any destination.
- ✓Lock important backups so they are skipped by manual deletion and automatic cleanup.
- ✓Recover from interruptions — if a backup is interrupted, the dashboard detects it and lets you clear the stuck status with one click.
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.
- ✓Scheduling: backup.pl — manual run or custom cron. Plugin — built-in scheduler, set and forget.
- ✓Destinations: backup.pl — local directory only. Plugin — local, FTP/FTPS, SFTP, OneDrive, Dropbox, Google Drive and Backblaze B2.
- ✓Encryption: backup.pl — unencrypted transfers only. Plugin — fully encrypted transfers, AES backup encryption.
- ✓Restore: backup.pl — multi-step CLI workflow. Plugin — one-click restore from dashboard.
- ✓Retention: backup.pl — manual flag only. Plugin — auto-enforced retention policy.
- ✓Notifications: backup.pl — no alerts. Plugin — email alerts on backup failure.
- ✓Docker: backup.pl — manual mounts and DB steps. Plugin — runs inside OTOBO, zero extra work.
- ✓Setup: backup.pl — SSH and CLI access required. Plugin — install via Package Manager, browser-only.
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:
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.
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:
- ✓Do you know where your current backups are stored, and are any of them off-site?
- ✓Is your backup schedule actually running? Check the last archive date.
- ✓Have you tested a restore in the last six months?
- ✓Are your backups encrypted at rest and in transit?
- ✓Would you be alerted if a backup failed tonight?
- ✓Do you have a retention policy, or is cleanup manual?
- ✓If you use Docker, are your backup and staging paths properly bind-mounted?
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