Database maintenance
Backing up, restoring, connecting to, and migrating the PostgreSQL database that holds Informer's metadata. PostgreSQL is the one component that cannot be easily recovered, so backups here matter most.
Back up before any database work
Connecting to or migrating PostgreSQL is an opportunity to lose data. Back up first, and stop all Informer components except PostgreSQL before restoring.
In this section
| Article | In one line |
|---|---|
| Informer backup guide | The quickest ways to back up: the in-app System Backup, the IR tool, and backing up to S3. |
| Backups and restores (Windows) | Back up and restore PostgreSQL from PowerShell on Windows. |
| Backups and restores (Linux w/ Docker) | Back up and restore PostgreSQL from the terminal on Docker. |
| Backups and restores with compression (Windows) | A compressed server-side backup for when the plain dump is too large. |
| Connecting to PostgreSQL | Open a psql session against the Informer database. |
| Creating a ./pgdata folder (Docker) | Move Postgres data to a host volume so it survives container changes. |
| Migrating PostgreSQL 11 to 16 (Windows) | The Windows path to PostgreSQL 16, required as of Informer 5.9. |
| Migrating PostgreSQL 11 to 16 (Linux w/ Docker) | The Docker path to PostgreSQL 16. |
| End of support for PostgreSQL 11 | What the PostgreSQL 11 end-of-support means for Informer. |
| End of support for SQL Server 2012 and earlier | Impact on legacy SQL Server Datasources, and the options. |
Where do I look when...
| You want to... | Start here |
|---|---|
| Take a quick backup | Informer backup guide |
| Back up or restore on Windows | Backups and restores (Windows) |
| Back up or restore on Docker | Backups and restores (Linux w/ Docker) |
| Shrink a backup that is too large | Backups and restores with compression (Windows) |
| Run a query against the database | Connecting to PostgreSQL |
| Move to PostgreSQL 16 | Migrating PostgreSQL 11 to 16 (Windows) or (Linux w/ Docker) |