Moving Exchange 2010 database to another server is quite a difficult as well as complicated process. However, some manual methods and automated tool is discussed in the segment that will help to move Exchange 2010 mailbox database to another server.
Moving Exchange 2010 Mailbox using Portability Method
It is an effective method to move Exchange 2010 mailbox database to another server. Data Portability facilitate to easily restore any Exchange Server database to specified server. Database Portability method exists for entire Exchange Server editions like Exchange 2007, 2010, 2013, 2016 and 2019.
Before starting the migration of Exchange 2010 mailbox database, there are some facts that you need to know:
- One should have assigned Organization Management permissions to implement the process.
- EAC cannot be used to move Exchange user mailboxes to another recovered database using the portability method.
Steps to Move Exchange 2010 Mailbox to another Server
Step 1. Run Exchange Management Shell.
Step 2. Ensure that desired data you want to move should be in clean shutdown state. If it is not in the mentioned state, then execute soft recovery procedure as shown.
ESEUTIL /R <Enn>
Step 3. Use below syntax to create database on new server.
New-MailboxDatabase –Name <DatabaseName> -Server <ServerName> -EdbFilePath <DatabaseFileNameandPath> -LogFolderPath <LogFilesPath>
Step 4. Now, set the attribute “This database can be over-written by restore” using the given command:
Set-MailboxDatabase <DatabaseName> -AllowFileRestore $true
Step 5. Now, move DB files of Exchange such as Log, EDB and Exchange Search catalogue files to a particular database folder that one have selected when creating new database.
Step 6. Mount the database by using the following command:
Mount-Database <DatabaseName>
Step 7. After process of mounting database gets complete, modify settings of user account by using Set-Mailbox cmdlet to make sure that account points towards the new server mailbox. Use the syntax mentioned below and move all users from old database to new one.
Get-Mailbox-Database <Source Database> |where {$_.ObjectClass –NotMatch ‘(SystemAttendantMailbox|ExOleDbSystemMailbox)’}| Set-Mailbox-Database <TargetDatabase>
Step 8. Lastly, trigger any message delivery remaining in the queues using following command:
Get-Queue <QueueName> | Retry-Queue-Resubmit $true
After replication completes in Active Directory, users can easily access the related mailboxes on new Exchange Server. Generally, the clients and users are redirected to new Exchange environment through Autodiscover. Moreover, Outlook Web users also need to be redirected to new Exchange Server profile.
Follow one of the method mentioned below to verify if mailboxes can be moved successfully to new Exchange Server:
- Use Outlook for Web to Open Exchange Mailboxes.
- Use of MS Outlook to open Exchange Mailboxes.
Opening one of these platform, you will find that mailboxes moved to new Exchange environment.
Drawbacks of Data Probability Method
After proved to be a reliable method, still there are some limitations it possesses:
- Allows to move the database in same organization.
- Exchange Server and OS version need to be same on both source and target.
- Not able to move public folder database.
- Not perform the action using EAC (Exchange Admin Center).
Moving Exchange 2010 Mailbox using Automated Method
Make use of Exchange Migrator to migrate Exchange 2010 mailbox to another server. With the help of the application, a user can move Exchange Server, Hosted Exchange Server and Office 365 mailboxes to another Exchange Server, Hosted Exchange Server, Office 365, PST and Default Outlook Profile account directly. The data remain intact and secure throughout the process. It is equipped with some remarkable features as discussed:
- Batch move Exchange multiple accounts at one time.
- Migrate mailboxes from Exchange/Hosted Exchange and Office 365.
- Export Exchange Server user mailbox with archive mailbox and public folder.
- Provides date filter and item filter for specified migration.
- Option to exclude empty and deleted folder during export.
- Migrate mailboxes to Exchange Server, Hosted Exchange Server, PST, O365 and default Outlook profile.
- Supports entire Windows OS and Exchange Server editions.
Such amazing features of Exchange Migration Tool make it more useful and recommended to move data from one environment into another.
Conclusion
Moving Exchange 2010 mailbox database is tedious task for users having lot of accounts for migration. However, Exchange Migrator makes it easy for them. It is direct, effortless and reliable source to directly move Exchange database of any edition into desired server without data loss. Try the application working by using the free demo version that allows to move first 25 files from each Exchange folder free of cost.
Discover more from TechBooky
Subscribe to get the latest posts sent to your email.