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

Quadrotech Archive Shuttle 10.3 - Administration Guide

EV Import Issues

EV Imports not working

If Archive Shuttle is unable to import data into Enterprise Vault, the following steps and information will help Support investigate the issue.

General Information

·EV version

·Location of the EV Import Module (is it on an EV Server)

·Archive Shuttle Core version

·Archive Shuttle modules version

Steps to follow

Is it all items for all mappings? Yes/No. If yes, go to step 1, if no, go to step 2.

 

Step 1

1.Check that the retention categories are mapped.

a.Unmapped categories can be seen on the System Health page

b.This is required for intra or inter site migrations

c.Take a screenshot of the Retention Category mappings

2.Check that the EV Import modules are scheduled

a.This is on the Modules page

b.Take a screenshot of the schedule

3.Check that the EV Import module is enabled, and the Core is able to communicate with it

a.The module should not show as ‘red’ on the Modules page

b.Take a screenshot of the Modules page

4.Check that the link containing the target vault store has an Import Module which is mapped

a.This is on the Links Page

b.Take a screenshot, and highlight the link

 

Step 2

Is it some items for all mappings? Yes/No. If yes, continue with this step, if no, go to step 3.

1.Check the disk space is not exhausted

a.Collect a screenshot

2.Check that the exported-but-not-imported figure has not exceeded 100%

a.Take a screenshot of the System Health page

3.Review any errors on the Failed Items screen

a.Take a screenshot of the errors

 

Step 3

Did the import start, and then just stop? Yes/No. If yes, continue with this step, if no go to step 4.

1.Check that the module doesn’t have a scheduled defined

a.This is on the modules page

b.Take a screenshot of the schedule

2.Check the System Health page to ensure the target vault store/link is not in backup mode

a.Take a screenshot of the System Health Page

3.Check the ‘Index Incomplete’ values on the System Health page

a.Take a screenshot of the System Health Page

4.Check the disk space is not exhausted

a.Collect a screenshot

5.Check that the exported-but-not-imported figure has not exceeded 100%

a.Take a screenshot of the System Health page

6.Review any errors on the Failed Items screen

a.Take a screenshot of the errors

 

Step 4

1.Gather logs:

a.Ensure that the module is configured for TRACE level logging

b.This is done on the modules page

c.Reprocess the item(s) or click on ‘Failed Imports’, or click on ‘Hanging Imports’

d.Wait one to five minutes

e.Generate a ‘Support Bundle’ for review by Support.

EV Collector Issues

EV Collector not working

If Archive Shuttle is unable to collect data from Enterprise Vault, the following steps and information will help Support investigate the issue:

General Information

·EV version

·Location of the EV Collector Module (is it on an EV Server?)

·Archive Shuttle Core version

·Archive Shuttle modules version

·Mailbox Archive Item collection or Journal Archive Item collection

o Verifying the type of EV Collector Module

 

Steps to follow

Is it all items for all mappings?  Yes/No. If Yes, go to step 1, if no, go to step 2.

Step 1

1.Check modules are associated with the links

a.Some links may not have had any modules configured for them

b.Collect a screenshot

2.Check the modules are enabled

a.This is on the ‘Modules’ page

b.Collect a screenshot

3.Check the modules are scheduled appropriately

a.This is on the ‘Modules’ page

b.Collect a screenshot

4.Check the Link database is created for the Source Link

a.Source Link should have a Link database created

b.Collect a screenshot

5.Check the EV vaults stores are collected

a.All vault stores should be showed on EV Environments screen

b.Collect a screenshot

 

Step 2

Is it some items for all mappings?   Yes/No.  If Yes continue with this step, if No go to Step 3.

1.Check if all Mappings are showing on Stage 1 and Existing Mapping screens

a.Include the source and target link name column

b.Collect a screenshot

2.Try re-collecting the items

a.Trigger the item collection from Existing mapping screen

b.Check the log files for the collection

c.Are there any errors? Yes/No

3.Check the license has not expired

a.Take a screenshot of the license page. Note: The license is month/day/year format.

 

Step 3

Did Collection start, and then just stop? Yes/No.  If Yes, continue with this step.

1.Check that the module doesn’t have a scheduled defined

a.This is on the ‘Modules’ page

b.Collect a screenshot

 

Step 4

1.Gather logs

a.Ensure that the module is configured for TRACE level logging

b.This is done on the Modules page

c.Reprocess the item(s), or click on ‘Failed Exports’, or click on ‘Hanging Exports’

d.Wait one to five minutes

e.Generate a ‘Support Bundle‘ for review by Support (Ensure each Collector Module is selected in the Bundle)

Office 365 Import Issues

Office 365 Imports not working

If Archive Shuttle is unable to import data into Office365, the following steps and information will help Support investigate the issue:

General Information

·Location of the Office365 Module (is it on the Archive Shuttle Core Server)

·Archive Shuttle Core version

·Archive Shuttle modules version

Steps to follow

