Enterprise Data Protection for SharePoint

Transcription

1 Enterprise Data Protection for SharePoint Saguenay (Sag) Baruss Senior TSP, AvePoint Canada ** ** This presentation was created and distributed independently of AvePoint. For additional information on AvePoint s products and services please visit

2 Section 1 Introduction Slide 2

3 Introduction Session Overview This is a 200-level session intended for SharePoint architects and technical leads, in particular the individuals responsible for: SharePoint backup and restore, SharePoint high availability, and Disaster recovery planning for SharePoint. Slide 3

4 Introduction Session Objectives To draw attention to the various components of an enterprise SharePoint implementation. To contrast the various data protection options available for SharePoint. To provide guidance on how to develop a complete and effective SharePoint data protection strategy. Slide 4

5 Introduction Agenda Introduction Data Protection in General Data Protection for SharePoint Supporting Large Quantities of Data High Availability for SharePoint Closing Thoughts 5 min 5 min 15 min 10 min 10 min 10 min Slide 5

6 Section 2 Data Protection in General Slide 6

7 Data Protection in General Terminology Service Level Agreement ( SLA ) An agreement between the business owner(s) of an application or service and the technical team responsible for providing that service. Data Protection: The process of ensuring application or service data is not lost in the event of a failure. High Availability: The process of ensuring the functionality provided by an application or service is not interrupted in the event of a failure. Slide 7

8 Data Protection in General Terminology (cont.) Recovery Point Objective ( RPO ): The point in time to which a system must be recovered in the event of a failure. Recovery Time Objective ( RTO ): The amount of time between the point of failure and restoration of service. System Recovery / Continuity Objectives: What objectives must be met following a failure in order for failover and / or system recovery to be considered successful. Slide 8

9 Data Protection in General Types of Failures Incremental data loss. Component failure. Application or service failure. Disaster. Slide 9

10 Data Protection in General Data Protection Strategies 1. Don t back it up. 2. Manual or end-user data protection. 3. Data capture. 4. Component capture. 5. System capture. Slide 10

11 Data Protection in General Data Protection Prerequisites A completed system architecture, including all dependencies. A completed Service Level Agreement which includes all items from the previous two slides. Business motivation. Sufficient resources. Slide 11

12 Presenter s Editorial What Makes SharePoint Data Protection so Difficult Slide 12

13 What Makes SharePoint Data Protection so Difficult On One Hand Nothing, it s not difficult. SharePoint is fundamentally the same as any other enterprise system. The same rules and guidance for data protection that apply to every other system also apply to SharePoint. Slide 13

14 What Makes SharePoint Data Protection so Difficult On the Other Hand SharePoint is a platform not an application. SharePoint implementations tends to include a large number of servers. SharePoint can be customized. SharePoint can be integrated with other applications or services. Slide 14

15 Section 3 Data Protection for SharePoint Slide 15

16 Data Protection for SharePoint Let s Build a SharePoint Farm Internal Users Users Web Internal Front End Servers WFEs Public-facing WFEs External User External App Server SharePoint Dedicated Server App Server SharePoint Databases Corporate Data SQL SQL Server Cluster BLOB Storage Slide 16

17 Data Protection for SharePoint Backing Up WFEs Components Requiring Backup: IIS. Customizations. Considerations: Multiple WFEs can be deployed in parallel. It is recommended to deploy identical WFEs. Only a small portion of the WFE needs to be backed up. Slide 17

18 Data Protection for SharePoint Backing Up Dedicated App Servers Components Requiring Backup: Configuration settings. Service-specific data. Considerations: Dedicated App servers often represent single points of failure. Slide 18

19 Data Protection for SharePoint Backing Up External App Servers Components Requiring Backup: Configuration settings. Service or application-specific data ( not stored within SharePoint ). Considerations: For services or applications storing data both in SharePoint and external to SharePoint, backup synchronicity needs to be considered. Slide 19

20 Data Protection for SharePoint Backing Up SQL Servers Components Requiring Backup: Configuration settings. Database and log files. External BLOBs. Considerations: SQL backups are SQL-specific, not application-specific. Watch out for externalized content. Slide 20

21 Data Protection for SharePoint Backing Up SharePoint Data Components Requiring Backup: Configuration databases Content databases Remote BLOBs Considerations: SharePoint data and SharePoint configuration are not the same thing. Slide 21

22 Data Protection for SharePoint An Holistic View of SharePoint Slide 22

23 Data Protection for SharePoint Native Data Protection SharePoint Recycle Bin: Protects against the controlled deletions of individual items. With SharePoint 2010 SP1, can also protect against the controlled deletion of sites. SharePoint Backup: Backs up farms, down to the content database level. Data Export / Import: SharePoint Designer and can be used to export and import sites. Slide 23

24 Data Protection for SharePoint Native Data Protection (cont.) SQL Database Backup: SQL can backup and restore SharePoint databases and associated configuration. Slide 24

25 Data Protection for SharePoint SharePoint Recycle Bin Slide 25

26 Data Protection for SharePoint SharePoint Backup Slide 26

27 Data Protection for SharePoint Data Export / Import Slide 267

28 Data Protection for SharePoint SQL Backup Slide 28

