SharePoint 2010 Backup and Restore – What’s New
Mai 28, 2010 1 Kommentar
Kurz vor dem Wochenende ist Backup & Recovery mein heutiges Thema. Unsere alte SharePoint 2007 Umgebung (Company Web / Knowledgebase / Blogs / MySite) haben wir mit DocAve for SharePoint gebackupt und ggf. Sites, oder Files wiederhergestellt. Jetzt suche ich neben den SharePoint eigenen Bordmitteln nach neuen Alternativen und teste gleichzeitig auch die Bordmittel im Detail.
Meine 2010er Umgebungen werden zurzeit via Content Database SQL Server Backup gesichert und, zum Glück musste ich das nur testen, wiederhergestellt. Zurzeit ist diese Methode noch ausreichend, für einen Restore auf File bzw. Elementebene in Kundenumgebungen später jedoch nicht vorteilhaft. Zur Auswahl stehen die bekannten Tools DocAve for SharePoint 2010 von AvePoint, Recovery Manager for SharePoint von Quest und Backup Exec 2010 & System Recovery von Symantec. Einen ausführlichen Testbericht gibt’s dann etwas später – jetzt richte ich erst einmal alle Tools ein, dann heißt es: testen bis der Arzt kommt 😉
Aber was ist jetzt eigentlich neu bzw. anders bei den SharePoint 2010 eigenen Bordmitteln als in SharePoint 2007? Dazu habe ich einen kurzen und doch recht informativen Artikel auf sharepointmonitor.com gefunden:
SharePoint 2010 Backups are a major advance over the backup facilities in SharePoint 2007. SharePoint can now easily maintain full backups and even granular backups, where only selected data can be restored. For this article I will demonstrate how to use PowerShell to backup and restore SharePoint applications as well as the standard the SharePoint web interface.
Content Database Recovery
In SharePoint 2007, my preference for SharePoint backup was to perform a database backup. It was easy to maintain and backup/restore over many SharePoint farms, and it needed little administrative work in case when I had to move the sites to different farms, or restore broken farms to new hardware. To the experienced SharePoint administrator, with the content databases only, it didn’t take long to restore the content. But the real disadvantage of SharePoint backup via database backup was not in the hard recovery, where you had to deal with the entire server failures – the pain was recovering a single file from a document library that was accidentally deleted. The only way to recover that file using the database backups, was to fully restore it on different farm, attach it to any temporary SharePoint site and browse to the file to restore it from the library. Now this is no longer an issue, since we have Unattached Content Database Recovery.
Unattached Content Database Recovery allows you to browse through the content database using SharePoint, navigate to a list or document library and save the list or library into .cmp file which can easily be moved between sites.
Unattached Content Database Recovery
To be able to use this feature, you simply need to attach the content database backup with a different name to a SQL server instance and then use the screen (shown above) to retrieve any content from the attached database backup. You do not need to attach that database to any site inside a farm anymore. This feature is a part of the Granular Backup functionality in SharePoint. You can store that way entire content databases using MS SQL management tools or decide to backup only the site collection.
Backup and Restore feature
The stsadm powered backup and restore features from SharePoint 2007 are still here, but they have changed and now they can be helpful rather than painful for the administrator.
Backup in Central Administration
Central Administration now checks if the required services are running and gives the choice to backup the entire farm, or only selected applications or services. Backup and restore from Central Administration performs the same operations as the command line and stsadm tool. When you choose the content to backup, you may decide to perform full or differential backup and provide the path to the storage location for the backup.
Backup Using StsAdm
To perform the backup using StsAdm (which may be helpful when configuring automatic backups) you should first type in the backup command itself, to see what it is capable of.
To be able to use StsAdm, open the CMD window and browse to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\bin directory and type in the stsadm command for backup as shown below:
The backup command for SharePoint 2010 is very similar to 2007 but now it is now much more efficient. For example, you can now easily backup search indexes and restore which was impossible in SharePoint 2007 and was a big issue for companies that had millions of documents and needed instant search access in their production environments.
Sample command to perform a farm backup with stsadm:
Stsadm –o backup –directory \\myServer\backup -backupmethod full
Using Powershell to Perform SharePoint Backups
To be able to use SharePoint commands with PowerShell, we first need to load the SharePoint snap-ins into the PowerShell console.
Now in a similar way to using StsAdm , we can test what PowerShell is capable of by typing the get-help Backup-SPFarm command. The PowerShell cmdlet allows for creating a backup of an individual database, web application or the entire farm. It is able to backup individual components or entire farm settings at once, but if we want to backup the site contents, we should check the Backup-SPSite cmdlet instead.
Examples of Backup-SPFarm:
Make full backup of configuration settings of the farm to the Backup directory:
Backup-SPFarm -Directory \\file_server\share\Backup -BackupMethod full -ConfigurationOnly
Backup the farm using 10 Backup threads and place the farm backup into C:\Backup folder. (the force parameter will force the backup even if there’s is insufficient space for the backup files:
Backup-SPFarm -Directory C:\Backup -BackupMethod full -BackupThreads 10 -Force
Backup a specific site collection to the C:\Backup folder:
Backup-SPSite http://server_name/sites/site_name -Path C:\Backup\site_name.bak
When I was using SharePoint Server 2007 the out-of-the-box backup and restore mechanisms were inadequate for backing up a large corporate SharePoint installation. Instead I stayed with the trusted the database backup, however there is always a need minimize the effort to accomplish a task, and and SharePoint 2010’s backup and restore are now enterprise ready.