EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution

(1)

EMC

®

NetWorker

®

Module for

Microsoft for Windows Bare Metal

Recovery Solution

Version 8.2 Service Pack 1

User Guide

302-001-235

(2)

Published January, 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com). EMC Corporation

Hopkinton, Massachusetts 01748-9103

(3)

5 7 9

Introduction 13

Bare Metal Recovery overview... 14

System requirements... 14

Supported operating systems... 14

Supported Microsoft applications... 14

NetWorker software version requirements... 15

Microsoft BMR requirements... 15

CPU requirements... 15

Hard disk requirements...15

NIC driver requirements...16

Critical and noncritical volume requirements...16

System Reserved Partition requirements... 16

Rollover requirements... 17

Protecting an environment before a disaster...17

BMR by using NetWorker and NMM... 17

Microsoft Active Directory Backup and BMR 19 Backing up an Active Directory for BMR... 20

Performing BMR of an Active Directory...20

Microsoft SQL Server Backup and BMR 21 SQL Server 2014, 2012, and 2008 R2...22

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the VDI technology...22

Performing BMR of a SQL Server 2014, 2012, or 2008 R2... 25

SQL Server 2008 and 2005...27

Backing up a SQL Server 2008 or 2005 for BMR by using the VSS technology... 27

Performing BMR of a SQL Server 2008 or 2005... 28

Microsoft SharePoint Server Backup and BMR 31 SharePoint Server 2013 and 2010...32

Backing up SharePoint Server 2013 or 2010 for BMR... 32

Performing BMR of SharePoint Server 2013 or 2010...35

SharePoint Server 2007... 36

Backing up SharePoint Server 2007 for BMR... 36

Performing BMR of SharePoint Server 2007...38

Figures Tables Preface Chapter 1 Chapter 2 Chapter 3 Chapter 4

FIGURES

(6)

(7)

Revision history... 9 Sample SharePoint Server 2010 configuration...32 1

2

TABLES

(8)

(9)

Preface

As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features.

Contact your EMC technical support professional if a product does not function properly or does not function as described in this document.

Note

This document was accurate at publication time. Go to EMC Online Support (https:// support.emc.com) to ensure that you are using the latest version of this document. Purpose

The purpose of this guide is to provide detailed information about performing Windows Bare Metal Recovery by using EMC NetWorker Module for Microsoft.

Audience

This guide is part of the EMC NetWorker Module for Microsoft documentation set. It is intended for use by system administrators to perform Windows Bare Metal Recovery of Microsoft applications.

Readers should be familiar with the following technologies used in backup and recovery:

l EMC NetWorker software

l EMC NetWorker snapshot management

l Microsoft Volume Shadow Copy Service (VSS) technology

Revision history

The following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

01 January 28, 2015 First release of this document for EMC NetWorker Module for Microsoft release 8.2 SP1.

CHAPTER 1 Introduction

l Bare Metal Recovery overview... 14

l System requirements... 14

l Protecting an environment before a disaster...17

l BMR by using NetWorker and NMM... 17

(14)

Bare Metal Recovery overview

This guide provides detailed information about Windows Bare Metal Recovery (BMR) solution by using EMC®_NetWorker®_{and EMC NetWorker Module for Microsoft (NMM),}

how this solution works, and the procedures that you are required to follow for BMR of the supported Microsoft applications.

BMR is a technique in the field of data recovery and restoration where the backed up data is available in a form that allows you to restore a system from bare metal, that is, without any requirements as to previously installed software or operating system.

Typically, the backed up data includes the necessary operating system, applications, and data components to rebuild or restore the backed up system to an entirely separate piece of hardware. The hardware receiving the restore should have a similar configuration as that of the hardware that was the source of the backup.

The basic BMR is the process of bringing up a server after a disaster and ensuring that the system recovers with the operating system, the applications, and the data as they were at the time of the failure.

Restoring a server to the exact configuration that it had at the time of its destruction can be a difficult task. When this restoration is performed to another hardware, it can add to the complexity of the process and can be time-consuming. Windows BMR solution provides a flexible and reliable method of restoring a server after a disaster.

System requirements

The following sections list requirements to perform Windows BMR. The EMC NetWorker Online Software Compatibility Guide that is available on the https://support.emc.com/ products/1095/Topics/pg41054/ page also provides the information about the versions of the supported operating systems, the software and hardware requirements, and the exact versions of the Microsoft applications to perform Windows BMR.

Supported operating systems

l Windows Server 2012 R2 (x64) l Windows Server 2012 (x64)

l Windows Server 2008 SP2 (x86 and x64) l Windows Server 2008 R2 SP1 (x64) l Windows Server 2008 R2 (x64) l Windows Server 2008 (x86 and x64)

Supported Microsoft applications

(15)

l SQL Server 2014 l SQL Server 2012 l SQL Server 2008 R2 SP2 or later l SQL Server 2008 SP3 or later l SQL Server 2005 l Active Directory

l System Center Virtual Machine Manager

NetWorker software version requirements

l NetWorker server 7.6 SP3 or later l NetWorker client 8.2 SP1

l NetWorker Management Console 8.2 SP1

l Use the NetWorker Windows BMR 32-bit ISO image to recover an x86 operating

system on either an x86 or x64 computer

l Use the NetWorker Windows BMR 64-bit ISO image to recover only an x64 operating

system on an x64 computer

Microsoft BMR requirements

Perform BMR recoveries to the same or similar hardware, and physical to virtual environment.

The following Microsoft KB article provides the requirements to perform a BMR to similar hardware:

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

CPU requirements

l The operating system architecture and the processor architecture must match. l The firmware—Basic Input/Output System (BIOS) or Unified Extensible Firmware

Interface (UEFI) must match.

l You can treat AMD or Intel processors as being the same if they follow the same

architecture. You can recover the operating system backup of an AMD x64 computer to an Intel x64 computer. The process is reversible.

l You can restore the backup of an x86 operating system version only to an x86

processor computer.

l You can restore the backup of an x64 operating system version only to an x64

processor computer.

Hard disk requirements

l The disk or RAID drivers that are used in the old system must be compatible with the

disk or RAID controllers in the new system.

l For each critical disk on the BMR target system, the startup hard disk capacity on the

new system must be greater than or equal to the capacity on the old system. BMR fails if the capacity is smaller by even a single byte.

l Windows BMR supports IDE, SATA, or SCSI hard disks. You can perform the backup

on one type of hard disk and recover on another type. For example, SAS to SATA is supported.

Introduction

(16)

l You must restore the backup to the same logical disk numbers as on the original

server. You cannot use different logical disk numbers on the target system to recover the critical volumes such as the operating system volume.

l Ensure that the RAID setup on destination computer does not interfere with the disk

order of the hard disks.

NIC driver requirements

To use different Network Interface Card (NIC) after a Windows BMR recovery, you must install new NIC drivers that match the NIC in the new computer after Windows boots on the new server.

Critical and noncritical volume requirements

l Windows BMR backs up only critical volumes, and can be used for offline disaster

recovery. You must use the NetWorker client to back up the non-critical volumes. Note

NetWorker 8.2 SP1 considers only system volume as a critical volume. If you have installed a Microsoft application on a drive other than the system drive, the drive is not considered as critical. On Windows Server 2008 R2, a volume is critical if a Microsoft application has installed a Windows service on it, but on Windows Server 2012, a volume that has a Windows application service installed is not critical.

l To make a volume critical on Windows Server 2012, set the value of the HKLM

\System\CurrentControlSet\Control\SystemWriter

\ReportWin32ServicesNonSystemState registry key to 0. This ensures that BMR includes the Microsoft application binaries, and the volume on which they are installed is marked as critical.

System Reserved Partition requirements

Ensure that System Reserved Partition (SRP) is online before you perform a BMR backup. Otherwise, the backup fails and displays the following error message:

84687:save: Unable to get volume information of file system '\\?

\Volume{245204f6-5ff7-11e2-a3ac-806e6f6e6963}\': The device is not ready. (Win32 error 0x15). VSS OTHER: ERROR: VSS failed to process snapshot: The shadow copy provider had an unexpected error while trying to process the specified operation. (VSS error 0x8004230f)

90108:save: Unable to save the SYSTEM STATE save sets: cannot create the snapshot. 86024:save: Error occured while saving disaster recovery save sets.

If SRP is offline, perform the following steps to bring it online: 1. In the WinPE command prompt, type diskpart and press Enter. 2. Run the following command to display the list of volumes:

DISKPART> list volume

3. Run the following command to select the volume that is offline: DISKPART> select volume_name

4. Run the following command to bring the selected volume online: DISKPART> online volume

(17)

Rollover requirements

Perform daily rollovers to avoid the following issues:

l Manual rollover of the snapshot fails.

l When you back up a save set with the snapshot policy 1/1/day/none, the process

applies retention and deletes the stale snapshot entry.

Protecting an environment before a disaster

To prepare for disaster recovery, back up application data and other necessary files. Procedure

1. Use NetWorker client to back up non-application data.

The NetWorker Release 8.2 SP1 Administration Guide provides details about using NetWorker client to back up the non-application files.

2. Create a NetWorker group without the Snapshot option enabled.

3. Create a NetWorker client resource, and assign it to the group that you created in step 2.

4. Configure the NetWorker client resource by typing All in the Save set field, and clearing the Backup command and Application information fields.

5. Perform a backup.

6. Use NMM to perform a full backup of application data.

The NetWorker Module for Microsoft Release 8.2 SP1 application specific user guides provide details about how to perform a full backup.

BMR by using NetWorker and NMM

From NMM 3.0 onwards, you must perform Windows file system backup and recovery by using the NetWorker client, and application-specific backup and recovery by using NMM. Specific information about how the backup and recovery process for various Microsoft applications in NMM 3.0 differs from previous NMM releases is provided in application-specific user guides.

NetWorker disaster recovery provides an automated BMR solution by using the Windows ASR writer and other VSS writers to identify critical volumes that are needed to perform a disaster recovery on a disabled system. BMR is performed offline, that is, when the Windows operating system is inactive. This avoids the necessity to manually reinstall Windows, and the problems that occur when operating system files are being restored to an active Windows system.

NMM 8.2 SP1 is compatible with the NetWorker 8.2 SP1 client, which provides a true BMR capability for Windows Server 2012, Windows Server 2008 R2, and Windows Server 2008. This capability is built into the NetWorker client and provides BMR support to the same or similar hardware. For Windows BMR, you should download the appropriate .iso recovery boot image file from EMC Online Support (https://support.emc.com). The ISO image provides a wizard that allows you to format disks, recover Windows critical volumes from backup, and reboot the server to bring it back online.

The Obtain the Windows Bare Metal Recovery wizard section in the NetWorker Release 8.2 SP1 Administration Guide provides information about how to download the NetWorker Windows BMR image.

Introduction

(18)

The Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide provides detailed information about how to use the NetWorker Windows BMR image to perform a BMR recovery on protected hosts and VMware virtual machines.

NOTICE

For all the Microsoft applications, after performing Windows disaster recovery and restarting the system, check all the disk and volume configurations. In most cases, the disks and volumes appear as on the original system.

However, it is possible, especially in BMR scenarios, that the volume or disk signatures do not match the original ones, and the non-critical volumes or disks are offline and not mounted. Use the Microsoft Disk Manager to bring the volumes and disks online, and then restart the system for drive letter reassignments. Assign the same drive letters that existed before the BMR. Non-critical volumes that the mount points access might have a similar issue.

(19)

CHAPTER 2 Microsoft Active Directory Backup and BMR

l Backing up an Active Directory for BMR... 20 l Performing BMR of an Active Directory...20

(20)

Backing up an Active Directory for BMR

Procedure

1. Create a backup group for Active Directory:

a. In the NetWorker Administrator window, click Configuration > right-click Groups > select New.

The Create Group dialog box appears.

b. In the Name field, type the name of the backup group. c. Click OK.

2. Create a client resource for Active Directory, and perform the backup:

a. In the NetWorker Administrator window, click Configuration > right-click Clients > select New.

The Create Client dialog box appears.

b. In the Name field, type the name of the client resource. c. Click OK.

3. Right-click the client and select Properties. 4. In the Client Properties dialog box:

a. On the General tab:

l In the Group list, select the group that you created in step 1. l In the Save set field, type All.

b. On the Apps & Modules tab, ensure that the Backup command and Application information fields are clear.

c. Specify other fields according to your requirements. d. Click OK.

5. Perform the backup.

Performing BMR of an Active Directory

Procedure

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide describes. The Performing post-recovery tasks for Active Directory services section in the NetWorker Release 8.2 SP1 Administration Guide provides information about how to perform an authoritative recovery of Active Directory.

2. Verify whether you can successfully log in as the domain administrator.

3. Verify whether all the Active Directory objects are present in both the Active Directory Users and the Computers and Domain Name System management.

(21)

CHAPTER 3 Microsoft SQL Server Backup and BMR

l SQL Server 2014, 2012, and 2008 R2...22 l SQL Server 2008 and 2005...27

(22)

SQL Server 2014, 2012, and 2008 R2

This section provides the BMR backup and recovery procedures for SQL Server 2014, 2012, and 2008 R2 by using the VDI technology in a cluster environment.

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the VDI

technology

You must configure a SQL Server client resource to back up SQL Server for BMR by using the VDI technology.

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the NMM Client Configuration

Wizard

Create separate client resources to back up application data and file system data which includes the DISASTER_RECOVERY:\ save set.

The By using the Client Configuration Wizard section in the NetWorker Module for Microsoft for SQL VDI Release 8.2 SP1 User Guide provides information about how to create a client resource to back up the application data.

The following procedure describes how to back up file system data. Procedure

1. In the Administration window of the NetWorker Management Console, perform one of the following steps:

l Click Configuration > Client Backup Configuration > New.

l Right-click the client and select Client Backup Configuration_>New.

2. On the Specify the Client Name and Type page:

a. In the Client name field, type the name of the client resource. b. Select Traditional NetWorker Client.

c. Click Next.

The wizard automatically detects the applications on the client that you have specified on the Specify the Client Name and Type page, and displays the list from which you can select the backup type.

3. On the Specify the Backup Configuration Type page: a. From the Available Applications list, select Filesystem. b. Click Next.

4. On the Specify the Client Backup Options page:

a. Select either a NetWorker volume pool or another target pool. If the Target Pool field is blank, the process does not associate the client with any pool.

b. Under Deduplication, select one of the following options:

l None —If you have not set up data deduplication.

l Data Domain backup—If you use a Data Domain device for data deduplication. l Avamar deduplication backup—If you use an Avamar device for data

(23)

c. Click Next.

5. On the Select Files to Backup page:

a. Select the save sets that you want to back up. Selecting the DISASTER_RECOVERY: \ save set automatically selects the dependent drives for the backup.

b. Click Next.

6. On the Select the Client Properties page:

a. Select browse policy, retention policy, and backup schedule for the backup from the respective drop-down lists.

b. In the Client Comment field, type a comment for the client resource. c. Click Next.

7. On the Choose the Backup Group page, select one of the following options and click Next:

l Add to an existing group—Select a group from the list.

After you select a group, if you use a storage node in the configuration setup, the Specify the Storage Node Options page appears.

l Create a new group—Perform the following steps: n In the Group Name field, type a name for the group. n In the Client Retries field, either select or type 0.

n In the Scheduled Backup Start Time field, specify the time at which the

scheduled backup must start.

n To automatically start the backup at the specified time, select Automatically

start the backup at the scheduled time. 8. On the Specify the Storage Node Options page:

a. Under Backup Storage Nodes, select one of the following options:

l Backup to NetWorker server only—If you do not use a NetWorker storage node. l Backup to the following storage nodes—If you use a NetWorker storage node.

Select the storage nodes. b. Click Next.

9. On the Backup Configuration Summary page, review the details and click Create to create a client resource.

The Check Results page appears with the details about the client resource that you have created.

10.To verify the details of the client, select the client and view the Client Properties page in the NMC.

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the NetWorker Administrator

program

This procedure uses the following sample SQL Server configuration:

l You have installed SQL Server on cluster volume P:\. l The cluster quorum drive is E:\.

l You have clustered all the drives except the C:\ drive in the cluster.

Microsoft SQL Server Backup and BMR

(24)

Note

The procedures apply to 2014, 2012, 2008, and 2005 versions also, in a cluster environment.

Procedure

1. Create a backup group for SQL Server:

2. Create a client resource to back up the DISASTER_RECOVERY:\ save set on the active node:

b. In the Name field, type the name of the active node. c. Click OK.

l In the Group list, select the group that you created in step 1. l In the Save set field, type DISASTER_RECOVERY:\.

b. Specify other fields according to your requirements. c. Click OK.

6. Perform step 2 and step 5 for the passive node.

7. Create a client resource with Windows cluster name to back up the All save set (quorum drive):

b. In the Name field, type the name of the Windows cluster. c. Click OK.

(25)

c. Click OK.

10.Perform the backup.

11.Create a client resource with SQL virtual name to back up the All save set (SQL cluster drives):

The Create Client dialog box appears. b. In the Name field, type the SQL virtual name. c. Click OK.

12.Right-click the client and select Properties. 13.In the Client Properties dialog box:

b. Specify other fields according to your requirements. c. Click OK.

15.Create a client resource with SQL virtual name to back up the SQL application data: a. In the NetWorker Administrator window, click Configuration > right-click Clients >

select New.

The Create Client dialog box appears. b. In the Name field, type the SQL virtual name. c. Click OK.

16.Right-click the client and select Properties. 17.In the Client Properties dialog box:

l In the Group list, select the group that you created in step 1.

l In the Save set field, type MSSQL: if the SQL instance is either the default

instance or a named instance in the cluster.

b. On the Apps & Modules tab, in the Backup command field, type nsrsqlsv. c. Specify other fields according to your requirements.

d. Click OK.

18.Create dummy client resources for the physical nodes of the cluster. 19.Perform the backup.

Performing BMR of a SQL Server 2014, 2012, or 2008 R2

The BMR process recovers C: drive only. It does not recover the SQL data, the quorum and SQL cluster drives, and the system databases such as master, msdb, and model.

(26)

Procedure

1. Separately recover the active and passive nodes by performing the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide describes.

2. Recover the cluster quorum database:

a. After you have started the active and passive nodes, ensure that the cluster disks are online on the active node in the Disk Management Console of the Windows GUI.

b. Add the quorum drive to Failover Cluster Management of the Cluster Configuration UI.

c. Select the storage node in Failover Cluster Management and ensure that the quorum disk is online.

d. On the SQL Server active node, start the NetWorker User program. e. Click Recover.

f. In the Source Client dialog box, select the source client with the Windows cluster name, and click OK.

g. In the Destination Client dialog box, select the destination client with the active node name, and click OK.

h. Select the quorum drive and recover the drive. 3. Recover the SQL cluster drives:

a. Add the SQL drives to Failover Cluster Management of the Cluster Configuration UI. b. Ensure that the disk is online.

c. Configure the drive mount points between the drives so that the mount points are the same as the mount points during the backup.

d. On the SQL Server active node, start the NetWorker User program. e. Click Recover.

f. In the Source Client dialog box, select the source client with the SQL virtual name and click OK.

g. In the Destination Client dialog box, select the destination client with the active node name and click OK.

h. Select all the SQL cluster drives and recover the drives. 4. Build the msdb and model databases:

a. Start the physical nodes of the cluster.

b. Ensure that you have the SQL Server installation software on the active node. c. In the software, go to the folder where the SETUP file exists and run the following

command:

Setup /QUIET/ACTION=REBUILDDATABASE/INSTANCENAME=<SQL

Server instance name>/SQLSYSADMINACCOUNTS=<Domain \administrator username>/IAcceptSQLServerLicenseTerms

5. In the Failover Cluster Management window of the Cluster Configuration UI, perform the following steps:

(27)

b. On the Dependencies tab, add all the SQL Server dependencies that you must bring online before you bring the SQL Server online. For example, any dependent cluster disk.

c. Bring the SQL virtual resources online. d. Bring the SQL Server online.

e. Perform the failover and ensure that the failover is successful.

To rebuild databases on SQL Server 2012, go to http://msdn.microsoft.com/en-us/library/dd207003.aspx

To rebuild databases on SQL Server 2008, go to http://msdn.microsoft.com/en-us/library/ms144259(v=sql.100).aspx

To rebuild databases on SQL Server 2005, go to http://msdn.microsoft.com/en-us/library/ms144259(v=sql.90).aspx

6. Restore the databases by using the NetWorker User for SQL Server program:

a. Start the NetWorker User for SQL Server program, and connect to the SQL virtual server instance.

b. Browse the backed up databases.

c. Select the databases and restore the databases.

SQL Server 2008 and 2005

This section provides the BMR backup and recovery procedures for SQL Server 2008 and 2005 by using the VSS technology in a standalone environment.

Backing up a SQL Server 2008 or 2005 for BMR by using the VSS technology

You must configure a SQL Server client resource to back up SQL Server for BMR by using the VSS technology.

Backing up a SQL Server 2008 or 2005 for BMR by using the NMM Client Configuration Wizard

Perform the procedures that the Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the NMM Client Configuration Wizard on page 22 section describes.

Backing up a SQL Server 2008 or 2005 for BMR by using the NetWorker Administrator program

Procedure

1. Create a backup group for SQL Server 2008 or 2005:

2. Create a client resource to back up the DISASTER_RECOVERY:\ save set:

(28)

l In the Group list, select the group that you have created in step 1. l In the Save set field, type DISASTER_RECOVERY:\.

b. On the Apps & Modules tab, ensure that the Backup command and Application information fields are clear.

6. Perform the All save set backup by using the NetWorker client. 7. For the backup group that you created in step 1:

a. Right-click the backup group and select Properties.

The Group Properties - <backup group name> dialog box appears. b. Select the Snapshot option.

c. Select the appropriate Snapshot Policy and Snapshot Pool from the respective lists.

d. Specify other fields according to your requirements. e. Click OK.

8. Create a client resource to back up the APPLICATIONS:\ SqlServerWriter save set: a. Perform step 2 and step 3.

The Client Properties dialog box appears. b. On the General tab:

l In the Group list, select the group that you have created in step 1. l In the Save set field, type APPLICATIONS:\ SqlServerWriter.

c. On the Apps & Modules tab:

l In the Backup command field, type nsrsnap_vss_save. l In the Application information field, type NSR_SNAP_TYPE=VSS.

Performing BMR of a SQL Server 2008 or 2005

The BMR process recovers only the C: drive. It does not recover the SQL data, quorum and SQL cluster drives, or the system databases such as master, msdb, and model.

Procedure

(29)

2. Start the NMM GUI.

3. Select the server and click Recover.

4. Under the APPLICATIONS save set, select SqlServerWriter. 5. Perform the recovery.

6. Ensure that the SQL Server service starts for the recovered instance.

7. To verify whether you have recovered the databases, open SQL Server Management Studio and connect to the instance. The databases that belong to the instance appear.

(30)

(31)

CHAPTER 4 Microsoft SharePoint Server Backup and BMR

l SharePoint Server 2013 and 2010...32 l SharePoint Server 2007...36

(32)

SharePoint Server 2013 and 2010

This section provides the BMR backup and recovery procedures for SharePoint Server 2013 and 2010.

Note

NMM 8.2 SP1 does not support the BMR backup and recovery of SharePoint 2013 and 2010 standalone servers with SQL embedded.

Backing up SharePoint Server 2013 or 2010 for BMR

Use the NetWorker Administrator program to create a SharePoint Server client resource to back up SharePoint Server for BMR.

The following table provides the sample SharePoint farm configuration that the procedures use.

Table 2 Sample SharePoint Server 2010 configuration

Components Operating

system Applicationversion Critical volume NetWorkerbuild

SQL Server Windows Server 2008 R2 SP1 SQL Server 2008 R2 SP1 l _{SQL application is} installed on the C: drive. l _{Databases reside on} the C: drive. NetWorker 8.2 SP1 Web front-end server 1 Windows Server 2008 R2 SP1 SharePoint Server 2010 SP1 SharePoint Server 2010 Application is installed on C: drive. NetWorker 8.2 SP1 Web front-end server 2 Windows Server 2008 R2 SP1 SharePoint Server2010 SP1 SharePoint Application is installed on the E: drive. So, the critical volumes are the C: and E: drives.

NetWorker 8.2 SP1

Backing up SharePoint Server 2010 includes backing up SQL Server, Web front-end server 1, and Web front-end server 2.

Backing up SQL Server in a SharePoint Server 2010 environment

Procedure

1. Create the first backup group for the SQL Server:

You have created the first backup group.

(33)

d. Right-click the backup group and select Properties.

The Group Properties - <backup group name> dialog box appears. e. Do not select Snapshot.

f. Specify other fields according to your requirements. g. Click OK.

2. Create the first client resource for the SQL Server:

You have created the first client resource. d. Right-click the client and select Properties.

The Client Properties dialog box appears. e. On the General tab:

l Ensure that you have selected Scheduled backup.

4. Create the second backup group for the SQL Server: a. Perform step a through step d of step 1.

b. Select Snapshot.

5. Create the second client resource for the SQL Server: a. Perform step a through step d of step 2.

b. On the General tab:

l Ensure that you have selected Scheduled backup.

l In the Group list, select the group that you created in step 4. l In the Save set field, type APPLICATIONS:\SqlServerWriter.

l In the Backup command field, type nsrsnap_vss_save. l In the Application information field, type NSR_SNAP_TYPE=vss.

Microsoft SharePoint Server Backup and BMR

(34)

Backing up web front-end server 1

Procedure

1. Create the first backup group for the web front-end server 1:

a. Perform step a through step d of step 1 in Backing up SQL Server in a SharePoint Server 2010 environment on page 32.

b. Do not select Snapshot.

2. Create the first client resource for the web front-end server 1:

4. Create the second backup group for the web front-end server 1:

b. Select Snapshot.

5. Create the second client resource for the web front-end server 1:

l In the Save set field, type APPLICATIONS:\Microsoft Office SharePoint

Services.

l In the Backup command field, type nsrsnap_vss_save. l In the Application information field, type NSR_SNAP_TYPE=vss.

(35)

Backing up web front-end server 2

Perform step 1 through step 6 in Backing up web front-end server 1 on page 34 to perform the BMR backup of web front-end server 2.

Performing BMR of SharePoint Server 2013 or 2010

The following sections describe the recovery procedures for SQL Server, web front-end server 1, and web front-end server 2.

Recovering SQL Server in a SharePoint 2010 environment

Note

The failure of a SQL master database recovery leads to the failure of the SharePoint disaster recovery. To proceed with recovery, move, rename, or delete the specified database files and perform the recovery from that point. The associated files are the master database file master.mdf, and the master log file mastlog.ldf.

Procedure

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide describes. 2. After SQL Server restarts:

a. Start the NMM GUI.

b. Select the server and click Recover.

c. In the APPLICATIONS save set, select SqlServerWriter. d. Perform the recovery.

e. Restart the machine if prompted.

f. Start the SQL Server service and verify whether all instances have started.

Recovering the web front-end servers

Procedure

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide describes. 2. After web front-end server restarts:

b. Select the server, and click Recover to recover the SharePoint configuration data. Use the NetWorker client to recover any other backed up file system drives. Ensure that the DISASTER_RECOVERY:\ save set is visible in the NetWorker client UI. c. Restart the machine if prompted.

d. In the APPLICATIONS save set, select the SharePoint save sets, and perform the recovery.

(36)

SharePoint Server 2007

This section provides the BMR backup and recovery procedures for SharePoint Server 2007.

Note

NMM 8.2 SP1 does not support the BMR backup and recovery of SharePoint 2007 standalone server with SQL embedded.

Backing up SharePoint Server 2007 for BMR

Use the NetWorker Administrator program to create a SharePoint Server client resource to back up SharePoint Server 2007 for BMR.

The procedures use the following SharePoint Server 2007 configuration on Windows 2008 R2:

l You have configured the target machine with four processors and 8 GB of RAM. l You have configured the environment with a single NIC.

l You have installed Windows 2008 R2 SP1 and updates on the C:\ drive. l The snapshot policy is 1\0\day\All (RolloverOnly policy).

l The NetWorker client performs the BMR backup by using non-snapshot. l The NMM client backs up the following save sets by using the VSS writer based

snapshot:

n APPLICATIONS:\Microsoft Office SharePoint Services n APPLICATIONS:\SQLServerWriter

Procedure

1. Create a backup group for the SharePoint Server:

You have created the backup group.

The Group Properties - <backup group name> dialog box appears.

l Select Snapshot.

l In the Snapshot Policy field, type either 11dayAll or 10dayAll.

e. Specify other fields according to your requirements. f. Click OK.

2. Create a client resource to back up the APPLICATIONS:\Microsoft Office SharePoint Services save set:

(37)

You have created the client resource. d. Right-click the client and select Properties.

l In the Save set field, type APPLICATIONS:\Microsoft Office SharePoint

Services.

3. Perform the backup on all machines in the SharePoint environment.

4. Create a client resource to back up the APPLICATIONS:\SqlServerWriter save set: a. Perform step a through step d of step 2.

l In the Group list, select the group that you created in step 1. l In the Save set field, type APPLICATIONS:\SqlServerWriter.

5. Perform the backup on all machines in the SharePoint environment. 6. Create a client resource to back up a non-critical volume:

a. Perform step a through step d of step 2. b. On the General tab:

l In the Save set field, type a volume drive letter other than critical volumes, for

example, D:\.

7. Perform the backup on all machines in the SharePoint environment. 8. Create a client resource to back up the DISASTER_RECOVERY:\ save set:

9. Perform backups on all machines in the SharePoint environment.

(38)

Performing BMR of SharePoint Server 2007

Procedure

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide describes. 2. After the machine restarts:

b. Select the server and click Recover. c. Select the following save sets:

l APPLICATIONS:\SqlServerWriter

l APPLICATIONS:\Microsoft Office SharePoint Services

d. Perform the recovery.

(39)

CHAPTER 5 Microsoft Exchange Server Backup and BMR

l Exchange Server 2013...40 l Exchange Server 2010...43 l Exchange Server 2007...45

(40)

Exchange Server 2013

This section provides the BMR backup and recovery procedures for Exchange Server 2013.

Backing up Exchange Server 2013 for BMR

You must configure an Exchange Server client resource to back up Exchange Server 2013 for BMR.

Backing up Exchange Server 2013 by using the NMM Client Configuration Wizard

Separately create a client resource to back up the application data and the file system data which includes the DISASTER_RECOVERY:\ save set.

The Create a client resource using the Client Configuration Wizard section in the NetWorker Module for Microsoft for Exchange Server VSS Release 8.2 SP1 User Guide provides information about how to create a client resource to back up the application data.

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the NMM Client Configuration Wizard on page 22 provides information about how to create a client resource to back up the file system data.

Backing up Exchange Server 2013 by using the NetWorker Administrator program

The following figure illustrates the sample configuration that the procedures use.

Figure 1 Sample configuration for BMR backups of Exchange Server 2013

Create two client resources for the Database Availability Group (DAG) node. You use one client resource to back up the system data (critical volumes) and the other client to back up the application data (non-critical volumes).

Procedure

1. Create a backup group for system backup:

(41)

2. Create a client resource for system backup:

l In the Group list, select the group that you created for system backup. l In the Save set field, type DISASTER_RECOVERY:\.

If you have installed Exchange Server 2013 on a drive other than the system drive, type the drive letter also. For example, E:\.

f. On the Apps & Modules tab, ensure that the Backup command and Application information fields are clear.

g. Specify other fields according to your requirements. h. Click OK.

3. Back up the system data.

4. Ensure that the backup successfully completes. 5. Create a backup group for application backup:

a. Perform step a through step d of step 1. b. Select Snapshot.

6. Create a client resource for application backup: a. Perform step a through step d of step 2. b. On the General tab:

l In the Group list, select the group that you created for application backup. l In the Save set field, type the save set. For example, APPLICATIONS:

\Microsoft Exchange 2013. c. On the Apps & Modules tab:

Microsoft Exchange Server Backup and BMR

(42)

l In the Backup command field, type nsrsnap_vss_save. l In the Application information field, type the following:

NSR_SNAP_TYPE=vss

NSR_ALT_PATH=<C:\Temp location>

NSR_EXCH2010_BACKUP=<Active/Passive/All> or NSR_EXCH_BACKUP=<Active/Passive/All >

NSR_EXCH2010_DAG=<Dag Client Instance> or NSR_EXCH_DAG=<Dag Client Instance>

7. Back up the application data.

8. Ensure that the backup successfully completes.

Performing BMR of Exchange Server 2013

Run the following command to mount the database:

mount-database -identity <database name> -force Procedure

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide describes. 2. If you have installed Exchange Server 2013 on a drive other than the system drive, use

the NetWorker client to recover the drive. During the recovery, if the Naming Conflict dialog box appears as shown in the following figure, select Rename the Recover File and click OK.

Figure 2 Naming conflict

3. After the recovery completes, restart the machine to start all the Exchange services. 4. After the machine restarts, ensure that you meet the following requirements:

a. You have recovered all the critical volumes.

(43)

c. You have selected a database, and performed recovery.

d. You have successfully mounted the database after the recovery, and checked whether the recovery process has successfully recovered all emails.

Exchange Server 2010

Backing up Exchange Server 2010 for BMR

Backing up Exchange Server 2010 for BMR by using the NMM Client Configuration Wizard

Perform the procedures that the Backing up Exchange Server 2013 by using the NMM Client Configuration Wizard on page 40 section describes.

Backing up Exchange Server 2010 for BMR by using the NetWorker Administrator program

The following figure illustrates the sample configuration that the procedures use.

Figure 3 Sample configuration for BMR backups of Exchange Server 2010

Create two client resources for the Database Availability Group (DAG) node. You use one client resource to back up the system data (critical volumes) and the other client to back up the application data (non-critical volumes).

Procedure

1. Create a backup group for system backup:

The Group Properties - <backup group name> dialog box appears.

(44)

e. Do not select Snapshot.

2. Create a client resource for system backup:

l In the Group list, select the group that you created for system backup. l In the Save set field, type DISASTER_RECOVERY:\.

If you have installed Exchange Server 2010 on a drive other than the system drive, type the drive letter also. For example, E:\.

f. On the Apps & Modules tab, ensure that the Backup command and Application information fields are clear.

g. Specify other fields according to your requirements. h. Click OK.

3. Back up the system data.

4. Ensure that the backup successfully completes. 5. Create a backup group for application backup:

a. Perform step a through step d of step 1. b. Select the Snapshot option.

6. Create a client resource for application backup: a. Perform step a through step d of step 2. b. On the General tab:

l In the Group list, select the group that you created for application backup. l In the Save set field, type the save set. For example, APPLICATIONS:\Microsoft

Exchange 2010.

l In the Backup command field, type nsrsnap_vss_save.

(45)

NSR_ALT_PATH=<C:\Temp location>

NSR_EXCH2010_BACKUP=<Active/Passive/All> NSR_EXCH2010_DAG=<Dag Client Instance> d. Specify other fields according to your requirements. e. Click OK.

7. Back up the application data.

8. Ensure that the backup successfully completes.

Performing BMR of Exchange Server 2010

Run the following command to mount the database:

mount-database -identity <database name> -force Procedure

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide describes. 2. After the machine restarts, ensure that you meet the following requirements:

a. You have recovered all the critical volumes.

b. You have created all the non-critical volumes with the exact drive letters that the volumes had before the disaster.

c. You have selected a database and performed recovery.

d. You have successfully mounted the database after the recovery, and checked whether the recovery process has successfully recovered all emails.

Exchange Server 2007

Backing up Exchange Server 2007 for BMR

Backing up Exchange Server 2007 for BMR by using the NMM Client Configuration Wizard

Perform the procedures that the Backing up Exchange Server 2013 by using the NMM Client Configuration Wizard on page 40 section describes.

(46)

Backing up Exchange Server 2007 for BMR by using the NetWorker Administrator program

The following figure illustrates the sample CCR configuration that the procedures use.

Figure 4 Sample configuration for BMR backups of Exchange Server 2007 SP3 Rollup5

Procedure

1. Create a backup group to back up critical volumes on the active node:

2. Create a client resource for the backup group to back up critical volumes on the active node:

l In the Group list, select the group that you created to back up critical volumes

on the active node.

l In the Save set field, type DISASTER_RECOVERY:\.

(47)

4. Perform step 1 to create a backup group to back up critical volumes on the passive node.

5. Perform step 2 to create a client resource for the backup group to back up critical volumes on the passive node.

7. Create a backup group for the Exchange virtual server instance to perform Exchange Server 2007 Writer-Level backups on the active node client instance:

a. Perform step a through step d of step 1. b. Select Snapshot.

8. Create the Exchange virtual server active node client instance: a. Perform step a through step d of step 2.

l In the Group list, select the group that you created to back up the Exchange

virtual server instance on the active node.

l In the Save set field, type Applications:\Microsoft Exchange 2007.

NSR_ALT-Path=C:\RM_MountPOINT NSR_VIRT_SERV=Exch2k7Virtual NSR_INDEX_CLIENT=Exch2k7Virtual

10.Perform step 7 to create a backup group for the Exchange virtual server instance to perform Exchange Server 2007 Writer-Level backups on the passive node client instance.

11.Create the Exchange virtual server passive node client instance: a. Perform step a and step b of step 8.

b. On the Apps & Modules tab:

NSR_ALT-Path=C:\RM_MountPOINT

(48)

Performing BMR of Exchange Server 2007

Procedure

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide describes, for the passive node client machine. Repeat these steps for the active node client machine.

2. After both the machines restart:

a. Create partitions and provide the same drive letters to the non-critical volumes where Exchange logs and databases existed.

b. On the current active node, start the NMM GUI.

c. Go to Recover > Exchange Recover Session > Database Recover. Run the following command to mount the database:

mount-database -identity <database name> -force

d. Select the storage groups and perform the conventional point-in-time recovery to bring the Exchange storage groups back online. The NetWorker Module for Microsoft Release 8.2 SP1 Administration Guide provides information about conventional point-in-time recovery.

(49)

CHAPTER 6 Microsoft Hyper-V Backup and BMR

l Backing up Hyper-V for BMR... 50 l Performing BMR of Hyper-V...52

(50)

Backing up Hyper-V for BMR

You must configure a Hyper-V client resource to back up Hyper-V for BMR.

Backing up Hyper-V for BMR by using the NMM Client Configuration Wizard

Separately create a client resource to back up the application data and the file system data which includes the DISASTER_RECOVERY:\ save set.

The By using the Client Configuration Wizard section in the NetWorker Module for Microsoft for Hyper-V VSS Release 8.2 SP1 User Guide provides information about how to create a client resource to back up the application data.

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the NMM Client Configuration Wizard on page 22 provides information about how to create a client resource to back up the file system data.

Backing up Hyper-V for BMR by using the NetWorker Administrator program

The procedures use the following sample Hyper-V configuration on a Windows server:

l Physical Node1: nmm-csv-node1 l Physical Node2: nmm-csv-node2 l Virtual Server: nmm-csv-cluster

Procedure

1. Create a backup group for Hyper-V:

2. Create a client resource to backup the Hyper-V application data that the non-CSV volumes host:

b. In the Name field, type the name of the physical node. c. Click OK.

l In the Group list, select the group that you created in step 1. l In the Save set field, type APPLICATIONS:\Microsoft Hyper-V.

(51)

g. Click OK.

3. Perform the backup on all Hyper-V cluster nodes.

4. Create a client resource to backup the Hyper-V application data that the CSV volumes host:

b. In the Name field, type the name of the virtual node. c. Click OK.

You have created the client resource. d. Right-click the client, and select Properties.

l In the Group list, select the group that you created in step 1. l In the Save set field, type APPLICATIONS:\Microsoft Hyper-V.

The process backs up only the virtual machines that the CSV hosts. You must have registered the CSV in the Cluster Manager.

6. Create a client resource to backup the non-critical volumes: a. Perform step a through step d of step 2.

l In the Save set field, type a volume drive letter other than critical volumes, for

example, D:\.

7. Perform the backup on all Hyper-V cluster nodes. 8. Create a client resource to backup the All save set:

9. Perform the backup on all Hyper-V cluster nodes.

Microsoft Hyper-V Backup and BMR

(52)

Performing BMR of Hyper-V

Ensure that the cluster service account is enabled. Otherwise, the explorer hangs when you browse CSVs and the recovery fails.

To enable the cluster service computer account, log in to the Domain Controller with the domain administrator credentials, and use the Active Directory Users and Computer snap-in.

Procedure

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 SP1 Administration Guide describes. After the recovery completes, the status of Hyper-V VMs in the Failover Cluster Manager window are either Pending or Failed.

2. Reconfigure quorum and cluster storage (CSV and non-CSV volumes): a. Create or configure the quorum, CSV, and non-CSV shared volumes. b. Ensure that you have documented the drive letters for quorum and non-CSV

(shared volume) and used here.

c. Ensure that you have configured the same CSV volume name as the original. 3. Recover all Hyper-V cluster nodes by using the NMM client.

4. Reconfigure the VMs with either the Pending or the Failed status.

5. Recover the Hyper-V VMs that the CSV volumes host with the virtual node as the client resource, by using the NMM client.

6. Recover the Hyper-V VMs that the non-CSV volumes host with the physical node as the client resource, by using the NMM client.

(53)

CHAPTER 7 Microsoft System Center Virtual Machine

Manager Backup and BMR

l Backing up System Center Virtual Machine Manager for BMR... 54 l Performing BMR of a System Center Virtual Machine Manager... 56

EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution

EMC

®

NetWorker

®

Module for

Microsoft for Windows Bare Metal

Recovery Solution

User Guide

CONTENTS

FIGURES

TABLES

Preface

CHAPTER 1

Introduction

Bare Metal Recovery overview

System requirements

Supported operating systems

Supported Microsoft applications

NetWorker software version requirements

Microsoft BMR requirements

CPU requirements

Hard disk requirements

NIC driver requirements

Critical and noncritical volume requirements

System Reserved Partition requirements

Rollover requirements

Protecting an environment before a disaster

BMR by using NetWorker and NMM

CHAPTER 2

Microsoft Active Directory Backup and BMR

Backing up an Active Directory for BMR

Performing BMR of an Active Directory

CHAPTER 3

Microsoft SQL Server Backup and BMR

SQL Server 2014, 2012, and 2008 R2

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the VDI

technology

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the NMM Client Configuration

Wizard

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the NetWorker Administrator

program

Performing BMR of a SQL Server 2014, 2012, or 2008 R2

SQL Server 2008 and 2005

Backing up a SQL Server 2008 or 2005 for BMR by using the VSS technology

Backing up a SQL Server 2008 or 2005 for BMR by using the NMM Client Configuration Wizard

Backing up a SQL Server 2008 or 2005 for BMR by using the NetWorker Administrator program

Performing BMR of a SQL Server 2008 or 2005

CHAPTER 4

Microsoft SharePoint Server Backup and BMR

SharePoint Server 2013 and 2010

Backing up SharePoint Server 2013 or 2010 for BMR

Backing up SQL Server in a SharePoint Server 2010 environment

Backing up web front-end server 1

Backing up web front-end server 2

Performing BMR of SharePoint Server 2013 or 2010

Recovering SQL Server in a SharePoint 2010 environment

Recovering the web front-end servers

SharePoint Server 2007

Backing up SharePoint Server 2007 for BMR

Performing BMR of SharePoint Server 2007

CHAPTER 5

Microsoft Exchange Server Backup and BMR

Exchange Server 2013

Backing up Exchange Server 2013 for BMR

Backing up Exchange Server 2013 by using the NMM Client Configuration Wizard

Backing up Exchange Server 2013 by using the NetWorker Administrator program

Performing BMR of Exchange Server 2013

Exchange Server 2010

Backing up Exchange Server 2010 for BMR

Backing up Exchange Server 2010 for BMR by using the NMM Client Configuration Wizard

Backing up Exchange Server 2010 for BMR by using the NetWorker Administrator program

Performing BMR of Exchange Server 2010

Exchange Server 2007

Backing up Exchange Server 2007 for BMR

Backing up Exchange Server 2007 for BMR by using the NMM Client Configuration Wizard

Backing up Exchange Server 2007 for BMR by using the NetWorker Administrator program

Performing BMR of Exchange Server 2007

CHAPTER 6

Microsoft Hyper-V Backup and BMR