ADMINISTERING
Back up all Domino® server data files including databases, template files, the NOTES.INI file, and ID files. Following your company's standardized backup procedures, back up files directly to tape or to a file server and then to tape. Never rely only on replication as your method of database backup. A damaged or accidentally changed database may replicate, and then your only recourse is to recover the database from a server backup tape.
About this task
You have two choices for backup procedures. You can use the traditional method of making backup copies of files, or you can use transaction logging.
Procedure
1. Domino requires that these files be open when it runs: LOG.NSF, NAMES.NSF, MAIL.BOX and the server ID file. If your backup utility cannot back up open files, you must shut down the server before you create the backup file.
2. Copy the server ID file to a disk, and store the disk in a secure place.
3. Make a replica of the Domino Directory on a workstation and keep it up-to-date by replicating the local replica with the server replica. Then if the Domino Directory becomes corrupted, you can quickly restore it by creating a new replica from the local workstation replica. Even if you do this, continue to back up the Domino Directory to tape. Never do this when transaction logging is used.
4. If your server participates in attachment consolidation using the Domino Attachment and Object Service (DAOS) back up the files in the DAOS repository using a standard file backup utility.
Related concepts Transaction logging
Related tasks Backing up servers that participate in attachment consolidation (DAOS)
Related reference How transaction logging works