Migration Workflow
Enterprise Vault to Enterprise Vault
Stage 1 – Synch
As soon as a user is enabled for migration, the synch process-flow shown above starts.
Archive Shuttle Core sends a command to collect all needed metadata information such as the number of items, size, and Enterprise Vault transaction ID’s for the archive of the user. The results are reported back to Archive Shuttle Core to allow item level tracking and auditing.
The Enterprise Vault Export and Enterprise Vault Ingest process is then started. It runs continuously in the background until the administrator initiates a “Switch” (stage 2) for the user or a specified “external” trigger is fired (e.g., the mailbox has been moved from Exchange 2003 to Exchange 2010)
Stage 2 – Switch
After the administrator has initiated a “Switch” (stage 2) to the target environment (per User), the Metadata Collector determines the gap between the source archive and the last imported items. Archive Shuttle then synchronizes the difference one last time to the target archive. The archive then gets assigned to the user and enabled. The last step is to cleanup shortcuts in the target mailbox.
Enterprise Vault to Exchange
Stage 1 – Synch
As soon as a user is enabled for migration, the synch process-flow shown above starts.
Archive Shuttle Core sends a command to collect all needed metadata information such as the number of items, size, and Enterprise Vault transaction ID’s for the archive of the user. The results are reported back to Archive Shuttle Core to allow item level tracking and auditing.
The Enterprise Vault Export and Exchange Ingest process is then started. It runs continuously in the background until the administrator initiates a “switch” (stage 2) for the user or a specified “external” trigger is fired (e.g., the mailbox has been moved from Exchange 2003 to Exchange 2010)
Stage 2 – Switch
After the administrator has initiated a “Switch” (stage 2) to the target environment, the Metadata Collector determines the gap between the source archive and the last imported item. Archive Shuttle then synchronizes the difference one last time to the target mailbox.
The last step is to cleanup shortcuts in the source mailbox by deleting them.
Enterprise Vault to Office 365
Stage 1 – Synch
As soon as a user is enabled for migration, the synch process-flow shown above starts.
Archive Shuttle Core sends a command to collect all needed metadata information such as the number of items, size, and Enterprise Vault transaction ID’s for the archive of the user. The results are reported back to Archive Shuttle Core to allow item level tracking and auditing.
The Enterprise Vault Export and Office 365 module then begin to work. This runs continuously in the background until the administrator initiates a “Switch” (stage 2).
Stage 2 – Switch
After the administrator has initiated a “Switch” (stage 2) to the target environment, the Metadata Collector determines the gap between the source archive and the last imported item. Archive Shuttle then synchronizes the difference one last time to the target mailbox.
The last step is to ‘Zap’ the mailbox to remove Enterprise Vault settings, cleanup shortcuts in the source mailbox by deleting them, and change any pending-archive items back to normal items.
Enterprise Vault to PST
Stage 1 – Synch
As soon as a user is enabled for migration, the synch process-flow shown above starts.
Archive Shuttle Core sends a command to collect all needed metadata information such as the number of items, size, and Enterprise Vault transaction ID’s for the archive of the user. The results are reported back to Archive Shuttle Core to allow item level tracking and auditing.
The Enterprise Vault Export and Native Format Import module then begin to work. This runs continuously in the background until the administrator initiates a “Switch” (stage 2).
PST files will be created by default of about 2 Gb in size. A lower size can be set in the UI if required
Stage 2 – Switch
After the administrator has initiated a “Switch” (stage 2) to the target environment, the Metadata Collector determines the gap between the source archive and the last imported item. Archive Shuttle then synchronizes the difference one last time to the target mailbox.
Archive Shuttle performs a ‘Zap’ of the mailbox to remove Enterprise Vault settings before closing the PST files and moving them to the PST Output Area. Finally, shortcuts are cleaned up in the source mailbox by deleting them, and any pending-archive items are changed back to normal items.
PST as a Source
Stage 1 – Synch
The first task which has to be performed is the discovery of the PSTs, followed by the assignment of those PSTs to target users.
Then when a PST is enabled for migration, the synch process-flow, shown above, starts.
Archive Shuttle Core sends a command to collect all needed metadata information from each PST file. The results are reported back to Archive ShuttleCore to allow item level tracking and auditing.
The PST Export and chosen target environment import module then start to process the items from the PSTs. This runs continuously in the background until the administrator initiates a ‘Switch’ (stage 2) for the arhcive.
Stage 2 – Switch
PST to Exchange or Office 365
PST to Enterprise Vault
After the administrator has initiated a “Switch” (stage 2) to the target, Archive Shuttle then synchronizes the difference one last time to the target environment. Depending on the target environment there then may be some additional steps (see the diagrams above).
EAS as a Source
Stage 1 – Synch
The first task which has to be performed is the discovery of archives in EAS. 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 ShuttleCore to allow item level tracking and auditing.
The EAS 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 a ‘Switch’ (stage 2) for the archive.
Stage 2 – Switch
EAS to Exchange or Office 365
EAS to PST
Metalogix as a Source
Stage 1 – Synch
The first task which has to be performed is the discovery of archives in Metalogix. 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 ShuttleCore to allow item level tracking and auditing.
The Metalogix 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 a ‘Switch’ (stage 2) for the archive.
Stage 2 – Switch
Metalogix to Exchange or Office 365
Metalogix to PST
Dell Archive Manager as a Source
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 ShuttleCore 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 a ‘Switch’ (stage 2) for the archive.
Stage 2 – Switch
DAM to Exchange or Office 365
DAM to PST
SourceOne as a Source
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 ShuttleCore 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 a ‘Switch’ (stage 2) for the archive.
Stage 2 – Switch
SourceOne to Exchange or Office 365
SourceOne to PST
