MailCOPA Multi User Email Software - Backup

See also this page about the system for connecting to the data from client machines using TCP/IP.

Note that with multi-machine installations (where the data is not held on the computer running MailCOPA) data access will be much slower than where the data is held on the local machine. the latter will be at least 20 times faster, probably much more. This means that there may be pauses on client machines that may make it appear that MailCOPA has stopped responding.

The proprietary database used to store messages and addresses has proved very reliable in this and other implementations.

Nevertheless, it is sensible to make regular backups of your data, in case of accidental deletion or corruption, or hardware failures.

All of the data files are held in a single directory

It is a good idea to backup this entire directory regularly, by whatever means is best for you. A copy can be kept anywhere, either on the same machine or another on the network, or on a removable medium.

This should only be done when MailCOPA is not running and accessing the data.

Should you wish to access or restore backed-up data, it is important that your read the notes below about Restoring Data

As an additional precaution, you can easily archive incoming and outgoing messages by adding an action in each of the filters to copy the message to a specified directory: each message will be given a unique filename (for that directory) and saved as a text (.TXT) file. The theoretical limit on the number of messages that can be stored in a directory in this way is very high, but it would be sensible to move them elsewhere (perhaps into a ZIP archive) from time to time.

Note that if the MailCOPA archive directory is emptied, filenames previously used may be reused.

Restoring Data.

This information only applies where the data was backed up from the current version of MailCOPA. If you have upgraded (eg from 8.01 to 8.02) since the backup was made, please contact MailCOPA Support. This is because major version changes may change the structure of the database, making the old data incompatible with the new version.