標題: Configuring managed replicas using the Desktop Settings document
網址: http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21437957
內容:
Configuring managed replicas using the Desktop Settings document

Technote (troubleshooting)

Problem
The 8.5.1 Administrator Help database that will be included with release 8.5.2 does not include this information. This technote is the repository for this information until a future release when the documentation content will again be updated.

Resolving the problem
You can specify settings for managed mail replicas on the Mail tab of the Desktop Settings document.
For users affected by the policy, you can use the policy to enable managed replicas by selecting one of the following options for "Local mail file":

Option	Result on user's desktop
Create local replica	Creates a local (non-managed) replica of the user's mail file. This setting was the default before the existence of managed replicas. If a managed replica already exists, this setting converts it to a non-managed local replica. Tip You can return to this default setting if you need to troubleshoot problems with managed replicas in your organization.
Create managed replica	Creates a new managed replica of the user's mail file. If a local replica already exists, this setting leaves it unconverted as a non-managed replica.
Create managed replica or convert local replica to managed replica	Converts the user's existing local mail replica to a managed mail replica, or if no local replica exists, creates a new managed mail replica.
Delete local replica or managed replica	Deletes any local mail replica, either non-managed or managed. Note Deletion occurs only after a final replication takes place and the mail file is no longer open in either the Lotus Notes or Domino Administrator client.

For each option, specify the following settings. The last five settings are in the new Managed Mail Replicas section that appears on the Mail tab if you select either "Create managed replica" or "Create managed replica or convert local replica to managed replica."

Setting	Action
Mail file location	To use managed replicas, choose Server.
Use local mail.box to send messages (faster)	Enter the number of mail messages that triggers outgoing mail when the mail file location is set to "on Server." If this setting has a value above 0, the client uses a local outgoing mail box for sending mail, and the client replicator routinely transfers messages from the local mail box to the server's mailbox. It is recommended that you enter 1, especially when using managed replicas, in order to transfer messages to the server as soon as they are deposited in the local mailbox.
Keep full document for most recent (days)	Enter a number of days. The default is 30. Non-modified documents older than the number of days will be truncated. The setting applies only when a new managed replica is created; it affects neither existing managed replicas nor existing non-managed (local) replicas.
Selective replica	Enable this check box to allow users to make the managed replica a partial replica.
Remove documents not modified in last (days)	This option appears only when the setting "Selective replica" is enabled. Enter a number of days, for example, 180, to control how long documents remain in the managed replica. The default keeps all documents indefinitely. 180 days should allow users to keep roughly six month's worth of messages. Note This setting applies only to managed replicas. Local non-managed replicas continue to use whatever settings the user chooses for a selective replica in the Notes Client preferences.
Amount of free space required before cache is created	Enter a number of megabytes. This setting does not allow the creation of a managed replica if the required space is not found. The default is 0 Mb and the client replicator attempts to create a managed replica no matter how much space a user has. If there is not enough space to create the replica, an error is added to log.nsf to alert the administrator to the problem, and no managed replica is created. Tip Specify a space number only if you expect users may have managed replicas too large for their local available storage, perhaps as a result of settings for the next two fields.
Amount of rich text to retrieve on truncated documents	This setting applies only to documents older than the value specified for the setting "Keep full document for most recent (days)." Enter a number of kilobytes. The setting controls how much rich text (body) data is initially added to the managed replica for any document older than the setting above. If the document's body is smaller than the value for this setting, the document is added. The default is 0 Kb. Note Entering a higher number can cause a longer creation time for the managed replica, but allows users to see more of their mail messages immediately. Tip This setting allows managed mail replicas to take up more space, so with this setting, it is recommended that you set a value for "Amount of free space required before cache is created."
Amount of attachment data to retrieve on truncated documents	This setting applies only to documents older than the value specified for the setting "Keep full document for most recent (days)." Enter a number of kilobytes. The setting controls how much attachment data is initially added to the managed replica for any document older than the setting above. If an attachment is smaller than the value for this setting, the attachment is added. The default is 0 Kb. Note Entering a higher number can cause a longer creation time for the managed replica, but allows users to see more attachments in mail messages. Tip This setting allows managed mail replicas to take up more space, so with this setting, it is recommended that you set a value for "Amount of free space required before cache is created."

The following settings under Client Settings also interact with the user's local non-mail replicas.

Setting	Action
Auto-retrieve document setting	This setting applies only to documents that are truncated (partial or summary documents) in any local replica. For fastest performance of managed mail replicas, select "Enable document without attachment." This setting retrieves rich text (body) data of a message when a user opens it in the managed replica, but does not retrieve attachment data without user action. Selecting "Enable document with attachment" for this setting retrieves all body and attachment data when a user opens the message.
Enable server to poll for new mail and trigger replication on notification of new mail	Select Enable to give users of managed replicas fastest performance. When this setting is enabled and a local mail replica (either managed or non-managed) exists, the client replicator pulls down new mail to the local replica any time the replicator detects a new message delivered to the user's server-based mail file.
Enable silent failover when a server goes down	Select Enable to prevent users from seeing an unnecessary message box when a server fails over to another in a cluster.

Controlling the number of managed mail replicas created concurrently in your organization

Performance of managed mail replicas can degrade if too many are created simultaneously. For this reason, 25 concurrent creations of managed replicas are allowed by default.

However, you can use a component of Smart Upgrade called the Smart Upgrade Governor to determine the number of replicas that can be created concurrently.

You can tell that you need to control the number of managed replicas created if users see the following message:
Access to this server has been restricted due to excessive load

Note Your users are not required to use the Smart Upgrade process in order for the governor component to control managed replica creation.

To allow more than 25 managed replicas to be created concurrently:

1. Edit the Server Configuration document
2. On the Client Upgrade tab, select "Enabled" for "Limit Concurrent Smart Upgrade" under "Smart Upgrade Governor.
3. Enter a smaller value for the Maximum Concurrent Downloads than the default of 100 that is set when the Smart Upgrade Governor is enabled, but larger than 25.
4. Save and close the Configuration document.