Pages

Tuesday, July 25, 2017

Migrate/Import Exchange EDB File to New Server in Few Steps

Have you ever thought of migrating EDB File of Microsoft Exchange to New Exchange Server? Do you ever need to import .edb to New Server? Let’s see how it can be done. Here in this blog, we will discuss two methods to export/move EDB file to New Server.
While Exchange mailbox data is designed, identified details are saved that resultantly benefits in discovering mailbox database for a particular organization or administrative group. Mainly, this data is mounted on the servers working with the MS Exchange that is installed in an organization with a similar administrative group. It is significant that Microsoft Exchange mailbox is not combined with the similar data storage group or the server in which data is created. It is not a problem to export any data to new Microsoft Exchange Server that has similar enterprise as well as the administrative group name.
The edition should be similar, revision service should be similar or edition upgraded could have been likely but on the situation, which should be suitable for original Exchange server.
If you have mounted Exchange mailbox database only once to the server upper-level then, it is not possible to get data back to down-level server. Thus, it is very important to be getting double assured about same MS Exchange server edition as well as patch level when you copy Exchange EDB to New Server.
Let’s move further to discuss the solutions.
Note:

Before migrating the Exchange files, make sure that the files must be healthy and error free. If not, then it is strongly recommneded to go for a good Recovery Software to recover the files.
You can go for such a tool i.e SysTools Exchange Recovery to repair multiple EDB files easily without losing any data.

Methodologies to Migrate Exchange EDB to New Exchange Server

There are two distinct methods that make easy in converting data from EDB file to New Server. These are as follows:

Method 1:

Online Back-up Databases Restoration
In a manner to implement this process, make sure that new server should be configured with storage group as well as a database that has the same name.
• Now, you have restored Exchange backup by changing backup and restore location to server B. Data has now migrated to server B within the same storage group and proper names.

Method 2: Exchange Online Backup of VSS Database Restoration

This solution works completely depending on capabilities of a vendor as well as restrictions at the time of mailbox database restoration to other location.
To execute this, it is first significant to discuss with a vendor about fetching instructions.
• Now, copy MS Exchange database from its original path to diverse path location that comprises of a Diverse Logical database as well as storage group.
• To execute this facility, it is not important that logical storage group and a name of a database should be matched. On the conflicting, database file requires being same as they are presented in original server. If you need to rename data files for creating a proper match, you can move ahead with this function. You are free to rename files in order to contest them.
Now, before putting these manual solutions into action, you must be aware of the protocols/directions to export EDB file to New Server. Let us read these instructions first.

Guidance Before Implementing the Above Solutions

To run both the above-mentioned solutions, read the given below points:
• While moving EDB data to a new server, checked the box ‘This Database can be overwritten by a restore’ before restoration from an online backup. You will get this option in the page of Database properties if you fail to restore/ mount /move database due to this issue then, the issue will get saved in server application log.
• Before you transfer EDB to the New Exchange Server, it should be shut down properly.
• Ensure that you stop database saved in a destination as well as delete the present data. It is better to mark option ‘do not start automatically’. This will help to stop your database from seeming online at the time of migration process.
• MS Exchange server makes numerous mailboxes so that system function such as SMTP can be performed. After copying EDB to New Server, there must be other mailboxes left for carrying out these processes. At such point, Mailbox clean-up agent disconnects them as well as eliminated for 30 days period.

Conclusion

Many times, data migration is quite important to maintain the continuity of work. Therefore, in the above-discussion, two solutions have been explained to export/move EDB file to New Server. So, one can go for any of the methods to import Exchange EDB to Microsoft Exchange Server, accordingly.

0 comments:

Post a Comment

Post a reply