Title
Create new category
Edit page index title
Edit category
Edit link
What is the pg_dump database restore file used by MetaDefender Core?
This article applies to all MetaDefender Core V4 and V5 releases deployed on Windows or Linux systems.
MetaDefender Core uses a PostgreSQL database to store critical system information required for normal operation, including processing history and the current state of modules and engines.
When creating a backup, the database restore file is generated through a process called a database dump, using the PostgreSQL utility pg_dump.
What is the .sql file generated by pg_dump?
If pg_dump is executed in its default (plain-text) format, the output is a .sql file.
This file is a plain-text SQL script that contains all commands required to fully reconstruct the database, including:
- Database schema (tables, indexes, constraints, etc.)
- Data stored in the tables (records/rows)
- Other database objects required by MetaDefender Core
In short, the .sql file represents a complete logical backup of the MetaDefender Core database at the time it was created.
How MetaDefender Core uses the restore file
During a restore operation, the .sql file is executed against a PostgreSQL database to recreate:
- The database structure
- All stored operational data
This allows MetaDefender Core to resume operation with the same configuration and historical context as the original system.
Standalone database backup and restore overview
For environments using a standalone database (local PostgreSQL instance on the same machine as MetaDefender Core):
- Use
pg_dumpto generate the.sqlbackup file. - Restore the file using PostgreSQL tools (for example,
psql) on the target system. - Ensure the new Core instance uses the same database configuration (database name, user, and deployment context).
For detailed step-by-step instructions, refer to the article:
How to Backup and Restore standalone database for MetaDefender Core? - MetaDefender Core
Additional notes
- Restoring to the same machine typically works without issue.
- Restoring to a different machine may fail if environment-specific values (such as deployment ID or database name) differ.
- Always verify whether your deployment uses a standalone or shared database before performing a restore.
If Further Assistance is required, please proceed to create a support case or chat with our support engineer.
