NetWorker Module For Microsoft Applications Release 2.2 SP1 Installation Guide

EMC® NetWorker®
Module for Microsoft Applications

Release 2.2 SP1
Installation Guide
P/N 300-010-429
REV A01
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 2007 - 2010 EMC Corporation. All rights reserved.
Published April, 2010
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.
For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section
on EMC Powerlink.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.
2 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Installation Guide
Contents
Preface
Chapter 1 Introduction
Supported configurations...................................................................................... 12
Simple LAN-based configuration .................................................................. 12
LAN-based configuration with a proxy client ............................................. 13
LAN-free configuration ................................................................................... 14
Installation roadmap .............................................................................................. 16
Installation checklist............................................................................................... 16
Installation media ............................................................................................. 16
Pathname ........................................................................................................... 16
License information.......................................................................................... 16
Installation requirements....................................................................................... 17
Privileged user level access ............................................................................. 17
Patches and hotfixes for NMM 2.2 ................................................................. 17
Patch for deduplication backup of NMM Client if using
NetWorker 7.5.1 server .................................................................................... 18
Exchange Server 2007 credentials .................................................................. 18
SQL Server 2005 support ................................................................................. 18
Hardware requirements .................................................................................. 18
Software requirements..................................................................................... 19
Microsoft SQL and SharePoint VSS Writers ................................................. 19
Installation directories............................................................................................ 20
Chapter 2 Installing the Software

Installing NMM....................................................................................................... 22
Access the installation files ............................................................................. 22
Install the software ........................................................................................... 23
Installing NMM in a MSCS environment ........................................................... 24
Verifying the installation ....................................................................................... 25
Maintaining the installation .................................................................................. 25
Changing the password or changing to a different authorized
server .................................................................................................................. 25
Repairing the installation ................................................................................ 26
Removing the software .......................................................................................... 26
Removing previous installation of Solutions Enabler....................................... 27
Upgrading the software......................................................................................... 27
EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Installation Guide 3
Contents
Upgrading to NMM storage node ........................................................................ 27

Installing Microsoft Office SharePoint service pack .......................................... 28
Chapter 3 Silent Installation of the Software

Overview .................................................................................................................. 30
Silent installation of NMM..................................................................................... 30
Commands for silent installation of NMM ................................................... 30
NetWorker NMM command line properties ................................................ 31
PowerSnap and Replication Manager command line properties .............. 31
Sample commands for silent installation of NMM ...................................... 32
Silent removal of NMM.......................................................................................... 32
Commands for silent removal of NMM ........................................................ 32
Sample scripts for installation and removal of NMM ....................................... 33
Installing and removing NMM by using SCCM 2007 Server ........................... 34
Troubleshooting the installation ........................................................................... 35
Errors in installation of Replication Manager............................................... 35
Using non-English characters in installation path ....................................... 35
Chapter 4 Licensing and Enabling the Software

NMM client software licensing ............................................................................. 38
Add-on enabler names ..................................................................................... 38
The evaluation process ........................................................................................... 39
Evaluating a new installation.......................................................................... 39
Evaluating features on an existing installation............................................. 39
The licensing process .............................................................................................. 40
Type the license enabler code.......................................................................... 40
Obtain an authorization code.......................................................................... 41
Type the authorization code............................................................................ 42
Update enablers....................................................................................................... 43
Additional licenses............................................................................................ 43
Managing EMC licenses ......................................................................................... 44
Chapter 5 Configuring the Software

Using NMM with a VSS Hardware Provider ..................................................... 46
Hardware array installation and configuration ........................................... 46
NMM installation and configuration for
hardware provider support............................................................................. 47
Setting up a proxy server for rapid backups of VSS snapshots........................ 47
Configurations specific to PowerSnap ................................................................. 47
Configurations specific to CLARiiON ................................................................. 48
Update the CLARiiON configuration file ..................................................... 48
Update the SYMCFG authorization list......................................................... 49
Update the Navisphere Privileged Users list................................................ 49
Configurations specific to Symmetrix.................................................................. 50
Setting up the TimeFinder/Mirror (BCV) configuration
for Symmetrix .................................................................................................... 50
Setting up the TimeFinder/Snap (VDEV) configuration
for Symmetrix .................................................................................................... 54
Updating NMM settings with Exchange username, password,
or domain ................................................................................................................ 60
Update account information in NMM for Exchange Server 2003.............. 60
Update Exchange Service account information in
NMM for Exchange Server 2007 ..................................................................... 60
Contents
Changing Replication Manager port settings..................................................... 61

Configuring NetWorker SharePoint services ..................................................... 62
Matching NetWorker SharePoint Service credentials with
credentials of SharePoint Server administrator ........................................... 62
Specifying temporary storage location.......................................................... 63
Specifying the restore lock type ..................................................................... 63
Configuring Windows firewall settings .............................................................. 64
Windows firewall exception error for irccd.exe........................................... 64
Manually creating NMM firewall exceptions..................................................... 65
Contents
Preface
As part of its effort to continuously improve and enhance the performance and capabilities of
its product lines, EMC periodically releases revisions of its hardware and software. Therefore,
some functions may not be supported by all revisions of the software or hardware currently in
use. For the most up-to-date information on product features, refer to the product release
notes.
If a product does not function properly or does not function as described in this document,
please contact your EMC representative.
Audience This guide is part of the EMC NetWorker Module for Microsoft Applications
documentation set. It is intended for use by system administrators, during
installation and setup of the product.
Readers should be familiar with the following technologies used in backup and
recovery:
◆ EMC NetWorker software
◆ EMC NetWorker Snapshot management
◆ Microsoft Volume Shadow Copy Service (VSS) technology
◆ Storage subsystems, such as EMC CLARiiON or Symmetrix, if used
Related Related documents include:

documentation
◆ EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Administration
Guide
◆ EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Release Notes
◆ EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Applications
Technical Notes for SharePoint and Exchange
◆ NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing
Proxy Node Backups 2.2 SP1 Technical Notes
◆ NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing
Proxy Node Backups 2.2 SP1 Technical Notes
◆ EMC NetWorker Release 7.5.x Multiplatform Version Administration Guide
◆ EMC NetWorker Release 7.5.x Multiplatform Version Installation Guide
◆ EMC NetWorker Release 7.5.x Multiplatform Version Release Notes
◆ EMC Information Protection Software Compatibility Guide
Preface
◆ EMC NetWorker License Manager Seventh Edition Installation and Administration

Guide
◆ EMC Solutions Enabler Symmetrix CLI Version 6.3 Quick Reference
Conventions used in EMC uses the following conventions for special notices.
this document
Note: A note presents information that is important, but not hazard-related.
! CAUTION
A caution contains information essential to avoid data loss or damage to the system
or equipment.
Typographical conventions
EMC uses the following type style conventions in this document:
Normal Used in running (nonprocedural) text for:
• Names of interface elements (such as names of windows, dialog boxes, buttons,
fields, and menus)
• Names of resources, attributes, pools, Boolean expressions, buttons, DQL
statements, keywords, clauses, environment variables, filenames, functions,
utilities
• URLs, pathnames, filenames, directory names, computer names, links, groups,
service keys, file systems, notifications
Bold: Used in running (nonprocedural) text for:
• Names of commands, daemons, options, programs, processes, services,
applications, utilities, kernels, notifications, system call, man pages
Used in procedures for:
• Names of interface elements (such as names of windows, dialog boxes, buttons,
fields, and menus)
• What user specifically selects, clicks, presses, or types
Italic: Used in all text (including procedures) for:
• Full titles of publications referenced in text
• Emphasis (for example a new term)
• Variables
Courier: Used for:
• System output, such as an error message or script
• URLs, complete paths, filenames, prompts, and syntax when shown outside of
running text
Courier bold: Used for:
• Specific user input (such as commands)
Courier italic: Used in procedures for:
• Variables on command line
• User input variables
<> Angle brackets enclose parameter or variable values supplied by the user
[] Square brackets enclose optional values
| Vertical bar indicates alternate selections - the bar means “or”
{} Braces indicate content that you must specify (that is, x or y or z)
... Ellipses indicate nonessential information omitted from the example
Preface
Where to get help EMC support, product, and licensing information can be obtained as follows.
Product information — For documentation, release notes, software updates, or for
information about EMC products, licensing, and service, go to the EMC Powerlink
website (registration required) at:
http://Powerlink.EMC.com
Technical support — For technical support, go to EMC Customer Service on
Powerlink. To open a service request through Powerlink, you must have a valid
support agreement. Please contact your EMC sales representative for details about
obtaining a valid support agreement or to answer any questions about your account.
Your comments Your suggestions will help us continue to improve the accuracy, organization, and
overall quality of the user publications. Please send your opinion of this document to:
techpubcomments@EMC.com
Preface
1
Invisible Body Tag
Preinstallation
information
This chapter includes the following sections:

◆ Preinstallation requirements ....................................................................................... 12
◆ Preinstallation checklist overview .............................................................................. 15
◆ Patches and hotfixes checklist ..................................................................................... 15
◆ Generic checklist............................................................................................................ 21
◆ CLARiiON checklist ..................................................................................................... 24
◆ Microsoft SharePoint checklist .................................................................................... 26
◆ Microsoft Exchange checklist ...................................................................................... 27
◆ Supported configurations ............................................................................................ 29
Preinstallation information 11
Preinstallation information
Preinstallation requirements
This section describes the preinstallation requirements for NetWorker Module for
Microsoft Applications (NMM) 2.2 SP1. You must review and adhere to the checks
and requirements described in this section thoroughly before attempting a NMM
installation. Failure to adhere to these checks and requirements will result in failure
to successfully protect the application and will require significant effort to
troubleshoot and resolve.
License information
The following license information is required after the installation:
◆ NMM temporary evaluation enabler
◆ EMC® NetWorker® base enabler
◆ NMM license add-on enabler
The NMM software requires a specific license: NetWorker Module for Microsoft
Applications. This license must be installed on the NetWorker Server.
◆ NetWorker Client enabler
Although the NetWorker Client is included with the NMM software, ensure to
purchase the NetWorker Client enabler.
Chapter 4, “Licensing and Enabling the Software,” provides more information on
enablers and licensing.
Privileged user-level access

As NMM requires access to protected data and system files, ensure that all users who
run or configure NMM backups and recoveries have the appropriate level of
privileges for all resources that they must access.
Table 1 on page 12 describes the required privilege levels.
Table 1 Access privileges needed for NMM (page 1 of 2)
Resource Privileges needed
NetWorker Server • NetWorker Administrator

or
• NetWorker Backup Operator
NetWorker Module for Microsoft • Windows Administrator

Applications client machine or
• Windows Backup Operator
All applications protected by NMM such • Windows Administrator

as:
• Windows Server
• Microsoft Data Protection Manager
• Microsoft Office SharePoint Server
• Microsoft SQL Server
• Microsoft Exchange Server
• Microsoft Hyper-V Server
Table 1 Access privileges needed for NMM (page 2 of 2)
Resource Privileges needed
Microsoft Office SharePoint Server (for • Windows Administrator

granular backup and recovery) • For only Microsoft Office SharePoint Server granular backup:
• An account that has full administrative privileges in
SharePoint farm or an install account used while creating the
SharePoint farm.
• The NetWorker SharePoint Service credentials specified in
the NetWorker SharePoint Service Configuration dialog box
must match the user and password credentials used for
SharePoint Server administration. If proper credentials are not
specified then the backup of SharePoint data fails. “Match
NetWorker SharePoint Service credentials with credentials of
SharePoint Server administrator” on page 76 provides details.
• A service account for each web application that needs to be
backed up.
Network domain Windows Domain Administrator
Storage node servers Windows Administrator
Adding Exchange Server 2007 credentials

You must first install Exchange and then NMM. If you have installed Exchange
Server 2007 after installing NMM, then ensure that NMM is reinstalled.
During the NMM installation, add Exchange credentials. “Installing NMM” on
page 34 provides more information about initial setup of Exchange credentials
during NMM installation.
The EMC Information Protection Software Compatibility Guide provides more
information on the supported hardware, software, and operating systems for the
NetWorker Module for Microsoft Applications software.
Hardware requirements
You require the following hardware before the installation:
◆ CPU: 2.0 GHz
◆ Physical memory: 1 GB
◆ Host architecture: x86 and x64 systems only
Software requirements
! CAUTION
To avoid potential data loss, do not install or use the NetWorker Module for
Microsoft Applications with other vendor’s VSS Requestor backup solutions. Data
loss may occur if other VSS Requestor backup solutions delete shadowcopies
created by the NetWorker Module for Microsoft Applications. Additionally,
restoring an application by using another vendor’s VSS Requestor backup
solution may prevent the same application from being restored with the
NetWorker Module for Microsoft Applications.
Preinstallation requirements 13
Microsoft SQL and SharePoint VSS Writers

If NMM is installed on a Microsoft Office SharePoint Server, ensure that the
following Windows services have the startup type as Automatic and are running:
◆ SQL Server VSS Writer
◆ Windows SharePoint Services VSS Writer
If NMM is installed on a Microsoft SQL Server, ensure that:
◆ The SQL Server VSS Writer service has the startup type as Automatic.
◆ The SQL Server VSS Writer service is running.
Installation services
When NMM is installed, the <Drive>:\Program File\Legato\nsr directory is created
by default. But you can select a location other than the default one during installation.
Table 2 on page 14 lists the installation services for the NetWorker software, and
EMC PowerSnapTM and Replication Manager services.
Table 2 Installation services
Service names Service nicknames

(in service control manager) (use with the ‘net start’ command) Process names
NetWorker Remote Exec nsrexecd nsrexecd.exe
NetWorker PowerSnap Service nsrpsd nsrpsd.exe
Replication Manager Client for RMAgentPS rmagentps irccd.exe
Preinstallation checklist overview

Preinstallation checklists provide a quick reference for you to implement the
accounts, permissions, and system requirements required before installing NMM 2.2
SP1.
The following preinstallation checklists are provided in this section. As each checklist
is completed, indicate it by using the checklist provided in Table 3 on page 15.
Table 3 Checklist overview
Mark
complete Checklist
“Patches and hotfixes checklist” on page 15, which contains these sections:
• “Patch for deduplication backup of NMM Client if using NetWorker 7.5.1.3 or later server” on
page 15
• “Microsoft hotfixes required for NMM 2.2 SP1” on page 16
“Generic checklist” on page 21
“CLARiiON checklist” on page 24
“Microsoft SharePoint checklist” on page 26
“Microsoft Exchange checklist” on page 27
Patches and hotfixes checklist

