Trying the PST import method. Honestly, it isn't much better.
Have a 3.28 GB PST upload to Office365 already. Started the import at 2:03. It is now 6 hours later and it is only 59% done. So this seems like it might even be SLOWER than the other way.
WTH, Microsoft. Why do you make it so hard to switch to your product?
@jaredbusch said in Potential Office365 (Exchange Online) Throttling Issue:
Outlook has always had this with size, if not message count. but if they match you should be good I would assume.
They never match exactly, though, which is the issue.
You can change Outlook to display the number of items, but that is also very manual as you have to do it for every folder.
I basically randomly write down folders, and check through them. I figure if 20 out of 40 are correct, they all should be.
I think Exchange must calculate storage differently than MDaemon and the PST. Not surprising. Maybe it compresses it by default.
I've never actually administered Exchange, so don't know.
@jaredbusch said
Or right click properties and check the file count and stuff?
Eh? You mean folder size in properties?
I wish Outlook and OWA had a way to easily display the number of messages in a folder. MDaemon has an option to show (X/Y) for each folder where x is unread and Y is total. It makes it so much easier to compare.
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
@dbeato said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
You uploaded a file that was .6 MB
How is it going, I didn't even know you had a thread on this and I told you the same thing about PST
It ended up taking about 70 minutes, but it completed. Now I have to look at the file and compare folders and see if everything copied over, especially since the PST file sizes were reported as different.
Was that the test upload or the 20Gb file
The test upload.
I am checking through it now ... it seems to have worked.
I got thrown off by the stupid filter setting Outlook has ... had to go through the folders and de-select that, but it seems to have gotten them all.
@dbeato said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
You uploaded a file that was .6 MB
How is it going, I didn't even know you had a thread on this and I told you the same thing about PST
It ended up taking about 70 minutes, but it completed. Now I have to look at the file and compare folders and see if everything copied over, especially since the PST file sizes were reported as different.
@dashrender said in Potential Office365 (Exchange Online) Throttling Issue:
You uploaded a file that was .6 MB and now MS is telling you it's 550 MB? damn, that's some expansion.
647K KB (647,000 KB) is .6 MB?
@scottalanmiller said
So basically, no one knows how to submit this request internally.
Considering the latest update is .. that after talking to the next level up, it turns out this CANNOT be done, except possibly for large migrations. (Which makes no sense, so is probably not true.)
I would actually update this to no one over there knows what they are doing, actually.
They recommended going with the PST upload, which I am testing now.
I uploaded a 647K KB PST file to the system. It said it would import it, though it only said it was 550MB. So I am wondering if it is some sort of compression thing, some sort of PST vs. message storage thing, or just a mess up on their end.
Once the file was uploaded, I hit IMPORT. That was at 3:02. It's now 3:38 and this is what I see. I wonder if this is going to be a typical Microsoft update. Stay at 0% for an hour then say it is done.
@scottalanmiller said in Potential Office365 (Exchange Online) Throttling Issue:
So basically, no one knows how to submit this request internally.
Uh, yeah, that would be a good way of saying that.
@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...
@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...
@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 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.
Fedora, Fedora...
Did @scottalanmiller hijack this thread?
@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.
@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.
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 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.
@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.
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.
@scottalanmiller said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
They keep telling me they can turn this throttling off temporarily, but then the next sentence is always "but this is normal behavior" so who knows what to believe.
Those aren't conflicting statements in any way.
Well, that is true.
I guess what I meant was ... I get the feeling that is a preface to "hey what we did didn't work, but too bad"
