How to restore a backup (PITR)

A PostgreSQL archive is restored from the Backups tab of the cluster page, in the Hikube console, or from Infrastructure > Backups > Archives.

Principle

Thanks to the continuous archiving of transaction logs, a restore can bring the database back to:

• the exact state of a backup;
• its most recent state;
• a precise point in time (PITR, Point-In-Time Recovery), between two backups.

The restore writes either onto the original cluster, whose content is overwritten, or onto another existing PostgreSQL cluster in the project, of the same major version.

Steps

• Restore a PostgreSQL or MariaDB database
• Restore a PostgreSQL database to a point in time

After the restore

Check your data before putting your applications back into service:

-- Check the data volume
SELECT schemaname, relname, n_live_tup
FROM pg_stat_user_tables
ORDER BY n_live_tup DESC;

If you restored onto another cluster, update your applications' configuration with its address (Internal and External zones of its page) and its credentials.

Restoring a logical export

If you have an export made with pg_dump, you can restore it yourself into an existing database:

pg_restore --no-owner --dbname "host=<host> port=5432 dbname=myapp user=app_user sslmode=require" \
  myapp-2026-06-15.dump

Going further

• Configure backups
• Manage users and databases