Your SlideShare is downloading. ×
SQL Server Disaster Recovery for Project Server
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

SQL Server Disaster Recovery for Project Server

1,770
views

Published on

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

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

Ing. Eduardo Castro Martinez, PhD
Microsoft SQL Server MVP
http://ecastrom.blogspot.com
http://comunidadwindows.org

Published in: Technology, Business

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,770
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SQL Server DB for Project Server 2007 Disaster RecoveryEduardo CastroGrupo Asesor en Informáticahttp://www.grupoasesor.net
  • 2. Session Objectives And Takeaways
    Session Objective(s):
    Where is my EPM data stored ?
    Discuss what are the options to backup any components of your SharePoint/EPM Farm
    Session will not cover in details 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
  • 3. Backup/Restore
    Content Recovery
    Backup And Restore Types
    Disaster Recovery
    Farm or Database Restore
    Hardware Failure or Disaster
    Hardware Migration or Replacement
    Minimize Downtime
    Large Amounts
    of Data
    Redundancy
    Additional Hardware
    End user driven
    Accidental update or deletion
    Frequent and small-scale
  • 4. Content Recovery Solutions
    EPM Administrative backup
    EPM Settings backup
    Recycle Bin
    Versioning
  • 5. EPM Components
  • 6. EPM Content (Where Is My Data)
    EPM Data (4 Databases)
    Project
    Enterprise Resource
    Enterprise Custom Fields
    Enterprise Global
    (…)
    EPM Data in SharePoint (Content DB)
    Documents
    Risks
    Issues
    Deliverables
  • 7. EPM Data
    EPM Administrative Backup/Restore
    Use of the Project_Archive Database
    Define the retention level (versions)
    Driven by EPM functional administrator
    Can be scheduled
    Define the retention level (policy)
    “Oops I have deleted my project!”
  • 8. EPM Data
    Pros
    Consistent Data
    No IT involvement
    You can use API to give more flexibility
    Cons
    All data is saved
    Not a backup or high availability solution
    Beware of space, depending on number of versions kept
  • 9. EPM Administrative Backup
    demo
  • 10. EPM 2007 Resource Kit
    Released !!
  • 11. EPM 2007 Resource Kit tools
    Portfolio Analyzer Views Migration
    Project Server Settings Backup and Restore (Playbooks)
    Project Server Data Populator
    Project Workspace Site Relinker
    View Effective Rights
  • 12. EPM Settings
    Backup/Restore Project Server 2007 Settings
    For example to move a configuration from/to differentenvironments
    Development/Integration/Production
    New tool in EPM 2007 Resource kit
    PlayBooks
    “How do I copy Project Server 2007 settings
    from development to production ?”
  • 13. Playbooks
  • 14. 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
  • 15. EPM Data In SharePoint
    SharePoint lists
    Issues, Risks, Deliverables
    Documents
    Recover Content
    SharePoint Recycle bin
    Versions
  • 16. Recycle Bin
    “I just deleted my deck and my presentation is in an hour!”
    End User Driven
    Supports Lists, Document Libraries, Folders, Documents, and List Items
    Two Stages
    End User
    Site Collection Administrator
    Site Collection Level
  • 17. Versioning
    Pros
    Supports both List Item and Document versioning
    End users can retrieve earlier versions
    Cons
    Versions count towards site quota
    Functionality needs to be enabled per List/Document Library (Disabled by Default)
    Does not support Folders, Webs and/or Sites
    “I made some changes but now I want to go back to a previous version!”
  • 18. Backup/Restore
    Content Recovery
    Backup And Restore Types
    Disaster Recovery
    Farm or Database Restore
    Hardware Failure or Disaster
    Hardware Migration or Replacement
    Minimize Downtime
    Large Amounts
    of Data
    Redundancy
    Additional Hardware
    End user errors
    Accidental update or deletion
    Frequent and small-scale
  • 19. Disaster RecoveryBackup and restore solutions
    SharePoint Backup/Restore
    SQL Server Backup and Restore
    System Center DPM 2007 (Data Protection Manager)
    Third-Party Solutions
    Use when hardware fails, and as a last resort for service level agreement.
  • 20. “I have a small to medium deployment. Do you have anything for me out of the box?
    SharePoint Backup/Restore
    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
  • 21. SharePoint Backup/RestoreHow it works
    Farm
    Central Admin Console
    File Server
    SQL Backup/Restore
  • 22. SharePoint Backup/RestoreDetails
    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
  • 23. SharePoint Backup/RestoreLimitations
    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
  • 24. Command line
    %CommonProgramFiles%Microsoft SharedWeb Server Extensions12inStsadm –o backup
    –directory HAREBackup
    –backupmethod full
    > D:LOGSLog_backup.txt
  • 25. Configuring SharePoint Backup/Restore
    demo
    Part 1
  • 26. Full FarmRecoveryProcess
  • 27. 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 backup http://server/site
    To 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 RelinkerRelinkAllWSSSites
  • 28. 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.”
  • 29. System Center DPM(Data Protection Manager)
    Content database > 100 GB
    Site Collection largerthan 12 GB
    Webcast
    http://blogs.technet.com/dpm/archive/2008/01/10/how-to-protect-sharepoint-with-dpm2007-new-streaming-video.aspx
  • 30. 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=0x409)
    How to Recover a Windows SharePoint Services Site (http://go.microsoft.com/fwlink/?LinkId=102826&clcid=0x409)
    How to Recover a Windows SharePoint Services Farm (http://go.microsoft.com/fwlink/?LinkId=102831&clcid=0x409)
  • 31. 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 3rd party tool to backup/restore my farm! Does SharePoint support that?”
  • 32. Backup/Restore
    Content Recovery
    Backup And Restore Types
    Disaster Recovery
    Farm or Database Restore
    Hardware Failure or Disaster
    Hardware Migration or Replacement
    Minimize Downtime
    Large Amounts
    of Data
    Redundancy
    Additional Hardware
    End user errors
    Accidental update or deletion
    Frequent and small-scale
  • 33. High Availability And Disaster Recovery Solutions
    Installation Scenarios
    Web Front End Availability
    Database Availability
    Log Shipping
    SQL Clustering
  • 34. Low AvailabilitySingle Server Scenario
    One Server Configured as:
    • Web Front-End Server Role
    • 35. Application Server Role
    • 36. 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
  • 37. Web Servers
    Clustered/Mirrored
    SQL Server
    Application Server
    High AvailabilityMulti-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 don’t give you fault tolerance
    You will need to remove any failed server from the farm – MOM can help you here
  • 38. SQL Failover Clustering
    “If my SQL server blows up (hardware failure), how do I keep my EPM/SharePoint farm running?”
    Unattended application availability: automatic failover capability without administrator intervention
    Shared cluster name means no app awareness necessary
    SharePoint Web Front Ends
    Server Cluster
    Heartbeat
    Node B
    Node A
    Shared Disk Array
  • 39. 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
  • 40. Log Shipping At A Glance
    Each action is governed by a separate SQLjob and can be controlled andscheduled independently
    SQL Agent on primary server backs uptransaction log to primary share
    SQL Agent on secondary server copies thetransaction log its own local share
    SQL Agent on secondary server restorestransaction log to the local database
  • 41. Clustering Versus Mirroring Versus Log Shipping
  • 42. What about DB Mirroring?
    Good News: DB Mirroringnumericlimitincreasedfrom 10 to 50*
    (07/24/2008) http://technet.microsoft.com/en-us/library/cc262910.aspx
  • 43. Putting It All Together
    What is your RTO/RPO?
    What does your EPM/SharePoint environment look like?
    What scenarios concern you?
  • 44. 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!
  • 45. RTO and RPO affect
    The strategies you deploy
    The technologies you choose
    The simplicity of your solution
    The location of your environments
  • 46. What Scenario’s Concern You?
    Hardware Failures?
    Infrastructure Problems?
    Application Problems?
    Facilities/Power Failures?
    Local or Regional Disasters?
  • 47. Restoring A Farm
    demo
    Part 2
  • 48. Backup/Restore
    Content Recovery
    Summary
    Disaster Recovery
    Administrative backup
    Settings backup
    Recycle Bin
    Versioning
    SharePoint Backup/Restore
    SQL-Only
    DPM 2007
    3rd Party Tools
    Log-Shipping
    SQL Clustering
    Which combination of tools is right for your environment?
    Once a DRP has been implemented it is IMPERATIVE to test it regularly !!!
  • 49. Related Resources (1/3)
    Office 2007 Technethttp://technet.microsoft.com/en-us/office
    Plan for data protection and recoveryhttp://technet2.microsoft.com/Office/en-us/library/9e69a470-f16c-4637-a6ae-4548bbed459b1033.mspx
    Office Project Server 2007 Operationshttp://technet2.microsoft.com/Office/en-us/library/8aee655b-1f87-4729-bf30-e79ad0debeec1033.mspx
    Office Project Server 2007 Resource kithttp://www.microsoft.com/downloads/details.aspx?FamilyId=A33D253C-6424-48E4-B87E-0861D1977BB7&displaylang=en
  • 50. Related Resources (2/3)
    Data protection and recovery for Office SharePoint Server in small to medium deploymentshttp://go.microsoft.com/fwlink/?LinkId=102839&clcid=0x409
    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
  • 51. Related Resources (3/3)
    SQL Server 2005 High Availability http://msdn2.microsoft.com/en-us/library/ms190202.aspx
    SQL Server 2005 Mirror Best Practices http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
    Blogs
    http://blogs.msdn.com/chrisfie
    http://blogs.msdn.com/shaden
    http://blogs.msdn.com/brismith
    http://blogs.msdn.com/project
    Codeplex
    http://www.codeplex.com
  • 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.
    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.

×