Chatta subito con l'assistenza
Chat con il supporto

Archive Shuttle 11.5 - Administration Guide

Introduction Configuring Archive Shuttle Using HOTS Using the Archive Shuttle user interface Dashboards Manage Configuration Advanced configuration Monitoring Logging Reporting Journal Transformation migration Troubleshooting

EV collector journal collection logs

Occasionally, it may be necessary to check the EV Collector log files if there are any issues present. With large journal archives, the collection can take some time, and it might be important to check for collection issues.

First, Archive Shuttle will need to find and open the log files. They are stored on:

a) Machine where are the modules installed (ie: C:\Program Files (x86)\QUADROtech\Logs), in many cases it is the Source EV server. The log file name is “AS_EVCollector_Log.txt”

b) Machine where is core installed (ie: C:\Program Files\QUADROtech\Logs). You will find there two different log files for EV collector, first is the Client (Module) log file with name “ArchiveShuttle.WebServicesLog.HOSTNAME.EVCollector.Client.txt”, and the second one is the core log ArchiveShuttle.WebServicesLog.HOSTNAME.EVCollector.txt

Second, the log level may need to be changed to TRACE to collect detailed information.

Alternate mailbox support for discovered addresses associated with active users

In a Journal Transformation migration you might want to migrate active user content into inactive alternate mailboxes. This may simplify the migration and reduce project complexity. You may also want to do this if active users recently departed the organization or re-join after leaving.

In the Bulk Mapping wizard, when you select the Journal Transformation options there is an option called ‘Use alternate mailboxes’:

JTBM

If the option is enabled all collected Journal Transformation users will be treated as leavers after consolidation. This means that the users will be managed from the Journal Transformation Leavers Management page in the user interface.

Retry failed remediations

When performing a Journal Transformation it is possible to retry any remediation actions which fail.

FailedRemidiations

To start this process click on the button in the user interface, and a new page will be displayed:

FailedRemidiations2

More information can be obtained on this screen for each action, and each action can be retried. If a retry operation is performed it’s executed immediately.

Support handling of invalid or changed SMTP addresses

Archive Shuttle has the option to handle invalid of changed addresses. A changed address can occur when a primary SMTP address is changed on a user object.

When Archive Shuttle performs an Office 365 Sync operation, the user mapping in Journal Commander will be marked as ‘changed address’.

SMTPInvalid

The ‘Repair changed address’ button can be used to update/replace the Primary SMTP Address in all the appropriate Archive Shuttle database tables for the selected user mappings.

If a user mapping is not enabled for import the change of address will be immediate, as there is only a small update required. For a user mapping which is enabled for import the change of address may take a few minutes because there could be a large number of updates required.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione