pghoard VS https://alanaknows.com/

• Multi-cloud object storage support
  pghoard supports backing up to multiple cloud storage providers including AWS S3, Google Cloud Storage, Azure Blob Storage, Swift, and local filesystem, giving flexibility in choosing or switching backup destinations.
• Streaming WAL archiving and compression
  It supports continuous WAL streaming and archiving with built-in compression (using algorithms like Snappy, LZMA, or zstd) and encryption, reducing storage costs and improving backup transfer efficiency.
• Point-in-time recovery (PITR)
  pghoard enables point-in-time recovery by combining base backups with WAL segments, allowing restoration of a PostgreSQL database to any specific moment, which is critical for disaster recovery scenarios.
• Open source and actively maintained by Aiven
  Being maintained by Aiven, a company specializing in managed database services, pghoard benefits from real-world production use, ongoing updates, and community contributions, ensuring reliability and continued support.
• REST API and monitoring integration
  It provides a REST API for managing and monitoring backup operations, and can integrate with monitoring systems, making it easier to automate backup workflows and track backup health in production environments.

Possible disadvantages

• PostgreSQL-specific tool
  pghoard is designed exclusively for PostgreSQL, so organizations using multiple database systems would need separate backup solutions for other databases, increasing operational complexity.
• Complex initial setup and configuration
  Setting up pghoard requires careful configuration of cloud storage credentials, encryption keys, and WAL-G-like settings, which can be complex for users unfamiliar with PostgreSQL internals or cloud storage APIs.
• Limited GUI or dashboard
  pghoard primarily operates via command-line and configuration files with a basic REST API, lacking a polished web-based dashboard for easier visualization and management compared to some commercial backup solutions.
• Documentation gaps for edge cases
  While basic documentation exists, users have reported that some advanced use cases, troubleshooting steps, and edge-case scenarios are not thoroughly documented, requiring deeper investigation into the source code.
• Smaller community compared to alternatives
  Compared to more widely adopted tools like pgBackRest or Barman, pghoard has a smaller user community and fewer third-party resources, tutorials, or plugins, which may limit support options for troubleshooting.

• Domain still registered
  The domain alanaknows.com is still owned and registered, meaning the owner has the option to reactivate or rebuild the site in the future rather than losing the domain entirely.
• Placeholder prevents dead link errors
  Instead of showing a generic browser error (like a DNS failure), the hosting provider displays a suspended page notice, which can be less confusing to visitors than a broken connection.
• Potential for future content
  Since the domain is intact, if the account issue is resolved, the original website content could potentially be restored without needing to re-register the domain.
• Clear indication of status
  The suspended page URL (cgi-sys/suspendedpage.cgi) clearly signals that this is a hosting-related suspension rather than the site being permanently deleted, which can help users or search engines understand the temporary nature of the outage.
• No malicious content risk
  Because the site is suspended and not actively serving custom content, there is no current risk of the site hosting malware, spam, or other harmful material that active but neglected sites might accumulate.

Possible disadvantages

• Website is completely inaccessible
  The main URL redirects to a suspended page, meaning visitors cannot access any actual content, information, or services that the site was intended to provide.
• Unprofessional appearance
  A suspended page gives a poor impression to visitors, potential clients, or collaborators, suggesting neglect, financial issues, or abandonment of the site or associated business/brand.
• Loss of SEO and traffic value
  Prolonged suspension can hurt search engine rankings and any previously built organic traffic, as search engines may de-index the site or lower its authority due to inaccessibility.
• Unknown cause of suspension
  The suspension could be due to unpaid hosting bills, terms of service violations, or technical issues, and without more context, users or stakeholders cannot know the severity or how soon it might be resolved.
• No information available
  Since the site is suspended, there is no way to evaluate the actual content, design, functionality, or purpose of the original website, making it impossible to assess its value or quality.

• Pgbackrest is no longer being maintained

  The "closest" would be using Barman with hook scripts (https://docs.pgbarman.org/release/3.18.0/user_guide/hook_scripts.html#hook-scripts-using-barman-cloud-scripts-as-hooks-in-barman) if you rely on cloud storage for storing backups.... - Source: Hacker News / 6 months ago

• Future PostgreSQL: improvement to the replication protocol

  This story starts with our own PgHoard, a PITR backup tool for PostgreSQL. PgHoard offers several methods to archive the WAL (Write Ahead Log), including pg_receivewal, a small application shipping with PostgreSQL which connects to a... - Source: dev.to / almost 5 years ago

Tracking https://alanaknows.com/ since Jan 2023.