ࡱ> 9      i bjbjVV  y <<-;SSSSSDY.!\?}eeeeeeeYte7S---eSSyG!G!G!-FSSeG!-eG!G!JI4S 8sMVne0MBo+o@SNSoSbS --G!-----eeG!-------o--------- :  Operations guide for servers and server farms for Microsoft SharePoint Server 2010 Microsoft Corporation Published: January 2011 Author: Microsoft Office System and Servers Team (itspdocs@microsoft.com) Abstract This book describes how to operate and maintain servers and server farms in a Microsoft SharePoint Server 2010 environment. The audiences for this book include application specialists, line-of-business application specialists, and IT administrators who operate and maintain installations of SharePoint Server 2010. The content in this book is a copy of selected content in the HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=181463"SharePoint Server 2010 technical library (http://go.microsoft.com/fwlink/?LinkId=181463) as of the publication date. For the most current content, see the technical library on the Web.  This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. 2011 Microsoft Corporation. All rights reserved. Microsoft, Access, Active Directory, Backstage, Excel, Groove, Hotmail, InfoPath, Internet Explorer, Outlook, PerformancePoint, PowerPoint, SharePoint, Silverlight, Windows, Windows Live, Windows Mobile, Windows PowerShell, WindowsServer, and WindowsVista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Contents TOC \o "1-3" \h \z \u   HYPERLINK \l "_Toc282771056" Getting help  PAGEREF _Toc282771056 \h xix  HYPERLINK \l "_Toc282771057" Operations for SharePoint Server 2010  PAGEREF _Toc282771057 \h 1  HYPERLINK \l "_Toc282771058" Server and server farm administration (SharePoint Server 2010)  PAGEREF _Toc282771058 \h 2  HYPERLINK \l "_Toc282771059" Backup and recovery (SharePoint Server 2010)  PAGEREF _Toc282771059 \h 3  HYPERLINK \l "_Toc282771060" Prepare to back up and recover (SharePoint Server 2010)  PAGEREF _Toc282771060 \h 4  HYPERLINK \l "_Toc282771061" Restrictions  PAGEREF _Toc282771061 \h 4  HYPERLINK \l "_Toc282771062" Requirements  PAGEREF _Toc282771062 \h 4  HYPERLINK \l "_Toc282771063" How to create a shared folder  PAGEREF _Toc282771063 \h 5  HYPERLINK \l "_Toc282771064" Backup and recovery best practices (SharePoint Server 2010)  PAGEREF _Toc282771064 \h 7  HYPERLINK \l "_Toc282771065" Performance best practices  PAGEREF _Toc282771065 \h 7  HYPERLINK \l "_Toc282771066" Minimize latency between SQL Server and the backup location  PAGEREF _Toc282771066 \h 7  HYPERLINK \l "_Toc282771067" Avoid processing conflicts  PAGEREF _Toc282771067 \h 7  HYPERLINK \l "_Toc282771068" Keep databases small for faster recovery times  PAGEREF _Toc282771068 \h 7  HYPERLINK \l "_Toc282771069" Use incremental backups for large databases  PAGEREF _Toc282771069 \h 8  HYPERLINK \l "_Toc282771070" Use compression during backup  PAGEREF _Toc282771070 \h 8  HYPERLINK \l "_Toc282771071" Follow SQL Server backup and restore optimization recommendations  PAGEREF _Toc282771071 \h 8  HYPERLINK \l "_Toc282771072" Use RAID 10 if you are going to use RAID  PAGEREF _Toc282771072 \h 8  HYPERLINK \l "_Toc282771073" Configure SharePoint settings for better backup or restore performance  PAGEREF _Toc282771073 \h 8  HYPERLINK \l "_Toc282771074" Consider site collection size when determining the tools to use  PAGEREF _Toc282771074 \h 9  HYPERLINK \l "_Toc282771075" Quality assurance best practices  PAGEREF _Toc282771075 \h 9  HYPERLINK \l "_Toc282771076" Ensure you have adequate storage space  PAGEREF _Toc282771076 \h 9  HYPERLINK \l "_Toc282771077" Routinely test backup quality  PAGEREF _Toc282771077 \h 10  HYPERLINK \l "_Toc282771078" Back up ULS trace logs  PAGEREF _Toc282771078 \h 10  HYPERLINK \l "_Toc282771079" Store a copy of backup files off-site  PAGEREF _Toc282771079 \h 10  HYPERLINK \l "_Toc282771080" Procedural best practices  PAGEREF _Toc282771080 \h 10  HYPERLINK \l "_Toc282771081" Use FQDN server names  PAGEREF _Toc282771081 \h 10  HYPERLINK \l "_Toc282771082" Keep accurate records  PAGEREF _Toc282771082 \h 10  HYPERLINK \l "_Toc282771083" Have a recovery environment ready  PAGEREF _Toc282771083 \h 10  HYPERLINK \l "_Toc282771084" Schedule backup operations  PAGEREF _Toc282771084 \h 11  HYPERLINK \l "_Toc282771085" Use the SQL FILESTREAM provider with BLOB storage  PAGEREF _Toc282771085 \h 11  HYPERLINK \l "_Toc282771086" Configuring permissions for backup and recovery (SharePoint Server 2010)  PAGEREF _Toc282771086 \h 12  HYPERLINK \l "_Toc282771087" Permissions for the SPTimerV4 timer service and SQL Server account  PAGEREF _Toc282771087 \h 12  HYPERLINK \l "_Toc282771088" Group memberships required to run backup and restore operations in Central Administration  PAGEREF _Toc282771088 \h 12  HYPERLINK \l "_Toc282771089" Setting permissions for running backup and restore operations by using Windows PowerShell  PAGEREF _Toc282771089 \h 13  HYPERLINK \l "_Toc282771090" Backup (SharePoint Server 2010)  PAGEREF _Toc282771090 \h 15  HYPERLINK \l "_Toc282771091" Back up all or part of a farm  PAGEREF _Toc282771091 \h 15  HYPERLINK \l "_Toc282771092" Back up a farm (SharePoint Server 2010)  PAGEREF _Toc282771092 \h 17  HYPERLINK \l "_Toc282771093" Considerations when backing up a farm  PAGEREF _Toc282771093 \h 17  HYPERLINK \l "_Toc282771094" Task requirements  PAGEREF _Toc282771094 \h 18  HYPERLINK \l "_Toc282771095" Use Windows PowerShell to back up a farm  PAGEREF _Toc282771095 \h 18  HYPERLINK \l "_Toc282771096" Use Central Administration to back up a farm  PAGEREF _Toc282771096 \h 19  HYPERLINK \l "_Toc282771097" Use SQL Server tools to back up a farm  PAGEREF _Toc282771097 \h 20  HYPERLINK \l "_Toc282771098" Related content  PAGEREF _Toc282771098 \h 20  HYPERLINK \l "_Toc282771099" Back up a farm configuration (SharePoint Server 2010)  PAGEREF _Toc282771099 \h 22  HYPERLINK \l "_Toc282771100" Task requirements  PAGEREF _Toc282771100 \h 22  HYPERLINK \l "_Toc282771101" Use Windows PowerShell to back up a farm configuration  PAGEREF _Toc282771101 \h 23  HYPERLINK \l "_Toc282771102" Use Central Administration to back up a farm configuration  PAGEREF _Toc282771102 \h 24  HYPERLINK \l "_Toc282771103" Back up a Web application (SharePoint Server 2010)  PAGEREF _Toc282771103 \h 25  HYPERLINK \l "_Toc282771104" Considerations when backing up a Web application  PAGEREF _Toc282771104 \h 25  HYPERLINK \l "_Toc282771105" Task requirements  PAGEREF _Toc282771105 \h 26  HYPERLINK \l "_Toc282771106" Use Windows PowerShell to back up a Web application  PAGEREF _Toc282771106 \h 26  HYPERLINK \l "_Toc282771107" Use Central Administration to back up a Web application  PAGEREF _Toc282771107 \h 27  HYPERLINK \l "_Toc282771108" Use SQL Server tools to back up a Web application  PAGEREF _Toc282771108 \h 28  HYPERLINK \l "_Toc282771109" Related content  PAGEREF _Toc282771109 \h 28  HYPERLINK \l "_Toc282771110" Back up a service application (SharePoint Server 2010)  PAGEREF _Toc282771110 \h 30  HYPERLINK \l "_Toc282771111" Task requirements  PAGEREF _Toc282771111 \h 30  HYPERLINK \l "_Toc282771112" Use Windows PowerShell to back up a service application  PAGEREF _Toc282771112 \h 31  HYPERLINK \l "_Toc282771113" Use Central Administration to back up a service application  PAGEREF _Toc282771113 \h 32  HYPERLINK \l "_Toc282771114" Back up search (SharePoint Server 2010)  PAGEREF _Toc282771114 \h 33  HYPERLINK \l "_Toc282771115" Task requirements  PAGEREF _Toc282771115 \h 33  HYPERLINK \l "_Toc282771116" Use Windows PowerShell to back up search  PAGEREF _Toc282771116 \h 33  HYPERLINK \l "_Toc282771117" Use Central Administration to back up search  PAGEREF _Toc282771117 \h 34  HYPERLINK \l "_Toc282771118" Back up the Secure Store service (SharePoint Server 2010)  PAGEREF _Toc282771118 \h 36  HYPERLINK \l "_Toc282771119" Task requirements  PAGEREF _Toc282771119 \h 36  HYPERLINK \l "_Toc282771120" Use Windows PowerShell to back up the Secure Store Service  PAGEREF _Toc282771120 \h 37  HYPERLINK \l "_Toc282771121" Use Central Administration to back up the Secure Store Service  PAGEREF _Toc282771121 \h 37  HYPERLINK \l "_Toc282771122" Back up a content database (SharePoint Server 2010)  PAGEREF _Toc282771122 \h 39  HYPERLINK \l "_Toc282771123" Task requirements  PAGEREF _Toc282771123 \h 39  HYPERLINK \l "_Toc282771124" Use Windows PowerShell to back up a content database  PAGEREF _Toc282771124 \h 40  HYPERLINK \l "_Toc282771125" Use Central Administration to back up a content database  PAGEREF _Toc282771125 \h 40  HYPERLINK \l "_Toc282771126" Use SQL Server tools to back up a content database  PAGEREF _Toc282771126 \h 41  HYPERLINK \l "_Toc282771127" Back up databases to snapshots (SharePoint Server 2010)  PAGEREF _Toc282771127 \h 43  HYPERLINK \l "_Toc282771128" Task requirements  PAGEREF _Toc282771128 \h 43  HYPERLINK \l "_Toc282771129" Use SQL Server tools to back up a database to a snapshot  PAGEREF _Toc282771129 \h 43  HYPERLINK \l "_Toc282771130" Back up customizations (SharePoint Server 2010)  PAGEREF _Toc282771130 \h 45  HYPERLINK \l "_Toc282771131" Backing up solution packages  PAGEREF _Toc282771131 \h 46  HYPERLINK \l "_Toc282771132" Backing up sandboxed solutions  PAGEREF _Toc282771132 \h 47  HYPERLINK \l "_Toc282771133" Backing up authored site elements  PAGEREF _Toc282771133 \h 47  HYPERLINK \l "_Toc282771134" Backing up workflows  PAGEREF _Toc282771134 \h 48  HYPERLINK \l "_Toc282771135" Backing up changes to the Web.config file  PAGEREF _Toc282771135 \h 48  HYPERLINK \l "_Toc282771136" Backing up third-party products  PAGEREF _Toc282771136 \h 49  HYPERLINK \l "_Toc282771137" Backing up changes made by direct editing  PAGEREF _Toc282771137 \h 49  HYPERLINK \l "_Toc282771138" Backing up developed customizations that are not packaged as solutions  PAGEREF _Toc282771138 \h 49  HYPERLINK \l "_Toc282771139" Related content  PAGEREF _Toc282771139 \h 50  HYPERLINK \l "_Toc282771140" Back up a site collection (SharePoint Server 2010)  PAGEREF _Toc282771140 \h 51  HYPERLINK \l "_Toc282771141" Task requirements  PAGEREF _Toc282771141 \h 51  HYPERLINK \l "_Toc282771142" Use Windows PowerShell to back up a site collection  PAGEREF _Toc282771142 \h 51  HYPERLINK \l "_Toc282771143" Use Central Administration to back up a site collection  PAGEREF _Toc282771143 \h 53  HYPERLINK \l "_Toc282771144" Export a site, list, or document library (SharePoint Server 2010)  PAGEREF _Toc282771144 \h 54  HYPERLINK \l "_Toc282771145" Task requirements  PAGEREF _Toc282771145 \h 54  HYPERLINK \l "_Toc282771146" Use Windows PowerShell to export a site, list, or document library  PAGEREF _Toc282771146 \h 54  HYPERLINK \l "_Toc282771147" Use Central Administration to export a site, list, or document library  PAGEREF _Toc282771147 \h 55  HYPERLINK \l "_Toc282771148" Back up or archive logs (SharePoint Server 2010)  PAGEREF _Toc282771148 \h 57  HYPERLINK \l "_Toc282771149" [Essential] Back up transaction logs  PAGEREF _Toc282771149 \h 57  HYPERLINK \l "_Toc282771150" How transaction log size affects farm backup times  PAGEREF _Toc282771150 \h 58  HYPERLINK \l "_Toc282771151" [Recommended] Collect usage data  PAGEREF _Toc282771151 \h 58  HYPERLINK \l "_Toc282771152" [Recommended] Archive diagnostic logs  PAGEREF _Toc282771152 \h 58  HYPERLINK \l "_Toc282771153" Recovery (SharePoint Server 2010)  PAGEREF _Toc282771153 \h 61  HYPERLINK \l "_Toc282771154" Recover all or part of a farm  PAGEREF _Toc282771154 \h 61  HYPERLINK \l "_Toc282771155" Restore a farm (SharePoint Server 2010)  PAGEREF _Toc282771155 \h 64  HYPERLINK \l "_Toc282771156" Considerations when recovering a farm  PAGEREF _Toc282771156 \h 64  HYPERLINK \l "_Toc282771157" Use Windows PowerShell to restore a farm  PAGEREF _Toc282771157 \h 66  HYPERLINK \l "_Toc282771158" Use Central Administration to restore a farm  PAGEREF _Toc282771158 \h 67  HYPERLINK \l "_Toc282771159" Use SQL Server tools to restore a farm  PAGEREF _Toc282771159 \h 68  HYPERLINK \l "_Toc282771160" Related content  PAGEREF _Toc282771160 \h 69  HYPERLINK \l "_Toc282771161" Restore a farm configuration (SharePoint Server 2010)  PAGEREF _Toc282771161 \h 71  HYPERLINK \l "_Toc282771162" Overview  PAGEREF _Toc282771162 \h 71  HYPERLINK \l "_Toc282771163" Use Windows PowerShell to restore a farms configuration  PAGEREF _Toc282771163 \h 71  HYPERLINK \l "_Toc282771164" Use Central Administration to restore a farms configuration  PAGEREF _Toc282771164 \h 72  HYPERLINK \l "_Toc282771165" Use SQL Server to restore a farm's configuration  PAGEREF _Toc282771165 \h 73  HYPERLINK \l "_Toc282771166" Document farm configuration settings (SharePoint Server 2010)  PAGEREF _Toc282771166 \h 74  HYPERLINK \l "_Toc282771167" Example of using a cmdlet  PAGEREF _Toc282771167 \h 84  HYPERLINK \l "_Toc282771168" Copy configuration settings from one farm to another (SharePoint Server 2010)  PAGEREF _Toc282771168 \h 87  HYPERLINK \l "_Toc282771169" Back up and recover a farm without content databases to copy configuration settings  PAGEREF _Toc282771169 \h 87  HYPERLINK \l "_Toc282771170" Back up and recover configuration settings only  PAGEREF _Toc282771170 \h 88  HYPERLINK \l "_Toc282771171" Create a scripted deployment to copy configuration settings  PAGEREF _Toc282771171 \h 89  HYPERLINK \l "_Toc282771172" Restore a Web application (SharePoint Server 2010)  PAGEREF _Toc282771172 \h 90  HYPERLINK \l "_Toc282771173" Considerations when backing up a Web application  PAGEREF _Toc282771173 \h 90  HYPERLINK \l "_Toc282771174" Use Windows PowerShell to restore a Web application  PAGEREF _Toc282771174 \h 90  HYPERLINK \l "_Toc282771175" Use Central Administration to restore a Web application  PAGEREF _Toc282771175 \h 91  HYPERLINK \l "_Toc282771176" Additional steps to restore a Web application that uses forms-based authentication  PAGEREF _Toc282771176 \h 92  HYPERLINK \l "_Toc282771177" Additional steps to remove duplicate claims providers after restoring a Web application that uses claims-based authentication  PAGEREF _Toc282771177 \h 93  HYPERLINK \l "_Toc282771178" Related content  PAGEREF _Toc282771178 \h 93  HYPERLINK \l "_Toc282771179" Restore a service application (SharePoint Server 2010)  PAGEREF _Toc282771179 \h 94  HYPERLINK \l "_Toc282771180" Use Windows PowerShell to restore a service application  PAGEREF _Toc282771180 \h 95  HYPERLINK \l "_Toc282771181" Use Central Administration to restore a service application  PAGEREF _Toc282771181 \h 95  HYPERLINK \l "_Toc282771182" Use SQL Server tools to restore the databases for a service application  PAGEREF _Toc282771182 \h 96  HYPERLINK \l "_Toc282771183" Restore search (SharePoint Server 2010)  PAGEREF _Toc282771183 \h 98  HYPERLINK \l "_Toc282771184" Use Windows PowerShell to restore a search service application  PAGEREF _Toc282771184 \h 98  HYPERLINK \l "_Toc282771185" Use Central Administration to restore a search service application  PAGEREF _Toc282771185 \h 99  HYPERLINK \l "_Toc282771186" Restore secure store services (SharePoint Server 2010)  PAGEREF _Toc282771186 \h 101  HYPERLINK \l "_Toc282771187" Use Central Administration to restore the Secure Store Service  PAGEREF _Toc282771187 \h 101  HYPERLINK \l "_Toc282771188" Use Windows PowerShell to restore the Secure Store Service  PAGEREF _Toc282771188 \h 102  HYPERLINK \l "_Toc282771189" Restore a content database (SharePoint Server 2010)  PAGEREF _Toc282771189 \h 104  HYPERLINK \l "_Toc282771190" Use Windows PowerShell to restore a content database  PAGEREF _Toc282771190 \h 104  HYPERLINK \l "_Toc282771191" Use Central Administration to restore a content database  PAGEREF _Toc282771191 \h 105  HYPERLINK \l "_Toc282771192" Use SQL Server tools to restore a content database  PAGEREF _Toc282771192 \h 106  HYPERLINK \l "_Toc282771193" Attach and restore a read-only content database (SharePoint Server 2010)  PAGEREF _Toc282771193 \h 108  HYPERLINK \l "_Toc282771194" Use Windows PowerShell to attach and restore a read-only content database  PAGEREF _Toc282771194 \h 108  HYPERLINK \l "_Toc282771195" Restore customizations (SharePoint Server 2010)  PAGEREF _Toc282771195 \h 109  HYPERLINK \l "_Toc282771196" Restoring solution packages  PAGEREF _Toc282771196 \h 109  HYPERLINK \l "_Toc282771197" Restoring a sandboxed solution  PAGEREF _Toc282771197 \h 111  HYPERLINK \l "_Toc282771198" Restoring authored site elements  PAGEREF _Toc282771198 \h 111  HYPERLINK \l "_Toc282771199" Restoring workflows  PAGEREF _Toc282771199 \h 111  HYPERLINK \l "_Toc282771200" Restoring changes to the Web.config file  PAGEREF _Toc282771200 \h 112  HYPERLINK \l "_Toc282771201" Recovering changes made by direct editing  PAGEREF _Toc282771201 \h 112  HYPERLINK \l "_Toc282771202" Restoring developed customizations that are not packaged as solutions  PAGEREF _Toc282771202 \h 113  HYPERLINK \l "_Toc282771203" Related content  PAGEREF _Toc282771203 \h 113  HYPERLINK \l "_Toc282771204" Restore a site collection (SharePoint Server 2010)  PAGEREF _Toc282771204 \h 114  HYPERLINK \l "_Toc282771205" Use Windows PowerShell to restore a site collection  PAGEREF _Toc282771205 \h 114  HYPERLINK \l "_Toc282771206" Import a list or document library (SharePoint Server 2010)  PAGEREF _Toc282771206 \h 116  HYPERLINK \l "_Toc282771207" Import a site, list or document library  PAGEREF _Toc282771207 \h 116  HYPERLINK \l "_Toc282771208" Database management (SharePoint Server 2010)  PAGEREF _Toc282771208 \h 118  HYPERLINK \l "_Toc282771209" Add a content database (SharePoint Server 2010)  PAGEREF _Toc282771209 \h 120  HYPERLINK \l "_Toc282771210" Attach or detach content databases (SharePoint Server 2010)  PAGEREF _Toc282771210 \h 122  HYPERLINK \l "_Toc282771211" Move site collections between databases (SharePoint Server 2010)  PAGEREF _Toc282771211 \h 126  HYPERLINK \l "_Toc282771212" Determining the size of the source site collection  PAGEREF _Toc282771212 \h 127  HYPERLINK \l "_Toc282771213" Moving site collections between content databases  PAGEREF _Toc282771213 \h 127  HYPERLINK \l "_Toc282771214" Move content databases (SharePoint Server 2010)  PAGEREF _Toc282771214 \h 129  HYPERLINK \l "_Toc282771215" Overview of moving content databases  PAGEREF _Toc282771215 \h 129  HYPERLINK \l "_Toc282771216" Moving content databases  PAGEREF _Toc282771216 \h 130  HYPERLINK \l "_Toc282771217" Rename or move service application databases (SharePoint Server 2010)  PAGEREF _Toc282771217 \h 136  HYPERLINK \l "_Toc282771218" Renaming or moving service application databases by using SQL Server  PAGEREF _Toc282771218 \h 139  HYPERLINK \l "_Toc282771219" Move a database by using SQL Server Management Studio and Windows Explorer  PAGEREF _Toc282771219 \h 140  HYPERLINK \l "_Toc282771220" General method for pointing a service application to a renamed or moved database  PAGEREF _Toc282771220 \h 140  HYPERLINK \l "_Toc282771221" Service application-specific guidance for renaming or moving databases  PAGEREF _Toc282771221 \h 142  HYPERLINK \l "_Toc282771222" Pointing the Usage and Health Data Collection service application to a renamed or moved database  PAGEREF _Toc282771222 \h 142  HYPERLINK \l "_Toc282771223" Pointing the Search service application to renamed or moved databases  PAGEREF _Toc282771223 \h 143  HYPERLINK \l "_Toc282771224" Pointing the Web Analytics service application to renamed or moved databases  PAGEREF _Toc282771224 \h 145  HYPERLINK \l "_Toc282771225" Pointing the State Service service application to a renamed or moved database  PAGEREF _Toc282771225 \h 147  HYPERLINK \l "_Toc282771226" Pointing the Managed Metadata service application to a renamed or moved database  PAGEREF _Toc282771226 \h 148  HYPERLINK \l "_Toc282771227" Pointing the Word Automation service application to a renamed or moved database  PAGEREF _Toc282771227 \h 149  HYPERLINK \l "_Toc282771228" Pointing the Secure Store service application to a renamed or moved database  PAGEREF _Toc282771228 \h 150  HYPERLINK \l "_Toc282771229" Pointing the Business Data Connectivity service application to a renamed or moved database  PAGEREF _Toc282771229 \h 151  HYPERLINK \l "_Toc282771230" Pointing the Application Registry service application to a renamed or moved database  PAGEREF _Toc282771230 \h 151  HYPERLINK \l "_Toc282771231" Pointing the User Profile service application to renamed or moved databases  PAGEREF _Toc282771231 \h 151  HYPERLINK \l "_Toc282771232" Pointing the PerformancePoint service application to a renamed or moved database  PAGEREF _Toc282771232 \h 151  HYPERLINK \l "_Toc282771233" Pointing the Subscription Settings service application to a renamed or moved database  PAGEREF _Toc282771233 \h 152  HYPERLINK \l "_Toc282771234" Move all databases (SharePoint Server 2010)  PAGEREF _Toc282771234 \h 154  HYPERLINK \l "_Toc282771235" Moving all databases  PAGEREF _Toc282771235 \h 154  HYPERLINK \l "_Toc282771236" Run a farm that uses read-only databases (SharePoint Server 2010)  PAGEREF _Toc282771236 \h 160  HYPERLINK \l "_Toc282771237" Prepare users for the read-only experience  PAGEREF _Toc282771237 \h 160  HYPERLINK \l "_Toc282771238" Sites that use read-only content databases  PAGEREF _Toc282771238 \h 160  HYPERLINK \l "_Toc282771239" Farms that use read-only service application databases  PAGEREF _Toc282771239 \h 161  HYPERLINK \l "_Toc282771240" Set content databases to be read-only  PAGEREF _Toc282771240 \h 161  HYPERLINK \l "_Toc282771241" Set service application databases to be read-only  PAGEREF _Toc282771241 \h 162  HYPERLINK \l "_Toc282771242" Manage Remote BLOB Storage (SharePoint Server 2010)  PAGEREF _Toc282771242 \h 164  HYPERLINK \l "_Toc282771243" In This Section  PAGEREF _Toc282771243 \h 164  HYPERLINK \l "_Toc282771244" Overview of Remote BLOB Storage (SharePoint Server 2010)  PAGEREF _Toc282771244 \h 165  HYPERLINK \l "_Toc282771245" Introduction to RBS  PAGEREF _Toc282771245 \h 165  HYPERLINK \l "_Toc282771246" Using RBS together with SharePoint 2010 Products  PAGEREF _Toc282771246 \h 166  HYPERLINK \l "_Toc282771247" Install and configure Remote BLOB Storage (RBS) with the FILESTREAM provider (SharePoint Server 2010)  PAGEREF _Toc282771247 \h 168  HYPERLINK \l "_Toc282771248" Enable FILESTREAM and provision the RBS data store  PAGEREF _Toc282771248 \h 168  HYPERLINK \l "_Toc282771249" Install RBS  PAGEREF _Toc282771249 \h 169  HYPERLINK \l "_Toc282771250" Enable and test RBS  PAGEREF _Toc282771250 \h 171  HYPERLINK \l "_Toc282771251" Install and configure Remote BLOB Storage (RBS) without the FILESTREAM provider (SharePoint Server 2010)  PAGEREF _Toc282771251 \h 173  HYPERLINK \l "_Toc282771252" Install RBS  PAGEREF _Toc282771252 \h 174  HYPERLINK \l "_Toc282771253" Enable and test RBS  PAGEREF _Toc282771253 \h 175  HYPERLINK \l "_Toc282771254" Set a content database to use Remote BLOB Storage (RBS) (SharePoint Server 2010)  PAGEREF _Toc282771254 \h 177  HYPERLINK \l "_Toc282771255" Set a content database to use RBS  PAGEREF _Toc282771255 \h 177  HYPERLINK \l "_Toc282771256" Migrate content into or out of Remote BLOB Storage (RBS) (SharePoint Server 2010)  PAGEREF _Toc282771256 \h 180  HYPERLINK \l "_Toc282771257" Maintain Remote BLOB Storage (RBS) (SharePoint Server 2010)  PAGEREF _Toc282771257 \h 182  HYPERLINK \l "_Toc282771258" Garbage collection  PAGEREF _Toc282771258 \h 182  HYPERLINK \l "_Toc282771259" Configuring RBS garbage collection  PAGEREF _Toc282771259 \h 183  HYPERLINK \l "_Toc282771260" RBS and BLOB store consistency checks  PAGEREF _Toc282771260 \h 183  HYPERLINK \l "_Toc282771261" Running the RBS Maintainer  PAGEREF _Toc282771261 \h 183  HYPERLINK \l "_Toc282771262" Disable Remote BLOB Storage (RBS) on a content database (SharePoint Server 2010)  PAGEREF _Toc282771262 \h 188  HYPERLINK \l "_Toc282771263" Security and permissions (SharePoint Server 2010)  PAGEREF _Toc282771263 \h 189  HYPERLINK \l "_Toc282771264" Configure custom permissions (SharePoint Server 2010)  PAGEREF _Toc282771264 \h 190  HYPERLINK \l "_Toc282771265" Customize an existing permission level  PAGEREF _Toc282771265 \h 190  HYPERLINK \l "_Toc282771266" Copy an existing permission level  PAGEREF _Toc282771266 \h 191  HYPERLINK \l "_Toc282771267" Create a permission level  PAGEREF _Toc282771267 \h 191  HYPERLINK \l "_Toc282771268" Change passwords used for administration accounts (SharePoint Server 2010)  PAGEREF _Toc282771268 \h 193  HYPERLINK \l "_Toc282771269" Configure automatic password change (SharePoint Server 2010)  PAGEREF _Toc282771269 \h 195  HYPERLINK \l "_Toc282771270" Configure managed accounts  PAGEREF _Toc282771270 \h 195  HYPERLINK \l "_Toc282771271" Configure automatic password change settings  PAGEREF _Toc282771271 \h 196  HYPERLINK \l "_Toc282771272" Troubleshooting automatic password change  PAGEREF _Toc282771272 \h 196  HYPERLINK \l "_Toc282771273" Password mismatch  PAGEREF _Toc282771273 \h 196  HYPERLINK \l "_Toc282771274" Service account provisioning failure  PAGEREF _Toc282771274 \h 197  HYPERLINK \l "_Toc282771275" Imminent password expiration  PAGEREF _Toc282771275 \h 198  HYPERLINK \l "_Toc282771276" Requirement to change the farm account to a different account  PAGEREF _Toc282771276 \h 198  HYPERLINK \l "_Toc282771277" Change passwords for SQL Server services (SharePoint Server 2010)  PAGEREF _Toc282771277 \h 199  HYPERLINK \l "_Toc282771278" Change the password for the SQL Server service  PAGEREF _Toc282771278 \h 199  HYPERLINK \l "_Toc282771279" To change the password for the SQL Server Agent service  PAGEREF _Toc282771279 \h 200  HYPERLINK \l "_Toc282771280" Change the password for the default content access account (SharePoint Server 2010)  PAGEREF _Toc282771280 \h 201  HYPERLINK \l "_Toc282771281" Change the password for the default content access account  PAGEREF _Toc282771281 \h 201  HYPERLINK \l "_Toc282771282" Service application and service management (SharePoint Server 2010)  PAGEREF _Toc282771282 \h 202  HYPERLINK \l "_Toc282771283" In This Section  PAGEREF _Toc282771283 \h 202  HYPERLINK \l "_Toc282771284" About service applications and services (SharePoint Server 2010)  PAGEREF _Toc282771284 \h 203  HYPERLINK \l "_Toc282771285" Manage service applications (SharePoint Server 2010)  PAGEREF _Toc282771285 \h 204  HYPERLINK \l "_Toc282771286" Share service applications across farms (SharePoint Server 2010)  PAGEREF _Toc282771286 \h 206  HYPERLINK \l "_Toc282771287" Exchange trust certificates between farms (SharePoint Server 2010)  PAGEREF _Toc282771287 \h 208  HYPERLINK \l "_Toc282771288" Exporting and copying certificates  PAGEREF _Toc282771288 \h 208  HYPERLINK \l "_Toc282771289" Managing trust certificates by using Windows Powershell  PAGEREF _Toc282771289 \h 210  HYPERLINK \l "_Toc282771290" Establishing trust on the consuming farm  PAGEREF _Toc282771290 \h 210  HYPERLINK \l "_Toc282771291" Establishing trust on the publishing farm  PAGEREF _Toc282771291 \h 210  HYPERLINK \l "_Toc282771292" Managing trust certificates by using Central Administration  PAGEREF _Toc282771292 \h 211  HYPERLINK \l "_Toc282771293" Publish a service application (SharePoint Server 2010)  PAGEREF _Toc282771293 \h 213  HYPERLINK \l "_Toc282771294" Set permission to a published service application (SharePoint Server)  PAGEREF _Toc282771294 \h 215  HYPERLINK \l "_Toc282771295" Set permission to the Application Discovery and Load Balancing Service Application and any other service application for a consuming farm by using Windows PowerShell  PAGEREF _Toc282771295 \h 215  HYPERLINK \l "_Toc282771296" Set permission to the Application Discovery and Load Balancing Service Application and any other published service application for a consuming farm by using Central Administration  PAGEREF _Toc282771296 \h 218  HYPERLINK \l "_Toc282771297" Connect to a service application on a remote farm (SharePoint Server 2010)  PAGEREF _Toc282771297 \h 219  HYPERLINK \l "_Toc282771298" Add or remove a service application connection to a Web application (SharePoint Server 2010)  PAGEREF _Toc282771298 \h 222  HYPERLINK \l "_Toc282771299" Editing a service connection group  PAGEREF _Toc282771299 \h 222  HYPERLINK \l "_Toc282771300" Restrict or enable access to a service application (SharePoint Server 2010)  PAGEREF _Toc282771300 \h 225  HYPERLINK \l "_Toc282771301" Restricting access to a service application  PAGEREF _Toc282771301 \h 225  HYPERLINK \l "_Toc282771302" Restrict access to a service application by using Central Administration  PAGEREF _Toc282771302 \h 226  HYPERLINK \l "_Toc282771303" Restore farm-wide access to a service application  PAGEREF _Toc282771303 \h 230  HYPERLINK \l "_Toc282771304" Windows PowerShell code examples  PAGEREF _Toc282771304 \h 232  HYPERLINK \l "_Toc282771305" Assign or remove administrators to a service application (SharePoint Server 2010)  PAGEREF _Toc282771305 \h 234  HYPERLINK \l "_Toc282771306" Delete a service application (SharePoint Server 2010)  PAGEREF _Toc282771306 \h 236  HYPERLINK \l "_Toc282771307" Example  PAGEREF _Toc282771307 \h 237  HYPERLINK \l "_Toc282771308" Access Services administration  PAGEREF _Toc282771308 \h 239  HYPERLINK \l "_Toc282771309" Using Access Services with SQL Reporting Services: Installing SQL Server 2008 R2 Reporting Services Add-In (SharePoint Server 2010)  PAGEREF _Toc282771309 \h 240  HYPERLINK \l "_Toc282771310" Business Data Connectivity service administration (SharePoint Server 2010)  PAGEREF _Toc282771310 \h 243  HYPERLINK \l "_Toc282771311" Manage external systems (SharePoint Server 2010)  PAGEREF _Toc282771311 \h 244  HYPERLINK \l "_Toc282771312" Set permissions on an external system  PAGEREF _Toc282771312 \h 244  HYPERLINK \l "_Toc282771313" View all external systems for a Business Data Connectivity service application instance  PAGEREF _Toc282771313 \h 246  HYPERLINK \l "_Toc282771314" Delete an external system  PAGEREF _Toc282771314 \h 246  HYPERLINK \l "_Toc282771315" View the external content types of an external system  PAGEREF _Toc282771315 \h 247  HYPERLINK \l "_Toc282771316" Configure an external system  PAGEREF _Toc282771316 \h 247  HYPERLINK \l "_Toc282771317" Configure an instance of an external system  PAGEREF _Toc282771317 \h 250  HYPERLINK \l "_Toc282771318" Manage BDC models (SharePoint Server 2010)  PAGEREF _Toc282771318 \h 255  HYPERLINK \l "_Toc282771319" Import a BDC model  PAGEREF _Toc282771319 \h 255  HYPERLINK \l "_Toc282771320" Export a BDC model or resource file  PAGEREF _Toc282771320 \h 257  HYPERLINK \l "_Toc282771321" Set permissions on a BDC model  PAGEREF _Toc282771321 \h 258  HYPERLINK \l "_Toc282771322" View all models  PAGEREF _Toc282771322 \h 259  HYPERLINK \l "_Toc282771323" Delete a BDC model  PAGEREF _Toc282771323 \h 260  HYPERLINK \l "_Toc282771324" View a models external content types  PAGEREF _Toc282771324 \h 260  HYPERLINK \l "_Toc282771325" Manage external content types (SharePoint Server 2010)  PAGEREF _Toc282771325 \h 262  HYPERLINK \l "_Toc282771326" Set permissions on an external content type  PAGEREF _Toc282771326 \h 263  HYPERLINK \l "_Toc282771327" View all external content types for an instance of a Business Data Connectivity service application  PAGEREF _Toc282771327 \h 264  HYPERLINK \l "_Toc282771328" View all external content types contained in a model  PAGEREF _Toc282771328 \h 264  HYPERLINK \l "_Toc282771329" View details of an external content type  PAGEREF _Toc282771329 \h 265  HYPERLINK \l "_Toc282771330" Delete an external content type  PAGEREF _Toc282771330 \h 265  HYPERLINK \l "_Toc282771331" Add an action to an external content type  PAGEREF _Toc282771331 \h 266  HYPERLINK \l "_Toc282771332" Specify the profile page host for a Business Data Connectivity service application instance  PAGEREF _Toc282771332 \h 268  HYPERLINK \l "_Toc282771333" Create or update a profile page for an external content type  PAGEREF _Toc282771333 \h 268  HYPERLINK \l "_Toc282771334" Create external content types using SharePoint Designer 2010  PAGEREF _Toc282771334 \h 270  HYPERLINK \l "_Toc282771335" About the author  PAGEREF _Toc282771335 \h 270  HYPERLINK \l "_Toc282771336" Related resources  PAGEREF _Toc282771336 \h 270  HYPERLINK \l "_Toc282771337" Excel Services administration (SharePoint Server 2010)  PAGEREF _Toc282771337 \h 272  HYPERLINK \l "_Toc282771338" Manage Excel Services custom applications (SharePoint Server 2010)  PAGEREF _Toc282771338 \h 273  HYPERLINK \l "_Toc282771339" UDFs  PAGEREF _Toc282771339 \h 273  HYPERLINK \l "_Toc282771340" ECMAScript  PAGEREF _Toc282771340 \h 274  HYPERLINK \l "_Toc282771341" REST API  PAGEREF _Toc282771341 \h 275  HYPERLINK \l "_Toc282771342" Managed metadata administration (SharePoint Server 2010)  PAGEREF _Toc282771342 \h 276  HYPERLINK \l "_Toc282771343" Create, update, publish, or delete a managed metadata service application (SharePoint Server 2010)  PAGEREF _Toc282771343 \h 277  HYPERLINK \l "_Toc282771344" Task Requirements  PAGEREF _Toc282771344 \h 277  HYPERLINK \l "_Toc282771345" Create a managed metadata service application  PAGEREF _Toc282771345 \h 277  HYPERLINK \l "_Toc282771346" Update a managed metadata service application  PAGEREF _Toc282771346 \h 280  HYPERLINK \l "_Toc282771347" Publish a managed metadata service application  PAGEREF _Toc282771347 \h 282  HYPERLINK \l "_Toc282771348" Delete a managed metadata service application  PAGEREF _Toc282771348 \h 282  HYPERLINK \l "_Toc282771349" Create, update, or delete a managed metadata service connection (SharePoint Server 2010)  PAGEREF _Toc282771349 \h 284  HYPERLINK \l "_Toc282771350" Task Requirements  PAGEREF _Toc282771350 \h 284  HYPERLINK \l "_Toc282771351" Create a managed metadata service connection  PAGEREF _Toc282771351 \h 284  HYPERLINK \l "_Toc282771352" Update a managed metadata service connection  PAGEREF _Toc282771352 \h 286  HYPERLINK \l "_Toc282771353" Delete a managed metadata service connection  PAGEREF _Toc282771353 \h 288  HYPERLINK \l "_Toc282771354" Add and remove term store administrators (SharePoint Server 2010)  PAGEREF _Toc282771354 \h 289  HYPERLINK \l "_Toc282771355" Task Requirements  PAGEREF _Toc282771355 \h 289  HYPERLINK \l "_Toc282771356" Add a term store administrator  PAGEREF _Toc282771356 \h 289  HYPERLINK \l "_Toc282771357" Remove a term store administrator  PAGEREF _Toc282771357 \h 290  HYPERLINK \l "_Toc282771358" PerformancePoint Services administration  PAGEREF _Toc282771358 \h 292  HYPERLINK \l "_Toc282771359" Import Wizard: PerformancePoint Server 2007 content to SharePoint Server 2010  PAGEREF _Toc282771359 \h 293  HYPERLINK \l "_Toc282771360" Import PerformancePoint Dashboard 2010 content from a SharePoint Server 2010 server, site, or list  PAGEREF _Toc282771360 \h 295  HYPERLINK \l "_Toc282771361" Import PerformancePoint Dashboard content from a SharePoint Server 2010 server, site, or list  PAGEREF _Toc282771361 \h 295  HYPERLINK \l "_Toc282771362" Create a PerformancePoint Services service application (SharePoint Server 2010)  PAGEREF _Toc282771362 \h 297  HYPERLINK \l "_Toc282771363" Overview  PAGEREF _Toc282771363 \h 297  HYPERLINK \l "_Toc282771364" Create a PerformancePoint Services service application by using the Farm Configuration wizard  PAGEREF _Toc282771364 \h 297  HYPERLINK \l "_Toc282771365" Create a PerformancePoint Services service application by using Central Administration  PAGEREF _Toc282771365 \h 298  HYPERLINK \l "_Toc282771366" Create a PerformancePoint Services service application by using Windows PowerShell  PAGEREF _Toc282771366 \h 299  HYPERLINK \l "_Toc282771367" Delete a PerformancePoint Services service application (SharePoint Server 2010)  PAGEREF _Toc282771367 \h 300  HYPERLINK \l "_Toc282771368" Set up and configure PerformancePoint Services (step-by-step)  PAGEREF _Toc282771368 \h 301  HYPERLINK \l "_Toc282771369" Overview  PAGEREF _Toc282771369 \h 301  HYPERLINK \l "_Toc282771370" Set up the Web application, site collection, and service application  PAGEREF _Toc282771370 \h 302  HYPERLINK \l "_Toc282771371" Manage the State Service (SharePoint Server 2010)  PAGEREF _Toc282771371 \h 306  HYPERLINK \l "_Toc282771372" Configure the State Service  PAGEREF _Toc282771372 \h 306  HYPERLINK \l "_Toc282771373" Configure the State Service by using the Farm Configuration Wizard  PAGEREF _Toc282771373 \h 307  HYPERLINK \l "_Toc282771374" Configure the State Service by using Windows PowerShell  PAGEREF _Toc282771374 \h 307  HYPERLINK \l "_Toc282771375" Monitoring the State Service  PAGEREF _Toc282771375 \h 309  HYPERLINK \l "_Toc282771376" Manage services on the server (SharePoint Server 2010)  PAGEREF _Toc282771376 \h 310  HYPERLINK \l "_Toc282771377" Configuring global settings  PAGEREF _Toc282771377 \h 310  HYPERLINK \l "_Toc282771378" Starting or stopping a service  PAGEREF _Toc282771378 \h 310  HYPERLINK \l "_Toc282771379" Configure Document Conversions Load Balancer and Launcher Services (SharePoint Server 2010)  PAGEREF _Toc282771379 \h 312  HYPERLINK \l "_Toc282771380" Overview  PAGEREF _Toc282771380 \h 312  HYPERLINK \l "_Toc282771381" Use Central Administration to enable the Document Conversions Launcher or Load Balancer services  PAGEREF _Toc282771381 \h 313  HYPERLINK \l "_Toc282771382" Use Central Administration to configure the Document Conversions Launcher Service  PAGEREF _Toc282771382 \h 314  HYPERLINK \l "_Toc282771383" Use Central Administration to configure the Document Conversions Load Balancer service  PAGEREF _Toc282771383 \h 314  HYPERLINK \l "_Toc282771384" Configure global workflow settings (SharePoint Server 2010)  PAGEREF _Toc282771384 \h 316  HYPERLINK \l "_Toc282771385" Enable or disable declarative workflows (SharePoint Server 2010)  PAGEREF _Toc282771385 \h 317  HYPERLINK \l "_Toc282771386" Allow non-authenticated users to participate in workflows (SharePoint Server 2010)  PAGEREF _Toc282771386 \h 318  HYPERLINK \l "_Toc282771387" Allow non-authenticated users to participate in workflows  PAGEREF _Toc282771387 \h 318  HYPERLINK \l "_Toc282771388" Disable preservation of workflow history (SharePoint Server 2010)  PAGEREF _Toc282771388 \h 320  HYPERLINK \l "_Toc282771389" Disable automatic workflow cleanup  PAGEREF _Toc282771389 \h 320  HYPERLINK \l "_Toc282771390" Manage the State Service (SharePoint Server 2010)  PAGEREF _Toc282771390 \h 322  HYPERLINK \l "_Toc282771391" Configure the State Service  PAGEREF _Toc282771391 \h 322  HYPERLINK \l "_Toc282771392" Configure the State Service by using the Farm Configuration Wizard  PAGEREF _Toc282771392 \h 323  HYPERLINK \l "_Toc282771393" Configure the State Service by using Windows PowerShell  PAGEREF _Toc282771393 \h 323  HYPERLINK \l "_Toc282771394" Monitoring the State Service  PAGEREF _Toc282771394 \h 325  HYPERLINK \l "_Toc282771395" Web applications management (SharePoint Server 2010)  PAGEREF _Toc282771395 \h 326  HYPERLINK \l "_Toc282771396" Create a Web application (SharePoint Server 2010)  PAGEREF _Toc282771396 \h 328  HYPERLINK \l "_Toc282771397" Create a Web application that uses Windows-claims authentication (SharePoint Server 2010)  PAGEREF _Toc282771397 \h 330  HYPERLINK \l "_Toc282771398" Create a Web application that uses Windows-classic authentication (SharePoint Server 2010)  PAGEREF _Toc282771398 \h 337  HYPERLINK \l "_Toc282771399" Configure settings for a Web application (SharePoint Server 2010)  PAGEREF _Toc282771399 \h 343  HYPERLINK \l "_Toc282771400" Web application general settings  PAGEREF _Toc282771400 \h 343  HYPERLINK \l "_Toc282771401" In this section  PAGEREF _Toc282771401 \h 346  HYPERLINK \l "_Toc282771402" Configure alert settings for a Web application (SharePoint Server 2010)  PAGEREF _Toc282771402 \h 348  HYPERLINK \l "_Toc282771403" Configure Recycle Bin settings (SharePoint Server 2010)  PAGEREF _Toc282771403 \h 352  HYPERLINK \l "_Toc282771404" Define managed paths (SharePoint Server 2010)  PAGEREF _Toc282771404 \h 354  HYPERLINK \l "_Toc282771405" Define managed paths for a Web application by using Central Administration  PAGEREF _Toc282771405 \h 354  HYPERLINK \l "_Toc282771406" Define managed paths for a Web application by using Windows Powershell  PAGEREF _Toc282771406 \h 355  HYPERLINK \l "_Toc282771407" Turn on or turn off self-service site creation (SharePoint Server 2010)  PAGEREF _Toc282771407 \h 358  HYPERLINK \l "_Toc282771408" Cache settings operations (SharePoint Server 2010)  PAGEREF _Toc282771408 \h 360  HYPERLINK \l "_Toc282771409" BLOB cache  PAGEREF _Toc282771409 \h 360  HYPERLINK \l "_Toc282771410" Page output cache profiles  PAGEREF _Toc282771410 \h 361  HYPERLINK \l "_Toc282771411" Object cache  PAGEREF _Toc282771411 \h 361  HYPERLINK \l "_Toc282771412" Task Requirements  PAGEREF _Toc282771412 \h 361  HYPERLINK \l "_Toc282771413" Configure cache settings for a Web application (SharePoint Server 2010)  PAGEREF _Toc282771413 \h 362  HYPERLINK \l "_Toc282771414" Configuring BLOB cache settings  PAGEREF _Toc282771414 \h 362  HYPERLINK \l "_Toc282771415" Configuring cache profile settings  PAGEREF _Toc282771415 \h 364  HYPERLINK \l "_Toc282771416" Configuring object cache settings  PAGEREF _Toc282771416 \h 365  HYPERLINK \l "_Toc282771417" Configure object cache user accounts  PAGEREF _Toc282771417 \h 368  HYPERLINK \l "_Toc282771418" Configure object cache user accounts by using Central Administration and Windows PowerShell  PAGEREF _Toc282771418 \h 369  HYPERLINK \l "_Toc282771419" Flush the BLOB cache (SharePoint Server 2010)  PAGEREF _Toc282771419 \h 372  HYPERLINK \l "_Toc282771420" Flush the BLOB cache  PAGEREF _Toc282771420 \h 372  HYPERLINK \l "_Toc282771421" Extend a Web application (SharePoint Server 2010)  PAGEREF _Toc282771421 \h 374  HYPERLINK \l "_Toc282771422" Extend a Web application that uses Windows-claims authentication (SharePoint Server 2010)  PAGEREF _Toc282771422 \h 375  HYPERLINK \l "_Toc282771423" Extend a Web application that uses Windows-classic authentication (SharePoint Server 2010)  PAGEREF _Toc282771423 \h 380  HYPERLINK \l "_Toc282771424" Unextend a Web application (SharePoint Server 2010)  PAGEREF _Toc282771424 \h 384  HYPERLINK \l "_Toc282771425" Delete a Web application (SharePoint Server 2010)  PAGEREF _Toc282771425 \h 386  HYPERLINK \l "_Toc282771426" View site collections in a Web application (SharePoint Server 2010)  PAGEREF _Toc282771426 \h 389  HYPERLINK \l "_Toc282771427" Manage permissions for a Web application (SharePoint Server 2010)  PAGEREF _Toc282771427 \h 391  HYPERLINK \l "_Toc282771428" Manage permissions for a Web application  PAGEREF _Toc282771428 \h 391  HYPERLINK \l "_Toc282771429" Manage permission policies for a Web application (SharePoint Server 2010)  PAGEREF _Toc282771429 \h 393  HYPERLINK \l "_Toc282771430" Manage user permission policy  PAGEREF _Toc282771430 \h 394  HYPERLINK \l "_Toc282771431" Add users to a permission policy  PAGEREF _Toc282771431 \h 394  HYPERLINK \l "_Toc282771432" Edit a user permissions policy  PAGEREF _Toc282771432 \h 395  HYPERLINK \l "_Toc282771433" Delete users from a permission policy  PAGEREF _Toc282771433 \h 395  HYPERLINK \l "_Toc282771434" Manage permission policy for anonymous users  PAGEREF _Toc282771434 \h 396  HYPERLINK \l "_Toc282771435" Manage permission policy levels  PAGEREF _Toc282771435 \h 397  HYPERLINK \l "_Toc282771436" Add a permission policy level  PAGEREF _Toc282771436 \h 397  HYPERLINK \l "_Toc282771437" Edit a permission policy level  PAGEREF _Toc282771437 \h 398  HYPERLINK \l "_Toc282771438" Delete a permission policy level  PAGEREF _Toc282771438 \h 398  HYPERLINK \l "_Toc282771439" Health monitoring (SharePoint Server 2010)  PAGEREF _Toc282771439 \h 399  HYPERLINK \l "_Toc282771440" Monitoring  PAGEREF _Toc282771440 \h 399  HYPERLINK \l "_Toc282771441" Monitoring overview (SharePoint Server 2010)  PAGEREF _Toc282771441 \h 400  HYPERLINK \l "_Toc282771442" Configuring monitoring  PAGEREF _Toc282771442 \h 400  HYPERLINK \l "_Toc282771443" Diagnostic logging  PAGEREF _Toc282771443 \h 400  HYPERLINK \l "_Toc282771444" Health and usage data collection  PAGEREF _Toc282771444 \h 400  HYPERLINK \l "_Toc282771445" Monitoring the farm and resolving problems by using SharePoint Health Analyzer  PAGEREF _Toc282771445 \h 401  HYPERLINK \l "_Toc282771446" View and use reports  PAGEREF _Toc282771446 \h 402  HYPERLINK \l "_Toc282771447" Configuring monitoring (SharePoint Server 2010)  PAGEREF _Toc282771447 \h 403  HYPERLINK \l "_Toc282771448" Configure monitoring  PAGEREF _Toc282771448 \h 403  HYPERLINK \l "_Toc282771449" Configure diagnostic logging (SharePoint Server 2010)  PAGEREF _Toc282771449 \h 404  HYPERLINK \l "_Toc282771450" Best practices  PAGEREF _Toc282771450 \h 404  HYPERLINK \l "_Toc282771451" Configure diagnostic logging by using Central Administration  PAGEREF _Toc282771451 \h 406  HYPERLINK \l "_Toc282771452" Configure diagnostic logging by using Windows PowerShell  PAGEREF _Toc282771452 \h 407  HYPERLINK \l "_Toc282771453" Configure SharePoint Health Analyzer timer jobs (SharePoint Server 2010)  PAGEREF _Toc282771453 \h 409  HYPERLINK \l "_Toc282771454" Use Central Administration to configure health data collection timer jobs  PAGEREF _Toc282771454 \h 409  HYPERLINK \l "_Toc282771455" Use Windows PowerShell to configure health data collection timer jobs  PAGEREF _Toc282771455 \h 410  HYPERLINK \l "_Toc282771456" Configure usage and health data collection (SharePoint Server 2010)  PAGEREF _Toc282771456 \h 412  HYPERLINK \l "_Toc282771457" Configure usage and health data collection by using Central Administration  PAGEREF _Toc282771457 \h 412  HYPERLINK \l "_Toc282771458" Configure usage data collection by using Windows PowerShell  PAGEREF _Toc282771458 \h 413  HYPERLINK \l "_Toc282771459" To configure usage data collection for a specific event type by using Windows PowerShell  PAGEREF _Toc282771459 \h 414  HYPERLINK \l "_Toc282771460" Log usage data in a different logging database by using Windows PowerShell  PAGEREF _Toc282771460 \h 414  HYPERLINK \l "_Toc282771461" Configure SharePoint Health Analyzer rules (SharePoint Server 2010)  PAGEREF _Toc282771461 \h 416  HYPERLINK \l "_Toc282771462" Configuring health rules  PAGEREF _Toc282771462 \h 416  HYPERLINK \l "_Toc282771463" Viewing reports and logs (SharePoint Server 2010)  PAGEREF _Toc282771463 \h 418  HYPERLINK \l "_Toc282771464" View administrative reports (SharePoint Server 2010)  PAGEREF _Toc282771464 \h 419  HYPERLINK \l "_Toc282771465" View administrative reports by using Central Administration  PAGEREF _Toc282771465 \h 419  HYPERLINK \l "_Toc282771466" View health reports (SharePoint Server 2010)  PAGEREF _Toc282771466 \h 420  HYPERLINK \l "_Toc282771467" View health reports by using Central Administration  PAGEREF _Toc282771467 \h 420  HYPERLINK \l "_Toc282771468" View Web Analytics reports (SharePoint Server 2010)  PAGEREF _Toc282771468 \h 421  HYPERLINK \l "_Toc282771469" View Web Analytics reports by using Central Administration  PAGEREF _Toc282771469 \h 421  HYPERLINK \l "_Toc282771470" View diagnostic logs (SharePoint Server 2010)  PAGEREF _Toc282771470 \h 423  HYPERLINK \l "_Toc282771471" View and filter log events by using Windows PowerShell  PAGEREF _Toc282771471 \h 423  HYPERLINK \l "_Toc282771472" View and export diagnostic logs by using the Windows PowerShell Out-GridView cmdlet  PAGEREF _Toc282771472 \h 424  HYPERLINK \l "_Toc282771473" View timer job status (SharePoint Server 2010)  PAGEREF _Toc282771473 \h 427  HYPERLINK \l "_Toc282771474" View timer job status by using Central Administration  PAGEREF _Toc282771474 \h 427  HYPERLINK \l "_Toc282771475" View timer job status by using Windows PowerShell  PAGEREF _Toc282771475 \h 427  HYPERLINK \l "_Toc282771476" Monitor cache performance (SharePoint Server 2010)  PAGEREF _Toc282771476 \h 429  HYPERLINK \l "_Toc282771477" About cache monitoring  PAGEREF _Toc282771477 \h 429  HYPERLINK \l "_Toc282771478" Monitoring BLOB cache performance  PAGEREF _Toc282771478 \h 430  HYPERLINK \l "_Toc282771479" Monitoring ASP.NET output cache performance  PAGEREF _Toc282771479 \h 431  HYPERLINK \l "_Toc282771480" Monitoring object cache performance  PAGEREF _Toc282771480 \h 432  HYPERLINK \l "_Toc282771481" Solving problems and troubleshooting (SharePoint Server 2010)  PAGEREF _Toc282771481 \h 434  HYPERLINK \l "_Toc282771482" Viewing and resolving SharePoint Health Analyzer alerts (SharePoint Server 2010)  PAGEREF _Toc282771482 \h 435  HYPERLINK \l "_Toc282771483" Viewing and resolving SharePoint Health Analyzer alerts  PAGEREF _Toc282771483 \h 435  HYPERLINK \l "_Toc282771484" Health alert fields  PAGEREF _Toc282771484 \h 435  HYPERLINK \l "_Toc282771485" Update alerts by using Windows PowerShell (SharePoint Server 2010)  PAGEREF _Toc282771485 \h 437  HYPERLINK \l "_Toc282771486" Example  PAGEREF _Toc282771486 \h 438  HYPERLINK \l "_Toc282771487" Monitor health and performance of a virtual environment (SharePoint Server 2010)  PAGEREF _Toc282771487 \h 440  HYPERLINK \l "_Toc282771488" Monitor SharePoint health and performance  PAGEREF _Toc282771488 \h 440  HYPERLINK \l "_Toc282771489" Monitor Hyper-V health and performance  PAGEREF _Toc282771489 \h 440  HYPERLINK \l "_Toc282771490" Health and performance resources  PAGEREF _Toc282771490 \h 441  HYPERLINK \l "_Toc282771491" SharePoint Server 2010 Operations Framework and Checklists (white paper)  PAGEREF _Toc282771491 \h 442  HYPERLINK \l "_Toc282771492" Manage farm administration settings (SharePoint Server 2010)  PAGEREF _Toc282771492 \h 443  HYPERLINK \l "_Toc282771493" Configure diagnostic logging (SharePoint Server 2010)  PAGEREF _Toc282771493 \h 444  HYPERLINK \l "_Toc282771494" Best practices  PAGEREF _Toc282771494 \h 444  HYPERLINK \l "_Toc282771495" Configure diagnostic logging by using Central Administration  PAGEREF _Toc282771495 \h 446  HYPERLINK \l "_Toc282771496" Configure diagnostic logging by using Windows PowerShell  PAGEREF _Toc282771496 \h 447  HYPERLINK \l "_Toc282771497" E-mail integration (SharePoint Server 2010)  PAGEREF _Toc282771497 \h 449  HYPERLINK \l "_Toc282771498" Configure incoming e-mail (SharePoint Server 2010)  PAGEREF _Toc282771498 \h 450  HYPERLINK \l "_Toc282771499" Overview  PAGEREF _Toc282771499 \h 450  HYPERLINK \l "_Toc282771500" Install and configure the SMTP service  PAGEREF _Toc282771500 \h 451  HYPERLINK \l "_Toc282771501" Install the SMTP service  PAGEREF _Toc282771501 \h 451  HYPERLINK \l "_Toc282771502" Install IIS 6.0 Management tools  PAGEREF _Toc282771502 \h 451  HYPERLINK \l "_Toc282771503" Configure the SMTP service  PAGEREF _Toc282771503 \h 452  HYPERLINK \l "_Toc282771504" Configure incoming e-mail in a basic scenario  PAGEREF _Toc282771504 \h 453  HYPERLINK \l "_Toc282771505" Configure incoming e-mail in an advanced scenario  PAGEREF _Toc282771505 \h 453  HYPERLINK \l "_Toc282771506" Prepare your environment for incoming e-mail in an advanced scenario  PAGEREF _Toc282771506 \h 457  HYPERLINK \l "_Toc282771507" Configure ADDS to be used with Directory Management Service  PAGEREF _Toc282771507 \h 457  HYPERLINK \l "_Toc282771508" Configure DNS Manager  PAGEREF _Toc282771508 \h 460  HYPERLINK \l "_Toc282771509" Add an SMTP connector in Microsoft Exchange Server 2010  PAGEREF _Toc282771509 \h 461  HYPERLINK \l "_Toc282771510" Configure permissions to the e-mail drop folder  PAGEREF _Toc282771510 \h 462  HYPERLINK \l "_Toc282771511" Are attachments missing from e-mail messages that are sent to a SharePoint document library?  PAGEREF _Toc282771511 \h 464  HYPERLINK \l "_Toc282771512" Configure outgoing e-mail (SharePoint Server 2010)  PAGEREF _Toc282771512 \h 466  HYPERLINK \l "_Toc282771513" Install and configure the SMTP service  PAGEREF _Toc282771513 \h 467  HYPERLINK \l "_Toc282771514" Install the SMTP service  PAGEREF _Toc282771514 \h 467  HYPERLINK \l "_Toc282771515" Configure the SMTP service  PAGEREF _Toc282771515 \h 468  HYPERLINK \l "_Toc282771516" Configure outgoing e-mail for a farm  PAGEREF _Toc282771516 \h 469  HYPERLINK \l "_Toc282771517" Configure outgoing e-mail for a specific Web application  PAGEREF _Toc282771517 \h 470  HYPERLINK \l "_Toc282771518" Configure a mobile account (SharePoint Server 2010)  PAGEREF _Toc282771518 \h 473  HYPERLINK \l "_Toc282771519" Import a root certificate and create a trusted root authority  PAGEREF _Toc282771519 \h 474  HYPERLINK \l "_Toc282771520" Configure a mobile account  PAGEREF _Toc282771520 \h 474  HYPERLINK \l "_Toc282771521" Retrieve mobile account information  PAGEREF _Toc282771521 \h 478  HYPERLINK \l "_Toc282771522" Delete a mobile account  PAGEREF _Toc282771522 \h 479  HYPERLINK \l "_Toc282771523" Change the Central Administration Web site port number (SharePoint Server 2010)  PAGEREF _Toc282771523 \h 481  HYPERLINK \l "_Toc282771524" Farm topology management (SharePoint Server 2010)  PAGEREF _Toc282771524 \h 483  HYPERLINK \l "_Toc282771525" Add a Web or application server to the farm (SharePoint Server 2010)  PAGEREF _Toc282771525 \h 484  HYPERLINK \l "_Toc282771526" Preparation  PAGEREF _Toc282771526 \h 484  HYPERLINK \l "_Toc282771527" Determine server role  PAGEREF _Toc282771527 \h 484  HYPERLINK \l "_Toc282771528" Additional tasks  PAGEREF _Toc282771528 \h 487  HYPERLINK \l "_Toc282771529" Install prerequisite software  PAGEREF _Toc282771529 \h 487  HYPERLINK \l "_Toc282771530" Install the SharePoint Products software  PAGEREF _Toc282771530 \h 488  HYPERLINK \l "_Toc282771531" To add the server to the farm  PAGEREF _Toc282771531 \h 489  HYPERLINK \l "_Toc282771532" Configure the new server  PAGEREF _Toc282771532 \h 491  HYPERLINK \l "_Toc282771533" Add a database server to an existing farm (SharePoint Server 2010)  PAGEREF _Toc282771533 \h 492  HYPERLINK \l "_Toc282771534" Prepare the new database server  PAGEREF _Toc282771534 \h 492  HYPERLINK \l "_Toc282771535" Configure and use the new database server  PAGEREF _Toc282771535 \h 493  HYPERLINK \l "_Toc282771536" Remove a server from the farm (SharePoint Server 2010)  PAGEREF _Toc282771536 \h 495  HYPERLINK \l "_Toc282771537" Remove a Web server or an application server from a farm by using Control Panel  PAGEREF _Toc282771537 \h 496  HYPERLINK \l "_Toc282771538" Remove any kind of server from a farm by using Central Administration  PAGEREF _Toc282771538 \h 497  HYPERLINK \l "_Toc282771539" Rename a stand-alone server (SharePoint Server 2010)  PAGEREF _Toc282771539 \h 498  HYPERLINK \l "_Toc282771540" Rename a stand-alone server by using Windows Powershell  PAGEREF _Toc282771540 \h 498  HYPERLINK \l "_Toc282771541" Update site access mappings  PAGEREF _Toc282771541 \h 499  HYPERLINK \l "_Toc282771542" Manage search topology  PAGEREF _Toc282771542 \h 500  HYPERLINK \l "_Toc282771543" Search topology operations in SharePoint Server 2010 (white paper)  PAGEREF _Toc282771543 \h 501  HYPERLINK \l "_Toc282771544" Add or remove an index partition  PAGEREF _Toc282771544 \h 502  HYPERLINK \l "_Toc282771545" To add an index partition to a Search Service Application  PAGEREF _Toc282771545 \h 502  HYPERLINK \l "_Toc282771546" To remove an index partition from a Search Service Application  PAGEREF _Toc282771546 \h 503  HYPERLINK \l "_Toc282771547" Add or remove a query component  PAGEREF _Toc282771547 \h 505  HYPERLINK \l "_Toc282771548" To add a query component to an index partition  PAGEREF _Toc282771548 \h 505  HYPERLINK \l "_Toc282771549" To remove a query component from an index partition  PAGEREF _Toc282771549 \h 506  HYPERLINK \l "_Toc282771550" Add or remove a crawl database  PAGEREF _Toc282771550 \h 508  HYPERLINK \l "_Toc282771551" To add a crawl database to a Search Service Application  PAGEREF _Toc282771551 \h 508  HYPERLINK \l "_Toc282771552" To remove a crawl database from a Search Service Application  PAGEREF _Toc282771552 \h 509  HYPERLINK \l "_Toc282771553" Add or remove a crawl component  PAGEREF _Toc282771553 \h 511  HYPERLINK \l "_Toc282771554" To add a crawl component to a Search Service Application  PAGEREF _Toc282771554 \h 511  HYPERLINK \l "_Toc282771555" To remove a crawl component from a Search Service Application  PAGEREF _Toc282771555 \h 512  HYPERLINK \l "_Toc282771556" Add or remove a property database  PAGEREF _Toc282771556 \h 513  HYPERLINK \l "_Toc282771557" To add a property database to a farm  PAGEREF _Toc282771557 \h 513  HYPERLINK \l "_Toc282771558" To remove a property database from a farm  PAGEREF _Toc282771558 \h 514  HYPERLINK \l "_Toc282771559" Add or remove a host distribution rule  PAGEREF _Toc282771559 \h 516  HYPERLINK \l "_Toc282771560" To add a host distribution rule  PAGEREF _Toc282771560 \h 516  HYPERLINK \l "_Toc282771561" To remove a host distribution rule  PAGEREF _Toc282771561 \h 516  HYPERLINK \l "_Toc282771562" Migrate a farm deployed on a failover cluster environment (SharePoint Server 2010)  PAGEREF _Toc282771562 \h 518  HYPERLINK \l "_Toc282771563" Migration strategy  PAGEREF _Toc282771563 \h 518  HYPERLINK \l "_Toc282771564" Migration resources  PAGEREF _Toc282771564 \h 519  HYPERLINK \l "_Toc282771565" Availability configuration (SharePoint Server 2010)  PAGEREF _Toc282771565 \h 520  HYPERLINK \l "_Toc282771566" Configure availability by using SQL Server clustering (SharePoint Server 2010)  PAGEREF _Toc282771566 \h 521  HYPERLINK \l "_Toc282771567" Configure availability by using SQL Server database mirroring (SharePoint Server 2010)  PAGEREF _Toc282771567 \h 522  HYPERLINK \l "_Toc282771568" Before you begin  PAGEREF _Toc282771568 \h 524  HYPERLINK \l "_Toc282771569" Database mirroring requirements  PAGEREF _Toc282771569 \h 524  HYPERLINK \l "_Toc282771570" Security associated with database mirroring  PAGEREF _Toc282771570 \h 525  HYPERLINK \l "_Toc282771571" Configure high-availability database mirroring  PAGEREF _Toc282771571 \h 526  HYPERLINK \l "_Toc282771572" Configure SharePoint 2010 Products to be aware of mirrored databases  PAGEREF _Toc282771572 \h 526  HYPERLINK \l "_Toc282771573" User experience during a failover  PAGEREF _Toc282771573 \h 527  HYPERLINK \l "_Toc282771574" Monitoring and troubleshooting mirroring  PAGEREF _Toc282771574 \h 527  HYPERLINK \l "_Toc282771575" Sample script for configuring SQL Server database mirroring (SharePoint Server 2010)  PAGEREF _Toc282771575 \h 528  HYPERLINK \l "_Toc282771576" Configure database mirroring with certificates and full recovery  PAGEREF _Toc282771576 \h 528  HYPERLINK \l "_Toc282771577" Set up a witness server  PAGEREF _Toc282771577 \h 533  HYPERLINK \l "_Toc282771578" Transfer permissions to the mirror server  PAGEREF _Toc282771578 \h 536  HYPERLINK \l "_Toc282771579" Removing mirroring from a server  PAGEREF _Toc282771579 \h 536  HYPERLINK \l "_Toc282771580" Track or block SharePoint Server 2010 installations  PAGEREF _Toc282771580 \h 537  HYPERLINK \l "_Toc282771581" Block installations  PAGEREF _Toc282771581 \h 537  HYPERLINK \l "_Toc282771582" Track installations  PAGEREF _Toc282771582 \h 537  Getting help Every effort has been made to ensure the accuracy of this book. This content is also available online in the Office System TechNet Library, so if you run into problems you can check for updates at: http://technet.microsoft.com/office If you do not find your answer in our online content, you can send an e-mail message to the Microsoft Office System and Servers content team at: itspdocs@microsoft.com If your question is about Microsoft Office products, and not about the content of this book, please search the Microsoft Help and Support Center or the Microsoft Knowledge Base at: http://support.microsoft.com Operations for SharePoint Server 2010 Welcome to the operations guide for Microsoft SharePoint Server 2010. The articles in this guide help you operate and maintain your servers, server farms, sites, and solutions. In this section: HYPERLINK \l "zd1e89000ec264a0c8eac40570640c585"Server and server farm administration (SharePoint Server 2010) This section describes how to maintain servers and server farms within a SharePoint Server 2010 environment. It includes articles about backup and recovery, managing databases, Web application management, service application management, health and monitoring, and security and permissions administration. HYPERLINK "http://technet.microsoft.com/library/86f8efd5-d255-497b-939f-5b0bb6d459ac(Office.14).aspx"Site and solution administration (SharePoint Server 2010) (http://technet.microsoft.com/library/86f8efd5-d255-497b-939f-5b0bb6d459ac(Office.14).aspx) This section describes how to maintain sites and solutions within a SharePoint Server 2010 environment. It includes articles about managing site collections, service applications and services, features such as workflow, and sandboxed solutions. Server and server farm administration (SharePoint Server 2010) This section describes how to configure administration settings for servers and server farms within a Microsoft SharePoint Server 2010 environment. In this section: HYPERLINK \l "z71abd06e6730442eb2c1e3ba9c04d497"Backup and recovery (SharePoint Server 2010) HYPERLINK \l "zf436a248984f40bdbbe2ac4dd1e1f961"Database management (SharePoint Server 2010) HYPERLINK \l "z119a29020f6540869192ac73b32149d8"Security and permissions (SharePoint Server 2010) HYPERLINK \l "z56187c2504444da79879a141da864704"Service application and service management (SharePoint Server 2010) HYPERLINK \l "z1ad49d4e598d446caabdde4a8f6ad391"Web applications management (SharePoint Server 2010) HYPERLINK \l "zde17a1ff79f44638918b380fb0a15205"Health monitoring (SharePoint Server 2010) HYPERLINK \l "z93caa879c50c4298bfb69319e429e265"Manage farm administration settings (SharePoint Server 2010) HYPERLINK \l "z3cd153fa638b43edb8d3857f678595b9"Farm topology management (SharePoint Server 2010) HYPERLINK \l "zbe4e1054ada64eeaa92de35d1da61eb9"Availability configuration (SharePoint Server 2010) HYPERLINK \l "zc8dfb1822cd945f29e42baa522a9c33d"Track or block SharePoint Server 2010 installations Backup and recovery (SharePoint Server 2010) The articles in this section are written to meet the requirements of information technology (IT) professionals who are responsible for the planning, design, deployment, and operations of backup and recovery solutions. These solutions might be in enterprise, corporate, or branch-office environments. The IT professionals who are responsible for backup and recovery solutions are expected to have an understanding of the technical details that are contained in this section. However, service-level expertise is not required to understand the enterprise-level discussions and decisions. A backup is a copy of data that is used to restore and recover that data after a system failure. Backups allow you to restore data after a failure. Recovery allows you to quickly restore the farm if a problem arises. You can recover the entire farm or one or more components of the farm from a backup.  Relevant backup and recovery articles for Project Server 2010 are available in the Project Server document library at HYPERLINK "http://technet.microsoft.com/library/800a2c1d-2415-4024-8b00-106c2e0beab2(Office.14).aspx"Project backup and recovery (Project Server 2010) (http://technet.microsoft.com/library/800a2c1d-2415-4024-8b00-106c2e0beab2(Office.14).aspx) and HYPERLINK "http://technet.microsoft.com/library/034ca3f9-82fb-426c-b687-7b9c59495496(Office.14).aspx"Back up and restore databases (Project Server 2010) ( HYPERLINK "http://technet.microsoft.com/library/034ca3f9-82fb-426c-b687-7b9c59495496(Office.14).aspx)" http://technet.microsoft.com/library/034ca3f9-82fb-426c-b687-7b9c59495496(Office.14).aspx). In this section: HYPERLINK \l "z56ea0f40426b43daaff5187fe5adc946"Prepare to back up and recover (SharePoint Server 2010) HYPERLINK \l "zd7d2dff9c7a9402b958ad233cbacab8f"Backup and recovery best practices (SharePoint Server 2010) HYPERLINK \l "z3a25437ae99442c7b4dfac9fa29f38f5"Configuring permissions for backup and recovery (SharePoint Server 2010) HYPERLINK \l "z79d47308a90a4c51a1ae93567e978236"Backup (SharePoint Server 2010) HYPERLINK \l "z2ea9549000c04c67b7e3551d2fe032b9"Recovery (SharePoint Server 2010) Prepare to back up and recover (SharePoint Server 2010) It is important to ensure that you have backed up and can recover the data that you need should a failure occur. Consider the information, procedures, and precautions that are described in this article before you back up and restore the environment. This article discusses restrictions and requirements for backup and recovery and how to create a shared folder on the network that can receive backed-up data. In this article:  HYPERLINK \l "_Restrictions" Restrictions  HYPERLINK \l "_Requirements" Requirements  HYPERLINK \l "_How_to_create" How to create a shared folder Restrictions There are some restrictions in what can be backed up or restored. For more information about backup and recovery architecture and about what can or cannot be backed up and restored, see HYPERLINK "http://technet.microsoft.com/library/ee879d48-44a3-46e7-a631-736c4430ec94(Office.14).aspx"Backup and recovery overview (SharePoint Server 2010) (http://technet.microsoft.com/library/ee879d48-44a3-46e7-a631-736c4430ec94(Office.14).aspx). You cannot use a backup made from one version to restore to another version. To do this, you must use the upgrade process. You cannot restore to a farm with a lower update level than the update level of the farm that you backed up. The destination farm must have the same or newer update level. For information about how to upgrade, see HYPERLINK "http://technet.microsoft.com/library/396c85d9-4b86-484e-9cc5-f6c4d725c578(Office.14).aspx"Upgrading to SharePoint Server 2010 (http://technet.microsoft.com/library/396c85d9-4b86-484e-9cc5-f6c4d725c578(Office.14).aspx). If you perform a backup while any task that creates or deletes databases is running, these changes might not be included in the backup. Do not modify the spbackup.xml file. This file is used by SharePoint Server 2010 and changing it can make the backups unusable. Requirements Before you back up data, you must create a shared folder in which the data will be stored. For best performance, you should create this folder on the database server. If you want to archive the backups to another server, you can copy the whole backup folder to that server after backup is complete. Be sure to copy and move the whole backup folder and not the individual backup folders under this folder. The SQL Server VSS Writer service, which is available with Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3 database software, must be started for the SharePoint 2010 VSS Writer service to work correctly. By default, the SharePoint 2010 VSS Writer service is not automatically started. You must make sure that the SharePoint 2010 Administration service is started on all farm servers before you perform a backup. By default, this service is not started on stand-alone installations. You must ensure that the user accounts that you want to perform a backup have access to the shared backup folder. If you are backing up by using Central Administration, the database server's SQL service account, the Timer service account, and the Central Administration application pool identity account must have Full Control permissions to the backup locations. The database server and farm server that you want to back up must be able to connect to one another. If you have changed the farm account, before you back up, you must grant the new account the correct permissions to the shared folder that will contain the backup data. If you are using SQL Server with Transparent Data Encryption (TDE), and you are backing up your environment by using either SharePoint tools or SQL Server tools, the TDE encryption key is not backed up or restored. You must manually back up the key. When restoring, you must manually restore the key before you restore the data. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=196394&clcid=0x409" \o "http://go.microsoft.com/fwlink/?LinkId=196394&clcid=0x409"Understanding Transparent Data Encryption (TDE) (http://go.microsoft.com/fwlink/?LinkId=196394&clcid=0x409). How to create a shared folder Use this procedure to create a shared folder on the network that can receive and hold backed-up data. You can also use this shared folder when you restore data. If you already have a shared folder that serves this purpose, you do not have to perform this procedure. By performing the following procedure, you ensure that you can access the shared folder from the computer that runs Microsoft SQL Server database software and from the computer that hosts the SharePoint Central Administration Web site. If you are backing up by using Central Administration and SQL Server is not running on the same server, the backup folder must be on the same network or on a database server as SharePoint Server 2010. If you have a stand-alone installation where both SQL Server and SharePoint Server 2010 are running on the same server, you can use a local drive path as the backup folder location. If you are using SQL Server to directly back up a database, such as by using SQL Server Management Studio, the backup folder can be either local or on the network. For best performance, we recommend that you back up to a local folder on the database server and then move or copy the backup files to a network folder. To create a shared folder 1. Verify that the user account that is performing this procedure is a member of the Administrators group on the computer on which you want to create the shared folder. 2. If you create the shared folder on a computer other than the one running SQL Server, ensure that the service account for SQL Server (MSSQLSERVER) is using a domain user account and that it has Full Control permissions on the shared folder. 3. On the server on which you want to store the backup data, create a shared folder. 4. On the Sharing tab of the Properties dialog box, click Share, and then in the File Sharing dialog box, add the following accounts and assign them the Co-Owner role: SQL Server service account (MSSQLSERVER) The SharePoint Central Administration application pool identity account The SharePoint 2010 Timer service account (if you are using SharePoint Server 2010 to perform backups) . See Also HYPERLINK "http://technet.microsoft.com/en-us/library/cc770406.aspx" \o "http://technet.microsoft.com/en-us/library/cc770406.aspx"Shared Folders (http://technet.microsoft.com/en-us/library/cc770406.aspx) Backup and recovery best practices (SharePoint Server 2010) This article describes best practices that you can use to help ensure that backup and recovery operations in Microsoft SharePoint Server 2010 are successful and that the environment is protected against data loss or continuity gaps. The article includes best practices for performance, quality assurance, security, and operational excellence. In this article:  HYPERLINK \l "_Performance_best_practices" Performance best practices  HYPERLINK \l "_Quality_assurance_best" Quality assurance best practices  HYPERLINK \l "_Procedural_best_practices" Procedural best practices Performance best practices Backup and restore operations can consume server resources and limit server performance while the operations are running. By following these best practices, you can reduce resource usage and increase the performance of servers and the backup or restore operation. Minimize latency between SQL Server and the backup location In general, it is best to use a local disk on the database server, not a network drive, for backups, and then copy the data later to a shared folder on the network. Network drives with 1 millisecond or less latency between them and the database server will perform well. To avoid I/O bottlenecks, perform the main backup to a separate disk from the disk running Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2. By design, most backup jobs consume all available I/O resources to complete the job. Therefore, you might see disk queuing, which can result in greater than usual I/O request latency. This is typical and should not be considered a problem. Avoid processing conflicts Do not run backup jobs during times when users require access to the system. Consider staggering backups so that not all databases are backed up at the same time. Keep databases small for faster recovery times Keep databases small to speed both backup and recovery. You can do this by using multiple content databases for a Web application instead of one large content database. Use incremental backups for large databases Use incremental backups for large database such as those available with DPM 2010. Incremental backups can be restored faster and more efficiently than full backups for larger databases. For more information about backup types, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=203863"Backup Overview (SQL Server) (http://go.microsoft.com/fwlink/?LinkId=203863). Use compression during backup In some circumstances, you can use compression to improve backup size (30% decrease) and times (25% decrease). Backup compression has been in introduced in SQL Server 2008 Enterprise. For more information about how backup compression affects performance in SQL Server, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=129381"Backup Compression (SQL Server) (http://go.microsoft.com/fwlink/?LinkID=129381). Follow SQL Server backup and restore optimization recommendations If you are using SQL Server backups, use a combination of full, differential, and transaction log backups (for the full or bulk-logged recovery model) to minimize recovery time. Differential database backups are usually faster to create than full database backups and reduce the amount of transaction log required to recover the database. If you are using the full recovery model, we recommend that you periodically truncate the transaction log files to avoid maintenance issues. For detailed recommendations about how to optimize SQL Server backup and restore performance, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=126630 "Optimizing Backup and Restore Performance in SQL Server (http://go.microsoft.com/fwlink/?LinkId=126630). Use RAID 10 if you are going to use RAID Carefully consider whether to use redundant array of independent disks (RAID) on the disk backup device. For example, RAID 5 has low write performance, approximately the same speed as for a single disk. (This is because RAID 5 has to maintain parity information.) Using RAID 10 for a backup device may provide faster backups. For more information about how to use RAID with backups, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=126632 "Configure RAID for maximum SQL Server I/O throughput (http://go.microsoft.com/fwlink/?LinkId=126632). Configure SharePoint settings for better backup or restore performance You can configure settings in both Central Administration and Windows PowerShell to increase backup or restore efficiency and performance. If you are using the Export-SPWeb Windows PowerShell cmdlet, you can use the NoFileCompression parameter. By default, SharePoint Server 2010 uses file compression while exporting Web applications, site collection, lists, or document libraries. You can use this parameter to suppress file compression while exporting and importing. File compression can use up to 30% more resources, but the exported file will use approximately 25% less disk space. If you use the NoFileCompression parameter when exporting, you must also use it when you import the same content. You can also use the NoLogFile parameter. By default, SharePoint Server 2010 always creates a log file when you export content. You can use this parameter to suppress log file creation to save resources. However, we recommend that you always create logs. This is because logs can be used in troubleshooting. Moreover, log creation does not use many resources. Note: These settings are not available through Central Administration. If you are using the Backup-SPFarm cmdlet, you can use the BackupThreads parameter to specify how many threads SharePoint Server 2010 will use during the backup process. The more threads you specify, the more resources that backup operation will take, but the faster that it will finish, if sufficient resources are available. However, each thread is reported individually in the log files, so using fewer threads makes interpreting the log files easier. By default, three threads are used. The maximum number of threads available is 10. Note: This setting is also available through Central Administration on the Default Backup and Restore Settings page in the Backup and Restore section. Consider site collection size when determining the tools to use If the business requires site collection backups in addition to farm-level or database-level backups, select the tools that you will use based on the site collection size. Less than 15 gigabytes (GB): Use the Windows PowerShell command Backup-SPSite. For more information, see HYPERLINK \l "z45acdd33b3224f3697f10701159e15f0"Back up a site collection (SharePoint Server 2010). 15-100 GB: Use a SharePoint Products and Technologies tool, a SQL Server tool, or other database backup tool to protect the content database that contains the site collection. For more information, see HYPERLINK \l "z45acdd33b3224f3697f10701159e15f0"Back up a site collection (SharePoint Server 2010). Larger than 100 GB: Use a differential backup solution, such as Microsoft SQL Server 2005 or DPM 2010, instead of the built-in backup and recovery tools. Quality assurance best practices You can follow these best practices to help ensure the quality of the backups of the farm environment and reduce the chances of data loss. Ensure you have adequate storage space Be certain that the system has adequate disk space to accommodate the backup. Routinely test backup quality Routinely test backups and validate their consistency. Run practice recovery operations to validate the contents of the backup and to ensure that you can restore the entire environment. For geographically dispersed environments, prepare for disaster recovery by setting up a remote farm. Then you can restore the environment by using the database attach command to upload a copy of the database to the remote farm and redirect users. Periodically perform a trial data recovery operation to verify that the files are correctly backed up. A trial restoration can expose hardware problems that do not show up with software verifications. Back up ULS trace logs The SharePoint Server 2010 tools do not back up the ULS trace logs. Data in ULS trace logs can be useful for performance analysis, troubleshooting, monitoring compliance with service-level agreements, and legal, regulatory, or business reasons. Therefore, protect this data as part of the routine maintenance. For more information about backing up the ULS logs, see HYPERLINK \l "z998f1f7936964e5e82655f6a6cc2e3d0"Back up or archive logs (SharePoint Server 2010). Store a copy of backup files off-site To safeguard against loss from a catastrophic event, such as a fire or earthquake, maintain duplicate copies of backups in a separate location from the servers. Doing so can help protect you against the loss of critical data. As a best practice, keep three copies of the backup media, and keep at least one copy offsite in a controlled environment. This should include all backup and recovery materials, documents, database and transaction log backups, and usage and trace log backups. Procedural best practices You can use these procedural best practices to help plan and perform backup and restore operations with better documentation, more ease, and greater assurance. Use FQDN server names When referring to servers in a different domain, always use fully qualified domain names (FQDN). Keep accurate records When you deploy SharePoint Server 2010, record the accounts that you create, and the computer names, passwords, and setup options that you choose. Keep this information in a safe place. Have a recovery environment ready Prepare for restore testing and disaster recovery by setting up a remote farm. Then you can restore the environment by using the database attach command to upload a copy of the database to the remote farm and redirect users. Similarly, you can set up a standby environment running the same version of software as the production environment so that you can restore the databases and recover documents quickly. Schedule backup operations If you want to schedule backups, you can use the Windows Task Scheduler to run them by using a Windows PowerShell script file (*.ps1). Use the SQL FILESTREAM provider with BLOB storage If you are using BLOB storage using the SQL FILESTREAM provider and you back up the content database with that Remote BLOB Store (RBS) defined, both the RBS and the content database will be backed up and restored when you use SharePoint tools or SQL Server tools. We do not recommend that you use RBS with other restore methods. Configuring permissions for backup and recovery (SharePoint Server 2010) Before backing up or restoring Microsoft SharePoint Server 2010, you must ensure that the timer service account, SQL Server service account, and users running the backup or restore operations have the correct permissions or are members of the correct Windows security groups or SharePoint groups. These permissions and group memberships must be configured initially. Subsequently, they must be updated when new farm components are added to the environment and if you want to add users who will perform backup and restore operations. In this topic:  HYPERLINK \l "_Permissions_for_the" Permissions for the SPTimerV4 timer service and SQL Server account  HYPERLINK \l "_Group_memberships_required" Group memberships required to run backup and restore operations in Central Administration  HYPERLINK \l "_Setting_permissions_for" Setting permissions for running backup and restore operations by using Windows PowerShell Permissions for the SPTimerV4 timer service and SQL Server account The Windows SharePoint Services Timer V4 (SPTimerV4) and the SQL Server service account in SharePoint Server 2010 perform backup and restore operations on behalf of the user. These service accounts require Full Control permissions on any backup folders. Group memberships required to run backup and restore operations in Central Administration You must ensure that all user accounts that will be backing up or restoring your farm and farm components by using Central Administration have the group memberships that are described in the following table. Required group memberships Farm componentMember of Administrators group on the local computerMember of Farm Administrators SharePoint groupFarmYesNoService ApplicationYesNoContent DatabaseYesNoSite CollectionNoYesSite, list, document libraryNoYes Setting permissions for running backup and restore operations by using Windows PowerShell You must ensure that all user accounts that will be backing up or restoring your farm and farm components by using Windows PowerShell are added to the SharePoint_Shell_Access role for a specified database and have the permissions described in the table later in this section. You can run the Add-SPShellAdmin cmdlet to add a user account to this role. You must run the command for each user account. Moreover, you must run the command for all databases to which you want to grant access. Note: You only need to grant a user account access to back up and restore a specific farm component one time. You will have to perform this task again only when new farm components are added to your environment or when you want to add users to perform backup and restore operations. To add a user to or remove a user from the SharePoint_Shell_Access role by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Add-SPShellAdmin -Username -Database To add a user account to all the databases in the farm, type the following command, and then press ENTER: ForEach ($db in Get-SPDatabase) {Add-SPShellAdmin -Username -Database $db} To remove a user account from all the databases in the farm, type the following command, and then press ENTER: ForEach ($db in Get-SPDatabase) {Remove-SPShellAdmin -Username -Database $db} To view the user accounts currently added to the databases in the farm, type the following command, and then press ENTER: ForEach ($db in Get-SPDatabase) {Get-SPShellAdmin -Database $db} For more information, see HYPERLINK "http://technet.microsoft.com/library/2ddfad84-7ca8-409e-878b-d09cb35ed4aa(Office.14).aspx"Add-SPShellAdmin (http://technet.microsoft.com/library/2ddfad84-7ca8-409e-878b-d09cb35ed4aa(Office.14).aspx).You might also have to grant additional permissions to the users running the backup or restore operation by using Windows PowerShell. The following table shows the permissions that are required. Required permissions for Windows PowerShell Farm componentMember of Administrators group on the local computerMember of Farm Administrators SharePoint groupFull Control on backup folderFarmYesNoYesService applicationYesNoYesContent databaseYesNoYesSite collectionNoYesYesSite, list, document libraryYesNoYes Backup (SharePoint Server 2010) The articles in this section are written to meet the requirements of information technology (IT) professionals who are responsible for the planning, design, deployment, and operations of backup and recovery solutions. These solutions might be in enterprise, corporate, or branch office environments. The IT professionals who are responsible for backup and recovery solutions are expected to have an understanding of the technical details that are contained in this section. A backup is a copy of data that is used to restore and recover that data after a system failure. Backups allow you to restore data after a failure. If you make the appropriate backups, you can recover from many system failures, including the following: Media failure User errors (such as deleting a file by mistake) Hardware failures (such as a damaged hard disk or permanent loss of a server) Natural disasters Additionally, it is useful to keep backups of data for routine purposes. Those purposes include copying a database from one server to another, setting up database mirroring, and archiving to comply with regulatory requirements. Back up all or part of a farm The following tasks for backup and recovery are performed on the entire farm, farm databases, sites, subsites, or files: HYPERLINK \l "z8daa31a50f8c4bd684c9ee1f5074594d"Back up a farm (SharePoint Server 2010) This article describes the procedures that you can use to back up the entire farm. HYPERLINK \l "za6d383c038174acdafa9ad7a9b7e6b5a"Back up a farm configuration (SharePoint Server 2010) This article describes the procedures that you can use to back up farm configuration settings. HYPERLINK \l "z8404adef6bfb4795be1615739e1212f5"Copy configuration settings from one farm to another (SharePoint Server 2010) This article describes the procedures that you can use to copy configuration settings from one farm to another, including how to back up and recover a farm without the content databases, how to back up and recover configurations only, and how to create a deployment script. HYPERLINK \l "ze0ad657df5d14caebb0dd2b619eed261"Back up a Web application (SharePoint Server 2010) This article describes the procedures that you can use to back up a Web application that is associated with the farm, including configuration and content databases. HYPERLINK \l "z96dc4ef1cec847d0b99546bca3e8eda2"Back up a service application (SharePoint Server 2010) This article describes the procedures that you can use to back up a service application that is associated with the farm, including configuration and content databases. HYPERLINK \l "z59c0540e12384138b98d0d74ca59b9db"Back up search (SharePoint Server 2010) This article describes the procedures that you can use to back up the Search service application that is associated with the farm, including configuration and indexes. HYPERLINK \l "zd08d6d6523c248cba8711e021a382e5e"Back up the Secure Store service (SharePoint Server 2010) This article describes the procedures that you can use to back up the Secure Store service application that is associated with the farm, including configuration and content databases. HYPERLINK \l "zdb44c8d7e08142a3a42a2ee1b369dd47"Back up a content database (SharePoint Server 2010) This article describes the procedures that you can use to back up a content database that is associated with the farm. HYPERLINK \l "z101dd66188434b98bab789c14abe65b8"Back up databases to snapshots (SharePoint Server 2010) This article describes the procedures that you can use to back up a content database that is associated with the farm by saving the database to a snapshot. HYPERLINK \l "z8f98a75019bb4ea09ff5719b85febbb3"Back up customizations (SharePoint Server 2010) This article describes the procedures that you can use to back up customizations that are associated with the farm. HYPERLINK \l "z45acdd33b3224f3697f10701159e15f0"Back up a site collection (SharePoint Server 2010) This article describes the procedures that you can use to back up site collections that are associated with the farm. HYPERLINK \l "z1e637e1726344601a574299a7c27bb24"Export a site, list, or document library (SharePoint Server 2010)This article describes the procedures that you can use to export a list, site, or document library that is associated with the farm. You can then import the items into another farm or move them to another place in this farm. HYPERLINK \l "z998f1f7936964e5e82655f6a6cc2e3d0"Back up or archive logs (SharePoint Server 2010) This article describes the procedures that you can use to back up or archive log files that are associated with the farm. See Also HYPERLINK \l "z2ea9549000c04c67b7e3551d2fe032b9"Recovery (SharePoint Server 2010) Back up a farm (SharePoint Server 2010) This topic describes how to back up a whole server farm. Procedures in this task:  HYPERLINK \l "_Use_Windows_PowerShell" Use Windows PowerShell to back up a farm  HYPERLINK \l "_Use_Central_Administration" Use Central Administration to back up a farm  HYPERLINK \l "_Use_SQL_Server" Use SQL Server tools to back up a farm For information about which tool to use for backups, see HYPERLINK "http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx"Plan for backup and recovery (SharePoint Server 2010) (http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx). We recommend that you regularly back up the complete farm by backing up both the configuration and content. Regularly backing up the farm reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps to ensure that all the farm data and configurations are available for recovery, if that is required. Considerations when backing up a farm Consider the following when you prepare to back up a farm. Performing a backup does not affect the state of the farm. However, it does require resources and might slightly affect farm performance when the backup is running. You can avoid performance issues by backing up the farm during hours when farm use is lowest, such as outside office hours. The farm backup process does not back up any certificates that you used to form trust relationships. Endure that you have copies of these certificates before you back up the farm. You must re-establish these trust relationships after restoring the farm. Backing up the farm backs up the configuration and Central Administration content databases, but these cannot be restored using Microsoft SharePoint Server 2010 tools. For more information about backing up and restoring all the farm databases, see HYPERLINK \l "zd9dac1890736448d928c68bf38603613"Move all databases (SharePoint Server 2010). When you back up a farm that contains a Web application that is configured to use forms-based authentication, you must also use a file backup system to protect the Web.config files because the Web.config files have been updated manually to register the membership and role providers, and manual changes to the Web.config files are not backed up. Similarly, Web.config files are not restored when you restore a Web application. After recovery, you must update the Web.config files and redeploy the providers. For more information, see HYPERLINK "http://technet.microsoft.com/library/40117fda-70a0-4e3d-8cd3-0def768da16c(Office.14).aspx"Plan authentication methods (SharePoint Server 2010) (http://technet.microsoft.com/library/40117fda-70a0-4e3d-8cd3-0def768da16c(Office.14).aspx) and HYPERLINK "http://technet.microsoft.com/library/83762baa-b23b-4b63-b14f-350421d9f18a(Office.14).aspx"Configure claims authentication (SharePoint Server 2010) (http://technet.microsoft.com/library/83762baa-b23b-4b63-b14f-350421d9f18a(Office.14).aspx). SharePoint Server 2010 backup backs up the Business Data Connectivity service external content type definitions but does not back up the data source itself. To protect the data, you should back up the data source when you back up the Business Data Connectivity service or the farm. If you restore the Business Data Connectivity service or the farm and then restore the data service to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity service might not be able to locate the data source. SharePoint Server 2010 backup backs up remote Binary Large Object (BLOB) stores but only if you are using the FILESTREAM remote BLOB store provider to put data in remote BLOB stores. If you are using another provider, you must manually back up the remote BLOB stores. If you are using SQL Server with Transparent Data Encryption (TDE), and you are backing up your environment by using either SharePoint tools or SQL Server tools, the TDE encryption key in not backed up or restored. You must backup the key manually. When restoring, you must manually restore the key before restoring the data. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=196394"Understanding Transparent Data Encryption (TDE) (http://go.microsoft.com/fwlink/?LinkID=196394). Task requirements Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see HYPERLINK \l "z56ea0f40426b43daaff5187fe5adc946"Prepare to back up and recover (SharePoint Server 2010). Use Windows PowerShell to back up a farm You can use Windows PowerShell to back up the farm manually or as part of a script that can be run at scheduled intervals. To back up a farm by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Backup-SPFarm -Directory -BackupMethod {Full | Differential} [-Verbose] Where is the path of a folder on the local computer or the network in which you want to store the backups. Note: If you are backing up the farm for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. For more information, see HYPERLINK "http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx"Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to back up a farm You can use Central Administration to back up the farm. To back up a farm by using Central Administration 1. To perform this procedure, you must be a member of the Farm Administrators group on the computer that is running Central Administration. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup. 3. On the Perform a Backup Step 1 of 2: Select Component to Back Up page, select the farm from the list of components, and then click Next. 4. On the Start Backup Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential. Note: If you are backing up the farm for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. 5. In the Back Up Only Configuration Settings section, click Back up content and configuration settings. 6. In the Backup File Location section, type the UNC path of the backup folder, and then click Start Backup. 7. You can view the general status of all backup jobs at the top of the Backup and Restore Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5.Use SQL Server tools to back up a farm If you want to back up the complete farm, you must use either Windows PowerShell or Central Administration. You cannot back up the complete farm by using the SQL Server tools because you cannot use the tools to back up the farms configuration. However, you can back up all the databases that are associated with the farm. The databases that are associated with the farm are determined by the services and features that you have installed on the farm. To back up the databases associated with a farm by using SQL Server tools 1. To use SQL Server tools to back up SharePoint Server 2010 databases, the account that is used to back up the databases must be a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored. 2. Open SQL Server Management Studio and connect to the database server. 3. In Object Explorer, expand Databases. 4. Right-click the database that you want to back up, point to Tasks, and then click Back Up. 5. In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see HYPERLINK " http://go.microsoft.com/fwlink/?LinkId=114396"Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396). 6. In the Backup component area, click Database. 7. Either use the default name provided or specify a name for the backup set in the Name text box. 8. Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days). 9. In the Destination area, specify where you want to store the backup. 10. Click OK to back up the database. 11. Repeat steps 1-10 for each farm database.Related content Resource centerHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199235"Business Continuity Management for SharePoint Server 2010 (http://go.microsoft.com/fwlink/?LinkID=199235)IT Pro contentHYPERLINK \l "z7942ef65c309402db4bbd54e686fc5d9"Restore a farm (SharePoint Server 2010) HYPERLINK \l "zcbb3b24276ed4539b4544685a84d57c5"Restore a Web application (SharePoint Server 2010) HYPERLINK "http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx"Plan for backup and recovery (SharePoint Server 2010) (http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx) HYPERLINK \l "z71abd06e6730442eb2c1e3ba9c04d497"Backup and recovery (SharePoint Server 2010)Developer contentHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199237"Data Protection and Recovery (http://go.microsoft.com/fwlink/?LinkID=199237) Back up a farm configuration (SharePoint Server 2010) This article describes how to back up the configuration of a server farm. In earlier versions of Microsoft SharePoint Server, you could not back up or restore the configuration database. In Microsoft SharePoint Server 2010, you can perform the equivalent operation by backing up or restoring the configuration of the server farm. We recommend that you regularly back up the complete farm by backing up both the configuration and content. However, you might want to perform configuration-only backups in test or development environments. Similarly, if you are using Microsoft SQL Server tools to back up the databases for the farm, you will want to back up the configuration. Regularly backing up the farm reduces the possibility of data losses that can occur from hardware failures, power outages, or other problems. It helps to ensure that all the farm data and configurations are available for recovery. For more information about what to back up, see HYPERLINK \l "za6d383c038174acdafa9ad7a9b7e6b5a"Back up a farm configuration (SharePoint Server 2010). The configuration backup will extract and back up the configuration settings from a SharePoint Server 2010 configuration database. You can back up configuration from any configuration database that includes the configuration database for the current farm or another farm, or a configuration database that is not associated with any farm. For information about which tool to use for backups, see HYPERLINK \l "za6d383c038174acdafa9ad7a9b7e6b5a"Back up a farm configuration (SharePoint Server 2010). Procedures in this task: HYPERLINK \l "z1216"Task requirements  HYPERLINK \l "z1217" Use Windows PowerShell to back up a farm configuration Note: You cannot use either SQL Server tools or Data Protection Manager to back up the farm configuration. Task requirements Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see HYPERLINK \l "z56ea0f40426b43daaff5187fe5adc946"Prepare to back up and recover (SharePoint Server 2010). Important: Backing up the farm configuration will not back up the information you have to have to restore service applications. If you want to restore a service application, you must perform a configuration and content backup of the farm. For more information about backing up service applications, see HYPERLINK \l "z96dc4ef1cec847d0b99546bca3e8eda2"Back up a service application (SharePoint Server 2010). Use Windows PowerShell to back up a farm configuration You can use Windows PowerShell to back up the configuration from any configuration database on the current farm, on another farm, or from a configuration database that is not associated with any farm. You can back up a farm configuration manually or as part of a script that can be run at scheduled intervals. To back up the configuration from any configuration database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Backup-SPConfigurationDatabase -Directory-DatabaseServer-DatabaseName-DatabaseCredentials[-Verbose] Where: <BackupFolder> is the path to the folder with the correct backup files. <DatabaseServerName> is the name of the database server for the farm that you are backing up. <DatabaseName> is the name of the farm configuration database. If you are not logged on with an account with db_backupoperator fixed database role on the database server where the configuration database is stored, you must specify the value for DatabaseCredentials parameter. For more information, see HYPERLINK "http://technet.microsoft.com/library/28ddc176-1b7f-47dd-868f-39b7c403a900(Office.14).aspx"Backup-SPConfigurationDatabase (http://technet.microsoft.com/library/28ddc176-1b7f-47dd-868f-39b7c403a900(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to back up a farm configuration You can use Central Administration to back up the configuration of the farm that Central Administration is running on. To back up the configuration of a remote farm, you must use the Central Administration Web site that is running on the remote farm. You cannot use Central Administration to back up an unattached configuration database. To back up a farm configuration by using Central Administration 1. Verify that the user account performing this procedure is a member of the Farm Administrators group. 2. On the Central Administration Home page, in the Backup and Restore section, click Perform a backup. 3. On the Perform a Backup Step 1 of 2: Select Component to Back Up page, select the farm from the list of components, and then click Next. Note: You can back up the configuration for any service or application. However, common practice is to back up configuration at the farm level. 4. On the Start Backup Step 2 of 2: Select Backup Options page, in the Backup Type section, select Full. 5. In the Backup Only Configuration Settings section, select the Backup only configuration settings option. 6. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup. 7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually refresh the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5. See Also HYPERLINK \l "zd849b7dfb26d45f6a74f6641f18788cf"Restore a farm configuration (SharePoint Server 2010) Back up a Web application (SharePoint Server 2010) This article describes how to back up a Web application. Regularly backing up a Web application reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that can help to ensure that all the Web application-related data and configurations are available for recovery, if that is required. We recommend that Web application backups be created in addition to regular backups at the farm level. This topic describes how to back up a single Web application. In this topic:  HYPERLINK \l "_Considerations_when_backing" Considerations when backing up a Web application  HYPERLINK \l "z1319" Task requirements  HYPERLINK \l "z1320" Use Windows PowerShell to back up a Web application  HYPERLINK \l "z1321" Use Central Administration to back up a Web application  HYPERLINK \l "z1322" Use SQL Server tools to back up a Web application Considerations when backing up a Web application Consider the following when you prepare to back up a Web application. You can back up only one Web application at a time by using the procedures in this article. However, you can simultaneously back up all Web applications by backing up the entire farm. Backing up a Web application does not affect the state of the farm. However, it does require resources and might slightly affect farm performance when the backup is running. You can avoid performance issues by backing up the Web application during hours when farm use is lowest, such as outside office hours. If the Web application uses the object cache, you must manually configure two special user accounts for the Web application after you restore the Web application. For more information about the object cache and how to configure these user accounts, see HYPERLINK \l "zcd646bb328c64040866c7d7936837ade"Configure object cache user accounts. When you back up a Web application, the Internet Information Services (IIS) settings and all content databases that are associated with the Web application are also backed up. When you back up a Web application that is configured to use forms-based authentication, you must also use a file backup system to protect the Web.config files because the Web.config files have been updated manually to register the membership and role providers, and manual changes to the Web.config files are not backed up. Similarly, Web.config files are not restored when you restore a Web application. After recovery, you must update the Web.config files and redeploy the providers. For more information, see HYPERLINK "http://technet.microsoft.com/library/40117fda-70a0-4e3d-8cd3-0def768da16c(Office.14).aspx"Plan authentication methods (SharePoint Server 2010) (http://technet.microsoft.com/library/40117fda-70a0-4e3d-8cd3-0def768da16c(Office.14).aspx) and HYPERLINK "http://technet.microsoft.com/library/83762baa-b23b-4b63-b14f-350421d9f18a(Office.14).aspx"Configure claims authentication (SharePoint Server 2010). (http://technet.microsoft.com/library/83762baa-b23b-4b63-b14f-350421d9f18a(Office.14).aspx) Task requirements Before you begin, you must create a network folder in which to store the backups. Both the Windows SharePoint Services Timer V4 service account and the server farm user account must have Full Control permissions to this folder. For more information about how to create a backup folder, see HYPERLINK \l "z56ea0f40426b43daaff5187fe5adc946"Prepare to back up and recover (SharePoint Server 2010). Use Windows PowerShell to back up a Web application You can use Windows PowerShell to back up a Web application manually or as part of a script that can be run at scheduled intervals. To back up a Web application by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. Additionally, the user account performing this procedure must be a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item <WebApplicationName> [-Verbose] Where: <BackupFolder> is the path of the folder you use for storing backup files. <WebApplicationName> is the name of the Web application. Note: If you are backing up the Web application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. For more information, see HYPERLINK "http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx"Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to back up a Web application You can use Central Administration to back up a Web application. To back up a Web application by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup. 3. On the Perform a Backup Step 1 of 2: Select Component to Back Up page, select the Web application from the list of components, and then click Next. Note: The Web application might consist of several components. You must select the top-level component. 4. On the Start Backup Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential. Note: If you are backing up the Web application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. 5. In the Back Up Only Configuration Settings section, click Back up content and configuration settings. 6. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup. 7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6.Use SQL Server tools to back up a Web application You cannot back up the complete Web application by using SQL Server tools. However, you can back up all the databases that are associated with the Web application. To back up the complete Web application, use either Windows PowerShell or Central Administration. To back up a Web application by using SQL Server tools 1. Verify that the user account that is used to back up the databases is a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored. Additionally, verify that the user account has Full Control permissions on the backup folder. 2. Open SQL Server Management Studio and connect to the database server. 3. In Object Explorer, expand Databases. 4. Right-click the database that you want to back up, point to Tasks, and then click Back Up. 5. In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see HYPERLINK " http://go.microsoft.com/fwlink/?LinkId=114396"Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396). 6. In the Backup component area, click Database. 7. Either use the default name provided or specify a name for the backup set in the Name text box. 8. Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days). 9. In the Destination area, specify where you want to store the backup. 10. Click OK to back up the database. 11. Repeat steps 1-10 for each database that is associated with the Web application.Related content Resource centerHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199235"Business Continuity Management for SharePoint Server 2010 (http://go.microsoft.com/fwlink/?LinkID=199235)IT Pro contentHYPERLINK "http://technet.microsoft.com/library/eae9208d-00ea-4cc1-919a-c399a0407bad(Office.14).aspx"Restore a Web application (Search Server 2010) (http://technet.microsoft.com/library/eae9208d-00ea-4cc1-919a-c399a0407bad(Office.14).aspx) HYPERLINK \l "zcbb3b24276ed4539b4544685a84d57c5"Restore a Web application (SharePoint Server 2010) HYPERLINK \l "z8daa31a50f8c4bd684c9ee1f5074594d"Back up a farm (SharePoint Server 2010) HYPERLINK "http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx"Plan for backup and recovery (SharePoint Server 2010) (http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx) HYPERLINK \l "z71abd06e6730442eb2c1e3ba9c04d497"Backup and recovery (SharePoint Server 2010)Developer contentHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199237"Data Protection and Recovery (http://go.microsoft.com/fwlink/?LinkID=199237) Back up a service application (SharePoint Server 2010) We recommend that you regularly back up at the farm level. However, business or IT requirements might require that you back up a service application. Regularly backing up a service application reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that helps to ensure that all the service application-related data and configurations are available for recovery, if that is required. You can back up only one service application at a time. For information about what to back up and which tools to use, see HYPERLINK "http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx"Plan for backup and recovery (SharePoint Server 2010) (http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx). You can back up all the service applications in the farm by backing up the complete farm. For more information, see HYPERLINK \l "z8daa31a50f8c4bd684c9ee1f5074594d"Back up a farm (SharePoint Server 2010). Backing up a service application does not affect the state of the farm. However, it does require resources. Therefore, backing up a service application might affect farm performance while the backup is running. You can avoid performance issues by backing up the service application during hours when farm use is lowest. Note SharePoint Server 2010 backup backs up remote Binary Large Object (BLOB) stores, but only if you are using the FILESTREAM remote BLOB store provider to put data in remote BLOB stores. If you are using another provider, you must manually back up the remote BLOB stores. Procedures in this topic:  HYPERLINK \l "z1423" Use Windows PowerShell to back up a service application  HYPERLINK \l "z1424" Use Central Administration to back up a service application Note: You cannot use SQL Server tools or Data Protection Manager to back up a service application. Task requirements Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. Note Microsoft SharePoint Server 2010 backup backs up the Business Data Connectivity service external content type definitions but does not back up the data source itself. To protect the data, you should back up the data source when you back up the Business Data Connectivity service or the farm. If you back up the Business Data Connectivity service or the farm and then restore the data source to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity service might not be able to locate the data source. Use Windows PowerShell to back up a service application You can use Windows PowerShell to back up one or more service applications manually or as part of a script that can be run at scheduled intervals. To back up a service application by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Backup-SPFarm -Directory -BackupMethod {Full | Differential} -Item [-Verbose] Note If you are backing up the service application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. Some service applications always require a full backup. For these service applications, even if you select the Differential option, the system performs a full backup. For more information, see HYPERLINK "http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx"Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to back up a service application You can use Central Administration to back up a service application. To back up a service application by using Central Administration 1. Verify that the user account that performs this procedure is a member of the Farm Administrators group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup. 3. On the Perform a Backup Step 1 of 2: Select Component to Back Up page, select the service application from the list of components, and then click Next. Note: The service application might consist of several components. You must select the top-level component. 4. On the Start Backup Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential. Note If you are backing up the service application for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. Some service applications always require a full backup. For these service applications, the system performs a full backup even if you select the Differential option. 5. In the Backup File Location section, in the Backup location box, type the path of the backup folder, and then click Start Backup. 6. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5. See Also HYPERLINK \l "z3e9dcd5053e64471a969aeb4d079dfa3"Restore a service application (SharePoint Server 2010) Back up search (SharePoint Server 2010) We recommend that you regularly back up at the farm level. However, business or IT requirements might require that you back up the search service and related resources. Regularly backing up the search system reduces the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that helps to ensure that data and configurations that compose the search system are available for recovery, if that is required. Backing up search does not affect the state of the farm. However, it does require resources. Therefore, backing up search might affect farm performance while the backup is running. You can avoid performance issues by backing up search during hours when farm use is lowest. Important: Use the procedures in this article to back up the search components of Microsoft SharePoint Server 2010. If the topology includes Microsoft FAST Search Server 2010 for SharePoint, the procedures in this article also back up the Content SSA and Query SSA (including the People Search index). However, in addition to the procedures in this article, you must run a backup of the FAST Search Server 2010 for SharePoint farm. Procedures in this article:  HYPERLINK \l "z1526" Use Windows PowerShell to back up search  HYPERLINK \l "z1527" Use Central Administration to back up search Note: You cannot use SQL Server tools or Data Protection Manager to back up all of the search components. Task requirements Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. Use Windows PowerShell to back up search You can use Windows PowerShell to back up search manually or as part of a script that can be run at scheduled intervals. This procedure backs up all of the search components including the databases, the search service configuration, and all of the index files. To back up search by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Backup-SPFarm -Directory-BackupMethod {Full | Differential} -Item[-Verbose] Note: If you are backing up the farm for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. To view the progress of the backup operation, use the Verbose parameter. For more information, see HYPERLINK "http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx"Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to back up search You can use Central Administration to back up search. This procedure backs up all of the search components including the databases, the search service configuration, and all of the index files. To back up search by using Central Administration 1. Verify that the user account that performs this procedure is a member of the Farm Administrators group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup. 3. On the Perform a Backup Step 1 of 2: Select Component to Back Up page, in the list of components, expand Shared Services and then expand Shared Services Applications to view the list of service applications in the farm. Select the search service application from the list of components, and then click Next. Note: The search service application might consist of several components. You must select the top-level component. By default, the service application is named Search Service Application. 4. On the Start Backup Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential. Note: If you are backing up search for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. 5. In the Backup File Location section, in the Backup location box, type the path of the backup folder, and then click Start Backup. 6. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are timer service jobs. Therefore, it might take several seconds for the backup to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6. Back up the Secure Store service (SharePoint Server 2010) In Microsoft SharePoint Server 2010, the Secure Store Service replaces Microsoft Office SharePoint Server 2007 Single Sign-on (SSO). The Secure Store Service provides the capability of securely storing credential sets and associating credentials to specific identities or a group of identities. Every time you enter a new passphrase, SharePoint Server 2010 creates a new Master Key and re-encrypts the credentials sets with that key. The passphrase gives you access to the Master Key created by SharePoint Server 2010 that is used to encrypt the credential sets. You should back up the Secure Store Service and record the passphrase after the Secure Store Service is initially configured and again every time that you make configuration changes to the Secure Store Service or re-encrypt the credential information. Important Before backing up the Secure Store Service, do the following: Record the passphrase. You will need the passphrase when you access the restored Secure Store Service. Ensure that you back up the Secure Store Service every time you change or refresh the Master Key. When you change or refresh the Master key, the database is automatically re-encrypted with the new key. Backing up the Secure Store Service ensures that the database and the Master key are in synchronization. Keep the passphrase in a secure location. Procedures in this task:  HYPERLINK \l "z1628" Use Windows PowerShell to back up the Secure Store Service  HYPERLINK \l "z1629" Use Central Administration to back up the Secure Store Service Task requirements Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. Use Windows PowerShell to back up the Secure Store Service You can use Windows PowerShell to back up the Secure Store Service manually or as part of a script that can be run at scheduled intervals. To back up the Secure Store Service by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Backup-SPFarm -Directory -BackupMethod Full -Item [-Verbose] Note: You must use the Full option to back up the Secure Store Service. For more information, see HYPERLINK "http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx"Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to back up the Secure Store Service You can use Central Administration to back up the Secure Store Service. To back up the Secure Store Service by using Central Administration 1. Verify that the user account that performs this procedure is a member of the Farm Administrators group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup. 3. On the Perform a Backup Step 1 of 2: Select Component to Back Up page, expand the Shared Services Applications node, select the Secure Store Service application from the list of components, and then click Next. Note: The Secure Store Service application might consist of several components. You must select the top-level component. 4. On the Start Backup Step 2 of 2: Select Backup Options page, in the Backup Type section, select Full. 5. In the Backup File Location section, in the Backup location box, type the path of the backup folder, and then click Start Backup. 6. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5. See Also HYPERLINK \l "z237d399eb50b42e690ffe659a94d8099"Restore secure store services (SharePoint Server 2010) Back up a content database (SharePoint Server 2010) Microsoft SharePoint Server 2010 content databases can grow to be very large. Therefore, you might want to back them up separately from farm backups. Regularly backing up content databases reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps to ensure that all the data is available for recovery, if that is required. You can only back up one content database at a time. This topic describes how to back up a single content database. Procedures in this task:  HYPERLINK \l "z1731" Use Windows PowerShell to back up a content database  HYPERLINK \l "z1732" Use Central Administration to back up a content database  HYPERLINK \l "z1733" Use SQL Server tools to back up a content database Task requirements Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. Note SharePoint Server 2010 backup backs up remote Binary Large Objects (BLOB) stores but only if you are using the SQL Filestream remote BLOB store provider to place data in remote BLOB stores. If you are using another provider you must manually back up these remote BLOB stores. Important: If you are using SQL Server with Transparent Data Encryption (TDE), and you are backing up your environment by using either SharePoint tools or SQL Server tools, the TDE encryption key in not backed up or restored. You must backup the key manually. When restoring, you must manually restore the key before restoring the data. For more information, see HYPERLINK "http://technet.microsoft.com/en-us/library/bb934049.aspx" \o "http://technet.microsoft.com/en-us/library/bb934049.aspx"Understanding Transparent Data Encryption (TDE) (http://technet.microsoft.com/en-us/library/bb934049.aspx). Use Windows PowerShell to back up a content database You can use Windows PowerShell to back up a content database manually or as part of a script that can be run at scheduled intervals. To back up a content database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Backup-SPFarm -Directory -BackupMethod {Full | Differential} -Item [-Verbose] Note: If you are backing up the content database for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. For more information, see HYPERLINK "http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx"Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to back up a content database You can use Central Administration to back up a content database. To back up a content database by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup. 3. On the Perform a Backup Step 1 of 2: Select Component to Back Up page, select the content database that you want to back up from the list of components, and then click Next. Note: Not all content databases can be selected in the list. If a database is not selectable, you must use Windows PowerShell to back up the content database. 4. On the Start Backup Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential. Note: If you are backing up the content database for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. 5. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup. 6. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status of the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, review the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 4.Use SQL Server tools to back up a content database You can use SQL Server tools to back up a content database. To back up a content database by using SQL Server tools 1. Verify that the user account that is performing this procedure is a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored. 2. Open SQL Server Management Studio and connect to the database server. 3. In Object Explorer, expand Databases. 4. Right-click the database that you want to back up, point to Tasks, and then click Back Up. 5. In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see HYPERLINK " http://go.microsoft.com/fwlink/?LinkId=114396"Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396) in SQL Server Books Online. 6. In the Backup component area, click Database. 7. Either use the default name provided or specify a name for the backup set in the Name text box. 8. Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days). 9. In the Destination area, specify where you want to store the backup. 10. Click OK to back up the database. 11. Repeat steps 1-9 for each content database that you want to back up. See Also HYPERLINK \l "z240f8caaafb344ce90bb861cfa258b09"Restore a content database (SharePoint Server 2010) Back up databases to snapshots (SharePoint Server 2010) This topic describes how to back up a farm database to a snapshot. You can only use SQL Server tools to back up a farm database to a snapshot. Important: You must be running Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2 Enterprise Edition to take database snapshots. We recommend that you regularly back up the complete farm. Regularly backing up the farm reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps to ensure that that all the farm data and configurations are available for recovery, if that is required. For more information, see HYPERLINK \l "z8daa31a50f8c4bd684c9ee1f5074594d"Back up a farm (SharePoint Server 2010). However, IT requirements might require that you backup databases to snapshots. Although you can back up any farm database to a snapshot, you typically back up content databases. A database snapshot provides a read-only, static view of a source database as it existed at snapshot creation, minus any uncommitted transactions. Uncommitted transactions are rolled back in a newly created database snapshot because the Database Engine runs recovery after the snapshot has been created (transactions in the database are not affected). For more information about database snapshots, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=163950"Database Snapshots (http://go.microsoft.com/fwlink/?LinkId=163950). Task requirements Before you begin, you must create a folder on the database server. If you want to store the snapshots at another location, you can move the backup files to a backup folder on the network after the operation is finished. Use SQL Server tools to back up a database to a snapshot If you want to back up databases to snapshots, you must use SQL Server tools. The databases that are associated with the farm are determined by the service applications and features that you have installed on the farm. To back up a database to a snapshot by using SQL Server tools 1. Verify that the account that is used to back up the databases is a member of the SQL Server db_owner fixed database role. 2. Open SQL Server Management Studio and connect to the database server. 3. In Object Explorer, expand Databases. 4. Select the database that you want to back up, and then click New Query. 5. Copy the following text, and then paste it to the query pane. CREATE DATABASE ON ( NAME=, FILENAME = 'c:\WSS_Backup1.ss') AS SNAPSHOT OF ;  See Also HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=163950"Database Snapshots (http://go.microsoft.com/fwlink/?LinkId=163950) Back up customizations (SharePoint Server 2010) This article describes how to back up customizations that have been made to Microsoft SharePoint Server 2010 sites. The following kinds of customizations can be made to sites: Customizations packaged as solutions (.wsp files). Solutions contain developed site elements, and are typically created by developers. Developed site elements include the following: Web Parts Workflows Site and list definitions Document converters Event receivers Timer jobs Assemblies Authored site elements, which are typically created by Web designers, are not explicitly compiled and reside in a content database. Authored site elements include the following: Master pages Cascading style sheets Forms Layout pages Changes to the Web.config file Third-party solutions and their associated binary files and registry keys, such as IFilters Changes to sites created by direct editing through the browser Developed customizations that are not packaged as solutions Each of these kinds of customizations requires a different type of backup. In this article:  HYPERLINK \l "_Backing_up_solution" Backing up solution packages  HYPERLINK \l "_Backing_up_authored" Backing up authored site elements  HYPERLINK \l "_Backing_up_workflows" Backing up workflows  HYPERLINK \l "_Backing_up_changes" Backing up changes to the Web.config file  HYPERLINK \l "_Backing_up_third-party" Backing up third-party products  HYPERLINK \l "z1941" Backing up changes made by direct editing  HYPERLINK \l "_Backing_up_developed" Backing up developed customizations that are not packaged as solutions Backing up solution packages Solution packages can be created by using Microsoft SharePoint Designer 2010 or Microsoft Visual Studio 2010. We strongly recommend that all customizations be deployed as solution packages. A solution package is a deployable, reusable file that can contain a set of Features, site definitions, and assemblies that apply to sites, and that you can enable or disable individually. Solution packages can include Web Parts, site or list definitions, custom columns, new content types, custom fields, custom actions, coded workflows, or workflow activities and conditions. The method that you use to back up solution packages is determined by whether the customizations are deployed as trusted solutions or sandboxed solutions. Trusted solutions are solution packages that farm administrators deploy. Trusted solutions are deployed to the entire farm and can be used on any site within the farm. Trusted solutions are stored in the configuration database. Trusted solutions are backed up when a farm is backed up by using SharePoint Server 2010 backup, and are included in configuration-only backups. You can also back up trusted solutions as a group or individually. Trusted solutions are visible in the backup hierarchy. Sandboxed solutions are solution packages that site collection administrators can deploy to a single site collection. Sandboxed solutions are stored in the content database that is associated with the site collection to which the solution packages are deployed. They are included in SharePoint Server 2010 farm, Web application, content database, and site collection backups, but are not visible in the backup hierarchy and cannot be selected or backed up individually. We recommend that you keep a backup of the original .wsp file as well as the source code used to build the .wsp file for both trusted solutions and sandboxed solutions. To back up trusted solutions by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup. 3. On the Perform a Backup Step 1 of 2: Select Component to Back Up page, select Solutions, and then click Next. You can also select an individual solution, if you only want to back up a single solution. 4. On the Start Backup Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential. Note: If you are backing up the solution for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup. 5. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup. 6. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status of the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, review the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 4.To back up trusted solutions by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command to back up all of the solutions in the farm. To back up a single solution, add the name of the solution to the item path "farm\solutions". Backup-SPFarm -backupmethod full -directory -item "farm\solutions" Where: <UNC location> is UNC location of the directory that you want to back up to. For more information, see HYPERLINK "http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx"Backup-SPFarm (http://technet.microsoft.com/library/c37704b5-5361-4090-a84d-fcdd17bbe345(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Backing up sandboxed solutions You cannot back up only sandboxed solutions. Instead, you must back up the farm, Web application, or content database with which the sandboxed solution is associated. For more information about these methods of backing up, see  HYPERLINK \l "_Related_content" Related content. Backing up authored site elements You cannot back up only authored site elements. Instead, you must back up the farm, Web application, or content database with which the authored site element is associated. For more information about these methods of backing up, see  HYPERLINK \l "z1943" Related content. Backing up workflows Workflows are a special case of customizations that you can back up. Make sure that your backup and recovery plan addresses any of the following scenarios that apply to your environment: Declarative workflows, such as those created in Microsoft SharePoint Designer 2010, are stored in the content database for the site collection to which they are they are deployed. Backing up the content database protects these workflows. Custom declarative workflow actions have components in the following three locations: a. The Visual Studio 2010assemblies for the actions are stored in the global assembly cache (GAC). b. The XML definition files (.ACTIONS files) are stored in the 14\TEMPLATE\\Workflow directory. c. An XML entry to mark the action as an authorized type is stored in the Web.config file for the Web applications in which it is used. If the farm workflows use custom actions, you should use a file backup system to protect these files and XML entries. Similar to SharePoint Server features such as Web Parts and event receivers, these files should be reapplied to the farm as needed after recovery. Workflows that depend on custom code, such as those that are created by using Visual Studio 2010, are stored in two locations. The Visual Studio 2010 assemblies for the workflow are stored in the GAC, and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Server features such as Web Parts and event receivers. If the workflow was installed as part of a solution package, backing up the farm, Web application, content database, or site collection protects these workflows. If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must back up both site collections to protect the workflow. This includes workflows that write to a history list or other custom list in another site collection. Performing a farm backup is sufficient to back up all site collections in the farm and all workflows that are associated with them. Workflows that are not yet deployed must be backed up and restored separately. When you are developing a new workflow but have not yet deployed it to the SharePoint Server farm, make sure that you back up the folder where you store the workflow project files by a file system backup application. Backing up changes to the Web.config file A common customization to SharePoint Server 2010 is to change the Web.config file. We strongly recommend that you make changes to the Web.config file by using Central Administration or the SharePoint Server 2010 APIs and object model. Because these changes are stored in the configuration database, they can be recovered from a farm or configuration-only backup. Changes to the Web.config file that are not made by using Central Administration or the SharePoint Server 2010 APIs and object model should be protected by using a file system backup. Note: If you are using forms-based authentication, provider registration in the Web.config file is manual, and is not protected by SharePoint Server 2010 backup. In this case, be sure to back up the Web.config file by using a file system backup. Backing up third-party products If third-party products are deployed as solution packages, they are protected by SharePoint Server 2010 backup. We recommend that you keep all the original files, distribution media, documentation, and the license and product keys that are required for installation. Backing up changes made by direct editing Changes made directly to a site by directly editing through the browser can be difficult to back up. The following table describes backup strategies for specific objects. Edited objectBackup strategyListUse SharePoint Designer 2010 and save as a template. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=199515"Save a SharePoint site as a template (http://go.microsoft.com/fwlink/?LinkId=199515).SiteUse SharePoint Designer 2010 and save as a template. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=199515"Save a SharePoint site as a template (http://go.microsoft.com/fwlink/?LinkId=199515).Site collectionUse site collection backup. For more information, see HYPERLINK \l "z45acdd33b3224f3697f10701159e15f0"Back up a site collection (SharePoint Server 2010).Backing up developed customizations that are not packaged as solutions Backing up developed customizations that are not deployed as solution packages can be a complex process because the customization file locations might not be stored in standardized places and SharePoint Server 2010 does not automatically back them up. Consult with the development team or customization vendor to determine whether the customizations involve additional add-in software or files in other locations. We recommend that you back up these directories with a file system backup solution. The following table lists locations where developed customizations are typically stored on Web servers. LocationDescription%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14Commonly updated files, custom assemblies, custom templates, custom site definitionsInetpubLocation of IIS virtual directories%WINDIR%\AssemblyGlobal assembly cache (GAC): a protected operating system location where the Microsoft .NET Framework code assemblies are installed to provide full system accessRelated content Resource CenterHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199235"Business Continuity Management for SharePoint Server 2010: Backup, Recovery, Availability, and Disaster Recovery (http://go.microsoft.com/fwlink/?LinkID=199235)IT Pro contentHYPERLINK "http://technet.microsoft.com/library/be4ca20f-520e-4fd7-9c42-140af800cbc8(Office.14).aspx"Deploy customizations - overview (SharePoint Server 2010) (http://technet.microsoft.com/library/be4ca20f-520e-4fd7-9c42-140af800cbc8(Office.14).aspx) HYPERLINK \l "z38147eecd89a478a956a779fe76c6679"Restore customizations (SharePoint Server 2010) HYPERLINK \l "z8daa31a50f8c4bd684c9ee1f5074594d"Back up a farm (SharePoint Server 2010) HYPERLINK \l "za6d383c038174acdafa9ad7a9b7e6b5a"Back up a farm configuration (SharePoint Server 2010) HYPERLINK \l "ze0ad657df5d14caebb0dd2b619eed261"Back up a Web application (SharePoint Server 2010) HYPERLINK \l "zdb44c8d7e08142a3a42a2ee1b369dd47"Back up a content database (SharePoint Server 2010) HYPERLINK \l "z45acdd33b3224f3697f10701159e15f0"Back up a site collection (SharePoint Server 2010)Developer contentHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=156638"Using solutions (MSDN) (http://go.microsoft.com/fwlink/?LinkID=156638) HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=199517"Sandboxed solutions (MSDN) (http://go.microsoft.com/fwlink/?LinkId=199517) Back up a site collection (SharePoint Server 2010) This article describes how to back up an individual site collection. We recommend that you regularly back up the complete farm. However, IT practices might require that you also back up a site collection. For more information about what to back up, see HYPERLINK "http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx"Plan for backup and recovery (SharePoint Server 2010) (http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx). Note: If the site collections Lock status is set to Not locked or Adding content prevented, Microsoft SharePoint Server 2010 temporarily sets the site to Read-Only while the backup operation is occurring. SharePoint Server 2010 does this to reduce the possibilities of users changing the site collection while it is being backed up. After the backup is finished, the setting is changed back its normal status. Performing a site collection backup might require resources and might slightly affect farm performance when the backup is running. You can help avoid performance issues by backing up the farm during hours when farm use is lowest, such as outside office hours. Procedures in this task:  HYPERLINK \l "z2044" Use Windows PowerShell to back up a site collection  HYPERLINK \l "z2045" Use Central Administration to back up a site collection Task requirements Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder. For more information about how to create a backup folder, see HYPERLINK \l "z56ea0f40426b43daaff5187fe5adc946"Prepare to back up and recover (SharePoint Server 2010). Use Windows PowerShell to back up a site collection You can use Windows PowerShell to back up a site collection manually or as part of a script that can be run at scheduled intervals. To back up a site collection by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt type the following command: Backup-SPSite -Identity -Path [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-Verbose] If you want to overwrite a previously used backup file, use the Force parameter. You can use the NoSiteLock parameter to keep the read-only lock from being set on the site collection while it is being backed up. However, using this parameter can allow users to change the site collection while it is being backed up and might lead to possible data corruption during backup. If the database server is running an Enterprise Edition of Microsoft SQL Server, we recommend that you also use the UseSqlSnapshot parameter for more consistent backups. You can also export sites or lists from these snapshots. Important When you perform a backup that uses the UseSqlSnapshot parameter, a backup will be completed successfully. However, you will see an error similar to the following: Backup-SPSite : Operation is not valid due to the current state of the object. At line:1 char:14+ Backup-SPSite <<<< http://site -Path + CategoryInfo : NotSpecified: (:) [Backup-SPSite], InvalidOperationException + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.SharePoint.PowerShell.SPCmdletBackupSite\\yourpath Note: If the RBS provider that you are using does not support snapshots, you cannot use snapshots for content deployment or backup. For example, the SQL FILESTREAM provider does not support snapshots. For more information about using SQL snap-shots, see HYPERLINK \l "z101dd66188434b98bab789c14abe65b8"Back up databases to snapshots (SharePoint Server 2010) and HYPERLINK "http://technet.microsoft.com/library/b44a57af-98a1-4818-aab3-a561908d0e07(Office.14).aspx"Content deployment overview (SharePoint Server 2010) (http://technet.microsoft.com/library/b44a57af-98a1-4818-aab3-a561908d0e07(Office.14).aspx). For more information, see HYPERLINK "http://technet.microsoft.com/library/d4c31a1a-82a7-425f-b1bb-22e70bedd338(Office.14).aspx"Backup-SPSite (http://technet.microsoft.com/library/d4c31a1a-82a7-425f-b1bb-22e70bedd338(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to back up a site collection You can use Central Administration to back up a site collection. To back up a site collection by using Central Administration 1. Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service has Full Control permissions on the backup folder. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Perform a site collection backup. 3. On the Site collection backup page, select the site collection from the Site Collection list. 4. Type the local path of the backup file in the Filename box. Note: If you want to reuse a file, select the Overwrite existing file check box. 5. Click Start Backup. 6. You can view the general status of all backup jobs at the top of the Granular Backup Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Site Collection Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, you can review them in the Failure Message column of the Granular Backup Job Status page. See Also HYPERLINK \l "zf8f81869a51f4d7fb4b652dd99078c23"Restore a site collection (SharePoint Server 2010) Export a site, list, or document library (SharePoint Server 2010) We recommend that you regularly back up the complete farm. However, business or IT requirements might require that you export a site, list, or document library. Regularly exporting sites, lists, and document libraries reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps to ensure that data is available for recovery, if that is required. You can only export one site, list, or document library at a time. For information about what to back up and which tools to use, see HYPERLINK "http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx"Plan for backup and recovery (SharePoint Server 2010) (http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx). Procedures in this task:  HYPERLINK \l "z2146" Use Windows PowerShell to export a site, list, or document library  HYPERLINK \l "z2147" Use Central Administration to export a site, list, or document library Note: You cannot use SQL Server tools or Data Protection Manager to export a site, list or document library. Task requirements Before you begin, you must create a folder on the local computer or the network in which to store the export file. For better performance, we recommend that you export to the local computer and then move the export file to a network folder. Use Windows PowerShell to export a site, list, or document library You can use Windows PowerShell to export a site, list, or document library manually or as part of a script that can be run at scheduled intervals. To export a site, list or document library by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Export-SPWeb -Identity-Path[-ItemUrl][-IncludeUserSecurity][-IncludeVersions][-NoFileCompression][-GradualDelete][-Verbose] If you are exporting a large site, list, or document library, you can use the GradualDelete parameter. When this parameter is used, the site collection is marked as deleted, which immediately prevents any further access to its content. The data in the deleted site collection is then deleted gradually over time by a timer job instead of all at once, which reduces its impact on the performance of farm servers and SQL Server. To specify which version of the site, list, or document library to include, use the IncludeVersions parameter and specify LastMajor (default), CurrentVersion, LastMajorandMinor, or All. To include the user security settings with the list or document library, use the IncludeUserSecurity parameter. If you want to overwrite the file that you specified, use the Force parameter. To view the progress of the backup operation, use the Verbose parameter. The NoFileCompression parameter lets you specify that no file compression is performed during the export process. Using this parameter can lower resource usage up to 30% during the export process. Using this parameter will result in a backup folder being created instead of a compressed file. If you use the NoFileCompression parameter in the Export-SPWeb command, you must also use it when you import the content by using the Import-SPWeb command. For more information, see HYPERLINK "http://technet.microsoft.com/library/cd85bf19-6f24-4f13-bd9c-37bbf279ea2b(Office.14).aspx"Export-SPWeb (http://technet.microsoft.com/library/cd85bf19-6f24-4f13-bd9c-37bbf279ea2b(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to export a site, list, or document library You can use Central Administration to export a site, list, or document library. You can only export one site, list, or document library at a time. To export a site, list, or document library by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group. 2. In Central Administration, on the Home page, click Backup and Restore. 3. On the Backup and Restore page, in the Granular Backup section, click Export a site or list. 4. On the Site or List Export page, in the Site Collection section, select the site collection from the Site Collection list, and then select the site from the Site list. 5. If you are exporting a site, skip this step, Select the list or document library from the List list. 6. In the File Location section, in the Filename box, type the UNC path of the shared folder and the file to which you want to export the list or document library. The file name must use the .cmp extension. 7. If the file already exists and you want to use this file, select the Overwrite existing files check box. Otherwise, specify a different file name. 8. If you want to export all the security and permissions settings with the list or library, in the Export Full Security section, select the Export full security check box. 9. If you want to specify which version of the list or library to export, select one of the following versions from the Export versions list: All Versions Last Major Current Version Last Major and Last Minor 10. When you have specified the settings that you want, click Start Export. 11. You can view the status of all backup jobs at the top of the Granular Backup Job Status page. You can view the status of the current backup job in the Content Export section of the page. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the .export.log file at the UNC path that you specified in step 6. See Also HYPERLINK "http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx"Plan for backup and recovery (SharePoint Server 2010) (http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx) Back up or archive logs (SharePoint Server 2010) A system-wide strategy for data protection should include backing up or archiving the logs in which data related to Microsoft SharePoint Server 2010 is recorded. This data can be useful for performance analysis, troubleshooting, monitoring compliance with service level agreements, and legal, regulatory, or business reasons. Therefore, protect this data as part of the routine maintenance by backing up or archiving the logs. The following sections are labeled in the following manner to indicate how important it is to back up or archive this kind of log: [Essential] means that the log contains data that is essential to the environment. The data would be lost if a disk failure or other problem occurred. [Recommended] means that the log contains data that is useful in most environments for troubleshooting, operational, legal, or other needs. In this article:  HYPERLINK \l "_[Essential]_Back_up" [Essential] Back up transaction logs  HYPERLINK \l "_[Recommended]_Collect_usage" [Recommended] Collect usage data  HYPERLINK \l "_[Recommended]_Archive_diagnostic" [Recommended] Archive diagnostic logs [Essential] Back up transaction logs Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3 transaction logs record all changes that were made to a database since the last checkpoint or full backup. These logs contain required data for restoring the farm. We recommend that you back up these logs every 510 minutes. When you back up these logs, they are automatically truncated. You can use the Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3 tools to back up the transaction log. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=124881" \o "Creating Transaction Log Backups"Creating Transaction Log Backups (http://go.microsoft.com/fwlink/?LinkId=124881) in the Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3 documentation. Transaction logs are also automatically backed up when you back up the farm, Web application, or databases by using either the SharePoint Central Administration Web site or the Windows PowerShell. For more information, see HYPERLINK \l "z8daa31a50f8c4bd684c9ee1f5074594d"Back up a farm (SharePoint Server 2010). How transaction log size affects farm backup times When you back up SharePoint Server 2010, the size of the transaction log can affect how long the backup operation takes. Because the transaction log records all changes to a database since the last checkpoint or full backup, the log can grow very large over time. If the transaction log has grown very large, backups might take a very long time. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=111458" \o "How to stop the transaction log of a SQL Server database from growing unexpectedly"How to stop the transaction log of a SQL Server database from growing unexpectedly  (http://go.microsoft.com/fwlink/?LinkID=111458). The recommended way to truncate the transaction log if you are using a full recovery model is to back up the log. Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, and SQL Server 2005 with SP3 and Cumulative Update 3 automatically truncates the inactive parts of the transaction log when you back up the log. We also recommend that you pre-grow the transaction log to avoid auto-growing the log. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=124882" \o "Managing the Size of the Transaction Log File"Managing the Size of the Transaction Log File (http://go.microsoft.com/fwlink/?LinkId=124882). For more information about using a full recovery model, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=127985" \o "Backup Under the Full Recovery Model"Backup Under the Full Recovery Model (http://go.microsoft.com/fwlink/?LinkId=127985). For more information about using a simple recovery model, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=127987" \o "Backup Under the Simple Recovery Model"Backup Under the Simple Recovery Model (http://go.microsoft.com/fwlink/?LinkId=127987). We do not recommend that you manually shrink the transaction log size or manually truncate the log by using the Truncate method. [Recommended] Collect usage data Usage analysis enables you to track how Web sites are being used. Log files are created daily to track usage. You can configure the setting for the collection of usage data. One of the most important settings is the location of the log files. By default, the log folder is configured to be on the same drive partition where SharePoint Server 2010 is installed. To make sure that the log files to not fill up that drive, you should change the log folder to be on a separate drive. The location of the log directory is a farm-level setting, and the directory that is specified in this setting must exist on all servers in the farm. These logs are automatically backed up when you back up the farm. For most environments, the default settings are adequate. For more information about configuring usage data collection settings, see HYPERLINK \l "z33ed78c825fc48eab0c150b540213cff"Configure usage and health data collection (SharePoint Server 2010). [Recommended] Archive diagnostic logs Diagnostic logs provide detailed information about the operation of the farm. You can configure the level of detail that is logged. We recommend that you archive these logs when you archive the farm. You can archive the logs for the whole farm or a specific server. You can archive these files by manually copying them to a shared folder, or by using the Windows PowerShell Merge-SPlogFile cmdlet. You can use the Merge-SPLogFIle cmdlet to archive the log files on all of the farm servers at once. You can use the Windows PowerShell Copy-Item cmdlet to archive log files from a single server. The Copy-Item cmdlet does not provide filtering and you must copy the entire log file. For more information about how to configure diagnostic logging, see HYPERLINK \l "zfaab1eb458484970b13fba6df14272fe"Configure diagnostic logging (SharePoint Server 2010). To archive diagnostic logs from all farm servers by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Merge-SPLogFile -Path ".log" -Overwrite For example, Merge-SPLogFile -Path "C:\Logs\MergedFiles\AllFarm_merged_12.20.2009.log" -Overwrite Important: Merging all log entries for all farm servers can take a long time and use resources. We recommend filtering the entries to match a specific set of criteria before merging. To merge log entries that match a specific set of criteria, type the following command: Merge-SPLogFile -Path "<path to merged log file>.log" -Area "<Area>" -Category "<Category>" You can filter by one or more of the following: Area (one or more, wildcard) Category (one or more, wildcard) Level Correlation (one or more) EventID (one or more, wildcard) Message (wildcard) StartTime EndTime Process (one or more, wildcard) ThreadID (one or more) Tip: You can name the merged log file however you want. We recommend that you use a naming convention that makes it easy to determine what the log file contains, such as __. For example, to signify all the farm server log entries forSharePoint Foundation 2010 that involve the database category and are marked as "High" use, "Dec_2009_ContosoInternet_Foundation_Database_High.log". For more information, see HYPERLINK "http://technet.microsoft.com/library/759702d7-bda2-4302-9345-abb43b609ad4(Office.14).aspx"Merge-SPLogFile (http://technet.microsoft.com/library/759702d7-bda2-4302-9345-abb43b609ad4(Office.14).aspx).To archive diagnostic logs for a specific server by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Copy-Item -Destination -Recurse For more information, type Get-Help Copy-Item -Full. Recovery (SharePoint Server 2010) The articles in this section are written to meet the requirements of information technology (IT) professionals who are responsible for the planning, design, deployment, and operations of backup and recovery solutions. These solutions might be in enterprise, corporate, or branch office environments. The IT professionals who are responsible for backup and recovery solutions are expected to have an understanding of the technical details that are contained in this section. However, service-level expertise is not needed to understand the enterprise-level discussions and decisions. Before you restore a farm, ensure that the following requirements are met: To restore a farm by using the SharePoint Central Administration Web site, you must be a member of the Farm Administrators group. To restore a farm by using Windows PowerShell, you must meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. The database server's SQL Server account, the Timer service account, and the Central Administration application pool account must have Read permissions to the backup locations. (The Timer service account and the Central Administration application pool account are usually the same.) The database server's SQL Server account must be a member of the sysadmin fixed server role. Your login account must have Read permissions to the backup locations. Ensure that the SharePoint Foundation Administration service is started on all farm servers. By default, this service is not started on stand-alone installations. Consider the following before you restore a farm: Restoring from one version of SharePoint Products and Technologies to a different version is not supported. After recovery, search might take as long as 15 minutes to be available again. It can take longer than 15 minutes if the search system has to crawl all the content again. If you back up and restore the complete service, the system does not have to perform a full crawl. You can only perform one recovery or one backup operation at a time. Recover all or part of a farm The following tasks for recovery are performed on the entire farm, farm databases, sites, subsites, or lists: HYPERLINK \l "z7942ef65c309402db4bbd54e686fc5d9"Restore a farm (SharePoint Server 2010) This article describes the procedures that you can use to restore the entire farm from a backup. HYPERLINK \l "zd849b7dfb26d45f6a74f6641f18788cf"Restore a farm configuration (SharePoint Server 2010) This article describes the procedures that you can use to restore the farm configuration to the same farm from a backup. HYPERLINK \l "z73d7f970c3784b3192d548cdeb8075e6"Document farm configuration settings (SharePoint Server 2010) This article describes how to use Windows PowerShell to document the configuration settings for your farm. Documenting configuration settings is important both so that you can create scripted deployments for your environment, and so that you can quickly re-create a set of configurations in the event of a failure. HYPERLINK \l "z8404adef6bfb4795be1615739e1212f5"Copy configuration settings from one farm to another (SharePoint Server 2010) This article describes the procedures that you can use to of copy configuration settings from one farm to another, including how to back up and recover a farm without the content databases, how to back up and recover configurations only, and how to create a deployment script. HYPERLINK \l "zcbb3b24276ed4539b4544685a84d57c5"Restore a Web application (SharePoint Server 2010) This article describes the procedures that you can use to restore a Web application that is associated with the farm, including configuration and content databases, from a backup. HYPERLINK \l "z3e9dcd5053e64471a969aeb4d079dfa3"Restore a service application (SharePoint Server 2010) This article describes the procedures that you can use to restore a service application that is associated with the farm, including configuration and content databases, from a backup. HYPERLINK \l "zf50ca1b2507549f6968946c7b8a29b47"Restore search (SharePoint Server 2010) This article describes the procedures that you can use to restore the Search service application associated with the farm, including configuration and indexes, from a backup. HYPERLINK \l "z237d399eb50b42e690ffe659a94d8099"Restore secure store services (SharePoint Server 2010) This article describes the procedures that you can use to restore the Secure Store service application that is associated with the farm, including configuration and content databases, from a backup. HYPERLINK \l "z240f8caaafb344ce90bb861cfa258b09"Restore a content database (SharePoint Server 2010) This article describes the procedures that you can use to restore a content database from a backup. HYPERLINK \l "z5417b04ac7d94e9a86fbee1d1c63508b"Attach and restore a read-only content database (SharePoint Server 2010) This article describes the procedures that you can use to attach a read-only content database to the farm. HYPERLINK \l "z38147eecd89a478a956a779fe76c6679"Restore customizations (SharePoint Server 2010) This article describes the procedures that you can use to restore customizations that are associated with the farm from backups. HYPERLINK \l "zf8f81869a51f4d7fb4b652dd99078c23"Restore a site collection (SharePoint Server 2010) This article describes the procedures that you can use to restore a site collection from a backup. HYPERLINK \l "zb3cb17a1939c43149f833c6b8a309bba"Import a list or document library (SharePoint Server 2010) This article describes the procedures that you can use to restore a site, list, or document library from a backup. See Also HYPERLINK \l "z79d47308a90a4c51a1ae93567e978236"Backup (SharePoint Server 2010) Restore a farm (SharePoint Server 2010) This article describes how to restore a Microsoft SharePoint Server 2010 farm. Farm-level recovery is usually performed only after a failure that involves the complete farm, or where partial recovery of part of the farm is not possible. If you only have to restore part of the farm, a specific database, a service application, a list, or document library, or a specific document, use another recovery method. For more information about alternate forms of recovery, see  HYPERLINK \l "z2455" Related content. Farm recovery is usually performed for any of the following reasons: Restoring a farm after a fire, disaster, equipment failure, or other data-loss event. Restoring farm configuration settings and data to a specific previous time and date. Moving a SharePoint Server 2010 deployment from one farm to another farm. In this article:  HYPERLINK \l "_Considerations_when_recovering" Considerations when recovering a farm  HYPERLINK \l "z2452" Use Windows PowerShell to restore a farm  HYPERLINK \l "z2453" Use Central Administration to restore a farm  HYPERLINK \l "z2454" Use SQL Server tools to restore a farm Considerations when recovering a farm When you prepare to recover a farm, be aware of the following issues: You cannot restore a multiple-server farm to a single-server farm or a single-server farm to a multiple-server farm. You cannot back up from one version of Microsoft SharePoint Server and restore to another version of SharePoint Server. Backing up the farm will back up the configuration and Central Administration content databases, but these cannot be restored using Microsoft SharePoint Server 2010 tools. For more information about backing up and restoring all the farm databases, see HYPERLINK \l "zd9dac1890736448d928c68bf38603613"Move all databases (SharePoint Server 2010). When you restore the farm by using Microsoft SharePoint Server 2010, the restore process will not automatically start all of the service applications. You must manually start them by using Central Administration or Windows PowerShell. Do not use SharePoint Products Configuration Wizard to start the services because doing so will also re-provision the services and service proxies. The identifier (ID) of each content database is retained when you restore or reattach a database by using built-in tools. Default change log retention behavior when using built-in tools is as follows: a. The change logs for all databases are retained when you restore a farm. b. The change log for content databases is retained when you reattach or restore a database. When a database ID and change log are retained, the search system continues crawling based on the regular schedule that is defined by crawl rules. When you restore an existing database and do not use the overwrite option, a new ID is assigned to the restored database, and the database change log is not preserved. The next crawl of the database will add data from the content database to the index. If a restore is performed and the ID in the backup package is already being used in the farm, a new ID is assigned to the restored database and a warning is added to the restore log. The ability to perform an incremental crawl instead of a full crawl depends on the content database ID being the same as before and the change log token that is used by the search system being valid for the current change log in the content database. If the change log is not preserved, the token is not valid and the search system has to perform a full crawl. SharePoint Server 2010 backup backs up the Business Data Connectivity service external content type definitions but does not back up the data source itself. To protect the data, you should back up the data source when you back up the Business Data Connectivity service or the farm. If you restore the Business Data Connectivity service or the farm and then restore the data source to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity service might be unable to locate the data source. SharePoint Server 2010 restores remote Binary Large Objects (BLOB) stores only if you are using the FILESTREAM remote BLOB store provider to put data in remote BLOB stores. If you are using another provider, you must manually restore the remote BLOB stores. If a user has taken copies of content for off-line editing in Microsoft SharePoint Workspace 2010 and the content is restored from a backup on the server, when the user re-connects, the server automatically synchronizes the off-line content with the restored content. This might result in data loss on the user's copies of the content. If you are sharing service applications across farms, be aware that trust certificates that have been exchanged are not included in farm backups. You must back up your certificate store separately or retain the certificates in a separate location. When you restore a farm that shares a service application, you must import and redeploy the certificates, and then re-establish any inter-farm trusts. For more information, see HYPERLINK \l "z6d8a9d37d4004d7cb4f1bf3c5643c98c"Exchange trust certificates between farms (SharePoint Server 2010). After a Web application that is configured to use claims-based authentication has been restored, duplicate or additional claims providers are often visible. If duplicates appear, you must then manually save each Web application zone to remove them. For more information, see HYPERLINK \l "zcbb3b24276ed4539b4544685a84d57c5"Restore a Web application (SharePoint Server 2010). Additional steps are required when you restore a farm that contains a Web application that is configured to use forms-based authentication. For more information, see HYPERLINK \l "zcbb3b24276ed4539b4544685a84d57c5"Restore a Web application (SharePoint Server 2010). Use Windows PowerShell to restore a farm You can use Windows PowerShell to restore a farm. To restore a farm by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Restore-SPFarm -Directory <BackupFolder> -RestoreMethod Overwrite [-BackupId <GUID>] Where: <BackupFolder> is the path of the folder you use for storing backup files. <GUID> is the identifier of the backup to restore from. Note: If you are not logged on as the Farm account, you are prompted for the Farm account s credentials. If you do not specify the BackupId, the most recent backup will be used. To view the backups for the farm, type the following command, and then press ENTER: Get-SPBackupHistory -Directory -ShowBackup [-Verbose] You cannot use a configuration-only backup to restore content databases together with the configuration. 6. To restart service applications, type the following command, and then press ENTER: Start-SPServiceInstance -Identity Where is the GUID of the service application. To restart all service applications, use Start-SPServiceInstance without any parameters. For more information about restarting service applications by using Windows PowerShell, see HYPERLINK "http://technet.microsoft.com/library/fcb4a4f8-a95f-468e-918b-d9a2d736cd2d(Office.14).aspx"Start-SPServiceInstance (http://technet.microsoft.com/library/fcb4a4f8-a95f-468e-918b-d9a2d736cd2d(Office.14).aspx). For more information about restoring the farm by using Windows PowerShell, see HYPERLINK "http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx"Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to restore a farm You can use the Central Administration Web site to restore a farm. To restore a farm by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup. 3. On the Restore from Backup Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the farm backup, and then click Next. You can view more details about each backup by clicking the (+) next to the backup. Note If the correct backup job does not appear, in the Backup Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh. You cannot use a configuration-only backup to restore the farm. 4. On the Restore from Backup Step 2 of 3: Select Component to Restore page, select the check box that is next to the farm, and then click Next. 5. On the Restore from Backup Step 3 of 3: Select Restore Options page, in the Restore Component section, ensure that Farm appears in the Restore the following component list. In the Restore Only Configuration Settings section, ensure that the Restore content and configuration settings option is selected. In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box will appear that asks you to confirm the operation. Click OK. Note: If the Restore Only Configuration Settings section does not appear, the backup that you selected is a configuration-only backup. You must select another backup. Click Start Restore. 6. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3. 7. When the restore process has completed, you may need to restart one or more service applications. In Central Administration, on the Home page, in the Application Management section, click Manage services on server. 8. On the Services on Server page, start any services related to service applications that you want to run by clicking Start in the Actions column next to the service application. 9. Re-establish any trust relationships. For more information, see HYPERLINK \l "z6d8a9d37d4004d7cb4f1bf3c5643c98c"Exchange trust certificates between farms (SharePoint Server 2010).Use SQL Server tools to restore a farm Although you cannot restore the complete farm by using SQL Server tools, you can restore most of the farm databases. If you restore the databases by using SQL Server tools, you must restore the farm configuration by using Central Administration or Windows PowerShell. For more information about how to restore the farms configuration settings, see HYPERLINK \l "zd849b7dfb26d45f6a74f6641f18788cf"Restore a farm configuration (SharePoint Server 2010). Note: The search index is not stored in SQL Server. If you use SQL Server tools to back up and restore search, you must perform a full crawl after you restore the content database. Before you restore SharePoint Server 2010, we recommend that you configure a recovery farm for site and item recovery. Restore the databases by following these steps: 1. If possible, back up the live transaction log of the current database to protect any changes that were made after the last full backup. 2. Restore the last full database backup. 3. Restore the most recent differential database backup that occurred after the most recent full database backup. 4. Restore all transaction log backups that occurred after the most recent full or differential database backup. To restore a farm by using SQL Server tools 1. Verify that the user account that is performing this procedure is a member of the sysadmin fixed server role. 2. If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish. Do not restart the service until after you restore all the databases that you have to restore. 3. Start SQL Server Management Studio and connect to the database server. 4. In Object Explorer, expand Databases. 5. Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database. The database is automatically taken offline during the recovery operation and cannot be accessed by other processes. 6. In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore. The default values for destination and source are appropriate for most recovery scenarios. 7. In the Select a page pane, click Options. 8. In the Restore options section, select only Overwrite the existing database. Unless your environment or policies require otherwise, do not select the other options in this section. 9. In the Recovery state section: If you have included all the transaction logs that you must restore, select RECOVER WITH RECOVERY. If you must restore additional transaction logs, select RECOVER WITH NORECOVERY. The third option, RECOVER WITH STANDBY is not used in this scenario. Note: For more information about these recovery options, see HYPERLINK " http://go.microsoft.com/fwlink/?LinkId=114420"Restore Database (Options Page) (http://go.microsoft.com/fwlink/?LinkId=114420). 10. Click OK to complete the recovery operation. 11. Except for the configuration database, repeat steps 4 through 9 for each database that you are restoring. Important: If you are restoring the User Profile database (by default named "User Profile Service_ProfileDB_), then also restore the Social database (by default named User Profile Service_SocialDB_). Failing to do so can cause inaccuracies in the User Profile data that might be difficult to detect and fix. 12. To restore the configuration settings, you must use the existing configuration database or manually create a new database and restore the configuration to that database. For more information about restoring the farm configuration, see HYPERLINK \l "zd849b7dfb26d45f6a74f6641f18788cf"Restore a farm configuration (SharePoint Server 2010). 13. Start the Windows SharePoint Services Timer service. 14. Start any service applications that have to be restarted. To do this, see steps 7 and 8 of the Use Central Administration to restore a farm procedure earlier in this article.Related content Resource centerHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199235"Business Continuity Management for SharePoint Server 2010: Backup, Recovery, Availability, and Disaster Recovery (http://go.microsoft.com/fwlink/?LinkID=199235)IT Pro contentHYPERLINK \l "z8daa31a50f8c4bd684c9ee1f5074594d"Back up a farm (SharePoint Server 2010). HYPERLINK \l "zd849b7dfb26d45f6a74f6641f18788cf"Restore a farm configuration (SharePoint Server 2010) HYPERLINK \l "zcbb3b24276ed4539b4544685a84d57c5"Restore a Web application (SharePoint Server 2010) HYPERLINK \l "z240f8caaafb344ce90bb861cfa258b09"Restore a content database (SharePoint Server 2010) Restore a farm configuration (SharePoint Server 2010) This topic describes how to a restore the configuration of a farm. Note: In previous versions of Microsoft SharePoint Server 2010, you could not restore the configuration database and, therefore, you could not restore the configuration of a farm. In this version of SharePoint Server 2010, you do not have to restore the configuration database because you can restore the farm configuration directly. Procedures in this task:  HYPERLINK \l "z2556" Use Windows PowerShell to restore a farm s configuration  HYPERLINK \l "z2557" Use Central Administration to restore a farm s configuration Overview Farm-level configuration recovery is performed only after a failure that involves the configuration database but does not involve other farm data, such as a content database or Web application. If restoring the farm configuration does not solve the problems, you must restore the complete farm. For more information about restoring the complete farm, see HYPERLINK \l "z7942ef65c309402db4bbd54e686fc5d9"Restore a farm (SharePoint Server 2010). You can restore the configuration from a farm backup that used either the Backup content and configuration settings option or the Backup only configuration settings option. Use Windows PowerShell to restore a farms configuration You can use Windows PowerShell to restore a farms configuration. To restore a farms configuration by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. From the Windows PowerShell command prompt (that is, PS C:\>), type the following command and press ENTER: Restore-SPFarm -Directory -RestoreMethod Overwrite -ConfigurationOnly You must use the ConfigurationOnly parameter. To view the progress of the operation, use the Verbose parameter. For more information, see HYPERLINK "http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx"Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to restore a farms configuration You can use Central Administration to restore a farms configuration. To restore a farm's configuration by using Central Administration 1. To perform this procedure, you must be a member of the Farm Administrators SharePoint group on the computer that is running Central Administration. You must also be a member of the sysadmin fixed server role on the database server where each database is stored. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup. 3. On the Restore from Backup Step 1 of 3: Select Backup to Restore page, select the backup job that contains the farm backup from the list of backups, and then click Next. Note: You can view additional information about the backups by expanding the row that contains the backup. Note: If the correct backup job does not appear, in the Backup Directory Location text box, enter the UNC path of the correct backup folder, and then click Refresh. 4. On the Restore from Backup Step 2 of 3: Select Component to Restore page, select the check box that is next to the farm, and then click Next. 5. On the Restore from Backup Step 3 of 3: Select Restore Options page, in the Restore Component section, ensure that "Farm" appears in the Restore the following content list. In the Restore Only Configuration Settings section, ensure that the Restore content and configuration settings option is selected. In the Restore Options section, select the Type of Restore option. Use the Same configuration setting. A dialog box will appear that asks you to confirm the operation. Click OK. Note: If the Restore Only Configuration Settings section does not appear, then the backup that you selected is a configuration-only backup. Click Start Restore. 6. You can view the general status of all recovery jobs at the top of the Backup and Restore Status page in the Readiness section. You can view the status of the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 2.Use SQL Server to restore a farm's configuration You cannot restore a farm's configuration by using SQL Server tools. See Also HYPERLINK \l "za6d383c038174acdafa9ad7a9b7e6b5a"Back up a farm configuration (SharePoint Server 2010) Document farm configuration settings (SharePoint Server 2010) This article describes how to use Windows PowerShell 2.0 to document the configuration settings for your farm. Documenting configuration settings is important both so that you can create scripted deployments for your environment, and so that you can quickly re-create a set of configurations in the event of a failure. To document configuration settings by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. Using Notepad, create a text file and then copy and paste the following script into the file. The commands in the example create XML files that document the configurations of the Web applications and service applications in the current farm. Choose only those commands that are relevant to your environment. ## ## Common SharePoint configuration settings ## #Retrieve Web Application information. The default depth of 2 does not return much detail--we recommend that you use a depth of 4 for this cmdlet. Get-SPWebApplication | Export-Clixml .\ WebAppFilename.xml -depth 4 #Retrieve custom layout information. Get-SPWebApplication | Get-SPCustomLayoutsPage | Export-Clixml .\Get-SPCustomLayoutsPage.xml #Determine how SharePoint designer access is configured. Get-SPWebApplication | Get-SPDesignerSettings | Export-Clixml .\Get-SPDesignerSettings.xml #Retrieve information about alternate access mapping Get-SPAlternateURL | Export-Clixml .\Get-SPAlternateURL.xml #Retrieve information about content databases Get-SPContentDatabase | Export-Clixml .\Get-SPContentDatabase.xml #Retrieve database properties for each database Get-SPDatabase | Export-Clixml .\Get-SPDatabase.xml #Retrieve information about all SharePoint Products installed in the farm, and the versions of all updates installed for each product. Get-SPProduct | Export-Clixml .\Get-SPProduct.xml #Retrieve farm information Get-SPFarm | Export-Clixml .\Get-SPFarm.xml Get-SPFarmConfig | Export-Clixml .\Get-SPFarmConfig.xml #Retrieve information about the servers in the farm Get-SPServer | Export-Clixml .\Get-SPServer.xml #Retrieve information about installed features Get-SPFeature | Export-Clixml .\Get-SPFeature.xml #Retrieve information about globally-installed site templates Get-SPWebTemplate | Export-Clixml .\Get-SPWebTemplate.xml #Retrieve information about deployed solutions Get-SPSolution | Export-Clixml .\Get-SPSolution.xml #Retrieve information about sandboxed solutions deployed in a site collection Get-SPSite | Get-SPUserSolution | Export-Clixml .\Get-SPUserSolution.xml #Retrieve information about claims authentication Get-SPTrustedIdentityTokenIssuer | Export-Clixml .\Get-SPTrustedIdentityTokenIssuer.xml Get-SPTrustedServiceTokenIssuer | Export-Clixml .\Get-SPTrustedServiceTokenIssuer.xml Get-SPTrustedRootAuthority | Export-Clixml .\Get-SPTrustedRootAuthority.xml #Retrieve information about installed Help Get-SPHelpCollection | Export-Clixml .\Get-SPHelpCollection.xml #Retrieve information about the logging levels that have been set Get-SPLogLevel | Export-Clixml .\Get-SPLogLevel.xml #Retrieve information about the sites in the farm Get-SPSite | Export-Clixml .\Get-SPSite.xml Get-SPSiteAdministration | Export-Clixml .\Get-SPSiteAdministration.xml Get-SPSiteSubscription | Export-Clixml .\Get-SPSiteSubscription.xml #Retrieve ULS logging information Get-SPDiagnosticConfig | Export-Clixml .\Get-SPDiagnosticConfig.xml Get-SPDiagnosticsPerformanceCounter | Export-Clixml .\Get-SPDiagnosticsPerformanceCounter.xml Get-SPDiagnosticsProvider | Export-Clixml .\Get-SPDiagnosticsProvider.xml #Retrieve information about accounts registered in the configuration database Get-SPManagedAccount | Export-Clixml .\Get-SPManagedAccount.xml Get-SPProcessAccount | Export-Clixml .\Get-SPProcessAccount.xml Get-SPShellAdmin | Export-Clixml .\Get-SPShellAdmin.xml #Retrieve specific information about the certificate authority Get-SPCertificateAuthority | Export-Clixml .\Get-SPCertificateAuthority.xml Get-SPClaimProvider | Export-Clixml .\Get-SPClaimProvider.xml Get-SPClaimProviderManager | Export-Clixml .\Get-SPClaimProviderManager.xml #Retrieve information about content deployment jobs Get-SPContentDeploymentJob | Export-Clixml .\Get-SPContentDeploymentJob.xml Get-SPContentDeploymentPath | Export-Clixml .\Get-SPContentDeploymentPath.xml #Retrieve information about the Mobile Messaging account. Get-SPWebApplication | Get-SPMobileMessagingAccount | Export-Clixml .\Get-SPMobileMessagingAccount.xml ## ##Common service infrastructure settings ## #Retrieve information about the service applications in the farm Get-SPServiceApplication | Export-Clixml .\Get-SPServiceApplication.xml Get-SPServiceApplicationPool | Export-Clixml .\Get-SPServiceApplicationPool.xml Get-SPServiceApplicationProxy | Export-Clixml .\Get-SPServiceApplicationProxy.xml Get-SPServiceApplicationProxyGroup | Export-Clixml .\Get-SPServiceApplicationProxyGroup.xml Get-SPServiceApplication | Get-SPServiceApplicationEndpoint | Export-Clixml .\Get-SPServiceApplicationEndpoint.xml #Retrieve information about the services running in the farm Get-SPServiceInstance | Export-Clixml .\Get-SPServiceInstance.xml #Retrieve information about InfoPath form services Get-SPInfoPathFormsService | Export-Clixml .\Get-SPInfoPathFormsService.xml Get-SPInfoPathFormTemplate | Export-Clixml .\Get-SPInfoPathFormTemplate.xml ###WARNING: The following cmdlet requires run as administrator rights. Get-SPInfoPathUserAgent | Export-Clixml .\Get-SPInfoPathUserAgent.xml #Retrieve information about common Web service settings Get-SPServiceHostConfig | Export-Clixml .\Get-SPServiceHostConfig.xml ## ## Common service application settings ## #Access Services #Retrieve specific information for the Access Services service application Get-SPAccessServiceApplication | Export-Clixml .\Get-SPAccessServiceApplication.xml #Application Discovery and Load Balancer Service Application Get-SPTopologyServiceApplication | Export-Clixml .\Get-SPTopologyServiceApplication.xml Get-SPTopologyServiceApplicationProxy | Export-Clixml .\Get-SPTopologyServiceApplicationProxy.xml #Business Data Connectivity Service #Retrieve information about data connection files. ###WARNING: The following cmdlet requires run as administrator rights Get-SPDataConnectionFile | Export-Clixml .\Get-SPDataConnectionFile.xml ###WARNING: The following cmdlet requires run as administrator rights Get-SPDataConnectionFile | Get-SPDataConnectionFileDependent | Export-Clixml .\Get-SPDataConnectionFileDependent.xml #Excel Services Application #Note: An Excel service application must be provisioned for the following cmdlets to succeed. Get-SPExcelServiceApplication | Get-SPExcelBlockedFileType | Export-Clixml .\Get-SPExcelBlockedFileType.xml Get-SPExcelServiceApplication | Get-SPExcelDataConnectionLibrary | Export-Clixml .\Get-SPExcelDataConnectionLibrary.xml Get-SPExcelServiceApplication | Get-SPExcelDataProvider | Export-Clixml .\Get-SPExcelDataProvider.xml Get-SPExcelServiceApplication | Get-SPExcelFileLocation | Export-Clixml .\Get-SPExcelFileLocation.xml Get-SPExcelServiceApplication | Export-Clixml .\Get-SPExcelServiceApplication.xml Get-SPExcelServiceApplication | Get-SPExcelUserDefinedFunction | Export-Clixml .\Get-SPExcelUserDefinedFunction.xml Get-SPWebApplication | Get-SPInfoPathWebServiceProxy | Export-Clixml .\Get-SPInfoPathWebServiceProxy.xml Get-SPWebApplication | Get-SPManagedPath | Export-Clixml .\Get-SPManagedPath.xml #Managed Metadata Service #Note: A Managed Metadata service application must be provisioned for the following cmdlets to succeed. Get-SPServiceApplication | ?{$_.TypeName -eq "Managed Metadata Service"} | %{$id = $_.Id;Get-SPMetadataServiceApplication -Id $_ | Export-Clixml .\Get-SPMetadataServiceApplication-$id.xml} Get-SPServiceApplicationProxy | ?{$_.TypeName -eq "Managed Metadata Service Connection"} | %{$id = $_.Id;Get-SPMetadataServiceApplicationProxy -Id $_ | Export-Clixml .\Get-SPMetadataServiceApplicationProxy-$id.xml} Get-SPSite | Get-SPTaxonomySession | Export-Clixml .\Get-SPTaxonomySession.xml #PerformancePoint Service Application #Note: A PerformancePoint service application must be provisioned for the following cmdlets to succeed. Get-SPPerformancePointServiceApplication | Get-SPPerformancePointSecureDataValues | Export-Clixml .\Get-SPPerformancePointSecureDataValues.xml Get-SPPerformancePointServiceApplication | Export-Clixml .\Get-SPPerformancePointServiceApplication.xml Get-SPPerformancePointServiceApplication | Get-SPPerformancePointServiceApplicationTrustedLocation | Export-Clixml .\Get-SPPerformancePointServiceApplicationTrustedLocation.xml #Search #Retrieve search information #Note: A Search service application must be provisioned for the following cmdlets to succeed. Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchAdministrationComponent | Export-Clixml .\Get-SPEnterpriseSearchAdministrationComponent.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchCrawlContentSource | Export-Clixml .\Get-SPEnterpriseSearchCrawlContentSource.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchCrawlCustomConnector | Export-Clixml .\Get-SPEnterpriseSearchCrawlCustomConnector.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchCrawlDatabase | Export-Clixml .\Get-SPEnterpriseSearchCrawlDatabase.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchCrawlExtension | Export-Clixml .\Get-SPEnterpriseSearchCrawlExtension.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchCrawlMapping | Export-Clixml .\Get-SPEnterpriseSearchCrawlMapping.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchCrawlRule | Export-Clixml .\Get-SPEnterpriseSearchCrawlRule.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchCrawlTopology | Export-Clixml .\Get-SPEnterpriseSearchCrawlTopology.xml $searchApp = Get-SPEnterpriseSearchServiceApplication; Get-SPEnterpriseSearchExtendedClickThroughExtractorJobDefinition -SearchApplication $searchApp | Export-Clixml .\Get-SPEnterpriseSearchExtendedClickThroughExtractorJobDefinition.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchExtendedConnectorProperty | Export-Clixml .\Get-SPEnterpriseSearchExtendedConnectorProperty.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchExtendedQueryProperty | Export-Clixml .\Get-SPEnterpriseSearchExtendedQueryProperty.xml ###WARNING: The following cmdlet generates a 120MB file that records the out of the box settings### Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchLanguageResourcePhrase | Export-Clixml .\Get-SPEnterpriseSearchLanguageResourcePhrase.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchMetadataCategory | Export-Clixml .\Get-SPEnterpriseSearchMetadataCategory.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchMetadataCrawledProperty | Export-Clixml .\Get-SPEnterpriseSearchMetadataCrawledProperty.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchMetadataManagedProperty | Export-Clixml .\Get-SPEnterpriseSearchMetadataManagedProperty.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchMetadataMapping | Export-Clixml .\Get-SPEnterpriseSearchMetadataMapping.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchPropertyDatabase | Export-Clixml .\Get-SPEnterpriseSearchPropertyDatabase.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchQueryAuthority | Export-Clixml .\Get-SPEnterpriseSearchQueryAuthority.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchQueryDemoted | Export-Clixml .\Get-SPEnterpriseSearchQueryDemoted.xml Get-SPEnterpriseSearchQueryAndSiteSettingsService | Export-Clixml .\Get-SPEnterpriseSearchQueryAndSiteSettingsService.xml Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance | Export-Clixml .\Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance.xml Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy | Export-Clixml .\Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy.xml Get-SPEnterpriseSearchService | Export-Clixml .\Get-SPEnterpriseSearchService.xml Get-SPEnterpriseSearchServiceInstance | Export-Clixml .\Get-SPEnterpriseSearchServiceInstance.xml Get-SPSearchService | Export-Clixml .\Get-SPSearchService.xml Get-SPSearchServiceInstance | Export-Clixml .\Get-SPSearchServiceInstance.xml ###WARNING: The following cmdlet generates a file per site collection### Get-SPSite | %{$id = $_.Id;Get-SPEnterpriseSearchQueryKeyword -Site $_ | Export-Clixml .\Get-SPEnterpriseSearchQueryKeyword-$id.xml} Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchQueryScope | Export-Clixml .\Get-SPEnterpriseSearchQueryScope.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchQueryScope | Get-SPEnterpriseSearchQueryScopeRule | Export-Clixml .\Get-SPEnterpriseSearchQueryScopeRule.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchQuerySuggestionCandidates | Export-Clixml .\Get-SPEnterpriseSearchQuerySuggestionCandidates.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchQueryTopology | Export-Clixml .\Get-SPEnterpriseSearchQueryTopology.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchRankingModel | Export-Clixml .\Get-SPEnterpriseSearchRankingModel.xml Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchSecurityTrimmer | Export-Clixml .\Get-SPEnterpriseSearchSecurityTrimmer.xml Get-SPEnterpriseSearchServiceApplication | Export-Clixml .\Get-SPEnterpriseSearchServiceApplication.xml Get-SPEnterpriseSearchServiceApplicationProxy | Export-Clixml .\Get-SPEnterpriseSearchServiceApplicationProxy.xml Get-SPEnterpriseSearchSiteHitRule | Export-Clixml .\Get-SPEnterpriseSearchSiteHitRule.xml #Security Token Service Application #Retrieve information about the security token service used for incoming SOAP messages. Get-SPSecurityTokenServiceConfig | Export-Clixml .\Get-SPSecurityTokenServiceConfig.xml #State Service #Retrieve information about the State Service. Get-SPSessionStateService | Export-Clixml .\Get-SPSessionStateService.xml Get-SPStateServiceApplication | Export-Clixml .\Get-SPStateServiceApplication.xml Get-SPStateServiceApplicationProxy | Export-Clixml .\Get-SPStateServiceApplicationProxy.xml Get-SPStateServiceDatabase | Export-Clixml .\Get-SPStateServiceDatabase.xml #Usage and Health data collection #Retrieve information about the Usage and Health Data Collection service application. Get-SPUsageApplication | Export-Clixml .\Get-SPUsageApplication.xml Get-SPUsageDefinition | Export-Clixml .\Get-SPUsageDefinition.xml Get-SPUsageService | Export-Clixml .\Get-SPUsageService.xml #Visio Service #A Visio service application must be provisioned for the following cmdlets to succeed. Get-SPVisioServiceApplication | Get-SPVisioExternalData | Export-Clixml .\Get-SPVisioExternalData.xml Get-SPVisioServiceApplication | Get-SPVisioPerformance | Export-Clixml .\Get-SPVisioPerformance.xml Get-SPVisioServiceApplication | Get-SPVisioSafeDataProvider | Export-Clixml .\Get-SPVisioSafeDataProvider.xml Get-SPVisioServiceApplication | Export-Clixml .\Get-SPVisioServiceApplication.xml Get-SPVisioServiceApplicationProxy | Export-Clixml .\Get-SPVisioServiceApplicationProxy.xml #Web Analytics Service Application A Web Analytics service application must be provisioned for the following cmdlets to succeed. Get-SPServiceApplication | ?{$_.TypeName -eq "Web Analytics Service Application"} | %{$id = $_.Id;Get-SPWebAnalyticsServiceApplication -Id $_ | Export-Clixml .\Get-SPWebAnalyticsServiceApplication-$id.xml} Get-SPServiceApplicationProxy | ?{$_.TypeName -eq "Web Analytics Service Application Proxy"} | %{$id = $_.Id;Get-SPWebAnalyticsServiceApplicationProxy -Id $_ | Export-Clixml .\Get-SPWebAnalyticsServiceApplicationProxy-$id.xml} Get-SPWebApplication | Get-SPWebApplicationHttpThrottlingMonitor | Export-Clixml .\Get-SPWebApplicationHttpThrottlingMonitor.xml Get-SPWebPartPack | Export-Clixml .\Get-SPWebPartPack.xml #Word Automation Services ###Note: These cmdlets are commented out because you are unlikely to want to run them. ### #Get-SPSite | %{$web=Get-SPWeb $_.Url;$webid=$web.Id;$web | Get-SPUser | Export-Clixml .\Get-SPUser-$webid.xml} # Get-SPSite | %{$web=Get-SPWeb $_.Url;$webid=$web.Id;$web | Export-Clixml .\Get-SPWeb-$webid.xml} 6. To run the script, in the Windows PowerShell console, at the command prompt (that is, PS C:\>), type the following command and press ENTER:C:\\.ps1 For more information, see HYPERLINK "http://technet.microsoft.com/en-us/library/dd347657.aspx"Export-Clixml (http://technet.microsoft.com/en-us/library/dd347657.aspx), HYPERLINK "http://technet.microsoft.com/library/11d6521f-f99c-433e-9ab5-7cf9e953457a(Office.14).aspx"Get-SPWebApplication (http://technet.microsoft.com/library/11d6521f-f99c-433e-9ab5-7cf9e953457a(Office.14).aspx), HYPERLINK "http://technet.microsoft.com/library/71a467dc-3b95-4b65-af93-0d0d6ebb8326(Office.14).aspx"Get-SPServiceApplication (http://technet.microsoft.com/library/71a467dc-3b95-4b65-af93-0d0d6ebb8326(Office.14).aspx). Example of using a cmdlet This section provides an example of ways that you can use one of the recommended cmdlets. The Get-SPAlternateURL cmdlet provides information about alternate access mapping. Piping the cmdlet to the Export-Clixml cmdlet writes the information to an XML file. Get-SPAlternateURL | Export-Clixml .\Get-SPAlternateURL.xml The following section lists the content of the Get-SPAlternateURL.xml file. Some sections are collapsed. - + - Microsoft.SharePoint.Administration.SPAlternateUrl - http://servername http://servername/ + - - - Microsoft.SharePoint.Administration.SPAlternateUrl + - Default http://servername - 1 false Alternate Access Mapping Collection SharePoint - 80 0 false false false SharePoint - 80 5b65a69a-222d-4fe0-904b-0fb928bc7a89 Online SPFarm Name=SERVERNAME_SharePoint_Configuration_Database 3661 + SPFarm Name=SERVERNAME_SharePoint_Configuration_Database + + Default 0 http://servername This example imports the output from the XML file, so that you can see its contents more easily. Import-Clixml .\Get-SPAlternateURL.xml Once an XML file is imported, you can use the objects in the pipeline as though they were real objects of the given type. Import-Clixml .\Get-SPAlternateURL.xml | %{$_.Uri} You can also pipe the objects as part of the cmdlet, and view all of the expected properties, methods, and TypeNames. The following example pipes URIs. Import-Clixml .\Get-SPAlternateURL.xml | %{$_.Uri | Get-Member} For more information, see HYPERLINK "http://technet.microsoft.com/en-us/library/dd347657.aspx"Export-Clixml (http://technet.microsoft.com/en-us/library/dd347657.aspx), HYPERLINK "http://technet.microsoft.com/en-us/library/dd315355.aspx"Import-Clixml (http://technet.microsoft.com/en-us/library/dd315355.aspx), HYPERLINK "http://technet.microsoft.com/library/ea38119d-a535-48a3-b498-9daa443399fb(Office.14).aspx"Get-SPAlternateURL (http://technet.microsoft.com/library/ea38119d-a535-48a3-b498-9daa443399fb(Office.14).aspx), HYPERLINK "http://technet.microsoft.com/en-us/library/dd347608.aspx"ForEach-Object (http://technet.microsoft.com/en-us/library/dd347608.aspx), HYPERLINK "http://technet.microsoft.com/en-us/library/dd315351.aspx"Get-Member (http://technet.microsoft.com/en-us/library/dd315351.aspx). Copy configuration settings from one farm to another (SharePoint Server 2010) This article describes how to copy configuration settings from one Microsoft SharePoint Server 2010 farm to another SharePoint Server 2010 farm. Copying the configuration settings of one farm to another can be useful in the following circumstances: Setting up similar development, test, and production environments. Establishing an organization standard for farm configuration settings. Setting up a disaster recovery environment. In this article: HYPERLINK \l "_Back_up_and"Back up and recover a farm without content databases to copy configuration settings () HYPERLINK \l "z2759"Back up and recover configuration settings only HYPERLINK \l "_Create_a_scripted"Create a scripted deployment to copy configuration settings There are many ways in which you can copy configurations from one farm to another. Determine which method to use based on the configuration settings that you want to copy and how often you need to copy them. Back up and recover a farm without the content databases attached. This method provides you with farm settings and Web application settings, in addition to the settings for any service applications that you select. Back up and recover configurations only. This method provides you with the core SharePoint Foundation 2010 settings only. Note: This method does not include Web application or service application settings. If Web application settings are required in the recovered farm, use one of the other methods. Create a deployment script, based on your documented configuration. This method may be more work initially, but is easy to use to maintain standardization. Back up and recover a farm without content databases to copy configuration settings To copy configuration settings by using a farm backup, we recommend that you first detach the content databases from the farm. This is not a step that we recommend that you take with a live production farm. Note: Creating a farm backup without content databases does back up the service applications. To back up and recover a farm without content databases by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command to document the current Web application URLs and content database mappings. Get-SPWebApplication | %{$_.Name;$_.Url;%{$_.ContentDatabases|%{$_.Name};Write-Host ""}} 6. Either dismount all content databases, as in the following example: Get-SPContentDatabase | Dismount-SPContentDatabase Or dismount a specific content database, as in the following example: Get-SPContentDatabase WSS_Content | Dismount-SPContentDatabase 7. Back up the farm. Backup-SPFarm -Directory \\servername\share -BackupMethod Full Note: You can view the progress of the backup by looking at the \\servername\share\spbr####\spbackup.log file. 8. After the backup is complete, re-mount the content databases. Replace and with each of the mappings documented in step 1). Mount-SPContentDatabase -Name -WebApplication Back up and recover configuration settings only As part of farm backup, you can choose to back up only configuration settings. A configuration-only backup extracts and backs up many, but not all, configuration settings from a configuration database. By using built-in tools, you can back up the configuration of any configuration database, whether it is currently attached to a farm or not. For detailed information about how to back up a configuration, see HYPERLINK \l "za6d383c038174acdafa9ad7a9b7e6b5a"Back up a farm configuration (SharePoint Server 2010).A configuration backup can be restored to the same or any other server farm. When a configuration is restored, it will overwrite any settings present in the farm that have values that are set within the configuration backup. If any settings present in the farm are not contained in the configuration backup, they will not be overwritten. For detailed information about how to restore a farm configuration, see HYPERLINK \l "zd849b7dfb26d45f6a74f6641f18788cf"Restore a farm configuration (SharePoint Server 2010). Create a scripted deployment to copy configuration settings When you create a scripted deployment of SharePoint Server 2010, you are creating copies of configuration settings. For more information, see HYPERLINK "http://technet.microsoft.com/library/7443092a-87a6-4063-a7d0-8d10d9d23682(Office.14).aspx"Install SharePoint Server 2010 by using Windows PowerShell (http://technet.microsoft.com/library/7443092a-87a6-4063-a7d0-8d10d9d23682(Office.14).aspx). Restore a Web application (SharePoint Server 2010) This article describes how to restore a Web application. When you restore a Web application, you also restore the Internet Information Services (IIS) settings and all content databases that are associated with the Web application. In this article:  HYPERLINK \l "z2861" Considerations when backing up a Web application  HYPERLINK \l "z2862" Use Windows PowerShell to restore a Web application  HYPERLINK \l "z2863" Use Central Administration to restore a Web application  HYPERLINK \l "_Additional_steps_to" Additional steps to restore a Web application that uses forms-based authentication Considerations when backing up a Web application Consider the following information as you prepare to restore a Web application. You can only restore one Web application at a time by using the procedures in this article. However, you can simultaneously restore all the Web applications in the farm by restoring the complete farm. If a Web application uses the object cache, you must manually configure two special user accounts for the Web application after you restore the Web application. For more information about the object cache and how to configure these user accounts, see HYPERLINK \l "zcd646bb328c64040866c7d7936837ade"Configure object cache user accounts. You cannot use SQL Server tools to restore a Web application. When you restore a Web application that is configured to use claims authentication, there are additional steps that you must follow after restoring the Web application to restore claims authentication. Use Windows PowerShell to restore a Web application You can use Windows PowerShell to restore a Web application manually or as part of a script that can be run at scheduled intervals. To restore a Web application by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Restore-SPFarm -Directory<BackupFolderName>-RestoreMethod Overwrite -Item <WebApplicationName>[-BackupId<GUID>][-Verbose] Where: <BackupFolderName> is the full path of the folder you use for backup files. <WebApplicationName> is the name of the Web application that was backed up. <GUID> is the identifier of the backup to use for the restore operation. If you do not specify the value of the BackupID parameter, the most recent backup will be used. You cannot restore a Web application by using a configuration-only backup. You can view the backups for the farm by typing the following: Get-SPBackupHistory -Directory-ShowBackup For more information, see HYPERLINK "http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx"Restore-SPFarm ( HYPERLINK "http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx)" http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to restore a Web application You can use Central Administration to restore a Web application. To restore a Web application by using Central Administration 1. Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service and the Farm Database Access account have Full Control permissions on the backup folder. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup. 3. On the Restore from Backup Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the farm or Web application backup, and then click Next. You can view more details about each backup by clicking the (+) next to the backup. Note If the correct backup job does not appear, in the Current Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh. You cannot use a configuration-only backup to restore the Web application. 4. On the Restore from Backup Step 2 of 3: Select Component to Restore page, select the check box that is next to the Web application, and then click Next. 5. On the Restore from Backup Step 3 of 3: Select Restore Options page, in the Restore Component section, make sure that Farm\ appears in the Restore the following content list. In the Restore Only Configuration Settings section, make sure that the Restore content and configuration settings option is selected. In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK. Note: If the Restore Only Configuration Settings section does not appear, the backup that you selected is a configuration-only backup. You must select another backup. Click Start Restore. 6. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified.Additional steps to restore a Web application that uses forms-based authentication After you restore a Web application that uses forms-based authentication, you must perform the following steps to reconfigure the Web application to use forms-based authentication. 1. Re-register the membership and role providers in the Web.config file. 2. Redeploy the providers. For more information, see HYPERLINK "http://technet.microsoft.com/library/fd1391bb-c787-4742-b007-bf57e18dad66(Office.14).aspx"Configure forms-based authentication for a claims-based Web application (SharePoint Server 2010) (http://technet.microsoft.com/library/fd1391bb-c787-4742-b007-bf57e18dad66(Office.14).aspx). Additional steps to remove duplicate claims providers after restoring a Web application that uses claims-based authentication After a Web application that is configured to use claims-based authentication has been restored, duplicate or additional claims providers are often visible. You must follow this process to remove the duplicate providers: 1. In Central Administration, click Manage Web application, select a Web application that uses claims-based authentication, and then click Authentication Providers. 2. Select a zone that the Web application is associated with to open the Edit Authentication page, and then click Save. 3. Repeat for each zone, and then for each Web application that uses claims-based authentication. Related content Resource centerHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199235"Business Continuity Management for SharePoint Server 2010 (http://go.microsoft.com/fwlink/?LinkID=199235)IT Pro contentHYPERLINK \l "ze0ad657df5d14caebb0dd2b619eed261"Back up a Web application (SharePoint Server 2010) HYPERLINK "http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx"Plan for backup and recovery (SharePoint Server 2010) (http://technet.microsoft.com/library/01abe8d2-33f8-48fe-af76-40522a5afe08(Office.14).aspx) HYPERLINK \l "z71abd06e6730442eb2c1e3ba9c04d497"Backup and recovery (SharePoint Server 2010)Developer contentHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199237"Data Protection and Recovery (http://go.microsoft.com/fwlink/?LinkID=199237) Restore a service application (SharePoint Server 2010) There are situations in which you might have to restore a specific service application instead of restoring the complete farm. Some service applications for example, the Business Data Connectivity service application and the User Profile service application provide data to other services and sites. As a result, users might experience some service interruption until the recovery process is finished. For information about how to simultaneously restore all the service applications in a farm, see HYPERLINK \l "z7942ef65c309402db4bbd54e686fc5d9"Restore a farm (SharePoint Server 2010). Important: You cannot back up from one version of Microsoft SharePoint Server and restore to another version of SharePoint Server. Note SharePoint Server 2010 backs up the Business Data Connectivity Service metadata store, which includes external content types, external systems, and BDC models. For more information, see HYPERLINK "http://technet.microsoft.com/library/e58bd6c6-74b2-4471-80b0-b627b482ab33(Office.14).aspx"Business Data Connectivity service administration overview (SharePoint Server 2010) (http://technet.microsoft.com/library/e58bd6c6-74b2-4471-80b0-b627b482ab33(Office.14).aspx). Note that this does not back up the external data sources. To protect the data, the external data sources must be backed up. If you restore the service application or the farm and then restore the data source to a different location, you must change the location information in the external content type definition. If you do not, the Business Data Connectivity Service might not be able to locate the data source. Note SharePoint Server 2010 restores remote Binary Large Object (BLOB) stores but only if you are using the FILESTREAM provider to put data in remote BLOB stores. If you are using another provider, you must manually restore remote BLOB stores. Procedures in this article:  HYPERLINK \l "z2965" Use Windows PowerShell to restore a service application  HYPERLINK \l "z2966" Use Central Administration to restore a service application  HYPERLINK \l "z2967" Use SQL Server tools to restore the databases for a service application Note: You cannot restore the complete service application but you can restore the databases associated with the service application. To flush the Office Web Apps cache by using Windows PowerShell Use Windows PowerShell to restore a service application You can use Windows PowerShell to restore a service application. To restore a service application by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Restore-SPFarm -Directory -Item -RecoveryMethod Overwrite [-BackupId ] [-Verbose] To specify which backup to use, use the BackupId parameter. You can view the backups for the farm by typing the following: Get-SPBackupHistory -Directory -ShowBackup. If you do not specify the BackupId, the most recent backup will be used. You cannot restore a service application from a configuration-only backup. For more information, see HYPERLINK "http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx"Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to restore a service application Use the following procedure to restore a service application by using the SharePoint Central Administration Web site. To restore a service application by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup. 3. On the Restore from Backup Step 1 of 3: Select Backup to Restore page, select the backup job that contains the service application backup, or a farm-level backup, from the list of backups, and then click Next. You can view more details about each backup by clicking the (+) next to the backup. Note If the correct backup job does not appear, in the Backup Directory Location text box, type the path of the correct backup folder, and then click Refresh. You cannot use a configuration-only backup to restore the farm. 4. On the Restore from Backup Step 2 of 3: Select Component to Restore page, expand Shared Services Applications, select the check box that is next to the service application, and then click Next. 5. On the Restore from Backup Step 3 of 3: Select Restore Options page, in the Restore Component section, make sure that Farm\Shared Services Applications\ appears in the Restore the following component list. In the Restore Options section, under Type of restore, select the Same configuration option. A dialog box will appear that asks you to confirm the operation. Click OK. Click Start Restore. 6. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take a several seconds for the recovery to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3.Use SQL Server tools to restore the databases for a service application You cannot restore the complete service application by using SQL Server tools. However, you can use SQL Server tools to restore the databases that are associated with the service application. To restore the complete service application, use either Windows PowerShell or Central Administration. To restore the databases for a service application by using SQL Server tools 1. Verify that the user account that you are using to restore the databases is a member of the SQL Server sysadmin fixed server role on the database server where each database is stored. 2. Open SQL Server Management Studio and connect to the database server. 3. In Object Explorer, expand Databases. 4. Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database. 5. In the Restore Database dialog box, on the General page, select the database to restore to from the To database drop-down list. 6. Select the restore source from the From database drop-down list. 7. In the Select the backup sets to restore section area, select the check box next to the database. 8. On the Options tab, select the recovery state from the Recover state section. For more information about which recovery type to use, see HYPERLINK " http://go.microsoft.com/fwlink/?LinkId=114396"Overview of Recovery Models (http://go.microsoft.com/fwlink/?LinkId=114396) in SQL Server Books Online. 9. Click OK to restore the database. 10. Repeat steps 1-9 for each database that is associated with the service application.To flush the Office Web Apps cache by using Windows PowerShell 1. If you are restoring Microsoft Office Web Apps, you must flush the cache after the restore process is complete to ensure that the correct timer jobs are created. 2. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 3. On the Start menu, click All Programs. 4. Click Microsoft SharePoint 2010 Products. 5. Click SharePoint 2010 Management Shell. 6. At the Windows PowerShell command prompt, type the following command: Get-SPOfficeWebAppsCache | Remove-SPOfficeWebAppsCache -Confirm:$false Restore search (SharePoint Server 2010) There are situations in which you might have to restore the search system instead of restoring the complete farm. Important: You cannot back up from one version of Microsoft SharePoint Server and restore to another version of SharePoint Server. Important: The procedures in this topic restore the search components of Microsoft SharePoint Server 2010. If the topology includes Microsoft FAST Search Server 2010 for SharePoint, then the procedures in this topic also restore the Content SSA and Query SSA (including the People Search index). However, in addition to the procedures in this topic, you must restore the FAST Search Server 2010 for SharePoint farm. Procedures in this topic:  HYPERLINK \l "z3069" Use Windows PowerShell to restore a search service application  HYPERLINK \l "z3070" Use Central Administration to restore a search service application Note: You cannot use SQL Server tools to restore all of the search components. Use Windows PowerShell to restore a search service application You can use Windows PowerShell to restore search. This procedure restores all of the search components including the databases, the search service configuration, and all of the index files. To restore a search service application by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Restore-SPFarm -Directory-Item-RecoveryMethod Overwrite[-BackupId][-Verbose] To specify which backup to use, use the BackupId parameter. To view the backups for the farm, type the following command, and then press ENTER: Get-SPBackupHistory -Directory-ShowBackup. If you do not use the BackupId parameter, the most recent backup will be used. You cannot restore search from a configuration-only backup. For more information, see HYPERLINK "http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx"Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to restore a search service application Use the following procedure to restore search by using the SharePoint Central Administration Web site. This procedure restores all of the search components including the databases, the search service configuration, and all of the index files. To restore a search service application by using Central Administration 1. Verify that the user account performing this procedure is a member of the Farm Administrators group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup. 3. On the Restore from Backup Step 1 of 3: Select Backup to Restore page, select the backup job that contains the search backup, or a farm-level backup, from the list of backups, and then click Next. You can view more details about each backup by clicking the (+) next to the backup. Note If the correct backup job does not appear, in the Backup Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh. You cannot use a configuration-only backup to restore search. 4. On the Restore from Backup Step 2 of 3: Select Component to Restore page, expand the Shared Services Applications node. 5. Select the check box that is next to the search service application, and then click Next. 6. On the Restore from Backup Step 3 of 3: Select Restore Options page, in the Restore Component section, make sure that Farm\Shared Services Applications\ appears in the Restore the following content list. In the Restore Options section, under Type of restore, select the Same configuration option. If you select this option, a dialog box appears that asks you to confirm the operation. Click OK. 7. Click Start Restore. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are timer service jobs. Therefore, it may take a several seconds for the recovery to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3. Restore secure store services (SharePoint Server 2010) In Microsoft SharePoint Server 2010, the Secure Store Service replaces Microsoft Office SharePoint Server 2007 Single Sign-on (SSO). The Secure Store Service provides the capability of securely storing credential sets and associating credentials to specific identities or a group of identities. Every time you enter a new passphrase, SharePoint Server 2010 creates a new Master Key and re-encrypts the credentials sets with that key. The passphrase gives you access to the Master Key created by SharePoint Server 2010 that is used to encrypt the credential sets. Important: You will need the passphrase that was recorded when the Secure Store Service was backed up to restore the Secure Store Service. Procedures in this task:  HYPERLINK \l "z3171" Use Central Administration to restore the Secure Store Service  HYPERLINK \l "z3172" Use Windows PowerShell to restore the Secure Store Service Use Central Administration to restore the Secure Store Service Use the following procedure to restore the Secure Store Service by using the SharePoint Central Administration Web site. To restore the Secure Store Service by using Central Administration 1. Verify that the user account performing this procedure is a member of the Farm Administrators group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup. 3. On the Restore from Backup Step 1 of 3: Select Backup to Restore page, select the backup job that contains the backup that you want, or a farm-level backup, from the list of backups, and then click Next. You can view more details about each backup by clicking the (+) next to the backup. Note If the correct backup job does not appear, in the Backup Directory Location text box, type the path of the correct backup folder, and then click Refresh. You cannot use a configuration-only backup to restore the Secure Store Service. 4. On the Restore from Backup Step 2 of 3: Select Component to Restore page, expand Shared Services Applications and select the check box that is next to the Secure Store Service application backup group, and then click Next. 5. On the Restore from Backup Step 3 of 3: Select Restore Options page, in the Restore Component section, make sure that Farm\Shared Services\Shared Services Applications\ appears in the Restore the following component list. In the Restore Options section, under Type of restore, select the Same configuration option. A dialog box will appear that asks you to confirm the operation. Click OK. Click Start Restore. 6. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take a several seconds for the recovery to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the path that you specified in step 3. 7. After the restore operation has successfully completed, you must refresh the passphrase. 8. In Central Administration, on the Home page, in the Application Management section, click Manage service applications. 9. On the Service Applications page, click the Secure Store Service name. You might receive an error that says Unable to obtain master key. 10. On the Secure Store Service page, on the ribbon, click Refresh Key. 11. In the Refresh Key dialog box, type the passphrase in the Pass Phrase box, and then click OK.Use Windows PowerShell to restore the Secure Store Service You can use Windows PowerShell to restore a the Secure Store Service. To restore the Secure Store Service by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Restore-SPFarm -Directory -Item-RecoveryMethod Overwrite[-BackupId][-Verbose] To specify which backup to use, use the BackupId parameter. You can view the backups for the farm by typing the following: Get-SPBackupHistory -Directory-ShowBackup. If you do not specify a value for the BackupId parameter, the most recent backup will be used. You cannot restore the Secure Store Service from a configuration-only backup. For more information, see HYPERLINK "http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx"Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx). 6. After the restore operation has successfully completed, you must refresh the passphrase. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Update-SPSecureStoreApplicationServerKey -Passphrase For more information, see HYPERLINK "http://technet.microsoft.com/library/53234b26-d767-483a-a75f-0f2c195f8747(Office.14).aspx"Update-SPSecureStoreApplicationServerKey (http://technet.microsoft.com/library/53234b26-d767-483a-a75f-0f2c195f8747(Office.14).aspx). See Also HYPERLINK \l "zd08d6d6523c248cba8711e021a382e5e"Back up the Secure Store service (SharePoint Server 2010) Restore a content database (SharePoint Server 2010) You can restore any content database or several content databases, one at a time. For information about how to back up all the content databases in a farm at the same time, see HYPERLINK \l "z8daa31a50f8c4bd684c9ee1f5074594d"Back up a farm (SharePoint Server 2010). Note SharePoint Server 2010 restores up remote Binary Large Objects (BLOB) stores but only if you are using the SQL Filestream remote BLOB store provider to place data in remote BLOB stores. If you are using another provider you must manually restore these remote BLOB stores. Note: If a user has taken copies of content for off-line editing in Microsoft SharePoint Workspace 2010 and the content is restored from a backup on the server, when the user re-connects, the server automatically synchronizes the off-line content with the restored content. This might result in data loss on the user's copies of the content. Procedures in this task:  HYPERLINK \l "z3273" Use Windows PowerShell to restore a content database  HYPERLINK \l "z3274" Use Central Administration to restore a content database  HYPERLINK \l "z3275" Use SQL Server tools to restore a content database Use Windows PowerShell to restore a content database You can use Windows PowerShell to restore a content database. To restore a content database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Restore-SPFarm -Directory-RestoreMethod Overwrite-Item[-BackupId][-Verbose] Note: If you are not logged on as the Farm account, you are prompted for the Farm accounts credentials. If you do not use the BackupId parameter, the most recent backup will be used. To view a list of the backups, including their Backup IDs, type the following command, and then press ENTER: Get-SPBackupHistory -Directory For more information, see HYPERLINK "http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx"Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Use Central Administration to restore a content database You can use Central Administration to restore a farm or components of a farm. To restore a content database by using Central Administration 1. Verify that you are logged on as a member of the Farm Administrators group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup. 3. On the Restore from Backup Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the content database backup, and then click Next. Note: If the correct backup job does not appear, in the Current Directory Location text box, enter the path of the correct backup folder, and then click Refresh. 4. On the Restore from Backup Step 2 of 3: Select Component to Restore page, select the check box that is next to the content database, and then click Next. Note: If the content database is not selectable, you must use Windows PowerShell or SQL Server tools to restore the content database. 5. On the Restore from Backup Step 3 of 3: Select Restore Options page, in the Restore Options section, under Type of Restore, click the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK. Click Start Restore. 6. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 2.Use SQL Server tools to restore a content database You can use SQL Server tools to restore a content database by following these steps: 1. If possible, back up the live transaction log of the content database to protect any changes that were made after the last full backup. 2. Restore the last full database backup. 3. Restore the most recent differential database backup that occurred after the most recent full database backup. 4. Restore all transaction log backups that occurred after the most recent full or differential database backup. To restore a content database by using SQL Server tools 1. Verify that the user account performing this procedure is a member of the sysadmin fixed server role. 2. If the Windows SharePoint Services Timer service is running, stop the service and wait for several minutes for any currently running stored procedures to finish. Do not restart the service until after you restore the content databases. 3. Start SQL Server Management Studio and connect to the database server. 4. In Object Explorer, expand Databases. 5. Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database. The database is automatically taken offline during the recovery operation and cannot be accessed by other processes. 6. In the Restore Database dialog box, specify the destination and the source, and then select the backup set or sets that you want to restore. The default values for destination and source are appropriate for most recovery scenarios. 7. In the Select a page pane, click Options. 8. In the Restore options section, select only Overwrite the existing database. Unless the environment or policies require otherwise, do not select the other options in this section. 9. In the Recovery state section: If you have included all the transaction logs that you must restore, select RECOVER WITH RECOVERY. If you must restore additional transaction logs, select RECOVER WITH NORECOVERY. The third option, RECOVER WITH STANDBY is not used in this scenario. Note: For more information about these recovery options, see HYPERLINK " http://go.microsoft.com/fwlink/?LinkId=114420"Restore Database (Options Page) (http://go.microsoft.com/fwlink/?LinkId=114420). 10. Click OK to complete the recovery operation. 11. Repeat steps 4 through 10 for each database that you are restoring. 12. Start the Windows SharePoint Services Timer service. See Also HYPERLINK \l "zdb44c8d7e08142a3a42a2ee1b369dd47"Back up a content database (SharePoint Server 2010) Attach and restore a read-only content database (SharePoint Server 2010) A Microsoft SharePoint Server 2010 farm in which content databases have been set to be read-only can be part of a failure recovery environment that runs against mirrored or log-shipped content databases or part of a highly available maintenance or patching environment that provides user access when another version of the farm is being updated. When you re-attach the read-only databases, they become read-write. For more information about how to use read-only databases, see HYPERLINK \l "z8b91dc0ac37d4ec8aa75deb3f268fb97"Run a farm that uses read-only databases (SharePoint Server 2010). Use Windows PowerShell to attach and restore a read-only content database You can use only Windows PowerShell to attach and restore a read-only content database. To attach and restore a read-only content database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Mount-SPContentDatabase -Name-WebApplication[-Verbose] Note: Attaching a content database by using the Mount-SPContentDatabase cmdlet differs from attaching a database in SQL Server by using SQL Server tools. Mount-SPContentDatabase associates the content database with a Web application so that the contents can be read. For more information, see HYPERLINK "http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx"Mount-SPContentDatabase (http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Restore customizations (SharePoint Server 2010) This article describes how to restore customizations that have been made to sites in a Microsoft SharePoint Server farm. This article assumes that you are familiar with the concepts and procedures in HYPERLINK \l "z8f98a75019bb4ea09ff5719b85febbb3"Back up customizations (SharePoint Server 2010). In this article:  HYPERLINK \l "_Restoring_solution_packages" Restoring solution packages  HYPERLINK \l "_Restoring_authored_site" Restoring authored site elements  HYPERLINK \l "_Restoring_workflows" Restoring workflows  HYPERLINK \l "_Restoring_changes_to" Restoring changes to the Web.config file  HYPERLINK \l "_Recovering_changes_made" Recovering changes made by direct editing  HYPERLINK \l "_Restoring_developed_customizations" Restoring developed customizations that are not packaged as solutions Restoring solution packages The method that you use to restore solution packages is determined by whether the customizations were deployed as trusted solutions or sandboxed solutions. Trusted solutions are solutions that farm administrators deploy. They are deployed to the entire farm, and can be used on any site within the farm. Trusted solutions are stored in the configuration database. Trusted solutions are backed up when a farm is backed up by using SharePoint Server 2010 backup, and are included in configuration-only backups, and can also be backed up as a group, or individually. They are visible in the restore hierarchy. Sandboxed solutions are solutions that site collection administrators can deploy to a single site collection. Sandboxed solutions are stored in the content database associated with the site collection that they are deployed to. They are included in SharePoint Server 2010 farm, Web application, content database, and site collection backups, but are not visible in the restore hierarchy, and cannot be selected or restored individually. We recommend that you keep a backup of the original .wsp file as well as the source code used to build the .wsp file for both trusted and sandboxed solutions. To restore a trusted solution by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. 2. In Central Administration, on the Home page, in the Backup and Restore section, click Restore from a backup. 3. On the Restore from Backup Step 1 of 3: Select Backup to Restore page, from the list of backups, select the backup job that contains the solution package, and then click Next. You can view more details about each backup by clicking the (+) next to the backup. Note: If the correct backup job does not appear, in the Backup Directory Location text box, type the Universal Naming Convention (UNC) path of the correct backup folder, and then click Refresh. 4. On the Restore from Backup Step 2 of 3: Select Component to Restore page, select the check box that is next to the solution, and then click Next. 5. On the Restore from Backup Step 3 of 3: Select Restore Options page, in the Restore Component section, ensure that Solution appears in the Restore the following component list. In the Restore Only Configuration Settings section, ensure that the Restore content and configuration settings option is selected. In the Restore Options section, under Type of Restore, select the Same configuration option. A dialog box appears that asks you to confirm the operation. Click OK. Click Start Restore. 6. You can view the general status of all recovery jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current recovery job in the lower part of the page in the Restore section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the recovery to start. If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Sprestore.log file at the UNC path that you specified in step 3.To restore a trusted solution by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Restore-SPFarm -Directory -RestoreMethod Overwrite -BackupId -Item Where: <BackupFolder> is the UNC location of the directory that you want to restore from. <GUID> is the GUID of the backup ID that you want to restore from. If you do not specify a backup, the most recent one is used. <SolutionPath> is the path of the solution within the backup tree (usually farm\solutions\SolutionName). For more information, see HYPERLINK "http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx"Restore-SPFarm (http://technet.microsoft.com/library/8e18ea80-0830-4ffa-b6b6-ad18a5a7ab3e(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.Restoring a sandboxed solution You cannot restore only customizations that were deployed as sandboxed solutions. Instead, you must restore the farm, Web application, content database, or site collection with which the customization is associated. For more information about these methods of restoring, see HYPERLINK "http://technet.microsoft.com/library/84346116-d592-4b9f-9992-b509ccdcefbe.aspx#Related"Related content later in this article. Restoring authored site elements You cannot restore only authored site elements. Instead, you must restore the farm, Web application, or content database with which the authored site element is associated. For more information about these methods of backing up, see HYPERLINK "http://technet.microsoft.com/library/84346116-d592-4b9f-9992-b509ccdcefbe.aspx#Related"Related content. Restoring workflows Workflows are a special case of customizations that you can restore. Make sure that the backup and recovery plan includes any of the following scenarios that apply to the environment: Declarative workflows, such as those created in Microsoft SharePoint Designer 2010, are stored in the content database for the site collection to which they are they are deployed. Restoring the content database or site collection restores these workflows. Custom declarative workflow actions have components in the following three locations: a. The Microsoft Visual Studio 2010assemblies for the actions are stored in the global assembly cache (GAC). b. The XML definition files (.actions files) are stored in the 14\TEMPLATE\\Workflow directory. c. An XML entry to mark the action as an authorized type is stored in the Web.config file for the Web applications in which it is used. If the farm workflows use custom actions, you should use a file restore system to restore these files and XML entries. You can reapply the files as needed after recovery. Workflows that depend on custom code, such as those that are created by using Visual Studio 2010, are stored in two locations. The Visual Studio 2010assemblies for the workflow are stored in the GAC, and the XML definition files are stored in the Features directory. This is the same as other types of SharePoint Server features such as Web Parts and event receivers. If the workflow was installed as part of a solution package, follow the instructions for restoring solution packages. If you create a custom workflow that interacts with a site collection other than the one where the workflow is deployed, you must restore both site collections to recover the workflow. Restoring a farm is sufficient to recover all site collections in the farm and all workflows that are associated with them. Workflows that have not been deployed must be restored separately by using a file system backup application. Restoring changes to the Web.config file You can recover changes to the Web.config file made by using Central Administration or the SharePoint Server 2010 APIs and object model by performing a farm or configuration-only restore. You should use a file system backup to protect changes to the Web.config file that are not made by using Central Administration or the SharePoint APIs and object model. You can recover the backup by using a file system restore. Recovering changes made by direct editing Changes made directly to a site by directly editing through the browser can be difficult to recover. The following table describes recovery strategies for specific objects. Edited objectBackup strategyListIf you have used SharePoint Designer 2010 to save as a template, you can deploy and activate the template. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199515"Save a SharePoint site as a template (http://go.microsoft.com/fwlink/?LinkID=199515).SiteIf you have used SharePoint Designer 2010 to save as a template, you can deploy and activate the template. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199515"Save a SharePoint site as a template (http://go.microsoft.com/fwlink/?LinkID=199515).Site collectionUse site collection recovery. For more information, see HYPERLINK \l "zf8f81869a51f4d7fb4b652dd99078c23"Restore a site collection (SharePoint Server 2010). Restoring developed customizations that are not packaged as solutions Restoring developed customizations that are not packaged as solutions can be a complex process because the customization file locations are not standardized. Consult with the development team or customization vendor to determine whether the customizations involve additional add-in software or files in other locations. We recommend that you restore directories with a file system restore solution. The following table lists locations where customizations are typically stored on Web servers. LocationDescription%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14Commonly updated files, custom assemblies, custom templates, custom site definitionsInetpubLocation of IIS virtual directories%WINDIR%\AssemblyGlobal assembly cache (GAC): a protected operating system location where the Microsoft .NET Framework code assemblies are installed to provide full system accessRelated content Resource CenterHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199235"Business Continuity Management for SharePoint Server 2010: Backup, Recovery, Availability, and Disaster Recovery (http://go.microsoft.com/fwlink/?LinkID=199235)IT Pro contentHYPERLINK "http://technet.microsoft.com/library/be4ca20f-520e-4fd7-9c42-140af800cbc8(Office.14).aspx"Deploy customizations - overview (SharePoint Server 2010) (http://technet.microsoft.com/library/be4ca20f-520e-4fd7-9c42-140af800cbc8(Office.14).aspx) HYPERLINK \l "z8f98a75019bb4ea09ff5719b85febbb3"Back up customizations (SharePoint Server 2010) HYPERLINK \l "z7942ef65c309402db4bbd54e686fc5d9"Restore a farm (SharePoint Server 2010) HYPERLINK \l "zd849b7dfb26d45f6a74f6641f18788cf"Restore a farm configuration (SharePoint Server 2010) HYPERLINK \l "zcbb3b24276ed4539b4544685a84d57c5"Restore a Web application (SharePoint Server 2010) HYPERLINK \l "z240f8caaafb344ce90bb861cfa258b09"Restore a content database (SharePoint Server 2010) HYPERLINK \l "zf8f81869a51f4d7fb4b652dd99078c23"Restore a site collection (SharePoint Server 2010)Developer contentHYPERLINK "http://go.microsoft.com/fwlink/?LinkID=156638"Using solutions (MSDN) (http://go.microsoft.com/fwlink/?LinkID=156638) HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=199517"Sandboxed solutions (MSDN) (http://go.microsoft.com/fwlink/?LinkID=199517)Restore a site collection (SharePoint Server 2010) You can use only Windows PowerShell to restore a site collection. Use Windows PowerShell to restore a site collection You can use Windows PowerShell to restore a site collection manually or as part of a script that can be run at scheduled intervals. Note: If a user has taken copies of content for off-line editing in Microsoft SharePoint Workspace 2010 and the content is restored from a backup on the server, when the user re-connects, the server automatically synchronizes the off-line content with the restored content. This might result in data loss on the user's copies of the content. To restore a site collection by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. Additionally, verify that the user account performing this procedure has read permissions to the backup folder and is a member of the db_owner fixed database role on both the farm configuration database and the content database where the site collection is being restored. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Restore-SPSite -Identity -Path [-DatabaseServer] [-DatabaseName] [-HostHeader] [-Force] [-GradualDelete] [-Verbose] If you want to restore the site collection to a specific content database, use the DatabaseServer and DatabaseName parameters to specify the content database. If you do not specify a content database, the site collection will be restored to a content database chosen by Microsoft SharePoint Server 2010. If you are restoring a host-named site collection, use the Identity parameter to specify the URL of the host-named site collection and use the HostHeader parameter to specify the URL of the Web application that will hold the host-named site collection. If you want to overwrite an existing site collection, use the Force parameter. Note: If the site collection that you are restoring is 1 gigabyte or larger, you can use the GradualDelete parameter for better performance during the restore process. When this parameter is used, the site collection that is overwritten is marked as deleted, which immediately prevents any additional access to its content. The data in the marked site collection is then deleted gradually over time by a timer job instead of all at the same time, which reduces the impact on server performance. For more information, see HYPERLINK "http://technet.microsoft.com/library/90f19a58-0455-470c-a8ee-3129fc341f62(Office.14).aspx"Restore-SPSite (http://technet.microsoft.com/library/90f19a58-0455-470c-a8ee-3129fc341f62(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. See Also HYPERLINK \l "z45acdd33b3224f3697f10701159e15f0"Back up a site collection (SharePoint Server 2010) Import a list or document library (SharePoint Server 2010) Although you can use either Windows PowerShell or Central Administration to export a site, list, or document library, you can use only Windows PowerShell to import a site, list, or document library. For information about how to export lists or libraries, see HYPERLINK \l "z1e637e1726344601a574299a7c27bb24"Export a site, list, or document library (SharePoint Server 2010). You can use importing as a method of restoring the items, or as a method of moving or copying the items from one farm to another farm. You can import a site, list, or document library from a backup of the current farm, from a backup of another farm, or from a read-only content database. To import from a read-only content database, you must first attach the read-only database. For more information, see HYPERLINK \l "z5417b04ac7d94e9a86fbee1d1c63508b"Attach and restore a read-only content database (SharePoint Server 2010). Important: You cannot import a site, list or document library exported from one version of Microsoft SharePoint Server to another version of SharePoint Server. Import a site, list or document library You can use Windows PowerShell to manually import a site, list, or document library or as part of a script that can be run at regular intervals. To import a site, list or document library by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (that is, PS C:\>), type the following command, and then press ENTER: Import-SPWeb -Identity -Path [-Force] [-NoFileCompression] [-Verbose] Important: The site or subsite that you are importing must have a template that matches the template of the site specified by Identity. You can also use the Get-SPWeb cmdlet and pass the ID to Import-SPWeb by using the Windows PowerShell pipeline. The value of the Path parameter specifies the path and file name of the file from which to import the list or library. To include the user security settings with the list or document library, use the IncludeUserSecurity parameter. To overwrite the list or library that you specified, use the Force parameter. You can use the UpdateVersions parameter to specify how versioning conflicts will be handled. To view the progress of the operation, use the Verbose parameter. The NoFileCompression parameter lets you specify that no file compression is performed during the import process. Using this parameter can lower resource usage up to 30% during the export and import process. If you are importing a site, list, or document library that you exported from Central Administration, or if you exported a site, list, or document library by using Windows PowerShell and you did not use the NoFileCompression parameter in the Export-SPWeb cmdlet, you cannot use this parameter in the Import-SPWeb cmdlet. Note: There is no facility in the Import-SPWeb cmdlet import a subset of the items within the export file. Therefore, the import operation will import everything from the file. For more information, see HYPERLINK "http://technet.microsoft.com/library/2ecc5b6e-1b23-4367-a966-b7bd3377db3a(Office.14).aspx"Import-SPWeb (http://technet.microsoft.com/library/2ecc5b6e-1b23-4367-a966-b7bd3377db3a(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. See Also HYPERLINK \l "z1e637e1726344601a574299a7c27bb24"Export a site, list, or document library (SharePoint Server 2010) Database management (SharePoint Server 2010) This section describes techniques for managing the databases that are associated with Microsoft SharePoint Server 2010. In this section: HYPERLINK \l "z0889004d68204282a63c863f4796ff85"Add a content database (SharePoint Server 2010) Adding a content database to an existing Web application is a common task. This article describes how to add a content database to an existing SharePoint Server 2010 implementation. HYPERLINK \l "zbfa2f924f4114b138c24bf251d7e4c91"Attach or detach content databases (SharePoint Server 2010) Certain operations, such as applying updates or creating copies of configuration settings, require that you detach and then attach databases. This article describes how to do these procedures. HYPERLINK \l "z86bb109d865f4f86bb3d87ecfc4e50ae"Move site collections between databases (SharePoint Server 2010) Under some circumstances, you might want to move one or more site collections to a different content database. For example, a site collection can outgrow the content database on which it is located, and you would have to move the site collection to a larger content database. Conversely, if site collections do not grow to their expected capacity, it might be convenient to combine several site collections onto one content database. This article describes how to move site collections between databases. HYPERLINK \l "z6aa16d9a812a4bbcb4211b4589452503"Move content databases (SharePoint Server 2010). This article describes how to move content databases between servers that are running Microsoft SQL Server, between instances of SQL Server, or from one Microsoft SharePoint Server 2010 Web application to another. You can also move a content database to load balance a database server or Web application. HYPERLINK \l "z677b4fb6f9a8490e99a4cd2e958d93f7"Rename or move service application databases (SharePoint Server 2010) This article describes how to rename or move service application databases by using SQL Server, and then how to point the service application to the renamed or moved database. This can be a complex process because different types of service applications require different methods of pointing to the new database name or location. This article directs you to the supported method of pointing to a renamed or moved database for each service application. HYPERLINK \l "zd9dac1890736448d928c68bf38603613"Move all databases (SharePoint Server 2010) This article describes how to move all of the databases associated with SharePoint Server 2010 from one database server to another database server. If your databases are hosted on different servers, this procedure applies to the database server that hosts the configuration database. HYPERLINK \l "z8b91dc0ac37d4ec8aa75deb3f268fb97"Run a farm that uses read-only databases (SharePoint Server 2010) A read-only farm can be part of a disaster recovery environment. Alternatively, it can be part of a highly available maintenance, patching, or upgrade environment that provides user access while another version of the farm is being updated. This article describes how to run a SharePoint Server 2010 farm in which content databases are set to be read-only (a read-only farm). HYPERLINK \l "z77722a6683404ae3ad15c3610f398da0"Manage Remote BLOB Storage (SharePoint Server 2010) Remote BLOB Storage (RBS) is an add-on feature pack for Microsoft SQL Server 2008. RBS is designed to move the storage of binary large objects (BLOBs) from database servers to commodity storage solutions. If the content databases in SharePoint Server 2010 are 4 gigabytes (GB) or larger, consider using RBS as part of your data storage solution. This article introduces RBS. See Also HYPERLINK "http://technet.microsoft.com/library/9b1e8b21-7675-4186-beb6-3adeef4360e6(Office.14).aspx"Database types and descriptions (SharePoint Server 2010) (http://technet.microsoft.com/library/9b1e8b21-7675-4186-beb6-3adeef4360e6(Office.14).aspx) Add a content database (SharePoint Server 2010) You can use the procedures that are described in this article to create a new content database and attach it to a Web application. In this article: HYPERLINK "http://technet.microsoft.com/library/7662910a-69b8-477b-a5b3-5c7bb91458c0.aspx#ProcCA"To add a content database to a Web application by using Central Administration HYPERLINK "http://technet.microsoft.com/library/7662910a-69b8-477b-a5b3-5c7bb91458c0.aspx#ProcWPS"To add a content database to a Web application by using Windows PowerShell To add a content database to a Web application by using Central Administration 1. Verify that the user account that is being used to perform this operation is a member of the Farm Administrators SharePoint group. If you are using Windows authentication to connect to SQL Server, the user account must also be a member the SQL Server dbcreator fixed server role on the SQL Server instance where the database will be created. If you are using SQL authentication to connect to SQL Server, the SQL authentication account that you specify when you create the content database must have dbcreator permission on the SQL Server instance where the database will be created. 2. On the SharePoint Central Administration Web site, click Application Management. 3. In the Databases section, click Manage content databases. 4. On the Manage Content Databases page, click Add a content database. 5. On the Add Content Database page: a. Specify a Web application for the new database. b. Specify a database server to host the new database. c. Specify the authentication method that the new database will use and supply an account name and password, if they are necessary. Important: The account name and password must already exist as a SQL Server login. d. Specify the name of the failover database server, if one exists. e. Specify the number of top-level sites that can be created before a warning is issued. By default, this is 9,000. f. Specify the total number of top-level sites that can be created in the database. By default, this is 15,000. Note: For information about how to determine the number of top-level sites that the system can support, see HYPERLINK "http://technet.microsoft.com/library/054526b9-417e-4140-b251-79b68e771c9a(Office.14).aspx"Performance and capacity technical case studies (SharePoint Server 2010) (http://technet.microsoft.com/library/054526b9-417e-4140-b251-79b68e771c9a(Office.14).aspx). g. Click OK.To add a content database to a Web application by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. If you are using Windows authentication to connect to SQL Server, the user account must also be a member the SQL Server dbcreator fixed server role on the SQL Server instance where the database will be created. If you are using SQL authentication to connect to SQL Server, the SQL authentication account that you specify when you create the content database must have dbcreator permission on the SQL Server instance where the database will be created. 2. On the Start menu, click Administrative Tools. 3. Click SharePoint 2010 Management Shell. 4. At the Windows PowerShell command prompt, type the following command: New-SPContentDatabase -Name -WebApplication Where is the name of the content database to create and is the name of the Web application to which the new database is attached. For more information, see HYPERLINK "http://technet.microsoft.com/library/18cf18cd-8fb7-4561-be71-41c767f27b51(Office.14).aspx"New-SPContentDatabase (http://technet.microsoft.com/library/18cf18cd-8fb7-4561-be71-41c767f27b51(Office.14).aspx).Note: To attach an existing content database to a Web application, use the Windows PowerShell cmdlet Mount-SPContentDatabase. For more information, see HYPERLINK "http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx"Mount-SPContentDatabase (http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx). We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. See Also HYPERLINK \l "zbfa2f924f4114b138c24bf251d7e4c91"Attach or detach content databases (SharePoint Server 2010) HYPERLINK \l "z86bb109d865f4f86bb3d87ecfc4e50ae"Move site collections between databases (SharePoint Server 2010) Attach or detach content databases (SharePoint Server 2010) This article describes how to attach or detach Microsoft SharePoint Server 2010 content databases by using the SharePoint Central Administration Web site or by using Windows PowerShell 2.0. You might want to attach or detach content databases in the following situations: You want to add a new content database for new site collections to keep content databases at a manageable size. You have restored a content database from another farm and you want the sites that it contains to be accessible from a Web application. You have archived site collections and you no longer need as many content databases. You can move the remaining site collections out of a content database and then detach the content database from the Web application. For more information, see HYPERLINK \l "z86bb109d865f4f86bb3d87ecfc4e50ae"Move site collections between databases (SharePoint Server 2010). The steps to add a database and to attach a database are very similar. For more information about how to add a database, see HYPERLINK \l "z0889004d68204282a63c863f4796ff85"Add a content database (SharePoint Server 2010). To attach a content database by using Central Administration 1. Verify that the user account that is being used to perform this operation is a member of the Farm Administrators SharePoint group. If you want to create a new content database at the same time that you attach it, the SharePoint farm service account must be a member of the SQL Server dbcreator fixed server role. To attach a content database to a Web application, the SharePoint farm service account must have db_owner permission for the content database. Tip: If the database already exists, it must be the same version as the Microsoft SharePoint 2010 Products farm or this operation will fail. To attach a content database that is a different version than the farm, use the Windows PowerShell 2.0 command in the following section. 2. On the SharePoint Central Administration Web site, click Application Management. 3. On the Application Management page, in the Databases section, click Manage content databases. 4. On the Manage Content Databases page, click Add a content database. 5. On the Add Content Database page: a. Use the Web Application drop-down menu to select the Web application to which you want to attach a content database. b. Specify the database server that hosts the database. c. Specify the database name. If the database does not already exist, it will be created. d. Specify the authentication method for the database, and supply an account name and password if you are using SQL authentication. Important: The account name and password must already exist as a SQL Server login. We recommend that you use Windows authentication instead of SQL authentication because, by default, SQL authentication sends an unencrypted password to the computer that is running SQL Server. If you use SQL authentication, the SQL account requires the same SQL permissions as the SharePoint farm service account. e. Click OK.To detach a content database by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. 2. On the SharePoint Central Administration Web site, click Application Management. 3. On the Application Management page, in the Databases section, click Manage content databases. 4. Select the Web application for which you want to detach a content database. 5. Click the content database that you want to detach. 6. On the Manage Content Database Settings page, select the Remove content database check box. If the content database contains data, you will receive a warning. Click OK to continue with the operation. 7. Click OK to confirm the detachment, or click Cancel to stop the operation without detaching the database. After detaching the content database in Central Administration, the content database still exists in SQL Server. If you want to permanently remove the content database, you must do so by using a SQL Server procedure.To attach or detach a content database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. The user account must also be a member of the SQL Serverdbcreator fixed server role on the SQL Server instance where the content database exists. 2. If you are using the Remove-SPContentDatabase cmdlet to delete the content database from SQL Server at the same time that you detach it, you must also be a member of the SharePoint_Shell_Access role on the content database. 3. On the Start menu, click All Programs. 4. Click Microsoft SharePoint 2010 Products. 5. Click SharePoint 2010 Management Shell. 6. At the Windows PowerShell command prompt, type the appropriate command. To attach an existing content database: Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" -WebApplication http://SiteName Where: <ContentDb> is the content database to be attached. <DbServer> is the name of the database server. http://SiteName is the name of the Web application to which the content database is being attached. To detach a content database: Dismount-SPContentDatabase "<ContentdBName>" Where <ContentdBName> is the name of the content database. Important: If you have multiple content databases that have the same name, you must use the content database GUID in this command instead of using the content database name. To retrieve the GUID of the content database, run the Get-SPContentDatabase cmdlet with no arguments. The Dismount-SPContentDatabase cmdlet detaches the content database from the Web application, but it does not delete the content database from SQL Server. After a content database is detached, you cannot delete it by using Windows PowerShell 2.0. You can only remove it by using SQL Server tools. If you want to delete the content database from SQL Server while you detach it, use the Remove-SPContentDatabase cmdlet instead. For more information, see HYPERLINK "http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx"Mount-SPContentDatabase (http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx) and HYPERLINK "http://technet.microsoft.com/library/89eea901-8d3f-4d4d-9638-941a1cafe259(Office.14).aspx"Dismount-SPContentDatabase (http://technet.microsoft.com/library/89eea901-8d3f-4d4d-9638-941a1cafe259(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.See Also HYPERLINK "http://technet.microsoft.com/library/a4a83bb0-0bab-4cad-9b59-0fd89a16f57b(Office.14).aspx"Get-SPContentDatabase (http://technet.microsoft.com/library/a4a83bb0-0bab-4cad-9b59-0fd89a16f57b(Office.14).aspx) HYPERLINK "http://technet.microsoft.com/library/18cf18cd-8fb7-4561-be71-41c767f27b51(Office.14).aspx"New-SPContentDatabase (http://technet.microsoft.com/library/18cf18cd-8fb7-4561-be71-41c767f27b51(Office.14).aspx) HYPERLINK "http://technet.microsoft.com/library/e8c337b6-37af-4fdd-8469-a32f4d45c040(Office.14).aspx"Remove-SPContentDatabase (http://technet.microsoft.com/library/e8c337b6-37af-4fdd-8469-a32f4d45c040(Office.14).aspx) Move site collections between databases (SharePoint Server 2010) Under some circumstances, you might want to move one or more site collections to a different content database. For example, a site collection can outgrow the content database on which it resides, and you would have to move the site collection to a larger content database. In Microsoft SharePoint Server 2007, this process was also known as splitting a content database because of the name of the Stsadm command that was used to perform the procedure. In Microsoft SharePoint Server 2010, it is more accurate to view this procedure as moving the site collection to a larger database. On the other hand, if site collections do not grow to their expected capacity, it might be convenient to combine several site collections onto one content database. In SharePoint Server 2007, this process was also known as merging content databases. During this process, no content databases are actually merged the site collections are moved to and consolidated on a new database. This article describes how to prepare for and move site collections between content databases. You can move site collections between content databases by using the Stsadm command-line tool or Windows PowerShell 2.0 commands. There is no graphical user interface for this task. Tip: You can also move site collections by using Backup and Restore procedures. For information about how to do this, see HYPERLINK \l "z45acdd33b3224f3697f10701159e15f0"Back up a site collection (SharePoint Server 2010) and HYPERLINK \l "zf8f81869a51f4d7fb4b652dd99078c23"Restore a site collection (SharePoint Server 2010) To perform the procedures that are described in this article, verify that the user account has access to one of the servers on which Windows PowerShell 2.0 is running, and that the user account is a member of the following groups: The db_owner fixed database role and the SharePoint_Shell_Access role in the SQL Server source content database, administration content database, destination content database, and configuration database. The WSS_ADMIN_WPG group on the local computer. For these procedures to work, the following conditions must be true: The destination content database must already exist. The source content database and destination content database must be located on the same instance of SQL Server. The source content database and destination content database must be attached to the same Web application. For more information about how to add a content database to a Web application, see HYPERLINK \l "z0889004d68204282a63c863f4796ff85"Add a content database (SharePoint Server 2010). In this article: HYPERLINK \l "z4089"Determining the size of the source site collection HYPERLINK \l "_Moving_site_collections"Moving site collections between content databases Determining the size of the source site collection Regardless of the reason for moving a site collection, you should always begin the task by determining the size of the site collection that is to be moved. You can then be sure that the destination hard disk can sufficiently contain the site collection contents. Verify that the destination hard disk has at least three times the free space that is required for the site collection. Tip: You can stay current about the space that site collections are using by creating site quotas and e-mail alerts. To determine the size of the site collection 1. On the Start menu, click All Programs. 2. Click SharePoint 2010 Products. 3. Click SharePoint 2010 Management Shell. 4. At the Windows PowerShell 2.0 command prompt, type the following commands: $used = (Get-SPSiteAdministration -Identity ).DiskUsed $used Where is the name of the site collection. The amount of disk space that is being used by the specified site collection is stored in the $used variable, and is displayed at the command prompt when the second command is run. For more information, see HYPERLINK "http://technet.microsoft.com/library/a05769b1-7559-4af4-8524-5cbcc1bd4f25(Office.14).aspx"Get-SPSiteAdministration (http://technet.microsoft.com/library/a05769b1-7559-4af4-8524-5cbcc1bd4f25(Office.14).aspx).Moving site collections between content databases You can use the Windows PowerShell command Move-SPSite to move site collections between content databases. Two procedures are provided here. The first procedure moves a single site collection to a new content database, and the second procedure moves multiple site collections to a new content database. To move a single site collection At the Windows PowerShell command prompt, type the following command: Move-SPSite -DestinationDatabase Where is the name of the site collection, and is the name of the destination content database.To move multiple site collections At the Windows PowerShell command prompt, type the following command: Get-SPSite -ContentDatabase <SourceContentDb> | Move-SPSite -DestinationDatabase <DestinationContentDb> Where <SourceContentDb> is the name of the original content database, and <DestinationContentDb> is the name of the destination content database. This command moves all site collections from the source content database to the destination content database. For more information, see HYPERLINK "http://technet.microsoft.com/library/e3bf1b34-78b9-4643-b0dd-24444e3cffc5(Office.14).aspx"Move-SPSite (http://technet.microsoft.com/library/e3bf1b34-78b9-4643-b0dd-24444e3cffc5(Office.14).aspx).Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. See Also HYPERLINK \l "z0889004d68204282a63c863f4796ff85"Add a content database (SharePoint Server 2010) Move content databases (SharePoint Server 2010) This article describes how you can move content databases between servers that are running Microsoft SQL Server, between instances of SQL Server, or from one Microsoft SharePoint Server 2010 Web application to another. You can move a content database to load balance a database server or Web application. Important: This article only describes how to move content databases. For information about how to move other kinds of databases that are associated with SharePoint Server 2010, see HYPERLINK \l "zd9dac1890736448d928c68bf38603613"Move all databases (SharePoint Server 2010). Overview of moving content databases When you are moving content databases, you must use both SharePoint Server 2010 tools and SQL Server tools. You can use either the SharePoint Server Central Administration Web site or Windows PowerShell 2.0. The following list summarizes how to move content databases: Record the name of the content database, and which Web application it is associated with. For details, see To record which content databases are associated with each Web application. Pause any service applications and services that may attempt to run against the database, including timer jobs and search crawls. For details, see To pause timer jobs by using Windows PowerShell (option 1) or To pause timer jobs by using Central Administration (option 2). In SharePoint Server, remove the content database from the Web application. This action can be performed either by using Central Administration or Windows PowerShell 2.0. In general, if you are only working with more than one database, it may be faster to write a Windows PowerShell 2.0 script. For details, see To detach the content databases from a Web application by using Central Administration (option 1) or To detach content databases from a Web application by using Windows PowerShell (option 2). In SQL Server, detach the database from the current instance. For details, see To detach the content databases from SQL Server. Using Windows Explorer, copy or move the .mdf, .ndf, and .ldf files associated with the database from the source location to the destination location. For details, see To move the content databases to a new location. Note: You can also backup and restore databases to move them, but backup and recovery are not described in this article. For information, see HYPERLINK \l "z71abd06e6730442eb2c1e3ba9c04d497"Backup and recovery (SharePoint Server 2010). In SQL Server, attach the database to the new instance. For details, see To attach the content databases to the new instance of SQL Server. In SharePoint Server, add the content database to the destination Web application. Be sure that you use exactly the same name when you reattach the content database. Otherwise, SharePoint Server creates a new content database. You can use either Central Administration or Windows PowerShell 2.0 to perform this action. For details, see To attach the content databases to the Web application by using Central Administration (option 1) or To attach content databases to a Web application by using Windows PowerShell (option 2). Restart any service applications and services that should be run against the database, including timer jobs and search crawls. For details, see To restart timer jobs by using Windows PowerShell (option 1) or To restart timer jobs by using Central Administration (option 2). Moving content databases Note Membership in the local Administrators group on the local computers is required to complete the following procedures. If you are running SharePoint Server 2010 in a least-privileged environment, and are running procedures from within Central Administration, you should ensure that you have the following roles in SQL Server: The dbowner fixed database role for the configuration database and the content database on the source server, in order to detach the content database. The dbcreator and securityadmin fixed server roles on the destination server, in order to attach the database and configure SQL Server logins. Note If you are moving a content database to a different farm, you must make the server farm account a member of the Administrators group on the database server during the restore process. This enables the account to replicate the security setting for the databases. This access level can be removed after the content database has been moved. For more information, see HYPERLINK "http://technet.microsoft.com/library/55b99d80-3fa7-49f0-bdf4-adb5aa959019(Office.14).aspx"Account permissions and security settings (SharePoint Server 2010) (http://technet.microsoft.com/library/55b99d80-3fa7-49f0-bdf4-adb5aa959019(Office.14).aspx). The destination farm must be at the same version of SharePoint Server 2010 or a later version than the source farm. To record which content databases are associated with each Web application 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Get-SPContentDatabase -WebApplication Where is the URL of the Web application. 6. Repeat for each Web application. For more information, see HYPERLINK "http://technet.microsoft.com/library/a4a83bb0-0bab-4cad-9b59-0fd89a16f57b(Office.14).aspx"Get-SPContentDatabase (http://technet.microsoft.com/library/a4a83bb0-0bab-4cad-9b59-0fd89a16f57b(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. To pause timer jobs by using Windows PowerShell (option 1) 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Get-SPTimerJob -webapplication | select name | Out-File Append Encoding ascii ForEach($tmrjob in (Get-Content )) { Get-SPTimerJob -Identity $tmrjob | Disable-SPTimerjob } Where: <http://WebApplicationURL> is the Web application associated with the content database that you are moving. <c:\timerjobfile.txt> is the location of the file that you are creating that lists all timer jobs associated with the Web application. For more information, see HYPERLINK "http://technet.microsoft.com/library/e2ec752d-7f04-457e-bc02-7213af5c14fe(Office.14).aspx"Get-SPTimerJob ( HYPERLINK "http://technet.microsoft.com/library/e2ec752d-7f04-457e-bc02-7213af5c14fe(Office.14).aspx)" http://technet.microsoft.com/library/e2ec752d-7f04-457e-bc02-7213af5c14fe(Office.14).aspx), HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=196616"Out-File (http://go.microsoft.com/fwlink/?LinkId=196616), HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=196617"ForEach-Object (http://go.microsoft.com/fwlink/?LinkId=196617), HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=196618"Get-Content (http://go.microsoft.com/fwlink/?LinkId=196618), and HYPERLINK "http://technet.microsoft.com/library/8d8d7ec5-3f09-4b7e-9124-8d0c0afeb637(Office.14).aspx"Disable-SPTimerJob (http://technet.microsoft.com/library/8d8d7ec5-3f09-4b7e-9124-8d0c0afeb637(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.To pause timer jobs by using Central Administration (option 2) 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. 2. In Central Administration, in the Monitoring section, click Check Job Status. 3. For each scheduled job that runs against the content database that you are moving, click the job to open the Edit Timer Job page, click Disable, and then click OK. 4. If you are running the search service application and crawling the content database, follow the steps to pause the crawl in the article HYPERLINK "http://technet.microsoft.com/library/c56c9985-6c17-4c77-a3f7-2c1aa1f9e152(Office.14).aspx"Start, pause, resume, or stop a crawl (SharePoint Server 2010) (http://technet.microsoft.com/library/c56c9985-6c17-4c77-a3f7-2c1aa1f9e152(Office.14).aspx).To detach the content databases from a Web application by using Central Administration (option 1) 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. 2. In Central Administration, in the Application Management section, click Manage Content databases. 3. On the Manage Content Databases page, click the content database that you want to move. The Manage Content Database Settings page opens. Note: If the content database does not appear in the list, it might be associated with another Web application. To select another Web application, on the Web Application menu, click Change Web Application. 4. On the Manage Content Database Settings page, in the Remove Content Database section, select the Remove content database check box, and then click OK. Note: Removing the content database does not delete the database; it only removes the association of the database with the Web application. 5. Repeat steps 3 and 4 for each content database that you want to move.To detach content databases from a Web application by using Windows PowerShell (option 2) 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Dismount-SPContentDatabase "" Where is the name of the content database. Note: If you have multiple content databases that have the same name, you must use the content database GUID in this command instead of using the content database name. To retrieve the GUID of the content database, run the Get-SPContentDatabase cmdlet without arguments. For more information, see HYPERLINK "http://technet.microsoft.com/library/89eea901-8d3f-4d4d-9638-941a1cafe259(Office.14).aspx"Dismount-SPContentDatabase (http://technet.microsoft.com/library/89eea901-8d3f-4d4d-9638-941a1cafe259(Office.14).aspx) and HYPERLINK "http://technet.microsoft.com/library/a4a83bb0-0bab-4cad-9b59-0fd89a16f57b(Office.14).aspx"Get-SPContentDatabase (http://technet.microsoft.com/library/a4a83bb0-0bab-4cad-9b59-0fd89a16f57b(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.To detach the content databases from SQL Server 1. In SQL Server Management Studio, open the source SQL Server instance, and then expand the Databases node. 2. Right-click the content database, point to Tasks, and then click Detach. Repeat this step for each content database that you want to move. Note: Use this procedure to move only content databases. Do not detach any other kinds of databases.To move the content databases to a new location 1. Using Windows Explorer, locate the .mdf, .ldf, and .ndf files for the content databases. 2. Select the .mdf, .ldf, and .ndf files for the database that you want to move and either copy or move them to the destination directory.To attach the content databases to the new instance of SQL Server 1. In Management Studio, open the destination SQL Server instance. 2. Right-click the Databases node, point to Tasks, and then click Attach. 3. In the Attach Database dialog box, browse to where you transferred the .mdf, .ldf, and .ndf files, select the .mdf file for the database that you want to attach, and then click OK. 4. Repeat for each content database that you are moving.To attach the content databases to the Web application by using Central Administration (option 1) 1. In Central Administration, in the Application Management section, click Manage Content databases. 2. On the Manage Content Databases page, click Add a content database. 3. On the Add Content Database page, verify that the Web Application menu displays the correct Web application. 4. In the Server box, specify the database server that hosts the database. 5. In the Database Name box, type the exact name of the transferred content database. Note: Verify that the name is correct. If it is not, a new database will be created. 6. Specify the authentication method for the database, and then click OK. 7. Repeat these steps for each database that you are adding. Be sure that you select the correct Web application from the Web Application menu for each database.To attach content databases to a Web application by using Windows PowerShell (option 2) 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Mount-SPContentDatabase "" -DatabaseServer "" -WebApplication Where: <ContentDB> is the content database to be attached. <DBServer> is the name of the database server. <http://sitename> is the URL of the Web application to which the content database is being attached. For more information, see HYPERLINK "http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx"Mount-SPContentDatabase (http://technet.microsoft.com/library/20d1bc07-805c-44d3-a278-e2793370e237(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.To restart timer jobs by using Windows PowerShell (option 1) 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: ForEach($tmrjob in (Get-Content )) {Get-SPTimerJob -Identity $tmrjob | Enable-SPTimerjob} Where: <c:\timerjobfile.txt> is the location of the file that you created that lists all of the timer jobs associated with the Web application. For more information, see HYPERLINK "http://technet.microsoft.com/library/e2ec752d-7f04-457e-bc02-7213af5c14fe(Office.14).aspx"Get-SPTimerJob (http://technet.microsoft.com/library/e2ec752d-7f04-457e-bc02-7213af5c14fe(Office.14).aspx), HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=196617"ForEach-Object (http://go.microsoft.com/fwlink/?LinkId=196617), HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=196618"Get-Content (http://go.microsoft.com/fwlink/?LinkId=196618), and HYPERLINK "http://technet.microsoft.com/library/ca2ce54c-1a9a-46d5-8055-a1f87c30a99a(Office.14).aspx"Enable-SPTimerJob (http://technet.microsoft.com/library/ca2ce54c-1a9a-46d5-8055-a1f87c30a99a(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.To restart timer jobs by using Central Administration (option 2) 1. In Central Administration, in the Monitoring section, click Check Job Status. 2. For each scheduled job that you disabled previously, click the job to open the Edit Timer Job page, click Enable, and then click OK. 3. If you are running the search service application and crawling the content database, follow the steps to resume the crawl in the article HYPERLINK "http://technet.microsoft.com/library/c56c9985-6c17-4c77-a3f7-2c1aa1f9e152(Office.14).aspx"Start, pause, resume, or stop a crawl (SharePoint Server 2010) (http://technet.microsoft.com/library/c56c9985-6c17-4c77-a3f7-2c1aa1f9e152(Office.14).aspx). You must run a full crawl of the content database. Rename or move service application databases (SharePoint Server 2010) This article describes how to rename or move Microsoft SharePoint Server 2010 service application databases. Renaming service application databases is typically done to remove the GUID from the database name after the databases have been created by the SharePoint Products Configuration Wizard, or to bring the databases into alignment with your organization's naming standards. Moving service application databases can be done to load-balance a system. The general process for renaming or moving service application databases is as follows: 1. Rename or move the database by using SQL Server tools. 2. Point the service application to the renamed or moved database. Pointing a service application to a renamed or moved service application database can be a complex process, especially if you must rename or move the databases for multiple service applications. This is because different types of service applications require different methods of pointing to the new database name or location. Based on the service application database that you are renaming or moving, you will use one of the following methods to point the service application to the renamed or moved database: Delete the service application, re-create the service application, and then point the service application to the existing renamed or moved database. You can use this method for most service application databases, but this method can be complex for some service applications, such as Search. Use Windows PowerShell to point the service application to the renamed or moved changed database. You can also use Central Administration for a subset of the service application databases that you can use Windows PowerShell to point to. When possible, we recommend that you use Central Administration to rename or move databases because that is the easiest way to perform the operation. Windows PowerShell is available for only some service application databases, and Central Administration is available for a subset of those service applications. The following table shows the methods that can be used to point each service application to a renamed or moved database. Methods available for pointing to renamed or moved service application databases Service application or databaseDelete and re-create service applicationUse Windows PowerShellUse Central AdministrationUsage and Health Data CollectionPossiblePossiblePreferredSearch: PropertyPossiblePossiblePreferredSearch: CrawlPossiblePossiblePreferredSearch: AdministrationPossiblePreferredNot availableWeb Analytics: StagingPossiblePossiblePreferredWeb Analytics: ReportingPossiblePossiblePreferredBusiness Data ConnectivityPreferredNot availableNot available1Application Registry2Not availableNot availableNot availableState ServiceNot availablePreferredNot availableUser Profile: ProfilePreferredNot availableNot availableUser Profile: Social TaggingPreferredNot availableNot availableUser Profile: SynchronizationPreferredNot availableNot availableMetadata ManagementPossiblePossiblePreferredWord Automation servicePossiblePossiblePreferredSecure StorePossibleNot available3PreferredPerformancePointNot availablePreferredNot availableSubscription settingsPossiblePreferredNot available 1It may appear that you can rename the Business Data Connectivity database in Central Administration or by using the Windows PowerShell cmdlet Set-SPBusinessDataCatalogServiceApplication. However, using either Central Administration or Set-SPBusinessDataCatalogServiceApplication creates a new database. It does not rename the existing database. 2Because there is no Windows PowerShell cmdlet to create the Application Registry service application, it cannot be renamed. It can be moved by using Microsoft SharePoint Server 2010 backup and recovery. 3It may appear that you can rename the Secure Store database by using the Windows PowerShell cmdlet Set-SPSecureStoreServiceApplication. However, using Set-SPSecureStoreServiceApplication creates a new database. It does not rename the existing database. In this article:  HYPERLINK \l "_Renaming_or_moving" Renaming or moving service application databases by using SQL Server This method includes the following procedures: To stop a service application To rename a database by using SQL Server Management Studio Move a database by using SQL Server Management Studio and Windows Explorer HYPERLINK "http://technet.microsoft.com/library/d72521b3-4b64-48b4-b96a-71a2d96222d1.aspx#General"General method for pointing a service application to a renamed or moved database (http://technet.microsoft.com/library/d72521b3-4b64-48b4-b96a-71a2d96222d1.aspx#General) This method includes the following procedures: To document service application settings To delete a service application To re-create a service application To restart a service application Note: This method does not apply to all service application databases. Refer to the guidance for the specific service application to determine which method to use. Service application-specific guidance for renaming or moving databases  HYPERLINK \l "_Pointing_the_Usage" Pointing the Usage and Health Data Collection service application to a renamed or moved database  HYPERLINK \l "_Pointing_the_Search" Pointing the Search service application to renamed or moved databases  HYPERLINK \l "_Pointing_the_Web" Pointing the Web Analytics service application to renamed or moved databases  HYPERLINK \l "_Pointing_the_State" Pointing the State Service service application to a renamed or moved database  HYPERLINK \l "_Pointing_the_Managed" Pointing the Managed Metadata service application to a renamed or moved database  HYPERLINK \l "_Pointing_the_Word" Pointing the Word Automation service application to a renamed or moved database  HYPERLINK \l "_Pointing_the_Secure" Pointing the Secure Store service application to a renamed or moved database  HYPERLINK \l "_Pointing_the_Business" Pointing the Business Data Connectivity service application to a renamed or moved database  HYPERLINK \l "_Pointing_the_Application" Pointing the Application Registry service application to a renamed or moved database  HYPERLINK \l "_Pointing_the_User" Pointing the User Profile service application to renamed or moved databases  HYPERLINK \l "_Pointing_the_PerformancePoint" Pointing the PerformancePoint service application to a renamed or moved database  HYPERLINK \l "_Pointing_the_Subscription" Pointing the Subscription Settings service application to a renamed or moved database Renaming or moving service application databases by using SQL Server To rename a service application database, you must use SQL Server. To move a service application database, you must use SQL Server and Windows Explorer. We recommend that you stop the services related to the service application before you rename or move the related database. In general, we expect that you will either rename or move a database. That is, you will typically not perform both actions. The instructions in this article assume that you have installed SQL Server Management Studio on the database server. If this is not the case, you can download and install Management Studio at HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=186132&clcid=0x409"Microsoft SQL Server 2008 Management Studio Express (http://go.microsoft.com/fwlink/?LinkID=186132&clcid=0x409). Important On the database servers on which the operations are performed, you must be a member of the following: Administrators group on the local server db_owner fixed database role In some environments, you must coordinate the rename and move procedures with the database administrator. Be sure to follow any applicable policies and guidelines for managing databases. To stop a service application 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. 2. For each service application that you plan to change the database for, you must stop the service or disable the service application by following the appropriate procedure for the service application that you are working with. For more information, see HYPERLINK \l "z0a785758694c4c5cabe670a17b490c6e"Manage service applications (SharePoint Server 2010).To rename a database by using SQL Server Management Studio 1. In SQL Server Management Studio, connect to the source SQL Server instance, and then expand the Databases node. 2. Right-click the database that you want to rename, click Rename, and then type the new name. Repeat this step for each database that you want to rename.Move a database by using SQL Server Management Studio and Windows Explorer Moving a database requires detaching the database from SQL Server, moving the files to the new location by using Windows Explorer, and then attaching the database to the new instance of SQL Server. To detach a database from SQL Server 1. In SQL Server Management Studio, open the source SQL Server instance, and then expand the Databases node. 2. Right-click the database, point to Tasks, and then click Detach. Repeat this step for each database that you want to move.To move database files to a new location by using Windows Explorer 1. In Windows Explorer, locate the .mdf, .ndf, and .ldf files for the service application databases. 2. Select the .mdf, .ndf, and .ldf files for the databases that you want to move, and then either copy or move them to the destination directory.To attach a database to a new instance of SQL Server 1. In Management Studio, open the destination SQL Server instance. 2. Right-click the Databases node, point to Tasks, and then click Attach. 3. In the Attach Database dialog box, browse to where you transferred the .mdf, .ndf, and .ldf files, select the .mdf file for the database that you want to attach, and then click OK. 4. Repeat for each database that you are moving.General method for pointing a service application to a renamed or moved database The method for pointing a service application to a renamed or moved database that works for most service applications is to delete the service application and then re-create the service application. When you re-create the service application, use the new name or new location. This is the only method that can be used to point to moved or renamed databases for the following service applications: Business Data Connectivity User Profile PerformancePoint This method includes the following steps: 1. To document service application settings 2. To delete a service application 3. To re-create a service application 4. To restart a service application To document service application settings Before you delete and re-create a service application, document the settings for the service application. To do this, use the recommended Windows PowerShell cmdlets that are described in the article HYPERLINK \l "z73d7f970c3784b3192d548cdeb8075e6"Document farm configuration settings (SharePoint Server 2010).To delete a service application To delete a service application, follow the procedure in HYPERLINK \l "zac2338f51b064a7c9dc04751b6421cb3"Delete a service application (SharePoint Server 2010), but do not delete the service application database.To re-create a service application Re-create the service application, pointing it to the renamed database, and reusing all the other initial configuration settings. For more information, see the following articles: HYPERLINK \l "z33ed78c825fc48eab0c150b540213cff"Configure usage and health data collection (SharePoint Server 2010) HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=197114"Enabling Multi Tenant Support in SharePoint 2010 (http://go.microsoft.com/fwlink/?LinkId=197114) HYPERLINK "http://technet.microsoft.com/library/e58bd6c6-74b2-4471-80b0-b627b482ab33(Office.14).aspx"Business Data Connectivity service administration overview (SharePoint Server 2010) (http://technet.microsoft.com/library/e58bd6c6-74b2-4471-80b0-b627b482ab33(Office.14).aspx) HYPERLINK \l "zd62ebc009252483e94db2b52b2cdb2c8"Managed metadata administration (SharePoint Server 2010) HYPERLINK "http://technet.microsoft.com/library/29c0bc76-d835-401b-a2fb-abb069e84125(Office.14).aspx"Configure the Secure Store Service (SharePoint Server 2010) (http://technet.microsoft.com/library/29c0bc76-d835-401b-a2fb-abb069e84125(Office.14).aspx) Note: As you configure the service application, you must use the same passphrase that you used when you first configured the service application. HYPERLINK \l "z5765c57c372b4974a60a2277996550aa"Manage the State Service (SharePoint Server 2010) HYPERLINK "http://technet.microsoft.com/library/e27a812e-9ddd-434f-a32c-70c74d4319f8(Office.14).aspx"Manage farm-level search settings (SharePoint Server 2010) (http://technet.microsoft.com/library/e27a812e-9ddd-434f-a32c-70c74d4319f8(Office.14).aspx) and HYPERLINK \l "zff30cd9ba8274beeb38aed2c3b6b3b47"Manage search topology HYPERLINK \l "z9fd89365cf744c41bcc1e38972dca7ef"Set up and configure PerformancePoint Services (step-by-step) HYPERLINK "http://technet.microsoft.com/library/25d888b2-035a-40b4-a2b9-a496657a36e3(Office.14).aspx"Create, edit, or delete a User Profile service application (SharePoint Server 2010) (http://technet.microsoft.com/library/25d888b2-035a-40b4-a2b9-a496657a36e3(Office.14).aspx) Depending on the service application, you may have to manually start the related service. To restart a service application 1. In Central Administration, under System Settings, click Manage services on server. 2. In the Service list, next to the appropriate service or services that support the service application that you are restarting, click Start.Service application-specific guidance for renaming or moving databases This section describes specific guidance for each kind of service application. Pointing the Usage and Health Data Collection service application to a renamed or moved database You can use either Central Administration or Windows PowerShell to point the Usage and Health Data Collection service application to a renamed or moved database. To point the Usage and Health Data Collection service application to a renamed or moved database by using Central Administration 1. Verify that the user account that is performing the procedure is a member of the Farm Administrators SharePoint group. 2. In Central Administration, click Monitoring, and then on the Monitoring page, click Configure usage and health data collection. The Configure web analytics and health data collection page appears. 3. Clear the Enable health data collection check box, and then click OK. You return to the Monitoring page. 4. Click Configure usage and health data collection to return to the Configure web analytics and health data collection page. 5. Select the Enable health data collection check box 6. In the Logging Database Server section, specify the updated database server and database name, and then click OK.To point the Usage and Health data collection service application to a renamed or moved database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Set-SPUsageApplication -Identity "<ServiceApplicationName>" -DatabaseName "<DbName>" -DatabaseServer "<SQLServerName>" Where: <ServiceApplicationName>is the name of the usage and health data collection service application. <DbName> is the name of the database. <SQLServerName> is the name of the database server. For more information, see HYPERLINK "http://technet.microsoft.com/library/4b918524-5af9-4265-9dcc-470f70fbaaba(Office.14).aspx"Set-SPUsageApplication (http://technet.microsoft.com/library/4b918524-5af9-4265-9dcc-470f70fbaaba(Office.14).aspx). Pointing the Search service application to renamed or moved databases You can point the Search service application to Crawl and Property databases that have been renamed by using Central Administration or by using Windows PowerShell 2.0. You must use Windows PowerShell 2.0 to point to a renamed Search Administration database. To point the Search service application to renamed or moved Crawl and Property databases by using Central Administration 1. Verify that the user account that is performing the procedure is a member of the Farm Administrators SharePoint group. 2. In Central Administration, click Application Management. 3. On the Application Management page, click Manage service applications. 4. Click the name of the Search Service Application. 5. On the Search Administration page, click Modify. 6. On the Manage Search Topology page, the following three databases are listed: Administration, Crawl, and Property. You can point to renamed or moved Crawl or Property databases by using this procedure. Note: You cannot point to a renamed or moved Search Administration database by using Central Administration. 7. Click the database that you want to change, and then click Edit Properties. 8. In the Database Server text box, type the new server location if there is one; in the Database Name text box, type the new name for the database; and then click OK. 9. On the Manage Search Topology page, click Apply Topology Changes. It might take several minutes for the changes to take effect.To point the Search service application to renamed or moved Crawl, Property, and Administration databases by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following commands: Point the Search Administration database to its new name or location. $searchapp | Set-SPEnterpriseSearchServiceApplication -DatabaseName "<NewDbName>" -DatabaseServer "<NewServerName>" Where: <NewDbName> is the name of the renamed database. <NewServerName> is the new database location. Monitor whether the search instances have finished re-provisioning. Do {write-host -NoNewline .;Sleep 10; $searchInstance = Get-SPEnterpriseSearchServiceInstance -Local} while ($searchInstance.Status -ne "Online") Set the crawl database to its new name or location. $CrawlDatabase0 | Set-SPEnterpriseSearchCrawlDatabase -DatabaseName "<NewDbName>"  DatabaseServer "<NewServerName>" Where: <NewDbName> is the name of the renamed database. <NewServerName> is the new database location. Monitor whether the search instances have finished re-provisioning. Do {write-host -NoNewline .;Sleep 10; $searchInstance = Get-SPEnterpriseSearchServiceInstance -Local} while ($searchInstance.Status -ne "Online") Set the property database to its new name or location. $PropertyDatabase0 | Set-SPEnterpriseSearchPropertyDatabase -DatabaseName "<NewDbName>" -DatabaseServer "<NewServerName>" Where: <NewDbName> is the name of the renamed database. <NewServerName> is the new database location. Monitor whether the search instances have finished re-provisioning. Do {write-host -NoNewline .;Sleep 10; $searchInstance = Get-SPEnterpriseSearchServiceInstance -Local} while ($searchInstance.Status -ne "Online") Restart the search service instance. get-SPEnterpriseSearchServiceInstance | start-SPEnterpriseSearchServiceInstance Resume running the search service application. $searchapp.Resume()Pointing the Web Analytics service application to renamed or moved databases You can use either Central Administration or Windows PowerShell to point the Web Analytics service application to renamed or moved databases. You can also delete and re-create the service application. To point to renamed or moved Web Analytics databases by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. 2. In Central Administration, click Application Management. 3. On the Application Management page, click Manage service applications. 4. Click the Web Analytics Service Application. The ribbon becomes active. 5. Click Properties on the ribbon. The Edit Web Analytics Service Application wizard opens. 6. Click Next on the first page. On the Edit Web Analytics Service Application Topology page, point to the database name, click Edit Properties, and then specify the new database server or database name. Repeat this step for each database. 7. Click OK to dismiss the Edit Database dialog box, and then click Next. You should see a message that the Web Analytics service application was successfully edited. 8. Click OK. 9. In Central Administration, under System Settings, click Manage services on server. 10. In the Service list, next to the Web Analytics Data Processing Service and Web Analytics Web Service, click Start.To point the Web Analytics service application to a renamed or moved database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command: Set-SPWebAnalyticsServiceApplication -Identity "" [-ListOfReportingDatabases ] [-ListOfStagingDatabases ] Where: <ServiceApplicationName> is the name of the service application. <ReportingServerAndDatabase> is an XML string that contains the server name and the database name for the Reporting database. Note: Despite the name of the option, only one Reporting database is supported per Web Analytics service application. <StagingServerAndDatabases> is an XML string that contains the server name and the database names for the staging databases. The following example shows how to use the Set-SPWebAnalyticsServiceApplication cmdlet: Set-SPWebAnalyticsServiceApplication -Identity WebAnalyticsServiceApplication1 -ListOfReportingDatabases "" -ListOfStagingDatabases " " For more information, see HYPERLINK "http://technet.microsoft.com/library/eafa4ad8-5991-44c4-93c9-0beb60d586df(Office.14).aspx"Set-SPWebAnalyticsServiceApplication (http://technet.microsoft.com/library/eafa4ad8-5991-44c4-93c9-0beb60d586df(Office.14).aspx). Pointing the State Service service application to a renamed or moved database The State Service database stores temporary data. You can use Windows PowerShell to point the State Service service application to a renamed or moved database by performing one of the following procedures: Add a new database in the new location, or create a database with a new name. Then add the new database to the service application, and delete the old database. For details, see HYPERLINK "http://technet.microsoft.com/library/d72521b3-4b64-48b4-b96a-71a2d96222d1.aspx#StateNew"To add a new database to the State service application, and remove an old database by using Windows PowerShell Dismount the old database, rename or move it by using SQL Server, and then remount the State Service database. For details, see HYPERLINK "http://technet.microsoft.com/library/d72521b3-4b64-48b4-b96a-71a2d96222d1.aspx#StateMove"To point the State service application to a renamed or moved database by using Windows PowerShell The following procedures have the following steps integrated into them. Therefore, they do not require that the steps have already been performed: Stopping a service application Renaming a database in SQL Server Management Studio Moving a database by using SQL Server Management Studio and Windows To add a new database to the State Service service application and remove an old database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the following command to create a new database: New-SPStateServiceDatabase -Name "" Then type the following command to remove the old database: Remove-SPStateServiceDatabase -Name "<OldDatabaseName>" Where: <NewDatabaseName> is the name of the new database that you want to create. <OldDatabaseName> is the name of the old database that you want to disassociate with the State service and detach from SQL Server. For more information, see HYPERLINK "http://technet.microsoft.com/library/221e439c-c501-4d4c-9d8a-171a01e67e25(Office.14).aspx"New-SPStateServiceDatabase (http://technet.microsoft.com/library/221e439c-c501-4d4c-9d8a-171a01e67e25(Office.14).aspx) and HYPERLINK "http://technet.microsoft.com/library/33f70dd1-01d2-4909-941c-1a5527ad6565(Office.14).aspx"Remove-SPStateServiceDatabase (http://technet.microsoft.com/library/33f70dd1-01d2-4909-941c-1a5527ad6565(Office.14).aspx). To point the State Service service application to a renamed or moved database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. Record the State Service service application ID and the database ID that you will configure. 3. On the Start menu, click All Programs. 4. Click Microsoft SharePoint 2010 Products. 5. Click SharePoint 2010 Management Shell. 6. At the Windows PowerShell command prompt, type the following command to dismount the database: Dismount-SPStateServiceDatabase -Identity <DatabaseID> Where: <DatabaseID> is the State Service database to remove from the service application.The type must be a valid GUID in the form 12345678-90ab-cdef-1234-567890bcdefgh, a valid name of a state database, or an instance of a valid SPStateServiceDatabase object. For more information, see HYPERLINK "http://technet.microsoft.com/library/6be172d6-fae1-400e-91b3-76357a9ccf10(Office.14).aspx"Dismount-SPStateServiceDatabase (http://technet.microsoft.com/library/6be172d6-fae1-400e-91b3-76357a9ccf10(Office.14).aspx). 7. Rename or move the database. For details, see To rename a database by using SQL Server Management Studio or Move a database by using SQL Server Management Studio and Windows Explorer . 8. At the Windows PowerShell command prompt, type the following command to mount the renamed or moved database: Mount-SPStateServiceDatabase -Name "<DatabaseName>" -DatabaseServer "<ServerName>" Where: <DatabaseName> is the name of the database to associate with the State service. <ServerName> is the name of the SQL Server that hosts the State service database. For more information, see HYPERLINK "http://technet.microsoft.com/library/bd559347-c8f9-4ecf-9fbc-17821ae0afc4(Office.14).aspx"Mount-SPStateServiceDatabase (http://technet.microsoft.com/library/bd559347-c8f9-4ecf-9fbc-17821ae0afc4(Office.14).aspx).Pointing the Managed Metadata service application to a renamed or moved database You can point the Managed Metadata service application to a renamed or moved database by using either Central Administration or Windows PowerShell. For information, see HYPERLINK \l "zbe30ab95f6bf41e193ac2f5c78ac703b"Create, update, publish, or delete a managed metadata service application (SharePoint Server 2010). Pointing the Word Automation service application to a renamed or moved database You can point the Word Automation service application to a renamed or moved database by using Central Administration or Windows PowerShell. This procedure has the following steps integrated into them, and do not require that they have already been performed: 1. Stopping a service application 2. Renaming a database in SQL Server Management Studio 3. Moving a database by using SQL Server Management Studio and Windows Explorer Note: You do not need to stop the Word Automation service before pointing to a renamed or moved database. However, stopping the Word Automation service will not cause a problem if you choose to do so. To point the Word Automation service application to a renamed or moved database by using Central Administration 1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group. 2. In Central Administration, under System Settings, click Manage services on server. 3. In the Service list, next to the Word Automation service, click Stop. 4. In the Quick Launch, click Application Management. 5. On the Application Management page, click Manage service applications. 6. Click the Word Automation service application. The ribbon becomes active. 7. Click Properties on the ribbon. The Edit Word Automation Service Application dialog box opens. 8. Change the database server or database name, and then click OK. 9. In the Quick Launch, click System Settings. 10. On the System Settings page, under Servers, click Manage services on server. 11. In the Service list, next to the Word Automation service, click Start.To point the Word Automation service application to a renamed or moved database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. Record the Word Automation service application name and the database name that you plan to configure. 3. On the Start menu, click All Programs. 4. Click Microsoft SharePoint 2010 Products. 5. Click SharePoint 2010 Management Shell. 6. At the Windows PowerShell command prompt, type the following command: $app = Get-SPServiceApplication -Name "" Set-SPWordConversionServiceApplication -Identity $app -DatabaseName "" -DatabaseServer "" Where: <ServiceApplicationName> is the name of the Word Automation service application. <DatabaseName> is the name of the renamed or moved database. <DatabaseServer> is the location of the renamed or moved database. Do not include this parameter if you are pointing to a renamed database in the same location. For more information, see HYPERLINK "http://technet.microsoft.com/library/ee2844c6-e0b9-480d-83c7-5cac9a8f293e(Office.14).aspx"Set-SPWordConversionServiceApplication (http://technet.microsoft.com/library/ee2844c6-e0b9-480d-83c7-5cac9a8f293e(Office.14).aspx).Pointing the Secure Store service application to a renamed or moved database You can point the Secure Store service application to a renamed or moved database by using Central Administration. Alternatively, you can rename or move the database, and then delete or re-create the service application. If you choose to delete and re-create the service application, you must use the same passphrase that you used when you initially configured the service application. For more information, see General method for pointing a service application to a renamed or moved database. To point the Secure Store Service service application to a renamed or moved database by using Central Administration 1. Verify that the user account that is performing this task is a member of the Farm Administrators SharePoint group. 2. In Central Administration, under System Settings, click Manage services on server. 3. In the Service list, next to the Secure Store service, click Stop. 4. In the Quick Launch, click Application Management. 5. On the Application Management page, click Manage service applications. 6. Click the Secure Store Service service application. The ribbon becomes active. 7. Click Properties on the ribbon. The Edit Secure Store Service Application page opens. 8. Change the database server or database name, and then click OK. Note: If you use an incorrect name, SharePoint Server 2010 creates a new database. 9. In the Quick Launch, click System Settings. 10. On the System Settings page, under Servers, click Manage services on server. 11. In the Service list, next to the Secure Store service, click Start.Pointing the Business Data Connectivity service application to a renamed or moved database You must delete the Business Data Connectivity service application, rename or move the database, and then re-create the service application to point to a renamed or moved database. For information, see General method for pointing a service application to a renamed or moved database. Pointing the Application Registry service application to a renamed or moved database Because there is no Windows PowerShell cmdlet to create the Application Registry service application, the associated database cannot be renamed. You can move the database by using SharePoint Server 2010 backup and recovery. For more information, see HYPERLINK \l "z96dc4ef1cec847d0b99546bca3e8eda2"Back up a service application (SharePoint Server 2010) and HYPERLINK \l "z3e9dcd5053e64471a969aeb4d079dfa3"Restore a service application (SharePoint Server 2010). Pointing the User Profile service application to renamed or moved databases You must delete the User Profile service application, rename or move the databases, and then re-create the service application to point to the renamed or moved databases. For information, see General method for pointing a service application to a renamed or moved database. Pointing the PerformancePoint service application to a renamed or moved database You can point the PerformancePoint service application to a renamed or moved database by using Windows PowerShell. Note: The PerformancePoint service application cannot be deleted and then re-created to point to an existing database. To point the PerformancePoint service application to a renamed or moved database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. Record the PerformancePoint service application name and the database name that you plan to configure. 3. On the Start menu, click All Programs. 4. Click Microsoft SharePoint 2010 Products. 5. Click SharePoint 2010 Management Shell. 6. At the Windows PowerShell command prompt, type the following command: Set-SPPerformancePointServiceApplication -Identity "<ServiceApplicationName>" -SettingsDatabase "<OptionalServerName\DatabaseName>" Where: <ServiceApplicationName> is the name of the PerformancePoint service application. <OptionalServerName\DatabaseName> is the location of and the name of the renamed or moved database. Do not include the location if you are just renaming the database. For more information, see HYPERLINK "http://technet.microsoft.com/library/21d352ec-eb64-44af-8d31-7b221676eb7a(Office.14).aspx"Set-SPPerformancePointServiceApplication (http://technet.microsoft.com/library/21d352ec-eb64-44af-8d31-7b221676eb7a(Office.14).aspx).Pointing the Subscription Settings service application to a renamed or moved database You can point the Subscription Settings service application to a renamed or moved database by using Windows PowerShell. To point the Subscription Settings service application to a renamed or moved database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. Record the Subscription Settings service application name and the database name that you plan to configure. 3. On the Start menu, click All Programs. 4. Click Microsoft SharePoint 2010 Products. 5. Click SharePoint 2010 Management Shell. 6. At the Windows PowerShell command prompt, type the following command: Set-SPSubscriptionSettingsServiceApplication -Identity "" -DatabaseName "" -DatabaseServer "" Where: <ServiceApplicationName> is the name of the Subscription Settings service application. <DatabaseName> is the name of the renamed or moved database. <DatabaseServer> is the location of the renamed or moved database. Do not include this parameter if you are just renaming the database in the same location. For more information, see HYPERLINK "http://technet.microsoft.com/library/462e367f-47bb-4eca-89fa-e7c1d3ba9126(Office.14).aspx"Set-SPSubscriptionSettingsServiceApplication (http://technet.microsoft.com/library/462e367f-47bb-4eca-89fa-e7c1d3ba9126(Office.14).aspx).See Also HYPERLINK "http://technet.microsoft.com/library/798aa915-7025-4adc-a210-4f6ff14c43fc(Office.14).aspx"Deploy by using DBA-created databases (SharePoint Server 2010) (http://technet.microsoft.com/library/798aa915-7025-4adc-a210-4f6ff14c43fc(Office.14).aspx) HYPERLINK "http://technet.microsoft.com/library/9b1e8b21-7675-4186-beb6-3adeef4360e6(Office.14).aspx"Database types and descriptions (SharePoint Server 2010) (http://technet.microsoft.com/library/9b1e8b21-7675-4186-beb6-3adeef4360e6(Office.14).aspx) HYPERLINK \l "z0a785758694c4c5cabe670a17b490c6e"Manage service applications (SharePoint Server 2010) Move all databases (SharePoint Server 2010) This article describes how to move all of the databases associated with Microsoft SharePoint Server 2010 from one database server to another database server. If your databases are hosted on different servers, this procedure applies to the database server that hosts the configuration database. For moving content databases only, see HYPERLINK \l "z6aa16d9a812a4bbcb4211b4589452503"Move content databases (SharePoint Server 2010). For moving service application databases only, see HYPERLINK \l "z677b4fb6f9a8490e99a4cd2e958d93f7"Rename or move service application databases (SharePoint Server 2010). Important: Moving databases makes all farm sites and assets unavailable to users until the process is completed. The following kinds of databases hosted on a single database server can be moved by using the procedures in this article: Configuration database Central Administration content database Content databases Service application databases Moving all databases The process of moving all of the databases from one database server to another database server requires you to work in both SharePoint Server 2010 and SQL Server. The following list summarizes the process of moving all databases, with detailed steps presented in the subsequent procedures: 1. Prepare the new database server. For details, see To prepare the new database server. 2. Close any open Windows PowerShell management shell windows and any open Stsadm command prompt windows. For details, see To close any open management sessions. 3. In the Services Microsoft Management Console snap-in, stop all of the services related to SharePoint Server 2010 and Internet Information Services (IIS). For details, see To stop the farm. 4. In SQL Server, detach the databases from the current instance. For details, see To detach databases. 5. Using Windows Explorer, copy or move the .mdf, .ldf, and .ndf files associated with the database from the source server to the destination server. For details, see To move database files to the new server. Note: You can also back up all databases and restore them to the new server. Procedures for backing up and restoring all databases are not included in this article. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=179208"How to: Back Up a Database (SQL Server Management Studio) (http://go.microsoft.com/fwlink/?LinkID=179208) and HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=183032"How to: Restore a Database Backup (SQL Server Management Studio) (http://go.microsoft.com/fwlink/?LinkID=183032). 6. In SQL Server, ensure that all of the SQL Server logins, fixed server roles, fixed database roles, and permissions for the databases from the source server have also been configured correctly on the destination server. For details, see To set up permissions on the new server. 7. In SQL Server, attach the database to the new instance. For details, see To attach databases to the new instance of SQL Server. 8. Use SQL Server connection aliases to point to the new database server, and then use the connection alias to update all Web servers. A connection alias is a defined alternate name that can be used to connect to an instance of SQL Server. You have to configure the alias on all Web servers and application servers in the farm. For details, see To point the Web application to the new database server by setting up SQL Server connection aliases. Note: The use of SQL Server client aliases is recommended as part of hardening SQL Server for SharePoint environments. For more information, see HYPERLINK "http://technet.microsoft.com/library/2c727311-e83e-4f7b-b02c-9a0699a81e64(Office.14).aspx"Harden SQL Server for SharePoint environments (SharePoint Server 2010) (http://technet.microsoft.com/library/2c727311-e83e-4f7b-b02c-9a0699a81e64(Office.14).aspx). 9. Restart the services. For details, see To restart the services in the farm. The following are the minimum permissions that are required to perform this process: You must be a member of the Farm Administrators SharePoint group. On the computer that is running the SharePoint Central Administration Web site, you must be a member of the Administrators group. On the database server from which the databases are being moved, you must be a member of the following: The Administrators group The db_backupoperator fixed database role On the database server to which the databases are being moved, you must be a member of the following: The Administrators group The db_owner fixed database role In some environments, you must coordinate the move procedures with the database administrator. Be sure to follow any applicable policies and guidelines for managing databases. To prepare the new database server Configure the new database server by using the procedures in the article HYPERLINK "http://technet.microsoft.com/library/2c727311-e83e-4f7b-b02c-9a0699a81e64(Office.14).aspx"Harden SQL Server for SharePoint environments (SharePoint Server 2010) (http://technet.microsoft.com/library/2c727311-e83e-4f7b-b02c-9a0699a81e64(Office.14).aspx). Note: The new database server must be running the same version of Windows Server and Microsoft SQL Server as the existing database server. To close any open management sessions Close any open Windows PowerShell management shell windows, and any open command prompt windows if you have been running the Stsadm command-line tool.To stop the farm 1. On the server that is running the Central Administration Web site, in the Services snap-in, stop the following services: SharePoint 2010 Administration SharePoint 2010 Timer SharePoint 2010 Tracing SharePoint 2010 User Code Host SharePoint 2010 VSS Writer SharePoint Foundation Search V4 World Wide Web Publishing Service SharePoint Server Search 14 Web Analytics Data Processing Service Web Analytics Web Service Note: The final two services are part of the Web Analytics service application. If you are running the Web Analytics service application and choose to rename your server, you must also reconfigure the Web Analytics database locations. For details, see To reconfigure Web Analytics database locations . 2. On the server that is running the Central Administration Web site, at the command prompt, type iisreset /stop. To detach databases In SQL Server Management Studio on the original database server, detach the databases that you want to move from the instance that they are attached to. If you are running many databases, you may want to run a Transact-SQL script to detach databases. Note A database cannot be detached if any one of the following is true: The database is being mirrored. A database snapshot exists on the database. For more information, see: HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=194806"Detaching and Attaching Databases (http://go.microsoft.com/fwlink/?LinkId=194806) HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=194807"How to: Detach a Database (SQL Server Management Studio) (http://go.microsoft.com/fwlink/?LinkId=194807) HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=194808"sp_detach_db (Transact-SQL) (http://go.microsoft.com/fwlink/?LinkId=194808)To move database files to the new server Using Windows Explorer, locate the .mdf, .ldf, and .ndf files associated with each database that you are moving, and then copy or move them to the destination directory on the new computer that is running SQL Server.To set up permissions on the new server On the destination database server, open SQL Server Management Studio and transfer your logins and permissions from the original instance to the destination instance. We recommend that you transfer permissions by running a script. An example script is available in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=122053"Knowledge Base article 918992: How to transfer the logins and the passwords between instances of SQL Server 2005 (http://go.microsoft.com/fwlink/?LinkId=122053). For more information about how to transfer SQL Server metadata between instances, see the SQL Server Books Online article HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=122055"Managing Metadata When Making a Database Available on Another Server Instance (http://go.microsoft.com/fwlink/?LinkId=122055).To attach databases to the new instance of SQL Server On the destination database server, attach the databases to the new instance. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=194809"How to: Attach a Database (SQL Server Management Studio) (http://go.microsoft.com/fwlink/?LinkId=194809) and HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=194810"sp_attach_db (Transact-SQL) ( HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=194810" http://go.microsoft.com/fwlink/?LinkId=194810). To point the Web application to the new database server by setting up SQL Server connection aliases 1. Start SQL Server Configuration Manager. On the Start menu, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Configuration Manager. Note: If SQL Server Configuration Manager is not installed, you must run SQL Server setup to install it. 2. Expand SQL Native Client Configuration, right-click Aliases, and then click New Alias. 3. In the Alias Name field, enter the name of the original SQL Server instance, for Protocol, verify that TCP/IP is selected, for Server, enter the name of the new server that is hosting the SharePoint Server 2010 databases, and then click OK. 4. Repeat this procedure on each Web and application server. 5. Optional. If your environment relies on System Center Data Protection Manager (DPM) 2010 or a third-party application that uses the Volume Shadow Copy Service (VSS) framework for backup and recovery, you must install the SQL Server connectivity components on each Web server or application server by running SQL Server setup. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=186119"How to: Install SQL Server 2008 R2 (Setup) (http://go.microsoft.com/fwlink/?LinkID=186119). To reconfigure Web Analytics database locations 1. Note: This procedure is required only if you are running a Web Analytics service application and if you have renamed your server instead of using SQL Server connection aliases. On the SharePoint Central Administration Web site, under Application Management, click Manage Service Applications. 2. Select the Web Analytics service application, and then click Properties. The Edit Web Analytics Service Application wizard appears. 3. Click Next. 4. On the second page of the wizard, update the location of each Web Analytics database to the new SQL Server instance, and then click Next. 5. In Central Administration, under System Settings, click Manage Services on Server. 6. Stop and restart the Web Analytics Data Processing Service, and the Web Analytics Web Service. Note: The SharePoint Web Analytics feature relies on SQL Server service broker to function. The SQL Server service broker cannot be started manually. A SharePoint timer job runs one time per day to ensure that SQL Server service broker is enabled on the necessary databases. 7. After moving databases, you should manually run the health rule "Web Analytics: Verifies that the SQL Server Service Broker is enabled for the Web Analytics staging databases." To manually run the health rule, follow these steps: In Central Administration, click Monitoring. In the Health Analyzer section, click Review rule definitions. The All Rules page is displayed. Under Category: Configuration, click the health rule Web Analytics: Verifies that the SQL Server Service Broker is enabled for the Web Analytics staging databases. The Health Analyzer Rule Definition dialog box opens. Note: In order to see the health rule, you may need to click the right arrow at the bottom of the All Rules page. On the ribbon of the Health Analyzer Rule Definitions dialog box, click Run Now.To restart the services in the farm 1. On the server that is running the Central Administration Web site, at the command prompt, type iisreset /start. 2. In the Microsoft Management Console Services snap-in, start all of the services related to SharePoint and Internet Information Services (IIS). These include the following services: SharePoint 2010 Administration SharePoint 2010 Timer SharePoint 2010 Tracing SharePoint 2010 User Code Host SharePoint 2010 VSS Writer SharePoint Foundation Search V4 World Wide Web Publishing Service SharePoint Server Search 14 Web Analytics Data Processing Service Web Analytics Web Service Run a farm that uses read-only databases (SharePoint Server 2010) This article describes how to run a Microsoft SharePoint Server 2010 farm in which some or all databases are set to be read-only (a read-only farm). A farm is considered to be read-only if any of the following are true: All content databases are set to read-only. Service application databases are set to read-only. Note: The Search service application does not function when its databases are set to read-only. The functionality and user experience in a read-only farm depends on which databases are set to read-only. A farm that uses read-only content and service application databases is likely to be part of a disaster recovery environment or a highly available maintenance, update, or upgrade environment. Procedures in this task: HYPERLINK \l "z44143"Prepare users for the read-only experience  HYPERLINK \l "_Set_content_databases" Set content databases to be read-only  HYPERLINK \l "_Set_service_application" Set service application databases to be read-only Prepare users for the read-only experience If you plan to provide users with access to a read-only site or farm, you should set expectations for what they will be able to do on the site and how the user interface (UI) will differ. Sites that use read-only content databases The user experience of a site that uses a content database that is set to read-only is characterized by the following: Common tasks that do not require writing to the content database are fully available. Most of the common tasks that require writing to the content database are not available, either because they have been disabled in the UI, or because the user is no longer allowed to apply changes. Some common tasks that require writing to the content database appear to be available, but return errors. For detailed information about the user experience on a read-only site, see HYPERLINK "http://technet.microsoft.com/library/b36df897-bc5a-462a-866e-b553eab9e032(Office.14).aspx"User experience on read-only sites (SharePoint Server 2010) (http://technet.microsoft.com/library/b36df897-bc5a-462a-866e-b553eab9e032(Office.14).aspx). Farms that use read-only service application databases The user experience of a farm that uses service application databases that are set to read-only is characterized by the following: Common tasks that do not require writing to the service databases are fully available. All common tasks that require writing to the service databases appear to be available, but return errors. Set content databases to be read-only Before you set content databases to be read-only, you may need to determine which content database is associated with a particular site collection. To determine which content database is associated with a site collection 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt (PS C:\>), type the following command, and then press ENTER: Get-SPContentDatabase -Site -Site specifies the site collection for which you want to know the associated content database. The command returns the content database associated with the site. For more information, see HYPERLINK "http://technet.microsoft.com/library/a4a83bb0-0bab-4cad-9b59-0fd89a16f57b(Office.14).aspx"Get-SPContentDatabase (http://technet.microsoft.com/library/a4a83bb0-0bab-4cad-9b59-0fd89a16f57b(Office.14).aspx). Note: We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions. You can use the following procedure to set read/write content databases to be read-only by using SQL Server Management Studio. You can also use the Transact-SQL ALTER DATABASE statement to set content databases to be read-only. For more information, see HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=148619"ALTER DATABASE (Transact-SQL) (http://go.microsoft.com/fwlink/?LinkId=148619). Important: Do not perform this procedure on databases in a failover environment that have been log-shipped or mirrored. To set content databases to be read-only 1. Verify that you have the following administrative credentials: You must be a member of the db_owner fixed database role in each database. 2. Open SQL Server Management Studio. 3. Right-click the content database that you want to change to read-only, and then click Properties. 4. Select the Options page, and, in the Other options list, scroll to the State section. 5. In the Database Read-Only row, click the arrow next to False, select True, and then click OK. 6. Repeat for all other content databases. Note: When a database is set to read-only, all connections except the one that is setting the read-only flag are stopped. After the read-only flag is set, other connections are enabled. The site collection that is associated with a read-only content database is automatically set to be read-only if the locking status of the site collection was previously None, No Additions, or Read-Only. If the locking status of the site collection was previously No Access, it remains No Access when the database locking status is changed. Set service application databases to be read-only It is possible to set any service application database to be read-only. However, some service applications do not function when their databases are set to read-only, including those associated with Search and Project Server. To set service application databases to be read-only 1. Verify that you have the following administrative credentials: You must be a member of the db_owner fixed database role in each database. 2. Open SQL Server Management Studio. 3. Right-click the database that you want to change to read-only, and then click Properties. 4. Select the Options page, and, in the Other options list, scroll to the State section. 5. In the Database Read-Only row, click the arrow next to False, select True, and then click OK. 6. Repeat for other service application databases as appropriate. Note: When a database is set to read-only, all connections except the one that is setting the read-only flag are stopped. After the read-only flag is set, other connections are enabled. Manage Remote BLOB Storage (SharePoint Server 2010) Remote BLOB Storage (RBS) is an add-on feature pack for Microsoft SQL Server 2008. RBS is designed to move the storage of binary large objects (BLOBs) from database servers to commodity storage solutions. If the content databases in Microsoft SharePoint Server 2010 are 4 gigabytes (GB) or larger, consider using RBS as part of your data storage solution. In This Section HYPERLINK \l "zd359cdaa0ebd4c598fc5002cba241b18"Overview of Remote BLOB Storage (SharePoint Server 2010) This article is a conceptual overview of how RBS works with Microsoft SQL Server 2008 Express and Microsoft SQL Server 2008 R2 Express. It contains important information about RBS features and providers. We strongly recommend that you read this article before you implement RBS. HYPERLINK \l "z4cf30b48f9084774920cd2f2916f2c1b"Install and configure Remote BLOB Storage (RBS) with the FILESTREAM provider (SharePoint Server 2010) This article describes how to install and configure RBS and implement the FILESTREAM provider for use with SharePoint Server 2010. HYPERLINK \l "z7c877590c6b448b2aee3330c5d42d44c"Install and configure Remote BLOB Storage (RBS) without the FILESTREAM provider (SharePoint Server 2010) This article describes how to install and configure RBS without using the FILESTREAM provider. HYPERLINK \l "z83ee2a381b914c6a83de1e968db74611"Set a content database to use Remote BLOB Storage (RBS) (SharePoint Server 2010) This article describes how to set a content database to use RBS. You must already have RBS installed to perform these procedures. HYPERLINK \l "z0317c12678ed47e09109fe143ddb0259"Migrate content into or out of Remote BLOB Storage (RBS) (SharePoint Server 2010) This article describes how to migrate content into or out of RBS, or to a different RBS provider. HYPERLINK \l "z75096f60b94e44c2bc848aa3e2c4fff3"Disable Remote BLOB Storage (RBS) on a content database (SharePoint Server 2010) This article describes how to disable RBS in a SharePoint Server 2010 environment. See Also HYPERLINK "http://technet.microsoft.com/library/c1f83b4f-a507-42f7-bd82-fed5404ed1ad(Office.14).aspx"Plan for Remote BLOB Storage (RBS) (SharePoint Server 2010) (http://technet.microsoft.com/library/c1f83b4f-a507-42f7-bd82-fed5404ed1ad(Office.14).aspx) Overview of Remote BLOB Storage (SharePoint Server 2010) This article describes how you can use Microsoft SharePoint Server 2010 together with Remote BLOB Storage (RBS) and Microsoft SQL Server 2008 Express and Microsoft SQL Server 2008 R2 Express to optimize database storage resources. Before you implement RBS, we highly recommend that you evaluate its potential costs and benefits. For more information and recommendations about using RBS in a SharePoint Server 2010 installation, see HYPERLINK "http://technet.microsoft.com/library/c1f83b4f-a507-42f7-bd82-fed5404ed1ad(Office.14).aspx"Plan for Remote BLOB Storage (RBS) (SharePoint Server 2010) (http://technet.microsoft.com/library/c1f83b4f-a507-42f7-bd82-fed5404ed1ad(Office.14).aspx). In this article: HYPERLINK \l "_Introduction_to_RBS"Introduction to RBS HYPERLINK \l "_Using_RBS_together"Using RBS together with SharePoint 2010 Products Introduction to RBS RBS is a library API set that is incorporated as an add-on feature pack for Microsoft SQL Server. It can be run on the local server running Microsoft SQL Server 2008 R2, SQL Server 2008 or SQL Server 2008 R2 Express. To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise edition. RBS is not supported for Microsoft SQL Server 2005. Binary large objects (BLOBs) are data elements that have either of the following characteristics: Unstructured data that has no schema (such as a piece of encrypted data). A large amount of binary data (many megabytes or gigabytes) that has a very simple schema, such as image files, streaming video, or sound clips. By default, Microsoft SQL Server stores BLOB data in its databases. As a databases usage increases, the total size of its BLOB data can expand quickly and grow larger than the total size of the document metadata and other structured data that is stored in the database. Because BLOB data can consume a lot of file space and uses server resources that are optimized for database access patterns, it can be helpful to move BLOB data out of the SQL Server database, and into a separate file. Before RBS was supported in SQL Server, expensive storage such as RAID 10 was required for the whole SQL database including BLOB data. By using RBS, you can move 80 to 90 percent of the data (that is, BLOBs) onto less expensive storage such as RAID 5 or external storage solutions. RBS uses a provider to connect to any dedicated BLOB store that uses the RBS APIs. Storage solution vendors can implement providers that work with RBS APIs. SharePoint Server 2010 supports a BLOB storage implementation that accesses BLOB data by using the RBS APIs through such a provider. You can implement RBS for Microsoft SharePoint 2010 Products by using a supported provider that you obtain from a third-party vendor. Most third-party providers store BLOBs remotely. In addition to third-party providers, you can use the RBS FILESTREAM provider that is available through the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. The RBS FILESTREAM provider uses the SQL Server FILESTREAM feature to store BLOBs in an additional resource that is attached to the same database and stored locally on the server. The FILESTREAM feature manages BLOBs in a SQL databaseby using the underlying NTFS file system. The location that an RBS provider stores the BLOB data depends on the provider that you use. In the case of the SQL FILESTREAM provider, the data is not stored in the MDF file, but in another file that is associated with the database. This implementation of the FILESTREAM provider is known as the local FILESTREAM provider. You can conserve resources by using the local RBS FILESTREAM provider to place the extracted BLOB data on a different (cheaper) local disk such as RAID 5 instead of RAID 10. You cannot use RBS with the local FILESTREAM provider on remote storage devices, such as network attached storage (NAS). The FILESTREAM provider is supported when it is used on local hard disk drives only. A remote RBS FILESTREAM provider that is available in SQL Server 2008 R2 Express can store BLOB data on remote commodity storage such as direct-attached storage (DAS) or NAS. However, SharePoint Server 2010 does not currently support the remote RBS FILESTREAM provider. Using RBS together with SharePoint 2010 Products SharePoint Server 2010 supports the FILESTREAM provider that is included in the SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2. This version of RBS is available at HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=177388"http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388). Be aware that this is the only version of RBS that is supported by SharePoint Server 2010. Earlier versions are not supported. Third-party RBS providers can also be used with the RBS APIs to create a BLOB storage solution that is compatible with SharePoint Server 2010. In SharePoint Server 2010, site collection backup and restore and site import or export will download the file contents and upload them back to the server regardless of which RBS provider is being used. However, the FILESTREAM provider is the only provider that is currently supported for SharePoint 2010 Products farm database backup and restore operations. When RBS is implemented, SQL Server itself is regarded as an RBS provider. You will encounter this factor when you migrate content into and out of RBS. If you plan to store BLOB data in an RBS store that differs from your SharePoint Server 2010 content databases, you must run SQL Server 2008 with SP1 and Cumulative Update 2. This is true for all RBS providers. The FILESTREAM provider that is recommended for upgrading from stand-alone installations of Windows SharePoint Services 3.0 that have content databases that are over 4 gigabytes (GB) to SharePoint Server 2010 associates data locally with the current content database, and does not require SQL Server Enterprise Edition. Important: RBS does not enable any kind of direct access to any files that are stored in Microsoft SharePoint 2010 Products. All access must occur by using SharePoint 2010 Products only. See Also HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=166020&clcid=0x409"FILESTREAM Overview (http://go.microsoft.com/fwlink/?LinkID=166020&clcid=0x409) HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=165746&clcid=0x409"FILESTREAM Storage in SQL Server 2008 (http://go.microsoft.com/fwlink/?LinkID=165746&clcid=0x409) HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=166066&clcid=0x409"Remote BLOB Store Provider Library Implementation Specification (http://go.microsoft.com/fwlink/?LinkID=166066&clcid=0x409) Install and configure Remote BLOB Storage (RBS) with the FILESTREAM provider (SharePoint Server 2010) This article describes how to install and configure Remote BLOB Storage (RBS) with the FILESTREAM provider on a Microsoft SQL Server 2008 database server that supports a Microsoft SharePoint Server 2010 system. RBS is typically recommended in the case where the content databases are 4 gigabytes (GB) or larger. RBS is a library API set that is incorporated as an add-on feature pack for Microsoft SQL Server 2008 and Microsoft SQL Server 2008 Express. RBS is designed to move the storage of binary large objects (BLOBs) from database servers to commodity storage solutions. RBS ships with the RBS FILESTREAM provider, which uses the RBS APIs to store BLOBs. Before installing and implementing RBS, we highly recommend that you read the articles HYPERLINK "http://technet.microsoft.com/library/c1f83b4f-a507-42f7-bd82-fed5404ed1ad(Office.14).aspx"Plan for Remote BLOB Storage (RBS) (SharePoint Server 2010) (http://technet.microsoft.com/library/c1f83b4f-a507-42f7-bd82-fed5404ed1ad(Office.14).aspx) and HYPERLINK \l "zd359cdaa0ebd4c598fc5002cba241b18"Overview of Remote BLOB Storage (SharePoint Server 2010). If you want to implement RBS with a provider other than FILESTREAM, read the article HYPERLINK \l "z7c877590c6b448b2aee3330c5d42d44c"Install and configure Remote BLOB Storage (RBS) without the FILESTREAM provider (SharePoint Server 2010). In this article:  HYPERLINK \l "_Enable_FILESTREAM_and" Enable FILESTREAM and provision the RBS data store  HYPERLINK \l "z47150" Install RBS  HYPERLINK \l "z47151" Enable and test RBS The user account that you use to perform the procedures that are described in this article must have the following memberships: Administrators group on the Web servers and application servers. Farm Administrators group for the SharePoint Server 2010 farm. SQL Server dbcreator and securityadmin fixed server roles on the computer that is running SQL Server 2008 Express or SQL Server 2008. Enable FILESTREAM and provision the RBS data store You must enable and configure FILESTREAM on the computer that is running SQL Server 2008 that hosts the SharePoint Server 2010 databases. To enable and configure FILESTREAM, follow the instructions in HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=166110&clcid=0x409"How to: Enable FILESTREAM (http://go.microsoft.com/fwlink/?LinkID=166110&clcid=0x409). After you have enabled and configured FILESTREAM, provision a BLOB store as described in the following procedure. To provision a BLOB Store with the FILESTREAM provider 1. Click Start, click All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio. 2. Expand Databases. 3. Select the content database for which you want to create a BLOB store, and then click New Query. 4. In the Query pane, copy and execute each of the following SQL queries in the sequence provided here. Tip: For best performance, simplified troubleshooting, and as a general best practice, we recommend that you create the BLOB store on a volume that does not contain the operating system, paging files, database data, log files, or the tempdb file. use [ContentDbName] if not exists (select * from sys.symmetric_keys where name = N'##MS_DatabaseMasterKey##')create master key encryption by password = N'Admin Key Password !2#4' use [ContentDbName] if not exists (select groupname from sysfilegroups where groupname=N'RBSFilestreamProvider')alter database [ContentDbName] add filegroup RBSFilestreamProvider contains filestream use [ContentDbName] alter database [ContentDbName] add file (name = RBSFilestreamFile, filename = 'c:\Blobstore') to filegroup RBSFilestreamProvider Where [ContentDbName] is the content database name, and c:\BLOBStore is the volume\directory in which you want the BLOB store created. Be aware that you can provision a BLOB store only one time. If you attempt to provision the same BLOB store more than one time, you will receive an error.Install RBS You must install RBS on the database server and on all Web servers and application servers in the SharePoint farm. You must configure RBS separately for each associated content database. Warning: We do not recommend that you install RBS by running the RBS_X64.msi file and launching the Install SQL Remote BLOB Storage wizard. The wizard configures the RBS Maintainer to run a scheduled task every 30 days. This setting might not be optimal for your environment. For more information about the RBS Maintainer, see the SQL Server Help documentation that is included with the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. To install RBS on a Web server 1. On any Web server, go to HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=177388"http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388) to download the RBS_X64.msi file. Important: You must install the version of RBS that is included in the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. The version of RBS must be 10.50.xxx. No earlier version of RBS is supported for SharePoint Server 2010. 2. Click Start and then type cmd in the text box. In the list of results, right-click cmd, and then click Run as administrator. Click OK. 3. Copy and paste the following command at the command prompt: msiexec /qn /lvx* rbs_install_log.txt /i RBS_X64.msiTRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="<ContentDbName>" DBINSTANCE="<DBInstanceName>" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1 Where: <ContentDbName> is the database name. <DBInstanceName> is the SQL Server instance name. The operation should complete in approximately one minute.To install RBS on all additional Web and application servers 1. On a Web server, go to HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=177388"http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388) and download the RBS_X64.msi file. Important: You must install the version of RBS that is included in the SQL Server Remote BLOB Store installation package from the SQL Server Remote BLOB Store installation package from the Feature Pack for SQL Server 2008 R2. The version of RBS must be 10.50.xxx. No earlier version of RBS is supported for SharePoint Server 2010. 2. Click Start and then type cmd in the text box. In the list of results, right-click cmd, and then click Run as administrator. Click OK. 3. Copy and paste the following command at the command prompt: msiexec /qn /lvx* rbs_install_log.txt /i RBS_X64.msiDBNAME="ContentDbName" DBINSTANCE="DBInstanceName" ADDLOCAL="Client,Docs,Maintainer,ServerScript,FilestreamClient,FilestreamServer" Where: ContentDbName is the database name DBInstanceName is the name of the SQL Server instance. The operation should finish within approximately one minute. 4. Repeat this procedure on all Web servers and application servers. If you do not install RBS on every Web and application server, users will encounter errors when they try to write to the content databases.To confirm the RBS installation 1. The rbs_install_log.txt log file is created in the same location as the RBS_X64.msi file. Open the rbs_install_log.txt log file with a text editor and scroll toward the bottom of the file. Within the last 20 lines of the end of the file, an entry should read as follows: Product: SQL Remote Blob Storage Installation completed successfully. 2. On the computer that is running SQL Server 2008, verify that the RBS tables were created in the content database. Several tables should reside under the content database with names that are preceded by the letters "mssqlrbs". Enable and test RBS You must enable RBS on one Web server in the SharePoint farm. It does not matter which Web server you choose for this activity, as long as RBS was installed on it by using the previous procedure. To enable RBS 1. On the Start menu, click Programs, click Microsoft SharePoint 2010 Products, and then click SharePoint 2010 Management Shell. 2. At the Windows PowerShell command prompt, type each of the following commands. $cdb = Get-SPContentDatabase WebApplication Where is the URL of the Web application that is connected to the content database. $rbss = $cdb.RemoteBlobStorageSettings $rbss.Installed() $rbss.Enable() $rbss.SetActiveProviderName($rbss.GetProviderNames()[0]) $rbssTo test the RBS data store 1. Connect to a document library on any Web server. 2. Upload a file that is at least 100 kilobytes (KB) to the document library. 3. On the computer that contains the RBS data store, click Start, and then click Computer. 4. Browse to the RBS data store directory. 5. Browse to the file list and open the folder that has the most recent modified date (other than $FSLOG). In that folder, open the file that has the most recent modified date. Verify that this file has the same size and contents as the file that you uploaded. If it does not, ensure that RBS is installed and enabled correctly. To enable additional databases to use RBS, see HYPERLINK \l "z83ee2a381b914c6a83de1e968db74611"Set a content database to use Remote BLOB Storage (RBS) (SharePoint Server 2010). See Also HYPERLINK \l "z0317c12678ed47e09109fe143ddb0259"Migrate content into or out of Remote BLOB Storage (RBS) (SharePoint Server 2010) HYPERLINK \l "z75096f60b94e44c2bc848aa3e2c4fff3"Disable Remote BLOB Storage (RBS) on a content database (SharePoint Server 2010) Install and configure Remote BLOB Storage (RBS) without the FILESTREAM provider (SharePoint Server 2010) This article describes how to install and configure Remote BLOB Storage (RBS) on a Microsoft SQL Server 2008 database server that supports a Microsoft SharePoint Server 2010 system. RBS is typically recommended in the case where the content databases are 4 gigabytes (4 GB) or larger. RBS is a library API set that is incorporated as an add-on feature pack for Microsoft SQL Server 2008 and Microsoft SQL Server 2008 Express. RBS is designed to move the storage of binary large objects (BLOBs) from database servers to commodity storage solutions. RBS uses a provider to connect to any dedicated BLOB store that implements the RBS APIs. RBS ships with the RBS FILESTREAM provider. Third-party RBS providers can also be used with the RBS APIs to create a BLOB storage solution. If you decide to implement RBS by using a third-party provider instead of FILESTREAM, you can use the information in this article to install RBS without installing the FILESTREAM provider. Before you can use RBS, you must install the third-party provider by using the documentation that is supplied with that provider. If you want to install and configure RBS with the FILESTREAM provider, see HYPERLINK \l "z4cf30b48f9084774920cd2f2916f2c1b"Install and configure Remote BLOB Storage (RBS) with the FILESTREAM provider (SharePoint Server 2010). Before installing and implementing RBS, we highly recommend that you read the articles HYPERLINK \l "zd359cdaa0ebd4c598fc5002cba241b18"Overview of Remote BLOB Storage (SharePoint Server 2010) and HYPERLINK "http://technet.microsoft.com/library/c1f83b4f-a507-42f7-bd82-fed5404ed1ad(Office.14).aspx"Plan for Remote BLOB Storage (RBS) (SharePoint Server 2010) ( HYPERLINK "http://technet.microsoft.com/library/c1f83b4f-a507-42f7-bd82-fed5404ed1ad(Office.14).aspx)" http://technet.microsoft.com/library/c1f83b4f-a507-42f7-bd82-fed5404ed1ad(Office.14).aspx). In this article: HYPERLINK \l "_Install_RBS"Install RBS  HYPERLINK \l "_Enable_and_test"Enable and test RBS The user account that you use to perform the procedures that are described in this article must have the following memberships: Administrators group on the Web servers and application servers. SQL Server dbcreator and securityadmin fixed server roles on the computer that is running SQL Server 2008 Express or SQL Server 2008. Install RBS You must install RBS on the database server and on all Web servers and application servers in the SharePoint farm. You must configure RBS separately for each associated content database. Warning: We do not recommend that you install RBS by running the RBS_X64.msi file and launching the Install SQL Remote BLOB Storage wizard. The wizard configures the RBS Maintainer to run a scheduled task every 30 days. This setting might not be optimal for your environment. For more information about the RBS Maintainer, see the SQL Server Help documentation that is included with the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. To install RBS on a Web server 1. On any Web server, go to HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=177388"http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388) to download the RBS_X64.msi file. When prompted whether to Run or Save the file, click Save. Important: You must install the version of RBS that is included in the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. The version of RBS must be 10.50.xxx. No earlier version of RBS is supported for SharePoint Server 2010. 2. Click Start, and then type cmd in the text box. In the list of results, right-click cmd, and then click Run as administrator. Click OK. 3. Copy and paste the following command at the command prompt: msiexec /lvx* rbs_install.log /q /i rbs.msi ADDLOCAL=ServerScript,Client,Maintainer The operation should finish in approximately one minute. Repeat this procedure on every Web server and application server in the farm. If you do not install RBS on every Web and application server, users will encounter errors when they try to write to the content databases.To install RBS on the database server and set a content database to use RBS 1. On the database server, go to HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=177388"http://go.microsoft.com/fwlink/?LinkID=177388 (http://go.microsoft.com/fwlink/?LinkID=177388) and download the RBS_X64.msi file. Important: You must install the version of RBS that is included in the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. The version of RBS must be 10.50.xxx. No earlier version of RBS is supported for SharePoint Server 2010. 2. Click Start and then type cmd in the text box. In the list of results, right-click cmd, and then click Run as administrator. Click OK. 3. Copy and paste the following command at the command prompt: msiexec /lvx* rbs_enable_WSS_Content.log /q /i rbs.msi ADDLOCAL=EnableRBS DBINSTANCE="<DBInstanceName>" DBNAME="<ContentDbName>" Where: <DBInstanceName> is the name of the SQL Server instance. <ContentDbName> is the name of the content database. The operation should finish within approximately one minute. To set additional content databases to use RBS, see HYPERLINK \l "z83ee2a381b914c6a83de1e968db74611"Set a content database to use Remote BLOB Storage (RBS) (SharePoint Server 2010)To confirm the RBS installation 1. The rbs_install_log.txt log file is created in the same location as the RBS_X64.msi file. Open the rbs_install_log.txt log file by using a text editor and scroll toward the bottom of the file. Within the last 20 lines of the end of the file, an entry should read as follows: Product: SQL Remote Blob Storage Installation completed successfully. 2. On the computer that is running SQL Server 2008, verify that the RBS tables were created in the content database. Several tables that have names that are preceded by the letters "mssqlrbs" should be located under the content database name. Enable and test RBS You must enable RBS on one Web server in the SharePoint farm. It is not important which Web server that you select for this activity, as long as RBS was installed on it by using the previous procedure. To enable RBS 1. On the Start menu, click Programs, click Microsoft SharePoint 2010 Products, and then click SharePoint 2010 Management Shell. 2. At the Windows PowerShell command prompt, type the following commands: $cdb = Get-SPContentDatabase WebApplication Where is the Web application that is attached to the content database. $rbss = $cdb.RemoteBlobStorageSettings $rbss.Installed() $rbss.Enable() $rbss To test the RBS data store 1. Connect to a document library on any Web server. 2. Upload a file that is at least 100 kilobytes (KB) to the document library. 3. On the computer that contains the RBS data store, click Start, and then click Computer. 4. Browse to the RBS data store directory. 5. Browse to the file list and open the folder that has the most recent modified date (other than $FSLOG). In that folder, open the file that has the most recent modified date. Verify that this file has the same size and contents as the file that you uploaded. If it does not, ensure that RBS is installed and enabled correctly. See Also HYPERLINK \l "z0317c12678ed47e09109fe143ddb0259"Migrate content into or out of Remote BLOB Storage (RBS) (SharePoint Server 2010) HYPERLINK \l "z75096f60b94e44c2bc848aa3e2c4fff3"Disable Remote BLOB Storage (RBS) on a content database (SharePoint Server 2010) Set a content database to use Remote BLOB Storage (RBS) (SharePoint Server 2010) This article describes how to set a content database to use Remote BLOB Storage (RBS). Its instructions assume that you have already installed RBS for use with Microsoft SharePoint Server 2010. To install and configure RBS, see HYPERLINK \l "z4cf30b48f9084774920cd2f2916f2c1b"Install and configure Remote BLOB Storage (RBS) with the FILESTREAM provider (SharePoint Server 2010). Set a content database to use RBS To set a content database to use RBS, you must provision a binary large object (BLOB) store in SQL Server, add the content database information to the RBS configuration on a Web server, and then test the BLOB data store. These instructions assume that you have installed SQL Server Management Studio on the database server. If this is not the case, you can download and install Management Studio from HYPERLINK "http://go.microsoft.com/fwlink/?LinkID=186132&clcid=0x409"Microsoft SQL Server 2008 Management Studio Express (http://go.microsoft.com/fwlink/?LinkID=186132&clcid=0x409). You can perform the following procedures on any Web server or application server in the farm. However, for simplicity in this article, we refer to this server as a Web server. Note: These instructions assume that you are using the FILESTREAM RBS provider. If you are using a different RBS provider, refer to that providers instructions to perform these operations. To set a content database to use RBS 1. Verify that the user account that you use to perform this procedure is a member of the Administrators group on the Web server, and is a member of the SQL Server dbcreator and securityadmin fixed server roles on the computer that is running Microsoft SQL Server 2008 R2, SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2, or SQL Server 2005 with SP3 and Cumulative Update 3. 2. Click Start, click All Programs, click Microsoft SQL Server 2008, and then click SQL Server Management Studio. 3. In the Connect to Server dialog box, specify the server type, server name, and authentication method of the database server that you want to connect to, and then click Connect. 4. Expand Databases. 5. Right-click the content database for which you want to create a BLOB store, and then click New Query. 6. In the Query pane, copy and execute the following SQL queries in the sequence that is provided. use [ContentDbName] if not exists (select * from sys.symmetric_keys where name = N'##MS_DatabaseMasterKey##') create master key encryption by password = N'Admin Key Password !2#4' use [ContentDbName] if not exists (select groupname from sysfilegroups where groupname=N'RBSFilestreamProvider') alter database [ContentDbName] add filegroup RBSFilestreamProvider contains filestream use [ContentDbName] alter database [ContentDbName] add file (name = RBSFilestreamFile, filename = 'c:\BLOBStore') to filegroup RBSFilestreamProvider Where [ContentDbName] is the content database name and c:\BLOBStore is the volume\directory that will contain the BLOB store. Be aware that you can provision a BLOB store only one time. If you attempt to provision the same BLOB store multiple times, you will receive an error. Tip: For best performance, simplified troubleshooting, and as a general best practice, we recommend that you create the BLOB store on a volume that does not contain the operating system, paging files, database data, log files, or the tempdb file. 7. Click Start, click Run, type cmd into the Run text box, and then click OK. 8. Copy and paste the following command at the command prompt. msiexec /qn /i rbs.msi REMOTEBLOBENABLE=1 FILESTREAMPROVIDERENABLE=1 DBNAME= FILESTREAMSTORENAME=FilestreamProvider_1 ADDLOCAL=EnableRBS,FilestreamRunScript DBINSTANCE=> Where is the name of the content database, and is the name of the SQL Server instance. The operation should finish within approximately one minute. To test the RBS data store 1. Connect to a document library on any Web server. 2. Upload a file that is at least 100 kilobytes (KB) to the document library. 3. On the computer that contains the RBS data store, click Start, and then click Computer. 4. Navigate to the RBS data store directory. 5. Locate the folder that has the most recent modification date, other than the $FSLOG folder. Open this folder and locate the file that has the most recent modification date. Verify that this file has the same size and contents as the file that you uploaded. If it does not, ensure that RBS is installed and enabled correctly. See Also HYPERLINK \l "zd359cdaa0ebd4c598fc5002cba241b18"Overview of Remote BLOB Storage (SharePoint Server 2010) HYPERLINK \l "z0317c12678ed47e09109fe143ddb0259"Migrate content into or out of Remote BLOB Storage (RBS) (SharePoint Server 2010) Migrate content into or out of Remote BLOB Storage (RBS) (SharePoint Server 2010) This article describes how to migrate content into or out of Remote BLOB Storage (RBS), or to a different RBS provider. After installing RBS and setting a content database to use RBS, all existing content in that database can be migrated into the database's active provider. You use the same Windows PowerShell 2.0 command to migrate content into or out of RBS, or to another RBS provider. When RBS is implemented, SQL Server itself is regarded as an RBS provider. You can migrate content databases at any time, but we recommend that you perform migrations during low usage periods so that this activity does not cause performance degradation for users. Migration moves all content from the specified content database into the storage mechanism of the newly named provider. This operation can be performed on any Web server in the farm. You only need to perform the operation one time on one Web server for each content database that you want to migrate. To migrate a content database by using Windows PowerShell 1. Verify that you meet the following minimum requirements: See HYPERLINK \l "z2ddfad847ca8409e878bd09cb35ed4aa"Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. At the Windows PowerShell command prompt, type the commands in the following steps. 6. To obtain the content database RBS settings object: $cdb=Get-SPContentDatabase $rbs=$cdb.RemoteBlobStorageSettings Where is the name of the content database. 7. To view a list of all RBS providers that are installed on the Web server: $rbs.GetProviderNames() 8. To set the active RBS provider: $rbs.SetActiveProviderName() Where is the name of the provider that you want to make active for this content database. If you want to migrate the content database out of RBS altogether and back into SQL Server inline storage, set this value to (). 9. Migrate the data from RBS to the new provider or to SQL Server: $rbs.Migrate()See Also HYPERLINK \l "z83ee2a381b914c6a83de1e968db74611"Set a content database to use Remote BLOB Storage (RBS) (SharePoint Server 2010) Maintain Remote BLOB Storage (RBS) (SharePoint Server 2010) The maintenance tasks associated with Remote BLOB Storage (RBS) are mainly performed through the RBS Maintainer. The RBS Maintainer performs periodic garbage collection and other maintenance tasks for an RBS deployment. You can schedule these tasks for each database that uses RBS by using Windows Task Scheduler or Microsoft SQL Server Agent. The RBS Maintainer must be provisioned through command-line parameters or through an XML file. In the case of mirrored or replicated databases, the Maintainer should be run against any single instance. In this article:  HYPERLINK \l "_Garbage_collection" Garbage collection  HYPERLINK \l "_RBS_and_BLOB" RBS and BLOB store consistency checks  HYPERLINK \l "_Running_the_RBS" Running the RBS Maintainer Garbage collection Garbage collection is how unreferenced or deleted data is removed from the remote BLOB store. Garbage collection in RBS is performed passively. References to BLOBs are counted by looking at the list of BLOB IDs stored by the application in its RBS table columns at the time of garbage collection. Any BLOB references that are present in the RBS auxiliary tables but absent in any RBS column in application tables are assumed to be deleted by the application and will be collected as garbage. BLOBs that are not present in any RBS column and were created before the Orphan Cleanup Time Window, described later in this article, are also assumed to be deleted by the application and will be collected as garbage. Because passive garbage collection tabulates BLOB references from the RBS columns of an application's tables, every RBS column must have a valid index before it can be registered in RBS. This garbage collection is performed by the RBS Maintainer tool. It should be scheduled to run at non-busy times to reduce the effect on regular database operations. RBS garbage collection is performed in the following three steps: Reference scan. The first step compares the contents of the application's RBS tables with RBS's own internal tables and determines which BLOBs are no longer referenced. Any unreferenced BLOBs are marked for deletion. Delete propagation. The next step determines which BLOBs have been marked for deletion for a period of time longer than the garbage_collection_time_window value and deletes them from the BLOB store. Orphan cleanup. The final step determines whether any BLOBs are present in the BLOB store but absent in the RBS tables. These orphaned BLOBs are then deleted. Configuring RBS garbage collection Garbage collection can be configured by adjusting several Maintainer and database settings. The Maintainer settings are as follows: Maintainer schedule. This setting determines how often the Maintainer will be executed. Task Duration. This setting determines the maximum length that a single Maintainer execution can run. The default setting is two hours. These Maintainer settings should be configured so that the Maintainer activity has minimal effect on regular activity. The database garbage collection settings are described in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=199638"Running RBS Maintainer (http://go.microsoft.com/fwlink/?LinkId=199638). RBS and BLOB store consistency checks The RBS Maintainer verifies the integrity of RBS BLOB references and corrects any errors that are found. It performs several consistency checks for the database, such as verifying that indexes exist for the RBS columns, and verifying that all BLOBs that are referenced by application tables exist in RBS. The Auxiliary Table Consistency Check verifies that the RBS auxiliary tables are in a consistent state by performing the following checks: Verifies that each RBS table column has a valid index. Verifies that registered-applications RBS table columns exist; have enabled, valid indexes; and have the correct column type. The following consistency checks are optional and can be omitted: Verifies that all BLOBs that are referenced in the application tables are present in the RBS tables. Verifies that no BLOBs are marked as both in use and deleted. Any discovered problems will be logged and the RBS Maintainer will attempt to fix them by creating missing index entries, unregistering missing columns, or marking in-use BLOBs as not deleted. Running the RBS Maintainer RBS requires you to define a connection string to each database that uses RBS before you run the Maintainer. This string is stored in a configuration file in the \Microsoft SQL Remote Blob Storage 10.50\Maintainer folder that is ordinarily created during installation. The Maintainer can be run manually by executing the Microsoft.Data.SqlRemoteBlobs.Maintainer.exe program together with the following parameters: Parameter nameDescriptionValuesRequiredConnectionStringName The name of the connection string for the configuration file.RBSMaintainerConnection is the default name that is created during RBS setup.Yes.Operation The garbage collection operations to perform. This parameter takes between one and four arguments. The ForceFinalize value cannot be used in combination with any other operation.ConsistencyCheck GarbageCollection Maintenance ConsistencyCheckForStores ForceFinalizeYes.GarbageCollectionPhases The garbage collection phases to perform. This parameter is used to run or complete the garbage collection. The value must be one or more letters without spaces.r Reference scan. d Delete propagation. o Orphan cleanup.Yes, if garbage collection is to be performed.ConsistencyCheckMode Specifies the type of consistency check to be performed. c Only a check will be performed. r A check will be performed and any issues found will be repaired. b A check, repair, and rebuild of the internal data structures.Yes, if a consistency check is to be performed.ConsistencyCheckExtent Specifies the extent of the consistency check.m Only metadata will be checked; individual BLOBs will remain unchecked. This is the default parameter. c A complete check will be performed.If not specified, m is assumed.ConsistencyCheckForStores Lists the names of the BLOB stores that will be checked for consistency.By default, all BLOB stores are checked.No.TimeLimit