Converse agora com nosso suporte
Chat com o suporte

Collaboration Services 3.9.1 - User Guide

Getting started with Collaboration Services Organizing objects for synchronization Resolving synchronization conflicts Managing the synchronization process Transport management Fine-tuning and maintenance Backup, restore, and troubleshooting

Set up debug logging

Collaboration Services service has debug logging when additional information is needed or when a support call is placed. Once turned on, a large number of files are generated which contain data from all areas within Collaboration Services. The logs are located in the follwoing folder: \Quest Software\Collaboration Services\ACSLOGS\Debug.

The debug log setting will consume a lot of disk space. The logs are archived in the Archive folder found in the folder for the logs mentioned above. The logging will have an impact on the speed Collaboration Services processes both incoming and outgoing data.

To enable debug logging
1
In the management console, right-click Collaboration Services and select Properties.
2
Click Logging | General, and select the Enable debug log check box.

Configure alerting

To receive notifications about service activities, configure the required notification method on the Logging | Email tab, the Logging | Net send tab, or both. For example, you can configure email notifications to be sent when a specified percentage of free disk space is exceeded.

Table 1. Alerting
Notification method
Used to
Configuration required
email
Send events of the selected types and notifications to the specified email address.
1.
Select the mailbox to which the email messages will be sent.
2. Select whether you wish to receive Error and Warning events, Information events, or both.
3. Specify the subject for the email message.
Net Send
Send the events of the selected types and notifications using net send to the specified computers.
1.
Specify the NetBIOS names, DNS names, or IP addresses of the computers to which net send should deliver messages. Separate multiple entries by semicolons.
2. Make sure the Messenger service is running on the Collaboration Services server and on the recipient computer.

Configure synchronization partners

Using the Synchronization partners node of the management tree, you can:

•
Configure new partners in the collaboration
•
Track current synchronization partners and their statistics
•
Manage the current collaboration structure and its forests

Configuring branch forests

The HQ forest administrator can manage the current collaboration structure in the following ways:

•
Add or remove branch forests
•
Include branch forests in the data synchronization process, or exclude them from it
•
Update the data encryption key (if it was changed by a branch) and provide an update for the appropriate public key file
To manage the collaboration structure
1
Select the Synchronization Partners node in the management tree.
2
Right-click and select Configure.
The Configure Branches Wizard is started.
On the Specify Branches step, you can add partners to or remove partners from the list of registered branch forests:
3
To add a partner, click Add and browse for the key file (.AKF) of the branch you need. Supply the authentication password and click OK.
4
To specify whether each branch is currently enabled (involved in synchronization), select the Enabled check box.
Clearing the box temporarily excludes the branch from collaboration. All statistics and configuration information related to the branch will be preserved until the branch is enabled again.
* 
NOTE: When you decide to re-enable the branch, be sure to request re-publication for all collections it is subscribed to; otherwise, all data included in updates sent during the time while the branch was disabled will be missing. The check box is not selected by default and should be left that way until the upgrade procedure is reviewed.
5
To specify whether upgrade packets should be sent to each branch, use the Send Upgrades check box.
* 
NOTE: The check box is not selected by default and should be left that way until the upgrade procedure is reviewed.
For details about upgrading the product and about this option, refer to the Quest Collaboration Services Deployment Guide.
* 
NOTE: Upgrade packages will not be sent to a disabled branch.
6
If any branch forest has changed its encryption key, you can update it by selecting the branch, clicking the Update Key button, and providing the appropriate public key file.
7
To remove a branch from the collaboration structure, select it in the list and click Remove.
* 
NOTE: If you remove a branch, all statistics and settings related to it will be lost. If you want to temporarily exclude a branch forest from the collaboration, clear the Enable check box instead of removing the branch.
Alternatively, to add, edit, or remove synchronization partners, you can use the Branches page of the Collaboration Services Properties dialog box.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação