Backup and Restore for Backup and Restore for SharePoint by pengxuezhi


     Backup and Restore for
P t ti Mission Critical SharePoint
Protecting Mi i C iti l Sh P i t
Data with New Tools and Technologies

             Michael Noel
       Convergent Computing
       Twitter: @MichaelTNoel
 Michael Noel
            gy            ;
• Technology book author; Over 15 titles translated into 20
  languages worldwide
• Partner at Convergent Computing ( – San
  F    i     U.S.A. based C
  Francisco, U S A b             lt t
                         d Consultants
• Specialties in SharePoint, Exchange, Security, and more…
Session Overview

• Understand SharePoint backup & recovery
  needs and considerations
• Look at Integrated backup options in
• Understand how DPM 2010 works
• View how DPM 2010 backs up and
  restores SharePoint content
• Compare and Contrast
SharePoint 2010 Backup

  Granular B k B ilt i
• G    l Backup Built-in
  ●   Export Site Collections, lists, sites
  ●   Recover from Unattached Content DB
• Farm Backup – Better Control and
SharePoint 2010 Integrated Backup

• Follow along in real time
SharePoint 2010 Integrated Backup

• While better still no:
  ●   Item-level recovery
  ●   Easy scheduling options
  ●   Management, monitoring
  ●   Tape backups
  Large di k requirements
• L     disk     i     t
Understanding How DPM
U d   t di H
       can Help

    Bridging h Gap
    B id i the G
 Data Protection Manager Overview

 Active Directory®
                                                                 O li S      h t
                                                                 Online Snapshots (up to 512)
 System State


                                Up to Every   15 minutes

           + Hyper-V                with integrated Disk & Tape                          based
         Windows XP
        Windows Vista

Windows Server 2003
+ Windows Server 2008
                                                                                   Offline tape
  file shares and directories
     How DPM Works

Understanding V l
U d                 Shadow
         di Volume Sh d
       Copy with DPM
DPM – Before Backup

  File 1

    Production Server   DPM Server
DPM – Take VSS Snapshot

  File 1

            File 1
    Production Server   DPM Server
DPM – First Backup

  File 1                                     File 1
                                        (Recovery Point 1)

                        Full Copy
            File 1
    Production Server               DPM Server
DPM – Delete Snapshot

  File 1                         File 1
                            (Recovery Point 1)

    Production Server   DPM Server
DPM – Second Backup

  File 1                                          File 1
                                              (Recovery Point

                        Changed Blocks
            File 1
    Production Server                    DPM Server
DPM – Create Shadow Copy

  File 1                         File 1
                            (Recovery Point 2)

                                         Shadow Copy
                                       (Recovery Point 1)

    Production Server   DPM Server
 How DPM W k f
 H       Works for

Understanding Sh P i
U d       di SharePoint
    specific DPM info
SharePoint – DPM’s View
                 IIS                 IIS                  IIS

                WFE.1               WFE.2               WFE.3

                          SQL                  Searc

                        Config DB              Index

  SQL         SQL          SQL                SQL           SQL        SQL

Content.1   Content.2   Content.3           Content.X    Content.Y   Content.Z
 Protection using DPM
                IIS                  IIS                 IIS

                WFE.1               WFE.2               WFE.3

                        Search                 SQL

                         I d
                         Index               ConfigDB
                                             C fi DB
  SQL         SQL         SQL                 SQL          SQL         SQL

Content.1   Content.2   Content.3           Content.X    Content.Y   Content.Z

 • DPM automatically re-configures
   itself based on SharePoint
   topology & configuration changes
SharePoint - Backup

• DPM Protects:
  ●   MOSS 2007 and MOSS 2010 farm content.
  ●   WSS 3.0 and MOSS 2007 Search
  ●                     g y                 p
      Web Servers – Using System State backup /
• No backup overhead to support ILR
• Supports SQL Clustering/Mirroring
  ●   Backup seamlessly on failovers and failbacks
• Optimized for large farms
SharePoint - Recovery
• Recover data at multiple levels
   ●   Complete F
       C      l t Farm
   ●   Individual content database
   ●   Site collections and sites
   ●   Documents and lists.
   ●   MOSS 2007/WSS 3.0 Search
• Retains the metadata/security settings
• Search for a site/document through all recovery
  points on disk and tape
                       front end
• Restore state of the front-end web
  server/backend SQL machine
 Backup Comparison
Features / Functionality           DPM2010   MOSS2010 Native Backup
Backup Scheduling                    Yes               No
Manageability/Reporting              Yes               No
Integration with SCOM
Integration with SCOM                Yes
                                     Yes               No
Block‐level Backup                   Yes            LIMITED+
Fast Backup Speeds                   Yes               No
Impact on SharePoint Performance     Low              High
Storage Required                     Low              High
Tape backups 
Tape backups                         Yes               No
Encryption on tape (Free)            Yes               No
Backup Dataset pruning               Yes               No
Farm‐level Backup                    Yes               Yes
Granular Backup                       No               Yes
O14 SharePoint Search backup
O14 SharePoint Search backup         No*
                                     No*               Yes 
Restore Comparison
Features / Functionality      Microsoft  MOSS2010 
                              DPM2010 Native Backup
Farm‐level Restore               Yes       Yes
Content Database Restore         Yes       Yes
Granular Restore                 Yes       Yes
Restore Process               Automated   Manual
Search for Content (across       Yes       No
Recovery Points)
Recovery Farm for Granular       No         No
Restore Metadata                 Yes        Yes
Restore Permissions              Yes        Yes
Early Scale Numbers …

    Parameter                 Value
    Farm Size                 5 TB
    Number f
    N b of SQL Nodes N d      5
    Daily churn               5%
    Initial Copy Time taken   13 hours
    Daily Full Time taken     1.5
                              1 5 hour
Example (for storage needs)

• Farm Size = 1 TB
• Daily churn of blocks = 5%
• Retention Range = 28 days (4 weeks)
SharePoint Native Backup
• Schedule:
    ●   Weekly Full
        W kl F ll
    ●   Daily Differential

7 days = Full + D1 + D2 + D3 + … +D6

Full = 1 TB
D1 = 0.05 * 1 = 50 GB
D2 = 0 05 * 1 * 2 = 100 GB

D6 = 0.05 * 1 * 6 = 300 GB

Total (7 days) = 1 TB + 50 GB + 100 GB + … + 300 GB
                 = 2.5 TB
Total (28 days) = 4 * 2.5 = 10 TB
DPM Backup
• Daily Full

     y              py       (Daily churn)
28 days = Initial Copy + 27* (    y      )

Initial Copy = 1 TB
Daily churn = 0.05 * 1 = 50 GB

Total (28 days) = 1 TB + 27 * 50 GB      = 2.35 TB

Space Saving = 10 – 2.35 = 7.65 TB !!!
   ect e Compression      65
Effective Co p ess o = 76.5 %
    DPM Secondary Backup
    (multi layers of protection)
     Active Directory®
     System State
     System State

                                                    Primary DPM

                  + Hyper-V
      Windows XP
      Windows Vista
     Windows Server 2003
     + Windows Server 2008
        file shares and directories
                                                    Secondary DPM

•   Secondary DPM takes over when primary is down
•   Directly recover f
    Di    l               Secondary DPM
                     from S    d
•   Take tape backups on Primary or Secondary DPM
DPM 2010 – Key Enhancements
• More reliable backups:
  ●   Seamlessly handles key configuration changes
       • New DB addition, DB move etc
  ●   Partial backups - Ski offline d b
      P i lb k          Skip ffli databases
  ●   Automatically re-run failed jobs
  ●   Automatically heal the backups
• Meet SLAs of larger deployments:
  ●   Significantly shortened backup time
  ●   Smarts to optimize disk throughput while backing up
      multiple DBs in parallel
• Bare Metal Recovery of servers
Scenario 1 – Some DB backups failed

• Continue backups of other DBs
  ●                   y point with successful DBs
      Create a recovery p
• Immediately after – retry the failed
  ●   Create a recovery point with these DBs
Scenario 2 – Backup becomes
• As soon as inconsistency is detected
  during backup:
  ●   Other DBs in the farm continue getting backed
      up normally
  ●   DPM triggers an auto-consistency check
  ●               backup
      After every backup, DPM tries to make invalid
      backups consistent again
Scenario 3 – Password Change
                                          p job
• When Found: Detects this on next backup j
• Impact: Cannot get latest farm topology details
• Behavior: Continues backup of already known DBs
• Resolution: SharePoint admin needs to run
  ConfigureSharePoint utility

• Impact of not running ConfigureSharePoint exe:
  ●   Cataloging fails -> ILR not available
  ●              g      g                        y
      Farm config change not handled automatically
  ●   Full farm recovery of these RPs –> Recover each DB
Scenario 4 – New DB added
• When found: At next backup DPM detects
  new DB
  Impact: C ti
• I                 to b k
       t Continues t backup remainingi i
• Resolutoin: Auto protection triggers:
  ●   Adds new DB(s) to the farm configuration
  ●   Backup the new DBs automatically!
• Subsequent backups take complete farm
Scenario 5 – Removing DBs
• When found: On next backup job, DPM unable
  to get information about the deleted DB
• Impact:
  ●   Raises alert
  ●   Continues following backups with other DBs
• Resolution: If DB added back to SharePoint
  ●   Detects in the next backup
  ●   Backs up the DB with other DBs
  ●   Resolves the alert
• Expects backup admin to manually delete DB
  from configuration
Scenario 6 – Moving a DB
• Impact & Resolution:
  ●   Combination of Add and Delete DB
Scenario 7 – More backups
• DPM 2007:
  ●   Cataloging integrated with backup (same job)
  ●   More than 50% time taken by cataloging!
• With DPM 2010:
  ●   Cataloging runs only once in a day
  ●   Does not bl k th completion & status of
      D       t block the     l ti      t t f
• Result: Faster, frequent & more successful
 Scenario 8 – DPM disk full
• Backup job is running and disk usage threshold
  (90% used) reached -> Alert raised
  Immediately after completion of current b k
  I   di l f            l i     f         backup,
  DPM tries to auto-grow* the volume
  Subsequent backups continue

  *Assumption – New disks are available in the
  DPM pool
Scenario 9 – Granular Recovery

                     ith t
• Granular Recovery without         a
 recovery farm!:
  ●   Attaches content DB to any SQL instance
  ●   Exports the item to a temporary location
  ●   Imports the item in the production farm
  ●   Import/Export uses uncompressed mode
  ●   SharePoint level import/export failures
Microsoft IT ‘Dogfood’ of DPM 2010

                            DPM 2010 Beta

   SQL        SQL Cluster

• Farm size ~ 4.5 TB.
Data Protection Needs
DPM as the SharePoint backup & recovery
Application   Uses application specific VSS writer.
  Aware       Automatic handling of HA configuration failovers.

               Uses snapshots - very little load on production server.
 Efficient      aste bac ups
               Faster backups.
               Low on storage.

               Backup at farm level, recover at granular level
 Flexible      Easy to configure and manage.
               Centralized reporting through SCOM.

   Cost        Single license to protect all data on a server.
 Effective     Single p
               S g point support.
Other workloads
• Laptop/Desktop protection
   ●   Seamless backups for roaming users (over VPN)
       S     l    b k       f      i        (
   ●   Integration with local Shadow Copies
• SQL Server
   ●   Backup at an instance level
   ●     pp
       Support for ~2000 DBs on the same SQL instance
   ●   End-user recovery of SQL DBs
• Hyper-V
   ●   Item Level Recovery from host level backup VHD
   ●   Support for Cluster Shared Volume (CSV)
   ●   Live Mi ti (Up to           d     ith      VMs)
       Li Migration (U t 8/16 nodes with 16/32 VM )
• Exchange
   ●   Support for Exchange 2010
Replica Volumes and Recovery Point
V l
• Replica volume required for each ‘unit’ that is
  being backed up
• Recovery Point volume also required for each
  ‘unit’, such as farm
• Plan for 3x-4x the amount of space in DPM as
  exists in SharePoint
• Replica volume must be as large as you think
  the content will grow (can be autogrown.)
• Recovery Point volume must be as the data
  churn multiplied by the time you keep the data
  on disk.
DPM Licensing
•   Check with local MS first!
•   DPM 2007 Licensing works as follows:
•   Standard Edition License – One license for each file
                       li ti
    server or non-application server.
•   Enterprise Edition License – One for each server that
    runs the following:
    • SharePoint (One front-end generally)
    • SQL (each cluster node requires a license)
    • Exchange (MB Servers)
    • DPM Console that is backed up by another DPM
•   Generally cost competitive…
•   Virtualization Licensing Options…

Taking a look at DPM 2007
Your Feedback is Important

Please fill out a session evaluation form and
  either put them in the basket near the exit
      or drop them off at the conference
                registration desk

                Thank you!
       Session Code: MSC22
      Michael Noel
   tte @ c ae      oe
Twitter: @MichaelTNoel

Session Code: MSC22

To top