NETWORKER 9 FOR

SHAREPOINT 2013 AND SQL

2012 AAG

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG

Table of Contents
Introduction.................................................................................................................................................. 4
Company Profile...............................................................................................................................................5

Solution ...........................................................................................................................................................6

Key Components........................................................................................................................................... 7
EMC Data Protection Suite................................................................................................................................8

Lab Overview .............................................................................................................................................. 14

Lab Overview .................................................................................................................................................15

Demo Environment Layout..............................................................................................................................17

Components & Credentials.............................................................................................................................19

SQL Server overview .................................................................................................................................. 21

Preparation Steps for SQL Server 2012 AAG Environment ...............................................................................22

NetWorker 9 backup and recovery of SQL Server ......................................................................................... 34

Backup of SQL 2012 Using NetWorker............................................................................................................35

Recovery of SQL 2012 DB in an Availability Group ..........................................................................................46

NetWorker 9 backup of SharePoint ............................................................................................................. 84

Overview of Lab Objectives ............................................................................................................................85

Perform a Full Backup ....................................................................................................................................86

Delete a Document from SharePoint Site ........................................................................................................95

Perform a Second Full Backup ........................................................................................................................99

Delete EMC Team 1 Database and log files ...................................................................................................104

NMM Configure Options Add SQL2012-01 from SP2013-01..........................................................................110

NetWorker 9 Recovery of SharePoint ......................................................................................................... 115

 Review the details of the SharePoint Backups ..............................................................................................116

Restoring the Content Database ...................................................................................................................119

Validate recovery and contents of the restored Share point Farm..................................................................126

Restoring a SharePoint Server 2013 document with GLR...............................................................................129

Conclusion ............................................................................................................................................... 150

Summary .....................................................................................................................................................151
 Introduction

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 4

Company Profile
Company Background

BIG Telco is a major Telco company in the United States with strong presences throughout the World. They also have
significant development shops in India and Bolivia. They are greatly diversified across communications infrastructure
as well as the newer Wireless Infrastructure around the United States and Canada. BIG Telco has also begun
establishing themselves in Hosting Facilities and has recently invested millions into a state of the art datacenter
located in the Middle East.

Business Challenge

BIG Telco has recently implemented a hosted SharePoint environment for it's clients. The challenge for BIG Telco has
been differentiating themselves as a hosted SharePoint provider and providing data protection capabilities along with
its hosted SharePoint services. Customer requirements for data retention increase along with increasing data growth.
BIG Telco is hoping to gain more market share and longer term customers by leveraging the EMC Data Protection Suite
and it's unique capabilities for protecting and recovering mission critical SharePoint data.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 5

Solution
EMC Data Protection Suite powered by EMC NetWorker

After evaluating several solutions to address the business challenge for robust and industry leading SharePoint Data
Protection. BIG Telco's IT team have selected EMC's Data Protection Suite, as their solution for enhancing and
differentiating there hosted SharePoint solution with data protection capabilties.

Here are the top 3 reasons why BIG Telco chose the EMC Data Protection Suite:

• SIMPLE & EFFICIENT - The EMC Data Protection Suite makes enterprise data protection extremely easy to
acquire, deploy, and manage. It eliminates the need to size and price every software component individually
as licensing based on front-end protected capacity, which simplifies sizing and capacity.
• FREEDOM & FLEXIBILITY - The EMC Data Protection Suite allows the ability mix and match backup and archive
components across physical and virtual environments to meet objectives and service levels. Full integration
with industry-leading Protection Storage EMC Data Domain® and EMC NetWorker® delivers IT infrastructure
mobility and flexibility.
• INDUSTRY-LEADING BACKUP & ARCHIVE - The components of the The Data Protection Suite featured in this lab
such as EMC NetWorker® backup and recovery software centralizes, automates, and accelerates data backup
and recovery across IT environment. Together with EMC DD Boost for Enterprise Applications which delivers
advanced integration with leading enterprise applications enabling application owner control and faster,
more efficient backups.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 6

 Key Components

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 7

EMC Data Protection Suite
EMC NetWorker Overview

EMC® NetWorker® backup and recovery software centralizes, automates, and accelerates data backup and recovery
across your IT environment. Boasting record-breaking performance and flexibility, NetWorker protects critical business
data in a fast, secure, and easy to manage way.

Whether your organization is a small office or a large data center, you can trust that your data will be protected with
NetWorker. NetWorker users know and trust that their data is backed up and recoverable in the event of user error,
data loss, system outage, or catastrophic event. All your business applications remain in service while data backups
are taking place, for zero downtime.

Data Protection for Microsoft SharePoint 2013

Just like Big Telco Company, demand for Microsoft SharePoint and SQL data protection is increasing, with the
explosion of unstructured data in the case of SharePoint as well as increased structured database demands of SQL. To
address this demand, Big Telco Company is looking to implement EMC Data Protection Suite and in particular EMC
NetWorker, as a robust and efficient solution to add backup and recovery of SharePoint and SQL Server to its portfolio
of hosted services.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 8

NetWorker delivers disaster recovery capabilities for SharePoint across the entire farm infrastructure. NetWorker has
broad SharePoint environment support, including SharePoint Server 2007, 2010, and 2013. This lab highlights the
SharePoint use case leveraging SharePoint 2013.

A key capability is full support for the SharePoint Server VSS Writer. This enables NetWorker to target the SharePoint
configuration database, the search database and index, the shared resource provider, and all of the content
databases. Using the SharePoint VSS Writer, NetWorker’s full farm-level backups ensure backup consistency.
SharePoint automatically notifies NetWorker of changes to the farm. Similarly, if a recovery is done to a SharePoint
content database, using the VSS interface, SharePoint is notified of the recovery—enabling SharePoint to properly
resume operations.

This is all possible with both traditional backup and deduplication backup workflows. For those who do invest in the
deduplication solution with NetWorker, there are significant advantages to be gained for SharePoint protection due to
the potential for a significant amount of redundant data that may be housed in the platform.

For recovery in the context of disaster recovery, NetWorker gives you a number of flexible options. You can restore the
entire farm and perform content database recoveries. You can recover a SharePoint configuration database. You can
recover the SharePoint Search database/index without the need for a full farm crawl—and you can recover SharePoint
Web Parts.

For granular protection of SharePoint with the NetWorker Module for Microsoft, EMC has partnered with Kroll Ontrack,
the provider of a software product called Ontrack PowerControls.

Ontrack PowerControls uses NetWorker SharePoint backups—those highlighted in the previous slide—for granular
item-level recoveries. Step one is to virtually mount the backup saveset via NetWorker and present it to the SharePoint
Administrator. Step two is to use PowerControls to extract the required item-level data.

You can recover SharePoint web applications, site collections, sites, lists, libraries, and so on, all the things that are a
part of the SharePoint logical structure and content. When you use PowerControls to restore, it will restore with full
fidelity, meaning you get back all of the metadata, security settings, details about authors, proper timestamps, and so
on—things that in other market solutions can sometimes be lost during backup and recovery.

With this solution, versioning within SharePoint items, as well as conditions such as checkout status and approval
status, will all be retained and recovered properly. And you have the option of restoring all versions or only specific
versions if you wish.

To find data to restore in such large environments, PowerControls enables search by a number of criteria so data can
be found quickly and restored. And with this solution, restore is as easy as dragging and dropping items you need
back into your target location, which can be the original location, a production server, another SharePoint server, or
even a file system location. There is quite a bit of flexibility possible through this third-party solution.

The slide below highlights particulars on the differentiating granular recovery qualities and features of EMC NetWorker
for SharePoint:

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 9

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 10
Data Protection for Microsoft SQL 2012

For SQL Server, EMC NetWorker backup and recovery can be performed with SQL Server 2005, 2008, including 2008
R2, and 2012. It delivers what is known as Simple Recovery Mode. Through the VSS Writer, NetWorker Module for
Microsoft supports full backups and recovers at the SQL database level. This lab will focus on highlighting the use
case with SQL Server 2012.

New with NetWorker Module for Microsoft 2.4 and above, is support for traditional SQL VDI. This allows SQL log
management, backup granularity including full, incremental and differential and database, file group and file level
recoveries. For customers using the previous Microsoft Module for SQL (NMSQL), the merge of NMSQL provides easy
migration. Also now supported is Client Direct for SQL VDI multi-streaming backups to Data Domain. This means up to
3x greater performance for SQL VDI backups to Data Domain via Client Direct.

NetWorker 8.1 introduced support for a new SQL Server Management Studio (SSMS) plug-in which, among other
features, allows the SQL DBA to run their own ad hoc backup. This feature gives control directly to the SQL DBA for
backup, if and when necessary.

NetWorker 8.2 now adds recovery support via the SSMS plug-in.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 11

Industry leading support for Microsoft SQL Always-On Availability Groups

SQL Server 2012 introduced the concept of AlwaysOn Availability Groups offering higher levels of availability,
flexibility, and resiliency for SQL Server. NetWorker support includes backup on the primary database including full,
differential, incremental and copy. This also includes backup from any secondary SQL database. By allowing
NetWorker to protect the secondary databases, backups do not impact the product servers.

NetWorker Module for Microsoft offers Federated Proxy Node Backup support for SQL Server Always On Availability
Groups. This policy-based feature can also be set by the SQL DBA from within SQL Server Management Studio via the
new plug-in. It enables the SQL DBA to choose which physical server they would like to use as the backup proxy
within the Always On Availability Group. Options are to backup from any replica in the AlwaysOn Availability Group, a
primary replica, a secondary replica, or a primary replica only if the secondary replica is not available.

Hybrid solutions supported include a primary and secondary database on premise, with a secondary database in the
Cloud for disaster recovery, or the customer may have their primary and/or secondary databases running in the Cloud,
but maintain a secondary copy on premises for backup and reporting. Finally, the customer may be running their
primary database on premise in one location with a secondary copy at another location, as well as another secondary
copy in the Cloud for DR. The new support in NetWorker enables the backup of on-premises secondary databases by
the Backup Administrator for all these scenarios.

Policy can be set by the SQL DBA using SQL Server Management Studio, including type of backup, backup media,
deduplication and retention.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 12

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 13
 Lab Overview

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 14

Lab Overview
The primary purpose of this lab is to demonstrate NetWorker's backup capabilities for SharePoint 2013 and Granular
Level Recovery (GLR) using Kroll OnTrack PowerControls (PC). The secondary purpose is to demonstrate NetWorker's
features and functions for backing up SQL 2012 AlwaysOn Availability Group (AAG).

This lab is unique in that it not only provides these two applications, SharePoint & SQL, but the SQL Server is
providing the backend database for SharePoint that doubles as the primary server in the AAG. In other words, the SQL
2012 Server sql2012-01 will be used in both demonstrations.

While the lab is designed to combine these two applications, the documentation for each demonstration is kept
separate to provide the capability to show SharePoint 2013 or SQL 2012 AlwaysOn Availability Groups.

Objectives

Objective 1 - SQL2012 Backup Using Always On Availability Groups

By using the AlwaysOn Availability Group feature of SQL Server 2012, users can keep their databases under an
Availability Group (AG) for high availability. The SQL Server 2012 uses Windows Failover Cluster components to
provide these HA features. The database administrator can set the backup priority for the AG or a database in the AG
and select a particular replica for the backup. Judicious use of the best replica can not only improve backup
performance but also be part of a strategic plan for data protection and business continuance.

NMM provides support for federated backups, during which NMM detects the SQL Server preferred backup (replica)
setting from the AG and then performs the backup at the preferred node/replica. The user can decide whether to
perform scheduled backup or federated backup by providing the appropriate NetWorker save set when creating the
client resource for the backup.

In this lab, you will be using one AAG called SQL12-AAG1 which works with the nodes SQL2012-01 and SQL2012-02
which are part of the cluster SQL12clus1. There are two replicas, one primary on SQL2012-01 and one secondary on
SQL2012-02. The SQLDB-AAG1 is being replicated in this AAG.

Objective 2 - SQL2012 Recovery Using the Always On Availability Groups

In this lab, you will be recovering the database SQLDB-AAG1 which is part of the SQL12-aag1 AAG. You will need to
remove a DB from an Availability Group before you can restore it.

