Permissions/access requirements for complex deployments
In complex environments crossing domains, organizations and forests, consideration must be given to the permissions / access requirements of the Archive Shuttle export and import modules that are required for the migration.
The basic requirement is that the Active Directory account that the export module runs under needs to be able to read/write to the storage location. In addition, the required import module also requires read/write access to the storage location.
|
|
NOTE: The export/import storage location is specified as a UNC. Hidden shares are supported. |
Sizing the PST output location
If Archive Shuttle is being used to extract data to PST files, the sizing of the PST Output location is important and should be carefully considered.
Consider the following options when sizing the storage area:
·It does not have to be locally attached storage to the Native Format Import Module. Network attached storage is supported.
·No data is written to the location until Stage 2 is activated for the chosen containers.
·Typically the space required for a PST file export of an archive will be almost double the size of the source archive.
|
|
NOTEs: ·PST files will be created by default of about 2 GB in size. A lower size can be set in the UI if required. ·The export item size estimate when importing using the Native Format Import module may be larger in the UI than the estimated size in the database. |
How to change folder translations
By going to System Configuration > General > Folder, you are able to add, remove and change the translation for new and existing folders.
Clicking on the Edit button brings up a pop-up menu, showing the list of labels of folders. Clicking one gives you a list of translations on the right pane.
You can edit the translations on the right hand pane by selecting one, or add a new translation by selecting the end of a translation and pressing Enter. You can edit as many folders as you wish, and once you are done, click Save, then Save in the top right. This is logged in the database dbo.MailboxFolderTranslation.
|
|
NOTES: ·Folder Translation is working only for Exchange 2013 and higher versions of Exchange mailboxes, as well as for Exchange Online mailboxes. ·Folder Translation is working only for root folders, not for split folders, therefore all split folders will use language of the source archive. |
Preserving the Chain of Custody
Archive Shuttle performs a number of operations in order to preserve and verify the Chain of Custody of data items during a migration. This section explains some of those which need to be taken into account in a migration.
Item level hashing
When an item is exported from a source environment. a hash is generated for that item and stored in the Archive Shuttle Item database. Sometime later, when the item is ingested, the hash is recomputed and compared with that stored value.
If the hashes do not match, a Chain of Custody violation is logged and the item will by default be re-exported and re-migrated.
|
|
NOTE: If a significant number of Chain of Custody alerts are reported, it is likely that anti virus is touching the files after they have been stored on the staging area. |
Migration-level hashing
As Archive Shuttle is performing the hashing on the items as mentioned in the previous section, a hash is generated on the whole message file, in order to avoid tampering during the migration.
Watermarks
When migrating from EV to EV Archive Shuttle adds a custom index entry to migrated item. This entry contains:
·Migration Time UTC
·Source Archive ID
·Source Transaction ID
·Archive Shuttle Version
When migrating from EV to Exchange, Archive Shuttle adds the same information to each migrated item as MAPI properties.
Retained databases
Following the migration, in case of Chain of Custody queries, you may consider retaining the Archive Shuttle SQL databases.