29 Data Protection for SharePoint External Data Protection Microsoft Data Protection Manager ( DPM ): Provides SharePoint-specific backup and restore. Does not provide a complete solution for SharePoint. Enterprise Backup Solutions: Can backup all components identified during previous slides. Uses the same backup method for SharePoint as for all other enterprise applications. SharePoint-Specific Data Protection: Provides advanced data protection for SharePoint only. Integrates with an existing enterprise backup solution for longterm retention of SharePoint backup data. Slide 29

30 Data Protection for SharePoint Selecting an Appropriate Solution The best data protection technology for a given situation depends on: Available data protection technologies, The parameters of the SLA, System size and complexity, and System criticality. Slide 30

31 Data Protection for SharePoint Recommendations 1. Understand the different components of SharePoint and how they tie together. 2. Know your SharePoint landscape. 3. Determine which components of SharePoint are most important to you. 4. Understand the limitations of your data protection technology. 5. Develop a phased backup and restore strategy. Slide 31

32 Section 4 Supporting Large Quantities of Data Slide 32

33 Supporting Large Quantities of Data How Large is Large? It depends on the organization. Key considerations are: Corporate data landscape. Data usage patterns. Underlying sub-systems. Legal and retention requirements. Informal Definition Your data is critical when you have to worry about it. Your quantity of data is large when you have to plan for it. Slide 33

34 Supporting Large Quantities of Data SharePoint Storage Scenarios Scenario Database Size 1 < 200 GB No fine print. Fine Print 2 < 4 TB Requires a certain level of performance from the disk sub-system. Subject to SharePoint boundaries and limits. 3 > 4 TB Must be an archive database using Document Center or Records Center site template. No alerts, workflows, link fix-ups or item-level security. Usage < 5% read and 1% write. Slide 34

35 Supporting Large Quantities of Data Recommendations 1. Embrace RBS. There is no way to take advantage of these increased storage limits without externalizing content. 2. Understand your data and data usage patterns. 3. Rethink ILM and data governance policies for large quantities of data. 4. Consider tiered SLAs. Slide 35

36 Supporting Large Quantities of Data Recommendations (cont.) 5. Configure backups based on business criticality of the data, not how it s stored. 6. Be prepared to invest in your storage sub-systems. Slide 36

37 Section 5 High Availability for SharePoint Slide 37

38 High Availability for SharePoint Preparing for SharePoint HA SharePoint HA is one component of a broader HA strategy. SharePoint HA is dependent on other services: Networking services, Active Directory, SAN fabric, and Perimeter security services. Remember, high availability is not about preventing failures, it s about mitigating risk. Slide 38

39 High Availability for SharePoint Virtual Machine-Based HA Warm-standby SAN-based HA solution leveraging SANbased replication to transport VM images between locations. In the event of a failure, VM s are restarted in the HA location as user sessions are redirected. Slide 39

40 High Availability for SharePoint GeoClustering-Based HA Warm-standby SAN-based HA solution leveraging SANbased replication of shared cluster resources. In the event of a failure, Windows clustering causes services to transition to the HA location as user sessions are redirected. Slide 40

41 High Availability for SharePoint Database-Based HA Warm-standby SQL-based HA solution leveraging SQL database mirroring or log shipping. In the event of a failure of the principle database, the mirror becomes the principle copy and user sessions are redirected. Slide 41

42 High Availability for SharePoint Replication-Based HA Hot-hot HA solution leveraging SharePoint interfarm replication. In the event of failure, user sessions are redirected to the alternate farm. Farm changes are managed through release management processes. Slide 42

43 High Availability for SharePoint Recommendations 1. Select a solution based on requirements. 2. Play to your organization s strengths. 3. Weigh the costs of each solution. 4. Look for opportunities to re-use your SharePoint HA technologies. 5. Favour simplicity. Slide 43

44 Section 6 Closing Thoughts Slide 44

45 Closing Thoughts Common Causes of Failure 1. Unclear requirements. 2. Mismatched expectations. 3. Incomplete backups / missed components. 4. Insufficient skills / experience. 5. Insufficient capacity. 6. Lack of governance. Slide 45

46 Closing Thoughts Data Protection Survival Kit 1. Corporate commitment to SharePoint. 2. Documented business expectations. 3. SharePoint usage patterns. 4. Corporate data landscape. 5. Service levels for each. 6. Corporate ILM strategy. 7. SharePoint governance strategy. Slide 46

47 Closing Thoughts Recommended Next Steps 1. Revisit your SharePoint documentation. 2. Reconsider your SharePoint data protection strategy. 3. Schedule a disaster recovery test. Slide 47

48 Closing Thoughts Resources SharePoint Data Protection: SharePoint Capacity Planning: SharePoint Content Database Sizing: DocAve SharePoint Community Sag Baruss Blog Slide 48

49 Closing Thoughts One Last Question Suppose a SharePoint user in your organization has overwritten several versions of his/her critical documents. The user now needs the missing versions, but can t lose their changes to the remaining versions. How long will it take you to recover the missing document versions? (a) 1 minute (d) 1 week (b) 1 hour (e) Not sure (c) 1 day Slide 49

50 Closing Thoughts Questions? Slide 50