Objective 3 - Sharepoint Full DB Recovery

In this scenario, you will be demonstrating how to restore an entire Content Database in the SharePoint Farm by
navigating through multiple instances to restore the database and its accompanying logs.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 15

Objective 4 - Sharepoint GLR

In this scenario, you will be demonstrating how to leverage NetWorker's virtual File System (NwFS) that supports a
real-time view of the backup session ready to immediately copy a missing document from the source (NwFS) back to
its prior (or any other location in the SharePoint Farm hierarchy one has the rights to) location using a Kroll GUI for the
last step.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 16

Demo Environment Layout
This Lab is a combined environment of both SharePoint 2013 and SQL 2012. The SQL 2012 servers are configured
with multiple SQL instances where one instance provides the backend databases for SharePoint and the other
instance provides the primary database location for an Always-On Availability Group (AAG).

The SharePoint specific components, other than SQL, are made up of a Web Front-End (WFE) server and an Index/
Search server. The WFE is the user interface to SharePoint where the Search server offers up information about the site
content to the browser UI.

The SQL specific components are made up of two servers that comprise the components to provide an Always-On
Availability Group (AAG) as well as the databases for SharePoint.

COMPONENTS

SP2013-01 is the SharePoint WFE Server and the primary interface for the backup applications.

SP2013-02 is the SharePoint Search Server.

SQL2012-01 is the SQL server for the SharePoint Farm as well as the primary server for the AAG. Two instances of SQL
have been configured on this server to make this combined environment possible.

• SQL2012-01/SP: The SQL 2012 instance on SQL2012-01 that provides the content database for SharePoint.
• SQL2012-01/SQ12INST1: The SQL 2012 instance on SQL2012-01 that provides the primary location in the
AAG for the company's production databases. SQL2012-02 is the second SQL server for the AAG. Only one
instance of SQL has been configured on this server.
• SQL2012-02/SQ12INST2: The SQL 2012 instance on sql2012-02 that provides the location for the secondary,
or passive copies of the SQL database.

SQL AAG (Always-On Availability Group)

The two SQL Servers (SQL2012-01/02) are clustered servers called SQ12CLUS1 where the AAG listener (aag1-listener)
lives and provides client connectivity to the database of a given availability group. An availability group listener is a
virtual network name (VNN) to which clients can connect in order to access a database in a primary or secondary
replica of an Always-On Availability Group. An availability group listener enables a client to connect to an availability
replica without knowing the name of the physical instance of SQL Server to which the client is connecting. The client
connection string does not need to be modified to connect to the current location of the current primary replica.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 17

Environment Topology

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 18

Components & Credentials
The following tables list the systems and credentials associated with this lab environment.

Components

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 19

Credentials

Use the following credentials to login to the individual systems, unless otherwise instructed in the specific steps
throughout this guide.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 20

 SQL Server overview

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 21

Preparation Steps for SQL Server 2012 AAG Environment
Open mRemote

Follow the mRemoteNG setup instructions to ensure access to each system. This must be verified before continuing.

Double-click mRemote on the desktop of the launchpad.

Connections Tab

1. Click “+
+” to expand Connections
Connections.
2. Double-click all individual connections to open.
3. Select SQL2012-01 (AAG)
(AAG).

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 22

Connect to Microsoft SQL Server Management Studio

1. On the SQL2012-01 (AAG) taskbar, click Microsoft SQL Server Management Studio
Studio.
2. In the Server name list box, select SQL2012-01\SQ12INST1
3. Click Connect

View the SQLDB-AAG1 database

1. Click “+
+” to expand AlwaysOn High Availability > Availability Groups > SQL12-AAG1 (Primary)

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 23

 2. Click “+
+” to expand Availability Database and view the SQLDB-AAG1 Database. This is the database you will
be working with.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 24

SQL12INST1 Properties

1. Click “+
+” to expand Availability Replica
Replica.
2. Right-click SQL2012-01\SQL12INST1 (Primary)
3. Select Properties

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 25

Review Properties

The Readable secondary field is set to Yes

This is important as you will be conducting the backup from the Secondary replica, not the Primary.

Click OK

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 26

Minimize Microsoft SQL Server Management Studio

Minimize Microsoft SQL Server Management Studio to prepare for the next part of the lab.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 27

Open NetWorker Console

On the Launchpad taskbar, click EMC NetWorker Management Console

Type the following credentials:

• administrator
• Password123!

Click OK

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 28

Launch NW Administration

Click NW-02.vlab.local

Click Launch NetWorker Administration

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 29

Networker Environment Readiness

1. Click Media
2. Click Media Pools
3. Double-click the pool DDVE01 to open the properties
4. The ddve01 media pool has been Enabled
Enabled. This means when a backup is run for groups that have selected
this media pool DDVE01, they will backup to the Data Domain.
5. Click Cancel, as you are only reviewing this pool.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 30

Protection Tab

1. Click Protection
2. Click Clients
3. Right-click sql12clus1.vlab.local
4. Select Modify Client Properties...

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 31

Client Properties

