EMC NetWorker Module for Microsoft Applications

Transcription

1 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide P/N REV 02

2 Copyright EMC Corporation. All rights reserved. Published in the USA. Published January, 2013 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 2, 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 ( 2 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

3 CONTENTS Preface Revision history Chapter 1 Chapter 2 Microsoft SQL Server VDI Backup and Recovery Overview SQL Server versions supported by NMM AlwaysOn Availability Group feature of Microsoft SQL Server Types of supported backups Traditional backup configurations Backup levels Types of supported recovery Recovery configurations Recovery modes Recovery time Recovery window restrictions Commands used in NMM for SQL Server VDI backup and recovery Error logs for backup and recovery Setting deduplication for SQL Server data Performing SQL Server manual backups Performing a backup with NetWorker User for SQL Server program Backup and recovery for Microsoft Cluster Servers The NetWorker client in a Microsoft Cluster The NMM software in a Microsoft Cluster How to run a scheduled backup Manual backups and recovery for a cluster Performing SQL Server scheduled backups Setting backup levels Configuring scheduled backups Unavailable databases and group backup failure Backing up the active portion of the transaction log Performing a SQL Server recovery Recovery requirements The recovery process Recovering SQL Server 2012 at instance level and database level Performing a recovery with NetWorker User for SQL Server Striped backup and recovery Interleaving Striped backups Striped recoveries Microsoft SQL Server VSS Backup and Recovery Overview Supported SQL Server versions AlwaysOn Availability Group feature of Microsoft SQL Server SQL Server Writer Types of supported backups EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 3

4 Contents Types of supported recovery Viewing valid application data save sets Configuring privileges for a user who does not have privileges on the NetWorker server Performing SQL Server scheduled backups Task 5: Configure a SQL Server client resource Performing SQL Server recovery Recovering SQL Server 2012 instance level Recovering SQL Server data in a non-clustered environment from the SQLServerWriter save set Recovering SQL Server Express databases from the SYSTEM COMPONENTS save set Recovering virtual SQL Server for SQL clusters Performing SQL Server directed recovery Requirements for SQL server directed recovery Unsupported types of directed recovery Configuring a SQL Server directed recovery Best practices and recommendations Chapter 3 Microsoft Exchange Server 2007 Backup and Recovery Overview Supported Exchange 2007 Server versions Required MAPI client and Collaboration Data Objects Types of supported backup Backup levels Types of supported recovery Exchange Server 2007 VSS Writers Compatibility with previous Exchange Server backups Creation of shadow copy and snapshot process in an Exchange Server production Example LAN-based Exchange Server configuration with a storage area network and a proxy client Configuring a dedicated storage node for Exchange 2007 CCR environment Configuring Avamar deduplication backups in a CCR Passive node backup environment Exchange consistency checker utility Configuring Exchange storage groups Viewing valid application data save sets Viewing required volumes for Exchange recovery Performing Exchange Server 2007 scheduled backups Backup requirements Configuring Exchange Server 2007 backups Performing Exchange Server 2007 recovery Recovery requirements Exchange recovery options Configuring Exchange recovery Selecting a storage group restore destination Performing Exchange Server 2007 directed recovery Performing a directed recovery Performing a quick recovery of a deleted mailbox in Exchange Server Performing an Exchange Server 2007 granular level recovery GLR considerations EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

5 Contents Performing an Exchange granular level recovery Performing a granular level recovery to an alternate mailbox Best practices and recommendations Exchange recovery limitations Chapter 4 Chapter 5 Microsoft Exchange Server 2010 Backup and Recovery Overview Circular logging is not supported Required MAPI client and Collaboration Data Objects Types of supported backup Types of supported recovery Exchange Server 2010 VSS Writers Backup initiated transaction log file truncation Viewing valid application data save sets Exchange database and log files can reside on the same LUN, volumes, and drives Viewing required volumes for Exchange recovery Performing Exchange Server 2010 scheduled backups Backup options Configuring persistent and non-persistent snapshots Configuring backups to use a remote storage node in a DAG environment Considerations for backing up Exchange Server 2010 in non-dag and DAG environment Exchange 2010 incremental backup promoted to full backup Configuring Exchange Server 2010 backups Verifying backups Configuring Avamar deduplication backups in a DAG environment Performing Exchange Server 2010 recovery Recovery requirements Performing full recovery Performing advanced recovery Performing granular recovery of Mailbox, folder, or Performing a quick recovery of a deleted Mailbox in Exchange Server Microsoft SharePoint Server 2007, 2010, and 2013 Backup and Recovery Overview Advantages of performing backup and recovery through the SharePoint VSS Writer Supported SharePoint Server versions and Windows versions Supported SharePoint Server versions and required SQL versions Support for FAST Search Server backup and recovery in SharePoint Server Types of supported backup Types of supported recovery Backup and recovery levels SharePoint Server 2007 VSS Writers SharePoint Server 2010 VSS Writers SharePoint Server 2013 VSS Writers Examples of SharePoint Server 2007, 2010, and 2013 farm configurations EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 5

6 Contents Viewing valid application data save sets Examples of save sets for various SharePoint farm configurations Viewing required volumes for SharePoint recovery Client parallelism optimization for backups Performing SharePoint Server scheduled backups Requirements Configuring scheduled backups Performing SharePoint Server full recovery Perform a full recovery of a stand-alone SharePoint farm Perform a full recovery of a distributed SharePoint farm Perform a recovery of individual SharePoint Server content databases Perform a recovery of SharePoint Server search and content index Performing SharePoint Server granular level recovery The GLR process that you must follow depends on your farm size Mounting backups for GLR Best practices and recommendations Chapter 6 Chapter 7 Microsoft Data Protection Manager Server Backup and Recovery Overview Types of supported backup Types of supported recovery Types of DPM data for backup DPM Server Writers DPM backup and recovery workflow Directed granular recovery process Viewing valid application data save sets Performing DPM Server scheduled backups Performing a DPM Server recovery Performing DPM granular recovery Reviewing settings before starting recovery Recovering a folder or file from a DPM replica Performing a granular directed recovery to a DPM-protected server Microsoft Hyper-V Server Backup and Recovery Overview Supported Windows server versions for Hyper-V Integration services components version Hyper-V components and NMM Types of supported backup Types of supported recovery Example Hyper-V configurations Viewing valid application data save sets Preparing a Hyper-V guest with multiple volumes for backup Image level backups NMM support for proxy backup of Hyper-V Preparing a virtual machine for backup Configuring Hyper-V backups Image level recovery Turning the virtual machine offline for recovery Hosting the recovered virtual systems Specifying the destinations for the Hyper-V configuration files and virtual system EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

7 Contents Selecting Hyper-V recovery options Selecting the destination of Hyper-V recovery Granular level recovery Recovering Hyper-V files and folders Federated Hyper-V CSV backup and recovery Viewing federated CSV save sets Performing cluster level and CSV virtual machine backups Restoring Hyper-V CSV virtual machines Best practices and recommendations Hyper-V Server backup and recovery Hyper-V virtual machine applications backup and recovery Data mining using Hyper-V granular level recovery Restrictions for backup and recovery of Hyper-V virtual machines i n a Windows 2008, 2008 R2, and 2012 Failover Cluster Chapter 8 Chapter 9 Microsoft Active Directory Backup and Recovery Overview Types of supported backup Backup levels Types of supported recovery Active Directory objects for granular backup and recovery Performing an Active Directory or ADAM scheduled backup Configure a client resource for Active Directory or ADAM full backup Performing Active Directory or ADAM granular backup Considerations for granular backup Configuring Active Directory or ADAM granular backups Performing Active Directory database recovery Performing an Active Directory granular recovery Recovery restrictions for Active Directory Recovering an Active Directory object or object attribute Selecting Active Directory object attributes Troubleshooting About the troubleshooting process Setting up events notifications and finding errors Error messages NMM.. Exchange2010 Shell Exception State of runspace is not valid for this operation Savegroup failed in scheduled backup E_VOLUME_NOT_SUPPORTED E_VETO_PROVIDER VSS_E_WRITERERROR_RETRYABLE error code 0x800423f VSS CLIENT... Invalid Writer Selection... for APPLICATIONS Insufficient permission to access mailbox. See documentation for required permission settings. Server MBX is not capable of RSG operations :nsrsnap_vss_save NMM validation for NPS writer failed, unable to restore NPS VSS writer data Error when the vicfg setup command is used on ESXi NetWorker Module for Microsoft Applications - KRIS-SUB6\ INST The system cannot find the file specified. Dismounting the EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 7

8 Contents SharePoint GLR backup CBFS error in cbfs_open_file() session id: 1, User defined message not understood. Message type: 50, request type: D:\views\nw\ntx64\fb_nmm24\nsr\vssclient\snapvsssave\ nsrsnap_vss_save.h(202) nsrsnap_vss_recover:cannot login to SQL Server SQLEXPRESS\ENGINEER Error starting Restore Troubleshooting NMM client issues General NMM client issues SQL Server VDI and VSS Exchange Server SharePoint Server Data Protection Manager Hyper-V CLARiiON NMM GUI Antivirus and firewall Snapshots NMM installation issues Recovery failure after.net 3.5 framework installation NMM uninstall and reinstall required to change the Replication Manager port number Procedure to force a clean NMM install on a client host Checking log files NMM client PowerSnap client Replication Manager EMC VSS provider Active Directory NetWorker server Manually stopping and starting services Using nsr.dir to skip files for NMM backup and recovery Troubleshooting issues during SQL databases directed recovery Other troubleshooting resources Appendix A Appendix B Appendix C Commands for SQL Server VDI Backup and Recovery Using the nsrsqlsv command Using the nsrsqlrc command Command options for nsrsqlrc Using the nwmssql command Backup and restore command syntax for SQL Server data Microsoft SQL Server topics Microsoft SQL Server recovery models Microsoft SQL Server named log marks SQL Server master database maintenance Multiple nonclustered instances of SQL Server How a restore interacts with SQL Server Exchange Server 2007 Backup and Recovery Scenarios Exchange backup scenarios Exchange recovery scenarios EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

9 Contents Appendix D Appendix E Exchange Server Backup and Recovery Example Scenarios Exchange Server 2007 standalone database Exchange Server 2007 Cluster Continuous Replication database Exchange Server 2010 standalone database Exchange Server 2010 DAG single-copy database Exchange Server 2010 DAG multiple-copy database SharePoint Server Recovery Examples Introduction Restoring deleted individual items from document library Restoring deleted search service application Restoring deleted web application Additional steps for SQL Server 2012 AlwaysOn configuration Glossary Index EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 9

10 Contents 10 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

11 FIGURES Title Page 1 Traditional backup command and data flow Traditional recovery command and data flow Restore Options error message Backup window Backup Options for SQL page Properties dialog box Properties dialog box for Administrators Specify the Backup Options page of Client Configuration Wizard Backup Configuration Summary page Apps & Modules tab Normal Restore window Properties dialog box, General tab Standby Undo File dialog box Properties dialog box, Files tab Specify the File Destination dialog box Properties dialog box, Restore Time tab Restore Options dialog box, General tab Review Options message Select the SQL Server dialog box NetWorker User for SQL Server message Restore (Copy) window Sample Properties dialog box Restore window Verify Only Restore window Piecemeal Restore window Restore Options message Change Browse Time dialog box Specify Browse Time dialog box Properties dialog box Specify the Standby Undo File dialog box Filegroup Restore Properties dialog box The Files tab of the Properties dialog box Specify the File Destination dialog box Read File Configuration dialog box The Restore Time tab in the Properties dialog box Point-in-Time Restore dialog box Save set output for SQL Server Snapshot process with Exchange production server and proxy client Select the Exchange 2007 Server Options page Exchange Recovery Options window with Conventional Restore option selected Available and unavailable storage groups Restore To command on context menu RSG Configuration error message RSG Configuration correct message Public folders cannot be recovered to an RSG Selected and partially selected items Select Storage Group Restore Destination dialog box Local client on the taskbar next to Client Select Viewable Clients dialog box Exchange Server Recovery page EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 11

12 Figures 51 Expand the database Backup Configuration Summary page for Exchange Server 2010 standalone setup Backup Configuration Summary page for Exchange Server 2010 DAG setup Apps & Modules tab with Deduplication attribute Select Exchange 2010 database Advanced Recovery dialog box Manage RDB window Create_DB window Delete RDB Confirmation window Exchange Recovery Summary Select Database window Select Database window Select mailbox, folder or for recovery SharePoint Server 2007, 2010, and 2013 stand-alone farm configurations SharePoint Server 2007 distributed farm configuration Granting permissions to view subcomponents in the NMM GUI Dialog box to recover remote components SharePoint Granular Recovery tab Mount SharePoint backup for Granular Level Recovery option Dismount SharePoint backup option SharePoint GLR service tray NMM protection of DPM Directed recovery of FileServer DPM disaster recovery options DPM recovery modes Recover submenu for DPM recovery DPM granular recovery available to file level DPM granular recovery options Windows Server 2008 or Windows Server 2008 R2 host with Hyper-V virtual machines NMM backup of Hyper-V components Hyper-V storage options Granular Level Recovery option Locate the folders or items on VM Active directory save set syntax Troubleshooting process Multiple server roles that coexist on a single computer SCC architecture CCR core architecture Example dependency dialog box Perform SQL VSS restore SharePoint Writer recovery Search Service Application listed in Central Administration Recovering IIS and C:\inetpub Successful SQL Writer restore for SharePoint databases Central Administration and check the SSP Restore the bootable system state from SYSTEM COMPONENTS:\ in NMM Deleted Search Service Application is restored Clear Microsoft best practices for selecting the system state Select IIS Writers Web application listed in Central Administration Recovering IIS and C:\inetpub Corresponding content database of deleted web application Example dependency dialog box Selecting all the dependent the configuration databases EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

13 Figures 105 The Monitor view that shows that the SharePoint Writer restore is successful Deleted web application is restored Remove the content database from Availability Group Add the content database to the Availability Group Select Initial Data Synchronization page Validation error Secondary replica copy in restoring mode Database part of Availability Group EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 13

14 Figures 14 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

15 TABLES Title Page 1 EMC publications for additional information Backup levels in NMM for SQL VDI backups Terminology Where to initiate backup operations Types of recovery for SQL Server VDI Recovery types supported for SQL Server with NMM Recovery modes Program and log file names Backup levels for SQL Server data Full backup every one to two weeks Incremental backup after a full backup Backup level advantages and disadvantages Creating additional backup levels with data objects Backup level promotion process Configuration tasks SQL VDI save set syntax Views displayed by the Modify the destination for the files in attribute List of attributes that can be configured Backup Versions table columns Log Mark table columns Guidelines for fail-safe striped recovery Levels of full backups Levels of full recoveries Special characters and their URL-encoded values Tasks for scheduling a backup SQL Server save set syntax SQL variable settings for Application Information attribute Best practices and considerations Types of supported backups Exchange 2007 backup levels Types of supported recoveries Writers used by NMM for Exchange Server backup and recovery Exchange application information variables for threading and throttling Special characters and their URL-encoded values Tasks for configuring an Exchange Server backup Different backup procedures for Exchange Exchange Server 2007 Name attribute Exchange Server 2007 save set names Application variables for Exchange Server Exchange application information variable settings Types of supported backups Types of supported recoveries Exchange 2010 VSS writers Special characters and their URL-encoded values Backup options for Exchange Server Tasks for configuring an Exchange Server backup Exchange 2010 save sets for application data Exchange application information variable settings Advantages of using VSS Writer for backup and recovery Types of supported SharePoint Server and Windows Server versions EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 15

16 Tableses 51 SharePoint Server versions and its minimum SQL Server versions Types of supported backups Types of supported recoveries List of supported SharePoint Server 2007 VSS Writers List of supported SharePoint Server 2010 VSS Writers List of supported SharePoint Server 2010 VSS Writers Services and servers in SharePoint Servers 2007, 2010, and 2013 farm Commands for displaying valid application data save sets Special characters and their URL-encoded values Example: Minimum required save sets to be backed up Tasks for SharePoint Server backups Example: Minimum required save sets to be backed up SharePoint Server application information variable settings Types of full backup for DPM Types of recovery in DPM DPM data types for backup Special characters and their URL-encoded values Tasks for scheduling a backup DPM Server 2007 save set syntax DPM application information variable settings Operating systems supported by NMM 2.4 SP Types of supported backups Types of supported recoveries Hyper-V virtual machine configurations Special characters and their URL-encoded values Backup tasks for Hyper-V Hyper-V save set syntax Hyper-V application information variable settings Types of backup Backup levels Types of backup Tasks for Active Directory or ADAM granular backup System-only attributes that are not backed up Retained attributes after object is deleted Notifications and errors Services and processes used in NMM client Command options for nsrsqlsv Command options for nsrqlrc Command options for nwmssql Command syntax for SQL Server data Command syntax for names containing a period Command syntax for names containing a backslash Command syntax for names containing a colon Command syntax for names containing periods, back slashes, and colons Legacy database options Supported backup types for SQL Servers recovery models Supported backup and restore functions for SQL Server recovery models Exchange 2007 standalone database backup and recovery example scenarios Exchange 2007 CCR database backup and recovery example scenarios Exchange Server 2010 standalone database backup and recovery example scenarios Exchange Server 2010 DAG single-copy database backup and recovery example scenarios EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

17 PREFACE As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC representative. This document was accurate at publication time. Go to EMC Online Support ( to ensure that you are using the latest version of this document. Purpose This guide contains information for backing up and recovering the supported versions of Microsoft applications, by using EMC NetWorker Module for Microsoft Applications (NMM). The NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide supplements the backup and recovery procedures described in this guide and must be referred to when performing application-specific tasks. Ensure to download a copy of the NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide from EMC Online Support before using this guide. Audience This guide is part of the EMC NetWorker Module for Microsoft Applications documentation set, and is intended for use by system administrators during the setup and maintenance of the product. 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 Storage subsystems, such as EMC CLARiiON or EMC Symmetrix, if used EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 17

18 Preface Related documentation Table 1 on page 18 lists the EMC publications that provide additional information. Table 1 EMC publications for additional information Guide names NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide NetWorker Module for Microsoft Applications Release 2.4 SP1 Installation Guide NetWorker Module for Microsoft Applications Release 2.4 SP1 Release Notes NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups Technical Note Description Contains information common to all the supported Microsoft applications that can be backed up and recovered by using EMC NetWorker Module for Microsoft Applications. Contains preinstallation, installation, silent installation, and post installation information about EMC NetWorker Module for Microsoft Applications. Contain information about new features and changes, problems fixed from previous releases, known limitations, and late-breaking information that was not updated in the remaining documentation set. Contains supplemental information about using EMC NetWorker Module for Microsoft Applications release 2.4 SP1 with EMC CLARiiON. NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing Proxy Node Backups Technical Note Contains supplemental information about using EMC NetWorker Module for Microsoft Applications release 2.4 SP1 with EMC Symmetrix. Simplified Windows Bare Metal Recovery Solution for Microsoft Applications by using EMC NetWorker Module for Microsoft Applications Release Technical Notes SharePoint Granular Recovery by using EMC NetWorker Module for Microsoft Applications and Kroll Ontrack PowerControls Release Technical Notes Protecting Virtual Machine Manager Environments Using EMC NetWorker Module for Microsoft Applications Release Technical Notes NetWorker Procedure Generator (NPG) NetWorker Cloning Integration Guide NetWorker Licensing Guide NetWorker Software Compatibility Guide NetWorker Data Domain Deduplication Devices Integration Guide NetWorker Avamar Integration Guide NetWorker documentation set Contain supplemental information about performing Windows Bare Metal Recovery by using NMM. Contain information about how to perform granular recovery of Microsoft SharePoint with NMM release 2.4 SP1 and third-party software Kroll Ontrack PowerControls. Provide a data protection strategy for Microsoft System Center Virtual Machine Manager (VMM) using EMC NetWorker Module for Microsoft Applications release 2.4 SP1 (NMM) and the EMC NetWorker Windows Disaster Recovery feature. The NPG is an executable download that can be used to generate precise, user-driven steps for high demand tasks carried out by customers, support, and the field. Contains planning, practices, and configuration information for using the NetWorker, NMM, and NMDA cloning feature. Contains information about licensing NetWorker and its modules. Contains a list of supported client, server, and storage node operating systems for the following software products: NetWorker and NetWorker application modules and options (including deduplication and virtualization support), AlphaStor, Data Protection Advisor, and HomeBase. Contains information about planning and configuration information on the use of Data Domain devices for data deduplication backup and storage in a NetWorker environment. Contains information about planning and configuration information on the use of Avamar in a NetWorker environment. Contains the documentation that is available with NetWorker. 18 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

19 Preface Conventions used in this document EMC uses the following conventions for special notices: NOTICE is used to present information that is important or essential to software or hardware operation. Note: A note presents information that is important, but not hazard-related. Typographical conventions EMC uses the following type style conventions in this document: Normal Used in running (nonprocedural) text for: Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, and utilities URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, and notifications Bold Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages Used in procedures for: Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus What the user specifically selects, clicks, presses, or types Italic Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis, for example, a new term Variables Courier Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Courier bold Used for specific user input, such as commands Courier italic Used in procedures for: Variables on the command line User input variables < > Angle brackets enclose parameter or variable values supplied by the user [ ] 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 nonessential information omitted from the example EMC support, product, and licensing information can be obtained as follows: Product information For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at: EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 19

20 Preface Technical support Go to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to: BSGdocumentation@emc.com 20 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

21 REVISION HISTORY your clarifications or suggestions for this document to: The following table lists the revision history of this document. Revision Date Description of added or changed sections 02 January 30, 2013 Second release of this document for General Availability (GA) release of the EMC NetWorker Module for Microsoft Applications Release 2.4 SP1. 01 December 17, 2012 First release of this document for Directed Availability (DA) release of EMC NetWorker Module for Microsoft Applications Release 2.4 SP1. EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide 21

22 Revision history 22 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

23 CHAPTER 1 Microsoft SQL Server VDI Backup and Recovery This chapter includes the following topics: Overview Performing SQL Server manual backups Backup and recovery for Microsoft Cluster Servers Performing SQL Server scheduled backups Performing a SQL Server recovery Striped backup and recovery Striped backup and recovery Microsoft SQL Server VDI Backup and Recovery 23

24 Microsoft SQL Server VDI Backup and Recovery Overview The NetWorker software provides backup and recovery capabilities for file system data only. A file system backup, however, does not save Microsoft SQL Server data in a recoverable form. The EMC NetWorker Module for Microsoft Applications (NMM) release 2.4 SP1 software utilizes Virtual Device Interface (VDI), an API provided by Microsoft SQL Server, to integrate with the SQL Server and enable the NetWorker software to back up and recover SQL Server data. The information in the following resources supplement the information in this chapter: The Microsoft documentation provides details about the VDI technology. Appendix A, Commands for SQL Server VDI Backup and Recovery provides syntax, notation, and related information for NMM commands and command options for SQL Server VDI backup and recovery. Appendix B, Microsoft SQL Server topics This section provides information on the following topics: SQL Server versions supported by NMM on page 24 AlwaysOn Availability Group feature of Microsoft SQL Server 2012 on page 25 Types of supported backups on page 25 Traditional backup configurations on page 26 Backup levels on page 27 Types of supported recovery on page 28 Recovery configurations on page 30 Recovery modes on page 31 Recovery time on page 31 Recovery window restrictions on page 32 Commands used in NMM for SQL Server VDI backup and recovery on page 32 Error logs for backup and recovery on page 33 SQL Server versions supported by NMM Setting deduplication for SQL Server data on page 34 TheNetWorker Software Compatibility Guide provides the most up-to-date lists of hardware, operating system, service pack, and application versions supported by the NMM client. The NMM software provides backup and recovery of the following SQL Server database and transaction logs: SQL Server 2012 (x86/x64) SQL Server 2008 R2 (x86/x64) 24 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

25 Microsoft SQL Server VDI Backup and Recovery SQL Server 2008 SP3 (x86/x64) SQL Server 2005 SP4 (x86/x64) AlwaysOn Availability Group feature of Microsoft SQL Server 2012 SQL Server 2012 introduced the new functionality Availability Group with AlwaysOn. Availability Group is a logical group of databases that have the AlwaysOn capability. The Availability Group is failed over to other nodes as a group, that is, all the databases that are part of the Availability group are failed over together during failure or manual failover. NMM 2.4 SP1 supports the new SQL Server 2012 AlwaysOn feature. AlwaysOn allows a database to have multiple replicas. There can be a maximum number of four secondary replicas. Multiple secondary replicas can be configured to be in either synchronous or asynchronous mode. A database that is configured as AlwaysOn is treated by NMM 2.4 SP1 as a normal database, and a backup of this database can be performed from the primary or secondary replica because the replicas are considered to be databases that are residing on separate instances. However, there are some restrictions on secondary replicas of the AlwaysOn database, and not all backup types are supported for secondary replicas. Types of supported backups For NMM 2.4 SP1 to perform backup of secondary replicas, the Readable Secondary option of SQL Server 2012 AlwaysOn configuration must be set to Yes. Enable this option for both primary and secondary replicas, as in case of failover of the availability group, secondary replicas become primary and vice versa. The Microsoft website describes the AlwaysOn Availability Group functionality in SQL Server 2012, and provides detailed information about how to configure your setup to utilize this support. NMM 2.4 SP1 supports: Manual or traditional backup The NMM software provides support for traditional backups. Traditional backups are often referred to as manual backups. A traditional backup of SQL data can be performed at any time and is independent of any scheduled backup. NMM supports traditional backup of: Database File Filegroup Filestream Instance Transaction log In addition to creating full backups of file or filegroup, the SQL Server supports the creation of filegroup differential and file differential backups. Overview 25

26 Microsoft SQL Server VDI Backup and Recovery A filegroup differential backup may actually reduce both media requirements and recovery time. The data can be stored across more than one disk or disk partition, and recovery time may be reduced. A differential can substitute for any log backups performed between the full and differential backups. A full backup must be performed first. A full, inremental, or differential backup of SQL Server data (including files and filegroups) created by using a previous NetWorker Module for SQL Server (NMSQL) can be recovered by using NMM 2.4 SP1. However, NMM 2.4 SP1 cannot recover snapshot backup created by using an earlier version of NMSQL. Scheduled backup The most reliable way of protecting SQL data is to ensure that backups of the SQL Server are run at regular intervals, that is, setting up scheduled backups. Scheduled backups ensure that all SQL Server data is automatically saved, including the NetWorker server s client indexes and bootstrap file. The client indexes and bootstrap file are vital for restoring data to the SQL Server in the event of a disaster. Traditional backup configurations Figure 1 on page 26 shows an overview of the process interactions among the NetWorker client (NMM) and server, and SQL server software during a traditional backup. Figure 1 Traditional backup command and data flow 26 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

27 Microsoft SQL Server VDI Backup and Recovery The following occurs in a traditional backup: 1. The nsrd program starts the backup on the NetWorker server. 2. The savegrp program executes the NMM backup command (nsrsqlsv) on the client instead of performing a standard NetWorker save. 3. The nsrsqlsv program passes the backup data from SQL Server to the NetWorker server through an X-Open Backup Services application programming interface (XBSA). The NetWorker server software performs all scheduling and storage management tasks. The NetWorker Administration Guide provides information about the NetWorker services and operations described in this chapter. Backup levels Table 2 on page 27 describes the SQL Server VDI backup levels. NMM supports three levels of backup. Table 2 Backup levels in NMM for SQL VDI backups Backup levels Full Incremental Description Entire database backup, including all filegroups or files in the database. An incremental backup, corresponds to a SQL Server transaction log backup. A log file backup by itself cannot be used to recover a database. A log file backup is used after a database recovery to restore the database to the point of the original failure. Note: This backup can also be run from the command line. Differential A differential backup, specified as any level from 1 to 9, is done from the command line, and makes a copy of all the pages in a database modified after the last full database backup. Table 3 on page 27 shows how the terminology for backup levels used in the SQL Server product differs from the terminology used for NMM. Table 3 Terminology NMM term Full Incremental Differential Function Backs up an entire file, filegroup, filestream, or database. Backs up all transaction log changes since the most recent full, differential, or transaction log backup. Backs up all database changes since the last full backup. Corresponding SQL Server term File, filegroup or filestream, or database backup Transaction log (also called xlog) backup Differential backup Overview 27

28 Microsoft SQL Server VDI Backup and Recovery Table 4 on page 28 summarizes where backup procedures can be initiated and which backup levels are supported for each interface. Table 4 Where to initiate backup operations Backup levels available Backup type Backup initiated from Full Incr Diff Scheduled NetWorker Administrator program on the server Yes Yes Yes Manual Command line on the SQL Server, which is the client Yes Yes Yes NMM client initiated GUI (adhoc backup) Yes No No Types of supported recovery NMM supports recovery of a SQL Sever 2012 database only after the AlwaysOn replication has been removed for the corresponding database. Table 5 on page 28 lists the types of recovery for SQL Server VDI in NMM. Table 5 Types of recovery for SQL Server VDI (page 1 of 2) Type of recovery When used Description Traditional recovery Normal recovery For data that was backed up by traditional backup, NMM supports traditional recovery. The NMM software uses the normal restore type as the default. Data recovery from a traditional backup can be performed: At any time by using the NMM software. By running the NMM recover command (nsrsqlrc) from the command prompt. Traditional recovery operations recover files, filegroups, databases, and transaction log backups. Performing a SQL Server recovery on page 60 provides additional information about traditional recovery operations. The normal restore type restores: The entire set of data associated with one or more SQL Server backups, including full, incremental, and differential backups. A file, filegroup, or a database to the database originally backed up. Level full, level 1 (differential), and level incremental backups in the order required by SQL Server. The NMM software can back up and restore specified files and filegroups. In addition, a single filegroup, or multiple filegroups or files, can be restored from a full database backup. 28 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

29 Microsoft SQL Server VDI Backup and Recovery Table 5 Types of recovery for SQL Server VDI (page 2 of 2) Type of recovery When used Description Piecemeal recovery Verify-only recovery Copy recovery The piecemeal restore is supported only with the Enterprise edition of the supported SQL Server versions. Selecting the verify-only restore type does not restore the SQL Server data. A copy restore is an operation in which data is recovered to a SQL Server host other than the one from which it was backed up. Note that copy restore from and to the same SQL Server instance can also be done. Piecemeal restore is a multi-stage process that enables you to restore filegroups incrementally to a new or existing database. The first stage of a piecemeal restore includes the primary filegroup and any number of secondary filegroups, which is similar to the piecemeal restore. After the primary filegroup is restored, the database can be brought online and additional filegroups can be restored as needed. The verify-only restore type validates the backup set and verifies the backup media for the selected SQL Server backups. In addition, when verify-only is specified, item level properties for file, filegroup, and database objects are not available. The copy recovery type creates a copy of a database by restoring a SQL Server database to a new location, or to a new database name. The copy recovery type makes it easy to duplicate a database that was previously backed up. You can only mark a single item for this operation. In addition, you can copy a system database, but you cannot overwrite it. Table 6 on page 29 lists the SQL Server versions and the type of recovery supported by each version. Table 6 Recovery types supported for SQL Server with NMM Recovery type Microsoft SQL Server version Normal Piecemeal Verify Copy SQL Server 2005 Enterprise SQL Server 2005 Standard, Workgroup, and Express X SQL Server 2008 Enterprise SQL Server 2008 Standard, Workgroup, and Express SQL Server 2008 R2, Standard, and Express X X SQL Server 2008 R2 Enterprise SQL Server 2012 Standard, Workgroup, and Express X SQL Server 2012 Enterprise Overview 29

30 Microsoft SQL Server VDI Backup and Recovery Recovery configurations Figure 2 on page 30 shows the functional relationship between the NetWorker server, NMM, and the SQL Server products during a traditional recovery operation. Figure 2 Traditional recovery command and data flow A request for a traditional restore operation: 1. The nsrsqlrc command starts the recover. 2. The NetWorker XBSA API translates the object names requested by the NMM into a format the NetWorker software understands, and forwards them to the NetWorker server nsrd service. 3. The media service, nsrmmd, invokes nsrmmdbd to search the NetWorker server s media database for the volumes that contain the objects requested. 4. After the media is mounted, the nsrmmd program sends the data through the NetWorker XBSA API to nsrsqlrc, which recovers the data to the SQL Server directories. 30 EMC NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide

31 Microsoft SQL Server VDI Backup and Recovery Recovery modes To recover a database, the NMM software requires that a recovery mode be specified. A recovery mode instructs the SQL Server how to interact with the database after the recovery operation completes. For instance, recovery modes can leave the database in an intermediate state, so that additional transaction logs can be applied. Table 7 on page 31 shows how the recovery modes correspond to SQL Server database restore options. Table 7 Recovery modes Types Normal restore mode No-recovery restore mode Standby restore mode Online restore mode Description The normal restore mode instructs SQL Server to leave the database in an operational state after the restore completes. This then enables database reads and writes. The normal restore mode is the default mode the NMM software uses when restoring a database. The no-recovery restore mode activates the SQL Server NORECOVERY database restore option for the last stage restored. The no-recovery restore mode places the database in a state that cannot be loaded after the restore, but is still able to process additional transaction log restore operations. The standby restore mode activates the SQL Server STANDBY database restore option for the last stage restored, which forces the database to be in a read-only state between transaction log restore operations. The standby restore mode provides an undo file for SQL Server to use when rolling back the transactions. SQL Server provides the ability to perform a restore operation while a SQL Server database is active. The database is completely offline only while the primary filegroup is being restored. Once the primary filegroup is restored, the database can be brought online while the rest of the filegroups are being restored, and then only the data that is being restored is unavailable. The rest of the database remains available during this type of restore. Earlier versions of SQL Server require that you bring a database offline before you restore the database. Recovery time Backups can be recovered to a specific time. The recovery time controls which backup data should be reinstated when a database is recovered. The recovery time may also control which portions of an incremental level backup are to be recovered when the NMM software is instructed to discard transactions performed after a given time. The default or current recovery time for each database comes from the create time of the marked item. By default, the most recent backup is recovered. If the most recent backup is incremental level or 1, dependent backups are recovered first. User-specified recovery times can restore older backup versions or perform point-in-time recovery operations. For instance, a point-in-time recovery may be specified by using a recovery time that is earlier than the create time of the transaction log backup, but later than the create time of the previous backup. The NMM software provides three methods for recovering to a specific time: Database backup versions Point-in-time recovery of a transaction log (level incremental) backup Recovering to a named log mark Overview 31