There are two complimentary ways of doing backups:
The native backup may be relatively slow since it will back up the entire database and its metadata each time it is run. It may also not produce backups that are suitable for migration to a different database.
Use pg_dump for PostgresQL.
If the Libelle Mail Archive backup system is to be used, it will have been configured as part of the Installation step 4: Downloaded file placement and customisation.
MABackup is designed to provide a fast, incremental backup and to be database-independent. Each time it is run:
MAUpdate has the ability to remove unwanted messages, e.g. spam, and associated addresses from the archive. To avoid keeping backups of the unwanted messages and addresses, MAUpdate notifies MABackup that deletions have taken place by making a note in the database. This causes MABackup's next run to delete all existing increments and do a complete backup. After this it reverts to incremental operation. The full backup is about 10-20% slower than the equivalent native database backup.
It is the archive owner's responsibility to organise the storage of offline copies of either type of backup.
Incremental backups are much faster than either native database backups or a full backup with MABackup. Representative performance details are given here.
See your database manual for details of how to restore native database backups.
Use pg_restore for PostgresQL.
Restoring from this type of backup is a four step process: