SQL Server Disaster Recovery for Project Server


Published on

Mecanismos de recuperación de desastres de SQL Server aplicados a Project Server 2007.

Ing. Eduardo Castro Martinez, PhD
Microsoft SQL Server MVP

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SQL Server Disaster Recovery for Project Server

  1. 1. SQL Server DB for Project Server 2007 Disaster RecoveryEduardo CastroGrupo Asesor en Informáticahttp://www.grupoasesor.net<br />
  2. 2. Session Objectives And Takeaways<br />Session Objective(s): <br />Where is my EPM data stored ?<br />Discuss what are the options to backup any components of your SharePoint/EPM Farm<br />Session will not cover in details backup/restore plan and all high availability options<br />Learn how to recover your data<br />Learn how to recover from a catastrophic failure on your EPM Farm<br />
  3. 3. Backup/Restore<br />Content Recovery<br />Backup And Restore Types<br />Disaster Recovery<br />Farm or Database Restore<br />Hardware Failure or Disaster<br />Hardware Migration or Replacement<br />Minimize Downtime<br />Large Amounts<br />of Data<br />Redundancy<br />Additional Hardware<br />End user driven<br />Accidental update or deletion<br />Frequent and small-scale<br />
  4. 4. Content Recovery Solutions<br />EPM Administrative backup<br />EPM Settings backup<br />Recycle Bin<br />Versioning<br />
  5. 5. EPM Components<br />
  6. 6. EPM Content (Where Is My Data)<br />EPM Data (4 Databases)<br />Project<br />Enterprise Resource<br />Enterprise Custom Fields<br />Enterprise Global<br />(…)<br />EPM Data in SharePoint (Content DB)<br />Documents<br />Risks<br />Issues<br />Deliverables<br />
  7. 7. EPM Data<br />EPM Administrative Backup/Restore<br />Use of the Project_Archive Database<br />Define the retention level (versions)<br />Driven by EPM functional administrator<br />Can be scheduled<br />Define the retention level (policy)<br />“Oops I have deleted my project!”<br />
  8. 8. EPM Data<br />Pros<br />Consistent Data<br />No IT involvement<br />You can use API to give more flexibility<br />Cons<br />All data is saved<br />Not a backup or high availability solution<br />Beware of space, depending on number of versions kept<br />
  9. 9. EPM Administrative Backup<br />demo<br />
  10. 10. EPM 2007 Resource Kit <br />Released !!<br />
  11. 11. EPM 2007 Resource Kit tools<br />Portfolio Analyzer Views Migration<br />Project Server Settings Backup and Restore (Playbooks)<br />Project Server Data Populator<br />Project Workspace Site Relinker<br />View Effective Rights<br />
  12. 12. EPM Settings<br />Backup/Restore Project Server 2007 Settings<br />For example to move a configuration from/to differentenvironments<br />Development/Integration/Production<br />New tool in EPM 2007 Resource kit<br />PlayBooks<br />“How do I copy Project Server 2007 settings <br />from development to production ?” <br />
  13. 13. Playbooks<br />
  14. 14. EPM Settings<br />Pros<br />No need to transfer the EPM data<br />Clean way to work with several environments<br />Backup your settings and keep history<br />Cons<br />Not a backup or high availability solution<br />
  15. 15. EPM Data In SharePoint<br />SharePoint lists<br />Issues, Risks, Deliverables<br />Documents<br />Recover Content<br />SharePoint Recycle bin<br />Versions<br />
  16. 16. Recycle Bin<br />“I just deleted my deck and my presentation is in an hour!”<br />End User Driven<br />Supports Lists, Document Libraries, Folders, Documents, and List Items<br />Two Stages<br />End User<br />Site Collection Administrator<br />Site Collection Level<br />
  17. 17. Versioning<br />Pros<br />Supports both List Item and Document versioning<br />End users can retrieve earlier versions<br />Cons<br />Versions count towards site quota<br />Functionality needs to be enabled per List/Document Library (Disabled by Default)<br />Does not support Folders, Webs and/or Sites<br />“I made some changes but now I want to go back to a previous version!”<br />
  18. 18. Backup/Restore<br />Content Recovery<br />Backup And Restore Types<br />Disaster Recovery<br />Farm or Database Restore<br />Hardware Failure or Disaster<br />Hardware Migration or Replacement<br />Minimize Downtime<br />Large Amounts<br />of Data<br />Redundancy<br />Additional Hardware<br />End user errors<br />Accidental update or deletion<br />Frequent and small-scale<br />
  19. 19. Disaster RecoveryBackup and restore solutions<br />SharePoint Backup/Restore<br />SQL Server Backup and Restore<br />System Center DPM 2007 (Data Protection Manager)<br />Third-Party Solutions<br />Use when hardware fails, and as a last resort for service level agreement.<br />
  20. 20. “I have a small to medium deployment. Do you have anything for me out of the box?<br />SharePoint Backup/Restore<br />Yes!<br />Out of the box Backup/Restore UI and Command Line for Central Administrators<br />Wondering…<br />Our recommended solution for small-medium deployments<br />Database Size &lt; 200 GB<br />
  21. 21. SharePoint Backup/RestoreHow it works<br />Farm<br />Central Admin Console<br />File Server<br />SQL Backup/Restore<br />
  22. 22. SharePoint Backup/RestoreDetails<br />Out of the Box UI and command line access for Central Administrator<br />‘Hooks up’ SharePoint databases and search index on Restore<br />Supports Full and Differential backup<br />Backs up the search index (MOSS only)<br />Extensible framework for 3rd party applications<br />
  23. 23. SharePoint Backup/RestoreLimitations<br />Use the command line with Windows Task Scheduler for scheduled backups<br />Backs up content, SSP, EPM Databases and search index<br />You must manually backup front end files<br />We recommend you keep images of your web front ends<br />High restore time  Low availability<br />
  24. 24. Command line<br />%CommonProgramFiles%Microsoft SharedWeb Server Extensions12inStsadm –o backup <br />–directory HAREBackup <br />–backupmethod full <br />&gt; D:LOGSLog_backup.txt<br />
  25. 25. Configuring SharePoint Backup/Restore<br />demo<br />Part 1<br />
  26. 26. Full FarmRecoveryProcess<br />
  27. 27. Solution For Each Scenario<br />For Disaster Recovery<br />To create a backup farm<br />Use stsadm –o backup/restore<br />To migrate a site collection<br />Use stsadm –o backup http://server/site<br />To migrate a site/list/library/item<br />Use stsadm –o export/import for sites<br />Use Site Manager within Site collection<br />Project Server 2007 Resource kit tool<br />Project Workspace Site RelinkerRelinkAllWSSSites<br />
  28. 28. SQL-Only Backup/Restore<br />Pros<br />Reuse existing technology and processes<br />Non-application specific<br />Can be faster than SharePoint backup<br />Can back up to tape<br />Remember<br />Post-restore reattachment and clean up<br />Search index must be backed up separately via SharePoint backup for MOSS<br />“My SQL servers are managed by a separate organization or data center from my SharePoint installations.”<br />
  29. 29. System Center DPM(Data Protection Manager)<br />Content database &gt; 100 GB<br />Site Collection largerthan 12 GB<br />Webcast<br />http://blogs.technet.com/dpm/archive/2008/01/10/how-to-protect-sharepoint-with-dpm2007-new-streaming-video.aspx<br />
  30. 30. DPM 2007 and SharePoint 2007<br />DPM can be used to recover content items, sites, and farms. For more information, see: <br />How to Recover a Windows SharePoint Services Item (http://go.microsoft.com/fwlink/?LinkId=102815&clcid=0x409)<br />How to Recover a Windows SharePoint Services Site (http://go.microsoft.com/fwlink/?LinkId=102826&clcid=0x409)<br />How to Recover a Windows SharePoint Services Farm (http://go.microsoft.com/fwlink/?LinkId=102831&clcid=0x409)<br />
  31. 31. 3rd Party Backup Tools<br />What to look for in a 3rd party solution<br />Does it back up the Search Index?<br />Does it require post-restore manual work<br />SharePoint integration with VSS framework<br />Easier for 3rd parties to write custom backup/restore tools<br />Entire server (search index is included)<br />Only supports catastrophic overwrite scenario (not migration)<br />“I want to use a custom or 3rd party tool to backup/restore my farm! Does SharePoint support that?”<br />
  32. 32. Backup/Restore<br />Content Recovery<br />Backup And Restore Types<br />Disaster Recovery<br />Farm or Database Restore<br />Hardware Failure or Disaster<br />Hardware Migration or Replacement<br />Minimize Downtime<br />Large Amounts<br />of Data<br />Redundancy<br />Additional Hardware<br />End user errors<br />Accidental update or deletion<br />Frequent and small-scale<br />
  33. 33. High Availability And Disaster Recovery Solutions<br />Installation Scenarios<br />Web Front End Availability<br />Database Availability<br />Log Shipping<br />SQL Clustering<br />
  34. 34. Low AvailabilitySingle Server Scenario<br />One Server Configured as:<br /><ul><li>Web Front-End Server Role
  35. 35. Application Server Role
  36. 36. Database Server Role</li></ul>Appropriate for limited use-scenarios including the following<br />Installing Office Project Server 2007 for evaluation purposes<br />Deploying only Microsoft Windows SharePoint Services 3.0<br />Deploying Office Project Server 2007 for a limited purpose (such as for a single department) or for a limited number of users<br />
  37. 37. Web Servers<br />Clustered/Mirrored <br />SQL Server<br />Application Server<br />High AvailabilityMulti-server farm scenario<br />Optimizes performance of web servers<br />Increases redundancy and reduces points of failure<br />Redundancy at WFE and Database server roles<br />Determine configuration based on your business needs and goals<br />Determine config of other Application roles (PSI, Excel Services, Index, Forms, etc)<br />Multiple Application Servers don’t give you fault tolerance<br />You will need to remove any failed server from the farm – MOM can help you here<br />
  38. 38. SQL Failover Clustering<br />“If my SQL server blows up (hardware failure), how do I keep my EPM/SharePoint farm running?”<br />Unattended application availability: automatic failover capability without administrator intervention<br />Shared cluster name means no app awareness necessary<br />SharePoint Web Front Ends<br />Server Cluster<br />Heartbeat<br />Node B<br />Node A<br />Shared Disk Array<br />
  39. 39. Log-Shipping<br />Backup/Restore based technology that relies on transaction log files<br />Need to have a shared folder that contains the log file backups <br />Configure the frequency of backups and shipping<br />No automatic failover<br />Allows you to replicate data to several databases (one to many)<br />Recommended to use Log Marking to keep databases in sync<br />
  40. 40. Log Shipping At A Glance<br />Each action is governed by a separate SQLjob and can be controlled andscheduled independently<br />SQL Agent on primary server backs uptransaction log to primary share<br />SQL Agent on secondary server copies thetransaction log its own local share<br />SQL Agent on secondary server restorestransaction log to the local database<br />
  41. 41. Clustering Versus Mirroring Versus Log Shipping<br />
  42. 42. What about DB Mirroring?<br />Good News: DB Mirroringnumericlimitincreasedfrom 10 to 50*<br />(07/24/2008) http://technet.microsoft.com/en-us/library/cc262910.aspx<br />
  43. 43. Putting It All Together<br />What is your RTO/RPO?<br />What does your EPM/SharePoint environment look like?<br />What scenarios concern you?<br />
  44. 44. What Is Your RTO/RPO?<br />RTO (Recovery Time Objective) = How long can my app be down before the business falls apart?<br />RPO (Recovery Point Objective) = How much data loss can be tolerated before the business falls apart?<br />RTO and RPO are the most important factors to your overall DR strategy!<br />
  45. 45. RTO and RPO affect<br />The strategies you deploy<br />The technologies you choose<br />The simplicity of your solution<br />The location of your environments<br />
  46. 46. What Scenario’s Concern You?<br />Hardware Failures?<br />Infrastructure Problems?<br />Application Problems?<br />Facilities/Power Failures?<br />Local or Regional Disasters?<br />
  47. 47. Restoring A Farm<br />demo <br />Part 2<br />
  48. 48. Backup/Restore<br />Content Recovery<br />Summary<br />Disaster Recovery<br />Administrative backup<br />Settings backup<br />Recycle Bin<br />Versioning<br />SharePoint Backup/Restore<br />SQL-Only<br />DPM 2007<br />3rd Party Tools<br />Log-Shipping<br />SQL Clustering<br />Which combination of tools is right for your environment?<br />Once a DRP has been implemented it is IMPERATIVE to test it regularly !!!<br />
  49. 49. Related Resources (1/3)<br />Office 2007 Technethttp://technet.microsoft.com/en-us/office<br />Plan for data protection and recoveryhttp://technet2.microsoft.com/Office/en-us/library/9e69a470-f16c-4637-a6ae-4548bbed459b1033.mspx<br />Office Project Server 2007 Operationshttp://technet2.microsoft.com/Office/en-us/library/8aee655b-1f87-4729-bf30-e79ad0debeec1033.mspx<br />Office Project Server 2007 Resource kithttp://www.microsoft.com/downloads/details.aspx?FamilyId=A33D253C-6424-48E4-B87E-0861D1977BB7&displaylang=en<br />
  50. 50. Related Resources (2/3)<br />Data protection and recovery for Office SharePoint Server in small to medium deploymentshttp://go.microsoft.com/fwlink/?LinkId=102839&clcid=0x409<br />How to automate the deletion of backups in SharePoint Server 2007 and in Windows SharePoint Services 3.0 by using a Visual Basic scripthttp://support.microsoft.com/kb/941330<br />
  51. 51. Related Resources (3/3)<br />SQL Server 2005 High Availability http://msdn2.microsoft.com/en-us/library/ms190202.aspx<br />SQL Server 2005 Mirror Best Practices http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx<br />Blogs<br />http://blogs.msdn.com/chrisfie<br />http://blogs.msdn.com/shaden<br />http://blogs.msdn.com/brismith<br />http://blogs.msdn.com/project<br />Codeplex<br />http://www.codeplex.com<br />
  52. 52. © 2008 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.<br />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.<br />