Experience unparalleled peace of mind with Ahsay backup for your PostgreSQL database servers! Leveraging cutting-edge data protection technologies like Immutable backups, AES 256-bit encryption, Two-factor authentication, and Restore Drill, Ahsay ensures your databases are always secure. In the event of a disaster, you can count on a complete recovery, guaranteed. Protect your data with the best in the business!
Enhance your PostgreSQL database protection with Ahsay’s robust backup solution
- Supports PostgreSQL versions 12 to 16.
- Protects PostgreSQL database servers on Windows, Linux (CLI and GUI), and macOS platforms.
- Ahsay ensures data consistency by utilizing the pg_dump utility to stream backup data directly to the storage destination, eliminating the need for a staging file.
- Backups done with pg_dump utility does not lock the PostgreSQL database, allowing uninterrupted access for other users and applications.
- Supports logical backups, offering flexible recovery options. This means your backup data can be used to restore the database across different PostgreSQL versions and operating systems, ensuring maximum versatility and convienence.
What are the benefits?
Automated recovery quickly restores PostgreSQL databases files from the backup destination and applies them to the PostgreSQL database instance either on the original database server or remotely to a standby server over the LAN. For system administrator's who prefer more control over the recovery process, they can use the "Restore raw file" option, where AhsayOBM will restore the database files to local disk, the system administrator will have to manually create the databases and import them into the PostgreSQL instance.
Ahsay supports three recovery scenarios:
- Restore the database files and automatically applies them to the PostgreSQL database instance on the original server.
- Restore the database files and automatically applies them to the PostgreSQL database instance on a replacement or standby server on the same LAN.
- Restore the database files as raw files, then use manual recovery method to apply them to the PostgreSQL database instance to a standby or replacement server.