www.quest.com-quest backup restore webcast with joel

8/14/2019 Www.quest.com-Quest Backup Restore WebCast With Joel

1/49


2/49

Who is Brent Ozar

SQL Server Expert for Quest Software Former DBA, SAN Admin, VMware Admin

Accidental Sharepoint Admin

Blog: www.BrentOzar.com

Twitter: @BrentO
http://www.brentozar.com/http://www.brentozar.com/


3/49

Who is SharePoint Joel?

8 year SharePoint Veteran First SharePoint Admin!

Sr. Technical ProductManager - SharePoint teamLaunch of SharePoint Server2007

Top IT SharePoint Blog

Blog: http://www.sharepointjoel.comTwitter: @joeloleson
http://www.sharepointjoel.com/http://www.sharepointjoel.com/


4/49

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 for Deck minus lolcats)


5/49

THE PROBLEM

Why is SharePoint Protection Difficult?


6/49

SharePoint and IKEA CAT have something in common

LOLCATS.COM


7/49

Why SharePoint Data Protection is Difficult

SharePoint is confusing Multiple servers with different roles

Different databases

Customizations

Configurations

Logical architecture doesnt translate into physical

components


8/49

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


9/49

Do you need to protect all of your farms, servers, services,customizations, and configurations?

What in Your SharePoint Environment NeedsProtection?

80

10

10

Backup Pie

Content

Configuration

Customization


10/49

SharePoint Components

Content Database(s) SSP Databases

Configuration Database **

Content (SQLServer Databases)

Master Pages, Page Layouts, CSS, etc Typically Stored in ContentDatabase

Web Parts, Site/List Definitions, Custom Features (Site Columns,

Content Types, Workflows, etc.) 3rd Party Solutions, Binaries, Registry Keys, etc. Changes to any files in 12 Hive (i.e. XML files)

Customizations

IIS Configurations (Application Pool, IIS Compression, Host Headers, SSLCertificates, etc.)

MOSS 2007 Configuration Settings

Web Application Names & Databases

Crawler Impact Rules

Configurations

Operating System Files (Windows Server) MOSS 2007 Binaries Service Packs/Hotfixes Language Packs

Binary Files


11/49

THE PLAN

Policy Driven Backup and Recovery


12/49

Creating a Backup/Recovery Solution

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 berestored?

Test and price potential solutions.

Mitigate issues. Choose and communicate solution.

Difficult but not impossible!


13/49

What needs to beprotected?

From whatscenarios?

How much data losscan be tolerated?

How quickly mustitems/environment

be restored?

Test and pricepotential solutions.

Mitigate issues.

Choose andcommunicate plan.


14/49

Protected From What Scenarios?

Scenario Likelihood

End user error 100%

Application/platform errors 100%

Hardware failures 100%

Infrastructure issues 10%

Facilities failures 1%

Regional disasters .09%


15/49

How SLA Affects Your Recovery Plan

Item LevelRecovery

DisasterRecovery

HighAvailability


16/49

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


17/49

RTO/RPO Very Important!

AsRTO/RPODecrease

Complexity & Cost

Increase

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 much data loss can betolerated?How quickly mustdata/environment be restored?


18/49

How the "Nines" Relate to Yearly Downtime

99.999%

99.99%

99.9%

99%

< 5 minutes

< 1 hour

9 hours

87 hours


19/49

BACKUP/RECOVERYSOLUTIONS AND STRATEGIES

Test & Price Potential Solutions


20/49

Protecting Content

For Content its all about the ContentDatabase!

Databases

Sites

Webs

Lists & Libraries

Documents,List items, &

Pages


21/49

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?


22/49

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.


23/49

Im planning on using SharePoints Native Backup

Restore, are there any considerations I should know?

SharePoint Native Backup/Restore

SharePoint Native Backup/Restore providesan out of the box base solution

SharePoints Native Backup/Restore is onlyrecommended for Small to Medium SizedDeployments


24/49

STSADM for Operations and Scripting

Tool for the right job To create a farm backup:

Use stsadmo backup -directory

To migrate a site collection:

Use stsadmo backup http://server/site (no directory)

To migrate a site:

Use stsadmo export/import for sites

To migrate a list:

Access or Excel or Third party tool

(watch creator/created date)
http://server/sitehttp://server/site


25/49

Characteristics of a Small to Medium-SizeDeployment (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 Webservers, one application server, and onecomputer or cluster running Microsoft SQLServer.)*

*Source: Whitepaper Data protection and recovery forOffice SharePoint Server in small to medium

deployments
http://technet2.microsoft.com/Office/en-us/library/288fecfb-53fb-4988-89d7-b7888f82bf961033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/288fecfb-53fb-4988-89d7-b7888f82bf961033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/288fecfb-53fb-4988-89d7-b7888f82bf961033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/288fecfb-53fb-4988-89d7-b7888f82bf961033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/288fecfb-53fb-4988-89d7-b7888f82bf961033.mspx?mfr=truehttp://technet2.microsoft.com/Office/en-us/library/288fecfb-53fb-4988-89d7-b7888f82bf961033.mspx?mfr=true


26/49

SharePoint 2007 Native Backup & Restore

Out of the Box User Interface via CentralAdministration

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 ApplicationLevel

The only way native way to backup/restore theSearch index


27/49

Microsoft Confidential

SharePoint 2007 Native Backup/RestoreHow it works

Config DB FileServer

Farm

Content DB

SSP DB

SearchIndex

Content DB

CentralAdmin UI

or Console

SQL Backup/Restore

Full Backup

Differential


28/49

SharePoint 2007 Native Backup/Restore

Whats 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 orWeb.config files Does not Backup IIS Settings/Configurations

Does not Backup Alternate Access Mappings (AAM)

Cannot Backup Directly to Tape (only to UNC)


29/49

SQL-Only Backup/Restore

Advantages & Benefits:

Existing SQL Server disaster recovery strategies canbe re-used

Can provider substantially faster Backup/Restore thanMOSS 2007s Native Backup/Restore

Can leverage 3rd party tools such as LiteSpeed forSQL Server to improve Backup/Restore Performance

Provides a full-fidelity data backup

My SQL servers are managed by a separate organization or datacenter from my SharePoint installations

I prefer SQL Server Backups for Performance and Availability


30/49

SQL-Only Backup/Restore

Considerations & Disadvantages: Does not Backup any WFE Configurations or Solutions

Requires Admin to Manually Reattach Content Databases tothe Web applications After a Recovery

Manually Backup / Restore all customizations on WFE Servers

(.Net Assemblies, Features, IIS Metabase, etc. batch file canhelp automate this process)

No need to Backup Search Database (As it cant be

synchronized with Search Index)

Recommend Backup/Restore of SSP separately via SharePointNative Backup & Restore


31/49

Why Backup/Restore is Not Highly Available orDR

Simply not fast enough

Rate of restore *content size = RTO

Example:

100MB/sec * 5TB > 14hours

Complicated recoveryprocedure

Prone to error

Some importantconfigurations will likelybe lost.


32/49

Failover SQL Mirroring 2 Farms


33/49

Mirroring Within Farm

< 1mslatency>LANspeed


34/49

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/restorefunctionality.

Caching/Synchronization Use a variety ofmethods to cache content to a remote store or

replicate content across sites/farms.


35/49

Quick Note on the Infrastructure Update

Infrastructure update includes some majorHA/DR improvements

Overall improvement in stability/perf (better storedprocs)

Faster patching reduces downtime. VSS Writer enhancements improve reliability.

Full crawls no longer necessary after DB attach:

Content DBs do not get assigned new GUIDs !!!!

Change log remains intact.

http://support.microsoft.com/kb/953750
http://support.microsoft.com/kb/953750http://support.microsoft.com/kb/953750


36/49

SharePoint Backup Strategy Summary

Ok for small environments A must for most Index requirements

Out of the Box

OK for content only/Not ok for Search/IndexNative SQL

Tried and True DR strategy, but dont forget thebackup part

SQL Log Shipping

Complex, but provides HA and Quicker Disaster

Recovery StrategySQL Mirroring

They each have their own issues (pros and cons)

Dont forget to backup the BOX!

Third Party BackupQuestLitespeed, Tivoli, Commvault,

AvePoint, DPM, etc..


37/49

TIPS AND TRICKS

Mitigating problems with backup/restore solutions


38/49


39/49

Use Solutions!

Roll up customizations as solutionpackages

Roll up as many customizations into a singlepackage as possible.

Solutions provide automatic deployment,simplified management, upgrade, and HA/DRefficiencies.

Store solutions offsite (and on standby farm) with

installation instructions. Build roll up packages on a regular basis.


40/49


41/49

44

Quest Solutions for SharePoint

Site Administrator for SharePointUnderstand, manage and secure your

SharePoint environment

Migration Manager for SharePointSharePoint 2003 to 2007 Migration

File Migrator for SharePointFile shares to SharePoint Migration

Recovery Manager for SharePointGranular SharePoint recovery for

enterprise-level needs

Quest Web PartsEnable rapid developmentof SharePoint applications

Quest SQL Server SolutionsMaximize SQL Server performancewhile simplifying tasks and providing

visibility and control

Public Folder Migrator for SharePointEfficient Exchange Public Folders to SharePoint Migration

Notes Migrator for SharePointReliable Notes application content migration to SharePoint


42/49

Provides granular and scalable recovery of anything in the backupof your SharePoint 2003 and 2007 content database


43/49


44/49

Quest SQL Server Solutions

Administration

Toad for SQLServer

Discovery

Wizard for SQLServer(freeware)

ChangeManagement

Change Directorfor SQL Server

Backup &Recovery

LiteSpeed forSQL Server

PerformanceManagement

CapacityManager forSQL Server

Spotlight onSQL ServerEnterprise

Quest SQL Server Productshttp://www.quest.com/sql-server
http://www.quest.com/sql-serverhttp://www.quest.com/sql-serverhttp://www.quest.com/sql-serverhttp://www.quest.com/sql-server


45/49

Summary

SharePoint Backup/Recovery is tricky, butnot impossible.

Traditional backup/restore is not HA or DR.

Different requirements sometimes requiredifferent solutions.

Most solutions have issues. Look around forinnovative fixes.

No one solutions meets all needs. Combinesolutions when necessary.


46/49

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!

Quest SharePoint tools discussion forums

Official Launch Feb 23!


47/49

Visit our SQL Server technical resource blog at:www.sqlserverpedia.com

Feel free to send your SQL Server related technical questions to:[email protected]

Visit our dedicated SQL Server communitysite at: http://sqlserver.quest.com

Check out our Backstage area with all of our collateral and

upcoming events including our Pain of the Week webcasts:

www.quest.com/backstage

www.quest.com/backstage/pow.aspx

SQL Resources
http://www.sqlserverpedia.com/mailto:[email protected]://sqlserver.quest.com/http://www.quest.com/backstagehttp://www.quest.com/backstage/pow.aspxhttp://www.quest.com/backstage/pow.aspxhttp://www.quest.com/backstagehttp://sqlserver.quest.com/mailto:[email protected]://www.sqlserverpedia.com/


48/49

Questions?

More information about all of Quests SharePoint solutions,

including Recovery Manager for SharePoint, is available at:

www.quest.com/sharepointmaster


49/49

Thank you for attending!

Please be sure to fill out your sessionevaluation!