Home

MigrationPermanentException

%3CLINGO-SUB%20id%3D%22lingo-sub-195786%22%20slang%3D%22en-US%22%3EMigrationPermanentException%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-195786%22%20slang%3D%22en-US%22%3E%3CP%3Ewe%20are%20in%20Hybrid%20environment%20while%20doing%20the%20migration%20from%20cloud%20to%20on-premises%20its%20shows%20as%20as%20below%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EError%3A%3C%2FSPAN%3E%20%3CSPAN%3EMigrationPermanentException%3A%20Mailbox%20dumpster%20size%2036.46%20GB%20%E2%80%8E(39%2C153%2C389%2C259%20bytes)%E2%80%8E%20exceeds%20target%20quota%2030%20GB%20%E2%80%8E(32%2C212%2C254%2C720%20bytes)%E2%80%8E.%20--%26gt%3B%20Mailbox%20dumpster%20size%2036.46%20GB%20%E2%80%8E(39%2C153%2C389%2C259%20bytes)%E2%80%8E%20exceeds%20target%20quota%2030%20GB%20%E2%80%8E(32%2C212%2C254%2C720%20bytes)%E2%80%8E.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ei%20have%20checked%20my%20on-premises%20database%20Storage%20Lmits%20as%20per%20my%20knowledge%20it%20was%20not%20issues%20with%20storage%20limits%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI'm%20Attaching%20the%20Storage%20Limit%20snap%20short%2C%20please%20check%20and%20let%20me%20know%20may%20be%20something%20wrong%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-195786%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMigration%20issue%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-195868%22%20slang%3D%22en-US%22%3ERe%3A%20MigrationPermanentException%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-195868%22%20slang%3D%22en-US%22%3E%3CP%3E30%20GB%20is%20the%20default%20dumpster%20quota%20in%20O365%2C%20hence%20the%20issue.%20According%20to%20this%20article%20by%20a%20Microsoft%20engineer%2C%20you%20should%20license%20the%20corresponding%20mail%20user%20object%20to%20work%20around%20this%3A%20%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fexovoice%2F2017%2F03%2F23%2Fmailboxes-not-being-migrated-to-exchange-online-because-their-sizes-exceed-the-mailbox-target-quota-of-50gb%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fexovoice%2F2017%2F03%2F23%2Fmailboxes-not-being-migrated-to-exchange-online-because-their-sizes-exceed-the-mailbox-target-quota-of-50gb%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOr%20just%20open%20a%20support%20case%20and%20ask%20them%20to%20adjust%20the%20default%20RecoverableItemsQuota%20value.%3C%2FP%3E%3C%2FLINGO-BODY%3E
raju narumanchi
Occasional Visitor

we are in Hybrid environment while doing the migration from cloud to on-premises its shows as as below    

Error: MigrationPermanentException: Mailbox dumpster size 36.46 GB ‎(39,153,389,259 bytes)‎ exceeds target quota 30 GB ‎(32,212,254,720 bytes)‎. --> Mailbox dumpster size 36.46 GB ‎(39,153,389,259 bytes)‎ exceeds target quota 30 GB ‎(32,212,254,720 bytes)‎.

 

i have checked my on-premises database Storage Lmits as per my knowledge it was not issues with storage limits 

 

I'm Attaching the Storage Limit snap short, please check and let me know may be something wrong 

 

  

1 Reply

30 GB is the default dumpster quota in O365, hence the issue. According to this article by a Microsoft engineer, you should license the corresponding mail user object to work around this: https://blogs.technet.microsoft.com/exovoice/2017/03/23/mailboxes-not-being-migrated-to-exchange-onl...

 

Or just open a support case and ask them to adjust the default RecoverableItemsQuota value.

Related Conversations