Potential Office365 (Exchange Online) Throttling Issue
-
I might also try IMAP migration, which a couple people have suggested. IMAP migration has a throttle as well, but the expected throughput is 14-20GB an hour, which would be perfect for me. (The current scenario is .5 GB per hour.)
Honestly, the way I was doing it was working so well, I didn't see a need to do anything else.
-
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
I used IMAP to download the messages to a new profile with no issue.
What file format did you download to? You can still create a non-exchange profile and import to a PST file, then upload that to Azure using AzCopy.
Also for $10 or $12 you can use IMAP to 365 with BitTitan Migrationwiz which you may find much simpler, since its only this single mailbox.
I will admit MigrationWiz is much simpler and it does multiple passes. Just gets expensive when you have hundreds of mailboxes.
-
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
I might also try IMAP migration
The IMAP tool I have found leaves out data, the MigrationWiz IMAP migration is probably worth the few dollars for the single large mailbox. Just to save you another headache. The Microsoft tools has missed large date ranges of data for me in the past. MIgrationwiz has always come through for me.
-
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
I might also try IMAP migration
The IMAP tool I have found leaves out data, the MigrationWiz IMAP migration is probably worth the few dollars for the single large mailbox. Just to save you another headache. The Microsoft tools has missed large date ranges of data for me in the past. MIgrationwiz has always come through for me.
That was my fear.
My users have all these weird folder structures and whatnot. Was really afraid the MS IMAP migration tool would louse things up. And TBH, it would mean I would have to go through folder by folder to ensure everything is there, both the folder itself and the number of messages in it.
I will give the other one a try.
-
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
What file format did you download to? You can still create a non-exchange profile and import to a PST file, then upload that to Azure using AzCopy.
Since I had issues with the MDaemon connector tool, I set up a VM, and set up a new Outlook profile. I then add in the existing IMAP account, and download everything. (THe new versions of Outlook download the entire mailbox.)
Once that is done, I add the O365 account, and just drag things over.
-
If they would just open the pipe up for a few days for me, this would be so simple.
They said they can, but I am not confident they know what they are talking about since they both said they did it to no avail.
-
@bigbear said
BitTitan Migrationwiz which you may find much simpler, since its only this single mailbox.
I wonder what "class" they consider MigrationWiz.
Because "third party Exchange migrations" (and they list BitTitan in this group) are also crippled at .5GB an hour if you notice.
-
We used to just use a Ruby script for IMAP transfers, worked really well.
-
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
If they would just open the pipe up for a few days for me, this would be so simple.
BTW are you using Outlook 2016? Just curious because of PST file limits in older versions.
I have always just setup the new user, run a migrationwiz pass for the last 2 weeks, contacts, calendar etc, let the user into their new 365 mailbox then started the full pass migration. This is what MS refers to as a "dial tone" migration. Then I run another pass a couple weeks later before shutting down the old server or services.
I would imagine the upload limits to be DoS Security best practices of some sort.
-
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
If they would just open the pipe up for a few days for me, this would be so simple.
BTW are you using Outlook 2016? Just curious because of PST file limits in older versions.
I have always just setup the new user, run a migrationwiz pass for the last 2 weeks, contacts, calendar etc, let the user into their new 365 mailbox then started the full pass migration. This is what MS refers to as a "dial tone" migration. Then I run another pass a couple weeks later before shutting down the old server or services.
I would imagine the upload limits to be DoS Security best practices of some sort.
How long does the actual migration take? The actual file copy, I mean.
In theory, if what I am doing works, it's not the end of the world if I do it on their actual machine.
It's the fact I staged it that is causing the problem.
-
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
How long does the actual migration take?
If you are talking about Outlook import I have never seen one complete over 15GB. Left one out there for 2 weeks.
If you are talking about Migrationwiz its all server to server and doesn't affect the user. You could manually import the last few weeks and all contact, setup their new Outlook and let the import run overnight. Outlook should only be caching 90 days or so of email anyway.
Are you going to configure an archiving policy?
-
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
If you are talking about Outlook import I have never seen one complete over 15GB. Left one out there for 2 weeks.
Shhhhhhhh! It's working its way through nicely. Just slooooowwwwww.
If you are talking about Migrationwiz its all server to server and doesn't affect the user. You could manually import the last few weeks and all contact, setup their new Outlook and let the import run overnight. Outlook should only be caching 90 days or so of email anyway.
Right, but according to that link, MS throttles 3rd party migrations to .1 to .3 GB per hour. So it would take forever, not overnight. You've seen large mailboxes import using Migrationwiz overnight?
Are you going to configure an archiving policy?
You mean to filter messages into the in-place archive?
No.
-
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
Right, but according to that link, MS throttles 3rd party migrations to .1 to .3 GB per hour.
We always open a ticket to request a temp lift on EWSLimits. I believe this has already been lifted for you per your comment above, but per my comment I don't believe the support guys know what you are talking about. And the EWS limits being increased has never made an Outlook import for a large mailbox go faster or finish for me. But will be interesting to see if it does for you. I just wouldnt bet my lunch on it.
-
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
Right, but according to that link, MS throttles 3rd party migrations to .1 to .3 GB per hour.
We always open a ticket to request a temp lift on EWSLimits. I believe this has already been lifted for you per your comment above, but per my comment I don't believe the support guys know what you are talking about. And the EWS limits being increased has never made an Outlook import for a large mailbox go faster or finish for me. But will be interesting to see if it does for you. I just wouldnt bet my lunch on it.
How long does that take to go into effect once you request it?
-
@bigbear said
And the EWS limits being increased has never made an Outlook import for a large mailbox go faster or finish for me. But will be interesting to see if it does for you. I just wouldnt bet my lunch on it.
So you are saying you saw the same thing as me .. they said the took off the throttling, but nothing actually changes...
-
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
Right, but according to that link, MS throttles 3rd party migrations to .1 to .3 GB per hour.
We always open a ticket to request a temp lift on EWSLimits. I believe this has already been lifted for you per your comment above, but per my comment I don't believe the support guys know what you are talking about. And the EWS limits being increased has never made an Outlook import for a large mailbox go faster or finish for me. But will be interesting to see if it does for you. I just wouldnt bet my lunch on it.
How long does that take to go into effect once you request it?
We always do it a week or so in advance and they give you 90 days. As we are discussing this I am curious as to whether you could run powershell command Get-ThrottlingPolicy to see if its working on EWS...
-
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
@bigbear said
And the EWS limits being increased has never made an Outlook import for a large mailbox go faster or finish for me. But will be interesting to see if it does for you. I just wouldnt bet my lunch on it.
So you are saying you saw the same thing as me .. they said the took off the throttling, but nothing actually changes...
They dont remove throttling but they increase the limits per your specific, kindly worded request
You would want to ask for throttling limits to be increased for 60 or 90 days in a new ticket and we always include these details (which came from MigrationWiz I think)
I always ask for xx (number of users) to be set for concurrent migration as well in the ticket.
EwsCutoffBalance = Unlimited
EwsMaxSubscriptions = xx
EwsMaxBurst = Unlimited
EwsMaxConcurrency = xx
EwsRechargeRate = UnlimitedAnd it did not seem to help Outlook import on a specific 15GB mailbox I recall, I had a dozen larger ones that also needed to complete so I moved on to MigrationWiz on that particular project.
-
A side note, per MigrationWiz support docs, you can no longer use Get-ThrottlingPolicy powershell commands against EWS/365
I had never thought of trying it before now... -
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
A side note, per MigrationWiz support docs, you can no longer use Get-ThrottlingPolicy powershell commands against EWS/365
I had never thought of trying it before now...Yeah I noticed that when I first starting Googling for this issue.
I spoke to the tech again just now. He said that his original request was for 15 days. And then a second tech asked for 30 days. He said they are very finicky about this, and he thought maybe going to 2 days would work, so he is going to try that, and also speak to the next level guys.
He did say we can use the PST option, and it seems to always be reliable. But that if they can get this throttle turned off temporarily, that THAT would be the best method.
Updates to come...
-
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
A side note, per MigrationWiz support docs, you can no longer use Get-ThrottlingPolicy powershell commands against EWS/365
I had never thought of trying it before now...Yeah I noticed that when I first starting Googling for this issue.
I spoke to the tech again just now. He said that his original request was for 15 days. And then a second tech asked for 30 days. He said they are very finicky about this, and he thought maybe going to 2 days would work, so he is going to try that, and also speak to the next level guys.
He did say we can use the PST option, and it seems to always be reliable. But that if they can get this throttle turned off temporarily, that THAT would be the best method.
Updates to come...
So basically, no one knows how to submit this request internally.
