ITEXVN

  A while back i wrote a post about data deduplication in 2012…. generally a very good feature, but as that specific post talked about, there was a collection of .iso and compressed data where not only did dedup not save me anything, it actually used up more space in the dedup folder than the orginal data size (which i found a little odd) Today i got around to doing something about this and found Disabling data deduplication (via GUI or powershell) only stops further deduplication from occuring – but data that has already been deduplicated will remain deduplicated In order to “move” (re-hydrate ?) the data back to the original files and out of the deduplication store, use the powershell command  start-dedupjob -Volume <VolumeLetter> -Type Unoptimization You can check the status on where this is at by using  get-dedupjob , or, i like using TreeSize which shows the size on disk of specific files…. including the deduplication chunks At this stage – i noticed the o...

 Move by command (Allow large data loss) New-MoveRequest -Identity UserID -AcceptLargeDataLoss -BadItemLimit 200 -TargetDatabase DB-MB-EX03 -ArchiveTargetDatabase DB-Archive-EX03

 Fatal error MapiExceptionNotFound has occurred. Error details: MapiExceptionNotFound: Unable to synchronize manifest. (hr=0x8004010f, ec=-2147221233) This error will appear due to mailbox corruption to eliminate the above error need repair the mailbox  execute the following shell command then clear the move request and initiate again move request   New-MailboxRepairRequest -Mailbox userID -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView

  Prerequisites An RDB must be created. The database and log files containing the recovered data must be restored or copied into the RDB folder structure that was created when the RDB was created. The database must be in a clean shutdown state. Because an RDB is an alternate restore location for all databases, all restored databases will be in a dirty shutdown state. You can use Eseutil /R to put the database in a clean shutdown state. (Text copied from technet) Step 1 Start up DPM 2010 and go to the Recovery section, select the appropriate database, also make sure to select a date very the user mailbox should be recovered from. Right click the database and select “Recover”. Check so that the date and time are correct and press “Next”. Select “copy to network folder” and select “Next”. Copy destination, select the appropriate server and folder press “Next”. On the next selection window we got a very nice option to select, it’s called “Bring the database to a clean state after copyi...

  Optimize Storage In Windows To Optimize the Storage in Windows Server 2012, 2012 R2, 2016 and 2019 Windows PowerShell cmdlet is available. It provides the ability to manually perform actions like TRIM, Defragment, etc. TRIM – The parameter is  ReTrim  which generates TRIM and Unmap hints for all currently unused sectors of a volume. Defrag – The parameter defrag/L performs the same TRIM (-ReTrim) as the Optimize-Storage PowerShell cmdlet

TỔNG HỢP CÁC VẤN ĐỀ QUANH ARCHIVE DATABASE LỆNH KIỂM TRA (XÁC ĐỊNH GUID) MAILBOX BỊ DISCONNECT VỚI ARCHIVE DATABASE Get-MailboxDatabase "xxx" | Get-MailboxStatistics | Where {($_.DisconnectDate -ne $null) -and ($_.IsArchiveMailbox -eq $true)} | Format-List LỆNH RE-CONNECT LẠI ARCHIVE MAILBOX SAU KHI DISABLE MAILBOX CHÍNH Enable-mailbox -identity <Name> -ArchiveGUID <GUID of archived Mailbox> -ArchiveDatabase <DB Name> -Archive Nếu lệnh trên không hoạt động thì làm thêm lệnh connect-mailbox: Connect-Mailbox -Identity "8734c04e-981e-4ccf-a547-1c1ac7ebf3e2" -Archive -User "Chris Ashton" -Database "DB01" Nếu báo lỗi mismatch Legacy DN thì thực hiện tiếp hướng dẫn bên dưới RE-CONNECT BỊ LỖI MISMATCH LEGACY DN Dùng ADSIEDIT để đổi lại LegacyDN cho khớp với DN trước đó Start à Run à adsiedit.msc à ADSI à Connect to à Domain Naming Context à Navigate to users location à  Properties of the account à here you can see the legacyExchangeDN ...

  Cách khắc phục: Tạo 1 mailbox database mới và move mailbox bị lỗi qua database mới đó ActiveSync Fails to Deliver E-Mail to Phones after Database Repair – Event ID 1008 We ran into an issue where an exchange server was down due to a full VM crash. We had to restore the server from a backup. After the backup was all up and running emails started flowing again. However, we also were notified that people were no longer receiving emails on their mobile devices. We also noticed that what started to happen were critical and error events to the application log.  While most appeared to be transient and would likely cure themselves – they did – one did not.  Event ID 1008.  Here is an excerpt from the description: Description: An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the ...