{"id":721,"date":"2017-06-29T09:53:20","date_gmt":"2017-06-29T09:53:20","guid":{"rendered":"http:\/\/www.stellarservertools.com\/blog\/?p=721"},"modified":"2020-08-18T14:28:58","modified_gmt":"2020-08-18T14:28:58","slug":"how-to-recover-exchange-server-data-in-office-365-environment","status":"publish","type":"post","link":"https:\/\/www.stellarservertools.com\/blog\/how-to-recover-exchange-server-data-in-office-365-environment\/","title":{"rendered":"How to Recover Exchange Server Data in Office 365 Environment?"},"content":{"rendered":"<p>There are times when users may wish to recover data from the corrupt or damaged Exchange Server database (EDB) file in Office 365 environment. For instance: A user has a hybrid Exchange Server 2010 SP3 environment with a Data Availability Group (DAG) having 4 members in the premise. Now, the user has migrated all the user mailboxes that were saved in the server\u2019s database EDB file. Also, the two mailbox servers (2 member DAG) and the other two are offline but with data still saved on them. Plus, the user removed a mailbox that was migrated to the 365 cloud environment and is no longer present in the Recycle Bin. This occurred within 10 days from today. Now, the user is worried if there is any way to recover data from the old mailbox of Exchange Server that is no longer a part of the DAG (On-Prem). Plus, as archiving was not there at that time, the question is how to recover Exchange data in Office 365 environment.<\/p>\n<p><strong><em>Note<\/em><\/strong><em> \u2013 In the sections below, solutions to this scenario have been explained.<\/em><\/p>\n<p><strong>\u00a0<\/strong><strong>Solutions to Recover Data from Exchange Server <\/strong><\/p>\n<ol>\n<li><strong>Powershell script \u2018Export-Mailbox\u2019<\/strong> &#8211; As a solution to this issue, the user can use the Powershell script \u2018Export-Mailbox\u2019 to export mailboxes from the database EDB file of Exchange Server. The condition here is that the user\u2019s EDB file should work properly.<\/li>\n<li><strong>Use of a Third-Party Software<\/strong> \u2013 In the above scenario, the user can recover the old mailbox even if the mailbox is not present in DAG and is deleted from the Recycle Bin of Windows system with the help of a third-party software that is proficient enough to do so. For instance, you can use Stellar Repair for Exchange software to recover Exchange Data in Office 365 environment.<\/li>\n<\/ol>\n<p><strong>How to use<\/strong> <strong>Stellar Repair for Exchange?<\/strong><\/p>\n<p>To use this software, users should download, install, and then activate it by registering. The registration can be done in both the circumstances, if one has the Registration Key and if one does not have the Registration Key. In the latter case, it can be done both online and offline. After completing the registration process, follow the steps mentioned below:<\/p>\n<ol>\n<li>Launch the software by giving a double click on its icon. After launching the software, the main user interface of the software will appear. It gives two options to select Exchange database EDB file and recover data from it.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"http:\/\/www.stellarservertools.com\/screenshots_iframe\/mailbox-exchange-recovery\/1.png\" alt=\"exchange server recovery\" width=\"630\" height=\"338\" \/><\/p>\n<ul>\n<li><strong>Open EDB<\/strong> to open the corrupt or damaged EDB file.<\/li>\n<\/ul>\n<p>For \u2018Open EDB\u2019, select the corrupt EDB file and click on the <strong>Start<\/strong> tab.<\/p>\n<ul>\n<li><strong>Find EDB<\/strong> to search and select the corrupt or damaged EDB file from which data is to be recovered. This option is highly useful when the location of the EDB file is not known to the user.<\/li>\n<\/ul>\n<p>For \u2018Find EDB\u2019,<strong> Find EDB File <\/strong>dialog box will appear. In<strong> Find Options<\/strong>, select the drive from the <strong>Look in<\/strong> drop-down menu, and select EDB file from the <strong>File Type <\/strong>drop-down menu. Check \u2018Find in Subfolders\u2019 checkbox and then click on the <strong>Start<\/strong> tab. This will enlist all the EDB files from which you need to select the one that you wish to recover. After selecting the EDB file, click on the <strong>OK<\/strong> tab.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"http:\/\/www.stellarservertools.com\/screenshots_iframe\/mailbox-exchange-recovery\/2.png\" alt=\"exchange server recovery\" width=\"630\" height=\"435\" \/><\/p>\n<ol start=\"2\">\n<li>The \u2018<strong>Select Scan Mode<\/strong>\u2019 dialog box will appear. Here, you will have to select either <strong>Quick Scan<\/strong> or <strong>Extensive Scan<\/strong> and click on the <strong>OK<\/strong><\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"http:\/\/www.stellarservertools.com\/screenshots_iframe\/mailbox-exchange-recovery\/3.png\" alt=\"exchange server recovery\" width=\"630\" height=\"339\" \/><\/p>\n<ul>\n<li><strong>Quick Scan<\/strong> \u2013 This is a fast scanning process and is successful in most cases of the corrupt EDB files.<\/li>\n<li><strong>Extensive Scan<\/strong> &#8211; This does extensive scanning of the selected EDB file for better results and is time consuming.<\/li>\n<\/ul>\n<ol start=\"3\">\n<li>The EDB file scanning is in progress.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"http:\/\/www.stellarservertools.com\/screenshots_iframe\/mailbox-exchange-recovery\/4.png\" alt=\"exchange server recovery\" width=\"630\" height=\"354\" \/><\/p>\n<ol start=\"4\">\n<li>If data from another corrupt EDB file is to be recovered, the user can select, add, and scan more EDB files at this phase of the recovery process.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"http:\/\/www.stellarservertools.com\/screenshots_iframe\/mailbox-exchange-recovery\/5.png\" alt=\"exchange server recovery\" width=\"584\" height=\"360\" \/><\/p>\n<p><strong>\u00a0<\/strong><\/p>\n<ol start=\"5\">\n<li>After completion of the scanning process, all the mailboxes with the mail folders that are recoverable appear in a three-pane window.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"http:\/\/www.stellarservertools.com\/screenshots_iframe\/mailbox-exchange-recovery\/6.png\" alt=\"exchange server recovery\" width=\"630\" height=\"341\" \/><\/p>\n<p><strong>\u00a0<\/strong><\/p>\n<ol start=\"6\">\n<li>From the window\u2019s left pane, select all or the required mailboxes and click on the <strong>Save Mailboxes<\/strong> icon from the \u2018Tool bar.\u2019 A <strong>Save As<\/strong> dialog box appears from which you need to select Office 365 option and click on the <strong>OK<\/strong><\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"http:\/\/www.stellarservertools.com\/screenshots_iframe\/mailbox-exchange-recovery\/8.png\" alt=\"exchange server recovery\" width=\"630\" height=\"343\" \/><\/p>\n<p><strong>\u00a0<\/strong><\/p>\n<ol start=\"7\">\n<li>\u2018Office 365 Details\u2019 dialog box appears wherein you need to enter Office 365 credentials that are \u2018Mail Id\u2019 and \u2018password\u2019 and click on the <strong>OK<\/strong> tab to export selected mailbox folders to Office 365 mailboxes.<\/li>\n<\/ol>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"http:\/\/www.stellarservertools.com\/screenshots_iframe\/mailbox-exchange-recovery\/9.png\" alt=\"exchange server recovery\" width=\"630\" height=\"341\" \/><\/p>\n<p><strong>\u00a0<\/strong><\/p>\n<p><strong>Why Use<\/strong> <strong>Stellar Repair for Exchange?<\/strong><\/p>\n<p>It is an out-of-the-box, and a top-notch feature rich software that can repair the corrupt Exchange Server Database (EDB) files efficiently without fail. It can extract mailboxes and the data stored within them correctly. Also, it is capable of handling severe corruption issues in EDB file and can restore emails, attachments, contacts, calendars, tasks, and the rest mailbox items. \u00a0You can download the software from here:<\/p>\n<p><a href=\"https:\/\/cloud.stellarinfo.com\/micro\/StellarConverterforEDB.exe\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-717 size-full\" src=\"https:\/\/www.stellarservertools.com\/blog\/wp-content\/uploads\/2015\/09\/download.png\" alt=\"\" width=\"240\" height=\"62\" \/><\/a><\/p>\n<p><strong>Conclusion<\/strong><\/p>\n<p>As users are now aware of the two ways using which they can <a href=\"http:\/\/www.stellarservertools.com\/recover-exchange-mailbox.php\">recover Exchange mailbox database<\/a> EDB file in Office 365 environment, they can use any of the two. Nonetheless, using Stellar Repair for Exchange is a better option as it is an easy-to-use software without involving any complexity. Also, it does not require users to have technical expertise in Exchange Server.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There are times when users may wish to recover data from the corrupt or damaged Exchange Server database (EDB) file in Office 365 environment. For instance: A user has a hybrid Exchange Server 2010 SP3 environment with a Data Availability Group (DAG) having 4 members in the premise. Now, the user has migrated all the user mailboxes that were saved in the server\u2019s database EDB file. Also, the two mailbox servers (2 member DAG) and the other two are offline but with data still saved on them. Plus, the user removed a mailbox that was migrated to the 365 cloud <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[89],"amp_validity":null,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts\/721"}],"collection":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/comments?post=721"}],"version-history":[{"count":8,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts\/721\/revisions"}],"predecessor-version":[{"id":1739,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/posts\/721\/revisions\/1739"}],"wp:attachment":[{"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/media?parent=721"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/categories?post=721"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.stellarservertools.com\/blog\/wp-json\/wp\/v2\/tags?post=721"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}