1. In the General tab in the Backup panel, the Save Set Name is assigned to the Microsoft VDI Writer
MSSQL$SQ12INST1#SQL12-AAG1
MSSQL$SQ12INST1#SQL12-AAG1: for the primary SQL replica instance named SQ12INST1 to backup the
databases for Listener SQL12-AAG1 (as delimited by the pound [#] sign)
2. The Protection Group list allows clients to be associated with the Bronze-Application group.
3. When you have completed reviewing this section, close the window.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 32

NetWorker Groups Starting Backups Of Save Sets

With this setup, the start of of the Bronze-Application Group backup uses the Save set as shown to backup the
payload to media pool named ddve01. You now have all the fundamentals of a NetWorker backup in play in the
context of a SQL backup for this particular use case.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 33

NetWorker 9 backup and recovery of
SQL Server

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 34

Backup of SQL 2012 Using NetWorker
Open mRemote

1. Click mRemoteNG
mRemoteNG.
2. Click SQL2012-01 (AAG)
(AAG).

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 35

Open Microsoft SQL Server Management Studio

1. On the SQL2012-01 (AAG) taskbar, click Microsoft SQL Server Management Studio
Studio.
2. Click “+
+” to expand AlwaysOn High Availability > Availability Groups > SQL12-AAG1 (Primary)
(Primary).

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 36

View Properties of the Availability Group

1. Right-click SQL12-AAG1 (Primary)

(Primary).
2. Select Properties
Properties.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 37

Choose Secondary only

1. Click Backup Preferences

2. Select Secondary only
3. Click OK

The SQL Server Preferred Server Order List (PSOL) has been set up to backup the Secondary Only copy of the SQLDB-
AAG1 database. When the NetWorker client SQL2012clus1 runs a backup, the listener AAG1-listener will redirect the
backup command (nsrsqlsv) to SQL2012-02 as a member of the AAG (AlwayOn Availability Group).

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 38

Availability Groups

Microsoft debuted Availability Group support in SQL Server 2012. Even though you only have one database, SQLDB-
AAG1 in your AG, more than one database can be in this group, ready for either Synchronous or Asynchronous failover
to a Secondary Replica on a different SQL 2012 server (SQL2012-02 in this case). In the case of a manual or automatic
failover, the Secondary Replica will eventually fail back to the Primary Replica once whatever caused it to failover has
been fixed.

Open NetWorker Administration Console

Hover over EMC NetWorker on the Launchpad taskbar (previously opened).

Click NetWorker Administration Console

Console.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 39

Run The Backup

1. Select Monitoring
Monitoring.
2. Right-click Bronze Policy which contains the SQL12clus1 client.
3. Select Start
Start.

Click Yes to confirm

Click Yes to start Bronze group

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 40

Monitoring the Backup Job (Group)

1. Click “+
+” to expand the Bronze Policy.
2. Right-click Applications
3. Select Show Details...

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 41

View Status

1. Observe the most recent Workflow runs

runs.
2. Highlight, and select the most recent backup.
3. Click Show Details to view the completed actions

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 42

Confirm Workflow Completed

1. Confirm Status: Succeeded

2. Scroll down the Action Messages to view the complete status
3. Click Show Action Logs to view full output of log file

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 43

Close the Show Action Logs window

Close both windows.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 44

Close the Workflow status windows

Close the status window.

Minimize Window

Minimize EMC Networker Administration to prepare for the next step.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 45

Recovery of SQL 2012 DB in an Availability Group
Introduction

In this section, you will execute a recovery in which you will take the backup of the SQLDB-AAG1 database from the
Secondary SQL Server, SQL2012-02, and restore it to the Primary SQL Server, SQL2012-01.

This restore will be followed with an Add New Database To Availability Group Microsoft wizard which will find, add and
synchronize the database from Primary to Secondary Replica, fully completing the recovery.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 46

Open SQL2012-01 (AAG)

1. On the Launchpad taskbar, click mRemoteNG

mRemoteNG.
2. Click SQL2012-01 (AAG)
(AAG).
3. Click “+
+” to expand AlwaysOn High Availability > Availability Groups > SQL12-AAG1 (Primary) > Availability
Replicas
Replicas.

Log into SQ12INST2

1. Right-click SQL2012-02\SQ12INST2 (Secondary)

(Secondary).

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 47

 2. Select Connect

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 48

Connect to Secondary Server

Click Connect

Overview of Object Explorer

Before attempting a restore, you must break the database, which will simulate a logical error or corruption from a SQL
server perspective. The best way to accomplish this is from the Primary replica.

• The Primary replica named SQL2012-01\SQ12INST1 Instance.

• The Secondary replica named SQL2012-02\SQ12INST2 Instance.
• The Availability Database is named SQLDB-AAG1.

Note: SQL2012-02/SQ12INST2 is now open in Microsoft SQL Server Management Studio.

These tasks inside Microsoft SQL Server Management Studio ensure that both Primary and Secondary replicas are
synchronized visibly highlight that both instances/databases are healthy PRIOR to removing the database from the
Availability Group to simulate a logical corruption/DR requiring a database recovery.

Break the Database Using The Primary Replica

You will now break the database to simulate disaster/error from this Primary replica.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 49

 1. Click “+
+” to expand SQL2012-01\SQ12INST1 > Databases > SQLDB-AAG1 (Synchronized) > Tables
Tables.
2. Right-click dbo.Table_1_AAG1
3. Select Delete
Delete.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 50

Delete Object Dialog

Click OK
OK.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 51

Confirm Deletion of Table_1_AAG1

1. Collapse SQL2012-01\SQ12INST1 (SQL Server 11.0.5058 - VLAB\sqlsvc)

VLAB\sqlsvc).
2. Click “+
+” to expand Databases for SQL2012-02\SQ12INST2 (SQL Server 11.0.5058 - VLAB\sqlsvc)
VLAB\sqlsvc).
3. Click “+
+” to expand SQLDB-AAG1 (Synchronizing)
(Synchronizing).
4. Click “+
+” to expand Tables and observe the absence of dbo.Table_1_AAG1 in the replica copy

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 52

Remove SQLDB-AAG1 Database From Availability Group on Primary Replica

1. Click “+
+” to expand SQL2012-01\SQ12INST1 (SQL Server 11.0.5058 - VLAB\sqlsvc)
VLAB\sqlsvc).
2. Click “+
+” to expand AlwaysOn High Availability > Availability Groups > SQL2012-AAG1 (Primary) > Availability
Databases
Databases.
3. Right-click SQLDB-AAG1
4. Select Remove Database from Availability Group
Group...

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 53

Remove Database from Availability Group named SQL12-AAG1

Click OK
OK.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 54

Offline Corrupted Database

1. Under SQL2012-01\SQ12INST1 (SQL Server 11.0.5058 - VLAB\sqlsvc), click “+

+” to expand Databases
Databases.
2. Right-click SQLDB-AAG1 (Synchronized)
3. Select Tasks
4. Select Take Offline

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 55

Take database offline

Click Close
Close.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 56

Refresh SSMS Window

A refresh of the Object Explorer is required in order to see SQLDB-AAG1 (Restoring...). This can take up to 60 seconds
to display.

1. Collapse SQL2012-01\SQ12INST1 (SQL Server 11.0.5058 - VLAB\sqlsvc)

