Skip to main content

Program Output

The "Program Output" backup type backs up the stdout (Standard Output) stream of any command execution. This allows you to make use of application-specific tooling for taking consistent, point-in-time snapshots of certain application software.

You may use the "Program Output" Protected Item type as an integration point to back up a variety of different programs with Comet. This includes, but is not limited to

  • MySQL and MariaDB using the mysqldump command
    • More integrated support is available using the dedicated MySQL Protected Item type
  • MongoDB, using the mongodump command
    • More integrated support is available using the dedicated MongoDB Protected Item type
  • PostgreSQL, using the pg_dump command
  • Materialize DB, using the Postgres-compatible pg_dump command
  • Interbase, using the gbak command
  • Firebird, using the gbak command
  • Wordpress, using the wp db export command
  • Docker, using the docker save command
  • OpenVZ, using the vzdump command
  • Proxmox VE, using the vzdump command
  • CockroachDB, using the cockroach dump command
  • Neo4j, using the neo4j-admin dump command
  • RethinkDB, using the rethinkdb dump command

Behavior

The program is run as part of the backup job. Any streamed data on stdout is saved as a virtual file within the backup job. The data is streamed directly to the backup destination and never touches the local disk. This has the consequence that no progress bar or ETA can be calculated or displayed during backup jobs.

You can choose any file name for the resulting virtual file within the backup job.

If the target application produces any content on stderr (Standard Error), it will be logged in the job report, and the final job status will not be less severe than "Warning".

If the target application exits with a non-zero error code, the error code will be logged in the job report, and the final job status will not be less severe than "Error".