Name: Akesh Lalla (Solutions Sales Professional: EPM) Bishan Ruder (Premier Field Engineer: EPM) Company: Microsoft Session Code : OFC314 Session Objectives and Takeaways Session Objectives Where is my EPM data? Discuss what are options to backup any components on your SharePoint/EPM Farm Session will not cover in detail backup/restore plan and all high availability options Learn how to recover your data Learn how to recover from a catastrophic failure on your EPM farm Backup and Restore Types Content RecoveryBackup/Restore End user driven Accidental update or deletion Frequent and small-scale Disaster Recovery Farm or Database Restore Hardware Failure or Disaster Hardware Migration or Replacement Minimize Downtime Large Amounts of Data Redundancy Additional Hardware Content Recovery Solutions EPM Administrative Backup EPM Settings Recycle Bin Versioning EPM Components EPM Content (Where is my data?) EPM Data Project Enterprise Resource Enterprise Custom Field Enterprise Global () EPM Data in SharePoint (Content DB) Documents Issues Risks Deliverables EPM Data EPM Administrative Backup/Restore Use of Project_Archive Database Define the retention levels (versioning) Driven by EPM Functional Administrator Can be scheduled Define the retention level (policy) Oops I have deleted my project! EPM Data Pros Consistent Data No IT Involvement You can use API for more flexibility Cons All data is saved Not a backup or high availability solution Beware of space number of versions EPM Administrative Backup EPM 2007 Resource Kit Portfolio Analyzer Views Migration Project Server Settings Backup and Restore (Playbooks) Project Server Data Populator Project Workspace Site Relinker View Effective Rights EPM Settings Backup/Restore Project Server 2007 Settings For example to move a configuration from/to different environments Development/Integration/Production Tool in EPM 2007 Resource Kit Playbooks How do I copy Project Server 2007 settings from development to production ? Playbooks EPM Settings Pros No need to transfer the EPM data Clean way to work with several environments Backup your settings and keep history Cons Not a backup or high availability solution EPM Data in SharePoint SharePoint lists Issues Risks, Deliverables Documents Recover Content SharePoint Recycle Bin Versions Recycle Bin End User Driven Support Lists, Documents Libraries, Folders, Documents, and List Items Two Stages End user Site Collection Administrator Site Collection Level Versioning Pros Supports both List Item and Document versioning End Users can retrieve earlier versions Cons Versions count towards site quota Functionality need to be enabled per List/Document library (Disabled on default) Does not support Folders, Webs, and/or sites Backup and Restore Types Content RecoveryBackup/Restore End user errors Accidental update or deletion Frequent and small-scale Disaster Recovery Farm or Database Restore Hardware Failure or Disaster Hardware Migration or Replacement Minimize Downtime Large Amounts of Data Redundancy Additional Hardware Disaster Recovery Backup and Restore Solutions SharePoint Backup/Restore SQL Server Backup and Restore System Center Data Protection Manager (DPM) Third-Party Solutions SharePoint Backup/Restore I have a small to medium deployment. Do you have anything for me out of the box? Yes! Out of the box Backup/Restore UI and Command Line for Central Administrators Wondering Our recommended solution for small-medium deployments Database Size < 200 GB SharePoint Backup/Restore How it works? File Server Farm Central Admin Console SQL Backup/Restore SharePoint Backup/Restore Details Out of the Box UI and command line access for Central Administrator Hooks up SharePoint databases and search index on Restore Supports Full and Differential backup Backs up the search index (MOSS only) Extensible framework for 3rd party applications SharePoint Backup/Restore Limitations Use the command line with Windows Task Scheduler for scheduled backups Backs up content, SSP, EPM Databases and search index You must manually backup front end files We recommend you keep images of your web front ends High restore time Low availability Command Line %CommonProgramFiles%\Microsoft Shared\Web Server Extensions\12\bin\Stsadm o backup directory \\SHARE\Backup backupmethod full > D:\LOGS\Log_backup.txt Configuring SharePoint Backup/Restore Part 1 Full Farm Recovery Process Prepare Servers and Install Prepare to restore Restore Backups Redeploy Customization SQL Server 1. Rebuild database servers Install Windows Server 2003 SQL Server 2005 Software updates. Application Server 2. Rebuild application servers. Install Windows Server 2003 and.NET Framework 3.0 Software updates. Install Office Project Server 2007 (Type: Complete) with SP1/IU/SP2 4. Run the SharePoint Products & Technologies wizard on the application server. 5. Start Project services. 7. Restore the Office SharePoint Server farm backup. 9. (Optional) Reconfigure alternate access mappings 10. (Optional) Start timer jobs. Front End Web servers 3. Rebuild front-end Web servers. Install Windows Server 2003, IIS, ASP.NET, and the.NET Framework 3.0. Install Office SharePoint Server 2007 (Type: front- end Web) with SP1/IU/SP2 6. Run the SharePoint Products and Technologies Wizard on the front-end Web servers 8. (Optional) Reconfigure IIS settings. 11. (Optional) On all front-end Web servers, redeploy solutions and reactivate features or restore the 12 hive using the Windows Server 2003 Backup tool Solution for each scenario For Disaster Recovery To create a backup farm Use stsadm o backup/restore To migrate a site collection Use stsadm o backupTo migrate a site/list/library/item Use stsadm o export/import for sites Use Site Manager within Site collection Project Server 2007 Resource kit tool Project Workspace Site Relinker RelinkAllWSSSites SQL-Only Backup/Restore Pros Reuse existing technology and processes Non-application specific Can be faster than SharePoint backup Can back up to tape Remember Post-restore reattachment and clean up Search index must be backed up separately via SharePoint backup for MOSS My SQL servers are managed by a separate organization or data center from my SharePoint installations. System Center DPM (Data Protection Manager) Content database > 100 GB Site Collection larger than 12 GB Webcast0/how-to-protect-sharepoint-with-dpm2007-new- streaming-video.aspx DPM 2007 and SharePoint 2007 DPM can be used to recover content items, sites, and farms. For more information, see: How to Recover a Windows SharePoint Services Item (http://go.microsoft.com/fwlink/?LinkId=102815&clcid=0x4 09)http://go.microsoft.com/fwlink/?LinkId=102815&clcid=0x4 09 How to Recover a Windows SharePoint Services Site (http://go.microsoft.com/fwlink/?LinkId=102826&clcid=0x4 09)http://go.microsoft.com/fwlink/?LinkId=102826&clcid=0x4 09 How to Recover a Windows SharePoint Services Farm (http://go.microsoft.com/fwlink/?LinkId=102831&clcid=0x4 09)http://go.microsoft.com/fwlink/?LinkId=102831&clcid=0x4 09 3rd Party Backup Tools What to look for in a 3rd party solution Does it back up the Search Index? Does it require post-restore manual work SharePoint integration with VSS framework Easier for 3rd parties to write custom backup/restore tools Entire server (search index is included) Only supports catastrophic overwrite scenario (not migration) I want to use a custom or 3 rd party tool to backup/restore my farm! Does SharePoint support that? Backup Restore Types Content RecoveryBackup/Restore End user errors Accidental update or deletion Frequent and small-scale Disaster Recovery Minimize Downtime Large Amounts of Data Redundancy Additional Hardware Farm or Database Restore Hardware Failure or Disaster Hardware Migration or Replacement High Availability and Disaster Recovery Solutions Installation Scenarios Web Front End Availability Database Availability Database Mirroring Log Shipping SQL Clustering Low Availability Single Server Scenario One Server Configured as: Web Front-End Server Role Application Server Role Database Server Role Appropriate for limited use-scenarios including the following Installing Office Project Server 2007 for evaluation purposes Deploying only Microsoft Windows SharePoint Services 3.0 Deploying Office Project Server 2007 for a limited purpose (such as for a single department) or for a limited number of users Server Type RAMDiskProcessor Stand-alone2 GB NTFS file systemformatted partition with 3 GB of free space plus adequate free space for your Web sites (Typically at least 100GB) Dual processors that are each 3 GHz or faster High Availability Multi-server farm scenario Optimizes performance of web servers Increases redundancy and reduces points of failure Redundancy at WFE and Database server roles Determine configuration based on your business needs and goals Determine config of other Application roles (PSI, Excel Services, Index, Forms, etc) Multiple Application Servers dont give you fault tolerance You will need to remove any failed server from the farm MOM can help you here Web Servers Application Server Clustered/Mirrored SQL Server SQL Server Failover Clustering Unattended application availability: automatic failover capability without administrator intervention Shared cluster name means no app awareness necessary If my SQL server blows up (hardware failure), how do I keep my EPM/SharePoint farm running? Server Cluster SharePoint Web Front Ends Shared Disk Array Node A Node B Heartbeat Database Mirroring Implemented on a per database level Transactions sent from principle to mirror Provides a warm standby in case of failure Principal and mirror must be separate SQL 2005 SP1 servers (Enterprise or Standard) Optional witness server to monitor primary and mirror to ensure both are working Automatic failover - on failure the witness will turn the mirror into the principle Using Database Mirroring with MOSS 2007:0x409 (updated December 2007)0x409 Database Mirroring Three modes that can be used High Protection: synchronizes transaction writes on both servers, manual failover. Intolerant to latency and performance problems High Availability: same as above but uses a witness server to manage failover High Performance: writes are not synchronized on both servers. Assumes everything will complete successfully on the mirror. Tolerant to latency and low bandwidth Database Mirroring Witness Server Principal Mirror Encrypted channel Everything ok? Principal Down! Im OK!New Principal SharePoint And Mirroring SharePoint is not mirroring aware. When failover occurs need to notify SharePoint Need to tell these DBs that a new server is now the principal Configuration Database, Admin Content Database Content Database Shared Service Provider Database (MOSS) Search Database (MOSS) Content DBs attach reattach Config DB and Admin content DB stsadm.exe -o renameserver -oldservername - newservername SharePoint And Mirroring SharePoint is not mirroring aware. When failover occurs need to notify SharePoint Need to tell these DBs that a new server is now the principal Configuration Database, Admin Content Database Content Database Shared Service Provider Database (MOSS) Search Database (MOSS) Content DBs attach reattach Config DB and Admin content DB stsadm.exe -o renameserver -oldservername - newservername EPM And DB Mirroring DB Mirroring has numeric limitation Can work just for the 4 project Dbs Use synchronous mirroring In case of failure edit your PWA instance to point to the new SQL server instance Log-Shipping Backup/Restore based technology that relies on transaction log files Need to have a shared folder that contains the log file backups Configure the frequency of backups and shipping No automatic failover Allows you to replicate data to several databases (one to many) Recommended to use Log Marking to keep databases in sync Log Shipping At A Glance SQL Agent on primary server backs up transaction log to primary share Each action is governed by a separate SQL job and can be controlled and scheduled independently SQL Agent on secondary server copies the transaction log its own local share SQL Agent on secondary server restores transaction log to the local database Clustering Versus Mirroring Versus Log Shipping Failover Clustering Mirroring Log Shipping The secondary node takes over immediately (hot) Mirror takes over immediately upon failure (with witness) Else run a single SQL statement to failover. Failover requires hands on to ensure last log is recovered. Failure is automatically detectedFailure detected automatically (if using a witness) No failure detection Does not protect against failed storageProtects against failed storage All databases protectedOnly mirrored DBs are protected Only log shipped DBs are protected. Transactionally consistentTransactionally consistent (sync) Potential for loss (async) Potential for loss Transactionally concurrentTransactionally concurrent (sync) May not be concurrent (async) At least 1 minute behind Limited distance (Win 2003)Limited distance (sync) Unlimited distance (async) Unlimited distance Short time to recovery (seconds/minutes) Longer time to recover due to steps involved. Putting It All Together What is your RTO/RPO? What does your EPM/SharePoint environment look like? What scenarios concern you? What Is Your RTO/RPO? RTO (Recovery Time Objective) = How long can my app be down before the business falls apart? RPO (Recovery Point Objective) = How much data loss can be tolerated before the business falls apart? RTO and RPO are the most important factors to your overall DR strategy! RTO and RPO affect As RTO/RPO Decrease Costs/Complexity Rise The strategies you deploy The technologies you choose The simplicity of your solution The location of your environments What Scenarios Concern You? Hardware Failures? Infrastructure Problems? Application Problems? Facilities/Power Failures? Local or Regional Disasters? Restoring a Farm Part 2 Summary Content Recovery Backup/Restore Administrative backup Settings backup Recycle Bin Versioning Disaster Recovery SharePoint Backup/Restore SQL-Only DPM rd Party Tools Database Mirroring Log-Shipping SQL Clustering International Content & CommunityResources for IT ProfessionalsResources for DevelopersMicrosoft Certification & Training Resources Resources Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings from Tech-Ed website. These will only be available after the event. Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings from Tech-Ed website. These will only be available after the event. Tech Ed Africa 2009 sessions will be made available for download the week after the event from: Related Resources (1/3) Office 2007 Technet Plan for data protection and recoveryf16c-4637-a6ae-4548bbed459b1033.mspxf16c-4637-a6ae-4548bbed459b1033.mspx Office Project Server 2007 Operations1f bf30-e79ad0debeec1033.mspx1f bf30-e79ad0debeec1033.mspx Office Project Server 2007 Resource kit3D253C E4-B87E-0861D1977BB7&displaylang=en3D253C E4-B87E-0861D1977BB7&displaylang=en Related Resources (2/3) Data protection and recovery for Office SharePoint Server in small to medium deployments0x4090x409 SharePoint and Mirroringx409x409 How to automate the deletion of backups in SharePoint Server 2007 and in Windows SharePoint Services 3.0 by using a Visual Basic script Related Resources (3/3) SQL Server 2005 High Availabilityus/library/ms aspxus/library/ms aspx SQL Server 2005 Mirror Best Practices005/technologies/dbm_best_pract.mspx005/technologies/dbm_best_pract.mspx Blogs Codeplex Upcoming Conferences Required Slide Complete a session evaluation and enter to win! 10 pairs of MP3 sunglasses to be won 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Required Slide