25.06.2013 Views

Lotus Domino Administrator 7 Help - Lotus documentation

Lotus Domino Administrator 7 Help - Lotus documentation

Lotus Domino Administrator 7 Help - Lotus documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ebuild if the Fixup task deletes corrupted documents from a source <strong>Domino</strong> Directory which are then<br />

replaced through replication. A partial rebuild is a longer process than an update, but takes less time than<br />

a full rebuild.<br />

Note: This is true of any replica of the <strong>Domino</strong> Directory that the DirCat task aggregates. If a replica of a<br />

<strong>Domino</strong> Directory is replaced with a file operating system copy with the same replica ID, when the Fixup<br />

task runs on that replica those changes are replicated back to the aggregation server’s <strong>Domino</strong> Directory.<br />

This in turn flags the DirCat task to do a partial rebuild on the aggregation server.<br />

Running the Dircat task<br />

Run the Dircat task to build a directory catalog initially. Then continue to run the task at scheduled<br />

intervals to keep the contents of the directory catalog synchronized with the contents of the source<br />

<strong>Domino</strong> Directories and to keep the directory catalog synchronized with the directory catalog<br />

configuration selections.<br />

Always run the Dircat task on one server to build and update a particular directory catalog. If you run<br />

the Dircat task on more than one server against the same directory catalog, replication conflicts occur. Use<br />

the field ″Restrict aggregation to server″ in a directory catalog configuration document to ensure that the<br />

Dircat task on only one server can process a particular directory catalog.<br />

Running the Dircat task on schedule: Schedule the Dircat task on a Dircat server to run at regular<br />

intervals by doing the following:<br />

1. Make sure there is a directory catalog database with a completed configuration document.<br />

2. From the <strong>Domino</strong> <strong>Administrator</strong>, click the Configuration tab.<br />

3. Expand Directories - Directory Cataloger, and choose Settings.<br />

4. Click the Server Tasks tab, then the Directory Cataloger tab.<br />

5. Complete these fields, and then click Save & Close:<br />

Field Enter<br />

Directory Catalog<br />

filenames<br />

Schedule Select Enabled.<br />

Run Directory Catalog<br />

aggregator at<br />

The file name(s) of the directory catalog(s) the Dircat task should process. Separate<br />

multiple file names with commas.<br />

A time range or one or more specific times to update the source directory catalog.<br />

Separate multiple time entries with commas (,).The default is the range 08:00 AM to<br />

10:00 PM.<br />

Repeat interval of A number representing the minutes between updates that are scheduled during a time<br />

range. The default is 360 minutes (every 6 hours). Consider reducing this interval to<br />

have the Dircat task run every 60 or 120 minutes.<br />

Days of week The days of week to run the Dircat task. The default is daily.<br />

Running the Dircat task manually: To run the Dircat task manually on a Dircat server, issue this server<br />

command:<br />

load dircat dc.nsf<br />

where dc.nsf is the file name of a local directory catalog on the server.<br />

You can do a full rebuild of a directory catalog. Keep in mind that a full rebuild removes and recreates all<br />

the aggregated documents so that the first replication after the rebuild will require a full replication of the<br />

database.<br />

To do a full rebuild of a directory catalog, you can run the dircat task against the directory catalog using<br />

the -r switch, for example:<br />

load dircat dc.nsf -r<br />

634 <strong>Lotus</strong> <strong>Domino</strong> <strong>Administrator</strong> 7 <strong>Help</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!