Enterprise Backup for SharePoint ® 2007 MOSS 2007 Backup Pros & Cons, Evaluation Standards & Strategies Speak

1. SharePoint User Group November 15, 2007 Enterprise Backup for SharePoint® 2007 MOSS 2007 Backup Pros & Cons, Evaluation Standards & Strategies Speakers: Don LaMure Michael LeComte

2. Introduction Hardware Failure Data Center Destruction Viruses, Worms, and Malicious Code Human Actions Data corruption Why backup SharePoint data? Business Requirements • Backup & Restore needs to be robust • Critical files need to be restored ASAP • Production systems need true 24x7 support • History, security, and template information needs to be maintained Introduction | Planning | Native Tools | Other Backup Strategies | Recommendations

3. Introduction Business critical application Distributed architecture Storage of content (documents and metadata) in single, locked down SQL database (SharePoint Content DBs) Use as a document repository, knowledge management system, and collaboration tool makes metadata critical, and may have compliance implications What make SharePoint different, from a backup perspective? Introduction | Planning | Native Tools | Other Backup Strategies | Recommendations

4. Introduction SharePoint Technology Stack

5. Planning Your Backup Strategy What are the SLAs I need to meet? • Restore: Downtime tolerance or RTO • Backup: Data loss tolerance or RPO What questions do you need to ask when planning your backup strategy? Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

6. Planning Your Backup Strategy How much storage do I have? How much of it can I devote to backup? • If one site needs to be backed up daily, am I willing to backup the entire content DB daily? • How many backup cycles can I keep? On what type of storage? What questions do you need to ask when planning your backup strategy? Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

7. Planning Your Backup Strategy What compliance implications do I need to be aware of? • If metadata (author, time, etc.) changes on restore, have I “falsified records”? • If I can’t recover a single document, have I “destroyed data”? What questions do you need to ask when planning your backup strategy? Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

8. Planning Your Backup Strategy What questions do you need to ask when planning your backup strategy? Who will I be relying on to do the backups? • Will it be the SharePoint admin or the storage admin? • Does the storage admin understand the business needs? Can they meet them? • Will it be a manual or automatic process? • Am I willing to use scripting, if only 1 or 2 people understand the script? Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

9. Planning Your Backup Strategy What questions do you need to ask when planning your backup strategy? How will my SharePoint backup strategy fit in to my other strategies? • Am I taking advantage of investments in tiered storage? • Is my backup part of my overall SharePoint solutions tool set? • Should my SharePoint backup strategy integrate in with my enterprise backup strategy? The answers to these question will determine what backup tools you should use. Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

10. MOSS 2007 Native Backup Tools

11. MOSS 2007 Native Backup & Restore Recycle Bin Versioning Central Administration Backup & Restore Command Line: stsadm Built-in “Data Protection” Tools Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

12. MOSS 2007 Native Backup & Restore 2-stage “real-time undelete” recycle bin strategy Recycle Bin Enable/Disable by Web Application Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

13. MOSS 2007 Native Backup & Restore First Stage Recycle Bin Second Stage Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

14. MOSS 2007 Native Backup & Restore Recycle Bin Cons: • Limited Granularity during restore – restores entire document library, folder, or file, depending on the delete action • No protection against data corruption • No coverage above folder level Pros: • Real-Time Undeletes • Can be selectively enabled/disabled Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

15. MOSS 2007 Native Backup & Restore Versioning Cons: • Uses up a great deal of storage • Adds complexity to other backup strategies Pros: • Useful for retrieving older version of documents • Keeps history of changes to documents • Can be selectively enabled/disabled Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

16. DEMO

17. MOSS 2007 Native Backup & Restore Is the Recycle Bin enabled? Is versioning enabled? Have I planned for the extra storage? Am I relying on these tools for backup? Be aware of the limitations of these two tools These tools will relieve some end-user restore requests, but they are NOT a backup solution Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

18. MOSS 2007 Native Backup & Restore Native GUI tool for data backup Central Administration Backup Backup down to Content DB level Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

19. MOSS 2007 Native Backup & Restore Control over Backup Location and Types of Backup Control over Backup Location and Types of Backup Central Administration Backup Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