VLAB\sqlsvc).
2. Select SQL2012-02\SQ12INST2 (SQL Server 11.0.5058 - VLAB\sqlsvc)
3. Select Refresh

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 57

Delete Restoring Attempt On Secondary

1. Click “+
+” to expand SQL2012-02\SQ12INST2 (SQL Server 11.0.5058 - VLAB\sqlsvc) > Databases
2. Right-click SQLDB-AAG1 (Restoring...)
3. Select Delete

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 58

Delete Object

Click OK
OK.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 59

Minimize Microsoft SQL Server Management Studio

Minimize Microsoft SQL Server Management Studio to prepare for the next step.

Run NetWorker User for SQL Server from SQL2012-01

On the SQL2012-01 (AAG) taskbar, click NetWorker User for SQL

SQL.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 60

Select SQL2012-01\SQINST1

Select SQL2012-01\SQINST1
SQL2012-01\SQINST1.

Click OK
OK.

Select NetWorker SQL Server Client

Click Operation
Operation, and select NetWorker SQL Server client

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 61

Select the SQL Server client

In the Networker SQL Server client list box, select sql12clus1.vlab.local

Click Continue

Select SQL Instance

Select A SQL Server named instance, and in the list box select sql12clus1\SQ12INST1

Click Continue
Continue.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 62

Review Properties of the SQLDB-AAG1 database on the SQL Cluster client

Select SQLDB-AAG1, and right-click SQLDB-AAG1

SQLDB-AAG1.

Select Properties

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 63

Enter Log File Destination In The Files tab

Select Files
Files.

Select SQLDB-AAG1_Log
SQLDB-AAG1_Log.

Click Destination
Destination. This provides file system scrolling to find the data base full path.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 64

Specify Database Log File Destination

1. Scroll down to drive FF: and click “+

+” to expand. Select SQL2012_log ensuring that this drive letter + full path is
populated in the Destination location field.
2. The Destination file name will pre-populate with an appended file name
3. Click OK
OK.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 65

Enter Database Data File Destination In Files tab

Select SQLDB-AAG1
SQLDB-AAG1.

Click Destination
Destination. This again provides file system scrolling to find the data base full path.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 66

Specify Database Data File Destination

1. Scroll down to drive E: and click “+

+” to expand. Select SQL2012_AAG ensuring that this drive letter + full path
is populated in the Destination location filed.
2. The Destination file name will pre-populate with an appended file name
3. Click OK
OK.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 67

Enable Overwrite the existing database

1. Select Overwrite the existing database

database.
2. Confirm F:\SQL2012_LOG and E:\SQL2012_AAG
3. Click OK

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 68

Start Database Recovery

Click Start to begin the recovery.

Final Restore Job With Correct Destination Paths

The Restore Status windows appears. Confirm Restore Completion.

Close both the Restore Status window and the NetWorker User for SQL window.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 69

Microsoft SQL Server Management Studio

On the SQL2012-01 (AAG) taskbar, click Microsoft SQL Server Management Studio
Studio.

Refresh Microsoft SQL Server Management Studio

1. Select SQL2012-01\SQINST1
2. Click Refresh
Refresh.
3. Click “+
+” to expand Databases
Databases.
4. Verify SQLDB-AAG1 exists.
5. Verify that the deleted table dbo.Table_1_AAG1 also exists under Tables
Tables.

Run Add Database To Availability Group Wizard

1. In SQL2012-01\SQINST1 (SQL Server 11.0.5058 - VLAB\sqlsvc) on the Primary Replica.

2. Click “+
+” to expand AlwaysOn High Availability > Availability Groups > SQL12-AAG1 (Primary)
3. Right-click Availability Databases
Databases.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 70

 4. Select Add Database...

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 71

Click Next

Click Next
Next.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 72

Select The Database To Add

Select SQLDB-AAG1
SQLDB-AAG1.

Click Next
Next.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 73

Select Initial Data Synchronization

1. Verify Full data synchronization is selected.

2. When Full is selected, the shared network location will be populated by default.
3. Click Next

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 74

Connect To Existing Secondary Replicas

Click Connect
Connect.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 75

Connect to Secondary Server

Click Connect
Connect.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 76

Confirm Connected

Confirm Connected As VLAB\sqlsvc

Click Next
Next.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 77

Validation Of AG Results

Review the Availability Group Validation and ensure the results are successful.

Click Next
Next.

Summary Of Add Database To AG Choices

In the next task, the \\SQL2012-01\Backup (identified as a shared network location in the Group Validation screen)
share will be the location leveraged for a full database backup.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 78

Click Finish to proceed to the Summary screen

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 79

Check the progress

Click More details to see the progress

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 80

The wizard completed successfully

Review the results window to view the processes that have completed.

Click Close
Close.

Confirmation Of Recovered Databases

After the SQLDB-AAG1 database is synchronized to the Secondary Replica.

1. Select SQL2012-01\SQINST1 (SQL Server 11.0.5058 - VLAB\sqlsvc)

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 81

 2. Click refresh
refresh.
3. Under the Databases tree, observe that the SQLDB-AAG1 (Synchronized) is a recovered database.
4. Click “+
+” to expand SQLDB-AAG1 (Synchronized) > Tables to confirm that table dbo.Table_1_AAG1 is present
with this recovery.
5. Click “+
+” to expand AlwaysOn High Availability > Availability Group > SQL12-AAG1 (Primary) > Availability
Databases
6. Ensure that SQLDB-AAG1 is listed under Availability Databases.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 82

Close Microsoft SQL Server Management Studio

Close Microsoft SQL Server Management Studio to prepare for the next lab.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 83

 NetWorker 9 backup of SharePoint

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 84

Overview of Lab Objectives
In this lab there are two goals, one is to complete a full content database recovery, the second is to complete a GLR
restore of a single file with-in the SharePoint farm using virtual mount and Kroll On track Power Controls.

In preparation for the demo you will perform a couple of backups, one backup of the whole farm, then delete a file and
perform a second full backup. You will also use the NMM UI and and modify a configuration option to ensure a
smooth running lab with an ease of use work-flow.

Note: Full backups take about 6.5 minutes in this environment, so you will proceed to the recovery immediately
following the client configuration review.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 85

Perform a Full Backup
In this setup step you will perform a full backup of the SharePoint 2013 Farm. Your goal here is to ensure you have a
backup of the content database, which contains a copy of all the documents.

Launch NetWorker Management Console (NMC)

On the Launchpad taskbar, click NetWorker Management Console (NMC)

(NMC).

Note: This action will take a minute to load the application. NMC may be opened already from the previous lab.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 86

Log in to NetWorker Management Console

Type the following credentials:

• administrator
• Password123!

Click OK
OK.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 87

Launch NetWorker Administrator for the NW-02 Server

Click NW-02.vlab.local

Select Launch NetWorker Administration

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 88

Protection Tab

1. Select Protection
Protection.
2. Click “+
+” to expand Groups
Groups.
3. Click Silver-Application
Silver-Application.
4. Observe that all members of the SharePoint configuration exist in the Silver-Application group.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 89

Start the Silver Policy

1. Click Monitoring
Monitoring.
2. Click “+
+” to expand Silver
Silver.
3. Right-click Applications
Applications.
4. Select Start
Start.

Click Yes to start Workflow Applications

Click Yes
Yes.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 90

Show Monitoring Details

1. Right-click Silver > Applications

Applications.
2. Select Show Details...

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 91

Monitor to Completion

1. Select the backup with the most recent Date and Time
2. Select the workflow action Name: Backup
3. Click Show Details
Details.

The duration of the backup will take about 4 minutes.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 92

Backup Details

1. Confirm Status: Succeeded

2. Scroll down to view all Action Messages
3. When finished viewing, close the window.

Close Workflow Status Window

Close the status window.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 93

Minimize NetWorker Administration

Minimize NetWorker Administration to prepare for the next step.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 94

Delete a Document from SharePoint Site
Open mRemoteNG

1. On the Launchpad taskbar, click mRemoteNG

mRemoteNG.
2. Ensure that SQL2012-01 (AAG) server is opened in mRemoteNG.
3. Ensure that SP2013-01 (WFE) server is opened in mRemoteNG.
4. Select SP2013-01 (WFE)
(WFE).
5. On the SP2013-01 (WFE) taskbar, click Internet Explorer
Explorer.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 95

Log into SP2013-01 Web Front End Server (WFE)

1. Select EMC Team Site - Home

Home.
2. Select NMDA_8.2_Administration_Guide
NMDA_8.2_Administration_Guide.
3. Click the ellipsis to view menu options.
4. Click the ellipsis again to view more menu options.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 96

Delete document

Select Delete
Delete.

Move deleted file to Recycle Bin

Click OK
OK.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 97

Confirm document removal from site

NMDA_8.2_Administration_Guide has been removed from the EMC Team 1 Site.

Close Internet Explorer

Explorer.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 98

Perform a Second Full Backup
In this step you will be backing up the SharePoint Farm without the file (a now deleted file) contained in the previous
task. This second backup will be used to perform the Content Database Recovery.

Open NW Administration Console

1. On the Launchpad taskbar, click EMC NetWorker Administration

Administration.
2. Ensure Monitoring is selected.

Initiate the Silver Policy for the Share point Farm Backup

1. Click “+
+” to expand Silver
Silver.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 99

 2. Right-click Applications
Applications.
3. Select Start
Start.

Select Yes when prompted Do you want to start Workflow Applications

Applications?

Click Yes to confirm

Click Yes to start Workflow Applications.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 100
Monitor the Silver Policy Details

1. Right-click Silver > Applications

Applications.
2. Select Show Details

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 101
Show Details

1. Select the Workflow of the most recent Date and Time

2. Select the Workflow action Name: Backup
3. Select Show Details
Details.

Confirm Status Succeeded

1. Ensure Status: Succeeded before proceeding.

Note
Note: This process will take several minutes to complete.

2. Scroll down to view all Action Messages.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 102
3. When finished viewing, close the window.

Close Details Window

Close the Workflow status window.

Minimize NW Administration Console for the next portion of the lab.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 103
Delete EMC Team 1 Database and log files
First you will detach the EMC Team 1 database using SSMS and and then delete it using Windows Explorer.

Connect to SharePoint Instance

1. On the Launchpad taskbar, click mRemoteNG

mRemoteNG.
2. Select SQL2012-01 (AAG)
(AAG).
3. On the SQL2012-01 (AAG) taskbar, click Microsoft SQL Server Management Studio
Studio.
4. In the Server name list box, select SQL2012-01\SP
5. Click Connect

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 104
Locate and detach the BRS_Lab database

1. Click “+
+” to expand Databases
2. Right-click EMC Team 1
3. Select Tasks
4. Select Detach...

Complete Detaching the BRS_Lab Database from SQL Server

The Detach Database dialog box appears

Select Drop Connection and Update Statistics

Statistics.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 105
Click OK

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 106
Verify Detachment

Verify that the EMC Team 1 Database has been removed.

Close Microsoft SQL Server Management Studio

Studio.

Locate the EMC Team 1 DB using Windows Explorer

On the SQL2012-01 (AAG) taskbar, click Windows Explorer

Explorer.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 107
Browse to the database location and delete it

1. Navigate to F:\SP\MSSQL11.SP\MSSQL\DATA\EMC Team 1

2. Right-click EMC Team 1
3. Select Delete

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 108
Browse to the log location and delete it

1. Navigate to F:\SP\MSSQL11.SP\MSSQL\DATA\EMC Team 1_log

2. Right-click EMC Team 1_log
3. Select Delete

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 109
NMM Configure Options Add SQL2012-01 from SP2013-01
Now you will return to the SP2013-1 (WFE) Sharepoint web front end server to add SQL2012-01 to the NMM
Configuration Options pull down menu. This will ensure that NetWorker can virtually mount the SQL Content Database
directly to the SP2013-01 Web Front End Server using NWFS followed by performing a single file GLR (granular level
recovery) restore using Kroll Ontrack directly from this [virtually] mounted copy of the backup.

This recovery directly from the virtual mount on the WFE straight to the EMC Team Site is where NetWorker has a
unique speed advantage since other backup products do not have a virtual folder mount and thus must recover their
data from an external source - a source other than the WFE, meaning a double hop of data sources for data recovery of
either an entire database or a single file using GLR technolgy.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 110
Launch NetWorker User for Microsoft on SP2013-01 (WFE)

1. Select SP2013-01 (WFE)

(WFE).
2. On the SP2013-01(WFE) taskbar, click NetWorker Module for Microsoft
Microsoft.
3. Click Options
Options.
4. Select Configure Options...

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 111
Configuration Options

In the Configuration Options dialog box, select the right/left arrows icon.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 112
Select Viewable Clients

In the Clients to list on menu bar: area, confirm SQL2012-01 is present.

Click OK
OK.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 113
Configuration Options

Click OK
OK.

Verify Client Selection Change

Select Recover
Recover.

In the Client list box, select SQL2012-01

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 114
NetWorker 9 Recovery of SharePoint

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 115
Review the details of the SharePoint Backups
Open NetWorker Administration Console

On the Launchpad taskbar, click NetWorker Administration Console

Console.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 116
Review details of successful backups

1. Select Monitoring
Monitoring.
2. Click “+
+” to expand Silver
Silver.
3. Right-click Applications
Applications.
4. Select Show Details...

Review Details of Previously Run Backups

Here you can see the Start Time of previously run backups.

Here you will see that you have already run two backups, both backups include a full backup of the Web Front End
Server, the Index Server and the SQL Server Content Database.

The first backup contains a file that was later deleted. This copy will be used for the nwfs virtual mount and GLR
restore.

The second backup does not contain the deleted file, but was a full backup of the entire farm. We will use this copy to
perform the content database recovery. The workflow of the recovery will be as follows:

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 117
 • Restore the content database from the most recent backup
• Perform the GLR restore from the prior backup.

Note: You have already detached and deleted the content database in preparation for the recovery demonstration.

This completes your review of the SharePoint client configuration.

Close Window

When finished viewing, close the window.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 118
Restoring the Content Database
Now that you have a successful backup of the Farm, you can restore the entire content database.

Use mRemote to log in to the SQL server host SQL2012-01

1. On the Launchpad taskbar, click mRemoteNG

mRemoteNG.
2. Select SQL2012-01 (AAG)
(AAG).
3. On the SQL2012-01(AAG) taskbar, click NetWorker Module for Microsoft
Microsoft.

Note: The NetWorker Module for Microsoft will take a minute to load.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 119
Mark the EMC Team 1 Data base for Recovery

1. Select Recover
Recover.
2. Click “+
+” to expand Applications > SqlServerWriter
SqlServerWriter, and select SQL2012-01\SP
3. Select EMC Team 1 1.
4. Click Recover
Recover.

NMM browses the directory structure of the client as of the most recent backup by default. Here, you are browsing to
the location of the EMC team 1 database.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 120
Recover Summary dialog box

NMM Recover provides a brief summary of your prior selections. You can now start the recovery to restore the EMC
Team 1 database to its original location.

Click Start Recover

Recover.

Monitor the Database Recovery

1. Select Monitor
Monitor.
2. To enable automatic scrolling of the logging information as updates occur, place the cursor in the right
navigation pane and click
3. After the restore completes, close the NMM UI.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 121
NetWorker is now performing a VSS (Volume ShadowCopy) conventional restore from the Data Domain using the most
recent full backup of the SQL database.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 122
Use Windows Explorer to Validate the Recovery

1. Select SQL2012-01(AAG)
SQL2012-01(AAG).
2. On the SQL2012-01(AAG) taskbar, click Windows Explorer
Explorer.
3. Click “+
+” to expand F_Vol
F_Vol, and navigate to \SP\MSSQL11.SP\MSSQL\DATA
4. Verify the successful restore of the EMC Team 1 content database and EMC Team 1_log log file

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 123
Log in to Microsoft SQL Server Management Studio

1. On the SQL2012-01(AAG) taskbar, click Microsoft SQL Server Management Studio

Studio.
2. In the Server name list box, select SQL2012-01\SP
3. Click Connect
Connect.

Verify the Database exists using Microsoft SQL Server Management Studio

1. Select SQL2012-01\SP (SQL Server 11.0.5058 - VLAB\sqlsvc)

2. Click “+
+” to expand Databases

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 124
 3. Verify that the EMC Team 1 database exists.

The deleted database has now been recovered and successfully re-attached to the SQL Server.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 125
Validate recovery and contents of the restored Share point Farm
Now that the EMC Team 1 database is restored, verify that the Sharepoint farm is recovered and also verify its
contents.

Recall that an accidentally deleted file called NMDA_8.2_Administration_Guide is still missing, because it is in a
previous backup - a backup conducted before the file was deleted.

In this step you will see that both the Farm has been Recovered and that the desired content is missing by looking at
the EMC Team 1 Site and browsing its content.

After this, you will then perform the GLR recovery from the previous backup.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 126
mRemote to the SP2013-01 (WFE) Server

1. Select SP2013-01(WFE)
SP2013-01(WFE).
2. On the SP2013-01 (WFE) taskbar, click Internet Explorer
Explorer.
3. Click EMC Team 1 Site-Home
Site-Home.

Now you will browse the contents of the site using the Web Front End Server.

Validate site contents

Observe that the NMDA_8.2_Administration_Guide file is missing.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 127
By accessing the EMC Team 1 Site, you know that the farm has been successfully recovered, but that the desired
NMDA_8.2_Administration_Guide file is still missing.

Now you will recover this file from a previous backup to demonstrate granular level recovery, meaning the ability to
recover a single file or number of objects, but not have to recover an entire database.

Close Internet Explorer

Explorer.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 128
Restoring a SharePoint Server 2013 document with GLR
Open NetWorker User for Microsoft

1. Click SP2013-01 (WFE)

(WFE).
2. On the SP2013-01 (WFE) taskbar, click NMM
NMM.
3. Select Recover
Recover.
4. Click Recover Options...

Specify Granular Level Recovery Options

1. Select SharePoint Granular Level Recovery

Recovery.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 129
 2. Click Browse

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 130
Browse for Folder

