Tech Ed Africa Demystifying Backup Restore In Share Point 2007

Demystifying Backup and Restore for SharePoint
Joel Oleson
Sr. Analyst
@joeloleson
Quest Software
Session Code:

Who is SharePoint Joel?
8 year SharePoint Veteran…
First SharePoint Admin
Sr. Architect – SharePoint at Quest software
Top IT SharePoint Blog
Blog: http://www.sharepointjoel.com
Twitter: @joeloleson

Agenda
Understanding the problem
Defining requirements
Discuss backup & recovery solutions
Tips & Tricks – Addressing gaps in backup/restore
Summary and Q&A
(Compliments to Mike Watson)

The problem
Why is SharePoint Protection Difficult?

Why SharePoint Data Protection is Difficult
SharePoint is confusing
Multiple servers with different roles
Different databases
Customizations
Configurations
Logical architecture doesn’t translate into physical components

Why SharePoint Data Protection is Difficult
Competing goals require different solutions:
Item level recovery
Disaster Recovery
High Availability
Many solutions available. Not obvious what to use:
SharePoint Native Backup
SharePoint Designer
Recycle Bin
SQL backup
DPM
Third-party solutions

What in Your SharePoint Environment Needs Protection?
Do you need to protect all of your farms, servers, services, customizations, and configurations?

What do you need to backup
Your Databases
All Configuration and settings
Your Services (Index)
External Code and Dev assets

SharePoint Components

The plan
Policy Driven Backup and Recovery

Creating a Backup/Recovery Solution
Difficult but not impossible!
What needs to be protected from what scenarios?
How likely are those scenarios?
How much data loss can be tolerated?
How quickly must items/environment be restored?
Test and price potential solutions.
Mitigate issues.
Choose and communicate solution.

Protected From What Scenarios?

How SLA Affects Your Recovery Plan

Recycle Bin with 2 levels of recovery
End-user targeted with access from the site itself
Site Administrator (at the Site Collection) accessible at the second level
Turned on by default through Central Admin
Configured at the Web Application Level
The No Brainer…

RTO/RPO – Very Important!
How much data loss can be tolerated?
How quickly must data/environment be restored?
RTO/RPO affect:
The technologies you choose
The strategies you deploy
The simplicity/complexity of your solution
The location of your backups and environments

How the "Nines" Relate to Yearly Downtime

Backup/Recovery solutions
Test & Price Potential Solutions

Protecting Content
It’s nearly all about the Content Database!

Content Database Protection
Simple Problem – Difficult Solution
Endless options:
SharePoint native backup
SQL Native backup
With compression?
Simple or Full recovery model?
Full, Differential, Incremental backups?
Transaction log backups?
What to store and how long?
SQL log shipping, mirroring, replication?
DPM?
Third-Party backup and replication tools?

Content Database Recovery
Even more difficult!
SQL database recovery workflow
Confirm item
Confirm location
Track down database backup timeline
Recover backups (online or offline (tape))
Position backups (same server/farm, recovery farm)
Confirm backups are valid
Restore backups
Attach backups to SharePoint
Confirm item is available
Retrieve item and position for end user
Recover to original farm
Recover to a restore farm
Extract data from SQL.
Bring DR database online.

“I’m planning on using SharePoint’s Native Backup Restore, are there any considerations I should know?
SharePoint Native Backup/Restore
SharePoint Native Backup/Restore provides an out of the box base solution
SharePoint’s Native Backup/Restore is only recommended for Small to Medium Sized Deployments… 

STSADM for Operations and Scripting
Tool for the right job…
To create a farm backup:
Use stsadm –o backup -directory
To migrate a site collection:
Use stsadm –o backup http://server/site (no directory)
To migrate a site:
Use stsadm –o export/import for sites
To migrate a list:
Access or Excel or Third party tool
(watch creator/created date)

Characteristics of a Small to Medium-Size Deployment (Data Perspective)
Site Collections No Larger than 12-15 GB*
Content Databases No Larger than 100 GB*
Deployed in up to three tiers, on no more than five servers (one to three front-end Web servers, one application server, and one computer or cluster running Microsoft SQL Server.)*
*Source: Whitepaper “Data protection and recovery for Office SharePoint Server in small to medium deployments”

SharePoint 2007 Native Backup & Restore
Out of the Box User Interface via Central Administration
Command line access via STSADM tool
‘Hooks up’ SharePoint Databases and Search index on Restore
Supports Full and Differential Backups*
Easy to Use
Backup/Restore at Farm or Web Application Level
The only way native way to backup/restore the Search index

How Native SharePoint Backup Works
Farm
Central Admin UI or Console
File Server
SQL Backup/Restore

SharePoint 2007 Native Backup/Restore
What’s Missing???
Does not Provide Scheduling Functionality in SharePoint (Use Windows Task Scheduler)
Does not Backup any Configurations/Customizations to any files in the “12 Hive” or Web.config files
Does not Backup IIS Settings/Configurations
Does not Backup Alternate Access Mappings (AAM)
Cannot Backup Directly to Tape (only to UNC)

SQL-Only Backup/Restore
“My SQL servers are managed by a separate organization or data center from my SharePoint installations…”
“I prefer SQL Server Backups for Performance and Availability…”
Advantages & Benefits:
Existing SQL Server disaster recovery strategies can be re-used
Can provider substantially faster Backup/Restore than
MOSS 2007’s Native Backup/Restore
Can leverage 3rd party tools such as LiteSpeed for SQL Server to improve Backup/Restore Performance
Provides a full-fidelity data backup

