The Performance Dashboard provides information about the migrations being performed on an hour by hour basis. The screen allows an administrator to select information relating to:
·The last day
·The last week
·The last month
·A custom time frame
Information about the migration is then displayed in a tabular format as follows:
Item |
Description |
---|---|
Hour |
Date/Time |
Exported Count |
Number of items exported |
Exported Size |
Size of all data exported |
Imported Count |
Number of items imported |
Imported Size |
Size of all data imported |
It is also possible to view the information on a per-link basis, and each set of data is also displayed as a graph at the right hand side of the page.
Optionally, you can configure the pages widgets to display compressed sizes.
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 |
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.
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 page shows an overview of any per-item failures that Archive Shuttle has encountered during the migration. When the screen is first entered a particular link should be chosen from the drop down list. This will filter the Failed Items screen to show only items relating to that link.
The following basic information about each failure is logged in the grid view:
·Container Mapping ID: The Archive Shuttle ID for the container mapping reference only
·Item Routing ID: The Archive Shuttle ID for the item which has failed reference only
·Is Exported Failed?: An indicator field to show whether it is an export failure
·Is Import Failed?: An indicator field to show whether it is an import failure
·Is Failed?: An indicator field to show whether it is concerned that the error is permanent (e.g., file not found on exporting an item)
·Item Routing Error Count: The current error count for the item
·Error Text: The error which was reported to Archive Shuttle from the underlying module, or from Exchange/Enterprise Vault
·Last Date Time UTC: The last date/time where this was reported by Archive Shuttle
·In FTP: An indicator to show whether the item was uploaded to the Quadrotech FTP Server.
·Download Link: A hyperlink to the failed item.
The Failed Items page also allows an administrator to submit failed items for reprocessing. This is achieved by selecting one or more items and selecting the button on the Actions Bar. It is also possible to reprocess all failed items. When reprocessing is selected, this will have the effect of resubmitting the item to the appropriate module. For example, if the issue is that the item could not be exported, then that item will be resubmitted to the export module. Likewise, if the issue is that the item could not be ingested into Office 365, then the item will be resubmitted to the Office 365 module.
NOTES: ·Reprocessing failed items will reset the Item Routing Error Count for those items. ·As of Archive Shuttle 9.5, FTP settings (URL, username, password) are no longer hardcoded for the ExportFailedItemsToFTP command and use the settings from System Configuration. ·As of Archive Shuttle 10.4, there is also the ability to permanently fail permanently fail certain export or import failures to other sources after the first attempt. |
This action of reprocessing failed items can take a few minutes before the appropriate modules receive the command, perform the action, and feedback the results.
An additional option on the Failed Items screen is to Move Selected Items. This is specifically for the situations where items have failed to be imported to the target, and never can be. By selecting one of more of these items, they can be moved from the staging area to a different area specified on the target link (via an option on the Links Page).
NOTE: Permanently failed items might include items which are too large to be ingested into the target (e.g., in an EV to Exchange migration where message size limits are in place). |
In the case of a missing setting for an operation, a notification will be shown.
Archive Shuttle has a reliance on a performant SQL Server in order to achieve high throughput of items during migration. If SQL is struggling to handle the load, performance will drop. The Index Fragmentation page shows some key metrics about the SQL Indices associated with each link database. These can get fragmented over time during the Enterprise Vault Collection and export/import processes. The information on the index fragmentation page is updated hourly.
The screen highlights tables/indices that are of particular concern according to this:
Row Highlighting |
Reason |
---|---|
No highlighting |
Fragmentation is not significant, or the number of pages in the index is not over 1000. |
Yellow |
Fragmentation is between 10 and 30 % and the page count in the index is more than 1000. |
Red |
Fragmentation is over 30 % and the page count in the index is more than 1000. Accessing data associated with this table/index will not be performant. |
The recommended actions to take are as follows:
Row Highlighting |
Action |
---|---|
No highlighting |
No action required |
Yellow |
Perform an Index Reorganization |
Red |
Perform an Index Rebuild |
More information specific to SQL Server and management of the Archive Shuttle databases can be found in the Quadrotech Archive Shuttle SQL Best Practices Guide.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center