Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Quadrotech Archive Shuttle 10.3 - Administration Guide

Logging Levels

There are several logging levels in log files, that vary in severity.

Solution

Here are listed all allowed logging levels in order from most severe to least severe along with explanation and example when to use it:

Fatal

·The highest log level, only the most important information is logged

·Minimum entries in the log file

Error

·High log level, application crashes/exceptions are logged

·Average number of entries in the log file

Warn

·High log level, incorrect behavior but the application can continue

·Average number of entries in the log file

Info

·Default log level, logging contains all above, used for normal behavior like item export

·Average number of entries in the log file

Debug

·Low log level, executed queries, user authenticated, session expired, etc

·Average number of entries in the log file

Trace

·The lowest log level, everything is logged, begin method X, end method X, etc.

·Maximal number of entries in the log file

Reporting

info

NOTE: The reports are in PDF format.

Each report can be configured to email one or more recipients, and is controlled via separate schedules, or, optionally triggered immediately using the ‘Send Now’ button.

info

NOTE: In order to send out reports it is necessary to use the System Configuration page and enter information in the SMTP Settings page.

This is controlled on the Scheduled Reports screen in the Archive Shuttle User Interface.

Scheduled Reports

Archive Shuttle includes a number of pre-built reports can be scheduled to be delivered to different recipients. This is controlled on the Scheduled Reports screen in the Archive Shuttle User Interface.

The current reports which are available:

Report Name

Description

Performance

This report shows export and import performance in a bar graph both as a summary and per source link for:

·The last day

·The last week

·The last 30 days

·The last 3 months

·The last 12 months

·A custom time frame can also be chosen

Stage2Reports

This report shows information relating to Stage 2, including:

·Containers that have finished Stage 2 in the last 24 hours

·Containers still in Stage 2

·Containers which are in Stage 2 and have errors

·Containers in Stage 2 which may be stuck/hung

·Containers in Stage 2 which have been paused.

FailedItemReport

This report shows items which have failed migration. The report is divided up per link, and shows:

·Items which have failed to export

·Items which have failed to import

 

info

NOTE: The reports are in PDF format.

Each report can be configured to email one or more recipients, and is controlled via separate schedules, or, optionally triggered immediately using the Send Now button.

info

NOTE: In order to send out reports it is necessary to use the System Configuration page and enter information in the SMTP Settings page.

Stage 1 (Sync Data)

This page shows an overview of all containers enabled for migration, and their synchronization status. It also allows data to be exported to a variety of formats for reporting on the progress of the migration.

info

NOTE: Additional columns are available if the Advanced view is enabled (under the Views tab) though this makes the user interface slower if there are a large number of mappings.

The following basic information about each container is visible in the grid view:

·Full Name

·Group

·Routed

·Exported

·Retryable Errors

·Permanent Errors

·Total Errors

·Exported Percentage

·Imported

·Retryable Errors

·Permanent Errors

·Total Errors

·Imported Percentage

·Priority

·Item Gathering Enabled

·Migration Enabled

·Stage 2 Enabled

·Stage 2 Finished

·Failed Item Threshold

·Ignore Failed Item Threshold

·Needs Provisioning

Actions to be performed on the Migration Status page

These actions can be performed on this page:

·Set Threshold: Sets the failed item threshold for the selected mapping or mappings

·Retry Failed Items: Retry any failed items

info

NOTE: A hanging export or import means that it has been running for more than 1 hour.

Retrying permanently failed items will reset the error count for those items and retry them.

info

NOTE: Retrying failed items from the UI (failed items page/stage 1 page) will work only for mappings where:

·stage 2 is not enabled or is enabled but not finished

·stage 2 is enabled and Workflow Policy has command WaitForImportFinished running (stating 'success' or 'skipped')

If Workflow Policy doesn't have this command, then only the first rule applies.

·Re-export Items: Items can be re-exported. It is possible to re-export all items, just those that failed to export or just those that failed to import.

·Enable Stage 2: Switch the selected container(s) to the target

·Add to Group: One or more containers can be added to an existing or new group. This group membership can then be used for filtering and batching of users for migration.

·Set Priority: Allow the migration priority to be set

·View Mappings Health: Switches to a status page which can be used to check mappings.  See the section in this document called ‘Mappings Health’ for more information.

·Comment: Set a comment of up to 256 characters on one or multiple mappings.

·Refresh: Refreshes the tables data

·Columns: Allows the selection of additional data columns, which might then be used to select groups of containers

·Reset: Resets the grid to the default columns, and removes any filters

·Load: Loads a saved filter/page-layout

·Save: Saves the current filter/page-layout

·Export to PDF, XLS, XLSX, CSV: Allow data to be exported to several formats

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation