When dunning falls through: a typical day-to-day scenario
An invoice is overdue and the dunning process needs to start — but the Debentra server does not respond, attachments are unreachable and reminders fail to send. Such situations create unnecessary extra work for accounting and receivables management. A clear, tested backup and restore plan prevents exactly these downtimes and protects the integrity of open items, documents and system configurations.
Why backup strategies for Debentra are important
Debentra runs on-premises in your environment and manages sensitive invoice data and attachments. The self-hosted architecture means full data sovereignty — but also responsibility for availability and recoverability. A pragmatic focus on two concrete benefits:
- Rapid resumption of dunning runs after disruptions (minimized downtime risk).
- Reliable traceability and integrity of open items, documents and settings.
Building blocks of a robust backup strategy
A complete solution combines three elements: consistent database dumps, filesystem snapshots for attachments and regular exports of configurations. Only the combination ensures that after a restore both the data and the workflows are recoverable.
Database dumps: the core of recovery
The relational database contains invoices, open items, payments, installment plans and status information. Regular, transactionally consistent dumps are mandatory:
- Create daily full backups and hourly incremental dumps if your business risk requires it.
- Use the native tools of the DB engine in use (e.g. pg_dump for PostgreSQL, mysqldump for MySQL) and enable transaction-consistent options (--single-transaction for PostgreSQL).
- Store dumps encrypted and at least in a second location (offsite or S3-compatible object storage).
- Maintain a rotation-based retention (e.g. daily backups 7 days, weekly 8 weeks, monthly 12 months) — adapt retention to legal and operational requirements.
Filesystem snapshots for documents and attachments
Attachments (PDFs, scans, emails) are often stored as files on the server or in an object store. In a restore these must be consistent with the DB:
- Use filesystem-level snapshots (LVM, ZFS) or block-level snapshotting of your storage layer to establish point-in-time consistency with the DB.
- If attachments reside in object stores: enable bucket versioning and replication to a secondary storage.
- Document the mapping between file paths and database entries to enable integrity checks.
Configuration Exports: Backing up system settings
System configurations, e-mail templates for dunning, user rights and workflow settings must be backed up separately:
- Export configurations regularly using the available export functions or via the API.
- Back up environment variables, secrets manager entries and web server or proxy configurations (e.g. nginx, HAProxy).
- Keep scripts and infrastructure-as-code (Terraform, Ansible) versioned in the Git repository.
Automation, Encryption and Retention
Automate backups with cron jobs or scheduling tools and monitor runtimes and return codes. Encrypt backups at rest and in transit (AES-256, TLS). Define clear retention periods and document permissions for restore access.
Recovery Checks and Validation: five sensible checks
A backup is only as good as the ability to restore it correctly. Perform these checks regularly:
- Integrity check of dumps (checksums / SHA256) after creation and before restore.
- Test restore in a staging environment: import the DB, mount attachments, import configuration.
- Application-level sanity: Are open items visible? Can dunning runs be simulated?
- Comparison of open items: export items before the backup and after the restore; compare counts and totals.
- Routine log review: Do transaction logs/journals match the expected activity periods?
Test Playbook for IT Teams: Step by step
The following playbook is suitable as a repeatable procedure for emergencies and drill tests. Align RTO (Recovery Time Objective) and RPO (Recovery Point Objective) with business requirements.
Preparation (weekly)
- Check the most recent backups: existence, size, checksums.
- Perform a test restore in a staging environment and document duration and issues.
- Export the list of open items (emergency CSV) and store it encrypted in a secure location.
Emergency Recovery (in case of incident)
- Perform an immediate up‑to‑date DB dump (if still possible) and secure attachments via snapshot.
- If the server has failed completely: provision replacement servers/containers and restore the operating system and dependencies from IaC templates.
- Apply the last consistent DB dump and mount the corresponding filesystem snapshot for attachments.
- Import configuration exports and review e‑mail templates for dunning notices.
- Perform a quick validation check: log into the system, view open items, send a test reminder e‑mail (always with manual approval before production sending).
- If recovery is delayed: use the emergency CSV export of open items to send manual reminders temporarily and to record incoming payments.
Practical tips for Debentra installations
- Debentra is self‑hosted – plan backups so that data sovereignty is maintained: no permanent dependency on third‑party cloud services without secured replication.
- If using Debentra PRO: pay special attention to DB consistency, since automatic allocations will need to be restored.
- With Debentra PREMIUM including integrated accounting: extend the backup with periodic exports of booking data so that external accounting audits remain possible.
- Create a runbook that documents responsibilities, contact lists and approval processes for dunning notices – automation relieves workload, final approval remains with the user.
Regular drills instead of theoretical plans
Schedule semi‑annual restore drills with accounting and the receivables team. Exercises should simulate real scenarios: partial data loss, corrupted attachments, faulty configurations. Only this way will you identify gaps in the process and documentation.
Conclusion: Practical, testable and aligned with your operational reality
A pragmatic backup plan for Debentra combines consistent DB dumps, filesystem snapshots for documents and regular configuration exports. Supplemented by automated monitoring, validation checks and a clear test playbook, it minimizes downtime during dunning runs and protects your company's data sovereignty.
Would you like to match the backup requirements to your Debentra edition? Check which edition best fits your operational size and integration needs: BASIS, PRO or PREMIUM. Find more details and an edition comparison here: Choose edition.
Next step
Try Debentra yourself
Central overview and process control for open items and payments with full data sovereignty; reduces manual allocation work (PRO) and enables integrated accounting (PREMIUM); selectable installation and licensing models.