This section describes that various patches and fixes that you must install for NMM
to function correctly:
◆ “Patch for deduplication backup of NMM Client if using NetWorker 7.5.1.3 or
later server” on page 15
◆ “Microsoft hotfixes required for NMM 2.2 SP1” on page 16
Patch for deduplication backup of NMM Client if using NetWorker 7.5.1.3 or later server
Ensure to install the patch, that is available at
ftp://ftp.legato.com/pub/NetWorker/Updates/NMM/NMM22/.
Without this patch, deduplication backup failure is observed when backups are
performed by using a NetWorker 7.5.1 server and the following error message
appears:
“50415:nsrsnap_vss_save:nsrsnap_vss_save: unable to extract key
and value for argument '-A De-duplication'. Expecting '-A
key=value'in this format.
69227:nsrsnap_vss_save:nsrsnap_vss_save: Failed to set value
for a key=De-duplication”.
Preinstallation checklist overview 15

Microsoft hotfixes required for NMM 2.2 SP1

In addition to the specific Microsoft Windows updates mentioned in this guide:
1. Keep NMM Client machine current with Microsoft Windows updates for the
operating system.
2. Keep NMM Client machine current with updates and hotfixes for each installed
Microsoft application protected by NMM.
3. Download the hotfixes from the Microsoft website.
Note: The EMC Module for Microsoft Applications Release 2.2 SP1 Release Notes also contains this
list of Microsoft hotfixes that are required for NMM to work correctly.
Table 4 Hotfixes required for NMM 2.2 SP1 (page 1 of 5)
Windows Windows Windows Windows Included

KnowledgeBase 2003 2003 2008 2008 in service
article ID (X32) (X64) (X32) (X64) Applies to pack Description
Volume shadowcopy service (VSS)
KB940349 X X VSS NA VSS update rollup package for Windows

Server 2003 to resolve some VSS
snapshot issues.
KB951568 X VSS NA VSS-based backup operations may fail if

VSS tracing is enabled on a Windows
Server 2003-based computer that has
hotfix 940349 applied.
KB949391 X X VSS NA When VSS tries to delete hardware

support snapshots on a computer that is
running Windows Server 2003 or an x64
version of Windows XP, the operation may
fail.
KB943545 X X VSS NA The following error message is displayed

by the
IOCTL_SCSI_GET_INQUIRY_DATA
operation on a Windows Server
2003-based computer:
"STATUS_INVALID_DEVICE_REQ
UEST"

KB939315 X X VSS NA
Note: Only apply this hotfix if needed.
When you shut down a computer that is

running the Microsoft Storport storage
driver (Storport.sys) on Windows Server
2003 Service Pack 2 (SP2), you may
receive a “Stop 0x0000009C” error
message that resembles the following:
“*** STOP: 0x0000009C
(parameter1, parameter2,
parameter3, parameter4)
MACHINE_CHECK_EXCEPTION”
This error occurs because of a problem in
the version of Storport that is included in
Windows Server 2003 SP2 and in update
932755. These versions of Storport
incorrectly forward interrupts to the
miniport after the PCI bus is in the “device
off” state (D3).
Microsoft Exchange
KB927673 X X Exchange NA Windows Server 2003 Post-Service Pack 1

Server 2007 COM+ 1.5 Hotfix Rollup Package 11 for
Service Pack Exchange 2007 CCR environments.
2
KB971534 X X Exchange NA Update Rollup 1.

Server 2007
Service Pack
2
KB936008 X X SP1, SP2, R2, Volume GUIDs become invalid in Windows

and R2 SP2 Server 2003 when the disk layout changes
outside the context of the Virtual Disk
Service and of the APIs.
Storage arrays
KB908980 X X EMC NA For Windows Server 2003 configurations

CLARiiON® running STORport drivers with CLARiiON
Storport storage arrays.
Drivers
KB916048 X X EMC NA Hotfix for any host running Microsoft

Symmetrix® Windows Server 2003/SP1 or Microsoft
/CLARiiON Windows Server 2003/R2 and connected
to Symmetrix or CLARiiON storage.
KB903081 X X Symmetrix NA Hotfix

Storport WindowsServer2003-KB903081-x86-ENU.
Drivers exe available for Windows Server 2003
configurations running STORport drivers
with Symmetrix storage arrays.
EMC Replication Manager SP1
Patches and hotfixes checklist 17


KB898790 X X RM SP1 NA Microsoft hotfix

WindowsServer2003-KB898790-x86-ENU.
exe for Replication Manager SP1.
This hotfix is required because the volume
mount points on disks in a server cluster
may intermittently become unavailable
after you install Windows Server 2003
Service Pack 1.

exe for Replication Manager SP1.
This hotfix is required because a Windows
Server 2003-based computer stops
responding when you perform a backup of
an Exchange Server database.

exe for Replication Manager SP1. This
update fixes various Volume Shadow Copy
Service issues in Windows Server 2003.
Server cluster
KB898790 X Microsoft NA Volume mount points on disks in a server

Windows cluster may intermittently become
Server 2003, unavailable after you install Windows
Enterprise x64 Server 2003 Service Pack 1.
edition or
Windows
Server 2003
Service Pack
1 (SP1) on a
server cluster
Microsoft SQL Server
KB934396 X X X X Microsoft SQL NA • Install Microsoft SQL hotfix KB934396

Server 2005 on the client to successfully backup and
restore SQL Server 2005 data. To apply
this hotfix, SQL Server 2005 Service
Pack 2 must be installed.
• Installation of Microsoft SQL Server
2005 Service Pack 3 includes this
hotfix.
Microsoft SharePoint

KB971538 X Microsoft NA • If you have already installed hotfix

SharePoint 961755, then install hotfix 971538 also.
2007; • If you have not installed hotfix 961755,
SharePoint then install only hotfix 971538.
Services 3.0 • Cumulative update packages for
Service Pack Windows SharePoint Services 3.0
2 contain hotfixes for the Windows
SharePoint Services 3.0 issues that
were fixed since the release of
Windows SharePoint Services 3.0. This
build of the cumulative update package
is also known as build 12.0.6510.5001.
• Go to the Microsoft support website and
search for KB971538 - “Description of
the Windows SharePoint Services 3.0
Cumulative Update Server Hotfix
Package (WSS server-package): June
30, 2009” and follow the directions
provided on the website.
Microsoft Hyper-V
KB950050 X X Microsoft NA If this update is not installed prior to

Hyper-V recovery, the system will not come back
after recovery of SYSTEM
COMPONENTS.
KB967560 X X Microsoft SP2 When a scheduled save is started, the

Hyper-V following error message might appear in
the event viewer:
“ASR Error: Failed to
collect critical
information for ASR
Backup.”
The reason this message appears is that
ASR is unable to obtain disk information for
device 3 (Win32 error code 0x2).
KB951308 X X Microsoft SP2 Apply to each cluster node for cluster

Hyper-V deployment. This provides increased
SP2 functionality and virtual machine control in
the Windows Server 2008 Failover Cluster
Management console for the Hyper-V role.
KB956697 X Microsoft SP2 When the Hyper-V writer seems to be

Hyper-V missing due to the presence of corrupt
SP2 virtual machine configuration files in the
Hyper-V Server.
KB958184 X Microsoft SP2 When virtual machine files are saved on a

Hyper-V volume mounted on a failover cluster using
SP2 a volume GUID.
Patches and hotfixes checklist 19


KB959962 X Microsoft SP2 Hyper-V writer update if the backup fails for
Hyper-V one of the following reasons:
SP2 • Retryable VSS error.
• VSS application writer provider is
moving to a bad state.
• If recovery of a virtual machine is failing
because it has legacy network adaptors
attached.
After performing this update, you must
update the integration services on each of
the virtual machines running on the server
by inserting the Integration Services Disk
from the Action menu in the virtual
machine's management console. This will
require a restart of virtual machine.
KB960038 X X Microsoft SP2 Apply to all Hyper-V hosts. This update for
Hyper-V Windows Server 2008 fixes a crash of the
SP2 Hyper-V host server, which you might
experience when backups are made by
using the Hyper-V writer.
KB959978 X X Microsoft SP2 Apply when you back up a Windows

Hyper-V Server 2003-based virtual machine on a
SP2 Windows Server 2008 Hyper-V-based
computer and get the following message:
“GetWriterStatus FAILED
for Selected writer
[Microsoft Hyper-V VSS
Writer], writer is in
state [9]
[VSS_WS_FAILED_AT_FREEZE]”
Data Protection Manager
KB959605 X X Microsoft SP2 • DPM support in NMM requires the

DPM installation of System Center Data
Protection Manager 2007 Service Pack
1. Otherwise, replicas may not
successfully recover.
• The System Center Data Protection
Manager 2007 Service Pack 1
download is available from Microsoft
website.
Generic checklist
Table 5 on page 21 provides the generic checklist for NMM 2.2 SP1. Review the
following checklist before installing NMM 2.2 SP1.
Table 5 Generic checklist (page 1 of 3)
Check to see if: Details
Supported operating system version and service pack level are Supported:
correct. • Windows 2003 SP2
• Windows 2003 R2 SP2
• Windows 2008
• Windows 2008 SP2
Not supported:
• Windows 2003 SP1
• Windows Vista
• Windows 7
• Windows 2000
• Windows XP
• Windows 2008 R2
Required hotfixes are installed. Review the hotfixes mentioned in “Patches and hotfixes checklist” on page 15:
Other backup software is installed and running. If yes, either uninstall them or stop their execution.
Note: Look at Add or Remove Program in Control panel and make

sure that no other backup application is installed. Also, check with
the backup administrator that this machine is not being backed up
with some other backup software, excluding Microsoft DPM 2007
SP1 software.
NetWorker Client, PowerSnap, or Replication Manager is installed. If yes, remove any that is installed.
Note: NMM can be installed on NetWorker storage node in case of

proxy.
Firewall is enabled. • If not enabled, pass.

• If enabled, run the next check.
There are open ports in the firewall to allow NMM to communicate. If the firewall is configured for NMM, then pass.
IPv6 status. If IPv6 is enabled, NMM will not work properly.
Host can connect with NetWorker server, proxy node, or storage If yes, pass.Otherwise, fail.
node hosts and this host is reachable from other hosts.
In case of cluster, check if nodes of virtual server are able to pass
this test and the virtual server is reachable.
DNS lookup of host — Host is reachable and can be looked up in If yes, pass. Otherwise, fail.
DNS, is properly configured on the network, and there are no IP
conflicts.
Both forward and reverse DNS lookup should pass.
In case of cluster, check if nodes of virtual server are able to pass
this test and the virtual server is reachable.
Dual-NIC environment. Only Exchange is supported in dual-NIC scenario.

Section “Setting up dual-NIC for Exchange backup” in the EMC NetWorker
Module for Microsoft Applications Release 2.2 SP1 Administration Guide
provides details.
Generic checklist 21
VSS Admin List volume — This gives a list of volumes that can be The saveset should only contain these volumes.
used for snapshots.
If the volume being backed up is one of the list.
Any of the disks are RAW. NMM does not support RAW disks.
Check for writer stability. Ensure that all writers on the system are in stable state by using the command:
vssadmin list writers
Version of VSS Hardware Provider currently installed and running. VSS hardware provider version 4.1.2.1 and Solution Enabler version 7.1.0.42
If there are providers other than Microsoft provider, they will be used for the
volumes they are associated with.
For Software Provider, there is enough free space to create shadow Ensure that a maximum area limit has not been set for shadow copies.
copies for each volume. The following command lists the shadow copy storage association for each
volume:
vssadmin list shadowstorage
After running this command, check that the value “Maximum Shadow Copy
Storage space:” is set to “UNBOUNDED” for the volume chosen for backup.
After installing NMM, Replication Manager, and PowerSnap If yes, pass.

services, Microsoft SharePoint Service Controller (granular), If no, start the services.
Replication Manager Exchange interface Service, the various “Installation services” on page 14 and “Verifying the installation” on page 37
services are up and running. provides details.
Correct versions of NetWorker Server, NetWorker Storage Node, • NetWorker Server and Storage Node: version 7.3.3 and later
and other applications are installed. • SharePoint granular: 7.4.3 and later
• NetWorker Server or NetWorker storage node OS Linux: 7.4.3 and later
• Deduplication: NetWorker 7.5 SP1 and “Patch for deduplication backup of
NMM Client if using NetWorker 7.5.1.3 or later server” on page 15
• Avamar Axiom 4.0.2 and later
• Exchange incremental backup: NetWorker Server 7.5 SP1 and later
• NetWorker cloning and staging support: NetWorker Server 7.5. and later
Note: NetWorker Server and storage node version 7.5. SP1 and cumulative
update 3 and later, will support all features for NMM.
Correct licenses are installed on NetWorker Server. If yes, pass. Otherwise, fail.
BitLocker encryption is enabled. Disable BitLocker encryption because Bitlocker encryption is not supported.
Group inactivity timeout is set to 0. Set group inactivity time-out to 0.
Client retries is set to 0 in group properties. Set client retries to 0.
Software and Hardware Providers are being used at the same time. Use either software provider or Hardware Provider. Using both will cause backup
to fail.
Install path is English only. Only English path is supported.
Application host and proxy host have same OS, same service pack, If application host and proxy host do not match backups would not work fine
same platform, and similar patch levelI.
Cluster type and cluster requirements. When Hardware Provider is used — If MSDTC is required or not:
• SQL 2005 on Windows 2003 Cluster: Yes
• SQL 2005 on Windows 2008 Cluster: No
• SQL 2008 on Windows 2008 Cluster: Yes
Windows 2003 (32-bit and 64-bit) MSCS cluster:
• SP1 and R2 require Microsoft hotfixes described in KnowledgeBase articles
KB903650 and KB919117.
• SP2 and R2 SP2 require Microsoft hotfix described in KnowledgeBase article
KB919117.
Note: MSDTC is not required for Window 2008 (Exchange). Dynamic disks are
not supported in an MSCS cluster.
The appropriate snapshot software for the array is installed and If yes, pass. Otherwise, fail.
licensed:
• For EMC CLARiiON:
— EMC SnapViewTM Clone
— EMC SnapView Snapshots
• For EMC Symmetrix DMXTM:
— EMC TimeFinder®/Mirror
— EMC TimeFinder/Snap
“Configurations specific to Symmetrix” on page 63 provides details.
• For EMC Celerra: Celerra® Snapshots
• For Dell EqualLogic PS Series: EqualLogic Snapshots
• For IBM System Storage DS6000/DS8000: IBM FlashCopy
The appropriate VSS Hardware Provider on the Windows Server If yes, pass. Otherwise, fail.
hosting the application is installed:
• EMC VSS Common Provider for EMC Symmetrix and CLARiiON
arrays:
• The EMC VSS Common Provider is available on Powerlink at
http://Powerlink.EMC.com.
• The release notes for the EMC VSS Common Provider can be
found on Powerlink at http://Powerlink.EMC.com.
• EMC Celerra VSS Provider for Celerra arrays — The EMC
Celerra VSS Provider is available on Powerlink at
http://Powerlink.EMC.com.
• Dell/EqualLogic Integration ToolKit for EqualLogic PS Series
arrays — The Dell documentation provides information on access
and support.
• IBM DS6000 and DS8000 arrays — The IBM System Storage DS
Open API Package is available at
http://www-1.ibm.com/support/docview.wss?uid=ssg1S4000372
&rs=555.
• Windows Unified Data Storage Server (WUDSS) — The
Microsoft documentation provides information on access and
support.
Generic checklist 23
CLARiiON checklist
Table 6 on page 24 provides the checklist for CLARiiON for NMM 2.2 SP1. Review
the following checklist before installing NMM 2.2 SP1.
Table 6 CLARiiON checklist (page 1 of 3)
Client and proxy base-level software requirements
• VSS Hardware Provider is installed and meets an VSS Hardware Provider 4.1.2.1
exact or minimum revision level. Solution Enabler version 7.1.0.42
• The version of Solutions Enabler is the one that was
provided with the VSS Hardware Provider version.
The target CLARiiON IP addresses are in the SYMAPI If yes, pass. Otherwise, fail.
authority listing.
Note: “Update the SYMCFG authorization list” on page 62, step 3 provides details about
how to verify that the SYMCFG authorization list has been updated correctly.
EMC PowerPath® is installed. If yes, pass. Otherwise, fail.
Note: PowerPath is not be required for EMC iSCSI on Windows 2008. Also, PowerPath is
not supported in VMware — VMware has its own path management capability.
The PowerPath version installed is correct. • For Windows 2003 (and R2) /SP2: Minimum 5.01
• For Windows 2008: minimum 5.1.2 (only applies if PowerPath is installed)
Note: On ESX server, PowerPath is not required. NaviAgent is recommended on both host
and guest.
The multipathing feature is installed on Windows Server • If multipathing is enabled on Windows 2008, PowerPath is not a mandatory requirement.
2008. • EMC FLARE® 26 required
• AULA mode required.
The iSCSI Initiator version installed is correct. • Version 2.06, 2.07, or 2.08 is required.
• There is no mention of iSCSI in the Provider Support Matrix:
• Replication Manager supports Matrix and supports iSCSI for CLARiiON with the
iSCSI initiator.
• PowerPath can handle both SAN and iSCSI, but iSCSI must be specified as part of
the PowerPath install.
• IP address of CLARiiON must be mentioned in iSCSI Initiator.
Host must be visible on CLARiiON.
The HBA driver version installed is correct. Must be a STORport driver.
Note: EMC requires “EMC certified” drivers for both Emules and Qlogic Fiber channel cards.
The EMC support matrix carries only the most current and previous version.
The appropriate Windows VSS/VDS hotfixes are If yes, pass. Otherwise, fail.
installed.
In VMware environment, on ESX server, NavihostAgent If yes, pass. Otherwise, fail.

