Quantcast
Channel: Exchange Server 2013 - Administration, Monitoring, and Performance 论坛
Viewing all articles
Browse latest Browse all 3457

Litigation Hold with Archive Mailboxes and Discovery Holds

$
0
0

Hi all

I have a customer that is moving to Exchange 2013 on prem from Exchange 2007.

They are wanting to use Archive mailboxes using Direct attached storage and 3 copies of the data and separate databases for primary mailboxes and archive mailboxes. They want to keep primary mailboxes lean and move items to the archive mailbox after 2 months. This will be implemented using retention policies. They also want to enable litigation hold on a good number of mailboxes.

Reading here it appears that there is a "Recoverable Items 14 days move to archive" default policy that should move items in the Recoverable Items folder into the archive mailbox. I assumed that this would be all Recoverable Items subfolders including DiscoveryHolds, reading the article.

During testing items that are deleted from the primary mailbox when a mailbox is on Litigation hold, stay in the DiscoveryHolds folder in primary mailbox and never seem to move to the Archive mailbox. I am using “Get-MailboxFolderStatistics -FolderScope RecoverableItems”  to view the items and sizes. Even after 18 days the items remain in the primary mailbox. Items deleted from the archive go to the DiscoveryHolds folder of recoverable items in the archive mailbox. I have tried forcing the managed folder assistant but that does not improve things

Can someone confirm how this actually works since the documentation says one thing but reality sems different. If deleted items from the primary mailbox remain in the primary mailbox then there seems little point in having archive mailboxes if litigation hold is in place. Otherwise the primary mailbox will end up having 7 years of deleted items in it as per the litigation hold duration .

Thanks





Viewing all articles
Browse latest Browse all 3457

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>