emc networker module for microsoft networker® module for microsoft release 8.2 service pack 1...

EMC® NetWorker®

Module for MicrosoftRelease 8.2 Service Pack 1

Advanced Recovery GuideP/N 302-001-236 REV 01

EMC NetWorker Module for Microsoft Release 8.2.1 Advanced Recovery Guide2

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

Published January 2015

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

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

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

http://support.emc.com

EMC NetWorker Module for Microsoft Release 8.2.1 Advanced Recovery Guide 3

CONTENTS

Preface

Revision History

Chapter 1 Overview of Advanced Recovery Guide

Cloning NetWorker Module for Microsoft (NMM) backups ............................ 12 Recovering NetWorker Module for Microsoft (NMM) backups ....................... 13

Chapter 2 Cloning

Cloning in NMM .......................................................................................... 15 Exchange considerations............................................................................. 27 Hyper-V considerations ............................................................................... 32 SharePoint considerations .......................................................................... 39 SQL Server considerations .......................................................................... 44

Chapter 3 Recovery

Recovering data with NMM.......................................................................... 48 Exchange considerations............................................................................. 61 Hyper-V CSV considerations ........................................................................ 63 Hyper-V considerations ............................................................................... 63 SharePoint considerations .......................................................................... 64 SQL considerations ..................................................................................... 64

Chapter 4 Troubleshooting

NMM client error messages ......................................................................... 67 Checking log files........................................................................................ 70 Other troubleshooting resources ................................................................. 70


Title Page

FIGURES

1 NMM save set example ............................................................................................... 282 NMM save set example with a NetWorker group .......................................................... 313 Hyper-V CSV save set using a single client in a backup group ...................................... 334 NMM save set example with a NetWorker group .......................................................... 355 Hyper-V save set using a single client ina backup group.............................................. 366 Hyper-V save set example with a NetWorker group ...................................................... 387 SharePoint single client in backup group..................................................................... 418 Save set example with a NetWorker group................................................................... 439 Single client in backup group ...................................................................................... 45


Title Page

TABLES

1 EMC publications for additional information.................................................................. 72 NetWorker server support matrix ................................................................................. 123 Media database attributes .......................................................................................... 154 Save set type .............................................................................................................. 165 Query attributes .......................................................................................................... 196 Save set options ......................................................................................................... 207 Save set query options................................................................................................ 218 Typical NMM deployments for Exchange server ........................................................... 289 Save set summary....................................................................................................... 2910 Hyper-V cloning considerations................................................................................... 3211 Hyper-V CSV save sets within the media database ...................................................... 3412 Hyper-V save sets within the media database.............................................................. 3713 SharePoint deployment considerations ....................................................................... 3914 SharePoint save sets within the media database......................................................... 4215 Save sets within the media database .......................................................................... 46

Preface

PREFACE

As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

This document was accurate at publication time. Go to EMC Online Support (https://support.emc.com) to ensure that you are using the latest version of this document.

PurposeThis guide contains information for all the Microsoft applications that can be backed up and recovered by using EMC NetWorker Module for Microsoft (NMM) release 8.2 Service Pack 1 (SP1).

IMPORTANT

You must download a copy of the appropriate user guide from EMC Online Support to use with this guide when working with a Microsoft application. “Related documentation” on page 7 provides a list of user guides and other documents that must be used with NMM.

AudienceThis guide is part of the NMM documentation set, and is intended for use by system administrators during the setup and maintenance of the product.

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

◆ NetWorker software◆ NetWorker snapshot management◆ Microsoft Volume Shadow Copy Service (VSS) technology

6 EMC NetWorker Module for Microsoft Release 8.2.1 Advanced Recovery Guide

https://support.emc.com

Preface

Related documentationThe following table lists the EMC publications that provide additional information.

Table 1 EMC publications for additional information

Guide Name Description

NetWorker Module for Microsoft Release Notes Provides information about new features and changes, problems fixed from previous releases, known limitations, and late-breaking information that was not provided in the remaining documentation set.

NetWorker Module for Microsoft Installation Guide Provides pre-installation, installation, silent installation, and post-installation information about NMM.

NetWorker Module for Microsoft Administration Guide Provides information common to all the supported Microsoft applications that can be backed up and recovered by using EMC NetWorker Module for Microsoft.

NetWorker Module for Microsoft for SQL and SharePoint VSS User Guide

Provides information about using NMM for backup and recovery of SQL Server VSS and SharePoint Server VSS.

NetWorker Module for Microsoft for Exchange VSS User Guide

Provides information about using NMM for backup and recovery of Exchange Server VSS.

NetWorker Module for Microsoft for Hyper-V VSS User Guide

Provides information about using NMM for backup and recovery of Hyper-V Server VSS.

NetWorker Module for Microsoft for SQL VDI User Guide Provides information about using NMM for backup and recovery of SQL Server using the Virtual Device Interface technology.

NetWorker Module for Microsoft for Windows Bare Metal Recovery User Guide

Provides information about performing Windows Bare Metal Recovery by using NMM.

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

Provides information for performing backup and recovery of a SharePoint Server by using the SQL Server Virtual Device Interface (VDI) technology and the SharePoint VSS Writer with NMM.

NetWorker Performing Exchange Server Granular Recovery by using NetWorker Module for Microsoft with Ontrack PowerControls Technical Notes

Provides information about using NMM with Ontrack PowerControls to perform granular level recovery (GLR) of deleted Microsoft Exchange Server mailboxes, public folders, and public folder mailboxes.

NetWorker SharePoint BLOB Backup and Recovery by using NetWorker Module for Microsoft and Metalogic StoragePoint Technical Notes

Provides information about backup and recovery of SharePoint Binary Large Objects (BLOB) by using EMC NetWorker Module for Microsoft and Metalogix StoragePoint.

NetWorker Cloning Integration Guide Provides planning, practices, and configuration information for using the NetWorker, NMM, and NMDA cloning feature.

7

Preface

EMC uses the following convention for special notices:

An important notice contains information essential to software or hardware operation.

Typographical conventions

EMC uses the following type style conventions in this document:

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

Product information — For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at:


Technical support — Go to EMC Online Support and click Service Center. You will see several options for contacting EMC Technical Support.

Normal Used in running (nonprocedural) text for:• Names of interface elements, such as names of windows, dialog boxes,

buttons, fields, and menus• Names of resources, attributes, pools, Boolean expressions, buttons,

DQL statements, keywords, clauses, environment variables, functions, and utilities

• URLs, pathnames, file names, directory names, computer names, links, groups, service keys, file systems, and notifications

Bold Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages

Used in procedures for:• Names of interface elements, such as names of windows, dialog boxes,

buttons, fields, and menus• What the user specifically selects, clicks, presses, or types

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis, for example, a new term• Variables

Courier Used for:• System output, such as an error message or script• URLs, complete paths, file names, prompts, and syntax when shown

outside of running text

Courier bold Used for specific user input, such as commands

Courier italic Used in procedures for:• Variables on the command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections — the bar means “or”

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

... Ellipses indicate nonessential information omitted from the example



Preface

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

[email protected]

9


Revision History

REVISION HISTORY

The following table lists the revision history of this document.

Revision Date Description of added or changed sections

01 January 2015 Update for EMC NetWorker Module for Microsoft release 8.2 SP1.

Overview of Advanced Recovery Guide

CHAPTER 1Overview of Advanced Recovery Guide

This chapter includes the following topics:

◆ Cloning NetWorker Module for Microsoft (NMM) backups ........................................ 12◆ Recovering NetWorker Module for Microsoft (NMM) backups ................................... 12

11


Cloning NetWorker Module for Microsoft (NMM) backupsCloning is used to replicate backups to a longer-term retention media pool. Cloning allows for secure off site storage, transfer of data from one location to another and verification of backups.

The NMM software creates multiple save sets during a NetWorker backup. Ensure that all required save sets that were created during an NMM backup are included in the cloning process

NetWorker server support matrix

The procedures in this document are written for specific NetWorker patch levels.

To use cloning and to ensure that the NMM software functions properly requires that the NetWorker server and storage nodes are at the patch levels outlined in the following table.

The NetWorker Cumulative Hotfixes documents, available on the EMC Online Support site at https://support.emc.com, provides more information on NetWorker cumulative builds.

Note: Data loss can result if the minimum required patch levels NetWorker server and storage node patch levels are not met. The NetWorker Online Compatibility Guide provides the most up-to-date information on NetWorker server support.

Recovering NetWorker Module for Microsoft (NMM) backupsWhen NMM save sets are present in the media database and are in a browsable state, special steps are not required to recover data from the original or clone save sets.

Additional steps are required if the save sets to be recovered are:

◆ In a recoverable or eligible for recycling state

◆ No longer present in the media database of the NetWorker server

The goals of the recovery processes in this guide are to ensure a successful recovery are to:

Table 2 NetWorker server support matrix

NetWorker Server/Storage Node Version Required Hot fix/Version

NetWorker server 7.6.2 and later None

NetWorker server 7.6.1 Cumulative build NetWorker server 7.6.1.51 or later

NetWorker server 7.6.0 Cumulative build NetWorker server 7.6.1.5 or later orCumulative build NetWorker server 7.6.0.9 or later

NetWorker server 7.5.4 Cumulative build NetWorker server 7.5.4.2 or later

1.Data Domain to Data Domain cloning requires 7.6.1.5 or later. If Data Domain toData Domain cloning is not used, 7.6.1.1 or higher is acceptable.



◆ Verify that all of the original or cloned save sets are scanned back into the media database

◆ Ensure that these save sets are browsable

This recovery process cannot be automated, and care and planning are required when performing these procedures.

Recovering NetWorker Module for Microsoft (NMM) backups 13

Cloning

CHAPTER 2Cloning

This chapter describes the cloning procedure and related information.

◆ Cloning with NMM................................................................................................... 15◆ Cloning Exchange databases................................................................................... 26◆ Cloning with NMM in Hyper-V environments ............................................................ 32◆ Cloning with NMM in a SharePoint environment ...................................................... 40◆ SQL Server requirements......................................................................................... 44


Cloning

Cloning with NMMThis section describes the various attributes and methods of cloning using NMM.

NetWorker save set concepts

A single NMM backup creates multiple save sets with different purposes, whereas traditional client backups only produce a single save set. To properly use clones, you must understand these save sets to ensure that they are included in the clone creation and the clone recovery procedures.

The following table provides an overview of the save sets created during a single backup group.

Table 3 Save set type (page 1 of 4)

Save set type Description

Rollover save set • Contains the data. • Is associated with a cover save set to form a cover-rollover pairing.

A rollover save set is fully visible with the media database CLI and reporting interfaces.

• Is split into multiple save sets by the backup optimization logic, based on the file systems that are being backed up. For environments where multiple file systems are backed up, for example databases where data files and log files reside on different volumes, multiple rollover save sets are created for a particular server during a single backup.

• Has the same save set name as the save set name for the application or file system that is being backed up. For example, if the save set name from the client resource is the following, then the rollover save set would have this same name:

• Browse and retention period follows standard NetWorker behavior, and is set based on the client resource or other overrides.

Cloning with NMM 15

Cloning

Rollover save set examples

In the following client resource save set name examples, the rollover save set would have the same name:• Exchange Server 2007:

APPLICATIONS:\Microsoft Exchange 2007\First Storage Group• Exchange Server 2010:

APPLICATIONS:\Microsoft Exchange 2010\First Mailbox Database• Exchange Server 2013:

APPLICATIONS:\Microsoft Exchange 2013\First Mailbox Database• Hyper-V Server:

APPLICATIONS:\Microsoft Hyper-V\<Virtual Machine Display Name>

• SharePoint Server:Save set:APPLICATIONS:\Microsoft Office SharePoint ServicesRollover save sets:APPLICATIONS:\Microsoft Office SharePoint ServicesSYSTEM COMPONENTS:\

• SQL Server:APPLICATIONS:\ SqlServerWriter\<SQLSERVER>[%5C<INSTANCE>]\<DATABASE>

Note: In SharePoint Server 2007, 2010, and 2013 environments, backing up APPLICATIONS:\Microsoft Office SharePoint Services will back up the SharePoint Configuration Data. SharePoint Configuration Data is internally mapped to SYSTEM COMPONENTS:\ in the media database, log files, and indexes.

Metadata save set A metadata save set is a special save set that contains additional metadata that is required by the NMM software to perform recovery operations. The metadata save set:• Includes VSS documents, file history, and other information• Is fully visible with the media database CLI and reporting

interfaces.• Browse and retention period follows standard NetWorker behavior,

and is set based on the client resource or other overrides.

Note: The save set name for the metadata save set is the same name as the metadata file that was created and backed up from disk. For example: C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT1192235146.xml




Cloning

Display save set A display save set is one that contains no backup data. It only contains index records that are used to display the backup in the NMM software.Consider the following:• The save set name for the display save set is always “VSS:/”.• The browse and retention period for the display save set is

recorded in the media database as having no browse or retention expiration. The save set inherits the browse and retention of other save sets for the same backup.

Note: The display save set is not associated with a cover save set, and is a special type of cover save set which has no rollover. However, unlike cover save sets associated with rollover data save sets, the display save set is fully visible with the Media Database Query utilities.

Dummy save set A dummy save set is specific to Exchange server passive node backup. The dummy save set does not contain any data and is used as part of the NetWorker scheduling workflow to manage index entries for the passive and active nodes. The save set is not required as part of the recovery process and there is no requirement to clone or stage this save set. It will not be covered in the cloning procedures.



Cloning with NMM 17

Cloning

Cover save set A cover save set is a special save set for snapshot management. Consider the following:• The cover save set is a placeholder save set that is created in the

backup workflow. • The cover save set is a hidden save set in that media database

utilities and reporting do not typically display this save set by default. Some forms of the media database query CLI display the save set.

• Multiple cover save sets are created when multiple file systems are backed up. Backup optimization logic splits the backup into multiple save sets by file system so that the backup can be performed in parallel. A separate cover save set is created for each of these per-file system save sets.

• The save set name for the cover save set is the same as the save set name for the application or file system being backed up: Exchange Server2007:

APPLICATIONS:\Microsoft Exchange 2007\First Storage GroupExchange Server 2010:

APPLICATIONS:\Microsoft Exchange 2010\First Mailbox Database

Exchange Server 2013:APPLICATIONS:\Microsoft Exchange 2013\First Mailbox Database

Hyper-V Server: APPLICATIONS:\Microsoft Hyper-V\<Virtual Machine Display Name>

SharePoint Server:APPLICATIONS:\Microsoft Office SharePoint Services SQL Server:APPLICATIONS:\SqlServerWriter\<SQLSERVER>[%5C<INSTANCE>]\<DATABASE>

Note: In SharePoint Server 2007, 2010, and 2013 environments, backing up APPLICATIONS:\Microsoft Office SharePoint Services will back up the SharePoint Configuration Data. SharePoint Configuration Data is internally mapped to SYSTEM COMPONENTS:\ in the media database, log files, and indexes. The cover save set should exist for both “APPLICATIONS:\Microsoft Office SharePoint Services” and SYSTEM COMPONENTS:\.

Notice: The cover save set has the same name.

• The browse and retention period for the cover save set is recorded in the media database as having an expiration of 2038. The cover inherits the browse and retention of its rollover save set pairing.




Cloning

NMM media database attributes

The media database record provides information to the NetWorker server and the NMM software to determine the relationship among save sets. This information is stored in the Media Database Record Attributes field, and is used internally by the NMM and the NetWorker software.

The snap_sessionid attribute is a globally unique identifier (GUID):

◆ It is generated when the backup starts on the client. If the group contains multiple clients, each client will be assigned its own snap_sessionid value.

◆ Provides a grouping of save sets created for a single backup.◆ Can be used to inspect the media database query results to identify the group of save

sets for a single backup.

The cover_id attribute is a SavesetID:

◆ It appears on the rollover save sets that contain the application data. ◆ Contains the cover save set ID pairing for a rollover save set.◆ Can be used to inspect the media database query results to identify the cover save set

pairing for a rollover save set.

Cloning procedures

The following topics describe how to perform various procedures related to cloning save sets.

Performing automated cloningSave sets can be automatically cloned when the backup group that contains the save set has completed.

This clone method is suitable for smaller environments, or a small number of clients where the clone operations must be completed quickly and automatically as part of the backup window:

To configure automated cloning:

1. Connect to the NetWorker server in NetWorker Management Console.

2. In the NetWorker Administration window, select Configuration.

3. Right-click the NMM group resource and then select Properties.

4. Select the Clones option.

5. Select the clone pool that will be used to direct the NMM backups.

Performing manual scripted cloningYou can build custom cloning scripts using the NetWorker mminfo and nsrclone commands. The mminfo command is used to generate the list of save sets to clone, and the nsrclone command is used to clone the NMM save sets.

Using mminfo -q for queries

When using the mminfo -q command to generate the list of save sets to clone, there are a number of attributes that can be specified to constrain the save sets that are queried in the media database.

Cloning with NMM 19

Cloning

The following table lists the common attributes that are used to specify a query, and describes their use to ensure that all NMM save sets are identified for cloning.

One form of the mminfo query returns all NMM save sets. This query uses the following parameters:

mminfo -s <server_name> -v -ot -q group=<group_name> -r ssid,nsavetime,ssflags,level,savetime(22),totalsize,name,client

The server name is optional if this command is run on the NetWorker server and required if run from an NMM client. Any change to the list of query parameters and the query will not return all of the NMM save sets.

The NetWorker Command Reference Guide provides more information about the query specifications supported by the mminfo command.

Using mminfo -r for reports

When using the mminfo command with the -r option to generate the list of save sets to clone, there are a number of attributes that can be specified to limit the reported save set information based on the query used.

Table 4 Mminfo query attributes

Attribute Usage details

Pool

Query by pool is supported but should not be used in combination with the group query option.When a query is performed by media pool, always consider whether a separate snapshot pool was used and include this pool in the query.

Volume

Query by volume is supported.When a query is performed by volume, always consider whether multiple volumes were used during the backup and include all of these volumes in the query. If using a snapshot pool, include that volume.

NameQuery by save set name is not recommended because the metadata save set will have a different save set name for each backup and is prone to error.

Savetime

Query by time range in conjunction with other parameters is supported.Always observe the run times for the backup groups that are being cloned to ensure that the time range is sufficient.

Client

Query by client name is supported.When cloning Exchange Server 2007 CCR passive node backups, always use the NetWorker client name for the Exchange Server 2007 virtual server. Backups are recorded against the Exchange Server 2007 virtual server.When cloning Exchange Server 2010 Database Availability Group (DAG) backups, always use the NetWorker client name for the Exchange Server 2010 DAG. Backups are recorded against the Exchange Server 2010 DAG.When cloning Exchange Server 2013 DAG backups, always use the NetWorker client name for the Exchange Server 2013 DAG. Backups are recorded against the Exchange Server2013 DAG.

GroupQuery by group name is supported but should not be used in combination with the pool query option.


Cloning

When using the -r option, do not use sumflags, pool, or volume.

These report specifications suppress the reporting of cover save sets, but will not impact the cloning of all save sets if the correct NetWorker server and storage node versions are used. When a rollover save set is passed to nsrclone, it automatically includes the cover save set. Ensure that all of the rollover save sets are present in the list, but do not include the cover save set.

Using nsrclone

When using the nsrclone command to clone NMM save sets, there are a number of options that can be specified.

The following table lists the common attributes that are used to clone NMM save sets, and describes their options.

The NetWorker Command Reference Guide provides additional information about nsrclone command options.

Performing save set cloning using the NMCWhen using the NetWorker Management Console (NMC) save set cloning feature, ensure that all of the save sets that were generated in the NMM backup are included in the clone.

To verify that all of the save sets that were generated in the backup are included in the clone:

1. Connect to the NetWorker server by using NMC.

2. Click Media.

Table 5 Save set options

nsrclone save set listing option Supported Notes

-S [ssid [, ssid …] Yes Scripts must ensure that all NMM save sets are listed.

-V [volid, [, volid …]

Yes Scripts must ensure that all volumes written to by an NMM backup are supported.

-g [group-name] Yes This option is supported by NMM.

-t, -e Yes Ensure that the scripts include all NMM save sets in the time range.

-N [saveset-name] No Do not use this option.

Save set names can not be predicted ahead of time for the NMM software.

-l [level spec] No Do not use this option.

Backup levels might be different than expected.

All other options Yes All other nsrclone options are supported.

Cloning with NMM 21

Cloning

3. In the left navigation tree, select Save sets.

4. Build a required save set query to determine the list of save sets to be cloned. The table below lists the supported query options.

5. Select Save Set List to generate the save set list based on the query specifications.

6. Select all of the required save sets to clone:

a. Right-click an item in the save set list and then click Clone.

b. In the Target Clone Media Pool list, select the appropriate clone pool.

c. Click OK.

7. To monitor the status of the clone job:

◆ For NetWorker 7.6.x and later, observe the Log window.

◆ For NetWorker 7.5.x, on the Monitoring menu, select Show Manual Clone.

Table 6 Save set query options (page 1 of 2)

Save set query option

Supported by NMM Considerations

Client name Yes When cloning Exchange Server 2007 CCR passive node backups, always use the NetWorker client name for the Exchange Server 2007 virtual server.Backups are recorded against the Exchange virtual server.

Save set No Do not use this feature. There are multiple save set names for each backup.

Save set ID No Do not use this feature.

Volume Yes When a query is performed by volume:• Always consider whether multiple volumes were used

during the backup.• Include all of these volumes in the query. If using a snapshot pool, include that volume.

Pool Yes This feature should not be used in combination with the group query option.When a query is performed by media pool:• Always consider whether a separate snapshot pool was

used.• Include this pool in the query.

Checkpoint ID No Do not use this feature.

Copies Yes The copies value will be 2 for save sets residing on any advanced file type device and 0 for all other device types. Higher values indicate that the save set has been cloned previously.

Save time range Yes Always observe the run times for the backup groups that are being cloned to ensure that the time range is sufficient.


Cloning

Performing scheduled cloning Clone jobs can be run according to a schedule. This method is suitable for environments where copies of the save sets are required to be regularly cloned as part of a well-defined maintenance cloning window. This cloning window runs independent of the main backup operation.

To configure a scheduled clone operation for either a regular or optimized clone, use the NMC. For example:

1. From the NetWorker Administration window, click Configuration.

2. In the navigation tree, click Clones.

3. From the File menu, select New to open the Create Clone window.

4. In the Name attribute:

a. Create a unique name to identify the scheduled Clone resource.

b. In the Comment attribute, type any additional information.

5. If the clones are to use policies that are different than the original backup policies:

a. Set the Browse Policy attribute.

b. Set the Retention Policy attribute.

6. In the Write clone data to pool attribute, specify the clone pool that targets the devices on which the clones will be stored.

7. To skip invalid save sets, select Continue on the save set error check box.

If the Skip invalid save sets attribute is not selected, which is the default setting, an invalid save set will stop the clone operation and generate an error message.

8. In the Limit number of save set clones attribute, specify a value to limit the number of clones for each save set that might be produced in the clone pool for a scheduled clone operation:

• The default value of 1 allows only one clone to be made to the target pool for each save set. For example, use this default value of 1 to manually restart an interrupted clone operation. This creates only the missed clones, but does not reproduce clones that were already successfully created.

• A zero (0) setting allows an unlimited number of duplicate clones.

Status No Do not use this feature.

Type No Do not use this feature.

Maximum level No Do not use this feature.

Table 6 Save set query options (page 2 of 2)

Save set query option

Supported by NMM Considerations

Cloning with NMM 23

Cloning

The NetWorker software allows only one unique save set clone to be stored on a single volume. If duplicate or multiple clones of the same save set are created, each is stored on a different volume in the pool.

9. Configure the schedule for the clone job:

To reduce the use of resources, schedule clone operations to be performed after the backup window has completed.

a. Select Enable to enable the clone job to run at its scheduled times.

b. In the Start Time attribute, set the start time. Click the spin arrows or type values.

c. For the Calendar:

– Select either Weekly by day or Monthly by day.

– Select the days on which the clone job is to run.

d. To repeat the clone job within a day, specify an Interval Time in hours.

For example:

• If the Start Time is 6 a.m., and the Interval Time is 6 hours, then the clone job will run at the following times: 6 a.m., 12 p.m., and 6 p.m.

• If the Limit the number of save set clones value is set, then the repeat clone job will fail after the limit is reached.

10. Select Save Set Filters and then specify the source save sets to include in the scheduled clone job.

There are two main options:

a. Select the clone save sets that match the selections and then limit the save sets that are to be cloned by specifying the following details:

– Save groups

– NetWorker clients

– Pools (in the case of NMM save sets, always consider whether a separate snapshot pool was used and include this pool)

– Save set levels (using this option can be problematic as backup levels can be different than expected)

– Save set name, as specified in the NetWorker Client resource.

When cloning NMM save sets, the save set name option is prone to error and not recommended. The metadata save set will have a different save set name for each backup.

– Save sets from the past number of days, weeks, months, or years


Cloning

b. Select Clone specific save sets and type the names of the source save sets to be cloned:

– Use either the save set ID (ssid) or the clone ID (clonid).

– Use a separate line for each save set name.

– To find save set and clone IDs, use either of the following methods:

In the NetWorker Administration window, click Media and then select Save Sets in the navigation tree. Specify values for the search.

Use the NetWorker mminfo command. The EMC NetWorker Administration Guide provides details.

11. To review save set filter settings, click Preview Save Set Selection.

12. Click OK to save the scheduled clone job.

Validating cloningYou must validate that all NMM save sets that were cloned from the start of clone process to the end time.

To validate that all the NMM save sets are cloned, use the following mminfo command:

mminfo -v -ot -q "group=[my-group],savetime>[t1],savetime<[t2]" -r"ssid,validcopies,nsavetime,ssflags,savetime(22),name,client,volume"

Consider the following:

◆ This query returns all of the save sets for the group in the time range specified with [t1] and [t2]. [t1] and [t2] should be specified in the MM/DD/YY HH:mm:SS format.

◆ The -ot flag sorts the save sets by time.

◆ The copies value indicates the number of copies.

◆ On Unix systems, one of the following is required:

• The options following -r must be enclosed in quotes

or

• The “22” following the savetime option in the example above must be enclosed in quotes.

A save set with a copy count of 1 does not have a clone. If the backup was done to AFTD, the number of copies for save sets is reported as 2 prior to cloning. For AFTD devices, ensure that the copy count is greater than 2.

Cloning with NMM 25

Cloning

Cloning Exchange databasesThe following table lists the typical NMM deployments for Exchange Server 2007, 2010, and 2013.

Exchange Server 2007 and 2010 are supported in NMM 2.4 and later.Exchange Server 2013 is supported in NMM 3.0 and later.

Although Microsoft currently supports 50 Exchange server databases per Exchange server, these deployments are based on supporting only a maximum of 16 Exchange Server databases per Exchange server in a single NetWorker backup group.

Exchange cloning save set example of a single NetWorker client resource

This Exchange server example illustrates NMM save sets that were created by a single run of a backup group.

In this example:

◆ The Exchange storage group with Exchange data files is on the E:\ drive.

◆ The Exchange log files are on the F:\ drive.

◆ The Serverless Backup policy is used so that a rollover is created but no persistent snapshot is retained.

Table 7 Factors for cloning NMM backups of Exchange Server

Factor Description

Multiple NetWorker groups Multiple NetWorker groups are deployed for a single Exchange server according to the configuration requirements of the NMM software.

Microsoft Exchange database save sets

The Exchange database save sets are listed in the client resource according to the configuration requirements of the NMM software.

Frequent backup failures Frequent backup failures occur in Exchange environments.

It is beyond the scope of this document to provide advice on how to resolve such failures. It is pointed out only to indicate that failures might result in partially successful backups that should be included in the recovery process.


Cloning

The following figure illustrates a single NetWorker client resource for Exchange in the NetWorker group.

Figure 1 NMM save set for single NetWorker client resource for Exchange

The preceding save set example is just one of many possible configurations. Your environment setting may differ from the displayed examples.

Exchange save sets within the media database

The following table summarizes the save sets within the media database. The save sets are created by using the output from the mminfo -S -q group=[groupname] command.

Cloning Exchange databases 27

Cloning

The -q group=[groupname] command is the only method to display the cover save sets. This command is used to validate scanning. However, when used in combination with certain -r flags, the cover save sets are not displayed.

In this example:

◆ There is one pair of save sets [one for original Connected_Save sets and *Coverid] per Volume [E:\]. Overall there are 4 save sets for both E:\ and F:\.

◆ The *connected save sets and *coverid attributes are used to link to the two pairs of save sets:

• The K flag indicates the cover save sets.

• One pair is for the files on the E:\ drive.

• The other pair is for the files on the F:\ drive.

Table 8 Exchange example save set summary

Save set name Description ssFlags Media database attributes

APPLICATIONS:\Microsoft Exchange 2013\ FirstDatabase

Cover save set for rollover save set as indicated by the *connected_savesets attribute.

vKF *connected save sets: <unique ID>; *coverset:Yes;*snap_sessionid: <unique ID>;


Rollover (data) save set for the files of E:\. The associated cover save set is determined from the *coverid attribute.

vF *coverid: <unique ID>; *snap_sessionid: <unique ID>


Cover save set for rollover save set as indicated by the *connected_savesets attribute.

vKF *connected save sets: <unique ID>; *coverset:Yes;*snap_sessionid :<unique ID>;


Rollover (data) save set for the files of F:\. The associated cover save set is determined from the *coverid attribute.

vF *coverid: <unique ID>; *snap_sessionid: <unique ID>;

C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENTxxxxxxxxxxxml

Metadata save set vrF *snap_sessionid: <unique ID>; *stream_metadata:Yes;

VSS:/ Display save set vKF *coverset:Yes; *snap_sessionid:<unique ID>;


Cloning

Note: The relationship between the other save sets is held in the *snap_sessionid attribute. All save sets have the same *snap_sessionid value for this client within this group at this backup time.Other backup groups, clients, or even the same groups and clients that are run at different times will have different and unique session IDs.

NMM cloning save set for Exchange with a NetWorker group and multiple client resources

The following figure illustrates an example of a NetWorker group that has three client resources for three Exchange servers.


Cloning

Figure 2 NMM save set for Exchange with a NetWorker group

This example illustrates the following:

◆ There is one cover/rollover save set pair for each file system per save set on a per client basis.

◆ There is one metadata and display save set per client resource.

◆ The snapshot session ID will be unique for each client.

In the preceding figure, a single group containing three clients generates a total of 18 save sets. These save sets will be required for upcoming operations such as cloning or recovery. The ability to determine the appropriate session IDs and save sets is critical to successful cloning and recovery operations.


Performing a volume clone for Exchange ServerWhen using the NMC volume cloning feature, ensure that all of the volumes that were used in the NMM backup are included in the clone.

To verify that all of the volumes that were used in the NMM backup are included in the clone:

1. On the NMM client, launch the NetWorker User for Microsoft software.

2. In the Client drop down list, select the NMM client.

If the NMM client is part of a cluster, select the virtual client.

3. From the left pane, select one of the following:

• Recover > Exchange Recover Session > Database for Microsoft Exchange 2007 systems

• Recover > Exchange 2010 Recover Session > Database for Microsoft Exchange 2010 systems

4. To change the backup time:

a. Click the calendar icon.

b. Select the required date and time.

c. In the Browse window, mark all of the backups that will be cloned.

5. Verify that the correct full and all associated incremental or differential backups have been selected:

a. Right-click one of the selected items.

b. Select Version.


Cloning

c. Click Cancel.

6. Verify that the correct volume has been selected:


b. Select Required Volumes.

The Required Volumes dialog box correctly displays all volumes needed for the currently browsed backup time, but if that backup is an incremental, volumes from dependent incrementals or the full might not be displayed. To obtain an accurate list of required volumes for an incremental backup, repeat this procedure for each backup of the database back to and including the most recent full.

NetWorker volumes are not associated with a snapshot backup until the snapshot has been rolled over to a NetWorker server. If you choose to view the required volumes for an application data snapshot that has not been rolled over, no volumes will be displayed.

c. Note the listed volumes.

d. Click OK.

For more information about how to use the NetWorker User for Microsoft required volumes feature, refer to the NetWorker Module for Microsoft Administration Guide.

7. Close the NetWorker User for Microsoft software.

8. Connect to the NetWorker server by using the NMC.

9. Click the Media button.

10. In the left navigation tree, select either of the following:

• Disk volumes

• Tape volumes

11. Select each volume that is displayed in the Required Volumes list:

a. Right-click in the Volume list window and then select Clone.


c. Click OK.

12. To monitor the status of the clone job observe the Log window.


Cloning

Cloning with NMM in Hyper-V environmentsThe following table lists factors that customers should consider when deploying cloning or restoring from clones with NMM for Hyper-V environments.

Hyper-V CSV example of a single NetWorker client resource

This example illustrates NMM save sets that were created by a single run of a backup group, a Hyper-V CSV single NetWorker client resource in the NetWorker group.

Figure 3 Hyper-V CSV save set using a single client in a backup group

Table 9 Cloning in Hyper-V environments

Factor Description

Full backup only • NMM only supports full backup for Hyper-V.• Deploying cloning for Hyper-V guarantees full backup capture

regardless of the cloning schedule.• When restoring from clones, the number of backups required is

simplified since only the full backup is required.

Single NetWorker groups A single NetWorker groups is typically deployed for a single Hyper-V environment.

Item-level save sets NMM supports item level save sets for the Hyper-V Initial Store and virtual machines.

Note these save set names when validating clones and restoring clones.


Cloning

In this example:

◆ The Hyper-V Child Partition .vhd and configuration files are on c:\ClusterStorage.

◆ The Serverless Backup policy is used to create a rollover that does not retain a persistent snapshot.


Hyper-V CSV save sets within the media database

The following table summarizes the save sets within the media database, derived from the output from the following command:

mminfo -S -s [NetWorker_servername] -q group=[groupname]

Cover save sets can only be displayed by using -S in combination with the -q group=[groupname] command. This command is used to validate scanning. However, when used in combination with certain -r flags, the cover save sets are not displayed.

Note the following:

◆ The relationship between the other save sets is held in the *snap_sessionid attribute.

◆ All save sets have the same *snap_sessionid value for this client within this group at this backup time.

Table 10 Hyper-V CSV save sets within the media database

Save set name Description FlagsMedia database attributes

C:\LG_PLACEHOLDER_<unique ID>

The associated cover save set is determined from the *coverid attribute.

vKF *connected savesets: <unique ID>;*coverset: Yes; *snap_sessionid: <unique ID>;

APPLICATIONS:\Microsoft Hyper-V\VMLOCALS1

Rollover (data) save set for the files of child partition VMLOCALS


APPLICATIONS:\Microsoft Hyper-V\VMLOCALS2

Rollover (data) save set for the files of child partition VMLOCALS


C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT17<unique ID>.xml


VSS:/ Display save set vKF *coverset:Yes; *snap_sessionid: <unique ID>;

Cloning with NMM in Hyper-V environments 33

Cloning

◆ Other backup groups, clients, or the same groups and clients that are run at different times will have different and unique session IDs.

NMM cloning save set example for Hyper-V with a NetWorker group

The following example describes a NetWorker group that contains three client resources for three Hyper-V servers.

Figure 4 NMM save set example for Hyper-V with a NetWorker group

This example illustrates the following:

◆ There is one rollover save set pair for each file system per save set on a per client basis.


◆ The snapshot session ID is unique for each client.


Cloning


Hyper-V example of a single NetWorker client resource

This example describes NMM save sets for Hyper-V that were created by a single run of a backup group.

In this example:

◆ The Hyper-V child partition.vhd files are on the D:\ drive.

◆ The Hyper-V child partition configuration files are on the C:\ drive.

◆ The Serverless Backup policy was used so a rollover is created but no persistent snapshot is retained.

The following figure illustrates a single Hyper-V child partition NetWorker client resource in the NetWorker group.

Figure 5 Hyper-V save set using a single client in a backup group



Cloning

Hyper-V save sets within the media database

This table summarizes the save sets within the media database. It was created by using the output from the following command:

mminfo -S -s [NetWorker_servername] -q group=[groupname]

Cover save sets can only be displayed by using -S in combination with the -q group=[groupname] command. This command is used to validate scanning. However, when used in combination with certain -r flags, the cover save sets are not displayed.

In this example, there are:

◆ Two pairs of save sets (four in total) with the name APPLICATIONS:\Microsoft Hyper-V\VMLOCALS. These are the cover-rollover save set pairs.

◆ The *connected save sets and *coverid attributes are used to link to the two pairs of save sets:

• The K flag indicates the cover save sets.

• One pair is for the files on the C:\ drive.

• The other pair is for the files on the D:\ drive.

Table 11 Hyper-V save sets within the media database

Save set name Description FlagsMedia database attributes

APPLICATIONS:\Microsoft Hyper-V\VMLOCALS

Cover save set for rollover save set as indicated by the *connected_save sets attribute.


APPLICATIONS:\Microsoft Hyper-V\VMLOCALS

Rollover (data) save set for the files of child partition VMLOCALS The associated cover save set is determined from the *coverid attribute


C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT1794653518.xml


VSS:/ Display save set vKF *coverset:Yes; *snap_sessionid:<unique ID>;


Cloning

Note the following:



◆ Other backup groups, clients or even the same groups and clients that are run at different times will have different and unique session IDs.

NetWorker group with resources for multiple Hyper-V servers example

This example describes a NetWorker group that is composed of three client resources for three Hyper-V servers.

Figure 6 Hyper-V multiple servers save set example with a NetWorker group

In this example:


Cloning




◆ A single group containing two clients generated a total of 12 save sets. The ability to determine the appropriate session IDs and save sets is critical to successful cloning and recovery operations.


Performing scheduled cloning for Hyper-V When using the NMC volume cloning feature, ensure that all of the volumes that were used in the NMM backup are included in the clone.

Note: In this procedure, replace Initial Store with Host Component for Windows Server 2012 and Windows Server 2012 R2.

To verify that all of the volumes that were used in the NMM backup are included in the clone:

1. On the NMM client, launch the NetWorker User for Microsoft software.


If the NMM client is part of a cluster, select the virtual client.

3. From the left pane, select Recover > Hyper-V Recover Session.

4. To change the backup time, do the following:

a. Click the Calendar icon and select the required date and time.

b. In the Browse window, mark all of the following:

– Hyper-V virtual machines

– Initial Store backups that will be cloned

5. To ensure the correct volume has been selected, do the following:



NetWorker volumes are not associated with a snapshot backup until the snapshot has been rolled over to a NetWorker server. If you select to view the required volumes for an application data snapshot that has not been rolled over, no volumes will be displayed.


http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-010-428.pdf

Cloning

c. Note the listed volumes.

d. Click OK.

For more information about how to use the NetWorker User for Microsoft required volumes feature, refer to the NetWorker Module for Microsoft Administration Guide.

6. Close the NetWorker User for Microsoft program.

7. Connect to the NetWorker server by using the NMC.

8. Click Media.

9. In the left navigation tree, select either of the following:

• Disk volumes

• Tape volumes

10. Select each volume that is displayed in the Required Volumes list:

a. Right-click in the Volume list window and then select Clone.


c. Click OK.

11. To monitor the status of the clone job, observe the Log window.


Cloning

Cloning with NMM in a SharePoint environmentThis section outlines the requirements for SharePoint Server versions supported by NMM.

The following table lists factors that customers should consider when deploying cloning or restoring from clones with NMM for SharePoint 2007, SharePoint 2010, and SharePoint 2013 environments.

The save set name for the metadata save set is the same name as the metadata file that was created and backed up from disk.

For example, C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT1192235146.xml”

Table 12 SharePoint deployment considerations

Factor Description

Full backup only • NMM only supports full backup for SharePoint 2007, SharePoint 2010, or SharePoint 2013 backups. This applies to both SharePoint farm level backups and SharePoint content database backups.

• When deploying cloning for SharePoint farm level backups, you are guaranteed to capture the full backup regardless of the cloning schedule.

• When restoring from clones, the number of backups required is simplified since only the full backup is required.

Item level save sets

NMM supports item level save sets for SharePoint 2007, SharePoint 2010, or SharePoint 2013 Content databases.The NMM software uses the SQL database save sets for backup of the SQL databases that are part of the SharePoint environment.Customers should understand these save set names as they validate cloning and recovery clones.

Multiple NetWorker clients

• Multiple NetWorker clients are deployed for each SharePoint farm member for SharePoint farm backups. The save sets described in NetWorker Save set Concepts will exist for each individual SharePoint farm member that is backed up as part of the NetWorker Group.

• Customers that deploy cloning for SharePoint farm backups must ensure that all farm clients are cloned.

• For SharePoint farm level recovery, cloning recovery procedures need to include all SharePoint farm clients.

• For SharePoint content database level recovery, cloning recovery procedures must include both of the following:-The SharePoint web front end client against which backups are scheduled.-The SQL Server clients where the content database to be restored was backed up.

Both farm and content database backups

NMM supports the ability to perform both a full backup of the SharePoint farm and backup of individual SharePoint content databases. You can deploy multiple NetWorker groups to perform both SharePoint farm level backup and more frequent SharePoint content database level backups.When deploying cloning, ensure that the SharePoint farm level backup is cloned to provide a full recovery point for the farm. You can choose to also clone the individual content database backups to provide additional recovery points.

Additional requirements

For SharePoint 2007, 2010, and 2013 environments, backing up APPLICATIONS:\Microsoft Office SharePoint Services backs up the SharePoint Configuration Data


Cloning

The display save set is not associated with a cover save set, and is a special type of cover save set that has no associated rollover set. However, unlike cover save sets associated with rollover data save sets, the display save set is fully visible with the Media Database Query utilities.

SharePoint cloning save set example of a single client in backup group

The following example illustrates NMM save sets that were created by a single run of a backup group.

In this example:

◆ The SharePoint database with data files is on the D:\ drive.

◆ The SharePoint database log files are on the C:\ drive.


The following figure illustrates a SharePoint single NetWorker client resource in the NetWorker group.

Figure 7 SharePoint single client in a backup group


Cloning with NMM in a SharePoint environment 41

Cloning

SharePoint save sets within the media database

The following table summarizes the save sets within the media database and were created using the output from the mminfo -S -s [NetWorker_servername] -q group=[groupname] command.

The only method to display the cover save sets is by using the -S in combination with the -q group=[groupname] command. This command will be used later in procedures in this document to validate scanning. However, when used in combination with certain -r flags, the cover save sets is not displayed.

In this example:

◆ One pair of save sets is named APPLICATIONS:\Microsoft Office SharePoint Services. This is the cover-rollover save set pair.

◆ The *connected save sets and *coverid attributes are used to link the two save sets.

◆ The K flag indicates the cover save sets.

Also, note the following:




Table 13 SharePoint save sets within the media database

Save set name Description Flags Media database attributes

APPLICATIONS:\Microsoft Office SharePoint Services

Cover save set for rollover save set as indicated by the *connected_save sets attribute.


APPLICATIONS:\Microsoft Office SharePoint Services

Rollover (data) save set The associated cover save set is determined from the *coverid attribute.

vF *coverid:<unique ID>; *snap_sessionid: <unique ID>;


Metadata save set vrF *snap_sessionid:<unique ID>; *stream_metadata:Yes;

VSS:/ Display save set vKF *coverset:Yes; *snap_sessionid: <unique ID>;


Cloning

Save set example with multiple SharePoint client resources in a NetWorker group

The following example describes a NetWorker group that has three client resources for three SharePoint servers.

Figure 8 Save set example of three client resources for three SharePoint servers

In this figure, a single group containing 3 clients generated a total of 14 save sets. These save sets are required for cloning and recovery operations. Determine the appropriate session IDs and save sets is critical to successful cloning and recovery operations.

Cloning with NMM in a SharePoint environment 43

Cloning

In this example:





SQL Server requirementsThis section outlines the requirements for SQL Server versions supported by NMM. The following example describes NMM save sets that were created by a single run of a backup group.

In this example:

◆ There is an SQL database with data files on the E:\ drive.

◆ The SQL database log files are on the F:\ drive.



Cloning

The following figure illustrates a single SQL Server NetWorker client resource in the NetWorker group.

Figure 9 Single SQL Server NetWorker client in backup group


SQL Server save sets within the media database

The following table summarizes the save sets within the media database, and were created using the output from the mminfo -S -s [NetWorker_servername] -q group=[groupname] command.

The only method to display the cover save sets is by using the -S in combination with the -q group=[groupname] command. This command will be used later in procedures in this document to validate scanning. However, when used in combination with certain -r flags, the cover save sets is not displayed.

SQL Server requirements 45

Cloning

In this example, there are two pairs of save sets (four in total) with the name APPLICATIONS:\ SqlServerWriter\ APPLICATIONS:\SqlServerWriter\MYSQLSVR\Reports.db These are the cover-rollover save set pairs.

The *connected save sets and *coverid attributes are used to link to the two pairs of save sets:

◆ The K flag indicates the cover save sets.

◆ One pair is for the files on the E:\ drive.

◆ The other pair is for the files on the F:\ drive.

Note the following:




Table 14 Save sets within the media database

Save Set Name Description Flags Media Database Attributes

APPLICATIONS:\SqlServerWriter\MYSQLSVR\Reports.db

Cover save set for rollover save set 4239685367 as indicated by the *connected_save sets attribute.

vKF *connected save sets:4239685367;*coverset:Yes;*snap_sessionid:1286895022;


Rollover (data) save set for the files of E:\ or F:\. The associated cover save set is determined from the *coverid attribute.

vF *coverid:4256462581;*snap_sessionid:1286895022;


Cover save set for rollover save set 4206130936 as indicated by the *connected_save sets attribute.

vKF *connected save sets:4206130936;*coverset:Yes;*snap_sessionid:1286895022;


Rollover (data) save set for the files of E:\ or F:\. The associated cover save set is determined from the *coverid attribute.

vF *coverid:4222908151; *snap_sessionid:1286895022;


Metadata save set vrF *snap_sessionid:1286895022; *stream_metadata:Yes;

VSS:/ Display save set vKF *coverset:Yes; *snap_sessionid:1286895022;


Recovery

CHAPTER 3Recovery

This chapter describes the recovery procedure and related information.

◆ Recovering data with NMM...................................................................................... 48◆ Exchange server notes ............................................................................................ 61◆ Hyper-V CSV notes .................................................................................................. 63◆ Hyper-V notes ......................................................................................................... 63◆ SharePoint notes .................................................................................................... 64◆ SQL notes ............................................................................................................... 65

47

Recovery

Recovering data with NMMThis section provides the steps necessary to recover a save set that is in a recoverable state.

Determining the rollover save set name

The rollover save set is the backup save set that contains the backup of the NMM data.

There are two methods to inspect the media database and determine the name of the save sets:

◆ Use NMC to inspect the save set field for the NMM client configured on the NetWorker server.

or

◆ On the NMM client, run the nsrsnap_vss_save command:

• If the Exchange server is a stand-alone node or local continuous replication (LCR) active node, type:

nsrsnap_vss_save -?

• If the Exchange server is on an Exchange Server 2007 single copy cluster (SCC) node

or

If the application server is on a virtual host, run this command from the physical node that is currently hosting the application server

type:

nsrsnap_vss_save -c virtual_server_name -?

• In an Exchange 2007 CCR environment, type the following on both the active and passive nodes on one line:

nsrsnap_vss_save -c <physical_server_name> -A NSR_VIRT_SERV=<virtual_server_name> -?

Where <physical_server_name> and <virtual_server_name> are replaced with the appropriate server names for your environment.

• If the Exchange Server 2010 or 2013 server is a stand-alone node, type:

nsrsnap_vss_save -?

• If the Exchange Server 2010 or 2013 server is a DAG, type:

nsrsnap_vss_save -v -?

Identifying the required save time range

You can use the mminfo command to identify the required save time range for the backup version that is being restored by querying the media database.

The save time range is the day before (date1) and the day after (date2) the date of the backup which is to be restored.


Recovery

Recovering NMM data from recoverable or eligible for recycling save sets

To determine the status of a save set in the media database, use the mminfo command. You can use the ssflags attribute to provide a summary of the status of each save set.

When generating a report of the ssflags summary of save sets:

◆ An r in the ssflags output denotes that a save set is recoverable and that it has exceeded its defined browse policy.

◆ An E in the ssflags output denotes a save set that is eligible for recycling and that it has exceeded its defined retention policy. This is also referred to as an expired save set.

In the case of incremental or differential save sets, the ssflags value will contain an E only when all dependent incremental, differential, or full backups have also exceeded their defined retention policy period. When all save sets on a volume are eligible for recycling, the volume can be overwritten.

Generating the media database list of the save sets

This section outlines the steps required to identify all of the required save sets for a recover operation of a recoverable original backup or clone.

Generating a media database list of all save sets

1. From a command line prompt on the NetWorker server, run the mminfo command to generate a list of NMM original or cloned save sets in the media database:

mminfo -S -s <NetWorker_server_name> -c <NMM_client_name> -q

”group= <group_name>, savetime>=<date1>, savetime<=<date2>” -ot 1>output.txt 2>&1

Where:

<NetWorker_server_name> is the name of the NetWorker server host.

<NMM_client_name> is the name of the NMM client host.

<group_name> is the name of the group which contained the NMM client when the backup occurred.

<date1> is at least one day before the date range of the NMM original or clone to be restored.

<date2> is at least one day after the date range of the NMM original or clone to be restored.

2. Edit the output.txt file, which resides in the same directory the mminfo command was executed.

3. If the output file contains the following message, the media database does not contain NMM save sets for the client or query options specified:

mminfo: no matches found for the query

Recovering data with NMM 49

Recovery

Make adjustments to the query options specified in the mminfo command. If the query results appear to be missing save sets, “Save set not in media database” on page 56 provides information on locating and adding save sets to the media database.

Identifying the rollover save set

Identify the most recent full backup for the file system or application save set in the output.txt file.

1. Use the rollover save set name identified in “Identifying additional cover and rollover save sets” on page 50 to identify the full backup.

This save set will:

• Not have a K value in the sflags attribute.

• List full in the level attribute.

2. From this full rollover save set backup, record the following:

• ssid

• coverid

• *snap_sessionid

Identifying the cover save set

1. Search the mminfo output for the cover save set associated with the full backup by using the *coverid.

2. Record the ssid value.

Identifying additional cover and rollover save sets

Use the recorded *snap_sessionid for the full backup to:

◆ Search for other rollover and cover save sets with the same *snap_sessionid that match the name of the save set that is being restored.

◆ Record the ssid values for each of these additional cover and rollover save sets.

Identifying the VSS: save set

1. Search the output.txt file for the save set VSS: that has the same *snap_sessionid as the rollover save set.

2. Make note of the following values for the VSS: save set:

• ssid

• All cloneid values

Identifying metadata save set

1. Search the output.txt file for the metadata save set that has the same *snap_sessionid as the rollover save set.

2. This save set has a different name for each backup. It can be recognized as a file name of the form “LG_VSS_CLIENT<unique-ID>.xml“

3. Make note of the ssid value for the xml save set.


Recovery

4. After all of the full backups have been restored, for all incremental backups repeat the steps outlined in this procedure.

This does not apply to the following applications:

• Hyper-V recoveries

• SharePoint Server 2007, SharePoint Server 2010, and SharePoint Server 2013

5. To recover multiple clients or save sets for a client, for each client or save set repeat the steps outlined in this procedure.

How to collect the save set requirementsUse this procedure to list required save sets. Once you are familiar with the NMM required save sets, you can use the backup time to identify the required save sets.

Do not use these procedures until you fully understand all of the NMM save set requirements. Use the procedures in “Generating a media database list of all save sets” on page 49 to identify all of the required save sets for recovery from the recoverable original or clone save sets.

Use the following command to ensure that the cover save sets are displayed:

mminfo -v -ot -q "group=group_name,savetime>=date1,savetime<date2" -r "ssid, cloneid, nsavetime, ssflags, level, savetime(22), ssbrowse, ssretent, name, client, volume” 1>output.txt 2>&1

Where:

group_name is the name of the group that contained the NMM client when the backup occurred.

date1 is at least one day before the date range of the NMM original or clone to be restored.

date2 is at least one day after the date range of the NMM original or clone to be restored.

This query returns all of the save sets for the group in the time range specified. The -ot flag sorts the save sets by time and the information is stored in a file called output.txt. This file resides in the same directory from which the mminfo command was run.

If you experience recovery issues using this method, use the procedures in “Generating a media database list of all save sets” on page 49 to validate the output.

Recovering recoverable save sets to the client file index

If the backup save sets for the rollover, display, metadata and cover save set are recoverable, they can be made browsable for the required length of time to perform the recovery operation. For example: sflags=vrF

1. For each display, metadata, and rollover save set, modify the browse and retention times of the existing save sets:

nsrmm -s <NetWorker_servername> -e <time1> -S <ssid>


Recovery

Where:

<NetWorker_servername> is the name of the NetWorker server.

<time1> is the new desired retention time.

<ssid> is the save set value recorded for each metadata or rollover save set.

Ensure that the new browse and retention dates for the save sets are far enough in the future to allow sufficient time for the recovery to complete.

2. Repopulate the client file index on the NetWorker server with the save set information:

nsrck -L 7 -t <date> <client> 1>nsrck.txt 2>&1

Where:

<date> is a date after the completion of the latest save set that will be restored.

<client> is the name of the NMM client.

Ensure that the volume containing the index backup is available for mounting.

3. Review the output in nsrck.txt for errors once the command has completed.

For example:

a. If any of the following errors are reported:

19779:nsrck: Please run ``nsrck clientname''

9348:nsrck: The index recovery for ' clientname ' failed.

39078:nsrck: SYSTEM error: The operation completed successfully.

Run the following command:

nsrck -L2<client>

Where <client> is the name of the NMM client.

b. Ignore file attribute messages such as the following, they will not impact the NMM recovery:

32222:uasm: Warning: Some file attributes were not recovered: C:\Program Files\EMC NetWorker\nsr\index\clientname\db6\tmprecov\C\Program Files\ EMC NetWorker \nsr\index\clientname\db6\

c. If the nsrck command fails with the error “xxxxx”, the index backup might no longer be referenced in the media database. Use the following command to scan all ssids recorded for the cover, display, metadata and rollover save sets:

scanner -i -S <ssid> <device>

Where:

<ssid> is the save set ID of the save set that will be restored.


Recovery

<device> is the device containing the volume for the save set to be restored.

Ensure that the NMM software is closed on the NMM clients before running the scanner command. If the software is open while the scanner is run, the scanner command may fail with ’Index error, flush Failed'.

d. If browse and retention times set by the scanner are not a long enough duration to complete recovery procedures, for each metadata and rollover save set, modify the browse times of the existing save sets:

nsrmm -s NetWorker_servername -w time2 -S ssid

Where:


<time2> is the new desired browse time.

<ssid> is the save set value recorded for each metadata or rollover save set described in Listing Required Save Sets.

Ensure that the new browse dates for the save sets are far enough in the future to allow sufficient time for the recovery to complete.

Performing an NMM recovery

The following procedure provides the general steps for performing an NMM recovery. Some applications may require additional steps or settings. The application-specific guides provide the full application-specific recovery procedures.

1. On the NMM client, launch the appropriate GUI for recovery, either the NetWorker User for Microsoft program.


3. If the NMM client is part of a cluster, select the virtual client.

4. In the left pane, select Recover, and then select the appropriate application such as:

• Exchange

• Hyper-V

• Hyper-V CSV

• SharePoint

• SQL Server (listed as System)

5. Click the Calendar icon.

6. Select the required date and time.

7. In the Browse window, select all of the required backups.

8. To ensure that the correct full and all of the associated incremental or differential backups have been selected:

a. Right-click one of the marked items.

b. Select Version.

c. Click Cancel.


Recovery

If the required backup version is not displayed, ensure that all of the appropriate save sets have been scanned in and are in a browsable state.

9. To ensure the correct volume has been selected:

a. Right-click on one of the marked items.


The Required Volumes dialog box correctly displays all volumes needed for the currently browsed backup time, but if that backup is an incremental, volumes from dependent incrementals or the full might not be displayed. To obtain an accurate list of required volumes for an incremental backup, repeat this procedure for each backup of the database back to and including the most recent full.

c. Make note of all the listed volumes.

d. Click OK.

10. Start the recovery.

Recovering recyclable save sets

This section discusses recovering a save set that is in a recyclable state.

Recovering NMM data from recoverable or eligible for recycling original or clone save sets

To determine the status of a save set in the media database, use the mminfo command. You can use the ssflags attribute to provide a summary of the status of each save set.

When generating a report of the ssflags summary of save sets:

◆ An r in the ssflags output denotes that a save set is recoverable and that it has exceeded its defined browse policy.

◆ An E in the ssflags output denotes a save set that is eligible for recycling and that it has exceeded its defined retention policy. This is also referred to as an expired save set.

In the case of incremental or differential save sets, the ssflags value will contain an E only when all dependent incremental, differential, or full backups have also exceeded their defined retention policy period. When all save sets on a volume are eligible for recycling, the volume can be overwritten.

The use of the mminfo command to generate a list of the required NMM save sets is covered later in this procedure.

Recovering recyclable save sets to the client file index

If the backup save sets for the rollover, display, metadata, and cover save set found in the Listing Required Save Sets section have expired and are recyclable, they can be made browsable for the required length of time to perform the recovery operation. For example: sflags=vrEF


Recovery

To recover recyclable save sets to the client file index:

1. Reset the browse and retention time for all save sets recorded in “Generating a media database list of all save sets” on page 49:

nsrmm -e <time1> -S <ssid>

Where:

<time1> is the new desired retention time.

<ssid> is the save set value recorded for each display and cover save set.

2. For each save set, use its associated ssid and cloneid to reset the save set to expired/recoverable:

nsrmm -o notrecyclable -S <ssid/cloneid>

3. Repopulate the client file index with the save set information:

nsrck -L 7 -t <date><client> 1>nsrck.txt 2>&1

where:

<date> is a date after the completion of the latest save set that will be restored.


Ensure that the volume containing the index backup is available for mounting.

4. Review the output in nsrck.txt for errors once the command has completed.

for example:

a. If the following messages are reported:

Messages:19779:nsrck: Please run ``nsrck clientname''9348:nsrck: The index recovery for ' clientname ' failed.39078:nsrck: SYSTEM error: The operation completed successfully.

Run the following command:

nsrck -L2 <client>

Where:


b. Ignore file attribute messages such as the following, which will not impact the NMM recovery and can be safely ignored:

32222:uasm: Warning: Some file attributes were not recovered: C:\Program Files\EMC NetWorker\nsr\index\clientname\db6\tmprecov\C\Program Files\EMC NetWorker\nsr\index\clientname\db6\

c. If the nsrck command fails with the error “xxxxx”, the index backup might no longer be referenced in the media database. Use the following command to scan all ssids recorded for the cover, display, metadata and rollover save sets:

scanner -i -S <ssid> <device>


Recovery

Where:

<ssid> is the save set ID of the save set that will be restored.

<device> is the device containing the volume for the save set to be restored.

Ensure that the NMM software is closed on the NMM clients before running the scanner command. If the NMM software is open while the scanner is running, the scanner command may fail with “Index error, flush Failed'.

5. For each metadata and rollover save set, modify the browse times of the existing save sets, if browse and retention times set by scanner are not a long enough duration to complete recovery procedures:

nsrmm -s NetWorker_servername -w time2 -S ssid

Where:


<time2> is the new desired browse time.

<ssid> is the save set value recorded for each metadata or rollover save set in the Listing Required Save Sets section.

Ensure that the new browse dates for the save sets are far enough in the future to allow sufficient time for the recovery to complete.

Save set not in media database

This section discusses recovering a save set that is not in the media database.

Determining the clone save sets that do not exist in the media databaseIf the NMM original or clone save sets that are required for a recovery operation are no longer in the media database, you must scan the original or clone volumes to regenerate the media and index database for these save sets. You can use the scanner command to scan the volumes.

Identifying volumes required for scanningThe scanning procedure is used to identify the required volumes for the backup that is being restored, in the following scenarios:

◆ Restoring from a full backup. The volumes from the date of the backup is required.

◆ Restoring from an incremental backup. The volumes from the day of the incremental backup completed back to the most recent full backup are required.


Recovery

If other volumes are required to be scanned, review the following procedures to identify what save sets are missing, so that the additional volumes can be retrieved.

Disabling idle device timeoutTo prevent devices from being unloaded from the drives while the scanner is in use, you must temporarily disable the Idle Device Timeout attribute, if it was configured.

To temporarily disable the Idle Device Timeout attribute:

1. Connect to the NetWorker server through the NMC.

2. Click the Devices button.

3. Click View and then select Diagnostic mode.

4. Right-click the device that will be used to scan the required volume.

5. Select Properties to modify the properties of the device.

6. Select the Advanced tab.

7. Set the Idle Device Timeout value to 0.

8. Click OK.

Scanning the required volume1. Mount the volume containing the clone save sets into the drive.

2. If the volume itself is no longer in the NetWorker media database, choose the option Load without mount while loading the tape.

3. From a command prompt on the NetWorker server, obtain a list of the save sets on the clone volume to generate a report of the save sets on the volume. Use the following command:

scanner -v <device> 1>scanner_output.txt 2>&1

Where <device> is the name of the device containing the volume

For example:

scanner -v C:\device\clone 1>C:\output1\5\scanner_output.txt 2>&1

or

scanner -v \\.\Tape0 1>scanner_output.txt 2>&1

4. Open the scanner_output.txt file, which resides in the same directory the scanner command was executed from.

If the scanner_output.txt file only contains the message

scanner: SYSTEM error: Cannot start <device_name>: No such file or directory

Check the device name specified in the scanner command for errors and retry the scanner command with the correct device name.


Recovery

Notes about identifying required save setsWhen identifying required save sets, note the following:

◆ Application backups will have multiple rollover save sets with the same name.

◆ If the save set was an application save set of an individual application object, there will be one save set for each file system that contains application data. For example, an individual Exchange Server Storage Group or Hyper-V virtual machine may have multiple rollover save sets. T

◆ For an application writer-level save set, there will also be one rollover save set for each file system that contains application data.

◆ Anticipate a larger number of save sets if the application data involves more file systems.

◆ If a backup retry occurred in the backup window, there might be multiple occurrences of the following:

• VSS:/save set

• Metadata save set

• Rollover save set

Since you might not be able to determine afterwords what happened, include redundant save sets in the list to scan.

◆ All of the following save sets must be scanned even when restoring only an individual application object. This is because it is not possible to determine which rollover save sets are needed without scanning them in first. For example:

• VSS:/save set

• Metadata save set

• Rollover save set

◆ When using the scanner command, the cover save sets must be scanned in before the rollover save sets. This allows for any repair of the *coverid and the *connected save sets attributes if required. You can distinguish the rollover save sets from their covers by save set size:

• Cover save sets are approximately 1 MB or less.

• Rollover save sets are the size of the data backed up.

Determining ssid of the required save sets1. Inspect the scanner_output.txt file to determine the ssids of the required save

sets. The save sets can be identified by using the following attributes values for each save set in the output file:

• Client name

• Save time

• Level

• Save set name


Recovery

2. Determine the ssids and save time of all of the rollover and cover save sets required to perform the recovery, including all of the dependent full and incremental save sets. Rollover and cover save sets will have the same save set name.

The ssid values will be used later in the procedure to scan the save sets back into the media database. The save time values will be used to validate that the repopulation of the client file index was successful.

If the date of the point-in-time recovery was an incremental or differential backup level as denoted by the value in the level column, all save sets from the point-in-time recovery to the last full must be identified. In some cases, the associated full backup might be on a different volume.

3. Determine the ssid and the savetime for the VSS save set for the client.

4. Determine the ssid for the metadata save set for the client.

Scanning required save sets into media database and client file indexNote the following:

◆ The cover save sets must be scanned into the media database and client file indexes before the metadata and rollover save sets are scanned in.

◆ It is not possible to specify the scanning order when save sets are supplied through the -S parameter to the scanner.

◆ Save sets are scanned based on their order on the volume. As such, it may be necessary to scan the rollover save sets twice. The roll overs are initially identified from the scanner save set report by using the save set size.

◆ When scanning the metadata and rollover save sets the -y option is used to establish a new retention policy for the save set. Once these save sets have been scanned back into the media database, the browse time will be reset with the nsrmm command. The end-to-end process of recovering from scanned clones might take several days, so resetting the browse and retention times to a sufficient point-in-time in the future will help to ensure that the scanned save sets do not prematurely expire before you are finished restoring the data.

To scan the required save sets into the media database and the client file index:

1. Use the scanner command to scan cover save sets:

scanner -i -S <ssid> <device> 1>scanneri.txt 2>&1

where <ssid> is the ssid recorded for save set and <device> is the device with media containing the save set

Ensure that the NetWorker User software is closed on the NMM clients before running the scanner command. If the NMM software is open while the scanner is running, the scanner command may fail with “Index error, flush Failed”.

It is critical that the cover save sets be scanned in first.

2. Review the output of the scanneri.txt file for errors.


Recovery

If a cover set save set was not scanned in before the metadata or rollover save sets, the scanner output will report a message similar to the following:

scanner: Coverset xxxxxxxx not found in the Media DB, whichmust exist in order to make use of this save set (yyyyyyyy).Please be sure to scan in all volumes relevant to thisbackup.

If this message is encountered:

a. Use the scanner -i command to scan in the referenced cover save set.

b. Rescan the metadata or rollover save set.

Validating save sets in the client file indexFor each save set that was scanned in, you can use the nsrinfo command to validate that the data has been repopulated in the client file index.

To validate that the save sets are in the client file index:

1. During the inspection of the scanner output, review the savetime recorded for each of the following save sets:

• Cover

• Display

• Rollover

2. Run the nsrinfo command against each savetime to confirm that the client file index was populated with the necessary save set details:

nsrinfo -t <exact_savetime><client>

Where:

<exact_savetime> is the savetime recorded from the scanner output.


3. Repeat the nsrinfo command for all recorded savetimes.

Generating a media database listing of all of the save sets1. From a command line prompt on the NetWorker server run the mminfo command to

generate a list of NMM original or cloned save sets in the media database:

mminfo -S -s <NetWorker_server_name> -c <NMM_client_name> -q ”group= <group_name>, savetime>=<date1>, savetime<=<date2>” -ot 1>output.txt 2>&1

Where:

<NetWorker_server_name> is the name of the NetWorker server host.

<NMM_client_name> is the name of the NMM client host.

<group_name> is the name of the group which contained the NMM client when the backup occurred.


Recovery

<date1> is at least one day before the date range of the NMM original or clone to be restored.

<date2> is at least one day after the date range of the NMM original or clone to be restored.

2. Edit the output.txt file, which resides in the same directory the mminfo command was executed.

3. Make adjustments to the query options specified in the mminfo command, if the following message appears in the output file: contains the following message,

mminfo: no matches found for the query

This message means that the media database does not contain NMM save sets for the client or query options specified.

Validating that the metadata save sets are in the media databaseFor each metadata save set that was scanned in, inspect the output.txt file to ensure that the xml files are present.

Metadata save sets do not have index entries, so the ssflags value for the save set will is not browsable.

Exchange server notesRefer to the following notes when restoring from original or clone save sets.

Performing RDB recovery on a DAG member server

If an RDB item level recovery will be performed on a DAG member server, MAPI/CDO software should be installed on the DAG member server prior to attempting the recovery.

To download this software, search the Microsoft Download Center for “Microsoft Exchange Server MAPI Client and Collaboration Data Objects.”

Database and storage group save sets

If you schedule multiple Exchange server Storage Groups as individual save sets of a single NetWorker group, determine the save set of the Exchange Server 2007 Storage Group, Exchange Server 2010 Database, or Exchange Server 2013 Database that you are going to recover.

This will save time when identifying save sets regardless of whether you are repairing recycled media or scanning to regenerate save sets.

Log chain

If you are restoring to an incremental backup, recover the full set of backups from the time of the full backup to the time of the incremental backup.

Exchange server notes 61

Recovery

Backup group retry

If you retry NetWorker groups after backup failures, you will notice that multiple backups for the following have taken place within a 24 hour window:

◆ Individual Exchange 2007 Storage Groups

◆ Individual Exchange 2010 Databases


Depending on the cause of the original backup failure, when you are restoring there might be multiple valid backups for the following:

◆ Individual Exchange 2007 Storage Groups



If Exchange incremental backups were cloned, include the retry backups in the recovery process if they fall in the time range between the full backup and the required recovery time.

Recoverable save sets

This section discusses recovering a save set that is in a recoverable state.

Determine the rollover save set nameThe rollover save set is the backup save set that contains the backup of the NMM data.

There are two ways to inspect the media database and determine the name of the save sets:

◆ Use NMC to inspect the save set field for the NMM client configured on the NetWorker server.

◆ On the NMM client, run the nsrsnap_vss_save command:

◆ If the Exchange 2007 server is a stand-alone node or Local Continuous Replication (LCR) active node, type:

nsrsnap_vss_save -?

◆ If the Exchange 2007 server is on an Exchange 2007 Single Copy Cluster (SCC) node, type:

nsrsnap_vss_save -c virtual_server_name -?

If the application server is on a virtual host, run this command from the physical node that is currently hosting the application server.

◆ In an Exchange 2007 CCR environment, type the following on both the active and passive nodes as one line:

nsrsnap_vss_save -c <physical_server_name> -A NSR_VIRT_SERV=<virtual_server_name> -?


Recovery

Where <physical_server_name> and <virtual_server_name> are replaced with the appropriate server names for your environment.

◆ If the Exchange 2010 or 2013 server is a stand-alone node type:

nsrsnap_vss_save -?

◆ If the Exchange 2010 or 2013 server is a DAG type:

nsrsnap_vss_save -v -?

Hyper-V CSV notesRefer to the following notes when restoring Hyper-V CSV data from original or clone save sets.

Hyper-V virtual machine save sets

If you schedule multiple Hyper-V virtual machines as individual save sets of a single NetWorker group, determine the save set of the Hyper-V virtual machine that you are going to recover.


Writer save set

If you are using a writer-level save set, include all writer save sets for a single backup in the process of repairing recycled media or scanning.

C:\LG_PLACEHOLDER_XXXXXXXXXX save set

The following save set is only backed up with Hyper-V CSV and has a cover-ID that uses the following syntax:

C:\LG_PLACEHOLDER_XXXXXXXXXX

The C:\LG_PLACEHOLDER_XXXXXXXXXX save set is generated during the creation of top level backup indexes. When all nodes in the cluster are backed up successfully, the master node (the node on which the Hyper-V CSV backup is initiated) creates the final indexes. You can use these indexes to browse the Hyper-V CSV virtual machine in the NMM GUI.

Hyper-V notesRefer to the following notes when restoring Hyper-V data from original or clone save sets.

For Windows Server 2012 and Windows Server 2012 R2, replace all instances of Initial Store with Host Component.

Hyper-V CSV notes 63

Recovery

Hyper-V virtual machine save setsIf you schedule multiple Hyper-V virtual machines as individual save sets of a single NetWorker group, determine the save set of the Hyper-V virtual machine that you are going to recover.


Writer save setIf you are using a writer-level save set, include all writer save sets for a single backup in the process of repairing recycled media or scanning.

SharePoint notesRefer to the following notes when restoring SharePoint data from original or clone save sets.

SharePoint farm level recovery

If you are performing a SharePoint farm level recovery, you must include all farm clients that were backed up in the recovery procedures.

SharePoint content database level recovery

If you are performing a SharePoint content database level recovery, you must include the following:

◆ Farm clients that were backed up in the backup procedures

◆ The SharePoint Web Front End where the backups were taken

◆ The SQL Server host.

Writer save set

If you are using a writer-level save set, include all writer save sets for a single backup in the process of repairing recycled media or scanning.

Additional requirements

For the following SharePoint environments, backing up APPLICATIONS:\Microsoft Office SharePoint Services will back up the SharePoint Configuration Data:

◆ SharePoint 2007

◆ SharePoint 2010

◆ SharePoint 2013


Recovery

SQL notesRefer to the following notes when restoring SQL data from original or clone save sets.

SQL database save sets

If you schedule multiple SQL databases as individual save sets of a single NetWorker Group, determine the save set of the SQL database that you are going to recover.


SQL writer save set or SQL instance save set

When repairing media that has been marked recycled or when scanning volumes, always include all of the following save sets in the backup:

◆ All SQL writer-level save sets

◆ All SQL instance-level save sets

SQL notes 65

Troubleshooting

CHAPTER 4Troubleshooting

This chapter includes the following topics:

◆ Checking log files.................................................................................................... 67◆ NMM client issues................................................................................................... 67◆ Other troubleshooting resources ............................................................................. 70


Troubleshooting

Checking log filesNMM and its associated features generate many log files. These log files include errors that occur during the processes.

In addition, third-party providers generate their own logs in place of the Solutions Enabler log, hwprov.log. The third-party documentation provides more information.

NMM client issuesThis section discusses troubleshooting scenarios.

Backup versions are not displayed in the NetWorker User GUI

After the scanning is complete, you can display the backup in the NetWorker User software.

If the application object is present in the most recent backup, you can view versions for that application object. The versions are not cached, so a newly scanned version should be detected if present.

1. From View Versions, look for the savetime scanned.

2. If found, choose this as the new browse time to proceed.

3. Use Change browse time to set the time slightly ahead of the most recent save set that is to be restored.

If you are restoring from an incremental backup, verify that the prior full and all incremental backups are also visible as backup versions by running View versions for the application object.

This does not apply to the following applications:

• Hyper-V restore

• SharePoint 2007, SharePoint 2010, and SharePoint 2013

If the scanned backup version does not appear in the NetWorker User software, validate the rollover save set.

Data recovery process fails when rollover save sets are not browsable

If the rollover save sets are not browsable, the data recovery process fails with errors similar to the following:

◆ NMM Hyper-V: Operation unit failed with error 'G:\SC2ATARIDES\SCVAtariDes.vhd not in index

If this occurs, validate that the rollover save sets are browsable. Run mminfo against the ssids noted during the recovery procedures for the Rollover save sets.

◆ nsrsnap_vss_recover:NMM.. Index retrieve of metadata key failed for index path <save set name> with savetime <savetime>

Checking log files 67

Troubleshooting

...

Recover completion status

Recover process has failed to locate correct logical savetime for requested selections -- error 4312..

With either of these sets of error messages, follow the steps in “Ensuring save sets are browsable” on page 68.

Ensuring save sets are browsable

Restore can fail before it even starts, if you cannot locate the backups you want to restore from. The NMM software includes logic to validate that a rollover or snapshot exists for an item and is browsable before it can be displayed. The *snap_sessionid attribute is used to perform this validation.

◆ If a rollover save set is not found with the same *snap_sessionid as the cover save set, the NMM software will not display the backup version.

◆ If the backup version does not display in the GUI, validate that the rollover save set and the cover save sets are in the media database and browsable for the save times.

The following topics describe how to validate that the save sets are browsable.

Validating that the rollover save set is browsableYou can use the contents of the output.txt file to validate that the rollover save set is browsable, and to find information that can be used in validating that the cover set is browsable.

1. Follow the steps in “Generating the media database list of the save sets” on page 49 to generate the output.txt file.

2. Open the output.txt file.

3. Identify the most recent full backup for the file system or application save set from the rollover save set name.

4. Check that the sflags attribute does not have a K value.

5. Check that the level attribute lists full.

6. Check the value in the sflags field, if it contains an E or r, the save set is not browsable.

7. Record the following to aid in validating the cover set:

• ssid

• coverid

• *snap_sessionid

Validating that the cover save set is browsableYou can use the information obtained from the output.txt file in “Validating that the rollover save set is browsable” on page 68 to validate that the cover set is browsable.

1. Using the *coverid from the output.txt file, search the mminfo output for the cover save set associated with the full backup.


Troubleshooting

2. Check the value in the sflags field. If the value contains an E or r, the save set is not browsable.

3. Record the ssid value.

4. Use the *snap_sessionid recorded for the full backup to search for other rollover and cover save sets with a *snap_sessionid that matches the name of the save set being restored.

5. Record the ssid values for each of these additional cover and rollover savesets.

Validating the VSS save setYou can use the information obtained from the output.txt file in “Validating that the rollover save set is browsable” on page 68 to validate that the VSS: set is browsable.

1. Search the output.txt file for the save set VSS: that has the same *snap_sessionid as the rollover save set.

2. Make note of the value in the sflags field. If the value contains an E or r, the save set is not browsable.

3. Make note of the ssid and all cloneid values for the VSS: save set.

If the save sets are not in the media database, you must identify what additional clone volumes are required and repeat the process.

If the save sets are recyclable, follow the steps in “Recovering recyclable save sets to the client file index” on page 54.

If the save sets are recoverable, follow the steps in “Recovering recoverable save sets to the client file index” on page 51.

Unable to read metadata save set

One of the first save sets that will be read during the recovery is the metadata save set. The metadata save set is identified by the data in the index, and its ssid is used during the recovery. If the metadata save set is not in the media database, the recovery operation will fail.

With the NMM software, failure to recover the metadata save set is indicated in the last line of the nsr\applogs\nmm.raw. log file:

NMM start recovery of metadata key for savetime xxxxx

The metadata save set contains a single XML document. This XML document is a file mapping section and consists of information regarding the files to recover and their corresponding cover save set times.

If a failure occurs:

1. Review the output.txt file. The file resides in the same directory where the mminfo command was run.

2. The metadata save set can be recognized as a file name of the form:

LG_VSS_CLIENTxxxxxxxxxx.xml

NMM client issues 69

Troubleshooting

3. Confirm that the value in the savetime column matches the savetime reported in the nmm.raw file.

Metadata save sets do not have client file index entries so it is not necessary to make these save sets browsable.

4. If the metadata save set with the savetime reported in the nmm.raw file is not found in the mminfo output, refer to the procedures in “Save set not in media database” on page 56.

Cover save set recovery fails

Once the metadata is read, the NMM software starts the recovery process. During recovery the cover save set and the rollover save sets are used by the NMM recover logic. The metadata save set contains a single XML document. This XML document contains information on the files to recover and their cover save set times, in the named file mapping section. The recovery request consists of the files that are required to be restored and their cover savetimes. If the cover save sets do not exist, the recovery fails.

If the recovery fails:

1. Inspect the logs under nsr\logs.

2. Locate the clone tape that contains the save set.

3. Generate a scanner report for the clone volume to find the matching save set and the savetime.

4. Scan in the cover save set and its rollover save set.

5. For additional help, refer to the procedures in “Save set not in media database” on page 56.

Other troubleshooting resourcesIf the problem appears to be related to the NetWorker server, check that the NetWorker server is installed and configured correctly. Also, check the log files and error message documentation for the NetWorker server. The following guides provide additional troubleshooting information:

◆ EMC NetWorker Installation Guide ◆ EMC NetWorker Administration Guide◆ EMC NetWorker Error Message Guide

The following resources provide additional troubleshooting information:

◆ http://support.microsoft.com◆ http://social.technet.microsoft.com/search/en-US



http://support.microsoft.com

http://social.technet.microsoft.com/search/en-US

Troubleshooting

Other troubleshooting resources 71

emc networker module for microsoft networker® module for microsoft release 8.2 service pack 1...

Documents