This section explains what the requirements are for migrating from Dell Archive Manager (DAM)/Quest Archive Manager (QAM) to a target environment, and then covers the basic steps that should be followed to start such a migration.
Stage 1 - Synch
The first task which has to be performed is the discovery of archives in DAM. One or more of these archives are mapped and enabled for migration, Archive Shuttle Core sends a command to collect all needed metadata information from each archive. The results are reported back to Archive Shuttle Core to allow item level tracking and auditing.
The DAM module and chosen target environment import module then start to process the items from the archives. This runs continuously in the background until the administrator initiates Stage 2 ('Switch') for the archive.
Stage 2 - Switch
DAM to Exchange or Office 365
DAM to PST
Requirements
The following is a list of requirements.
Requirement |
Description |
---|---|
Modules installed on source |
The DAM/QAM module should be installed on an appropriate server. |
Modules installed on target |
The appropriate modules should be installed on each appropriate target server involved in the migration. |
AD Collector module installed |
An AD Collector module should be installed so that it can collect user-level information for the migration project. |
Staging Area created |
One or more staging areas should be setup, of an appropriate size and should be excluded from virus scanners. |
Workflows reviewed |
The Stage 2 workflows should be reviewed, and if necessary, customized to meet the needs of the project. |
Apply appropriate failed item threshold |
It is best practice to find an appropriate failed item threshold for the project/customer and apply that at the links level. This way all mappings which are created will inherit this value. |
Basic steps
The following are the basic steps to start this type of migration.
Step |
Screen |
Description |
---|---|---|
Enable Modules |
Modules |
All Archive Shuttle modules must be enabled, and optionally a schedule for them defined. It is important to verify that none of the modules have a red background (this indicates that Archive Shuttle Core has not had contact with the module) and that the module versions are as expected. |
Enable Domains |
Active Directory |
Select and enable one or more domains for synchronization. |
Configure Dell Archive Manager Environment |
Dell Archive Manager Environment |
Add a new Dell Archive Manager environment, specifying the following: ·Module to associate with this link ·Display name to use for this link ·SQL Server Name ·SQL Database Name Finally indicate that you want to Create Item Database, an Enable Archive Collection. The Link SQL Server should be set to the server where the Archive ShuttleItem databases are hosted. |
Assign Post Processing module to DAM Link |
Links |
Select the newly created link, and map a Shortcut Process Module to it. |
Map Modules to Target Link |
Links |
Ensure that the link for the migration target is added, and modules associated with it. |
Add Staging Area |
Links |
Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of vault stores being used as the source for the migration, the high water mark can be adjusted upwards. |
Map one or more containers |
Manual Mapping/Bulk Mapping |
One or more containers can now be mapped and migration can begin. It is often easiest to use a filter on the bulk mapping screen to show only DAM as a source. |
Determining DAM archive owner(s)
When the Dell Archive Manager (DAM) module sends results of DellArchiveManager collection to the core, the user is assigned to an archive based on LegacyMailboxDN.
First, Archive Shuttle looks into the [ExchangeMailbox] table in the Archive Shuttle Directory DB for the particular ExchangeLegacyDn. If no record is found, then it looks in the [UserProxyAddress] table.
The steps are:
Step 1
SELECT * FROM [User]
INNER JOIN ExchangeMailbox ON [User].UserSid = ExchangeMailbox.OwnerUserSid
WHERE ExchangeMailbox.LegacyExchangeDN = '{SourceDN}' -- SourceDN -> ExchangeLegacyDN from source DB (DAM DB)
If a user is found, theyre assigned to the archive. If no user is found, Step 2 below runs.
Step 2
SELECT * FROM [User]
INNER JOIN UserProxyAddress ON [User].UserSid = UserProxyAddress.UserSid
WHERE UserProxyAddress.[Address] = '{SourceDN}' -- SourceDN -> ExchangeLegacyDN from source DB (DAM DB)
If a user is found, the user is assigned to the archive.
If the user record is not found, then the archive is considered ownerless. Archive Shuttle is not able to pair the DAM archive with a user, which exists in the Archive Shuttle Directory database.
If you need to troubleshoot why a user is not assigned to the DAM archive, it might be worth to know which columns/values are fetched when DellArchiveManager collection is completed by Archive Shuttle.
Archive Shuttle fetches the following columns/values from the [MailBox] table from Dell Archive Manager DB:
1.MailboxID
2.Name
3.MailBoxType
4.ActiveDirectoryExchangeLegacyDN
Data in the [ExchangeMailbox] table and the [UserProxyAddress] table in Archive Shuttle Directory DB is collected by the Active Directory Collector module.
First, Archive Shuttle looks into the [ExchangeMailbox] table in Archive Shuttle Directory DB for particular ExchangeLegacyDn and if no record is found, then it looks also in [UserProxyAddress] table.
If no record/ExchangeLegacyDn is found in the [ExchangeMailbox] table and the [UserProxyAddress] table Archive Shuttle is not able to pair the DAM archive with a user that exists in Archive Shuttle Directory DB.
Value ActiveDirectoryExchangeLegacyDN in the [MailBox] table in the Dell Archive Manager DB should also be available in the [ExchangeMailbox] table or the [UserProxyAddress] table in Archive Shuttle Directory DB to be able to pair the DAM archive with some user that exists in Archive Shuttle Directory DB.
General considerations
The following general considerations should be taken into account for this type of migration:
·Ensure Shortcut Processing is configured to use EWS.
This section outlines the the steps to migrate a single test DAM to any supported target environment.
|
NOTE: The steps are specific to migrating to PST, but the steps are largely the same when migrating from DAM to any supported target environment. |
Prerequisites
It is essential that the following steps have been completed prior to beginning the migration:
·All Modules are enabled.
·Appropriate Active Directory Domains have been enabled for scanning.
·The PST target links should be configured with a specific staging area, and with modules associated to the link.
·The PST Rollover Threshold should be configured to an appropriate value.
·The PST Filename policy should be defined.
Add a DAM environment
To use DAM as a source for migration, a DAM Environment needs to be added, and configured as follows:
1.Go to the DAM Environment page (Configuration -> Dell Archive Manager Environment).
2.Click Add.
3.Enter the details required to connect to the DAM Environment
Map modules to link
The newly added DAM Environment will be added as a Link to the Links page, but modules may still need to be associated with it. This can be achieved as follows:
1.Go to Configuration > Links.
2.Select the DAM Link which was created previously.
3.Click on Map Modules and check and assign the modules on the link.
Map containers - for the test archive
In order to migrate a test DAM archive to PST file, the source and target containers must be mapped. This can be done as follows:
1.Navigate to the Bulk Mapping page.
2.Change the filter for Type so it is set to DAM. This will show all the discovered DAM archives.
3.Locate the archive you wish to use to test the migration, and select it.
4.With the container still selected, click Add Mappings from the navigation bar.
|
NOTE: A short wizard will start, which gathers information relating to the mapping for the select archive. (Multiple archives can also be selected) |
5.On the Target Container Type screen, select PST, and click [Next].
6.On the Choose a format screen, select PST, and then click Next.
7.On the Choose Target Link screen, choose the appropriate PST link.
8.On the Workflow Policy screen, select the Dell Archive Manager to PST option, and click [Next].
9.On the Filter Policy screen, select the Default (No Filter) option, and click [Next].
10.On the Container Mapping Settings screen, select Enabled for both Migration Status and Item Gathering Status, and click [Next].
11.Review the summary screen before clicking [Confirm].
Review Stage 1 Status
A few minutes after the mapping has been created, the program will instruct the appropriate modules to start the actions defined in the mapping. The progress for this stage of the migration can be reviewed by doing the following:
1.Go to the Stage 1 (Sync Data) page.
2.Type the beginning of the archive name in the Name filter. Click the Apply button at the right of the filter row.
3.Once the source archive is displayed, click Refresh from time to time to show the progress of the export of the archive and the ingesting of the data into the target Archive. Continue to click Refresh until both export and import are 100%.
Validate exported data
If there is a large amount of data to export and import, you can view the progress bars for the Stage 1 (Sync Data) move by clicking Refresh from the navigation bar on the Stage 1 (Sync Data) page of the user interface.
In addition, you can use Windows Explorer to browse the export/import storage area data on the disk.
Enable Stage 2
Before enabling Stage 2, the switch, for the test archive, the Stage 1 (Sync Data) page should be checked for issues such as failed item-export or item-import.
To enable Stage 2 for the test archive, perform the following steps:
1.Navigate to the Stage 1 (Sync Data) page.
2.Select the checkbox next to the test archive, and then click Enable Stage 2 in the navigation bar.
3.When the Stage 1 (Sync Data) page is refreshed, there should be a green and white check mark in the Stage 2 Enabled column.
Stage 2 is the switchover to the target environment. A final synchronization is performed of archived items from the source environment to the temporary PST file, before several additional migration tasks are performed.
After a few minutes, the progress of the test archive migration will be visible in the Stage 2 Status page, as follows:
1.Navigate to the Stage 2 (Switch User) page.
2.Type the beginning of the archive name in the Name filter. Click the Apply button at the right of the filter row.
|
NOTE: If the archive is not displayed, wait one to two minutes and click Refresh in the navigation bar. |
3.Once the source archive is displayed, you can click Refresh from time to time to show the progress of the final stages of the archive migration. By default, since the workflow policy that was selected was Dell Archive Manager to PST, the following steps will be performed:
Disable archiving in DAM
a)Import the remaining items in to the target.
b)Close the PST file.
c)Rename the PST file, according to the file name policy.
a)Delete the shortcuts from the mailbox.
Verify data has migrated
Once all of the Stage 2 operations have been completed the Stage 2 (Sync Data) for the test archive will have a green and white check mark in the Finished column.
The PST file can that was created can then be attached to Outlook and reviewed to ensure that the data was successfully migrated.
This section explains the requirements for migrating from SourceOne or EmailXtender to another environment, and then covers the basic steps that should be followed to start such a migration.
Stage 1 - Synch
The first task which has to be performed is the discovery of archives in SourceOne. One or more of these archives are mapped and enabled for migration, Archive Shuttle Core sends a command to collect all needed metadata information from each archive. The results are reported back to Archive Shuttle Core to allow item level tracking and auditing.
The SourceOne module and chosen target environment import module then start to process the items from the archives. This runs continuously in the background until the administrator initiates Stage 2 ('Switch') for the archive.
Stage 2 - Switch
SourceOne to Exchange or Office 365
SourceOne to PST
Requirements
The following is a list of requirements.
Requirement |
Description |
---|---|
Modules installed on source |
The SourceOne module should be installed on an appropriate source server. |
Modules installed on target |
The appropriate modules should be installed on each appropriate target server involved in the migration. |
AD Collector module installed |
An AD Collector module should be installed so that it can collect user-level information for the migration project. |
Staging Area created |
One or more staging areas should be setup, of an appropriate size and should be excluded from virus scanners. |
Workflows reviewed |
The Stage 2 workflows should be reviewed, and if necessary, customized to meet the needs of the project. |
Apply appropriate failed item threshold |
It is best practice to find an appropriate failed item threshold for the project/customer and apply that at the links level. This way all mappings which are created will inherit this value. |
Basic steps
The following are the basic steps to start this type of migration.
Step |
Screen |
Description |
---|---|---|
Enable Modules |
Modules |
All Archive Shuttle modules must be enabled, and a schedule for them defined if necessary. It is important to verify that none of the modules have a red background (indicating that the Archive Shuttle Core has not had contact with the module), and that the module versions are as expected. |
Enable Domains |
Active Directory |
Select and enable one or more domains for synchronization. Note: Configuration of EmailXtender is done in the same way as SourceOne. |
Configure SourceOne Environment |
SourceOne Environment |
Add a new SourceOne environment, specifying the following: ·Module to associate with this link ·Display name to use for this link ·SourceOne Basepaths (These are the share paths for each archive folder. Multiple paths should be semicolon separated.) ·SourceOne/EMX SQL server A Link Database will be created for this environment. It is possible to override the SQL Server and instance, if required. |
Enable Organization |
SourceOne Environment |
The module will scan for organizations and present them in a list. The required organizations should be enabled so that the module can scan for archives. |
Map Modules to Target Link |
Links |
Ensure that the link for the migration target is added, and modules associated with it. |
Map Modules to Source Link |
Links |
Ensure that the source links have a Shortcut Processing module assigned to them. This module will scan mailboxes to find shortcuts. This is required before the import can begin. |
Add Staging Area |
Links |
Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of archive folders being used as the source for the migration, the high water mark can be adjusted upwards. |
Configure Folder-less folder name |
System Configuration |
SourceOne does not maintain folder information for items. Therefore, a folder will be created to migrate items into. The name of this folder can be specified under Folder name for folder-less items on the General System Settings Page. The module scans for shortcuts in a mailbox and any items which have a shortcut will be migrated to the current folder where that shortcut resides. |
Map one or more containers |
Manual Mapping/Bulk Mapping |
One or more containers can now be mapped and migration can begin. It is often easiest to use a filter on the bulk mapping screen to show only SourceOne as a source. |
Determining SourceOne archive owner(s)
Archive Shuttle follows steps below to assign an owner to SourceOne archive:
1. If there is still an Exchange on-premises mailbox, then Archive Shuttle matches it with EmailAddress in dbo.SourceOneArchive table and LegacyExchangeDN in dbo.ExchangeMailbox table and UserSID in dbo.User
2. If there is only an Office 365 mailbox, then Archive Shuttle tries to match owner with SourceOne archive using Address in dbo.UserProxyAddress and EmailAddress in dbo.SourceOneArchive
·dbo.ExchangeMailbox and dbo.UserProxyAddress table are populated during the Azure Directory sync.
·dbo.SourceOneArchive archive is populated during the archive collection.
General considerations
The following general considerations should be taken into account for this type of migration.
·If you need to migrate the primary S1 archive into a primary mailbox, and a secondary S1 archive into a personal archive (in Exchange or Office 365), then two mappings will be required.
·It is recommended to add the following index to the SQL databases relating to S1. It will improve the item collection process: CREATE NONCLUSTERED INDEX [QT_IX_Route_EmailId] ON [dbo].[Route] ([EmailId] ASC) INCLUDE ([MessageID], [RouteMask], [PartitionId])
·It is recommended to add the following index to the SQL databases relating to EmailXtender. It will improve the item collection process: CREATE NONCLUSTERED INDEX [QT_IX_Route_EmailId] ON [dbo].[Route] ([EmailId] ASC) INCLUDE ([MD5HashKey], [TimeStamp])
·Disabling source archives is currently not available as part of a Workflow Policy and will need to be done manually post migration.
·You may find that items exported from these sources are not placed in the folder it originated from. For more information on this, click here.
The following filters are not supported:
·ArchivedDate
·RetentionCategory
·HasLegalHold
This section outlines the steps to migrate a single test SourceOne archive to PST. The same steps can be used to migrate from EmailXtender.
|
NOTE: The steps are largely the same when migrating from SourceOne to any supported target environment. |
Prerequisites
It is essential that the following steps have been completed prior to beginning the migration:
·All Modules are enabled.
·Appropriate Active Directory Domains have been enabled for scanning.
·The PST target links are configured with a specific staging area, and with modules associated to the link.
·The PST Rollover Threshold is configured to an appropriate value.
·The PST Filename policy is defined.
·The Shortcut Process Module must be installed, regardless if shortcuts are being used.
Add a SourceOne Environment
To use SourceOne as a source for migration, a SourceOne Environment needs to be added, and configured as follows:
1.Go to the SourceOne Environment page (Configuration -> SourceOne Environment)
2.Click Add.
3.Enter the details required to connect to the SourceOne Environment
Map Modules to Links
The newly added SourceOne Environment will be added as a Link to the Links page, but modules may still need to be associated with it. This can be achieved as follows:
1.Go to the Links page (Configuration -> Links).
2.Select the SourceOne Link which was created previously.
3.Click Map Modules and check and assign the modules on the link.
Map containers - for the test archive
To migrate a test SourceOne archive to PST file, the source and target containers must be mapped. This can be done as follows:
1.Navigate to the Bulk Mapping page.
2.Change the filter for Type, so it is set to SourceOne. This will show all the discovered SourceOne archives.
3.Locate the archive you wish to use to test the migration, and select it.
4.With the container still selected, click Add Mappings from the navigation bar.
|
NOTE: A short wizard will start, which gathers information relating to the mapping for the select archive. (Multiple archives can also be selected) |
5.On the Target Container Type screen, select PST, and click [Next].
6.On the Choose a format screen, select PST, and then click [Next].
7.On the Choose Target Link screen, choose the appropriate PST link.
8.On the Workflow Policy screen, select the SourceOne to PST option, and click [Next].
9.On the Filter Policy screen, select the Default (No Filter) option, and click Next.
10.On the Container Mapping Settings screen, select Enabled for both Migration Status and Item Gathering Status, and click on Next.
11.Review the summary screen before clicking Confirm.
Review Stage 1 Status
A few minutes after the mapping has been created, the program will instruct the appropriate modules to start the actions defined in the mapping. The progress for this stage of the migration can be reviewed by doing the following:
1.Go to the Stage 1 (Sync Data) page.
2.Type the beginning of the archive name in the Name filter. Click the Apply button at the right of the filter row.
3.Once the source archive is displayed, click Refresh from time to time to show the progress of the export of the archive and the ingesting of the data into the target Archive. Continue to click Refresh until both export and import are 100%.
If further data is added to the source archive, it will be synchronized every 24 hours to the target archive via the connection made with the mapping performed in the previous section. In addition, part of the Stage 2 Workflow is to perform a final synch. Therefore, its not necessary to ensure that export and import has reached 100% before moving on to the next steps.
Validate exported data
If there is a large amount of data to export and import, you can view the progress bars for the Stage 1 (Sync Data) move by clicking Refresh from the navigation bar on the Stage 1 (Sync Data) page of the user interface.
In addition, you can use Windows Explorer to browse the export/import storage area data on the disk.
Also at this time it will be possible to login to Outlook or Outlook Web Access as the test user. The migrated data will be present in the Personal Archive, and can be freely opened and manipulated.
|
NOTE: If the test user previously used the Personal Archive feature, it might be difficult to locate the migrated data. Because of this, Archive Shuttle recommends that the test user has an empty personal archive before migration. |
Enable Stage 2 Status
Before enabling Stage 2, the switch, for the test archive, the Stage 1 (Sync Data) page should be checked for issues such as failed item-export or item-import.
To enable Stage 2 for the test archive, perform the following steps:
1.Navigate to the Stage 1 (Sync Data) page.
2.Select the checkbox next to the test archive, and then click Enable Stage 2 in the navigation bar.
3.When the Stage 1 (Sync Data) page is refreshed, there should be a green and white check mark in the Stage 2 Enabled column.
Stage 2 is the switchover to the target environment. A final synchronization is performed of archived items from the source environment to the temporary PST file, before several additional migration tasks are performed.
Review Stage 2 Status
After a few minutes, the progress of the test archive migration will be visible in the Stage 2 Status page, as follows:
1.Navigate to the Stage 2 (Switch User) page.
2.Type the beginning of the archive name in the Name filter. Click the Apply button at the right of the filter row.
|
NOTE: If the archive is not displayed, wait one to two minutes and click Refresh in the navigation bar |
Once the source archive is displayed, you can click Refresh from time to time to show the progress of the final stages of the archive migration. By default, since the workflow policy that was selected was PST to Exchange/Office 365 (without archive deletion), the following steps will be performed:
a)Export any remaining items from the PST file
b)Import the remaining items in to the target
Verify data has been migrated
Once all of the Stage 2 operations have been completed the Stage 2 (Sync Data) for the test archive will have a green and white check mark in the Finished column.
In addition, if Outlook or Outlook Web Access is used to access the test mailbox then all of the archived items will be in the Personal Archive, and no Enterprise Vault shortcuts will remain in the source mailbox.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center