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...