• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 381
  • Last Modified:

EXCHANGE 2010, EXCHANGE 2013

can we make public folders part of DAG in exchange 2010

also how many mailbox servers or databases we can transfer  at one time if migrating from exchange 2010 to exchange 2013
0
pramod1
Asked:
pramod1
1 Solution
 
MASTechnical Department HeadCommented:
-->can we make public folders part of DAG in exchange 2010
No

-->how many mailbox servers or databases we can transfer  at one time if migrating from exchange 2010 to exchange 2013
You are moving mailboxes not databases. Create database in exchange2013 move all together. It will get queued and finish based on server availability/performance
0
 
Adam FarageEnterprise ArchCommented:
can we make public folders part of DAG in exchange 2010

Nope. Not possible, as PF have there own replication mechanism

also how many mailbox servers or databases we can transfer  at one time if migrating from exchange 2010 to exchange 2013

Going to Exchange 2013, you would use what is called "Batch Moves". This basically is a set of mailboxes set to move at the same time, but by default Exchange 2013 will only the following:

- 5 MRS (mailbox replication service) move threads per target (where you are moving it too) server
- 2 MRS threads per active database you are moving too (meaning if you are moving all to a single database, you can only have 2 moves going at the same time to that database. You then have an additional 3 move threads you can use for another mailbox database)


The other moves within the batch will actually be in the "pending" state until a new MRS thread is available. You can also edit these move settings on the Exchange 2010 CAS and the 2013 CAS / Mailbox ( http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html )

More about batch moves: http://technet.microsoft.com/en-us/library/jj150543%28v=exchg.150%29.aspx
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now