1. disaster recovery
   1. recovery point objective: amount of data to be recovered
   2. recovery time objective: amount of time it takes to be back online
2. Backup
   1. content stored in sites and site collections
   2. Central administration
   3. backup content databases using sql server management studio
   4. data protection manager
   5. granular backups
      1. central administration
         1. site collection backup
         2. export site or list
         3. recover data from unattached content database
      2. More read and process intensive than farm backup. (uses transact sql)
   6. sql snapshot
      1. when ms sql server enterprise ed is used
      2. ensure that data is consisten when backup or export is in progress
      3. sp uses snapshot to create backup package, deleted afterwards
   7. farm backup
      1. content and configuration databases
      2. considerations
         1. run off hours: avoid performance issues
         2. configuration and central admin db cannot restored using sp tools
         3. blob backup: use filestream remote blob provider (if other: backup manually
         4. trust relationships are not backuped
            1. reestablish trusts after restore
         5. sql server with tde (transparant data encryption): tde key is not restored / backuped automatically
         6. farm backup cannot be restored to other product versions
         7. downgrade and upgrade topologies are not possible
         8. destination farm must have the same topology
   8. configuration - service backups
      1. farm backup includes configuration - not possible to restore configuration alone
      2. considerations
         1. detach content db and perform config backup
         2. for farm configuration: can't use sql server tools or data protection manager
         3. meer lezen hierover!
         4. first time backup service application: use the full option (defines marker, so differential backups can be used)
      3. powershell
         1. configuration backup: Backup-SPconfigurationDatabase
         2. service appl backup: Backup-SPfarm ...
3. Protecting customizations
   1. custom dll, assemblies deployed by the global assembly cache (gac)
   2. xml files used to configure feature
   3. master pages, page layouts, css
   4. web parts, custom columns, new content types, workflows...
   5. third party solutions and associated binary files and registry keys, such as ifilters
   6. backup defined by type of customization
4. Restore
   1. member of farm admin group
   2. member of sharepoint_shell_access role (sql server; Add-SPShellAdmin cmdlet)
   3. member of wss_admin_wpg local group
   4. sql server account, timer service account, ca appl pool acount must have read permissions on the backup locations
   5. database sql server account must be member of sysadmin server role
   6. login account must have read permissions to backup locations
   7. sp foundaton administration service must be started on all servers (by default not started on standalone servers)
   8. search: if backup and restore complete service: no new crawl needed, else search not available during crawl (+ 15 min)
5. System center Data protection manager
   1. unified data protection for servers
   2. benefits
      1. no need for recovery farm
      2. automatic protection
      3. scheduling of the sp catalog job
   3. how
      1. after intial copy of data: express full backups
      2. only blocks that changed are send
   4. restore
      1. farm configuration and content can be restored (zie tabel eerder: staat dat configuratie niet kan gerestored)
      2. content database (single) can be restored)
      3. copy to network folder or tape