20. MOSS 2007 Native Backup & Restore 4-step restore process: Central Administration Backup Select content to be restored: Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

21. MOSS 2007 Native Backup & Restore Restore Options: Overwrite or Create New Central Administration Backup Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

22. MOSS 2007 Native Backup & Restore Central Administration Backup Cons: • Limited Granularity – Can’t specify site, subsite, or folders • No scheduling options • No incremental backups • Difficult to debug any errors • Resource intensive and sites will be down or look different during certain operations Pros: • GUI tool to perform backup • Full & Differential Backups • Control over location of backup data Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

23. MOSS 2007 Native Backup & Restore Command Line Backup: smigrate Command Line “Backup”: Stsadm –import Stsadm –export Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

24. MOSS 2007 Native Backup & Restore Command Line Backup Cons: • Not full fidelity backup, will lose some customization and security settings when migrating contents • stsadmmust be executed locally on server by administrators with proper permissions Pros: • Command line migration utility, can be used to migrate a copy of a site and hence back it up Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

25. MOSS 2007 Native Backup & Restore Often fails for sites over 10 GB Often fails for highly customized sites Debugging is extremely difficult Extremely resource intensive, Microsoft does not recommend running it during production hours or using it for backup Can be scripted, but how many people know how to debug the scripts? Issues with stsadm Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

26. Other Backup Strategies SQL Backups Cons: • No granularity on backup, entire database needs to be backed up at highest frequency required to meet SLA • No granularity on restore • Only backs up the DB, what about other SharePoint components? • Restore can be a long process Pros: • Familiar backup operation • Backs up entire content databases Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

27. Other Backup Strategies Restoration of individual items or content • Entire DB needs to be restored to offline environment • Content to be restored must be manually copied to production database • Metadata will be altered or lost • Process often requires storage admin involvement and takes a long time Disaster Recovery of entire SharePoint environment • Does not handle components above database level –you will need to install SharePoint, set up web applications, re-attach all content databases, set web application settings, configure alternate URLs, policies, security, etc. • Will this meet your SLAs? SQL Backups – what are you using the backups for? Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

28. Other Backup Strategies Standby Environment Pros: • Environment can be available immediately for DR • Can also be used to restore individual sites or items Cons: • Requires additional hardware or resources • Need mechanism and procedures to keep them in synch • Cascading corruption or failures possible • Metadata will be altered or lost Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

29. Other Backup Strategies Is all of your SharePoint data of the same value to your business? Is it all being updated/modified at the same frequency? Is it acceptable to your business that metadata is lost during recovery? Do they meet your SLA? Are any of the above solutions good enough for your business? Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

30. Recommended Criteria and Methods

31. Backup Evaluation Standards Preserving Metadata Satisfying Compliance Policies Criteria #1: Full Fidelity of Original Data Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

32. Backup Evaluation Standards Supports item-, site- and site collection level backup and recovery Allows restore of any individual item, including documents (or version), list items, attachments, events, etc. Enables to restore of the entire environment quickly Criteria #2: Granularity of Backup and Recovery Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

33. Backup Evaluation Standards Scheduling options for administrators Backup frequencies vary with importance of business data Real-time backup during production hours Efficient use of storage investments Criteria #3: Flexibility of Schedules Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

34. Backup Evaluation Standards Business Importance of Data: Criticality Matrix Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

35. Backup Evaluation Standards Storage Differentiation Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

36. Backup Strategy Recommendations The tools covered may be enough for your SharePoint environment Make sure you know their limitations, and communicate them clearly to your users Robust third-party backup tools do exist Evaluate any third-party tool thoroughly against the standards presented in this presentation Yes, AvePoint does offer such tools Backup, High Availability, and Platform Recovery are all part of our DocAve platform, a modular suite of complete SharePoint back-end management software Recommendations Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

37. Planning Your Backup Strategy Available at: www.avepoint.com Where can you get more info on planning your backup strategy? Free Whitepaper: “Can Your SharePoint Backup Harm Your Business?” Evaluation Standards and Best Practices Introduction| Planning | Native Tools | Other Backup Strategies | Recommendations

