Problems with Exchange 2013

Aleksandar Babakov 41 Reputation points
2021-03-28T19:37:32.223+00:00

Hi folks, I know that, this is an old story, but I have one problematic Exchange Server 2013 SP1.
This server is pre CU5, and I can not upgrade to CU23. Even if a make restart to this server, I have very big problems, making it to work. As long as it up and running, we can not eve breath on it.
I can not even start any migration to Exchange 2016/2019, until I have at least CU18. It have around 500 mailboxes and successful backup on mailboxes (with DPM 2016) and probably System state. It can not run Bare metal backup.

I can not avoid this issue, so I have to do something, so I was thinking about two scenarios:

Scenario 1:

  • I think to install new Server 2012 R2 with Exchange 2013 SP1 CU23 (to highest update). To create new Databases and start live migrating mailboxes to new server. I'm not planning to crate DAG.
  • While I'm migrating the mailboxes, can those two Exchange server communicate which other?
  • Do I need to create some send/receive connector between them?
  • What about the mailboxes migrated on the new Exchange, are the users will be able to send and receive mails?
  • What about Outlooks, are going to be able to automatically find there mailboxes, on second Exchange?

After migrating all mailboxes, I will redirect mail traffic to second Exchange and dismantle first one.
Than, after I have working Exchange, I will proceed with upgrade to Exchange 2019.

Scenario 2:

  1. To install new Server 2012 R2,
  2. To disable network adapter on existing Exchange 2013,
  3. To install Exchange 2013 CU23 in restore/repair mode, on new Server 2012 R2,
  4. To create same disk and partition, as the existing one and restore DB from backup
  5. What if this doesn't work? Can I simply shut down new Exchange and re-enable network adapter on old one?
  6. It will crate a problems to entire Domain infrastructure?

This will crate unknown downtime...

Please if any has experience with this kind of situation?

Best regards,
Aleksandar

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,787 questions
0 comments No comments
{count} votes

Accepted answer
  1. Joyce Shen - MSFT 16,686 Reputation points
    2021-03-29T02:40:50.207+00:00

    Hi @Aleksandar Babakov

    I would recommend scenario 1 you mentioned above.

    Serveral ways can meet your requirement like below

    1. Standing up a new 2013 server, move mailboxes.
    2. Creating a DAG, add 2nd server, seed DB's, make DB's active on new server, remove DB's from first server, decommission first server. (You could ignore this since you don't want to create DAG)

    If you choose scenario 1 to 'replace' your old server, this article should be helpful to you: Performing a Like for Like Exchange Server Migration, it introduces about some details we need to pay attention to (contains your concerns above) .

    Mainly steps list

    1.Install the new Exchange server
    2.Configure the new Exchange server

    • Client access (Outlook, OWA, mobile devices, etc)
    • Transport (mail flow)
    • Mailbox databases

    3.Migrate data and services to the new Exchange server

    • Client access
    • Transport services
    • Mailboxes

    4.Decommission the old server


    If an Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
     

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Aleksandar Babakov 41 Reputation points
    2021-03-30T07:33:34.13+00:00

    Thank you joyceshen-MSFT.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.