Back to Main Site

PolyCMS Database Backup and Restore for RISE CRM

Last updated on Nov 22, 2026 7:37 AM 7:37 AM 2,121.66 ms

PolyCMS for RISE CRM includes a scoped Database Backup and Restore utility under PolyCMS > Tools > Backup / Restore (/polycms/tools#backup_restore). It exports and restores SQL snapshots covering only the dedicated PolyCMS {db_prefix}blog_* tables (default prefix rise_blog_*), leaving your core RISE CRM clients, projects, invoices, estimates, and support tickets completely untouched.

Accessing Backup and Restore

Navigate to PolyCMS > Tools and select the Backup / Restore tab (or open /polycms/tools#backup_restore directly using URL hash deep-linking). Both backup generation and SQL restoration are restricted to RISE CRM Administrators (polycms_is_admin()).

Private backup working storage lives outside the public media folder at writable/polycms/backups/, protecting operational files from direct web access.

Creating a Database Backup

  1. Navigate to PolyCMS > Tools and open the Backup / Restore tab.
  2. Under Database Backup, click Download SQL Backup.
  3. PolyCMS dynamically resolves your RISE CRM database prefix ($db->getPrefix(), default rise_) and generates an SQL dump containing table drop/create definitions and insert statements for your CMS tables.
  4. Your browser downloads a timestamped file named polycms_backup_YYYY-MM-DD_HH-ii.sql.
  5. Store the .sql snapshot in a secure off-site location (such as encrypted cloud storage or a versioned backup drive).

PolyCMS 19-Table Database Architecture

PolyCMS stores all website content, taxonomy, navigation, extensions, and settings in 19 dedicated InnoDB tables prefixed with your RISE CRM database prefix ({db_prefix}, default rise_):

Table Group Tables ({db_prefix} + Name) Count
Content blog_posts, blog_pages, blog_page_meta 3
Taxonomy blog_categories, blog_tags, blog_post_categories, blog_post_tags, blog_post_meta 5
Engagement blog_comments 1
Media blog_media 1
Navigation blog_menus, blog_menu_items, blog_widgets 3
Extensions blog_plugins, blog_plugin_options, blog_themes, blog_theme_options 4
Configuration blog_settings, blog_permalink_settings 2

No core RISE CRM business tables (such as clients, projects, invoices, tickets, tasks, or users) are modified by PolyCMS backup or restore operations.

Restoring from an SQL Backup

  1. Navigate to PolyCMS > Tools > Backup / Restore.
  2. Under Database Restore, select a valid .sql backup file (maximum file size: 50 MB).
  3. Click Restore Database.
  4. Confirm the operation inside the SweetAlert2 confirmation dialog.
  5. PolyCMS validates the SQL file, executes the restore inside a database transaction with foreign key checks temporarily paused, and automatically clears the frontend HTML cache (writable/polycms/cache/) upon completion.

Built-In SQL Restore Security Guardrails

Before running a single statement, Tools::restore() enforces strict server-side security validation:

  • File Type and Size Check: Accepts only .sql files up to 50 MB.
  • Blocked Dangerous Directives: Rejects files containing INTO OUTFILE, INTO DUMPFILE, LOAD_FILE, LOAD DATA, GRANT, REVOKE, CREATE/ALTER/DROP USER, or CREATE/DROP DATABASE.
  • CMS Table Allowlist: Permits DROP TABLE, CREATE TABLE, INSERT, REPLACE, and TRUNCATE statements only when the target table strictly matches {db_prefix}blog_* or {db_prefix}polycms_*. Any statement targeting a core RISE CRM table is immediately blocked and logged.

Important Warnings and Best Practices

  • Backup Before Restoring: Restoring an SQL snapshot overwrites your existing PolyCMS tables. Always download a fresh backup before restoring an older snapshot or running Generate Content Template in Demo Data.
  • Back Up Uploaded Media Separately: SQL backups preserve database records (including blog_media metadata) but do not include physical image or file uploads. Back up {rise_crm_root}/files/polycms/ alongside your .sql files for complete disaster recovery.
  • Maintain Full CRM Backups: Because PolyCMS isolates backups to CMS tables, keep your standard server-level RISE CRM database backups running on a regular schedule.
  • Verify on Staging First: Before restoring a major snapshot onto a live company site, test the .sql file on a staging RISE CRM instance.

Related Documentation