Program Output

Imagine taking a picture of your running application at a specific time. Program Output Backup does something similar, but instead of copying all the application files, it captures its internal communication with the computer. This communication, often referred to as "standard output" (stdout), contains all the essential information needed to recreate the application's state if necessary.

Supported Applications:

Program Output Backup is versatile and works with a wide range of applications, including:

  • Databases: MySQL & MariaDB (using the mysqldump command)

  • MongoDB (using the mongodump command) - Dedicated support also available for a more streamlined experience.

  • PostgreSQL (using the pg_dump command)

  • Materialize DB (leveraging the Postgres-compatible pg_dump command)

  • Interbase & Firebird (using the gbak command for both)

  • WordPress (using the wp db export command)

  • Virtual Machines: Docker (using the docker save command)

  • OpenVZ & Proxmox VE (using the vzdump command for both)

  • Other Databases: CockroachDB (using the cockroach dump command)

  • Neo4j (using the neo4j-admin dump command)

  • RethinkDB (using the rethinkdb dump command)

Important Considerations:

  • Progress Tracking Limitation: Due to the direct data streaming nature, progress bars or estimated time remaining (ETA) calculations are unavailable during backups using Program Output Backup.

  • Warning Signs: Errors appearing on stderr are considered warnings and documented in the backup report. These might indicate potential issues with the application's data during the backup process.

  • Error Codes and Job Status: If the application exits with an error code (non-zero exit code), it's logged in the report, and the entire backup job might be marked as unsuccessful.

Last updated