Note Before creating a replica on a server, make sure you are listed in the database ACL as a Manager. Otherwise, you may not have access to delete server replicas you create. If you attempt to replicate a server-based database to another server, you may encounter issues with server access. If so, ask your administrator for assistance.

If the Create Replica dialog box is not open, select or open the database you want to replicate and choose File - Replicate - New Replica.

When creating a replica, keep in mind that your user preferences control certain default settings for all replicas, such as general limits on document and attachment size, full-text index creation, and encryption.

For more information see Replication preferences.

Caution If you create a replica of your mail, make sure you give the new replica the same file name and path as the file specified in the "Mail file" field on the Mail tab of your current location document. You can use different mail file names/paths for different locations; make sure replicas you use for those locations have matching file names/paths. For more information, see Using different locations.

To create a full replica

1. Do one of the following:

• Open the database you want to create a replica for, and from the menu, choose File - Replication - New Replica.
• Drag the database's bookmark to the Replicator icon on the bookmark bar.
• Right-click the bookmark and choose Copy Bookmark to Clipboard. Click the Replicator icon on the Bookmark bar to open the Replicator page. From the menu, choose Edit - Paste.

• To create the replica locally in the data directory (the default), proceed to step 4.
• To create the replica on a server, in the Server list, select or enter the name of a server on which you want to create the replica, and click OK.
• Modify the file name for the replica in the "File path" field. To specify a file path, click the folder icon and browse to the directory on the server where you want to save the replica.

• To create the replica on a server, in the Server list, select or enter the name of a server on which you want to create the replica, and click OK. Notes changes the title of the dialog box to Create Replica for Database DatabaseName.
• To create the replica locally, modify the file name for the replica in the "File path" field. To specify a file path, click the folder icon and browse to the directory in your operating system where you want to save the replica. Modifying the file name in any way will prevent overwriting if the original database is local, but the title of the dialog box changes only if you enter a different file path.

• (Optional) Select "Encrypt the replica using" and choose an encryption type (Strong, Simple, or Medium) from the list.
• (Optional) To improve full-text searching of this replica, select "Create full text index for searching." To save space on your hard drive, deselect it.
• (Optional) To use the same security settings for the replica as for the original database, leave "Copy Access Control List" selected. To use different settings, deselect it. The check box is available only when you are not the database manager and the database's ACL is not set to enforce a consistent ACL across all replicas.
• (Optional) To create the new replica when you click OK, regardless of the setting in your replication preferences, leave "Create Immediately" selected. To wait until the next scheduled replication, deselect this option.
• (Optional) To customize settings for this replica, such as whether to replicate to or from the server (or both), a schedule, and which documents in the database to replicate, click More Settings.

Note Notes adds a bookmark (in your History folder) and a database entry to the Replicator page for each local replica you create. You can use the Replicator page to update (replicate) your replicas.

Access levels

When you create a local replica, Notes assigns you Manager access to the replica. However, if you do not have the appropriate access to the original database on the server (for example, you have only Reader access), you cannot replicate changes you make in the replica back to the server.

Note If a database manager enforces a database's access control list (ACL) across all replicas and you create a replica of the database, Notes assigns you the same access to the replica that you have to the original database. For example, if you have Author access to a database, Notes assigns you Author access to the replica. For more information about a database's ACL, see the database's manager.

Purge intervals

When you delete a document from a database, Notes keeps a deletion record that identifies the document. This way, Notes can replicate the document to other replicas even though it's been deleted from the original database. The default purge interval is 30 days. To make sure you receive documents deleted from a database, replicate at least once during every purge interval (for example, once every 30 days).

Notes removes deletion records from a database when they are older than the database's purge interval. A database's purge interval is one-third the number of days specified in the "Remove documents not modified in the last" box (on the "Space Savers" tab of the Replication Settings dialog box). For example, if 60 days are specified, the purge interval is 20 days. Removing deletion records frees up the disk space the deleted documents occupied.

When Notes removes documents that are older than the purge interval from a replica, Notes does not create deletion records for the documents.

See Also

Replication: the secret to working offline