1Backup & Restore Michele Adamomichele.adamo@decatec.it
SommarioLevels of Data RecoveryContent RecoverySite RecoveryDisaster Recovery
Levelsof Data RecoveryContent RecoveryRecovering a document or list by using the Recycle Bin or versioningSite RecoveryRecovering from accidental deletion or data corruption of a site. Site recovery can be performed by site administratorsDisasterRecoveryPerforming recoveries (by using built-in tools or external tools or both) and possibly migrating a site, database, or farm to new hardware. Disaster recovery can be performed by farm administrators.
ContentRecoveryVersioningLosing data by overwriting a documentDocument Library Settings > Versioning SettingsMajor VersionsAlso known as Simple Versioning. Each iteration becomes a full copy of the document with the versions numbered sequentially (1, 2, 3, …)Major & Minor VersionsUse this option if you need to differentiate between Draft versions and Final/Publishedversions.Read-only users can only view major versions
ContentRecoveryRecycle BinFist Stage Recycle BinIt provides an “un-delete” feature that allows end users with appropriate permissions to recover accidentally deleted files, documents, list items, lists, and document libraries from a site. Second Stage Recycle BinWhen an item is deleted from the first-stage Recycle Bin, it can only be recovered by a site collection administrator from the second-stage Recycle Bin.Site and site collection deletion is not managed through the Recycle Bins.
Site RecoveryDirectly recovering a deleted site is not available in MOSS.Youmustplan Backup & Recoveryoperation.
Site Recovery
DisasterRecoveryOffice SharePoint Server ComponentsDisasterRecoveryBinaryFilesPlan regular backups for both operating system files and Office SharePoint Server program fileskeep copies of the installation disks for your operating system, SQL Server, Office SharePoint Server, and software updates.
DisasterRecovery IIS ConfigurationsIIS Configurationforeachfront-end Web Server and ReportingServices Web ServerApplication pool settings, including service accountsHTTP compression settingsTime-out settingsCustom Internet Server Application Programming Interface (ISAPI) filtersComputer domain membershipInternet Protocol security (IPsec) settingsNetwork Load Balancing settingsHost header entriesSecure Sockets Layer (SSL) certificatesDedicated IP address settings
DisasterRecoveryConfiguration DatabaseConfigurations are set inFarm Config DatabaseCentralAdmin Site Content DatabaseConfiguration settings in Office SharePoint Server include the following:
DisasterRecoveryConfiguration DatabaseRestoring backups of the configuration databases taken from a running farm by using the tools built in to SharePoint Products and Technologies or SQL Server is not supportedSQL Backup & Restore Restore of Content Admin & Config DBMove all databases to a new serverhttp://go.microsoft.com/fwlink/?LinkId=118325&clcid=0x409you must stop the farm to ensure that no changes are madef this data is not synchronized, users might experience various random errorsScripted SharePoint Farm Installation using PSConfig.exe and stsadm.exeInstalling Office SharePoint Server 2007 by using the command line (http://go.microsoft.com/fwlink/?LinkId=118674&clcid=0x409).Joel Oleson’s blog entry: Scripted, Unattended and Silent Installs(http://blogs.msdn.com/joelo/archive/2007/07/16/unattended-and-silent-installs.aspx).Ben Curry’s blog entry:  Scripted SharePoint Farm Installation using PSConfig.exe and stsadm.exe (http://mindsharpblogs.com/ben/archive/2008/03/08/4411.aspx).
DisasterRecoveryCustomizationsCustomizations to SharePoint sites can include: Master pages, page layouts and cascading style sheets. These objects are stored in the content database for a Web application.Web Parts, site or list definitions, custom columns, new content types, custom fields, custom actions, coded workflows, or workflow activities and conditions.(Program Files\Common Files\Microsoft Shared\web server extensions\12)Third party solutions and their associated binary files and registry keys, such as IFilters.Changes to standard XML files.Custom site definitions (webtemp.xml).
DisasterRecoveryContentBack up all content and Shared Services Provider (SSP) databases using:Office SharePoint Server built-in toolsSQL ServerMicrosoft System Center Data Protection Manager, Third-party tools built on supported APIs
Office SharePoint Server built-in toolsOffice SharePoint Server provides two built-in backup and recovery tools:Central Administration and the Stsadm command-line tool
Backup & RecoveryCentral Administration
Backup & RecoveryStsadmcommand-line tool
Backup & RecoverySQL Server
Backup strategy recommendations
Backup strategy recommendations
Backup strategy recommendations
Backup strategy recommendations
Backup strategy recommendations
Planning your disaster recovery strategy
Determine likely recovery scenariosAs you plan your disaster recovery scenarios, determine whatcommon recovery  scenarios:Software updatesUser errorsServer hardware failures
Recommended backup standardsStart with the standards that follow for your production environment,and adjust them to meet your needs over time.Minimum!!Create a scheduled full backup of all content databases and frequent differential backups using any tool that backs up databases.Run full backups of any affected content database before and after you perform any significant reorganization of your siteDocument all configurations set in Central AdministrationFor each front-end Web server, document all IIS settingsBack up customizationsCarefully consider when to schedule your backups. During a backup, the resources that are being backed up cannot be written to, the system may also be slow in responding to requests. test your backup and recovery process regularly to ensure that your administrators and operators are able to restore the system quickly.
Recommended recovery environmentThe recovery environment you require depends on the scenario for which you arerecovering content:Recover an out-of-date site collection, site, or database to restore specific contentCreate a recovery farm to support this scenarioRecover a database or site collection to move it to a new locationMove your content directly to your new locationNew Location must have the same updates and software versions Recover a database or site collection as part of an upgrade or migrationMove your content directly to your new locationNew Location must have the same updates and software versionsRecover a farmconfigure a failover farm that you can connect to your environment while you are recovering your primary farm
Data Protection ToolsMicrosoft System Center Data Protection Manager 2007AvePoint Backup & RecoveryQuest RecoverySymantec Agent for SharePointCheck if your Data Protection Software has an Agent for SharePoint!
Sharepoint 2007 backup & restore