is installed.
In virtual machine environment, LUNs are assigned as If yes, pass. Otherwise, fail.
raw mapping device from the ESX server to the guest
virtual machine.
In virtual machine environment, the authorization has If yes, pass. Otherwise, fail.
been provided by using the following commands in the
guest virtual machine:
C:\Program Files\EMC\SYMCLI\shlib>
vicfg setup [-u
<username> -p <password> -s
<esx_network_address> [-force]]
where, username and password are the credentials of
ESX.
Client or proxy resident EMC Navisphere software for CLARiiON configurations
NaviCLI and NaviSecCLI are installed and their location If installed and in location is in system environment variable, then pass. Otherwise, fail.
are in system environment variable.
Admsnap is installed and its location is in system If installed and in location is in system environment variable, then pass. Otherwise, fail.
environment variable.
The Admsnap version installed is correct. • For Windows 2003 with FLARE 19: minimum Admsnap 2.9.0.0.7
• For Windows 2003 with FLARE 20: minimum Admsnap 2.9.0.0.7
• For Windows 2003 and 2008 FLARE 28: minimum Admsnap 2.28.0.0.2
The SPA and SPB belong to the same CLARiiON. If yes, pass. Otherwise, fail.
The FLARE operating environment version installed on If the release of the CLARiiON is in the list, then pass. Otherwise, fail.
the CLARiiON arrays is correct.
The following CLARiiON arrays running FLARE are
supported: 19, 22, 24, 26, or 28
EMC Access Logix™ is active. If yes, pass. Otherwise, fail.
SNAPVIEW enabler installed. If enabler is present, pass. Otherwise, fail.
CLARiiON setup
The host's NaviCLI version is compatible with CLARiiON • If host NaviCLI version is the same or higher than CLARiiON release version, pass.
array release. • If host NaviCLI version is lower than CLARiiON release version, fail.
There are LUNs in the reserved LUN pool. If there are LUNs in the reserved LUN pool, pass. Otherwise, fail.
Note: Ensure that the number of LUNs in the LUN pool are sufficient to cover the number of
snapshots at any given time.
The array is capable of creating clones. If clones are enabled, pass. Otherwise, fail.
There are clone private LUNs. If clones are private clones, pass. Otherwise, fail.
The failover mode settings for the CLARiiON are set: If yes, pass. Otherwise, fail.
• The CLARiiON failover mode or trespassing must be
set to 1.
• For iSCSI, the connectivity is 4.
The specified username and password works for that If yes, pass. Otherwise, fail.
CLARiiON.
CLARiiON checklist 25
The CLARiiON using NaviCLI (classic) interface to see if • If there are privileged users and the system@<host_Id> is on the list, then pass.
"system@<host_id>” is in the “privileged user” list on the • If there are privileged users and system@<hostId> is not in the list, then fail.
CLARiiON. • If the privileged user list was empty, then unknown.
The Solutions Enabler is licensed.
Saveset has one partition per LUN. If yes, pass. Otherwise, fail.
Is the base ESX registered on the guest virtual machine The authorization must be provided by using the following commands in the guest virtual
of both proxy and application host. machine:
C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u
<username> -p <password> -s <esx_network_address>
[-force]]
where, username and password are the credentials of ESX.
Orphaned snapshot or snap session for particular storage If yes, then delete them.
group is present.
Host is registered with both SPA and SPB. If yes, pass. Otherwise, fail.
At least one CLARiiON LUN is visible to the proxy. If yes, pass. Otherwise, fail.
The appropriate host-based EMC storage software, such If yes, pass. Otherwise, fail.
as PowerPath and Navisphere for EMC CLARiiON
host-based utilities, as required by the supporting array
and customer environment are installed.
Microsoft SharePoint checklist

Table 7 on page 26 provides the checklist for SharePoint for NMM 2.2 SP1. Review
the following checklist before installing NMM 2.2 SP1.
Table 7 SharePoint checklist (page 1 of 2)
• Microsoft Office SharePoint Server 2007 (for x86 and x64) Standard or If yes, pass. Otherwise, fail.
Enterprise editions with SP2 or later and Windows SharePoint Services 3.0 with
SP2.
• Microsoft SharePoint Server 2003 (for x86) Standard or Enterprise editions with
SP2 and Windows SharePoint Services 2.0 with SP2.
Cluster is installed, then check the state of the cluster service for SQL Virtual For WSFC or MSCS, pass if cluster in healthy.
Server.
KB971538 for Microsoft Office SharePoint Server 2007 (for x86 and x64) Standard If yes, pass. Otherwise, fail.
or Enterprise editions with SP2 is installed.
All essential SharePoint services are up and running: If yes, pass. Otherwise, fail.
• SQL Server Writer (running and set to automatic) for SQL databases
• SharePoint Services Write (running and set to automatic) for SharePoint 2007
• SharePoint Search Writer for SharePoint 2007 Search — If not running, then it
is a warning to check if role is enabled. Ensure that the services are started.
• Microsoft Office Server Search Writer for Microsoft Office Server search — If
not running, then it is a warning to check if role is enabled. Ensure that the
services are started.
NMM Client is installed on all machines participating in a farm in web front-end for If yes, pass. Otherwise, fail.
NMM granular backup.
Table 7 SharePoint checklist (page 2 of 2)
SharePoint VSS writer is registered on at least one web front-end within a farm. If yes, pass. If no, run stsadm -o registerwsswriter. Else, it is a
warning.
Savesets contain non-ASCII character. For granular backup to work correctly, set I18N:mode = utf8path.
Either SQL Server Writer or MSDE Writer-SQL2000 is enabled for SharePoint If yes, pass. Otherwise, fail.
Server 2003.
NMM is installed on a Microsoft Office SharePoint Server and if these Windows If yes, pass. Otherwise, fail.
services are running and are set to automatic:
• SQL Server VSS Writer
• Windows SharePoint Services VSS Writer. This will only run if Windows
SharePoint Services Writer is registered.
The SharePoint environment is stable or not using the SharePoint Server If yes, pass. Otherwise, fail.
Administration tool.
Staging area space requirements are fulfilled. If requirements are fulfilled, pass if.
• For granular backup — NMM performs the backup process in
stages, so that you do not need as much free space for the
backup as the data in the SharePoint databases. The section
“Staging requirements in SharePoint backup“ in the EMC
NetWorker Module for Microsoft Applications Release 2.2 SP1
Administration Guide contains more details.
• For optimized backup — The number of processors on web
front-end must be the size of largest site-collection.
SharePoint Shared Service Provider (SSP) is properly configured or not. If yes, pass. Otherwise, fail.
Upgrading from SharePoint 2003 to SharePoint 2007. Check the configuration in If yes, pass. Otherwise, fail.
SharePoint Server with WSS SP2 stsadm:
X:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\12\BIN\STSADM.EXE" -o
where X is the drive letter where SharePoint is installed.
Version of SQL Server SQL 2005 SP3. If yes, pass. Otherwise, fail.
NetWorker SharePoint Service Controller is started. If yes, pass. Otherwise, fail.
Privileges of NetWorker SharePoint Service Controller is set correctly. If NetWorker SharePoint Controller Service has SharePoint
Server administrator privileges or SharePoint install account,
pass.
Microsoft Exchange checklist

Table 8 on page 28 provides the checklist for Exchange for NMM 2.2 SP1. Review the
following checklist before installing NMM 2.2 SP1.
Microsoft Exchange checklist 27

Table 8 Exchange checklist
• Microsoft Exchange Server 2003 (for x86) Standard and Enterprise editions with SP2 or later is If yes, pass. Otherwise, fail.
installed.
• Microsoft Exchange Server 2007 (for x64) Standard and Enterprise Edition with SPI or later is
installed.
Cluster is installed, then check the state of the cluster service. For WSFC or MSCS, pass if cluster in healthy.
Message API (MAPI) and Collaboration Data Object (CDO) kits are installed and are version 1.2.1 or If yes, pass. Otherwise, fail.
later for Exchange 2007.
Credentials of user of Exchange Server are correct. If appropriate privileges are present, pass.
Exchange server is a part of domain. If yes, pass. Otherwise, fail.
Essential Exchange Services are up and running: If yes, pass. Otherwise, fail.
• Microsoft Exchange Information Store
• Microsoft Exchange Attendant
• Microsoft Exchange Resource Agent
• Message Transfer Agent (MTA)
• Microsoft Replication Service for cluster environment
Following conditions are met: If yes, pass. Otherwise, fail.

• System path and the log path are in the same location.
• In normal backup of Exchange, the database files and transaction log files are in different
volumes.
• In hardware scenario, the system files and log files are in different LUNs.
The writer for both the active node and passive node in the CCR environment is stable. If yes, pass. Otherwise, fail.
Exchange storage groups locale should be the same as the Exchange server locale. If yes, pass. Otherwise, fail.
The saveset contains only Exchange writer and that no other writer is included during backup. If yes, pass. Otherwise, fail.
The group are properly mounted, else the whole backup will fail. If yes, pass. Otherwise, fail.
The CCR of active node and passive node is consistent, that is, the health of CCR before taking If yes, pass. Otherwise, fail.
backup.
Backup is grouped with not more than ten storage groups at a time, if If yes, pass. Otherwise, fail.
NSR_EXCHANGE_LIMIT_SG=yes. Otherwise, the maximum limit is governed by a limit of 64
snapshots, which means a maximum of 32 storage groups.
Exchange management tools are installed on proxy client. If yes, pass. Otherwise, fail.
Supported configurations
This section describes the basic configurations in which the NMM is supported:
◆ “Simple LAN-based configuration” on page 29
◆ “LAN-based configuration with a proxy client” on page 30
◆ “LAN-free configuration” on page 31
Note: Although the version of NetWorker Storage Node in Figure 1 on page 30, Figure 2 on
page 31, and Figure 3 on page 32 is given as 7.3.x, use NetWorker Storage Node release 7.3.3 or
later.
Simple LAN-based configuration

Figure 1 on page 30 shows a simple LAN-based configuration with a storage area
network. In a LAN-based configuration, the production data is stored on a storage
area network (SAN) or direct-attached storage (DAS). The data path to the
NetWorker storage node devices is over a LAN. The application server that is being
protected has the NMM installed.
The data moves as follows:
1. The NetWorker Server, which must be release 7.3.3 or later, initiates the process
by contacting the application server where the NMM software is installed.
2. The application server with the NMM software creates a snapshot of the data on
the storage volume.
Note: In Figure 1 on page 30, snapshots are represented by S1 through S5.
3. The application server with the NMM software uses a snapshot in primary
storage to transfer the data over the LAN and into a conventional backup
medium such as a file type disk, advanced file type disk, or tape.
Supported configurations 29
NetWorker
Server 7.3.3 or later
LAN
Application server
NetWorker Module for
Microsoft Applications
NetWorker Traditional
SAN Storage storage
Node 7.3.x
Primary storage S4
(For example, S5 S3
CLARiiON or Symmetrix)
S1 S2
GEN-000747
Figure 1 Simple LAN-based configuration
LAN-based configuration with a proxy client

Figure 2 on page 31 shows a LAN-based configuration with a storage area network
and a proxy client. Both the application server and the proxy client have the NMM
installed. Install the proxy client software by using the NMM software package.
Note: The application server and the proxy client must use the same version, NetWorker
Module for Microsoft Applications release 2.2 SP1. If NMM 2.2 SP1 is installed on either the
application server or the proxy client machine, then the other machine must also use NMM 2.2
SP1. Backup and recovery will fail if NMM 2.2 SP1 is used on one of these machines, and an
earlier version of NMM is used on the other.
A proxy client is a host that acts as a remote data mover (DM) when snapshots are
rolled over to a conventional backup medium. A proxy client frees resources on the
application server. When a backup operation uses a proxy client, it is known as a
serverless backup.
1. The NetWorker server initiates the process by contacting the application server
where the NMM software is installed.
the storage volume.
3. The snapshot is made visible to the proxy client.

4. The proxy client uses a snapshot in primary storage to transfer the data over the
LAN and into a conventional backup medium such as a file type disk, advanced
file type disk, or tape.
NetWorker Server
7.3.3 or later
LAN
Application server Proxy client