1. Click “+
+” to expand This PC
PC.
2. Select Local Disk (C:)
3. Click Make New Folder
Folder.
4. Specify the GLR path.
5. Click OK
OK.

In the recover options you'll see the GLR tab the path that will be used to perform the virtual mount on this host and
how long the virtual mount of the content database will be retained. NetWorker will be virtually mounting the backup
residing on the protection storage, in this case EMC Data Domain. By virtually mounting the the data from protection
storage directly, it is more instantaneously accessible for recovery use. Virtual mounting the backup is a unique
feature of EMC next generation data protection solutions that helps dramatically reduce recovery times.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 131
Create Folder for GLR

Select C:\GLR
C:\GLR.

Click OK
OK.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 132
Select Recovery Client

You must select the SQL database server from the Client list, the reason you do this is because this is the client that
hosts the content database, and the client who's database backup you will mount for the GLR restore.

In the Client list box, select SQL2012-01

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 133
Change the Browse Time

1. Click the calender icon in NMM to change the browse time to a time prior to the most recent successful
backup
2. Change the browse time to a time just prior to the most recent successful backup, the backup prior to it
contains the file you need to recover. Refer to the next step if you need to determine what to set the browse
time to.
3. Click OK
OK.

Determine Browse Time using Group Detail in NMC Monitoring Show Details

Before performing the GLR you will need to determine a browse time prior to the most recent backup from NetWorker
Administration Console, which can be accessed from the Launchpad taskbar.

1. Click “+
+” to expand the Silver Policy
Policy, and then right-click Applications
Applications. Click Show Details
Details. Here you will use
the most recent backup times to ensure that we browse a backup performed just prior to it.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 134
 2. Note the time stamp of the two backups previously taken.

By looking at the group details you now know you need to set the browse time at least 4-5 minutes prior to the group
completion time reported, since you know the backup takes several minutes.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 135
Mark the EMC Team 1 content database

1. Click “+
+” to expandApplications
Applications > SqlServerWriter
SqlServerWriter, and then click SQL2012-01\SP
2. Select EMC Team 1

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 136
Mount EMC Team 1 Content DB for Granular Level Recovery

1. Right-click EMC Team 1

2. Select Mount SharePoint backup for Granular Level Recovery

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 137
Ensure virtual drive has been mounted

1. Select Monitor
2. Click in the Monitor window and scroll down to verify the backup has been mounted

At this point you can see that we have virtually mounted the backup to the nwfs mount point, you are now ready to
perform GLR using Kroll.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 138
Use Kroll OnTrack To Restore Document

1. On the SP2013-01 (WFE) taskbar, click Ontrack Power Controls for SharePoint
SharePoint.
2. Click Add to select Source Path

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 139
Browse to the nwfs mount point that contains the .mdf

1. Click “+
+” to expand C: and navigate to \GLR\1449002048\F$\SP\MSSQL11.SP\MSSQL\DATA\
2. Select EMC Team 1.mdf
3. Click Open
Open.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 140
Browse to the nwfs mount point that contains the .LDF

Click Add
Add.

The next step is to select the LDF files that are associate with the content database you are performing the GLR for.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 141
Browse to the nwfs mount point that contains the .ldf

1. Click “+
+” to expand C: and navigate to \GLR\1449002047\F$\SP\MSSQL11.SP\MSSQL\DATA\
2. Select EMC Team 1_log.ldf
3. Click Open
Open.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 142
Add source data path

1. Ensure that the Source Files have been selected.

2. Click Next
Next.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 143
Missing Temporary File Path

Click Yes
Yes.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 144
Target Server Selection

Now select the target site, that Kroll will allow you to restore the document into. The URL specified is for the BRS_Lab
Team Site that you want to recover the missing NMDA_8.2_Administration_Guide into.

1. In the SharePoint Server Site URL list box, verify http://sp2013-01:30001

2. In the Authentication Information area, select Connect using the current Windows credentials
credentials.
3. Click Next

Connect, expand and then drag and drop

1. Click “+
+” to expandSources.
Sources. Click the Documents folder of the EMC Team 1 Site to locate the
NMDA_8.2_Administration_Guide contained in the previous backup, which has been virtually mounted.
2. Click “+
+” to expandTargets.
Targets. Click the Documents folder of the EMC Team 1 Site in the same path as the
source.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 145
 3. Select the NMDA_8.2_Administration_Guide from the Sources panel, and then drag and drop it into the
Documents folder of the Targets EMC Team 1 Site in the lower left panel.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 146
View Copy Progress

Confirm Copy finished

finished.

Click Close
Close.

You can see that the copy process has completed and this also shows the source and destination locations, notice
that the source is your nwfs virtual mount location.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 147
Verify Copy from Kroll

Select NMDA_8.2_Administration_Guide in the target location of the documents folder of the EMC Team 1 Site.

Observe inside Kroll that the file has been successfully copied.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 148
Verify file recovery from Share Point

1. On the SP2013-01(WFE) taskbar, click Internet Explorer

Explorer.
2. Click EMC Team Site - Home
3. Select the restored NMDA_8.2_Administration_Guide in the EMC Team 1 Site

The NMDA_8.2_Administration_Guide file has been successfully recovered to Sharepoint.

This concludes your granular level restore using the virtual mount feature of NetWorker.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 149
 Conclusion

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 150
Summary
Thank you for taking the time to walk through this hands-on lab exploring how the EMC Data Protection Suite has
extended it's industry leading capabilities to include efficient support for Microsoft SQL Server 2012 and Microsoft
SharePoint 2013.

As a review you completed the following objectives in this vlab:

• SQL2012 Backup Using Always On Availability Groups

• SQL2012 Recovery Using the Always On Availability Groups
• Sharepoint Full DB Recovery
• Sharepoint GLR

The goal of this lab was to showcase how EMC's Industry Leading Backup and Archive solutions enhance backup and
recovery by enabling BIG Telco to change the game for it's SharePoint and SQL Hosting services by differentiating their
offering and including data protection services along with it's hosting services. Big Telco has now been implementing
these components now and have truly set themselves apart as a bringing unique data protection capabilities to their
enterprise.

NetWorker 9 for SharePoint 2013 and SQL 2012 AAG Page 151