2. Sommario Levels of Data Recovery Content Recovery Site Recovery Disaster Recovery
3. Levelsof Data Recovery Content RecoveryRecovering a document or list by using the Recycle Bin or versioning Site RecoveryRecovering from accidental deletion or data corruption of a site. Site recovery can be performed by site administrators DisasterRecoveryPerforming 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. ContentRecoveryVersioning Losing data by overwriting a document Document Library Settings > Versioning Settings Major Versions Also known as Simple Versioning. Each iteration becomes a full copy of the document with the versions numbered sequentially (1, 2, 3, …) Major & Minor Versions Use this option if you need to differentiate between Draft versions and Final/Publishedversions. Read-only users can only view major versions
5. ContentRecoveryRecycle Bin Fist 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.
6. Site Recovery Directly recovering a deleted site is not available in MOSS. Youmustplan Backup & Recoveryoperation.
9. DisasterRecovery IIS Configurations IIS Configurationforeachfront-end Web Server and ReportingServices Web Server Application pool settings, including service accounts HTTP compression settings Time-out settings Custom Internet Server Application Programming Interface (ISAPI) filters Computer domain membership Internet Protocol security (IPsec) settings Network Load Balancing settings Host header entries Secure Sockets Layer (SSL) certificates Dedicated IP address settings
11. DisasterRecoveryConfiguration Database Restoring 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 supported SQL Backup & Restore Restore of Content Admin & Config DBMove all databases to a new serverhttp://go.microsoft.com/fwlink/?LinkId=118325&clcid=0x409 you must stop the farm to ensure that no changes are madef this data is not synchronized, users might experience various random errors Scripted SharePoint Farm Installation using PSConfig.exe and stsadm.exe Installing 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. DisasterRecoveryCustomizations Customizations 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 Filesommon Filesicrosoft Sharedeb server extensions2) 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. DisasterRecoveryContent Back up all content and Shared Services Provider (SSP) databases using: Office SharePoint Server built-in tools SQL Server Microsoft System Center Data Protection Manager, Third-party tools built on supported APIs
14. Office SharePoint Server built-in tools Office SharePoint Server provides two built-in backup and recovery tools: Central Administration and the Stsadm command-line tool
24. Determine likely recovery scenarios As you plan your disaster recovery scenarios, determine what common recovery scenarios: Software updates User errors Server hardware failures
25. Recommended backup standards Start 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 site Document all configurations set in Central Administration For each front-end Web server, document all IIS settings Back up customizations Carefully 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 environment The recovery environment you require depends on the scenario for which you are recovering content: Recover an out-of-date site collection, site, or database to restore specific contentCreate a recovery farm to support this scenario Recover 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 versions Recover a farmconfigure a failover farm that you can connect to your environment while you are recovering your primary farm
27.
28. Data Protection Tools Microsoft System Center Data Protection Manager 2007 AvePoint Backup & Recovery Quest Recovery Symantec Agent for SharePoint Check if your Data Protection Software has an Agent for SharePoint!