emc networker module for microsoft for windows bare metal ... · emc® networker® module for...

EMC® NetWorker® Module forMicrosoft for Windows Bare MetalRecovery SolutionVersion 9.0.1

User Guide302-002-939

REV 02

Copyright © 2007-2016 EMC Corporation. All rights reserved. Published in the USA.

Published July, 2016

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

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

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. 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 CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0.1 User Guide

5

7

Introduction 11

Bare Metal Recovery overview....................................................................... 12System requirements.................................................................................... 12

Supported operating systems.......................................................... 12Supported Microsoft applications.................................................... 12NetWorker software version requirements........................................ 12Microsoft BMR requirements............................................................ 13CPU requirements............................................................................ 13Hard disk requirements....................................................................13NIC driver requirements....................................................................13Critical and noncritical volume requirements....................................13System Reserved Partition requirements.......................................... 14

Protecting an environment before a disaster..................................................14BMR by using NetWorker and NMM............................................................... 15

Microsoft Active Directory Backup and BMR 17

Backing up an Active Directory for BMR......................................................... 18Performing BMR of an Active Directory...........................................................18

Microsoft SQL Server Backup and BMR 19

SQL Server in a cluster environment.............................................................. 20Backing up a SQL Server for BMR by using the VDI technology..........20Performing BMR of a SQL Server....................................................... 22

SQL Server in a stand-alone environment...................................................... 24Backing up a SQL Server for BMR by using the VSS technology.........24Performing BMR of a SQL Server....................................................... 26

Microsoft SharePoint Server Backup and BMR 27

SharePoint Server 2013 and 2010.................................................................28Backing up SharePoint Server 2013 or 2010 for BMR....................... 28Performing BMR of SharePoint Server 2013 or 2010.........................30

SharePoint Server 2007................................................................................ 31Backing up SharePoint Server 2007 for BMR.................................... 31Performing BMR of SharePoint Server 2007......................................33

Microsoft Exchange Server Backup and BMR 35

Backing up an Exchange Server for BMR........................................................ 36Backing up an Exchange Server by using the NetWorker Client BackupConfiguration Wizard........................................................................36

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

CONTENTS

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

Backing up an Exchange Server by using the NetWorker Administratorprogram........................................................................................... 36

Performing BMR of an Exchange Server......................................................... 37

Microsoft Hyper-V Backup and BMR 39

Backing up Hyper-V for BMR.......................................................................... 40Backing up Hyper-V for BMR by using the NetWorker Client BackupConfiguration Wizard........................................................................40Backing up Hyper-V for BMR by using the NetWorker Administratorprogram........................................................................................... 40

Performing BMR of Hyper-V............................................................................42

Microsoft System Center Virtual Machine Manager Backup and BMR43

Backing up System Center Virtual Machine Manager for BMR........................ 44Backing up the VMM server for BMR................................................. 44Backing up the VMM library for BMR.................................................45Backing up the VMM database for BMR............................................45

Performing BMR of a System Center Virtual Machine Manager....................... 46Performing BMR of the VMM server.................................................. 46Performing BMR of the VMM library.................................................. 46Performing BMR of the VMM database............................................. 46

49

Chapter 6

Chapter 7

Glossary

CONTENTS


Revision history............................................................................................................... 7Style conventions............................................................................................................ 8Sample SharePoint Server 2010 configuration...............................................................28

123

TABLES


TABLES


Preface

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

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

Contact your EMC technical support professional if a product does not function correctlyor 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.

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

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

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

l EMC NetWorker software

l Microsoft Volume Shadow Copy Service (VSS) technology

Revision historyThe following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

02 July 15, 2016 The "Related documentation" section in the Preface hasbeen updated.

01 June, 2016 First release of this document for EMC NetWorker Modulefor Microsoft 9.0.1.

Related documentationThe NMM documentation set includes the following publications:

l EMC NetWorker Module for Microsoft Release Notes

l EMC NetWorker Module for Microsoft Administration Guide

l EMC NetWorker Module for Microsoft Installation Guide

l EMC NetWorker Module for Microsoft for SQL and SharePoint VSS User Guide


https://support.emc.com/

https://support.emc.com/

l EMC NetWorker Module for Microsoft for SQL VDI User Guide

l EMC NetWorker Module for Microsoft for Exchange VSS User Guide

l EMC NetWorker Module for Microsoft for Hyper-V VSS User Guide

l EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution UserGuide

l EMC ItemPoint for Microsoft SharePoint Server User Guide

l EMC ItemPoint for Microsoft Exchange Server User Guide

l NetWorker documentation set

Special notice conventions that are used in this documentEMC uses the following conventions for special notices:

NOTICE

Identifies content that warns of potential business or data loss.

Note

Contains information that is incidental, but not essential, to the topic.

