EMC NetWorker Module for Microsoft for Windows Bare · PDF fileEMC® NetWorker® Module for Microsoft for Windows Bare Metal Recovery Solution Version 8.2 Service Pack 1 User Guide

EMC® NetWorker® Module forMicrosoft for Windows Bare MetalRecovery SolutionVersion 8.2 Service Pack 1

User Guide302-001-235

REV 01

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

Published January, 2015

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 8.2 Service Pack 1 User Guide

5

7

9

Introduction 13

Bare Metal Recovery overview....................................................................... 14System requirements.................................................................................... 14

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

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

Microsoft Active Directory Backup and BMR 19

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

Microsoft SQL Server Backup and BMR 21

SQL Server 2014, 2012, and 2008 R2............................................................22Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using theVDI technology.................................................................................22Performing BMR of a SQL Server 2014, 2012, or 2008 R2................. 25

SQL Server 2008 and 2005............................................................................27Backing up a SQL Server 2008 or 2005 for BMR by using the VSStechnology....................................................................................... 27Performing BMR of a SQL Server 2008 or 2005................................. 28

Microsoft SharePoint Server Backup and BMR 31

SharePoint Server 2013 and 2010.................................................................32Backing up SharePoint Server 2013 or 2010 for BMR....................... 32Performing BMR of SharePoint Server 2013 or 2010.........................35

SharePoint Server 2007................................................................................ 36Backing up SharePoint Server 2007 for BMR.................................... 36Performing BMR of SharePoint Server 2007......................................38

Figures

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

Chapter 4

CONTENTS

EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 8.2 Service Pack 1 User Guide 3

Microsoft Exchange Server Backup and BMR 39

Exchange Server 2013...................................................................................40Backing up Exchange Server 2013 for BMR.......................................40Performing BMR of Exchange Server 2013........................................ 42



Microsoft Hyper-V Backup and BMR 49

Backing up Hyper-V for BMR.......................................................................... 50Backing up Hyper-V for BMR by using the NMM Client ConfigurationWizard............................................................................................. 50Backing up Hyper-V for BMR by using the NetWorker Administratorprogram........................................................................................... 50

Performing BMR of Hyper-V............................................................................52

Microsoft System Center Virtual Machine Manager Backup and BMR53

Backing up System Center Virtual Machine Manager for BMR........................ 54Backing up the VMM server for BMR................................................. 54Backing up the VMM library for BMR.................................................55Backing up the VMM database for BMR............................................55

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

59

Chapter 5

Chapter 6

Chapter 7

Glossary

CONTENTS


Sample configuration for BMR backups of Exchange Server 2013.................................. 40Naming conflict............................................................................................................. 42Sample configuration for BMR backups of Exchange Server 2010.................................. 43Sample configuration for BMR backups of Exchange Server 2007 SP3 Rollup5...............46

1234

FIGURES


FIGURES


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

12

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

Contact your EMC technical support professional if a product does not function properlyor 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 EMC NetWorker snapshot management

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

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

Related documentationThe NMM documentation set includes the following publications:

l NetWorker Module for Microsoft Release Notes

l NetWorker Module for Microsoft Administration Guide

l NetWorker Module for Microsoft Installation Guide

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

l NetWorker Module for Microsoft for SQL VDI User Guide


https://support.emc.com/

https://support.emc.com/

l NetWorker Module for Microsoft for Exchange VSS User Guide

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

l NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution User Guide

l NetWorker Module for Microsoft Advanced Recovery Guide

l NetWorker Performing backup and recovery of SharePoint Server by using NetWorkerModule for Microsoft SQL VDI solution Technical Notes

l NetWorker Performing Exchange Server Granular Recovery by using NetWorker Module forMicrosoft with Ontrack PowerControls Technical Notes

l NetWorker SharePoint BLOB Backup and Recovery by using NetWorker Module forMicrosoft and Metalogix StoragePoint Technical Notes

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

NOTICE

Addresses practices not related to personal injury.

Note

Presents information that is important, but not hazard-related.

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

Italic Use for full titles of publications referenced in text

Monospace Use 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 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

... Ellipses indicate non-essential information omitted from the example

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.

Technical supportGo to EMC Online Support and click Service Center. You will see several options forcontacting EMC Technical Support. Note that to open a service request, you must have avalid support agreement. Contact your EMC sales representative for details aboutobtaining a valid support agreement or with questions about your account.

Preface


https://support.emc.com

Online communitiesVisit 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 will help us continue to improve the accuracy, organization, and overallquality of the user publications. Send your opinions of this document to [email protected]

Preface


https://community.emc.com

mailto:[email protected]

Preface


CHAPTER 1

Introduction

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

Introduction 13

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. The EMC NetWorkerOnline Software Compatibility Guide that is available on the https://support.emc.com/products/1095/Topics/pg41054/ page also provides the information about the versionsof the supported operating systems, the software and hardware requirements, and theexact versions of the Microsoft applications to perform Windows BMR.

Supported operating systemsl Windows Server 2012 R2 (x64)

l Windows Server 2012 (x64)

l Windows Server 2008 SP2 (x86 and x64)

l Windows Server 2008 R2 SP1 (x64)

l Windows Server 2008 R2 (x64)

l Windows Server 2008 (x86 and x64)

Supported Microsoft applicationsl Exchange Server 2013

l Exchange Server 2010

l Exchange Server 2007

l SharePoint Server 2013



l Hyper-V Server

Introduction


https://support.emc.com/products/1095/Topics/pg41054/

https://support.emc.com/products/1095/Topics/pg41054/

l SQL Server 2014

l SQL Server 2012

l SQL Server 2008 R2 SP2 or later

l SQL Server 2008 SP3 or later

l SQL Server 2005

l Active Directory

l System Center Virtual Machine Manager

NetWorker software version requirementsl NetWorker server 7.6 SP3 or later

l NetWorker client 8.2 SP1

l NetWorker Management Console 8.2 SP1

l Use the NetWorker Windows BMR 32-bit ISO image to recover an x86 operatingsystem on either an x86 or x64 computer

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

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 The firmware—Basic Input/Output System (BIOS) or Unified Extensible FirmwareInterface (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.

Introduction

NetWorker software version requirements 15

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

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 destination computer does not interfere with the diskorder of the hard disks.

NIC driver requirementsTo use different Network Interface Card (NIC) after a Windows BMR recovery, you mustinstall new NIC drivers that match the NIC in the new computer after Windows boots onthe new server.

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

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

Note

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

l To make a volume critical on Windows Server 2012, set the value of the HKLM\System\CurrentControlSet\Control\SystemWriter\ReportWin32ServicesNonSystemState registry key to 0. This ensures 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 message:

84687:save: Unable to get volume information of file system '\\?\Volume{245204f6-5ff7-11e2-a3ac-806e6f6e6963}\': The device is not ready. (Win32error 0x15). VSS OTHER: ERROR: VSS failed to process snapshot: The shadow copyprovider had an unexpected error while trying to process the specified operation. (VSSerror 0x8004230f)

90108:save: Unable to save the SYSTEM STATE save sets: cannot create the snapshot.

86024:save: Error occured while saving disaster recovery save sets.

If SRP is offline, perform the following steps to bring it online:

1. In the WinPE command prompt, type diskpart and press Enter.

2. Run the following command to display the list of volumes:DISKPART> list volume

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

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

Introduction


Rollover requirementsPerform daily rollovers to avoid the following issues:

l Manual rollover of the snapshot fails.

l When you back up a save set with the snapshot policy 1/1/day/none, the processapplies retention and deletes the stale snapshot entry.

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 NetWorker Release 8.2 SP1 Administration Guide provides details about usingNetWorker 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 step2.

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 NetWorker Module for Microsoft Release 8.2 SP1 application specific user guidesprovide details about how to perform a full backup.

BMR by using NetWorker and NMMFrom NMM 3.0 onwards, you must perform Windows file system backup and recovery byusing the NetWorker client, and application-specific backup and recovery by using NMM.Specific information about how the backup and recovery process for various Microsoftapplications 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 WindowsASR writer and other VSS writers to identify critical volumes that are needed 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 8.2 SP1 is compatible with the NetWorker 8.2 SP1 client, which provides a true BMRcapability for Windows Server 2012, Windows Server 2008 R2, and Windows Server2008. This capability is built into the NetWorker client and provides BMR support to thesame or similar hardware. For Windows BMR, you should download the appropriate .isorecovery boot image file from EMC Online Support (https://support.emc.com). The ISOimage provides a wizard that allows you to format disks, recover Windows criticalvolumes 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.2SP1 Administration Guide provides information about how to download the NetWorkerWindows BMR image.

Introduction

Rollover requirements 17

http://support.emc.com

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

NOTICE

For all the Microsoft applications, after performing Windows disaster recovery andrestarting the system, check all the disk and volume configurations. In most cases, thedisks and 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


CHAPTER 2

Microsoft Active Directory Backup and BMR

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

Microsoft Active Directory Backup and BMR 19

Backing up an Active Directory for BMRProcedure

1. Create a backup group for Active Directory:

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

The Create Group dialog box appears.

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

c. Click OK.

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

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

The Create Client dialog box appears.

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

c. Click OK.

3. Right-click the client and select Properties.

4. In the Client Properties dialog box:

a. On the General tab:

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

l In the Save set field, type All.

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

c. Specify other fields according to your requirements.

d. Click OK.

5. Perform the backup.

Performing BMR of an Active DirectoryProcedure

1. Perform the procedures that the Windows Bare Metal Recovery to Physical or VirtualComputers section in the NetWorker Release 8.2 SP1 Administration Guide describes.

The Performing post-recovery tasks for Active Directory services section in theNetWorker Release 8.2 SP1 Administration Guide provides information about how toperform an authoritative recovery of Active Directory.

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

3. Verify whether all the Active Directory objects are present in both the Active 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 2014, 2012, and 2008 R2....................................................................22l SQL Server 2008 and 2005....................................................................................27

Microsoft SQL Server Backup and BMR 21

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

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

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

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

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

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

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

Procedure

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

l Click Configuration > Client Backup Configuration > New.

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

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

a. In the Client name field, type the name of the client resource.

b. Select Traditional NetWorker Client.

c. Click Next.

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

3. On the Specify the Backup Configuration Type page:

a. From the Available Applications list, select Filesystem.

b. Click Next.

4. On the Specify the Client Backup Options page:

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

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

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

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

l Avamar deduplication backup—If you use an Avamar device for datadeduplication. After you select this option, choose the Avamar node from theavailable 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 fromthe respective drop-down lists.

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

c. Click Next.

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

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

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

l Create a new group—Perform the following steps:

n In the Group Name field, type a name for the group.

n In the Client Retries field, either select or type 0.

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

n To automatically start the backup at the specified time, select Automaticallystart the backup at the scheduled time.

8. On the Specify the Storage Node Options page:

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

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

l Backup to the following storage nodes—If you use a NetWorker storage node.Select the storage nodes.

b. Click Next.

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

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

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

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

This procedure uses the following sample SQL Server configuration:

l You have installed SQL Server on cluster volume P:\.

l The cluster quorum drive is E:\.

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


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

Note

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

Procedure

1. Create a backup group for SQL Server:




c. Click OK.

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



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

c. Click OK.





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

b. Specify other fields according to your requirements.

c. Click OK.


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

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



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

c. Click OK.









c. Click OK.

10.Perform the backup.

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



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

c. Click OK.

12.Right-click the client and select Properties.

13.In the Client Properties dialog box:





c. Click OK.


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



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

c. Click OK.

16.Right-click the client and select Properties.

17.In the Client Properties dialog box:



l In the 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.

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


Performing BMR of a SQL Server 2014, 2012, or 2008 R2The BMR process recovers C: drive only. It does not recover the SQL data, the quorum andSQL cluster drives, and the system databases such as master, msdb, and model.


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

Procedure

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

2. Recover the cluster quorum database:

a. After you have started the active and passive nodes, ensure that the cluster 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=<SQLServer instance 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.



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.

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

b. Browse the backed up databases.

c. Select the databases and restore the databases.

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

Backing up a SQL Server 2008 or 2005 for BMR by using the VSS technologyYou must configure a SQL Server client resource to back up SQL Server for BMR by usingthe VSS technology.

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

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

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




c. Click OK.

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




SQL Server 2008 and 2005 27

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





c. Click OK.




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


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


d. Click OK.


6. Perform the All save set backup by using the NetWorker client.

7. For the backup group that you created in step 1:

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

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

b. Select the Snapshot option.

c. Select the appropriate Snapshot Policy and Snapshot Pool from the respectivelists.

d. Specify other fields according to your requirements.

e. Click OK.

8. Create a client resource to back up the APPLICATIONS:\ SqlServerWriter save set:

a. Perform step 2 and step 3.

The Client Properties dialog box appears.

b. On the General tab:

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

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

c. On the Apps & Modules tab:

l In the Backup command field, type nsrsnap_vss_save.

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


e. Click OK.


Performing BMR of a SQL Server 2008 or 2005The BMR process recovers only the C: drive. It does not recover the SQL data, quorum andSQL 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.


Performing BMR of a SQL Server 2008 or 2005 29



CHAPTER 4

Microsoft SharePoint Server Backup and BMR

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

Microsoft SharePoint Server Backup and BMR 31

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

Note

NMM 8.2 SP1 does not support the BMR backup and recovery of SharePoint 2013 and2010 standalone 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 2 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.

NetWorker 8.2SP1

Web front-endserver 1

WindowsServer 2008 R2SP1

SharePointServer 2010SP1

SharePoint Server 2010Application is installed onC: drive.

NetWorker 8.2SP1

Web front-endserver 2

WindowsServer 2008 R2SP1

SharePointServer2010 SP1

SharePoint Application isinstalled on the E: drive.So, the critical volumesare the C: and E: drives.

NetWorker 8.2SP1

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. Create the first backup group for the SQL Server:




c. Click OK.

You have created the first backup group.



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


e. Do not select Snapshot.

f. Specify other fields according to your requirements.

g. Click OK.

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




c. Click OK.

You have created the first client resource.

d. Right-click the client and select Properties.


e. On the General tab:

l Ensure that you have selected Scheduled backup.




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


d. Click OK.

5. Create the second client resource for the SQL Server:



l Ensure that you have selected Scheduled backup.


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



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


e. Click OK.


Backing up SharePoint Server 2013 or 2010 for BMR 33


Backing up web front-end server 1Procedure

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 SharePointServer 2010 environment on page 32.

b. Do not select Snapshot.


d. Click OK.

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






d. Click OK.


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


b. Select Snapshot.


d. Click OK.

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




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



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


e. Click OK.




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

Performing BMR of SharePoint Server 2013 or 2010The following sections describe the recovery procedures for SQL Server, web front-endserver 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 proceed 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 machine 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 machine if prompted.

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



Performing BMR of SharePoint Server 2013 or 2010 35

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

Note

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

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

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

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

l You have configured the environment with a single NIC.

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

l The snapshot policy is 1\0\day\All (RolloverOnly policy).

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

l The NMM client backs up the following save sets by using the VSS writer basedsnapshot:

n APPLICATIONS:\Microsoft Office SharePoint Services

n APPLICATIONS:\SQLServerWriter

Procedure

1. Create a backup group for the SharePoint Server:




c. Click OK.

You have created the backup group.



l Select Snapshot.

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

e. Specify other fields according to your requirements.

f. Click OK.

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






c. Click OK.

You have created the client resource.





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


g. Click OK.

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

4. Create a client resource to back up the APPLICATIONS:\SqlServerWriter save set:




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


d. Click OK.


6. 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:\.


d. Click OK.


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






d. Click OK.

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


Backing up SharePoint Server 2007 for BMR 37

Performing BMR of SharePoint Server 2007

Procedure


2. After the machine restarts:


b. Select the server and click Recover.

c. Select the following save sets:

l APPLICATIONS:\SqlServerWriter

l APPLICATIONS:\Microsoft Office SharePoint Services

d. Perform the recovery.




CHAPTER 5

Microsoft Exchange Server Backup and BMR

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

Microsoft Exchange Server Backup and BMR 39

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

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

Backing up Exchange Server 2013 by using the NMM Client Configuration WizardSeparately create a client resource to back up the application data and the file systemdata which includes the DISASTER_RECOVERY:\ save set.

The Create a client resource using the Client Configuration Wizard section in theNetWorker Module for Microsoft for Exchange Server VSS Release 8.2 SP1 User Guideprovides information about how to create a client resource to back up the applicationdata.

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

Backing up Exchange Server 2013 by using the NetWorker Administrator programThe following figure illustrates the sample configuration that the procedures use.

Figure 1 Sample configuration for BMR backups of Exchange Server 2013

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

Procedure

1. Create a backup group for system backup:




c. Click OK.








g. Click OK.

2. Create a client resource for system backup:




c. Click OK.





l In the Group list, select the group that you created for system backup.

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

f. On the Apps & Modules tab, ensure that the Backup command and Applicationinformation 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:


b. Select Snapshot.



e. Click OK.

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



Backing up Exchange Server 2013 for BMR 41


l In the Application information field, type the following:NSR_SNAP_TYPE=vssNSR_ALT_PATH=<C:\Temp location>NSR_EXCH2010_BACKUP=<Active/Passive/All> orNSR_EXCH_BACKUP=<Active/Passive/All >NSR_EXCH2010_DAG=<Dag Client Instance> or NSR_EXCH_DAG=<DagClient Instance>


e. Click OK.

7. Back up the application data.


Performing BMR of Exchange Server 2013Run the following command to mount the database:

mount-database -identity <database name> -forceProcedure


2. If you have installed Exchange Server 2013 on a drive other than the system drive, usethe NetWorker client to recover the drive. During the recovery, if the Naming Conflictdialog box appears as shown in the following figure, select Rename the Recover Fileand click OK.

Figure 2 Naming conflict

3. After the recovery completes, restart the machine to start all the Exchange services.

4. After the machine restarts, ensure that you meet the following requirements:

a. You have recovered all the critical volumes.

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



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



Backing up Exchange Server 2010 for BMR by using the NMM Client Configuration WizardPerform the procedures that the Backing up Exchange Server 2013 by using the NMMClient Configuration Wizard on page 40 section describes.

Backing up Exchange Server 2010 for BMR by using the NetWorker Administrator programThe following figure illustrates the sample configuration that the procedures use.

Figure 3 Sample configuration for BMR backups of Exchange Server 2010

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

Procedure

1. Create a backup group for system backup:




c. Click OK.





Exchange Server 2010 43



g. Click OK.

2. Create a client resource for system backup:




c. Click OK.





l In the Group list, select the group that you created for system backup.


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

g. Specify other fields according to your requirements.

h. Click OK.

3. Back up the system data.


5. Create a backup group for application backup:


b. Select the Snapshot option.



e. Click OK.

6. 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:\MicrosoftExchange 2010.



l In the Application information field, type the following:NSR_SNAP_TYPE=vss



NSR_ALT_PATH=<C:\Temp location>NSR_EXCH2010_BACKUP=<Active/Passive/All>NSR_EXCH2010_DAG=<Dag Client Instance>


e. Click OK.

7. Back up the application data.


Performing BMR of Exchange Server 2010Run the following command to mount the database:

mount-database -identity <database name> -forceProcedure


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 thevolumes had before the disaster.

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



Backing up Exchange Server 2007 for BMR by using the NMM Client Configuration WizardPerform the procedures that the Backing up Exchange Server 2013 by using the NMMClient Configuration Wizard on page 40 section describes.


Performing BMR of Exchange Server 2010 45

Backing up Exchange Server 2007 for BMR by using the NetWorker Administrator programThe following figure illustrates the sample CCR configuration that the procedures use.

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

Procedure

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




c. Click OK.






g. Click OK.

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




c. Click OK.





l In the Group list, select the group that you created to back up critical volumeson the active node.





g. Click OK.


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

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


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


b. Select Snapshot.


d. Click OK.

8. Create the Exchange virtual server active node client instance:



l In the Group list, select the group that you created to back up the Exchangevirtual server instance on the active node.

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



l In the Application information field, type the following:NSR_SNAP_TYPE=vssNSR_ALT-Path=C:\RM_MountPOINTNSR_VIRT_SERV=Exch2k7VirtualNSR_INDEX_CLIENT=Exch2k7Virtual


e. Click OK.


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

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:


l In the Application information field, type the following:NSR_SNAP_TYPE=vssNSR_ALT-Path=C:\RM_MountPOINT


Backing up Exchange Server 2007 for BMR 47


d. Click OK.


Performing BMR of Exchange Server 2007

Procedure

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

2. After both the machines restart:

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

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

c. Go to Recover > Exchange Recover Session > Database Recover.

Run the following command to mount the database:

mount-database -identity <database name> -forced. Select the storage groups and perform the conventional point-in-time recovery to

bring the Exchange storage groups back online. The NetWorker Module for MicrosoftRelease 8.2 SP1 Administration Guide provides information about conventionalpoint-in-time recovery.



CHAPTER 6

Microsoft Hyper-V Backup and BMR

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

Microsoft Hyper-V Backup and BMR 49

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

Backing up Hyper-V for BMR by using the NMM Client Configuration WizardSeparately create a client resource to back up the application data and the file systemdata which includes the DISASTER_RECOVERY:\ save set.

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

Backing up a SQL Server 2014, 2012, or 2008 R2 for BMR by using the NMM ClientConfiguration Wizard on page 22 provides information about how to create a clientresource to back up the file system 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-node1

l Physical Node2: nmm-csv-node2

l Virtual Server: nmm-csv-cluster

Procedure

1. Create a backup group for Hyper-V:




c. Click OK.

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



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

c. Click OK.






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




g. Click OK.

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

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



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

c. Click OK.


d. Right-click the client, and select Properties.




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


g. Click OK.


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

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




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


d. Click OK.


8. Create a client resource to backup the All save set:






d. Click OK.



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

Performing BMR of Hyper-VEnsure that the cluster service account is enabled. Otherwise, the explorer hangs whenyou 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................................ 54l Performing BMR of a System Center Virtual Machine Manager............................... 56

Microsoft System Center Virtual Machine Manager Backup and BMR 53

Backing up System Center Virtual Machine Manager for BMRYou must back up and recover the following key components of VMM to ensure aprotected VMM environment:

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 NetWorker Module for Microsoft for Hyper-V VSSRelease 8.2 SP1 User Guide provides information about how to back up yourenvironment’s virtual machines.

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 NetWorker Module for Microsoft for Hyper-V VSS Release 8.2 SP1 User Guide providesinformation about 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 themachine 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 machine account is available to interact with the VMM database afterrecovery.

l All virtual machine hosts associates and communicates with the VMM server.

l You can recover any communication certificates so that the existing agents continueto 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 data file

Microsoft System Center Virtual Machine Manager Backup and BMR


which is typically %ProgramData%\Microsoft\Virtual Machine Manager\HyperVAuthStore.xml when protecting the critical system drive.

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 2014, 2012, or 2008 R2 forBMR by using the NMM Client Configuration Wizard on page 22 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 2014, 2012, or 2008 R2 forBMR by using the NMM Client Configuration Wizard on page 22 describes to configurea NetWorker client resource.

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 8.2 SP1 clients support the backup and restore of SQL databases.

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

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 55

Results

The NetWorker Module for Microsoft for SQL VDI Release 8.2 SP1 User Guide providesinformation about how to protect a SQL server.

Performing BMR of a System Center Virtual Machine ManagerThe VMM components have interdependencies. So, recover the entire VMM environmentfor a 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 that the Windows Bare Metal Recovery to Physical or VirtualComputers section in the NetWorker Release 8.2 SP1 Administration Guide describes.

Performing BMR of the VMM libraryPerform the following steps to perform BMR of VMM library:

Procedure


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 Windows Bare Metal Recovery to Physical or VirtualComputers section in the NetWorker Release 8.2 SP1 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 and



start 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 recreate 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 21 provides more information about how to perform BMR of SQL Server.


Performing BMR of the VMM database 57



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 Volume Shadow Copy Service (VSS) writer that is responsible for identifying criticaldata that is needed to perform an offline restore.

B

backup group See group

backup volume See 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 See NetWorker client

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 1. A group of independent network servers that operate and appear to clients as if theywere a single unit.

2. A group of disk sectors. The operating system assigns a unique number to each clusterand then keeps track of files according to which clusters they use.


critical volume A critical volume can be any of the following types of volumes:

l Any volume that contains system state files or files for an installed service, includingvolumes mounted as NTFS directories that contain such files. An example of aninstalled service is the Exchange 2010 application binaries. However, the Exchangedatabase and log files are not considered critical.

l Any parent volume where a critical volume is mounted.

l All volumes on all dynamic disks if at least one of those volumes is critical.

l A current backup of all critical volumes that is required to perform a Windows BMR.

D

disaster recovery The restoration of a computer operating system and its data after a catastrophic failuresuch as a hard disk failure or the corruption of critical operating system components. Adisaster recovery might not be a bare metal recovery.

G

group A client or group of clients configured to start backing up files to the NetWorker server at adesignated time of day.

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 A computer that has the NetWorker client software installed and can access the backupand recover services from a NetWorker server.

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 The computer on a network running the NetWorker software, containing the online indexes,and providing backup and recovery services to the clients on the same 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.

Glossary


O

offline restore A restore operation that is performed from the NetWorker Windows Disaster Recovery bootimage. An offline restore is an automated process, and does not require the manualinstallation 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. Anonline restore requires that the computer has been booted from an installed operatingsystem.

R

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

S

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

save set A set of files backed up onto storage media using the NetWorker software.

save set ID An internal identification number that NetWorker software assigns to a save set.

V

volume A unit of storage media, such as a magnetic tape, an optical disk, or a file. A storage devicereads from and writes to volumes, which can be physical units (for example, a labeled tapecartridge) or logical units (for example, optical media can store multiple volumes on asingle physical platter).

volume ID The internal identification NetWorker software assigns to a backup volume

volume name The name assigned to a backup volume when it is labeled.

Glossary


Glossary


Documents

EMC NetWorker Module for Microsoft for Windows Bare · PDF fileEMC® NetWorker® Module for Microsoft for Windows Bare Metal Recovery Solution Version 8.2 Service Pack 1 User Guide