Archive:SEP SharePoint en

From SEPsesam
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.

Template:Copyright SEP AG en


SEP sesam supports backups of the Microsoft SharePoint server 2007(partially), 2010 and 2013. The following Backup Tasks must be set up to allow a complete system restore:

  • Backup the IIS Configuration with source 'VSS:IIS Configuration Writer' - (covered by backup type 'System Recovery').
  • Backup the IIS Metabase data with source 'VSS:IIS Metabase Writer' - (covered by backup type 'System Recovery').
  • Backup the SharePoint data with task type 'SharePoint Server' and source 'all'.
  • Backup of the System it self with Backup-Type "Path" and source "all" + VSS enabled
  • Backup the SharePoint MSSQL Server with the SEP sesam MSSQL extension.

The following options are available for restoring:

This article describes SharePoint backup with Sesam version 4.2.2.x! The previous SharePoint backup article for is here!


  • For the Version the following Patch must be installed on the SEP sesam Server

[SharePoint Patch für die SEP sesam Version]

Quick Setup


System Requirements

  • SEP sesam version since
  • Microsoft SharePoint 2007/2010/2013
Distributed SQL Server Environment
The SEP sesam SharePoint module only supports a complete (Full/Copy) backup of SharePoint Server environments which are set up with one SQL Server. In case of more databases several backup tasks for the distributed SQL Server databases must be set up and no automated document restore for such databases is available.
SQL Server Log Truncation
The 'SharePoint Server' backup does not truncate the SQLServer Transaction logs. SEP recommends to set up a periodic execution of SQLServer backup tasks with level FULL and INCR in addition to the 'SharePoint Server' tasks.

Configuration of a SharePoint Backup

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. This user must have the sysadmin role.
  • If the SQL Server is running on another node then the SEP sesam service on that SQL Server node must run with an AD user with full access to the SQL Server. The user must have the sysadmin role.
  • The SharePoint writer 'SharePoint Services Writer' must be registered. The following command must be executed by an user with administration rights for the SharePoint System (like qs12\sp_sfa): #> stsadm.exe -o registerwsswriter

Example for SharePoint Server 2010:

#> "%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\bin\stsadm.exe" -o registerwsswriter

Note: The STSADM.exe is the command-line tool for administration of Office SharePoint Server (SharePoint 2007, SharePoint 2010/2013). It is installed on the same location as SharePoint Products and Technologies location: "%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\12\bin" (for SharePoint 2007), "%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\14\bin" (for SharePoint 2010) or "%COMMONPROGRAMFILES%\Microsoft Shared\Web Server Extensions\15\bin" (for SharePoint 2013). You must be Farm Administrator to be able to run the tool.

Benutzerrechte MOSS en.jpg

Retrieving the SQL Server

The backup module must connect to the SQL Server to get the database data. Therefore the browsing command on the Share Point Server is used to get the serving SQL Servers. The name for the SQL Server host must be present in the Sesam Clients table otherwise an error "E004-BACKUP {task} Could not find client [xyz] in table 'clients'" may occur. The name resolution may retrieve a different name even for the Share Point server itself, e.g. without fully qualified domain name (FQDN).

Attention: Currently a distributed environment with more then 1 SQL Server is not supported.

Retrieving the SharePoint Documents

To retrieve the SharePoint documents the appropriate sqlmgr.dll must be used at SQLServer clients.

Hint: The sqlmgr.dll for SharePoint Server 2010/2013 is included in the Sesam srv package. It must not be exchanged if srv package is used on a SharePoint 2010/2013 system. Since version the sqlmgr.dll for SharePoint Server 2010/2013 is included in all Sesam packeges (SRV/GUI/CLI).

The Sesam service must run under a SharePoint administration account which has sysadmin role. Therefore if the sysadmin role is not set it must be added to the SharePoint administrator account, e.g. the user sp_sfa.

Configuration of a SharePoint Server Backup

The SharePoint backup is used to back up all relevant SharePoint databases. For this backup currently only the types COPY and FULL are available. A DIFF backup is under construction.

SharePoint Task 4.2.2.jpg

Note: There is no extra SharePoint site backup needed. The information about the sites and the documents is extracted from the SQL Server databases during the SharePoint Server backup.

SharePoint restore scenarios

Supported restore scenarios for the SEP sesam SharePoint module for version

  • Restore of single documents "always the latest version" only to the "original" destination
    • Restore of attachments from a document are not supported
  • For a SharePoint-Database restore, an additional MSSQL Backup has to be performed via the SEP sesam MSSQL extension.
  • For all other restore scenarios, contact your SharePoint administrator, respectively your SharePoint developer in case some special modifications, developments and changes were performed on your SharePoint system. It has to be clarified first, what parts of the SharePoint Farm are effected from this data lost.

In case it is not clear what single parts of the system or the DB has to be restored, plan a recovery of all SharePoint components. It is important that a disaster recovery situation must be planed before setting up the backup solution!

SEP sesam BSR and VM backups can be very helpful to provide a fast restore of all SharePoint components to a previous state.

How to restore a single document to the original destination with the version

  • Select the SharePoint backup -> Next
  • Select the deleted document (make sure that the document doesn't exists on the SharePoint server anymore)-> Next
  • Select the SharePoint MSSQL Server as the "new" target node (see screenshot)
  • Select the first option "Restore to generated RDB" (see screenshot) -> New window pops up
    • Select a new and empty directory on your MSSQL server with enough space for the restore of the restore DB
  • Select "Import to original database" (see screenshot)

New Restore Task Save and Start2.jpg

Exchange Paths for automatic RDB.jpg

The data is restored with a document restore or via a database restore. The document restore is processed by the creation of a temporary database, restoring of the original database into the temporary and merging of the selected documents into the original database.

  • After the successful document restore, open the "SQL Server Management Studio", then stop + delete the generated RDB database
    • Delete the DB files in the temporary restore directory as well

Additional Links/Literature

  • SharePoint 2013 VSS Writer [1]