38. DocAve 4.1 Enterprise Edition Backup Content Manager Archiver DocAve 4.1 Platform Disaster Recovery Migrator

39. DocAve 4.1 Enterprise Backup Multiple customizable backup plans and schedules Full, incremental, and differential backups Plans can be run during production hours Fast backup speeds: 60GBs / hr per plan, plans can be run simultaneously Tree mode, List mode, and a Smart Plan filter mode Compression and encryption options Granular backup with full-fidelity restore

40. DocAve 4.1 Enterprise Backup Complete Control Over Your Data Protection Strategies! • Item-, subsite-, site-level backup & full-fidelity restore • Full, incremental, and differential backups • Multiple customizable backup plans • Multiple schedules, plans can be run during production hours - NO index file lockups • Fast backup speeds: 60GBs /hr per plan at the item level

41. DocAve 4.1 DR High Availability Continuous replication of entire SharePoint environment , including data on index and SQL databases, to a stand-by environment Replication can be done either in real time or incrementally at either the SQL server, virtual server, or content database level Switch to stand-by environment immediately with a simple DNS switch 24x7 Replication for SharePoint Environment

42. DocAve 4.1 DR Platform Recovery Backs up entire SharePoint farm including all servers, databases with all configurations, and file systems Allows for quick restore of SQL, Index, Search, Job, and Front-End Servers Up-to-the-minute restore using SQL logs restoration A client should be installed on each server to provide complete disaster recovery solution Solution for Complete Farm: All-Server Restoration

43. Disaster Recovery | SharePoint Hierarchy Platform Recovery SharePoint • Web Application Content Database • Site Collection Sub-Site • Folder Level Item Level • Version/Attachment High Availability

44. DocAve 4.1 Archiver Archive inactive dataArchive everything from entire sites to specific documents, or specify by last time modified, version histories, attachments, and file type/size. Archiver will leave a stubSeamless access by end-users to view or retrieve archived content. Fully indexed and searchable via native SharePoint search. Preserves data integrityFull-fidelity item-level restore (un-archive), with full text keyword and identification criteria mask search. Technical Features

45. DocAve 4.1 Content Manager • Move live contents within the SharePoint environment Site to Site | Folder to Folder Server to Server | Farm to Farm • User-friendly two URL tree system browser-based GUI • All done in real time with no backups required – Live Move • Full-fidelity content managementMaintains all metadata, version histories and securities • Deploy contents from development or testing (stage) environments to the production environment Flexible Content Organization and Management

46. DocAve 4.1 SharePoint Migration • Granular Migration Sites | Sub-sites| Lists | Folders | Individual items • Full-fidelity MigrationMaintains all metadata, version histories and securities • Removes 2003 RestrictionsCreate a SharePoint 2007 Environment following best practices and according to your current business needs • Coexistence of 2003 and 2007 EnvironmentsContent can be migrated as needed according to your schedule Stress-free Content Migration to SharePoint 2007

47. SharePoint Administration DocAve 4.5

48. DocAve 4.5 Major Components AvePoint confidential and proprietary. This document may not be distributed in any form without the prior written consent from AvePoint, Inc.

49. DocAve 4.5 Administration Key Features SharePoint Management System • A fully integrated SharePoint Management platform based on established technology • Advanced multi-tiered architecture (4th generation) that is scalable, extensible, reliable, and secure • Efficient Management of SharePoint deployments of various sizes across geographical regions • Support for other vendors and technologies AvePoint confidential and proprietary. This document may not be distributed in any form without the prior written consent from AvePoint, Inc.

50. DocAve 4.5 Administration Key Features • Exclusive SharePoint EngineEfficient, granular, full fidelity access to SharePoint content at various levels through proprietary data engine. • Centralized InterfaceIntuitive SharePoint centric user interface that can control all of the modules (or just a subset based on user permission) • Classification of DataWith AvePoint’s SharePoint engine, modules can offer levels of services at much more granular level than just content DBs. Especially when combined with SMS’s flexible scheduling options. AvePoint confidential and proprietary. This document may not be distributed in any form without the prior written consent from AvePoint, Inc.