EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution

Transcription

1 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution Version 9.0 User Guide REV 01

2 Copyright EMC Corporation. All rights reserved. Published in USA. Published September, 2015 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to EMC Online Support ( EMC Corporation Hopkinton, Massachusetts In North America EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

3 CONTENTS Tables 5 Preface 7 Chapter 1 Introduction 11 Bare Metal Recovery overview System requirements Supported operating systems Supported Microsoft applications NetWorker software version requirements Microsoft BMR requirements CPU requirements Hard disk requirements...13 NIC driver requirements...14 Critical and noncritical volume requirements...14 System Reserved Partition requirements Rollover requirements Protecting an environment before a disaster...15 BMR by using NetWorker and NMM Chapter 2 Microsoft Active Directory Backup and BMR 17 Backing up an Active Directory for BMR Performing BMR of an Active Directory...18 Chapter 3 Microsoft SQL Server Backup and BMR 19 SQL Server in a cluster environment Backing up a SQL Server for BMR by using the VDI technology...20 Performing BMR of a SQL Server SQL Server in a standalone environment Backing up a SQL Server for BMR by using the VSS technology...24 Performing BMR of a SQL Server Chapter 4 Microsoft SharePoint Server Backup and BMR 27 SharePoint Server 2013 and Backing up SharePoint Server 2013 or 2010 for BMR Performing BMR of SharePoint Server 2013 or SharePoint Server Backing up SharePoint Server 2007 for BMR Performing BMR of SharePoint Server Chapter 5 Microsoft Exchange Server Backup and BMR 35 Backing up an Exchange Server for BMR Backing up an Exchange Server by using the NetWorker Client Backup Configuration Wizard...36 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide 3

4 CONTENTS Backing up an Exchange Server by using the NetWorker Administrator program Performing BMR of an Exchange Server Chapter 6 Microsoft Hyper-V Backup and BMR 39 Backing up Hyper-V for BMR Backing up Hyper-V for BMR by using the NetWorker Client Backup Configuration Wizard...40 Backing up Hyper-V for BMR by using the NetWorker Administrator program Performing BMR of Hyper-V...41 Chapter 7 Microsoft System Center Virtual Machine Manager Backup and BMR 43 Backing up System Center Virtual Machine Manager for BMR Backing up the VMM server for BMR Backing up the VMM library for BMR...45 Backing up the VMM database for BMR...45 Performing BMR of a System Center Virtual Machine Manager Performing BMR of the VMM server Performing BMR of the VMM library Performing BMR of the VMM database Glossary 49 4 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

5 TABLES Revision history... 7 Style conventions... 8 Sample SharePoint Server 2010 configuration...28 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide 5

6 TABLES 6 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

7 Preface As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions that are described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your EMC technical support professional if a product does not function correctly or does not function as described in this document. Note This document was accurate at publication time. Go to EMC Online Support ( support.emc.com) to ensure that you are using the latest version of this document. Purpose The purpose of this guide is to provide detailed information about performing Windows Bare Metal Recovery by using EMC NetWorker Module for Microsoft. Audience This guide is part of the EMC NetWorker Module for Microsoft documentation set. It is intended for use by system administrators to perform Windows Bare Metal Recovery of Microsoft applications. Readers should be familiar with the following technologies used in backup and recovery: EMC NetWorker software EMC NetWorker snapshot management Microsoft Volume Shadow Copy Service (VSS) technology Revision history The following table presents the revision history of this document. Table 1 Revision history Revision Date Description 01 September, 2015 First release of this document for EMC NetWorker Module for Microsoft 9.0. Related documentation The NMM documentation set includes the following publications: EMC NetWorker Module for Microsoft Release Notes EMC NetWorker Module for Microsoft Administration Guide EMC NetWorker Module for Microsoft Installation Guide EMC NetWorker Module for Microsoft for SQL and SharePoint VSS User Guide EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide 7

8 Preface EMC NetWorker Module for Microsoft for SQL VDI User Guide EMC NetWorker Module for Microsoft for Exchange VSS User Guide EMC EMC NetWorker Module for Microsoft for Hyper-V VSS User Guide EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution User Guide EMC NetWorker Performing backup and recovery of SharePoint Server by using NetWorker Module for Microsoft SQL VDI solution Technical Notes EMC NetWorker Performing Exchange Server Granular Recovery by using NetWorker Module for Microsoft with Ontrack PowerControls Technical Notes EMC NetWorker SharePoint BLOB Backup and Recovery by using NetWorker Module for Microsoft and Metalogix StoragePoint Technical Notes Special notice conventions that are used in this document EMC uses the following conventions for special notices: NOTICE Addresses practices that are not related to personal injury. Note Presents information that is important, but not hazard-related. Typographical conventions EMC uses the following type style conventions in this document: Table 2 Style conventions Bold Italic Monospace Used for names of interface elements, such as names of buttons, fields, tab names, and menu paths (what the user specifically selects or clicks) Used for full titles of publications that are referenced in text Used for: System code System output, such as an error message or script Pathnames, file names, prompts, and syntax Commands and options Monospace italic Monospace bold Used for variables 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 the example Where to get help EMC support, product, and licensing information can be obtained as follows: 8 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

9 Preface Product information For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at Technical support Go to EMC Online Support and click Service Center. Several options for contacting EMC Technical Support appear on the site. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. Online communities Go to EMC Community Network at for peer contacts, conversations, and content on product support and solutions. Interactively engage online with customers, partners, and certified professionals for all EMC products. Your comments Your suggestions help to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to [email protected]. EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide 9

10 Preface 10 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

11 CHAPTER 1 Introduction This chapter includes the following sections: Bare Metal Recovery overview System requirements Protecting an environment before a disaster...15 BMR by using NetWorker and NMM Introduction 11

12 Introduction Bare Metal Recovery overview System requirements Supported operating systems This guide provides detailed information about Windows Bare Metal Recovery (BMR) solution by using EMC NetWorker and EMC NetWorker Module for Microsoft (NMM), how this solution works, and the procedures that you are required to follow for BMR of the supported Microsoft applications. BMR is a technique in the field of data recovery and restoration where the backed up data is available in a form that allows you to restore a system from bare metal, that is, without any requirements as to previously installed software or operating system. Typically, the backed up data includes the necessary operating system, applications, and data components to rebuild or restore the backed up system to an entirely separate piece of hardware. The hardware receiving the restore should have a similar configuration as that of the hardware that was the source of the backup. The basic BMR is the process of bringing up a server after a disaster and ensuring that the system recovers with the operating system, the applications, and the data as they were at the time of the failure. Restoring a server to the exact configuration that it had at the time of its destruction can be a difficult task. When this restoration is performed to another hardware, it can add to the complexity of the process and can be time-consuming. Windows BMR solution provides a flexible and reliable method of restoring a server after a disaster. The following sections list requirements to perform Windows BMR. The EMC NetWorker Online Software Compatibility Guide that is available on the products/1095/topics/pg41054/ page also provides the information about the versions of the supported operating systems, the software and hardware requirements, and the exact versions of the Microsoft applications to perform Windows BMR. Windows Server 2012 R2 (x64) Windows Server 2012 (x64) Windows Server 2008 SP2 (x86 and x64) Windows Server 2008 R2 SP1 (x64) Windows Server 2008 R2 (x64) Supported Microsoft applications Windows Server 2008 (x86 and x64) Active Directory SQL Server 2014 RTM SQL Server 2012 SP2 SQL Server 2008 R2 SP3 SQL Server 2008 SP4 SQL Server 2005 SP4 SharePoint Server EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

13 Introduction SharePoint Server 2010 SharePoint Server 2007 Exchange Server 2013 Exchange Server 2010 Hyper-V Server System Center Virtual Machine Manager NetWorker software version requirements Microsoft BMR requirements NetWorker server 7.6 SP3 or later NetWorker client 9.0 NetWorker Management Console 9.0 Use the NetWorker Windows BMR 32-bit ISO image to recover an x86 operating system on either an x86 or x64 computer Use the NetWorker Windows BMR 64-bit ISO image to recover only an x64 operating system on an x64 computer Perform BMR recoveries to the same or similar hardware, and physical to virtual environment. The following Microsoft KB article provides the requirements to perform a BMR to similar hardware: CPU requirements The operating system architecture and the processor architecture must match. Hard disk requirements The firmware Basic Input/Output System (BIOS) or Unified Extensible Firmware Interface (UEFI) must match. You can treat AMD or Intel processors as being the same if they follow the same architecture. You can recover the operating system backup of an AMD x64 computer to an Intel x64 computer. The process is reversible. You can restore the backup of an x86 operating system version only to an x86 processor computer. You can restore the backup of an x64 operating system version only to an x64 processor computer. The disk or RAID drivers that are used in the old system must be compatible with the disk or RAID controllers in the new system. For each critical disk on the BMR target system, the startup hard disk capacity on the new system must be greater than or equal to the capacity on the old system. BMR fails if the capacity is smaller by even a single byte. Windows BMR supports IDE, SATA, or SCSI hard disks. You can perform the backup on one type of hard disk and recover on another type. For example, SAS to SATA is supported. NetWorker software version requirements 13

14 Introduction NIC driver requirements You must restore the backup to the same logical disk numbers as on the original server. You cannot use different logical disk numbers on the target system to recover the critical volumes such as the operating system volume. Ensure that the RAID setup on destination computer does not interfere with the disk order of the hard disks. To use different Network Interface Card (NIC) after a Windows BMR recovery, install new NIC drivers that match the NIC in the new computer after Windows boots on the new server. Critical and noncritical volume requirements 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. Note System Reserved Partition requirements NetWorker 9.0 considers only system volume as a critical volume. If you have installed a Microsoft application on a drive other than the system drive, the drive is not considered as critical. On Windows Server 2008 R2, a volume is critical if a Microsoft application has installed a Windows service on it, but on Windows Server 2012, a volume that has a Windows application service installed is not critical. To make a volume critical on Windows Server 2012, set the value of the HKLM \System\CurrentControlSet\Control\SystemWriter \ReportWin32ServicesNonSystemState registry key to 0. This ensures that BMR includes the Microsoft application binaries, and the volume on which they are installed is marked as critical. Ensure that System Reserved Partition (SRP) is online before you perform a BMR backup. Otherwise, the backup fails and displays the following error message: 84687:save: Unable to get volume information of file system '\\? \Volume{245204f6-5ff7-11e2-a3ac-806e6f6e6963}\': The device is not ready. (Win32 error 0x15). VSS OTHER: ERROR: VSS failed to process snapshot: The shadow copy provider had an unexpected error while trying to process the specified operation. (VSS error 0x f) 90108:save: Unable to save the SYSTEM STATE save sets: cannot create the snapshot :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 14 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

15 Introduction Rollover requirements Perform daily rollovers to avoid the following issues: Manual rollover of the snapshot fails. When you back up a save set with the snapshot policy 1/1/day/none, the process applies retention and deletes the stale snapshot entry. Protecting an environment before a disaster To prepare for disaster recovery, back up application data and other necessary files. Procedure 1. Use NetWorker client to back up non-application data. The EMC NetWorker 9.0 Administration Guide provides details about using NetWorker client to back up the non-application files. 2. Create a NetWorker group without the Snapshot option enabled. 3. Create a NetWorker client resource, and assign it to the group that you created in step Configure the NetWorker client resource by typing All in the Save set field, and clearing the Backup command and Application information fields. 5. Perform a backup. 6. Use NMM to perform a full backup of application data. The EMC NetWorker Module for Microsoft 9.0 application specific user guides provide details about how to perform a full backup. BMR by using NetWorker and NMM From NMM 3.0 onwards, perform Windows file system backup and recovery by using the NetWorker client, and application-specific backup and recovery by using NMM. Specific information about how the backup and recovery process for various Microsoft applications in NMM 3.0 differs from previous NMM releases is provided in applicationspecific user guides. NetWorker disaster recovery provides an automated BMR solution by using the Windows ASR writer and other VSS writers to identify critical volumes that are needed to perform a disaster recovery on a disabled system. BMR is performed offline, that is, when the Windows operating system is inactive. This avoids the necessity to manually reinstall Windows, and the problems that occur when operating system files are being restored to an active Windows system. NMM 9.0 is compatible with the NetWorker 9.0 client, which provides a true BMR capability for Windows Server 2012, Windows Server 2008 R2, and Windows Server This capability is built into the NetWorker client and provides BMR support to the same or similar hardware. For Windows BMR, you should download the appropriate.iso recovery boot image file from EMC Online Support ( The ISO image provides a wizard that allows you to format disks, recover Windows critical volumes from backup, and reboot the server to bring it back online. To support a NetWorker Windows BMR recovery, download the Windows BMR image from EMC Online Support ( This download enables you to create a Rollover requirements 15

16 Introduction bootable Windows BMR ISO that contains NetWorker binaries and a wizard, which controls the recovery process. The Windows Bare Metal Recovery to Physical or Virtual Computers section in the EMC NetWorker Administration Guide provides detailed information about how to use the NetWorker Windows BMR image to perform a BMR recovery on protected hosts and VMware virtual machines. NOTICE For all the Microsoft applications, after performing Windows disaster recovery and restarting the system, check all the disk and volume configurations. In most cases, the disks and volumes appear as on the original system. However, it is possible, especially in BMR scenarios, that the volume or disk signatures do not match the original ones, and the non-critical volumes or disks are offline and not mounted. Use the Microsoft Disk Manager to bring the volumes and disks online, and then restart the system for drive letter reassignments. Assign the same drive letters that existed before the BMR. Non-critical volumes that the mount points access might have a similar issue. 16 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

17 CHAPTER 2 Microsoft Active Directory Backup and BMR This chapter includes the following sections: Backing up an Active Directory for BMR Performing BMR of an Active Directory...18 Microsoft Active Directory Backup and BMR 17

18 Microsoft Active Directory Backup and BMR Backing up an Active Directory for BMR Procedure 1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, and an action for Active Directory. The Data Protection Policies chapter in the EMC NetWorker Administration Guide provides 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: In the Group list, select the group that you created in step 1. In the Save set field, type All. b. On the Apps & Modules tab, ensure that the Backup command and Application information fields are clear. c. Specify other fields according to your requirements. d. Click OK. 5. Perform the backup. Performing BMR of an Active Directory Procedure 1. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the EMC NetWorker Administration Guide describes. The Performing post-recovery tasks for Active Directory services section in the EMC NetWorker Administration Guide provides information about how to perform an authoritative recovery of Active Directory. 2. Verify whether you can successfully log in as the domain administrator. 3. Verify whether all the Active Directory objects are present in both the Active Directory Users and the Computers and Domain Name System management. 18 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

19 CHAPTER 3 Microsoft SQL Server Backup and BMR This chapter includes the following sections: SQL Server in a cluster environment SQL Server in a standalone environment Microsoft SQL Server Backup and BMR 19

20 Microsoft SQL Server Backup and BMR SQL Server in a cluster environment This section provides the BMR backup and recovery procedures for SQL Server by using the VDI technology in a cluster environment. Backing up a SQL Server for BMR by using the VDI technology Configure a SQL Server client resource to back up SQL Server for BMR by using the VDI technology. Backing up a SQL Server by using the NetWorker Client Backup Configuration Wizard Create 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 NetWorker Module for Microsoft for SQL VDI User Guide provides information about how to create a client resource to back up the application data. The Creating a client resource with the Client Backup Configuration Wizard section in the EMC NetWorker Administration Guide provides information about how to create a client resource to back up the file system data. Backing up a SQL Server by using the NetWorker Administrator program This procedure uses the following sample SQL Server configuration: You have installed SQL Server on cluster volume P:\. The cluster quorum drive is E:\. You have clustered all the drives except the C:\ drive in the cluster. Note The procedures apply to 2014, 2012, 2008, and 2005 versions also, in a cluster environment. Procedure 1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, and an action for Active Directory. The Data Protection Policies chapter in the EMC NetWorker Administration Guide provides information. 2. Create a client resource to back up the DISASTER_RECOVERY:\ save set on the active node: 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 active node. d. Click OK. 3. In the right panel, right-click the client resource and select Modify Client Properties. 20 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

21 Microsoft SQL Server Backup and BMR 4. In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created in step 1. In the Save set field, type DISASTER_RECOVERY:\. b. Specify other fields according to your requirements. c. Click OK. 5. Perform the backup. 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): 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 Windows cluster. d. Click OK. 8. In the right panel, right-click the client resource and select Modify Client Properties. 9. In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created in step 1. In the Save set field, type All. b. Specify other fields according to your requirements. c. Click OK. 10.Perform the backup. 11.Create a client resource with SQL virtual name to back up the All save set (SQL cluster drives): 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 SQL virtual name. d. Click OK. 12.In the right panel, right-click the client resource and select Modify Client Properties. 13.Perform step 9 and step Create a client resource with SQL virtual name to back up the SQL application data: 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. Backing up a SQL Server for BMR by using the VDI technology 21

22 Microsoft SQL Server Backup and BMR c. In the Name field, type the SQL virtual name. d. Click OK. 15.In the right panel, right-click the client resource and select Modify Client Properties. 16.In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created in step 1. In the Save set field, type MSSQL: if the SQL instance is either the default instance or a named instance in the cluster. b. On the Apps & Modules tab, in the Backup command field, type nsrsqlsv. c. Specify other fields according to your requirements. d. Click OK. 17.Create dummy client resources for the physical nodes of the cluster. 18.Perform the backup. Performing BMR of a SQL Server The BMR process recovers C: drive only. It does not recover the SQL data, the quorum and SQL cluster drives, and the system databases such as master, msdb, and model. Procedure 1. Separately recover the active and passive nodes by performing the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the 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 disks are online on the active node in the Disk Management Console of the Windows GUI. b. Add the quorum drive to Failover Cluster Management of the Cluster Configuration UI. c. Select the storage node in Failover Cluster Management and ensure that the quorum disk is online. d. On the SQL Server active node, start the NetWorker User program. e. Click Recover. f. In the Source Client dialog box, select the source client with the Windows cluster name, and click OK. g. In the Destination Client dialog box, select the destination client with the active node name, and click OK. h. Select the quorum drive and recover the drive. 3. Recover the SQL cluster drives: a. Add the SQL drives to Failover Cluster Management of the Cluster Configuration UI. b. Ensure that the disk is online. c. Configure the drive mount points between the drives so that the mount points are the same as the mount points during the backup. 22 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

23 Microsoft SQL Server Backup and BMR d. On the SQL Server active node, start the NetWorker User program. e. Click Recover. f. In the Source Client dialog box, select the source client with the SQL virtual name and click OK. g. In the Destination Client dialog box, select the destination client with the active node name and click OK. h. Select all the SQL cluster drives and recover the drives. 4. Build the msdb and model databases: a. Start the physical nodes of the cluster. b. Ensure that you have the SQL Server installation software on the active node. c. In the software, go to the folder where the SETUP file exists and run the following command: Setup /QUIET/ACTION=REBUILDDATABASE/INSTANCENAME=<SQL Server instance name>/sqlsysadminaccounts=<domain \administrator username>/iacceptsqlserverlicenseterms 5. In the Failover Cluster Management window of the Cluster Configuration UI, perform the following steps: 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 must bring online before you bring the SQL Server online. For example, any dependent cluster disk. c. Bring the SQL virtual resources online. d. Bring the SQL Server online. e. Perform the failover and ensure that the failover is successful. To rebuild databases on SQL Server 2012, go to To rebuild databases on SQL Server 2008, go to Performing BMR of a SQL Server 23

24 Microsoft SQL Server Backup and BMR To rebuild databases on SQL Server 2005, go to 6. Restore the databases by using the NetWorker User for SQL Server program: a. Start the NetWorker User for SQL Server program, and connect to the SQL virtual server instance. b. Browse the backed up databases. c. Select the databases and restore the databases. SQL Server in a standalone environment This section provides the BMR backup and recovery procedures for SQL Server by using the VSS technology in a standalone environment. Backing up a SQL Server for BMR by using the VSS technology Configure a SQL Server client resource to back up SQL Server for BMR by using the VSS technology. Backing up a SQL Server by using the NetWorker Client Backup Configuration Wizard Create 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 NetWorker Module for Microsoft for SQL VDI User Guide provides information about how to create a client resource to back up the application data. The Creating a client resource with the Client Backup Configuration Wizard section in the EMC NetWorker Administration Guide provides information about how to create a client resource to back up the file system data. Backing up a SQL Server by using the NetWorker Administrator program Procedure 1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, and an action for Active Directory. The Data Protection Policies chapter in the EMC NetWorker Administration Guide provides information. 2. Create a client resource to back up the DISASTER_RECOVERY:\ save set: 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 of 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: 24 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

25 Microsoft SQL Server Backup and BMR a. On the General tab: In the Group list, select the group that you have created in step 1. In the Save set field, type DISASTER_RECOVERY:\. b. On the Apps & Modules tab, ensure that the Backup command and Application information fields are clear. c. Specify other fields according to your requirements. d. Click OK. 5. Perform the backup. 6. Create a client resource to back up the All save set. Perform step a to step d of step In the right panel, right-click the client resource and select Modify Client Properties. 8. In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you have created in step 1. In the Save set field, type All. b. Specify other fields according to your requirements. c. Click OK. 9. Perform the backup. 10.Create a client resource to back up the APPLICATIONS:\ SqlServerWriter save set: Perform step a to step d of step In the right panel, right-click the client resource and select Modify Client Properties. 12.In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you have created in step 1. In the Save set field, type APPLICATIONS:\ SqlServerWriter. b. On the Apps & Modules tab: In the Backup command field, type nsrnmmsv. In the Application information field, type NSR_SNAP_TYPE=VSS. c. Specify other fields according to your requirements. d. Click OK. 13.Perform the backup. Backing up a SQL Server for BMR by using the VSS technology 25

26 Microsoft SQL Server Backup and BMR Performing BMR of a SQL Server The BMR process recovers only the C: drive. It does not recover the SQL data, quorum and SQL cluster drives, or the system databases such as master, msdb, and model. Procedure 1. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the EMC NetWorker Administration Guide describes. 2. Start the NMM GUI. 3. Select the server and click Recover. 4. Under the APPLICATIONS save set, select SqlServerWriter. 5. Perform the recovery. 6. Ensure that the SQL Server service starts for the recovered instance. 7. To verify whether you have recovered the databases, open SQL Server Management Studio and connect to the instance. The databases that belong to the instance appear. 26 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

27 CHAPTER 4 Microsoft SharePoint Server Backup and BMR This chapter includes the following sections: SharePoint Server 2013 and SharePoint Server Microsoft SharePoint Server Backup and BMR 27

28 Microsoft SharePoint Server Backup and BMR SharePoint Server 2013 and 2010 This section provides the BMR backup and recovery procedures for SharePoint Server 2013 and Note NMM 9.0 does not support the BMR backup and recovery of SharePoint 2013 and 2010 standalone servers with SQL embedded. Backing up SharePoint Server 2013 or 2010 for BMR Use the NetWorker Administrator program to create a SharePoint Server client resource to back up SharePoint Server for BMR. The following table provides the sample SharePoint farm configuration that the procedures use. Table 3 Sample SharePoint Server 2010 configuration Components Operating system Application version Critical volume NetWorker build SQL Server Windows Server 2008 R2 SP1 SQL Server 2008 R2 SP1 SQL application is installed on the C: drive. NetWorker 9.0 Databases reside on the C: drive. Web front-end server 1 Windows Server 2008 R2 SP1 SharePoint Server 2010 SP1 SharePoint Server 2010 Application is installed on C: drive. NetWorker 9.0 Web front-end server 2 Windows Server 2008 R2 SP1 SharePoint Server2010 SP1 SharePoint Application is installed on the E: drive. So, the critical volumes are the C: and E: drives. NetWorker 9.0 Backing up SharePoint Server 2010 includes backing up SQL Server, Web front-end server 1, and Web front-end server 2. Backing up SQL Server in a SharePoint Server 2010 environment Procedure 1. By using the NetWorker Administration GUI, create the first policy, workflow, group, and action for the SQL Server. The Data Protection Policies chapter in the EMC NetWorker Administration Guide provides information. 2. Create the first client resource for the SQL Server: 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. 28 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

29 Microsoft SharePoint Server Backup and BMR c. In the Name field, type the name for the client resource. d. Click OK. 3. In the NetWorker Administrator window, select the View tab and select Diagnostic Mode. 4. In the right panel, right-click the client resource and select Modify Client Properties. 5. In the Client Properties dialog box: a. On the General tab: Ensure that you have selected Scheduled backup. In the Group list, select the group that you created in step 1. In the Save set field, type DISASTER_RECOVERY:\. b. Specify other fields according to your requirements. c. Click OK. 6. Perform the backup. 7. By using the NetWorker Administration GUI, create the second policy, workflow, group, and action for the SQL Server. The Data Protection Policies chapter in the EMC NetWorker Administration Guide provides information. 8. Create the second client resource for the SQL Server. Perform step a through step d of step Perform step 3 and step In the Client Properties dialog box: a. On the General tab: Ensure that you have selected Scheduled backup. In the Group list, select the group that you created in step 6. In the Save set field, type APPLICATIONS:\SqlServerWriter. b. On the Apps & Modules tab, in the Backup command field, type nsrnmmsv. c. Specify other fields according to your requirements. d. Click OK. Backing up web front-end server 1 11.Perform the backup. Perform all the steps in Backing up SQL Server in a SharePoint Server 2010 environment on page 28 except the following substep of step 10a: In the Save set field, type APPLICATIONS:\SqlServerWriter. For the web front-end server 1, in the Save set field, type APPLICATIONS:\Microsoft Office SharePoint Services. Backing up SharePoint Server 2013 or 2010 for BMR 29

30 Microsoft SharePoint Server Backup and BMR Backing up web front-end server 2 The steps to perform the BMR backup of web front-end server 2 are the same as the steps in Backing up web front-end server 1 on page 29. Performing BMR of SharePoint Server 2013 or 2010 The following sections describe the recovery procedures for SQL Server, web front-end server 1, and web front-end server 2. Recovering SQL Server in a SharePoint 2010 environment Note The failure of a SQL master database recovery leads to the failure of the SharePoint disaster recovery. To proceed with recovery, move, rename, or delete the specified database files and perform the recovery from that point. The associated files are the master database file master.mdf, and the master log file mastlog.ldf. Procedure 1. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the EMC NetWorker Administration Guide describes. 2. After SQL Server restarts: a. Start the NMM GUI. Recovering the web front-end servers 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. Procedure 1. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the EMC NetWorker Administration Guide describes. 2. After web front-end server restarts: a. Start the NMM GUI. b. Select the server, and click Recover to recover the SharePoint configuration data. Use the NetWorker client to recover any other backed up file system drives. Ensure that the DISASTER_RECOVERY:\ save set is visible in the NetWorker client UI. c. Restart the machine if prompted. d. In the APPLICATIONS save set, select the SharePoint save sets, and perform the recovery. e. Restart the machine if prompted. 30 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

31 Microsoft SharePoint Server Backup and BMR SharePoint Server 2007 This section provides the BMR backup and recovery procedures for SharePoint Server Note NMM 9.0 does not support the BMR backup and recovery of SharePoint 2007 standalone server with SQL embedded. Backing up SharePoint Server 2007 for BMR The procedures use the following SharePoint Server 2007 configuration on Windows 2008 R2: You have configured the target machine with four processors and 8 GB of RAM. You have configured the environment with a single NIC. You have installed Windows 2008 R2 SP1 and updates on the C:\ drive. The NetWorker client performs the BMR backup by using non-snapshot. The NMM client backs up the following save sets by using the VSS writer based snapshot: APPLICATIONS:\Microsoft Office SharePoint Services APPLICATIONS:\SQLServerWriter Procedure 1. By using the NetWorker Administration GUI, create the first policy, workflow, group, and action for the SharePoint Server. The Data Protection Policies chapter in the EMC NetWorker Administration Guide provides information. 2. Create a client resource to back up the APPLICATIONS:\Microsoft Office SharePoint Services save set: 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 NetWorker Administrator window, select the View tab and select Diagnostic Mode. 4. In the right panel, right-click the client resource and select Modify Client Properties. 5. In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created in step 1. In the Save set field, type APPLICATIONS:\Microsoft Office SharePoint Services. SharePoint Server

32 Microsoft SharePoint Server Backup and BMR b. Specify other fields according to your requirements. c. Click OK. 6. Perform the backup on all machines in the SharePoint environment. 7. Create a client resource to back up the APPLICATIONS:\SqlServerWriter save set. Perform step a through step d of step Perform step 3 and step In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created in step 1. In the Save set field, type APPLICATIONS:\SqlServerWriter. b. Specify other fields according to your requirements. c. Click OK. 10.Perform the backup on all machines in the SharePoint environment. 11.Create a client resource to back up a non-critical volume. Perform step a through step d of step Perform step 3 and step In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created in step 1. In the Save set field, type a volume drive letter other than critical volumes, for example, D:\. b. Specify other fields according to your requirements. c. Click OK. 14.Perform the backup on all machines in the SharePoint environment. 15.Create a client resource to back up the DISASTER_RECOVERY:\ save set. Perform step a through step d of step Perform step 3 and step In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created in step 1. In the Save set field, type DISASTER_RECOVERY:\. b. Specify other fields according to your requirements. c. Click OK. 18.Perform backups on all machines in the SharePoint environment. 32 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

33 Microsoft SharePoint Server Backup and BMR Performing BMR of SharePoint Server 2007 Procedure 1. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the EMC NetWorker Administration Guide describes. 2. After the machine restarts: a. Start the NMM GUI. b. Select the server and click Recover. c. Select the following save sets: APPLICATIONS:\SqlServerWriter APPLICATIONS:\Microsoft Office SharePoint Services d. Perform the recovery. e. Restart the machine if prompted. Performing BMR of SharePoint Server

34 Microsoft SharePoint Server Backup and BMR 34 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

35 CHAPTER 5 Microsoft Exchange Server Backup and BMR This chapter includes the following sections: Backing up an Exchange Server for BMR Performing BMR of an Exchange Server Microsoft Exchange Server Backup and BMR 35

36 Microsoft Exchange Server Backup and BMR Backing up an Exchange Server for BMR Configure an Exchange Server client resource to back up an Exchange Server for BMR. Backing up an Exchange Server by using the NetWorker Client Backup Configuration Wizard Separately create a client resource to back up the application data and the file system data which includes the DISASTER_RECOVERY:\ save set. The Creating a client resource using the Client Backup Configuration wizard section in the EMC NetWorker Module for Microsoft for Exchange VSS User Guide provides information about how to create a client resource to back up the application data. The Creating a client resource with the Client Backup Configuration Wizard section in the EMC NetWorker Administration Guide provides information about how to create a client resource to back up the file system data. Backing up an Exchange Server by using the NetWorker Administrator program Create two client resources for the Database Availability Group (DAG) node. You use one client resource to back up the system data (critical volumes) and the other client to back up the application data (non-critical volumes). Procedure 1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, and an action for system backup. The Data Protection Policies chapter in the EMC NetWorker Administration Guide provides information. 2. Create a client resource for system backup: 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 of 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: In the Group list, select the group that you created in step 1. In the Save set field, type DISASTER_RECOVERY:\. If you have installed Exchange Server 2013 on a drive other than the system drive, type the drive letter also. For example, E:\. b. On the Apps & Modules tab, ensure that the Backup command and Application information fields are clear. c. Specify other fields according to your requirements. 36 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

37 Microsoft Exchange Server Backup and BMR d. Click OK. 5. Perform the backup. 6. Ensure that the backup successfully completes. 7. By using the NetWorker Administration GUI, create a policy, a workflow, a group, and an action for application backup. The Data Protection Policies chapter in the EMC NetWorker Administration Guide provides information. 8. Create a client resource for application backup. Perform step a through step d of step In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created for application backup. In the Save set field, type the save set. For example, APPLICATIONS:\Microsoft Exchange 2013 or APPLICATIONS:\Microsoft Exchange b. On the Apps & Modules tab: In the Backup command field, type nsrnmmsv. In the Application information field, type the following: NSR_FEDERATED_BACKUP=yes NSR_FEDERATED_PSOL=<DAG_MEMBER_NODES> NSR_EXCH_DAG=<DAG_INSTANCE_NAME> NSR_EXCH_BACKUP=<preferred/passive/Active> NSR_EXCH_CHECK=<Yes/No> c. Specify other fields according to your requirements. d. Click OK. 10.Perform the backup. 11.Ensure that the backup successfully completes. Performing BMR of an Exchange Server Run the following command to mount the database: mount-database -identity <database name> -force Procedure 1. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the EMC NetWorker Administration Guide describes. 2. After the recovery completes, restart the machine to start all the Exchange services. 3. After the machine restarts, ensure that you meet the following requirements: a. You have recovered all the critical volumes. b. You have created all the non-critical volumes with the exact drive letters that the volumes had before the disaster. Performing BMR of an Exchange Server 37

38 Microsoft Exchange Server Backup and BMR c. You have selected a database, and performed recovery. d. You have successfully mounted the database after the recovery, and checked whether the recovery process has successfully recovered all s. 38 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

39 CHAPTER 6 Microsoft Hyper-V Backup and BMR This chapter includes the following sections: Backing up Hyper-V for BMR Performing BMR of Hyper-V...41 Microsoft Hyper-V Backup and BMR 39

40 Microsoft Hyper-V Backup and BMR Backing up Hyper-V for BMR Configure a Hyper-V client resource to back up Hyper-V for BMR. Backing up Hyper-V for BMR by using the NetWorker Client Backup Configuration Wizard Separately create a client resource to back up the application data and the file system data which includes the DISASTER_RECOVERY:\ save set. The Creating the client by using the Client Configuration Wizard section in the EMC EMC NetWorker Module for Microsoft for Hyper-V VSS User Guide provides information about how to create a client resource to back up the application data. The Creating a client resource with the Client Backup Configuration Wizard section in the EMC NetWorker Administration Guide provides information about how to create a client resource to back up the file system data. Backing up Hyper-V for BMR by using the NetWorker Administrator program The procedures use the following sample Hyper-V configuration on a Windows server: Physical Node1: nmm-csv-node1 Physical Node2: nmm-csv-node2 Virtual Server: nmm-csv-cluster Procedure 1. By using the NetWorker Administration GUI, create a policy, a workflow, a group, and an action for Hyper-V. The Data Protection Policies chapter in the EMC NetWorker Administration Guide provides information. 2. Create a client resource to backup the Hyper-V application data that the non-csv volumes host: 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 physical node. 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: In the Group list, select the group that you created in step 1. In the Save set field, type APPLICATIONS:\Microsoft Hyper-V. b. Specify other fields according to your requirements. c. Click OK. 40 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

41 Microsoft Hyper-V Backup and BMR 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 volumes host. Perform step a through d of step Perform steps 3 and Perform the backup. The process backs up only the virtual machines that the CSV hosts. You must have registered the CSV in the Cluster Manager. 9. Create a client resource to backup the non-critical volumes. Perform step a through step d of step Perform step In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created in step 1. In the Save set field, type a volume drive letter other than critical volumes, for example, D:\. b. Specify other fields according to your requirements. c. Click OK. 12.Perform the backup on all Hyper-V cluster nodes. 13.Create a client resource to backup the All save set. Perform step a through step d of step In the Client Properties dialog box: a. On the General tab: In the Group list, select the group that you created in step 1. In the Save set field, type All. b. Specify other fields according to your requirements. c. Click OK. Performing BMR of Hyper-V 15.Perform the backup on all Hyper-V cluster nodes. Ensure that the cluster service account is enabled. Otherwise, the explorer hangs when you browse CSVs and the recovery fails. To enable the cluster service computer account, log in to the Domain Controller with the domain administrator credentials, and use the Active Directory Users and Computer snapin. Procedure 1. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the EMC NetWorker Administration Guide describes. Performing BMR of Hyper-V 41

42 Microsoft Hyper-V Backup and BMR After the recovery completes, the status of Hyper-V VMs in the Failover Cluster Manager window are either Pending or Failed. 2. Reconfigure quorum and cluster storage (CSV and non-csv volumes): a. Create or configure the quorum, CSV, and non-csv shared volumes. b. Ensure that you have documented the drive letters for quorum and non-csv (shared volume) and used here. c. Ensure that you have configured the same CSV volume name as the original. 3. Recover all Hyper-V cluster nodes by using the NMM client. 4. Reconfigure the VMs with either the Pending or the Failed status. 5. Recover the Hyper-V VMs that the CSV volumes host with the virtual node as the client resource, by using the NMM client. 6. Recover the Hyper-V VMs that the non-csv volumes host with the physical node as the client resource, by using the NMM client. 42 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

43 CHAPTER 7 Microsoft System Center Virtual Machine Manager Backup and BMR This chapter includes the following sections: Backing up System Center Virtual Machine Manager for BMR Performing BMR of a System Center Virtual Machine Manager Microsoft System Center Virtual Machine Manager Backup and BMR 43

44 Microsoft System Center Virtual Machine Manager Backup and BMR Backing up System Center Virtual Machine Manager for BMR Backing up the VMM server for BMR Back up and recover the following key components of VMM to ensure a protected VMM environment: VMM server: The VMM server is the central component of a VMM deployment. The server contains the core Windows service that includes the VMM engine. VMM database: The VMM database resides on either the VMM server or on a remote database server. You must regularly save the VMM database to quickly recovery the VMM environment. VMM library: The VMM library is either one file server or multiple file servers with file shares that index specific file types that the VMM uses. The VMM library shares include VHD, VMDK, ISO, PS1, INF, VFD, FLP, and XML files besides stored virtual machines. You must frequently back up the data such as, the data on the virtual machines, which VMM manages, that often changes. NMM supports the Microsoft Hyper-V VSS writer to protect Hyper-V virtual machines. The EMC EMC NetWorker Module for Microsoft for Hyper-V VSS User Guide provides information about how to back up your environment 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 can protect it by using the NMM client s Hyper-V. Use NMMM to protect the VMM server, the VMM library, or the VMM database on a virtual machine. NMM takes image backups of Hyper-V virtual machines. You do not need to install an NMM client on the virtual machine. Instead, install an NMM client on the Hyper-V server and configure NMM client resources to back up the virtual machines. Use the NMM GUI Hyper-V plug-in to recover a virtual machine that contains a VMM component. The EMC EMC NetWorker Module for Microsoft for Hyper-V VSS User Guide provides information about how to protect a Hyper-V server s information. The VMM server relies on the VMM database to store data. The VMM database uses the machine account to encrypt that data. You must perform a full backup of the VMM server host to ensure that you meet the following requirements: The same machine account is available to interact with the VMM database after recovery. All virtual machine hosts associates and communicates with the VMM server. 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 along with an NMM backup of local file systems and application-specific data, such as the data associated with Hyper-V Server, SQL Server, or SharePoint Server. The advantage of a Windows BMR backup and recovery capability for a VMM server is that the backup includes the system state. When you perform recovery, the system state recovers the computer security identifier (SID) that uniquely identifies the computer to the network. The computer-recovered SID enables the VMM server to quickly and easily interact with any existing VMM database, VMM library, and managed servers without additional postrecovery operations. The Windows BMR backup captures the VMM authorization data file 44 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

45 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 Backing up the VMM library for BMR 1. Use the NetWorker client to back up the VMM server non-application files by specifying the All save set. This setting enables the backup of the local file systems and 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 NetWorker Client Backup Configuration Wizard on page 20 section describes. 2. Use an NMM client resource specification to perform a full backup of any application data on the VMM server. The VMM library is a catalog of resources that enables you to store objects that are not running or associated with a host. The library contains the files that are present on library shares, templates, operating system profiles, and hardware profiles. Procedure Backing up the VMM database for BMR Use the NMM backup and recovery techniques for Windows files servers to back up and recover a VMM library server. Use the NetWorker client to back up the VMM library by specifying the All save set to perform a Windows BMR backup of the VMM library. The All save set enables you to back up the local file systems and the DISASTER_RECOVERY:\ save set of the VMM library. Perform the procedure that the Backing up a SQL Server by using the NetWorker Client Backup Configuration Wizard on page 20 describes to configure a NetWorker client resource. The VMM database is a SQL Server database that contains all the configuration information for VMM. Give the highest priority to protect the VMM database. The default installation of VMM uses Windows Internal Database (WID), a version of Microsoft SQL Express, on the same host as the VMM server. The database name is MICROSOFT$VMM$\Virtual Manager DB. However, the VMM database can also reside on either an existing Microsoft SQL Server Standard or SQL Server Enterprise server. To find out the location of the database for VMM, inspect the Registry values entries under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\Sql key. NMM 9.0 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 about how 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. Backing up the VMM library for BMR 45

46 Microsoft System Center Virtual Machine Manager Backup and BMR 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 individual databases. Performing BMR of a System Center Virtual Machine Manager The VMM components have interdependencies. So, recover the entire VMM environment for 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 you shared 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. Performing BMR of the VMM server Performing BMR of the VMM library 4. After the operating system and VMM server are stable, perform the required postrecovery VMM steps that the Microsoft documentation describes. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the EMC NetWorker 9.0 Administration Guide describes. Procedure Performing BMR of the VMM database 1. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual computers section in the EMC NetWorker Administration Guide describes. 2. After you recover the file share directories, either adjust the VMM Library Refresher interval or manually trigger the Library Refresher to enable VMM to refresh the contents of the file server share. The VMM Administrator Console embedded help describes how to set the Library Refresher interval and perform a manual refresh. Perform the procedures that the Performing a Windows BMR recovery to physical or virtual 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 instance of 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 46 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

47 Microsoft System Center Virtual Machine Manager Backup and BMR start the VMM Windows service, VMM synchronizes the database with the VMM server and VMM library computers. Note You must reapply any changes that you made to the VMM environment between the time of the backup and the restore. For example, you must recreate the templates that you created 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 you perform a SQL Server recovery as part of BMR, Microsoft SQL Server Backup and BMR on page 19 provides more information about how to perform BMR of SQL Server. Performing BMR of the VMM database 47

48 Microsoft System Center Virtual Machine Manager Backup and BMR 48 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

49 GLOSSARY This glossary contains terms related to the NetWorker Module for Microsoft. Many of these terms are used in this manual. A application data ASR writer User data such as a log file that is created by the application, or user data such as an application database that is created with the application. For example, an SQL Server s application data includes its databases and log files. Application data is neither included in nor recoverable from a Windows BMR operation. Application data must be backed up and recovered with NMM. The Volume Shadow Copy Service (VSS) writer that is responsible for identifying critical data that is needed to perform an offline restore. B backup group backup volume Boot Configuration Data (BCD) See group See volume The BCD store contains boot configuration parameters, and controls how Microsoft Windows Server 2008 operating system starts. A backup of this ASR Writer component is required to perform an offline restore. C client client resource See NetWorker client NetWorker server resource that identifies the save sets to be backed up on a client. The Client resource also specifies information about the backup, such as the schedule, browse policy, and retention policy for the save sets. cluster 1. A group of independent network servers that operate and appear to clients as if they were a single unit. 2. A group of disk sectors. The operating system assigns a unique number to each cluster and then keeps track of files according to which clusters they use. EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide 49

50 Glossary critical volume A critical volume can be any of the following types of volumes: Any volume that contains system state files or files for an installed service, including volumes mounted as NTFS directories that contain such files. An example of an installed service is the Exchange 2010 application binaries. However, the Exchange database and log files are not considered critical. Any parent volume where a critical volume is mounted. All volumes on all dynamic disks if at least one of those volumes is critical. A current backup of all critical volumes that is required to perform a Windows BMR. D disaster recovery The restoration of a computer operating system and its data after a catastrophic failure such as a hard disk failure or the corruption of critical operating system components. A disaster recovery might not be a bare metal recovery. G group A client or group of clients configured to start backing up files to the NetWorker server at a designated time of day. M master database The SQL Server master database contains information about all SQL Server databases on the SQL Server host. N NetWorker NetWorker client NetWorker resource NetWorker server NetWorker Windows BMR image non-critical volume An EMC network-based software product for backing up and recovering file systems. A computer that has the NetWorker client software installed and can access the backup and recover services from a NetWorker server. A component of the s software that controls the functionality of the NetWorker server and its 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 specific parameters. 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. A bootable image that contains NetWorker binaries and a wizard to control the Windows BMR process. A volume that contains files that are not part of the system state or an installed service. 50 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide

51 Glossary O offline restore online restore A restore operation that is performed from the NetWorker Windows Disaster Recovery boot image. An offline restore is an automated process, and does not require the manual installation of an operating system. A BMR is an offline restore. A restore operation that is performed from the regular NetWorker recover user interface. An online restore requires that the computer has been booted from an installed operating system. R recovery The process of retrieving individual data files from backup storage and copying to disk. S save save set save set ID The NetWorker command that backs up client files to backup volumes and makes data entries in the online index. A set of files backed up onto storage media using the NetWorker software. An internal identification number that NetWorker software assigns to a save set. V volume volume ID volume name A unit of storage media, such as a magnetic tape, an optical disk, or a file. A storage device reads from and writes to volumes, which can be physical units (for example, a labeled tape cartridge) or logical units (for example, optical media can store multiple volumes on a single physical platter). The internal identification NetWorker software assigns to a backup volume The name assigned to a backup volume when it is labeled. EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide 51

52 Glossary 52 EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution 9.0 User Guide