Are all mappings affected? Yes/No. If yes, go to step 1, if no, go to step 2.

Step 1

1.Check that the Office365 modules are scheduled

a.This is on the Modules page

b.Take a screenshot of the schedule

2.Check that the Office365 module is enabled, and the Core is able to communicate with it

a.The module should not show as ‘red’ on the Modules page

b.Take a screenshot of the Modules page

3.Check that the Office365 link has the Office365 module mapped

a.This is on the Links Page

b.Take a screenshot, and highlight the link

4.Check that the link has the same staging area as where the export was performed to

a.This is on the Links page

b.Take a screenshot, and highlight the link

5.Check that the Office365 Credentials Editor has been provided Admin Credentials

a.You can see this in the Office365 Credentials Editor on the Server where the module is installed

b.Take a screenshot of the Credentials Editor

6.Check that the Office365 Service Accounts have been granted the Application Impersonation role:

a.You can see this PowerShell. More information is available in this article.

b.Take a screenshot of the role assignment.

7.Review errors on the Failed Items screen

a.If the autodiscover service couldn’t be located, you will have to change that setting in the module.exe.config.

 

Step 2

Is it some items for all mappings? Yes/No. If yes, continue with this step, if no, go to step 3.

1.Check the storage quota is not exhausted

a.Take a screenshot of the mailbox properties

2.Check that the exported-but-not-imported figure has not exceeded 100%

a.Take a screenshot of the System Health page

3.Review any errors on the Failed Items screen

a.Take a screenshot of the errors

 

Step 3

Did the import start, and then just stop? Yes/No. If yes, continue with this step, if no go to step 4.

1.Check that the module doesn’t have a schedule defined

a.This is on the modules page

b.Take a screenshot of the schedule

2.Check the storage quota is not exhausted

a.Take a screenshot of the mailbox properties

3.Check that the exported-but-not-imported figure has not exceeded 100%

a.Take a screenshot of the System Health page

4.Review any errors on the Failed Items screen

a.Take a screenshot of the errors

 

Step 4

1.Gather logs:

a.Ensure that the module is configured for TRACE level logging

b.This is done on the modules page

c.Reprocess the item(s) or click on ‘Failed Imports’, or click on ‘Hanging Imports’

d.Wait one to five minutes

e.Generate a ‘Support Bundle’ for review by Support

Exchange Import Issues

Exchange Imports not working

If Archive Shuttle is unable to import data into Exchange, the following steps and information will help Support investigate the issue:

General Information

·Exchange Version information

·Location of the Exchange Import Module (is it on the Archive Shuttle Core Server)

·Archive Shuttle Core version

·Archive Shuttle modules version

·Outlook version

Steps to follow

Is it all items for all mappings? Yes/No. If yes, go to step 1, if no, go to step 2

Step 1

1.Check that the Exchange Import modules are scheduled.

a.This is on the Modules page

b.Take a screenshot of the schedule

2.Check that the Exchange Import module is enabled, and the Core is able to communicate with it.

a.The module should not show as red on the Modules page

b.Take a screenshot of the Modules page

3.Check that the link containing the target Exchange Information store has an Exchange Import Module that is mapped.

a.This is on the Links page

b.Take a screenshot, and highlight the link

4.Check that the link has the same staging area as the export was performed to.

a.This is on the Links page

b.Take a screenshot, and highlight the link

5.Check the version of Outlook that is installed where the module is located.

a.Ensure that the default profile is configured for an account that has full control on all mailboxes

b.Ensure that the default profile is configured to launch straight into Outlook, and that it is an online profile

 

Step 2

Is it all items for all mappings? Yes/No. If yes, go to step 1, if no, go to step 2.

1.Check that the disk space is not exhausted.

a.Collect a screenshot

2.Check that the exported-but-not-imported figure has not exceeded 100%.

a.Take a screenshot of the System Health page

3.Review any errors on the Failed Items page.

a.Take a screenshot of the errors

4.Check that EWS Impersonation has been configured.

a.This is a setting in the module’s .exe.config file.

 

Step 3

Did the import start, and then just stop? Yes/No. If yes, continue with this step, if no go to step 4

1.Check that the module doesn’t have a schedule defined.

a.This is on the modules page

b.Take a screenshot of the schedule

2.Check the disk space is not exhausted.

a.Collect a screenshot

3.Check that the exported-but-not-imported figure has not exceeded 100%.

a.Take a screenshot of the System Health page

4.Review any errors on the Failed Items page.

a.Take a screenshot of the errors

5.Check that EWS Impersonation has been configured.

a.This is a setting in the modules .exe.config file.

 

Step 4

1.Gather logs:

a.Ensure that the module is configured for TRACE level logging

b.This is done on the modules page

c.Reprocess the item(s) or click on ‘Failed Imports’, or click on ‘Hanging Imports’

d.Wait 1-5 minutes

e.Generate a ‘Support Bundle’ for review by Support.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation