Contents

Dell PowerProtect 19.12 Data Manager Microsoft SQL Server User Guide PDF

1 of 201
1 of 201

Summary of Content for Dell PowerProtect 19.12 Data Manager Microsoft SQL Server User Guide PDF

PowerProtect Data Manager 19.12 Microsoft SQL Server User Guide

October 2022 Rev. 01

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid

the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

2020 - 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Figures..........................................................................................................................................8

Tables........................................................................................................................................... 9

Preface....................................................................................................................................................................................... 10

Chapter 1: PowerProtect Data Manager for Microsoft Application Agent Overview...................... 14 PowerProtect Data Manager overview........................................................................................................................ 14 Introducing the Microsoft application agent............................................................................................................... 14 VM Direct limitations.........................................................................................................................................................15

Configure VM Direct with IPv4 and IPv6............................................................................................................... 15 Prerequisites....................................................................................................................................................................... 16 Supported Internet Protocol versions...........................................................................................................................16 Firewall and port considerations.....................................................................................................................................18 Role-based security........................................................................................................................................................... 19

Prerequisites for role-based security with Microsoft SQL Server................................................................... 19 Data-in-flight encryption................................................................................................................................................. 20 PowerProtect Data Manager new deployment overview....................................................................................... 20 PowerProtect Data Manager existing deployment overview..................................................................................21

Chapter 2: Enabling the Microsoft Application Agent for Microsoft SQL Server.......................... 22 Microsoft SQL Server data protection and replication requirements.................................................................. 22 Microsoft SQL Server operational log files for backup and restore operations.................................................23 Protecting a stand-alone Microsoft SQL Server.......................................................................................................24 Protecting Microsoft SQL Server clustered environments.................................................................................... 24 Install and configure the application agent................................................................................................................. 25

Prerequisites ................................................................................................................................................................25 Install the Microsoft application agent with the wizard.....................................................................................25 Install the Microsoft application agent with a silent installation...................................................................... 28 Update the Microsoft application agent................................................................................................................30 Update the application agent in the PowerProtect Data Manager UI............................................................ 31 Uninstall the Microsoft application agent with the setup file...........................................................................32 Uninstall the Microsoft application agent with a silent uninstallation............................................................ 32 Recommission the Microsoft application agent after Microsoft SQL Server hostname is changed

or reused....................................................................................................................................................................33 Required privileges for Application Direct backup and recovery..................................................................... 33 Stagger Microsoft SQL Server discovery jobs in host scale-out environments.......................................... 34 Configure the database backup stripe level..........................................................................................................34 Enable multi-stream backups for Microsoft SQL Server protection policy.................................................. 35

Manage the Microsoft application agent.....................................................................................................................36 View application agent details.................................................................................................................................. 37

Support for existing Microsoft application agent backups with PowerProtect Data Manager..................... 38 Supporting existing Microsoft application agent backups with PowerProtect Data Manager................ 39 Using the backup discovery tool for PowerProtect Data Manager management of existing

backups......................................................................................................................................................................39 Microsoft application agent for application-aware protection...............................................................................40

Contents

Contents 3

Multiple virtual networks (MVLANs) for Microsoft SQL Server application-aware protection...............42 Naming conventions for backups with VM Direct...............................................................................................42 Minimum required privileges for VM Direct backup and recovery.................................................................. 42

Chapter 3: Managing Storage, Assets, and Protection.................................................................44 Add protection storage ...................................................................................................................................................44

View the storage unit password.............................................................................................................................. 45 Enable an asset source.................................................................................................................................................... 46

Disable an asset source..............................................................................................................................................46 Delete an asset source..................................................................................................................................................... 47 Recommission the Microsoft application agent......................................................................................................... 47 Setting the sysadmin privilege for Microsoft SQL Server hosts........................................................................... 47 Discover a Microsoft SQL Server application host...................................................................................................48 Replication triggers...........................................................................................................................................................49 Add a protection policy for Microsoft SQL Server database protection.............................................................50 Cancel a Microsoft application agent protection or restore job............................................................................ 57 Add a service-level agreement...................................................................................................................................... 58 Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier).....60 Edit the retention period for backup copies............................................................................................................... 62 Delete backup copies....................................................................................................................................................... 63

Retry a failed backup copy deletion........................................................................................................................64 Export data for deleted backup copies.................................................................................................................. 64 Remove backup copies from the PowerProtect Data Manager database....................................................65

Enable the Microsoft application agent after Internet Protocol change.............................................................65 Enable the Microsoft application agent after hostname change.......................................................................... 66 Manage the PowerProtect agent service................................................................................................................... 67

About the PowerProtect agent service................................................................................................................. 67 Start, stop, or obtain the status of the PowerProtect agent service............................................................68 Troubleshooting PowerProtect agent service installations.............................................................................. 68 Troubleshooting PowerProtect agent service operations.................................................................................68 Register the PowerProtect agent service to a different server address on Windows.............................. 69 Recovering the PowerProtect agent service from a disaster..........................................................................69

Manage the cloud tier operations with PowerProtect Data Manager................................................................. 70 Add a cloud tier schedule to a protection policy..................................................................................................70 Tier the PowerProtect Data Manager backups from DD to the cloud............................................................71 Restore the cloud tier backups to DD.................................................................................................................... 72

Chapter 4: Performing Self-Service Backups of Microsoft SQL Server Databases....................... 73 Performing self-service Microsoft SQL Server database backups....................................................................... 73 Overview of Application Direct with Microsoft SQL Server backups.................................................................. 73

Federated backups of Always On availability groups..........................................................................................74 Distributed segment processing...............................................................................................................................74 Configuring distributed segment processing........................................................................................................ 75

Best practices to back up Microsoft SQL Server with Application Direct..........................................................75 Configuring usage limits of DD resources..............................................................................................................76 Configure the database backup stripe level..........................................................................................................79

Naming conventions for backups with Application Direct...................................................................................... 80 Circumstances that promote Microsoft SQL Server backups to level full ......................................................... 81 Scheduling backup jobs....................................................................................................................................................82

4 Contents

Scheduling Microsoft SQL Server backups by using SQL Server Agent.......................................................82 Scheduling Microsoft SQL Server backups by using Windows Task Scheduler.......................................... 87

Performing manual backups .......................................................................................................................................... 88 Perform backups with the Microsoft app agent for Application Direct SSMS plug-in.............................. 88 Back up Microsoft SQL Server with the Application Direct backup command........................................... 94 Perform backups with T-SQL scripts................................................................................................................... 100

Chapter 5: Performing Self-Service Restores of Microsoft SQL Server Databases.....................103 Restoring a Microsoft SQL Server application host............................................................................................... 103 Best practices to restore Microsoft SQL Server with Application Direct......................................................... 103 Restoring Microsoft SQL Server databases ............................................................................................................ 104

Prerequisites............................................................................................................................................................... 104 Restore a database with the Microsoft app agent for Application Direct plug-in..................................... 105 Perform database restores with the Microsoft application agent for Application Direct recover

command.................................................................................................................................................................. 112 Perform database restores with T-SQL scripts.................................................................................................. 119

Performing table-level recovery................................................................................................................................... 121 Table-level restore workflow................................................................................................................................... 121 Launching the Microsoft application agent for Application Direct SSMS plug-in......................................122 Configure general table restore settings..............................................................................................................122 Configure optional table restore settings............................................................................................................ 123 Monitor the table restore mount operation ....................................................................................................... 125 Restore table-level data using ItemPoint.............................................................................................................125

Performing Microsoft SQL Server disaster recovery............................................................................................. 127 Perform Microsoft SQL Server disaster recovery............................................................................................. 127 Perform disaster recovery from the Cloud Tier..................................................................................................127

Chapter 6: Performing Centralized Restores of Application Direct Backups............................... 129 Centralized restores of Microsoft SQL Server Application Direct backups...................................................... 129 Considerations for centralized Microsoft SQL Server Application Direct restores.........................................130 Centralized restore of Microsoft SQL Server system databases........................................................................ 130 Centralized restore of a Microsoft SQL Server stand-alone database.............................................................. 132 Centralized restore of a Microsoft SQL Server AAG database............................................................................133 Centralized restore of multiple Microsoft SQL Server databases.......................................................................135

Chapter 7: Performing Self-Service Restores of Virtual Machine Backups..................................137 Restoring a Microsoft SQL Server virtual machine backup.................................................................................. 137 Overview of Microsoft SQL Server virtual machine restore operations ........................................................... 137 Prerequisites..................................................................................................................................................................... 138 Restoring Microsoft SQL Server databases to a virtual machine........................................................................138

Restore Microsoft SQL Server databases with the VM Direct SSMS plug-in........................................... 139 Restore a Microsoft SQL Server database with the VM Direct recover command.................................. 147

Performing Microsoft SQL Server table-level recovery to a virtual machine...................................................152 Restore Microsoft SQL Server tables with the VM Direct SSMS plug-in................................................... 152 Restore Microsoft SQL Server tables with the VM Direct recover command........................................... 158

Performing an instant access recovery...................................................................................................................... 161 Instant access recovery overview .........................................................................................................................161 Instant access recovery use cases........................................................................................................................ 162 Perform an instant access restore with the VM Direct SSMS plug-in.........................................................162

Contents 5

Chapter 8: Performing Centralized Restores of Virtual Machine Backups................................... 171 Centralized restores of Microsoft SQL Server virtual machine backups............................................................171 Considerations for centralized Microsoft SQL Server application-aware restores......................................... 172 Centralized restore of Microsoft SQL Server system databases........................................................................ 173 Centralized restore of a Microsoft SQL Server stand-alone database.............................................................. 174 Centralized restore of a Microsoft SQL Server AAG database............................................................................175 Centralized restore of multiple Microsoft SQL Server databases....................................................................... 177

Appendix A: Microsoft SQL Server Best Practices and Troubleshooting.................................... 179 Troubleshooting configuration issues......................................................................................................................... 179

Troubleshooting storage units................................................................................................................................ 179 Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname...............179 Troubleshooting agent registration ...................................................................................................................... 180 Troubleshooting PowerProtect agent service installations.............................................................................180 Troubleshooting PowerProtect agent service operations................................................................................ 181 Troubleshooting an error about lockbox stable value threshold after major system update................... 181 Troubleshooting an asset discovery failure in an FCI environment............................................................... 183 Troubleshooting an error during configuration of Microsoft SQL Server application-aware

protection................................................................................................................................................................ 183 Troubleshooting an issue with trailing spaces in Microsoft SQL Server database names.......................183 Troubleshooting incorrect database size in PowerProtect Data Manager UI.............................................184 Troubleshooting an uninstallation issue in a UAC enabled environment...................................................... 184 Troubleshooting the exit of agent service register.bat with error code 2...................................................184 Troubleshooting a VM Direct support issue with an AAG cluster in an IPv6 environment..................... 185 Multiple virtual networks (MVLANs) for Microsoft SQL Server application-aware protection............. 185

Troubleshooting backup issues.................................................................................................................................... 185 Troubleshooting backup failures when credentials include a backslash character (\).............................185 Troubleshooting memory or paging issues during Microsoft SQL Server backups................................... 185 Troubleshooting application-aware backup failure with msagentcon message......................................... 186 Troubleshooting application-aware backup failure with persisted settings message............................... 186 Troubleshooting application-aware backup failure in multiple VLAN environment ...................................187 Troubleshooting application-aware backup failure after software update.................................................. 187 Troubleshooting a missing duration value for centralized backup................................................................. 187 Troubleshooting TLOG backup issue with mirrored database configuration.............................................. 187 Troubleshooting self-service T-SQL backups with an I/O error message.................................................. 188 Troubleshooting expired onboarded backup copies that are not deleted....................................................188 Troubleshooting backup failure during FCI cluster failover............................................................................. 189 Troubleshooting Microsoft SQL Server databases skipped during virtual machine transaction log

backup...................................................................................................................................................................... 189 Troubleshooting Microsoft SQL Server application-aware backup error about disk.EnableUUID

variable..................................................................................................................................................................... 189 Troubleshooting restore issues.................................................................................................................................... 189

Troubleshooting errors in the restore window after updating from PowerProtect Data Manager 19.8 or earlier.......................................................................................................................................................... 190

Troubleshooting restores of multiple databases from multiple policies........................................................190 Troubleshooting centralized Microsoft SQL Server Application Direct restore operations.................... 190 Troubleshooting centralized Microsoft SQL Server Application Direct restore of backup tiered to

the cloud.................................................................................................................................................................. 190 Troubleshooting centralized Microsoft SQL Server virtual machine restore operations..........................191

6 Contents

Troubleshooting virtual machine restore and recovery failures with AAG named instances from SSMS UI................................................................................................................................................................... 191

Troubleshooting centralized Microsoft SQL Server virtual machine restore failure after VM Direct update.......................................................................................................................................................................192

Troubleshooting centralized Microsoft SQL Server virtual machine restore failure to Windows or CIFS shared path................................................................................................................................................... 192

Troubleshooting VM Direct SSMS restore failure with enabled UAC...........................................................192 Troubleshooting VM Direct SSMS restore failure after PowerProtect Data Manager server update. 192 Troubleshooting VM Direct SSMS restore of replicated log backup............................................................ 192 Troubleshooting SSMS UI crash after switch from table restore to database restore tab.................... 193

Appendix B: Glossary of Acronyms ....................................................................................... 194

Glossary.................................................................................................................................... 195

Contents 7

1 Extended Properties page with backup stripe levels...................................................................................... 35

2 Extend retention backup behavior.......................................................................................................................62

3 Federated backup command and data flow...................................................................................................... 74

4 Extended Properties page with backup stripe levels......................................................................................80

5 Application Direct - Backup-General page........................................................................................................ 89

6 DD system list and lockbox settings................................................................................................................... 90

7 Add DD system details............................................................................................................................................ 91

8 Application Direct - Backup-Options page........................................................................................................ 92

9 Application Direct - Backup-Monitor page........................................................................................................ 94

10 Application Direct - Database Restore-General page................................................................................... 106

11 Specifying the restore point................................................................................................................................ 107

12 Application Direct - Database Restore-Files page......................................................................................... 108

13 Application Direct - Database Restore-Options page.................................................................................... 110

14 Application Direct - Database Restore-Monitor page....................................................................................112

15 Application Direct - Table Restore-General page...........................................................................................122

16 Application Direct - Table Restore-Options page.......................................................................................... 124

17 Application Direct - Table Restore-Monitor page.......................................................................................... 125

18 ItemPoint Data Wizard: select the source files...............................................................................................126

19 ItemPoint Data Wizard: select the target server........................................................................................... 126

20 VM Direct: Database Restore General page....................................................................................................140

21 Specifying the restore point.................................................................................................................................141

22 VM Direct: Database Restore Files page..........................................................................................................143

23 VM Direct: Database Restore Options page....................................................................................................144

24 VM Direct: Database Restore Monitor page....................................................................................................147

25 VM Direct: Table Restore General page........................................................................................................... 153

26 VM Direct: Table Restore Options page...........................................................................................................154

27 VM Direct: Table Restore Monitor page.......................................................................................................... 156

28 ItemPoint Data Wizard: select the source files...............................................................................................157

29 ItemPoint Data Wizard: select the target server........................................................................................... 157

30 ItemPoint Data Wizard: select the source files.............................................................................................. 160

31 ItemPoint Data Wizard: select the target server........................................................................................... 160

32 VM Direct: Instant Access General page......................................................................................................... 163

33 Specifying the access point.................................................................................................................................164

34 VM Direct: Instant Access Options page......................................................................................................... 165

35 VM Direct: Instant Access Active Mounts page.............................................................................................167

36 VM Direct: Instant Access Active Mounts page.............................................................................................168

37 VM Direct: Instant Access Active Mounts page............................................................................................ 169

38 VM Direct: Instant Access Active Mounts page.............................................................................................170

Figures

8 Figures

1 Revision history..........................................................................................................................................................11

2 Related documentation............................................................................................................................................11

3 Style conventions..................................................................................................................................................... 12

4 Supported configurations....................................................................................................................................... 16

5 PowerProtect Data Manager port requirements.............................................................................................. 18

6 Required silent installation command options...................................................................................................28

7 Optional silent installation command options....................................................................................................28

8 Application agent information............................................................................................................................... 37

9 Special characters supported with VM Direct..................................................................................................42

10 Supported special characters............................................................................................................................... 80

11 Microsoft SQL Server skipped database cases and descriptions.............................................................. 189

Tables

Tables 9

Preface As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of the software or hardware currently in use might not support some functions that are described in this document. The product release notes provide the most up-to-date information on product features.

If a product does not function correctly or does not function as described in this document, contact Customer Support.

NOTE: This document was accurate at publication time. To ensure that you are using the latest version of this document,

go to the Customer Support website.

Product naming Data Domain (DD) is now PowerProtect DD. References to Data Domain or Data Domain systems in this documentation, in the user interface, and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many cases the user interface has not yet been updated to reflect this change.

Language use This document might contain language that is not consistent with Dell Technologies current guidelines. Dell Technologies plans to update the document over subsequent future releases to revise the language accordingly.

This document might contain language from third-party content that is not under Dell Technologies control and is not consistent with the current guidelines for Dell Technologies own content. When such third-party content is updated by the relevant third parties, this document will be revised accordingly.

Acronyms The acronyms used in this document might not be familiar to everyone. Although most acronyms are defined on their first use, a definition is not always provided with later uses of the acronym. For a list of all acronyms and their definitions, see the glossary at the end of the document.

Website links The website links used in this document were valid at publication time. If you find a broken link, provide feedback on the document, and a Dell Technologies employee will update the link in the next release as necessary.

Purpose This document describes how to configure and use the Dell PowerProtect Data Manager with the Microsoft application agent to back up and restore Microsoft SQL Server. The PowerProtect Data Manager Administration and User Guide provides additional details about configuration and usage procedures.

Audience This document is intended for the host system administrator who configures and uses the PowerProtect Data Manager with the Microsoft application agent to back up and restore Microsoft SQL Server.

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

10 Preface

Table 1. Revision history

Revision Date Description

01 October 25, 2022 Initial release of this document for PowerProtect Data Manager version 19.12.

Compatibility information Software compatibility information for the PowerProtect Data Manager software is provided by the E-Lab Navigator.

Related documentation The following publications are available at Customer Support and provide additional information:

Table 2. Related documentation

Title Content

PowerProtect Data Manager Administration and User Guide Describes how to configure the software.

PowerProtect Data Manager Deployment Guide Describes how to deploy the software.

PowerProtect Data Manager Licensing Guide Describes how to license the software.

PowerProtect Data Manager Release Notes Contains information about new features, known limitations, environment, and system requirements for the software.

PowerProtect Data Manager Security Configuration Guide Contains security information.

PowerProtect Data Manager Amazon Web Services Deployment Guide

Describes how to deploy the software to Amazon Web Services (AWS).

PowerProtect Data Manager Azure Deployment Guide Describes how to deploy the software to Microsoft Azure.

PowerProtect Data Manager Google Cloud Platform Deployment Guide

Describes how to deploy the software to Google Cloud Platform (GCP).

PowerProtect Data Manager Cloud Disaster Recovery Administration and User Guide

Describes how to deploy Cloud Disaster Recovery (Cloud DR), protect virtual machines in the AWS or Azure cloud, and run recovery operations.

PowerProtect Data Manager Cyber Recovery User Guide Describes how to install, update, patch, and uninstall the PowerProtect Cyber Recovery software.

PowerProtect Data Manager File System User Guide Describes how to configure and use the software with the File System agent for file-system data protection.

PowerProtect Data Manager Kubernetes User Guide Describes how to configure and use the software to back up and restore namespaces and PVCs in a Kubernetes cluster.

PowerProtect Data Manager Microsoft Exchange Server User Guide

Describes how to configure and use the software to back up and restore the data in a Microsoft Exchange Server environment.

PowerProtect Data Manager Microsoft SQL Server User Guide

Describes how to configure and use the software to back up and restore the data in a Microsoft SQL Server environment.

PowerProtect Data Manager Oracle RMAN User Guide Describes how to configure and use the software to back up and restore the data in an Oracle Server environment.

PowerProtect Data Manager SAP HANA User Guide Describes how to configure and use the software to back up and restore the data in an SAP HANA Server environment.

PowerProtect Data Manager Storage Direct User Guide Describes how to configure and use the software with the Storage Direct agent to protect data on VMAX storage arrays through snapshot backup technology.

Preface 11

Table 2. Related documentation (continued)

Title Content

PowerProtect Data Manager Network Attached Storage User Guide

Describes how to configure and use the software to protect and recover the data on network-attached storage (NAS) shares and appliances.

PowerProtect Data Manager Virtual Machine User Guide Describes how to configure and use the software to back up and restore virtual machines and virtual machine disks (VMDKs) in a vCenter Server environment.

VMware Cloud Foundation Disaster Recovery With PowerProtect Data Manager

Provides a detailed description of how to perform an end-to- end disaster recovery of a VMware Cloud Foundation (VCF) environment.

PowerProtect Data Manager Public REST API documentation Contains the Dell Technologies APIs and includes tutorials to guide you in their use.

vRealize Automation Data Protection Extension for Data Protection Systems Installation and Administration Guide

Describes how to install, configure, and use the vRealize Data Protection Extension.

Typographical conventions The following type style conventions are used in this document:

Table 3. Style conventions

Formatting Description

Bold Used for interface elements that a user specifically selects or clicks, for example, names of buttons, fields, tab names, and menu paths. Also used for the name of a dialog box, page, pane, screen area with title, table label, and window.

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

Monospace Used for: System code System output, such as an error message or script Pathnames, file names, file name extensions, prompts, and syntax Commands and options

Monospace italic Used for variables.

Monospace bold Used for user input.

[ ] Square brackets enclose optional values.

| Vertical line indicates alternate selections. The vertical line means or for the alternate selections.

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

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

You can use the following resources to find more information about this product, obtain support, and provide feedback.

Where to find product documentation The Customer Support website The Community Network The PowerProtect Data Manager Info Hub

12 Preface

Where to get support The Customer Support website provides access to product licensing, documentation, advisories, downloads, and how-to and troubleshooting information. The information can enable you to resolve a product issue before you contact Customer Support.

To access a product-specific page:

1. Go to the Customer Support website. 2. In the search box, type a product name, and then from the list that appears, select the product.

Support Library The Support Library contains a knowledge base of applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by keyword.

To search the Support Library:

1. Go to the Customer Support website. 2. On the Support tab, click Support Library. 3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by

typing a product name in the search box, and then selecting the product from the list that appears.

Live chat To participate in a live interactive chat with a support agent:

1. Go to the Customer Support website. 2. On the Support tab, click Contact Support. 3. On the Contact Information page, click the relevant support, and then proceed.

Service requests To obtain in-depth help from a support agent, submit a service request. To submit a service request:

1. Go to the Customer Support website. 2. On the Support tab, click Service Requests.

NOTE: To create a service request, you must have a valid support agreement. For details about either an account or

obtaining a valid support agreement, contact a sales representative. To find the details of a service request, in the

Service Request Number field, type the service request number, and then click the right arrow.

To review an open service request:

1. Go to the Customer Support website. 2. On the Support tab, click Service Requests. 3. On the Service Requests page, under Manage Your Service Requests, click View All Dell Service Requests.

Online communities For peer contacts, conversations, and content on product support and solutions, go to the Community Network. Interactively engage with customers, partners, and certified professionals online.

How to provide feedback Feedback helps to improve the accuracy, organization, and overall quality of publications. You can send feedback to DPADDocFeedback@dell.com.

Preface 13

PowerProtect Data Manager for Microsoft Application Agent Overview

Topics:

PowerProtect Data Manager overview Introducing the Microsoft application agent VM Direct limitations Prerequisites Supported Internet Protocol versions Firewall and port considerations Role-based security Data-in-flight encryption PowerProtect Data Manager new deployment overview PowerProtect Data Manager existing deployment overview

PowerProtect Data Manager overview Use PowerProtect Data Manager with the application agent to perform the following operations:

Automate the configuration of the application agent backup policy and protection storage settings. Create a catalog of backups that the application agent creates. Then, monitor that catalog data to determine if retention

policies are being adhered to. Manage the life cycle of backups that the application agent creates. Ensure that the backups are marked for garbage

collection, based on the rules of the retention policy.

PowerProtect Data Manager does not change the way that the application agent works. DBAs, system administrators, or backup administrators create the backups and perform the restore operations.

Introducing the Microsoft application agent The Microsoft application agent enables an application administrator to protect and recover the Microsoft SQL Server application data on the application host. PowerProtect Data Manager integrates with the Microsoft application agent to check and monitor back up compliance against protection policies. PowerProtect Data Manager also enables central scheduling for backups.

You can install the Microsoft application agent on a Windows Microsoft SQL Server host by using the install wizard. Install and configure the application agent provides instructions.

NOTE:

PowerProtect Data Manager supports the coexistence of the Microsoft application agent and the File System agent on

Windows. When a volume includes any application database and log files:

File System agent block-based backups of the volume automatically exclude the database and log files from the file

system backup.

File System agent file-based backups of the volume do not automatically exclude the database and log files, but you

can explicitly exclude those files through the exclusion filters in the policy. It is recommended that you exclude the

application database and log files from file system backups if you use the corresponding application agent to back up the

files.

1

14 PowerProtect Data Manager for Microsoft Application Agent Overview

In both cases, File System agent backups do not involve any database writer, regardless of whether or not the database and

log files are excluded. The backups do not interfere with the database backup chaining.

The PowerProtect Data Manager File System User Guide provides more details.

In the PowerProtect Data Manager UI, when you select Infrastructure > Assets > SQL and click View Copies, the size

of a Microsoft SQL Server database that is backed up through application-aware protection is displayed as 0 bytes. The

correct size is displayed at the Microsoft SQL Server database asset level. For a transaction log backup, the correct size is

displayed at the Protection Copy Set (PCS) level.

To enable the discovery and scheduling of backups with PowerProtect Data Manager, you must approve the client in the PowerProtect Data Manager UI. Manage the Microsoft application agent provides more information.

The Microsoft application agent supports two protection technologies, Application Direct backup and VM Direct backup. A Microsoft SQL Server host may only be registered to PowerProtect Data Manager with one protection technology. Once registered, it is not possible to change the protection policy for that host.

Software compatibility information for the PowerProtect Data Manager software and application agents is provided by the E-Lab Navigator.

VM Direct limitations The Microsoft application agent does not support the following items for VM Direct operations due to VMware restrictions and feature limitations:

Application-consistent quiescing for virtual machines with IDE disks. Dynamic disks on the virtual machine. Multiple virtual network (MVLAN) environment where the application-aware client is connected to the data network only.

NOTE: The Microsoft application agent supports an MVLAN environment where the application-aware client is

connected to both data and management networks. In this case, the PowerProtect Data Manager server must have

an additional non-default virtual network that is tagged against Data, not against Management.

Read-only volumes mounted on the Microsoft SQL Server virtual machine. VMware encrypted virtual machines. VMware Fault Tolerant virtual machines. RDM storage.

Configure VM Direct with IPv4 and IPv6

When using VM Direct with Microsoft SQL Server, you should explicitly separate virtual machine network communication by the version of Internet Protocol used.

About this task

CAUTION: If this process is not followed, you might not be able to restore assets that have been backed up.

Steps

1. Ensure that all replication DD network interfaces used by the Microsoft SQL Server virtual machines have a name and have the Data network purpose selected.

NOTE: Including IPv4 or IPv6 in the interface names can make it easier to follow the remaining steps.

2. Assign all assets of IPv4 Microsoft SQL Server hosts and their databases to the names of one or more IPv4 replication DD network interfaces.

3. Assign all assets of IPv6 Microsoft SQL Server hosts and their databases to the names of one or more IPv6 replication DD network interfaces.

PowerProtect Data Manager for Microsoft Application Agent Overview 15

Prerequisites Ensure that your environment meets the requirements for a new deployment or update of PowerProtect Data Manager.

Requirements: NOTE: The most up-to-date software compatibility information for the PowerProtect Data Manager software and the

application agents is provided by the E-Lab Navigator.

A list of hosts that write backups to DD systems is available. DDOS version 6.2 or later and the PowerProtect DD Management Center are required. All models of DD systems are

supported. NOTE: PowerProtect DD Management Center is required with a DDOS version earlier than 6.1.2. With DDOS version

6.1.2 or later, you can add and use a DD system directly without PowerProtect DD Management Center.

Application agent 19.12 or earlier is required. License: A trial license is provided with the PowerProtect Data Manager software. Customers can contact Customer

Support for assistance with a permanent PowerProtect Data Manager license. Large environments require multiple PowerProtect Data Manager instances. Contact Champions.eCDM@emc.com for

assistance with sizing requests. The PowerProtect Data Manager 19.12 download file requires the following:

ESXi version 6.5, 6.7, or 7.0. 10 vCPUs, 24 GB RAM, one 100 GB disk, and one 500 GB disk. The latest version of the Google Chrome browser to access the PowerProtect Data Manager UI. TCP port 7000 is open between PowerProtect Data Manager and the application agent hosts.

VMware ESXi server that hosts PowerProtect Data Manager meets the following minimum system requirements: 10 CPU cores 24 GB RAM for PowerProtect Data Manager Five disks with the following capacities:

Disk 1100 GB Disk 2500 GB Disk 310 GB Disk 410 GB Disk 55 GB

One 1-GB NIC Each Microsoft SQL Server host meets the following minimum system requirements:

In a scaled environment: 8 CPU cores 16 GB of RAM

In a stand-alone environment: 4 CPU cores 4 GB of RAM

Microsoft SQL Server host must not have been previously registered to PowerProtect Data Manager using a different protection type, either Application Direct or VM Direct.

For example, if the Microsoft SQL Server host was previously registered to PowerProtect Data Manager with Application Direct during the Microsoft application agent installation, the protection type for that host may not be changed to VM Direct, even if the Microsoft application agent is uninstalled.

NOTE: It is recommended to use stripes only for large databases.

Supported Internet Protocol versions PowerProtect Data Manager and its components support IPv4 and IPv6 addresses in certain configurations.

Table 4. Supported configurations

Component Internet Protocol

PowerProtect Data Manager core

IPv4 only or both IPv4 and IPv6

16 PowerProtect Data Manager for Microsoft Application Agent Overview

Table 4. Supported configurations (continued)

Component Internet Protocol

VM Direct and Search IPv4 only or IPv6 only NOTE: Virtual machines that are backed up must use the same protocol that VM Direct uses. Virtual machines can use both IPv4 and IPv6, even though VM Direct cannot.

Application agents integrated with PowerProtect Data Manager:

NOTE: If both IPv4 and IPv6 are configured and the PowerProtect Data Manager FQDN is used, the agent uses IPv6 for network communication.

File System IPv4, IPv6, or both

Microsoft Exchange Server IPv4 only or both IPv4 and IPv6

Microsoft SQL Server (Application Direct)

IPv4, IPv6, or both

Microsoft SQL Server (VM Direct)

IPv4 only or IPv6 only

NOTE: Only the Microsoft SQL Server agent supports VM Direct.

Oracle RMAN IPv4, IPv6, or both

SAP HANA IPv4, IPv6, or both

Storage Direct IPv4 only

Standalone application agents IPv4 only

Network-attached storage (NAS)

IPv4 only

Kubernetes IPv4 only

PowerProtect Data Manager management

IPv4 or IPv6

PowerProtect DD communication

IPv4 or IPv6

Report Browser IPv4 only

SupportAssist IPv4, IPv6, or both

Syslog Log Server Gateway IPv4 or IPv6

The following limitations and considerations apply.

Communication with components

If PowerProtect Data Manager is configured to only use one protocol, all components it communicates with must also use that protocol. If some components that PowerProtect Data Manager communicates with use IPv4 and others use IPv6, PowerProtect Data Manager must be configured to use both IPv4 and IPv6.

DD systems and DDVE

If a DD system or a DDVE instance uses only IPv6, the required IPv6 interface must be manually selected when a protection policy is added or edited.

Disaster recovery

Recovering a PowerProtect Data Manager server might result in a conflict with protection-policy configurations. For instance, if the recovered server is configured to use only IPv4, a protection policy that is configured to use IPv6 cannot run.

PowerProtect Data Manager for Microsoft Application Agent Overview 17

Name resolution

Name resolution and reverse IP lookup must be configured to ensure the following:

Fully qualified domain names of PowerProtect Data Manager, its components, and DD components resolve to a valid IPv4 or IPv6 address.

If both IPv4 and IPv6 addresses are used for DD, both addresses resolve to the same FQDN. All IPv4 and IPv6 addresses are valid and reachable.

Server updates

IPv6 is only supported with new installations. Using IPv6 after updating from PowerProtect Data Manager 19.11 or earlier is unsupported.

Storage Policy Based Management

If using vCenter or ESXi 7.0u2 or earlier with only IPv6, SPBM providers must be added using their PowerProtect Data Manager FQDN.

Service Unavailable messages with the vSphere Client PowerProtect plug-in

If vCenter uses the vSphere Client PowerProtect plug-in with IPv6 and the vCenter host is added to PowerProtect Data Manager using its IPv6 address or FQDN, Service Unavailable messages might be seen for the protected virtual machine. Backups and restores of the protected virtual machine are unaffected, and these messages can be ignored.

Uncompressed IPv6 formatting

Network interfaces that exist on a DD 7.4.x or earlier system and that are configured to use an uncompressed IPv6 format cannot be discovered. An example of an uncompressed IPv6 format is 2620:0000:0170:0597:0000:0000:0001:001a. An example of a compressed IPv6 format is 2620:0:170:597::1:1a. To use these network interfaces, reconfigure them to use either an IPv4 address or a compressed IPv6 address, and then initiate a discovery.

Firewall and port considerations The latest version of the PowerProtect Data Manager Security Configuration Guide provides more details about the port requirements.

Table 5. PowerProtect Data Manager port requirements

Description Communication Port

SSH communications Bi-directional communication between the SSH client and the PowerProtect Data Manager appliance.

22 TCP/UDP

Microsoft SQL Server, Oracle, Microsoft Exchange Server, SAP HANA, File System

Bi-directional communication between the PowerProtect Data Manager agent and the PowerProtect Data Manager appliance.

Requirement applies to Application Direct and VM Direct.

7000 TCP

REST Server Bi-directional communication between the HTTP client and the PowerProtect Data Manager appliance.

8443 TCP

RESTAPI Server - VM Direct

Bi-directional communication between the PowerProtect Data Manager agent and the PowerProtect Data Manager appliance.

8443 TCP

18 PowerProtect Data Manager for Microsoft Application Agent Overview

Table 5. PowerProtect Data Manager port requirements (continued)

Description Communication Port

Requirement applies to Microsoft SQL Server VM application- aware.

UI redirect Inbound only. 80 TCP

443

LDAP Outbound only. 389 TCP/UDP

636 TCP

Discovery (devices) Outbound between the PowerProtect Data Manager appliance and the device.

3009 TCPStorage Direct and DD system

5989 TCPSMI-S

443 TCPXtremIO

7225 TCPRecoverPoint

PowerProtect Data Manager agent

Bi-directional communication between the database hosts and the PowerProtect Data Manager appliance.

This requirement applies to both Application Direct and VM Direct.

7000 TCP

Embedded VM Direct service

Outbound. 9090 TCP

Role-based security PowerProtect Data Manager provides predefined user roles that control access to areas of the user interface and to protected operations. Some of the functionality in this guide is reserved for particular roles and may not be accessible from every user account.

By using the predefined roles, you can limit access to PowerProtect Data Manager and to backup data by applying the principle of least privilege.

The PowerProtect Data Manager Security Configuration Guide provides more information about user roles, including the associated privileges and the tasks that each role can perform.

Prerequisites for role-based security with Microsoft SQL Server

The PowerProtect Data Manager Administrator role creates resource groups and scopes of authority that enable limited- privilege users to work with specific assets and data.

Before you request a scope of authority from the administrator, review the PowerProtect Data Manager Release Notes and observe the following prerequisites:

For SQL application-aware workflows within scopes of authority, PowerProtect Data Manager does not automatically assign databases to the resource group which contains the corresponding virtual machines. Only manual asset selection is supported. To automatically make the database assets visible to limited-privilege users when selecting by protection policy, configure the resource group to include All Assets for the SQL asset type. This selection is in addition to any virtual machine assets.

PowerProtect Data Manager for Microsoft Application Agent Overview 19

Data-in-flight encryption PowerProtect Data Manager provides centralized management of backup and restore encryption for application agents. Backup and restore encryption is supported for both centralized and self-service operations where applicable.

You can ensure that the backup and restore content is encrypted when read on the source system, transmitted in encrypted form, and then decrypted before it is saved on the destination storage. This prevents another party from intercepting private data.

PowerProtect Data Manager only supports encryption in-flight for File System, Kubernetes clusters, Microsoft SQL Server, Microsoft Exchange Server, network attached storage (NAS), Oracle, and SAP HANA workloads. This is a global setting that is applicable to all supported workloads.

For File System, Microsoft SQL Server, Microsoft Exchange Server, Oracle, SAP HANA, and NAS workloads, backup and restore encryption is only supported for Application Direct hosts. For File System agents, restore encryption is supported for image-level restore only. For Microsoft SQL Server agents, restore encryption is supported for database-level restore only.

The PowerProtect Data Manager Administration and User Guide and PowerProtect Data Manager Security Configuration Guide provide more information about encryption in-flight, such as how to enable the feature and important considerations to understand before enabling.

PowerProtect Data Manager new deployment overview Familiarize yourself with the high-level steps required to install PowerProtect Data Manager with the application agent.

Steps

1. Design how to group the backups, based on the storage requirements and retention policies.

The account team can help with backup storage design.

2. Install PowerProtect DD Management Center.

PowerProtect Data Manager uses PowerProtect DD Management Center to connect to the DD systems. The DD Management Center Installation and Administration Guide provides instructions.

NOTE: PowerProtect DD Management Center is required with a DDOS version earlier than 6.1.2. With DDOS version

6.1.2 or later, you can add and use a DD system directly without PowerProtect DD Management Center.

3. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

4. Add external DD systems or PowerProtect DD Management Center to PowerProtect Data Manager.

The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.

5. Install the application agent on the appropriate hosts and connect them to PowerProtect Data Manager according to the instructions in the next "Enabling" chapter.

DBAs should perform this operation.

6. Add new or approve pending agent requests in the PowerProtect Data Manager according to the instructions in the next "Enabling" chapter.

7. After the approval of agent requests, PowerProtect Data Manager must run a discovery operation to discover the assets.

The PowerProtect Data Manager Administration and User Guide provides information.

8. Add a protection policy for groups of assets that you want to back up.

NOTE: After you create a centralized protection job, the first backup is a full backup.

9. Monitor protection compliance in the PowerProtect Data Manager dashboard.

20 PowerProtect Data Manager for Microsoft Application Agent Overview

PowerProtect Data Manager existing deployment overview Familiarize yourself with the high-level steps required to install PowerProtect Data Manager with the application agent in an existing environment.

Steps

1. Install PowerProtect DD Management Center.

PowerProtect Data Manager uses PowerProtect DD Management Center to connect to the DD systems. The DD Management Center Installation and Administration Guide provides instructions.

NOTE: PowerProtect DD Management Center is required with a DDOS version earlier than 6.1.2. With DDOS version

6.1.2 or later, you can add and use a DD system directly without PowerProtect DD Management Center.

2. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

3. Add external DD systems or PowerProtect DD Management Center to PowerProtect Data Manager.

The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.

4. Update the application agent or uninstall and then reinstall the application agent on the hosts and connect them to PowerProtect Data Manager. Follow the instructions in the next "Enabling" chapter.

DBAs should perform this operation.

5. Add new or approve pending agent requests in the PowerProtect Data Manager according to the instructions in the next "Enabling" chapter.

6. After the approval of agent requests, PowerProtect Data Manager must run a discovery operation to discover the assets.

The PowerProtect Data Manager Administration and User Guide provides information.

7. Add a protection policy for groups of assets that you want to back up.

NOTE: After you create a centralized protection job, the first backup is a full backup.

8. Monitor protection compliance in the PowerProtect Data Manager dashboard.

PowerProtect Data Manager for Microsoft Application Agent Overview 21

Enabling the Microsoft Application Agent for Microsoft SQL Server

Topics:

Microsoft SQL Server data protection and replication requirements Microsoft SQL Server operational log files for backup and restore operations Protecting a stand-alone Microsoft SQL Server Protecting Microsoft SQL Server clustered environments Install and configure the application agent Manage the Microsoft application agent Support for existing Microsoft application agent backups with PowerProtect Data Manager Microsoft application agent for application-aware protection

Microsoft SQL Server data protection and replication requirements PowerProtect Data Manager can manage and monitor data protection and replication for Microsoft SQL Server assets through integration with the Microsoft application agent.

After installing the Microsoft application agent, review the following information for additional requirements before adding the Microsoft application agent as an asset source in PowerProtect Data Manager and discovering the Microsoft SQL Server assets.

Verify that the environment meets the following requirements:

Ensure that you do not mix 32-bit and 64-bit instances on the same Microsoft SQL Server host.

PowerProtect Data Manager operations do not support hosts with a mix of 32-bit and 64-bit Microsoft SQL Server instances.

Ensure that all clocks on the Microsoft SQL Server host, domain controller, and PowerProtect Data Manager are time- synced to the local NTP server to ensure discovery of the backups.

Ensure that the Microsoft SQL Server and the PowerProtect Data Manager system network can see and resolve each other. Ensure that port 7000 is open on the Microsoft SQL Server host. Ensure that port 8443 is open on the Microsoft SQL Server host. This requirement applies only to VM Direct. Ensure that DNS is configured correctly on the application agent host for Microsoft SQL Server. Ensure that DNS is configured correctly on the PowerProtect Data Manager host and the name resolution matches. Ensure that the Microsoft SQL Server host was not previously registered to PowerProtect Data Manager using a different

protection type, either Application Direct or VM Direct.

For example, if the Microsoft SQL Server host was previously registered to PowerProtect Data Manager with Application Direct during the Microsoft application agent installation, the protection type for that host may not be changed to VM Direct, even if the Microsoft application agent is uninstalled.

2

22 Enabling the Microsoft Application Agent for Microsoft SQL Server

Microsoft SQL Server operational log files for backup and restore operations The Microsoft application agent uses the Microsoft SQL Server operational log file _{cent| self}_ _ .log for centralized and self-service backup and restore operations integrated with PowerProtect Data Manager on a Microsoft SQL Server host.

Example logs for Application Direct operations:

Operational log for centralized backup:

ddbmsqlsv_cent_20210729193042_TRACE_ID81adc95d817a1151EXEC_IDa15c4d5c6cc3be6d.log Operational log for centralized restore:

ddbmsqlrc_cent_20210729193042_TRACE_ID81adc95d817a1151EXEC_IDa15c4d5c6cc3be6d.log Operational log for self-service backup:

ddbmsqlsv_self_20210729193042_TRACE_ID81adc95d817a1151EXEC_IDa15c4d5c6cc3be6d.log Operational log for self-service restore:

ddbmsqlrc_self_20210729193042_TRACE_ID81adc95d817a1151EXEC_IDa15c4d5c6cc3be6d.log

Example logs for VM Direct operations:

Operational log for centralized full backup:

msagentcon_cent_ _ .log msagentcon_cent_20220110225147_b84156867446134a_80d7aa6817fba5c2.log

Operational log for centralized TLOG backup:

ddbmsqlsv_cent_ _ .log ddbmsqlsv_cent_20220110225203_b84156867446134a80d7aa6817fba5c2.log

Operational log for centralized full restore:

msagentrc_cent_ _ .log msagentrc_cent_20220110233331_TRACE_ID_b1d721e93e8efa85_EXEC_ID_bbb6ec0de4c98023.log

Operational log for centralized TLOG restore:

ddbmsqlrc_cent_ _ .log ddbmsqlrc_cent_20220111143527_TRACE_ID8ba1d54326cd8fb1EXEC_IDae318092dce5bdf0.log

Operational log for tail log backup:

ddbmsqlsv_cent_20220111144533_TRACE_ID84897b4095326fd0EXEC_IDb9850192b6d8cedd.log Operational log for self-service full restore:

msagentrc_self_ _ .log msagentrc_self_20220111145318_TRACE_ID_ae360518ea36e815.log

Operational log for self-service TLOG restore:

ddbmsqlrc_self_ _ .log ddbmsqlrc_self_20220111145447_TRACE_IDbadeadf11898892f.log

The operational logs are deleted after 15 days by default. To override this default behavior and have the logs deleted before 15 days, you can add the parameter setting purgeOperationalLogDays = in the file \MSAPPAGENT\settings\.ddbmcon.msappagentconfig. Based on this parameter setting, the logs older than the are deleted.

For example, with the following parameter setting, the operational logs are deleted after 5 days:

purgeOperationalLogDays = 5

Enabling the Microsoft Application Agent for Microsoft SQL Server 23

NOTE:

Debug logs are deleted after 30 days.

For VM Direct, the PowerProtect Data Manager export log for backup or restore must include the trace ID.

Protecting a stand-alone Microsoft SQL Server Learn how to configure protection of a stand-alone Microsoft SQL Server.

Steps

1. Add storage for DD Management Console or the external DD.

Add protection storage provides information.

2. Install the Microsoft application agent on the Microsoft SQL Server host.

Install the Microsoft application agent with the wizard provides information.

3. Add or approve the Microsoft application agent in PowerProtect Data Manager.

Manage the Microsoft application agent provides information.

4. Discover and add the credentials for the Microsoft SQL Server application host.

Discover a Microsoft SQL Server application host provides information.

5. Create a protection policy to protect the Microsoft SQL Server host.

Add a protection policy for Microsoft SQL Server database protection provides information.

NOTE: You cannot perform a backup to a secondary DD device. You can only restore from a secondary DD device.

Protecting Microsoft SQL Server clustered environments Learn how to configure protection of Microsoft SQL Server clustered environments, including Always On availability groups and Failover Cluster Instances.

About this task

NOTE:

PowerProtect Data Manager does not support a clusterless Always On Failover Cluster Instance (AAG over FCI)

Microsoft SQL Server.

PowerProtect Data Manager does not support a distributed Always On availability group (distributed AAG) Microsoft

SQL Server. A distributed Always On availability group is a special type of availability group that spans two separate

availability groups.

On each node in the cluster. Repeat the steps to install the Microsoft application agent, and then add and discover the application host in PowerProtect Data Manager.

CAUTION: Protection of Failover Cluster Instances (FCI) requires that all nodes in the cluster be registered

to the PowerProtect Data Manager server. Before registration, the node must be the active node and own all

the disks in the cluster. The recommended method is to failover all nodes to the registering node. Repeat this

step for all nodes in the cluster and any nodes added to the cluster. Failure to perform this step results in

unpredictable results during protection policy.

Steps

1. Add a storage system.

Add protection storage provides information.

2. Install the Microsoft application agent on each node in the cluster.

24 Enabling the Microsoft Application Agent for Microsoft SQL Server

Install the Microsoft application agent with the wizard provides information.

3. Configure the required user privileges on each node in the cluster.

Required privileges for Application Direct backup and recovery provides information.

4. Add or approve the Microsoft application agent on each node in the cluster.

Manage the Microsoft application agent provides information.

5. Discover and add the credentials for each Microsoft SQL Server application host.

Discover a Microsoft SQL Server application host provides information.

6. Create a protection policy to protect the cluster.

Add a protection policy for Microsoft SQL Server database protection provides information.

NOTE: You cannot perform a backup to a secondary DD device. You can only restore from a secondary DD device.

Install and configure the application agent

Prerequisites

Ensure that a Microsoft SQL Server environment meets the following prerequisites before you install the Microsoft application agent:

Install the following applications on the Windows host: Microsoft SQL Server .NET Framework 4.0

If you are installing ItemPoint for table-level recovery, install .NET Framework 4.5.

Ensure that you have a minimum of 2 GB disk space for the installation of the Microsoft application agent.

NOTE: The required log space continues to increase based on the activity on the application agent host. You can

estimate the required log space based on the retention period of the logs as set by the user.

In the PowerProtect Data Manager UI, click and select Downloads from the System Settings menu. Under Microsoft SQL Server, select Download Agent to download the Microsoft application agent download package, msappagent1912_win_x64.zip, to the Windows Microsoft SQL Server host.

Log in to the Microsoft SQL Server host as an administrator to install the Microsoft application agent. To deploy the Common Language Runtime (CLR) assembly, ensure that you have administrator access to the Microsoft SQL

Server host and master database. If the Microsoft SQL Server host is running in a domain, ensure that you have access as a Domain administrator.

Ensure that the required permissions are set up for the discovery of Microsoft SQL Server instances and databases by the PowerProtect agent service. Required privileges for Application Direct backup and recovery provide more information.

Ensure that the sysadmin privilege is set, as required to integrate the Microsoft SQL Server host with the PowerProtect Data Manager and facilitate the discovery of assets with the correct size. Setting the sysadmin privilege for Microsoft SQL Server hosts provides more information.

Install the Microsoft application agent with the wizard

Learn how to install the Microsoft application agent with the installation wizard.

About this task

NOTE:

In Always On availability group (AAG) or cluster environments, install the Microsoft application agent on each node in the

cluster.

Install the same version of Microsoft application agent on each node in an AAG or FCI cluster that is registered to

PowerProtect Data Manager.

Enabling the Microsoft Application Agent for Microsoft SQL Server 25

Steps

1. In the PowerProtect Data Manager UI:

a. Click , and then select Downloads from the System Settings menu. b. Under Microsoft SQL Server, select Download Agent.

The Microsoft application agent download package, msappagent1912_win_x64.zip, is downloaded.

c. Upload the package to the Microsoft SQL Server host on Windows.

NOTE: To verify the authenticity and integrity of the downloaded package, follow the instructions in the PowerProtect

Data Manager Security Configuration Guide.

2. Open msappagent1912_win_x64.zip with WinZip.

3. Use WinZip to extract the msappagent1912_win_x64.zip file.

4. In the extracted folder, launch emcmsappagent-19.12.0.0.exe. The installation wizard appears.

5. On the Welcome Wizard page, select I agree to the license term and agreements, and then click Next.

6. On the Change Install Location page, perform one of the following tasks: To install the Microsoft application agent in the default folder, leave the installation location as is.

The default installation folder is C:\Program Files\DPSAPPS\MSAPPAGENT.

To specify a different installation location, perform the following steps:

a. Click Change. b. In the dialog box that appears, specify the installation location. c. Click OK.

7. Click Next.

8. On the Configure Installation Options page, specify any of the following installation options, as required: To integrate the Microsoft application agent with PowerProtect Data Manager for centralized or self-service protection

of Microsoft SQL Server data, select the following options, as required: To install the Microsoft application agent software, select Application Direct in the Data Paths group box.

NOTE:

The Microsoft application agent supports only the Application Direct and VM Direct workflows.

Ensure that the Microsoft SQL Server host was not previously registered to PowerProtect Data Manager with

the VM Direct option or as part of a virtual machine application-aware protection policy.

For example, if the Microsoft SQL Server host was previously registered to PowerProtect Data Manager with VM

Direct during the Microsoft application agent installation, the protection type for that host may not be changed

to Application Direct, even if the Microsoft application agent is uninstalled.

To install the SQL Server Management Studio (SSMS) plug-in user interface, select SSMS Plug-in.

You can use the SSMS plug-in to perform self-service Microsoft SQL Server backup and restore operations.

To enable table-level restores, select ItemPoint.

This option installs ItemPoint for Microsoft SQL Server, which you can use to perform table-level restores.

Specify the PowerProtect Data Manager appliance details by performing the following steps: a. Select PowerProtect Data Manager in the Common Core Components group box. b. To enable the PowerProtect Data Manager communications port 7000, ensure that the Configure the Windows

Firewall option is selected under Common Core Components. This option is selected by default.

NOTE:

When the Configure the Windows Firewall option is enabled, the installation creates the Windows firewall

rule that allows inbound and outbound connections for the agent service process. Installation of the Microsoft

application agent requires port 7000 on Microsoft SQL Server and port 8443 on PowerProtect Data Manager

to be open bidirectionally. These ports enable communication between the Microsoft application agent and

PowerProtect Data Manager.

26 Enabling the Microsoft Application Agent for Microsoft SQL Server

If the File System agent is already installed and firewall rules are configured, then the Configure the

Windows Firewall option is selected by default but disabled for the Microsoft application agent.

c. In the Appliance hostname or IP address field in the PowerProtect Data Manager Registration group box, type the hostname or IP address of the PowerProtect Data Manager server.

NOTE: If you specify a hostname or fully qualified domain name (FQDN) with an underscore (_) for the

PowerProtect Data Manager server, then the communication will be done by the system's IP, if provided by

the system on registration.

To install the VM Direct Engine onto a virtual machine that is not part of a protection policy, so as to recover application- aware virtual machine backups from a differential virtual machine, select the following options as required:

NOTE:

By default, when a Microsoft SQL Server virtual machine is added to a virtual machine application-aware protection

policy in PowerProtect Data Manager, the Microsoft application agent and ItemPoint are silently installed on the

protected virtual machine. Before you restore a VM Direct Engine backup to an alternate virtual machine that is not

part of a protection policy, you must install the Microsoft application agent on the target virtual machine.

As part of centralized restores, PowerProtect Data Manager also has centralized management for installing the

Microsoft application agent on the virtual machine application-aware host that acts as a recovery-only host.

Select VM Direct in the Data Paths group box.

NOTE:

The PowerProtect Data Manager appliance details are disabled when you select the VM Direct option.

Ensure that the Microsoft SQL Server host was not previously registered to PowerProtect Data Manager with

the Application Direct option.

For example, if the Microsoft SQL Server host was previously registered to PowerProtect Data Manager with

Application Direct during the Microsoft application agent installation, the protection type for that host may not be

changed to VM Direct, even if the Microsoft application agent is uninstalled.

To install the SQL Server Management Studio plug-in user interface, select SSMS Plug-in. To enable table-level restores, select ItemPoint.

This option installs ItemPoint for Microsoft SQL Server, which you can use to perform table-level restores.

9. Click Install >.

10. On the CLR assembly deployment wizard page, perform the following steps:

a. Select or clear the Microsoft SQL Server instances on which you want to deploy the CLR assembly. By default, all the Microsoft SQL Server instances are selected.

Deploying the CLR assembly enables you to run the T-SQL backup and restore scripts that use the CLR-integrated T-SQL functions.

b. To deploy the CLR assembly, select one of the following authentication options:

NOTE: When you deploy the CLR assembly during the Microsoft application agent installation, the deployment

creates a Microsoft SQL Server login with the name ddbmaCLRExtLogin. The CLR procedures run under this

account.

Current Windows User Use Windows Authentication Use Database Authentication

NOTE: The option Enable Storage Direct Stored Procedures is not applicable to Application Direct and VM

Direct workflows.

c. In the User name and Password fields respectively, type the username and the password of the user who has the privileges to deploy the CLR assembly.

d. Click Deploy. e. Click Install. f. After the deployment is complete, click Next.

11. On the Complete the Setup page, click Finish.

Enabling the Microsoft Application Agent for Microsoft SQL Server 27

Install the Microsoft application agent with a silent installation

Learn how to install the Microsoft application agent (including the agent service) with the command prompt for a silent installation.

To silently install the Microsoft application agent (including the agent service), run the following command:

emcmsappagent-19.12.0.0.exe -silent -log " " [ProductInstallPath=" "] [EnableSSMS={0|1}] [EnableVMDirect={0|1}] [EnableProtectPoint={0|1}] [EnableSSMSProtectPoint={0|1}] [InstallPPDMAgentCheckBox={0| 1}] [EnableFirewallRules={0|1}] [PPDMHostname=" "] [EnableCLR={0|1}]

NOTE: The ItemPoint software cannot be installed silently. To install ItemPoint for granular-level recovery, use the

Microsoft application agent installation wizard.

The following table describes the required silent installation command options.

Table 6. Required silent installation command options

Command option Description

-silent Specifies a silent installation.

-log " " Specifies the path where the log file is created or saved. The log file displays the status of the installation. For a silent installation, you must use the -log " " option.

The following table describes the optional silent installation command options.

Table 7. Optional silent installation command options

Command option Description

ProductInstallPath=" " Specifies a modified path where the product and agent service must be installed. This option must be specified for an installation to a custom location. If you do not specify this option, the product and agent service are installed in the default location.

NOTE: The agent service is always installed, regardless of the InstallPPDMAgentCheckBox command option setting.

EnableSSMS={0|1} Specifies whether to install the SSMS plug-in. The default value is 1, which installs the SSMS plug-in.

EnableVMDirect={0|1} Installs VM Direct when you specify the value 1. The default value is 0, which does not install VM Direct.

EnableProtectPoint={0|1} Installs the Storage Direct hardware provider when you specify the value 1. The default value is 0, which does not install Storage Direct.

EnableSSMSProtectPoint={0|1} Installs the Storage Direct hardware provider and the SSMS plug-in for Storage Direct when you specify the value 1. The default value is 0, which does not install these options.

InstallPPDMAgentCheckBox={0|1} Integrates the Microsoft application agent with the PowerProtect Data Manager server during installation when you specify the value 1. The default value is 0.

NOTE: Installation of the PowerProtect agent requires port 7000 to be open bidirectionally. Ensure that you use the EnableFirewallRules=1 command option setting to open the

Windows firewall. Port 7000 is required to enable communication between the Microsoft application agent and the PowerProtect Data Manager appliance.

EnableFirewallRules={0|1} Specifies to configure the Windows firewall when you specify the value 1. The default value is 0. The Windows firewall enables the bidirectional inbound and outbound connections for the agent service over port 7000,

28 Enabling the Microsoft Application Agent for Microsoft SQL Server

Table 7. Optional silent installation command options (continued)

Command option Description

which enables the communication between the Microsoft application agent and PowerProtect Data Manager.

PPDMHostname=" " Specifies the hostname or IP address of the PowerProtect Data Manager server where the backup information is reported.

EnableCLR={0|1} Specifies whether to deploy CLR. By default, this option is enabled and has the value 1, which deploys CLR.

Example commands to silently install the Microsoft application agent

Consider the following example commands to silently install the Microsoft application agent (including the agent service):

The following command installs the Microsoft application agent with VM Direct:

emcmsappagent-19.12.0.0.exe -silent EnableVMDirect=1 The following command installs the Microsoft application agent with the Application Direct SSMS plug-in:

emcmsappagent-19.12.0.0.exe -silent -log "C:\Users\Administrator\Desktop\installLog.txt" ProductInstallPath="C: \Users\Administrator\Desktop\EMC msappagentsappagent40"

The following command installs the Microsoft application agent without deploying CLR:

emcmsappagent-19.12.0.0.exe -silent -log "C:\Users\Administrator\Desktop\installLog.txt" ProductInstallPath="C: \Users\Administrator\Desktop\EMC msappagentsappagent40" EnableCLR=0

The following command installs the Microsoft application agent with Storage Direct only:

emcmsappagent-19.12.0.0.exe -silent -log "C:\Users\Administrator\Desktop\installLog.txt" ProductInstallPath="C: \Users\Administrator\Desktop\EMC msappagentsappagent40" EnableProtectPoint=1 EnableSSMS=0

The following command installs the Microsoft application agent with Storage Direct and the SSMS plug-in:

emcmsappagent-19.12.0.0.exe -silent -log "C:\Users\Administrator\Desktop\installLog.txt" ProductInstallPath="C: \Users\Administrator\Desktop\EMC msappagentsappagent40" EnableSSMSProtectPoint=1

The following command installs the Microsoft application agent with the PowerProtect Data Manager integration:

emcmsappagent-19.12.0.0.exe -silent InstallPPDMAgentCheckBox=1 PPDMHostname=" "

The following command installs the Microsoft application agent (including the agent service) to a custom location that is not on the system drive:

emcmsappagent-19.12.0.0.exe -silent ProductInstallPath="G:\Software\MSAPPAGENT" InstallPPDMAgentCheckBox=1 PPDMHostname=" " EnableCLR=0

The following command installs the Microsoft application agent (including the agent service) to a custom location and enables the firewall for communication with PowerProtect Data Manager:

emcmsappagent-19.12.0.0.exe -silent -log "C:\Temp\PPDM.log" EnableSSMS=1 ProductInstallPath="C:\custom\MSAPPAGENT" InstallPPDMAgentCheckBox=1 EnableFirewallRules=1 PPDMHostname="10.118.136.192" EnableCLR=0

Enabling the Microsoft Application Agent for Microsoft SQL Server 29

Update the Microsoft application agent

If you are using the latest version of PowerProtect Data Manager, the Microsoft application agent 19.12 supports a direct update from version 19.8 or later.

NOTE:

The same version of Microsoft application agent must be installed on each node in an AAG or FCI cluster that is registered

to PowerProtect Data Manager.

During an update from a earlier version, first update the PowerProtect Data Manager to version 19.12 as needed and then

proceed to update the Microsoft application agent on the Microsoft SQL Server host.

If a table-level restore was performed since the last reboot of the host, Microsoft application agent requests a reboot

during an uninstall operation. The Microsoft application agent installs and uses the Eldos CBFS driver for table-level

restores. The Eldos CBFS driver is loaded during the table-level restore operation. Microsoft requires the driver to be

unloaded before an uninstall operation.

1. Launch emcmsappagent-19.12.0.0.exe. The installation wizard appears.

2. On the Welcome Wizard page, select I agree to the license term and agreements, and then click Next. 3. By default, the PowerProtect Data Manager option is selected and the IP address is displayed. If these components were

installed in the previous version, SSMS Plug-in and ItemPoint are also selected.

Whether the PowerProtect Data Manager option was previously selected or you select the option during this update, you can change the firewall rule setting by the Configure the Windows Firewall option under Common Core Components. Select the option to enable the PowerProtect Data Manager communications port 7000 by creating the Windows firewall rule that grants the agent service inbound and outbound access.

NOTE:

The Microsoft application agent requires port 7000 on Microsoft SQL Server and port 8443 on PowerProtect Data

Manager to be open bidirectionally. These ports enable communication between the Microsoft application agent and

PowerProtect Data Manager.

If the File System agent is already installed and firewall rules are configured, then the Configure the Windows Firewall

option is selected by default but disabled for the Microsoft application agent.

Click Upgrade.

4. On the CLR assembly deployment wizard page, perform the following steps:

NOTE: When you deploy the CLR assembly during the Microsoft application agent update, the deployment creates a

Microsoft SQL Server login with the name ddbmaCLRExtLogin. The CLR procedures run under this account.

a. Select or clear the Microsoft SQL Server instances on which you want to deploy the CLR assembly. By default, all the Microsoft SQL Server instances are selected.

b. To deploy CLR assembly, select one of the following authentication options:

Current Windows User Use Windows Authentication Use Database Authentication

c. In the User name and Password fields, respectively, type the username and password of the user who has the privileges to deploy the CLR assembly.

d. Click Deploy. e. Click Install. f. After the deployment is completed, click Next.

5. On the Complete the Setup page, click Finish.

30 Enabling the Microsoft Application Agent for Microsoft SQL Server

Update the application agent in the PowerProtect Data Manager UI

Learn how to perform a precheck operation and update the application agent software on one or more hosts in the PowerProtect Data Manager UI.

Prerequisites

The precheck and update operations are only available for registered clients and application agent versions 19.10 and later.

Steps

To perform a precheck:

1. From the left navigation pane in the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

The Application Agents window opens.

2. Select the check box next to each application agent host to be included in the precheck. When the application agent versions on the selected hosts are 19.10 or later and the versions are earlier than the current PowerProtect Data Manager version, the More Actions button becomes enabled.

3. Click More Actions > Precheck Update.

The Precheck Update window opens.

4. On the Schedule Precheck page:

a. In the Name text box, type a name for the precheck operation. b. Select one of the following options:

Precheck nowPerforms the precheck immediately. Precheck laterSchedules the precheck to occur at a later time. If you select this option, specify the date and time

to perform the precheck.

c. Click Next.

5. On the Summary page, review the information for the selected application agent hosts, and then click OK.

The precheck verifies that the application agent hosts meet the minimum update requirements, including system memory, disk space, and version requirements. If the precheck passes, PowerProtect Data Manager downloads the update software package on each application agent host.

You can monitor the progress of the precheck operation in the System Jobs window.

To perform an update:

6. From the left navigation pane in the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

The Application Agents window opens.

7. Select the check box next to each application agent host to be included in the update.

NOTE: In a cluster environment, select each host of the cluster; otherwise, any unselected hosts are automatically

selected for the update. It is recommended that each host of a cluster has the same application agent version.

When the application agent versions on the selected hosts are 19.10 or later and the versions are earlier than the current PowerProtect Data Manager version, the More Actions button becomes enabled.

8. Click More Actions > Configure Update.

The Configure Update window opens.

9. On the Schedule Updates page:

a. In the Name text box, type a name for the update operation. b. Select one of the following options:

Update nowPerforms the update immediately. Update laterSchedules the update to occur at a later time. If you select this option, specify the date and time to

perform the update.

c. Click Next.

10. On the Summary page, review the information for the selected application agent hosts, and then click OK.

On each selected host, the update performs a precheck, places the host in maintenance mode, updates the application agent, and then returns the host to normal mode.

You can monitor the progress of the update operation in the System Jobs window.

When the update is complete, the update status of each host changes to Up to date in the Application Agents window.

Enabling the Microsoft Application Agent for Microsoft SQL Server 31

If the update fails:

An error is displayed, and you must manually return the hosts to normal mode. Check the agent service logs for details on how to manually restore the host system. Check the ADM logs for more information. For detailed steps to downgrade to a previous version of the application agent, run the following command:

./pushupdate.sh -r -n

Uninstall the Microsoft application agent with the setup file

About this task

To uninstall the Microsoft application agent for Microsoft SQL Server with the setup file, perform the following steps.

NOTE: If a table-level restore was performed since the last reboot of the host, Microsoft application agent requests a

reboot during an uninstall operation. The Microsoft application agent installs and uses the Eldos CBFS driver for table-level

restores. The Eldos CBFS driver is loaded during the table-level restore operation. Microsoft requires the driver to be

unloaded before an uninstall operation.

Steps

1. Launch emcmsappagent-19.12.0.0.exe.

2. On the Install Modification page, select Remove, and then click Next.

3. On the Configure Uninstallation Options page, click Remove.

4. On the Removing the CLR assembly page:

a. Select the required Microsoft SQL Server instances to remove the CLR assembly.

By default, all the Microsoft SQL Server instances are selected.

b. Select one of the following options to remove the CLR assembly:

Use Windows Authentication Use Database Authentication

c. In the User name and Password fields, type the credentials for the user who has the privileges to remove CLR assembly.

d. Click Remove. e. After the removal is completed, click Next.

5. On the Complete the Setup page, click Finish.

Uninstall the Microsoft application agent with a silent uninstallation

Learn how to uninstall the Microsoft application agent with the command prompt for a silent installation.

NOTE: If a table-level restore was performed since the last reboot of the host, Microsoft application agent requests a

reboot during an uninstall operation. The Microsoft application agent installs and uses the Eldos CBFS driver for table-level

restores. The Eldos CBFS driver is loaded during the table-level restore operation. Microsoft requires the driver to be

unloaded prior to an uninstall operation.

To uninstall the Microsoft application agent without any intervention, run the following command:

emcmsappagent-19.12.0.0.exe -uninstall -q UninstallAgentService=1 -log " "

where:

-q indicates a silent uninstallation.

UninstallAgentService=1 is mandatory for a silent uninstallation. If this option is not added in the uninstall command, then the agent service still exists after the Microsoft application agent is uninstalled.

-log specifies the path where the log file must be created or saved.

32 Enabling the Microsoft Application Agent for Microsoft SQL Server

NOTE: The log file displays the status of the uninstallation. For a silent uninstallation, you must use the -log option.

Consider the following example command to silently uninstall the Microsoft application agent:

emcmsappagent-19.12.0.0.exe -uninstall -q UninstallAgentService=1 -log "C: \Users\Administrator\Desktop\uninstallLog.txt"

Recommission the Microsoft application agent after Microsoft SQL Server hostname is changed or reused

Use the procedure in this topic to register and recommission the Microsoft application agent with PowerProtect Data Manager in the following cases: You changed the IP address (static IP), FQDN, or short name of the Microsoft SQL Server host that is registered with

PowerProtect Data Manager. You unregistered the Microsoft SQL Server host from PowerProtect Data Manager and then registered a new host by

reusing the same IP address and hostname of the former host.

NOTE: DHCP is not supported.

Complete the following steps to register and recommission the Microsoft application agent.

1. Disable the protection policy before you change or reuse the IP address (static IP), FQDN, or short name of the Microsoft SQL Server host.

2. Decommission the host by deleting the asset source according to Delete an asset source. This procedure unregisters the host from PowerProtect Data Manager and removes the host assets after all the asset copies have expired.

At this point, the assets and asset source of the original host are still in the "Deleted" state, unless the asset copies have expired and garbage collection has run.

NOTE: If you unregister and reregister the Microsoft application agent instead of completing this decommission step,

then duplicated asset names might appear in the PowerProtect Data Manager UI.

3. Change the IP address (static IP) of the Microsoft SQL Server host. 4. Run the application agent installer and select the change option to register the Microsoft SQL Server host with the same

PowerProtect Data Manager server. 5. Enable the protection policy to continue with the scheduled backups.

Required privileges for Application Direct backup and recovery

Learn about the user requirements for Application Direct backup and recovery.

Required Microsoft SQL Server roles

Assign the user the following Microsoft SQL Server roles:

sysadmin public

Required Windows user permissions

Create a local or domain Windows user account and assign the following roles:

The built-in Windows Administrator. A domain user added to the local Administrators user group. For a stand-alone server only:

For table-level backup and recovery, assign the administrative privileges. For database-level backup and recovery, assign the following permissions:

Add the user to the "Create global objects" Windows policy.

Enabling the Microsoft Application Agent for Microsoft SQL Server 33

For all Microsoft SQL Server instances on the host that will be protected, assign the following permissions to the data and log folder of the database: - Read - Write - List folder contents

Assign the permissions for all paths where databases are stored, including the default data and log folder of the Microsoft SQL Server installation. The default data and log folder may be under the Microsoft SQL Server installation folder. For example, for Microsoft SQL Server 2012, the default folder is C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\.

For an Always On availability group only:

A local user account added to the Administrators user group on each node in the cluster. The username and password must be the same on each node.

NOTE: For an Always On availability group, Failover Cluster Instance, or Always On Failover Cluster Instance, if you

use an account that you created (an account that is not the built-in Windows Administrator), you must launch the tool

where you perform the backup or recovery with elevated permissions (run as administrator).

Setting the sysadmin privilege for the Microsoft SQL Server host

To enable the integration with PowerProtect Data Manager on the Microsoft SQL Server host, the database OS account or NT AUTHORITY\SYSTEM account on the host requires the sysadmin privilege. Setting the sysadmin privilege for Microsoft SQL Server hosts provides more information.

Stagger Microsoft SQL Server discovery jobs in host scale-out environments

In a host scale-out environment with many Microsoft SQL Server hosts to register to PowerProtect Data Manager, consider the following method for staggering the Microsoft SQL Server discovery jobs.

Kick off the installer in smaller group of hosts

When you install the Microsoft application agent by script, kick off the installer in smaller groups of hosts. The discovery jobs will kick off after the agent installation. Distributing the installer in smaller groups helps to stagger the incoming discovery results to PowerProtect Data Manager.

Configure the database backup stripe level

Starting with version 19.6, you can modify the stripe level of a backup at the individual database level by using the following procedures. You can set the stripe level through the following procedures only for self-service stand-alone Microsoft SQL Server backups, not for centralized backups performed through PowerProtect Data Manager.

CAUTION: After you update from version 19.6, centralized backups ignore any parallelism and backup stripe

settings that were previously configured on the Extended Properties page in SQL Server Management Studio

(SSMS). For centralized backups with version 19.6 or later, you must configure the parallelism settings through

the PowerProtect Data Manager UI, as described in the next topic.

The backup stripe level configuration includes the following features:

The backup stripe level setting for individual databases has a higher priority than the stripe level setting through the backup command with the -S option.

For any database, the minimum supported stripe level is 1 and the maximum supported stripe level is 32. In an FCI or AAG cluster, setting the backup stripe level of a database at any node reflects across all the nodes in the cluster.

To set the backup stripe level for any database, use either of the following procedures:

Perform the following steps in the SQL Server Management Studio (SSMS):

1. Right-click the database name, and select Properties. 2. In the properties window, select Extended Properties from the left side pane.

34 Enabling the Microsoft Application Agent for Microsoft SQL Server

3. Add the required property name and the backup stripe level value:

For a full backup, add the property name ppdmFullStripes and a value between 1 and 32. For a differential backup, add the property name ppdmDiffStripes and a value between 1 and 32. For a log backup, add the property name ppdmLogStripes and a value between 1 and 32.

Figure 1. Extended Properties page with backup stripe levels Run the following T-SQL statements to set the backup stripe level for any database:

USE ; GO EXEC sp_addextendedproperty @name = N'ppdmDiffStripes', @value = '4'; EXEC sp_addextendedproperty @name = N'ppdmFullStripes', @value = '8'; EXEC sp_addextendedproperty @name = N'ppdmLogStripes', @value = '2';

Enable multi-stream backups for Microsoft SQL Server protection policy

To enable multi-stream Microsoft SQL Server backups for a centralized protection policy, you can set the parallelism value in the PowerProtect Data Manager UI. The parallelism value controls the number of parallel streams that the Microsoft application agent uses to write the backup data to DD.

The preceding topic describes how to set the stripe level at the individual database level for a self-service stand-alone Microsoft SQL Server backup performed through PowerProtect Data Manager.

The following procedure enables the setting of separate stripe levels for the backup types that are supported for Microsoft SQL Server. If you do not change the settings, the default settings are used for a centralized backup, with a default stripe value of 4 for full and differential backups and a default stripe value of 1 for log backups.

Enabling the Microsoft Application Agent for Microsoft SQL Server 35

CAUTION: After you update from version 19.6, centralized backups ignore any parallelism and backup stripe

settings that were previously configured on the Extended Properties page in SQL Server Management Studio

(SSMS). For centralized backups with version 19.6 or later, you must configure the parallelism settings through

the PowerProtect Data Manager UI.

In the PowerProtect Data Manager UI, perform the following steps to set the parallelism for multi-stream backups:

1. Select Infrastructure > Assets > SQL. 2. Select the required Microsoft SQL Server asset. 3. Select More Actions > Set Stream Count. 4. Set the stream count for each backup type as a value between 1 and 32 in the Full, Differential, and Log fields. The default

stream count values are 4 for full and differential backups and 1 for log backups.

NOTE: A stream count value of 1 is recommended for log backups.

5. Click Save.

Manage the Microsoft application agent You can use the PowerProtect Data Manager UI to add a Microsoft application agent for data protection, approve and reject pending agent requests, and edit and delete existing agents.

Steps

1. Select Infrastructure > Application Agents.

The Application Agents window appears.

NOTE: If the PowerProtect agent service could register during the installation, the Microsoft SQL Server host is already

listed and does not need to be added.

2. C In the Application Agents window, click Add.

3. Select one of the following options:

Select Add FQDN or CSV Filename.

If you select Add FQDN, perform the following steps: a. Type the fully qualified domain name (FQDN) for the application agent. b. Specify the date until which the application agent is preapproved. c. Click Save.

If you select CSV Filename, perform the following steps: a. Click the Choose File icon.

NOTE: The contents of the .csv file must be in the following format, for example:

"ppdm.dell.com" "ppdm2.emc.com" "ppdm.dellemc.com"

The Explorer window appears.

b. Select the .csv file, and then click Open.

The file appears in the window.

c. Select the date until which the application agent is preapproved. d. Click Save.

If you have disabled Auto Allow List, perform the following steps:

NOTE: The Auto Allow List option is disabled by default. When Auto Allow List is enabled, all

preapproved application agents are automatically approved.

a. Select the required application agent. b. Select one of the following options:

Approve

36 Enabling the Microsoft Application Agent for Microsoft SQL Server

Reject Edit, and then make the required changes. Remove

c. Click Save.

Next steps

Discover a Microsoft SQL Server application host describes how to set the host credentials before you schedule a backup.

View application agent details

Use the Application Agents window in the PowerProtect Data Manager UI to monitor the registration and update status of application agents, and view details for individual application agents.

To view application agent details, from the left navigation pane, select Infrastructure > Application Agents.

Agent registration status displays the total number of application agents that are awaiting approval, approved, registered, or rejected.

Agent update status displays the total number of application agents that are up-to-date, available, scheduled, in progress, or failed.

NOTE: If the update of an application agent fails for any reason, the agent host is counted as available. The host is included

in the total number of available applicant agents.

At the end of the Agent update status row, you can click the arrow to view information about scheduled updates. The Schedules table appears and displays the following information:

Update/Precheck Name Date and Time Schedule Status Host Count Actions

The lower table in the Application Agents window displays information about individual application agents. The following table describes the available information.

Table 8. Application agent information

Column Description

Details Click in the Details column to view details and summary information for the application agent, including registration status.

Host Name The name of the application agent host.

IP The IPv4 or IPv6 address of the application agent host.

Registration Status The registration status of the application agent: Awaiting Approval Pending Approval Registered Approved Rejected Expired Accepting Certificates Failed

OS The operating system of the application agent host.

Agent Type The application agent type.

Current Version The current version of the application agent.

Update Status The update status of the application agent host: AvailableThe PowerProtect Data Manager release is 19.12 and the application

agent release is 19.10 or 19.11.

Enabling the Microsoft Application Agent for Microsoft SQL Server 37

Table 8. Application agent information (continued)

Column Description

In ProgressThe update of the application agent is in progress. Up to DateThe PowerProtect Data Manager release and the application agent

release are both 19.12. ScheduledThe application agent is scheduled for an update. FailedThe update of the application agent failed. Not SupportedThe PowerProtect Data Manager release is 19.12 and application

agent release is earlier than 19.10.

Filter and sort information

Use the filtering and sorting options to find specific application agents, and to organize the information that you see.

You can filter and sort the information that appears in table columns. Click in the column heading to filter the information in a table column, or click a table column heading to sort that column.

Use the Search field to filter application agents based on a search string. When you type a keyword in the Search field, the PowerProtect Data Manager UI filters the results as you type. To clear the search filter, remove all keywords from the Search field.

Export application agent data

To export the data that is shown in the table to a .CSV file, click Export All.

For more information about the Export All functionality, see the PowerProtect Data Manager Administration and User Guide.

Support for existing Microsoft application agent backups with PowerProtect Data Manager The Microsoft application agent provides the capability to onboard existing stand-alone deployments, including their existing backups, to PowerProtect Data Manager. Existing backups are Microsoft application agent backups that you performed before integrating the Microsoft application agent with the PowerProtect Data Manager software and before adding an asset to a PowerProtect Data Manager protection policy.

NOTE:

Onboarding of Microsoft SQL Server backup copies to PowerProtect Data Manager is supported only from backups that are

performed with Microsoft application agent 4.7 and later.

You can onboard up to three previous months of existing backups.

Retention lock is not supported for discovered existing backups in PowerProtect Data Manager.

Onboarding is not supported for DD Boost-over-FC backups and 32-bit FCI instance backups.

With the onboarding capability, PowerProtect provides the following centralized features:

Visibility of both existing backups and any new self-service or PowerProtect Data Manager policy-driven backups of onboarded assets.

Automatic configuration of target protection storage based on the PowerProtect Data Manager protection policies that are used for your database.

All the other functionality that is provided for PowerProtect Data Manager protection policies.

When you create a protection policy, the PowerProtect Data Manager software can either create or reuse a storage unit on the specified DD system backup host, subject to limitations. All subsequent backups of assets in that protection policy go to this storage unit. This implementation uses scripts (T-SQL or CLI) or the Microsoft application agent SSMS plug-in UI to override the storage unit information that is provided in any running backup with the storage unit information from PowerProtect Data Manager.

38 Enabling the Microsoft Application Agent for Microsoft SQL Server

Supporting existing Microsoft application agent backups with PowerProtect Data Manager

Learn how to support the existing Microsoft application agent backups.

Steps

1. Update the Microsoft application agent on the Microsoft SQL Server host.

Update the Microsoft application agent provides information.

2. Run the backup discovery tool, AgentBackupDiscovery.exe, to enable management of existing Microsoft application agent backups with PowerProtect Data Manager.

Using the backup discovery tool for PowerProtect Data Manager management of existing backups provides information.

NOTE: This step enables the discovery of old backup copies that the Microsoft application agent created during

self-service backups with stand-alone deployments.

3. Register and approve the Microsoft application agent in PowerProtect Data Manager.

Manage the Microsoft application agent provides information.

After a few minutes of approving the Microsoft SQL Server host, older backup copies are discovered. Depending on the number of backups, the discovery and subsequent visibility of the backups in PowerProtect Data Manager can take some time. The retention time of the discovered existing backup copies equals the retention time that was set in the protection policy plus 14 days, rounded off to the next day.

4. Discover and add the credentials for the Microsoft SQL Server application host.

Discover a Microsoft SQL Server application host provides information.

5. Create a protection policy to protect the Microsoft SQL Server host. For onboarding assets, only a subset of databases can be onboarded. It is not mandatory for all the databases on the host to be onboarded.

Add a protection policy for Microsoft SQL Server database protection provides information.

The first backup after onboarding must be a full backup:

The first centralized backup is automatically promoted to a full backup. The first self-service backup is automatically performed as a full backup.

NOTE: You cannot perform a backup to a secondary DD system device. You can restore only from a secondary DD

system device.

6. Perform a self-service backup of the Microsoft SQL Server databases. Onboarded assets can be part of either a centralized or self-service protection policy.

Performing self-service Microsoft SQL Server database backups provides information.

Using the backup discovery tool for PowerProtect Data Manager management of existing backups

To enable the PowerProtect Data Manager management of existing backups after you have updated the Microsoft application agent or onboarded the current version, you must run the backup discovery tool, AgentBackupDiscovery.exe. Existing backups are Microsoft application agent backups that you performed before integrating the Microsoft application agent with the PowerProtect Data Manager software.

At the end of an update of the Microsoft application agent with the installer, the wizard displays a message about running the AgentBackupDiscovery.exe tool to discover existing backups and manage them in PowerProtect Data Manager software.

CAUTION:

Onboarding of Microsoft SQL Server backup copies to PowerProtect Data Manager is supported only from

backups that are performed with Microsoft application agent 4.7 and later.

Retention lock is not supported for discovered existing backups in PowerProtect Data Manager.

Enabling the Microsoft Application Agent for Microsoft SQL Server 39

You cannot use the backup discovery tool to discover existing DD Boost-over-FC backups or 32-bit FCI instance

backups.

If you delete a Microsoft SQL Server database before onboarding but the database backup copies exist on the

DD system, then after onboarding, PowerProtect Data Manager will not manage those backup copies.

After you run the backup discovery tool, you can continue to use the existing backup scripts to perform the

Microsoft application agent backups. Ensure that all the databases backed up with a particular script are added

to a single protection policy. By default, the PowerProtect Data Manager overrides the DD details by using

the storage unit from the protection policy. If you do not want the DD details to be overridden, use the -a "SKIP_DD_OVERRIDE=TRUE" option in the backup scripts.

To discover the existing backups by using the backup discovery tool, perform the following steps.

1. In the Microsoft application agent installation directory, C:\Program Files\DPSAPPS\MSAPPAGENT\bin, run AgentBackupDiscovery.exe as the administrator.

The Discovery of existing backups dialog box appears.

NOTE: If the program does not start but displays the following message, an ongoing backup discovery process is

running, as invoked by the PowerProtect Data Manager:

Backup discovery is in progress. Please wait for it to complete.

When the discovery process is complete, you can run the backup discovery tool.

2. In the DD system list in the dialog box, select the appropriate DD IP address or hostname, storage unit, and username for the existing backups that you want the PowerProtect Data Manager software to discover.

NOTE: Select only one storage unit at a time. After discovery is complete for the storage unit, you can run the backup

discovery tool again to discover the backups of another storage unit.

3. In the Client hostname field, you can change the client hostname from the default local hostname as needed.

To enable the backup discovery for an AAG or FCI, you must specify the appropriate client hostname:

If the host is part of an AAG, specify the Windows cluster name. If the host is part of a Microsoft SQL Server virtual server or FCI, specify the virtual server name.

4. In the Backup discovery time period field, select the number of months for the time period, as the time in the past when the backups were performed. You can select 1 month, 2 months, or 3 months for the time period.

5. In the Application field, select SQL as the application. 6. After you have specified the required field values, click Generate.

When the PowerProtect Data Manager software completes the generation of the backup metadata or breadcrumbs, the following message appears in the dialog box. Depending on the number of old backups, the generation of breadcrumbs can take some time:

Breadcrumbs generated successfully.

The retention time for the discovered backup is the same as the expiration time set when the backup was taken.

Microsoft application agent for application-aware protection The Microsoft application agent is a component of the PowerProtect Data Manager data protection solution for VMware virtual machines.

A PowerProtect Data Manager application-aware VM protection policy uses the Microsoft application agent to provide advanced application-consistent protection for the following Microsoft SQL Server workloads:

Full backup to DDConfigure a PowerProtect Data Manager protection policy with the application-aware option to perform a Microsoft SQL Server backup to a DD device as part of a VMware image-level backup. A Microsoft SQL Server full backup is performed during the in-guest quiesce by VMware Tools. When the backup is performed as part of the VMware image-level backup, the Microsoft SQL Server data files are backed up as part of the VMDKs during the VM Direct backup. After completing the backup, the Microsoft application agent is automatically run on the virtual machine to catalog the Microsoft SQL Server backup on the DD associated with the protection policy.

40 Enabling the Microsoft Application Agent for Microsoft SQL Server

Transaction log backupWhen configuring a PowerProtect Data Manager protection policy with the Application Aware option, set an interval for Transaction log backup to enable transaction log backups for Microsoft SQL Server instances running on the virtual machine, and specify the frequency of backups. The Microsoft application agent is run on the virtual machine to perform the transaction log backup. Backups are written directly to the DD associated with the protection policy. A transaction log backup is only performed for databases in the proper state; otherwise, databases are skipped.

Database restore, flat file restore, table-level restore, or database Instant Access restore to the source virtual machine or an alternate virtual machine. To perform restores to an alternate virtual machine, that virtual machine must be an asset of PowerProtect Data Manager. However, instance-level restores can only be performed to the original source instance. Performing Self-Service Restores of Virtual Machine Backups provides details on how to use Microsoft application agent to restore Microsoft SQL Server databases backed up with an application-aware VM protection policy.

The Microsoft application agent software package is bundled with the PowerProtect Data Manager appliance, and is automatically configured on a virtual machine when you add the virtual machine asset to a VM application-aware protection policy. As part of the VM protection policy configuration, both the VM Direct Agent and the Microsoft application agent are installed on the virtual machine. The Microsoft application agent installation includes the software components that are required for self-service restore, including the Microsoft application agent SQL Server Management Studio (SSMS) plug-in and ItemPoint. After the agent installations, configuration information for the DD is also sent to the virtual machine, calling the Microsoft application agent to perform the lockbox configuration. Subsequent protection policy backups and self-service restore operations jobs also use this information without any further action required. During application-aware Microsoft SQL Server full backups and transaction log backups, PowerProtect Data Manager updates the VM Direct Agent and Microsoft application agent software packages as required.

The virtual machine credentials that are provided in the protection policy or within the virtual machine asset are used during Microsoft application agent installation and during Microsoft SQL Server full and transaction log backups. The Microsoft application agent is first called to validate the virtual machine configuration. The agent verifies that the Microsoft SQL Server is installed and running, and that the provided virtual machine credentials have the necessary permissions to perform a Microsoft SQL Server backup.

In order to perform Microsoft SQL Server application-consistent data protection for virtual machines, the Microsoft application agent requires the following:

The Microsoft application agent runs under the virtual machine credentials that are provided in the VM protection policy or virtual machine asset for installation and data protection operations. Configure all Microsoft SQL Server instances on the virtual machine to grant account rights for this account to perform Microsoft SQL Server database backup and recovery operations: Add the account to Microsoft SQL Server logins. Grant the account the sysadmin role.

NOTE: The Microsoft application agent supports only a domain Administrator or local Administrator account for the

virtual machine credentials. The user can be an Administrator, a domain user with local Administrator privileges, or a local

user with local Administrator privileges. Minimum required privileges for VM Direct backup and recovery provides details

on how to enable the support for a domain or local user with Administrator privileges.

Network connectivity, hostname resolution, and firewall ports between the DD device and the virtual machines that are part of Microsoft SQL Server application-consistent protection policies and restore to alternate operations. This connectivity is required to enable the Microsoft application agent to perform client direct operations to DD.

VMware vCenter server version 6.5 or later. VMware ESXi server version 6.5 or later. VMware Tools version 10.1 or later. Enable the UUID attribute (disk.EnableUUID=TRUE) in the vSphere Client.

NOTE: After you set disk.EnableUUID to TRUE, ensure that you reboot the virtual machine.

The virtual machine must use SCSI disks only, and the number of available SCSI slots must at least match the number of disks. For example, a virtual machine with 7 disks only requires one SCSI controller, but a virtual machine with 8 disks requires 2 SCSI controllers.

The VM Direct Engine requires live network connectivity to the ESXi where the targeted Microsoft SQL Server virtual machine resides.

Enabling the Microsoft Application Agent for Microsoft SQL Server 41

Multiple virtual networks (MVLANs) for Microsoft SQL Server application-aware protection

PowerProtect Data Manager cannot automatically configure a virtual network connection between an agent in a virtual machine and PowerProtect Data Manager when PowerProtect Data Manager is configured with multiple virtual network connections.

If you use multiple virtual networks, the virtual machine asset must have a connection to the default interface for PowerProtect Data Manager. Manually configure the VLAN to provide access to the virtual machine before you add the virtual machine to the protection policy.

Naming conventions for backups with VM Direct

When naming Microsoft SQL Server instance, database, and filegroups, consider that the Microsoft application agent does not distinguish the difference between upper and lowercase letters. The names are not case-sensitive.

Therefore, if there are two or more databases with the same name but with different capitalization, such as DB1 and db1, the Microsoft application agent views these databases as the same and by default backs up only one of the databases.

The following table describes the special characters that are supported for naming database backups in Microsoft SQL Server stand-alone, cluster, and Always On availability group configurations with VM Direct.

Table 9. Special characters supported with VM Direct

Special character Name

~ Tilde

` Accent grave

! Exclamation mark

@ At the rate

% Percentage

^ Caret

& Ampersand

( Open parenthesis

) Close parenthesis

- Hyphen

_ Underscore

{ Open curly bracket

} Close curly bracket

\ Backslash

. Period

NOTE: While Microsoft SQL Server supports naming instances with the hash symbol (#), the Microsoft application agent

does not. If an instance includes a hash symbol, backups of that instance will fail.

Minimum required privileges for VM Direct backup and recovery

Learn about the user requirements for VM Direct backup and recovery.

The minimum required privileges for VM Direct backup and restore operations depend on the version of vmtools that is installed on the VM system:

With the vmtools version 11.x or later, the Microsoft application agent supports a domain user or local user account with enabled UAC for the virtual machine credentials.

42 Enabling the Microsoft Application Agent for Microsoft SQL Server

With the vmtools version earlier than 11.x, the Microsoft application agent supports only a domain Administrator or local Administrator account with disabled UAC for the virtual machine credentials. The user can be an Administrator, a domain user with local Administrator privileges, or a local user with local Administrator privileges (user is added to the domain of PowerProtect Data Manager).

The following subtopic provides more details about enabling the required user privileges for VM Direct operations.

Windows permissions required for the domain user or local user for VM Direct workflow

With vmtools version 11.x or later installed on the VM system, you can configure the protection policies and perform the VM Direct backup and restore operations by using domain user or local user credentials with enabled UAC.

To enable the support for a domain user or local user with enabled UAC, make the user a member of the "Administrators" Active Directory group in Computer Management > System Tools > Local Users and Groups.

The user can be an Administrator, a domain user with local Administrator privileges, or a local user with local Administrator privileges.

NOTE: UAC is enabled by default on a Windows VM system. If you need to enable UAC, complete the following steps:

1. Select Control Panel > User Accounts > User Accounts > Change User Account Control Settings, and move the

slider to select Notify me only when apps try to make changes to my computer.

2. Select Local Security Policy > Local Policies > Security Options > User Account Control: Run all

administrators in Admin Approval Mode, and select Enabled on the Local Security Setting tab.

3. Reboot the VM system.

When you configure a protection policy, edit the policy and select the domain user or local user.

NOTE: To use the SSMS plug-in as the local user to perform a self-service restore of a VM Direct backup, you must launch

the SSMS plug-in by selecting Run as administrator.

Enabling the Microsoft Application Agent for Microsoft SQL Server 43

Managing Storage, Assets, and Protection

Topics:

Add protection storage Enable an asset source Delete an asset source Recommission the Microsoft application agent Setting the sysadmin privilege for Microsoft SQL Server hosts Discover a Microsoft SQL Server application host Replication triggers Add a protection policy for Microsoft SQL Server database protection Cancel a Microsoft application agent protection or restore job Add a service-level agreement Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier) Edit the retention period for backup copies Delete backup copies Enable the Microsoft application agent after Internet Protocol change Enable the Microsoft application agent after hostname change Manage the PowerProtect agent service Manage the cloud tier operations with PowerProtect Data Manager

Add protection storage Add and configure protection storage to use as a target for protection policies. Adding protection storage requires the Administrator role.

Prerequisites

NOTE:

When adding a High Availability PowerProtect DD system, observe the following points:

Do not add the individual active and standby DD systems to PowerProtect Data Manager.

In the Address field, use the hostname that corresponds to the floating IP address of the High Availability PowerProtect

DD system.

The High Availability PowerProtect DD system is verified with the root certificate.

About this task

The PowerProtect Data Manager Administration and User Guide provides more information about protection storage and related concepts:

High availability options Smart Scale system pools, a single interface to a flexible group of pool members Working with protection storage Working with storage units

Steps

1. From the left navigation pane, select Infrastructure > Storage.

The Storage window appears.

2. In the Protection Storage tab, click Add.

3

44 Managing Storage, Assets, and Protection

3. In the Add Storage dialog box, select a storage system (PowerProtect DD System or PowerProtect DD Management Center).

For a system pool, select DDMC.

4. To add a High Availability PowerProtect DD system, select the checkbox.

5. Specify the storage system attributes:

a. In the Name field, specify a storage name. b. In the Address field, specify the hostname, fully qualified domain name (FQDN), or the IP address. c. In the Port field, specify the port for SSL communication. Default is 3009.

6. Under Host Credentials click Add, if you have already configured protection storage credentials that are common across storage systems, select an existing password. Alternatively, you can add new credentials, and then click Save.

7. If a trusted certificate does not exist on the storage system, a dialog box appears requesting certificate approval. Click Verify to review the certificate, and then click Accept.

8. Click Save to exit the Add Storage dialog and initiate the discovery of the storage system.

A dialog box appears to indicate that the request to add storage has been initiated.

9. In the Storage window, click Discover to refresh the window with any newly discovered storage systems. When a discovery completes successfully, the Status column updates to OK. If DDMC is selected, all DD systems managed by the host will be listed after discovery.

10. To modify a storage system location, complete the following steps:

A storage system location is a label that is applied to a storage system. If you want to store your copies in a specific location, the label helps you select the correct storage system during policy creation.

a. In the Storage window, select the storage system from the table. b. Click More Actions > Set Location.

The Set Location window appears. c. Click Add in the Location list.

The Add Location window appears. d. In the Name field, type a location name for the asset, and click Save.

Results

PowerProtect Data Manager displays external DD systems only in the Storage window Name column. PowerProtect Data Manager displays PowerProtect DD Management Center storage types in the Managed By column.

View the storage unit password

PowerProtect Data Manager provides a script to retrieve the password for a storage unit that you configured as a backup target.

Prerequisites

This task requires the name of the protection storage system MTree where the storage unit resides.

Steps

1. Connect to the PowerProtect Data Manager console as an admin user.

2. Navigate to the /usr/local/brs/puppet/scripts directory.

3. Obtain the storage unit password by typing the following command:

python get_dd_mtree_credential.py MTree-name For example:

python get_dd_mtree_credential.py accounting-75914 ==============PowerProtect DD MTree credential============== Full MTree path: /data/col1/accounting-75914 User name: accounting-75914 Password: IwWXT#DC93m={XV+K ========================================================

Managing Storage, Assets, and Protection 45

Enable an asset source An asset source must be enabled in PowerProtect Data Manager before you can add and register the asset source for the protection of assets.

About this task

Only the Administrator role can manage asset sources.

In some circumstances, the enabling of multiple asset sources is required. For example, a vCenter Server and a Kubernetes cluster asset source must be enabled for Tanzu Kubernetes guest cluster protection.

There are other circumstances where enabling an asset source is not required, such as the following:

For application agents and other agents such as File System and Storage Direct, an asset source is enabled automatically when you register and approve the agent host. For example, if you have not enabled an Oracle asset source but have registered the application host though the API or the PowerProtect Data Manager user interface, PowerProtect Data Manager automatically enables the Oracle asset source.

When you update to the latest version of PowerProtect Data Manager from an earlier release, any asset sources that were previously enabled appear in the PowerProtect Data Manager user interface. On a new deployment, however, no asset sources are enabled by default.

Steps

1. From the PowerProtect Data Manager user interface, select Infrastructure > Asset Sources, and then click + to reveal the New Asset Source tab.

2. In the pane for the asset source that you want to add, click Enable Source. The Asset Sources window updates to display a tab for the new asset source.

Results

You can now add or approve the asset source for use in PowerProtect Data Manager. For a vCenter server, Kubernetes cluster, SMIS Server, or PowerProtect Cloud Snapshot Manager tenant, select the appropriate tab in this window and click Add. For an application host, select Infrastructure > Application Agents and click Add or Approve as required.

NOTE: Although you can add a Cloud Snapshot Manager tenant to PowerProtect Data Manager in order to view its health,

alerts, and the status of its protection, recovery, and system jobs, you cannot manage the protection of its assets from

PowerProtect Data Manager. To manage the protection of its assets, use Cloud Snapshot Manager. For more information,

see the PowerProtect Cloud Snapshot Manager Online Help.

Disable an asset source

If you enabled an asset source that you no longer require, and the host has not been registered in PowerProtect Data Manager, perform the following steps to disable the asset source.

About this task

NOTE: An asset source cannot be disabled when one or more sources are still registered or there are backup copies of the

source assets. For example, if you registered a vCenter server and created policy backups for the vCenter Server virtual

machines, then you cannot disable the vCenter Server asset source. But if you register a vCenter server and then delete it

without creating any backups, you can disable the asset source.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then select the tab of the asset source that you want to disable. If no host registration is detected, a red Disable button appears.

2. Click Disable.

Results

PowerProtect Data Manager removes the tab for this asset source.

46 Managing Storage, Assets, and Protection

Delete an asset source If you want to remove an asset source that you no longer require, perform the following steps to delete the asset source in the PowerProtect Data Manager UI.

About this task

Only the Administrator role can manage the asset sources.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then select the tab for the type of asset source that you want to delete.

2. Select the asset source name in the asset source list, and then click Delete.

3. At the warning prompt that appears, click Continue. The asset source is deleted from the list.

Results

PowerProtect Data Manager removes the specified asset source in the Asset Sources window.

Any associated assets that are protected by the protection policy are removed from the protection policy and their status is changed to deleted. These assets are removed automatically as part of daily PowerProtect Data Manager cleanup after all associated backup copies have been deleted. These assets can also be removed manually. The PowerProtect Data Manager Administration and User Guide provides details on how to remove assets from PowerProtect Data Manager.

The copies of assets from the asset source are retained (not deleted). You can delete the copies from the copies page, if required.

Recommission the Microsoft application agent You can use the procedure in this topic to register and recommission the Microsoft application agent with the PowerProtect Data Manager server.

About this task

To register the application agent back to the same PowerProtect Data Manager server after you delete an asset source, complete the following steps.

Steps

1. Go to Control Panel > Programs > Programs and Features.

2. Use the Change option for the Microsoft application agent to recommission the Microsoft application agent.

3. In the installation wizard, select the PowerProtect Data Manager option.

Results

After the installation completes, the Microsoft application agent is re-registered to the PowerProtect Data Manager server.

Setting the sysadmin privilege for Microsoft SQL Server hosts To enable the integration with PowerProtect Data Manager on each Microsoft SQL Server host, ensure that the database OS account or NT AUTHORITY\SYSTEM account on each host has the required sysadmin privilege.

Before you register any Microsoft SQL Server host with PowerProtect Data Manager, set the required sysadmin privilege by completing one of the following two procedures on each Microsoft SQL Server host.

Managing Storage, Assets, and Protection 47

Setting the sysadmin privilege for database OS account

By default, the Microsoft application agent uses the SYSTEM account for asset discovery. However, this requires granting the SYSTEM account the Microsoft SQL Server sysadmin role, which might not comply with corporate security requirements. As an alternative, you can complete the following procedure to use a domain or local user account instead for asset discovery. When you select the option Use the credentials for both asset discovery and backup as follows, the configuration for using the domain or local user account is centrally managed from PowerProtect Data Manager.

NOTE: This procedure is only supported for a host with application agent release 19.11 or later installed.

Complete the following steps to ensure that the database OS account on each host has the sysadmin privilege.

1. Log in to each Microsoft SQL Server instance, open the SQL Server Management Studio (SSMS), and select View > Object Explorer.

2. In the Object Explorer, expand Security and then expand Logins. 3. Right-click the database OS account name, and then select Properties. 4. In the Login properties window, select Server Roles. 5. Select sysadmin under Server roles. 6. Click OK.

The Login properties window closes.

7. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then select the SQL tab. 8. Select the required hostname in the list, and then click Edit Credentials. 9. On the Set Credential page, specify the database OS credentials and select the option Use the credentials for both

asset discovery and backup.

NOTE: On the Set Credential page, the option Use the credentials for both asset discovery and backup does not

appear when the database OS credentials setting is None or the application agent release is earlier than 19.11.

10. Click Save.

Setting the sysadmin privilege for NT AUTHORITY\SYSTEM account

Complete the following steps to ensure that the NT AUTHORITY\SYSTEM account on each host has the sysadmin privilege.

1. Log in to each Microsoft SQL Server instance, open the SQL Server Management Studio (SSMS), and select View > Object Explorer.

2. In the Object Explorer, expand Security and then expand Logins. 3. Right-click NT AUTHORITY\SYSTEM, and then select Properties. 4. In the Login properties window, select Server Roles. 5. Select sysadmin under Server roles. 6. Click OK.

The Login properties window closes.

Discover a Microsoft SQL Server application host After you register an application host with PowerProtect Data Manager, the host appears in the Asset Sources window. Then you can select the host, perform discovery, and modify the application host credentials. For application hosts, discovery is required if you want to schedule a backup. Assets must also be discovered for the centralized copy management of self-service backups.

About this task

Perform the following steps to discover a Microsoft SQL Server application host as an asset source in the PowerProtect Data Manager UI.

Steps

1. Select Infrastructure > Asset Sources.

The Asset Sources window appears.

48 Managing Storage, Assets, and Protection

2. Select the SQL tab.

3. If you are adding a Microsoft SQL Server database, select the host entry and click Edit Credentials.

The Edit Credentials dialog appears.

NOTE: The supported syntax for credentials is @ or @ . The syntax \ or

\ is not supported.

4. If you are adding credentials for a Microsoft SQL Server database, ensure that you specify the OS credentials for the Microsoft SQL Server host. Ensure that these credentials have the rights to perform the Microsoft SQL Server backup and restore operations.

5. Click Save.

6. On the SQL tab, select the application host and then click Discover.

The Initiate Discovery dialog appears with an option to immediately start a full discovery of the assets on the host.

NOTE: On the SQL tab, you can click Discover at any time if any additions or other changes to your Asset Sources

have taken place outside of the PowerProtect Data Manager environment. Asset discovery is also initiated by default

after registration of the host to PowerProtect Data Manager and at hourly intervals. Discovery time is based on

networking bandwidth. Each time you initiate a discovery process, the resources that are discovered and those that are

handling the discovery impact the system performance.

7. Click Yes.

Results

If the application host is properly configured and discovery is successful, the database assets can now be added to a PowerProtect Data Manager protection policy.

Replication triggers PowerProtect Data Manager orchestrates protection policy replication objectives independently of the primary backup. When you add a replication objective to a policy, select one of the available triggers.

The default replication trigger is a schedule window that you define by setting a recurrence period plus start and end times. Replication occurs during the defined window. For example, every day between 8 p.m. and 12 a.m.

You can also trigger replication immediately after the completion of the associated primary backup, whether scheduled or manual. At the start of the primary backup, PowerProtect Data Manager generates an associated replication job that remains queued until the end of the protection job. If the backup fails or completes with exception, the associated replication job is skipped. Restarting the protection job queues the associated replication job again.

When you create a replication objective, you can specify either scheduled replication or replication after backup completion, which is applicable to both centralized and self-service protection policies.

NOTE: For replication after backup completion, PowerProtect Data Manager 19.12 or later and application agents 19.10 or

later are required. It is recommended that you update the application agents to the latest version.

Using a schedule can help you manage network traffic by replicating during off-peak hours. However, for larger backup sets, the primary backup may not finish before the start of the replication schedule, which creates a replication backlog. Replication after backup completion prevents a replication backlog from forming.

To prevent data loss, the replication after backup completion trigger replicates new backups from the primary objective and any outstanding backups that have not yet replicated.

A job status of Completed with Exceptions during replication

After a triggered replication job, you might see a job status message similar to the following:

Completed with Exceptions ABA0017: plc_linux_rac: Backup was successful for the ORACLE_DATABASE asset ORCLPP on the host blrv009d132.blr.lab.emc.com but the copy metadata information is currently unavailable.

The backup of this asset completed successfully but the copy metadata information has

Managing Storage, Assets, and Protection 49

not yet been discovered by PowerProtect Data Manager. If the 'Replicate immediately upon backup completion' option is enabled for this protection policy, the replication job for the copy might appear in 'Unknown' or 'Cancel' state. Once the copy metadata is discovered by PowerProtect Data Manager, the copy will be replicated.

Review the backup copy details in the View Copies pane of the PowerProtect Data Manager UI Infrastructure > Assets window to determine when the discovery is complete.

If you see this message, the replication backup is not immediately available.

To correct this issue, either wait for the next automatic discovery or initiate a discovery.

Add a protection policy for Microsoft SQL Server database protection Use the PowerProtect Data Manager UI to add a protection policy group for the purposes of Microsoft SQL Server database protection.

Prerequisites

Before you perform a backup on a weekly or monthly schedule from the protection policy, ensure that the PowerProtect Data Manager time zone is set to the local time zone. If the PowerProtect Data Manager time zone is not set to the local time zone, the weekly or monthly backup still runs but is triggered based on the PowerProtect Data Manager time zone.

If applicable, complete all of the virtual network configuration tasks before you assign any virtual networks to the protection policy. The PowerProtect Data Manager Administration and User Guide provides more information.

NOTE: The option to create a storage unit during protection policy configuration does not support compliance mode

retention locking, only governance mode. To use compliance mode retention locking, create and configure a storage unit

before you configure an associated protection policy. If you enable retention locking and select a storage unit where

the retention lock mode is None, the retention lock defaults to governance mode. The PowerProtect Data Manager

Administration and User Guide provides more information.

About this task

NOTE: If a database is protected in an Always On availability group, you cannot configure stand-alone backups of that

database in a protection policy group.

Steps

1. From the left navigation pane, select Protection > Protection Policies.

The Protection Policies window appears.

2. In the Protection Policies window, click Add.

The Add Policy wizard appears.

3. On the Type page, specify the following fields, and then click Next:

NameType a descriptive name for the protection policy. DescriptionType a description for the policy. TypeSelect Microsoft SQL.

4. On the Purpose page, select from the following options to indicate the purpose of the new protection policy group, and then click Next:

Centralized ProtectionSelect this option to use PowerProtect Data Manager to centrally manage all objectives of the protection policy. This option also enables the self-service operations.

Centralized protection means that PowerProtect Data Manager schedules the backups and manages the life cycle of the copies. DBAs can also schedule the self-service backups when required.

Click Set Credentials to specify new credentials or select existing credentials from the list.

NOTE:

50 Managing Storage, Assets, and Protection

The supported syntax for credentials is @ or @ . The syntax \ or

\ is not supported.

The host-level credentials take precedence over protection policy-level credentials.

Self-Service ProtectionSelect this option to use Microsoft SQL Server to create local backup protection. PowerProtect Data Manager creates a protection policy and manages extra objectives.

Self-service protection means that DBAs schedule the backups but PowerProtect Data Manager discovers and manages the life cycle of the copies.

ExclusionSelect this type if there are assets within the protection policy that you plan to exclude from data protection operations.

5. On the Assets page, select the assets for inclusion in this policy by using either the Microsoft SQL Server hierarchical view or the list view. To select the preferred view, click one of the two icons on the top right of the page. You can switch between the views by clicking the icons:

NOTE: A Microsoft SQL Server database asset can be protected by only one protection policy at a time.

Hierarchical viewThis view uses a tree view that shows the hierarchical relationships of the Microsoft SQL Server hosts, their application servers or instances (including Failover Cluster Instances (FCIs)), stand-alone database assets, and any Always On availability groups (AAGs) with their database assets. When you expand the hierarchical or tree view, you can see all the assets and AAGs within a host and instance. When you select a host or instance container, all the contained assets and objects are also selected. You can also select individual assets or a group of assets within the host or instance container to include in the protection policy.

NOTE:

For FCIs and AAGs, when you select the node of one host, the same selection automatically applies to the other

hosts in the cluster.

The hierarchical view is supported only for an Application Direct protection policy, not an application-aware

protection policy.

The hierarchical view is also available on the following pages in the PowerProtect Data Manager UI:

Protection > Protection Policies > Protect Now

Protection > Protection Policies > Edit Policy > Assets

Infrastructure > Assets

Restore > Assets

When you select a host or instance within the hierarchical view, the Dynamic Protection and AAG Selection icons appear on the container line:

NOTE: If a selected instance is the only instance on a host, the icons appear on the host line above the instance, not

on the instance line.

Dynamic ProtectionWhen this icon is enabled (by default), a dynamic protection rule is automatically created to ensure that all the selected assets within the selected host or instance container are dynamically protected by the protection policy. PowerProtect Data Manager manages the protection rule. The rule is updated automatically when you edit the policy and make changes to the container selections, or when assets are moved into or out of a selected container.

With dynamic protection, any new databases or assets that you add to the instance or AAG or container after the policy is created or edited will be automatically added to the protection policy. Any databases or assets that you remove from the instance or AAG or container are also removed from the policy. When any selection overlap occurs between different policies, the UI displays the overlaps and helps you to resolve the asset assignment conflicts by adjusting the protection rules' priority.

To disable the dynamic protection for a container, click the Dynamic Protection icon and then click Disable in the displayed text box. When the dynamic protection is disabled, the protection policy does not dynamically protect the selected container and its objects. As a result, all the selected objects within the container become static selections that are not automatically protected by the policy.

After you create or edit a protection policy that has dynamic protection, you can select Protection > Protection Rules to see the protection rule details for the protection policy, including the priority of the protection rule. Dynamic protection rules apply only at the container level.

Managing Storage, Assets, and Protection 51

AAG SelectionThis icon appears when the selected host or instance includes one or more AAGs. By default, the icon is enabled and all the AAGs within the host or instance are selected. When you want to exclude all the contained AAGs from the protection policy, click the AAG Selection icon and then click Exclude in the displayed text box.

In the hierarchical view, you might see a yellow warning icon in the Protection Policy column, next to a selected host, instance, database, or AAG. The warning icon indicates that one of the following issues exists. Hover over the warning icon to see the issue description:

When the Microsoft application agent version is earlier than 19.9, an AAG folder might display an incomplete hierarchical view of the data. To obtain a complete view of the data, update the Microsoft application agent.

An asset assignment conflict exists because the host, instance, or contained object is already protected by another protection policy. After you click Next on the Assets page and click OK on a notification page, the Check conflicts due to rule priority page appears, where you can adjust the protection rule priorities and resolve the conflicts.

List viewThis view uses a table display that enables you to see all unprotected assets within a table, and then select individual unprotected assets that you want to include in the protection policy.

6. Click Next.

If the Assets page included any asset assignment conflicts with other protection policies, a notification page appears that describes the assets that are already assigned to other protection policies. Click OK to continue or Cancel to return to the Assets page.

When you click OK, the Check conflicts due to rule priority page appears, displaying the assets with conflicting assignments and their protection policies and rules. In the Protection Rules pane, you can click the up and down arrows to change the protection rule priority of any policy. When you raise the rule priority for a policy, the assets with conflicts in a lower-priority policy are moved to the policy with the higher protection rule priority.

7. Click Next.

If you selected Exclusion on the Purpose page, the Summary page appears. Proceed to the final two steps.

If you selected Centralized Protection or Self-Service Protection on the Purpose page, the Objectives page appears for creating the protection policy backup configuration.

8. On the Objectives page, select a policy-level Service Level Agreement (SLA) from the Set Policy Level SLA list, or select Add to open the Add Policy Service Level Agreement wizard and create a new policy-level SLA.

Add a service-level agreement provides instructions.

9. Complete the steps for the specified type of protection policy group:

For Centralized Protection:

a. Click Add under Primary Backup.

The Add Primary Backup dialog appears.

b. On the Target pane of the Add Primary Backup dialog, specify the following fields:

Storage NameSelect a backup destination from the list of existing DD systems, or select Add to add a system and complete the details in the Storage Target dialog.

Storage UnitSelect whether this protection policy should use a New storage unit on the selected DD system, or select an existing storage unit from the list. Hover over a storage unit to view the full name and statistics for available capacity and total capacity, for example, testvmpolicy-ppdm-daily-123ab (300 GB/1 TB).

When you select New, a new storage unit in the format policy name hostname unique identifier is created in the storage system upon policy completion, for example, testvmpolicy-ppdm-daily-123cd.

NOTE: The Space field indicates the total amount of space, and the percentage of available space, on the

storage system.

Network InterfaceSelect a network interface from the list, if applicable. Retention LockMove the Retention Lock slider to the right to enable retention locking for these backups.

The retention lock mode setting comes from the configuration of the selected storage unit. When you enable retention locking, the Retention Lock Mode field displays the corresponding storage unit setting.

Setting a retention lock applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.

NOTE: Primary backups are assigned a default retention lock period of 14 days. Replicated backups, however,

are not assigned a default retention lock period. If you enable Retention Lock for a replicated backup, ensure

that you set the Retain for field in the Add Replication dialog to a minimum number of 14 days so that the

replicated backup does not expire before the primary backup.

52 Managing Storage, Assets, and Protection

SLASelect an existing service level agreement that you want to apply to this schedule from the list, or select Add to create an SLA within the Add Backup Service Level Agreement wizard.

Add a service-level agreement provides instructions.

c. On the Schedules pane of the Add Primary Backup dialog:

i. Specify the following fields to schedule the full backup of this protection policy:

Create a Full backup everySpecify how often to create a full backup. Retain forSpecify the retention period for the backup.

NOTE: For database backups, PowerProtect Data Manager chains the dependent backups together. For

example, the incremental or transaction log backups are chained to their base full backup. The backups do

not expire until the last backup in the chain expires. This ensures that all incremental and transaction log

backups are recoverable until they have all expired.

Start and EndThe activity window. Specify a time of day to start the full backup, and a time of day after which backups cannot be started.

NOTE: Any backups started before the End time occurs continue until completion.

ii. Click Add backup if you want to add a differential or log backup, and then specify the following fields to schedule the backup of this protection policy:

NOTE: When you select this option, the backup chain is reset.

Create a backup every For , select Differential or Log from the drop- down list, and then specify the interval at which the backup job runs within the window that you specify. The backup interval depends on the backup interval of the full backup schedule:

If the full backup schedule is hourly or daily, the backup interval of subsequent backup levels can be between 1 and 12 hours or between 1 and 60 minutes.

If the full backup schedule is weekly or monthly, the backup interval of subsequent backup levels can be daily, between 1 and 12 hours, or between 1 and 60 minutes.

Retain forSpecify the retention period for the backup.

CAUTION: If you set a shorter retention period for a differential or log backup than for the

corresponding full backup, then data loss might occur and you might be unable to recover the

point-in-time copies.

Start and EndThe activity window. Specify a time of day to start the backup, and a time of day after which backups cannot be started.

NOTE: Any backups started before the End Time occurs continue until completion.

iii. Click Add Backup and repeat the procedure for creating full backups if you want to create additional backup copies at different intervals with different retention periods.

Within this protection policy, when a full schedule conflicts with another full backup schedule, a message appears, indicating that there is a conflict. Schedule occurrences can conflict with each other when the activity windows are identical or occur entirely within the same time range. To avoid full schedule conflicts in a policy, edit the activity windows. If you proceed with conflicting schedules, the backup of the lower priority schedule will be skipped. Schedule priority is ranked according to the following criteria:

Full schedules have a higher priority than Synthetic Full schedules. For schedules of the same backup type, the schedules that run less frequently have a higher priority than

schedules that run more frequently. For schedules with the same backup type and frequency, the schedule with the longest activity window has

the higher priority. If the activity windows are also identical, only one of these schedules will run.

NOTE: When a schedule conflict between full backups occurs, PowerProtect Data Manager retains the full

backup with the longest retention period.

d. Click Save to save the changes and return to the Objectives page.

The Objectives page updates to display the name and location of the target storage system under Primary Backup.

After completing the objective, you can change any details by clicking Edit next to the objective.

NOTE: When a new asset is added to a protection policy, the asset is not protected until the next full backup

runs, whether or not the asset is added within the backup schedule window. To immediately start protecting the

Managing Storage, Assets, and Protection 53

asset, run a manual full backup of the entire policy from the policy page or the newly added asset from the assets

page.

For Self-Service Protection:

a. Click Add under Primary Retention.

The Add Primary Retention dialog appears.

b. On the Target pane of the Add Primary Retention dialog, specify the following fields:

Storage NameSelect a backup destination from the list of existing DD systems, or select Add to add a system and complete the details in the Storage Target dialog.

Storage UnitSelect whether this protection policy should use a New storage unit on the selected DD system, or select an existing storage unit from the list. Hover over a storage unit to view the full name and statistics for available capacity and total capacity, for example, testvmpolicy-ppdm-daily-123ab (300 GB/1 TB).

When you select New, a new storage unit in the format policy name hostname unique identifier is created in the storage system upon policy completion, for example, testvmpolicy-ppdm-daily-123cd.

NOTE: The Space field indicates the total amount of space, and the percentage of available space, on the

storage system.

Network InterfaceSelect a network interface from the list, if applicable. Retention LockMove the Retention Lock slider to the right to enable retention locking for these backups.

The retention lock mode setting comes from the configuration of the selected storage unit. When you enable retention locking, the Retention Lock Mode field displays the corresponding storage unit setting.

Setting a retention lock applies to the current backup copy only, and does not impact the retention lock setting for existing backup copies.

NOTE: Primary backups are assigned a default retention lock period of 14 days. Replicated backups, however,

are not assigned a default retention lock period. If you enable Retention Lock for a replicated backup, ensure

that you set the Retain for field in the Add Replication dialog to a minimum number of 14 days so that the

replicated backup does not expire before the primary backup.

SLASelect an existing service level agreement that you want to apply to this schedule from the list, or select Add to create an SLA within the Add Backup Service Level Agreement wizard.

Add a service-level agreement provides instructions.

c. On the Retention (Self Service) pane of the Add Primary Retention dialog, change any required retention times.

By default, all backup types have the same retention time. To change the retention times for specific backup types, clear Set the same retention time for all backup types and change the Retain For field values as required.

When a different retention time for all backup types is set, you can create additional full backup patterns with different retention times. For example, you can add a full backup pattern Retain full backups created every week on the Monday and Tuesday for 2 months.

CAUTION: If you set a shorter retention period for a differential or log backup than for the

corresponding full backup, then data loss might occur and you might be unable to recover the point-in-

time copies.

d. Click Save to save the changes and return to the Objectives page.

The Objectives page updates to display the name and location of the target storage system under Primary Retention.

After completing the objective, you can change any details by clicking Edit next to the objective.

When a different retention time for all backup types is set, you can create additional full backup patterns with different retention times. For example, you can add a full backup pattern Retain full backups created every week on the Monday and Tuesday for 2 months.

10. Optionally, replicate the backups:

NOTE:

To enable replication, ensure that you add remote protection storage as the replication location. The PowerProtect Data

Manager Administration and User Guide provides detailed instructions about adding remote protection storage.

54 Managing Storage, Assets, and Protection

When creating multiple replicas for the same protection policy, it is recommended to select a different storage system

for each copy. If you select a storage unit that is the target of another objective for the same policy, the UI issues

a warning. The PowerProtect Data Manager Administration and User Guide provides information about replicating to

shared protection storage to support PowerProtect Cyber Recovery. Verify the storage targets and the use case before

you continue.

When you create a replication objective, you can specify either scheduled replication or replication after backup completion.

NOTE: For replication after backup completion, PowerProtect Data Manager 19.12 or later and application agents 19.10

or later are required. It is recommended that you update the application agents to the latest version.

For replicas of centralized backups, when you set retention periods for different backup types, any undefined types use the full backup retention period. For example, if you do not define a log backup in the primary objective, the log backup for the replication objective is also undefined. After you run a manual log backup, replicas of that log backup use the same retention period as the full backup.

a. Click Replicate next to Primary Backup or Primary Retention. An entry for Replicate is created to the right of the primary backup objective.

b. Under Replicate, click Add. The Add Replication dialog appears, with information in the left pane for each schedule that has been added for the primary backup objective of this protection policy.

NOTE: Backups for all of the listed schedules will be replicated. You cannot select individual schedules for

replication.

c. Select a storage target:

Storage NameSelect a destination from the list of protection storage. Or, select Add to add a protection storage system and complete the details in the Storage Target window.

Storage UnitSelect an existing storage unit on the protection storage system. Or, select New to automatically create a storage unit.

Network InterfaceSelect a network interface from the list, if applicable. Retention LockMove the Retention Lock slider to the right to enable retention locking for these replicas.

The retention lock mode setting comes from the configuration of the selected storage unit. When you enable retention locking, the Retention Lock Mode field displays the corresponding storage unit setting.

SLASelect an existing replication service level agreement that you want to apply to this schedule from the list. Or, select Add to create a replication SLA within the Add Service Level Agreement wizard.

The PowerProtect Data Manager Administration and User Guide provides more information about replication targets, such as SLAs.

d. Select when to replicate the backups:

Replication triggers provides more information.

To replicate after the backup finishes, move the Replicate immediately upon backup completion slider to on. For scheduled replication, move the Replicate immediately upon backup completion slider to off, and then

complete the schedule details in the Add Replication dialog.

For replication of the primary backup, the schedule frequency can be every day, week, month, or x hours.

For daily, weekly, and monthly schedules, the numeric value cannot be modified. For hourly, however, you can edit the numeric value. For example, if you set Create a Full backup every 4 hours, you can set a value of anywhere from 1 to 12 hours.

By default, all replicas of the primary backup objective inherit the retention period from the Retain For value of the synthetic full and full backup schedules.

e. To specify a different retention period for individual synthetic full and full replicas, clear Set the same retention time for all replicated copies, click Edit in the row of each schedule that you want to change, update the value in the Retain For field, and then click Save.

CAUTION: Setting a retention period for the replicas of other backup types (such as log backups,

incremental, and differential backups, where applicable) that is shorter than the retention period of the

corresponding full backup may result in being unable to recover from those replicas.

f. Click Save to save your changes and return to the Objectives page.

Managing Storage, Assets, and Protection 55

11. Optionally, to move backups from protection storage to Cloud Tier, add a Cloud objective for the primary or replication objective:

NOTE: To move a backup or replica to Cloud Tier, objectives must have a retention time of 14 days or more.

PowerProtect Data Manager also requires the discovery of protection storage with a configured Cloud unit.

a. Click Cloud Tier next to Primary Backup or Primary Retention. Or, if adding a Cloud objective for a replication objective that you have added, click Cloud Tier under Replicate. An entry for Cloud Tier is created to the right of the primary objective, or below the replication objective.

b. Under the entry for Cloud Tier, click Add. The Add Cloud Tier Backup dialog appears, with summary information for the parent objective to indicate whether you are adding this Cloud Tier objective for the primary objective or the replication objective.

c. Keep the All applicable full backups slider to the right if you want to tier the backups from all of the full primary backup or replication schedules of this policy. Otherwise, move the slider to the left and select the full schedule(s) that you want to tier.

NOTE: If the retention period of a schedule is less than the minimum 14 days required before tiering occurs, or is less

than the value in the Tier After field, you can still select this schedule for tiering. However, if you do not edit the

retention period of this schedule or its backup or replication copy to a value greater than the Tier After field before

the retention period of the copy expires, the backup or replication copy of this schedule will not be cloud tiered.

d. Complete the objective details in the Add Cloud Tier Backup dialog, and then click Save to save your changes and return to the Objectives page.

The PowerProtect Data Manager Administration and User Guide provides detailed instructions for adding a Cloud objective for a primary or replication objective.

12. Click Next. The Options page appears.

13. On the Options page, select the additional options that are required for the policy:

NOTE: If the PowerProtect Data Manager version is 19.6 but the application agent version is earlier than 19.6, then

the Backup Promotion and Exclude Simple Database options are not supported, although the options appear in the

PowerProtect Data Manager UI.

Exclude Simple DatabaseSelect this option to exclude the databases in simple recovery model from the transaction log backups.

Exclude System DatabasesSelect this option to exclude the Microsoft SQL Server system databases (including databases named master, model, and msdb) from the differential and transaction log backups.

Exclude Unprotectable DatabaseSelect this option to exclude the databases in an unprotectable state from all backups.

Backup PromotionSelect one of the following backup promotion options to use for differential and transaction log backups:

ALLEnables backup promotion. This setting is the default backup promotion setting. NONEDisables backup promotion, without displaying a warning during backups. NONE_WITH_WARNINGSDisables backup promotion, but displays a warning during a backup when a backup

promotion would normally occur. TroubleshootingSelect this option to enable the debug logs for troubleshooting purposes.

14. Click Next. The Summary page appears.

15. Review the protection policy group configuration details. You can click Edit next to any completed window's details to change any information. When completed, click Finish. An informational message appears to confirm that PowerProtect Data Manager has saved the protection policy. When a new protection policy is created, PowerProtect Data Manager performs the first full backup and subsequent backups according to the specified schedule.

16. Click OK to exit the window, or click Go to Jobs to open the Jobs window to monitor the backup of the new protection policy group.

You can monitor and view detailed information in the Jobs window for both centralized and self-service backups and restores of database application agents.

NOTE: The Cancel and Retry options are not available for self-service jobs that are created by database application

agents.

56 Managing Storage, Assets, and Protection

Results

From the PowerProtect Data Manager UI left navigation pane, you can select Jobs > Protection Jobs to view the Protection Jobs window, which displays the protection job group status. You can also click the job ID in the Protection Jobs window to view the Job ID Summary window, which displays the status of each asset job.

The status of an asset job is Skipped when the asset is present in the Microsoft SQL Server host but unavailable for backup because it is offline or in a restoring, recovery pending, or suspect state. You can see the reason for the Skipped status in the details section of the Job ID Summary window.

When all the assets in a job group are skipped, the job group status appears as Skipped in the Protection Jobs window. When some but not all assets in a job group are skipped, the job group status appears as Completed with Exceptions.

NOTE:

When at least one asset in a job group has the Failed status, the job group status appears as Failed.

When a backup fails or a backup is skipped, the backup job steps appear as canceled for the particular database. The

backup job steps are displayed on the Step Log tab in the details section of the Job ID Summary window.

Cancel a Microsoft application agent protection or restore job You can cancel an application agent protection job from the PowerProtect Data Manager UI. The job must be in a queued or running state. The protection job runs for a primary backup that is configured through an application agent protection policy.

About this task

You can perform two types of application agent job cancellations in the PowerProtect Data Manager UI:

Cancellation of a job group that includes one or more asset jobs. Cancellation of an individual asset job.

NOTE:

When a job completes before the cancel request reaches the application host, the status of the canceled job transitions to

either success or failure.

You can also cancel a queued restore job. However, you cannot cancel a restore job that is in progress. The restore job

status transitions to either success or failure based on the restore status on the application host.

You can cancel many other types of jobs, in addition to protection and restore jobs. The PowerProtect Data Manager

Administration and User Guide provides more information.

Perform the following steps to cancel an application agent protection job in the PowerProtect Data Manager UI.

Steps

1. From the PowerProtect Data Manager UI left navigation pane, select Jobs > Protection Jobs.

The Protection Jobs window opens to display a list of protection jobs and job groups.

2. In the Protection Jobs window, perform the required type of job cancellation:

To cancel a job group:

a. In the Protection Jobs window, select the required job group and click Cancel.

A job group warning prompt appears.

b. Click OK at the prompt.

You can monitor the job group cancellation in the Protection Jobs window. The job group status changes to Canceled when the cancellation of all the asset jobs is complete.

To monitor the cancellation of individual asset jobs within the job group, click the job ID in the Protection Jobs window. The Job ID Summary window opens, where you can view the status of each asset job.

To cancel an asset job:

Managing Storage, Assets, and Protection 57

a. In the Protection Jobs window, click the job ID.

The Job ID Summary window opens to display the job details of the assets in the job group.

b. In the Job ID Summary window, select the required asset job and click Cancel.

A job warning prompt appears.

c. Click OK at the prompt.

You can monitor the asset job cancellation in the Job ID Summary window. The asset job status changes to Canceled when the job cancellation is complete.

NOTE: When the cancel request for a job cannot be completed, an informational alert is displayed.

Add a service-level agreement SLA Compliance in the PowerProtect Data Manager UI enables you to add a service-level agreement (SLA) that identifies your service-level objectives (SLOs). You use the SLOs to verify that your protected assets are meeting the service-level agreements (SLAs).

About this task

NOTE: When you create an SLA for Cloud Tier, you can include only full backups in the SLA. Also, the Extended Retention

SLA applies to protection policies created in PowerProtect Data Manager 19.11 and earlier only. The Extended Retention

objective was removed in PowerProtect Data Manager 19.12. When updating to PowerProtect Data Manager 19.12 from a

previous release, any protection policies created in the earlier release with the Extended Retention SLA will continue to be

supported, however, you will not be able to edit the Extended Retention SLA in these policies.

In the SLA Compliance window, you can export compliance data by using the Export All functionality.

Steps

1. From the PowerProtect Data Manager UI, select Protection > SLA Compliance.

The SLA Compliance window appears.

2. Click Add or, if the assets that you want to apply the SLA to are listed, select these assets and then click Add.

The Add Service Level Agreement wizard appears.

3. Select the type of SLA that you want to add, and then click Next. Policy. If you choose this type, go to step 4. Backup. If you choose this type, go to step 5. Replication. If you choose this type, go to step 6. Cloud Tier. If you choose this type, go to step 7.

You can select only one type of Service Level Agreement.

4. If you selected Policy, specify the following fields regarding the purpose of the new Policy SLA:

a. The SLA Name. b. If applicable, select Minimum Copies, and specify the number of Backup, Replication, and Cloud Tier copies. c. If applicable, select Maximum Copies, and specify the number of Backup, Replication, and Cloud Tier copies. d. If applicable, select Available Location and select the applicable locations. To add a location, click Add Location.

Options include the following: InInclude locations of all copies in the SLO locations. Selecting this option does not require every SLO location to

have a copy. Must InInclude locations of all copies in the SLO locations. Selecting this option requires every SLO location to

have at least one copy. ExcludeLocations of all copies must be non-SLO locations.

e. If applicable, select Allowed in Cloud through Cloud Tier/Cloud DR. f. Click Finish, and then go to step 9.

5. If you selected Backup, specify the following fields regarding the purpose of the new Backup SLA:

a. The SLA Name.

58 Managing Storage, Assets, and Protection

b. If applicable, select Recovery Point Objective required (RPO), and then set the duration. The purpose of an RPO is business continuity planning, and indicates the maximum targeted period in which data (transactions) might be lost from an IT service due to a major incident.

NOTE: You can select only Recovery Point Objective required to configure as an independent objective in the

SLA, or select both Recovery Point Objective required and Compliance Window for copy type. If you select

both, the RPO setting must be one of the following:

Greater than 24 hours or more than the Compliance window duration, in which case RPO validation occurs

independent of the Compliance Window.

Less than or equal to the Compliance Window duration, in which case RPO validation occurs within the

Compliance Window.

c. If applicable, select Compliance Window for copy type, and then select a schedule level from the list, for example, All, Full, Cumulative, and set the duration. Duration indicates the amount of time necessary to create the backup copy. Ensure that the Start Time and End Time of backup copy creation falls within the Compliance Window duration specified.

This window specifies the time during which you expect the specified activity to take place. Any specified activity that occurs outside of this Start Time and End Time triggers an alert.

d. If applicable, select the Verify expired copies are deleted option.

Verify expired copies are deleted is a compliance check to see if PowerProtect Data Manager is deleting expired copies. This option is disabled by default.

e. If applicable, select Retention Time Objective, and specify the number of Days, Months, Weeks, or Years.

NOTE: For compliance validation to pass, the value set for the Retention Time Objective must match the lowest

retention value set for the backup levels of this policy's target objectives. For example, if you set the synthetic full

backup Retain For to 30 days but set the full backup Retain For to 60 days, the Retention Time Objective must be

set to the lower value, in this case, 30 days.

f. If applicable, select the Verify Retention Lock is enabled for all copies option. This option is disabled by default. g. Click Finish, and go to step 9.

The SLA Compliance window appears with the new SLA.

6. If you selected Replication, specify the following fields regarding the purpose of the new Replication SLA:

a. The SLA Name. b. If applicable, select the Compliance Window, and specify the Start Time and End Time.

This window specifies the times that are permissible and during which you can expect the specified activity to occur. Any specified activity that occurs outside of this start time and end time triggers an alert.

c. If applicable, select the Verify expired copies are deleted option.

Verify expired copies are deleted is a compliance check to see if PowerProtect Data Manager is deleting expired copies. This option is disabled by default.

d. If applicable, select Retention Time Objective, and specify the number of Days, Months, Weeks, or Years.

NOTE: For compliance validation to pass, the value set for the Retention Time Objective must match the lowest

retention value set for the backup levels of this policy's target objectives.

e. If applicable, select the Verify Retention Lock is enabled for all copies option. This option is disabled by default. f. Click Finish, and go to step 9.

The SLA Compliance window appears with the newly added SLA.

7. If you selected Cloud Tier type SLA, specify the following fields regarding the purpose of the new Cloud Tier SLA:

a. The SLA Name. b. If applicable, select the Verify expired copies are deleted option.

This option is a compliance check to determine if PowerProtect Data Manager is deleting expired copies. This option is disabled by default.

c. If applicable, select Retention Time Objective and specify the number of Days, Months, Weeks, or Years.

NOTE: For compliance validation to pass, the value set for the Retention Time Objective must match the lowest

retention value set for the backup levels of this policy's target objectives.

d. If applicable, select the Verify Retention Lock is enabled for all copies option. This option is disabled by default. e. Click Finish.

8. If the SLA has not already been applied to a protection policy:

Managing Storage, Assets, and Protection 59

a. Go to Protection > Protection Policies. b. Select the policy, and then click Edit.

9. In the Objectives row of the Summary window, click Edit.

10. Do one of the following, and then click Next: Select the added Policy SLA from the Set Policy Level SLA list. Create and add the SLA policy from the Set Policy Level SLA list. The Summary window appears.

11. Click Finish. An informational message appears to confirm that PowerProtect Data Manager has saved the protection policy.

12. Click Go to Jobs to open the Jobs window to monitor the backup and compliance results, or click OK to exit.

NOTE: Compliance checks occur automatically every day at 2 a.m. Coordinated Universal Time (UTC). If any objectives

are out of compliance, an alert is generated at 2 a.m. UTC. The Validate job in the System Jobs window indicates the

results of the daily compliance check.

For a backup SLA with a required RPO setting that is less than 24 hours, PowerProtect Data Manager performs real-time compliance checks. If you selected Compliance Window for copy type and set the backup level to All, the real-time compliance check occurs every 15 minutes only within the compliance window. If the backup level is not All, or if a compliance window is not specified, the real-time compliance check occurs every 15 minutes without stop.

NOTE: If the backup SLA has a required RPO setting of 24 hours or greater, compliance checks occur daily at 2 a.m.

UTC. Real-time compliance checks do not occur for backup SLAs with an RPO setting of 24 hours or greater.

Real-time compliance-check behavior

If the interval of time between the most recent backup of the asset and the compliance check is greater than the RPO requirement, then an alert indicates the RPO of the asset is out of compliance. This alert is generated once within an RPO period. If the same backup copy is missed when the next compliance check occurs, no further alerts are generated.

If the interval of time between the most recent backup of the asset and the compliance check is less than the RPO requirement, the RPO of the asset is in compliance.

If multiple assets in a policy are out of compliance at the same time when a compliance check occurs, a single alert is generated and includes information for all assets that are out of compliance in the policy. In the Alerts window, the asset count next to the alert summary indicates the number of assets that are out of compliance in the policy.

13. In the Jobs window, click next to an entry to view details on the SLA Compliance result.

Extended retention (for protection policies created in PowerProtect Data Manager 19.11 and earlier)

NOTE: This section applies to protection policies created in PowerProtect Data Manager 19.11 and earlier only. For

protection policies created in PowerProtect Data Manager 19.12, instead of using the Extend Retention objective to

extend the retention period of certain full copies, you can now add multiple full schedules for primary backup and replication

objectives. When updating to PowerProtect Data Manager 19.12 from a previous release, any protection policies created

in the earlier release with the Extend Retention objective will continue to be supported, however, you will not be able

to edit existing extended retention objectives, or add new extended retention objectives, in these policies. The Knowledge

Base article 000204454 at https://www.dell.com/support/ provides detailed information about specific Extend Retention

objective migration scenarios when updating to PowerProtect Data Manager 19.12.

For protection policies created in PowerProtect Data Manager 19.11 and earlier, the Extend Retention objective allows you to extend the retention period for the primary backup copy for long-term retention. For example, your regular schedule for daily backups can use a retention period of 30 days, but you can extend the retention period to keep the full backups taken on Mondays for 10 weeks.

Both centralized and self-service protection policies support weekly, monthly, and yearly recurrence schedules to meet the demands of your compliance objectives. For example, you can retain the last full backup containing the last transaction of a fiscal year for 10 years. When you extend the retention period of a backup in a protection policy, you can retain scheduled full backups with a repeating pattern for a specified amount of time.

For example:

60 Managing Storage, Assets, and Protection

Retain full yearly backups that are set to repeat on the first day of January for 5 years. Retain full monthly backups that are set to repeat on the last day of every month for 1 year. Retain full yearly backups that are set to repeat on the third Monday of December for 7 years.

Preferred alternatives

When you define an extended retention objective for a protection policy, you define a set of matching criteria that select preferred backups to retain. If the matching criteria do not identify a matching backup, PowerProtect Data Manager automatically retains the preferred alternative backup according to one of the following methods:

Look-backRetain the last available full backup that was taken before the matching criteria. Look-forwardRetain the next available full backup that was taken after the matching criteria.

For example, consider a situation where you configured a protection policy to retain the daily backup for the last day of the month to extended retention. However, a network issue caused that backup to fail. In this case, look-back matching retains the backup that was taken the previous day, while look-forward matching retains the backup that was taken the following day.

By default, PowerProtect Data Manager uses look-back matching to select the preferred alternative backup. A grace period defines how far PowerProtect Data Manager can look in the configured direction for an alternative backup. If PowerProtect Data Manager cannot find an alternative backup within the grace period, extended retention fails.

You can use the REST API to change the matching method or the grace period for look-forward matching. The PowerProtect Data Manager Public REST API documentation provides instructions. If there are no available backups for the defined matching period, you can change the matching method to a different backup.

For look-forward matching, the next available backup can be a manual backup or the next scheduled backup.

Selecting backups by weekday

This section applies to centralized protection policies. Self-service protection policies have no primary backup objective configuration.

When you configure extended retention to match backups by weekday, PowerProtect Data Manager may identify a backup that was taken on one weekday as being taken on a different weekday. This behavior happens where the backup window does not align with the start of the day. PowerProtect Data Manager identifies backups according to the day on which the corresponding backup window started, rather than the start of the backup itself.

For example, consider a backup schedule with an 8:00 p.m. to 6:00 a.m. backup window:

Backups that start at 12:00 a.m. on Sunday and end at 6:00 a.m. on Sunday are identified as Saturday backups, since the backup window started on Saturday.

Backups that start at 8:01 p.m. on Sunday and end at 12:00 a.m. on Monday are identified as Sunday backups, since the backup window started on Sunday.

Backups that start at 12:00 a.m. on Monday and end at 6:00 a.m. on Monday are identified as Sunday backups, since the backup window started on Sunday.

In this example, when you select Sunday backups for extended retention, PowerProtect Data Manager does not retain backups that were taken between 12:00 a.m. and 8:00 p.m. This behavior happens even though the backups occurred on Sunday. Instead, PowerProtect Data Manager selects the first available backup that started after 8:00 p.m. on Sunday for extended retention.

If no backups were created between 8:01 p.m. on Sunday and 6:00 a.m. on Monday, PowerProtect Data Manager retains the next alternative to extended retention. In this example, the alternative was taken after 6:00 a.m. on Monday.

Extended retention backup behavior

When PowerProtect Data Manager identifies a matching backup, automatic extended retention creates a job at the beginning of the backup window for the primary objective. This job remains queued until the end of the backup window and then starts.

The following examples describe the behavior of backups with extended retention for centralized and self-service protection.

Managing Storage, Assets, and Protection 61

Centralized protection

For an hourly primary backup schedule that starts on Sunday at 8:00 p.m. and ends on Monday at 6:00 p.m. with a weekly extended retention objective that is set to repeat every Sunday, PowerProtect Data Manager selects the first available backup starting after 8:00 p.m. on Sunday for long-term retention.

The following diagram illustrates the behavior of backups with extended retention for a configured protection policy. In this example, full daily backups starting at 10:00 p.m. and ending at 6:00 a.m. are kept for 1 week. Full weekly backups are set to repeat every Sunday and are kept for 1 month.

Figure 2. Extend retention backup behavior

Self-service protection

For self-service backups, PowerProtect Data Manager uses a default backup window of 24 hours. For a backup schedule that starts on Sunday at 12:00 p.m and ends on Monday at 12:00 p.m. with a weekly extended retention objective that is set to repeat every Sunday, PowerProtect Data Manager selects the first available backup that is taken between 12:00 p.m. on Sunday and 12:00 p.m. on Monday for long-term retention.

Replication of extended retention backups

You can change the retention time of selected full primary backups in a replication objective by adding a replication objective to the extended retention backup. The rules in the extended retention objective define the selected full primary backups. Review the following information about replication of extended retention backups.

Before you configure replication of extended retention backups, create a replication objective for the primary backup. Configure the replication objective of the extended retention and match this objective with one of the existing replication

objectives based on the primary backup. Any changes to a new or existing storage unit in the extended retention replication objective or the replication objective of the primary backup is applied to both replication objectives.

The replication objective of extended retention backups only updates the retention time of replicated backup copies and does not create any new backup copies in the replication storage.

Edit the retention period for backup copies You can edit the retention period of one or more backup copies to extend or shorten the amount of time that backups are retained.

About this task

You can edit the retention period for all asset types and backup types.

Steps

1. Select Infrastructure > Assets.

62 Managing Storage, Assets, and Protection

2. From the Assets window, select the tab for the asset type for which you want to edit the retention period. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more backup copies from the table, and click Edit Retention.

6. Select one of the following options: To select a calendar date as the expiration date for backups, select Retention Date. To define a fixed retention period in days, weeks, months, or years after the backup is performed, select Retention

Value. For example, you can specify that backups expire after 6 months.

NOTE: When you edit the retention period for copies that are retention locked, you can only extend the retention

period.

7. When satisfied with the changes, click Save. The asset is displayed in the list with the changes. The Retention column displays both the original and new retention periods, and indicates whether the retention period has been extended or shortened.

Delete backup copies In addition to deleting backups after the retention period expires, PowerProtect Data Manager enables you to manually delete backup copies from protection storage.

About this task

If you no longer require a backup copy and the retention lock is not enabled, you can delete backup copies prior to their expiration date.

Starting with PowerProtect Data Manager version 19.6, you can perform a backup copy deletion that deletes only a specified part of a backup copy chain, without impacting the ability to restore other backup copies in the chain. When you select a specific backup copy for deletion, only that backup copy and the backup copies that depend on the selected backup copy are deleted:

When you select to delete a full backup copy, any other backup copies in the chain that depend on the full backup copy are also deleted.

When you select to delete a differential backup copy, only the differential backup copy is deleted because there are no other dependent backup copies. The whole backup chain is not deleted.

When you select to delete a log backup copy, any other log backup copies that depend on the selected log backup copy are also deleted. The whole backup chain is not deleted.

When you select to delete all log backup copies, the full and differential backup copies are automatically excluded from deletion.

Regarding expired copy deletion for a backup chain, the full backup expires last. The differential and log backups that expire earlier than the full backup can be deleted when their retention time expires:

The full backup expires only when every other backup in the chain has expired. A differential backup expires when its retention time expires. A log backup expires only when all the log backups that depend on it have expired.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more copies from the table that you want to delete from the DD system, and then click Delete.

A preview window opens and displays the selected backup copies and all the backup copies that depend on the selected backup copies.

Managing Storage, Assets, and Protection 63

NOTE: If you delete a backup copy, PowerProtect Data Manager deletes the specified backup copy and all backup

copies that depend on the specified backup copy.

6. For all asset types, you can choose to keep the latest backup copies or delete them. By default, PowerProtect Data Manager keeps the latest backup copies. To delete the latest backup copies, clear the check box next to Include latest copies.

7. To delete the backup copies, in the preview window, click Delete.

NOTE: The delete operation may take a few minutes and cannot be undone.

An informational dialog box opens to confirm the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

When the job completes, the task summary provides details of each deleted backup copy, including the time that each copy was created, the backup level, and the retention time. The time of copy creation and the retention time are shown in UTC.

An audit log is also generated and provides details of each deleted backup copy, including the time that each copy was created, the backup level, and the retention time. The time of copy creation and the retention time are shown in UTC. Go to Alerts > Audit Logs to view the audit log.

8. Verify that the copies are deleted successfully from protection storage. If the deletion is successful, the deleted copies no longer appear in the table.

Retry a failed backup copy deletion

If a backup copy is not deleted successfully, you can manually retry the operation.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more backup copies with the Deletion Failed status from the table, and then click Delete.

You can also filter and sort the list of backup copies by status in the Copy Status column.

The system displays a warning to confirm that you want to delete the selected backup copies.

6. Click OK. An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

7. Verify that the copies are successfully deleted from protection storage. If the deletion is successful, the deleted copies no longer appear in the table.

Export data for deleted backup copies

This option enables you to export results of deleted backup copies to a .csv file so that you can download an Excel file of the data.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to export results of deleted backup copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select one or more protected assets from the table, and then select More Actions > Export Deleted Copies.

If you do not select an asset, PowerProtect Data Manager exports the data for deleted backup copies for all assets for the specific asset type.

4. Specify the following fields for the export:

a. Time Range

The default is Last 24 Hours.

64 Managing Storage, Assets, and Protection

b. Copy Status

In order to export data for deleted backup copies, the backup copies must be in one of the following states:

DeletedThe copy is deleted successfully from protection storage, and, if applicable, the agent catalog is deleted successfully from the agent host.

DeletingCopy deletion is in progress. Deletion FailedCopy deletion from protection storage is unsuccessful.

NOTE: You cannot export data for backup copies that are in an Available state.

5. Click Download. If applicable, the navigation window appears for you to select the location to save the .csv file.

6. Save the .csv file in the desired location and click Save.

Remove backup copies from the PowerProtect Data Manager database

This option enables you to delete the backup copy records from the PowerProtect Data Manager database, but keep the backup copies in protection storage.

About this task

For backup copies that could not be deleted from protection storage, you can remove the backup copies from the PowerProtect Data Manager database. Removing the backup copies from PowerProtect Data Manager does not delete the copies in protection storage.

Steps

1. From the PowerProtect Data Manager UI, select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more backup copies with the Deletion Failed status from the table, and then click Remove from PowerProtect. The system displays a warning to confirm that you want to delete the selected backup copies.

6. Click OK. An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

7. Verify that the copies are deleted from the PowerProtect Data Manager database. If the deletion is successful, the deleted copies no longer appear in the table. The backup copies remain in protection storage.

Enable the Microsoft application agent after Internet Protocol change PowerProtect Data Manager 19.12 introduced support for IPv6. When you modify the configured Internet Protocols after updating to or installing PowerProtect Data Manager 19.12 on the Microsoft SQL Server host, the Microsoft application agent must be enabled for backup and restore operations.

About this task

Supported Internet Protocol versions provides details about the IPv4 and IPv6 addresses that PowerProtect Data Manager and its components support in specific configurations.

You must perform the required procedure to enable the Microsoft application agent operations in the following cases:

Managing Storage, Assets, and Protection 65

With Microsoft application agent 19.11 or earlier on the Microsoft SQL Server host, you registered the host to PowerProtect Data Manager. Then after updating to PowerProtect Data Manager 19.12, you want to use IPv6 in either a dual-stack or IPv6 configuration.

With Microsoft application agent 19.12 newly installed on the Microsoft SQL Server host, you registered the host to PowerProtect Data Manager. Then you want to change the network configuration to add or remove either IPv4 or IPv6.

In these cases, perform the following procedure to enable the Microsoft application agent backup and restore operations.

Steps

1. Decommission the Microsoft SQL Server host:

a. Remove the assets from the protection policies. The PowerProtect Data Manager Administration and User Guide provides details on how to remove assets from PowerProtect Data Manager.

b. Delete the Microsoft SQL Server host according to Delete an asset source. This procedure unregisters the host from PowerProtect Data Manager and removes the host assets after all the asset copies have expired.

2. Make the network configuration changes on the Microsoft SQL Server host:

a. Enable the IPv4 or IPv6 protocol in the network settings, and assign the required static address. b. To configure a pure IPv4 or pure IPv6 environment, disable the required protocol in the network settings.

3. Run the installation wizard and select the Change option to register the Microsoft SQL Server host with the same PowerProtect Data Manager server.

4. Add the required assets back into the protection policy.

Enable the Microsoft application agent after hostname change After the hostname of the Microsoft application agent host is changed, you must update the lockbox setting for the protection policy and add assets back to the protection policies.

About this task

Perform the following steps to enable the Microsoft application agent operations after the hostname is changed.

Steps

1. From the C:\Program Files\DPSAPPS\AgentService directory:

a. Unregister the Microsoft application agent from PowerProtect Data Manager by running unregister.bat.

b. Register the Microsoft application agent with PowerProtect Data Manager by running register.bat.

2. Delete the existing agents.clb* lockbox files in the C:\Program Files\DPSAPPS\common\lockbox directory.

NOTE: If the Microsoft application agent is installed to a non-default path, delete the agents.clb* files in the

lockbox subdirectory of the installation directory.

3. In the PowerProtect Data Manager UI, configure the lockbox:

a. In the left navigation pane, select Protection > Protection Policies. b. On the Protection Policies page, select the applicable protection policy in the list and click Set Lockbox.

4. From the protection policy, remove any assets that were protected under the old hostname.

NOTE: Until steps 4 through 6 are followed, any asset that was protected under the old hostname is no longer

protected under the new hostname.

5. Run a manual discovery.

6. Add any asset now in an available state back to the protection policy.

66 Managing Storage, Assets, and Protection

Manage the PowerProtect agent service The PowerProtect agent service provides important functionality for the application agent operations with the PowerProtect Data Manager.

Review the following topics to ensure that you enable and manage the PowerProtect agent service functionality as required for application agent operations.

About the PowerProtect agent service

The PowerProtect agent service is a REST API based service that is installed by the application agent on the application host. The agent service provides services and APIs for discovery, protection, restore, instant access, and other related operations. The PowerProtect Data Manager uses the agent service to provide integrated data protection for the application assets.

This section uses to represent the PowerProtect agent service installation directory. By default, the agent service installation location is C:\Program Files\DPSAPPS\AgentService on Windows and /opt/dpsapps/agentsvc on Linux. All files that are referenced in this section are the relative paths to the agent service installation location.

The PowerProtect agent service performs the following operations:

Addon detectionAn addon integrates the application agent into the agent service. The agent service automatically detects the addons on the system for each application asset type and notifies the PowerProtect Data Manager. While multiple addons can operate with different asset types, only one agent service runs on the application host. Specific asset types can coexist on the same application host.

DiscoveryThe agent service discovers both stand-alone and clustered database servers (application systems), databases and file systems (assets), and their backup copies on the application agent host. After the initial discovery, when the agent service discovers any new application systems, assets, or copies, the agent service notifies the PowerProtect Data Manager.

Self-service configurationThe agent service can configure the application agent for self-service operations by using information that is provided by the PowerProtect Data Manager. When you add an asset to a protection policy for self-service or centralized protection, or modify the protection policy, including changing the DD Boost credentials, the PowerProtect Data Manager automatically pushes the protection configuration to the agents.

NOTE: If you change the DD Boost credentials to include \ in the password, the protection policy configuration will not

be pushed to the agents unless you also select the protection policy from the Protection Policies window, and then

click Set LockBox.

Centralized backupsThe agent service performs the centralized backups as requested by the PowerProtect Data Manager.

Centralized restoresThe agent service performs the centralized restores as requested by the PowerProtect Data Manager.

NOTE: In the current release, the centralized restores are only available for the File System agent, Microsoft SQL

Server agent, and Storage Direct agent.

Backup deletion and catalog cleanupThe PowerProtect Data Manager deletes the backup files directly from the protection storage when a backup expires or an explicit delete request is received and no dependent (incremental or log) backups exist. The PowerProtect Data Manager goes through the agent service to delete the catalog entries from the database vendor's catalog and the agent's local datastore.

NOTE: Deletion of any backup copies manually or through the command line is not recommended. PowerProtect Data

Manager deletes all the expired copies as needed.

The agent service is started during the agent installation by the installer. The agent service runs in the background as a service and you do not interact with it directly.

The config.yml file contains the configuration information for the agent service, including several parameter settings that you can change within the file. The config.yml file is located in the directory.

The agent service periodically starts subprocesses to perform the discovery jobs. You can see the type and frequency of these jobs in the jobs: section of the config.yml file. The job interval unit is minutes.

The agent service maintains a datastore in the /dbs/v1 directory, which contains information about the application system, assets, and backups discovered on the system. The size of the datastore files depends on the number of applications and copies on the host. The agent service periodically creates a backup of its datastore in the /dbs/v1/backups directory, as used to recover the datastore if this datastore is lost.

Managing Storage, Assets, and Protection 67

NOTE: The size of each datastore backup is the same as the datastore itself. By default, a backup is created every hour.

To save space on the file system, you can reduce this datastore backup frequency for large datastores. By default, the

datastore backup is retained for one week. You can change the datastore backup frequency, retention period, and backup

location in the config.yml file.

Start, stop, or obtain the status of the PowerProtect agent service

The PowerProtect agent service is started during the agent installation by the installer. If needed, you can use the appropriate procedure to start, stop, or obtain the status of the agent service.

On Windows, you can start, stop, or obtain the status of the PowerProtect agent service from the Services Manager, similar to other Windows services. The name of the service in the Services Manager is PowerProtect Agent Service.

Troubleshooting PowerProtect agent service installations

A PowerProtect agent service installation might fail with the following error message:

Service 'PowerProtect Agent Service' (AgentService) could not be installed. Verify that you have sufficient privileges to install system services.

Possible causes of the installation failure are as follows:

The installation was attempted on a passive node of a Failover Cluster Instance (FCI). The installation was canceled and a rollback left some stale entries of PowerProtect agent services.

As a workaround, clean up the PowerProtect agent service entries, and retry the installation.

Troubleshooting PowerProtect agent service operations

To troubleshoot agent service operations, you can check the agent service log file OpAgentSvc- .log, which is created in \logs on Windows and /logs on AIX or Linux. To modify the log level and retention of temporary files, you can modify specific parameter settings in the config.yml file.

About this task

To modify the log level and retention of temporary files, you can perform the following steps.

Steps

1. Stop the agent service by using the appropriate procedure from the preceding topic.

2. Open the config.yml file in an editor.

3. Modify the log-level settings in the following parameters, as required:

NOTE: These parameters are listed in order of decreasing number of messages in the debug information output. The

default log-level is INFO.

DEBUG INFO WARNING ERROR CRITICAL

4. To retain the temporary files, set the keepTempFiles parameter to True in the config.yml file.

NOTE: The agent service and application agent communicate through the temporary files, which are typically deleted

after use but can be useful for troubleshooting purposes. Do not leave the keepTempFiles parameter set to True

permanently, or the temporary files can use excessive space on the file system.

5. Start the agent service by using the appropriate procedure from the preceding topic.

68 Managing Storage, Assets, and Protection

Register the PowerProtect agent service to a different server address on Windows

The PowerProtect agent service is registered to a particular PowerProtect Data Manager server during the agent installation by the installer. If needed, you can register the agent service to a different PowerProtect Data Manager server address. If there are multiple agents installed on a host, all agents will be re-registered to the new PowerProtect server.

The agent service can only be registered to a single PowerProtect Data Manager server.

Before you register the agent service to a new server, ensure that you complete the following steps:

1. Stop the agent service as described in a preceding topic. 2. Delete the \ssl folder and

\dbs\v1\objects.db.

On Windows, perform the following steps to register the agent service to a different server address.

1. To unregister from the current PowerProtect Data Manager server, go to the C:\Program Files\DPSAPPS\AgentService directory and run unregister.bat.

2. In the dbs\v1 directory, rename the copies.db file to copies-backup.db.

3. To register the agent service to the different server address, run register.bat and provide the new PowerProtect Data Manager server IP address or hostname.

NOTE: If the host is already decommissioned from PowerProtect Data Manager using asset source deletion and you

want to register the host again to the same or different PowerProtect Data Manager, then go to the Add/Remove

Programs window and use the change option in the installer to register again. In this case, do not use register.bat.

4. Verify the agent registration status:

a. In the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

b. In the Application Agents window, select the entry that contains the agent hostname and ensure that the status is Registered.

5. To perform asset discovery for the agent:

a. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources.

The Asset Sources window appears.

b. Select the tab for your application agent or file system host. c. Select the agent hostname and click Discover. At the confirmation prompt, click Yes.

When you select Infrastructure > Assets, the Assets window displays the discovered assets.

Recovering the PowerProtect agent service from a disaster

You can perform self-service restores of application assets by using a file system or application agent, regardless of the state of the agent service or PowerProtect Data Manager. The information in this section describes how to bring the agent service to an operational state to continue if a disaster occurs and the agent service datastore is lost.

The agent service periodically creates a backup of its datastore in the /dbs/v1/backups repository. If all of these backups are lost, the agent service can still start. The agent service discovers all the application systems, assets, and backup copies on the system again, and notifies PowerProtect Data Manager. Depending on when the failure occurred, the agent service might not be able to find older backup copies for some asset types. As a result, the centralized deletion operations might fail when cleaning up the database vendor catalog or removing older backups that are taken before the asset is added to PowerProtect Data Manager.

By default, the agent service backs up consistent copies of its datastore files to the local disk every hour and keeps the copies for 7 days. Each time the agent service backs up the contents of the datastore, it creates a subdirectory under the /dbs/v1/backups repository. The subdirectories are named after the time the operation occurred, in the format YYYY-MM-DD_HH-MM-SS_epochTime.

By default, the datastore repository is on the local disk. To ensure that the agent service datastore and its local backups are not lost, it is recommended that you back up the datastore through file system backups. You can also change the datastore backup location to a different location that is not local to the system. To change the datastore backup location, update the values in the config.yml file.

Managing Storage, Assets, and Protection 69

Restore the PowerProtect Data Manager agent service datastore

Prerequisites

NOTE: Ensure that the agent service is powered off. Do not start the agent service until disaster recovery is complete.

About this task

You can restore the datastore from the datastore backup repository. If the repository is no longer on the local disk, restore the datastore from file system backups first.

To restore the datastore from a backup in the datastore backup repository, complete the following steps:

Steps

1. Move the files in the /dbs/v1 directory to a location for safe keeping.

NOTE: Do not move or delete any /dbs/v1 subdirectories.

2. Select the most recent datastore backup.

The directories in the datastore backup repository are named after the time the backup was created.

3. Copy the contents of the datastore backup directory to the /dbs/v1 directory. After the copy operation is complete, the /dbs/v1 directory should contain the following files: copies.db objects.db resources.db sessions.db

4. Start the agent service.

Manage the cloud tier operations with PowerProtect Data Manager The PowerProtect Data Manager cloud tier feature works in tandem with the Cloud Tier feature to move PowerProtect Data Manager backups from DD systems to the cloud. This provides long-term storage of PowerProtect Data Manager backups by seamlessly and securely tiering data to the cloud.

From the PowerProtect Data Manager UI, you configure cloud tier to move PowerProtect Data Manager backups from DD to the cloud, and you can perform seamless recovery of these backups.

Cloud storage units must be pre-configured on the DD system before they are configured for cloud tier in the PowerProtect Data Manager UI. The DDOS Administration Guide provides more information.

Add a cloud tier schedule to a protection policy

You can add a cloud tier schedule to a protection policy for Microsoft SQL Server centralized and self-service backups to cloud tier.

Prerequisites

Ensure that a DD system is set up for cloud tiering.

About this task

Both Microsoft SQL Server centralized and self-service protection policies support cloud tiering. You can create the cloud tier schedule from primary and replication objectives. Schedules must have a retention time of 14 days or more.

Cloud tiering happens at 00:00 UTC each day. Depending on your time zone, this time may be within business hours and thus cloud tiering may impact available network bandwidth.

70 Managing Storage, Assets, and Protection

Steps

1. Log in to PowerProtect Data Manager with administrator credentials.

2. From the PowerProtect Data Manager UI, select Protection > Protection Policies, and then click Add.

The Add Policy wizard appears.

3. On the Type page, enter a name and description, select Microsoft SQL as the type of system to back up, and click Next.

4. On the Purpose page, select from the available options to indicate the purpose of the new protection policy, and then click Next.

5. On the Assets page, select the assets to be protected with this policy, and then click Next.

6. On the Objectives page, click Add under Primary Backup if the primary backup schedule is not already created, and fill out the fields in the Target and Schedules panes on the Add Primary Backup dialog.

NOTE: There is no minimum recurrence required for the cloud objective. However, the cloud tier schedule requires a

minimum retention period of 14 days in the Retain for field.

7. Click Cloud Tier next to Primary Backup or, if adding a cloud objective for a replication schedule that you have added, click Cloud Tier under Replicate. An entry for Cloud Tier is created to the right of the primary backup schedule, or below the replication schedule.

8. Under the entry for Cloud Tier, click Add. The Add Cloud Tier Backup dialog appears, with summary schedule information for the parent node. This information indicates whether you are adding this cloud tier objective for the primary backup schedule or the replication schedule.

9. In the Add Cloud Tier Backup dialog box, set the following parameters and then click Save:

Select the appropriate storage unit from the Cloud Target list. For Tier After, set a time of 14 days or more.

The protection policy schedule is now enabled with cloud tiering.

10. Click Next to proceed with the remaining pages of the Add Policy wizard, verify the information, and then click Finish. A new job is created, which you can view under the Jobs tab after the job completes.

Tier the PowerProtect Data Manager backups from DD to the cloud

Once you add the Microsoft SQL Server database assets to a protection policy that contains a cloud tier objective, you can perform tiering of these assets by using the PowerProtect Data Manager UI.

Steps

1. Log in to PowerProtect Data Manager with administrator credentials.

2. Select Infrastructure > Assets > SQL.

3. On the Type Assets page, select the asset, and then click View Copies.

4. Select the DD system where the PowerProtect Data Manager backups for Microsoft SQL Server reside, and then select Full protection copy which is older than 2 weeks.

5. Click Tier to tier the backups.

A new job is created, which you can view under the Jobs tab after the job completes. When you monitor the cloud tier progress of backup copies for the asset job, the status remains in the running state until the data movement occurs from the DD system.

6. Log in to the DD system, and obtain the storage unit details by running the command data-movement policy show. For example:

# data-movement policy show

Mtree Target(Tier/Unit Name) Policy Value ----------------------------------------- ---------------------- ----------- ------- /data/col1/rman137-blrv136g140-840dd Cloud/ecs-unit app-managed enabled /data/col1/rman134-copy-blrv136g138-61900 Cloud/ecs-unit app-managed enabled /data/col1/rman-11-blrv136h010-7014f Cloud/ecs-unit app-managed enabled

7. Run the data-movement start mtrees command for the particular MTree. For example:

# data-movement start mtrees /data/col1/rman137-blrv136g140-840dd

Managing Storage, Assets, and Protection 71

After the successful data movement to the cloud, the cloud tier monitoring job completes. After some time, on the Assets > View Copies page, the Location field of the protection backups changes to Cloud.

The DDOS Administration Guide provides more details about cloud tier data movement.

Restore the cloud tier backups to DD

Before you run a self-service restore of a backup that was performed through a centralized policy and moved to the cloud tier, recall the backup to the active tier from PowerProtect Data Manager.

NOTE: Only Elastic Cloud Storage (ECS) supports a direct restore from the cloud tier.

Recall and re-tier the cloud tier backup

You can manually recall the backup from the cloud tier and restore the local copy:

NOTE: When a backup is recalled from the cloud tier to the active tier, the copy is removed from the cloud tier.

1. In the PowerProtect Data Manager UI, go to Infrastructure > Assets and select the SQL tab. 2. Select the required asset, and then click View Copies. 3. Select the backup in the cloud, click Recall, and then specify how long to keep the copy on the active tier.

A job is created to recall the backup copy from the cloud tier for the selected asset. The copy moves from the cloud tier, and the status changes from Cloud to Local_Recalled. Then you can perform the restore from the Microsoft SQL Server host.

4. To re-tier the recalled copy, select the recalled copy and click Re-tier. 5. To change the retention period for the recalled copy, select the recalled copy and click Edit Recall Retention.

72 Managing Storage, Assets, and Protection

Performing Self-Service Backups of Microsoft SQL Server Databases

Topics:

Performing self-service Microsoft SQL Server database backups Overview of Application Direct with Microsoft SQL Server backups Best practices to back up Microsoft SQL Server with Application Direct Naming conventions for backups with Application Direct Circumstances that promote Microsoft SQL Server backups to level full Scheduling backup jobs Performing manual backups

Performing self-service Microsoft SQL Server database backups To enable self-service protection, when you create the Microsoft SQL Server protection policy, select Self-Service Protection.

When performing a self-service stand-alone backup of an AAG asset, the backups appear under the AAG asset.

The following topics provide instructions on how to perform a self-service Microsoft SQL Server backup.

Overview of Application Direct with Microsoft SQL Server backups The Microsoft application agent for Application Direct with Microsoft SQL Server module integrates with the Microsoft SQL Server Virtual Device Interface (VDI).

The interface enables you to configure the module by using a SQL Server Management Studio plug-in.

The plug-in is similar to the Microsoft SQL Server native backup and restore graphical user interface (GUI). Database administrators (DBAs) can use the Microsoft native tools to back up and restore the Microsoft SQL Server data.

NOTE: Self-service backups and restores are backups and restores that you perform through the SQL Server Management

Studio (SSMS), Transact-SQL (T-SQL) scripting, or the Microsoft application agent command-line interface.

For assets with single and multiple stripes, you might see a difference in the backup time reported in the Microsoft application agent SSMS UI and the msdb of Microsoft SQL Server. The backup time difference is due to the Microsoft application agent threading algorithm for striped backups:

For a single stripe backup, the backup time reported in the SSMS UI corresponds to the backup_start_date of msdb. The SSMS reported time may be slightly ahead of or equal to the msdb table reported time.

For a multiple stripe backup, the backup time reported in the SSMS UI corresponds to the backup_end_date of msdb.

Application Direct backups to a DD system use the following components:

The Application Direct library API enables the backup software to communicate with the DD system.

The DDBEA section of the E-Lab Navigator provides information about the supported versions of the Application Direct library and the DDOS.

The distributed segment processing component reviews the data that is already stored on the DD system, and sends only unique data for storage. The distributed segment processing component enables the backup data to be deduplicated on the

4

Performing Self-Service Backups of Microsoft SQL Server Databases 73

database or application host to reduce the amount of data transferred over the network. Distributed segment processing provides information.

When the DD system restores data to a client, the system converts the stored data to its original non-deduplicated state before sending it over the network.

Federated backups of Always On availability groups

You can use the Microsoft SQL Server Always On availability groups feature to place databases in an Availability Group for high availability.

The database administrator can set backup preferences for the availability group and nominate a particular copy, which can be either the primary copy or one of the secondary copies, to use for the backup.

The Microsoft application agent supports federated backups for Application Direct backups. During federated backups, the Microsoft application agent detects the Microsoft SQL Server's backup preferences setting for the availability group, and then performs the backup on the preferred node.

NOTE: On a secondary node, Microsoft SQL Server supports only copy-only backups of databases. If the preferred node is

a secondary node, the Microsoft application agent performs a copy-only backup of databases. Microsoft SQL Server does

not support differential backups on secondary Microsoft SQL Server replicas. However, you can perform transaction log

backups from either copies.

The following figure illustrates an overview of the process interactions during federated backups. In the figure, the backup starts on Node A, but Node B is preferred.

Figure 3. Federated backup command and data flow

Distributed segment processing

Distributed segment processing uses the DD Boost library on the database server and the DD software on DD Replicator. The Microsoft application agent loads the DD Boost library during backup and restore operations.

Distributed segment processing allows the Microsoft application agent to perform parts of the deduplication process, which avoids sending duplicate data to the DD system that you configured as a storage server.

The distributed segment processing feature provides the following benefits:

Increases throughput because the DD Boost library sends only unique data to the DD system. The throughput improvements depend on the redundant nature of the data that you back up, the overall workload on the database server, and the database server capability. In general, greater throughput is attained with higher redundancy, greater database server workload, and greater database server capability.

Decreases network bandwidth requirements by sending the unique data to the DD system through the network.

Manage distributed segment processing by using the ddboost command options. Use distributed segment processing if the network connection is 1 Gb Ethernet. Configuring distributed segment processing provides information on how to configure the distributed segment processing.

Distributed segment processing supports the following modes of operation for sending backup data to a DD system:

Distributed segment processing enabled

74 Performing Self-Service Backups of Microsoft SQL Server Databases

Distributed segment processing disabled

Set the operation mode on the DD system. The Microsoft application agent negotiates with the DD system for the current setting of the option and accordingly performs backups.

Distributed segment processing enabled mode

When you enable the distributed segment processing feature, the DD Boost library performs the following tasks: 1. Segments the data. 2. Computes IDs for the data segments. 3. Checks with the DD system for duplicate segments. 4. Compresses unique segments that the DD system does not contain. 5. Sends the compressed data to the DD system, which writes the unique data to disk.

You must configure the local compression algorithm that the DD Boost library uses on the DD system. The DDOS Administration Guide provides more information about local compression and its configuration.

Distributed segment processing disabled mode

When you disable the distributed segment processing feature, the DD Boost library sends the data directly to the DD system through the network. The DD system then segments, deduplicates, and compresses the data before writing it to the disk.

NOTE: You cannot disable the distributed segment processing feature on an Extended Retention DD system.

Configuring distributed segment processing

You must configure the distributed segment processing option on the DD system. The option setting applies to all the database servers and all the software that uses DD Boost.

You can manage the distributed segment processing by using one of the following methods:

The ddboost command.

DD System Manager on the Data Management > DD Boost page.

The DDOS Administration Guide provides information.

To configure the distributed segment processing option, run the following command:

ddboost option set distributed-segment-processing {enabled | disabled} Enabling or disabling the distributed segment processing option does not require a restart of the DD file system.

A host on which you have installed the DDOS release 5.2 or later enables the distributed segment processing feature by default. If you update a host from DDOS release 5.0.x or 5.1.x to DDOS release 5.2 or later, the distributed segment processing option remains in its previous state, that is, either enabled or disabled.

Best practices to back up Microsoft SQL Server with Application Direct Consider the best practices to back up Microsoft SQL Server by using Application Direct.

Configure backups to use the same DD path

To ensure the consistency of the backups on the DD system, configure all the backups of a Microsoft SQL Server instance to use the same DD system and path.

Performing Self-Service Backups of Microsoft SQL Server Databases 75

Configure connection settings

DD Boost devices do not distinguish among Transmission Control Protocol (TCP)/Internet Protocol (IP), Fibre Channel (FC), and LAN, WAN, and MAN network types. DD Boost devices can successfully operate where packet loss is strictly 0% and latency is less than 20 ms.

Use supported characters

The Microsoft application supports locale-specific date and time processing and setting the date and time display language to non-English characters. However, the database name, hostname, instance name, Windows cluster name, virtual server name, and pathnames must be written in ASCII characters only. Naming conventions for backups with Application Direct provides more information on supported characters for database and instance names.

Configure DD quota limits

The Microsoft application agent does not have a parameter to control the total size that it consumes. The quota limits can only be set on the DD system on a per-MTree (storage unit) basis.

An MTree's quota limits are calculated based on the logical size, which is the size before compression and de-duplication of the data.

The quota limits impact only backup operations.

Configuring usage limits of DD resources provides more information about quota limit, impact of exceeding the limits, and configuring the usage limits.

Configure usage limits for DD streams

Configure a sufficient number of DD streams for better performance of backups and restores. The streams control backup and restore parallelism for each database.

The Microsoft application agent requires one stream per save set that you back up or restore. When you perform striped backups, each stripe requires one stream. The stripes are concurrently run for each database. Databases are sequentially backed up and restored. When you use stripes, the number of streams must be equal to or more than the number of stripes.

The minimum number of streams for a non-stripe environment is 1.

Configuring usage limits of DD streams provides more information about streams limit, impact of exceeding the limits, and configuring the usage limits.

Configuring usage limits of DD resources

Use the PowerProtect Data Manager UI to configure capacity quotas and stream limits for the DD system storage units that are under the control of PowerProtect Data Manager. The PowerProtect Data Manager Administration and User Guide provides more information about working with storage units.

For other storage units, use either the DDOS commands or the DD Administration UI to set limits on usage of the following DD resources:

Capacity: The amount of hard drive capacity that the application agent uses on a DD host.

Capacity limits are based on the used logical space, which depends on the amount of data that is written to a storage unit before deduplication. Logical capacity is the size of the uncompressed data. For example, when a 1 GB file is written twice to the same empty storage unit, the storage unit has a logical size of 2 GB, but a physical size of 1 GB.

Streams: The number of DD Boost streams that the application agent uses to read data from a storage unit or write data to a storage unit on a DD host.

NOTE: The Microsoft application agent supports usage limits on DD resources for Application Direct operations only.

The term quota collectively describes the capacity soft and hard limits of a storage unit. Stream limits are called limits.

Both capacity and stream usage support soft and hard limits:

76 Performing Self-Service Backups of Microsoft SQL Server Databases

When the Microsoft application agent exceeds a soft limit, the DD host generates an alert. If the administrator has configured a tenant-unit notification list, the DD host sends an email to each address in the list. The Microsoft application agent can continue to use more of the limited resource after a soft limit is exceeded.

When the Microsoft application agent exceeds a hard limit, it cannot use any more of the limited resource.

The administrator must create (or ask to have created) a separate storage unit for each application agent host or set of hosts that are limited.

For example, if there are 10 application agent hosts, the administrator must create at least 10 storage units to limit the storage unit capacity that each application agent host uses. To use fewer storage units, the administrator must group the application agent hosts and assign the group to a single storage unit. The application agent hosts in the group share this storage unit. However, you cannot limit the consumption of a storage unit by each host. One application agent host can consume 100% of the storage unit. The resources are consumed on the first-come, first-serve basis.

To determine the stream limits of a storage unit, run the following command:

msagentadmin.exe administration --listSU --config [-- debug 9] Example output of the command:

active write streams: 11 active read streams: 0 soft limit write streams: none soft limit read streams: none soft limit combined streams: 40 hard limit combined streams: 60

NOTE: Depending on the number and type of parallel operations that are performed at a given time, the stream usage

varies. To determine the exact usage of the streams, monitor the number of streams that the storage units use over a

period of time.

Impact of exceeding quota limits

At the start of a backup, the Microsoft application agent cannot determine how much capacity is required for the backup. The Microsoft application agent can perform a requested backup only when the destination host has sufficient space or storage capacity.

Exceeding the soft quota limit

When the Microsoft application agent exceeds the capacity soft limit: During a backup, if the storage unit is part of a tenant-unit with a notification list, the DD host sends an email to each

address in the list. The list can include the DD administrator and the application agent user. Alerts appear in the Current Alerts panel in the DD Administration GUI regardless of whether the storage unit is part of a

tenant-unit. The backup or restore operation continues without any adverse impact. The application agent does not generate any warning

or error message in its log file or operational output.

Exceeding the hard quota limit

When the Microsoft application agent exceeds the capacity hard limit during a backup, the Microsoft application agent cancels the backup.

Check the client backup and restore logs for error messages related to insufficient space on the storage unit. The following message shows an example:

145732:(pid 4584):Max DD Stream Count: 60 153003:(pid 4584): Unable to write to a file due to a lack of space. The error message is: [5005] [ 4584] [984] Thu Apr 14 10:14:18 2016 ddp_write() failed Offset 163577856, BytesToWrite 524288, BytesWritten 0 Err: 5005-ddcl_pwrite failed (nfs: No space left on device) 86699:(pid 4584): Unable to write data into multiple buffers for save-set ID '1460654052': Invalid argument (errno=22)

Performing Self-Service Backups of Microsoft SQL Server Databases 77

Configuring usage limits of DD quota

To configure capacity usage limits for the application agent, the DD administrator must set the hard capacity limit for the storage unit that the application agent uses for backups:

Steps

1. Determine which application agent hosts use the storage unit.

2. Determine the amount of capacity to allow for the storage unit.

3. Create the storage unit, and then set the capacity quota by using either the GUI or the command prompt. The DD documentation provides information.

4. Provide the DD hostname, storage unit name, username, and password of the storage unit to the application agent users to use to perform backups.

The DD administrator can also set the soft capacity quota for the storage unit, which sends alerts and notifications, but does not limit the capacity usage.

NOTE: When a storage unit is almost full and the capacity quota is decreased, the next backup can fail. DD

administrators must notify the Microsoft application agent users when they decrease a capacity quota, so that the

application agent users can evaluate the potential impact on backups.

Impact of exceeding the soft stream limit

When the Microsoft application agent exceeds the stream soft stream limit: During a backup, if the storage unit is part of a tenant-unit with a notification list, the DD host sends an email to each

address in the list. The list can include the DD administrator and the application agent user. Alerts appear in the Current Alerts panel in the DD Administration GUI regardless of whether the storage unit is part of a

tenant-unit. The backup or restore operation continues without any adverse impact. The application agent does not generate any warning

or error message in its log file or operational output.

Impact of exceeding the hard stream limit

When the Microsoft application agent exceeds the hard stream limit during an operation, the Microsoft application agent cancels the operation.

Check the client backup and restore logs for error messages related to an exceeded stream limit. The following message shows an example:

153004:(pid 4144): Unable to write to a file because the streams limit was exceeded.

Configuring usage limits of DD streams

A storage unit can have soft and hard limits for streams. The DD administrator can set individual soft limits for read, write, and replication streams. The administrator can set a hard limit only for the total number of streams.

About this task

To configure a streams usage limit for a storage unit, the DD administrator must set the hard limit for the storage unit that the application agent uses for backups:

Steps

1. Determine which application agent hosts use the storage unit.

2. Determine the number of backup streams to allow for the storage unit.

3. Create the storage unit.

78 Performing Self-Service Backups of Microsoft SQL Server Databases

The DD administrator can set the streams limit either as part of the ddboost storage-unit create command or after creating the storage unit by using the ddboost storage-unit modify command. The DD documentation provides information.

NOTE: The DD administrator cannot set a streams limit by using the DD Administration GUI.

4. Provide the DD hostname, storage unit name, username, and password of the storage unit to the application agent users to use to perform backups.

The DD administrator can also set soft limits for the storage unit, which send alerts and notifications, but do not limit the number of streams used.

The DD administrator can use the ddboost storage-unit modify command to modify the streams limits of storage units. The DD documentation provides information.

CAUTION: The DD administrator must use caution when setting a streams hard limit. Setting the streams

limit to a low value can impact the backup and restore performance. Decreasing a streams limit can result in

a restore failure. The DD administrator must notify the application agent users when decreasing a streams

hard limit so that the application agent users can evaluate the potential impact on backups and restores.

Configure the database backup stripe level

Starting with version 19.6, you can modify the stripe level of a backup at the individual database level by using the following procedures. You can set the stripe level through the following procedures only for self-service stand-alone Microsoft SQL Server backups, not for centralized backups performed through PowerProtect Data Manager.

CAUTION: After you update from version 19.6, centralized backups ignore any parallelism and backup stripe

settings that were previously configured on the Extended Properties page in SQL Server Management Studio

(SSMS). For centralized backups with version 19.6 or later, you must configure the parallelism settings through

the PowerProtect Data Manager UI, as described in the next topic.

The backup stripe level configuration includes the following features:

The backup stripe level setting for individual databases has a higher priority than the stripe level setting through the backup command with the -S option.

For any database, the minimum supported stripe level is 1 and the maximum supported stripe level is 32. In an FCI or AAG cluster, setting the backup stripe level of a database at any node reflects across all the nodes in the cluster.

To set the backup stripe level for any database, use either of the following procedures:

Perform the following steps in the SQL Server Management Studio (SSMS):

1. Right-click the database name, and select Properties. 2. In the properties window, select Extended Properties from the left side pane. 3. Add the required property name and the backup stripe level value:

For a full backup, add the property name ppdmFullStripes and a value between 1 and 32. For a differential backup, add the property name ppdmDiffStripes and a value between 1 and 32. For a log backup, add the property name ppdmLogStripes and a value between 1 and 32.

Performing Self-Service Backups of Microsoft SQL Server Databases 79

Figure 4. Extended Properties page with backup stripe levels Run the following T-SQL statements to set the backup stripe level for any database:

USE ; GO EXEC sp_addextendedproperty @name = N'ppdmDiffStripes', @value = '4'; EXEC sp_addextendedproperty @name = N'ppdmFullStripes', @value = '8'; EXEC sp_addextendedproperty @name = N'ppdmLogStripes', @value = '2';

Naming conventions for backups with Application Direct When naming Microsoft SQL Server instance, database, and filegroups, consider that the Microsoft application agent does not distinguish the difference between upper and lowercase letters. The names are not case-sensitive.

Therefore, if there are two or more databases with the same name but with different capitalization, such as DB1 and db1, the Microsoft application agent views these databases as the same and by default backs up only one of the databases.

The following table describes the special characters that are supported for naming database backups in Microsoft SQL Server stand-alone, cluster, and Always On availability group configurations with Application Direct.

Table 10. Supported special characters

Special character Name

~ Tilde

` Accent grave

80 Performing Self-Service Backups of Microsoft SQL Server Databases

Table 10. Supported special characters (continued)

Special character Name

! Exclamation mark

@ At the rate

% Percentage

^ Caret

& Ampersand

( Open parenthesis

) Close parenthesis

- Hyphen

_ Underscore

{ Open curly bracket

} Close curly bracket

\ Backslash

. Period

' Apostrophe

NOTE: While Microsoft SQL Server supports naming instances with the hash symbol (#), the Microsoft application agent

does not. If an instance includes a hash symbol, backups of that instance will fail.

Circumstances that promote Microsoft SQL Server backups to level full Transaction log and differential backups are promoted to full backups in certain situations.

By default, transaction log and differential backups are promoted to level full in the following scenarios:

When there is not an existing level full backup. When a log gap is detected. When the recovery model is changed. When the backup includes simple model databases, either the simple model databases are promoted to a full backup or the

simple model databases are skipped, depending on the backup settings. When the database has been newly restored.

Options to tune the behavior of automatic promotion are available while configuring a backup. The ddbmsqlsv -a "BACKUP_PROMOTION" command flag and the Microsoft app agent for Application Direct SSMS plugin Backup Promotion option both control backup promotion.

Performing Self-Service Backups of Microsoft SQL Server Databases 81

Scheduling backup jobs You can schedule Microsoft SQL Server backup jobs by using either the SQL Server Agent or the Windows Task Scheduler.

Scheduling Microsoft SQL Server backups by using SQL Server Agent

The SQL Server Agent is a job-scheduling agent which is contained in the Microsoft SQL Server package.

This section describes how to schedule Microsoft SQL Server backups by using the SQL Server Agent job for the CmdExec and T-SQL subsystems. The SQL Server Agent, a job-scheduling agent within the Microsoft SQL Server package, consists of a Windows service that runs jobs.

Each job can contain one or more job steps and each step can contain its own tasks. The Microsoft application agent uses Microsoft SQL Server to store job information and can run jobs on a schedule in response to a specific event or in response to a specific demand.

Configuring the SQL Server Agent to schedule jobs

Configuring the SQL Server Agent consists of the following tasks:

Enabling the SQL Server Agent Configuring security

Enabling the SQL Server Agent

The SQL Server Agent is in disabled state, by default. To enable the SQL Server Agent:

1. Open SSMS, and then select View > Object Explorer. 2. Right-click SQL Server Agent, and then select Start.

Configuring security

To run the Microsoft application agent command prompt commands in the CmdExec subsystem, you must have administrator privileges. You can either change the SQL Server Agent service login credentials to administrator or configure a proxy host to the CmdExec subsystem.

Changing the SQL Server Agent service login credentials

Steps

1. From the Windows desktop, click Start > Run.

2. In the Run dialog box, in the Open field, type services.msc, and then click OK.

3. In the Services window, right-click SQL Server Agent Service, and then select Properties.

4. In the SQL Server Agent Service Properties dialog box:

a. On the Log On tab, select This account. b. Type the administrator user credentials in the relevant fields.

You can also click Browse and select the user who has the administrator privileges.

c. Click OK.

82 Performing Self-Service Backups of Microsoft SQL Server Databases

Creating a proxy for the CmdExec subsystem

The SQL Server Agent uses proxies, which are objects that enable the SQL Server Agent to access stored credentials for Windows users, to define the security context for job steps.

About this task

When you run a job step that is configured to use a proxy, the SQL Server Agent uses the credentials that are defined in the proxy, and then uses the corresponding security context to run the job step.

Steps

1. Open SSMS, and then select View > Object Explorer.

2. Specify user credentials:

a. In the Object Explorer, expand Security, right-click Credentials, and then select Properties. b. On the Credential Properties - EMC page, specify the following fields, and then click OK:

Credential name: Type a name for the credential. Identity: Type the administrator username. Password: Type the password for the user that you specified in the Identity field. Confirm password: Retype the password that you specified in the Password field.

3. Create a proxy:

a. In the Object Explorer, expand SQL Server Agent, and then expand Proxies. b. Right-click Proxies, and then select New proxy. c. On the EMC Proxy Account Properties page, specify the following fields, and then click OK:

Proxy name: Type a name for the proxy. Credential name: Type the credential name that you specified in step 2b. Active to the following subsystems: Under this field, select Operating system (CmdExec).

NOTE: When you create a job step, you must select this proxy from the Run as list on the Job Step Properties

page.

Scheduling a CmdExec job

You can schedule a CmdExec job on either a single Microsoft SQL Server or multiple Microsoft SQL Servers.

Scheduling a CmdExec job on a single Microsoft SQL Server

Steps

1. Open SSMS, and then select View > Object Explorer.

2. In the Object Explorer, expand SQL Server Agent, right-click Jobs, and then select New job.

3. On the Job Properties window:

a. On the General page, type the appropriate information in the Name, Owner, and Description fields. b. On the Steps page, click New to create a step. c. In the Job Step Properties window, on the General page, specify the following fields:

Step name: Type a name for the job step. Type: Select Operating system (CmdExec). Run as: According to your configuration, select either proxy or SQL Server Agent Service Account. Process execute exit code of a successful command: Type the process success exit code. Command: Specify the required command.

Perform backups with the Microsoft app agent for Application Direct SSMS plug-in provides information about how to generate the command.

The generated command does not have a full path to the binary. When you specify the generated command in this field, you must add the full path to the binary. If the binary path contains spaces, specify the path in the quotes.

Performing Self-Service Backups of Microsoft SQL Server Databases 83

For example:

"C:\Program Files\DPSAPPS\MSAPPAGENT\bin\ddbmsqlsv.exe" -D9 -c NMMDB154.nmmdev.com -l full -a "NSR_DFA_SI_DD_HOST=10.31.192.14" -a "NSR_DFA_SI_DD_USER=ddbma" -a "NSR_DFA_SI_DEVICE_PATH=/ddbma-sqlagent2" "MSSQL:master"

d. On the Advanced page, specify the following fields: On success action: Select whether to proceed to the next job step or quit the current job step and report success,

after the current job step succeeds. Specify the other fields according to your requirements. Click OK.

e. On the Schedules page, click New to schedule a job. f. In the Job Schedule Properties window, specify appropriate information in the corresponding fields, and then click OK. g. On the Alerts page, click Add to create an alert that will perform a job when a certain event occurs. h. In the New Alert window, on the General page, specify the following fields:

Name: Type a name for the alert. Type: Select the type of the event. Specify the appropriate information in the other fields.

i. On the Response page, specify the following fields: Notify operators: Select this option to send a message to the operators about the job step status. New Operator: Click this button to add an operator to the Operator list.

j. On the Options page, configure a method, such as E-mail, Pager, or Net Send, to notify operators about the status of the job step.

k. On the Notifications page, under Actions to perform when the job completes, select the appropriate notification methods to notify operators about the status of the job step.

l. On the Targets page, select Target local server. m. Click OK.

Scheduling a CmdExec job on multiple Microsoft SQL Servers

Scheduling jobs from one central location to multiple target Microsoft SQL Servers eases the database administrators job. To configure this setup, you must install the Microsoft application agent on all target hosts, make one SQL Server Agent a primary, and make the rest of the hosts targets.

Configuring primary and target SQL Server Agents

Steps

1. Open the Microsoft SSMS, and then select View > Object Explorer.

2. Right-click SQL Server Agent, and then select Multi Server Administrator > Make this a Master.

The Master Server Wizard appears.

3. On the Welcome to the Master Server Wizard page, click Next.

4. On the Master Server Operator page, type the appropriate information in the E-mail address, Pager address, and Net send address fields to notify the operators about the status of the job, and then click Next.

5. On the Target Servers page:

a. Under the Registered servers panel, select the servers that you want to use as targets for the SQL Server Agent jobs, and then click the right arrow to move them to the Target servers panel.

b. If you want to add servers to the Registered servers panel, click Add Connection. c. In the Checking Server Compatibility dialog box, review the information, and then click Close.

The Master Server Login Credentials page appears.

6. Enable Microsoft SQL Server remote connectivity:

a. In SSMS, right-click the Microsoft SQL Server, and then click Properties. b. In the Server Properties window, under the Select a page group, select Connections. c. Select Allow remote connections to this server.

84 Performing Self-Service Backups of Microsoft SQL Server Databases

d. Click OK.

7. Specify general firewall exceptions on the Microsoft SQL Server.

8. If an SSL certificate does not exist, set the encryption level on the target hosts to 1 or 0 according to the security level you need.

To set the encryption level, change the MsxEncryptChannelOptions registry entry to 1 or 0. The registry key is located in \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\ \SQLServerAgent\.

9. On the Master Server Login Credentials page, click Next.

10. On the Complete the Wizard page, review the information, and then click Finish.

Running a job on the target servers

Steps

1. Open the SSMS, and then select View > Object Explorer.

2. In the Object Explorer, expand SQL Server Agent, right-click Jobs, and then select New job.

3. On the Job Properties window:

a. On the General page, type the appropriate information in the Name, Owner, and Description fields. b. On the Steps page, click New to create a step. c. In the Job Step Properties window, complete the following steps:

i. On the General page, specify the following fields: Step name: Type a name for the job step. Type: Select Operating system (CmdExec). Run as: According to your configuration, select either proxy or SQL Server Agent Service Account. Process execute exit code of a successful command: Type the process success exit code. Command: Specify the required command.

Perform backups with the Microsoft app agent for Application Direct SSMS plug-in provides information about how to generate the command.

The generated command does not have a full path to the binary. When you specify the generated command in this field, you must add the full path to the binary. If the binary path contains spaces, specify the path in the quotes.

For example:

"C:\Program Files\DPSAPPS\MSAPPAGENT\bin\ddbmsqlsv.exe" -D9 -c NMMDB154.nmmdev.com -l full -a "NSR_DFA_SI_DD_HOST=10.31.192.14" -a "NSR_DFA_SI_DD_USER=ddbma" -a "NSR_DFA_SI_DEVICE_PATH=/ddbma-sqlagent2" "MSSQL:master"

ii. On the Advanced page, specify the following fields: On success action: Select whether to proceed to the next job step or quit the current job step and report

success, after the current job step succeeds. Specify the other fields according to your requirements. Click OK.

d. On the Schedules page, click New to schedule a job. e. In the Job Schedule Properties window, specify appropriate information in the corresponding fields, and then click OK. f. On the Alerts page, click Add to create an alert that will perform a job when a certain event occurs. g. In the New Alert window:

i. On the General page, specify the following fields. Name: Type a name for the alert. Type: Select the type of the event. Specify the appropriate information in the other fields.

ii. On the Response page, specify the following fields: Notify operators: Select this option to send a message to the operators about the job step status. New Operator: Click this button to add an operator to the Operator list.

iii. On the Options page, configure a method, such as E-mail, Pager, or Net Send, to notify operators about the status of the job step.

Performing Self-Service Backups of Microsoft SQL Server Databases 85

iv. On the Notifications page, under Actions to perform when the job completes, select the appropriate notification methods to notify operators about the status of the job step.

v. On the Targets page, from the Target multiple servers list, select the target servers.

h. Click OK.

Scheduling a T-SQL job

About this task

NOTE: T-SQL subsystem does not work under proxies.

Steps

1. Open the SSMS, and then select View > Object Explorer.

2. In the Object Explorer, expand SQL Server Agent, right-click Jobs, and then select New job.

3. In the Job Properties window:

a. On the General page, specify the following fields:

Name: Type a name for the job. Owner: Click the button beside the text box, and then complete the following steps:

i. In the Select Login dialog box, click Browse. ii. In the Browse for Objects dialog box, under Matching objects, select NT SERVICE\SQLSERVERAGENT, and

then click OK. iii. In the Select Login dialog box, click OK.

Description: Type a description for the job.

b. On the Steps page, click New. c. In the Job Step Properties window, on the General page, specify the following fields:

Step name: Type a name for the job step. Type: Select Transact-SQL script (T-SQL). Run as: Select SQL Server Agent Service Account. Process execute exit code of a successful command: Type the process success exit code. Command: Specify the required T-SQL command.

Perform backups with the Microsoft app agent for Application Direct SSMS plug-in provides information about how to generate the T-SQL command.

You can run the generated T-SQL command by using the New Query menu option to check whether the operation succeeds. If the command runs successfully, the scheduled backups will be successful.

If you want to use return codes in the generated T-SQL command, you must modify the command.

Consider the following example raw T-SQL command:

USE [master] GO DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_backup ' -c NMMDB154.nmmdev.com -l full -a "NSR_DFA_SI_DD_HOST=10.31.192.14" -a "NSR_DFA_SI_DD_USER=ddbma" -a "NSR_DFA_SI_DEVICE_PATH=/ddbma-sqlagent2" "MSSQL:Fabrics"' PRINT @returnCode GO

Consider the following example T-SQL command with return codes:

DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_backup ' -c NMMDA224.heroines.local -l full -a "NSR_DFA_SI_DD_HOST=10.31.77.27" -a "NSR_DFA_SI_DD_USER=ost112" -a "NSR_DFA_SI_DEVICE_PATH=/heroines" "MSSQL:CopyOftest_db_1" "MSSQL:db1"' IF @returnCode <>0 BEGIN RAISERROR ('Fail!', 16, 1) END

If the return code is error, the job step fails.

86 Performing Self-Service Backups of Microsoft SQL Server Databases

NOTE: The last two parameters, 16 and 1 are necessary to raise an error if a job step fails.

d. On the Advanced page, specify the following fields:

On success action: Select whether to proceed to the next job step or quit the current job step and report success, after the current job step succeeds.

Specify the other fields according to your requirements. Click OK. On the Schedules page, click New to schedule a job. In the Job Schedule Properties window, specify appropriate information in the corresponding fields, and then click

OK. On the Alerts page, click Add to create an alert that will perform a job when a certain event occurs. In the New Alert window:

On the General page, specify the following fields.

Name: Type a name for the alert. Type: Select the type of the event. Specify the appropriate information in the other fields.

e. On the Response page, specify the following fields:

Notify operators: Select this option to send a message to the operators about the job step status. New Operator: Click this button to add an operator to the Operator list.

f. On the Options page, configure a method, such as E-mail, Pager, or Net Send, to notify operators about the status of the job step.

g. On the Notifications page, under Actions to perform when the job completes, select the appropriate notification methods to notify operators about the status of the job step.

h. On the Targets page, select Target local server. i. Click OK.

Next steps

To check the status of a job, either right-click the job and select View History or review the log files in the nsr/applogs/ folder.

Scheduling Microsoft SQL Server backups by using Windows Task Scheduler

To schedule Microsoft SQL Server backups by using Windows Task Scheduler, perform the following steps:

Steps

1. On the Windows desktop, click Start > All Programs > Accessories > System Tools > Task Scheduler.

2. In the left pane of the Task Scheduler window, right-click Task Scheduler Library, and then select Create Basic Task.

The Create Basic Task Wizard wizard appears.

3. On the Create a Basic Task page, in the Name field, type a name for the task, and then click Next.

4. On the Task Trigger page, select the appropriate option to start the task, and then click Next.

The page that corresponds to the selected option appears.

5. Specify or select all the fields that you require to perform the task, and then click Next.

6. On the Action page, select Start a program, and then click Next.

7. On the Start a program page, browse for the .bat file and in the Program/script field, type the file path, and then click Next.

8. On the Summary page, review the details of the task, and then click Finish.

The process creates the task and adds it to your Windows schedule.

Performing Self-Service Backups of Microsoft SQL Server Databases 87

Performing manual backups The Microsoft application agent for Application Direct supports multiple tools to perform manual backups.

You can configure backups using the Microsoft application agent SQL Server Management Studio plug-in (GUI), Microsoft application agent for Application Direct commands, or T-SQL scripts.

Perform backups with the Microsoft app agent for Application Direct SSMS plug-in

The Microsoft application agent supports a user interface to perform backup operations through a SQL Server Management Studio (SSMS) plug-in.

If the DD device is connected only on the backup LAN, and the Microsoft SQL Server host is multi-homed and has an interface on the backup LAN, the backups to the DD device proceed over the backup LAN by default.

If both the DD device and the Microsoft SQL Server host are multi-homed, and are connected to the backup LAN, ensure that the DD server name that you specify in the Microsoft app agent for Application Direct SSMS plug-in is the same as the backup LAN IP address. The backups to the DD device proceed over the backup LAN.

To back up Microsoft SQL Server to a DD server over Fibre Channel (FC), you must first configure FC on the DD server.

The Script view is available in each page of the Backup tab, which generates a command prompt equivalent script. You can use the script to create a .bat file to perform scheduled backups, automation, and other tasks. The following script options are available:

CLI Scripts: To generate the CLI script, which you can use to run a backup from the CLI. T-SQL Scripts: To generate a backup script in the T-SQL format.

Configure general backup settings

To configure Microsoft SQL Server backups with the Microsoft app agent for Application Direct SSMS plug-in, you must first specify general backup options on the Backup > General page.

Steps

1. Open the Microsoft app agent for Application Direct window to the Backup > General page.

The General page appears as shown in the following figure.

88 Performing Self-Service Backups of Microsoft SQL Server Databases

Figure 5. Application Direct - Backup-General page

2. Leave the SQL Server Host as-is. The instance is populated by default.

3. In the SQL Server Instance field, select the name of the Microsoft SQL Server instance that contains the databases that you want to back up.

4. In the Database Filter list, select one of the following options:

All Databases: Displays the regular databases and the Always On availability group databases of the selected Microsoft SQL Server instance in the database table, which is located below the Database Filter field.

This option is selected by default.

You can back up the Always On availability group databases as regular databases without considering the Always On availability group preferences.

Non AAG Databases: Displays only the regular databases of the selected Microsoft SQL Server instance in the database table.

A list of Always On availability groups if available: Selecting one of the Always On availability groups displays the corresponding databases in the database table.

The Connections panel displays the name of the cluster that contains the Always On availability group and the backup preference that specifies the preferred replica to perform the backup. You can configure the replica preference of the Always On availability groups through the SSMS.

5. In the database table, select either all the databases by selecting the check box in the header row or only the individual databases that you want to back up.

6. In the Backup type list, select the type of the backup that you want to perform such as, Full, Transaction log, or Differential.

7. (Optional) To perform a copy-only backup, select Copy-only backup.

Copy-only backups do not disturb the Microsoft SQL Server backup chain or affect backup-level promotion and log truncation. Copy-only backups are supported for level full or transaction log backups.

8. (Optional) To exclude databases from a Microsoft SQL Server instance-level backup, perform the following steps:

a. Click the Excluded Databases button.

Performing Self-Service Backups of Microsoft SQL Server Databases 89

The Exclude Databases window appears.

b. Select each database that you want to exclude from the backup. c. Click OK.

The databases that are selected for exclusion appear grayed out in the list of databases and the number of excluded databases is displayed.

9. In the Name field, type a name for the backup that you want to perform.

After the backup completes, the save set names of the backed-up databases will be in the following format:

: For example, you select the databases db1 and db2, specify test as the backup or save set name, and then perform the backup. After the backup completes, the save set names of the backed-up databases are test: db1 and test:db2.

NOTE: The number sign (#) character is not supported for save set names. If you use this character, backups fail.

10. In the Description field, type a description for the backup that you want to perform.

11. In the Expires after (days) field, select the number of days after which the backup must expire. The default value is 30.

12. Under Destination, to select the target DD server for the backup, perform the following steps:

a. Click the PowerProtect DD System browse button. The PowerProtect DD System List & Lockbox Settings dialog box appears, as shown in the following figure.

Figure 6. DD system list and lockbox settings b. In the Lockbox Folder field, type the path to lockbox, and then click Refresh.

The default path to the lockbox is C:\Program Files\DPSAPPS\common\lockbox.

The PowerProtect DD Systems list is refreshed. c. In the PowerProtect DD Systems table, select the target DD server for the backup. d. (Optional) To add or remove DD servers from the PowerProtect DD Systems table, perform one of the following

action sequences:

To add a server, perform the following steps: i. Click Add.

The Add PowerProtect DD System details dialog box appears as shown in the following figure.

90 Performing Self-Service Backups of Microsoft SQL Server Databases

Figure 7. Add DD system details ii. In the PowerProtect DD System field, type the name of the server. iii. In the Communication Protocol list, select either Ethernet or Fibre channel, the medium through which you

want to back up the database to the server. Ethernet is selected by default. iv. If you have selected Fibre channel from the Communication Protocol list, type the name of the DD server as

the FC service name in the FC Service Name field. v. In the Username field, type the username of the DD Boost user. vi. In the Password field, type the password of the DD Boost user. vii. In the Storage Unit field, type the name of the target storage unit for the backup.

DD Boost user credentials are verified before they are saved in the lockbox. Verification of the user credentials requires some time to complete.

To remove a DD server, select the server, and then click Remove. To add a virtual server to either back up databases to Microsoft SQL Server clustered instances or restore databases

from Microsoft SQL Server clustered instances, perform the following steps: Select Edit LockBox Settings. In the Enter Host Name field, type the FQDN of the virtual server. Click OK.

To remove a virtual server, select the FQDN of the virtual server from the Select Host Name list, and then click Remove.

The PersistedSettings.xml file in the lockbox folder contains the information about DD servers. Adding a server to a new lockbox creates the PersistedSettings.xml file. Adding a server to or removing a server from the lockbox updates the PersistedSettings.xml file.

13. To start the backup operation, click Run.

Configure optional backup settings

When you configure Microsoft SQL Server backups with the Microsoft app agent for Application Direct SSMS plug-in, you can specify optional backup settings on the Backup > Options page.

About this task

All settings on the Options page are optional.

Steps

1. From the left panel, click Options to specify optional backup settings.

The Options page appears as shown in the following figure.

Performing Self-Service Backups of Microsoft SQL Server Databases 91

Figure 8. Application Direct - Backup-Options page

2. To perform a checksum operation with the backup and save the information to the backup media, select Perform checksum before writing to media.

The Microsoft application agent performs another checksum before a restore to ensure that the checksum matches the backup.

3. To use a checksum to detect a partial backup or restore state, select Continue on error.

The Microsoft SQL Server verifies the checksum by calculating a local result and comparing the result with the stored value. If the values do not match and you encounter errors, you can select this option to continue the backup or restore operation.

4. To truncate the transaction logs before a backup, select Truncate the transaction log.

The Microsoft application agent enables this option if you select transaction log as the backup type.

5. To perform a tail-log backup of the database and leave the database in the restoring state, select Backup the tail of the log and leave database in restoring state.

6. Under Stripes, select Create a striped backup to create a striped backup. You can also specify the number of stripes. If you specify a value greater than the maximum limit of 32, the value defaults to 32.

7. To promote backups of SIMPLE recovery model databases to level full, select Promote to full backup.

SIMPLE recovery model databases do not support transaction log backups. The Microsoft application agent enables this option if you select the SIMPLE recovery model databases to back up, and transaction log as the backup type.

8. To omit SIMPLE recovery model databases from the backup, select Skip backup.

Microsoft application agent enables this option if you select the SIMPLE recovery model databases to back up, and transaction log as the backup type. SIMPLE recovery model databases do not support transaction log backups.

9. To check the status of the selected databases and ignore the databases that are unready or unavailable for the backup, select Skip databases that cannot be backed up at its current state.

If the status of the databases is ONLINE, the databases are ready or available for backups.

If the status of the databases is OFFLINE, EMERGENCY (SINGLE_USER Mode), SUSPECT, RESTORING, RECOVERING, or RECOVERY_PENDING, the databases are unready or unavailable for backups.

92 Performing Self-Service Backups of Microsoft SQL Server Databases

10. To generate detailed logs, which you can use to troubleshoot backup issues, specify a number between 1 and 9 in the Select a debug level field. The default value is 0 (zero).

11. To delete debug logs older than a certain number of days, in the Delete debug logs after field, specify the number of days with a number between 1 and 32767 days. The default value is 0 and does not delete any debug logs.

Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

NOTE: This option only deletes debug logs named in the default format and located in the logs folder at

\MSAPPAGENT\logs.

12. To specify backup promotion options, select one of the following values from the Backup Promotion list: ALL: Enables backup promotion to occur in any applicable scenario. NONE: Disables all backup promotion. NONE_WITH_WARNINGS: Disables backup promotion, but logs a warning when backup promotion would normally

occur. SKIP_RECOVERY_MODEL: Disables database recovery model change detection. Backup promotion as a result of

recovery model change will not occur, but backup promotion in other scenarios will still occur. SKIP_RECOVERY_MODEL_WITH_WARNINGS: Enables database recovery model change detection, but if a recover

model change is discovered, logs a warning instead of promoting the backup. Backup promotion in other scenarios will still occur.

13. To specify advanced backup options, use the Advanced Options field to select or type advanced options.

Separate multiple entries with a comma, for example:

BUFFERCOUNT=2, READ_WRITE_FILEGROUPS The following advanced backup options are supported:

BUFFERCOUNT=number_of_IO_buffers: Specifies the total number of IO buffers that can be used during the backup operation.

READ_WRITE_FILEGROUPS: Backs up only the read/write (active) filegroups within the database.

14. To start the backup operation, click Run.

Monitor the backup operation

After a backup operation is run from the Microsoft app agent for Application Direct SSMS plug-in, the Backup > Monitor page displays the backup script and status.

The following figure shows the backup information and status as it appears on the Monitor page.

Performing Self-Service Backups of Microsoft SQL Server Databases 93

Figure 9. Application Direct - Backup-Monitor page

NOTE: For information about the success or failure of the backup operation, review the log files that are located in the

installation folder. The typical location of the log files is C:\Program Files\DPSAPPS\MSAPPAGENT\logs.

Back up Microsoft SQL Server with the Application Direct backup command

Use the ddbmsqlsv command to configure backups of Microsoft SQL Server data from a command prompt.

NOTE: In the syntaxes, the options that are enclosed in square brackets, that is, [ and ] are optional.

To perform specific backup-related and restore-related operations, the Microsoft application agent also supports the ddbmadmin.exe command besides the msagentadmin.exe command. However, the ddbmadmin.exe command is deprecated.

Syntax for backups of a stand-alone server

Run the ddbmsqlsv command with the following syntax to back up a stand-alone Microsoft SQL Server:

ddbmsqlsv -c -l {full | incr | diff} -a "NSR_DFA_SI_DD_HOST= " -a "NSR_DFA_SI_DEVICE_PATH= " -a "NSR_DFA_SI_DD_USER= " [ ] " "

where:

-c

94 Performing Self-Service Backups of Microsoft SQL Server Databases

Specifies the Microsoft SQL Server hostname that contains the Microsoft SQL Server instance that you want to back up.

-l {full | incr | diff}

Specifies the type of the backup to perform such as full (full), transaction log (incr), or differential (diff). The default value is full.

-a "NSR_DFA_SI_DD_HOST= "

Specifies whether the backup destination is a DD server.

-a "NSR_DFA_SI_DEVICE_PATH= "

Specifies the name and the path of the storage unit where you want to direct the backup.

-a "NSR_DFA_SI_DD_USER= "

Specifies the username of the DD Boost user.

You must register the hostname and the DD Boost username in the lockbox to enable Microsoft application agent to retrieve the password for the registered user.

Specifies the backup path.

Type the backup path in one of the following formats: For a default instance, type the path in one of the following formats:

To back up the entire instance, type MSSQL: To back up specific databases, type [MSSQL:] [[MSSQL:]

[...]]

For example: "MSSQL:database1" "MSSQL:database2" For a named instance, type the path in one of the following formats:

To back up the entire instance, type MSSQL$ : To back up specific databases, type MSSQL$ : [...] For example: "MSSQL$SqlInst1:database1" "MSSQL$SqlInst1:database2"

Microsoft SQL Server stand-alone backup command

ddbmsqlsv.exe -c SQLX86.adesc.com -l full -a "NSR_DFA_SI_DD_HOST=10.31.196.90" -a "NSR_DFA_SI_DD_USER=ost" -a "NSR_DFA_SI_DEVICE_PATH=/sqlserver" "MSSQL$INST2008:d2"

Syntax for backups of an Always On availability group

Run the ddbmsqlsv command with the following syntax to back up a stand-alone Microsoft SQL Server:

ddbmsqlsv -c -A -l {full | incr | diff} -a "NSR_DFA_SI_DD_HOST= " -a "NSR_DFA_SI_DEVICE_PATH= " -a "NSR_DFA_SI_DD_USER= " [ ] " "

Run the ddbmsqlsv command with the following syntax to back up a clusterless Always On availability group (AAG):

ddbmsqlsv -a "SKIP_CLIENT_RESOLUTION=TRUE" -c _ -l {full | incr | diff} -a "NSR_DFA_SI_DD_HOST= " -a "NSR_DFA_SI_DEVICE_PATH= " -a "NSR_DFA_SI_DD_USER= " [ ] " "

NOTE: For a clusterless AAG, you must add the option -a "SKIP_CLIENT_RESOLUTION=TRUE" and specify

_ with the -c option.

where:

-c

Specifies the Windows cluster name that you want to back up.

-c _

Performing Self-Service Backups of Microsoft SQL Server Databases 95

Specifies the clusterless AAG that you want to back up, for example, -c AAG1_ef770eaf-ebe3-f5be- bdff-3a7243ff1236.

-A

Specifies the fully qualified domain name (FQDN) of the virtual server.

NOTE: The -A option does not apply to clusterless AAG backups.

-l {full | incr | diff}

Specifies the type of the backup to perform such as full (full), transaction log (incr), or differential (diff). The default value is full.

-a "NSR_DFA_SI_DD_HOST= "

Specifies the name of the DD server that contains the storage unit where you want to back up the databases.

-a "NSR_DFA_SI_DEVICE_PATH= "

Specifies the name and the path of the storage unit where you want to direct the backup.

-a "NSR_DFA_SI_DD_USER= "

Specifies the username of the DD Boost user.

You must register the hostname and the DD Boost username in the lockbox to enable Microsoft application agent to retrieve the password for the registered user.

-a "SKIP_CLIENT_RESOLUTION=TRUE"

Specifies to skip the client resolution for _ , as specified with the -c option. Skipping the client resolution is required for a clusterless AAG backup.

" "

Specifies the path to the objects that you want to back up.

Type the backup path in one of the following formats: For a default instance, type the path in one of the following formats:

To back up the entire instance, type MSSQL# : To back up specific databases, type [MSSQL# :]

[[MSSQL# :] [...]] For example: For example: "MSSQL#aag1:database1" "MSSQL#aag1:database2"

For a named instance, type the path in one of the following formats: To back up the entire instance, type MSSQL$ # : To back up specific databases, type MSSQL$ # :

[...] For example: "MSSQL$SqlInst1#sql2012-aag3:database1" "MSSQL$SqlInst1#sql2012-aag3:database2"

NOTE: The Microsoft application agent does not support backing up multiple Always On availability groups in the same

operation.

Microsoft SQL Server cluster backup command

The following command backs up databases in a Microsoft SQL Server cluster environment:

ddbmsqlsv.exe -c SQLcluster1.adesc.com -A SQLcluster1.adesc.com -l full -a "NSR_DFA_SI_DD_HOST=10.31.196.90" -a "NSR_DFA_SI_DD_USER=ost" -a "NSR_DFA_SI_DEVICE_PATH=/sqlserver" "MSSQL$SQ12INST4#sql2012-aag3:"

Backing up an Always On availability group when all instance names are the same

When the server nodes contain only default instances, or when the Microsoft SQL Server instance names are all the same in the availability group, type the backup command in the following syntax:

96 Performing Self-Service Backups of Microsoft SQL Server Databases

NOTE: A retention setting in PowerProtect Data Manager overrides a retention setting specified by the -y option.

ddbmsqlsv.exe -c SQL2012clus3.brsvlab.local -S 4 -l full -y +30d -a "NSR_DFA_SI_DD_HOST=ddve-01" -a "NSR_DFA_SI_DD_USER=sqlboost" -a "NSR_DFA_SI_PATH=/ sqlboost" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C:\Program Files\DPSAPPS\common\lockbox" -a "NSR_SKIP_NON_BACKUPABLE_STATE_DB=TRUE" "MSSQL$SQ12INST4#sql2012-aag3:"

where:

-c SQL2012clus3.brsvlab.local specifies the cluster name.

"MSSQL$SQ12INST4#sql2012-aag3:" is the backup object name, where all the databases of the sql2012-aag3 Always On availability group are backed up. The backup object name is made of the following components: MSSQL is a mandatory term.

If you use named instances, $SQ12INST4 is the Microsoft SQL Server instance name.

If you use a default instance, do not specify $ in the backup object.

# indicates a federated backup.

sql2012-aag3 is the AlwaysOn Availability Group name.

Backing up an Always On availability group when there are multiple instance names

When you back up an Always On availability group where the nodes contain Microsoft SQL Servers with different instance names, the backup command on each instance should reflect the available instance.

For example, consider the following scenario:

There are two different instances: SQ12INST4 resides on Node1. SQ12INST5 resides on Node2

Node1 is the primary replica. Node2 is the secondary replica. The Always On availability group backup preference is set to secondary.

In this scenario, the backup command on SQL2INST4 should specify the backup object as "MSSQL$SQL2INST4#sql2012- aag3:", while backup command on SQL2INST5 should specify the backup object as "MSSQL$SQL2INST5#sql2012- aag3:". After failover of Node1 and Node2, Node1 becomes secondary, and Node2 becomes primary. The backup command is the same after failover.

NOTE: When browsing the backups for a restore operation, the save sets could be in either of the instances (SQL2INST4

or SQL2INST5). The save set depends on the instance that is used for the first backup.

Backing up multiple databases in an Always On availability group

To back up only certain databases in an Always On availability group, use " " " " " "... to specify the database names as the backup objects.

Type the backup command with the following syntax:

NOTE: A retention setting in PowerProtect Data Manager overrides a retention setting specified by the -y option.

ddbmsqlsv.exe -c SQL2012clus3.brsvlab.local -S 4 -l full -y +30d -a "NSR_DFA_SI_DD_HOST=ddve-01" -a "NSR_DFA_SI_DD_USER=sqlboost" -a "NSR_DFA_SI_PATH=/ sqlboost" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C:\Program Files\DPSAPPS\common\lockbox" -a "NSR_SKIP_NON_BACKUPABLE_STATE_DB=TRUE" "MSSQL$SQ12INST4#sql2012- aag3:database1" "MSSQL$SQ12INST4#sql2012-aag3:database3" "MSSQL $SQ12INST4#sql2012-aag3:database8"

where:

MSSQL$SQ12INST4#sql2012-aag3:database1, MSSQL$SQ12INST4#sql2012-aag3:database3, and MSSQL$SQ12INST4#sql2012-aag3:database8 are the backup objects

Only database1, database3, and database8 of the sql2012-aag3 Always On availability group are backed up.

Performing Self-Service Backups of Microsoft SQL Server Databases 97

Optional parameters for the ddbmsqlsv command

The following list describes the optional parameters that you can use with the ddbmsqlsv command:

-N

Specifies a name for the backup.

-b

Specifies a description for the backup.

-S

Specifies to perform a striped backup using the number of stripes that you specify. If you specify a value greater than a maximum limit of 32, the value defaults to 32.

-a "SKIP_SIMPLE_DATABASE={TRUE | FALSE}"

Specifies whether to ignore backing up SIMPLE recovery model databases. Use this option if you select the SIMPLE recovery model databases for backup, and specify Transaction log as the backup type. The SIMPLE recovery model databases do not support transaction log backups.

The default value is FALSE.

-a "NSR_SKIP_NON_BACKUPABLE_STATE_DB={TRUE | FALSE}"

Specifies whether to check the status of the selected databases and ignore the databases that are unready or unavailable for the backup.

If the status of the databases is ONLINE, the databases are ready or available for backups.

If the status of the databases is OFFLINE, EMERGENCY (SINGLE_USER Mode), SUSPECT, RESTORING, RECOVERING, or RECOVERY_PENDING, the databases are not ready or available for backups.

The default value is TRUE.

-q

Displays ddbmsqlsv messages in the quiet mode, that is, the option displays summary information and error messages only.

-v

Displays ddbmsqlsv messages in the verbose mode, that is, the option provides detailed information about the progress of the backup operation.

-G

Specifies to perform a NO_LOG transaction log backup before backing up the database.

-R

Uses the NO_TRUNCATE option when backing up transaction logs.

-T

Performs a TRUNCATE_ONLY transaction log backup before backing up the database.

-k

Specifies to perform a checksum before backing up the data to the device.

-u

Specifies to perform a checksum before the backup but to proceed with the backup operation even in the case of errors.

-y + {d | w | m | y}

Specifies the period of time after which the backup must expire. For example:

-y +20d

NOTE: A retention setting in PowerProtect Data Manager overrides a retention setting specified by

the -y option.

You can specify any positive integer, followed by one of the following units of time: d for day

w for week

m for month

98 Performing Self-Service Backups of Microsoft SQL Server Databases

y for year

The maximum possible retention date is 2/7/2106.

If you omit this option or specify 0, the default value of 30 days is used.

-h " "

Specifies databases to omit from the backup. You can use this option to specify exact database names or use wildcard characters.

Two wildcard characters are supported: Question mark (?): Matches any single character Asterisk (*): Matches zero to unlimited characters

When you use wildcard characters you must enclose the database name in square brackets, for example, [DB?].

For example, consider the following scenarios:

To exclude only DB_1 and DB_2 from the backup, add -h DB_1 -h DB_2 to the backup command.

To exclude all databases named with the format of DB_x, such as DB_9 and DB_a, add -h [DB_?] to the backup command.

To exclude all databases with names ending in DB, add -h [*DB] to the backup command.

-O {BUFFERCOUNT | READ_WRITE_FILEGROUPS}

Specifies advanced backup options.

You can specify the following advanced backup options: BUFFERCOUNT= : Specifies the total number of IO buffers that can be used

during a backup operation. READ_WRITE_FILEGROUPS: Specifies to back up only the read/write (active) filegroups within the

database.

If you are specifying multiple options, separate each argument with a comma. The syntax is as follows:

-O "Option1, Option2, Option3"

-D

Generates detailed logs that you can use to troubleshoot backup issues. The default value is 0 (zero).

-a "DELETE_DEBUG_LOG_DAYS= "

Specifies to delete debug log files that are older than the specified number of days. The valid range is between 1 and 32767. By default, debug logs are not deleted. Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

This parameter only deletes debug logs named in the default format and located in the logs folder at \MSAPPAGENT\logs.

-a "NSR_COPY_ONLY={TRUE | FALSE}"

Performs a copy-only backup from a Microsoft SQL Server. The copy-only backups do not disturb the Microsoft SQL Server backup chain and do not affect backup-level promotion and log truncation. The default value is FALSE.

This option applies only if you specify either full or incr as the backup type with the -l parameter.

Copy-only transaction log backups are generally required only to perform online restores.

-a "NSR_ENABLE_FC={TRUE | FALSE}"

Enables or disables backing up the databases to the DD server through Fibre Channel. The default value is FALSE.

-a "NSR_FC_HOSTNAME=

Specifies the hostname of the Fibre Channel. Use this option with the -a "NSR_ENABLE_FC=TRUE" parameter.

-a "NSR_INCLUDE_AAG_DATABASE=None

Specifies to omit Always On availability group databases from an instance-level backup operation.

-a "NSR_DFA_SI_DD_LOCKBOX_PATH= "

Performing Self-Service Backups of Microsoft SQL Server Databases 99

Specifies the folder that contains the lockbox file, which contains encrypted information about the registered hosts and the corresponding usernames in pairs. Each pair is associated with a password that backups use.

If you do not specify a value, the path defaults to lockbox path in the default installation path, which is C:\Program Files\DPSAPPS\common\lockbox.

-a "SKIP_SYSTEM_DATABASE={TRUE | FALSE}"

Specifies whether to skip the system databases during instance-level transaction log backups. The default value is FALSE.

-a "BACKUP_PROMOTION={ALL | NONE | NONE_WITH_WARNINGS | SKIP_RECOVERY_MODEL | SKIP_RECOVERY_MODEL_WITH_WARNINGS}"

Specifies backup promotion options. The following values are valid: ALL (Default): Enables backup promotion to occur in any applicable scenario.

NONE: Disables all backup promotion.

NONE_WITH_WARNINGS: Disables backup promotion, but logs a warning when backup promotion would normally occur.

SKIP_RECOVERY_MODEL: Disables database recovery model change detection. Backup promotion as a result of recovery model change will not occur, but backup promotion in other scenarios will still occur.

SKIP_RECOVERY_MODEL_WITH_WARNINGS: Enables database recovery model change detection, but if a recover model change is discovered, logs a warning instead of promoting the backup. Backup promotion in other scenarios will still occur.

The setting specified with this option applies to every database in the Microsoft SQL Server instance when this setting is specified along with a Microsoft SQL Server instance-level backup path.

Similarly, the setting specified with this option applies only to specified databases when this setting is specified with a database level backup path.

Perform backups with T-SQL scripts

The Microsoft application agent for Application Direct enables you to generate a SQL-CLR script that you can use to back up Microsoft SQL Server.

The SQL-CLR backup command, emc_run_backup, uses the Microsoft application agent for Application Direct with Microsoft SQL Server backup command prompt options. You must also provide VARCHAR parameters to this command.

To use this command, you must have a detailed knowledge of the Microsoft application agent for Application Direct with Microsoft SQL Server backup command prompt options. Back up Microsoft SQL Server with the Application Direct backup command provides information about the Microsoft application agent for Application Direct with Microsoft SQL Server backup command prompt options.

Sample T-SQL backup script

The following SQL-CLR script is an example of a backup script:

NOTE: A retention setting in PowerProtect Data Manager overrides a retention setting specified by the -y option.

USE [master] GO DECLARE @returnCode int 8 -l full -N "Set1" -y +0d -a "NSR_DFA_SI_DD_HOST=10.31.192.10" -a "NSR_DFA_SI_DD_USER=ost" -a "NSR_DFA_SI_DEVICE_PATH=/ddsub7" -a "NSR_SKIP_NON_BACKUPABLE_STATE_DB=TRUE" "MSSQL:"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

You can use any Microsoft SQL Server standard interfaces, such as the SSMS Query window and OSQL command line tool, to run the SQL-CLR scripts.

100 Performing Self-Service Backups of Microsoft SQL Server Databases

You can use the SQL-CLR script to schedule Microsoft SQL Server backups by using the SQL Server Agent. Scheduling Microsoft SQL Server backups by using SQL Server Agent provides information.

Best practices to back up Microsoft SQL Server with Application Direct provides guidelines for better performance of Microsoft SQL Server backups by using the Microsoft application agent for Application Direct SQL-CLR scripts.

Performing Microsoft SQL Server push backups by using the Microsoft application agent for Application Direct T-SQL scripts

About this task

To back up either all databases or only the specific databases of a Microsoft SQL Server instance from a source host to a DD device by using a different host, perform the following steps:

Steps

1. Start SSMS on a different host that you use to perform the backup.

2. Connect to the source Microsoft SQL Server instance on the source host.

3. In the SSMS window on the different host, click New Query.

4. In the New Query window, run the T-SQL script to perform the backup.

Results

You can either generate the T-SQL script by using the Microsoft application agent GUI on the source host and copy it to the New Query window on the different host or write the T-SQL script in the New Query window. Perform backups with the Microsoft app agent for Application Direct SSMS plug-in and Perform backups with T-SQL scripts provide information.

T-SQL push backup script

NOTE: A retention setting in PowerProtect Data Manager overrides a retention setting specified by the -y option.

USE [master] GO DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_backup ' -c CLUST-SQL-02.contoso.com -A CLUST-SQL-02.contoso.com -l full -y +0d -a "NSR_DFA_SI_DD_HOST=nmmddtwo.sp2010.com" - a "NSR_DFA_SI_DD_USER=ost" -a "NSR_DFA_SI_DEVICE_PATH=/ddbmav2b75" -a "NSR_SKIP_NON_BACKUPABLE_STATE_DB=TRUE" "MSSQL$Inst1:Clus-SQL-01-DB01" "MSSQL$Inst1:CLUST-SQL-02-DB01" "MSSQL$Inst1:CLUST-SQL-02-DB02" "MSSQL $Inst1:CLUST-SQL-02-DB03"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

where:

CLUST-SQL-02.contoso.com is the source host that has the source Microsoft SQL Server instance that you want to back up.

Inst1 is the source Microsoft SQL Server instance, to which you must connect from the different host to perform the backup.

Clus-SQL-01-DB01, CLUST-SQL-02-DB01, CLUST-SQL-02-DB02, and CLUST-SQL-02-DB03 are the databases that you have selected in the Inst1 instance to back up.

Performing federated backups of SQL Always On availability group databases by using T-SQL scripts

To perform federated backups, use the same backup command and options that Perform backups with T-SQL scripts describes, but with the following modifications:

Specify the Windows cluster name for in -c .

Specify the backup object name for in -N .

Specify # in the backup object name.

Performing Self-Service Backups of Microsoft SQL Server Databases 101

The options in the following sample scripts indicate these modifications.

NOTE:

The Microsoft application agent does not support backing up multiple Always On availability groups in the same operation.

A retention setting in PowerProtect Data Manager overrides a retention setting specified by the -y option.

Sample T-SQL script to back up an entire Always On availability group

USE [master] GO DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_backup '-c SQL2012clus3.brsvlab.local -S 4 -l full -y +30d -a "NSR_DFA_SI_DD_HOST=ddve-01" -a "NSR_DFA_SI_DD_USER=sqlboost" -a "NSR_DFA_SI_PATH=/sqlboost" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C:\ProgramFiles\DPSAPPS\common\lockbox" -a "NSR_SKIP_NON_BACKUPABLE_STATE_DB=TRUE" -N "MSSQL$SQ12INST4#sql2012-aag3:" "MSSQL$SQ12INST4#sql2012-aag3:"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

Sample T-SQL script to back up multiple databases (a subset of databases) of an Always On availability group

USE [master] GO DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_backup '-c SQL2012clus3.brsvlab.local - S 4 -l full -y +30d -a "NSR_DFA_SI_DD_HOST=ddve-01" -a "NSR_DFA_SI_DD_USER=sqlboost" -a "NSR_DFA_SI_PATH=/sqlboost" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C:\ProgramFiles\DPSAPPS\common\lockbox" -a "NSR_SKIP_NON_BACKUPABLE_STATE_DB=TRUE" -N "MSSQL$SQ12INST4#sql2012-aag3:DB" "MSSQL$SQ12INST4#sql2012-aag3:database1" "MSSQL$SQ12INST4#sql2012-aag3:database3" "MSSQL$SQ12INST4#sql2012-aag3:database8"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

Sample T-SQL script to back up a specific database of an Always On availability group

USE [master] GO DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_backup '-c SQL2012clus3.brsvlab.local - S 4 -l full -y +30d -a "NSR_DFA_SI_DD_HOST=ddve-01" -a "NSR_DFA_SI_DD_USER=sqlboost" -a "NSR_DFA_SI_PATH=/sqlboost" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C:\ProgramFiles\DPSAPPS\common\lockbox" -a "NSR_SKIP_NON_BACKUPABLE_STATE_DB=TRUE" -N "MSSQL$SQ12INST4#sql2012-aag3:database1" "MSSQL$SQ12INST4#sql2012-aag3:database1"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

102 Performing Self-Service Backups of Microsoft SQL Server Databases

Performing Self-Service Restores of Microsoft SQL Server Databases

Topics:

Restoring a Microsoft SQL Server application host Best practices to restore Microsoft SQL Server with Application Direct Restoring Microsoft SQL Server databases Performing table-level recovery Performing Microsoft SQL Server disaster recovery

Restoring a Microsoft SQL Server application host You can use the Microsoft application agent to restore the database or table-level backups directly to the Microsoft SQL Server application host.

NOTE: The Microsoft application agent does not support the quick recovery feature with PowerProtect Data Manager. The

PowerProtect Data Manager Administration and User Guide provides more information about the quick recovery feature.

The following topics provide instructions on how to restore an application-aware Microsoft SQL Server backup.

Best practices to restore Microsoft SQL Server with Application Direct Consider the best practices to restore Microsoft SQL Server using Application Direct.

Configure connection settings

DD Boost devices do not distinguish among Transmission Control Protocol (TCP)/Internet Protocol (IP), Fibre Channel (FC), and LAN, WAN, and MAN network types. DD Boost devices can successfully operate where packet loss is strictly 0% and latency is less than 20 ms.

Enable instant file initialization

For better restores, enable the instant file initialization feature on Microsoft SQL Server. The Microsoft SQL Server initialization procedure writes zeros to the portion of the disk that contains the data and the log files. Enabling the instant file initialization feature does not enable zeroing of the disk for the data files.

Configure usage limits for DD streams

Configure a sufficient number of DD streams for better performance of backups and restores. The streams control backup and restore parallelism for each database.

The Microsoft application agent requires one stream per save set that you back up or restore. When you perform striped backups, each stripe requires one stream. The stripes are concurrently run for each database. Databases are sequentially backed up and restored. When you use stripes, the number of streams must be equal to or more than the number of stripes.

The minimum number of streams for a non-stripe environment is 1.

5

Performing Self-Service Restores of Microsoft SQL Server Databases 103

Configuring usage limits of DD streams provides more information about streams limit, impact of exceeding the limits, and configuring the usage limits.

Restoring Microsoft SQL Server databases The Microsoft application agent for Application Direct with Microsoft SQL Server supports multiple tools to recover databases.

You can recover databases using the Microsoft application agent SQL Server Management Studio plug-in (GUI), Microsoft application agent for Application Direct commands, or T-SQL scripts.

Prerequisites

Learn about prerequisites for database restores.

Prerequisites for restoring a database to a remote server

Learn how to restore a database to a remote Microsoft SQL Server instance.

The Microsoft application agent supports browsing and restoring backups to a remote server.

Restore operations to a remote server are supported through the Application Direct SQL Server Management Studio (SSMS) plug-in only.

The Microsoft application agent and Application Direct SSMS plug-in must be installed on the Microsoft SQL Server where you will configure the restore operation. Using the SSMS plug-in, you can browse Microsoft SQL Server backups from any server on the DD storage unit and set the target destination to the remote server where you want to restore the data.

Prerequisites

Ensure that your environment meets the following requirements:

The Microsoft application agent must be installed on the target remote instance. Configure the same lockbox on the target remote instance as the lockbox on the instance where you configure the restore

operation.

For example, if the instance where you are running the restore has a lockbox with DataDomain1 and StorageUnit1, you must create the same lockbox with DataDomain1 and StorageUnit1 on the target remote instance.

The SQL Server Agent must be running on the target remote instance.

If the remote instance is on the same domain as the server where you are configuring the restore operation, the Microsoft application agent starts the SQL Server Agent automatically during the restore operation. If the remote server is on a different domain, then you must launch the SQL Server Agent on the target server manually.

You should be able to connect with the remote instance using the Connect to Server option in the SQL Server Management Studio.

If you cannot connect to the remote instance, the restore will fail.

Prerequisite to restore a database in an Always On availability group

To restore a database that is part of an Always On availability group, before you start the restore operation, you must remove the database from the Always On availability group.

Re-add the database to the availability group after the restore operation is complete.

104 Performing Self-Service Restores of Microsoft SQL Server Databases

Restore a database with the Microsoft app agent for Application Direct plug-in

The Microsoft application agent supports a user interface to perform restore operations through a SQL Server Management Studio (SSMS) plug-in.

The Microsoft application agent caches Microsoft SQL Server restore settings. The Microsoft application agent automatically loads the information from the last recovery operation and populates restore settings. Caching saves time by eliminating the need to reselect the settings each time you run a restore operation. To clear the cached settings, click Clear Cache.

The Script option is available in each page of the Database Restore tab, which generates a command prompt equivalent script. You can use the script to create a .bat file to perform automation and other tasks. The following script options are available:

CLI Scripts: To generate the command script, which you can use to run a restore from the command prompt. T-SQL Scripts: To generate a restore script in the T-SQL format.

Launching the Microsoft application agent for Application Direct SSMS plug-in

To launch the Microsoft application agent for Application Direct SSMS plug-in, perform the following steps. 1. From the Windows Start menu, select Microsoft SQL Server Management Studio. 2. In the Microsoft SQL Server Management Studio, in the Connect to Server window, specify the server information and

credentials, and then click Connect. 3. On the toolbar, click Microsoft App Agent (Application Direct).

NOTE: If the Microsoft App Agent (Application Direct) button is not on the toolbar, the plug-in may be unable to

register. In this scenario, you can launch the plug-in directly from the Start menu. From the Windows Start menu, select

DDBMA Plugin for SQL Server Management Studio.

Configure general restore settings

To configure Microsoft SQL Server restores with the Microsoft app agent for Application Direct SSMS plug-in, you must first specify general restore options on the Database Restore > General page.

Steps

1. Open the Microsoft app agent for Application Direct window to the Database Restore > General page.

The General page appears as shown in the following figure.

Performing Self-Service Restores of Microsoft SQL Server Databases 105

Figure 10. Application Direct - Database Restore-General page

The Microsoft application agent automatically loads the information from the last recovery operation and populates all of the fields under Sources. To clear the cached settings, click Clear Cache.

2. In the PowerProtect DD System field, select the DD server that contains the backup.

NOTE: When you want to restore a replicated backup from a secondary DD server, select the secondary server. The DD

user on the secondary DD server must be in the same group as the primary server.

3. From the SQL Server host list, select the Microsoft SQL Server host that is the source of the backup. Select the Windows cluster name in the case of federated backups.

4. From the SQL Server Instance list, select the Microsoft SQL Server instance that contains the databases that you want to restore.

The databases located on the Microsoft SQL Server instance appear in the database table below the SQL Server Instance field.

5. From the database table, select either the entire Microsoft SQL Server instance by selecting the check box in the header row or select only the required databases to restore.

The save sets on the Microsoft SQL Server instance that are available for recovery appear in the save sets table below the Browse time field.

By default, the restore process selects the most recent backup timestamp for each selected database. If you have selected a single database, you can perform a point-in-time (PIT) restore.

6. (Optional) To perform a point-in-time restore of a single database, perform the following steps:

a. From the Browse time list, select a date and time, and click Show Versions.

All of the backups that were performed within the specified timeline appear in the save sets table.

b. From the save sets table, select the save set with the timestamp that you want to restore.

106 Performing Self-Service Restores of Microsoft SQL Server Databases

Click < < Older or Newer > > to browse additional save sets.

NOTE: You cannot perform a PIT restore of multiple databases.

7. (Optional) To select the backup timestamp, perform the following steps

By default, the most recent timestamp is used.

a. Click Timeline. The Backup Timeline dialog box appears, as shown in the following figure.

Figure 11. Specifying the restore point b. Select the backup timestamp, and then click OK.

8. Choose the location where the backup is restored to: To perform a recovery directly to the database, perform the following steps:

a. Select Restore to SQL Server. b. From the Instance list, select the instance where you want to restore the database.

You can restore the database to the source instance or an alternate instance.

If you are restoring the database to an instance on a remote Microsoft SQL Server that is not listed, perform the following steps:

i. From the Instance list, select Browse for more.

The Connect to Server window appears.

ii. In the Connect to Server window, beside Server Name, click ... to load the Microsoft SQL Server Instances on the network.

iii. In the Server Name field, type the instance name or select the name from the list. iv. From the Authentication list, select one of the following authentication modes to connect to the Microsoft SQL

Server: Select Windows Authentication when you are restoring to a host in the same domain. Select SQL Server Authentication when you are restoring to a host in a different domain

v. Type the login credentials in the Login and Password fields. vi. To access the SQL Agent Service with a proxy user, under Proxy User Of SQL Agent, type the login credentials

in the User Name and Password fields. You must type the username in the format of Domain Name\User Name.

Specify the proxy user credentials if the SQL Agent Service user does not have sufficient permissions to perform a restore operation or if you want to perform restore as a different user.

If the SQL Agent Service on the target server uses a Windows Domain account and you select Windows Authentication, the proxy user credentials are optional.

vii. Click OK. c. From the Database list, select the database where the backup will be recovered to.

To perform a flat-file recovery, perform the following steps: a. Select Restore backups as files. b. In the Folder field, specify the destination for the files. The Folder field is populated with the default destination

path.

9. To start the restore operation, click Run.

Performing Self-Service Restores of Microsoft SQL Server Databases 107

Configure files and filegroup restore settings

When you configure Microsoft SQL Server restores with the Microsoft app agent for Application Direct SSMS plug-in, you change the default destination folders of the database files (.mdf and .ndf) and log files (.ldf) on the Database Restore > Files/Filegroups page.

About this task

All settings on the Files/Filegroups page are optional. NOTE: Settings on the Files/Filegroups page are disabled when you configure a restore to a remote server, including

changing the restore path.

Steps

1. From the left panel, click Files/Filegroups.

The Files/Filegroups page appears as shown in the following figure.

Figure 12. Application Direct - Database Restore-Files page

2. Under Filegroup Options, to display the corresponding database files of the databases that you have selected on the General page, from the Select Filegroup to restore list, select one of the following options: All Files: Displays the database files of all the selected databases.

PRIMARY: Displays the database files of the selected databases that belong to the PRIMARY filegroup only.

Custom filegroup name: Displays the database files of the selected databases that belong to the selected custom filegroup name only. In the figure, the custom filegroup names are sec and third.

3. Under Relocation Options, to change the destination restore paths, perform one of the following action sequences: To change the destination paths of all of the data and log files, perform the following steps:

108 Performing Self-Service Restores of Microsoft SQL Server Databases

a. Select Relocate all files to folder. b. Click the Data file folder browse button to specify a location for the data files, or click inside the field to type the

folder path. c. Click the Log file folder browse button to specify a location for the log files, or click inside the field to type the

folder path. To change the destination path for each individual data or log file, perform one of the following actions in the files table:

To browse for a destination path, click the browse button to the right of each data or log file. A window appears where you can browse and select the file path.

To type a new destination path, in the Restore As column, click the appropriate cell and type a destination path. If the path does not exist, a dialog box appears asking if you want to create the folder.

NOTE: The settings under Relocation Options are disabled if you have selected the Restore backups as files option

on the General page.

4. To start the restore operation, click Run.

Configure optional database restore settings

When you configure Microsoft SQL Server database restores with the Microsoft app agent for Application Direct SSMS plug-in, you can specify optional restore settings on the Database Restore > Options page.

About this task

All settings on the Options page are optional.

Steps

1. From the left panel, click Options to specify optional restore settings.

The Options page appears as shown in the following figure.

Performing Self-Service Restores of Microsoft SQL Server Databases 109

Figure 13. Application Direct - Database Restore-Options page

2. To overwrite the existing database with the restored data, select Overwrite the existing database (WITH REPLACE). The database is overwritten only if the database name is unchanged.

If you selected the Restore backups as files option, this option is disabled.

NOTE: After you perform a system database rebuild in the Microsoft SQL Server, you must specify the WITH REPLACE option with the ddbmsqlrc.exe command when you restore the system databases, including master,

model, and msdb.

3. To specify a recovery state, select one of the following options in the Recovery state field: RESTORE WITH RECOVERY: To leave the database in the ready-to-use state by rolling back uncommitted

transactions, and disable the ability to restore the most recent or additional transaction logs. RESTORE WITH NORECOVERY: To leave the database in the non-operational state by not rolling back uncommitted

transactions, and enable the ability to restore the most recent or additional transaction logs. RESTORE WITH STANDBY: To enable the ability to undo committed transactions, save the undo actions in a standby

file that enables you to reverse the restore effects, and put the database in the read-only mode. If you select this option, specify the Standby file field by clicking the button that is located on the right of the field, browsing for the file, and then selecting it.

4. To perform a verify only operation, select Verify only.

A verify only operation verifies that the restore process meets the following requirements without performing the restore operation: The backup set that you want to restore is complete and all volumes are readable Header fields, such as database page IDs are ready to write data Whether the checksum is proper if the backup was performed by selecting the Perform checksum before writing to

media option Whether the destination host has sufficient space to restore data

110 Performing Self-Service Restores of Microsoft SQL Server Databases

NOTE:

The Verify only option requires sufficient space on the client host to operate.

If you select the Restore backups as files option, this option is disabled.

5. To compress the restore contents and transport them from the DD Replicator to the application host, select PowerProtect DD System Boost compressed restore.

This option reduces the impact on network bandwidth.

6. To generate detailed logs, which you can use to troubleshoot any restore issues, specify a number between 1 and 9 in the Select a debug level field. The default value is 0 (zero).

7. To delete debug logs older than a certain number of days, in the Delete debug logs after field, specify the number of days with a number between 1 and 32767 days. The default value is 0 and does not delete any debug logs.

Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

NOTE: This option only deletes debug logs named in the default format and located in the logs folder at

\MSAPPAGENT\logs.

8. To restore all the backups that were performed during or after a specified start time and up until the time of the backup that is being restored, select Specify a start time for restore.

Specify the start date and time in the corresponding fields beside the Specify a start time for restore field. The start date and time must be before the backup time of the save set that is being restored.

9. To specify advanced recovery options, use the Advanced options field to select or type advanced recovery options.

Separate multiple entries with a comma, for example:

BUFFERCOUNT=2, KEEP_CDC, KEEP_REPLICATION The following advanced recovery options are supported:

BUFFERCOUNT=buffer_number: Specifies the total number of IO buffers that can be used during recovery.

KEEP_CDC: Enables change data capture (CDC) recovery.

When restoring a database with CDC enabled, the recover operation works differently depending on the recovery destination.

Use the KEEP_CDC option to:

Recover the CDC enabled database on the same Microsoft SQL Server instance by overwriting an existing database.

In this scenario, KEEP_CDC is optional.

Recover the CDC enabled database with a different name on the same Microsoft SQL Server instance.

In this scenario, KEEP_CDC is required.

Recover the CDC enabled database on a different Microsoft SQL Server instance.

In this scenario, KEEP_CDC is required.

KEEP_REPLICATION: Preserves the replication when recovering a published database. This option is required if a database was replicated when the backup was created.

10. To edit the number of save sets or versions that the Microsoft application agent cache retrieves, specify a number in the Number of entries to retrieve field.

You can specify a value of 1 through 10000. The default value is 50.

11. To perform a tail-log backup of the data before performing a restore operation, select Take tail-log backup before restore.

A tail-log backup ensures that the Microsoft application agent backs up the data that has changed since the previous backup.

NOTE:

The Microsoft application agent for Application Direct does not support tail-log backups of multiple databases.

This option is disabled if the Restore backups as files or Verify only options are selected.

12. To ensure exclusive access to the database during the restore operation if multiple connections exist, select Close existing connections to destination database.

13. To start the restore operation, click Run.

Performing Self-Service Restores of Microsoft SQL Server Databases 111

Monitor the restore operation

After a database restore operation is run from the Microsoft app agent for Application Direct SSMS plug-in, the Database Restore > Monitor page displays the restore script and status.

The following figure shows the restore information and status as it appears on the Monitor page.

Figure 14. Application Direct - Database Restore-Monitor page

NOTE: For information about the success or failure of the restore operation, review the log files that are located in the

installation folder. The typical location of the log files is C:\Program Files\DPSAPPS\MSAPPAGENT\logs.

Perform database restores with the Microsoft application agent for Application Direct recover command

Use the ddbmsqlrc command to configure a restore of Microsoft SQL Server databases from a command prompt.

NOTE: In the syntaxes, the options that are enclosed in square brackets, that is, [ and ] are optional.

To perform specific backup-related and restore-related operations, the Microsoft application agent also supports the ddbmadmin.exe command besides the msagentadmin.exe command. However, the ddbmadmin.exe command is deprecated.

112 Performing Self-Service Restores of Microsoft SQL Server Databases

Syntax to restore databases on a stand-alone server

Run the following command to restore databases in a stand-alone environment:

ddbmsqlrc.exe -c -S {normal | norecover | standby: \undo.ldf} -a "NSR_DFA_SI_DD_HOST= " -a "NSR_DFA_SI_DD_USER= " -a "NSR_DFA_SI_DEVICE_PATH= " [ ] " "

where:

-c

Specifies the Microsoft SQL Server hostname, to which you want to restore the required databases. A Microsoft SQL Server host contains the backed-up stand-alone or clustered Microsoft SQL Server instances and the corresponding databases.

-S {normal | norecover | standby: \undo.ldf}

Performs one of the following tasks: normal: Enables you to roll back uncommitted transactions and use the database to restore the

most recent or additional transaction logs. norecover: Disables your ability to roll back uncommitted transactions and use the database to

restore the most recent or additional transaction logs. standby: \undo.ldf: Enables you to undo committed transactions, saves the undo actions

in a standby file that enables you to reverse the restore effects, and puts the database in the read-only mode.

-a "NSR_DFA_SI_DD_HOST= "

Specifies the name of the DD server that contains the backup.

When you have a remote (secondary) DD server that has replicated databases to restore, type the name of the secondary server. A DD user on the secondary DD server must be in the same group as the primary server.

-a "NSR_DFA_SI_DD_USER= "

Specifies the username of the DD Boost user.

You must register the hostname and the DD Boost username in the lockbox to enable Microsoft application agent to retrieve the password for the registered user.

-a "NSR_DFA_SI_DEVICE_PATH= "

Specifies the name and the path of the storage unit that contains the backup.

" "

Specifies the path to the backup objects that you want to restore.

Type the restore path in one of the following formats: For a default instance, type the path in one of the following formats:

To restore backups of the entire instance, type MSSQL: To restore backups of specific databases, type [MSSQL:]

[[MSSQL:] [...]] For example: "MSSQL:database1" "MSSQL:database2"

For a named instance, type the path in one of the following formats: To restore backups of the entire instance, type MSSQL$ : To restore backups of specific databases, type MSSQL$ :

[...] For example: "MSSQL$SqlInst1:database1" "MSSQL$SqlInst1:database2"

Microsoft SQL Server stand-alone restore command

ddbmsqlrc.exe -c sqlx86.adesc.com -t "Monday, November 11, 2013 1:05:47 PM" -S normal -a "NSR_DFA_SI_DD_HOST=10.31.77.27" -a "NSR_DFA_SI_DD_USER=arti1" -a "NSR_DFA_SI_DEVICE_PATH=/artrep2" "MSSQL$SQL2K8:testddr1"

Performing Self-Service Restores of Microsoft SQL Server Databases 113

Syntax to restore databases in an Always On availability group

Run the following command to restore databases in an Always On availability group environment:

ddbmsqlrc.exe -c -A -S {normal | norecover | standby: \undo.ldf} -a "NSR_DFA_SI_DD_HOST= " -a "NSR_DFA_SI_DD_USER= " -a "NSR_DFA_SI_DEVICE_PATH= " [ ] " "

Run the following command to restore databases in a clusterless Always On availability group (AAG) environment:

ddbmsqlrc.exe -a "SKIP_CLIENT_RESOLUTION=TRUE" -c _ -S {normal | norecover | standby: \undo.ldf} -a "NSR_DFA_SI_DD_HOST= " -a "NSR_DFA_SI_DD_USER= " -a "NSR_DFA_SI_DEVICE_PATH= " [ ] " "

NOTE: For a clusterless AAG, you must add the option -a "SKIP_CLIENT_RESOLUTION=TRUE" and specify

_ with the -c option.

where:

-c

Specifies the Windows cluster name for the restore.

To perform a redirected restore, specify a Microsoft SQL Server host that is not the current host.

-c _

Specifies the clusterless AAG for the restore, for example, -c AAG1_ef770eaf-ebe3-f5be- bdff-3a7243ff1236.

-A

Specifies the virtual server FQDN to restore the databases from the Microsoft SQL Server clustered instance.

NOTE: The -A option does not apply to clusterless AAG restores.

-S {normal | norecover | standby: \undo.ldf}

Performs one of the following tasks: normal: Enables you to roll back uncommitted transactions and use the database to restore the

most recent or additional transaction logs. norecover: Disables your ability to roll back uncommitted transactions and use the database to

restore the most recent or additional transaction logs. standby: \undo.ldf: Enables you to undo committed transactions, saves the undo actions

in a standby file that enables you to reverse the restore effects, and puts the database in the read-only mode.

-a "NSR_DFA_SI_DD_HOST= "

Specifies the name of the DD server that contains the backup.

When you have a remote (secondary) DD server that has replicated databases to restore, type the name of the secondary server. A DD user on the secondary DD server must be in the same group as the primary server.

-a "NSR_DFA_SI_DD_USER= "

Specifies the username of the DD Boost user.

You must register the hostname and the DD Boost username in the lockbox to enable Microsoft application agent to retrieve the password for the registered user.

-a "NSR_DFA_SI_DEVICE_PATH= "

Specifies the name and the path of the storage unit that contains the backup.

-a "SKIP_CLIENT_RESOLUTION=TRUE"

Specifies to skip the client resolution for _ , as specified with the -c option. Skipping the client resolution is required for a clusterless AAG restore.

114 Performing Self-Service Restores of Microsoft SQL Server Databases

" "

Specifies the path to the backup objects that you want to restore.

Type the backup path in one of the following formats: For a default instance, type the path in one of the following formats:

To restore backups of the entire instance, type MSSQL# : To restore backups of specific databases, type [MSSQL# :]

[[MSSQL# :] [...]] For example: "MSSQL#aag1:database1" "MSSQL#aag1:database2"

For a named instance, type the path in one of the following formats: To restore backups of the entire instance, type MSSQL$ # : To restore backups of specific databases, type

MSSQL$ # : [...] For example: "MSSQL$SqlInst1#sql2012-aag3:database1" "MSSQL$SqlInst1#sql2012-aag3:database2"

Microsoft SQL Server Always On availability group restore command

ddbmsqlrc.exe -c sqlcluster1.adesc.com -A sqlcluster1.adesc.com -t "Monday, November 11, 2013 1:05:47 PM" -S normal -a "NSR_DFA_SI_DD_HOST=10.31.77.27" -a "NSR_DFA_SI_DD_USER=arti1" -a "NSR_DFA_SI_DEVICE_PATH=/artrep2" "MSSQL$SqlInst1#sql2012- aag3:database2"

Microsoft SQL Server clusterless Always On availability group restore command

ddbmsqlrc.exe -a "SKIP_CLIENT_RESOLUTION=TRUE" -c clusterlessa_6f27c29c-5d83-0062-8301-357210660ac6 -S normal -a "NSR_DFA_SI_DD_HOST=10.31.140.154" -a "NSR_DFA_SI_DD_USER=ost" -a "NSR_DFA_SI_DEVICE_PATH=/aru" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C: \Program Files\DPSAPPS\common\lockbox" -C "'ClusterlessADB01'='H: \MSSQL14.MSSQLSERVER\MSSQL\DATA\ClusterlessADB01.mdf', 'ClusterlessADB01_log'='H: \MSSQL14.MSSQLSERVER\MSSQL\DATA\ClusterlessADB01_log.ldf'" -f -d MSSQL:ClusterlessADB01 MSSQL:ClusterlessADB01

Optional parameters for the ddbmsqlrc command

You can use the following optional parameters with the ddbmsqlrc command.

-a "NSR_DFA_SI_DD_LOCKBOX_PATH= "

Specifies the folder that contains the lockbox file, which contains encrypted information about the registered hosts and the corresponding usernames in pairs. Each pair is associated with a password that backups use. If you do not specify a value, the path defaults to the installation path, which is typically C:\Program Files\DPSAPPS\common\lockbox.

-t " "

Specifies the backup time stamp that you want to restore.

-a "NSR_ENABLE_FC={TRUE | FALSE}"

Enables database restoration to the DD server through Fibre Channel. The default value is FALSE.

-a "NSR_FC_HOSTNAME= "

Specifies the hostname of the Fibre Channel.

-a "FLAT_FILE_RECOVERY={TRUE | FALSE}"

Performs a flat file restore to files, that is, restores a save set that has a full backup and multiple transaction log and differential backups to files.

To know the order in which multiple transaction log backup files are restored, use the save times that are present in the filenames.

The default value is FALSE.

-a "FLAT_FILE_RECOVERY_DIR= "

Specifies the folder, in which the flat file restore files are generated.

Performing Self-Service Restores of Microsoft SQL Server Databases 115

You can see the generated files in the \ \ location.

-a "DDBOOST_COMPRESSED_RESTORE={TRUE | FALSE}"

Compresses the restore contents and transports them from the DD Replicator to the application host. This option saves network bandwidth.

The default value is FALSE.

-a "RESTORE_START_TIME= "

Restores all the backups that were performed at or after a specified backup time (start date and time) and up to the backup time of the selected save set, that is, -t .

Specify the start date and time in the /

/
: : {AM | PM} format.

The start date and time must not be after the backup time of the selected save set, that is, -t .

-a "RESTORE_TO_SOURCE_PATH=TRUE"

Ensures that the backup is restored to the original source path by default. The -a "RESTORE_TO_SOURCE_PATH=TRUE" option is overridden if the -C or -H relocation options are used.

-a "CLOSE_SQL_CONNECTIONS={TRUE | FALSE}

Specifies whether to enable exclusive access to the target database by changing the database to single user mode during the restore operation to ensure a successful recovery.

-$

Specifies the target Microsoft SQL Server instance that contains the target databases that you want to restore. The default value is the instance where the backup was taken.

Type the value in one of the following formats: For the default instance, type MSSQL For a named instance, type MSSQL$

-d

Specifies the target database, to which you want to restore the backup.

Type the value in one of the following formats: MSSQL: MSSQL$ :

-C file=path,file2=path2,...

Relocates the database files (.mdf, .ndf, and .ldf) to a different folder.

You cannot use the -C parameter and the -H parameter in the same operation.

-H " ' ';' '"

Relocates file paths and all files contained in a path to a different location during a restore operation.

The -H command option can be used to relocate multiple file paths in the same command line.

The -H option is supported on standard and redirected restores, which includes the following:

Normal restoreSame server and same instance. Different instance restoreSame server and different instance. Restore to different database file. Different server restore.

To relocate individual files, see the table entry for the -C option.

You cannot use the -C option and the -H option in the same operation.

-f

Overwrites the existing database with the current database that you restore if the names of both the databases are same.

NOTE: After you perform a system database rebuild in the Microsoft SQL Server, you must specify

the WITH REPLACE option with the ddbmsqlrc.exe command when you restore the system

databases, including master, model, and msdb.

116 Performing Self-Service Restores of Microsoft SQL Server Databases

-q

Displays ddbmsqlsv messages in the quiet mode, that is, the option displays summary information and error messages only.

-k

Specifies to perform a checksum before restoring the data.

-u

Specifies to perform a checksum before the restore operation but to proceed with the operation even in the case of errors.

-D

Generates detailed logs that you can use to troubleshoot backup issues. The default value is 0 (zero).

-a "DELETE_DEBUG_LOG_DAYS= "

Specifies to delete debug log files that are older than the specified number of days. The valid range is between 1 and 32767. By default, debug logs are not deleted. Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

This parameter only deletes debug logs named in the default format and located in the logs folder at \MSAPPAGENT\logs.

-V

Verifies whether the restore process meets the following requirements: The backup set that you want to restore is complete and all volumes are readable Header fields, such as database page IDs, are ready to write data Whether the backup was performed by using the checksum option Whether the destination host has sufficient space to restore data

-l incr

Restores from the last transaction log backup.

When you use the -l incr option, you must restore the backup chain in order. For example, consider the following backup history:

A full backup taken at 1:31:49PM A logs only backup taken at 1:32:42PM A logs only backup taken at 1:34:03PM A logs only backup taken at 1:34:50PM

To restore this backup chain, perform the following steps:

1. Type the following command to restore up to the second last transaction log backup:

ddbmsqlrc.exe -a NSR_DFA_SI_DD_HOST=10.34.156.120 -a NSR_DFA_SI_DD_USER=ost -a NSR_DFA_SI_DEVICE_PATH=/msappstu4 -a NSR_DFA_SI_DD_LOCKBOX_PATH=C:\Program Files\DPSAPPS\common\lockbox -c mars-jupiter.planets.com -a SKIP_CLIENT_RESOLUTION=TRUE -f -t 09/06/2017 01:34:03 PM -S norecover MSSQL$TESTDB02:info3

2. Type the following command to restore the last transaction log backup with -l incr:

ddbmsqlrc.exe -a NSR_DFA_SI_DD_HOST=10.34.156.120 -a NSR_DFA_SI_DD_USER=ost -a NSR_DFA_SI_DEVICE_PATH=/msappstu4 -a NSR_DFA_SI_DD_LOCKBOX_PATH=C:\Program Files\DPSAPPS\common\lockbox -c mars-jupiter.planets.com -a SKIP_CLIENT_RESOLUTION=TRUE -f -l incr -S normal MSSQL$TESTDB02:info3

-O " , , ..."

Specifies advanced recovery options. Separate each option with a comma.

The following table describes the advanced recovery options that are available:

BUFFERCOUNT= : Specifies the total number of IO buffers that can be used during a recovery operation.

KEEP_CDC: Enables change data capture (CDC) recovery.

KEEP_REPLICATION: Preserves the replication when you recover a published database. This option is required if a database was replicated when the backup was created.

Performing Self-Service Restores of Microsoft SQL Server Databases 117

READ_WRITE_FILEGROUPS: Recovers only the read/write (active) filegroups from the backup. This option can only be used to recover backups performed with the READ_WRITE_FILEGROUPS option. You cannot specify filegroup or file-level recover targets with the READ_WRITE_FILEGROUPS option.

If you are relocating multiple filegroups during the restore, you can use the -H option for global relocation.

After you restore a backup with the READ_WRITE_FILEGROUPS option, any read-only filegroups in the database will enter the recovery pending state and the rest of the filegroups will go online.

There are two different scenarios to recover cumulative incremental READ_WRITE_FILEGROUPS backups:

If you have taken a full READ_WRITE_FILEGROUPS backup prior to the cumulative incremental backup, the Microsoft application agent will chain together the two backups in the correct order and complete the restore.

If you have not taken a full READ_WRITE_FILEGROUPS backup but want to use a normal full backup as the differential base for the cumulative incremental READ_WRITE_FILEGROUPS backup, you must first restore the full backup normally and leave the database in no recovery mode, and then apply the READ_WRITE_FILEGROUPS differential backup with the -z option.

-z

Enables implementation of a recovery plan in independent command line operations. Normally the Microsoft application agent builds the recovery plan, ensuring that all the required backups are available and that they run in the proper order and with the proper options. The -z option removes safety checks.

This option is used in more complex recoveries. The following example commands use the following backup history:

savetime 1:00 - full backup savetime 2:00 - txnlog backup savetime 3:00 - txnlog backup

To recover multiple backups and restore a database in a single command, run the following command:

ddbmsqlrc ... -t "savetime 3:00" ...

This command recovers the entire recovery chain, from the first full backup to the last logs-only backup.

To recover this recovery chain and restore a database in a series of independent commands, run the following commands:

ddbmsqlrc ... -z -S norecover -t "savetime 1:00" ...

ddbmsqlrc ... -z -S norecover -t "savetime 2:00" ...

ddbmsqlrc ... -z -S normal -t "savetime 3:00" ...

These three commands recover each backup individually.

The -z option disables building the recovery plan and recovers only the specified backup. This command is required for all backups except for level full backups.

Use the -S norecover option with the -z option to prepare the database for more restores. This command is required for all except the last recovery command. The final command recovers the last logs-only backup and brings the database online.

NOTE: A point-in-time restore within the final txnlog can be specified by replacing the save time.

For instance, in the previous example, you can replace 3:00 with 2:45. The database is not available

for general use until after the final recovery completes. Any missing, incorrect, or out-of-order save

times result in Microsoft SQL Server reporting errors.

Starting with Microsoft application agent 19.2, you can specify the ddbmsqlrc command option -S norecover when you restore a read-write (active) filegroup, which leaves the database in the recovering mode. In this mode, you can then apply subsequent transaction logs to complete a point-in- time restore of the active filegroup, for example, when backups are configured as in the following example. The following example commands use the following backup history:

118 Performing Self-Service Restores of Microsoft SQL Server Databases

savetime 6/21/2019 12:10:35 PM - full read/write filegroup backup with -O "READ_WRITE_FILEGROUPS" option

savetime 6/21/2019 12:21:30 PM - txnlog backup savetime 6/21/2019 12:25:34 PM - txnlog backup

To perform a point-in-time restore of the active filegroup, run the following commands:

1. Restore the filegroup backup in norecover mode:

ddbmsqlrc ... -z -f -t "06/21/2019 12:10:35 PM" -S norecover -O "READ_WRITE_FILEGROUPS" ...

2. Restore the second last log backup in norecover mode:

ddbmsqlrc ... -z -f -t "06/21/2019 12:21:30 PM" -S norecover ... 3. Complete the point-in-time restore in normal mode to a time before the final log backup:

ddbmsqlrc ... -z -f -t "06/21/2019 12:25:34 PM" -S normal ...

Perform database restores with T-SQL scripts

The Microsoft application agent for Application Direct enables you to generate a SQL-CLR script that you can use to restore Microsoft SQL Server databases.

The SQL-CLR restore command, emc_run_restore uses the Microsoft application agent for Application Direct with Microsoft SQL Server restore CLI options. You must also provide VARCHAR parameters to this command. To use this command, you must have a detailed knowledge of the Microsoft application agent for Application Direct with Microsoft SQL Server restore CLI options. Perform database restores with the Microsoft application agent for Application Direct recover command provides information about the Microsoft application agent for Application Direct with Microsoft SQL Server restore CLI options.

Sample T-SQL restore script

The following SQL-CLR script is an example of a restore script:

USE [master] GO DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_restore ' -c win8sqlsp.sharepoint.com -f -t "02/03/2015 04:04:36 AM" -S normal -a "NSR_DFA_SI_DD_HOST=10.31.192.10" -a "NSR_DFA_SI_DD_USER=ost" -a "NSR_DFA_SI_DEVICE_PATH=/ddsub7" -d "MSSQL:dbtest" "MSSQL:db100"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

You can use any Microsoft SQL Server standard interfaces, such as the SSMS Query window and OSQL command prompt tool, to run the SQL-CLR scripts.

Best practices to back up Microsoft SQL Server with Application Direct provides guidelines for better performance of Microsoft SQL Server restores by using the Microsoft application agent for Application Direct SQL-CLR scripts.

Performing Microsoft SQL Server push restores by using the Microsoft application agent for Application Direct T-SQL scripts

About this task

To restore either all databases or only the specific databases of a Microsoft SQL Server instance from a DD device to a destination host by using a different host, perform the following steps.

NOTE: When the data to be restored exists in a Cloud Tier, perform a recall operation prior to the push restore operation.

Performing Self-Service Restores of Microsoft SQL Server Databases 119

Steps

1. Start SSMS on a different host that you use to perform the restore.

2. Connect to the destination Microsoft SQL Server instance on the destination host.

3. In the SSMS window on the different host, click New Query.

4. In the New Query window, run the T-SQL script to perform the restore.

Results

You can either generate the T-SQL script by using the Microsoft application agent SSMS plug-in GUI on the destination host and copy it to the New Query window on the different host or write the T-SQL script in the New Query window. Restore a database with the Microsoft app agent for Application Direct plug-in and Perform database restores with T-SQL scripts provide information.

T-SQL push restore script

Consider the following example T-SQL push restore script:

USE [master] GO DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_restore ' -c clust-sql-01.contoso.com -A clust-sql-02.contoso.com -f -t "06/22/2015 02:38:48 PM" -S normal -a "NSR_DFA_SI_DD_HOST=nmmddtwo.sp2010.com" -a "NSR_DFA_SI_DD_USER=ost" -a "NSR_DFA_SI_DEVICE_PATH=/ddbmav2b75" -d "MSSQL$Inst1:CLUST-SQL-02- DB02" "MSSQL$Inst1:CLUST-SQL-02-DB01"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

where:

clust-sql-01.contoso.com is the source host from which the backup was performed.

Inst1 is the destination Microsoft SQL Server instance, to which you must connect from the different host to perform the restore.

CLUST-SQL-02-DB02 is the destination database.

CLUST-SQL-02-DB01 is the database that was backed up from the source host.

Restoring Always On availability groups by using T-SQL scripts

To restore databases from federated backups, use the same restore command and options that Perform database restores with T-SQL scripts describes, but for in -c , specify the Windows cluster name.

The options in the following example scripts indicate the modification.

Sample T-SQL script to restore a federated backup to the source database

USE [master] GO DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_restore '-a "NSR_DFA_SI_DD_HOST=ddve-01" -a "NSR_DFA_SI_DD_USER=sqlboost" -a "NSR_DFA_SI_DEVICE_PATH=/sqlboost" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C: \Program Files\DPSAPPS\common\lockbox" -c sql2012clus3.brsvlab.local - C" 'testdb1_Data'='E:\sql2012_data\ database1.mdf', 'testdb1_Log'='F: \sql2012_log\database1_log.LDF'" -f -S normal -$ "MSSQL$SQ12INST4:" -d "MSSQL$SQ12INST4:database1" "MSSQL$SQ12INST4:database1"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

Sample T-SQL script to restore a federated backup to a different instance and database (redirected restore)

USE [master] GO DECLARE @returnCode int

120 Performing Self-Service Restores of Microsoft SQL Server Databases

EXEC @returnCode = dbo.emc_run_restore '-a "NSR_DFA_SI_DD_HOST=ddve-01" -a "NSR_DFA_SI_DD_USER=sqlboost" -a "NSR_DFA_SI_DEVICE_PATH=/sqlboost" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C: \Program Files\DPSAPPS\common\lockbox" -c sql2012clus3.brsvlab.local - C" 'testdb1_Data'='E:\sql2012_data\database1.mdf', 'testdb1_Log'='F: \sql2012_log\database1_log.LDF'" -f -S normal -$ "MSSQL$SQ12INST4:" -d "MSSQL$SQ12INST5:copy-database1" "MSSQL$SQ12INST4:database1"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

Sample T-SQL script to restore multiple databases of a federated backup

NOTE: When you restore multiple databases, do not use the -C and -d options with the T-SQL restore command. If you do,

the restore fails.

USE [master] GO DECLARE @returnCode int EXEC @returnCode = dbo.emc_run_restore '-a "NSR_DFA_SI_DD_HOST=ddve-01" -a "NSR_DFA_SI_DD_USER=sqlboost" -a "NSR_DFA_SI_DEVICE_PATH=/sqlboost" -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C: \Program Files\DPSAPPS\common\lockbox" -c sql2012clus3.brsvlab.local - f -S normal -$ "MSSQL$SQ12INST4:database1" "MSSQL $SQ12INST4:database2"' IF @returnCode <> 0 BEGIN RAISERROR ('Fail!', 16, 1) END

Performing table-level recovery The Microsoft application agent supports table-level recovery of Microsoft SQL Server data using the Microsoft app agent for Application Direct SSMS plug-in.

The Microsoft application agent does not support the Script option to perform table restores using a command prompt or T-SQL scripts.

Table-level restore workflow

When you install the Microsoft application agent, you must install ItemPoint to perform table-level restores. Otherwise, the Table Restore tab does not appear in the Microsoft app agent for Application Direct SSMS plug-in. During the Microsoft application agent installation, you can select the provided check box to install ItemPoint.

NOTE: ItemPoint 8.6.1 as integrated with the Microsoft application agent now supports the Microsoft SQL Server

Transparent Data Encryption (TDE). However, only the AES_128, AES_192, and AES_256 encryption algorithms are

supported.

To perform table-level restores, you must first mount the backup images and specify mount options by using the Microsoft app agent for Application Direct SSMS plug-in. Once the backup is mounted, use ItemPoint for Microsoft SQL Server to complete the table restore.

CAUTION: In the scenario where you have large databases where a large amount of data is recently committed

to the databases, a table restore may not be appropriate.

Committed data is represented as outstanding transactions when there are Microsoft SQL Server full and incremental backups on the database. When you perform table-level recovery, ItemPoint must load all the outstanding transactions that are present in a backup.

To load large databases, ItemPoint requires a few hours to read the data because of poor Virtual File System performance. This problem occurs while ItemPoint loads the database and ItemPoint may appear to stop responding while reading the backup. If you observe this problem, an alternative to using Microsoft SQL Server table-level recovery is to restore the backup as flat files to a server where you have enough space, and then use ItemPoint to restore the files on the local disk.

Performing Self-Service Restores of Microsoft SQL Server Databases 121

Launching the Microsoft application agent for Application Direct SSMS plug-in

To launch the Microsoft application agent for Application Direct SSMS plug-in, perform the following steps. 1. From the Windows Start menu, select Microsoft SQL Server Management Studio. 2. In the Microsoft SQL Server Management Studio, in the Connect to Server window, specify the server information and

credentials, and then click Connect. 3. On the toolbar, click Microsoft App Agent (Application Direct).

NOTE: If the Microsoft App Agent (Application Direct) button is not on the toolbar, the plug-in may be unable to

register. In this scenario, you can launch the plug-in directly from the Start menu. From the Windows Start menu, select

DDBMA Plugin for SQL Server Management Studio.

Configure general table restore settings

To configure Microsoft SQL Server table-level restores with the Microsoft app agent for Application Direct SSMS plug-in, you must first specify general table restore options on the Database Restore > General page.

Steps

1. Open the Microsoft app agent for Application Direct window to the Table Restore > General page.

The General page appears as shown in the following figure.

Figure 15. Application Direct - Table Restore-General page

The Microsoft application agent caches Microsoft SQL Server restore settings. The Microsoft application agent automatically loads the information from the last recovery operation and populates restore settings. Caching saves time

122 Performing Self-Service Restores of Microsoft SQL Server Databases

by eliminating the need to reselect the settings each time you run a restore operation. To clear the cached settings, click Clear Cache.

2. Use the PowerProtect DD System field to select the DD server and the storage unit to restore the data. A storage unit contains the backed-up Microsoft SQL Server hosts.

NOTE: When you want to restore a replicated backup from a secondary DD server, select the relevant server. The DD

user on the secondary DD server must be in the same group as the primary DD server.

3. From the SQL Server host list, select the Microsoft SQL Server host that contains the backup. Select the Windows cluster name in the case of federated backups.

To perform a redirected restore, select the Microsoft SQL Server host where you want to restore the backup to.

4. From the SQL Server Instance list, select the Microsoft SQL Server instance that contains the backup.

5. From the Database list, select the database that you want to restore. The corresponding save sets appear in the save sets table that is located below the Browse time field.

6. To select the backup that you want to restore, perform either of the following actions: Select a save set in the save sets table that is located below the Browse time field. Use the backup timestamp to

choose the backup. To browse for a backup that is not listed, perform the following steps:

From the Browse time list, select a date and time, and then click Show Versions. From the save sets table, select the save set with the timestamp that you want to restore.

Click < < Older or Newer > > to browse additional save sets.

7. To mount the backup and proceed with the table restore, click Run.

Results

The backup is mounted and the ItemPoint for Microsoft SQL Server GUI appears.

Configure optional table restore settings

When you configure Microsoft SQL Server backups with the Microsoft app agent for Application Direct SSMS plug-in, you can specify optional backup settings on the Table Restore > Options page.

About this task

All settings on the Options page are optional.

Steps

1. From the left panel, click Options.

The Options page appears as shown in the following figure.

Performing Self-Service Restores of Microsoft SQL Server Databases 123

Figure 16. Application Direct - Table Restore-Options page

All settings on the Options page are optional.

2. In the Mount Folder field, specify the location to mount the backup images.

NOTE: The location (folder or drive) to mount the backup images must be empty. Otherwise, the mount operation fails.

To mount the backup as a drive, specify an unused drive letter. The restore operation, after completion, deletes the

mount location.

3. In the Mount Expire list, specify the number of hours, after which the mounted backup image must be dismounted. The default value is 8. The valid range is between 1 and 24 hours.

4. To select the level of information recorded in the logs which can be used in troubleshooting recovery issues, select Select a debug level.

Levels range 0-9, with 0 representing no information and 9 representing the most amount of information. The default value is 0 (zero).

5. To change the restore parallelism setting, type or select a value in the Parallelism field.

Parallelism controls the number of recovery sessions the NWFS process uses while mounting a backup. The default and maximum value is 31.

6. To mount the backup and proceed with the table restore, click Run.

Results

The backup is mounted and the ItemPoint for Microsoft SQL Server GUI appears.

124 Performing Self-Service Restores of Microsoft SQL Server Databases

Monitor the table restore mount operation

After a table-level restore mount operation is run from the Microsoft app agent for Application Direct SSMS plug-in, the Table Restore > Monitor page displays the mount script and status.

The following figure shows the mount information and status as it appears on the Monitor page.

Figure 17. Application Direct - Table Restore-Monitor page

NOTE: For information about the success or failure of the restore operation, review the log files that are located in the

installation folder. The typical location of the log files is C:\Program Files\DPSAPPS\MSAPPAGENT\logs.

Restore table-level data using ItemPoint

After the backup images are mounted using the Microsoft application agent SSMS plug-in, complete the table-level restore using ItemPoint for Microsoft SQL Server.

Prerequisites

Configure and run the table level restore operation with the Table Restore tab in the Microsoft application agent SSMS plug-in.

NOTE: ItemPoint 8.6.1 as integrated with the Microsoft application agent now supports the Microsoft SQL Server

Transparent Data Encryption (TDE). However, only the AES_128, AES_192, and AES_256 encryption algorithms are

supported.

About this task

Once the table level restore is configured and run through the Microsoft application agent SSMS plug-in, ItemPoint launches.

Performing Self-Service Restores of Microsoft SQL Server Databases 125

If you select Do not run ItemPoint after mounting the backup images when you configure the table level restore, you must manually launch ItemPoint, and then launch the Data Wizard.

Steps

1. On the Select Source page, select the source backup files from the mounted volume that contains the Microsoft SQL Server backup data as shown in the following figure, and then click Next.

Figure 18. ItemPoint Data Wizard: select the source files

2. On the Select Target Server page, specify the details and login credentials for the target Microsoft SQL Server and database.

The following figure shows the ItemPoint Data Wizard Select Target Server page:

Figure 19. ItemPoint Data Wizard: select the target server

3. Click Finish. The Data Wizard closes and ItemPoint loads the tables contained in the source backup files.

4. Use ItemPoint to browse and restore the individual tables.

NOTE: The PowerProtect ItemPoint for Microsoft SQL Server User Guide provides more information on using ItemPoint

for Microsoft SQL Server to restore table-level data.

5. To dismount the mounted backup images, exit ItemPoint for Microsoft SQL Server.

126 Performing Self-Service Restores of Microsoft SQL Server Databases

NOTE: If you select Leave backup images mounted after ItemPoint exits or Do not run ItemPoint after

mounting the backup images when you configure the mount operation, the backup image remains mounted for 4

hours. To dismount the backup manually, use the msagentadmin command.

Performing Microsoft SQL Server disaster recovery When a disaster scenario occurs, the Microsoft application agent supports disaster recovery of data located on both a DD server and Cloud Tier.

Perform Microsoft SQL Server disaster recovery

The Microsoft application agent for Application Direct supports disaster recovery.

Steps

1. Create a target Windows host with the same name as the source hostname.

2. Install a Microsoft SQL Server instance with the same name as the source instance name.

3. Install the Microsoft application agent on the target Windows host.

4. Browse the backups of the source instance by selecting the appropriate storage unit.

5. Restore the Microsoft SQL Server system databases, such as databases named master, model, msdb, and so on, to the target instance.

6. Restore all the user databases to the target instance.

Perform disaster recovery from the Cloud Tier

The Microsoft application agent provides a command line tool to complete disaster recovery of save sets that are located in a Cloud Tier.

After an MTree is recovered according to the disaster recovery procedure described in Perform Microsoft SQL Server disaster recovery, you must restore the backup indexes from the Cloud Tier.

When the Microsoft application agent moves a backup to the cloud, the index files are maintained on the active tier. A copy of the index files is created and moved to the cloud tier for long-term retention.

After an MTree is restored during a disaster recovery, all the files that resided only on the active tier are lost and unavailable. Only the files that were moved to the cloud are available.

In this case, you must run msagentadmin administration with the --dr-recall or -M flag to restore the indexes.

After the indexes are recalled to the active tier, the data save sets for the same time range are also recalled unless you type n when prompted with Continue with the recall of the found save sets [y/n]. If you choose to not recall the save sets, you can manually recall the save sets later.

Type the msagentadmin administration command with the following syntax to recall the indexes to the active tier:

msagentadmin administration --dr-recall --ddhost "<DD_server_name>" --ddpath "<storage_unit_name_and_path>" --dduser "<DD_Boost_username>" --appID "mssql"

where:

--dr-recall

Specifies an operation to recall save sets for disaster recovery.

You can use the -M alias for the --dr-recall parameter.

--ddhost " "

Specifies the name of the DD server that contains the storage unit, to which you backed up the databases.

--ddpath "<storage_unit_name_and_path>"

Specifies the name and the path of the storage unit, to which you backed up the databases.

Performing Self-Service Restores of Microsoft SQL Server Databases 127

--dduser "<DD_Boost_username>"

Specifies the username of the DD Boost user.

--appID "mssql"

Specifies the application ID (namespace) to locate backups.

You can use the -n alias for the --appID parameter.

Consider the following example commands to perform disaster recovery of Microsoft SQL Server with data located on a Cloud Tier device:

Cloud tier disaster recovery recall command without a configuration file

msagentadmin administration --dr-recall --tier --after 1481104962 --before 1481105533 -- appID mssql --ddhost "10.70.102.111" --ddpath "/mt1" --dduser "ost" --confirm --client SQLX86.adesc.com --debug 9

Cloud tier disaster recovery recall command with a configuration file

msagentadmin administration --dr-recall --tier --after 1481104962 --before 1481105533 -- appID mssql --confirm --config c:\temp\config_pp.txt --debug 9

128 Performing Self-Service Restores of Microsoft SQL Server Databases

Performing Centralized Restores of Application Direct Backups

Topics:

Centralized restores of Microsoft SQL Server Application Direct backups Considerations for centralized Microsoft SQL Server Application Direct restores Centralized restore of Microsoft SQL Server system databases Centralized restore of a Microsoft SQL Server stand-alone database Centralized restore of a Microsoft SQL Server AAG database Centralized restore of multiple Microsoft SQL Server databases

Centralized restores of Microsoft SQL Server Application Direct backups When Microsoft SQL Server data is backed up as part of an Application Direct protection policy in PowerProtect Data Manager, you can recover the Microsoft SQL Server Application Direct backups by using the centralized restore functionality in the PowerProtect Data Manager UI.

You can perform the following types of centralized restores of Microsoft SQL Server Application Direct backups, depending on the type of database assets:

Centralized restore of a system database Centralized restore of a stand-alone database Centralized restore of an Always On availability group (AAG) database Centralized restore of a Failover Cluster Instance (FCI) database Centralized restore of an Always On Failover Cluster Instance (AAG over FCI) database

NOTE: You cannot perform the centralized restore of a Microsoft SQL Server Application Direct backup and the centralized

restore of a Microsoft SQL Server virtual machine backup at the same time.

You can restore single or multiple databases from the same Microsoft SQL Server host and instance. You can restore the databases either to the original Microsoft SQL Server host or to an alternate Microsoft SQL Server host with the following requirements:

The alternate host must be a Microsoft SQL Server Application Direct machine. The Microsoft application agent software must be installed and configured on the alternate host, as described in Application

agent manual installation and configuration. You cannot restore a system database to an alternate host or Microsoft SQL Server instance.

You must perform all centralized restores from the Restore > Assets > SQL window in the PowerProtect Data Manager UI. You can perform a centralized restore of a full, differential, or transaction log backup to a specified Microsoft SQL Server host and instance. Select one of the following restore options to specify the file system location where the databases are restored:

Original file location (location at backup time)Restores the backup data to the file directory that was used during the backup and overwrites the existing contents.

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

Default file location as set by Microsoft SQL ServerRestores the backup data to the default file directory as used by the Microsoft SQL Server.

User-specified file locationRestores the backup data to file directories that you specify for the database files and log files.

The following topics describe the considerations, prerequisites, and procedures for the supported types of centralized restores of Microsoft SQL Server Application Direct backups.

6

Performing Centralized Restores of Application Direct Backups 129

Considerations for centralized Microsoft SQL Server Application Direct restores Ensure that you review the following information before you perform the centralized restores of Microsoft SQL Server Application Direct backups.

The centralized restore of multiple Microsoft SQL Server databases supports the following use cases:

Performing disaster recovery of the original Microsoft SQL Server instance. Performing a restore rehearsal by restoring a Microsoft SQL Server instance database to an alternate host to validate the

backups.

For disaster recovery to the original host, you can select all the databases for the Microsoft SQL Server instance. Once the restore job starts, the application agent automates the disaster recovery procedures as outlined by Microsoft. The disaster recovery includes a restart of the Microsoft SQL Server instance in single user mode to restore the master database.

For disaster recovery to an alternate host, ensure that the alternate host is a Microsoft SQL Server Application Direct host that is a discovered asset of PowerProtect Data Manager.

NOTE: During the centralized restore to an alternate host, if the alternate host is not included in the list of available hosts,

follow the instructions to install and configure the Microsoft application agent. The Microsoft SQL Server host must be

registered to the same PowerProtect Data Manager server.

PowerProtect Data Manager applies the following concurrency rules for jobs associated with either a single-database or multi-database centralized restore, including any backup, restore, and manual agent installation jobs that you run on the same host:

If an asset backup is in progress, the Microsoft SQL Server restore against the same asset is queued. If the Microsoft SQL Server restore against an asset is in progress, the backup against the same asset is queued.

Application agent manual installation and configuration

When you want to restore to a host that is not part of a protection policy, you must manually install and configure the Microsoft application agent on the target host of the restore.

Ensure that the target host meets the following prerequisites:

A Windows OS is running. The Microsoft SQL Server is installed and running. The SYSTEM account has the same security configuration as required for backup. The network ports are configured as required for backup.

Before you manually install and configure the application agent, ensure that the Windows account credentials are set at the asset level, not the protection policy level.

To set the credentials at the asset level, select Infrastructure > Assets > SQL, select the required asset, and select More Actions > Set Credential.

Centralized restore of Microsoft SQL Server system databases You can perform a centralized restore of a full backup of a Microsoft SQL Server system database in the PowerProtect Data Manager UI.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the SQL tab.

The Restore window displays all the databases that are available for restore.

To filter the displayed list of assets if needed, you can click the Host/Cluster/Group Name, Application Name, and Protection Type column headings:

130 Performing Centralized Restores of Application Direct Backups

The Host/Cluster/Group Name column lists the hostnames. The Application Name column lists the Microsoft SQL Server instance names. The Protection Type column lists the Application Direct or VM Direct protection type for each asset.

NOTE: Only the assets that were created by a Microsoft SQL Server Application Direct or virtual machine application-

aware protection policy and have at least one copy are displayed. You can select assets only from the same Microsoft

SQL Server host and instance.

2. Select the check box next to the Microsoft SQL Server master, model, or msdb database, and click Restore.

The restore wizard opens on the Select Copy page.

3. On the Select Copy page, click the DD icon in the left pane. You can select the primary or secondary DD.

The right pane displays the available backup copies.

4. In the right pane, select the check box next to the full backup copy that you want to restore, and then click Next.

5. On the Select Destination page, the Host, SQL Instance, and Database fields are prepopulated for the system database. You cannot edit the field values on the page.

NOTE: You can only restore a system database to the original host and instance, overwriting the source database.

Click Next to continue.

6. On the Select File Location page, select one of the following options for Restore database files to, and then click Next:

Original file location (location at backup time)

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

Default file location as set by Microsoft SQL Server User-specified file location

NOTE:

When you select this option, you must specify the restore file directories for the database files and log files.

To restore a database to a different name, ensure that you specify a custom destination directory that is different

from the directory that contains the source mdf and ldf files.

7. On the Select Options page, select any the following options, and then click Next:

NOTE: The tail-log backup option is not supported for a system database.

Overwrite Databases WITH REPLACEOverwrites the existing databases during the restore operation.

NOTE:

When a database exists but the Overwrite Databases WITH REPLACE option is not selected, the restore fails.

After you perform a system database rebuild in the Microsoft SQL Server, you must specify the WITH REPLACE option when you restore the system databases, including master, model, and msdb.

Compressed RestoreUses DD Boost compression for the restore operation. Disconnect UsersDisconnects the database users before the restore operation. TroubleshootingEnables the debug log, setting the debug level to a value of 9. Restore StateSelect one of the following options:

RESTORE WITH RECOVERYLeaves the database ready to use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored.

RESTORE WITH NO RECOVERYLeaves the database nonoperational and does not roll back the uncommitted transactions. Additional transaction logs can be restored.

8. On the Summary page:

a. Review the Source, Destination, File Location, and Options information to ensure that the restore details are correct.

NOTE: When the specified database name matches the name of an existing database, the restore overwrites the

existing database.

b. Click Restore.

The restore operation starts. Then the Go to Jobs informational dialog box appears with a link to the Jobs page where you can monitor the restore job.

Performing Centralized Restores of Application Direct Backups 131

Centralized restore of a Microsoft SQL Server stand- alone database You can perform a centralized restore of a full or transaction log backup of a Microsoft SQL Server stand-alone database in the PowerProtect Data Manager UI. The following procedure restores a single database.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the SQL tab.

The Restore window displays all the databases that are available for restore.

To filter the displayed list of assets if needed, you can click the Host/Cluster/Group Name, Application Name, and Protection Type column headings:

The Host/Cluster/Group Name column lists the hostnames. The Application Name column lists the Microsoft SQL Server instance names. The Protection Type column lists the Application Direct or VM Direct protection type for each asset.

NOTE: Only the assets that were created by a Microsoft SQL Server Application Direct or virtual machine application-

aware protection policy and have at least one copy are displayed. You can select assets only from the same Microsoft

SQL Server host and instance.

2. Select the check box next to the stand-alone database, and click Restore.

The restore wizard opens on the Select Copy page.

3. On the Select Copy page, click the DD icon in the left pane. You can select the primary or secondary DD.

The right pane displays the available backup copies.

4. In the right pane, select the check box next to the backup copy that you want to restore.

NOTE: You can select only one backup copy at a time, as a Differential, Full, or Log copy type. The Selected Copy

Time appears at the top of the right pane.

To see the log copies, click the > symbol beside a full copy, which displays a list of the available log copies. When you select a log copy, you can optionally click Select Point in Time and follow the prompts to specify a point-in-time restore. When you select a point-in-time, the Selected Point in Time also appears at the top of the right pane.

Click Next to continue.

5. On the Select Destination page, the Host, SQL Instance, and Database fields are prepopulated, but you can click Select for each field to specify the host, instance, and database values as needed. You may choose to restore to an existing database name or type a new database name.

NOTE:

The database name must have 128 or fewer characters. Do not specify a Microsoft SQL Server system database name

such as master, model, msdb, or tempdb.

If you specify a Microsoft SQL Server instance that is part of an Always On Failover Cluster Instance, the database

restore is directed to the active node.

Click Next to continue.

6. On the Select File Location page, select one of the following options for Restore database files to, and then click Next:

Original file location (location at backup time)

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

Default file location as set by Microsoft SQL Server User-specified file location

NOTE:

When you select this option, you must specify the restore file directories for the database files and log files.

To restore a database to a different name, ensure that you specify a custom destination directory that is different

from the directory that contains the source mdf and ldf files.

132 Performing Centralized Restores of Application Direct Backups

7. On the Select Options page, select any the following options, and then click Next:

Overwrite Databases WITH REPLACEOverwrites the existing databases during the restore operation.

NOTE:

When a database exists but the Overwrite Databases WITH REPLACE option is not selected, the restore fails.

After you perform a system database rebuild in the Microsoft SQL Server, you must specify the WITH REPLACE option when you restore the system databases, including master, model, and msdb.

Tail LogPerforms a tail-log backup.

NOTE: The tail-log backup option is displayed when the destination is the same as the host. This option is selected

by default.

Compressed RestoreUses DD Boost compression for the restore operation. Disconnect UsersDisconnects the database users before the restore operation. TroubleshootingEnables the debug log, setting the debug level to a value of 9. Restore StateSelect one of the following options:

RESTORE WITH RECOVERYLeaves the database ready to use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored.

RESTORE WITH NO RECOVERYLeaves the database nonoperational and does not roll back the uncommitted transactions. Additional transaction logs can be restored.

8. On the Summary page:

a. Review the Source, Destination, File Location, and Options information to ensure that the restore details are correct.

NOTE: When the specified database name matches the name of an existing database, the restore overwrites the

existing database.

b. Click Restore.

The restore operation starts. Then the Go to Jobs informational dialog box appears with a link to the Jobs page where you can monitor the restore job.

Centralized restore of a Microsoft SQL Server AAG database You can perform a centralized restore of a full or transaction log backup of a Microsoft SQL Server Always On availability group (AAG) database in the PowerProtect Data Manager UI. The following procedure restores a single database.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the SQL tab.

The Restore window displays all the databases that are available for restore.

To filter the displayed list of assets if needed, you can click the Host/Cluster/Group Name, Application Name, and Protection Type column headings:

The Host/Cluster/Group Name column lists the hostnames. The Application Name column lists the Microsoft SQL Server instance names. The Protection Type column lists the Application Direct or VM Direct protection type for each asset.

NOTE: Only the assets that were created by a Microsoft SQL Server Application Direct or virtual machine application-

aware protection policy and have at least one copy are displayed. You can select assets only from the same Microsoft

SQL Server host and instance.

2. Select the check box next to the AAG database, and click Restore.

NOTE: You cannot restore a database that is currently part of an AAG. To enable the database restore, you must

remove the database from the AAG on the Microsoft SQL Server.

The restore wizard opens on the Select Copy page.

3. On the Select Copy page, click the DD icon in the left pane. You can select the primary or secondary DD.

Performing Centralized Restores of Application Direct Backups 133

The right pane displays the available backup copies.

4. In the right pane, select the check box next to the backup copy that you want to restore.

NOTE: You can select only one backup copy at a time, as a Differential, Full, or Log copy type. The Selected Copy

Time appears at the top of the right pane.

To see the log copies, click the > symbol beside a full copy, which displays a list of the available log copies. When you select a log copy, you can optionally click Select Point in Time and follow the prompts to specify a point-in-time restore. When you select a point-in-time, the Selected Point in Time also appears at the top of the right pane.

Click Next to continue.

5. On the Select Destination page, click Select for each of the Host, SQL Instance, and Database fields to specify the required host, instance, and database values. You may choose to restore to an existing database name or type a new database name.

NOTE:

The database name must have 128 or fewer characters. Do not specify a Microsoft SQL Server system database name

such as master, model, msdb, or tempdb.

If you specify a Microsoft SQL Server instance that is part of an Always On Failover Cluster Instance, the database

restore is directed to the active node.

Click Next to continue.

6. On the Select File Location page, select one of the following options for Restore database files to, and then click Next:

Original file location (location at backup time)

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

Default file location as set by Microsoft SQL Server User-specified file location

NOTE:

When you select this option, you must specify the restore file directories for the database files and log files.

To restore a database to a different name, ensure that you specify a custom destination directory that is different

from the directory that contains the source mdf and ldf files.

7. On the Select Options page, select any the following options, and then click Next:

NOTE: The tail-log backup option is not supported for an AAG configuration.

Overwrite Databases WITH REPLACEOverwrites the existing databases during the restore operation.

NOTE: When a database exists but the Overwrite Databases WITH REPLACE option is not selected, the restore

fails.

Compressed RestoreUses DD Boost compression for the restore operation. Disconnect UsersDisconnects the database users before the restore operation. TroubleshootingEnables the debug log, setting the debug level to a value of 9. Restore StateSelect one of the following options:

RESTORE WITH RECOVERYLeaves the database ready to use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored.

RESTORE WITH NO RECOVERYLeaves the database nonoperational and does not roll back the uncommitted transactions. Additional transaction logs can be restored.

8. On the Summary page:

a. Review the Source, Destination, File Location, and Options information to ensure that the restore details are correct.

NOTE: When the specified database name matches the name of an existing database, the restore overwrites the

existing database.

b. Click Restore.

The restore operation starts. Then the Go to Jobs informational dialog box appears with a link to the Jobs page where you can monitor the restore job.

134 Performing Centralized Restores of Application Direct Backups

Centralized restore of multiple Microsoft SQL Server databases You can perform a centralized restore of the full or transaction log backups of multiple Microsoft SQL Server databases in the PowerProtect Data Manager UI.

Prerequisites

Before you perform a multi-database restore, review the Considerations for centralized Microsoft SQL Server Application Direct restores.

About this task

The centralized restore of multiple databases includes the following restrictions:

A multi-database restore can restore only the most recent database backups.

If you need to restore older backup copies of multiple databases, then perform a single database restore of each older backup copy, one at a time.

A multi-database restore can restore only to the original database names.

If you need to restore multiple databases and rename the databases, then perform a single database restore of each backup copy, one at a time.

A multi-database restore does not support the tail-log backup option.

Multiple databases are restored serially (one at time).

A multi-database restore also supports partial success:

If a given database exists on the target host and the overwrite option is not specified, the database restore is not attempted and the next database restore is attempted.

If the restore fails for a given database, the next database restore is attempted.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the SQL tab.

The Restore window displays all the databases that are available for restore.

To filter the displayed list of assets if needed, you can click the Host/Cluster/Group Name, Application Name, and Protection Type column headings:

The Host/Cluster/Group Name column lists the hostnames. The Application Name column lists the Microsoft SQL Server instance names. The Protection Type column lists the Application Direct or VM Direct protection type for each asset.

NOTE: Only the assets that were created by a Microsoft SQL Server Application Direct or virtual machine application-

aware protection policy and have at least one copy are displayed. You can select assets only from the same Microsoft

SQL Server host and instance.

2. Select the check box next to each database that you want to restore, or in a filtered view, select multiple databases through a check box in a column heading, and then click Restore.

The restore wizard opens on the Select Copy page.

3. On the Select Copy page, click the DD icon in the left pane for the primary or secondary source DD.

The right pane displays a message that the restore operation uses the latest copy on the storage target, when available. The most recent full or transaction log backup copy is restored.

NOTE: If a transaction log backup is the most recent copy, the entire backup chain from the base full backup is

restored. If you need to restore older backup copies, use a single database restore to restore the backup copies one at a

time.

Click Next to continue.

4. On the Select Destination page, the Host and SQL Instance fields are prepopulated, but you can click Select for each field to specify the host and instance as needed.

Performing Centralized Restores of Application Direct Backups 135

NOTE:

Microsoft SQL Server system databases (master, model, msdb) can only be restored to the original host and Microsoft

SQL Server instance. If the required host is not listed, follow the instructions in Application agent manual installation and

configuration.

If you specify a Microsoft SQL Server instance that is part of an Always On Failover Cluster Instance, the database

restore is directed to the active node.

Click Next to continue.

5. On the Select File Location page, select one of the following options for Restore database files to, and then click Next:

Original file location (location at backup time)

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

Default file location as set by Microsoft SQL Server User-specified file location

NOTE:

When you select this option, you must specify the restore file directories for the database files and log files.

To restore a database to a different name, ensure that you specify a custom destination directory that is different

from the directory that contains the source mdf and ldf files.

6. On the Select Options page, select any the following options, and then click Next:

Overwrite Databases WITH REPLACEOverwrites the existing databases during the restore operation.

NOTE:

When a database exists but the Overwrite Databases WITH REPLACE option is not selected, the restore fails.

After you perform a system database rebuild in the Microsoft SQL Server, you must specify the WITH REPLACE option when you restore the system databases, including master, model, and msdb.

Compressed RestoreUses DD Boost compression for the restore operation. Disconnect UsersDisconnects the database users before the restore operation. TroubleshootingEnables the debug log, setting the debug level to a value of 9. Restore StateSelect one of the following options:

RESTORE WITH RECOVERYLeaves the database ready to use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored.

RESTORE WITH NO RECOVERYLeaves the database nonoperational and does not roll back the uncommitted transactions. Additional transaction logs can be restored.

7. On the Summary page:

a. Review the Source, Destination, File Location, and Options information to ensure that the restore details are correct.

NOTE: When the specified database name matches the name of an existing database, the restore overwrites the

existing database.

b. Click Restore.

The restore operation starts. Then the Go to Jobs informational dialog box appears with a link to the Jobs page where you can monitor the restore job.

136 Performing Centralized Restores of Application Direct Backups

Performing Self-Service Restores of Virtual Machine Backups

Topics:

Restoring a Microsoft SQL Server virtual machine backup Overview of Microsoft SQL Server virtual machine restore operations Prerequisites Restoring Microsoft SQL Server databases to a virtual machine Performing Microsoft SQL Server table-level recovery to a virtual machine Performing an instant access recovery

Restoring a Microsoft SQL Server virtual machine backup You can use the Microsoft application agent to restore the Microsoft SQL Server databases that are backed up with an application-aware VM protection policy.

NOTE: The Microsoft application agent does not support the quick recovery feature with PowerProtect Data Manager. The

PowerProtect Data Manager Administration and User Guide provides more information about the quick recovery feature.

The following topics provide instructions on how to restore a Microsoft SQL Server virtual machine backup.

Overview of Microsoft SQL Server virtual machine restore operations Use the Microsoft application agent tools to restore full and transaction log backups created by a PowerProtect virtual machine application-aware protection policy. The backups are restored to a Microsoft SQL Server hosted on a VMware virtual machine.

When you add a Microsoft SQL Server virtual machine asset to a PowerProtect Data Manager virtual machine application-aware protection policy, the Microsoft application agent and ItemPoint are silently installed on the protected Microsoft SQL Server.

The Microsoft application agent automatically stores the DD host and login information from the protection settings that are configured in the PowerProtect Data Manager protection policy. This automatic configuration occurs when the Microsoft SQL Server virtual machine asset is added to the PowerProtect Data Manager protection policy.

You can use the Microsoft app agent for VM Direct SQL Server Management Studio (SSMS) plug-in or the command prompt to perform the restore operations. T-SQL scripts are not supported with VM Direct.

The Microsoft application agent can perform a database restore, table-level restore, or database instant access restore to the source virtual machine or an alternate virtual machine. To perform restores to an alternate virtual machine, that virtual machine must be an asset of PowerProtect Data Manager. However, instance-level restores can only be performed to the original source instance.

The Microsoft application agent supports both full backups and transaction log backups for a Microsoft SQL Server Always On availability group (AAG). The AAG databases are indexed against the AAG cluster name. Full backups index the AAG database for all the AAG cluster nodes for one cycle of backup. Transaction log backups occur only on the preferred node. You may restore the AAG database to any copy. When you restore an AAG database for the purpose of adding back into the AAG, you may restore to any AAG database copy but first remove the database from the AAG, as required by Microsoft. Once the restore is complete, you must add the database back into the AAG and re-seed the replicas.

7

Performing Self-Service Restores of Virtual Machine Backups 137

Prerequisites An environment must meet the following requirements for application-aware virtual machine restore operations:

vCenter 6.5 and VMware ESXi 6.5 or later must be installed. VMware Tools version 10.1 or later must be installed and running on the Microsoft SQL Server host (virtual machine). The UUID attribute must be enabled in the vSphere Client (disk.EnableUUID=TRUE).

The following VMware Knowledge Base article provides instructions:

https://kb.vmware.com/s/article/52815

NOTE: After you set disk.EnableUUID to TRUE, ensure that you reboot the virtual machine.

The virtual machine must use SCSI disks only and the number of available SCSI slots must match the number of disks at a minimum.

For example, a virtual machine with 7 disks requires one SCSI controller but a virtual machine with 8 disks requires 2 SCSI controllers.

The Microsoft SQL Server instance must be up and running on the virtual machine. The Microsoft SQL Server must be a stand-alone instance or part of a clustered or clusterless Always On availability group

that is configured with file share witness. The SQL writer service must be running. The full computer name and FQDN for the Microsoft SQL Server virtual machine that are added in the application-aware

protection policy must be identical and have the DNS resolve. The user account that is configured in the PowerProtect Data Manager protection policy must have access to perform

backup and recovery operations.

To configure the required permissions, perform the following steps on each protected Microsoft SQL Server instance:

1. Create a SQL Login with the user account configured in the PowerProtect Data Manager protection policy. 2. Add the user the sysadmin Microsoft SQL Server role.

The Microsoft SQL Server to which the data will be restored must be hosted on a virtual machine that is a discovered asset of PowerProtect Data Manager.

NOTE: If you are restoring data to an alternate location to a Microsoft SQL Server virtual machine that is not protected

in PowerProtect Data Manager, you must manually install the Microsoft application agent on the target virtual machine

before you can restore the data. The PowerProtect Microsoft Application Agent Installation Guide provides instructions

to install the Microsoft application agent for VM Direct. When you configure the restore operation, you must manually

register the DD server, PowerProtect Data Manager appliance, and lockbox details.

Restoring Microsoft SQL Server databases to a virtual machine Learn how to restore Microsoft SQL Server database backups taken in a PowerProtect Data Manager virtual machine application-aware protection policy.

You can restore database full and transaction log backups from the primary DD system or from the secondary DD system if replication is enabled for the PowerProtect Data Manager protection policy. However, when you are restoring from the secondary DD system, the tail-log backup option is not supported.

Restoring a backup that was moved to the cloud using Cloud Tier

An application-aware workflow supports application-aware full backups that are tiered to the cloud using Cloud Tier. This support is available for Amazon Web Services (AWS) and Elastic Cloud Storage (ECS) profiles.

For a Microsoft SQL Server database recovery from backups that have been tiered using an application-aware workflow, the backups must be recalled to the active tier before you perform the recovery.

When you try to restore a backup after an associated full backup has been moved to the cloud using Cloud Tier, the restore operation fails with the following error message:

138 Performing Self-Service Restores of Virtual Machine Backups

"reason" : "Missing or invalid value specified for property 'copyId'"

This error occurs when you try to restore either a full backup that has been tiered to the cloud or a tail-log backup when the associated full backup has been tiered to the cloud. For example, the following full and tail-log backups are performed at the specified times:

FULL1: 10:00 a.m. (in cloud tier) TLOG1: 10:30 a.m. TLOG2: 11:00 a.m. FULL2: 11:15 a.m. (in active tier) TLOG4: 11:30 a.m. TLOG5: 12:00 p.m.

In this case, the restore of the FULL1, TLOG1, or TLOG2 backup fails with the error message because the FULL1 backup has been tiered to the cloud. The restore of the FULL2, TLOG4, or TLOG5 backup succeeds because the FULL2 backup is in the active tier.

To resolve this issue, contact the PowerProtect Data Manager administrator to recall the associated full backup (FULL1 in this example) from the cloud tier to the active tier, and then perform the restore.

Restore Microsoft SQL Server databases with the VM Direct SSMS plug-in

Learn how to perform a VM Direct Microsoft SQL Server database restore operation using the Microsoft app agent for VM Direct SSMS plug-in.

Launching the Microsoft application agent for VM Direct SSMS plug-in

About this task

Steps

1. From the Windows Start menu, select Microsoft SQL Server Management Studio.

2. In the Microsoft SQL Server Management Studio, in the Connect to Server window, specify the server information and credentials, and then click Connect.

3. On the toolbar, click Microsoft App Agent (VM Direct). The Microsoft app agent for VM Direct window appears.

NOTE: If the Microsoft App Agent (VM Direct) button is not on the toolbar, the plug-in may be unable to register. In

this scenario, you can launch the plug-in directly from the start menu. From the Windows Start menu, select DDBMA

Plugin for SQL Server Management Studio and select Run as administrator for UAC enabled environments.

Configure general database restore settings

To configure Microsoft SQL Server restores with the Microsoft app agent for VM Direct SSMS plug-in, you must first specify general restore options on the Database Restore > General page.

Steps

1. Open the Microsoft app agent for VM Direct window to the Database Restore > General page.

The General page appears as shown in the following figure.

Performing Self-Service Restores of Virtual Machine Backups 139

Figure 20. VM Direct: Database Restore General page

2. Beside PowerProtect DD System, click ... The PowerProtect DD System List & Lockbox Settings window appears and lists the DD server and lockbox that is configured in the PowerProtect Data Manager protection policy. If the protection policy is configured for replication, the secondary DD server and storage unit also appear.

3. In the PowerProtect DD System List & Lockbox Settings window, select the DD server that contains the backup, and then click OK.

NOTE: If you are restoring the backup to an alternate virtual machine that is not protected in a PowerProtect Data

Manager protection policy, contact the PowerProtect Data Manager administrator to retrieve the DD host details for the

protection policy associated with the original virtual machine. You must also request the PowerProtect Data Manager

administrator to perform either of the following actions:

Approve the Microsoft application agent on the target virtual machine.

Provide the DD storage unit login credentials.

The SQL Server host field is updated with the client backups that are available on the selected DD server storage unit.

4. From the SQL Server host list, select the Microsoft SQL Server host that is the source of the backup.

If you are restoring an AAG database, you must select the Windows cluster name, which enables you to browse the list of AAGs hosted on this cluster.

If you are restoring a clusterless AAG database, you must select the AAG group name, which enables you to browse the list of AAGs hosted on the clusterless AAG group. In the case of a clusterless AAG, the AAG name plus GUID is displayed.

5. Use the Start browsing from list to select a backup save time, and then click Show Versions.

The SQL Server Instance field and save sets table are updated with the backups that are within the specified browse time. If no level full backups are found in the specified time range, you are prompted for confirmation to load the latest full backup.

140 Performing Self-Service Restores of Virtual Machine Backups

NOTE: If you selected a cluster name or AAG group name with GUID in the preceding step, then the list of AAGs in the

cluster or the list of AAGs in the AAG group named with GUID is displayed instead of the list of Microsoft SQL Server

instances.

6. From the SQL Server Instance list, select the Microsoft SQL Server instance that contains the databases that you want to restore.

The databases located on the Microsoft SQL Server instance appear in the database table below the SQL Server Instance field.

7. From the database table, select either the entire Microsoft SQL Server instance by selecting the check box in the header row or select only the required databases to restore. The corresponding save sets appear in the save sets table that is below the databases table.

8. For single database restores, from the save sets table, select the database backup and timestamp that you want to restore. By default, the most recent backup is selected.

NOTE: This step only applies to single database restores. For multiple database and instance-level restores, the most

recent backup is restored.

9. (Optional) To restore the database to a specific point-in-time, perform the following steps:

a. Under Destination, click Timeline. The Backup Timeline dialog box appears as shown in the following figure.

Figure 21. Specifying the restore point b. Specify the backup date and time, and then click OK.

10. Specify the restore destination by performing one of the following action sequences: To perform a recovery directly to a database, perform the following steps:

a. Select Restore to SQL Server. b. From the Instance list, select the Microsoft SQL Server instance where you want to restore the backup.

NOTE:

If you are restoring the backup to an alternate instance, the data and log files are automatically relocated to the

target Microsoft SQL Server instance default data and log path. You can change the file destination settings on

the Files page.

If you are restoring an AAG database, select the target instance that is part of the AAG for the restore. You must

remove the database from the AAG first. You can add the database back to the AAG after the restore completes.

c. From the Database list, select or type the name of the database where the backup will be restored to.

If the database exists, the operation prompts you for confirmation to overwrite the database.

To recover the database as flat-files, perform the following steps: a. Select Restore backups as files. b. In the Folder field, specify the destination for the files. The Folder field is populated with the default destination

path.

To perform a redirected restore, change the destination path by clicking ... beside the Folder field, and specifying the required destination.

NOTE:

Ensure that the destination path is not a root drive, for example, E:\.

Performing Self-Service Restores of Virtual Machine Backups 141

Full backups are restored as .mdf, .ndf, and .ldf files. Transaction log backups are restored as .bak files.

Next steps

Specify the PowerProtect Data Manager server details and additional restore options on the Options page. Also, to change the file destination settings, use the Files page.

Configure file destination settings

View and change the default destination folders of the database files that are data files (.mdf and .ndf) and log files (.ldf) from the Database Restore > Files page.

About this task

All settings on the Files page are optional.

File information on the Files page is shown only when a single database and a backup version is selected on the General page. If you select multiple databases or do not select a backup version, file information does not appear and the databases are restored to the latest backup.

NOTE:

If you are restoring the backup to an alternate instance, the data and log files are automatically relocated to the target

Microsoft SQL Server instance default data and log path. You can change the file destination settings on the Files page.

Ensure that the Microsoft SQL Server administrative account for the target Microsoft SQL Server instance has access to

the selected path so that it can access the database files once they are mounted.

Steps

1. From the left panel, click Files.

The Files page appears as shown in the following figure.

142 Performing Self-Service Restores of Virtual Machine Backups

Figure 22. VM Direct: Database Restore Files page

The table on the page displays the source locations of the database files.

2. To change the destination paths of all of the data and log files, perform the following steps:

a. Select Relocate all files to folder. b. Click the Data file folder browse button to specify a location for the data files, or click inside the field to type the folder

path. c. Click the Log file folder browse button to specify a location for the log files, or click inside the field to type the folder

path.

3. To change the destination path at the file group level, perform one of the following actions in the table: To browse for a destination path, click the browse button to the right of each file group.

A window appears where you can browse and select the file path.

To type a new destination path, in the Restore To column, click the appropriate cell and type a destination path.

If the path does not exist, a dialog box appears asking if you want to create the folder.

NOTE: Ensure that the destination paths are not root drives, for example, E:\.

Next steps

Specify the PowerProtect Data Manager server details and additional restore options on the Options page.

Performing Self-Service Restores of Virtual Machine Backups 143

Configure database restore options

When you configure Microsoft SQL Server database restores with the Microsoft app agent for VM Direct SSMS plug-in, you can specify additional restore options on the Database Restore > Options page.

About this task

NOTE: If you want to restore an AAG database, you must remove the database from the AAG first. You can add the

database back to the AAG after the restore completes. If you have not removed the database from the AAG before you

start the restore, the restore UI displays a prompt about the requirement.

Steps

1. From the left panel, click Options. The Options page appears as shown in the following figure.

Figure 23. VM Direct: Database Restore Options page

2. In the Recovery state list, select one of the following options, as required:

Option Description

RESTORE WITH RECOVERY

(Default) To leave the database in the ready-to-use state by rolling back uncommitted transactions, and disable the ability to restore the latest or additional transaction logs.

RESTORE WITH NORECOVERY

To leave the database in the non-operational state by not rolling back uncommitted transactions, and enable the ability to restore the latest or additional transaction logs.

3. To compress the restore contents and transport them from the DD Replicator to the application host, select PowerProtect DD System Boost compressed restore.

This option reduces network bandwidth.

144 Performing Self-Service Restores of Virtual Machine Backups

4. To generate detailed logs, which you can use to troubleshoot the restore issues, select Select a debug level, and then specify a value of 1 through 9. The default value is 0 (zero).

5. To delete debug logs older than a certain number of days, select Delete debug logs after, and then specify the number of days with a number between 1 and 32767 days. The default value is 0 and does not delete any debug logs.

NOTE: This option only deletes debug logs named in the default format and located in the logs folder at

\MSAPPAGENT\logs.

Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

6. To enable advanced restore options, type or select one of the following options in the Advanced options list:

Option Description

KEEP_REPLICATION Preserves the replication when recovering a published database. This option is required if a database was replicated when the backup was created.

KEEP_CDC Enables change data capture (CDC) recovery. When restoring a database with CDC enabled, the recover operation works differently depending on the recovery destination. Use the to KEEP_CDC option to: Recover the CDC enabled database with a different name on the same Microsoft SQL Server

instance.

In this scenario, KEEP_CDC is required.

Recover the CDC enabled database on a different Microsoft SQL Server instance.

In this scenario, KEEP_CDC is required.

Recover the CDC enabled database on the same Microsoft SQL Server instance by overwriting an existing database.

In this scenario, KEEP_CDC is optional.

Separate multiple advanced options with a comma.

7. To limit the backup history of the databases on the General page to a set number of days, type or select a number in the Days of backup history field.

The default value is 7 days.

If no level full backups are found in the specified time range, you are prompted for confirmation to load the latest full backup.

8. Exclude client name resolution is selected by default, as required to use the client name that is provided as is without converting it to the fully qualified domain name (FQDN).

Use this option when you restore to a virtual machine in a different domain that does not have name resolution for the source client, or when the source host is no longer available.

Unselect the option to resolve the source FQDN during restore.

9. To perform a transaction log backup of the data before performing restore, select Take tail-log backup before restore.

The tail-log backup ensures that the Microsoft application agent backs up the transaction logs that has changed from the previous backup. The restore operation does not restore the logs of the previous tail-log backup.

NOTE:

The tail-log backup feature through the SSMS plug-in is not supported for AAG. Only scheduled transaction log backups

through a PowerProtect protection policy may be performed.

Tail-log backup is not supported in the following scenarios:

When you select Restore backups as files on the General page.

When the PowerProtect Data Manager protection policy has DD MTree replication enabled and you select the

secondary DD system as the backup source.

The Microsoft application agent does not support tail-log backups of multiple databases.

10. To specify the PowerProtect Data Manager appliance, perform the following steps:

Performing Self-Service Restores of Virtual Machine Backups 145

a. Beside Appliance Host, click ...

The PowerProtect Data Manager List & Lockbox Settings window appears.

When you restore a backup to the original virtual machine, the details for the PowerProtect Data Manager appliance that protects the Microsoft SQL Server in a protection policy automatically appear.

b. If you do not see the PowerProtect Data Manager appliance that you want to use for the restore operation, click Add, and then in the Add PowerProtect Data Manager details dialog box, perform one of the following actions:

To add a PowerProtect Data Manager with credential-based authentication, specify the appliance hostname and the login credentials.

Contact the PowerProtect Data Manager administrator to retrieve the PowerProtect Data Manager appliance host and login details.

To add a PowerProtect Data Manager with certificate-based authentication, specify only the appliance hostname. Do not specify the username and password fields.

To use certificate-based authentication, the PowerProtect Data Manager administrator must approve the target Microsoft application agent.

When you add a virtual machine to a protection policy, that virtual machine is approved with a certificate that expires after one day. If you are restoring to an alternate virtual machine that is an asset of PowerProtect Data Manager but not a member of a protection policy, the PowerProtect Data Manager administrator must approve the target virtual machine.

The PowerProtect Data Manager administrator can approve the target Microsoft application agent on the PowerProtect Data Manager Infrastructure > Application Agents page.

c. Select the PowerProtect Data Manager appliance that will mount the backup, and then click OK.

11. To start the restore operation, click Run.

Monitor the database restore operation

After a database restore operation is run from the Microsoft app agent for VM Direct SSMS plug-in, the Database Restore > Monitor page displays the restore script and status.

The following figure shows the restore information and status as it appears on the Monitor page.

146 Performing Self-Service Restores of Virtual Machine Backups

Figure 24. VM Direct: Database Restore Monitor page

NOTE: For information about the success or failure of the restore operation, review the log files that are located in the

installation folder. The location of the log files when the Microsoft application agent is installed in the default path is

C:\Program Files\DPSAPPS\MSAPPAGENT\logs.

Restore a Microsoft SQL Server database with the VM Direct recover command

Learn how to perform a VM Direct Microsoft SQL Server database restore operation using the command line.

Syntax to restore a database with a level full backup

Run the following command to restore databases with VM Direct:

msagentrc.exe -A VM_DIRECT=TRUE -A "DM_PORT= " -A "NSR_RESTORE_TYPE=regular" -c -A "NSR_DFA_SI_DD_HOST= " -A "NSR_DFA_SI_DD_USER= " -A "NSR_DFA_SI_DEVICE_PATH= " -A "NSR_DFA_SI_DD_LOCKBOX_PATH= " -A "DM_HOST= " -A RESTORE_FROM_DD_ONLY=YES -A EXCLUDE_CLIENT_NAME_RESOLUTION=TRUE [ ] -I - -t

where:

-A VM_DIRECT=TRUE

Performing Self-Service Restores of Virtual Machine Backups 147

Specifies to use the VM Direct workflow for the recover operation.

-A "DM_PORT= "

Specifies the port number to communicate with the PowerProtect Data Manager server. The default value is 8443.

-A "NSR_RESTORE_TYPE=regular"

Specifies to perform a database level restore.

-c

Specifies the client name that was used for the backup.

-A "NSR_DFA_SI_DD_HOST= "

Specifies the name of the DD server that contains the backup.

When you have a remote (secondary) DD server that has replicated databases to restore, type the name of the secondary server. A DD user on the secondary DD server must be in the same group as the primary server.

-A "NSR_DFA_SI_DD_USER= "

Specifies the username of the DD Boost user.

You must register the hostname and the DD Boost username in the lockbox to enable Microsoft application agent to retrieve the password for the registered user.

-A "NSR_DFA_SI_DEVICE_PATH= "

Specifies the name and the path of the storage unit that contains the backup.

-A "NSR_DFA_SI_DD_LOCKBOX_PATH= "

Specifies the folder that contains the lockbox file, which contains encrypted information about the registered hosts and the corresponding usernames in pairs. Each pair is associated with a password that backups use. If you do not specify a value, the path defaults to the installation path, which is typically C:\Program Files\DPSAPPS\common\lockbox.

-A "DM_HOST= "

Specifies the PowerProtect Data Manager appliance hostname or IP address.

-A RESTORE_FROM_DD_ONLY=YES

Specifies to restore from the DD server.

-A EXCLUDE_CLIENT_NAME_RESOLUTION=TRUE

Specifies to use the client name that is provided as-is without converting it to the fully qualified domain name (FQDN).

-t

Specifies the save time of the backup. Specify this parameter along with the restore path for each database in the restore operation. The application pauses for you to input this option line by line. Press Enter to move to the next line. A blank line indicates completion of the list.

Specifies the path to the backup objects that you want to restore.

Type the backup path in one of the following formats: For a default instance, type the path in one of the following formats:

To restore a backup of the entire instance, type APPLICATIONS: \SqlServerWriter\

To restore a backup of specific databases, type APPLICATIONS: \SqlServerWriter\ \ \ [...]\

For example: "APPLICATIONS:\SqlServerWriter\LEDMF158\dbtest3" For a named instance, type the path in one of the following formats:

To restore a backup of the entire instance, type APPLICATIONS:\SqlServerWriter\ encoded_SQL_instance_name>

To restore a backup of specific databases, type APPLICATIONS:\SqlServerWriter\ encoded_SQL_instance_name>\ \ [...]\ The is typically %5C

148 Performing Self-Service Restores of Virtual Machine Backups

For example: "APPLICATIONS:\SqlServerWriter\LEDMF158%5Cinst1\dbtest3"

Example VM Direct level full database restore commands

msagentrc.exe -A VM_DIRECT=TRUE -A DM_MOUNT_TIMEOUT=240 -A DM_HOST=10.125.2.17 -A DM_PORT=8443 -c blrv016b102.vmdirect.com -A NSR_DFA_SI_DD_HOST=10.125.2.34 -A NSR_DFA_SI_DD_USER=SQLite102-blrv016c017-d94a3 -A NSR_DFA_SI_DEVICE_PATH=/SQLite102-blrv016c017-d94a3 -A "NSR_DFA_SI_DD_LOCKBOX_PATH=C: \Program Files\DPSAPPS\common\lockbox" -A RESTORE_FROM_DD_ONLY=YES -A EXCLUDE_CLIENT_NAME_RESOLUTION=TRUE -A NSR_RESTORE_TYPE=regular -I - -t 1603971364 APPLICATIONS:\SqlServerWriter\BLRV016B102%5CSQL2017A\sqldatabasename\

msagentrc.exe -A VM_DIRECT=TRUE -A DM_MOUNT_TIMEOUT=240 -A DM_HOST=12.34.222.184 -A DM_PORT=8443 -c win-appvm-000.appsvm.com -A NSR_DFA_SI_DD_HOST=host.lss.emc.com -A NSR_DFA_SI_DD_USER=POLICY-PROTECTION-USER -A NSR_DFA_SI_DEVICE_PATH=/POLICY- PROTECTION-154 -A "NSR_DFA_SI_DD_LOCKBOX_PATH=C:\Program Files\DPSAPPS\common\lockbox" -A RESTORE_FROM_DD_ONLY=YES -A NSR_RESTORE_TYPE=regular -I - -t 1543513971 APPLICATIONS:\SqlServerWriter\WIN-APPVM-191\ReportServerTempDB\ -t 1543513971 APPLICATIONS:\SqlServerWriter\WIN-APPVM-191\master\ -t 1543513971 APPLICATIONS:\SqlServerWriter\WIN-APPVM-191\model\ -t 1543513971 APPLICATIONS:\SqlServerWriter\WIN-APPVM-191\msdb\ -t 1543513971 -A ADDITIONAL_RESTORES=yes APPLICATIONS:\SqlServerWriter\WIN- APPVM-191\ReportServer\ -t 1543513971 -A ADDITIONAL_RESTORES=yes APPLICATIONS:\SqlServerWriter\WIN- APPVM-191\data1\ -t 1543513971 -A ADDITIONAL_RESTORES=yes APPLICATIONS:\SqlServerWriter\WIN- APPVM-191\data10\ -t 1543513971 -A ADDITIONAL_RESTORES=yes APPLICATIONS:\SqlServerWriter\WIN- APPVM-191\data11\

Syntax to restore a database with a transaction log backup

Use the ddbmsqlrc command to restore a transaction log from the command prompt for VM Direct workflow backups. This command may be used if the database full backup was restored in the NORECOVERY state.

Run the following command to restore database transaction logs in a stand-alone environment with VM Direct:

ddbmsqlrc.exe -a VM_DIRECT=TRUE -a "NSR_DFA_SI_DD_HOST= " -a "NSR_DFA_SI_DD_USER= " -a "NSR_DFA_SI_DEVICE_PATH= " -c [-a "SKIP_CLIENT_RESOLUTION=TRUE"] -C -t -S normal -a "RESTORE_START_TIME= "

where:

-A VM_DIRECT=TRUE

Specifies to use the VM Direct workflow for the recover operation.

-a "NSR_DFA_SI_DD_HOST= "

Specifies the name of the DD server that contains the backup.

When you have a remote (secondary) DD server that has replicated databases to restore, type the name of the secondary server. A DD user on the secondary DD server must be in the same group as the primary server.

-a "NSR_DFA_SI_DD_USER= "

Specifies the username of the DD Boost user.

You must register the hostname and the DD Boost username in the lockbox to enable Microsoft application agent to retrieve the password for the registered user.

-a "NSR_DFA_SI_DEVICE_PATH= "

Specifies the name and the path of the storage unit that contains the backup.

-c

Specifies the client name that was used for the backup.

-a "SKIP_CLIENT_RESOLUTION=TRUE"

Performing Self-Service Restores of Virtual Machine Backups 149

(Optional) Specifies to use the client name as it is exactly entered with the -c option and to skip the FQDN lookup to automatically resolve the client name.

-C

Specifies the database and log files for the restore operation.

-t " "

Specifies the backup time stamp that you want to restore.

-S normal

Enables you to roll back uncommitted transactions and use the database to restore the most recent or additional transaction logs.

-a "RESTORE_START_TIME= "

Restores all the backups that were performed at or after a specified backup time (start date and time) and up to the backup time of the selected save set, that is, -t .

Specify the start date and time in the /

/
: : {AM | PM} format.

The start date and time must not be after the backup time of the selected save set, that is, -t .

" "

Specifies the path to the backup objects that you want to restore.

Type the restore path in one of the following formats: For a default instance, type the path in one of the following formats:

To restore backups of the entire instance, type MSSQL: To restore backups of specific databases, type [MSSQL:]

[[MSSQL:] [...]] For example: "MSSQL:database1" "MSSQL:database2"

For a named instance, type the path in one of the following formats: To restore backups of the entire instance, type MSSQL$ : To restore backups of specific databases, type MSSQL$ :

[...] For example: "MSSQL$SqlInst1:database1" "MSSQL$SqlInst1:database2"

Example VM Direct transaction logs database restore commands

ddbmsqlrc.exe -a NSR_DFA_SI_DD_HOST=mars.jupiter.emc.com -a NSR_DFA_SI_DD_USER=POLICY- PROTECTION-USER -a NSR_DFA_SI_DEVICE_PATH=/POLICY-PROTECTION-123456 -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C:\Program Files\DPSAPPS\common\lockbox" -c appvm- sql.appvmdc.com -a "SKIP_CLIENT_RESOLUTION=TRUE" -C "'DB1'='C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\DB1.mdf', 'DB1_log'='C: \Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA\DB1_log.ldf'" -t "11/12/2018 08:54:53 AM" -S normal -a "RESTORE_START_TIME=11/12/2018 08:26:25 AM" -a VM_DIRECT=TRUE MSSQL:DB1

ddbmsqlrc.exe -a NSR_DFA_SI_DD_HOST=host.lss.emc.com -a NSR_DFA_SI_DD_USER=POLICY- PROTECTION-USER -a NSR_DFA_SI_DEVICE_PATH=/POLICY-PROTECTION-154 -a "NSR_DFA_SI_DD_LOCKBOX_PATH=C:\Program Files\DPSAPPS\common\lockbox" -c win- appvm-191.appsvm.com -a "SKIP_CLIENT_RESOLUTION=TRUE" -C "'ReportServer'='C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\ReportServer.mdf', 'ReportServer_log'='C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\ReportServer_log.ldf'" -S normal -a "RESTORE_START_TIME=11/29/2018 09:52:52 AM" -a VM_DIRECT=TRUE MSSQL:ReportServer

Optional parameters for VM Direct database-level restores

You can use the following optional parameters with the msagentrc.exe command.

-A "DM_USER= "

Specifies the username to use for the PowerProtect Data Manager connection.

150 Performing Self-Service Restores of Virtual Machine Backups

This parameter is mandatory only for credential-based access to the PowerProtect Data Manager appliance. You are not required to specify this parameter when the Microsoft application agent is approved by PowerProtect Data Manager.

When you add a virtual machine to a protection policy, that virtual machine is approved with a certificate that expires after one day. The PowerProtect Data Manager administrator can approve the target Microsoft application agent on the PowerProtect Data Manager Infrastructure > Agents page.

-A "DM_LOG_LEVEL={WARNINGS | INFO | TRACE | DEBUG}"

Specifies the PowerProtect Data Manager log level, with WARNINGS providing the least amount of detail, and DEBUG providing the most amount of detail.

-A "DM_LOG_TAG= "

Specifies the PowerProtect Data Manager log tag.

-A "ADDITIONAL_RESTORES={yes | no}"

Specifying yes disables the ability to roll back uncommitted transactions and uses the database to restore the latest or additional transaction logs. The default value is no.

-A "RENAME_TO= "

Specifies the new name for the destination database. The selected database will be restored to the new database. The new name of the database must be a valid Microsoft SQL Server database name. If the destination contains a database with the same name as the database that you have specified, the restore operation overwrites the existing database.

The database files that are data files (.mdf and .ndf) and log file (.ldf) will be restored to their source locations only. If the source database exists, its files can be in use. So, to avoid conflicts for using a new database name, use the -A RELOCATE_TO option along with the -A RENAME_TO option.

-A "INSTANCE_TO= \ "

Performs a redirected restore operation to a Microsoft SQL Server instance that is different from the source instance where the backup was taken.

NOTE: The target instance must reside on the same system where the restore operation is

configured. You cannot restore the backup to an instance on a remote host.

-A "RELOCATE_TO=' '='destination_folder-1', ' '='destination_folder-2',[...]"

Performs redirected restores of the database files that are data files (.mdf and .ndf) and log file (.ldf). You can rename or change only the destination folders, but not the filenames.

Ensure that the destination paths are not root drives, for example, E:\.

-A "NSR_SQL_RECOVER_MODE= "

Performs a redirected restore to the specified path.

-A "NSR_SQL_TARGET_DIR= "

Specifies the destination path, to which you want to copy the restored files. You can then manually either move the files to the required folder or attach the files to a Microsoft SQL Server instance.

Ensure that the destination path is not a root drive, for example, E:\.

-D

Generates detailed logs that you can use to troubleshoot the restore issues. The supported debug levels are 1 through 9.

-A "DELETE_DEBUG_LOG_DAYS= "

Deletes debug log files that are older than the specified number of days. The valid range is between 1 and 32767. By default, debug logs are not deleted. Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

NOTE: This parameter only deletes debug logs named in the default format and located in the logs

folder at \MSAPPAGENT\logs.

Performing Self-Service Restores of Virtual Machine Backups 151

Performing Microsoft SQL Server table-level recovery to a virtual machine To recover table-level data, you can use the SSMS plug-in to first mount the backup, and then use ItemPoint for Microsoft SQL Server to browse and restore the tables.

NOTE: You can only mount and restore tables from the level full backups.

Table-level restore operations mount the application-aware virtual machine image backup on the target virtual machine.

The Microsoft application agent sends a request to the PowerProtect Data Manager appliance to mount the selected backup.

When the backup is mounted, the VMDK images from the virtual machine image backup are added to the target-virtual machine and assigned mount points.

The backup is mounted with the PowerProtect Data Manager appliance for 4 hours by default. The valid range for the mount timeout is between 1 and 24 hours, after which the mounted backup must be dismounted.

NOTE: When backup images are mounted, you cannot start a new session of backup, database restore, table-level restore,

or instant access.

Restore Microsoft SQL Server tables with the VM Direct SSMS plug-in

Learn how to perform a VM Direct Microsoft SQL Server table-level restore operation using the Microsoft app agent for VM Direct SSMS plug-in.

Launching the Microsoft application agent for VM Direct SSMS plug-in

About this task

Steps

1. From the Windows Start menu, select Microsoft SQL Server Management Studio.

2. In the Microsoft SQL Server Management Studio, in the Connect to Server window, specify the server information and credentials, and then click Connect.

3. On the toolbar, click Microsoft App Agent (VM Direct). The Microsoft app agent for VM Direct window appears.

NOTE: If the Microsoft App Agent (VM Direct) button is not on the toolbar, the plug-in may be unable to register. In

this scenario, you can launch the plug-in directly from the start menu. From the Windows Start menu, select DDBMA

Plugin for SQL Server Management Studio and select Run as administrator for UAC enabled environments.

Configure general table restore settings

To configure Microsoft SQL Server table-level restores with the Microsoft app agent for VM Direct SSMS plug-in, you must first specify general table restore options on the Table Restore > General page.

Steps

1. Open the Microsoft app agent for VM Direct window to the Table Restore > General page.

The General page appears as shown in the following figure.

152 Performing Self-Service Restores of Virtual Machine Backups

Figure 25. VM Direct: Table Restore General page

2. Beside PowerProtect DD System, click ... The PowerProtect DD System List & Lockbox Settings window appears and lists the DD server and lockbox that is configured in the PowerProtect Data Manager protection policy. If the protection policy is configured for replication, the secondary DD server and storage unit also appear.

3. In the PowerProtect DD System List & Lockbox Settings window, select the DD server that contains the backup, and then click OK. The SQL Server host field is updated with the client backups that are available on the selected DD server.

4. From the SQL Server host list, select the Microsoft SQL Server host that is the source of the backup.

If you are restoring an AAG database, you must select the Windows cluster name, which enables you to browse the list of AAGs hosted on this cluster.

If you are restoring a clusterless AAG database, you must select the AAG group name, which enables you to browse the list of AAGs hosted on the clusterless AAG group. In the case of a clusterless AAG, the AAG name plus GUID is displayed.

5. Use the Start browsing from list to select a backup save time, and then click Show Versions.

The SQL Server Instance field and save sets table are updated with the backups that are within the specified browse time. If no level full backups are found in the specified time range, you are prompted for confirmation to load the latest full backup.

NOTE: If you selected a cluster name or AAG group name with GUID in the preceding step, then the list of AAGs in the

cluster or the list of AAGs in the AAG group named with GUID is displayed instead of the list of Microsoft SQL Server

instances.

6. From the SQL Server Instance list, select the Microsoft SQL Server instance that contains the databases that you want to restore.

Performing Self-Service Restores of Virtual Machine Backups 153

The databases located on the Microsoft SQL Server instance appear in the database table below the SQL Server Instance field.

7. From the databases table, select the database that contains the tables that you want to restore. The corresponding save sets appear in the save sets table.

8. In the save sets table, select the save set that contains the tables that you want to restore.

Next steps

Specify the PowerProtect Data Manager server details and additional restore options on the Options page.

Configure table restore options

When you configure Microsoft SQL Server table-level restores with the Microsoft app agent for VM Direct SSMS plug-in, you can specify additional restore options on the Table Restore > Options page.

Steps

1. From the left panel, click Options.

The Options page appears as shown in the following figure.

Figure 26. VM Direct: Table Restore Options page

2. Under Mount, specify the following fields as required:

The Mount Folder field specifies the location where backup images are mounted. You cannot edit the value in this field. In the Mount Timeout list, specify the number of hours, after which the mounted backup image must be dismounted.

The default value is 4, and the value cannot be more than 24 hours.

154 Performing Self-Service Restores of Virtual Machine Backups

To prevent ItemPoint from launching after you run the mount operation, select Do not run ItemPoint after mounting the backup images.

Selecting this option disables the Leave backup images mounted after ItemPoint exits option, and enables you to perform manual table-level restores.

To leave the backup images in the mounted state after you close ItemPoint, select Leave backup images mounted after ItemPoint exits.

This option is enabled only if you have not selected the Do not run ItemPoint after mounting the backup images option.

3. To generate detailed logs, which you can use to troubleshoot the restore issues, select Select a debug level, and then specify a value of 1 through 9. The default value is 0 (zero).

4. To delete debug logs older than a certain number of days, select Delete debug logs after, and then specify the number of days with a number between 1 and 32767 days. The default value is 0 and does not delete any debug logs.

NOTE: This option only deletes debug logs named in the default format and located in the logs folder at

\MSAPPAGENT\logs.

Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

5. To limit the backup history of the databases on the General page to a set number of days, type or select a number in the Days of backup history field.

The default value is 7 days.

If no level full backups are found in the specified time range, you are prompted for confirmation to load the latest full backup.

6. Exclude client name resolution is selected by default, as required to use the client name that is provided as is without converting it to the fully qualified domain name (FQDN).

Use this option when you restore to a virtual machine in a different domain that does not have name resolution for the source client.

Unselect the option to resolve the source FQDN during restore.

7. To specify the PowerProtect Data Manager appliance, perform the following steps:

a. Beside Appliance Host, click ... The PowerProtect Data Manager List & Lockbox Settings window appears.

When you restore a backup to the original virtual machine, the details for the PowerProtect Data Manager appliance that protects the Microsoft SQL Server in a protection policy automatically appear.

b. If you do not see the PowerProtect Data Manager appliance that you want to use for the restore operation, click Add, and then in the Add PowerProtect Data Manager details dialog box, perform one of the following actions:

To add a PowerProtect Data Manager with credential-based authentication, specify the appliance hostname and the login credentials.

Contact the PowerProtect Data Manager administrator to retrieve the PowerProtect Data Manager appliance host and login details.

To add a PowerProtect Data Manager with certificate-based authentication, specify only the appliance hostname. Do not specify the username and password fields.

To use certificate-based authentication, the PowerProtect Data Manager administrator must approve the target Microsoft application agent.

When you add a virtual machine to a protection policy, that virtual machine is approved with a certificate that expires after one day. If you are restoring to an alternate virtual machine that is an asset of PowerProtect Data Manager but not a member of a protection policy, the PowerProtect Data Manager administrator must approve the target virtual machine.

The PowerProtect Data Manager administrator can approve the target Microsoft application agent on the PowerProtect Data Manager Infrastructure > Application Agents page.

c. Select the PowerProtect Data Manager appliance that will mount the backup, and then click OK.

8. To mount the backup and proceed with the table restore, click Run.

Performing Self-Service Restores of Virtual Machine Backups 155

Monitor the table restore mount operation

After a table-level restore mount operation is run from the Microsoft app agent VM Direct SSMS plug-in, the Table Restore > Monitor page displays the mount script and status.

The following figure shows the mount information and status as it appears on the Monitor page.

Figure 27. VM Direct: Table Restore Monitor page

NOTE: For information about the success or failure of the restore operation, review the log files that are located in the

installation folder. The typical location of the log files is C:\Program Files\DPSAPPS\MSAPPAGENT\logs.

Restore table-level data using ItemPoint

After the backup images are mounted using the Microsoft application agent SSMS plug-in, complete the table-level restore using ItemPoint for Microsoft SQL Server.

Prerequisites

Configure and run the table level restore operation with the Table Restore tab in the Microsoft application agent SSMS plug-in.

NOTE: ItemPoint 8.6.1 as integrated with the Microsoft application agent now supports the Microsoft SQL Server

Transparent Data Encryption (TDE). However, only the AES_128, AES_192, and AES_256 encryption algorithms are

supported.

About this task

Once the table level restore is configured and run through the Microsoft application agent SSMS plug-in, ItemPoint launches.

156 Performing Self-Service Restores of Virtual Machine Backups

If you select Do not run ItemPoint after mounting the backup images when you configure the table level restore, you must manually launch ItemPoint, and then launch the Data Wizard.

Steps

1. On the Select Source page, select the source backup files from the mounted volume that contains the Microsoft SQL Server backup data as shown in the following figure, and then click Next.

Figure 28. ItemPoint Data Wizard: select the source files

2. On the Select Target Server page, specify the details and login credentials for the target Microsoft SQL Server and database.

The following figure shows the ItemPoint Data Wizard Select Target Server page:

Figure 29. ItemPoint Data Wizard: select the target server

3. Click Finish. The Data Wizard closes and ItemPoint loads the tables contained in the source backup files.

4. Use ItemPoint to browse and restore the individual tables.

NOTE: The PowerProtect ItemPoint for Microsoft SQL Server User Guide provides more information on using ItemPoint

for Microsoft SQL Server to restore table-level data.

5. To dismount the mounted backup images, exit ItemPoint for Microsoft SQL Server.

Performing Self-Service Restores of Virtual Machine Backups 157

NOTE: If you select Leave backup images mounted after ItemPoint exits or Do not run ItemPoint after

mounting the backup images when you configure the mount operation, the backup image remains mounted for 4

hours. To dismount the backup manually, use the msagentadmin command.

Restore Microsoft SQL Server tables with the VM Direct recover command

Learn how to perform a VM Direct Microsoft SQL Server table-level restore operation using a command prompt.

Mount VM Direct backups for table-level recovery using the command prompt

Use the msagentrc.exe command with the -A NSR_RESTORE_TYPE=mount parameter to mount backups for table-level recovery.

Type the recover command with the following syntax to mount VM Direct backup images:

msagentrc.exe -A VM_DIRECT=TRUE -c [- A "SKIP_CLIENT_RESOLUTION=TRUE"] -A NSR_RESTORE_TYPE=mount -A "NSR_DFA_SI_DD_HOST= " -A "NSR_DFA_SI_DD_USER= " -A "NSR_DFA_SI_DEVICE_PATH= " -A "DM_HOST= " [- A "DM_USER= "] [- A "DM_PORT= "] [- A "DM_MOUNT_TIMEOUT= "] [-A "NSR_DFA_SI_DD_LOCKBOX_PATH= "] -I - -t

where:

-A VM_DIRECT=TRUE

Specifies to use the VM Direct workflow for the recover operation.

-c

Specifies the client name that was used for the backup.

-A "SKIP_CLIENT_RESOLUTION=TRUE"

(Optional) Specifies to use the client name as it is exactly entered with the -c option and to skip the FQDN lookup to automatically resolve the client name.

-A NSR_RESTORE_TYPE=mount

Specifies a mount operation

-A "NSR_DFA_SI_DD_HOST= "

Specifies the name of the DD server that contains the backup.

When you have a remote (secondary) DD server that has replicated databases to restore, type the name of the secondary server. A DD user on the secondary DD server must be in the same group as the primary server.

-A "NSR_DFA_SI_DD_USER= "

Specifies the username of the DD Boost user.

You must register the hostname and the DD Boost username in the lockbox to enable Microsoft application agent to retrieve the password for the registered user.

-A "NSR_DFA_SI_DEVICE_PATH= "

Specifies the name and the path of the storage unit that contains the backup.

-A "DM_HOST= "

Specifies the PowerProtect Data Manager appliance hostname or IP address.

-A "DM_USER= "

(Optional) Specifies the username to use for the PowerProtect Data Manager connection.

158 Performing Self-Service Restores of Virtual Machine Backups

This parameter is mandatory only for credential-based access to the PowerProtect Data Manager appliance. You are not required to specify this parameter when the Microsoft application agent is approved by PowerProtect Data Manager.

When you add a virtual machine to a Lifecycle group, that virtual machine is approved with a certificate that expires after one day. The PowerProtect Data Manager administrator can approve the target Microsoft application agent on the PowerProtect Data Manager Infrastructure > Agents page.

-A "DM_PORT= "

(Optional) Specifies the port number to communicate with the PowerProtect Data Manager server. The default value is 8443.

-A "DM_MOUNT_TIMEOUT= "

(Optional) Specifies the amount of time in minutes until the mount times out. The default value is 4 hours (240 minutes).

-A "NSR_DFA_SI_DD_LOCKBOX_PATH= "

(Optional) Specifies the folder that contains the lockbox file, which contains encrypted information about the registered hosts and the corresponding usernames in pairs. Each pair is associated with a password that backups use. If you do not specify a value, the path defaults to the installation path, which is typically C:\Program Files\DPSAPPS\common\lockbox.

-t

Specifies the save time of the backup. Specify this parameter along with the restore path for each database in the restore operation. The application pauses for you to input this option line by line. Press Enter to move to the next line. A blank line indicates completion of the list.

Specifies the path to the objects that you want to restore.

Type the backup path in one of the following formats: For a default instance, type the path in one of the following formats:

To restore a backup of the entire instance, type APPLICATIONS: \SqlServerWriter\

To restore a backup of specific databases, type APPLICATIONS: \SqlServerWriter\ \ \ [...]\

For example: "APPLICATIONS:\SqlServerWriter\LEDMF158\dbtest3" For a named instance, type the path in one of the following formats:

To restore a backup of the entire instance, type APPLICATIONS:\SqlServerWriter\ encoded_SQL_instance_name>

To restore a backup of specific databases, type APPLICATIONS:\SqlServerWriter\ encoded_SQL_instance_name>\ \ [...]\ The is typically %5C

For example: "APPLICATIONS:\SqlServerWriter\LEDMF158%5Cinst1\dbtest3"

Restore table-level data using ItemPoint

Steps

1. Launch the command prompt.

2. Run the following command:

C:\Program Files (x86)\DPSAPPS\MSAPPAGENT\ItemPoint\Sql\EMCIPSQL.exe

The ItemPoint for Microsoft SQL Server appears.

3. Launch the Data Wizard. The Data Wizard appears to the Select Source page.

4. On the Select Source page, select the source backup files from the mounted volume that contains the Microsoft SQL Server backup data as shown in the following figure, and then click Next.

Performing Self-Service Restores of Virtual Machine Backups 159

Figure 30. ItemPoint Data Wizard: select the source files

5. On the Select Target Server page, specify the details and login credentials for the target Microsoft SQL Server and database.

The following figure shows the ItemPoint Data Wizard Select Target Server page:

Figure 31. ItemPoint Data Wizard: select the target server

6. Click Finish. The Data Wizard closes and ItemPoint loads the tables contained in the source backup files.

7. Use ItemPoint to browse and restore the individual tables.

NOTE: The PowerProtect ItemPoint for Microsoft SQL Server User Guide provides more information on using ItemPoint

for Microsoft SQL Server to restore table-level data.

Next steps

Dismount the backups using the msagentadmin.exe command.

160 Performing Self-Service Restores of Virtual Machine Backups

Dismount the backup images

You must dismount the backup images after the table-level restore operation is complete.

To dismount the backup images, run the following command:

msagentadmin dismount --ddhost " " --ddpath " " --dduser " " --dmhost " " -dmport [--lockbox ]

where: dismount

Specifies an operation to dismount backups.

--ddhost " "

Specifies the name of the DD server that contains the storage unit, to which you backed up the databases.

--ddpath " "

Specifies the name and the path of the storage unit, to which you backed up the databases.

--dduser " "

Specifies the username of the DD Boost user.

---dmhost " "

Specifies the PowerProtect Data Manager appliance hostname or IP address.

--dmport

Specifies the port number to communicate with the PowerProtect Data Manager server. The default value is 8443.

--lockbox

(Optional) Specifies the folder that contains the lockbox file, which contains encrypted information about the registered hosts and the corresponding usernames in pairs. Each pair is associated with a password that backups use. If you do not specify a value, the path defaults to the installation path, which is typically C:\Program Files\DPSAPPS\common\lockbox.

Example VM Direct dismount command

msagentadmin.exe dismount --ddhost mars.jupiter.emc.com --ddpath /POLICY- PROTECTION-123456 --dduser POLICY-PROTECTION-USER --dmhost 11.22.333.44 --dmport 8443 -- lockbox "C:\Program Files\DPSAPPS\common\lockbox"

Performing an instant access recovery An instant access recovery enables you to quickly bring a database online from a point-in-time by running the database directly on protection storage, which is added to the host through a backup image mount.

Instant access recovery overview

Instant access recovery enables you to access a live-mounted Microsoft SQL Server database from protection storage without restoring the virtual machine or Microsoft SQL Server database.

This type of operation is useful for database administrators who must use or query a Microsoft SQL Server database before restoring the database due to time and resource constraints.

This feature also supports the migration of mounted disks containing live mounted databases from protection storage to production datastore.

When you initiate instant access recovery, the operation locates the corresponding backup virtual disks and mounts them from the DD protection storage. The operation locates the Microsoft SQL Server database selected by the database administrator from mounted disks and connects the database to the Microsoft SQL Server instance. If transaction logs were selected, the transaction logs are replayed against the instant access database.

Performing Self-Service Restores of Virtual Machine Backups 161

Instant access recovery use cases

Instant access recovery to a Microsoft SQL Server database is useful in a number of cases, including ad hoc queries, health checks, disaster recovery, and development tests.

Ad hoc queries

When you need a history of changes, perform an instant access restore to mount Microsoft SQL Server databases for browsing and finding historical data.

With Microsoft SQL Server instant access recovery, you can browse the history of changes in specific rows or tables quickly by running the SQL queries on the mounted database. You can also run the SQL queries to move data from a mounted database to a live Microsoft SQL Server database.

Health checks

You can validate the Microsoft SQL Server database health by running health check queries on the live mounted database.

By performing health checks on the mounted database instead of the live database in the production environment, you can reduce the impact on production resources while checking the health status.

Disaster recovery

During a disaster recovery, Microsoft SQL Server instant access recovery provides temporary access to Microsoft SQL Server data while the database is down.

You can connect the live mounted database to a Microsoft SQL Server instance for urgent queries.

Development tests

Merging changes to the production database is an operation with a risk of breaking applications.

With Microsoft SQL Server instant access recovery, you can use a replica of the database to test changes before you upload them to the live production database.

Perform an instant access restore with the VM Direct SSMS plug- in

Learn how to perform a VM Direct Microsoft SQL Server instant access restore operation using the Microsoft app agent for VM Direct SSMS plug-in.

Launching the Microsoft application agent for VM Direct SSMS plug-in

To launch the Microsoft application agent for VM Direct SSMS plug-in, perform the following steps: 1. From the Windows Start menu, select Microsoft SQL Server Management Studio. 2. In the Microsoft SQL Server Management Studio, in the Connect to Server window, specify the server information and

credentials, and then click Connect. 3. On the toolbar, click Microsoft app agent for VM Direct.

NOTE: If the Microsoft App Agent (VM Direct) button is not on the toolbar, the plug-in may be unable to register. In this

scenario, you can launch the plug-in directly from the Start menu. From the Windows Start menu, select DDBMA Plugin

for SQL Server Management Studio.

162 Performing Self-Service Restores of Virtual Machine Backups

Configure general instant access settings

To configure Microsoft SQL Server restores with the Microsoft app agent for VM Direct SSMS plug-in, you must first specify general restore options on the Instant Access > General page.

Steps

1. Open the Microsoft app agent for VM Direct window to the Instant Access > General page.

The General page appears as shown in the following figure.

Figure 32. VM Direct: Instant Access General page

2. Beside PowerProtect DD System, click ... The PowerProtect DD System List & Lockbox Settings window appears and lists the DD server and lockbox that is configured in the PowerProtect Data Manager protection policy. If the protection policy is configured for replication, the secondary DD server and storage unit also appear.

3. In the PowerProtect DD System List & Lockbox Settings window, select the DD server that contains the backup, and then click OK. The SQL Server host field is updated with the client backups that are available on the selected DD server.

4. From the SQL Server host list, select the Microsoft SQL Server host that is the source of the backup.

If you are restoring an AAG database, you must select the Windows cluster name, which enables you to browse the list of AAGs hosted on this cluster.

If you are restoring a clusterless AAG database, you must select the AAG group name, which enables you to browse the list of AAGs hosted on the clusterless AAG group. In the case of a clusterless AAG, the AAG name plus GUID is displayed.

5. Use the Start browsing from list to select a backup save time, and then click Show Versions.

Performing Self-Service Restores of Virtual Machine Backups 163

The SQL Server Instance field and save sets table are updated with the backups that are within the specified browse time. If no level full backups are found in the specified time range, you are prompted for confirmation to load the latest full backup.

NOTE: If you selected a cluster name or AAG group name with GUID in the preceding step, then the list of AAGs in the

cluster or the list of AAGs in the AAG group named with GUID is displayed instead of the list of Microsoft SQL Server

instances.

6. From the SQL Server Instance list, select the Microsoft SQL Server instance that contains the databases that you want to mount for instant access.

The databases located on the Microsoft SQL Server instance appear in the database table below the SQL Server Instance field.

7. From the database table, select either the entire Microsoft SQL Server instance by selecting the check box in the header row or select only the required databases to mount for instant access.

The corresponding save sets appear in the save sets table that is below the databases table.

NOTE: The Microsoft application agent does not support instant access for system databases. The system databases

do not appear in the database table.

8. For single database instant access, from the save sets table, select the database backup and timestamp that you want to mount for instant access. By default, the most recent backup is selected.

NOTE: This step only applies to single database instant access. For multiple database and instance-level operations, the

most recent backup is mounted and the most recent transaction logs for the browse time are restored.

9. (Optional) To access the database from a specific point-in-time, perform the following steps:

a. Under Access by time, click Timeline. The Backup Timeline dialog box appears as shown in the following figure.

Figure 33. Specifying the access point b. Specify the backup date and time, and then click OK.

10. Under Destination, specify the details for the mount operation:

a. From the Instance list, select the target Microsoft SQL Server instance to mount the backup. b. From the Database list, select the name of the Microsoft SQL Server database for instant access.

When you select a single database, you can specify a new name for the database. For instant access, a default name is generated, by appending the text "InstantAccess" and a date/time stamp to the original database name. For a single database restore, you may change this name. For a multiple database restore, you may not change the database name and the default database name is used.

Configure optional instant access settings

When you configure Microsoft SQL Server database instant access restores with the Microsoft app agent for VM Direct SSMS plug-in, you can specify optional settings on the Instant Access > Options page.

About this task

164 Performing Self-Service Restores of Virtual Machine Backups

Steps

1. From the left panel, click Options to specify optional instant access settings.

The Options page appears as shown in the following figure.

Figure 34. VM Direct: Instant Access Options page

2. Under Mount:

The Mount Folder field specifies the location where backup images are mounted.

NOTE:

The value in the Mount Folder field is the default mount location under the config directory of the Microsoft

application agent installation path, for example, C:\Program Files\DPSAPPS\MSAPPAGENT\config\mount.

Ensure that the Microsoft SQL Server administrative account for the target Microsoft SQL Server instance has

access to this path so that it can access the database files once they are mounted.

In Mount Timeout, specify the number of days after which the mounted backup image must be dismounted. The default value is 7 days.

NOTE: The maximum mount timeout setting is 7 days but can be extended up to 7 more days. After the mount

starts, you can extend the mount timeout on the Instant Access > Active Mounts page by specifying the number

of days in the Change mount timeout field and clicking Change. The specified number of days are added to

the initial timeout value that was set during the mount. Dismount the mounted database provides more details. To

preserve any changes that you make to the database during the instant access active time, you can vMotion the

database.

3. To generate detailed logs, which you can use to troubleshoot the mount issues, select Select a debug level, and then specify a value of 1 through 9. The default value is 0 (zero).

Performing Self-Service Restores of Virtual Machine Backups 165

4. To delete debug logs older than a certain number of days, select Delete debug logs after, and then specify the number of days with a number between 1 and 32767 days. The default value is 0 and does not delete any debug logs.

NOTE: This option only deletes debug logs named in the default format and located in the logs folder at

\MSAPPAGENT\logs.

Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

5. To limit the backup history of the databases on the General page to a set number of days, type or select a number in the Days of backup history field.

The default value is 7 days.

If no level full backups are found in the specified time range, you are prompted for confirmation to load the latest full backup.

6. Exclude client name resolution is selected by default, as required to use the client name that is provided as is without converting it to the fully qualified domain name (FQDN).

Use this option when you restore to a virtual machine in a different domain that does not have name resolution for the source client.

Unselect the option to resolve the source FQDN during restore.

7. To specify the PowerProtect Data Manager appliance, under Mount Method, perform the following steps:

a. Beside Appliance Host, click ...

The PowerProtect Data Manager List & Lockbox Settings window appears.

The details for the PowerProtect Data Manager appliance that protects the Microsoft SQL Server in a protection policy automatically appear.

b. If you do not see the PowerProtect Data Manager appliance that you want to use for the mount operation, click Add, and then in the Add PowerProtect Data Manager details dialog box, perform one of the following actions:

To add an PowerProtect Data Manager with credential-based authentication, specify the appliance hostname and the login credentials.

Contact the PowerProtect Data Manager administrator to retrieve the PowerProtect Data Manager appliance host and login details.

To add an PowerProtect Data Manager with certificate-based authentication, specify only the appliance hostname. Do not specify the username and password fields.

To use certificate-based authentication, the PowerProtect Data Manager administrator must approve the target Microsoft application agent.

The PowerProtect Data Manager administrator can approve the target Microsoft application agent on the PowerProtect Data Manager Infrastructure > Application Agents page.

c. Select the PowerProtect Data Manager appliance that will mount the backup, and then click OK.

8. To mount the database for instant access, click Mount.

Monitor the instant access mount operation

After an instant access mount operation is run from the Microsoft app agent for VM Direct SSMS plug-in, the Instant Access > Monitor page displays the restore script and status.

NOTE: For information about the success or failure of the mount operation, review the log files that are located in the

installation folder. The typical location of the log files is C:\Program Files\DPSAPPS\MSAPPAGENT\logs.

Change the mount timeout

After the mount starts, you can change the mount timeout on the Instant Access > Active Mounts page by specifying the number of days in the Change mount timeout field and clicking Change. The mount timeout is changed by the specified number of days.

About this task

Starting with the Microsoft application agent 19.2, a msagentadmin process runs in the background with a keep_mount_alive option to keep the mount session active for the number of days specified by the user. When the user-

166 Performing Self-Service Restores of Virtual Machine Backups

specified mount period expires, the msagentadmin process removes the Microsoft SQL Server databases and dismounts the instant access session. After a machine reboot, the Microsoft application agent restarts the mount monitoring process to ensure that the user-specified mount period is maintained. For example, the following monitoring process runs in the background:

msagentadmin.exe keep_mount_alive --mountperiod --dmhost --dmport --lockbox "C:\Program Files\DPSAPPS\common\lockbox"

Steps

1. From the left panel, click Active Mounts.

The Active Mounts page appears as shown in the following figure.

Figure 35. VM Direct: Instant Access Active Mounts page

2. Use the Change mount timeout control to select the number of days by which you want to change the mount time.

3. Click Change.

A confirmation dialog box appears.

4. Click OK.

Results

The mount timeout is modified as shown in the following figure.

Performing Self-Service Restores of Virtual Machine Backups 167

Figure 36. VM Direct: Instant Access Active Mounts page

Dismount the mounted database

After you mount a database for instant access, you can use the Instant Access > Active Mounts page to dismount the mounted database.

About this task

All settings on the Instant Access > Active Mounts page are optional. If you do not manually dismount the database, the database will be dismounted when the mount timeout period passes, as specified on the Instant Access > Options page.

Steps

1. From the left panel, click Active Mounts.

The Active Mounts page appears as shown in the following figure.

168 Performing Self-Service Restores of Virtual Machine Backups

Figure 37. VM Direct: Instant Access Active Mounts page

The Active Mounts table displays the details for each active mount session.

2. From the Active Mounts table, select the backup that you want to dismount.

NOTE: All changes to the database will be lost. To preserve the changes, select to vMotion the database instead or

extend the mount timeout.

3. Click Dismount. The backup is dismounted.

Configure vMotion data movement

After you mount a database for instant access, use the Instant Access > Active Mounts page configure vMotion data movement.

About this task

NOTE: Once vMotion is started, you cannot cancel the vMotion data movement.

Steps

1. From the left panel, click Active Mounts.

The Active Mounts page appears as shown in the following figure.

Performing Self-Service Restores of Virtual Machine Backups 169

Figure 38. VM Direct: Instant Access Active Mounts page

2. To update the table and list available datastores, click Show datastores.

3. Select the datastore to which you want the virtual disk to be migrated.

The vdisks will be allocated from the selected datastore. Ensure that the database administrator checks with the data center administrator or backup administrator about the appropriate datastore to select.

4. In the Disk Provisioning field, select the vdisk provisioning mode to be used for the vMotion operation.

5. Click Migrate.

Results

The virtual disk is migrated to the selected datastore by using storage vMotion. You can observe the progress in the Monitor window. Once the vMotion is complete, the mount is removed from the Active Mounts page as the databases are then on permanent VMDKs on the vCenter datastore.

170 Performing Self-Service Restores of Virtual Machine Backups

Performing Centralized Restores of Virtual Machine Backups

Topics:

Centralized restores of Microsoft SQL Server virtual machine backups Considerations for centralized Microsoft SQL Server application-aware restores Centralized restore of Microsoft SQL Server system databases Centralized restore of a Microsoft SQL Server stand-alone database Centralized restore of a Microsoft SQL Server AAG database Centralized restore of multiple Microsoft SQL Server databases

Centralized restores of Microsoft SQL Server virtual machine backups When Microsoft SQL Server data is backed up as part of a virtual machine application-aware protection policy in PowerProtect Data Manager, you can restore the Microsoft SQL Server virtual machine backups by using the centralized restore functionality in the PowerProtect Data Manager UI.

You can perform the following types of centralized restores of Microsoft SQL Server virtual machine backups, depending on the type of database assets:

Centralized restore of a system database Centralized restore of a stand-alone database Centralized restore of an Always On availability group (AAG) database

NOTE:

You cannot perform the centralized restore of a Microsoft SQL Server virtual machine backup and the centralized restore

of a Microsoft SQL Server Application Direct backup at the same time.

The Microsoft SQL Server application-aware backups cannot be restored to a Windows or CIFS shared path by using either

a centralized restore or a restore through the VM Direct SQL Server Management Studio (SSMS) UI plug-in.

You can restore single or multiple databases from the same Microsoft SQL Server host and instance. You can restore the databases either to the original Microsoft SQL Server host or to an alternate Microsoft SQL Server host with the following requirements:

The alternate host must be a Microsoft SQL Server virtual machine. The Microsoft application agent software must be installed and configured on the alternate host, as described in Application

agent manual installation and configuration.

NOTE: When you install the Microsoft application agent to perform a restore of a Microsoft SQL Server virtual machine

backup to an alternate Microsoft SQL Server host, ensure that the host was not previously registered to PowerProtect

Data Manager as an Application Direct host.

You cannot restore a system database to an alternate host or Microsoft SQL Server instance.

You must perform all centralized restores from the Restore > Assets > SQL window in the PowerProtect Data Manager UI. You can perform a centralized restore of a full or transaction log backup to a specified Microsoft SQL Server host and instance. Select one of the following restore options to specify the file system location where the databases are restored:

Original file location (location at backup time)Restores the backup data to the file directory that was used during the backup and overwrites the existing contents.

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

8

Performing Centralized Restores of Virtual Machine Backups 171

Default file location as set by Microsoft SQL ServerRestores the backup data to the default file directory as used by the Microsoft SQL Server.

User-specified file locationRestores the backup data to file directories that you specify for the database files and log files.

The following topics describe the considerations, prerequisites, and procedures for the supported types of centralized restores of Microsoft SQL Server virtual machine backups.

Considerations for centralized Microsoft SQL Server application-aware restores Ensure that you review the following information before you perform the centralized restores of Microsoft SQL Server application-aware virtual machine backups.

The centralized restore of multiple Microsoft SQL Server databases supports the following use cases:

Performing disaster recovery of the original Microsoft SQL Server instance. Performing a restore rehearsal by restoring a Microsoft SQL Server instance database to an alternate host to validate the

backups.

For disaster recovery to the original host, you can select all the databases for the Microsoft SQL Server instance. Once the restore job starts, the application agent automates the disaster recovery procedures as outlined by Microsoft. The disaster recovery includes a restart of the Microsoft SQL Server instance in single user mode to restore the master database.

For disaster recovery to an alternate host, ensure that the alternate host is a Microsoft SQL Server virtual machine that is a discovered asset of PowerProtect Data Manager.

NOTE: During the centralized restore to an alternate host, if the alternate host is not included in the list of available hosts,

follow the instructions in Application agent manual installation and configuration to ensure that the application agent is

properly installed and configured.

PowerProtect Data Manager applies the following concurrency rules for jobs associated with either a single-database or multi-database centralized restore, including any backup, restore, and manual agent installation jobs that you run on the same virtual machine, VM1:

If an agent installation for VM1 is in progress, the VM1 backup is queued and the Microsoft SQL Server restore against target VM1 is queued.

If a VM1 backup is in progress, the agent installation for VM1 is queued and the Microsoft SQL Server restore against target VM1 is queued.

If the Microsoft SQL Server restore against target VM1 is in progress, the agent installation for VM1 is queued and the VM1 backup is queued.

Application agent manual installation and configuration

NOTE:

Ensure that the Microsoft SQL Server host was not previously registered to PowerProtect Data Manager using the

Application Direct option.

For example, if the Microsoft SQL Server host was previously registered to PowerProtect Data Manager with Application

Direct during a Microsoft application agent installation, the protection type for that host may not be changed to VM Direct,

even if the Microsoft application agent is uninstalled.

In either of the following cases, you must manually install and configure the Microsoft application agent on the target virtual machine host of the restore:

The PowerProtect Data Manager has been updated.

NOTE: If PowerProtect Data Manager has been updated from a pre-19.6 version, then you must use the following steps

to manually install and configure the application agent. You must install the application agent on all the client machines.

You want to restore to a virtual machine that is not part of a protection policy.

Ensure that the target virtual machine meets the following prerequisites:

A Windows OS is running.

172 Performing Centralized Restores of Virtual Machine Backups

The VMware Tools are installed at the same version as required for backup. The Microsoft SQL Server is installed and running. The SYSTEM account has the same security configuration as required for backup. The network ports are configured as required for backup.

Perform the following steps to manually install and configure the application agent:

1. Ensure that the Windows account credentials for the virtual machine are set at the virtual machine asset level, not the protection policy level.

To set the credentials at the asset level, select Infrastructure > Assets > Virtual Machine, select the virtual machine, and select More Actions > Set Credential.

2. To install the application agent, select Infrastructure > Assets > Virtual Machine, select the virtual machine, and select More Actions > Install Agent.

After you confirm to start the installation, you can monitor the installation job status on the Jobs page.

Centralized restore of Microsoft SQL Server system databases You can perform a centralized restore of a full backup of a Microsoft SQL Server system database in the PowerProtect Data Manager UI.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the SQL tab.

The Restore window displays all the databases that are available for restore.

To filter the displayed list of assets if needed, you can click the Host/Cluster/Group Name, Application Name, and Protection Type column headings:

The Host/Cluster/Group Name column lists the hostnames. The Application Name column lists the Microsoft SQL Server instance names. The Protection Type column lists the Application Direct or VM Direct protection type for each asset.

NOTE: Only the assets that were created by a Microsoft SQL Server Application Direct or virtual machine application-

aware protection policy and have at least one copy are displayed. You can select assets only from the same Microsoft

SQL Server host and instance.

2. Select the check box next to the Microsoft SQL Server master, model, or msdb database, and click Restore.

The restore wizard opens on the Select Copy page.

3. On the Select Copy page, click the DD icon in the left pane. You can select the primary or secondary DD.

The right pane displays the available backup copies.

4. In the right pane, select the check box next to the full backup copy that you want to restore, and then click Next.

5. On the Select Destination page, the Host, SQL Instance, and Database fields are prepopulated for the system database. You cannot edit the field values on the page.

NOTE: You can only restore a system database to the original host and instance, overwriting the source database.

Click Next to continue.

6. On the Select File Location page, select one of the following options for Restore database files to, and then click Next:

Original file location (location at backup time)

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

Default file location as set by Microsoft SQL Server User-specified file location

NOTE: When you select this option, you must specify the restore file directories for the database files and log files.

7. On the Select Options page, select any the following options, and then click Next:

Performing Centralized Restores of Virtual Machine Backups 173

NOTE: The tail-log backup option is not supported for a system database.

Overwrite Databases WITH REPLACEEnables the overwrite of the existing database.

NOTE:

When the database exists but the Overwrite Databases WITH REPLACE option is not selected, the restore fails.

After you perform a system database rebuild in the Microsoft SQL Server, you must specify the WITH REPLACE option when you restore the system databases, including master, model, and msdb.

TroubleshootingEnables the debug log, setting the debug level to a value of 9. Restore StateSelect one of the following options:

RESTORE WITH RECOVERYLeaves the database ready to use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored.

RESTORE WITH NO RECOVERYLeaves the database nonoperational and does not roll back the uncommitted transactions. Additional transaction logs can be restored.

8. On the Summary page:

a. Review the Source, Destination, File Location, and Options information to ensure that the restore details are correct.

NOTE: When the specified database name matches the name of an existing database, the restore overwrites the

existing database.

b. Click Restore.

The restore operation starts. Then the Go to Jobs informational dialog box appears with a link to the Jobs page where you can monitor the restore job.

Centralized restore of a Microsoft SQL Server stand- alone database You can perform a centralized restore of a full or transaction log backup of a Microsoft SQL Server stand-alone database in the PowerProtect Data Manager UI. The following procedure restores a single database.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the SQL tab.

The Restore window displays all the databases that are available for restore.

To filter the displayed list of assets if needed, you can click the Host/Cluster/Group Name, Application Name, and Protection Type column headings:

The Host/Cluster/Group Name column lists the hostnames. The Application Name column lists the Microsoft SQL Server instance names. The Protection Type column lists the Application Direct or VM Direct protection type for each asset.

NOTE: Only the assets that were created by a Microsoft SQL Server Application Direct or virtual machine application-

aware protection policy and have at least one copy are displayed. You can select assets only from the same Microsoft

SQL Server host and instance.

2. Select the check box next to the stand-alone database, and click Restore.

The restore wizard opens on the Select Copy page.

3. On the Select Copy page, click the DD icon in the left pane. You can select the primary or secondary DD.

The right pane displays the available backup copies.

4. In the right pane, select the check box next to the backup copy that you want to restore.

NOTE: You can select only one backup copy at a time, either Log or Full. The Selected Copy Time appears at the top

of the right pane.

To see the log copies, click the > symbol beside a full copy, which displays a list of the available log copies. When you select a log copy, you can optionally click Select Point in Time and follow the prompts to specify a point-in-time restore. When you select a point-in-time, the Selected Point in Time also appears at the top of the right pane.

174 Performing Centralized Restores of Virtual Machine Backups

Click Next to continue.

5. On the Select Destination page, the Host, SQL Instance, and Database fields are prepopulated, but you can click Select for each field to specify the host, instance, and database values as needed. You may choose to restore to an existing database name or type a new database name.

NOTE: The database name must have 128 or fewer characters. Do not specify a Microsoft SQL Server system database

name such as master, model, msdb, or tempdb.

Click Next to continue.

6. On the Select File Location page, select one of the following options for Restore database files to, and then click Next:

Original file location (location at backup time)

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

Default file location as set by Microsoft SQL Server User-specified file location

NOTE: When you select this option, you must specify the restore file directories for the database files and log files.

7. On the Select Options page, select any the following options, and then click Next:

Overwrite Databases WITH REPLACEEnables the overwrite of the existing database.

NOTE:

When the database exists but the Overwrite Databases WITH REPLACE option is not selected, the restore fails.

After you perform a system database rebuild in the Microsoft SQL Server, you must specify the WITH REPLACE option when you restore the system databases, including master, model, and msdb.

Tail LogPerforms a tail-log backup.

NOTE: The tail-log backup option is displayed when the destination is the same as the host. This option is selected

by default.

TroubleshootingEnables the debug log, setting the debug level to a value of 9. Restore StateSelect one of the following options:

RESTORE WITH RECOVERYLeaves the database ready to use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored.

RESTORE WITH NO RECOVERYLeaves the database nonoperational and does not roll back the uncommitted transactions. Additional transaction logs can be restored.

8. On the Summary page:

a. Review the Source, Destination, File Location, and Options information to ensure that the restore details are correct.

NOTE: When the specified database name matches the name of an existing database, the restore overwrites the

existing database.

b. Click Restore.

The restore operation starts. Then the Go to Jobs informational dialog box appears with a link to the Jobs page where you can monitor the restore job.

Centralized restore of a Microsoft SQL Server AAG database You can perform a centralized restore of a full or transaction log backup of a Microsoft SQL Server Always On availability group (AAG) database in the PowerProtect Data Manager UI. The following procedure restores a single database.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the SQL tab.

The Restore window displays all the databases that are available for restore.

Performing Centralized Restores of Virtual Machine Backups 175

To filter the displayed list of assets if needed, you can click the Host/Cluster/Group Name, Application Name, and Protection Type column headings:

The Host/Cluster/Group Name column lists the hostnames. The Application Name column lists the Microsoft SQL Server instance names. The Protection Type column lists the Application Direct or VM Direct protection type for each asset.

NOTE: Only the assets that were created by a Microsoft SQL Server Application Direct or virtual machine application-

aware protection policy and have at least one copy are displayed. You can select assets only from the same Microsoft

SQL Server host and instance.

2. Select the check box next to the AAG database, and click Restore.

NOTE: You cannot restore a database that is currently part of an AAG. To enable the database restore, you must

remove the database from the AAG on the Microsoft SQL Server.

The restore wizard opens on the Select Copy page.

3. On the Select Copy page, click the DD icon in the left pane. You can select the primary or secondary DD.

The right pane displays the available backup copies.

4. In the right pane, select the check box next to the backup copy that you want to restore.

NOTE: You can select only one backup copy at a time, either Log or Full. The Selected Copy Time appears at the top

of the right pane.

To see the log copies, click the > symbol beside a full copy, which displays a list of the available log copies. When you select a log copy, you can optionally click Select Point in Time and follow the prompts to specify a point-in-time restore. When you select a point-in-time, the Selected Point in Time also appears at the top of the right pane.

Click Next to continue.

5. On the Select Destination page, click Select for each of the Host, SQL Instance, and Database fields to specify the required host, instance, and database values. You may choose to restore to an existing database name or type a new database name.

NOTE: The database name must have 128 or fewer characters. Do not specify a Microsoft SQL Server system database

name such as master, model, msdb, or tempdb.

Click Next to continue.

6. On the Select File Location page, select one of the following options for Restore database files to, and then click Next:

Original file location (location at backup time)

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

Default file location as set by Microsoft SQL Server User-specified file location

NOTE: When you select this option, you must specify the restore file directories for the database files and log files.

7. On the Select Options page, select any the following options, and then click Next:

NOTE: The tail-log backup option is not supported for an AAG configuration.

Overwrite Databases WITH REPLACEEnables the overwrite of the existing database.

NOTE: When the database exists but the Overwrite Databases WITH REPLACE option is not selected, the

restore fails.

TroubleshootingEnables the debug log, setting the debug level to a value of 9. Restore StateSelect one of the following options:

RESTORE WITH RECOVERYLeaves the database ready to use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored.

RESTORE WITH NO RECOVERYLeaves the database nonoperational and does not roll back the uncommitted transactions. Additional transaction logs can be restored.

8. On the Summary page:

a. Review the Source, Destination, File Location, and Options information to ensure that the restore details are correct.

176 Performing Centralized Restores of Virtual Machine Backups

NOTE: When the specified database name matches the name of an existing database, the restore overwrites the

existing database.

b. Click Restore.

The restore operation starts. Then the Go to Jobs informational dialog box appears with a link to the Jobs page where you can monitor the restore job.

Centralized restore of multiple Microsoft SQL Server databases You can perform a centralized restore of the full or transaction log backups of multiple Microsoft SQL Server databases in the PowerProtect Data Manager UI.

Prerequisites

Before you perform a multi-database restore, review the Considerations for centralized Microsoft SQL Server application-aware restores.

About this task

The centralized restore of multiple databases includes the following restrictions:

A multi-database restore can restore only the most recent database backups.

If you need to restore older backup copies of multiple databases, then perform a single database restore of each older backup copy, one at a time.

A multi-database restore can restore only to the original database names.

If you need to restore multiple databases and rename the databases, then perform a single database restore of each backup copy, one at a time.

A multi-database restore does not support the tail-log backup option.

Multiple databases are restored serially (one at time).

A multi-database restore also supports partial success:

If a given database exists on the target host and the overwrite option is not specified, the database restore is not attempted and the next database restore is attempted.

If the restore fails for a given database, the next database restore is attempted.

Steps

1. In the PowerProtect Data Manager UI, select Restore > Assets and select the SQL tab.

The Restore window displays all the databases that are available for recovery.

To filter the displayed list of assets if needed, you can click the Host/Cluster/Group Name, Application Name, and Protection Type column headings:

The Host/Cluster/Group Name column lists the hostnames. The Application Name column lists the Microsoft SQL Server instance names. The Protection Type column lists the Application Direct or VM Direct protection type for each asset.

NOTE: Only the assets that were created by a Microsoft SQL Server Application Direct or virtual machine application-

aware protection policy and have at least one copy are displayed. You can select assets only from the same Microsoft

SQL Server host and instance.

2. Select the check box next to each database that you want to restore, or in a filtered view, select multiple databases through a check box in a column heading, and then click Restore.

The restore wizard opens on the Select Copy page.

3. On the Select Copy page, click the DD icon in the left pane for the primary or secondary source DD.

The right pane displays a message that the restore operation uses the latest copy on the storage target, when available. The most recent full or transaction log backup copy is restored.

Performing Centralized Restores of Virtual Machine Backups 177

NOTE: If a transaction log backup is the most recent copy, the entire backup chain from the base full backup is

restored. If you need to restore older backup copies, use a single database restore to restore the backup copies one at a

time.

Click Next to continue.

4. On the Select Destination page, the Host and SQL Instance fields are prepopulated, but you can click Select for each field to specify the host and instance as needed.

NOTE: Microsoft SQL Server system databases (master, model, msdb) can only be restored to the original host and

Microsoft SQL Server instance. If the required host is not listed, follow the instructions in Application agent manual

installation and configuration.

Click Next to continue.

5. On the Select File Location page, select one of the following options for Restore database files to, and then click Next:

Original file location (location at backup time)

NOTE: If the directory path cannot be created during the centralized restore, the restore fails.

Default file location as set by Microsoft SQL Server User-specified file location

NOTE: When you select this option, you must specify the restore file directories for the database files and log files.

6. On the Select Options page, select any the following options, and then click Next:

Overwrite Databases WITH REPLACEEnables the overwrite of the existing database.

NOTE:

When the database exists but the Overwrite Databases WITH REPLACE option is not selected, the restore fails.

After you perform a system database rebuild in the Microsoft SQL Server, you must specify the WITH REPLACE option when you restore the system databases, including master, model, and msdb.

TroubleshootingEnables the debug log, setting the debug level to a value of 9. Restore StateSelect one of the following options:

RESTORE WITH RECOVERYLeaves the database ready to use by rolling back the uncommitted transactions. Additional transaction logs cannot be restored.

RESTORE WITH NO RECOVERYLeaves the database nonoperational and does not roll back the uncommitted transactions. Additional transaction logs can be restored.

7. On the Summary page:

a. Review the Source, Destination, File Location, and Options information to ensure that the restore details are correct.

NOTE: When the specified database name matches the name of an existing database, the restore overwrites the

existing database.

b. Click Restore.

The restore operation starts. Then the Go to Jobs informational dialog box appears with a link to the Jobs page where you can monitor the restore job.

178 Performing Centralized Restores of Virtual Machine Backups

Microsoft SQL Server Best Practices and Troubleshooting

Before troubleshooting issues with Microsoft application agent, review VM Direct limitations.

Topics:

Troubleshooting configuration issues Troubleshooting backup issues Troubleshooting restore issues

Troubleshooting configuration issues

Troubleshooting storage units

Review the following issues related to storage units in PowerProtect Data Manager.

Discrepancy between storage unit capacity reported in PowerProtect Data Manager and DD Virtual Edition

Due to differences in space calculation (physical capacity vs. logical capacity), there is a discrepancy between storage unit capacity reported in PowerProtect Data Manager and DD Virtual Edition. For example, the DD storage unit capacity displayed in the Protection > Storage > Manage Storage window of the PowerProtect Data Manager UI might be greater than the amount displayed in DDVE.

To determine storage unit capacity, use DDVE instead.

Creating storage unit fails when maximum MTree and Users count on DD system reached

When you add a protection policy or create a storage unit in PowerProtect Data Manager, storage unit creation fails if you reach the maximum MTree and Users count on the selected DD system. PowerProtect Data Manager enables you to finish adding a protection policy without a storage unit. However, if you subsequently run a backup with this protection policy, the backup process is suspended indefinitely with no error message.

To continue backup operations, you must perform a cleanup on the DD system.

Troubleshooting PowerProtect Data Manager UI display of localhost.localdomain hostname

In the PowerProtect Data Manager UI, the Application Agents, Asset Sources, and Protection Jobs windows might list the asset primary hostname as localhost.localdomain instead of the expected FQDN.

The display of localhost.localdomain as the hostname in the PowerProtect Data Manager UI windows might occur when you specify the host's actual FQDN setting for the loopback address in the /etc/hosts file. For example, when you add the

A

Microsoft SQL Server Best Practices and Troubleshooting 179

following settings in the /etc/hosts file, the first setting value, localhost.localdomain, appears as the hostname in the PowerProtect Data Manager UI windows, instead of the actual FQDN:

127.0.0.1 localhost.localdomain localhost6 localhost6.localdomain6 127.0.0.1 blrv027d233.blr.lab.emc.com blrv027d233

Ensure that the host's actual FQDN is not specified for the loopback address and do not specify hostnames that start with "local" in the /etc/hosts file.

Troubleshooting agent registration

Review the following information that is related to troubleshooting agent registration issues.

On Windows, if the agent fails to establish a connection with the PowerProtect Data Manager server, agent registration might fail with the following error message:

During a network connectivity test, the agent is unable to reach the PowerProtect Data Manager server by using ping.

1. If the ping command is blocked in the environment, the agent registration can still complete successfully. Review the agent service logs at INSTALL_DIR\DPSAPPS\AgentService\logs to verify that the registration is successful. If the registration is successful, the status of the agent host indicates Registered in the PowerProtect Data Manager UI. 2. If the ping command is not blocked in the environment, the agent registration might not complete successfully because a network connection cannot be started. If this occurs, complete the following steps to troubleshoot the issue:

On Linux or AIX, if the agent fails to establish a connection with the PowerProtect Data Manager server, agent registration might fail with the following error message:

During a network connectivity test, the agent is unable to reach the PowerProtect Data Manager server by using ping and curl.

1. If the ping command is blocked in the environment and curl is not installed, the agent registration can still complete successfully. Review the agent service logs at /opt/dpsapps/agentsvc/logs to verify that the registration is successful. If the registration is successful, the status of the agent host indicates Registered in the PowerProtect Data Manager UI. 2. If the ping command is not blocked in the environment, the agent registration might not complete successfully because a network connection cannot be started. If this occurs, complete the following steps to troubleshoot the issue:

If agent registration fails with these error messages, complete the following operation:

1. Use any network packet tracing tool to trace the packets from the agent system to PowerProtect Data Manager. 2. Start the packet tracing between the source IP of the agent system and the destination IP of PowerProtect Data Manager. 3. Start the network traffic between the agent system and PowerProtect Data Manager.

Wait 10 to 15 seconds.

4. Analyze the captured packets. 5. Look for SYN and SYN_ACK packets to see if a 3-way handshake is being performed.

Determine whether the source agent or the destination PowerProtect Data Manager is blocking the connection.

If network traffic is blocked, contact your network security team to resolve the port communication issue.

Troubleshooting PowerProtect agent service installations

A PowerProtect agent service installation might fail with the following error message:

Service 'PowerProtect Agent Service' (AgentService) could not be installed. Verify that you have sufficient privileges to install system services.

Possible causes of the installation failure are as follows:

180 Microsoft SQL Server Best Practices and Troubleshooting

The installation was attempted on a passive node of a Failover Cluster Instance (FCI). The installation was canceled and a rollback left some stale entries of PowerProtect agent services.

As a workaround, clean up the PowerProtect agent service entries, and retry the installation.

Troubleshooting PowerProtect agent service operations

To troubleshoot agent service operations, you can check the agent service log file OpAgentSvc- .log, which is created in \logs on Windows and /logs on AIX or Linux. To modify the log level and retention of temporary files, you can modify specific parameter settings in the config.yml file.

About this task

To modify the log level and retention of temporary files, you can perform the following steps.

Steps

1. Stop the agent service by using the appropriate procedure from the preceding topic.

2. Open the config.yml file in an editor.

3. Modify the log-level settings in the following parameters, as required:

NOTE: These parameters are listed in order of decreasing number of messages in the debug information output. The

default log-level is INFO.

DEBUG INFO WARNING ERROR CRITICAL

4. To retain the temporary files, set the keepTempFiles parameter to True in the config.yml file.

NOTE: The agent service and application agent communicate through the temporary files, which are typically deleted

after use but can be useful for troubleshooting purposes. Do not leave the keepTempFiles parameter set to True

permanently, or the temporary files can use excessive space on the file system.

5. Start the agent service by using the appropriate procedure from the preceding topic.

Troubleshooting an error about lockbox stable value threshold after major system update

When a host first accesses a stand-alone or shared lockbox, certain System Stable Values (SSVs) are stored in the lockbox for the host. The Microsoft application agent requires a specific number of the SSVs to be matched for the host for each subsequent lockbox access.

When a major update of the host system causes multiple SSVs to change, the required number of SSVs might not match when the host tries to access the lockbox during a backup or restore operation. In this case, the host's attempt to access the lockbox might produce the following error:

The Lockbox stable value threshold was not met because the system fingerprint has changed. To reset the system fingerprint, open the Lockbox using the passphrase.

If you encounter this error, you can complete the following operation to enable the lockbox access for the host:

In a stand-alone system, re-create the lockbox for the host and perform the registration again. In a high-availability system with a shared lockbox:

1. Revoke the lockbox access of the host by running the msagentadmin administration -R command from another host.

2. Grant the lockbox access to the host by running the msagentadmin administration -G command from another host.

Microsoft SQL Server Best Practices and Troubleshooting 181

NOTE: To update the lockbox configuration on a host, run the msagentadmin administration -U command on that

host. This operation ensures that the lockbox is continuously accessible to the host.

The following msagentadmin administration commands perform the lockbox operations:

msagentadmin administration -G [-a LOCKBOX_PATH= ] [-a LOCKBOX_REMOTE_HOST= ] [-a VIRTUAL_HOST={yes|no}] [-D 9]

msagentadmin administration -R [-a LOCKBOX_PATH= ] [-a LOCKBOX_REMOTE_HOST= ] [-D 9]

msagentadmin administration -U [-a LOCKBOX_PATH= ] [-D 9]

msagentadmin administration -U -a LOCKBOX_IMPORT=TRUE -a LOCKBOX_PATH= [-D 9]

msagentadmin administration -U -a SET_LOCKBOX_PASSPHRASE=TRUE -a LOCKBOX_PATH= [-D 9]

You can optionally set and use a customized passphrase that enables you to reset the lockbox or regain access for a host when the lockbox becomes inaccessible. This feature is useful when a nonshared lockbox becomes inaccessible on an occasional basis. Set and use a customized passphrase for lockbox access provides details about setting a customized passphrase.

You can also use a lockbox security option to select either a default level or custom level for the lockbox security. The default security level is recommended. The custom security level can enable easier access to the lockbox after a major OS update. However, the custom level has potential security concerns, so the setting and use of a customized passphrase is recommended. Reset the lockbox security level provides more details about setting the lockbox security level.

Set and use a customized passphrase for lockbox access

You can optionally set a customized passphrase that enables you to reset the lockbox or regain access for a host when the lockbox becomes inaccessible. This feature is useful when a host frequently loses access to a nonshared lockbox due to reasons such as OS updates. In this case, it is useful to set a customized passphrase when the lockbox is still accessible, so that when any access issue occurs, the lockbox can be reset by the host.

A customized passphrase must meet the following passphrase requirements:

Minimum of nine characters. Minimum of one uppercase letter. Minimum of one lowercase letter. Minimum of one special character, such as % or $. Minimum of one numeric character.

To set a customized passphrase for the lockbox, run the following command as the root user or administrative user and type the passphrase at the prompts:

msagentadmin administration -U -a SET_LOCKBOX_PASSPHRASE=TRUE -a LOCKBOX_PATH=

Enter a passphrase (refer to the administration guide for passphrase complexity requirements): Confirm the passphrase: The passphrase for the lockbox 'agents.clb' in the directory '/opt/lockbox' has been updated.

NOTE: Treat the customized lockbox passphrase with care, and guard it against use by unauthorized persons. If a person

learns the passphrase and obtains a copy of the lockbox files, the person can access the lockbox.

After you set a customized passphrase, you can use the passphrase to reset the lockbox or regain access to the lockbox. For example, if the lockbox becomes inaccessible, run the following command as the root user or administrative user and type the customized passphrase at the prompt:

msagentadmin administration -U -a USE_LOCKBOX_PASSPHRASE=TRUE -a LOCKBOX_PATH=

182 Microsoft SQL Server Best Practices and Troubleshooting

Enter a previously set passphrase: The lockbox 'agents.clb' in the directory '/opt/lockbox' has been reset.

Reset the lockbox security level

You can optionally select a default level or custom level for the lockbox security. The custom security level is not recommended due to potential security concerns. However, the custom level might be useful when you do not want to set a customized passphrase for lockbox inaccessibility issues. The custom security level reduces the frequency at which the lockbox becomes inaccessible after major OS updates, but it does not guarantee that the inaccessibility will not recur.

Setting and using a customized passphrase ensures that the lockbox is always accessible, and does not have any security implications.

To set the lockbox security level, run the following command as the root user or administrative user:

msagentadmin administration -U -a SET_LOCKBOX_SECURITY={"custom"|"default"} -a LOCKBOX_PATH=

For example, the following command sets the custom level of lockbox security:

msagentadmin administration -U -a SET_LOCKBOX_SECURITY="custom" -a LOCKBOX_PATH=/opt/ lockbox

The lockbox 'agents.clb' in the directory '/opt/lockbox' has been reset with the custom security level. Note that with a lower security level, the lockbox is more vulnerable to external threats. If you are not sure whether you want a lower security, we recommend using LOCKBOX_SECURITY="default" for regular usage.

Troubleshooting an asset discovery failure in an FCI environment

If reverse DNS lookup is not configured for the Microsoft SQL Server virtual server name used in a Failover Cluster Instance (FCI), asset discovery can fail and leave the assets unprotected.

As a workaround, configure the reverse DNS lookups for the Microsoft SQL Server virtual server names used in all Failover Cluster Instances.

Troubleshooting an error during configuration of Microsoft SQL Server application-aware protection

When you configure the support for Microsoft SQL Server application-aware protection, the configuration job might fail with the following error message:

Unable to register PowerProtect Agent Service. SSL certificates are not present.

After this error message is displayed, restart the configuration job.

Troubleshooting an issue with trailing spaces in Microsoft SQL Server database names

Due to a VSS limitation, you cannot use trailing spaces within the names of Microsoft SQL Server databases protected by an application-consistent data protection policy.

Microsoft SQL Server Best Practices and Troubleshooting 183

Troubleshooting incorrect database size in PowerProtect Data Manager UI

If a file stream Microsoft SQL Server database is offline, the database size might be displayed incorrectly in the PowerProtect Data Manager UI.

The incorrect database size is displayed when you go to Infrastructure > Assets in the PowerProtect Data Manager UI and select the SQL tab.

If the database comes online later, the database size is displayed correctly after the next assets discovery operation.

Troubleshooting an uninstallation issue in a UAC enabled environment

In a UAC enabled environment, an issue occurs when a domain user or local user that is added in the "Administrators" Active Directory group performs a manual uninstallation of the VM Direct agent. The User Account Control window appears with the following prompt about the XXXXXX.msi program:

Do you want to allow the following program to update software on this computer?

This prompt message can be ignored.

Troubleshooting the exit of agent service register.bat with error code 2

When you try to add a host to an existing virtual machine application-aware protection policy, the agent service register.bat script might exit with error code 2:

Unable to register PowerProtect Agent Service. Registration script returned with exit code 2.

To resolve this issue, complete the following steps.

1. Edit the PowerProtect Data Manager protection policy, and remove the Microsoft SQL Server client. 2. On the Microsoft SQL Server client, uninstall the Microsoft application agent and vProxy agent:

To uninstall the Microsoft application agent, refer to the uninstallation topics in Enabling the Microsoft Application Agent for Microsoft SQL Server.

To uninstall the vProxy agent, complete the following steps:

a. Select Control Panel > Programs > Programs and Features. b. Right-click Dell EMC vProxy Agent in the list, and select Uninstall.

3. Rename the DPSAPPS and vProxy installation directories. The vProxy installation directory is C:\Program Files (x86)\EMC\vProxy FLR Agent.

4. Complete the following Microsoft instructions to change the default control manager timeout limit to 120000 (about 2 minutes):

https://support.microsoft.com/en-in/help/922918/a-service-does-not-start-and-events-7000-and-7011-are-logged-in- window

5. Reboot the Microsoft SQL Server client. 6. In the PowerProtect Data Manager UI, edit the protection policy, add the Microsoft SQL Server client to the policy, and wait

for the configuration job to finish. 7. Confirm that the PowerProtect agent service is running on the Microsoft SQL Server client. Check the PowerProtect agent

service status from the Services Manager.

184 Microsoft SQL Server Best Practices and Troubleshooting

Troubleshooting a VM Direct support issue with an AAG cluster in an IPv6 environment

In an IPv6 environment, registration with PowerProtect Data Manager might fail for a node in a clustered Always On availability group (AAG) that is configured for VM Direct operations. The following error message might be displayed:

Unable to register PowerProtect Agent Service. Registration script returned with exit code 13.

In an IPv6 environment with VMware Tools version pre-12.0.5, Microsoft SQL Server VM Direct operations are not supported for an AAG cluster that is configured with file share witness in PowerProtect Data Manager.

As a workaround, upgrade the VMware Tools to version 12.0.5 or later and then register the clustered AAG node with PowerProtect Data Manager.

Multiple virtual networks (MVLANs) for Microsoft SQL Server application-aware protection

PowerProtect Data Manager cannot automatically configure a virtual network connection between an agent in a virtual machine and PowerProtect Data Manager when PowerProtect Data Manager is configured with multiple virtual network connections.

If you use multiple virtual networks, the virtual machine asset must have a connection to the default interface for PowerProtect Data Manager. Manually configure the VLAN to provide access to the virtual machine before you add the virtual machine to the protection policy.

Troubleshooting backup issues

Troubleshooting backup failures when credentials include a backslash character (\)

When you enter credentials that include a backslash character (\) for an application agent in the PowerProtect Data Manager UI, the backups fail.

For example, when you enter a password for the operating system or database user that includes the backslash character, subsequent backups fail with the following error message:

systemErr: Unable to log in. This error might occur when updating the password for a storage unit.

To resolve this issue, type \\ (double backslash) instead of \ (single backslash) when you enter the credentials for an application agent in the PowerProtect Data Manager UI.

Troubleshooting memory or paging issues during Microsoft SQL Server backups

When the Microsoft application agent is integrated with the PowerProtect Data Manager, Microsoft SQL Server backups that are initiated by a protection policy might fail with the following types of error messages:

ddbmsqlsv: BackupVirtualDeviceSet::SetBufferParms: Request large buffers failure on backup device 'EMC#6f1e7adf-678f-4ceb-88fb-248211218add'. Operating system error 0x8007000e (Not enough storage is available to complete this operation.).

ddbmsqlsv SYSTEM critical Unable to allocate memory: Not enough space ddbmsqlsv PowerProtect Data Manager critical BackupVirtualDeviceSet::SetBufferParms: Request large buffers failure on backup device

Microsoft SQL Server Best Practices and Troubleshooting 185

'EMC#77002120-0a31-4f53-98b1-3311f997e8ac'. Operating system error 0x800705af (The paging file is too small for this operation to complete.).

To prevent or resolve these backup issues, use any of the following procedures:

Increase the RAM size on the Microsoft SQL Server host. Increase the virtual paging value (swap size) on the Microsoft SQL Server host by completing the following steps:

1. Select Control Panel > System and Security > System. 2. Select Advanced system settings to display the system properties of the Microsoft SQL Server host. 3. In the System Properties dialog box, select the Advanced tab. 4. Under Performance, select Settings. 5. In the Performance Options dialog box, select the Advanced tab. 6. Under Virtual memory, select Change. 7. In the Virtual Memory dialog box:

a. Clear the default setting, Automatically manage paging file size for all drives. b. Select the drive for which you want to change the paging file size. c. Select Custom size. d. Set the Initial size to the same value as the Currently allocated size. e. Set the Maximum size required for the paging file, based on the recommended size for the Microsoft SQL Server

host system. To ensure system stability, Windows restricts the paging file size to three times the value of the installed RAM.

On the Infrastructure > Assets page in the PowerProtect Data Manager UI, reduce the stripe value for all databases. Enable multi-stream backups for Microsoft SQL Server protection policy provides details about how to set the stripe value.

NOTE: If the stripe value is decreased to 1, full and differential backups can take longer to complete, depending on the

size of the database.

If the backup schedule results in overlapping backups that run at the same time, such as concurrent FULL and LOG backups, modify the backup schedule to prevent the overlapping backups.

If possible, create multiple protection policies with fewer databases that have non-overlapping schedules.

NOTE: A Microsoft SQL Server database asset may be included in only one protection policy.

Troubleshooting application-aware backup failure with msagentcon message

An application-aware backup might fail in the PowerProtect Data Manager UI, with the following error message in the msagentcon log file:

msagentcon PowerProtect Data Manager info Unable to retrieve lockbox password :'Error encountered while retrieving information from the lockbox 'C:\Program Files\DPSAPPS\common\lockbox\agents.clb' for the device host '10.125.196.91': The Lockbox contains no entries. The drive that contains the lockbox might be full, causing possible corruption of the lockbox. Try the operation again after you reconfigure the lockbox.

To resolve this issue, free up disk space on the C:\ drive and reconfigure the policy for the Microsoft SQL Server asset so that the lockbox is updated.

Troubleshooting application-aware backup failure with persisted settings message

An application-aware virtual machine backup performed through a protection policy might fail with the following error message, where xx.xx.xx.xx is the PowerProtect Data Manager IP address:

PowerProtect agent for Microsoft Applications: Unable to update persisted settings for PowerProtect Data Manager host 'xx.xx.xx.xx': Unable to log in to PowerProtect Data Manager host 'xx.xx.xx.xx'. Received the HTTP code 400 and response 'Invalid FQDN'.

186 Microsoft SQL Server Best Practices and Troubleshooting

As a workaround, when the Microsoft SQL Server host is a member of a workgroup but is assigned an IP address that is DNS resolvable by PowerProtect Data Manager, if the DNS resolution is only available for FQDN, ensure that the Microsoft SQL Server host adds the same domain suffix to the Advanced TCP/IP parameters DNS settings.

In the System Properties dialog box:

1. On the Computer Name tab, click Change and then click More. 2. In Primary DNS suffix of this computer field, specify the PowerProtect Data Manager resolvable FQDN of the Microsoft

SQL Server virtual machine domain name. 3. Click OK.

Troubleshooting application-aware backup failure in multiple VLAN environment

In a Microsoft SQL Server environment of multiple virtual networks (VLANs) where each application client has access to only one network interface, an application-aware backup fails with the following error message:

PowerProtect agent for Microsoft Applications: Unable to update persisted settings for PowerProtect Data Manager host ' ': Exception 'Timeout was reached' occurred while sending Certificate Signing Request.

A Microsoft SQL Server application-aware backup is not supported in this type of multiple virtual network environment.

In a multiple virtual network environment, ensure that the Microsoft SQL Server application-aware host has network connectivity to both the management network and data network. The "Virtual networks (VLANs)" section in the PowerProtect Data Manager Administration and User Guide provides more details.

Troubleshooting application-aware backup failure after software update

After you perform an update of the Microsoft application agent to the latest version, a Microsoft SQL Server application-aware backup might fail due to an issue with the software update.

After the software update completes, confirm that the Microsoft application agent was updated to the latest version. If the software version was not updated as expected, you must manually uninstall the Microsoft application agent and then manually install the latest version of the agent software.

Once the manual uninstall and install procedures are completed, you can rerun the Microsoft SQL Server application-aware backup.

Troubleshooting a missing duration value for centralized backup

A centralized Microsoft SQL Server backup succeeds, but the backup job duration at the asset level appears as 0 ms on the Step Log tab and Details tab in the PowerProtect Data Manager UI.

The Step Log tab and Details tab appear in the Job ID Summary window, which you can access by selecting Jobs > Protection Jobs and clicking the job ID next to the job name.

As a workaround, view the correct backup duration in the Duration column in the left pane that has a grid format.

Troubleshooting TLOG backup issue with mirrored database configuration

When you use a mirrored database configuration with Microsoft SQL Server 2012 or later, a TLOG backup is promoted to a full backup and the following type of error message appears:

Unable to determine the status of mirror partner backups for database DBA_TEST. Promoting the backup level full database backup.

Microsoft SQL Server Best Practices and Troubleshooting 187

With Microsoft SQL Server 2012 or later, use of an Always On availability group (AAG) is recommended. A mirrored database configuration is not supported with Microsoft SQL Server 2012 or later.

Troubleshooting self-service T-SQL backups with an I/O error message

When the Microsoft application agent is integrated with the PowerProtect Data Manager, a successful self-service Transact- SQL (T-SQL) backup might display the following error message:

IO error: Permission denied

To prevent this error message during self-service T-SQL backups, ensure that the Microsoft SQL Server instance service runs as the OS/Microsoft SQL Server user, instead of NT SERVICE\ .

Troubleshooting expired onboarded backup copies that are not deleted

PowerProtect Data Manager does not delete any Microsoft SQL Server backup copies that are onboarded but not associated with a protection policy, even when the backup copies are expired.

When you try to delete such copies by using the ddbmexptool or msagentadmin tool, you receive the following error message:

Write and delete operations are not supported on the storage unit ' ' because the storage unit is managed by the PowerProtect Data Manager system.

To delete the expired backup copies, you can use the following procedures from the PowerProtect Data Manager UI or Microsoft SQL Server host:

From the PowerProtect Data Manager UI, select the expired backup copies and delete the backup copies by clicking the Delete button.

From the Microsoft SQL Server host, perform the following steps:

1. Open the \Settings\.app.settings file for editing. The file content is in XML format, for example:

10.31.140.153 sql_rc-5b2bbffe443d-6451a sql_rc-5b2bbffe443d-6451a PROTECTION DDBOOST false false 86400 sql_rc INST1_SQL2012::dell1 INST1_SQL2012::dell2 MSSQLSERVER::dell_1 MSSQLSERVER::dell_2

2. In the \Settings\.app.settings file, locate the section between the and tags that contains the , , , and tags for the DD or MTree where the backup copies are generated and onboarded to PowerProtect Data Manager.

188 Microsoft SQL Server Best Practices and Troubleshooting

3. Delete that section in the \Settings\.app.settings file.

CAUTION: Delete only the tags , , , ,

, , , and and the information between those tags. Do not delete any

other tags or information in the file, which contain the DD details that the PowerProtect Data Manager

generates.

Troubleshooting backup failure during FCI cluster failover

While the failover of a Microsoft SQL Server Failover Cluster Instances (FCI) cluster is in process, Microsoft SQL Server backups that are initiated by a protection policy fail.

As a workaround, wait until the failover process is complete and then perform the Microsoft SQL Server backup.

Troubleshooting Microsoft SQL Server databases skipped during virtual machine transaction log backup

If a transaction log backup is not appropriate for a database, the database is automatically skipped. Databases are skipped for the reasons outlined in the following table.

Table 11. Microsoft SQL Server skipped database cases and descriptions

Case Description

Database has been restored

When a database has been restored, this database is skipped during a transaction log backup because there is no backup promotion.

System database System databases are automatically skipped during a transaction log backup.

Database state The database is not in a state that allows a backup. For example, the database is in the NORECOVERY state.

Recovery model The database is in the SIMPLE recovery model, which does not support a transaction log backup.

Other backup product

The most recent backup for the database was performed by a different backup product.

New database The database was created after the most recent full backup.

Backup failure The database was in a state that allows a backup, and a backup was tried, but the backup failed.

All skipped databases are backed up as part of the next full backup. Also, a skipped database does not result in a failure.

The only instance in which a transaction log backup job would potentially fail is if all Microsoft SQL Server instance databases failed to be backed up or were skipped.

Troubleshooting Microsoft SQL Server application-aware backup error about disk.EnableUUID variable

A Microsoft SQL Server application-aware virtual machine backup succeeds but displays the following error when the disk.EnableUUID variable for the virtual machine is set to TRUE:

VM ' ' configuration parameter 'disk.EnableUUID' cannot be evaluated. Map item 'disk.EnableUUID' not found. (1071) To resolve this issue, set the disk.EnableUUID variable to TRUE and then reboot the virtual machine.

Troubleshooting restore issues

Microsoft SQL Server Best Practices and Troubleshooting 189

Troubleshooting errors in the restore window after updating from PowerProtect Data Manager 19.8 or earlier

If you update PowerProtect Data Manager from version 19.8 or earlier, you might see 500: Internal Server Error in the default hierarchical view of the Restore > Assets window when viewing Microsoft SQL Server assets.

To view the assets, use the list view. To resolve the issue, contact Customer Support.

Troubleshooting restores of multiple databases from multiple policies

During a centralized restore of multiple databases from multiple policies, with the backup copies located on separate DD systems, the Select Copy page displays the following message for one of the databases:

No copies are available for the listed assets. The restore operation will not include these assets.

You also cannot perform the centralized restore of multiple databases from multiple policies when the backup copies are located on separate storage units in the same DD system.

As a workaround, perform the centralized restore of each database separately.

Troubleshooting centralized Microsoft SQL Server Application Direct restore operations

You can use the following information to troubleshoot issues with the centralized Microsoft SQL Server Application Direct restore operations.

Troubleshooting the PowerProtect Data Manager restores

You can perform the following tasks to troubleshoot issues with the PowerProtect Data Manager restores:

Inspect the ADM logs in /var/log/brs/adm/adm.log in PowerProtect Data Manager.

Inspect the Microsoft application agent logs in C:\Program Files\DPSAPPS\MSAPPAGENT\logs.

Enable advanced debugging output for the PowerProtect agent service by setting the DEBUG parameter in the file config.yml in the agent service installation directory.

Enable advanced debugging output for the Microsoft application agent by setting the debug option in the PowerProtect Data Manager restore wizard. The preceding topics about how to perform the centralized restores describe how you can set the Troubleshooting option, which causes the application agent to generate the diagnostic logs.

Troubleshooting centralized Microsoft SQL Server Application Direct restore of backup tiered to the cloud

During a centralized restore of a Microsoft SQL Server Application Direct backup that is tiered to the cloud, the full backup copy is not browsable in the PowerProtect Data Manager UI. However, the backup copy is browsable in the SQL Server Management Studio (SSMS) UI.

This issue applies to both Amazon Web Services (AWS) and Elastic Cloud Storage (ECS) tiered copies.

As a workaround, perform a manual recall of the cloud tiered backup copies in the PowerProtect Data Manager UI, and then perform the centralized restore operation.

190 Microsoft SQL Server Best Practices and Troubleshooting

Troubleshooting centralized Microsoft SQL Server virtual machine restore operations

You can use the information in the following topics to troubleshoot issues with the centralized Microsoft SQL Server virtual machine restore operations.

Troubleshooting the PowerProtect agent service registration

With a virtual machine that is part of a protection policy, the failure of the PowerProtect agent service registration causes the virtual machine asset configuration to also fail. Despite these failures:

The protection policy backups continue to run. The virtual machine configuration job continues to run if the virtual machine asset configuration did not fail for other

reasons.

You can perform the following steps to troubleshoot these failures:

1. Review the job details for the virtual machine configuration in PowerProtect Data Manager. 2. Enable the Microsoft application agent debugging on the client. Run the following command on the command line, where

is the debug level from 1 to 9. The default debug level is 0:

msagentcon --administration --debug=

When you set the debug level to a value from 1 to 9, the Microsoft application agent generates the debug logs on the virtual machine when the PowerProtect protection group runs. To deactivate the debug logs, set the debug level to 0.

3. After the next failed job, inspect the following logs:

Microsoft application agent diagnostic logs in C:\Program Files\DPSAPPS\MSAPPAGENT\bin\msagentcon.XXXXX.log

Agent service log in agentsvc.log in the agent service home directory on the Microsoft SQL Server host

ADM log from PowerProtect in C:\Program Files\DPSAPPS\AgentService\logs\OPAgentSVC.xxx.log

Troubleshooting the PowerProtect Data Manager restores

You can perform the following tasks to troubleshoot issues with the PowerProtect Data Manager restores:

Inspect the ADM logs in /var/log/brs/adm/adm.log in PowerProtect Data Manager.

Inspect the Microsoft application agent logs in C:\Program Files\DPSAPPS\MSAPPAGENT\logs.

Enable advanced debugging output for the PowerProtect agent service by setting the DEBUG parameter in the file config.yml in the agent service installation directory.

Enable advanced debugging output for the Microsoft application agent by setting the debug option in the PowerProtect Data Manager restore wizard. The preceding topics about how to perform the centralized restores describe how you can set the Troubleshooting option, which causes the application agent to generate the diagnostic logs.

Troubleshooting virtual machine restore and recovery failures with AAG named instances from SSMS UI

In an AAG environment with named instances, a Microsoft SQL Server virtual machine log restore, table-level recovery, or instant access recovery from the SSMS UI for an AAG database might fail. The following type of error message is displayed:

Unable to build the file relocation list.

As a workaround, perform centralized restores of the same AAG database by selecting the following restore options on the Select File Location page in the PowerProtect Data Manager UI:

Default file location as set by Microsoft SQL Server User-specified file location

Performing Centralized Restores of Virtual Machine Backups provides details about the centralized restore procedures.

Microsoft SQL Server Best Practices and Troubleshooting 191

Troubleshooting centralized Microsoft SQL Server virtual machine restore failure after VM Direct update

If registration fails during a VM Direct update, the silent installation completes (it is not rolled back) and an error message is recorded in the installation log. A subsequent centralized restore might fail.

To resolve this issue, configure the Microsoft SQL Server host by using the Install Agent option in the PowerProtect Data Manager UI, and then restart the centralized restore.

Troubleshooting centralized Microsoft SQL Server virtual machine restore failure to Windows or CIFS shared path

A centralized restore of a Microsoft SQL Server virtual machine backup to a Windows or CIFS shared path fails with PowerProtect Data Manager.

To resolve this issue, perform a self-service restore to the Windows or CIFS shared path by using either the SQL Server Management Studio (SSMS) UI or the restore command on the command line.

Troubleshooting VM Direct SSMS restore failure with enabled UAC

A VM Direct self-service restore might fail with the following error message when you use the SQL Server Management Studio (SSMS) plug-in to perform the restore as a domain or local user with enabled UAC and vmtools 11.x or later. This error message appears for a database restore, table restore, or instant access restore operation when you do not launch the SSMS plug-in by selecting Run as administrator:

Unable to initialize the generic information context: Cannot create shared memory mapping, permission denied: ERROR_ACCESS_DENIED.

As a workaround, launch the SSMS plug-in by selecting Run as administrator and rerun the self-service restore operation.

Troubleshooting VM Direct SSMS restore failure after PowerProtect Data Manager server update

After an update of the PowerProtect Data Manager server, if no protection policy operations have run since the update, a VM Direct restore of an old backup through the SQL Server Management Studio (SSMS) UI might fail. The restore failure produces the following type of message in the error logs:

158905:msagentrc: A failure occurred trying to mount the backup images: (Failed to login, please check your configuration and/or credentials). 102437:msagentrc: Recovery operation failed. Refer to log file(s) and Windows event logs for details.

As a workaround, perform at least one successful protection policy operation after the update of the PowerProtect Data Manager server. Then perform the VM Direct restore of an old backup through the SSMS UI.

Troubleshooting VM Direct SSMS restore of replicated log backup

In a federated configuration, you can create replication backups on a secondary DD by replicating the VM Direct Microsoft SQL Server full and transaction log backups located on a primary DD. When you try to restore the replicated backups by using the SQL Server Management Studio (SSMS) UI, the SSMS UI displays only the replicated full backup, not the replicated transaction log backup.

You cannot restore the replicated VM Direct transaction log backup on the secondary DD by using the SSMS UI.

As a workaround, you can perform a centralized restore of the replicated transaction log backup in the PowerProtect Data Manager UI.

192 Microsoft SQL Server Best Practices and Troubleshooting

Troubleshooting SSMS UI crash after switch from table restore to database restore tab

During a restore using the SQL Server Management Studio (SSMS) UI, the SSMS UI might crash after you perform the following sequence of operations in the UI:

1. You select a database on the database restore tab. 2. You select a different storage unit on the table restore tab. 3. You switch quickly to the database restore tab to try to check a preloaded database.

The SSMS UI crashes when the switch from table restore tab to database restore tab occurs so quickly that the database list has not yet been updated before you try to check the preloaded database. An Assertion Failed exception message window is displayed.

As a workaround, clear the SSMS cache and retry the operation.

Microsoft SQL Server Best Practices and Troubleshooting 193

Glossary of Acronyms This glossary provides definitions of acronyms used in the PowerProtect Data Manager documentation.

B

194 Glossary of Acronyms

A

AAG: Always On availability group

ACL: access control list

AD: Active Directory

AKS: Azure Kubernetes Service

API: application programming interface

ARM: Azure Resource Manager

AVS: Azure VMware Solution

AWS: Amazon Web Services

AZ: availability zone

B

BBB: block-based backup

C

CA: certificate authority

CBT: Changed Block Tracking

CDC: change data capture

CIFS: Common Internet File System

CLI: command-line interface

CLR: Common Language Runtime

CN: common name

CPU: central processing unit

CR: custom resource

CRD: custom resource definition

CSI: container storage interface

CSV: Cluster Shared Volume

D

DA: database administrator

DAG: database availability group

Glossary

Glossary 195

DBID: database identifier

DDMC: DD Management Center

DDOS: DD Operating System

DDVE: DD Virtual Edition

DFC: DD Boost over Fibre Channel

DNS: Domain Name System

DPC: Data Protection Central

DR: disaster recovery

DRS: Distributed Resource Scheduler

DSA: Dell security advisory

E

EBS: Elastic Block Store

EC2: Elastic Compute Cloud

eCDM: Enterprise Copy Data Management

ECS: Elastic Cloud Storage

EFI: Extensible Firmware Interface

EKS: Elastic Kubernetes Service

ENI: Elastic Network Interface

EULA: end-user license agreement

F

FC: Fibre Channel

FCD: first class disk

FCI: failover cluster instance

FETB: front-end protected capacity by terabyte

FLR: file-level restore

FQDN: fully qualified domain name

FTP: File Transfer Protocol

G

GB: gigabyte At Dell, this is 230 bytes.

Gb/s: gigabits per second At Dell, this is 230 bits per second.

196 Glossary

GCP: Google Cloud Platform

GCVE: Google Cloud Virtual Edition

GID: group identifier

GLR: granular-level restore

GUI: graphical user interface

GUID: globally unique identifier

H

HA: High Availability

HANA: high-performance analytic appliance

HTML: Hypertext Markup Language

HTTP: Hypertext Transfer Protocol

HTTPS: Hypertext Transfer Protocol Secure

I

IAM: identity and access management

IDE: Integrated Device Electronics

IP: Internet Protocol

IPv4: Internet Protocol version 4

IPv6: Internet Protocol version 6

K

KB: kilobyte At Dell, this is 210 bytes.

L

LAC: License Authorization Code

LAN: local area network

M

MB: megabyte At Dell, this is 220 bytes.

ms: millisecond

MTU: maximum transmission unit

Glossary 197

N

NAS: network-attached storage

NBD: network block device

NBDSSL: network block device over SSL

NDMP: Network Data Management Protocol

NFC: Network File Copy

NFS: Network File System

NIC: network interface card

NTFS: New Technology File System

NTP: Network Time Protocol

O

OS: operating system

OSS: open-source software

OVA: Open Virtualization Appliance

P

PCS: Protection Copy Set

PDF: Portable Document Format

PEM: Privacy-enhanced Electronic Mail

PIN: personal identification number

PIT: point in time

PKCS: Public Key Cryptography Standards

PSC: Platform Service Controller

PVC (cloud computing): private virtual cloud

PVC (Kubernetes): Persistent Volume Claim

R

RAC: Real Application Clusters

RAM: random-access memory

RBAC: role-based access control

ReFS: Resilient File System

REST API: representational-state transfer API

RHEL: RedHat Enterprise Linux

198 Glossary

RMAN: Recovery Manager

RPO: recovery-point objective

RSA: Rivest-Shamir-Adleman

S

S3: Simple Storage Services

SaaS: software as a service

SAP: System Analysis Program Development From the SAP website (2022), "the name is an initialism of the company's original German name: Systemanalyse Programmentwicklung, which translates to System Analysis Program Development. Today the company's legal corporate name is SAP SE - SE stands for societas Europaea, a public company registered in accordance with the European Union corporate law.

SCSI: Small Computer System Interface

SDDC: software-defined data center

SELinux: Security-Enhanced Linux

SFTP: Secure File Transfer Protocol

SLA: service-level agreement

SLES: SuSE Linux Enterprise Server

SLO: service-level objective

SPBM: Storage Policy Based Management

SQL: Structured Query Language

SRS: Secure Remote Services

SSD: solid-state drive

SSH: Secure Shell

SSL: Secure Sockets Layer

SSMS: SQL Server Management Studio

SSVs: System Stable Values

T

TB: terabyte At Dell, this is 240 bytes.

TCP: Transmission Control Protocol

TDE: Transparent Data Encryption

TLS: Transport Layer Security

TPM: Trusted Platform Module

TSDM: Transparent Snapshot Data Mover

T-SQL: Transact-SQL

Glossary 199

U

UAC: user account control

UDP: User Datagram Protocol

UI: user interface

UID: user identifier

UTC: Coordinated Universal Time From Wikipedia (2022), "this abbreviation comes as a result of the International Telecommunication Union and the International Astronomical Union wanting to use the same abbreviation in all languages. English speakers originally proposed CUT (for 'coordinated universal time'), while French speakers proposed TUC (for 'temps universel coordonn')."

V

VADP: VMware vStorage APIs for Storage Awareness

VBS: virtualization-based security

VCF: VMware Cloud Foundation

vCLS: vSphere Cluster Service

vCSA: vCenter Server Appliance

VCSA: vCenter Server Appliance

VDI: Virtual Device Interface

vDisk: virtual disk

vDS: virtual distributed switch

vFRC: Virtual Flash Read Cache

VGT: Virtual Guest Tagging

VIB: vSphere Installation Bundle

VLAN: virtual LAN

VM: virtual machine

VMC: VMware Cloud

VMDK: virtual machine disk

VNet: virtual network

VPC: virtual private cloud

vRSLCM: vRealize Suite Lifecycle Manager

VST: Virtual Switch Tagging

vTPM: Virtual Trusted Platform Module

VVD: VMware Validated Design

vVol: virtual volume

Manualsnet FAQs

If you want to find out how the PowerProtect Dell works, you can view and download the Dell PowerProtect 19.12 Data Manager Microsoft SQL Server User Guide on the Manualsnet website.

Yes, we have the Microsoft SQL Server User Guide for Dell PowerProtect as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The Microsoft SQL Server User Guide should include all the details that are needed to use a Dell PowerProtect. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell PowerProtect 19.12 Data Manager Microsoft SQL Server User Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell PowerProtect 19.12 Data Manager Microsoft SQL Server User Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell PowerProtect 19.12 Data Manager Microsoft SQL Server User Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell PowerProtect 19.12 Data Manager Microsoft SQL Server User Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell PowerProtect 19.12 Data Manager Microsoft SQL Server User Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.