NetWorker Module for NetWorker Module for
Microsoft Applications Microsoft Applications
SAN
NetWorker Traditional
Storage storage
Primary storage S4 Node 7.3.x
(For example, S5 S3
S1 S2
GEN-000748
Figure 2 LAN-based configuration with a proxy client
LAN-free configuration
Figure 3 on page 32 shows a LAN-free configuration with a storage area network.
The NMM is installed on the application server. The proxy client is installed on the
NetWorker storage node.
You can set up a NetWorker storage node release 7.3.3 or later as a proxy client to
avoid the network traffic that is generated when a snapshot is rolled over to a
conventional backup medium. Network traffic is avoided because both the
conventional backup device and the snapshot are directly attached to the storage
node.
1. The NetWorker Server initiates the process by contacting the application server
where the NMM software is installed.
the storage volume.
3. The snapshot is made visible to the proxy client.
Supported configurations 31
4. The proxy client, in this case the storage node, uses a snapshot in primary storage
to transfer the data into a conventional backup medium such as a file type disk,
advanced file type disk, or tape.
The NetWorker Server and the application server communicate through the
LAN. However, the data itself is not transferred across the LAN because the
conventional backup medium is attached directly to the NetWorker storage node.
NetWorker Server
7.3.3 or later
LAN
Application server Proxy client

NetWorker Module for NetWorker Storage
Microsoft Applications Node 7.3.x
SAN
Traditional
Primary storage S4 storage
(For example, S5 S3
S1 S2
GEN-000750
Figure 3 LAN-free configuration
2
Installing the
Software

◆ Installing NMM ............................................................................................................. 34
◆ Installing NMM in a MSCS environment .................................................................. 36
◆ Installing NMM on Windows 2008 Server Core....................................................... 37
◆ Verifying the installation.............................................................................................. 37
◆ Maintaining the installation......................................................................................... 37
◆ Removing the software................................................................................................. 38
◆ Removing previous installation of Solutions Enabler ............................................. 39
◆ Upgrading the software ............................................................................................... 39
◆ Upgrading to NMM storage node .............................................................................. 39
◆ Installing Microsoft Office SharePoint Server service pack .................................... 40
Installing the Software 33

Installing the Software
Installing NMM
! CAUTION
Remove all previous installations of NetWorker before installing NMM, except if
you want to use the LAN-free configuration. In the LAN-free configuration, only
the NetWorker Storage Node should be installed.
To install the NMM software on a Microsoft Windows computer, complete the

following tasks:
◆ “Access the installation files” on page 34
◆ “Install the software” on page 34
Access the installation files

Access the installation files from a DVD or the EMC website.
From a DVD
To access the NMM software from a local DVD:
1. Log in as administrator or equivalent on the NetWorker Server.
2. Insert the NMM DVD into the DVD drive.
3. Run setup.exe directly from the DVD.
From the EMC website

To access the evaluation version of the NMM software from the EMC Support
website:
1. Go to http://Powerlink.EMC.com.
2. Select Support > Software Downloads and Licensing > Downloads J-O >
NetWorker Module.
3. In the table of NetWorker Module Software Downloads, click the NetWorker
Module for Microsoft Applications Release 2.2 SP1.
Install the software

Once you have accessed the NMM software files, you are ready to begin the
installation. The NetWorker Client is included with the NMM software, and you are
not required to install a NetWorker Client before installing the NMM software.
To install NMM:
1. Run the Setup program (setup.exe) to start the installation wizard.The Welcome
to NetWorker Module for Microsoft Applications Installation wizard appears.
2. Click Next. The Customer Information dialog box appears.
3. Type the name and organization information and click Next. The License
Agreement dialog box appears.
4. Read the license agreement. To accept, select the I accept the terms in the license
agreement option, and click Next. The Installation Location dialog box appears.
5. To choose an alternate location for the installation folder:
a. Click Change and then select a different installation location.

b. Click Next. The Windows Firewall dialog box appears.
6. Select either of these options:
• Configure the Windows Firewall. This option allows you to set greater
security. Ensure to set an exception for the NetWorker software, otherwise the
NetWorker software might not function properly.
or
• Do not configure the Windows Firewall. The Change Folder dialog box
appears.
7. Click Next.
8. Specify the alternate folder location and name, and then click OK. The
Replication Manager Client Setup dialog box appears.
9. For Control Port and Data Port:
• Specify two different port number values that will be used by the Replication
Manager Client service. For most installations, the values supplied will be
satisfactory.
! CAUTION
EMC Replication Manager is also sold as a separate product. If you have
purchased Replication Manager as a separate product, do not attempt to run
the product on the same system as NMM.
• You can change the Replication Manager port settings from the command line
after the installation is complete. “Changing Replication Manager port
settings” on page 75 provides more information.
Note: Occasionally, an error message is displayed that installation was unable to create
a Windows firewall exception for irccd.exe. “Windows firewall exception error for
irccd.exe” on page 78 provides steps to manually add the exception.
10. In the Ready to Install dialog box, click Next to start the NMM installation:
Note: The installation may take several minutes.
• If Microsoft Exchange Server is installed on the same installation machine, the

nwexinfo.exe is started at the end of the NMM installation.
In the nwexinfo dialog box:
a. Type the Exchange Server domain information (Domain, Username, and
Password).
b. Click OK.
• If Microsoft Office SharePoint Server 2007 host is installed on the same
installation machine, the nwmossinst.exe is started at the end of the NMM
installation.
In the NetWorker SharePoint Service Configuration dialog box:
a. Type the domain user name, password, temporary storage location, and
lock type to complete the configuration required to perform Microsoft
Office SharePoint Server 2007 granular backup and recovery.
Installing NMM 35
b. Click OK.
11. In the NetWorker Module for Microsoft Applications Setup Complete window,
click Finish to complete the installation and exit the installation wizard.
During the NMM installation:
• Replication Manager and PowerSnap services are installed along with the
NMM software.
• The Replication Manager, PowerSnap services, and the NMM software,
appear as separate entries under Add/Remove Programs in Microsoft
Windows Server 2003, or Programs and Features in Microsoft Windows
Server 2008.
12. Enable and register the NMM software. Chapter 4, “Licensing and Enabling the
Software,” provides detailed instructions.
13. Configure the setup according to instructions in Chapter 5, “Configuring the
Software,” provides detailed instructions.
Installing NMM in a MSCS environment

When installing the NMM software in a Microsoft Cluster Server (MSCS)
environment, if you plan to use CLARiiON or Symmetrix hardware with EMC VSS
Provider, ensure that first Microsoft Distributed Transaction Coordinator (MSDTC) is
installed and running before installing the EMC VSS Provider. The EMC VSS
Provider will install EMC Solutions Enabler, and Solutions Enabler requires that
MSDTC be running. The EMC Solutions Enabler Version 6.3 Installation Guide provides
details about installing and running Solutions Enabler.
Note: EMC Solutions Enabler will be present only when using EMC VSS Provider.
To install the NMM software in a MSCS environment:

1. Install the NMM software on the private disk of each physical node.
2. Configure each physical node as a client resource on the NetWorker Server.
3. In the Remote Access attribute of each virtual client resource, type the names of
the physical nodes.
4. Configure privileges for each physical node on the NetWorker Server:
c. In the Users attribute of the Administrators user group, add the following
values for each physical node in the cluster. Add each value on a separate line:
user=administrator,host=VSS_cluster_node
user=system,host=VSS_cluster_node
where VSS_cluster_node is the DNS hostname of the physical node.
d. Click OK.
The EMC NetWorker Module for Microsoft Applications Release 2.2 SP1
Administration Guide provides more information about configuring a clustered
client resource.
The Microsoft website provides information about deploying Microsoft Exchange
Server 2003 in a cluster.
Installing NMM on Windows 2008 Server Core

To install the NMM software on Windows 2008 Server Core:
1. Access the NMM binaries as described in “Access the installation files” on
page 34. Use the net use command to access remote machines from the 2008
Server Core.
1. Copy the NMM binaries to the 2008 Server Core, by using FTP or general access
method.
2. Access setup.exe in the networkr directory and press Enter to start NMM
installation.
Note: Do not use autorun.exe to install the NMM software.
There is no GUI when NMM is installed on 2008 Server Core, however the NMM
installation wizard starts. This installation wizard is the same wizard that is
started while installing NMM on other OS.
Verifying the installation

Ensure that the following services are up and running:
◆ For NetWorker — nsrexecd.exe
◆ For PowerSnap — nsrpsd.exe
◆ For Replication Manager — irccd.exe
◆ If NMM detects SharePoint during installation — NetWorker SharePoint Service
Controller
◆ If NMM detects Exchange during installation — Replication Manager Exchange
Interface
Maintaining the installation

After installing the NMM software, you may run the Setup program in maintenance
mode to change or remove the existing client installation.
To run the Setup program in maintenance mode:
1. Log in as administrator on the client server.
2. To run the Setup program in maintenance mode, perform one of the following:
• Run the setup.exe file.
or
• Select Start > Settings > Control Panel > Add/Remove Programs. Select the
NetWorker Module for Microsoft Applications and click Change.
The Welcome to NetWorker Module for Microsoft Applications Maintenance
dialog box appears.
3. Click Next. The Setup program detects the existing NMM installation and
displays the Maintenance Type dialog box.
Installing NMM on Windows 2008 Server Core 37

4. Select the type of maintenance to perform:

• Use the Change option to change:
– The configuration settings of the NetWorker SharePoint Service
Configuration dialog box.
– The password for Exchange Server by using nwexinfo.
– To a different authorized NetWorker Server.
“Changing the password or changing to a different authorized server” on
page 38 provides more information.
• Use the Remove option to remove the NMM software from the system.
“Removing the software” on page 38 provides more information.
5. Click Next.
Changing the password or changing to a different authorized server

To change the password or change to a different authorized server:
1. Start the Setup program in the maintenance mode. “Maintaining the installation”
on page 37 provides more information.
2. In the Maintenance Type dialog box, select Change and click Next. The Ready to
Change dialog box appears.
3. In the Ready to Change dialog box, click Change to proceed.
4. In the NetWorker Server Selection dialog box, do any of the following:
a. Click Update List to browse for all the available servers, and click Add to add
a server to the Available Servers list.
b. Select a server from the Available Servers list and click to move the
server to the Selected Servers list.
c. Select a server from the Selected Servers list and click to return it to
the Available Servers list.
d. Type a server name in the Enter a server name field.
! CAUTION
If an authorized server list is used together with a proxy server, then the proxy
server must also authorize the production server, and the production server
authorize the proxy server.
5. Click Next.
Note: The selected NetWorker Server is used to back up the data on the client. If you have not
selected an alternate server, the default server is used to back up the data on the client.
Removing the software

To remove the NMM software:
1. Start the Setup program in the maintenance mode. “Maintaining the installation”
on page 37 provides more information.
2. In the Maintenance Type dialog box, select Remove and then click Next.
3. In the Ready to Remove dialog box, select the Remove NetWorker Module for
Microsoft Applications Metadata option to remove the existing metadata.
• NMM creates and maintains several types of metadata in the course of
operation. This metadata, for example the media database, client file indexes,
log files, the Legato and rmagentps directories, and the Legato and RMService
registry entries are removed.
• To keep the existing metadata for reinstallation of NMM, then leave the
Remove NetWorker Module for Microsoft Applications Metadata option
clear.
4. Click Remove.
Note: Removing NMM, also removes the PowerSnap and Replication Manager services.
The three entries for these programs are removed from under Add/Remove Programs in
the Control Panel.
Removing previous installation of Solutions Enabler

To uninstall Solutions Enabler:
1. Stop the Solutions Enabler services before uninstalling the Solutions Enabler
software by using the following command:
net stop storapid
2. Select Start > Settings > Control Panel > Add/Remove Programs, and select
EMC Solutions Enabler.
3. Click Remove.
Upgrading the software

A direct upgrade of an existing installation of NMM or NetWorker VSS Client to
NMM 2.2 SP1 cannot be done.
Before installing NMM release 2.2 SP1:
◆ Remove any existing version of NMM or NetWorker VSS Client by running the
Setup program in maintenance mode. Select the Remove option.
◆ Remove all existing snapshots. Ensure that PowerSnap snapshot entries are
deleted before reinstallation. Delete PowerSnap entries using the PowerSnap
Client SnapManager or nsrnapadmin.
Note: You may decide to keep the existing metadata for installation of NMM 2.2 SP1.
“Removing the software” on page 38 provides more information.
Upgrading to NMM storage node

NMM supports upgrading NetWorker 7.3.3 or later to NMM storage node.
Removing previous installation of Solutions Enabler 39

Note: You can also use the following procedure to install the NMM storage node.
To upgrade to NetWorker Module for Microsoft Applications storage node:

1. Ensure that you have installed the NetWorker storage node on the server.
The EMC NetWorker Release 7.5.x Multiplatform Version Installation Guide provides
information about installing the NetWorker storage node.
2. Install the NMM software. “Installing NMM” on page 34 provides more
information.
Note: When the NMM installation detects that a NetWorker storage node is already
installed on the server, a message window appears. It states that an existing NetWorker
storage node installation has been detected, and asks if you want to install the NetWorker
Module for Microsoft Applications Client as the storage node.
3. Click OK to upgrade to NMM storage node.

The NMM storage node is installed.
! IMPORTANT
Although the PowerSnap service and Replication Manager service binaries are
installed on the existing storage node during the upgrade procedure, the NMM
storage node cannot be used as the NMM Client.
Installing Microsoft Office SharePoint Server service pack

Microsoft Office SharePoint Server Service Pack 1 (SP1 or later) must be installed.
Without this fix installed on SharePoint machines, NMM might incorrectly list the
presence of the SharePoint Help Search Writer (SPSearch Writer) on a SharePoint
machine that does not actually have the writer. This could lead to a user creating an
invalid saveset, and backup or recovery failure.
Go to the Microsoft website and search for “Microsoft Office SharePoint Server 2007
Service Pack 1 (SP1).” Download and install this service pack on all machines in the
SharePoint Server farm. Once it is installed, no further action is required for NMM.
When installing SP1 on a SharePoint farm, Microsoft recommends installing it in a
specific order:
1. Start the SP1 installation on all machines at the same time.
2. When the Proceed message box is displayed, click OK on all remote clients, but
do not click OK to proceed on the web front end yet.
3. After installation completes on all remote clients, click OK on all remote clients,
and then click OK to proceed with installation on the web front end.
4. Start the SharePoint configuration wizard.
3
Silent Installation of
the Software

◆ Overview ........................................................................................................................ 42
◆ Silent installation of NMM........................................................................................... 42
◆ Silent removal of NMM................................................................................................ 46
◆ Sample scripts for installation and removal of NMM ............................................. 46
◆ Installing and removing NMM by using SCCM 2007 Server ................................. 48
◆ Troubleshooting the installation ................................................................................. 49
Silent Installation of the Software 41

Silent Installation of the Software
Overview
This release of NMM 2.2 SP1 provides support for:
◆ Silent (unattended) installation and removal of the software on a standalone
server.
“Silent installation of NMM” on page 42 and “Silent removal of NMM” on
page 46 provide more information.
◆ Remote installation and removal of the software by using Microsoft System
Center Configuration Manager 2007 (SCCM) Server.
“Installing and removing NMM by using SCCM 2007 Server” on page 48
provides more information.
Silent installation of NMM

Silent installation of NMM 2.2 SP1 is a standalone method that uses the command
line and scripts. In this process, all the information that is required for a successful
installation is gathered by the Setup file (setup.exe) from the command line, which
makes any GUI dialog boxes unnecessary. You may type full setup.exe commands
directly in the command line, or may include such commands in scripts and save it as
a .cmd file.
In a basic silent installation, first the NetWorker software is installed, and then the
PowerSnap and Replication Manager services.
The silent (unattended) installation status log files are available in the client
computer’s temp directory.
For fast access to the temp directory:
1. Click Start > Run.
2. Type %temp%.
! IMPORTANT
Silent installation of NMM as a storage node is not supported.
Commands for silent installation of NMM

Table 9 on page 43 lists the commands for silent installation of NMM 2.2 SP1.
Table 9 Commands for silent installation of NMM
Option Description
setup /s /v" /qb" Silent installation with progress bar.
Note: Ensure that there is space between:

setup and /s
/s and /v”
/v” and /qb”
setup /s /v" /qn" Basic installation with no progress bar.

setup and /s
/s and /v”
/v” and /qn”
setup /s /v"/l*v \"%temp%\mylog.log\" /qb Installs NMM and creates a MSI log file.
Note: Ensure that there is space between: This command is useful for troubleshooting installation
setup and /s problems. The log file is created in the %temp%
/s and /v”/l*v directory. Ensure to use triple quotes in the command
/v”/l*v and \"%temp%\mylog.log\" in case the %temp% path contains spaces.
\"%temp%\mylog.log\" and /qb
Note: The following command opens the Windows Installer, which is an engine for the
installation, maintenance, and removal of software on modern Microsoft Windows systems:
setup /s /v" qn /L*v """%temp%\filename.log"""
Ensure that there is space between:
setup and /s
/s and /v”
/v” and qn
qn and /L*v
/L*v and """%temp%\filename.log"""
Silent installation of NMM 43

NetWorker NMM command line properties

Table 10 on page 44 lists the command line properties that are recognized for
NetWorker NMM.
Table 10 NetWorker NMM command line properties
Property Value Description
INSTALLDIR default = %SystemDrive%\Program Files\Legato\nsr Changes the installation directory for NMM.
To specify a pathname that contains spaces, use the following

syntax:
INSTALLDIR="""c:\program files\legato"""
Note: Ensure to use triple quotes in the syntax.
NW_REMOVEMETADATA {0|1}default = 0 (leave metadata) When removing NMM, if the value is set to 1, the metadata is
removed.
NW_SERVERS default = <no NW servers name specified> By default, the \res\server file is blank when the servers
command is not used or no name is used after the server
command.
To create the SERVERS file with a list of NetWorker servers to

back up the NMM Client, use the following syntax:
SERVERS="""srv1 srv2"""
Note: Ensure to use triple quotes when specifying more than one
server. The use of triple quotes when specifying one server is
optional.
PowerSnap and Replication Manager command line properties

Table 11 on page 44 lists the command line properties that are recognized for
PowerSnap and Replication Manager.
Table 11 PowerSnap and Replication Manager command line properties
Property Value Description
ALLUSERS 1 Always set value to 1.
VSSREG 0 Always set value to 0.
REBOOT S Suppress Reboot. Always set value to S.
ADDLOCAL (x86) Proxy, Host, VSS, and EMCRecoverPoint Features to be installed for x86. All values must be specified.
ADDLOCAL (x64) Proxy, Host, and VSS Features to be installed for x64. All values must be specified.
DORMINST 1 Install Replication Manager. Always set value to 1.
DORMINST_VSS 1 Always set value to 1.
DORMINST_EXCH {1|0} To install Exchange, set value to 1, otherwise set value to 0.
RMCPORT default = 6728 Specify Replication Manager control port.
RMDPORT default = 6729 Specify Replication Manager data port.
Sample commands for silent installation of NMM

This section contains sample commands that you can use for silent installation of
NetWorker, PowerSnap, and Replication Manager.
Sample 1
This sample command contains all the properties that can be passed from the
command line for NetWorker. These properties are optional.
In this sample command:
◆ The NetWorker software is installed in the C:\Legato\nsr directory.
◆ A MSI log file NMMinstall11.log is created in %temp%\filename.log directory.
◆ A SERVERS file contains the server names server1 and server2.
\networker\setup /s /v" /qn /L*v ”””%temp%\NMMinstall11.log
””” INSTALLDIR="""c:\Legato\nsr"""NW_SERVERS=
"""server1 server2""" " / w

setup and /s
/s and /v"
/v" and /qn
/qn and /L*v
/L*v and ”””%temp%\NMMinstall11.log”””
”””%temp%\NMMinstall11.log””” and
INSTALLDIR="""c:\Legato\nsr"""NW_SERVERS="""server1
INSTALLDIR="""c:\Legato\nsr"""NW_SERVERS="""server1 and server2"""
server2""" and “
“ and /
/ and w
Sample 2
Use these sample commands for installing the PowerSnap and Replication Manager
services:
◆ All the properties in the samples must be passed from the command line when
installing the PowerSnap and Replication Manager services.
◆ None of the properties are optional.
◆ When the PowerSnap service is installed, the Replication Manager service is also
installed.
For PowerSnap/Replication Manager silent install for nt86:
\networkr\ps\setup.exe /s /v"/qb ALLUSERS=1 VSSREG=0 REBOOT=S
RMCPORT=6728 RMDPORT=6729 DORMINST=1 DORMINST_EXCH=0
DORMINST_VSS=1 ADDLOCAL=Proxy,Host,VSS,EMCRecoverPoint"/ w
For PowerSnap/Replication Manager silent install for ntx64:
\networkr\ps\setup.exe /s /v"/qb ALLUSERS=1 VSSREG=0 REBOOT=S
RMCPORT=6728 RMDPORT=6729 DORMINST=1 DORMINST_EXCH=0
DORMINST_VSS=1 ADDLOCAL=Proxy,Host,VSS"/ w
Silent installation of NMM 45

Silent removal of NMM

In a silent removal of NMM 2.2 SP1, first the PowerSnap service is removed and then
the NetWorker software. When the PowerSnap service is removed, the Replication
Manager service is also removed.
Commands for silent removal of NMM

◆ Use the following command to remove PowerSnap and Replication Manager
services:
\networkr\ps\setup.exe /s /v "/qn /L*v """%temp%\PSuninstall.log""" " /x

\networkr\ps\setup.exe and /s
/s and /v
/v and "/qn
"/qn and /L*v """%temp%\PSuninstall.log"""
/L*v """%temp%\PSuninstall.log""" and "
" and /x
◆ Use the following command to remove NetWorker, create a MSI log file, and
remove the metadata:
\networkr\setup.exe /s /v "/qn /L*v """%temp%\NMMuninstall.log"""
NW_REMOVEMETADATA=1" /x

\networkr\setup.exe and /s
/s and /v
/v and "/qn
"/qn and /L*v """%temp%\NMMuninstall.log"""
\NMMuninstall.log""" and NW_REMOVEMETADATA=1"
NW_REMOVEMETADATA=1" and /x
Sample scripts for installation and removal of NMM

Table 12 on page 47 lists sample scripts that you can use during the installation and
removal of NMM. All of these samples are included in the NMM 2.2 SP1 installation
media kit, in the directory where setup.exe is located.
Each sample script creates a log in the %temp% directory, whose name is the same as
the script, the only difference being that the file extension .cmd is replaced by .log. For
example, the log for install_nmm_silent_sample.cmd is named
install_nmm_silent_sample.log. These logs can be used to troubleshoot installation
problems.
The install_nmm_silent_sample.cmd script is used for the silent installation of the
NMM 2.2 SP1 software. The install_nmm_silent_sample.cmd script is the master
script, and executes all the scripts in Table 12 on page 47, except for
uninstall_nmm_silent_sample.cmd.
The install_nmm_silent_sample.cmd script

The install_nmm_silent_sample.cmd script performs the following:
1. Checks if NMM or NetWorker is installed. If either is installed, the script exits.
2. Installs the Microsoft .NET Framework 2.0, if it is not installed.
3. Installs the Microsoft VC80 side-by-side redistributable DLLs.
4. Installs NetWorker.
5. Installs the PowerSnap and Replication Manager services.
6. Configures the Windows firewall.
You can modify these sample scripts to provide correct installations for your
environment.
Table 12 Sample scripts for silent installation
Script name Description
install_nmm_silent_sample.cmd Silently installs the NMM 2.2 SP1 software. This sample script
can be modified by the customer.
uninstall_nmm_silent_sample.cmd Silently removes the NMM 2.2 SP1 software. This sample
script can be modified by the customer.
NMMInstalled.vbs Determines if NMM or NetWorker is currently installed.
DotNetInstalled.vbs Determines if Microsoft .NET Framework 2.0 is currently

installed.
DotNetInst.cmd Installs Microsoft .NET Framework 2.0.
NMMConfigFW.vbs Configures the Windows firewall for NMM.
How to install the NMM software using the default installation path
The install_nmm_silent_sample.cmd script uses the following command to install
NMM, and uses the default installation path and leaves res\server file blank:
%~dp0\setup /s /v"/qn /L*v """%temp%\NMMinstall.log""" " / w

%~dp0\setup and /s
/s and /v"/qn
/v"/qn and /L*v
/L*v and """%temp%\NMMinstall.log"""
"""%temp%\NMMinstall.log""" and "
" and /
/ and w
Sample scripts for installation and removal of NMM 47

How to install the NMM software using a different location

To install NMM in a different location and have the NetWorker Server name listed in
res\servers file, use the following command:
@rem %~dp0\setup /s /v"/qn /L*v """%temp%\nmminstall.log"""
INSTALLDIR="""c:\Legato"""NW_SERVERS="""serv1 serv2""" " / w

@rem and %~dp0\setup
%~dp0\setup and /s
/s and /v"/qn
/v"/qn and /L*v
/L*v and """%temp%\nmminstall.log"""
"""%temp%\nmminstall.log""" and INSTALLDIR="""c:\Legato"""NW_SERVERS="""serv1
INSTALLDIR="""c:\Legato"""NW_SERVERS="""serv1 and serv2"""
serv2""" and "
" and /
/ and w
By default, this command is disabled by rem in install_nmm_silent_sample.cmd file.
Installing and removing NMM by using SCCM 2007 Server

To install NMM 2.2 SP1 by using the Microsoft System Center Configuration
Manager (SCCM) 2007 server:
1. Use the New Collection Wizard to specify the client machine, where the NMM
2.2 SP1 software is to be installed.
2. Copy the NMM 2.2 SP1 installation package to the local drive on SCCM Server
and specify a local SCCM machine name as a new distribution point for the
distribution package.
3. Use the New Package Wizard to create a software distribution package. Specify
general information, data source, distribution settings, and other information for
the new package.
4. Use the New Program Wizard to create a installation program for a software
distribution package:
Note: To simplify the source installation command used by SCCM Server, the
install_nmm_silent_sample.cmd and uninstall_nmm_silent_sample.cmd files containing
all the necessary scripts to install and remove NMM respectively are created as examples
in the installation kit \networkr directory. “Sample scripts for installation and removal of
NMM” on page 46 provides details about the scripts’ function.
• To use the Install_nmm_silent_sample.cmd file as a source installation file in

SCCM Server:
a. Start the New Program Wizard.
b. Click Browse in the General Tab, select Show all files, and then select the
install_nmm_silent_sample.cmd file in /networker directory.
• In Environment Wizard window:
a. Ensure that the administrative rights are set to Run Mode.
b. Use the default setting for all other options.
c. Click Close to complete program creation.

5. Use the New Advertisement Wizard to create an advertisement. Specify general
information, package name, program, and the collection to which the
advertisement should be distributed:
a. For schedule option, select Run as soon as possible.
b. For delivery method, use Run program from distribution point.
c. For all other options, use default setting to complete New Advertisement
Wizard.
Once the advertisement is created, the SCCM Server is set up to install the
software. The Advertisement Status section in SCCM Server can be used to check
the installation process status. It may take more than 30 minutes for the SCCM
Server to process the advertised installation.
The SCCM server installation status log files are available in the client computer’s
C:\Windows\temp directory. For fast access to the temp directory, select Start >
Run and then type %SystemRoot%\temp.
To remove NMM 2.2 SP1 by using the SCCM 2007 Server:
◆ The steps to remove NMM by using the SCCM Server are the same as that of
installing NMM on the SCCM Server.
◆ Instead of using the install_nmm_silent_sample.cmd file, use
uninstall_nmm_silent_sample.cmd file.
Troubleshooting the installation

This section provides tips to troubleshoot errors that may appear during installation,
when moving from a previous release of NMM or NetWorker VVS Client to NMM
2.2 SP1, or if NMM is not running correctly after a fresh installation.
Errors in installation of Replication Manager

Most frequently, a problem in the installation is due to errors in the installation of
Replication Manager services.
1. Check Add/Remove Programs in Microsoft Windows Server 2003, or Programs
and Features in Microsoft Windows Server 2008. The NMM software, and
Replication Manager and PowerSnap services should appear installed. The
Replication Manager entry appears as RMagentPS:
a. If NMM, PowerSnap service or Replication Manager service is missing,
remove all, and then reinstall.
Remove the programs in the following order:
1. Replication Manager service
2. PowerSnap service
3. NMM software
b. Reinstall.
2. If all the three programs appear to be installed but not running, or you get an
error about a service not starting, verify that the services for NMM, PowerSnap,
and Replication Manager are running.
Troubleshooting the installation 49

• If any of the services is not running, remove and reinstall all of the programs
as described in step a .
• If irccd.exe is not running, but nsrexecd.exe and nsrpsd.exe are running, then
manually install the Replication Manager service from the following directory
networkr\ps\rmc\setup.exe.
Using non-English characters in installation path

During silent or GUI installation, ensure not to use non-English characters in the
installation path because although NetWorker seems to be installed properly, the
installation of PowerSnap service and Replication Manager service fail and an error
message appears.
4
Licensing and
Enabling the
Software

◆ NMM client software licensing ................................................................................... 52
◆ The evaluation process ................................................................................................. 53
◆ The licensing process .................................................................................................... 54
◆ Update enablers............................................................................................................. 57
◆ Managing EMC licenses ............................................................................................... 58
Licensing and Enabling the Software 51

Licensing and Enabling the Software
NMM client software licensing

The NetWorker software is installed in evaluation mode. The licensing of NetWorker
software means entry of enabler and authorization codes on the server for the
NetWorker environment. Without these codes, the software or added features will
not run beyond the evaluation period.
Each installation of NMM client must be licensed with an enabler that activates the
software and allows you to use the software. All licensing takes place on the server.
The licenses are typed and stored on the server, and the server enforces the licensing.
Base enablers come in different editions, which enable varying degrees of
functionality. Add-on enablers allow a broader scope of features.
Add-on enabler names

The specific add-on enabler for the NMM client is NetWorker Module for Microsoft
Applications. The enabler name for NMM may vary depending on which version of
NetWorker is installed, whether NetWorker Server has been upgraded, and in what
order it was installed or upgraded:
◆ If an NMM add-on enabler is installed on NetWorker 7.4 SP2 or later, the add-on
enabler is displayed as NetWorker Module for Microsoft Applications.
◆ If an NMM add-on enabler is installed on NetWorker prior to release 7.4 SP2, the
add-on enabler is displayed under the old VSS license name Volume Shadowcopy
Service for Windows. If the same NetWorker Server is then upgraded to NetWorker
7.4 SP2 or later, the existing add-on enabler is still displayed under the old VSS
license name Volume Shadowcopy Service for Windows.
◆ If an older version of NetWorker Server, with an add-on enabler that uses the old
name, is upgraded to NetWorker Server 7.4 SP2 or later, and then a new NMM
add-on enabler is installed, then the new add-on enabler is displayed as
NetWorker Module for Microsoft Applications in addition to the old enabler Volume
Shadowcopy Service for Windows. Even though both names are present, the enablers
will be combined and used correctly as different client systems claim them.
The steps in this chapter assume that all of the software and hardware requirements
have been met and the NMM client software is installed.
The evaluation process

Evaluating NMM client software can take place in two ways:
◆ By evaluating a new installation of the software on a Windows Server
◆ By evaluating NetWorker features on an existing NetWorker installation
Evaluating a new installation

When you first install the NMM client software, you can evaluate it with all the
modules and features for 30 days free without typing any codes.
By the end of the evaluation period, you must purchase, type, and authorize a base
enabler to continue to use the NMM client software to restore data. The base enabler
is the license that enables the edition purchased.
To continue to use the modules and features that were available with the evaluation
software, you might need to purchase the NMM client add-on enabler, depending on
the edition of the base enabler.
Evaluating features on an existing installation

If you are evaluating one or more NMM client modules or features on an edition of
the software that has already been installed and enabled, you must type a temporary
enabler for each module or feature. The temporary enabler is valid for 45 days.
Contents documentation in the EMC Information Protection and Availability Product
Families Media Kit and “Where to get help” on page 9 provide information about how
to obtain a temporary enabler code.
“Typing a temporary enabler code” on page 53 provides information about how to
type the temporary enabler code. By the end of the evaluation period, you must
purchase, type, and authorize the corresponding license enablers to continue to use
modules or features evaluated by you. “The licensing process” on page 54 provides
instructions.
Typing a temporary enabler code
! CAUTION
The temporary enabler code is valid on only one computer in a network. If you
type the same code on more than one computer in a network, a copy protection
violation error occurs and the NMM client software is disabled on all NetWorker
Servers with duplicate enablers.
To type the temporary enabler code:

1. Start the NetWorker Management Console software.
2. Launch the Administration window:
a. From the Console window, click Enterprise.
b. From the left pane, select a NetWorker Server in the Enterprise list.
c. From the right pane, select the application.
d. From the Enterprise menu, click Launch Application. The Administration
window is launched as a separate application.
The evaluation process 53

3. From the Administration window, click Configuration.

4. In the left pane, select Registration.
5. From the File menu, select New.
6. In the Enabler Code attribute, type the enabler code.
7. In the Name attribute, type the name of the license.
8. (Optional) In the Comment attribute, type a description of the license.
9. Click OK.
The licensing process

To permanently use NMM client software, you must purchase and type a license
enabler code, and then authorize it. This licensing process is the same for all editions
of software as well as for individual modules and features.
The license enabler code that you purchase is valid for 45 days, as a registration
period. During the registration period, you must obtain and type a corresponding
authorization code.
The following sections explain how to type and authorize the license enabler:
◆ “Type the license enabler code” on page 54
◆ “Obtain an authorization code” on page 55
◆ “Type the authorization code” on page 56
Type the license enabler code

License enabler codes are included in either the letter announcing the updated or
upgraded software, or on the Enabler Certificate you receive when you purchase a
software license. This depends on whether the software purchased is a first-time
purchase or an updated or upgraded version.
Note: To save time when typing multiple licenses, type the base enabler last. Otherwise, once a
base enabler is typed, devices that do not yet have licenses typed may be disabled. Those
devices would have to be reenabled manually after their licenses are installed.
To type the license enabler code:

b. From the left pane, click a NetWorker Server in the Enterprise list.
c. From the right pane, click the application.
d. From the Enterprise menu, select Launch Application. The Administration
3. In the Administration window, click Configuration.
4. In the left pane, select Registrations.
5. From the File menu, select New. The Create Registration dialog box appears.
6. In the Enabler Code attribute, type the enabler code.
7. In the Name attribute, type the name of the license.

8. (Optional) In the Comment attribute, type a description of the license.
9. Click OK.
The new license is added and appears in the right pane. Repeat the procedure to
add any additional enabler codes. After you type a license enabler code, you have
45 days as a registration period to authorize the NMM client software.
Obtain an authorization code

Registration of NMM client software takes place by obtaining an authorization code.
Obtain a unique authorization code through one of the following methods:
◆ “Using the EMC website” on page 55
◆ “Using email” on page 55
! CAUTION
If the software or feature is not authorized by the end of the 45-day registration
period, the NMM client function or feature is disabled.
Using the EMC website

Register products and obtain authorization codes online by completing a registration
form on the EMC website at http://Powerlink.EMC.com. Web registration takes just
a few minutes and is available 24 hours a day, 7 days a week.
An authorization code that permanently enables the NetWorker license is sent by
email.
Using email
To register the software and obtain an authorization code by email:
4. In the left pane, select the NetWorker Server.
5. From the File menu, select Properties. The Properties dialog box appears.
6. Click the Customer Information tab and complete your contact information.
7. Email your registration information. For contact information, go to the EMC
CustomerNet portal at http://Powerlink.EMC.com.
An authorization code that permanently enables the updated NetWorker
software is sent to you.
The licensing process 55

Type the authorization code

To complete the licensing process, you must type the unique authorization code on
the NetWorker Server within 45 days of typing the license enabler code.
If the authorization process is successful, the expiration date for the license displays
“Authorized - No expiration date.” If the authorization is not verified in this way,
contact http://Powerlink.EMC.com.
To avoid an interruption in restores, if you move the NMM client software from one
computer to another, or to change the network address of a computer after the
software is installed, perform one of the following:
◆ Obtain a new authorization code. You need the host ID of the original server as
well as the new server. The host ID appears in the server’s Registration window.
◆ Install and configure the License Manager software. “Managing EMC licenses”
on page 58 and the latest EMC NetWorker License Manager Installation Guide
provide more information about using the License Manager.
To type the authorization code:
4. In the left pane, select Registration.
5. In the right pane, select a license.
6. From the File menu, select Properties.
7. In the Auth Code attribute, type the authorization code for the product (the
authorization code assigned to the specified permanent enabler or update enabler
code).
8. Click OK. The license is now permanently enabled.
Update enablers
To update existing NMM client software to a major release (one that introduces
important new features), an update enabler is necessary. Update enablers are
required for any major NetWorker software update, including the current NetWorker
release. To use the License Manager, the NetWorker Server must be release 5.0 or
later.
With a first-time purchase of NMM client software, a one-year update agreement
might be included. After one year, an update enabler may be acquired with a new
update agreement purchase.
Additional licenses
This section describes a few of the additional licenses required to operate some of the
NetWorker features.
Client connection licenses

Every computer to be restored in a NetWorker datazone requires a client connection
license, even the NetWorker Server. The client connection license may be one of the
licenses supplied with the base enabler or purchased separately. A cluster client or
NDMP data server requires a special type of client connection license, as described in
“Cluster clients” on page 57 or “Managing EMC licenses” on page 58.
NetWorker application modules

NetWorker application modules are licensed on the basis of one enabler per database
type host. For example, to back up the Exchange database on two hosts, two
NetWorker module for Exchange enablers are required, even if the two hosts are
backed up by the same server.
However, if multiple database instances are running on a NetWorker Client host, only
one NetWorker module enabler is required for that one host.
Cluster clients
For each physical node in a cluster, you must purchase a Cluster Client Connection,
which takes the place of one standard client connection. The EMC NetWorker Release
7.5.x Multiplatform Version Administration Guide provides more information on
licensing computers in a cluster.
Update enablers 57
Managing EMC licenses

The License Manager provides centralized license management, allowing you to
maintain all of an enterprise’s NetWorker licenses from a single computer. With the
License Manager, you can move NMM client software from one computer to another,
or change the IP address on an existing NetWorker Server without having to
reauthorize the software. The License Manager can be installed as an option during
NMM client software installation.
To implement the License Manager:
1. Contact Licensing to obtain bulk enabler codes. Go to
http://Powerlink.EMC.com for more information.
2. Install the License Manager software.
3. Configure the License Manager software.
4. Configure the NetWorker Servers to access the License Manager for their licenses.
The EMC NetWorker License Manager Installation Guide provides details on installing
and using the License Manager.
5
Configuring the
Software

◆ Using NMM with a VSS Hardware Provider ........................................................... 60
◆ Setting up a proxy server for rapid backups of VSS snapshots ............................. 60
◆ Configurations specific to PowerSnap ....................................................................... 61
◆ Configurations specific to CLARiiON ....................................................................... 61
◆ Configurations specific to Symmetrix........................................................................ 63
◆ Configurations specific to VMware ESX guest environment ................................. 72
◆ Changing Replication Manager port settings ........................................................... 75
◆ Configuring NetWorker SharePoint services............................................................ 76
◆ Configuring Windows firewall settings .................................................................... 78
◆ Manually creating NMM firewall exceptions ........................................................... 80
Configuring the Software 59

Configuring the Software
Using NMM with a VSS Hardware Provider

NMM can use a VSS Hardware Provider for persistent snapshots or off-host backups.
To enable these to work together, use the following processes to configure the
hardware array and NMM:
◆ “Hardware array configuration” on page 60
◆ “NMM configuration for hardware provider support” on page 60
Hardware array configuration

Perform the following steps for hardware array configuration:
1. Ensure that you have first reviewed the “Supported configurations” on page 29.
2. Configure the EMC CLARiiON snapshot or clones, EMC Symmetrix BCV mirrors
or snapshots or EMC Celera snapshots as required.
3. Verify that the VSS Hardware Provider is available for use:
a. Run vssadmin list providers on the application server.
b. Test if the hardware provider is functioning properly by using
VSHADOW.exe in Windows Server 2003 or DISKSHADOW.exe in
Windows Server 2008 to validate creation of hardware snapshots.
NMM configuration for hardware provider support

To configure NMM for hardware provide support:
1. Ensure that NMM Client is installed on the Windows Server hosting the
application.
2. Configure a NetWorker Client scheduled backup as needed for the application:
a. Configure a snapshot policy to match application requirements.
b. Configure a backup group, referencing the snapshot policy.
c. Configure a client resource as required for the application, including
NetWorker User Group entries.
d. Configure a proxy client if required, including NetWorker User Group entries.
3. Run and test the NMM scheduled backup.
Setting up a proxy server for rapid backups of VSS snapshots

To be able to take rapid backups of VSS snapshots created by NMM, you can set up
the NMM software or the NMM storage node to act as the proxy client. The storage
node acts as the proxy client in a SAN-based storage node configuration.
The EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Administration
Guide provides more information.
Configurations specific to PowerSnap

Review the following sections for configuration information specific to PowerSnap.
Adding username for account that is logged in the server

If you do not have administrative rights and are running programs, add the
username for the account that is logged in to the server:
1. Set the PowerSnap NetWorker security by using NMC (from Configuration >
User Groups).
2. Add the following values to the Administrators User Group for the production
host and proxy host:
user=Administrator,host=<fqdn>
For example:
• For production host:
user=system,host=bv-clsrv.belred.emc.com
• For proxy host:
user=system,host=qe2.belred.emc.com
Running a backup with CLARiiON array LUNs

For PowerSnap to run a successful backup with CLARiiON array LUNs, run the
following command:
naviseccli -h "HOST" -addusersecurity
-user "CLARiiON_ARRAY_USER" - password
"CLARiiON_ARRAY_USER_PASSWORD" -Scope 0
Configurations specific to CLARiiON

The CLARiiON documentation provides information about how to configure
CLARiiON storage arrays. Additionally, ensure that the following configuration
tasks are performed:
1. This step is required only when CLARiiON FLARE 19 is used. “Update the
CLARiiON configuration file” on page 62
2. “Update the SYMCFG authorization list” on page 62
3. “Update the Navisphere Privileged Users list” on page 63
If a CLARiiON array is migrated, or the information in the CLARiiON configuration
is not up-to-date, rollback may fail. If there is more than one entry in the CLARiiON
clarcnfg file, Replication Manager only uses the first entry. If the clarcnfg file is not
current, the first entry may be pointing to a CLARiiON that is no longer connected to
the system. Edit the clarcnfg file so that there is only entry, pointing to the current
CLARiiON you want to use.
Configurations specific to PowerSnap 61

Update the CLARiiON configuration file

To support Replication Manager, edit the CLARiiON configuration file (clarcnfg)
with the CLARiiON array name and the IP addresses or DNS hostnames of the two
storage processors that exist in each CLARiiON machine.
The clarcnfg file is located in the
%ProgramFiles%\EMC\SYMAPI\config\clarcnfg directory.
Use the following sample configuration file template as a guide when adding values
to your CLARiiON configuration file. Obtain the values from the CLARiiON array
configuration:
###########################################################
# CLARiiON CONFIGURATION FILE TEMPLATE
# This CLARiiON configuration file provides network addresses
# (hostnames or IP addresses) for the two Storage Processors on
# each CLARiiON which can be seen by this host. To load
# information about CLARiiON systems, CLARAPI must be able to
# communicate with the Navisphere Agent that administers them.
# CLARAPI Discovery depends on valid entries in this file.
#
# CLARiiON Arrayname Storage Processor A Storage Processor B
# XXXXXXXXXXXX losat246 losat247
APM00052211461 10.5.221.132 10.5.221.133
Update the SYMCFG authorization list

The SYMCFG authorization list must be updated to support the EMC VSS Provider.
Use the following example to update the SYMCFG authorization list for your
configuration.
In the following example, the two hostname IP addresses identify the two storage
processors that exist on each CLARiiON machine:
1. Update the SYMCFG authorization list with the hostname IP address, username,
and password for storage processor A. For example:
%ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization add -host
10.5.221.132 -username gadmin -password rdc4xyz
2. Update the SYMCFG authorization list with the hostname IP address, username,
and password for storage processor B. For example:
%ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization add -host
10.5.221.133 -username gadmin -password rdc4xyz
3. Verify that the SYMCFG authorization list has been updated correctly. For
example:
%ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization list
Hostname Username
------------------- --------------------
10.5.221.132 gadmin
10.5.221.133 gadmin
Update the Navisphere Privileged Users list

In addition to the information provided in this section, review The EMC Navisphere
Manager Administrator’s Guide for more information about adding entries to the
Privileged Users list.
EMC Navisphere is a software that enables the management of CLARiiON storage
systems. These configurations are done when setting up CLARiiON and are carried
out by the CLARiiON administrator.
To create a secure environment:
1. Update the EMC Navisphere Privileged Users list with the DNS hostname or IP
address of the CLARiiON storage processors (SPA and SPB).
2. Type values in the Privileged Users list in the following format:
system@hostname_SPA
system@hostname_SPB
where hostname_SPA and hostname_SPB are the DNS hostnames or IP addresses of
the CLARiiON storage processors.
Configurations specific to Symmetrix

The following sections describe how to set up Symmetrix for data protection. Before
you begin, determine the Symmetrix technology that you will be using for data
protection and the number of persistent snapshots that will be required.
The two primary options are:
◆ TimeFinder/Mirror, based on Symmetrix BCVs — Symmetrix BCVs are
appropriate for data protection scenarios where you want to retain the snapshot
as a backup copy for a full volume restore or rollback.
◆ TimeFinder/Snap, based on Symmetrix VDEVs — Symmetrix VDEVs are
appropriate for temporary snapshot data protection scenarios where the snapshot
is only used to create the backup copy to disk or tape and then deleted.
The initialization of Symmetrix for these two technologies is quite different.
For the following discussion, it is assumed that Symmetrix volumes 8B and 8C are
being backed up by using BCVs and Symmetrix volumes 7D and 7E, which are being
backed up with VDEVs. Further, it is assumed that two snapshots a day are going to
be created.
Note: If both BCVs and VDEVs are available for use with an STD, then the determination of the
backup being a Copy-On-Write copy (snapshot) or a full copy (BCV) is made by the EMC VSS
Provider.
Configurations specific to Symmetrix 63

Setting up the TimeFinder/Mirror (BCV) configuration for Symmetrix

The TimeFinder/Mirror technology is a full copy technology where a Business
Continuance Volume (BCV) is mirrored or established to a production volume,
referred to as a STandard Device (STD). While being established, the BCV
synchronizes with the STD and once fully synchronized any new writes to the STD
are copied to the BCV as well. When the BCV is disconnected from the STD, also
know as split, it becomes a point-in-time copy of the STD.
The relationship between a BCV and a STD can be thought of as permanent until the
BCV is mirrored to a different STD. Once fully synchronized and split the Symmetrix
tracks change to either the STD and BCV. When the two are reestablished, the tracks
that were changed on STD are copied to the BCV. Any tracks that have changed on
the BCV is refreshed from the STD so that the BCV is once again a full mirror of the
STD.
Preparation of TimeFinder/Mirror for use with a proxy consists of the establishing
one or more BCVs to the production volume (STD) and waiting for them to become
synchronized. Note that if more than two BCVs are required then the first BCVs will
need to be split after they have become synchronized in order to allow new BCVs to
be synchronized.
Solutions Enabler's SYMCLI is used to do this work. The SYMCLI is very flexible and
in many cases there is more than one way to accomplish a given task. The procedures
described in this section reflect the simplest steps whenever possible. In the example,
the BCV volumes are B6, B7, B8 and B9. The example establishes B6 and B7 to volume
8B, and B8 and B9 to volume 8C.
Setting up the device group and establishing mirrors with BCVs on Symmetrix
This section contains instructions for setting up the device group and establishing
mirrors with BCVs on Symmetrix. A device group is a SYMCLI object created on
hosts. It is a logical grouping of production volumes (STDs) and copy volumes
(BCVs, VDEVs, and so on).
For all other options, use the -help option with any SYMCLI command. The EMC
Solutions Enabler Symmetrix CLI Version 6.3 Quick Reference or EMC Solutions Enabler
Symmetrix TimeFinder Family CLI Version 6.3 Product Guide provides more information
about using the -help option.
To set up the device group, complete the following tasks:
1. Create a device group.
To create a device group, use the following command:
symdg create <device group name>
For example: symdg create mgrp
2. Add devices to the device group.
The STDs is assigned a logical name based on the order in which they are entered.
To add a STD device to the device group, use the following command:
symld -sid <Symm ID> -g <group> add dev <Symm device>
For example:
symld -sid 829 -g mgrp add dev 8b
symld -sid 829 -g mgrp add dev 8c
The Symmetrix ID is typically the last digits of Symmetrix's serial number to make
it unique if there is more than one Symmetrix that can be seen by the host.
After the STD device is added, to add a BCV to the device group, use the
following command:
symbcv -g <device group name> -sid <Symm id> add dev <symm
device name>
For example:
symbcv -sid 829 -g mgrp add dev b6
3. Verify the group.
To check what is in a group, use the following command:
symdg show <group name>
For example: symdg show mgrp
Figure 4 on page 66 displays the output.

Figure 4 Output of verify the group command
4. Use the attach command to relate the STD device with respective BCV:
symmir -g <Groupname> attach <STD DEV ID> bcv dev <bcv DEV
ID>
5. Perform the initial device establish.
For the initial establish of the STDs to their partner BCVs, use the following
command:
symmir -g <device group name> establish <STD logical device>
bcv ld <BCV logical device>
For example:
symmir -g mgrp establish DEV001 bcv ld BCV001 -full
6. Query the mirror state.
Do not initiate a backup until the BCVs are fully synchronized. To check the state
of the mirrors, use the following command:
symmir -g <device group name> query -multi
For example: symmir -g mgrp query -multi
Figure 5 Output of query the mirror state command
When at least one BCV for each production volume is synchronized the system is
ready to be used for NMM backups. If more BCVs are needed to cover the
number of snapshots then the currently synchronized BCVs must be manually
split with the following command:
symmir -g <group> split <logical device> bcv ld <logical
device>
For example:
symmir -g mgrp split DEV001 bcv ld BCV001
At this point another pair of BCVs can be established to the STDs and
synchronized. Once the BCVs are established with an STD, the BCVs are rotated
by the EMC VSS Provider as needed.
7. Rerun the mirror query after the backup.
Once the backup is complete, it is useful to rerun the mirror query command.
Figure 6 Output of mirror query rerun command
Notice that one BCV for each production volume is split from its STD. These are
the copies that were used to make the backup.
During subsequent backups, all the BCVs will most likely be seen to be in the split
state. What happens is that when a backup is requested the EMC VSS Provider
establishes BCV to each of the production volumes. When the BCVs are
synchronized the EMC VSS Provider then splits them and the actual backup
starts.

Setting up the TimeFinder/Snap (VDEV) configuration for Symmetrix

The TimeFinder/Snap technology is a copy-on-write technology, where a virtual
device (VDEV) is connected paired to a STD (production volume). The pairing is
done by creating a session between the STD and VDEV. Once paired with an STD the
VDEV can be activated at which moment it becomes a copy-on-write snapshot of the
STD for that point-in-time.
Note: The VDEV is really a block of logical pointers that are initially set to point to the STD. As
new writes are made to the STD the old data is first copied to a persistent Save Device (SDEV)
that backs up the VDEV. The logical pointer on the VDEV for that data region is then updated
to point to the old data on the SDEV.
SDEVs are allocated to named pools. The default pool is named DEFAULT_POOL.
When a session between a STD and VDEV is created the pool for the SDEVs must be
specified. NMM currently is limited by underlying technology to using the default
pool.
Unlike a BCV, when a terminate operation is done to a VDEV, its relationship to a
particular STD stops and the SDEVs connected with that VDEV are freed.
In the example, the STD volumes being backed up are Symmetrix devices 7D and 7E.
Symmetrix VDEVs DF -> EE use the SDEVs from the default pool for persistent
storage.
Preparing for backups with NMM is only necessary to create the initial sessions
between a STD and the VDEVs that are used as snapshots.
In the examples used in the following tasks, the STD volumes that are backed up are
Symmetrix devices 7D and 7E. Symmetrix VDEVs DF -> EE then uses the SDEVs
from the default pool for persistent storage.
To set up the TimeFinder Snap configuration for Symmetrix, complete the following
tasks:
1. Add SDEVs to a pool.
Note: This step might not be necessary depending on how the Symmetrix has been
configured. It is provided for completeness.
To add SDEVs to a pool, use the following command:

symconfigure -sid <Symm Id> -cmd "ADD DEV <sdev device
range> TO POOL DEFAULT_POOL TYPE=SNAP MEMBER_STATE=ENABLE;"
commit
For example:
symconfigure -sid 829 -cmd "ADD DEV F7:107 TO POOL
DEFAULT_POOL TYPE=SNAP MEMBER_STATE=ENABLE;", commit
2. Create a device group.
To create a device group, use the following command:
symdg create <group name>
For example:
symdg create sgrp
3. Add devices to the device group.

Next add the STDs to the device group. The STDs will be assigned a logical name
based on the order in which they are entered.
To add a device to the device group, use the following command:
symld -sid <Symm ID> -g <group> add dev <Symm device>
For example:
symld -sid 829 -g sgrp add dev 7d
symld -sid 829 -g sgrp add dev 7e
The Symmetrix ID is typically enough last digits of Symmetrix's serial number to
make it unique if there is more than one Symmetrix that can be seen by the host.
After the STD volumes are added, to add the VDEV devices, use the following
command:
symld -sid <Symm ID> -g <group> add dev <Symm device> -vdev
For example:
symld -sid 829 -g sgrp add dev df -vdev
symld -sid 829 -g sgrp add dev e0 -vdev
4. Verify the group.
To check what is in a group, use the following command:
symdg show <group name>
For example: symdg show sgrp
5. Create the initial sessions.
To create initial sessions, use the following command:
symsnap -g <group> create -svp <pool name> <STD logical
name> vdev ld <VDEV logical name> -nop
For example:
symsnap -g sgrp create -svp DEFAULT_POOL DEV001 vdev ld
VDEV001 -nop
VDEV002 -nop
VDEV003 -nop
VDEV004 -nop

Figure 7 Output of initial sessions
6. Query the snap state.

The state of the snapshots is done with the following command.
symsnap -g <group> query -multi
For example: symsnap -g sgrp query -multi
Figure 8 Output of querying the snap state command
7. Running snapshot againquery after the backup.

At this point the system is ready to be used for NMM backups. Once the backup
is complete, run the following commands:
a. Run the snapshot query again.
Figure 9 Output of running the snapshot query command again

b. The second command is a similar view, but is done by pool. Note that this
command displays all the sessions that are using SDEVs in the pool, and not
just the ones that are yours.
symsnap -svp <pool> list
For example: symsnap -svp DEFAULT_POOL list
Figure 10 Output of second command of running the snapshot query again
Configurations specific to VMware ESX guest environment

The following sections provide information about:
◆ “Prerequisites” on page 72
◆ “Configuring NMM backups with EMC VSS Hardware Providers for CLARiiON
LUNs” on page 73
◆ “Configuring NMM backups with EMC VSS Hardware Providers backups for
Symmetrix LUNs” on page 74
◆ “Configuring data mover between the ESX guest virtual machine and a physical
windows host” on page 74
Prerequisites
Review the following prerequisites before starting the configuration:
◆ Ensure that you have SSH enabled on ESX server system. The VMware
KnowledgeBase article “Enabling root SSH login on an ESX host“provides details
about how to enable SSH on VMware host. This article can be found at:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cm
d=displayKC&externalId=8375637
◆ Latest windows service pack updates must be applied on all NMM clients.
◆ During installation of VMware tools on ESX guest virtual machine, select the
"complete" installation option.
◆ During installation of VSS Provider version 4.1.2, select the "complete"

installation option.
◆ Install PowerPath on the physical machine that is used as the data mover.
Configuring NMM backups with EMC VSS Hardware Providers for CLARiiON LUNs
To configure a NMM backup with EMC VSS Hardware Provider for CLARiiON
LUNs:
1. Install NaviHost agent on ESX Server Host system.
Note: The NaviHost agent version must be same as the CLARiiON storage flare version
assigned to ESX Host system.
2. Add LUNs to NMM client as RAW device mapping in physical compatibility

mode. The virtual compatibility mode is not supported by EMC VSS Provider.
3. Set VICLIENT_DISABLE_CACHE=1 as system environment variable in ESX
guest virtual machine.
4. Install VSS Provider version 4.1.2. Select complete installation and provide the
required license.
5. Install NaviAgent, NaviCLI, and ADAM snap. Provide the required
authorization to the Windows client.
Note: The NaviAgent and NaviCLI versions must be the same as the CLARiiON storage
flare version assigned to ESX host system.
6. Add NaviSecCli.exe as the installation path in System Variables Path entry.

For example: C:\Program Files\EMC\Navisphere CLI\NaviSECCli.exe
7. To authorize Solutions Enabler access to the CLARiiON storage array, use the
SYMCLI symcfg command.
For example, to add authorization for a CLARiiON storage processor with IP
address 172.23.193.86, username clariion and password clarpass, type:
symcfg authorization add -host 172.23.193.86 -username
clariion -password clarpass
It is important to add the authorization for each of the CLARiiON storage
processors.
8. Add NaviSECCli security credentials on ESX guest virtual machine.
For example, to add NaviSECCli security credentials for a CLARiiON storage
processor with IP address 172.23.193.86, username clariion and password clarpass,
type:
NaviSECCli -user clariion -Scope 0 -address 172.23.193.86
-AddUserSecurity
Provide password when prompted. It is necessary to add NaviSECCli security
credentials for each of the CLARiiON storage processors.
9. Use the vicfg commands to authorize access to ESX server from the ESX guest
virtual machine.
Configurations specific to VMware ESX guest environment 73

For example:
C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u
<username> -p <password> -s <esx_network_address> [-force]]
10. For SnapView clone configuration, create CLARiiON clone by using CLARiiON
Navisphere Management user interface.
11. Install the NMM Client on the ESX guest virtual machine.
12. Restart the ESX guest virtual machine. This is required to save the environment
variables settings that are added during the installation.
Configuring NMM backups with EMC VSS Hardware Providers backups for Symmetrix LUNs
To configure a NMM backup with EMC VSS Hardware Provider for Symmetrix
LUNs:
1. Add STD, BCV, and gatekeeper LUNs to NMM client as RAW device mapping in
physical compatibility mode. Virtual compatibility mode is not supported by
EMC VSS Provider.
2. Install VSS Provider v4.1.2. Select complete installation and provide the required
license.
3. By using the Symmetrix configuration tools, create suitable device group and
synchronize the STD and BCV LUNs. For backup operations, provide the STD
device save set or application save sets, as applicable.
4. Set VICLIENT_DISABLE_CACHE=1 as system environment variable in ESX
guest virtual machine.
5. Use vicfg commands to authorize access to the ESX server from the ESX guest
virtual machine.
For example:
C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u username
-p password -s esx_network_address [-force]]
6. Install the NMM Client on the ESX guest virtual machine.
7. Restart the ESX guest virtual machine. This is required to save the environment
variables settings that are added during the installation.
Configuring data mover between the ESX guest virtual machine and a physical windows host
The data mover between the ESX guest virtual machine is the production client and
the physical Windows host, which is the proxy client.
To configure data mover between the ESX guest virtual machine:
1. For proxy client, ensure that the LUNs are configured from same array as that of
production client.
2. Ensure that the Hardware Providers backup are working for both the:
• Production clients
• Proxy clients.
3. For Symmetrix, pair standard from the production client with the BCV from the
proxy client.
4. In application information window of the production client, type the following:
NSR_DATA_MOVER = proxy.domain.com
5. Perform the following command on both the production client and proxy client:
vicfg setup [-u username -p password -s esx_network_address
[-force]]
Updating NMM settings with Exchange username, password, or domain

If changes are made to the Microsoft Exchange Services account, changes may be
necessary in the NMM settings to continue NMM access to the account.
The steps for updating the Exchange username or account information in NMM are
different for Exchange Server 2003 and Exchange Server 2007.
Update account information in NMM for Exchange Server 2003

When NMM is installed on an Exchange Server 2003, the utility runs as part of the
NMM installation. This utility updates the NMM software with the Exchange
username, password, and domain.
Run the utility again if:
◆ The Exchange Server is installed after the NMM is installed.
◆ The username, password, or domain changes after the NMM is installed.
To run the utility, double-click the file from the %ProgramFiles%\Legato\nsr\bin
directory.
Update Exchange Service account information in NMM for Exchange Server 2007
When changes are made to the Exchange Services account in Exchange Server 2007,
the username and account information must be updated in:
◆ The Replication Manager-supplied Exchange 2007 Service for NMM.
◆ The COM registration associated with that Replication Manager-supplied
Exchange 2007 Service for NMM.
Changing Replication Manager port settings

The Replication Manager port settings are specified during the NMM installation.
However, you can use the following procedure to change the Replication Manager
port settings after NMM is installed.
To change the Replication Manager port settings:
1. From the command line, stop the rmagentps service.
For example:
net stop rmagentps
2. From the %Program Files%\Legato\nsr\rmagentps\client\bin directory, run
the irccd command to change the port settings.
For example:
irccd –p <control_channel_port> -P <data_channel_port>
Updating NMM settings with Exchange username, password, or domain 75

3. From the %ProgramFiles%\Legato\nsr\res directory, edit rmps.res.

For example:
type: RM Service Ports;
Control Port: <control_channel_port>
Data Port: <data_channel_port>
For example:
type: RM Service Ports;
Control Port: 6728;
Data Port: 6729;
4. Start the rmagentps service.
For example:
net start rmagentps
Configuring NetWorker SharePoint services

During NMM installation, the NetWorker SharePoint Service Configuration dialog
box appears.
You can:
◆ “Match NetWorker SharePoint Service credentials with credentials of SharePoint
Server administrator” on page 76
◆ “Specify temporary storage location” on page 77
◆ “Specify the restore lock type” on page 78
! IMPORTANT
You can update your credentials, and change the temporary storage location and
the restore lock type for SharePoint granular back even after completing the NMM
installation.
To view the NetWorker SharePoint Service Configuration dialog box after the
installation is complete, type the following command at the command line:
C:\Program Files\Legato\nsr\bin\nwmossinst.exe. The NetWorker SharePoint
Service Configuration dialog box appears.
Match NetWorker SharePoint Service credentials with credentials of SharePoint Server

administrator
The NetWorker SharePoint Service credentials specified in the NetWorker SharePoint
Service Configuration dialog box must match the user and password credentials used
for SharePoint Server administration. If proper credentials are not specified then
backup of SharePoint data fails.
The NetWorker SharePoint Service Configuration dialog box provides fields to
specify the Domain/User Name and Password for SharePoint Service credentials. If
you do not fill in the fields to specify the same credentials as those of the SharePoint
Server administrator, backup of SharePoint data fails with a Windows
E_ACCESSDENIED error.
If you have already completed installation and want to test whether your credentials
are correct, you can run the following commands at the command line on the
SharePoint machine:
nsr_moss_save.exe –f
nsr_moss_save.exe –w
nsr_moss_save.exe –w <web application name>
nsr_moss_save.exe –u <site collection URL>
If no error messages appear, your credentials are probably specified correctly. But if
you get error messages or failures with SharePoint backups, you can update the
NetWorker SharePoint Service credentials.
To update or correct SharePoint credentials by using the NetWorker SharePoint
Service Configuration dialog box:
1. In the Domain\User Name field, specify the domain and username you use for
your Microsoft SharePoint Server administrator account.
2. In Password and Confirm Password, specify the password you use for your
Microsoft SharePoint Server administrator account.
3. Click OK to save your changes.
Specify temporary storage location

You can browse and select the temporary storage location in the NetWorker
SharePoint Service Configuration dialog box. The temporary storage location is a
temporary staging area and is reclaimed after recovery.
This area is used to:
◆ Temporarily store the backup data going to the NetWorker Server during backup.
◆ Temporarily store the data coming from the NetWorker Server during restore.
Sharepoint service picks the data from this area and updates the Sharepoint
databases.
To specify the staging area for SharePoint granular backups by using the NetWorker
SharePoint Service Configuration dialog box:
1. In Temporary Storage Location, specify the path for the staging area for
SharePoint granular backups.
The Temporary Storage Location must be a valid drive. A new folder or an
existing folder can be specified in that drive.
Note: Specifying a value in the size of file field does not have any effect on the
configuration process.
2. Click OK to save your changes.

The NetWorker SharePoint Service Configuration saves the staging location to the
Windows Registry.
Configuring NetWorker SharePoint services 77

Specify the restore lock type

You can specify the restore lock type in the NetWorker SharePoint Service
Configuration dialog box. The options are:
◆ Read unlocked/Write unlocked
◆ Read unlocked/Write locked
◆ Read locked/Write unlocked
◆ Read locked/Write locked
After restore, depending on the option selected, the read/write locks are enabled for
restored site collections. The option specified here is used as the default setting
throughout. However, the option can be changed from the NMM GUI using the
Recovery Options tab just before restore. The EMC NetWorker Module for Microsoft
Applications Release 2.2 SP1 Administration Guide provides details about the Recovery
Options tab.
Configuring Windows firewall settings

NMM automatically configures Windows firewall settings during installation. There
is no need to run the Security Configuration Wizard to create firewall exceptions for
the NMM client. The previous version of NMM, NetWorker VSS Client, required
running the SCW, and then saving the SCW settings to the configuration file
NetWorkerEXT.xml, which is no longer needed.
NMM settings can also be modified after installation:

1. Click Start > Control Panel > Add or Remove Programs.
2. Select NetWorker Module for Microsoft Applications, and then click Change.
Windows firewall exception error for irccd.exe

Occasionally, the following error message appears during installation:
“Unable to create a Windows Firewall exception for C:\Program
Files\Legato\nsr\rmagentps\client\bin\irccd.exe. File not
found.”
If this occurs, configure the firewall setting manually, and then validate the
configuration.
To configure the firewall:
1. Select Start > Control Panel > Add or Remove Programs.
3. In the Welcome to NetWorker Module for Microsoft Applications Maintenance
dialog box, click Next.
4. In the Windows Firewall window, select Configure the Windows Firewall.
5. Click Next until you finish the configuration wizard.
6. Click Start, and then click Control Panel.
7. Open Windows Firewall.
8. Click the Exceptions tab.
9. In the Programs and Services list, verify that EMC Replication Manager Client
for RMAgentPS appears and is selected:
• If the checkbox is not selected, select it.
• If there is no entry for EMC Replication Manager Client for RMAgentPS,
manually add it:
a. Click Add Program.
b. Click Browse.
c. Type C:\Program Files\Legato\nsr\rmagentps\client\bin\irccd.exe.
If NMM was installed on an another drive letter other than C:\, specify the
correct path to irccd.exe as needed.
d. Click OK.
Configuring Windows firewall settings 79

Manually creating NMM firewall exceptions

When NMM is installed on a NetWorker storage node, NMM firewall exceptions are
not created. This option is not provided by the installer. When the NetWorker Client
is used as a data mover, backups fail. If you are using Windows firewall and
installing NMM 2.2 SP1 on an existing storage node, create and manually add the
firewall exceptions listed in Table 13 on page 80.
Table 13 Windows firewall exceptions
Display name Program name
EMC NetWorker PowerSnap Service nsrpsd.exe
EMC NetWorker PowerSnap Mover Agent nsrsnapagent.exe
EMC NetWorker PowerSnap SnapCopy Agent nsrbragent.exe
EMC NetWorker NSRSnapBwrAgent process nsrsnapbwragent.exe
EMC NetWorker VSS Client Save Process nsrsnap_vss_save.exe
EMC NetWorker VSS Client Recover Process nsrsnap_vss_recover.exe
EMC NetWorker Client Configuration Server nsrcscd.exe
EMC NetWorker User winworkr.exe
EMC Replication Manager Client for RMAgentPS irccd.exe
To manually add the exceptions:

1. Select Start, and then select Control Panel and Add or Remove Programs.
3. When the Welcome to NetWorker Module for Microsoft Applications
Maintenance dialog box appears, click Next.
4. In the Windows Firewall window:
• For Windows Server 2008, click Allow a program through Windows Firewall.
• For Windows Server 2003, click Exceptions.
5. For both Windows Server 2008 and Windows Server 2003, type the pathname of
the program. All programs are located in C:\Program Files\Legato\nsr\bin,
except for irccd.exe, which is located in C:\Program
Files\Legato\nsr\rmagentps\client\bin.
For example, the pathname for:
• winworkr.exe is C:\Program Files\Legato\nsr\bin\winworkr.exe.
• irccd.exe is C:\Program Files\Legato\nsr\rmagentps\client\bin\irccd.exe.
6. Click Add Program.
Index
A N
add-on enablers 38 new authorization code 42
authorization code 41 NMC 47
NMM Firewall exceptions 65
utility 60
B
base enablers 38
BCVs 51 P
PowerSnap NetWorker security 47
production host 47
C
proxy host 47
CLARiiON array configuration 48
purchased edition 39
CLARiiON configuration file 48
copy protection violation error 39
create device group 51 R
registration period 40
Replication Manager port settings 61
D
rmagentps service 61
device group 51
duplicate enablers 39
S
sample commands 32
E
sample configuration file 48
enabler certificate 40
standalone method 30
establishing mirrors 51
SYMCLI 51
evaluating NetWorker software 39
Exchange server 60
T
temporary enabler 39
H
-help option 51
U
uninstall_nmm_silent_sample.cmd 35
I
utility 60
install_nmm_silent_sample.cmd 33
W
L Windows E_ACCESSDENIED error 62
License Manager software 42
licensing process 42
M
Microsoft System Center Configuration Manager 2007
server 34
Index

NetWorker Module For Microsoft Applications Release 2.2 SP1 Installation Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetWorker Module For Microsoft Applications Release 2.2 SP1 Installation Guide

Uploaded by

Copyright:

Available Formats

EMC® NetWorker®

Module for Microsoft Applications

Published April, 2010

Chapter 2 Installing the Software

Upgrading to NMM storage node ........................................................................ 27

Chapter 3 Silent Installation of the Software

Chapter 4 Licensing and Enabling the Software

Chapter 5 Configuring the Software

Changing Replication Manager port settings..................................................... 61

Related Related documents include:

◆ EMC NetWorker License Manager Seventh Edition Installation and Administration

This chapter includes the following sections:

Privileged user-level access

Table 1 Access privileges needed for NMM (page 1 of 2)

Resource Privileges needed

NetWorker Server • NetWorker Administrator

NetWorker Module for Microsoft • Windows Administrator

All applications protected by NMM such • Windows Administrator

Table 1 Access privileges needed for NMM (page 2 of 2)

Resource Privileges needed

Microsoft Office SharePoint Server (for • Windows Administrator

Network domain Windows Domain Administrator

Storage node servers Windows Administrator

Adding Exchange Server 2007 credentials

Microsoft SQL and SharePoint VSS Writers

Table 2 Installation services

Service names Service nicknames

NetWorker Remote Exec nsrexecd nsrexecd.exe

NetWorker PowerSnap Service nsrpsd nsrpsd.exe

Replication Manager Client for RMAgentPS rmagentps irccd.exe

Preinstallation checklist overview

Table 3 Checklist overview

“Generic checklist” on page 21

“CLARiiON checklist” on page 24

“Microsoft SharePoint checklist” on page 26

“Microsoft Exchange checklist” on page 27

Patches and hotfixes checklist

Preinstallation checklist overview 15

Microsoft hotfixes required for NMM 2.2 SP1

Table 4 Hotfixes required for NMM 2.2 SP1 (page 1 of 5)

Windows Windows Windows Windows Included

Volume shadowcopy service (VSS)

KB940349 X X VSS NA VSS update rollup package for Windows

KB951568 X VSS NA VSS-based backup operations may fail if

KB949391 X X VSS NA When VSS tries to delete hardware

KB943545 X X VSS NA The following error message is displayed

Table 4 Hotfixes required for NMM 2.2 SP1 (page 2 of 5)

Windows Windows Windows Windows Included

When you shut down a computer that is

KB927673 X X Exchange NA Windows Server 2003 Post-Service Pack 1

KB971534 X X Exchange NA Update Rollup 1.

KB936008 X X SP1, SP2, R2, Volume GUIDs become invalid in Windows

KB908980 X X EMC NA For Windows Server 2003 configurations

KB916048 X X EMC NA Hotfix for any host running Microsoft

KB903081 X X Symmetrix NA Hotfix

EMC Replication Manager SP1

Patches and hotfixes checklist 17

Table 4 Hotfixes required for NMM 2.2 SP1 (page 3 of 5)

Windows Windows Windows Windows Included

KB898790 X X RM SP1 NA Microsoft hotfix

KB912063 X X RM SP1 NA Microsoft hotfix

KB891957 X X RM SP1 NA Microsoft hotfix