Back up and restore your builder pages.

What to back up and how to restore builder content

Learn DXPR BuilderManage the siteMeet compliance requirements

You keep a copy of every builder page, image and setting, and you can bring back a whole site or a single page. DXPR Builder keeps pages in Drupal's database and uploads in the files directory, so a normal Drupal backup covers it. This page lists what to include and how to restore it.

What to back up

Component	Location	Contains
Database	MySQL, MariaDB or PostgreSQL	Page content and every revision, plus the active configuration
Files directory	`sites/default/files/`	Uploads in `dxpr_builder_images`, `dxpr_builder_videos` and `dxpr_builder_files`
Configuration export	Your sync directory, often `config/sync/`	Settings, page templates, user templates, user profiles and the product key's Key entity

The editor's undo history lives in each editor's browser and is not part of any backup.

Back up a site

Dump the database:

drush sql:dump --result-file=backup.sql

Copy the files directory:

cp -r sites/default/files/ /backup/files/

If you keep configuration in code, export it as well:
```
drush config:export
```

Restore a site

Import the database:
```
drush sql:cli < backup.sql
```
Copy the files directory back to sites/default/files/.
If your configuration lives in code, import it:
```
drush config:import
```
Rebuild caches:
```
drush cache:rebuild
```

Roll back one page

Every builder save creates a revision, so one page comes back without a full restore.

Open the page's Revisions tab.
Find the revision before the unwanted change. Builder saves show the log message Saved with DXPR builder.
Click Revert.

What you see

The restored pages open in the editor with their layouts, images show for visitors, and the License section under General Settings still holds your product key.

If you don't see your content

Pages are back but images are broken. The files directory was not restored. Copy the dxpr_builder_images, dxpr_builder_videos and dxpr_builder_files folders back.
The editor asks for a product key. The Key entity that holds the key was not restored, or its environment variable is missing on this server. Check the License section at DXPR Studio

DXPR Builder > General Settings.
Visitors still see the pages from before the restore. A cache in front of the site serves old copies. Run drush cache:rebuild and purge Varnish or your CDN.

What's next?

Version control for tracking changes to continue exploring DXPR Builder.