Skip to content

KB-103 – Backup Strategy

Knowledge Base ID: KB-103 Project: BLACK ERP Version: 1.0 Status: Certified Last Update: 2026-06-26

Change History

Version Date Description
1.0 2026-06-26 Initial Backup Strategy document.

1. Objective

Define the official backup strategy for the BLACK ERP platform.

This document establishes the components that must be protected, the backup procedures, naming conventions, storage locations, validation process, and recovery objectives.

2. Backup Philosophy

A backup is considered valid only if it has been successfully restored and validated.

BLACK ERP maintains independent backups for:

  • Application Runtime
  • Database
  • Configuration
  • Knowledge Base Documentation

Every backup shall be verified periodically through recovery testing.

3. Backup Scope

The following components are part of the certified backup strategy.

Component Backup Required Status
PostgreSQL Database Yes ✅
ADempiere Application Yes ✅
Tomcat Runtime Yes ✅
Nginx Configuration Recommended ⏳
SSL Certificates Recommended ⏳
Knowledge Base Yes ✅

4. Certified Backup Files

Database Backup

blackerp_mx_template_v1.backup

Purpose:

Logical PostgreSQL backup generated using pg_dump.

Contains:

  • Database schema
  • Metadata
  • Business data
  • Accounting configuration
  • Application Dictionary
  • Customizations

Application Backup

blackerp_application_v1.tar.gz

Contains:

  • ADempiere installation
  • Tomcat Runtime
  • Shared Libraries
  • WAR Applications
  • Packages
  • Configuration
  • Startup Scripts

5. Backup Storage

Current backup location:

/opt/backups/adempiere/

Recommended contents:

README_TEMPLATE.txt
blackerp_application_v1.tar.gz
blackerp_mx_template_v1.backup

Additional backups should follow the same directory structure.

6. Naming Convention

Application backups:

blackerp_application_YYYYMMDD.tar.gz

Database backups:

blackerp_database_YYYYMMDD.backup

Template backups:

blackerp_template_vX.backup

7. Backup Frequency

Component Frequency
Database Before every structural change
Application Before every deployment
Full Infrastructure Before major upgrades
Knowledge Base After approved documentation updates

8. Recovery Validation

A backup shall not be considered certified until it has been restored successfully.

Minimum validation includes:

  • Service startup
  • WebUI accessibility
  • Admin accessibility
  • WStore accessibility
  • Database connectivity

9. Recovery Objectives

Objective Status
Application Runtime Recovery ✅ Certified
Database Recovery ⏳ Pending Validation
Full Infrastructure Recovery ⏳ Pending Validation

10. Backup Checklist

Before generating a backup:

  • Verify system health.
  • Ensure sufficient disk space.
  • Confirm active services.
  • Notify maintenance window if required.

After generating a backup:

  • Verify file integrity.
  • Record file size.
  • Store backup in certified location.
  • Update backup inventory.
  • Schedule recovery validation.

11. Engineering Principles

The following principles govern the backup strategy:

  1. Every backup must be reproducible.
  2. Every backup must be recoverable.
  3. Every recovery must be documented.
  4. Every certified recovery updates the Knowledge Base.
  5. Recovery validation is more important than backup generation.

12. Related Knowledge Base

  • KB-101 – Infrastructure
  • KB-102 – Disaster Recovery
  • KB-104 – Deployment Procedure
  • KB-106 – PostgreSQL Administration

Revision History

Version Date Description
1.0 2026-06-26 Initial document.