SQL-Only Backup/Restore
Considerations & Disadvantages:
Does not Backup any WFE Configurations or Solutions
Requires Admin to Manually Reattach Content Databases to the Web applications After a Recovery
Manually Backup / Restore all customizations on WFE Servers (.Net Assemblies, Features, IIS Metabase, etc. – batch file can help automate this process)
No need to Backup Search Database (As it can’t be synchronized with Search Index)
Recommend Backup/Restore of SSP separately via SharePoint Native Backup & Restore

Why Backup/Restore is Not Highly Available or DR
Simply not fast enough
Rate of restore * content size = RTO
Example:
100MB/sec * 5TB > 14 hours
Complicated recovery procedure
Prone to error
Some important configurations will likely be lost.

Failover SQL Mirroring 2 Farms

Mirroring Within Farm
< 1ms latency
>LAN speed

Third Party Solutions
There are three main categories:
Storage Solutions – Replication of content on disk to another storage set or system.
Backup/Restore – Integrate with SQL, file system, or VSS to provide backup/restore functionality.
Caching/Synchronization – Use a variety of methods to cache content to a remote store or replicate content across sites/farms.

Quick Note on the Infrastructure Update
Infrastructure update includes some major HA/DR improvements
Overall improvement in stability/perf (better stored procs)
Faster patching reduces downtime.
VSS Writer enhancements improve reliability.
Full crawls no longer necessary after DB attach:
Content DB’s do not get assigned new GUID’s !!!!
Change log remains intact.
http://support.microsoft.com/kb/953750

Tips and tricks
Mitigating problems with backup/restore solutions

Improving Performance of Native Backup
Co locate the backup share with the largest backup components.
Ensure the index disk has good read performance. (100MB/sec or better)
Ensure the backup LUN has good write performance. (100MB/sec or better)
Ensure database LUN(s) have good read performance. (150MB/sec or better)
Ensure Gbps connectivity between remote components and backup share. (1Gbps or 100MB/sec)
Ensure all crawls (including anchor text) are stopped/paused.

Using A SQL Connection Alias with SharePoint
1. SharePoint configured to use SQL1 as default SQL server
2. Connection Alias defined: SQL1 = SQL1
3. Upon failover. Connection Alias updated: SQL1 = SQL2
SQL1
SQL2

Prevent Database Restores
Use granular protection solutions instead.
Recycle bin
List item versioning
Publishing (page versioning)
Quick Recovery Tool (like Quest)
Gaps exist.
No site or web recycle bin. Use the MSIT Site Delete capture tool http://www.codeplex.com/governance/Release/ProjectReleases.aspx?ReleaseId=14351
No centralized control over item and page versioning

Use Solutions!
Roll up customizations as solution packages
Roll up as many customizations into a single package as possible.
Solutions provide automatic deployment, simplified management, upgrade, and HA/DR efficiencies.
Store solutions offsite (and on standby farm) with installation instructions.
Build roll up packages on a regular basis.

DEMO: Quest Recovery Manager
Provides granular and scalable recovery of anything in the backup of your SharePoint 2003 and 2007 content database

SharePoint 2010 sneak Peak Video Demo – Backup/Recovery

Sneak Peak Video: SharePointFilter out noise 
video

SharePoint 2010 sneak Peak
Sneak Peak Videos: http://sharepoint.microsoft.com/2010/Sneak_Peek/

Summary
SharePoint Backup/Recovery is tricky, but not impossible.
Traditional backup/restore is not HA or DR.
Different requirements sometimes require different solutions.
Most solutions have issues. Look around for innovative fixes.
No one solutions meets all needs. Combine solutions when necessary.

SharePointForAll.com
Aggregation of Quest SharePoint Team Feeds
Unique IT Content
Migration
Disaster Recovery/Backup
Product Update Drilldown and Webcast Announcements
Beta access to new SharePoint tools and products!
DropThis
Reorg Wizard
AND MORE!!!
Quest SharePoint tools discussion forums

Watch Out for Killer Bunnies

Quest Solutions for SharePoint
Site Administrator for SharePoint Discover, understand and manage your SharePoint environment
Quest SQL Server Solutions
Maximize SQL Server performance while simplifying tasks and providing visibility and control
Quest Web Parts
Enable rapid development of SharePoint applications
Recovery Manager for SharePoint
Granular SharePoint recovery for enterprise-level needs
Migration Manager for SharePoint
SharePoint 2003 to 2007 migration
File Migrator for SharePoint
File shares to SharePoint migration
Public Folder Migrator for SharePoint
Exchange Public Folders to SharePoint migration
Notes Migrator for SharePoint
Notes application content to SharePoint migration
48

Required Slide
10 pairs of MP3 sunglasses to be won
Complete a session evaluation and enter to win!

Thank You!

Required Slide
© 2009 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.

Required Slide
Speakers,
TechEd 2009 is not producing
a DVD. Please announce that
attendees can access session
recordings from Tech-Ed website. These will only be available after the event.
Tech·Ed Africa 2009 sessions will be made available for download the week after the event from: www.tech-ed.co.za
www.microsoft.com/teched
International Content & Community
www.microsoft.com/learning
Microsoft Certification & Training Resources
http://microsoft.com/technet
Resources for IT Professionals
http://microsoft.com/msdn
Resources for Developers
Resources

Tech Ed Africa Demystifying Backup Restore In Share Point 2007

by Joel Oleson

Accessibility

Categories

Upload Details

Usage Rights

1 Embed 4

Statistics

Tech Ed Africa Demystifying Backup Restore In Share Point 2007 Presentation Transcript