RADARPRINT GUIDE

Planning database and archive storage

Distinguish the product database from document storage and plan growth and recovery together.

In this guide

Database choice

The current setup wizard includes SQLite, PostgreSQL and other enterprise database options. Embedded SQLite can support a single-server installation without a separate database server. If your organization has an established database standard, verify support in the delivered release.

Plan these separately

  • Database: Users, job records, settings and reporting data.
  • Document archive: Archived files and related content.
  • Held jobs: Temporary storage for jobs awaiting release.
  • Backups: A restricted destination reserved for recovery.

Sizing

Measure daily document size and job count in the pilot. Multiply by the retention period and add room for growth. Page count alone is not a reliable estimate of disk use: high-resolution scans differ considerably from text documents.

Operational checks

Monitor free space and backup results regularly. Do not assume that a database backup automatically includes the document archive; verify the selected scope. Changing database engines requires a planned migration and recovery test, not an arbitrary configuration switch.