Backup and restore

A useful backup includes PostgreSQL, filestore, configuration, package versions, and keys needed to decrypt or sign documents.

Learning objectives

• Automate encrypted backups with retention. When finished, verify the result with a test record and document ownership.
• Keep at least one copy outside the server. When finished, verify the result with a test record and document ownership.
• Record Tryton and installed module versions. When finished, verify the result with a test record and document ownership.
• Restore periodically in isolation. When finished, verify the result with a test record and document ownership.
• Verify accounting integrity and files after restore. When finished, verify the result with a test record and document ownership.

Concepts to master

• Automate encrypted backups with retention.
• Keep at least one copy outside the server.
• Record Tryton and installed module versions.
• Restore periodically in isolation.
• Verify accounting integrity and files after restore.

Guided practice

1. Activity 1. Automate encrypted backups with retention. Perform it in staging first, record preconditions, and compare expected and actual results.

2. Activity 2. Keep at least one copy outside the server. Perform it in staging first, record preconditions, and compare expected and actual results.

3. Activity 3. Record Tryton and installed module versions. Perform it in staging first, record preconditions, and compare expected and actual results.

4. Activity 4. Restore periodically in isolation. Perform it in staging first, record preconditions, and compare expected and actual results.

5. Activity 5. Verify accounting integrity and files after restore. Perform it in staging first, record preconditions, and compare expected and actual results.

How to verify the result

• Company, user, language, time zone, and date match the scenario.
• Permissions allow only operations assigned to the responsibility.
• Changes are traceable and related documents remain consistent.
• The procedure is repeatable and has a documented correction path.
• A restored backup can reproduce the process without relying on production.

Common mistakes

• Confusing save with confirm, post, pay, or close.
• Testing only as administrator and assuming access rights work.
• Changing states or totals with SQL to bypass validation.
• Upgrading without inventory, restorable backup, and post-upgrade reconciliation.
• Documenting only the happy path while omitting cancellation, correction, and exceptions.

Developer perspective

Identify the models, fields, buttons, domains, and access rules involved. Before extending the process, locate the module that owns the rule, review its tests, and preserve invariants through super(). A correct customization must work across companies, languages, permissions, and states.

Production checklist

• Company, user, language, time zone, and date match the scenario.
• Permissions allow only operations assigned to the responsibility.
• Changes are traceable and related documents remain consistent.
• The procedure is repeatable and has a documented correction path.
• A restored backup can reproduce the process without relying on production.