Backup options for primedocs
Options for Database Backup and Transfer in primedocs
primedocs supports various methods to back up databases or transfer content between systems. This page provides an overview of the available options, their typical use cases, as well as key advantages and disadvantages to help you choose the right solution for your scenario.
Use this overview especially if you want to create a full backup, migrate a database between systems, or specifically transfer template data from one primedocs installation to another.
| Option | File Format | Use Case | Advantages | Disadvantages |
|---|---|---|---|---|
| SQL Database Backup | .bak | 1:1 copy or backup of the database. | Complete copy of the database. | - Typically requires direct access to the SQL Server. - Tied to the specific SQL Server version used. - No direct import into SQL Azure possible. - Import overwrites existing data; no partial import possible. |
| Package Export/Import (via Admin Dashboard) | .oopx | Export and import template data between different systems. | Selective choice of which template data to export and import. | - Not intended as a backup for the entire database. - Not all data can be exported. - primedocs proprietary format; no third-party products usable. |
| Datasource Export (via Admin Dashboard) | .zip | Copy databases between different systems. | - Complete copy of the database. - Import also possible on SQL Azure. | - RowVersions are rewritten, so no direct 1:1 copy. - Cannot be imported across versions. - primedocs proprietary format; no third-party products usable. - Import overwrites existing data; no partial import possible. |
| DACPAC Export (via Admin Dashboard) | .dacpac | Copy databases between different systems. | - Complete copy of the database. - Import also possible on SQL Azure. - Import across versions possible. - Microsoft tooling can be used. | - RowVersions are rewritten, so no direct 1:1 copy. - Import overwrites existing data; no partial import possible. |
The Datasource Export (.zip) and the DACPAC Export (.dacpac) are created in the Dashboard via the gear icon under database → export; the step-by-step instructions for these and for the Package Export (.oopx) can be found under Export (database and package), and the corresponding import under Import (database and package).
For a classic, complete backup of the primedocs database, the SQL Database Backup (.bak) is especially suitable, provided there is access to the SQL Server. For system changes or migrations between different environments, the DACPAC Export and the Datasource Export are useful, particularly if the target system is based on SQL Azure or Microsoft tooling is to be used — the DACPAC Export can additionally be imported across versions. If only specific template data is to be selectively transferred from one primedocs system to another, the Package Export/Import with .oopx files is recommended.
Recommended approach
- Back up regularly: Include the primedocs database in the existing database backup cycle (e.g. regular SQL backups). In addition, an export before server updates and before major changes to the template solution is recommended.
- Include the Operations database and configuration: In addition to the Datasource database, also include the Operations database (e.g. SCIM data) and the server-side configuration file
primedocs.configin the backup so that an environment can be fully restored. - Test the restore: Regularly verify backups with a test restore in a separate environment. A backup is only reliable if the restore has been demonstrably shown to work.
- Mind encryption: If the encryption key is database-specific, make sure the matching key is available when restoring into a different environment.