Typographical conventionsEMC uses the following type style conventions in this document:

Table 2 Style conventions

Bold Used for names of interface elements, such as names of buttons, fields,tab names, and menu paths (what the user specifically selects orclicks)

Italic Used for full titles of publications that are referenced in text

Monospace Used for:

l System code

l System output, such as an error message or script

l Pathnames, file names, prompts, and syntax

l Commands and options

Monospace italic Used for variables

Monospace bold Used 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

... Ellipses indicate non-essential information that is omitted from theexample

Where to get helpEMC support, product, and licensing information can be obtained as follows:

Product informationFor documentation, release notes, software updates, or information about EMC products,go to EMC Online Support at https://support.emc.com.

Preface


https://support.emc.com

Technical supportGo to EMC Online Support and click Service Center. Several options for contacting EMCTechnical Support appear on the site. Note that to open a service request, you must havea valid support agreement. Contact your EMC sales representative for details aboutobtaining a valid support agreement or with questions about your account.

Online communitiesGo to EMC Community Network at https://community.emc.com for peer contacts,conversations, and content on product support and solutions. Interactively engage onlinewith customers, partners, and certified professionals for all EMC products.

Your commentsYour suggestions help to improve the accuracy, organization, and overall quality of theuser publications. Send your opinions of this document to [email protected].

Preface


https://community.emc.com

mailto:[email protected]

Preface


CHAPTER 1

Introduction

This chapter includes the following sections:

l Bare Metal Recovery overview............................................................................... 12l System requirements............................................................................................ 12l Protecting an environment before a disaster..........................................................14l BMR by using NetWorker and NMM....................................................................... 15

Introduction 11

Bare Metal Recovery overviewThis 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 ofthe supported Microsoft applications.

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

Typically, the backed up data includes the necessary operating system, applications, anddata components to rebuild or restore the backed up system to an entirely separate pieceof hardware. The hardware receiving the restore should have a similar configuration asthat 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 thesystem recovers with the operating system, the applications, and the data as they were atthe time of the failure.

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

System requirementsThe following sections list requirements to perform Windows BMR. However, the EMCNetWorker Online Software Compatibility Guide provides the latest information about thesystem requirements to perform Windows BMR by using NMM.

Supported operating systemsThe EMC NetWorker Online Software Compatibility Guide provides information about theoperating systems and versions that NMM supports.

Supported Microsoft applicationsThe EMC NetWorker Online Software Compatibility Guide provides information about theMicrosoft applications and versions that NMM supports.

NetWorker software version requirementsThe EMC NetWorker Online Software Compatibility Guide provides information about theNetWorker software versions that NMM supports.

Use the NetWorker Windows BMR 32-bit ISO image to recover an x86 operating system oneither an x86 or x64 computer.

Use the NetWorker Windows BMR 64-bit ISO image to recover only an x64 operatingsystem on an x64 computer.

Introduction


Microsoft BMR requirementsPerform BMR recoveries to the same or similar hardware, and physical to virtualenvironment.

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

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

CPU requirementsl The operating system architecture and the processor architecture must match.

l 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 samearchitecture. You can recover the operating system backup of an AMD x64 computerto an Intel x64 computer. The process is reversible.

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

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

Hard disk requirementsl 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 thenew system must be greater than or equal to the capacity on the old system. BMRfails if the capacity is smaller by even a single byte.

l Windows BMR supports IDE, SATA, or SCSI hard disks. You can perform the backupon one type of hard disk and recover on another type. For example, SAS to SATA issupported.

l You must restore the backup to the same logical disk numbers as on the originalserver. You cannot use different logical disk numbers on the target system to recoverthe critical volumes such as the operating system volume.

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

NIC driver requirementsTo use different Network Interface Card (NIC) after a Windows BMR recovery, install newNIC drivers that match the NIC in the new computer after Windows starts on the newserver.

Critical and noncritical volume requirementsl Windows BMR backs up only critical volumes, and can be used for offline disaster

recovery. Use the NetWorker client to back up the non-critical volumes.

Introduction

Microsoft BMR requirements 13

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

Note

NetWorker considers only system volume as a critical volume. If you have installed aMicrosoft application on a drive other than the system drive, the drive is notconsidered as critical. On Windows Server 2008 R2, a volume is critical if a Microsoftapplication has installed a Windows service on it, but on Windows Server 2012, avolume 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 thatBMR includes the Microsoft application binaries, and the volume on which they areinstalled is marked as critical.

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

84687:save: Unable to get volume information of file system '\\?\Volume{245204f6-5ff7-11e2-a3ac-806e6f6e6963}\': The deviceis not ready. (Win32 error 0x15). VSS OTHER: ERROR: VSS failedto process snapshot: The shadow copy provider had an unexpectederror while trying to process the specified operation. (VSSerror 0x8004230f)90108:save: Unable to save the SYSTEM STATE save sets: cannotcreate the snapshot.86024:save: Error occured while saving disaster recovery savesets.

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

Protecting an environment before a disasterTo prepare for disaster recovery, back up application data and other necessary files.

Procedure

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

The EMC NetWorker Administration Guide provides details about using the NetWorkerclient to backup non-application files.

2. If you use a NetWorker server earlier than 9.0.x, create a NetWorker group withoutenabling the Snapshot option. Otherwise, create a policy.

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

Introduction


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

5. Perform a backup.

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

The NMM application specific user guides, available from EMC Online Support,provide details about how to perform a full backup.

BMR by using NetWorker and NMMFrom NMM 9.0, perform Windows file system backup and recovery by using theNetWorker client, and application-specific backup and recovery by using NMM. Specificinformation about how the backup and recovery process for various Microsoftapplications in NMM 9.0 differs from previous NMM releases is provided in application-specific user guides.

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

NMM 9.0.1 is compatible with the NetWorker 9.0.1 client, which provides a true BMRcapability for Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2,and Windows Server 2008. This capability is built into the NetWorker client and providesBMR support to the same or similar hardware. For Windows BMR, you should downloadthe 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 criticalvolumes from backup, and restart the server to bring it back online.

To support a NetWorker Windows BMR recovery, download the Windows BMR image fromEMC Online Support (https://support.emc.com). This download enables you to create abootable Windows BMR ISO that contains NetWorker binaries and a wizard, whichcontrols the recovery process.

The "Windows Bare Metal Recovery to Physical or Virtual Computers" section in the EMCNetWorker Administration Guide provides detailed information about how to use theNetWorker Windows BMR image to perform a BMR recovery on protected hosts andVMware virtual machines.

NOTICE

For all the Microsoft applications, after performing Windows disaster recovery andrestarting the system, check all the disk and volume configurations. Usually, the disksand volumes appear as on the original system. However, it is possible, especially in BMR scenarios, that the volume or disk signaturesdo not match the original ones, and the non-critical volumes or disks are offline and notmounted. Use the Microsoft Disk Manager to bring the volumes and disks online, andthen restart the system for drive letter reassignments. Assign the same drive letters thatexisted before the BMR. Non-critical volumes that the mount points access might have asimilar issue.

Introduction

BMR by using NetWorker and NMM 15

http://support.emc.com

http://support.emc.com

Introduction


CHAPTER 2

Microsoft Active Directory Backup and BMR


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

Microsoft Active Directory Backup and BMR 17

Backing up an Active Directory for BMRProcedure

1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, andan action for Active Directory.

The Data Protection Policies chapter in the EMC NetWorker Administration Guideprovides information.

2. Create a client resource for Active Directory:

a. In the NetWorker Administrator window, click Protection.

b. In the expanded left panel, right-click Clients and select New.

The Create Client dialog box appears.

c. In the Name field, type the name for the client resource.

d. Click OK.

3. In the right panel, right-click the client resource and select Modify Client 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 Applicationinformation fields are clear.

c. Specify other fields according to the requirements.

d. Click OK.

5. Perform the backup.

Ensure that the backup successfully completes.

Performing BMR of an Active DirectoryProcedure

1. Perform the procedures that the "Performing a Windows BMR recovery to physical orvirtual computers" section in the EMC NetWorker Administration Guide describes.

The "Performing post-recovery tasks for Active Directory services" section in the EMCNetWorker Administration Guide provides information about how to perform anauthoritative 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 DirectoryUsers and the Computers and Domain Name System management.

Microsoft Active Directory Backup and BMR


CHAPTER 3

Microsoft SQL Server Backup and BMR


l SQL Server in a cluster environment...................................................................... 20l SQL Server in a stand-alone environment.............................................................. 24

Microsoft SQL Server Backup and BMR 19

SQL Server in a cluster environmentThis section provides the BMR backup and recovery procedures for SQL Server by usingthe VDI technology in a cluster environment.

Backing up a SQL Server for BMR by using the VDI technologyConfigure a SQL Server client resource to back up SQL Server for BMR by using the VDItechnology.

Backing up a SQL Server by using the NetWorker Client Backup Configuration WizardCreate separate client resources to back up the application data and the file system data.The client resource for the file system data must include the ALL save set.

The "Client Backup Configuration Wizard" section in the EMC NetWorker Module forMicrosoft for SQL VDI User Guide provides information about how to create a clientresource to back up the application data.

The "Creating a client resource with the Client Backup Configuration Wizard" section inthe EMC NetWorker Administration Guide provides information about how to create a clientresource to back up the file system data.

Backing up a SQL Server by using the NetWorker Administrator programThis 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.

Note

The procedures apply to 2014, 2012, 2008 R2, 2008, and 2005 versions also, in a clusterenvironment.

Procedure

1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, andan action for SQL Server.


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




c. In the Name field, type the name for the active node.

d. Click OK.








b. Specify other fields according to the requirements.

c. Click OK.



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

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




c. In the Name field, type the name for the Windows cluster.

d. Click OK.







c. Click OK.



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




c. In the Name field, type the SQL virtual name.

d. Click OK.


13. Perform step 9 and step 10.

14. Create a client resource with SQL virtual name to back up the SQL application data:




Backing up a SQL Server for BMR by using the VDI technology 21


c. In the Name field, type the SQL virtual name.

d. Click OK.





l In the Save set field, type MSSQL: if the SQL instance is either the defaultinstance or a named instance in the cluster.

b. On the Apps & Modules tab, in the Backup command field, type nsrsqlsv.


d. Click OK.

17. Create dummy client resources for the physical nodes of the cluster.



Performing BMR of a SQL ServerThe BMR process recovers C: drive only. It does not recover the SQL data, the quorumand SQL cluster drives, and the system databases such as master, msdb, and model.

Procedure

1. Separately recover the active and passive nodes by performing the procedures thatthe "Performing a Windows BMR recovery to physical or virtual computers" section inthe EMC NetWorker Administration Guide describes.

2. Recover the cluster quorum database:

a. After you have started the active and passive nodes, ensure that the cluster disksare online on the active node in the Disk Management Console of the WindowsGUI.

b. Add the quorum drive to Failover Cluster Management of the Cluster ConfigurationUI.

c. Select the storage node in Failover Cluster Management and ensure that thequorum 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 clustername, and click OK.

g. In the Destination Client dialog box, select the destination client with the activenode 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 arethe 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 nameand click OK.

g. In the Destination Client dialog box, select the destination client with the activenode 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 followingcommand:

Setup/QUIET/ACTION=REBUILDDATABASE/INSTANCENAME=SQL Serverinstance name/SQLSYSADMINACCOUNTS=Domain\administrator username/IAcceptSQLServerLicenseTerms

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

a. Open the SQL Server Properties dialog box as shown in the following figure.

Figure 1 SQL Server Properties dialog box

b. On the Dependencies tab, add all the SQL Server dependencies that you mustbring online before you bring the SQL Server online. For example, any dependentcluster 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.


Performing BMR of a SQL Server 23

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

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

l 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 virtualserver instance.

b. Browse the backed up databases.

c. Select the databases and restore the databases.

SQL Server in a stand-alone environmentThis section provides the BMR backup and recovery procedures for SQL Server by usingthe VSS technology in a stand-alone environment.

Backing up a SQL Server for BMR by using the VSS technologyConfigure a SQL Server client resource to back up SQL Server for BMR by using the VSStechnology.

Backing up a SQL Server by using the NetWorker Client Backup Configuration WizardCreate separate client resources to back up the application data and the file system data.The client resource for the file system data must include the DISASTER_RECOVERY:\save set.

The "By using the Client Backup Configuration Wizard" section in the EMC NetWorkerModule for Microsoft for SQL VDI User Guide provides information about how to create aclient resource to back up the application data.


Backing up a SQL Server by using the NetWorker Administrator programProcedure

1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, andan action for Active Directory.


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




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



http://msdn.microsoft.com/en-us/library/dd207003.aspx

http://msdn.microsoft.com/en-us/library/dd207003.aspx

http://msdn.microsoft.com/en-us/library/ms144259(v=sql.100).aspx




d. Click OK.




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




d. Click OK.



6. Create a client resource to back up the ALL save set.

Perform step a to substep d of step 2.







c. Click OK.



10. Create a client resource to back up the APPLICATIONS:\SqlServerWriter saveset:

Perform step a to step d of step 2.





l In the Save set field, type APPLICATIONS:\SqlServerWriter.

b. On the Apps & Modules tab, in the Backup command field, type nsrnmmsv.


d. Click OK.



Backing up a SQL Server for BMR by using the VSS technology 25


Performing BMR of a SQL ServerThe BMR process recovers only the C: drive. It does not recover the SQL data, quorumand SQL cluster drives, or the system databases such as master, msdb, and model.

Procedure


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 ManagementStudio and connect to the instance. The databases that belong to the instanceappear.



CHAPTER 4

Microsoft SharePoint Server Backup and BMR


l SharePoint Server 2013 and 2010.........................................................................28l SharePoint Server 2007.........................................................................................31

Microsoft SharePoint Server Backup and BMR 27

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

Note

NMM 9.0.1 does not support the BMR backup and recovery of SharePoint 2013 and 2010stand-alone servers with SQL embedded.

Backing up SharePoint Server 2013 or 2010 for BMRUse the NetWorker Administrator program to create a SharePoint Server client resource toback up SharePoint Server for BMR.

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

Table 3 Sample SharePoint Server 2010 configuration

Components Operatingsystem

Applicationversion

Critical volume NetWorkerbuild

SQL Server WindowsServer 2008 R2SP1

SQL Server2008 R2 SP1

l SQL application isinstalled on the C:drive.

l Databases reside onthe C: drive.

NetWorker9.0.1

Web front-endserver 1

WindowsServer 2008 R2SP1

SharePointServer 2010SP1

SharePoint Server 2010Application is installed onC: drive.

NetWorker9.0.1

Web front-endserver 2

WindowsServer 2008 R2SP1

SharePointServer2010 SP1

SharePoint Application isinstalled on the E: drive.

So, the critical volumes arethe C: and E: drives.

NetWorker9.0.1

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

Backing up SQL Server in a SharePoint Server 2010 environmentProcedure

1. By using the NetWorker Administration GUI, create the first policy, workflow, group,and action for the SQL Server.


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







d. Click OK.

3. In the NetWorker Administrator window, select the View tab and select DiagnosticMode.




l Ensure that you have selected Scheduled backup.




c. Click OK.



7. By using the NetWorker Administration GUI, create the second policy, workflow,group, and action for the SQL Server.


8. Create the second client resource for the SQL Server.

Perform step a through step d of step 2.




l Ensure that you have selected Scheduled backup.



b. On the Apps & Modules tab, in the Backup command field, type nsrnmmsv.


d. Click OK.



Backing up web front-end server 1

Perform all the steps in Backing up SQL Server in a SharePoint Server 2010environment on page 28 except the following substep of step 10a:

In the Save set field, type APPLICATIONS:\SqlServerWriter.


Backing up SharePoint Server 2013 or 2010 for BMR 29

For the web front-end server 1, in the Save set field, type APPLICATIONS:\MicrosoftOffice SharePoint Services.

Backing up web front-end server 2The steps to perform the BMR backup of web front-end server 2 are the same as the stepsin Backing up web front-end server 1 on page 29.

Performing BMR of SharePoint Server 2013 or 2010This section describes 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 SharePointdisaster recovery. To continue with recovery, move, rename, or delete the specifieddatabase files and perform the recovery from that point. The associated files are themaster database file master.mdf, and the master log file mastlog.ldf.

Procedure


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 host if prompted.

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

Recovering the web front-end serversProcedure


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. Ensurethat the DISASTER_RECOVERY:\ save set is visible in the NetWorker client UI.

c. Restart the host if prompted.

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




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

Note

NMM 9.0.1 does not support the BMR backup and recovery of SharePoint 2007 stand-alone server with SQL embedded.

Backing up SharePoint Server 2007 for BMRThe procedures use the following SharePoint Server 2007 configuration on WindowsServer 2008 R2:

l You have installed Windows Server 2008 R2 SP1 and updates on the C:\ drive.

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

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

Procedure

1. By using the NetWorker Administration GUI, create the first policy, workflow, group,and action for the SharePoint Server.


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





d. Click OK.

3. In the NetWorker Administrator window, select the View tab and select DiagnosticMode.





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



SharePoint Server 2007 31

c. Click OK.

6. Perform the backup on all hosts in the SharePoint environment.

Ensure that the backups successfully complete.

7. Create a client resource to back up the APPLICATIONS:\SqlServerWriter saveset.








c. Click OK.



11. Create a client resource to back up a non-critical volume.






l In the Save set field, type a volume drive letter other than critical volumes, forexample, D:\.


c. Click OK.



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






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




c. Click OK.

18. Perform backups on all hosts in the SharePoint environment.

Performing BMR of SharePoint Server 2007Procedure


2. After the host restarts:


b. Select the server and click Recover.

c. Select the following save sets:

l APPLICATIONS:\SqlServerWriterl APPLICATIONS:\Microsoft Office SharePoint Services

d. Perform the recovery.



Performing BMR of SharePoint Server 2007 33

CHAPTER 5

Microsoft Exchange Server Backup and BMR


l Backing up an Exchange Server for BMR................................................................ 36l Performing BMR of an Exchange Server................................................................. 37

Microsoft Exchange Server Backup and BMR 35

Backing up an Exchange Server for BMRConfigure an Exchange Server client resource to back up an Exchange Server for BMR.

Backing up an Exchange Server by using the NetWorker Client Backup ConfigurationWizard

Separately create a client resource to back up the application data and the file systemdata which includes the ALL save set.

The "Creating a client resource using the Client Backup Configuration Wizard" section inthe EMC NetWorker Module for Microsoft for Exchange VSS User Guide provides informationabout how to create a client resource to back up the application data.


Backing up an Exchange Server by using the NetWorker Administrator programCreate two client resources for the Database Availability Group (DAG) node. You use oneclient resource to back up the system data (critical volumes) and the other client to backup the application data (non-critical volumes).

Procedure

1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, andan action for system backup.


2. Create a client resource for system backup:




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

d. Click OK.





l In the Save set field, type ALL.If you have installed Exchange Server 2013 on a drive other than the systemdrive, type the drive letter also. For example, E:\.





d. Click OK.



6. By using the NetWorker Administration GUI, create a policy, a workflow, a group, andan action for application backup.


7. Create a client resource for application backup.




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 2016 orAPPLICATIONS:\Microsoft Exchange 2013.

b. On the Apps & Modules tab:

l In the Backup command field, type nsrnmmsv.

l In the Application information field, type the following:NSR_FEDERATED_BACKUP=yesNSR_FEDERATED_PSOL=<DAG_MEMBER_NODES>NSR_EXCH_DAG=<DAG_INSTANCE_NAME>NSR_EXCH_BACKUP=<preferred/passive/Active>NSR_EXCH_CHECK=<Yes/No>


d. Click OK.



Performing BMR of an Exchange ServerProcedure


2. After the recovery completes, restart the host to start all the Exchange services.

3. After the host restarts, ensure that you meet the following requirements:

a. You have recovered all critical volumes.

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


Performing BMR of an Exchange Server 37

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

d. You have successfully mounted the database after the recovery, and checkedwhether the recovery process has successfully recovered all email messages.



CHAPTER 6

Microsoft Hyper-V Backup and BMR


l Backing up Hyper-V for BMR.................................................................................. 40l Performing BMR of Hyper-V....................................................................................42

Microsoft Hyper-V Backup and BMR 39

Backing up Hyper-V for BMRConfigure a Hyper-V client resource to back up Hyper-V for BMR.

Backing up Hyper-V for BMR by using the NetWorker Client Backup ConfigurationWizard

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

The "Creating the client by using the Client Configuration Wizard" section in the EMCNetWorker Module for Microsoft for Hyper-V VSS User Guide provides information about howto create a client resource to back up the application data.


Backing up Hyper-V for BMR by using the NetWorker Administrator programThe procedures use the following sample Hyper-V configuration on a Windows server:

l Physical Node1: nmm-csv-node1l Physical Node2: nmm-csv-node2l Virtual Server: nmm-csv-clusterProcedure

1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, andan action for Hyper-V.


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




c. In the Name field, type the name for the physical node.

d. Click OK.





l In the Save set field, type APPLICATIONS:\Microsoft Hyper-V.


c. Click OK.



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


6. Create a client resource to backup the Hyper-V application data that the CSV volumeshost.

Perform step a through d of step 2.

7. Perform steps 3 and 4.


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


9. Create a client resource to backup the non-critical volumes.


10. Perform step 3.




l In the Save set field, type a volume drive letter other than critical volumes, forexample, D:\.


c. Click OK.



13. Create a client resource to backup the ALL save set.







c. Click OK.




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

Performing BMR of Hyper-VEnsure that the cluster service account is enabled. Otherwise, the explorer stopsresponding when you browse CSVs and the recovery fails.

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

Procedure


After the recovery completes, the status of Hyper-V VMs in the Failover ClusterManager 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 clientresource, by using the NMM client.

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



CHAPTER 7

Microsoft System Center Virtual MachineManager Backup and BMR


l Backing up System Center Virtual Machine Manager for BMR................................ 44l Performing BMR of a System Center Virtual Machine Manager............................... 46

Microsoft System Center Virtual Machine Manager Backup and BMR 43

Backing up System Center Virtual Machine Manager for BMRBack up and recover the following key components of VMM to ensure a protected VMMenvironment:

l VMM server: The VMM server is the central component of a VMM deployment. Theserver contains the core Windows service that includes the VMM engine.

l VMM database: The VMM database resides on either the VMM server or on a remotedatabase server. You must regularly save the VMM database to quickly recovery theVMM environment.

l VMM library: The VMM library is either one file server or multiple file servers with fileshares that index specific file types that the VMM uses. The VMM library sharesinclude VHD, VMDK, ISO, PS1, INF, VFD, FLP, and XML files besides stored virtualmachines.

You must frequently back up the data such as, the data on the virtual machines, whichVMM manages, that often changes. NMM supports the Microsoft Hyper-V VSS writer toprotect Hyper-V virtual machines. The EMC NetWorker Module for Microsoft for Hyper-V VSSUser Guide provides information about how to back up the environment’s virtualmachines.

You must perform BMR backups for the Hyper-V servers also.

If you have installed any component of VMM on a Hyper-V virtual machine, you canprotect it by using the NMM client’s Hyper-V. Use NMMM to protect the VMM server, theVMM library, or the VMM database on a virtual machine. NMM takes image backups ofHyper-V virtual machines. You do not need to install an NMM client on the virtualmachine. Instead, install an NMM client on the Hyper-V server and configure NMM clientresources to back up the virtual machines. Use the NMM GUI Hyper-V plug-in to recover avirtual machine that contains a VMM component.

The EMC NetWorker Module for Microsoft for Hyper-V VSS User Guide provides informationabout how to protect a Hyper-V server’s information.

Backing up the VMM server for BMRThe VMM server relies on the VMM database to store data. The VMM database uses theserver account to encrypt that data.

You must perform a full backup of the VMM server host to ensure that you meet thefollowing requirements:

l The same host account is available to interact with the VMM database after recovery.l All virtual machine hosts associates and communicates with the VMM server.l You can recover any communication certificates so that the existing agents continue

to work as you expected.

You can protect the VMM server by performing a NetWorker Windows BMR backup alongwith an NMM backup of local file systems and application-specific data, such as the dataassociated with Hyper-V Server, SQL Server, or SharePoint Server. The advantage of aWindows BMR backup and recovery capability for a VMM server is that the backupincludes the system state. When you perform recovery, the system state recovers thecomputer security identifier (SID) that uniquely identifies the computer to the network.The computer-recovered SID enables the VMM server to quickly and easily interact withany existing VMM database, VMM library, and managed servers without additional post-recovery operations. The Windows BMR backup captures the VMM authorization datafilewhich is typically %ProgramData%\Microsoft\Virtual Machine Manager\HyperVAuthStore.xml when protecting the critical system drive.

Microsoft System Center Virtual Machine Manager Backup and BMR


Procedure

1. Use the NetWorker client to back up the VMM server non-application files byspecifying the ALL save set. This setting enables the backup of the local file systemsand the DISASTER_RECOVERY:\ save set of the VMM server.

To configure a NetWorker client resource by using the client configuration wizard,perform the procedures that the Backing up a SQL Server by using the NetWorkerClient Backup Configuration Wizard on page 20 section describes.

2. Use an NMM client resource specification to perform a full backup of any applicationdata on the VMM server.

Backing up the VMM library for BMRThe VMM library is a catalog of resources that enables you to store objects that are notrunning or associated with a host. The library contains the files that are present on libraryshares, templates, operating system profiles, and hardware profiles.

Procedure

l Use the NMM backup and recovery techniques for Windows files servers to back upand recover a VMM library server.

l Use the NetWorker client to back up the VMM library by specifying the ALL save set toperform a Windows BMR backup of the VMM library. The ALL save set enables you toback up the local file systems and the DISASTER_RECOVERY:\ save set of the VMMlibrary.

l Perform the procedure that the Backing up a SQL Server by using the NetWorker ClientBackup Configuration Wizard on page 20 describes to configure a NetWorker clientresource.

Backing up the VMM database for BMRThe VMM database is a SQL Server database that contains all the configurationinformation for VMM. Give the highest priority to protect the VMM database.

The default installation of VMM uses Windows Internal Database (WID), a version ofMicrosoft SQL Express, on the same host as the VMM server. The database name isMICROSOFT$VMM$\Virtual Manager DB. However, the VMM database can alsoreside on either an existing Microsoft SQL Server Standard or SQL Server Enterpriseserver. To find out the location of the database for VMM, inspect the Registry valuesentries under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MicrosoftSystem Center Virtual Machine Manager Server\Settings\Sql key.

NMM 9.0.1 clients support the backup and restore of SQL databases.

Back up the VMM database that is part of a SQL Server installation.

The EMC NetWorker Module for Microsoft for SQL VDI User Guide provides information abouthow to protect a SQL server.

Procedure

1. Configure an NMM SQL Server client resource for the system with the VMM database.

2. Include the VMM databases when you schedule a backup.

3. In the Client Properties dialog box, in the Save set field, specify the VMM database.You can save either the entire SQL Server or named instances and individualdatabases.


Backing up the VMM library for BMR 45

Performing BMR of a System Center Virtual Machine ManagerThe VMM components have interdependencies. Recover the entire VMM environment fora disaster recovery.

Procedure

1. Recover the library file server.

a. Recover the physical VMM library file server with a Windows BMR save set.

b. Use the NetWorker client file system plug-in to recover the file system that youshared as the VMM library.

2. Recover the VMM database.

a. Recover the physical SQL server with a Windows BMR save set.

b. Stop the VMM services.

c. Use the NMM GUI SQL plug-in to restore the VMM database.

d. Start the VMM services.

3. Recover the VMM host.

4. After the operating system and VMM server are stable, perform the required post-recovery VMM steps that the Microsoft documentation describes.

Performing BMR of the VMM serverPerform the procedures described in the "Performing a Windows BMR recovery tophysical or virtual computers" section in the EMC NetWorker Administration Guide.

Performing BMR of the VMM libraryProcedure


2. After you recover the file share directories, either adjust the VMM Library Refresherinterval or manually trigger the Library Refresher to enable VMM to refresh thecontents of the file server share.

The VMM Administrator Console embedded help describes how to set the LibraryRefresher interval and perform a manual refresh.

Performing BMR of the VMM databasePerform the procedures that the "Performing a Windows BMR recovery to physical orvirtual computers" section in the EMC NetWorker Administration Guide describes.

If you only back up and recover the VMM database, then you must use the same instanceof the VMM server component for the restore. This is important to reduce VMM post -restore steps. Microsoft VMM documentation provides more information.

You must manually stop the VMM Windows service before you restore the VMM database.After you restore the database, start the service. After you restore the VMM database andstart the VMM Windows service, VMM synchronizes the database with the VMM serverand VMM library computers.



Note

You must reapply any changes that you made to the VMM environment between the timeof the backup and the restore. For example, you must re-create the templates that youcreated in VMM after performing the backup that you use to perform the restore.

Before you restore a SQL database, verify whether all the SQL services have started. If youperform a SQL Server recovery as part of BMR, Microsoft SQL Server Backup and BMR onpage 19 provides more information about how to perform BMR of SQL Server.


Performing BMR of the VMM database 47

GLOSSARY

This glossary contains terms related to the NetWorker Module for Microsoft. Many ofthese terms are used in this manual.

A

application data User data such as a log file that is created by the application, or user data such as anapplication database that is created with the application. For example, an SQL Server’sapplication data includes its databases and log files. Application data is neither includedin nor recoverable from a Windows BMR operation. Application data must be backed upand recovered with NMM.

ASR writer The VSS Writer, which is responsible for identifying critical data that is needed to performan offline restores.

B

backup group See group.

backup volume A volume used to store backup data. NetWorker backup data cannot be stored on anarchive volume or a clone volume.

Boot Configuration Data(BCD)

The BCD store contains boot configuration parameters, and controls how MicrosoftWindows Server 2008 operating system starts. A backup of this ASR Writer component isrequired to perform an offline restore.

C

client Host on a network, such as a computer, workstation, or application server whose data canbe backed up and restored with the backup server software.

Client resource NetWorker server resource that identifies the save sets to be backed up on a client. TheClient resource also specifies information about the backup, such as the schedule, browsepolicy, and retention policy for the save sets.

cluster Group of linked virtual or physical hosts, each of which is identified as a node, with sharedstorage that work together and represent themselves as a single host.

critical volume Any volume containing system state files or files for an installed service, including volumesmounted as NTFS directories which contain such files. The volume where a critical volumeis mounted is also considered to be critical. This is required to perform an offline restore,however maybe optional for this release depending upon the difficulties of implementingthis feature.


D

disaster recovery Restore and recovery of data and business operations in the event of hardware failure orsoftware corruption.

G

group One or more client computers that are configured to perform a backup together, accordingto a single designated schedule or set of conditions.

M

master database The SQL Server master database contains information about all SQL Server databases onthe SQL Server host.

N

NetWorker An EMC network-based software product for backing up and recovering file systems.

NetWorker client See client.

NetWorker resource A component of the s software that controls the functionality of the NetWorker server andits clients. Examples of NetWorker resources include devices, schedules, clients, groups,and policies. Each resource consists of a list of values that defines the resource’s specificparameters.

NetWorker server Computer on a network that runs the NetWorker server software, contains the onlineindexes, and provides backup and restore services to the clients and storage nodes on thesame network.

NetWorker Windows BMRimage

A bootable image that contains NetWorker binaries and a wizard to control the WindowsBMR process.

non-critical volume A volume that contains files that are not part of the system state or an installed service.

O

offline restore Automated restore that does not require the manual installation of an operating system. Abare metal recovery (BMR) is an offline restore.

online restore Restore operation that is performed from a NetWorker recover program. An online restorerequires that the computer has been booted from an installed operating system. See alsooffline restore.

R

recovery The process of retrieving individual data files from backup storage and copying to disk.

Glossary


S

save NetWorker command that backs up client files to backup media volumes and makes dataentries in the online index.

save set 1. Group of tiles or a file system copied to storage media by a backup or snapshotrollover operation.

2. NetWorker media database record for a specific backup or rollover.

V

volume 1. Unit of physical storage medium, such as a disk or magnetic tape, to which backupdata is written.

2. Identifiable unit of data storage that may reside on one or more computer disks.

volume ID Internal identification that NetWorker software assigns to a backup volume.

volume name Name that you assign to a backup volume when it is labeled.

Glossary


Glossary


emc networker module for microsoft for windows bare metal ... · emc® networker® module for...

Documents