Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Administration Guide
P/N 300-012-874
REV 03
Copyright 2007 - 2012 EMC Corporation. All rights reserved. Published in the USA.
Published September 28, 2012
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 (http://support.emc.com).
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
CONTENTS
Preface
Revision History
Chapter 1
Overview
About the NetWorker Module for Microsoft Applications software................
Support provided by NMM 2.4 ....................................................................
Supported NetWorker features ..............................................................
Supported Windows versions and related features................................
Support for IPv4 and IPv6 ......................................................................
Support for data deduplication .............................................................
Support for VSS backup and recovery....................................................
Support for dynamic volumes that use the Microsoft Software
Shadow Copy provider ..........................................................................
Support for SQL VDI Servers recovery models ........................................
Full backup and recovery.............................................................................
Granular-level recovery for Exchange, Hyper-V and SharePoint
applications.................................................................................................
GLR Process Overview ...........................................................................
GLR-compatible backup availability ......................................................
NWFS Logs and Attributes .....................................................................
Normal and directed recovery......................................................................
The VSS snapshot creation process .............................................................
Components in the VSS snapshot creation process ...............................
The VSS backup process .......................................................................
About snapshots and types of snapshot backups........................................
Copy-on-write snapshot versus split-mirror snapshot
technology ............................................................................................
Roll over a snapshot..............................................................................
Types of NMM client snapshot backups ................................................
Types of NMM client recoveries .............................................................
The NMM client graphical user interface......................................................
NetWorker User for NMM program overview...........................................
NetWorker User for SQL Server program overview ..................................
Basic tasks in NetWorker User for NMM client user interface........................
Opening the software and connecting to a NetWorker server .................
Selecting an item for recovery ...............................................................
Searching for an item ............................................................................
Specifying a recovery browse time.........................................................
Marking items .......................................................................................
Selecting a backup version for recovery.................................................
Viewing the volumes required for a recovery..........................................
Performing a snapshot rollover..............................................................
Deleting a snapshot ..............................................................................
Access privileges for backup and recovery...................................................
Microsoft Windows groups and NetWorker administrative privileges............
Name resolution to identify and back-translate computer names.................
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
18
18
19
19
20
20
20
22
22
23
24
24
25
25
25
27
27
29
30
30
31
31
33
34
34
37
40
41
41
42
43
43
43
44
44
45
46
47
48
Contents
Chapter 2
Chapter 3
Chapter 4
61
61
61
62
62
64
65
79
79
80
82
84
57
57
59
59
Scheduled Backup
Backup configuration roadmap ...................................................................
Configuration tasks .....................................................................................
Backing up a clustered NMM client .............................................................
Moving a NMM client to another NetWorker server ......................................
Performing a directed recovery with NMM....................................................
Setting AES data encryption ........................................................................
Best practices and recommendations for backing up application
data.............................................................................................................
Chapter 5
52
52
52
52
53
54
54
54
55
55
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
86
86
86
87
87
88
88
89
89
90
91
Contents
Chapter 6
92
92
93
93
94
94
94
95
98
98
99
Chapter 7
91
91
102
102
102
104
104
104
105
106
106
109
109
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
112
112
115
115
116
117
118
118
119
120
123
124
126
128
129
130
131
132
134
135
135
135
Contents
Chapter 8
138
Glossary
Index
135
136
136
136
137
137
137
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
140
140
140
141
142
143
143
144
FIGURES
Title
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Page
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Figures
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
TABLES
Title
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
Page
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Tableses
10
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
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.
Note: This document was accurate at publication time. Go to EMC Online Support
(http://support.emc.com) to ensure that you are using the latest version of this document.
Purpose
This guide contains information common to all the Microsoft applications that can be
backed up and recovered by using EMC NetWorker Module for Microsoft Applications.
Ensure to download a copy of the NetWorker Module for Microsoft Applications Release
2.4 Application Guide from the EMC Online Support to use along with this guide. The
NetWorker Module for Microsoft Applications Release 2.4 Application Guide contains
information specific to an application, and must be referred to when backing up and
recovering an application.
Audience
This guide is part of the EMC NetWorker Module for Microsoft Applications documentation
set, and is intended for use by system administrators during the setup and maintenance
of the product.
Readers should be familiar with the following technologies used in backup and recovery:
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
11
Preface
Related documentation
Table 1 on page 12 lists the EMC publications that provide additional information.
Table 1 EMC publications for additional information
Guide names
Description
12
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Preface
An important notice contains information essential to software or hardware operation.
Typographical conventions
EMC uses the following type style conventions in this document:
Normal
Bold
Italic
Courier
Used for:
System output, such as an error message or script
URLs, complete paths, filenames, prompts, and syntax when shown
outside of running text
Courier bold
Courier italic
<>
[]
{}
...
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
13
Preface
Technical support Go to EMC Online Support and click Service Center. You will see
several options for contacting EMC Technical Support. Note that to open a service request,
you must have a valid support agreement. Contact your EMC sales representative for
details about obtaining a valid support agreement or with questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall
quality of the user publications. Send your opinions of this document to:
BSGdocumentation@emc.com
14
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
REVISION HISTORY
Date
03
Third release of this document for General Availability (GA) release of the EMC
NetWorker Module for Microsoft Applications Release 2.4. Updated to include
Exchange in list of supported applications for granular level recovery.
02
Second release of this document for General Availability (GA) release of the EMC
NetWorker Module for Microsoft Applications Release 2.4. The updates made in this
release are:
Updated Granular-level recovery for Exchange, Hyper-V and SharePoint
applications on page 24.
Incorporated technical feedback received from the EMC Support team.
Updated the new website location for documentation and software downloads
(http://support.emc.com).
A01
First release of this document for Restricted Availability (RA) release of EMC NetWorker
Module for Microsoft Applications Release 2.4.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
15
Revision History
16
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
CHAPTER 1
Overview
This chapter includes the following topics:
Overview
18
18
23
24
25
27
30
34
40
46
47
48
49
17
Overview
Microsoft Volume Shadow Copy Service (VSS) technologyWhere NMM works with
Microsoft Volume Shadow Copy Service (VSS) technology to provide snapshot backup
and recovery services for file systems, Microsoft applications, and Windows system
data. The NMM client allows the creation of point-in-time snapshot data. A snapshot
can be retained on storage volumes for quick access.
You can also perform a rollover of a snapshot to a traditional backup medium, such as
tape, file type device, advanced file type device, EMC Avamar device, and EMC Data
Domain device.
Data can be recovered from either of the following: snapshot or backup media.
Microsoft applications and Windows components on page 21 provides the list of
Microsoft applications and Windows components for which backup and recovery of
data by using the VSS technology is available.
Microsoft Virtual Device Interface (VDI) technologyWhere NMM uses the Virtual
Device Interface (VDI) technology to communicate with the SQL Server.
In NMM, backup and recovery of data by using the VDI technology is available for SQL
Server.
Note: The NMM client clock must be kept in sync with that of the NetWorker server. If the
clock times are not in sync and differ more than five minutes, problems occur when
recovering full and incremental backups. The clock times for the client, server, and data
mover must match for backups to work without any issues.
18
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Support for dynamic volumes that use the Microsoft Software Shadow Copy provider
on page 22
Internationalization (I18N)
NetWorker cloning and staging to create and manage additional copies of save sets.
This NMM support requires NetWorker 7.6 SP2 or later.
Offline disaster recovery, which means that the Windows operating system is not
active
Localization (L10N) is not supported in NMM 2.4.
System state recovery, file servers, and operating system roles including the following:
Active Directory
DHCP
Terminal Services
19
Overview
NMM does not support the following operating system and features:
Windows IA64 editions
BitLocker encryption
VSS Hardware Provider based proxy backup of Windows dynamic disks
Single Instance Storage (SIS)
Details
20
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Details
Note: Application support often requires a minimum specific service-pack level. The
service-pack levels frequently change. The NetWorker Software Compatibility Guide
provides the most up-to-date information about service packs that are required for each
application.
System providers
Microsoft System Provider are available for use with disks that are directly attached to the
host or are part of a hardware array:
This includes directly connected disks such as SATA or SCSI and storage arrays. For
example, where a hardware provider does not exist or has not been installed.
The Microsoft System Provider will not take advantage of any features that a storage
array can provide including any built-in snapshot capabilities.
The Microsoft System Provider is part of the operating system. The sizes and locations are
managed in the Disk Management applet.
The EMC VSS providers available are:
When EMC VSS hardware providers are used with VMware ESX 3.5 or ESX 4.0 and
Windows guest operating system in NMM clients, set the environment variable
VICLIENT_DISABLE_CACHE=1 to disable Virtual Infrastructure Client (VI Client) cache in the
NMM clients.
21
Overview
Support for dynamic volumes that use the Microsoft Software Shadow Copy provider
In Windows Server 2008 R2, Windows Server 2008 R2 SP1, and Windows Server 2008 SP2:
NMM supports snapshots of dynamic volumes that use the Microsoft Software
Shadow Copy provider.
Any attempt to take a hardware-based replica of a dynamic volume fails, and causes
instability in the system.
Although Windows Server 2008 introduces support for local, hardware-based snapshots
of dynamic volumes, NMM does not support the following snapshots of dynamic volumes
on Windows Server 2008:
Local
Non-transportable
Hardware-based
For environments where dynamic volumes are provisioned by using a storage array, do not
install the storage array vendors VSS provider on the production host. For example, if a
dynamic volume was created on a CLARiiON LUN, do not install the EMC VSS Hardware
Provider on the production host.
22
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
A point-in-time restore is not supported for SQL Servers if the following conditions
apply:
If a bulk log change has occurred for the transaction log backup that corresponds
to the current browse time.
If bulk changes in the transaction log that contains the time or day marker.
The NetWorker Module rolls forward all transactions to the end of the transaction log
and leaves the database in an operational state.
Only level full and differential database backup types are supported.
Backup data is restorable up to the last level full or differential database backup.
VSS based backups for Microsoft applications are always full.
23
Overview
SQL
Server Exchange
*
2007
ShareExchange Point
Server
Server
2010
2007
SharePoint
Server
2010
DPM
*
Hyper- File
V*
system
*
SQL Server*
Full
backup
Full
recovery
For disaster recovery, only full backup and recovery are used.
24
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Once a GLR session is complete, the plug-in shuts down the NWFS virtual file system. The
client closes NWFS, removes the virtual file system from the system, and deletes the
temporary locally stored data.
Type
GLR_OFFSET_MAP Boolean
GLR_Hint
Value
Yes
25
Overview
The control client is the computer running the NMM UI to initiate the recover
process.
The destination client is the computer that the data is restored to.
Directed recoveryThe source, control, and destination roles are not all on the same
computer.
There are two types of directed recovery:
In pull directed recovery, the control role and destination role are performed on the
same computer. The control role running on the destination computer pulls the
recovery data to itself. Backup data from the source client is restored to the
destination client.
In push directed recovery, the control role can be run on the source client or a
different client. Backup data from the source client is restored to the destination
client. The control client computer pushes it out to another computer, the
destination client. The destination client is not the same computer as the source
client or control client.
Table 6 on page 26 lists the pull and push directed recovery support provided by NMM.
Table 6 Pull and push support
Application
DPM
Hyper-V
Filesystem
For pull directed recovery for the supported applications listed in Table 6 on page 26, you
can:
Run the NMM software recovery (the control role) on the same computer that the data
is being restored to (the destination client).
Note: Additional or different steps may be required. The NetWorker Module for
Microsoft Applications Release 2.4 Application Guide provides details for each
application.
26
Specify the alternate server to recover to in the normal recovery steps for the
application. Recovering the Windows system configuration to an earlier state on
page 134 provides more information.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Note: The NMM software does not support directed recovery of SYSTEM COMPONENTS.
Rollback recovery is not supported in NMM.
EMC Celerra VSS Hardware ProviderThe EMC Celerra VSS Hardware Provider
supports Celerra arrays.
More information about using NMM with an EMC VSS Hardware Provider, including
hardware array installation and configuration is provided in:
The NetWorker Module for Microsoft Applications and EMC CLARiiON:
Conventional restore and snapshot restore are supported for backups performed
by Dell EqualLogic or Celerra hardware.
WritersWriters provide information about what data to back up, and specific
methods for handling components and applications during backup and recovery.
They also identify the type of application or service that is being backed up. If a
27
Overview
service or application is present on a system but is not active, information from its
writer will not be available. Consequently, a writer can appear or disappear from
backup to backup.
Table 7 on page 28 lists the writers that are supported for the NMM client.
Table 7 Currently supported writers
Writer type
Volumes
Microsoft applications
Windows versions
Windows SYSTEM
COMPONENTS
28
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Some of the VSS writers appear under Bootable System State in SYSTEM COMPONENTS:\
save set. These writers are listed when the vssadmin list writers command is used at the
command prompt.
Files located in an FTP directory are not included in a SYSTEM COMPONENTS snapshot.
Typically, FTP files are stored by Internet Information Services (IIS) in C:\inetpub. IIS
metabase files are configuration files, which are backed up as part of SYSTEM
COMPONENTS. The FTP files are content files, and must be backed up separately.
29
Overview
Requestor
4. Requestor
asks VSS
to create
snapshot.
Writer
Writer
Writer
Writer
Disk 1
Disk 2
Disk 3
Disk 3
GEN-000188
30
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Roll over the snapshot to tape to protect the data if the snapshot becomes corrupted
during the recovery process.
Create a convention backup copy of the snapshot data. This conventional copy will
reside on the device even if the retention deletes the snapshot.
Conventional backup
Conventional backup includes snapshot rollover backup to tape, file type, or advanced file
type devices.
Serverless backup
Serverless backup is a method of offloading backup procedures from an application
server so that the time ordinarily devoted to backup functions can be used to carry out
other server tasks. Serverless backup uses an NMM proxy client to move the data from the
proxy client to the backup media for a snapshot created on application server host.
Serverless backup is available only with EMC VSS Hardware Providers. The EMC VSS
Provider for CLARiiON and Symmetrix provides the capability to perform serverless backup
operations for these storage platforms.
In this kind of backup:
1. The snapshot is created on the application server and immediately mounted to the
proxy client.
2. After the snapshot is created, the application server is not involved in the backup
operation.
3. During the rollover, that is backup of the snapshot, the application server is free and
all of its resources are available for use.
31
Overview
When Exchange Server is backed up by using serverless backup, Outlook users can
continue to use the application server.
Performing serverless backups are also useful when there is additional processing
involved in a snapshot backup and is CPU intensive.
For example, to help determine whether a snapshot of a Exchange database is
consistent, the Exchange utility eseutil is run against the snapshot.
Running eseutil can be disk and processor intensive.
Using serverless backup helps free resources on the Exchange Server because the
backup operation workload from the Exchange Server is offloaded to a proxy client.
Ensure that the following is the same on both the application server host and the
proxy host:
Operating system version
Service pack
Update level
For example, do not use a Windows Server 2008 R2 system as the proxy mount host
for Windows Server 2008 SP2 production host, otherwise backup fails.
If a production server is a virtual machine, then the proxy host should be a physical
machine.
Specify the following in the Application Information field of the client resource:
NSR_DATA_MOVER=<Proxy host>
32
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
For persistent backup with or without rollover, the Retain Snapshots is set to any non-zero
value in the Snapshot Policy during the client resource configuration process.
Conventional recovery
A conventional recovery consists of recovering data that has already been rolled over to a
backup media. Conventional recoveries support the same level of item selection as
instant recoveries.
Instant recovery
Instant recoveries are performed with persistent snapshots. An instant recovery can take
less time to complete than a conventional recovery because the snapshot is available on a
mounted disk storage volume rather than on a conventional backup medium.
Instant recoveries support the selection of individual files in a file system snapshot.
Additionally, instant recoveries support the selection of individual components at
whatever level of granularity is supported by the application writer.
If the persistent snapshot is created by using a proxy client, the snapshot file system on
the proxy client is read to restore the files. In this way, performance is improved even
further because the job of processing the snapshot for recovery is off-loaded from the
NMM client production host to the proxy client.
The procedure to perform an instant recovery of file system data differs if only a persistent
snapshot is available. provides more information about performing recoveries.
Note: When performing an instant recovery, the snapshot may become invalidated. This
can occur if the snapshot is based on copy-on-write technology. If a large amount of data
is recovered to the original volume, the cache may overflow. This is true for the Microsoft
Software Shadow Copy provider and for hardware providers that use copy-on-write
technology, such as CLARiiON snapview snapshot and Symmetrix virtual devices.
33
Overview
NetWorker User for NMM program overview on page 34 This GUI can be used to
recover the following Microsoft applications (all supported versions) by using the VSS
technology:
SQL Server
Data Protection Manager Server
Exchange Server
Hyper-V Server
SharePoint Server
Active Directory
Go to Start > Program > NetWorker Modules > NetWorker User for NMM on the host
where the NMM 2.4 software is installed to start this GUI.
NetWorker User for SQL Server program overview on page 37This GUI can be used
to back up and recover the supported versions of SQL Server by using the VDI
technology.
Go to Start > Program > NetWorker Modules > NetWorker User for SQL on the host where
the NMM 2.4 software is installed to start this GUI.
34
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Recover view
All recoveries are performed from the Recover view by selecting the Recover icon
the left.
on
client selection
(clustered client only)
Main toolbar
Available views
Summary of selected
items
The summary of selected items can also display exclusions, which shows only those items
that are not selected for recovery. This view can be helpful when many items are selected
for recovery.
Delete snapshot
Mount a snapshot
Rollover snapshot
35
Overview
Monitor view
Recovery and snapshot management operations can be monitored in the Monitor view by
selecting the Monitor icon
on the left, shown in Figure 3 on page 36.
Most messages displayed in the Monitor view are also written to log files.
Display conventions
The NetWorker User for NMM Server program uses specific icons to identify various tasks
and operations. Table 9 on page 39 outlines the main conventions used in the NMM GUI.
Table 8 Main conventions used in the NMM GUI
36
Data item
Description
Pane
NetWorker server
Top
Recover
Left
Left
Exchange Recover
Session
Left
Monitor
Log files
Right
Database
Right
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Icon
Overview
Backup view All backups are performed from the Backup window. Select the
icon to view the Backup window.
Figure 4 on page 37 shows the Backup view.
Select the database that needs to be backed up, and either right-click or select
Options > Backup Options to view the Backup Options dialog box.
37
Overview
Restore Operation view Normal, Copy, or Piecemeal restores are performed from the
Restore Operation view. Select the
icon to view the Restore Operation window as
shown in Figure 5 on page 38.
Fake objects
The NMM software enables the browsing of filegroups and files contained in a database.
However, the software can display data items that are not available for backup or restore
operations. These are referred to as fake objects.
38
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
When a file or filegroup exists in the SQL Server storage hierarchy, but cannot be backed
up because of SQL Server settings on the database, the item is displayed in the Backup
window by using the fake filegroup or fake file convention. In addition, if you try to mark a
fake object, an error dialog box is displayed as in Figure 8 on page 39
The NetWorker Module for Microsoft Applications Release 2.4 Application Guide provides
more information about the constraints SQL Servers enforce that determine whether an
item is available for backup or restore.
Description
Pane
SQL Server
Left only
Database
Descendant of root
Signifies a database
May contain filegroups
Filegroup
Descendant of a database
Signifies a database filegroup or filestream
data
May contain files
Left or right
Icon
39
Overview
Description
Pane
Fake filegroup
Left or right
File
Descendant of a filegroup
Signifies a database file
Right only
Fake file
Right only
Icon
Mark an item when any of that items surrounding items are already marked.
Mark or unmark all SQL Server data by right-clicking the root item and selecting Mark
All Databases or Unmark All Databases from the shortcut menu.
The NetWorker User for SQL Server program imposes the following restrictions:
You cannot mark an item if any of the predecessors of descendants are already
marked except in the SQL Server root.
When a database is marked, all of the items descendants are not automatically
marked.
When a filegroup is marked, all of the files are not automatically marked.
40
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
41
Overview
Figure 9 on page 42 depicts one selected item and several partially selected nodes in the
navigation tree.
Selecting an item
for recovery
xyzABCde.
Name starts with (case-insensitive)Type abc% to return abcd or ABCde but not
xyzABCde.
Name ends with (case-insensitive)Type %abc to return xyzAbc but not ABCde.
Single-character match search by using the ? wildcard:
Type ? to return single character entries and drive volumes, such as C or D.
Type WMI?Writer to return WMI Writer.
Multiple-character match search by using the * wildcard:
Type *.txt to return all entries with a .txt extension.
Type * to return all items within the selected container.
Type *writer* to return all writers.
Search by using both the * and ? wildcardType *???*writer* to return WMI Writer.
4. Click Search. The Details pane displays the results of the search.
42
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Marking items
The NMM software provides marking indicators that help determine the state of each item
in the browse tree:
UnmarkedAn unmarked item is one that is not selected for backup or restore. An
empty checkbox appears to the left of each unselected item to indicate it is unmarked.
MarkedA marked item is one that is selected for backup or restore. A checkmark
appears in the checkbox to the left of each marked item.
Partially markedA partially marked item is one that has marked descendants, but
the item itself is not explicitly marked. A partially marked item is not backed up or
restored. A checkmark appears in a gray checkbox to the left of each partially marked
item.
5. Click OK. The recover items displayed in the navigation tree are from the selected
browse time.
43
Overview
Limit the number of snapshots for a volume with the EMC VSS Provider
You can create a maximum of eight shadow copies for a single LUN on an EMC CLARiiON or
EMC Symmetrix machine.
The VSS framework also limits the number of shadow copies per volume, for example 64.
This limit also applies to all VSS providers, including the VSS software provider.
44
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Figure 10 on page 45 displays the snapshots and snapshot save sets available for
rollover.
Note: When performing a rollover of a snapshot of a drive that contains the NMM binaries,
at least one drive letter must be available for use as the temporary location for the
mounted snapshot.
Deleting a snapshot
Snapshot deletion policies are typically controlled automatically through snapshot policy
settings on the NetWorker server. However, you can delete a snapshot manually. For
instance, if space must be made available immediately on the storage system, you can
manually rollover and then delete snapshots.
Note: To prevent the loss of data from a snapshot that is to be deleted, perform a rollover
of the snapshot before the deletion operation. Roll over a snapshot on page 31 provides
more information about rolling over a snapshot.
If a snapshot is deleted without the use of the NMM client user interface, the snapshot
may still appear to be recoverable in the NMM client user interface.
If such a snapshot is selected for recovery, the recover operation will fail. A snapshot could
also be deleted by VSS or the storage subsystem if resources are exhausted due to high
input/output rates on the volumes.
45
Overview
To delete a snapshot:
1. Open the NMM client GUI.
2. Select the NetWorker server on which the NetWorker client was configured for backup.
Opening the software and connecting to a NetWorker server on page 41 provides
more information about opening NMM and connecting to a NetWorker server.
3. In the left pane, select Snapshot Management.
4. In the navigation tree, select the snapshot to be deleted.
5. Right-click the selected snapshot.
6. Select Delete Snapshot.
In the left pane, select Monitor to view the progress of the delete operation.
Required privileges
NetWorker server
NetWorker Administrator
or
NetWorker Backup Operator
Windows Administrator
or
Windows Backup Operator
Windows Administrator
46
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
Required privileges
Network domain
Windows Administrator
Exchange Server
Administrators group
If you are logged into a domain, only the global group is recognized. You can find out the
name of your group by running the Windows utility findgrp.exe, which is available with the
Windows Resource Kit.
If you are logged into an individual Windows computer, only the local group is recognized,
because there is no global group.
In cases where a user belongs to a domain that cannot be contacted by the server and
therefore the username cannot be verified, you can use a more specific user description to
guarantee that the appropriate user will have administrative rights to the server. The
syntax for this user description is as follows:
47
Overview
Single user:
user=user_name, domain=domain_name
For example:
user=joe,domain=NT-ENG
Group:
group=group_name, domainsid=domain_id
For example:
group=Administrators,domainsid=S-1-5-32-323121-123
name-to-IP address
or
IP address-to-name
Also, the NMM client uses the host machine NETBIOS or short name when connecting to
the NetWorker server to browse backups. If the NETBIOS name is not found, NMM will not
be able to display backups.
To ensure clear communication of computer names:
1. Add the NetWorker server name to either of the following:
The local hosts file, which is located in the following location:
%SystemRoot%\system32\drivers\etc
The Domain Name System that contains the names of all servers on your network.
2. When configuring a client resource for solutions like Exchange, SharePoint, and so on,
specify the NETBIOS name for the client in the Aliases attribute.
48
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Overview
The Cloning and Recovery of Expired Save Sets for NetWorker Module for Microsoft
Applications Technical Note provides additional details on the cloning and recovery
procedures.
Cloning and recovering from original or cloned NMM backups that are no longer browsable or present in the media database
49
Overview
50
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
CHAPTER 2
NetWorker Client Management
This chapter includes the following topics:
52
53
54
54
55
51
Requirements
To recover a remote client requires the following:
The NetWorker server must have at least two NMM clients configured.
A volume backup created on the remote client. The backup must be a conventional
backup, not a snapshot.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
You can also connect to a NetWorker server by clicking the NetWorker Server icon on
the Application toolbar.
53
Configuring TCP Networks and Network Firewalls for EMC NetWorker Technical Note
available on EMC Online Support provides more information on how to identify and
configure the required ports for NetWorker hosts that need to communicate across a
packet filtering or stateful inspection firewall.
54
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Specifying a password
The password is used to protect items that will be backed up with either PW1
password-protection, or PW2 encryption and password-protection. PW1 and PW2
protection is enabled on the NetWorker server with a local or global directive.
The NetWorker Administration Guide provides more information about PW1 and PW2
protection.
Changing the password does not change the password for files that have already been
backed up.
To recover PW1 or PW2 password-protected files, you must provide the password that was
in effect at the time of the backup.
Specifying a password
55
56
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
CHAPTER 3
Multihomed setup for backup and recovery
This chapter includes the following topics:
Overview.................................................................................................................
Basic requirements for setting up a multihomed environment .................................
Requirements for multihomed NMM client's network configuration .........................
Requirements for multihomed NetWorker server's network configuration ................
Requirements for network configuration on NetWorker storage node .......................
Configuring NMM client resources in a multihomed environment.............................
57
57
59
61
61
61
Overview
In a multihomed environment, NetWorker Module for Microsoft Applications (NMM) backs
up data by using Microsoft VSS technology and writes to a backup device like Avamar or
Data Domain by using a dedicated backup LAN instead of using a production LAN. Backing
up NMM production data in a multihomed environment helps avoid contention between
the data application traffic and data backup traffic.
Note: For cluster virtual clients, the connection from NetWorker server is initiated on the
backup media production network. But the backup payload flows through the backup
network.
In a multihomed environment, NMM 2.4 supports backup and recovery for the following
Microsoft applications:
DPM Server
Exchange Server
Hyper-V Server
SharePoint Server
SQL Server
The IP belonging to any specific NIC resides in a separate subnet or VLAN (The IP
subnet or VLAN through which the backup traffic is meant to pass is called the backup
subnet. )
57
All the hosts, such as the following that are participating in the backup must have at
least one NIC (called the backup NIC) configured with an IP address (called backup IP)
on the backup subnet:
NetWorker server
NetWorker storage node
NetWorker client
The backup IP on any host must always resolve to its FQDN on a backup LAN. This IP
address to hostname mapping can be implemented in various ways:
By creating an entry for the backup IP on a backup domain. The backup domain is a
domain that offers a mechanism to identify backup IPs by names.
Examples of where and how to configure a backup domain are as follows:
Backup domain can be a separate domain hosted on an exclusive DNS server
on the backup subnet.
A zone configured on existing DNS server accessible from NMM client.
This might require customized configurations in the DNS server depending on the
status of the DNS server, if the DNS server is separate or if the preexisting DNS
server being used for multi-NIC configuration.
By updating etc\hosts file with the IP to FQDN mapping.
58
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Storage Node
Backup Lan
NetWorker Server
Production
Management Lan
NetWorker Client
GEN-001729
59
Do not use the Append these DNS suffixes (in order) attribute.
60
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
The minimum requirement is that the NetWorker server must have a backup IP, which
is essentially an IP address for a NIC on backup subnet. This backup IP should also
resolve to a unique FQDN on backup domain.
The backup NIC configuration on NetWorker server should follow the guidelines in
Requirements for multihomed NMM client's network configuration on page 59.
61
4. Create an NMM client for the cluster virtual server with either of the following:
NetBIOS name
or
Production domain FQDN
5. If you are using the NetBIOS name, ensure that the following attribute is enabled for
the production NIC on the NetWorker server:
NetBIOS over TCP/IP
6. Ensure that all clients have the following attribute set to backup domain FQDN of the
storage nodes in the Globals (2 of 2) tab:
Storage nodes
62
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
CHAPTER 4
Scheduled Backup
This chapter includes the following topics:
Scheduled Backup
64
65
79
79
80
82
84
63
Scheduled Backup
Required action
Windows volumes:
Volume data such as a drive letter, for example: D:\
A file system path, for example D:\data
64
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
Configuration tasks
Table 12 on page 65 lists the tasks that you must follow when configuring backups for the
Microsoft application that you are using. The respective chapter for each application in the
NetWorker Microsoft Module for Microsoft Applications Release 2.4 Application Guide
provides the list of tasks that are required for a particular application.
Table 12 List of tasks required for VSS based and VDI based backups
VSS based backup
Tasks
All the procedures described in this section must be performed on a NetWorker server.
Use the NetWorker Management Console program (NMC) to access the NetWorker
Administration page to perform all the procedures. Click the question mark icon
at the
bottom left of each page of the NMC for details about each field in the page. Review the
NetWorker Administration Guide for details about the NetWorker Management Console
program.
Configuration tasks
65
Scheduled Backup
Description
Configuring a device
Note: You can use the New Device Wizard in the NetWorker Management Console to
configure a device.
To configure a device:
1. In the NetWorker Administration page of the NetWorker Management Console, select
Devices on the taskbar.
2. In the expanded left pane, select Devices.
3. From the File menu, select New, and complete the following attributes:
a. In the Name attribute, replace the default name with the path and name of the
device:
If the device is configured on the NetWorker servers storage node, the name is
the simple device path.
For example, C:\tmp\d0 for a file type device. A tape device would have a
format similar to \\.\Tape0.
Note: Do not use the 'temp' directory for NetWorker DiskBackup devices
because the data will be overwritten.
66
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
If the device is configured on a remote storage node, the name must indicate
that the storage node is remote, by including rd= and the name of the remote
storage node in the device path.
For example, if the remote storage node is neptune, then the device path might
be rd=neptune:c:\tmp\d0.
b. In the Comment field, specify a comment for the device.
c. From the Media Type attribute, select the appropriate media type.
d. Select the Auto Media Management attribute.
4. Click Configuration, and in the Target Sessions attribute:
a. Type or select a value.
b. Set this attribute to a value that will speed up the backup, for example, 32.
5. Click OK.
67
Scheduled Backup
e. For the Label template attribute, select the matching label template.
f. Perform either of the following steps, but not both:
Click the Selection Criteria tab, specify a NMM client for the Clients attribute.
or
For the Groups attribute, select the applicable backup groups.
g. In the Devices attribute:
a. Select the device that you created in the previous step.
b. Ensure that this device can accept snapshot rollovers for this pool. Labeling
the device on page 68 provides details.
4. Click OK.
Note: Snapshots can also be manually rolled over or deleted. Roll over a snapshot on
page 31 describes these procedures in more detail.
You can specify:
68
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
Description
Serverless
A single snapshot is taken per day. The data is then rolled over to
conventional storage and the snapshot is deleted. This is a simple snapshot
policy that can be considered as a default snapshot policy in NMM.
The serverless snapshot policy in NMC can be used in true serverless backup
operations, as described in Serverless backup on page 31, and can also
be used in normal non-serverless operations.
Daily
The daily snapshot policy in NMC has Retain Snapshots set to eight. This
indicates that NMM should keep eight snapshots per day. When the ninth
backup starts at the beginning of the next day, the oldest snapshot is
deleted, and so on. Each snapshot has 24-hour expiration policy. If you
select the daily snapshot policy, persistent snapshots are created.
Configuration tasks
69
Scheduled Backup
Description
All
The All attribute is used to roll over the replica for every backup to the
conventional backup medium. The data can be recovered from the
conventional backup medium, even if persistent snapshots (valid or
invalid) are not available:
To back up SYSTEM COMPONENTS, the snapshot policy must specify
All in the Backup Snapshot field. NMM enforces this policy to
ensure that a permanent backup of the snapshot exists. If you attempt
to restore SYSTEM COMPONENTS from a persistent snapshot, the
snapshot can become invalid and leave the system in an
unrecoverable state.
For Data Protection Manager backups, the Backup Snapshot attribute
must be set to All. Backup will fail if any other value is used.
Every n
First
Last
None
4. Click OK.
70
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
Conventional backup
Comment
Retain snapshots
Day
Backup snapshots
All
Table 17 on page 71 lists the settings for an instant backup for hardware snapshots.
Table 17 Hardware instant snapshot policy
Name
Instant backup
Comment
Retain snapshots
Week
Backup snapshots
None
Table 18 on page 71 depicts settings for an instant backup hardware snapshots with
rollover to a conventional medium.
Table 18 Hardware instant snapshot with rollover policy (page 1 of 2)
Name
Comment
Configuration tasks
71
Scheduled Backup
Week
Backup snapshots
Every 1
Every 3
Consideration
Full level
Incremental backups
Level 1 to 9 backups
72
Backup pools
Schedules
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
Snapshot policy
A client resource or backup group cannot specify volumes that use both CLARiiON and
Symmetrix storage systems. Each backup group and its client resources can specify
volumes from only one type of storage system. For hosts that have both CLARiiON and
Symmetrix volumes, create separate backup groups and client resources.
Do not create multiple instances of the same client in one backup group when
configuring a backup. Two backups on one client in parallel cannot be performed.
When creating a backup group, it is important to keep in mind the NMM and group
resources impact on browse and retention policies. For example, if client resource A
has save set X, and client A belongs to two groups: group_1 for full backup and
group_2 for incremental backup, the full backup of save set X expires before the
incremental backup of save set X. This is because the client resource client A and save
set belong two different groups. You are recommended to create only one group
resource for one client resource even when both full and incremental level backups
are performed.
Note: For SQL VDI based backups, in the Start Time attribute type the time when
you want the first VDI backup to begin.
d. For the Autostart attribute, select Enabled.
e. For VSS based (snapshot) backups, select the Snapshot attribute.
Note: For SQL Server VDI based backups, leave the Snapshot attribute clear.
f. For the Snapshot Policy attribute, select a snapshot policy:
The Number of Snapshots attribute works in conjunction with the Group
Resource Interval and Start Time attributes.
Configuration tasks
73
Scheduled Backup
The value for the Start Time and Interval attributes must allow the specified
number of snapshots to be created in a 24-hour period.
Note: Skip this step for SQL Server VDI based backups.
g. For the Snapshot Pool attribute, select a pool that was created for the snapshot.
Note: Skip this step for SQL Server VDI based backups.
4. Click the Advanced tab:
a. For the Interval attribute, specify how often a snapshot will be created. The Interval
attribute works in conjunction with the following:
The backup group Start Time attribute
The snapshot policy Number of Snapshots attribute.
b. Ensure that Restart Window attribute value is set to 00:01.
c. Set the Client Retries attribute to 0 (zero). This value specifies the number of times
the NetWorker software attempts to back up a failed client.
5. Click OK to create the backup group.
After you have started a snapshot of a save group, do not interrupt or halt the snapshot
process. For example, in an Exchange Server backup, the nsrsnap_vss_save.exe process
on the production server and the eseutil process on the proxy may continue to run after
the snapshot is halted.
Any attempt to stop a group in NetWorker Management Console will take a long time to
complete.
For each client resource, the NetWorker server does the following:
74
Maintains the client resource information, including entries in the online client file
index and media database.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
You can create multiple client resources for the same NMM client host. In this way, you can
apply different backup attributes to different types of information on the same host.
For example, if the NMM client host is an Exchange Server:
This way, you can back up Exchange databases many times a day, and back up Windows
system component data once a day.
URL-encoded value
Special
character
URL-encoded value
%5C
%3F
%2F
%5D
"
%22
%5B
%25
%7D
%23
%7B
Configuration tasks
75
Scheduled Backup
URL-encoded value
Special
character
URL-encoded value
&
%26
%5E
<
%3C
%60
>
%3E
%7C
Entering the details manually in the Client Properties pageFor file system,
SharePoint Server, Exchange Server, DPM Server, Hyper-V Server, SQL Server (both
VSS and VDI), and Active Directory, you can manually enter the details in the Client
Properties page.
To manually create a client resource:
a. In the Administration page of the NetWorker Management Console, click
Configuration.
b. In the expanded left pane, select Clients.
c. From the File menu, select New.
The Client Properties page displays. Enter the details in the Client Properties page.
The settings and requirements are described in the scheduled backup sections for
each application in the NetWorker Module for Microsoft Applications Release 2.4
Application Guide.
Using the Client Configuration Wizard You can use the Client Configuration Wizard to
create client resources for VDI based backups of SQL Server, and VSS based backups
of SharePoint Server and Exchange Server. The Client Configuration Wizard is not
available for creating client resources for VSS based backups of file system, SQL
Server, Hyper-V, DPM, and Active Directory.
The Client Configuration Wizard configures the client resources by fetching the details
from the configuration setup and displays the details in a summary page. To use the
Client Configuration Wizard option from the NetWorker Management Console, you
must installed:
NetWorker server 8.0
NetWorker Management Console server 8.0
NetWorker client 7.6 SP2 or later
76
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
Where multiple users are configured and added to an administrator group and that
group is added on NetWorker privilege list. All the users under this group have
administrator rights.
To perform all the NetWorker functionality for a host, add the following values:
group=administrator,host=NMM_clientproxy_host
group=system,host=NMM_clientproxy_host
Configuration tasks
77
Scheduled Backup
Description
The proxy client must have the same version of the NMM client software, and operating
system version and patch level, as the host for which it is acting as the proxy client.
Configuration
78
Connectivity
Serverless backups
At least one CLARiiON LUN must be permanently assigned to the proxy host.
Third-party hardware
providers
Hardware providers may have additional configuration requirements for proxy clients.
The vendors product documentation provides details on these requirements.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
Details
Do not use the pathownerignore functionality because this restriction is not enforced by
NMM. Ensure that ansr\bin\pathownerignore file is not used or set. In some
circumstances, during backup, the path owner may be ignored by NMM and the data from
a clustered disk is backed up under the indexes of the physical node. However, the
recovery of the data fails.
Clustered disks must be backed up under a virtual cluster client.
79
Scheduled Backup
80
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
6. Click Refresh (
).
Figure 16 on page 81 shows the Select Viewable Clients dialog box. The clients
available on the NetWorker server that you are attached to are listed under Available
clients on.
81
Scheduled Backup
8. Click the Client list, and select the client that created the volume backup as the
browsable client.
9. If the Snapshot Management or Monitor is the active navigation bar item, and you are
prompted with the Navigate Away dialog box, click Yes.
10. On the System Recover Sessions bar, select Recover Options. The NetWorker System
Recover Session Options dialog box displays.
11. On the NetWorker tab:
a. Specify the destination for the recovery in the Relocate Recovered Data box.
b. Click OK.
12. Recover remote client's backup to local destination.
Note: Although SharePoint Server 2007 save sets are browsable in Snapshot Management
view on a host with SharePoint Server 2010, do not perform any operation for snapshots
from remote machine.
82
For filesystem and VSS backups Select the Encyrption directive from the Directive
menu in the general tab when configuring the client resource. This must be done for
all applications for which AES encryption must be implemented.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Scheduled Backup
For example, in Figure 18 on page 83, the Encryption directive is selected in the
Directive field when configuring the client resource for SQL VSS backup.
For VDI backups The NetWorker Module for Microsoft Applications Release 2.4
Application Guide provides details on AES encryption for SQL VDI client resource.
83
Scheduled Backup
Best practice
For application servers, such as SQL Servers or Exchange Server, back up the server
application data under a schedule different than the host operating system data and
volumes.
Typically, application data is backed up several times a day while operating system
data and volumes are backed up less frequently.
To accomplish this task:
1. Create a separate backup group, snapshot policy, and client resource for the
following:
Server application data
Volumes and operating system data
2. Assign the appropriate snapshot policy and client resource to each backup group.
Do not install application server program files on the same volume as the
applications database files and the log files.
If SQL Server Writer service is disabled, you can enable the recovery of all SQL data
by performing the following:
1. Re-enabling the SQL Server writer service.
2. Backing up the SQL Server, this will enable you to recover all SQL data.
French and Spanish characters are not printed in the command prompt on Windows.
This is a Windows operating system issue.
84
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
CHAPTER 5
Data Deduplication with Avamar
This chapter includes the following topics:
86
87
87
90
91
91
92
95
98
98
99
85
Deduplication differentiators
The key deduplication differentiators are as follows:
Deduplicates backup data at the source, before data transfer across the network
Enables fast, daily full backups across existing networks and infrastructure
Patented RAIN technology provides fault tolerance across nodes and eliminates single
points of failure
Data deduplication replaces multiple copies of the same data scattered across networks
with a reference to a single instance or source for the data. Edited files also have
tremendous redundancy with previous versions.
86
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Backup type
Full initial
backup
Subsequent
daily, full
backups
Subsequent daily,
incremental
backups (with a
weekly full)
Non-deduplication
x hours
x hours
1/10 x hours
Deduplication
(daily full)
x hours
1/5 x hours
1/20 x hours
Deduplication
x hours
(daily incremental)
87
Supported applications for single and multi streams when using Avamar on page 89
The NetWorker Software Compatibility Guide contains additional and the most up-to-date
information about NMM compatibility.
Because the data deduplication process in NetWorker Module for Microsoft Applications
(NMM) requires Avamar and NetWorker installation and configuration, we recommend that
you review the listed documentation in Related documentation on Avamar and
NetWorker on page 90 for details about Avamar and NetWorker installation and
configuration for more information.
88
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Data deduplication with Avamar is not supported for Active Directory granular and System
Center Data Protection Manager 2007.
Supported configurations
NMM supports deduplication on the following configurations:
System Provider
Cluster configurations are supported for the following in the preceding lists:
Operating systems
Applications
Configurations
NMM does not support deduplication for the following features and configurations:
NetWorker features: AES Encryption, Cloning/Staging, and Compression
Windows configurations: EFS File Systems
Supported applications for single and multi streams when using Avamar
Related documentation on Avamar and NetWorker on page 90 lists the documentation
that provides details about single and multi streams when using Avamar.
Table 25 on page 89 lists the Microsoft applications for which single and multi stream
support is available when using Avamar .
Table 25 Single and multi streams support to and from Avamar (page 1 of 2)
To Avamar
From Avamar
Microsoft Applications
SIngle
stream
Multi
stream
SIngle
stream
Multi
stream
89
Table 25 Single and multi streams support to and from Avamar (page 2 of 2)
To Avamar
From Avamar
Microsoft Applications
SIngle
stream
Multi
stream
SIngle
stream
Multi
stream
Hyper-V
Active Directory
Note: If you are using both, Avamar data deduplication support and stripes support for
SQL Server VDI backup and recovery, ensure that the save streams value is less than or
equal to four.
The white paper: Efficient Backup and Recovery with EMC Avamar Deduplication
Software and Systems This white paper provides a technical overview of EMC
Avamar backup and recovery software and systems with integrated global, source
data deduplication technology. It includes an in-depth look at the Avamar
architecture, data deduplication technology, key applications, and deployment
options.
The NetWorker Administration Guide This document describes how to create the
following:
Deduplication storage node
Replication nodes
Additional deduplication operation information is available with the documentation
on the following NetWorker features:
Backup statistics basic reports
Events
90
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Perform deduplication recover The process for recovering data from a deduplication
node is the same as that for recovering from a storage node.
File and data sizes vary between applications, so Avamar optimizes compression by
analyzing the data in the save set and by using the best chunking size for that data.
Set the DNS resolution for NetWorker deduplication node and NMM on page 92
91
Set the DNS resolution for NetWorker deduplication node and NMM
The NetWorker deduplication node and the NMM hosts require a DNS resolution between
nodes.
The NMM hosts include one or more of the following:
NMM client
On the NMM hosts, ensure the hosts have DNS name resolution for the NetWorker
deduplication node:
If the NMM hosts do not have DNS resolution for the NetWorker deduplication
node, then that needs to be repaired.
Check your operating system documentation for information on how to fix DNS
resolution problems.
On the NetWorker deduplication node, ensure it has DNS name resolution to the NMM
hosts:
If the NetWorker deduplication node does not have DNS resolution for the NMM
hosts, then that needs to be repaired.
Check your operating system documentation for information on how to fix DNS
resolution problems.
92
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Only the metadata is stored on a NetWorker storage node. The backed-up client data is
stored on a deduplication node (Avamar server). The metadata can be cloned in the usual
manner, while a copy of the backed-up data can be replicated on another deduplication
node.
When configuring a NMM client resource for deduplication, there are several special
requirements or considerations:
If the deduplication node for an existing deduplication client is changed or if another type
of client is upgraded to a deduplication client, a new full backup of the client data must be
performed, regardless whether the most recent backup performed was a full backup.
The initial full backup of a deduplication client takes longer than a regular backup of the
same client data due to the initial overhead involved in deduplicating the data. All
subsequent deduplication backups benefit from the fact that now only the data segments
(not files) that have changed since the previous backup will be backed up. However, the
choice of subsequent backup levels, depends on what is more important to the user:
backup performance or recovery performance. Deduplication clients should use backup
schedules that support that priority.
Deduplication backups must be scheduled to avoid the deduplication node's read-only
periods. The Avamar server documentation provides more information regarding the
read-only periods and backup level strategies.
This schedule benefits an environment in which the speed of the backup is most
important.
The daily incremental (Level 1) deduplication backups will take significantly less time
than daily regular incremental backups and even less time than daily full
deduplication backups.
93
After 1 week of backups, this schedule results in slightly longer recovery times, due to
the latency involved in restoring seven backup images (the initial full backup,
followed by applying each incremental backup to the full backup).
This schedule benefits an environment in which the speed of data recovery is most
important.
After the initial full backup, daily full deduplication backups take only slightly longer
than regular daily incremental backups.
After 1 week of backups, this schedule results in much shorter recovery times, since
only a single backup image must be recovered.
Retention policies
If a volume contains one or more deduplication save sets, the resource for the
deduplication node that was used to create the backup must exist when the save sets
pass their retention policy.
If the resource for the deduplication node has been deleted, the volume cannot be made
recyclable or relabeled. When deduplication save sets pass their retention time, the
NetWorker server will begin the process of deleting the deduplicated data from the
deduplication node. Therefore, deduplication data may not be recoverable by using the
scanner program after the deduplication save set has passed its retention time.
The NetWorker Administration Guide provides more information about retention policies,
and the save set recover and scanner programs.
Do not place both regular and deduplication clients in the same groups.
Ensure that all deduplication clients in the same group have the same deduplication
node setting.
An alternate method is available to handle tape backups of the deduplication client data:
1. Create a second instance of the client to be backed up.
Do not configure the second instance as a deduplication client.
94
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
2. If you are using multiple backup schedules, ensure that the backup level is set to full
for all groups.
This is required because the backup level and the last backup time are calculated by
using both the group name and save set name, and the groups would interfere with
each other.
The NetWorker Module for Microsoft Applications Release 2.4 Application Guide provides
details.
When configuring a client resource, review these considerations:
Ensure that the deduplication client has been assigned to a group that contains only
deduplication clients.
Do not mix regular and deduplication clients within a group. Configure a backup
group on page 72 provides information about creating backup groups.
To configure a deduplication scheduled backup for any client resource by using Avamar:
1. In the Administration page of the NetWorker Management Console, click
Configuration.
2. In the expanded left pane, select Clients to view all the clients that have been already
created.
Configuring a client resource for deduplication backup
95
96
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
d. For the Retention Policy attribute, select a retention policy from the list. The
retention policy determines the time period during which the rolled-over data is
available, although not necessarily quickly.
e. Select the Scheduled Backups attribute.
f. In the Save Set attribute, specify the save set name for the specific application that
is being backed up.
5. Click the Apps & Modules tab, as shown in Figure 20 on page 97:
97
a. By default, NMM uses client parallelism set to 4 for all deduplication clients.
Because deduplication backups require more CPU and memory resources on the
host where the backup is performed, it might be necessary to reduce the client
parallelism for configurations with either a large number of save sets, or a large
number of volumes.
b. Complete the remaining configuration information, for the specific application that
is being backed up.
7. Click OK.
Save sets in which nothing was backed up as the result of a skip schedule
These save sets are treated as regular save sets, not as deduplicated save sets.
98
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Under some conditions, if recovery from the primary deduplication node fails,
autorecovery uses a replication node. The NetWorker Administration Guide provides
detailed information about recovery from a replication node.
99
100
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
CHAPTER 6
Data Deduplication with Data Domain
This chapter includes the following topics:
101
Software requirements
For NMM to leverage the NetWorker Data Domain integration support, the following
software are required:
Data Domain Appliance with Data Domain OS version supported by NetWorker client
installed on NMM 2.4 host
The DD Boost library API enables the NetWorker software to communicate with the
Data Domain system.
Deduplicated data backups are stored on special NetWorker Data Domain (DD Boost)
storage devices on the Data Domain system that are accessed by the NetWorker storage
nodes and server.
102
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
The client will directly write to a Data Domain device, ruling out the need for a
dedicated storage node configuration.
Deduplication on the client host reduces the bandwidth for the data transfer.
DFA deduplication enables a NetWorker Data Domain device to be shared among multiple
hosts. Multiple sessions on a device improves performance without the need to create
multiple devices, which can impair performance.
NMM does not support multi-stream DFA-based backups for SQL Server VDI backup and
recovery. SQL Server VDI backup and recovery should be performed using the non-DFA
method, which uses the traditional storage node and supports both single and
multi-stream based backup.
Figure 22 on page 103 shows an example environment where DFA with DSP is used to
send deduplicated backup data directly to a NetWorker Data Domain device. The same
device can also be used by non-DFA clients that use the storage node for deduplication
backup.
Backup support
The DFA feature enables supported NetWorker clients to deduplicate their backup data
locally and store it directly on a NetWorker Data Domain device, thereby bypassing the
NetWorker storage node and reducing network bandwidth usage. Because multiple clients
with DFA backup support can share a device by using multiple sessions, DFA can reduce
the number of devices used, thereby reducing the impact on the Data Domain system
performance and maintenance.
Recovery support
If a supported DFA client has access to its NetWorker Data Domain storage device, it will
recover data directly from the device, regardless of whether DFA was used for the backup.
Because DFA bypasses the storage node, performance is improved. If the DFA client
103
cannot access the data, then the recovery process reverts to the traditional method that
uses the storage node. The Data Domain system converts the stored data to its original
non-deduplicated state for the recovery.
Supported applications for single and multi streams when using Data Domain on
page 105
The NetWorker Software Compatibility Guide contains additional and the most up-to-date
information about NMM compatibility.
104
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Client-side Domain Boost deduplication support is not available for Active Directory and
DPM Server.
Supported applications for single and multi streams when using Data Domain
Related documentation about Data Domain and NetWorker server on page 109 lists the
documentation that provides details about single and multi streams when using Data
Domain.
Table 27 on page 106 lists the Microsoft applications for which single and multi stream
support is available when using Data Domain.
Table 26 Single and multi streams support to and from Data Domain
To Data Domain
Microsoft Applications
SIngle
stream
Multi
stream
SIngle
stream
Multi
stream
Hyper-V
* SQL Server VDI support for multi stream is only available when using Dedicated Storage Nodes (DSN).
105
Consideration
Optimized
cloning
Data Domain
storage node
Client-side IO
optimization
(Data Domain
Boost)
106
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Configuring a client resource for client-side Data Domain Boost deduplication backups
107
d. For the Retention Policy attribute, select a retention policy from the list. The
retention policy determines the time period during which the rolled-over data is
available, although not necessarily quickly.
e. Select the Scheduled Backups attribute. A recommended backup schedule for
deduplication clients depends on whether your priority is faster backups or faster,
less complicated recoveries. Configure a backup schedule on page 72 provides
general information about setting backup schedules. Backup levels and
schedules for deduplication clients on page 93 provides backup level and
schedule information that is specific to deduplication clients.
f. Select the Client direct option.
Note: The client direct functionality is only available when using a Data Domain
device, and is not available for other devices.
g. In the Save Set attribute, specify the save set name for the specific application that
is being backed up.
In the Group attribute, select the group for the client resource:
Ensure that the deduplication client has been assigned to a group that contains
only deduplication clients.
Do not mix regular and deduplication clients within a group.
Configure a backup group on page 72 provides information about creating
backup groups.
5. Click the Apps & Modules tab, as shown in Figure 24 on page 108:
a. In the Access area, leave the Remote user and Password fields empty.
b. In the Backup command attribute, type the backup command:
nsrsnap_vss_save.exe
108
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
c. In the Application Information field, add parameters required for the particular
application. The NetWorker Module for Microsoft Applications Release 2.4
Application Guide provides details for each application.
d. In the Deduplication area, select the Data Domain Backup option.
6. Click Globals (2 of 2) tab of the client configuration.
7. Provide the remote storage node name where the Data Domain device is configured.
This should be the first or only entry.
During backup, the NMM 2.4 client:
Contacts this storage node to obtain the DD device credentials.
Establishes connection by using these credentials.
Sends data directly to the DD system.
8. Complete the remaining configuration information as for any normal client.
9. To verify if a backup is successful, use the following command:
mminfo -avot -s server_name -c client_name
where:
server_name is the name of the NetWorker server
client_name is the name of NMM client
Documentation related to the use of Data Domain systems can be found at the Data
Domain Support Portal (support account required), https://my.datadomain.com/,
including:
109
110
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
CHAPTER 7
Microsoft Windows System Backup and Recovery
This chapter includes the following topics:
112
112
115
118
130
131
132
134
135
135
135
136
137
111
Active Directory
Windows Clusters
Consideration
Task 2: Configure snapshot policies on page 68 To back up SYSTEM COMPONENTS:\ the snapshot policy must specify All.
NMM enforces this policy to ensure that a permanent backup of the
snapshot exists.
Attempting to restore system components from a persistent snapshot might
invalidate the snapshot and leave the system in an unrecoverable state.
Task 3: Configure a backup schedule on
page 72
112
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Details
Examples
All
Volume
SYSTEM
COMPONENTS:\
113
To protect against a disaster, ensure that all volumes and Windows system
components are backed up. Backup of SYSTEM COMPONENTS or save set All are
required to have a snapshot policy of All. This ensures that SYSTEM COMPONENTS
data is rolled over.
The snapshot policy for volumes, while not required to be rolled over, should also
specify a value of 'First', 'Last', or 'All' in the Backup Snapshots field. Online
disaster Recovery can only be performed from a conventional backup. Do not
specify None in the Backup Snapshots field.
g. For the Group attribute, select the backup group to which this client resource will
be added.
If client resources for the same NMM client host are added to different backup
groups, ensure that the Start Time attribute for each backup group is set far
enough apart so that the backups for the hosts client resources do not overlap.
h. For the Schedule attribute, select a backup schedule.
5. Click the Apps & Modules tab:
a. In the Access area, leave the Remote user and Password fields empty.
b. In the Backup command attribute, type the following backup command for all
types of backup data except for Active Directory conventional backups:
nsrsnap_vss_save.exe
c. In the Application information attribute, type the following variable and value:
NSR_SNAP_TYPE=vss
If hardware LUNs are configured in the NMM client machine, while performing
system components backup, set the following:
NSR_VSS_FORCE_SYSTEM_PROVIDER=yes
Note: An NMM backup fails in standalone data mover setups, when both the
NSR_VSS_FORCE_SYSTEM_PROVIDER=yes and
NSR_DATA_MOVER=clientname.domain.com parameters are used in the
Application Information field of the client resource.
6. Click the Globals (2 of 2) tab:
a. If a storage node is configured for the backup of SYSTEM COMPONENTS, specify
the name of the following in the Storage nodes field:
Dedicated Storage Node (DSN)
or
Remote Storage Node (RSN)
7. Click OK.
114
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Performing a recovery
This section provides information on the following:
Recovery considerations
Review the following options and considerations before performing the procedures in
these sections:
Recovering file system snapshots that have not been rolled over on page 130
provides more information about recovering data from a persistent snapshot that has
not been rolled over to a conventional backup medium.
Attempting to restore system components from a persistent snapshot may invalidate the
snapshot and leave the system in an unrecoverable state. NMM does not prevent an
attempt to restore SYSTEM COMPONENTS from a point-in-time backup. Roll over a
snapshot on page 31 describes how to rollover a snapshot.
To recover backup data that was password-protected and encrypted with another VSS
client program, and not NetWorker VSS Client for Microsoft Windows 1.0 or NMM, use
the recover.exe command from the command line interface (CLI).
The NetWorker Command Reference Guide provides more information about the
recover.exe command.
Data that was backed up from a mount point is available for browsing at the root of the
navigation tree.
For example, if the drive H:\ has a mount point named H:\CAD_Drawings, then a
separate entry for the mount point H:\CAD_Drawings will be available at the root of the
navigation tree instead of as a subfolder under H:\.
To recover data to a mount point that has been deleted, manually re-create the mount
point before recovering the data. Otherwise, the data will be recovered to a local
directory whose name corresponds to the deleted mount point.
If the disk that is referenced by the mount point has been replaced, manually re-create
the mount point.
If a file was not backed up due to a skip directive, you may still be able to select the
file for a recovery operation. In this case, although you can select the file, it is not
recoverable.
If you are recovering FRS or Windows NT Directory Services (NTDS) data, boot the
NetWorker client in Directory Service Restore mode (DSRM) before completing the recovery
options in this section. Booting the NMM host in Directory Service Restore mode on
page 131 provides more information about these recovery options.
Performing a recovery
115
Application-specific recovery steps are provided in separate chapters for the applications.
The NetWorker Module for Microsoft Applications Release 2.4 Application Guide provides
details.
116
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
117
To view the System Recover Sessions Options settings, see the following tabs:
General
NetWorker
Security
Recovery options
This section describes the following recovery options:
Note: The NetWorker Module for Microsoft Applications Release 2.4 Application Guide
includes information on the Microsoft Exchange recovery options.
118
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
2. From the Diagnostic Output Level attribute, select a level from normal to 9:
A value of 1 produces the least amount of diagnostic information.
A value of 9 produces the most diagnostic information.
The value Normal produces no diagnostic information.
3. Click OK.
Note: After each recovery, the Diagnostic Level attribute is automatically set to Normal.
Recovery options
119
5. Select Use Microsoft best practices for selecting the system state to enforce Microsoft
recommendations that determine which system state items must be selected as a
group for recovery:
This feature is only applicable to System State Restore.
Clear this attribute to select system state items individually.
Do not clear the Use Microsoft best practices for selecting the system state box except
where specifically instructed to do otherwise in this document. For instance, there are
some procedures, such as recovering DFS data, where you can clear this attribute.
Microsoft does not support recovery of portions of the operating system. Attempted
recovery of portions of the operating system, with this box cleared, may render the system
unbootable. After each recovery operation, this option is automatically selected.
6. For Directory Services Restore Mode (DSRM), to recover the Bootable System State in a
domain controller setup, ensure that the following checkbox is unchecked:
Microsoft Best Practices
7. Select Terminate recover of item if errors are encountered if it is not already selected:
This option is selected by default.
If this option is selected, then when an error occurs only the recovery of the
specific item causing the error is halted.
For example, during the recovery of the items C:\test and
APPLICATIONS:\SqlServerWriter, an error occurs during recovery of a single file in the
C:\test folder:
If the option is selected, the rest of the recovery of C:\test is terminated, but NMM
still attempts to recover APPLICATIONS:\SqlServerWriter\.
If option is cleared and there is a recovery error with a file in C:\test, NMM still
attempts to recover the rest of C:\test and APPLICATIONS:\SqlServerWriter.
8. Clear this option if file system recovery fails, and you encounter the error message:
Files failed to be restored for File system marked objects.
When this error occurs, open the EMC PowerSnap client log file and note which files
caused the error.
9. Click OK.
120
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Nonauthoritative restores will restore the cluster but will not restore a particular version of
the database, for example a file server, SQL, Exchange.
After the nonauthoritative restore is complete:
1. Perform an authoritative restore to recover a specific version of the database.
2. Select the following save set to restore the registry:
SYSTEM COMPONENTS:\BootableSystemState
This restores the Registry that contains entries for the following:
Cluster node
Cluster database
Quorum that exists only on active cluster node
Note: The NMM software performs an nonauthoritative restore by default.
Note: The registry entry for the quorum exists only in active cluster node.
7. From the System Recover Session toolbar:
a. Click Recover.
b. Click Restore.
8. Restart the system when prompted.
9. On the other nodes if required, repeat step 1 to step 8 .
121
Note: Authoritative restores of the Cluster Writer are only supported for Windows Server
2008 and Windows Server 2008 R2.
122
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
123
Chapter 4, Scheduled Backup, provides more information about specifying save sets
when configuring a backup.
DFS can have DFS shares, and also be part of Active Directory recovery.
DFS is part of Active Directory recovery if it was promoted to a Domain Controller with
the either of the following settings selected:
2008 Functional Level
2008 R2 Functional Level
To restore DFS as part of Active Directory, the system must be restarted into DSRM.
Booting the NMM host in Directory Service Restore mode on page 131 provides
more information.
The steps for performing a DFS recovery from the following Microsoft servers are described
in separate procedures:
124
A nonauthoritative recovery relies on at least one other DFS Server in the domain to
have accurate up-to-date DFS data.
Nonauthoritative recoveries are typically performed when the host is recovered due to
catastrophic loss of data such as a disk failure. This occurs when two or more domain
controllers are restored:
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Authoritative restore
An authoritative recovery restores the most recent DFS data from backups, and then
updates other DFS Servers in the domain with the recovered data.
Perform an authoritative recovery only when corrupted or deleted DFS data has been
propagated to other DFS Servers.
To recover DFS data:
1. The APPLICATIONS:\DFS Replication service writer save set must have been backed
up.
2. The SYSTEM COMPONENTS:\ save set on the namespace server (usually the domain
controller) that is associated with the DFS configuration must have been backed up.
Chapter 4, Scheduled Backup, provides more information about specifying save
sets when configuring a backup.
Recovery options
125
Do not clear the Use Microsoft best practices for selecting the system state box except
where specifically instructed to do otherwise in this document. For instance, there are
some procedures, such as recovering DFS data, where you can clear this attribute.
Microsoft does not support recovery of portions of the operating system. Attempted
recovery of portions of the operating system, with this box cleared, may render the system
unbootable. After each recovery operation, this option is automatically selected.
Boot the NetWorker client in Directory Service Recovery mode before completing the
recovery options in this section. Booting the NMM host in Directory Service Restore
mode on page 131 provides more information.
The other domain controllers must be reinitialized in direct replication partner order.
The Microsoft documentation provides details about reinitialization.
Nonauthoritative recoveries are typically performed when the host is recovered due to
catastrophic loss of data such as a disk failure.
126
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
To recover FRS data, the SYSTEM COMPONENTS:\ save set must have been backed up.
Chapter 4, Scheduled Backup, provides more information about specifying save sets
when configuring a backup.
To specify whether to perform an authoritative or nonauthoritative recovery:
1. From the Options menu:
a. Select System Recover Session Options.
b. Click the FRS tab.
2. Select one of the following options:
Non Authoritative Restore to perform a nonauthoritative recovery.
or
Authoritative Restore to perform an authoritative recovery.
3. Click the NetWorker tab.
4. Clear the following attribute:
Use Microsoft best practices for selecting the system state
Do not clear the Use Microsoft best practices for selecting the system state box except
where specifically instructed to do otherwise in this document. For instance, there are
some procedures, such as recovering DFS data, where you can clear this attribute.
Microsoft does not support recovery of portions of the operating system. Attempted
recovery of portions of the operating system, with this box cleared, may render the system
unbootable. After each recovery operation, this option is automatically selected.
6. Click OK to close the System Recover Session Options dialog box.
7. From the navigation tree:
a. Expand the SYSTEM COMPONENTS folder.
b. Click FRS.
8. From the System Recover Session toolbar:
a. Click Recover.
b. Click Restore.
If you are performing an authoritative recovery, complete the remaining steps in
Authoritative recovery of NTDS or FRS data on page 132.
Recovery options
127
Boot the NetWorker client in Directory Service Recovery mode before completing the
recovery options in this section. Booting the NMM host in Directory Service Restore
mode on page 131 provides more information about these recovery options.
Computers
Groups
Organizational units
Users
Note: To recover NTDS data, the SYSTEM COMPONENTS:\ save set must have been backed
up. Chapter 4, Scheduled Backup, provides more information about specifying save
sets when configuring a backup.
128
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Do not clear the "Use Microsoft best practices for selecting the system state" box except
where specifically instructed to do otherwise in this document. For instance, there are
some procedures, such as recovering DFS data, where you can clear this attribute.
Microsoft does not support recovery of portions of the operating system. Attempted
recovery of portions of the operating system, with this box cleared, may render the system
unbootable. After each recovery operation, this option is automatically selected.
6. For DSRM, to recover "Bootable System State" in a domain controller setup, ensure
that the Microsoft Best Practices checkbox is cleared.
7. Click OK to close the System Recover Session Options dialog box.
8. From the navigation tree:
a. Expand the SYSTEM COMPONENTS folder.
b. Click NTDS.
9. From the System Recover Session toolbar, click Start Restore.
If you are performing an authoritative recovery, complete the remaining steps in
Authoritative recovery of NTDS or FRS data on page 132.
Recovery options
129
Do not use AES encryption when backing up files that are encrypted by using Windows
Encrypting File System (EFS). When AES encryption is applied to a file that is also
encrypted by using the Microsoft EFS, the backup will be reported as successful. However,
recovery of the file will fail.
To specify pass phrases:
1. From the Options menu:
a. Select System Recover Session Options.
b. Click the Security tab.
2. Type the pass phrases.
3. Click OK.
The NetWorker Administration Guide provides more information about AES encryption,
and setting the pass phrase.
Recovering file system snapshots that have not been rolled over
Note: If a snapshot volume has been mounted by using a client utility such as the EMC
NaviCLI interface or the Windows Disk Management utility, remove the mount point before
performing the next backup or recovery operation. If the mount point is not removed, it will
be removed at the end of the next NetWorker backup or recovery operation.
To recover items in a file system backup that has not been rolled over:
1. Connect to the NetWorker server on which the NetWorker client was configured for
backup.
Connecting to a NetWorker server on page 53 provides more information about
connecting to the NetWorker server.
2. From the left pane, select Recover > System Recover Session.
3. In the navigation tree:
a. Right-click the snapshot.
b. Select Mount Snapshot.
The following occurs:
If another snapshot is currently mounted, a message indicates that the currently
mounted volume will be unmounted:
a. Click OK to unmount the volume.
b. When the taskbar animation stops and a green mark appears, click the
mounted snapshot.
The mounted snapshot item will expand in the navigation tree.
130
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
DFS recovery
FRS recovery
NTDS recovery
131
5. Log in as administrator:
Use the password that was specified when the domain controller was created.
Windows starts in safe mode.
6. Open the NMM client application.
7. From the left pane, select Recover > System Recover Session.
8. Continue with the recovery options. The following sections provide more specific
information:
DFS recovery options on page 124
FRS recovery options on page 126
NTDS recovery options on page 128
Security recovery options on page 129
Recovering the Windows system configuration to an earlier state on page 134
includes information about SYSTEM STATE or VSS SYSTEM BOOT save sets, and
save set recovery.
Granular Active Directory or ADAM backup optionThe NetWorker Module for
Microsoft Application Release 2.4 Application Guide includes information about
save sets on a domain controller.
Note: Active Directory schema objects cannot be recovered and therefore, should
never be deleted.
132
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
3. From the command line, use the xcopy command to copy sysvol\domain to another
location.
4. This preserves the following information:
Group policy
File permissions
Directory permissions
5. Run the Windows ntdsutil utility.
6. At the ntdsutil prompt, type:
NTDSUTIL: authoritative restore
For example:
NTDSUTIL: restore subtree
OU=engineering,DC=Seattle,DC=jupiter,DC=com
NTDSUTIL: restore subtree
CN=mars,CN=users,DC=Seattle,DC=jupiter,DC=com
The Microsoft Windows Server Resource Kit provides more information and Active
Directory documentation.
8. Exit the ntdsutil utility by typing quit at each successive ntdsutil prompt until the
command prompt displays.
9. Copy the entire recovered SYSVOL\domain directory and all of its subdirectories to a
new location.
10. Restart the domain controller in normal mode.
11. Log in to the domain controller.
12. Wait for the SYSVOL share to be published.
Note: This can take several minutes while the recovered domain controller
synchronizes with its replication partners.
13. After the SYSVOL share has been published, perform one of the following:
For an authoritative recovery of the entire database:
a. Copy the entire SYSVOL\domain directory tree from the new location to the
existing SYSVOL\domain directory as described in step 9 .
b. When the copy operation prompts for confirmation, select Yes to All.
133
For an authoritative recovery of only a part of AD that includes Policy objects, copy
the policy folders from the new location as described in step 9 to the existing
policy folders:
Policy objects can be identified by their global universal ID (GUID).
Policy folders are located in SYSVOL\domain\Policies.
If the Windows operating system was upgraded on the host, you cannot recover the
Windows system configuration to the state it was in before the operating system software
was upgraded.
To recover the Windows system state to a point-in-time that precedes the installation of
the NMM client:
1. If the NMM client is a Windows domain controller, boot the NMM client in Directory
Services Restore mode. Booting the NMM host in Directory Service Restore mode on
page 131 provides more information about booting in this mode.
If the NMM client is not a Windows domain controller, start with step 2 .
2. Recover the contents of the volume on which the Windows operating system was
installed.
3. Recover the Windows configuration save sets:
If VSS was licensed and enabled, recover:
VSS SYSTEM BOOT
VSS SYSTEM FILESET
VSS SYSTEM SERVICES
If VSS was not licensed or enabled, recover:
SYSTEM DB
SYSTEM FILES
SYSTEM STATE
4. Update the recovered registry with NMM client entries. Because the registry was
recovered to a client state prior to the NMM client installation, you must update the
registry with entries for the NMM client.
To update the registry:
a. Uninstall the NMM client software.
b. Reinstall the NMM client software.
134
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Reinstall, as necessary, any other applications that were installed after the point-in-time to
which the Windows operating system configuration was recovered. The NetWorker Module
for Microsoft Applications Release 2.4 Installation Guide provides more information about
the uninstall and install steps.
135
Because DFS-R replicated folders and data is backed up as file system data, all the
features supported by file system data backup and recovery are supported by DFS-R
granular support.
precmd.bat script
You can create a precmd.bat script file to enable actions to be performed before a backup
operation. When the NetWorker server starts the backup, the contents of the
nsrsnap_vss_savepnpc.exe file is run on the client to perform the required actions.
To create a precmd.bat script file:
1. Create a new file on the Windows client by using Notepad.
2. Specify a command to run before the backup. For example, add the following lines to
the file:
echo
time
date
<Add
echo
time
date
3. Save this file as precmd.bat in a new directory that does not contain spaces. For
example: C:\Scripts.
postcmd.bat script
You can create a postcmd.bat script file to enable actions to be performed after a backup
operation.
To create a postcmd.bat script:
1. Create a new file on the Windows client by using Notepad.
2. Specify a command to run after the NetWorker software has backed up the data.
136
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
3. Save this file as postcmd.bat in a new directory that does not contain spaces. For
example: C:\Scripts.
nsrsnapvsssavepnpc file
To run the pre and post command scripts that were created in the previous steps, you
must create the nsrsnapvsssavepnpc file. This file lets the NetWorker software know that a
pre and post action is required.
To create a nsrsnapvsssavepnpc file to run the pre and post actions:
1. Create a new file on the Windows client by using Notepad.
2. Add the following lines to the file:
type: nsrsnapvsssavepnpc;
precmd: "C:\\Scripts\\precmd.bat";
pstcmd: "C:\\Scripts\\postcmd.bat";
where groupname is the name of the NetWorker backup group to which this client
belongs.
where volume_name is the volume that contains the client file index.
3. From the mminfo output, find the ssid that contains the required file. Ensure it is not
the bootstrap ssid.
4. Type the nsrmm command with a new browse time:
nsrmm -S ssid -w <browse_time>
137
Restoring a save set entry to the client file index and media database
If a volume has a save set that does not appear in the media database and the save set's
files are not browsable, you can restore these entries in the media database and the client
file index so that the save set's files can be browsed.
To rebuild the save set's entry in the media database and the client file index:
1. Log in as root or Windows Administrator.
2. At the command prompt, run the scanner program on the volumes that contain the
appropriate file or files:
scanner <device_name>
If the volume contains data from an earlier version of NetWorker, there may be no pool
information on the volume. In this case, the volume is considered to belong to the
Default pool. To assign the volume to another pool, use the -b pool_name option in
this step. If the volume already belongs to a pool, the -b option will have no effect.
b. Query the media database to determine the sequence in which the volumes were
written:
mminfo -a -v
In Step 5, the volumes must be reintroduced into the online indexes in the same order
in which they were written.
5. Starting with the first volume that was written, run the scanner program:
scanner -i <device_name>
The scanner program prompts for a new volume until you terminate it. Scan in the
remaining volumes in the order in which they were written.
6. Browse for the file to be recovered. Recovering by file selection provides information
about browsing for a file.
138
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
CHAPTER 8
Microsoft Windows Cluster Backup and Recovery
This chapter includes the following topics:
Overview............................................................................................................... 140
Performing Windows Server Cluster backups ......................................................... 143
Performing Windows Server Cluster recovery ......................................................... 144
139
Overview
This chapter supplements the overall NetWorker Module for Microsoft Applications (NMM)
backup procedures in the following sections:
Backup and recover information is also included for the following clusters:
Components used by NMM for Windows Cluster backup and recovery on page 140
Windows Server 2008 SP2 (x86, x64) Enterprise Edition and Datacenter Edition
Description
SYSTEM COMPONENTS:\
140
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
The virtual client is saturn, which can reside on Node A or fail over to Node B.
In a normal NetWorker backup of saturn without curphyhost listed in the virtual clients
Storage Nodes attribute the save data is directed to the remote device (rd=) on Node A.
When saturn fails over to Node B and a backup for saturn is initiated, the save data is still
directed to the remote device (rd=) on Node A.
Listing "curphyhost" first in saturns Storage Nodes attribute modifies the NetWorker
operation so that if saturn fails over to Node B and a backup of saturn is initiated, the save
data is directed to the remote device (rd=) on Node B. This action takes place because,
after the failover saturn resides on Node B, the current physical host.
Note: The curphyhost attribute is not supported for Exchange Server 2010.
Overview
141
142
Attribute Name
Description
Values
NSR_SNAP_TYPE=value
vss
This value is required.
NSR_DATA_MOVER=value
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Description
Tasks 1, 2, and 3 are performed for scheduling a backup, and are the same
for all VSS writers supported by NMM.
Tasks 4, 5, and 6 are additional considerations that are required for setting
up a virtual NMM client.
There is an additional consideration for backing up a clustered client resource. The proxy
client is not allowed to be a member of the cluster. This is by Microsoft design and
Microsoft describes this restriction in a MSDN article at
http://msdn.microsoft.com/en-us/library/aa384600(VS.85).aspx, in the subsection
Auto-Import Hardware Shadow Copies Are Not Supported on Windows Cluster Service.
If a node within a cluster undergoes failover during a backup operation, the operation
fails. The next scheduled backup operation will be the next valid backup.
If using a hardware provider, such as the EMC VSS Provider, use the disk management
utilities provided with the associated hardware to delete any resources that may be
left in an indeterminate state as a result of the failed backup.
For example, a CLARiiON storage solution may have an inactive snapshot as the result of a
failed backup. In this case, use the Navisphere/Unisphere user interface or the NaviCLI
command line interface to search for and delete the inactive snapshot.
143
144
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
GLOSSARY
This glossary contains terms related to disk storage subsystems. Many of these terms are
used in this manual.
A
ad hoc backup
administrator
administrators group
Application Specific
Module (ASM)
ASR writer
The VSS Writer, which is responsible for identifying critical data that is needed to perform
an offline restores.
archive
Backing up directories or files to an archive volume to free disk space. Archived data is not
recyclable.
archive volume
Volume used to store archive data. Archived data cannot be stored on a backup volume or
a clone volume.
autochanger
autochanger sharing
Feature that enables the storage device to automatically label, mount, and overwrite an
unlabeled or recyclable volume.
See library.
See library sharing.
B
backup
backup group
See group.
backup level
See level.
backup volume
Volume used to store backup data. Backup data cannot be stored on an archive volume or
a clone volume. See also volume.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
145
Glossary
bootstrap
Save set that is essential for NetWorker disaster recovery procedures. The bootstrap
consists of three components that reside on the NetWorker server. The media database,
the resource database, and the server index.
The ASR Writer component that identifies the location of the boot configuration database.
This is required to perform an offline restore.
NetWorker policy that specifies how long backed-up data will be readily available for
recovery. Backed-up data that has not exceeded its browse policy time can be recovered
more quickly than data that has exceeded its browse policy time but not its retention
policy time. See also retention policy.
C
carousel
client
client file index
client-initiated backup
See library.
Computer, workstation, or fileserver whose data can be backed up and recovered.
Database that tracks every database object, file, or file system that is backed up. The
NetWorker server maintains a single client index file for each client.
client resource
NetWorker server resource that identifies the save sets to be backed up on a client. The
client resource also specifies information about the backup, such as the schedule, browse
policy, and retention policy for the save sets. See also client and resource.
clone
Reliable copy of backed up data. Unlike volumes created with a simple copy command,
clone volumes can be used in exactly the same way as the original backup volume. Single
save sets or entire volumes can be cloned.
clone volume
Exact duplicate of a backup volume. One of four types of volumes that NetWorker software
can track (backup, archive, backup clone, and archive clone). Save sets of these different
types may not be intermixed on one volume.
cluster
1. Two or more independent network servers that operate and appear to clients as if they
are a single unit. The cluster configuration enables work to be shifted from one server to
another, providing "high availability" that allows application services to continue despite
most hardware or software failures. Also known as an agent (Sun), logical server (HP
TruCluster), package (HP-UX), and virtual server (Microsoft).
2. Group of disk sectors. The operating system assigns a unique number to each cluster
and keeps track of files according to which clusters they use.
command line
component
Line on a display screen, also known as a command prompt or shell prompt, where you
type software commands.
1. Group of related data that must be treated as a single unit for backup and recovery.
2. In Microsoft VSS terminology, a component is a subordinate unit of a writer.
components metadata
document
146
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Glossary
consistent
console server
conventional backup
critical volume
D
domain controller
Computer that stores directory data and manages user interactions within a domain,
including logon, authentication, directory searches, and access to shared resources.
Client system or application, such as NetWorker, that moves the data during a backup,
recovery, or snapshot operation. See also proxy client.
directive
disk subsystem
Microsoft Windows add-on that allows you to create a logical directory of shared
directories that span multiple machines across a network.
Method of recovery that recovers data that originated on one client computer and
re-creates it on another client computer.
Instruction that directs NetWorker software to take special actions on a given set of files
for a specified client during a backup or recovery operation. Directives are ignored in
manual (unscheduled) backups.
Integrated collection of storage controllers or HBAs, disks, and any required control
software that provides storage services to one or more hosts, such as CLARiiON arrays.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
147
Glossary
F
file index
file system
full backup
See level.
G
group
Client or group of client computers that are configured to back up files at a designated
time of day.
granular recovery
Granular recovery provides the ability to recover specific files in seconds from a single
backup. This dramatically reduces the recovery time and the footprint of the backup on
storage resources.
H
high-available system
host ID
System of multiple computers configured as cluster nodes on a network that ensures that
the application services continue despite a hardware or software failure. Each cluster
node has its own IP address with private resources or disks that are available only to that
computer.
Serial number that uniquely identifies a host computer.
I
inactivity timeout
incremental backup
Process of creating a point-in-time copy (snapshot) of data from a single client and saving
it on a primary storage volume, which can be immediately recovered as a backup copy.
instant restore
Process of copying data created during an instant backup to its original location, or to an
alternate location, during a recover operation.
J
jukebox
label
legacy method
148
See library.
Electronic header on a volume used for identification by NetWorker or other Data Mover
application.
Use of special-case Microsoft APIs to back up and recover operating system components,
services, and applications.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Glossary
level
Backup configuration option that specifies how much data is saved during a scheduled or
manual backup. A full (f) backup backs up all files, regardless of whether they have
changed. Levels one through nine [1-9] backup files that have changed since the last lower
numbered backup level. An incremental (incr) backup backs up only files that have
changed since the last backup.
library
Hardware device that contains one or more removable media drives, as well as slots for
pieces of media, media access ports, and a robotic mechanism for moving pieces of
media between these components. Libraries automate media loading and mounting
functions during backup and recovery. The term library is synonymous with autochanger,
autoloader, carousel, datawheel, jukebox, and near-line storage.
library sharing
Shared access of servers and storage nodes to the individual tape drives within a library.
locale settings
NetWorker client that is not bound to a physical machine, but is instead managed by a
cluster manager. It is also referred to as a logical or virtual client.
Settings that specify the input and output formats for date and time, based on local
language conventions.
Logical unit of storage on a CLARiiON system. This refers to a device or set of devices,
usually in a CLARiiON storage array.
LUN address
SCSI identifier of a logical unit number (LUN) within a device target. Each LUN address
identifies a device on a SCSI bus that can perform input/output (I/O) operations.
M
manual backup
media
media database
media index
metadata document
mount
mount point
Backup that a user performs from the client, also known as an unscheduled backup or an
ad hoc backup. The user specifies the files, file systems, and directories to back up.
Physical storage medium, such as magnetic tape, optical disk, or file system to which
backup data is written.
Database that contains indexed entries of storage volume location and the life cycle
status of all data and volumes managed by the NetWorker server. See also volume.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
149
Glossary
N
Network Data
Management Protocol
(NDMP)
NetWorker administrator
NetWorker client
See client.
NetWorker Console
server
NetWorker Management
Console
NetWorker server
nonpersistent snapshot
Computer on a network running the NetWorker software, containing the online indexes,
and providing backup and recover services to the clients on the same network.
O
online indexes
Databases located on the NetWorker server that contain all the information pertaining to
the client backups (client file index) and backup volumes (media database).
online restore
A restore operation performed using the normal recover UI, and the computer has been
booted from an installed operating system.
offline restore
operator
Person who monitors the server status, loads backup volumes into storage devices, and
executes day-to-day NetWorker tasks.
150
pathname
Set of instructions to the operating system for accessing a file. An absolute pathname
indicates how to find a file starting from the root directory. A relative pathname indicates
how to find the file starting from the current directory.
persistent snapshot
Snapshot that is retained on disk. A persistent snapshot may or may not be rolled over to
tape.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Glossary
Fully usable copy of a defined collection of data, such as a consistent file system,
database, or volume, which contains an image of the data as it appeared at a single point
in time. A PiT copy is also called a shadow copy or a snapshot.
policy
Set of constraints that specify how long the save sets for a client are available for recovery.
Each client has a browse policy and a retention policy. When the retention policy expires,
the save sets associated with that policy are marked recyclable.
pool
PowerSnap
provider
proxy client
Q
quiescing
Process in which all writes to disk are stopped and the file system cache is flushed.
Quiescing the database prior to creating the snapshot provides a transactionally
consistent image that can be remounted without file system checks or database
consistency checks. Quiescing a database is the most common way of creating a database
snapshot.
R
recover
Registry
requestor
replica
resource
Component that describes the NetWorker server or its clients. Clients, devices, schedules,
groups, and policies are all NetWorker resources. Each resource has attributes that define
its properties.
restore
Process of retrieving individual datafiles from backup storage and copying the files to disk.
retention policy
NetWorker policy that specifies the minimum period of time that must elapse before
backed-up data is eligible to be overwritten on the backup media. Backed-up data that
has not exceeded its browse policy time can be recovered more quickly than data that has
exceeded its browse policy time but not its retention policy time. See also browse policy.
retrieve
151
Glossary
rollover
root
S
save set
To recover data by specifying save sets rather than by browsing and selecting files or
directories.
save stream
The data and save set information being written to a storage volume during a backup.
server index
serverless backup
service port
Backup method that uses a proxy client to move the data from primary storage on the
application server host to secondary storage on another host. Serverless backups free up
resources on the application server by offloading the work of processing snapshots to a
secondary host.
Port used to listen for backup and recover requests from clients through a firewall.
shadow copy
Temporary, point-in-time copy of a volume created using VSS technology. See also Volume
Shadow Copy Service (VSS).
Complete roadmap of what was backed up at a single instant in time. The shadow copy set
contains information about the Writers, their components, metadata, and the volumes. A
backup components metadata document containing that information is created and
returned to the requestor after the snapshot is complete. NetWorker uses this document
with the corresponding save set at recover time.
skip
snap clone
152
Group of files or a file system from a single client computer, which is backed up on storage
media.
Defined and standard coordination between business application, file system, and
backup application that allows a consistent copy of application and volume data to exist
for replication purposes.
Backup level in which designated files are not backed up.
Exact copy of a snap set data backup. The clone operation is an archive operation without
the deletion of the source data. A new snap ID is assigned to the cloned copy.
snap ID
Also known as a snapid, a unique 64-bit internal identification number for a snap set.
snap set
Group of files, volumes, or file systems from a single client, describing the collection of
data for which a point-in-time copy is created on an external disk subsystem, such as a
storage array.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
Glossary
snapshot
snapshot expiration
policy
Policy that determines how long snapshots are retained before their storage space is
made available for the creation of a new snapshot.
snapshot policy
Set of rules that control the lifecycle of a snap set. The snapshot policy specifies the
frequency of snapshots, and how long snapshots are retained before recycling.
snapshot retention
policy
staging
stand-alone device
storage device
Policy that determines how many PIT copies are retained in the media database and thus
are recoverable.
Moving data from one storage medium to a less-costly medium, and later removing the
data from its original location.
Storage device that contains a single drive for backing up data. Stand-alone devices
cannot store or automatically load backup volumes.
See device.
storage node
Storage device physically attached to a computer other than the NetWorker server, whose
backup operations are administered from the controlling NetWorker server.
system state
All files that belong to VSS Writers with a usage type of BootableSystemState or
SystemService. This is required to perform an offline restore.
V
volume
1. A unit of physical storage medium, such as a magnetic tape, optical disk, or file system
to which backup data is written.
2. An identifiable unit of data storage that may reside on one or more host disks.
volume ID
volume mount point
volume name
volume pool
Volume Shadow Copy
Service (VSS)
VSS
VSS component
See pool.
Microsoft technology that creates a point-in-time shadow copyof a disk volume.
NetWorker software backs up data from the shadow copy. This allows applications to
continue to write data during the backup operation, and ensures that open files are not
omitted.
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
153
Glossary
W
writer
154
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
INDEX
A
Active Directory (AD)
disaster backup and recovery 24
granular backup and recovery 24
ADAM
authoritative restore 123
nonauthoritative restore 123
All save set
considerations for 113
application information attribute
Cluster Writer 142
Application Specific Module (ASM) pass phrase 129
authoritative restore
ADAM 123
Cluster Writer 144
DFS 125
FRS 127
NTDS 129
Avamar 109
configuration 91
B
backup client resource
configuring multiple 75
backup command attribute
applications 114
Exchange 97, 108
backup groups
configuring 72
backup levels,
deduplication 93
backup pool
creating for snapshots 66
backup save sets
specifying 113
backup schedule
configuring 72
backup time
selecting for recovery 43
backups
deduplication 93
browse policy 74
browse time
selecting for recovery 43
bulk_logged recovery model 23
cluster server
scheduling backups for 79, 112, 143
Cluster tab 144
Cluster Writer recovery
authoritative restore 144
for Windows Server 2008 122
nonauthoritative restore 144
common provider
See EMC VSS Provider 29
connection port range
specifying 54
connection to NetWorker server 41
conventional recovery
overview 33
D
deduplication
Avamar integration 109
backup configuration notes 94
backups 93
configuration 91
configuring client 95
prerequisites 109
querying deduplication save sets with mminfo 98
Deduplication Node
configuration 91
DFS recovery options 124
directory services restore mode
booting in for FRS recovery 131
booting in for NTDS recovery 131
disaster recovery
support in NMM 24
display conventions 39
DNS resolution, NetWorker Deduplication Node 92
DPM
disaster backup and recovery 24
granular backup and recovery 24
E
EMC VSS Provider
overview 29
encryption
recovering backup data 115
Exchange
disaster backup and recovery 24
granular backup and recovery 24
C
CLARiiON
provider overview 27
client resource
configuring for deduplication 95
configuring multiple 75
configuring when in a cluster 79, 112, 143
F
fake objects 39
file system
disaster backup and recovery 24
granular backup and recovery 24
recovery options 119, 122
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
155
Index
filestream data 39
FRS recovery
booting in directory services restore mode 131
consideration for 115
options 126
full backup level
consideration for 72
full recovery model 22
G
granular backup and recovery
support in NMM 24
groups
configuring for backup 72
H
hardware providers 27
HIDD_SELECT_VIEWABLE_CLIENTS 52
Hyper-V
disaster backup and recovery 24
granular backup and recovery 24
I
incremental backup level
consideration for 72
instant backup
overview 32
instant recovery
overview 33
instant snapshot policy example 71
interface
overview 35
items
searching for recovery 42
L
label
creating for pool 67
level 1 to 9 backups
consideration for 72
level for backup
considerations for 72
M
marking items
indicators 43
partially 43
semantics 40
marking items for recovery 41
Microsoft VSS software provider
overview 29
Microsoft Windows Server 2008 28, 121, 122, 140
Microsoft Windows Server 2008 support 122
mminfo, querying deduplication save sets using 98
monitoring a recovery 46, 115, 131
multihomed environment 57
multiple client resources for backup 75
156
N
NetWorker
client file index 74
media database 74
NetWorker Deduplication Node, DNS resolution 92
Networker recovery options 119, 122
NetWorker server
connecting to 41
NetWorker User for SQL Server
40
display conventions 39
fake objects 39
marking items partially 43
nonauthoritative restore
ADAM 123
Cluster Writer 144
DFS 125
FRS 127
NTDS 129
nonpersistent backup
overview 32
NTDS recovery
booting in directory services restore mode 131
consideration for 115
options 128
O
overview
conventional recovery 33
instant backup 32
instant recovery 33
interface 35
nonpersistent backup 32
persistent backup 32
provider 29
requestor 29
rollover backup 32
software provider 29
VSS writers 27
P
partially marking items 43
pass phrase
recovering AES encrypted data 129
password
changing 55
consideration for changing 55
specifying for backup 55
password-protected
recovering backup data 115
persistent backup
overview 32
policies for snapshots 68
pool
creating for snapshots 66
label for 67
ports
service and connection port ranges 54
prerequisites
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
IndexIndex
deduplication 109
provider
overview 29
proxy client
configuring 78
requirements for 78
R
recover.exe 115
recovery
ADAM options 123
browse time selection 43
Cluster options 120
default method, choosing 119
DFS options 124
encrypted backup data 115
FRS options 126
marking items 41
NTDS options 128
password-protected backup data 115
performing for system data 116
searching for items 42
selecting a version 43
viewing progress for 46, 115, 131
volumes required for 44
recovery model
bulk_logged 23
full 22
simple 23
recovery, deduplication 98, 109
requestor
overview 29
resource for backup
configuring multiple 75
retention policy 74
rollover backup
overview 32
performing 31
pool for 66
rollover operation 31
software provider
overview 29
SQL
disaster backup and recovery 24
Symmetrix
provider overview 27
system recovery
performing 116
T
time of backup
selecting for recovery 43
topology of NetWorker multihomed 59
U
unmarking items
indicators 43
URL encoding
save sets 75
user access control 47
V
version
selecting for recovery 43
virtual cluster server
scheduling backups for 79, 112, 143
Volume Shadow Copy Service (VSS)
writers 27
volumes required for recovery 44
W
Windows Server 2008 28, 121, 122
Windows Server 2008 Cluster Writer
nonauthoritative restore 121
Windows Server Failover Clustering (WSFC) 140
S
safe mode, booting in 131
save sets
specifying for backup 113
URL encoding 75
searching for a recovery item 42
selecting items for recovery 41
server
connecting to NetWorker 41
serverless backup 27
proxy client requirement 78
service port range
specifying 54
SharePoint 2007
disaster backup and recovery 24
granular backup and recovery 24
simple recovery model 23
snapshot policies
configuring 68
snapshots
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide
157
Index
158
EMC NetWorker Module for Microsoft Applications Release 2.4 Administration Guide