Ensure the user account (you’ll be using) has Databases<\/strong> role assigned. To assign this role, use the below-mentioned PowerShell cmdlet in the EMS:<\/p> To verify if the role has been successfully assigned to the user, run the following command:<\/p> From the list of roles, check that the Databases<\/strong> role is assigned to your user account.<\/p> To mount an orphaned EDB file on a different Exchange Server, you need to rebuild the destination server with the same configurations of the original server. You need to ensure that new server has the same operating system, IP addresses, drives, drive letters, Exchange Server version, and computer name. Also, when rebuilding the server, you need to keep the following media in hand:<\/p> If the original server is not in working condition, transfer the latest backup to the destination server. You can use one of the below mentioned process depending on the scenario:<\/p> Let us now look at the process to restore backup on the destination server.<\/p> Note<\/em><\/strong>: For demonstration purpose, we will describe the process to restore the backup using Windows Server Backup. However, you can use any other backup recovery software that is compatible with your Exchange Server.<\/em><\/p>\n<\/blockquote> Verify that the database that you’ve restored from backup is in the clean shutdown state. Use the EseUtil \/mh<\/strong><\/a> command (as given below) to check the state of database.<\/p> The State<\/strong> field in the command output will show either Clean Shutdown<\/strong> or Dirty Shutdown<\/strong>. If it shows Dirty Shutdown<\/strong>, perform EseUtil Soft Recovery<\/strong> process using the eseutil \/R<\/strong> command as shown below:<\/p> Confirm the state of the database again using the Eseutil \/mh<\/strong> command. It should now be in Clean Shutdown<\/strong> state.<\/p> Now that the database is restored from backup and is in the clean shutdown state, you can use the New-MailboxDatabase<\/strong> cmdlet and create a new database on the destination server. You can use the syntax given below:<\/p> In the above command, replace the locations of EDB file and Log files with the locations where you’ve saved your recovered files.<\/p> To verify that database is successfully created, run the following command:<\/p> To mount the database on the server, you can use the Mount-Database<\/a> command as given below:<\/p> Now, run the Get-MailboxDatabase command<\/a> to ensure that the database is successfully mounted on the server (see the below example).<\/p> The above-described process is time-consuming and requires a lot of manual work. To avoid the hassles, you can take the help of third-party Exchange recovery tools, like Stellar Repair for Exchange<\/strong><\/a>. This tool comes in handy when the backup is unavailable or obsolete and the database is in dirty shutdown state. You can open offline EDB file from a decommissioned Exchange Server of any version and directly export the EDB file data to another live Exchange Server. You can also export the EDB file data to Microsoft 365 (Office 365).<\/p> You may need to mount the EDB file of one Exchange Server on another server in case the original server has failed due to a disaster or other issue. If you want to retrieve data from the EDB file<\/a> of a decommissioned Exchange Server, then you can mount the EDB file on a new Exchange Server. To mount the EDB file on a different Exchange Server, you can follow the stepwise process mentioned above. However, the process is lengthy and requires technical expertise. Additionally, this process will not work if the backup is unavailable. As an alternative, you can use Stellar Repair for Exchange to scan the EDB file of decommissioned Exchange Server and recover data from it. You can then directly export this data to another live Exchange Server. The software is compatible with all the versions of Exchange Server – from 5.5 to 2019.<\/p>New-ManagementRoleAssignment -Name Admin -User \"Anubhuti@exch16adib.com\" -Role \"Databases\"<\/strong><\/code><\/pre>Get-ManagementRoleAssignment -RoleAssignee \"Anubhuti@exch16adib.com\"<\/strong><\/code><\/pre>![\"role](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2019\/07\/Picture1.png\")
<\/figure>2. Prepare the destination Exchange Server<\/strong><\/h3>
\n
3. Recover the EDB file from backup<\/strong><\/h3>
\n
\n
\n
![\"Run Windows](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2019\/07\/Picture2.png\")
<\/figure>\n
![\"Select](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2019\/07\/Picture3.png\")
<\/figure>\n
![\"Select](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2019\/07\/Picture4.png\")
<\/figure>\n
4. Check the state of recovered database and repair it if required<\/strong><\/h3>
Eseutil \/mh “Path to the database”<\/strong><\/code><\/pre> eseutil \/r E00 \/l “C:\\Path to log file” \/d “C:\\Path to database”<\/strong><\/code><\/pre>5. Create a New Database<\/strong><\/h3>
New-MailboxDatabase -Server Stellar -Name RDB01 -Recovery -EdbFilePath “C:\\Database\\IBDB01.EDB\" -LogFolderPath \"C:\\Database\\IBDB01\"<\/strong><\/code><\/pre>Get-MailboxDatabase <\/strong><\/code><\/pre>![\"database](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2019\/07\/Picture5-1.png\")
<\/figure>6. Mount the Database on the Destination Server<\/strong><\/h3>
Mount-Database <database name><\/strong><\/code><\/pre>Get-MailboxDatabase -Status | Sort Name | Format-Table Name, Server, Mounted<\/strong><\/code><\/pre>![\"database](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2019\/07\/Picture6.png\")
<\/figure>To Sum Up<\/h2>