This is an old revision of the document!
To backup VPOP3 version 5 you should:
The DBBack-<number>.DMP files contain all the settings/data, so you can just backup those files now if you wish, although we'd recommend doing a full directory (except for the VPOP3\pgsql folder) backup if possible.
You do not need to backup the registry in version 5 (as you did for earlier versions) because settings are now stored in the main database.
If you want to make a Database backup at a specific time (rather than just the automated daily backups of the database) you can do the following:
This will create a file 'database.dmp' containing a backup of the database at the current state in the VPOP3 directory.
VPOP3 version 5 uses PostgreSQL 9.1, and stores all settings/messages in the database. This means that you can use alternative PostgreSQL backup procedures. These are outside the scope of this article, but for advanced users may give big benefits, eg hot standby servers, point-in-time-recovery (PITR), incremental backups etc.
There are articles on the PostgreSQL website describing how to set these up, for instance:
There will generally be a minute or less of downtime to do this, as, apart from the reconfiguration of the master PostgreSQL server, the rest of the process can be performed with the master PostgreSQL server running and operating normally.
(If you have a support contract, or pay for a single support incident, then we can help set this up for you.)
To backup VPOP3 version 3 or 4 you should:
If you want to make a Database backup at a specific time (rather than just the automated daily backups of the database) you can do the following:
This will create a file 'database.dmp' containing a backup of the database at the current state in the VPOP3 directory.
To backup earlier versions of VPOP3 you should: