APPLICATION MANAGEMENT
Users or server administrators can copy documents in a database that meet specified criteria to an archive database and then delete the documents from the database. When documents that meet the specified criteria are deleted from the database, replica stubs remain so that deletions can replicate if there are replicas of the database.
Users or administrators can archive documents based on days since the documents were last read, last modified, and/or marked as expired. From IBM® Lotus® Domino(TM) Designer, you enable archiving and specify settings that control what happens when a database is archived.
To enable database archiving
1. Select a database and choose Edit - Properties or right-click the database name and choose Database - Properties.
2. In the Settings section on the Info (i) tab of the Database Properties box, select "Archive Settings."
3. View or edit archive settings on the Basics, Settings, or Advanced tabs of the Archive Settings dialog box.
Archive Settings
The tool creates an archive database with the title of the source database followed by the word "Archive" in parentheses -- for example, "Sales (Archive)." By default, the archive database is stored on a client or server within the data folder in a folder called \archive. The file name for the archive database is a_xxxxx.nsf where xxxxx represents the first five characters in the source database file name -- for example, a_sales.nsf. You can customize the location and file name of the archive database.
The tool can also report information about the archiving process to an archive log database with the title Archiving Log. By default, the Archiving Log is stored on a client or server within the data folder in a folder called \archive. The file name for the archive database is l_xxxxx.nsf where xxxxx represents the first five characters in the source database file name -- for example, l_sales.nsf. You can customize the location and file name of the archive log. Multiple databases can share one Archiving Log.
You can archive documents on the client or on a server.
When you archive documents on the client, you use an archive database and archive log on the client, and you run the archiving tool from the client. When you archive documents on a server, you create the archive database on a server rather than create it on the client. In addition, if the source database is located on a server, you can set up server-based archiving to use the Compact task on that server to archive the database rather than manually archive from the client. When you set up archiving, the tool signs the archive settings with your signature; the Compact task uses the signature to verify that you have the necessary database access to archive and then archive on your behalf. Server-based archiving also allows you to: