Skip Ribbon Commands
Skip to main content


This survey aims to gather information about specific tools in advance of the AORA EA2OHS workshop on Tools for EBM. 
Please enter the case name:
migration of recovery guide for users
Contact person  (name and email)
Reference to documentation. Please include references to method descriptions and links to reports of the application in management.
Performance factors and finest techniques
This section defines aspects that affect transfers utilizing the IMAP, cutover, or even presented transfer methods. It additionally recognizes ideal methods to boost movement performance.

Element 1: Information source
To-do list Summary Best practices
Body performanceData removal is actually a demanding job. The source unit requires to have enough information, like processor opportunity as well as mind, to give optimum transfer performance. During transfer, the source unit is actually usually close to total capacity in relations to the frequent end-user work. If system information are inadequate, the added workload that arises from migration can easily impact final user.
Screen body functionality during a captain movement exam. If the system is active, our company recommend staying clear of a threatening movement timetable for the certain body as a result of possible transfer slowness and company schedule concerns. If possible, boost the source system efficiency through including components resources and decrease the lots on the system through relocating activities and also users to various other web servers that aren't associated with the movement.

To learn more, view:
Swap 2013 Hosting Server Health and also Efficiency
Knowing Exchange 2010 Efficiency
Substitution 2007: Keeping Track Of Mailbox Servers

When shifting coming from an on-premises Substitution company where there are various mailbox hosting servers, our company advise that you develop a migration-user checklist that is actually evenly circulated all over a number of mail box servers. Based upon specific hosting server performance, the listing could be more fine-tuned to maximize throughput.

For example, if server A has 50 percent extra source schedule than server B, it proves out to have 50 percent even more individuals coming from web server A in the same migration set. Identical methods may be put on various other source systems. Perform migrations when servers possess maximum resource availability including after hrs or on weekend breaks and also holidays.

Back-end tasksOther back-end jobs that are operating throughout movement time. Because it is actually an absolute best process to do migration after business hrs, it's common that movements conflict with servicing tasks (including data back-up) running on your on-premises servers.Review various other device jobs that may be running throughout transfer. Our experts advise that you carry out records migration when not one other resource-intensive jobs are managing.
Note: For consumers utilizing on-premises Exchange, the usual back-end tasks are backup solutions as well as Substitution establishment routine maintenance.
Strangling policyIt's a common strategy to safeguard email units along with a strangling policy that sets a particular restriction on exactly how fast as well as the amount of data could be extracted from the system during the course of a specific volume of your time.
Validate what choking plan is actually released for your email system. For example, Google Email restricts the amount of records could be extracted in a particular period.

Depending upon the variation, Swap has plans that restrict IMAP accessibility to the on-premises email hosting server (made use of through IMAP movements) as well as RPC over HTTP Protocol gain access to (made use of by cutover Swap transfers and also presented Exchange migrations).

To check out the choking environments in a Swap 2013 institution, jog the Get-ThrottlingPolicy cmdlet. To read more, see Swap Amount of work Monitoring.

To read more regarding IMAP strangling, visit Move your IMAP mail boxes to Microsoft 365 or even Office 365

For additional information concerning RPC over HTTP Method choking, visit:
Substitution 2013 Work Monitoring
Swap 2010: Understanding Client Throttling Plans
Exchange 2007: Recognizing Customer Throttling

Element 2: System
Proof exams: Relying on the movement technique, you can easily attempt the observing proof tests:

IMAP migrations: Pre-populate a resource mail box along with sample records. Then from the web (outside your on-premises system), hook up to the source mail box by using a common IMAP email client including Microsoft Overview, and afterwards assess system efficiency through finding out how much time it needs to download and install all the data from the source mailbox. The throughput must resemble what clients may manage utilizing the IMAP transfer tool in Microsoft 365 or Office 365, dued to the fact that there are actually no other restraints.

Variable 3: Microsoft 365 and Office 365 company
Microsoft 365 or even Office 365 source health-based throttling affects transfers utilizing the native Microsoft 365 or Office 365 simple transfer resources. View the Microsoft 365 or even Office 365 resource health-based throttling area.;u=157172;area=summary;u=180729;u=12955*sh_/*sh_/*sh_/*sh_/*sh_/*sh_/;u=364681;area=summary;u=60074

Please provide a short description of the case, include a list of aims and the management options explored:
Please indicate the specific geographic location of the case: 12
If possible, please indicate the geographic extent of the case (e.g. km2) United States
Please indicate the name of the tool(s) used:
Shoviv tools
Please choose a category that best describes  the tool used in the case: Trait based and sized based modelling
Please describe the data required to use the tool:
Please shortly describe the strength of the tool(s) used in this case:
Please shortly describe the limitations of the tool(s) used in this case:
Please select the best description of how the tool(s) has been applied in management (to date): Operational
Please choose the type of application that best describes the tool:
(Please choose all that apply)
Tactical; Strategic
Please shortly describe any visualisations associated with the tool:
(E.g. graphs, infographics, videos)
Please shortly describe any strengths of the visualisations:
Please shortly describe any limitations of the use of visualisations in the case:
Please indicate how much time was spent with managers familiarising them with the tool before they started using it in management:
Could this tool be adopted for use in other areas? Please indicate how easy/hard this adaptation might be:
What data would be required to use the tool in a different case/area?
How much time would be required to adopt the tool for use in a new case?

Management success: The tool helped to achieve ecosystem targets.
  Strongly disagree Neutral Strongly agreeh 
Please indicate if you agree with the statement: 

Management success: The tool was accepted by the public.
  Strongly disagree Neutral Strongly agree
Please indicate if you agree with the statement: 

Management success: The tool was easy to implement.
  Strongly disagree Neutral Strongly agree
Please indicate if you agree with the statement: