Needs Work

SharePoint 2010 Mirroring and Log Shipping

According to this TechNet article updated July 29, 2010, All databases can be mirrored for high availability except:

• WebAnalyticsServiceApplication_StagingDB_
• User Profile Service Application_SyncDB_
• User Profile Service Application_SocialDB_
• FASTSearchAdminDatabase
• Reporting Services databases.

The only databases that can be logged shipped or use async mirroring:

• WSS_Content
• WSS_UsageApplication (not recommended)
• Secure_Store_Service_DB_
• All ProjectServer DBs if all db logs are synched
• DefaultPowerPivotServiceApplicationDB (SQL server only)

Another TechNet article also updated July 29, 2010 indicates that the following databases can also be log shipped:

• Application_Registry_server_DB_
• Managed Metadata Service_
• PerformancePoint Service Application_
• WebAnalyticsServiceApplication_StagingDB_
• WebAnalyticsServiceApplication_ReportingDB_
• User Profile Service Application_SocialDB_

Backup Components

The following components will be backed up:

• Content Databases
• Search Databases
• Index
• IIS data and Hive files
• Administrative (configuration) Databases
  

The following components will not be backed up:

• Query Databases (Index will hold master copy)
• SharePoint Logs (Log Aggregator will collect these)

Off-site backup and recovery

SnapMirror will replicate data between datacenters

Recovery Point Objectives (RPO)

4 hours

Recovery Time Objectives (RTO)

8 hours; The SnapManager must index all items which could take this long with millions of documens.