O365 throttling

Thanks for the reply, I'm still a bit confused.

I have under a 1000 users so it says "Microsoft will not provide increases to the default throttles, so service requests should not be submitted."

In regards to the PowerShell max connections part - I have one machine only so does that mean that the powershell setting should be 9?

I also dont get the Admin Pooling bit.

I would appreciate any more help if possible.

thanks

Ok Admin pooling. 

One admin account migrating 10 mailboxes at the same time is NOT admin pooling. 

10 Admin accounts migrating 10 mailboxes at the same time is Admin Pooling and also less likely to be throttled. 

PowerShell connections

MFNE using a single thread of the batch to process administrative tasks using powershell. So the default PS throttle settings will be more then enough. 

Thanks Jeff.

So my understanding then is that there is nothing I can do?

I have one MFNE server with one admin account and Quest is at the default configs.

I am seeing huge latency when migrating a MB, eg, 5Gb took over 20 hours - starting at around 3.5 items per hour and quickly dropping back to under 1000 an hour. Is this me being throttled by MS?

Thanks

raj kumar_72431 said:

So my understanding then is that there is nothing I can do?

No, I am saying you can use an Admin pool. That works around throttling by using separate admin accounts for each mailbox in the collection. 
If you had 12 mailbox in your collection, and 12 Admin accounts and you were using 12 threads, each mailbox would be migrating using their own admin account concurrently.

The first part of the mailbox migration is slow as the calendar items are translated from Notes entries to Outlook entries. This is a one to many translations due to how notes can do things and how exchange does things. So this is really slow. Once that part of the migration is over, the throughput picks up. Running a pass for 1 mailbox is roughtly what you will see for 10-12 mailboxes. If you have 500MB has hour at the end of the process, you will see 10-12 times that at the end of the process. 

There are known error messages for MAPI throttling. Based on what you just disclosed, you are not hitting throttling limits, you are just seeing the exppected performance of calendar translations. 

Hello Raj,

Thanks for posting to the Migrator for Notes to Exchange (MNE) forum. I understand you have questions about getting the best performance when migrating to Office 365. As Jeff mentioned above, the answer lies in the MNE Admin Pool feature. When migrating to Office 365 with MNE, the migration admin account is performing the heavy lifting and is limited to 500MB per hour. The MNE Admin Pool feature allows you to create additional migration admin "worker" accounts so that each user being migrated in a collection is using its own migration admin (worker) account to get to the 500MB per hour limit for each user (thread) being migrated.

One Admin Pool account should be created for each thread that will be used across all MNE migration server simultaneously. For example, if you have five MNE migration servers, each running ten threads at the same time, then you would need 50 Admin Pool accounts to achieve the best performance.

If you need additional clarity or assistance with the MNE Admin Pool feature, you may want to put in a Service Request with Support:

support.quest.com/create-service-request

Trevor Taegder
Senior Technical Support Engineer
Quest | Support

Hi, thanks for the help guys! I now know that I need to create an admin pool.

I'm having a problem doing that however,. This is what happens:

Place a tick in Use admin account pool

Click Manage

After a few coonection messages at the bottom of the window, I enter a password, place a tick in the Licence box

Choose a pool size of 3

Hit Apply

Few more connection messages at the bottom and then it just says:

Waiting 1 sec for creation of user "xxxxxx" to propagate (waited xx seconds)

this just continues to count up for hundreds to seconds and does not ever create any accounts.

Any idea what the issue could be?

Thanks

Hello Raj,

Thanks for the update. Have you installed the prerequisites from the Migrator for Notes to Exchange (MNE) Release Notes:

https://support.quest.com/technical-documents/migrator-for-notes-to-exchange/4.16/release-notes/3#TOPIC-1264138

Specifically under the "Also required for Office 365 target" section?

At this point, we may need to perform a deeper investigation of log files. In order to maintain confidentiality of your data, we would suggest creating a Service Request:

https://support.quest.com/create-service-request

Trevor Taegder
Senior Technical Support Engineer
Quest | Support

