|THE CONTENT OF THIS PAGE IS OUTDATED
|SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.
SEP sesam supports backups of the Microsoft SharePoint server 2007 and 2010. For this there are 2 backup types available: Farm-backup and Site-Backup. The Farm-backup can be used to back up all databases consistently. The Site-backup is used to back up web applications and all documents consistently.
The following options are available for restoring:
- Restore the database
- Restore the IIS-Sites
- Restore documents (also "Single document restore")
Scope: This article describes SharePoint backup with Sesam version 18.104.22.168!
- SEP sesam version 22.214.171.124
- Microsoft SharePoint 2007/2010
The configuration of a backup strongly depends on the SharePoint environment. There are several requirements that have to be met:
- The SEP sesam service has to have the rights of an AD user that has full access to the SharePoint server.
- In order to save the files temporarily, a Share that the SharePoint server as well as the MS-SQL server have full access to, has to be created.
- Additionally, this Share has to be defined on the SEP sesam Client in
<SESAM_ROOT>/var/ini/sm.iniunder [PATHES], e.g.
The Farm backup is used to back up all relevant SharePoint databases. For this backup the types FULL and DIFF are available.
The SharePoint site backup is used to back up all site collections. Individual site collections and single web applications within a site collection, can also be saved (for this the according collection or application has to be selected).
The files are either restored with a Farm-restore or a Site-restore. In the following paragraphs all restore scenarios that are possible with SEP sesam are described. For this it is important to have exact knowledge of your own SharePoint environment because these restore scenarios may have to be adjusted to the according SharePoint environment.
For the Site-restore select the according site collection or the web application.
Single Document Restore
In order to restore single documents, select them in the according web application.
Using the Farm-restore, the required databases of the SharePoint server can be restored. The options "Auto recover after restore" and "overwrite existing files" are important here in order to replace the existing database.
In case of a Site Backup only Sites which are changed since the last FULL backup are backed up. SharePoint backup only allows for a Farm to process a backup with the level 'Full' or 'Differential'.
In case of SharePoint sites there is no way to restrict the data on changed content of the sites. So a Differential backup will always back up the entire content of a site which was changed since the last FULL backup. Only the sites which are completely unchanged since the last FULL backup will not be saved. Therefore it is clear that a site DIFF backup will always back up most of the sites as the main sites are often changed.
In case of a Farm backup or a 'Content Component' of a Farm the SharePoint API offers the possibility to do a real Differential Backup. To allow this the Differential Backup needs the spbrtoc.xml of the last successful FULL backup. This must not interfere with COPY Backups of the Farm or the Content Components.
- After a FULL backup the summary file spbrtoc.xml must reside on the SharePoint host, in the same directory where the next Differential backup will run. So in case of a FULL or DIFF backup the sbc must delete all intermediate backup files after the backup except the spbrtoc.xml.
- To achieve a common directory for FULL and DIFF the path for the intermediate backup files for FULL and DIFF must contain only the SEP sesam jobname - not the saveset name. e.g. "
- In case of a COPY backup the path must be different so the saveset name is postfixed to it.
- The sbc must save the recent spbrtoc.xml before the backup starts to allow a reset to the old one if the backup fails, e.g. the data transfer to the SEP sesam Server failed.
- In case of restore the saved spbrtoc.xml must be restored to the intermediate location before recovering the data.
- Generation Restore: SEP sesam Restore Wizard must show data of FULL and DIFF savesets (generation restore) and restore must start the FULL and the DIFF restore job (SEP sesam Kernel).
-  Backup and restore: Stsadm operations (Office SharePoint Server)