Sharepoint 2007 backup & restore

  • 1.
    1Backup & RestoreMichele Adamomichele.adamo@decatec.it
  • 2.
    SommarioLevels of DataRecoveryContent RecoverySite RecoveryDisaster Recovery
  • 3.
    Levelsof Data RecoveryContentRecoveryRecovering a document or list by using the Recycle Bin or versioningSite RecoveryRecovering from accidental deletion or data corruption of a site. Site recovery can be performed by site administratorsDisasterRecoveryPerforming recoveries (by using built-in tools or external tools or both) and possibly migrating a site, database, or farm to new hardware. Disaster recovery can be performed by farm administrators.
  • 4.
    ContentRecoveryVersioningLosing data byoverwriting a documentDocument Library Settings > Versioning SettingsMajor VersionsAlso known as Simple Versioning. Each iteration becomes a full copy of the document with the versions numbered sequentially (1, 2, 3, …)Major & Minor VersionsUse this option if you need to differentiate between Draft versions and Final/Publishedversions.Read-only users can only view major versions
  • 5.
    ContentRecoveryRecycle BinFist StageRecycle BinIt provides an “un-delete” feature that allows end users with appropriate permissions to recover accidentally deleted files, documents, list items, lists, and document libraries from a site. Second Stage Recycle BinWhen an item is deleted from the first-stage Recycle Bin, it can only be recovered by a site collection administrator from the second-stage Recycle Bin.Site and site collection deletion is not managed through the Recycle Bins.
  • 6.
    Site RecoveryDirectly recoveringa deleted site is not available in MOSS.Youmustplan Backup & Recoveryoperation.
  • 7.
  • 8.
    DisasterRecoveryOffice SharePoint ServerComponentsDisasterRecoveryBinaryFilesPlan regular backups for both operating system files and Office SharePoint Server program fileskeep copies of the installation disks for your operating system, SQL Server, Office SharePoint Server, and software updates.
  • 9.
    DisasterRecovery IIS ConfigurationsIISConfigurationforeachfront-end Web Server and ReportingServices Web ServerApplication pool settings, including service accountsHTTP compression settingsTime-out settingsCustom Internet Server Application Programming Interface (ISAPI) filtersComputer domain membershipInternet Protocol security (IPsec) settingsNetwork Load Balancing settingsHost header entriesSecure Sockets Layer (SSL) certificatesDedicated IP address settings
  • 10.
    DisasterRecoveryConfiguration DatabaseConfigurations areset inFarm Config DatabaseCentralAdmin Site Content DatabaseConfiguration settings in Office SharePoint Server include the following:
  • 11.
    DisasterRecoveryConfiguration DatabaseRestoring backupsof the configuration databases taken from a running farm by using the tools built in to SharePoint Products and Technologies or SQL Server is not supportedSQL Backup & Restore Restore of Content Admin & Config DBMove all databases to a new serverhttp://go.microsoft.com/fwlink/?LinkId=118325&clcid=0x409you must stop the farm to ensure that no changes are madef this data is not synchronized, users might experience various random errorsScripted SharePoint Farm Installation using PSConfig.exe and stsadm.exeInstalling Office SharePoint Server 2007 by using the command line (http://go.microsoft.com/fwlink/?LinkId=118674&clcid=0x409).Joel Oleson’s blog entry: Scripted, Unattended and Silent Installs(http://blogs.msdn.com/joelo/archive/2007/07/16/unattended-and-silent-installs.aspx).Ben Curry’s blog entry: Scripted SharePoint Farm Installation using PSConfig.exe and stsadm.exe (http://mindsharpblogs.com/ben/archive/2008/03/08/4411.aspx).
  • 12.
    DisasterRecoveryCustomizationsCustomizations to SharePointsites can include: Master pages, page layouts and cascading style sheets. These objects are stored in the content database for a Web application.Web Parts, site or list definitions, custom columns, new content types, custom fields, custom actions, coded workflows, or workflow activities and conditions.(Program Files\Common Files\Microsoft Shared\web server extensions\12)Third party solutions and their associated binary files and registry keys, such as IFilters.Changes to standard XML files.Custom site definitions (webtemp.xml).
  • 13.
    DisasterRecoveryContentBack up allcontent and Shared Services Provider (SSP) databases using:Office SharePoint Server built-in toolsSQL ServerMicrosoft System Center Data Protection Manager, Third-party tools built on supported APIs
  • 14.
    Office SharePoint Serverbuilt-in toolsOffice SharePoint Server provides two built-in backup and recovery tools:Central Administration and the Stsadm command-line tool
  • 15.
  • 16.
  • 17.
  • 18.
  • 19.
  • 20.
  • 21.
  • 22.
  • 23.
    Planning your disasterrecovery strategy
  • 24.
    Determine likely recoveryscenariosAs you plan your disaster recovery scenarios, determine whatcommon recovery scenarios:Software updatesUser errorsServer hardware failures
  • 25.
    Recommended backup standardsStartwith the standards that follow for your production environment,and adjust them to meet your needs over time.Minimum!!Create a scheduled full backup of all content databases and frequent differential backups using any tool that backs up databases.Run full backups of any affected content database before and after you perform any significant reorganization of your siteDocument all configurations set in Central AdministrationFor each front-end Web server, document all IIS settingsBack up customizationsCarefully consider when to schedule your backups. During a backup, the resources that are being backed up cannot be written to, the system may also be slow in responding to requests. test your backup and recovery process regularly to ensure that your administrators and operators are able to restore the system quickly.
  • 26.
    Recommended recovery environmentTherecovery environment you require depends on the scenario for which you arerecovering content:Recover an out-of-date site collection, site, or database to restore specific contentCreate a recovery farm to support this scenarioRecover a database or site collection to move it to a new locationMove your content directly to your new locationNew Location must have the same updates and software versions Recover a database or site collection as part of an upgrade or migrationMove your content directly to your new locationNew Location must have the same updates and software versionsRecover a farmconfigure a failover farm that you can connect to your environment while you are recovering your primary farm
  • 28.
    Data Protection ToolsMicrosoftSystem Center Data Protection Manager 2007AvePoint Backup & RecoveryQuest RecoverySymantec Agent for SharePointCheck if your Data Protection Software has an Agent for SharePoint!