Hello Raj,

Thanks for the update. Have you installed the prerequisites from the Migrator for Notes to Exchange (MNE) Release Notes:

https://support.quest.com/technical-documents/migrator-for-notes-to-exchange/4.16/release-notes/3#TOPIC-1264138

Specifically under the "Also required for Office 365 target" section?

At this point, we may need to perform a deeper investigation of log files. In order to maintain confidentiality of your data, we would suggest creating a Service Request:

https://support.quest.com/create-service-request

Trevor Taegder
Senior Technical Support Engineer
Quest | Support

Hi Trevor, I managed to sort it out, I simply needed to run MNE as an admin!

One quick question - Now that I have configured Admin Pools (via the Exchange Server config screen), would I need to re-create any migration templates or would they automatically use the new admin pool?

Thanks

Hello Raj,

If you are using Migrator for Notes to Exchange (MNE), version 4.16.2 or later, then you should be using "Differential Templates", which would be updated with the new Admin Pool settings automatically. If you are using an older version of MNE, or upgraded from an older version and didn't select the option to upgrade to "Differential Templates", then you can use the steps below to change existing MNE Configuration Templates (or create new Configuration Templates):

1.) Open the MNE Migration Manager.
2.) Click on the menu button in the upper-right (3 lines)
3.) Enable "Advanced Wizard Settings".
4.) Click on Migrate User Data, select the Collection and click Migrate.
5.) Select the option to Modify the template.
6.) Click on the Edit button.
7.) Edit the parameter(s) as required.
8.) Continue through the wizard until you get to the screen to schedule the migration, which says "Now on this Computer" and click Cancel, which will allow the new configuration to be saved. Alternatively, you can actually start the migration if desired as well.

The new parameter is now saved in this template. If there are multiple templates for migrating user mail data, then they will need to be updated using the steps above.

If the new parameter is added to the MNE Global Default Settings, then it will be automatically be included for new templates created in the future.

Regards,

Trevor Taegder
Senior Technical Support Engineer
Quest | Support

Thanks Trevor - I'm using 4.16.0.44.

There is a bit in the wizard where it show it is using the Admin Pool so all good!

One other question - can the number of threads be changed during a migration or does it need to be set earlier? The reason I ask is that mine always start at 2 threads and then I manually have to change it to 10 after the copy process kicks off.

Thanks

Hello Raj,

Using the same steps as above to modify existing Configuration Templates, you can increase the threads by adjusting the parameter below, which should already be present in the settings file:

[General]
ThreadCnt=4

Or, you can certainly increase the thread counts after starting the migration as well.

Regards,

Trevor Taegder
Senior Technical Support Engineer
Quest | Support

Thanks for the great support Trevor.

Thanks Trevor.

I have one more issue:

When I do a migration of around 10 mailboxes, 6 or 7 fail to connect to the target mailbox and I end up having to wait for the successful ones to complete before trying the failed ones again. This happens every time. What is going on here?

The log file errors are:

ERROR: [4072-25-4-00000000]Unable to open target mail store 'xxxxxxxxx@xxxxxxx.com'.

or

09:26:16 ERROR: [7444-1-156-00000000]ADFWD::AddProxies (1): Processing 'xxxxxxx@xxxxxx.com'
09:26:16 Single object not found in AD.

Thanks

forgot to add - could this me a Microsoft replication problem? I always apply the full access permissions via a PowerShell script to all the newly created MBs at the same time so I can't understand how some of them are inaccessible?

This could be related to Office 365 propagation delay but I see you have an open Service Request. The engineer that picks this up will be able to better understand once they have a chance to review the logs.

Darin MacKenzie
Sr. Technical Product Specialist
Quest | Support

Thanks Darin - I think you are correct - I ran a migration this morning for 10 mailboxes - 3 were OK and 7 failed. I then ran the other 7 about 2 hours later and 5 were ok and 2 failed. I then ran the last two again an hour later and they finally migrated. This definitely proves its permissions propagation.