EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution

(1)

EMC

®

NetWorker

®

Module for Microsoft for Windows

Bare Metal Recovery Solution

Release 8.2

User Guide

(2)

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. EMC2_{, 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.

(3)

EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution Release 8.2 User Guide 3

Preface

Revision History

Chapter 1 Overview

Bare Metal Recovery overview ... 12

Terminology ... 13

How BMR works with NetWorker and NMM ... 14

Recommendations ... 14

Chapter 2 Bare Metal Recovery

Protecting the application data before a disaster... 18

Using NetWorker for performing BMR ... 18

Chapter 3 Bare Metal Recovery of Microsoft Active Directory

Active Directory... 20

Backing up Active Directory for BMR ... 20

BMR of Active Directory ... 21

Chapter 4 Bare Metal Recovery of Microsoft SQL Server

SQL Server 2014, 2012, and 2008 R2 ... 24

Backing up SQL Server for BMR by using the VDI technology ... 24

BMR of SQL Server 2012 or 2008 R2... 29

SQL Server 2008 and 2005 ... 32

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

BMR of SQL Server 2008 or 2005 ... 34

Chapter 5 Bare Metal Recovery of Microsoft SharePoint Server

SharePoint Server 2013 and 2010 ... 36

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

BMR of SharePoint Server 2013 or 2010... 39

SharePoint Server 2007 ... 40

Backing up SharePoint Server 2007 for BMR ... 40

(4)

Contents

Chapter 6 Bare Metal Recovery of Microsoft Exchange Server

Exchange Server 2013 ... 44

Backing up Exchange Server 2013 for BMR... 44

BMR of Exchange Server 2013... 46

Chapter 7 Bare Metal Recovery of Microsoft Hyper-V

Hyper-V... 56

Backing up Hyper-V for BMR... 56

BMR of Hyper-V ... 58

Chapter 8 Bare Metal Recovery of Microsoft System Center Virtual Machine

Manager

Overview... 62

Virtual Machine Manager server ... 63

Backing up VMM server for BMR... 63

BMR of VMM server ... 63

Virtual Machine Manager library... 64

Backing up VMM library for BMR... 64

BMR of VMM library... 64

Virtual Machine Manager database ... 64

Backing up VMM database for BMR... 64

BMR of VMM database ... 65

Virtual Machine Manager environment ... 66

Protecting data on Hyper-V virtual machines ... 66

(5)

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:

◆ EMC NetWorker software

◆ EMC NetWorker snapshot management

◆ Microsoft Volume Shadow Copy Service (VSS) technology

Conventions used in this document

EMC uses the following conventions for special notices:

NOTICE is used to address practices not related to personal injury.

Note: A note presents information that is important, but not hazard-related. EMC NetWorker Module for Microsoft for

Hyper-V VSS Release 8.2 User Guide Contains information about backup and recovery of Hyper-V Server VSS by using EMC NetWorker Module for Microsoft.

8.2 Advanced Recovery Guide Provides supplemental information about using NMM for backup and recovery of all supported Microsoft applications. Use this guide along with application-specific user guides for backup and recovery information.

EMC NetWorker Performing backup and recovery of SharePoint Server by using NetWorker Module for Microsoft SQL VDI solution Release 8.2 Technical Notes

Provides information for performing backup and recovery of a SharePoint Server by using the SQL Server Virtual Device Interface (VDI) technology and the SharePoint VSS Writer with NMM.

EMC NetWorker Performing Exchange Server Granular Recovery by using NetWorker Module for Microsoft with Ontrack PowerControls Release 8.2 Technical Notes

Provides information about using NMM with Ontrack PowerControls to perform granular level recovery (GLR) of deleted Microsoft Exchange Server mailboxes, public folders, and public folder mailboxes.

EMC NetWorker SharePoint BLOB Backup and Recovery by using NetWorker Module for Microsoft and Metalogix StoragePoint Release 8.2 Technical Notes

Provides information about backup and recovery of SharePoint Binary Large Objects (BLOB) by using EMC NetWorker Module for Microsoft release 8.2 and Metalogix StoragePoint.

EMC NetWorker Cloning Integration Guide Contains planning, practices, and configuration information for using the NetWorker, NMM, and NMDA cloning feature.

EMC NetWorker Licensing Guide Contains information about licensing NetWorker and its modules.

EMC NetWorker Online Software Compatibility

Guide Provides a list of supported client, server, and storage node operating systems for the following software products: NetWorker and NetWorker application modules and options (including deduplication and virtualization support), AlphaStor, Data Protection Advisor, and HomeBase.

EMC NetWorker and EMC Data Domain

Deduplication Devices Integration Guide Contains planning and configuration information on the use of Data Domain devices for data deduplication backup and storage in a NetWorker environment.

EMC NetWorker and EMC Avamar Integration

Guide Contains planning and configuration information on the use of Avamar in a NetWorker environment. Table 1 EMC publications for additional information (page 2 of 2)

(7)

Preface

Typographical conventions

EMC uses the following type style conventions in this document:

Where to get help

EMC support, product, and licensing information can be obtained as follows: Product information — For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at:

https://support.emc.com

Technical support — Go to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. Online communities — Visit EMC Community Network https://community.EMC.com/ for peer contacts, conversations, and content on product support and solutions. Interactively engage online with customers, partners, and certified professionals for all EMC products.

Your comments

Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

[email protected]

Bold Use for names of interface elements, such as names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user specifically selects or clicks)

Italic Use for full titles of publications referenced in text

Monospace Use for:

• System output, such as an error message or script • System code

• Pathnames, filenames, prompts, and syntax • Commands and options

Monospace italic Use for variables.

Monospace bold Use for user input.

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections — the bar means “or”

{ } Braces enclose content that the user must specify, such as x or y or z

(8)

(9)

REVISION HISTORY

Email your clarifications or suggestions for this document to: [email protected]

The following table presents the revision history of this document.

Revision Date Description of added or changed sections

(10)

(11)

Overview 11

CHAPTER 1 Overview

This chapter includes the following sections:

◆ Bare Metal Recovery overview ... 12

◆ Terminology ... 13

◆ How BMR works with NetWorker and NMM ... 14

(12)

Overview

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. Windows BMR support is available on the following platforms:

◆ Windows Server 2012 R2 (x64) ◆ Windows Server 2012 (x64)

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

You can use the BMR support for the following Microsoft applications:

(13)

Terminology 13

Overview

◆ SQL Server 2005 ◆ Active Directory

◆ System Center Virtual Machine Manager

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

For BMR support, you must have installed NetWorker server 7.6 SP3 or later, NetWorker client 8.2, and NetWorker Management Console 8.2 or later along with NMM 8.2.

Terminology

This section defines terms that are used in this document to describe NetWorker support for Windows BMR.

◆ Application data — User data such as a log file that is created by the application, or

user data such as an application database that is created with the application. For example, an SQL Server’s application data includes its databases and log files. Application data is neither included in nor recoverable from a Windows BMR operation. Application data must be backed up and recovered with NMM.

◆ ASR Writer — The Volume Shadow Copy Service (VSS) writer that is responsible for

identifying critical data that is needed to perform an offline restore.

◆ Boot Configuration Data (BCD) — The BCD store contains boot configuration

parameters, and controls how Microsoft Windows Server 2008 operating system starts. A backup of this ASR Writer component is required to perform an offline restore.

◆ Critical Volume — A critical volume includes:

• Any volume that contains system state files or files for an installed service, including volumes mounted as NTFS directories that contain such files. An example of an installed service is the Exchange 2010 application binaries. However, the Exchange database and log files are not considered critical. • Any parent volume where a critical volume is mounted.

• All volumes on all dynamic disks if at least one of those volumes is critical. • A current backup of all critical volumes that is required to perform a Windows BMR.

◆ Disaster recovery — The restoration of a computer operating system and its data after

a catastrophic failure such as a hard disk failure or the corruption of critical operating system components. A disaster recovery might not be a bare metal recovery.

◆ NetWorker Windows BMR image — A bootable image that contains NetWorker binaries

and a wizard to control the Windows BMR process.

◆ Non-critical volume — A volume that contains files that are not part of the system state

(14)

Overview

◆ Offline restore — A restore operation that is performed from the NetWorker Windows

Disaster Recovery boot image. An offline restore is an automated process, and does not require the manual installation of an operating system. A BMR is an offline restore.

◆ Online restore — A restore operation that is performed from the regular NetWorker

recover user interface. An online restore requires that the computer has been booted from an installed operating system.

How BMR works with 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 is compatible with the NetWorker 8.2 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 Administration Guide provides information about how to download the NetWorker Windows BMR image.

The NetWorker Release 8.2 Administration Guide provides information about how to use NetWorker for Windows BMR. Review the information in the guide before proceeding with the procedures in this document.

Recommendations

(15)

Recommendations 15

Overview

◆ You can use the NetWorker Windows BMR 32-bit ISO image to recover an x86

operating system on either an x86 or x64 computer. You can use the NetWorker Windows BMR 64-bit ISO image to recover only an x64 operating system on an x64 computer.

◆ Review and follow these CPU guidelines:

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

Interface (UEFI) must match.

• 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.

• You can restore the backup of an x86 operating system version only to an x86 processor computer.

• You can restore the backup of an x64 operating system version only to an x64 processor computer.

◆ Review and follow these hard disk requirements:

• 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.

• 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.

• 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.

• 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.

• Ensure that the RAID setup on destination computer does not interfere with the disk order of the hard disks.

◆ After a Windows BMR recovery, if you want to use different Network Interface Card

(NIC), you must install new NIC drivers that match the NIC in the new computer after Windows boots on the new server.

◆ 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.

(16)

Overview

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

HKLM\System\CurrentControlSet\Control\SystemWriter\ReportWin32ServicesNonSys temState 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.

◆ 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:

(17)

Bare Metal Recovery 17

CHAPTER 2 Bare Metal Recovery

(18)

Bare Metal Recovery

Protecting the application data before a disaster

To prepare for disaster recovery, back up application data and other files: 1. Use NetWorker client to back up non-application data.

The NetWorker Release 8.2 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 specifying 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 application specific user guides provide details about how to perform a full backup.

Using NetWorker for performing BMR

NetWorker provides a bootable Windows BMR image that contains NetWorker binaries and a wizard to control the disaster recovery process.

The Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 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.

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.

(19)

Bare Metal Recovery of Microsoft Active Directory 19

CHAPTER 3 Bare Metal Recovery of Microsoft Active Directory

This chapter includes the following section:

(20)

Bare Metal Recovery of Microsoft Active Directory

Active Directory

This section provides the BMR backup and recovery procedures for Active Directory.

Backing up Active Directory for BMR

Perform the following steps to back up Active Directory for BMR: 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, specify 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, specify the name of the client resource. c. Click OK.

3. Right-click the client and select Properties.

In the Client Properties dialog box, perform the following steps: a. On the General tab:

– In the Group list, select the group that you created in step 1. – In the Save set field, specify 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.

(21)

Active Directory 21

Bare Metal Recovery of Microsoft Active Directory

BMR of Active Directory

Perform the following steps to perform the BMR of Active Directory:

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 Administration Guide describes. The Performing post-recovery tasks for Active Directory services section in the NetWorker Release 8.2 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.

(22)

(23)

Bare Metal Recovery of Microsoft SQL Server 23

CHAPTER 4 Bare Metal Recovery of Microsoft SQL Server

(24)

Bare Metal Recovery of Microsoft SQL Server

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 SQL Server 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.

Configuring an SQL Server client resource

Use one of the following methods to create a client resource:

◆ “By using the Client Configuration Wizard” on page 24 ◆ “By using the NetWorker Administrator program” on page 26

By using the Client Configuration Wizard

You should separately create a client resource for backing up the application data and the file system data which includes the DISASTER_RECOVERY: save set.

Creating a client resource to back up the application data

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

Creating a client resource to back up the file system data

Perform the following steps to create a client resource to back up the file system data: 1. In the Administration window of the NetWorker Management Console, perform one of

the following steps:

• Click Configuration > Client Backup Configuration > New.

• Right-click the client and from the menu that appears, click Client Backup Configuration > New.

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

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

c. Click Next.

(25)

SQL Server 2014, 2012, and 2008 R2 25

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: – None —If you have not set up data deduplication.

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

deduplication. After you select this option, choose the Avamar node from the available list.

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, specify 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:

• 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.

• Create a new group—Perform the following steps:

– In the Group Name field, specify a name for the group. – In the Client Retries field, either select or specify 0.

– In the Scheduled Backup Start Time field, specify the time at which the scheduled backup must start.

(26)

8. On the Specify the Storage Node Options page:

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

– Backup to NetWorker server only—If you do not use a NetWorker storage node. – 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.

By using the NetWorker Administrator program

The procedures use the following sample SQL Server configuration:

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

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

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

Perform the following steps to back up SQL Server for BMR: 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.

(27)

SQL Server 2014, 2012, and 2008 R2 27

4. In the Client Properties dialog box, perform the following steps: a. On the General tab:

– In the Group list, select the group that you created in step 1. – In the Save set field, specify DISASTER_RECOVERY:\. b. Specify other fields according to your requirements. c. Click OK.

5. Perform the backup.

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, specify the name of the Windows cluster. c. Click OK.

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

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

b. In the Name field, specify the SQL virtual name. c. Click OK.

(28)

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.

b. In the Name field, specify the SQL virtual name. c. Click OK.

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

– In the Save set field, specify MSSQL: if the SQL instance is either the default instance or a named instance in the cluster.

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

d. Click OK.

(29)

SQL Server 2014, 2012, and 2008 R2 29

BMR of SQL Server 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.

Perform the following steps to perform the BMR of SQL Server 2008 R2:

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 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, as shown in Figure 1 on page 29.

Figure 1 Quorum drive configuration in Failover Cluster Management

(30)

Figure 2 Quorum drive statistics on the Storage page in Failover Cluster Management

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.

(31)

SQL Server 2014, 2012, and 2008 R2 31

b. Ensure that the disk is online as shown in Figure 4 on page 31.

Figure 4 Viewing disk drive status in Failover Cluster Management

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

(32)

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

a. Open the SQL Server Properties dialog box.

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

Configuring a SQL Server client resource

(33)

SQL Server 2008 and 2005 33

By using the NetWorker Administrator program

To back up SQL Server 2008 or 2005 for BMR:

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

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

– In the Group list, select the group that you have created in step 1. – In the Save set field, specify 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, perform the following steps: 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.

(34)

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:

– In the Group list, select the group that you have created in step 1. – In the Save set field, specify APPLICATIONS:\ SqlServerWriter. c. On the Apps & Modules tab:

– In the Backup command field, specify nsrsnap_vss_save.

– In the Application information field, specify NSR_SNAP_TYPE=VSS. d. Specify other fields according to your requirements.

e. Click OK. 9. Perform the backup.

BMR of SQL Server 2008 or 2005

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.

To perform the BMR of SQL Server 2008:

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 Administration Guide describes. 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.

(35)

Bare Metal Recovery of Microsoft SharePoint Server 35

CHAPTER 5 Bare Metal Recovery of Microsoft SharePoint

Server

(36)

Bare Metal Recovery of Microsoft SharePoint Server

SharePoint Server 2013 and 2010

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

NMM 8.2 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

You must configure a SharePoint Server client resource to back up SharePoint Server for BMR.

Configuring a SharePoint Server client resource

Use the NetWorker Administrator program to create a client resource.

Table 2 on page 36 provides the sample SharePoint farm configuration that the procedures use.

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

Perform the following steps to back up SQL Server in a SharePoint environment for BMR: 1. Create the first backup group for the SQL Server.

Table 2 Sample SharePoint Server 2010 configuration

Components Operating system Application version Critical volume NetWorker build SQL Server Windows Server

2008 R2 SP1 SQL Server 2008 R2 SP1 • SQL application is installed on the C: drive._{• Databases reside on the C: drive.} NetWorker 8.2 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 Web front-end

(37)

SharePoint Server 2013 and 2010 37

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:

– Ensure that you have selected Scheduled backup.

– In the Group list, select the group that you created in step 1. – In the Save set field, specify DISASTER_RECOVERY:\. f. Specify other fields according to your requirements. g. Click OK.

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

b. Select the Snapshot option.

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:

– Ensure that you have selected Scheduled backup.

– In the Group list, select the group that you created in step 4. – In the Save set field, specify APPLICATIONS:\SqlServerWriter. c. On the Apps & Modules tab:

– In the Backup command field, specify nsrsnap_vss_save.

– In the Application information field, specify NSR_SNAP_TYPE=vss. d. Specify other fields according to your requirements.

(38)

Backing up web front-end server 1

Perform the following steps to perform the BMR backup of web front-end server 1: 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 36.

b. Do not select the Snapshot option.

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

– In the Group list, select the group that you created in step 1. – In the Save set field, specify DISASTER_RECOVERY:\. c. Specify other fields according to your requirements. d. Click OK.

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

b. Select the Snapshot option.

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

(39)

SharePoint Server 2013 and 2010 39

Backing up web front-end server 2

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

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

Perform the following steps to perform BMR of SQL Server in a SharePoint environment: 1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual

Computers section in the NetWorker Release 8.2 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

Perform the following steps to perform the BMR of web front-end servers:

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 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.

(40)

SharePoint Server 2007

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

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

Backing up SharePoint Server 2007 for BMR

You must configure a SharePoint Server client resource to back up SharePoint Server 2007 for BMR.

Configuring a SharePoint Server client resource

Use the NetWorker Administrator program to create a client resource.

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

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

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

◆ The NetWorker client performs the BMR backup by using non-snapshot.

◆ The NMM client backs up the following save sets by using the VSS writer based

snapshot:

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

Perform the following steps to back up SharePoint Server 2007 for BMR: 1. Create a backup group for the SharePoint Server.

(41)

SharePoint Server 2007 41

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.

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

– In the Save set field, specify 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.

– In the Group list, select the group that you created in step 1. – In the Save set field, specify APPLICATIONS:\SqlServerWriter. c. Specify other fields according to your requirements.

d. Click OK.

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:

– In the Save set field, specify a volume other than critical volumes, for example, D:\.

(42)

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

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

– In the Group list, select the group that you created in step 1. – In the Save set field, specify DISASTER_RECOVERY:\. c. Specify other fields according to your requirements. d. Click OK.

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

BMR of SharePoint Server 2007

Perform the following steps to perform the BMR of SharePoint Server 2007:

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

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

– APPLICATIONS:\SqlServerWriter

– APPLICATIONS:\Microsoft Office SharePoint Services d. Perform the recovery.

(43)

Bare Metal Recovery of Microsoft Exchange Server 43

CHAPTER 6 Bare Metal Recovery of Microsoft Exchange Server

(44)

Bare Metal Recovery of Microsoft Exchange Server

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.

Configuring an Exchange Server client resource

By using the 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 User Guide provides

information about how to create a client resource to back up the application data. Creating a client resource to back up the file system data

“Creating a client resource to back up the file system data” on page 24 provides information about how to create a client resource to back up the file system data.

By using the NetWorker Administrator program

(45)

Exchange Server 2013 45

c. Click OK.

You have created the backup group.

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

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

2. Create a client resource for system backup.

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

If you have installed Exchange Server 2013 on a drive other than the system drive, specify 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.

(46)

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

– In the Group list, select the group that you created for application backup. – In the Save set field, specify the save set. For example,

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

– In the Backup command field, specify nsrsnap_vss_save. – In the Application information field, specify 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>

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

7. Back up the application data.

8. Ensure that the backup successfully completes.

BMR of Exchange Server 2013

To perform BMR of Exchange Server 2013:

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

(47)

Figure 6 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.

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.

Run the following command to mount the database:

mount-database -identity <database name> -force

Exchange Server 2010

Backing up Exchange Server 2010 for BMR

Configuring an Exchange Server client resource

(48)

By using the Client Configuration Wizard

Perform the procedures that the “By using the Client Configuration Wizard” on page 44 section describes.

By using the NetWorker Administrator program

Figure 7 on page 48 illustrates the sample configuration that the procedures use. Create two client resources for the Database Availability Group (DAG) node as shown in Figure 7 on page 48. 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).

Figure 7 Sample configuration for BMR backups of Exchange Server 2010

Perform the following steps to back up Exchange Server 2010 for BMR: 1. Create a backup group for system backup.

(49)

e. On the General tab:

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

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.

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

– In the Group list, select the group that you created for application backup. – In the Save set field, specify the save set. For example,

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

NSR_SNAP_TYPE=vss

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.

(50)

BMR of Exchange Server 2010

Perform the following steps to perform BMR of Exchange Server 2010:

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 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.

Run the following command to mount the database:

Exchange Server 2007

Backing up Exchange Server 2007 for BMR

Configuring an Exchange Server client resource

By using the Client Configuration Wizard

Perform the procedures that the “By using the Client Configuration Wizard” on page 44 section describes.

By using the NetWorker Administrator program

(51)

In this sample configuration:

◆ The client instance Exchnode2 is a physical node.

◆ The Exchange Virtual Server instance Exch2k7Virtual is active on the Exchnode2

physical node.

◆ The client instance Exchnode1 is a passive node.

Perform the following steps to back up Exchange Server 2007 for BMR: 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.

– In the Group list, select the group that you created to back up critical volumes on the active node.

– In the Save set field, specify DISASTER_RECOVERY:\.

(52)

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.

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

– In the Group list, select the group that you created to back up the Exchange virtual server instance on the active node.

– In the Save set field, specify Applications:\Microsoft Exchange 2007. c. On the Apps & Modules tab:

NSR_SNAP_TYPE=vss

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

(53)

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_SNAP_TYPE=vss

NSR_ALT-Path=C:\RM_MountPOINT

BMR of Exchange Server 2007

Perform the following steps to perform BMR of Exchange Server 2007:

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or Virtual Computers section in the NetWorker Release 8.2 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:

(54)

(55)

Bare Metal Recovery of Microsoft Hyper-V 55

CHAPTER 7 Bare Metal Recovery of Microsoft Hyper-V

This chapter includes the following section:

(56)

Bare Metal Recovery of Microsoft Hyper-V

Hyper-V

This section provides the BMR backup and recovery procedures for Hyper-V CSV and non-CSV.

Backing up Hyper-V for BMR

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

Configuring a Hyper-V client resource

By using the 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 User Guide provides information about how to create a client resource to back up the application data.

Creating a client resource to back up the file system data

“Creating a client resource to back up the file system data” on page 24 provides information about how to create a client resource to back up the file system data.

By using the NetWorker Administrator program

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

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

Perform the following steps to back up Hyper-V for BMR: 1. Create a backup group for Hyper-V.

EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution

EMC

®

NetWorker

®

Module for Microsoft for Windows

Bare Metal Recovery Solution

Release 8.2

User Guide

CONTENTS

Preface

Revision History

Chapter 1

Overview

Chapter 2

Bare Metal Recovery

Chapter 3

Bare Metal Recovery of Microsoft Active Directory

Chapter 4

Bare Metal Recovery of Microsoft SQL Server

Chapter 5

Bare Metal Recovery of Microsoft SharePoint Server

Chapter 6

Bare Metal Recovery of Microsoft Exchange Server

Chapter 7

Bare Metal Recovery of Microsoft Hyper-V

Chapter 8

Bare Metal Recovery of Microsoft System Center Virtual Machine

Manager

PREFACE

Purpose

Audience

Related documentation

Conventions used in this document



Typographical conventions

Where to get help

Your comments

REVISION HISTORY

CHAPTER 1

Overview

Bare Metal Recovery overview

Terminology

How BMR works with NetWorker and NMM

Recommendations



CHAPTER 2

Bare Metal Recovery

Protecting the application data before a disaster

Using NetWorker for performing BMR



CHAPTER 3

Bare Metal Recovery of Microsoft Active Directory

Active Directory

Backing up Active Directory for BMR

BMR of Active Directory

CHAPTER 4

Bare Metal Recovery of Microsoft SQL Server

SQL Server 2014, 2012, and 2008 R2

Backing up SQL Server for BMR by using the VDI technology

Configuring an SQL Server client resource

By using the Client Configuration Wizard

By using the NetWorker Administrator program



BMR of SQL Server 2012 or 2008 R2



SQL Server 2008 and 2005

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

Configuring a SQL Server client resource

By using the NetWorker Administrator program

BMR of SQL Server 2008 or 2005



CHAPTER 5

Bare Metal Recovery of Microsoft SharePoint

Server

SharePoint Server 2013 and 2010



Backing up SharePoint Server 2013 or 2010 for BMR

Configuring a SharePoint Server client resource

Backing up SQL Server in a SharePoint Server 2010 environment