{"id":3593,"date":"2017-03-10T12:14:00","date_gmt":"2017-03-10T12:14:00","guid":{"rendered":"http:\/\/wordpress.semnaitik.com\/?p=3593"},"modified":"2025-01-25T10:26:45","modified_gmt":"2025-01-25T09:26:45","slug":"sharepoint-server-recovery","status":"publish","type":"post","link":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/","title":{"rendered":"SharePoint Server Recovery &#8211; Mistakes You Should Avoid"},"content":{"rendered":"<blockquote>\n<p style=\"text-align: justify;\">SharePoint users often experience failure or crash due to various reasons. Such an inappropriate action certainly causes corruption in the SharePoint database. You can&#8217;t open or access a corrupt database file until you repair it. In a case of severe corruption, repairing the database might be challenging. In such a situation, you must use a smart SharePoint Server Recovery tool to restore SharePoint Server data.<\/p>\n<p><a href=\"https:\/\/www.sysinfotools.com\/demo-version\/SysInfoTools-SharePoint-Server-Recovery.exe\" rel=\"attachment wp-att-4273\"><img decoding=\"async\" class=\"aligncenter size-full wp-image-4273\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2013\/11\/download-free-demo.png\" alt=\"\" width=\"217\" height=\"62\" \/><\/a><\/p><\/blockquote>\n<h2 style=\"text-align: justify;\"><strong>Microsoft SharePoint Server<\/strong><\/h2>\n<p style=\"text-align: justify;\">Microsoft SharePoint is a popular web-based application integrated with the Microsoft Office suite. It was first launched in 2001, and it has been commonly using for document management and storage system since then. SharePoint is highly popular among large customer\/consumer organizations. Such organizations use SharePoint to create websites.<\/p>\n<p style=\"text-align: justify;\">You can use SharePoint as a secure place where you can store crucial\/confidential data and information. Also, you can organize, share and access the stored information from any device (almost all). The only thing what you actually need is a web browser; you can use any like <strong>Internet Explorer<\/strong>, <strong>Chrome<\/strong> or <strong>Firefox<\/strong>.<\/p>\n<p style=\"text-align: justify;\">Microsoft SharePoint provides different editions which have different functions: <em>SharePoint Server<\/em>, <em>SharePoint Standard<\/em>, <em>SharePoint Enterprise<\/em>, and <em>SharePoint Online<\/em>. Here in this post, we&#8217;ll discuss the most common reasons for corruption in SharePoint Server. Also, we&#8217;ll learn how to repair SharePoint database and perform SharePoint Server recovery.<\/p>\n<p style=\"text-align: justify;\"><img fetchpriority=\"high\" decoding=\"async\" class=\"aligncenter wp-image-3645 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/Microsoft-SharePoint-Server.png\" alt=\"Microsoft SharePoint Server\" width=\"516\" height=\"251\" srcset=\"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/Microsoft-SharePoint-Server.png 516w, https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/Microsoft-SharePoint-Server-300x146.png 300w\" sizes=\"(max-width: 516px) 100vw, 516px\" \/><\/p>\n<h3 style=\"text-align: justify;\"><strong>Some common SharePoint benefits are:\u00a0<\/strong><\/h3>\n<ul>\n<li style=\"text-align: justify;\">Microsoft SharePoint Server allows users\u00a0to create online content such as <em><strong>web pages<\/strong><\/em>, <strong><em>wiki&#8217;s<\/em><\/strong>, <em><strong>blogs<\/strong><\/em>, etc.<\/li>\n<li style=\"text-align: justify;\">Microsoft SharePoint Server helps you manage and control the entire content of your business. If you&#8217;re running a business, you must know how painful security violation or hacking can be as it may put your invaluable data at high risk. Such action can definitely cause a great deal of damage\/loss to the company. SharePoint Server contains various tools which help you track the online content and streamline various business processes with ease.<\/li>\n<li style=\"text-align: justify;\">Microsoft SharePoint Server has\u00a0an\u00a0ability to organize documents and edit them quickly and easily. There are a number of\u00a0different criteria to organize documents in SharePoint. Also, collaborative editing is possible using the applications available with the software.<\/li>\n<li style=\"text-align: justify;\">You can also use SharePoint platform\u00a0to access documents and workspaces which you need to share with a number of individuals, such as databases, commonly used forms, etc.<\/li>\n<\/ul>\n<p style=\"text-align: justify;\">Though SharePoint Server has many advantages, on the other hand, you may experience some serious issues like Server crash and corruption.<\/p>\n<h2 style=\"text-align: justify;\"><strong>Corruption in SharePoint Server<\/strong><\/h2>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#1 &#8211;<\/strong>\u00a0<strong>SharePoint has low RAM or hard disk space<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img decoding=\"async\" class=\"alignleft wp-image-3647 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/low-RAM-or-hard-disk-space.png\" alt=\"SharePoint has low RAM or hard disk space\" width=\"145\" height=\"145\" \/>SharePoint Server works as hard as possible to keep its users happy, although it has limited resources. If it has low RAM or hard disk space, it causes serious issues to users. Due to low RAM or disk space, it starts shutting off the functionalities in order to get fit into the available space. Also, it\u00a0starts caching less in the web application pools and recycles them more often. Since\u00a0SharePoint must compile the same ASP.NET code\u00a0persistently, actions of less caching and more recycling will result in\u00a0degraded end-user experience.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution<\/strong><strong>:<\/strong>\u00a0The easiest solution to resolve this issue is to add more RAM. Also, make sure you&#8217;re having enough free space on your hard disk, especially on C Drive.<\/p>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#2 &#8211;<\/strong> <strong>Use of virtualized Microsoft SQL Server<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3652 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/Use-of-Virtualization.png\" alt=\"Use of virtualized Microsoft SQL Server\" width=\"145\" height=\"145\" \/>Though virtualization is not bad, make sure you do that very smartly without sacrificing the ability of SharePoint Server. But sometimes\u00a0aggressive virtualization may cause serious issues. It\u00a0allows administrators to make mistakes on a huge level. Just for an example, you&#8217;re using virtualized MS SQL Server. Sometimes the action of virtualizing SQL Server starts over-committing the host through\u00a0RAM, CPU, or hard disk\u00a0space. Since everything of SharePoint is stored in SQL Server, slow SQL Server will cause slow SharePoint.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution<\/strong><strong>:<\/strong>\u00a0The obvious solution to resolve this issue is to move\u00a0the SQL Server to a physical box so that there&#8217;s no need to share resources. It&#8217;s all easy to move\u00a0SharePoint&#8217;s SQL Server instance.<\/p>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#3 &#8211;\u00a0Incorrect URL during Content Web App&#8217;s creation<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3654 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/incorrect-url.png\" alt=\"Incorrect URL during Content Web App\u2019s creation\" width=\"145\" height=\"145\" \/>Generally, SharePoint Server and Microsoft <span style=\"text-decoration: underline;\"><a href=\"https:\/\/en.wikipedia.org\/wiki\/Internet_Information_Services\"><strong>Internet Information Services<\/strong><\/a><\/span> (IIS), formerly known as\u00a0<em><strong>Internet Information Server<\/strong><\/em>, face communication problems. When you make any changes to a web app, there&#8217;s no way for SharePoint to tell IIS about this change after its creation.\u00a0Just for an example,\u00a0you create an <a href=\"https:\/\/blogs.msdn.microsoft.com\/sharepoint_strategery\/2013\/05\/27\/alternate-access-mappings-aams-explained\/\"><strong><span style=\"text-decoration: underline;\">Alternate Access Mapping<\/span><\/strong><\/a> (AAM) for a web app in Central Administration. You&#8217;re not done yet. You still need to go to AAM to add the host header to the new address. Generally,\u00a0SharePoint administrators give their web apps short URLs like <em><span style=\"text-decoration: underline;\">https:\/\/portal<\/span><\/em>, in order to avoid more typing. Since\u00a0the web app needs a fully qualified URL, such short URLs fail to\u00a0route across the Internet. Though it&#8217;s not that big deal, sometimes it may cause serious problems.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution<\/strong><strong>:<\/strong>\u00a0Make notes of all your web app settings.\u00a0Avoid using short incorrect URLs. Make sure you\u00a0enter the correct, fully qualified URL in the <em><strong>Host Header<\/strong><\/em> box.<\/p>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#4 &#8211; Running Web or Service Apps in separate App Pools<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3662 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/SharePoint-Web-Service-Apps.png\" alt=\"Running Web or Service Apps in separate App Pools\" width=\"145\" height=\"145\" \/>An application pool runs Web apps and other service applications inside it.\u00a0It&#8217;s a <strong>W3WP.exe<\/strong> process that runs on your SharePoint Server. Make sure you\u00a0run all SharePoint web apps inside one application pool. And the very same thing goes for service applications as well. Using multiple application pools will cache the same content multiple times. If you run\u00a0each web app in its own application pool, it makes inefficient use of the Server&#8217;s memory for sure.\u00a0Sometimes it may cause some serious problems.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution:<\/strong>\u00a0The best way to resolve this problem is to run web and service apps in a single app pool so\u00a0that Server consumes less memory.<\/p>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#5 &#8211;\u00a0Use of single account for almost everything<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3666 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/Use-of-single-account-for-almost-everything.png\" alt=\"Use of single account for almost everything\" width=\"145\" height=\"145\" \/>Security is always complicated, even in SharePoint Server. Using a single account for everything looks okay, but many of you don&#8217;t\u00a0know it&#8217;s a bad idea. Why? If you&#8217;re using a single account, this may cause\u00a0several security issues in SharePoint Server. How? Anyone who knows your account password can make unnecessary changes to SharePoint Server. Also, you\u00a0can&#8217;t verify what changes have been made and by whom. And if you change the password of that single account more than often, this may put SharePoint&#8217;s uptime at high risk.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution:<\/strong>\u00a0First of all, avoid using a single account for everything in SharePoint Server. Don&#8217;t forget to add the <em><strong>sp_webapps<\/strong><\/em> and <em><strong>sp_serviceapps<\/strong><\/em> accounts as managed accounts.\u00a0On the <em><strong>Search Service Application<\/strong><\/em> page, you can change the default content access account for the Search service application. Also, you\u00a0can change the accounts which are used by other processes as well (Under Central Administration, Security, Configure Service Accounts).<\/p>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#6 &#8211;\u00a0Enable default SharePoint database settings<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3664 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/SharePoint-Database-Settings.png\" alt=\"Enable default SharePoint database settings\" width=\"145\" height=\"145\" \/>Keeping default settings for SharePoint database might be risky sometimes.\u00a0When SharePoint Server starts creating its multitudes of databases,\u00a0it may cause\u00a0some\u00a0severe issues. Just for an example, if you enable the <em><strong>&#8220;autogrow&#8221;<\/strong><\/em> setting option, this will let the database files grow by 1 MB. This means\u00a0with every upload, the database files will auto-grow. It can slow down SQL Server as well as SharePoint. Also, it may cause some issues in database files\u00a0which are spread all over the\u00a0drives in\u00a0small parts (1 MB).<\/p>\n<p style=\"text-align: justify;\">SharePoint\u00a0creates most of its databases (especially <em><strong>Config<\/strong><\/em> and <em><strong>Content<\/strong><\/em>) with the recovery model set to Full by default. Although it&#8217;s helpful in recovering data, you must manage this whole process correctly. Otherwise, those LDF files will fill your hard disk slowly. When SQL Drives are full, SharePoint stops completely or starts crashing frequently.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution:<\/strong>\u00a0To resolve this issue, you can set the <em><strong>&#8220;autogrow&#8221;<\/strong><\/em> setting in such a way that\u00a0doesn&#8217;t let the database files grow frequently. It&#8217;s strongly recommended that you should change the auto-grow setting from 1 MB to 500 MB or 1 GB. Also, make sure that your recovery model setting is consistent with your disaster recovery plans.<\/p>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#7 &#8211;\u00a0Use of Farm Configuration Wizard<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3660 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/Use-of-Farm-Configuration-Wizard.png\" alt=\"Use of Farm Configuration Wizard\" width=\"145\" height=\"145\" \/>Sometimes using the <strong><em>Farm Configuration Wizard<\/em><\/strong> may cause some serious issues. All the database files created by Farm Configuration Wizard, contain\u00a0bad globally unique identifiers (GUIDs) at the end of their names. Also, it creates a content web\u00a0app,\u00a0at <span style=\"text-decoration: underline;\"><em>https:\/\/servername<\/em><\/span>, which fails to scale well.\u00a0The situation becomes much worse when the wizard creates your My Site host on that same web app, at <em><span style=\"text-decoration: underline;\">https:\/\/servername\/my<\/span><\/em>.<\/p>\n<p style=\"text-align: justify;\">Also, the wizard\u00a0encourages you to create service applications which you may\u00a0not use in actual. The Farm Configuration Wizard can create a mess on SharePoint, and it may become a challenge to fix that.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution:<\/strong>\u00a0To resolve the issues caused by Farm Configuration Wizard, you can take the following measures:<\/p>\n<ul>\n<li style=\"text-align: justify;\">First, you should start with your web apps &#8211; Create a web app for My Site and provide a <em>fully-qualified domain name<\/em> <strong>(FQDN)<\/strong>, such as <em><span style=\"text-decoration: underline;\">mysites.company.com<\/span><\/em>. Now create a host, My Site, at the web app&#8217;s root. Move any My Site to one content database by using\u00a0<strong>Windows PowerShell<\/strong> <em>cmdlet Move-SPSite<\/em>. After that, attach this content database to your new web app.\u00a0Also, you need to adjust your <em><strong>User Profile Service<\/strong><\/em> in order to tell your new My Site location.<\/li>\n<li style=\"text-align: justify;\">Clean up your service applications &#8211; Go to your list of service applications and delete\/remove those which you don&#8217;t use anymore. There&#8217;s no need to keep the service applications which you aren&#8217;t going to use for another six months. Once you successfully delete\/remove all the unnecessary\u00a0service applications, you should\u00a0stop the associated service instances. If it&#8217;s possible\u00a0to\u00a0remove the GUIDs from the service application database names, then do that.<\/li>\n<\/ul>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#8 &#8211;\u00a0Disable Blob caching<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3656 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/disable-blob-caching.png\" alt=\"Disable blob caching\" width=\"145\" height=\"145\" \/>Should SharePoint work slow or fast? What do you think? Most of us want SharePoint to get files to the users as quickly as possible, and BLOB caching plays an important role in that.\u00a0It&#8217;s one of the easiest and least expensive ways which can help you improve SharePoint performance. But if the BLOB caching is disabled, you may come across to some serious issues related to SharePoint performance.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution:<\/strong>\u00a0Make sure the BLOB caching is enabled because it helps SharePoint to get files to users more quickly, Also, it eases the burden on SQL Server.<\/p>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#9 &#8211; SharePoint Server doesn&#8217;t point at itself<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3668 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/SharePoint-Server-does-not-point-at-itself.png\" alt=\"SharePoint Server doesn\u2019t point at itself\" width=\"145\" height=\"145\" \/>If\u00a0SharePoint is working perfectly, it\u2019s great for users. But if\u00a0it doesn\u2019t work due to any reason, it\u2019s not less than a nightmare for anyone. Therefore, troubleshooting in a timely manner becomes mandatory. Make sure that every server in the SharePoint farm is pointing to itself for all web apps instead of pointing to others. It\u2019s highly beneficial. How? If sometimes SharePoint fails to respond, you can easily use <span style=\"text-decoration: underline;\"><a href=\"https:\/\/en.wikipedia.org\/wiki\/Remote_Desktop_Protocol\"><strong>Remote Desktop Protocol<\/strong><\/a><\/span> (RDP) to log in to each server and try to fix SharePoint. There\u2019s one more advantage of pointing Search index at itself. It can improve SharePoint&#8217;s performance.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution:<\/strong>\u00a0The only fix for this problem is to\u00a0point your Search indexer at itself. This will help you get the correct LOG files quickly. And the more quickly you get the LOG files, the more quickly you can resolve the errors.<\/p>\n<h4 style=\"text-align: justify;\"><strong>Mistake\u00a0#10 &#8211;\u00a0No use of\u00a0PDF iFilter<\/strong><\/h4>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-3658 size-full\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2017\/03\/No-use-of-PDF-iFilter.png\" alt=\"No use of PDF iFilter\" width=\"145\" height=\"145\" \/>In most organizations, SharePoint stores a large number of PDF files containing invaluable information. Users are able to\u00a0access the information stored in PDF files via\u00a0SharePoint Search. Generally, SharePoint Server is a great way to get users excited about SharePoint. You must install <em><strong>PDF iFilter<\/strong><\/em>, it&#8217;s easy and very useful. Adobe provides a <span style=\"text-decoration: underline;\"><strong>free PDF iFilter<\/strong><\/span> which you can use here. Make sure you install iFilter only on those SharePoint Servers which run the Search Index role. But if you don&#8217;t use any PDF iFilter, this may cause serious troubles.<\/p>\n<p style=\"text-align: justify;\"><strong>Solution:<\/strong> The only possible solution to this problem is PDF iFilter. Make sure you&#8217;re using PDF iFilter.\u00a0If you have a large farm in SharePoint and you want to reduce the time needed to index PDF files, you should try PDF iFilter provided by Foxit. It&#8217;s better than Adobe iFilter and provides you excellent performance (but it&#8217;s not a freeware).<\/p>\n<p style=\"text-align: justify;\">Aforementioned reasons cause failure in SharePoint Server and lead to corruption in its database. You&#8217;re lucky if you have the backup. Backup has the ability to restore what you lost due to\u00a0accidental deletion or corruption. Also, you can create a new database with the backup at the time of SharePoint Server failure or crash. This is the main reason why backup is strongly recommended by computer experts and professional users. Don&#8217;t forget to take backup of your data. Also, do practice your restore procedures regularly even before you actually need to.\u00a0Refer to this article to know <span style=\"text-decoration: underline;\"><a href=\"https:\/\/www.petri.com\/how-to-backup-restore-sharepoint-2013\"><strong>how to backup\u00a0and restore SharePoint<\/strong><\/a><\/span>.<\/p>\n<p style=\"text-align: justify;\">Interested users may find this useful &#8211;\u00a0<a href=\"https:\/\/wordpress.semnaitik.com\/repair-sql-database\/\"><span style=\"text-decoration: underline;\"><strong>Repair SQL Database File Via SQL Server Management Studio<\/strong><\/span><\/a><\/p>\n<h4 style=\"text-align: justify;\"><strong>Fix SharePoint Server corruption manually<\/strong><\/h4>\n<p style=\"text-align: justify;\">In case you don&#8217;t have any backup, you&#8217;re in deep trouble. Fortunately, SharePoint Server 2010 provides\u00a0you a feature to restore the configuration database and thus you can restore the farm configuration. And if you&#8217;re using SharePoint Server 2013 or 2016,\u00a0you have no need to restore configuration database since you can\u00a0directly restore farm configuration.<\/p>\n<p style=\"text-align: justify;\"><strong>Important note:<\/strong>\u00a0Before you can restore farm configuration, make sure:<\/p>\n<ul>\n<li style=\"text-align: justify;\">You must be the member of the Farm Administrators group on the system, which is running the Central Administration.<\/li>\n<li style=\"text-align: justify;\">Also, you must have permissions for the sysadmin server role on the database server, which contains all the databases.<\/li>\n<\/ul>\n<p><strong>Follow the points given below:<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>Step #1:<\/strong> First of all, go to Central Administration&#8217;s home page. Now click <em><strong>Restore from a backup<\/strong><\/em> in the\u00a0<strong>Backup and Restore<\/strong> section.<\/p>\n<p style=\"text-align: justify;\"><strong>Step\u00a0#2:<\/strong> On the <strong><em>&#8220;Restore from Backup&#8221;<\/em><\/strong>\u00a0screen, choose <em><strong>Backup to Restore<\/strong><\/em> page. Now select the backup job and click <strong>Next<\/strong> to continue the process.<\/p>\n<p style=\"text-align: justify;\"><strong>Step #3:<\/strong>\u00a0Choose <em><strong>Component to Restore<\/strong><\/em> page, and\u00a0click the checkbox shown next to the farm. Click <strong>Next<\/strong> to continue the process.<\/p>\n<p style=\"text-align: justify;\"><strong>Step #4:<\/strong>\u00a0In the <strong><em>&#8220;Restore Component&#8221;<\/em><\/strong> section, choose <em><strong>Restore Options page<\/strong><\/em> from <em><strong>Restore from Backup<\/strong><\/em> option. Make sure the Farm appears in <em>Restore the following content listing<\/em>.<\/p>\n<p style=\"text-align: justify;\"><strong>Step #5:<\/strong> In the <em><strong>&#8220;Restore Only Configuration Settings&#8221;<\/strong><\/em> part, make sure that <em><strong>Restore content and configuration settings preference<\/strong><\/em> is selected.<\/p>\n<p style=\"text-align: justify;\"><strong>Step #6:<\/strong> Choose <em><strong>Type of Restore preference<\/strong><\/em> in the\u00a0<em><strong>Restore Options<\/strong><\/em> section. Use <em><strong>Same configuration<\/strong><\/em> settings. Click <strong>OK<\/strong> button to confirm this operation. Then click <em><strong>Start Restore<\/strong><\/em> option.<\/p>\n<p style=\"text-align: justify;\">You can see the status of all SharePoint repair jobs.<\/p>\n<h3 style=\"text-align: justify;\"><strong>Professional SharePoint Server Recovery Software<\/strong><\/h3>\n<p style=\"text-align: justify;\">Unluckily if you fail to restore farm configuration manually, there&#8217;s an effective way to perform SharePoint Server recovery via a professional recovery solution. You must try something that can restore SharePoint Server data from the MDF database. There are many software vendors in the market which provide professional recovery solutions for SharePoint Server. Download free\u00a0SharePoint Server Recovery software\u00a0to recover\u00a0SharePoint data without causing any alteration or modification to their originality.<\/p>\n<p style=\"text-align: justify;\"><strong>Important note:<\/strong> I strongly recommend my readers to evaluate the <a href=\"https:\/\/www.sysinfotools.com\/sharepoint-server-recovery.html\"><span style=\"text-decoration: underline;\"><strong>SharePoint Server Recovery software<\/strong><\/span><\/a> before purchasing its licensed version. Download its free demo version first to see what you can possibly recover from the database. If you&#8217;re satisfied with the results, then only you should purchase the licensed version of SharePoint Server Recovery software.<\/p>\n<p style=\"text-align: justify;\"><strong>What you get in this SharePoint Server Recovery software:<\/strong><\/p>\n<ul>\n<li style=\"text-align: justify;\">Smart support for\u00a0<em><strong>Complete Database Recovery<\/strong><\/em> or <em><strong>Document Recovery<\/strong><\/em>;<\/li>\n<li style=\"text-align: justify;\">Intensive scanning of the corrupt database in just no time;<\/li>\n<li style=\"text-align: justify;\"><strong><em>Dual recovery modes<\/em><\/strong>, standard and advanced for handling the different level of corruption;<\/li>\n<li style=\"text-align: justify;\">Define <em><strong>collation type<\/strong><\/em> for the selected database before the recovery process;<\/li>\n<li style=\"text-align: justify;\"><em><strong>Tree-structure preview<\/strong><\/em> of recovered database objects before saving them;<\/li>\n<li style=\"text-align: justify;\"><em><strong>Easy-to-use<\/strong><\/em> application, i.e. it requires no prior technical expertise for SharePoint Server recovery.<\/li>\n<\/ul>\n<p><a href=\"https:\/\/www.sysinfotools.com\/demo-version\/SysInfoTools-SharePoint-Server-Recovery.exe\" rel=\"attachment wp-att-4273\"><img decoding=\"async\" class=\"aligncenter size-full wp-image-4273\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2013\/11\/download-free-demo.png\" alt=\"\" width=\"217\" height=\"62\" \/><\/a><\/p>\n<p><a href=\"https:\/\/www.sysinfotools.com\/demo-version\/SysInfoTools-SharePoint-Server-Recovery.exe\" rel=\"attachment wp-att-4246\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-4246\" src=\"https:\/\/wordpress.semnaitik.com\/wp-content\/uploads\/2013\/11\/DownloadButton.png\" alt=\"\" width=\"411\" height=\"100\" \/><\/a><\/p>\n<h4 style=\"text-align: justify;\"><strong>Watch the online video tutorial below<\/strong><\/h4>\n<p><iframe src=\"https:\/\/www.youtube.com\/embed\/vlVm0ZISgSE?rel=0\" width=\"690\" height=\"388\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><\/iframe><\/p>\n","protected":false},"excerpt":{"rendered":"<p>SharePoint users often experience failure or crash due to various reasons. Such an inappropriate action certainly causes corruption in the<a class=\"read-more ml-1 main-read-more\" href=\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/\">Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":5759,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[285],"tags":[698,523,526,699,524,525,522],"class_list":["post-3593","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-file-data-recovery","tag-microsoft-sharepoint","tag-repair-sharepoint-database","tag-restore-farm-configuration","tag-restore-sharepoint-server","tag-sharepoint-benefits","tag-sharepoint-server","tag-sharepoint-server-recovery"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>SharePoint Server Recovery - Mistakes You Should Avoid<\/title>\n<meta name=\"description\" content=\"There are various reasons which cause corruption in SharePoint. You must know their fix to resolve corruption. Read here for SharePoint Server recovery\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SharePoint Server Recovery - Mistakes You Should Avoid\" \/>\n<meta property=\"og:description\" content=\"There are various reasons which cause corruption in SharePoint. You must know their fix to resolve corruption. Read here for SharePoint Server recovery\" \/>\n<meta property=\"og:url\" content=\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/\" \/>\n<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/naitik.semwaal.5\" \/>\n<meta property=\"article:published_time\" content=\"2017-03-10T12:14:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-01-25T09:26:45+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png\" \/>\n\t<meta property=\"og:image:width\" content=\"678\" \/>\n\t<meta property=\"og:image:height\" content=\"381\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Danish\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Danish\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/\"},\"author\":{\"name\":\"Danish\",\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/#\/schema\/person\/2a69018b8418db3a31ca2d0a0a3e2c77\"},\"headline\":\"SharePoint Server Recovery &#8211; Mistakes You Should Avoid\",\"datePublished\":\"2017-03-10T12:14:00+00:00\",\"dateModified\":\"2025-01-25T09:26:45+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/\"},\"wordCount\":2605,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png\",\"keywords\":[\"Microsoft SharePoint\",\"repair SharePoint database\",\"restore farm configuration\",\"restore SharePoint Server\",\"SharePoint benefits\",\"SharePoint Server\",\"SharePoint server recovery\"],\"articleSection\":[\"Data Recovery\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/\",\"url\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/\",\"name\":\"SharePoint Server Recovery - Mistakes You Should Avoid\",\"isPartOf\":{\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png\",\"datePublished\":\"2017-03-10T12:14:00+00:00\",\"dateModified\":\"2025-01-25T09:26:45+00:00\",\"author\":{\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/#\/schema\/person\/2a69018b8418db3a31ca2d0a0a3e2c77\"},\"description\":\"There are various reasons which cause corruption in SharePoint. You must know their fix to resolve corruption. Read here for SharePoint Server recovery\",\"breadcrumb\":{\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#primaryimage\",\"url\":\"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png\",\"contentUrl\":\"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png\",\"width\":678,\"height\":381,\"caption\":\"SharePoint server recovery\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/wordpress.semnaitik.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SharePoint Server Recovery &#8211; Mistakes You Should Avoid\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/#website\",\"url\":\"https:\/\/wordpress.semnaitik.com\/blog\/\",\"name\":\"\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/wordpress.semnaitik.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/wordpress.semnaitik.com\/blog\/#\/schema\/person\/2a69018b8418db3a31ca2d0a0a3e2c77\",\"name\":\"Danish\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/be8cb8e17fe5afcda9b1aeea9726aaedbd8e1a8c1418f44f8b6ebc679cc527b4?s=96&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/be8cb8e17fe5afcda9b1aeea9726aaedbd8e1a8c1418f44f8b6ebc679cc527b4?s=96&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/be8cb8e17fe5afcda9b1aeea9726aaedbd8e1a8c1418f44f8b6ebc679cc527b4?s=96&r=g\",\"caption\":\"Danish\"},\"sameAs\":[\"http:\/\/semnaitik.com\/\",\"https:\/\/www.facebook.com\/naitik.semwaal.5\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"SharePoint Server Recovery - Mistakes You Should Avoid","description":"There are various reasons which cause corruption in SharePoint. You must know their fix to resolve corruption. Read here for SharePoint Server recovery","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/","og_locale":"en_US","og_type":"article","og_title":"SharePoint Server Recovery - Mistakes You Should Avoid","og_description":"There are various reasons which cause corruption in SharePoint. You must know their fix to resolve corruption. Read here for SharePoint Server recovery","og_url":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/","article_author":"https:\/\/www.facebook.com\/naitik.semwaal.5","article_published_time":"2017-03-10T12:14:00+00:00","article_modified_time":"2025-01-25T09:26:45+00:00","og_image":[{"width":678,"height":381,"url":"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png","type":"image\/png"}],"author":"Danish","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Danish","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#article","isPartOf":{"@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/"},"author":{"name":"Danish","@id":"https:\/\/wordpress.semnaitik.com\/blog\/#\/schema\/person\/2a69018b8418db3a31ca2d0a0a3e2c77"},"headline":"SharePoint Server Recovery &#8211; Mistakes You Should Avoid","datePublished":"2017-03-10T12:14:00+00:00","dateModified":"2025-01-25T09:26:45+00:00","mainEntityOfPage":{"@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/"},"wordCount":2605,"commentCount":0,"image":{"@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#primaryimage"},"thumbnailUrl":"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png","keywords":["Microsoft SharePoint","repair SharePoint database","restore farm configuration","restore SharePoint Server","SharePoint benefits","SharePoint Server","SharePoint server recovery"],"articleSection":["Data Recovery"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/","url":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/","name":"SharePoint Server Recovery - Mistakes You Should Avoid","isPartOf":{"@id":"https:\/\/wordpress.semnaitik.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#primaryimage"},"image":{"@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#primaryimage"},"thumbnailUrl":"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png","datePublished":"2017-03-10T12:14:00+00:00","dateModified":"2025-01-25T09:26:45+00:00","author":{"@id":"https:\/\/wordpress.semnaitik.com\/blog\/#\/schema\/person\/2a69018b8418db3a31ca2d0a0a3e2c77"},"description":"There are various reasons which cause corruption in SharePoint. You must know their fix to resolve corruption. Read here for SharePoint Server recovery","breadcrumb":{"@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#primaryimage","url":"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png","contentUrl":"https:\/\/wordpress.semnaitik.com\/blog\/wp-content\/uploads\/2017\/03\/sharepoint-server-recovery.png","width":678,"height":381,"caption":"SharePoint server recovery"},{"@type":"BreadcrumbList","@id":"https:\/\/wordpress.semnaitik.com\/blog\/sharepoint-server-recovery\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/wordpress.semnaitik.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SharePoint Server Recovery &#8211; Mistakes You Should Avoid"}]},{"@type":"WebSite","@id":"https:\/\/wordpress.semnaitik.com\/blog\/#website","url":"https:\/\/wordpress.semnaitik.com\/blog\/","name":"","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/wordpress.semnaitik.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/wordpress.semnaitik.com\/blog\/#\/schema\/person\/2a69018b8418db3a31ca2d0a0a3e2c77","name":"Danish","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/be8cb8e17fe5afcda9b1aeea9726aaedbd8e1a8c1418f44f8b6ebc679cc527b4?s=96&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/be8cb8e17fe5afcda9b1aeea9726aaedbd8e1a8c1418f44f8b6ebc679cc527b4?s=96&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/be8cb8e17fe5afcda9b1aeea9726aaedbd8e1a8c1418f44f8b6ebc679cc527b4?s=96&r=g","caption":"Danish"},"sameAs":["http:\/\/semnaitik.com\/","https:\/\/www.facebook.com\/naitik.semwaal.5"]}]}},"_links":{"self":[{"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/posts\/3593","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/comments?post=3593"}],"version-history":[{"count":4,"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/posts\/3593\/revisions"}],"predecessor-version":[{"id":7792,"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/posts\/3593\/revisions\/7792"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/media\/5759"}],"wp:attachment":[{"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/media?parent=3593"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/categories?post=3593"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.semnaitik.com\/blog\/wp-json\/wp\/v2\/tags?post=3593"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}