This article contains a list of changes to the current version of Archive Shuttle 10.0 versus the original release of Archive Shuttle 10.0.
|Original release of Archive Shuttle 10.0|
|10.0.40428.1||42e8c83d||Made fabric icons load offline.|
|10.0.40253.1||600138d9||UI – about popUp – changed link for technical support|
|10.0.40253.1||cbd1317b||Changed product link|
|10.0.40260.1||7c4cc060||WaitForImportFinished – fixed issue with processing archives with 0 items|
|10.0.40265.1||2ed6ff02||Existing mappings page – properly display green tick for column Stage 2 enabled|
|10.0.40265.1||c47a67be||Added condition for stage 2 finished when getting eligible stage 2 commands for execution (GetReadyContainerMappings)|
|10.0.40268.1||91f45889||Fixed calculation of LastChunk for collection of items from PST.|
|10.0.40268.1||c1e931c5||Added missing DevExpress.Data.Desktop.v20.1.dll to Core installer|
|10.0.40286.2||f5c3a6c5||Created Get-ASArchive PS command.|
|10.0.40286.2||565bece6||Fixed problem with not showing P&P stats for QAM.|
|10.0.40288.1||3c2751ee||Enhanced export speed for S1.|
|10.0.40293.1||a0d731c6||Fixed problem with not showing P&P stats for QAM.|
|10.0.40288.1||3c2751ee||Enhanced export speed for S1.|
|10.0.40293.1||a0d731c6||Implemented missing move of failed items from PermanentlyFailed.pst functionality during reprocess of items.|
|10.0.40297.1||2736a33f||Implemented All switch in Get-ASStage2Status PS command|
|10.0.40297.1||fc39d8d4||Always get items from CORE for RestoreForeignShortcut|
|10.0.40297.1||304e678f||Enhanced collection of items for S1 to deal with wrong email addresses stored in S1 DB.|
|10.0.40307.1||7127bf3d||Fixed wrong casting for auto Stage 2 switch command|
|10.0.40307.1||aabb42d0||Fixed issue with WaitForImportFinish command and Stage2 automatic switch|
|10.0.40307.1||603efd72||Adjusted PStRouting to ignore stats for not valid SubContainers.|
|10.0.40309.2||64e1dac0||Process EV folder icons – added DATABASE_DEFAULT collation for varchar join columns on temp table (fixed collation conflict)|
|10.0.40309.2||1a4a5692||Adjusted WaitForImportFinished command logic to count also failed items to notExported/notImported checks|
|10.0.40317.1||186e16ad||Get item to retry prior move from permFailed.pst in case of retry action executed from Stage1.|
|10.0.40317.1||3e89ffe7||Check only permFailed error during CheckImportCompleted command execution.|
|10.0.40323.1||a635aaad||Added additional log to show count of skipped S1 archives per batch while processing collected archive results.|
|10.0.40323.2||8c684e10||Introduced retry functionality to S1SyncArchives command in case of deadlock victim error.|
|10.0.40328.1||6e401667||Changed UncPath column type on table PstFile|
|10.0.40328.1||bcf2bf37||Reset DbUpgrade process in DB in case of start of AS.Core service|
|10.0.40328.1||e843817e||MEtalogix: Remove hardcoded MamExch DB string from collect archives query.|
|10.0.40332.1||1318e5ac||Added possibility to define DB schema for Metalogix environment.|
|10.0.40336.1||5bf3c7a2||Changed UseEws Property to nullable while processing of coolected archives.|
|10.0.40337.1||4a6c910f||Retry hanging items after 12 hours by default instead of 1.|
|10.0.40343.1||4f43762e||Fixed issue with flawed filtering in selective migration GetToExportBySenderRecipientMapping function|
|10.0.40343.1||5c2dc05b||Extend logs for SenderRecipient collection + fix issue with parsing SenderRecipientType enum|
|10.0.40346.1||1369d94e||Adjusted logs for SenderRecipient Collection.|
|10.0.40346.2||bc0476cb||Stop to check filtered items count for sub mappings during AutoEnableStage2.|
|10.0.40349.1||6d357834||Adjusted o365 mailbox creation validation to support just (_, -, ‘, .) special chars.|
|10.0.40351.1||11e3be3e||EV Export: FetchItem without DETAIL_LEVEL_ARCHIVE_METADATA property in case of “One of Id or CustomIdentifier or SequenceNum must be set” error.|
|10.0.40351.1||6f843896||Adjustments to code and logs while processing of senderRecipients.|
|10.0.40351.2||db156259||Reduced amount of logs generated while exporting from EV.|
|10.0.40352.1||0e909c2e||Adjusted ResetTimeouts for SenderRecipient collection.|
|10.0.40357.1||f5839c3c||EVExport: Introduced fallback mechanism in case of “one of id or customidentifier or sequencenum must be set” error.|
Due to exclusive file locks on the PST file or message being imported, one of the following errors may occur:
- The process cannot access the file
Consecutive attempts at processing the file should be successful. There is a known issue with Outlook 2013 used with the Native Format Import module. More information is available here.
Ticket ID: 5969 & 5654
When customizing Stage 2 Workflows, it should be noted that DisableMailbox and DisableOrphanedArchive are mutually exclusive. This means that only one of those should be present in the workflow. If both are included then unpredictable results will be observed with some commands appearing to ‘hang’ during Stage 2.
The dates relating to oldest and youngest item in archive can vary from what is eventually collected from the item-level metadata in the source archive. This is because the data comes from different databases tables in the source environment. More details in the knowledge base article
Office 365 hold types
As of 1st July 2017, Microsoft is changing the way that legal holds can be used in Office 365. Archive Shuttle currently allows the usage of one, or the other, or both of these types of hold:
- Litigation Hold
- In-place hold
From 1st July it is required to use the legal hold type called ‘Litigation Hold’. More information is available in this Microsoft article.
The ‘In-place hold’ will be removed from a future version of the product.
Migrations involving folders with leading and trailing spaces.
This issue affects only Enterprise Vault migrations (to any supported target). All versions of Enterprise Vault are affected. A known issue in Enterprise Vault means that leading and trailing spaces in folder names are not provided to Archive Shuttle by the Enterprise Vault API. This can result in mis-named folders in the target environment. Veritas is aware of this issue, but there are no current plans to fix the issue.
Note: Confer with Microsoft to determine whether the terms of your licensing agreement are impacted by the legal hold feature.