###BeginCaseStudy###
Topic 2, World Wide Importers
Background
General Background
Wide World Importers plans to upgrade from SharePoint 2010 to SharePoint 2013 to take advantage of
additional business intelligence (BI) services, including PerformancePoint Services, PowerPivot for Excel, and
SQL Server Reporting Services 2012 (SSRS). All users are members of an Active Directory Domain Services
(AD DS) domain.
Technical Background
The current environment integrates with a stand-alone instance of Microsoft SQL Server 2008 R2 Analysis
Services (SSAS). Wide World Importers has acquired SQL Server 2012 licenses for the purpose of upgrading
all the SQL Server instances to SQL Server 2012.
Business Requirements
The SharePoint 2013 environment and supporting back-end servers that run SQL Server must be highly
available and redundant in the case of unplanned downtime or a disaster.
Technical Environment
SharePoint 2013 Production Farm Topology
The SharePoint 2013 production farm topology consists of the servers listed in the following table.
The Wide World Importers SharePoint 2013 environment has the following characteristics:
A hardware load-balancer is configured to balance traffic between PROD- WEB-01 and PROD-WEB-02.
SSRS is installed on PROD-APP-01 in SharePoint integrated mode.
SSRS report databases are stored on PROD-DB-01.
A site collection named Report Center has been created at http://reports.wideworldimporters.com.
All SharePoint content and configuration databases are stored on PROD-DB-01.
All site collections have been migrated to a single content database named WSS_Content.
A content database named WSS_TempContent has been restored to PROD-DB-01, but not attached to the
SharePoint 2013 farm.
An AD DS domain user account named PPS_SVC has been created.
SharePoint 2013 Disaster Recovery Site
The SharePoint 2013 Disaster Recovery farm topology consists of the servers listed in the following table.
Technical RequirementsLog shipping must be used to send transaction log backups to the instance of SQL Server that is running in
the disaster recovery site.
Discrete sets of SharePoint content databases must be configured to automatically failover together.
An additional SQL Server 2012 Report Server must be added to the SharePoint 2013 environment. The
server must be configured to use SharePoint integrated mode.
Additional SQL Server 2012 Report Servers must not be installed on machines that are running SharePoint
as a front-end web server.
Site Collection administrators must not have the ability to upgrade site collections.
Site Collection upgrade jobs must be throttled to a maximum of five site collections at a time.
A daily backup schedule must be created to perform SQL Server backups of all SharePoint content and
configuration databases.
The PPS_SVC AD DS user account must be used for the PerformancePoint service application.
Farm administrators must be able to recover content from WSS_TempContent without attaching the
database to the farm. All content databases within the production farm must be set to read-only when
patching and upgrading the farm.
Farm administrators must be able to determine which sites were missed or skipped during the upgrade
process and must be able to monitor any future upgrades.
###EndCaseStudy###
You need to meet the disaster recovery requirements.
What should you do? (To answer, drag the appropriate terms to the correct location or locations in the answer
area. Each term may be used once, more than once, or not at all. You may need to drag the split bar between
panes or scroll to view content.)
Select and Place:
Answer: 
Explanation:
Scenario:
Log shipping must be used to send transaction log backups to the instance of SQL Server that is running in
the disaster recovery site.
A hardware load-balancer is configured to balance traffic between PROD-WEB-01 and PROD-WEB-02.
Both are running SQL Server 2012.
The SharePoint 2013 Disaster Recovery farm topology consists of the servers listed in the following table.
Log shipping must be used to send transaction log backups to the instance of SQL Server that is running in
the disaster recovery site.SQL Server Log shipping allows you to automatically send transaction log backups from a primary database
on a primary serverinstance to one or more secondary databases on separate secondary server instances. The
transaction log backups are applied to each of the secondary databases individually.
Terms and Definitions
Primary server – the instance of SQL Server that is your production server.
Primary database – the database on the primary server that you want to back up to another server. All
administration of the log shipping configuration through SQL Server Management Studio is performed from the
primary database.
Secondary server – the instance of SQL Server where you want to keep a warm standby copy of your primary
database.
Secondary database – the warm standby copy of the primary database. The secondary database may be in
either the RECOVERING state or the STANDBY state, which leaves the database available for limited readonly access.
