Microsoft SharePoint
Microsoft SharePoint is a content management system (CMS) that hosts business-relevant data for businesses of any size. With its document and file management, collaboration, system integration, and workflow automation features, failure of a SharePoint system affects far more than just email communication, it affects the entire business.
SEP sesam restores all SharePoint servers as well as all files that are saved in databases in no time. This includes site collections, sites, lists and the configuration of the SharePoint environment. With the SEP sesam extension for SharePoint, everything is backed up without disrupting applications.
| SharePoint Component | SEP sesam |
| Farm | ✔ |
| Service Applications | ✔ |
| Web Application | ✔ |
| Content databases | ✔ |
| Site collection | ✔ |
| Site | ✔ |
| Document library or list | ✔ |
| List item or document | ✔ |
| Content stored in remote BLOB stores | ✔ |
| Customization deployed as solution packages | ✔ |
| Changes to Web.config made by using Central Administration or an API | ✔ |
| Configuration settings | ✔ |
| Customizations not deployed as solution packages | ✔ |
| Changes to Web.config not made by using Central administration or an API | ✔ |
| IIS configurations not set through SharePoint | ✔ |
| SQL Server Reporting Services databases | ✔ |
Site Collection:
Database-level backups and restores can be used for site collection recovery if a single site collection is stored in a database. For unattached database recovery, Farm-level backups must be implemented in order to restore site collections, sites, lists, and configurations.
Site:
Farm-level and database-level backups can be used with the SharePoint Server unattached database recovery to restore site collections, sites, lists, and configurations.
BLOB Stores:
Content stored in remote BLOB stores can be restored by using a SEP sesam database extensions
Web.config
Web.config configurations are supported and backed up by SEP sesam
ISS
ISS configurations are supported and backed up by SEP sesam
Customization
Fully-trusted solution packages are stored in the configuration database. Sandboxed solutions are stored in content databases. Both of which can be recovered as part of farm or content database recovery.
Configuration settings
Configuration settings can be recovered from farm-level backups.
