emc networker module for microsoft 9.0 installation guide · upgrading the client operating system...

EMC® NetWorker® Module forMicrosoftVersion 9.0

Installation Guide302-001-749

REV 04

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

Published December, 2015

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

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

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

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

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC NetWorker Module for Microsoft 9.0 Installation Guide

5

7

9

Introduction 13

Overview....................................................................................................... 14Requirements................................................................................................14

Requirement when restoring previous NMM release backups........... 15Supported Microsoft Windows systems and features....................... 15Supported Microsoft .NET Framework versions................................. 15Supported NetWorker server and client versions.............................. 16Hardware requirements....................................................................17License requirements.......................................................................18Authorization requirements..............................................................18Microsoft hotfixes............................................................................ 18

Exchange Server-specific tasks......................................................................19Exchange administrator configuration tool....................................... 19MAPI client and Collaboration Data Objects..................................... 20Exchange backup prerequisites........................................................20For Restricted Datazones environments............................................21

Supported Network Configurations 23

Simple LAN-based environment.................................................................... 24LAN-free dedicated storage node environment.............................................. 25

Configuration Checks and Installation 27

Accessing the installation files...................................................................... 28Running preconfiguration checks and installing the software........................ 28Installing NMM in MSCS and MSFCS environments........................................31Installing NMM on Windows Server Core........................................................31Identifying or diagnosing system configuration issues...................................32Uninstalling or changing installation options.................................................32Upgrading NMM............................................................................................ 33

Upgrading the client operating system from Windows Server 2012 to alater version.....................................................................................33Upgrading from NMM 3.0 or later in a stand-alone environment....... 34Upgrading from NMM 3.0 or later in a clustered environment orupgrade from an earlier release in a stand-alone or clusteredenvironment.................................................................................... 34Upgrading from NME or NMSQL........................................................35Upgrading to NMM with a dedicated storage node........................... 35

Silent Installation 37

Figures

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

Chapter 4

CONTENTS

EMC NetWorker Module for Microsoft 9.0 Installation Guide 3

Silent installation of NMM............................................................................. 38Commands for silent installation of NMM.........................................38

Silent removal of NMM.................................................................................. 40Silent upgrade of NMM..................................................................................40Silent modification of NMM........................................................................... 40Sample scripts for silent installation and removal of NMM............................ 41Installing and removing NMM by using an SCCM 2007 Server........................41

Installing NMM using an SCCM 2007 server..................................... 41Uninstalling NMM using an SCCM 2007 server................................. 42

Troubleshooting the installation....................................................................42Using non-English characters in installation path............................. 42

Configuration Tasks 43

Configuring a dedicated storage node for NMM............................................. 44Configuring NMM Proxy Recovery Agent for Hyper-V FLR.................................44Set up events notifications and find errors.................................................... 45Removing directives after migrating to NMM..................................................45Troubleshooting installation issues...............................................................46

Required Microsoft Hotfixes 49

Hotfix updates required for backup and recovery of all applications.............. 50Hotfix updates required for VSS backup and recovery....................................51Hotfix updates required for Exchange Server backup and recovery................ 52Hotfix updates required for SharePoint Server backup and recovery.............. 52

Chapter 5

Appendix A

CONTENTS


Exchange admin configuration tool................................................................................19Simple LAN-based environment.....................................................................................24LAN-free environment with a DSN.................................................................................. 26

123

FIGURES


FIGURES


Revision history............................................................................................................... 9Style conventions.......................................................................................................... 10NMM supported Microsoft .NET Framework versions...................................................... 15NMM support matrix for NetWorker server versions........................................................16NMM support matrix for NetWorker client versions.........................................................16Exchange server hardware requirements ...................................................................... 17Permissions configured by the Exchange administrator configuration tool .................... 19NMM installer variables................................................................................................. 39Commands for NMM installation ...................................................................................39Sample scripts for silent installation..............................................................................41Notifications and errors................................................................................................. 45Hotfixes required for NMM general backup and recovery................................................50Hotfixes required for NMMfor VSS backup and recovery.................................................51Hotfixes required for NMM for Exchange Server backup and recovery.............................52Hotfixes required for NMM for SharePoint Server backup and recovery...........................52

123456789101112131415

TABLES


TABLES


Preface

As part of an effort to improve its product lines, EMC periodically releases revisions of itssoftware and hardware. Therefore, some functions described in this document might notbe supported by all versions of the software or hardware currently in use. The productrelease notes provide the most up-to-date information on product features.

Contact your EMC technical support professional if a product does not function correctlyor does not function as described in this document.

Note

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

PurposeThis guide contains information about how to install and configure the EMC

® NetWorker

®

Module for Microsoft (NMM) Release 9.0 software.

Note

The EMC NetWorker Module for Microsoft Administration Guide supplements the backupand recovery procedures described in this guide and must be referred to when performingapplication-specific tasks. Ensure to download a copy of the EMC NetWorker Module forMicrosoft Administration Guide from EMC Online Support (support.emc.com) before usingthis guide.

AudienceThis guide is part of the NetWorker Module for Microsoft documentation set, and isintended for use by system administrators during the setup and maintenance of theproduct.

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

l EMC NetWorker software

l EMC NetWorker backup management

l Microsoft Volume Shadow Copy Service (VSS) technology

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

Table 1 Revision history

Revision Date Description

04 December 16, 2015 Updated to incorporate technical feedback fromengineering team.

03 November 20,2015

Updated Table 5 in "Supported NetWorker server andclient versions" section:

l Replaced "NetWorker server 8.2 SP1 or later" with"NetWorker client 8.2 SP1 or later"

l Replaced "NetWorker server 8.2" with "NetWorkerclient 8.2"


https://support.emc.com/

https://support.emc.com/

http://support.emc.com

Table 1 Revision history (continued)

Revision Date Description

Updated the note after Table 5 in "Supported NetWorkerserver and client versions" section.

02 September 29,2015

Updated Table 4 in "Supported NetWorker server andclient versions" section.

01 September 24,2015

First release of this document for EMC®

NetWorker®

Module for Microsoft 9.0.

Related documentationThe NMM documentation set includes the following publications:

l EMC NetWorker Module for Microsoft Release Notes

l EMC NetWorker Module for Microsoft Administration Guide

l EMC NetWorker Module for Microsoft Installation Guide

l EMC NetWorker Module for Microsoft for SQL and SharePoint VSS User Guide

l EMC NetWorker Module for Microsoft for SQL VDI User Guide

l EMC NetWorker Module for Microsoft for Exchange VSS User Guide

l EMC EMC NetWorker Module for Microsoft for Hyper-V VSS User Guide

l EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution UserGuide

l EMC NetWorker Performing Backup and Recovery of SharePoint Server by using NetWorkerModule for Microsoft SQL VDI solution Technical Notes

l EMC NetWorker Performing Exchange Server Granular Recovery by using NetWorkerModule for Microsoft with Ontrack PowerControls Technical Notes

l EMC NetWorker SharePoint BLOB Backup and Recovery by using NetWorker Module forMicrosoft and Metalogix StoragePoint Technical Notes

l NetWorker documentation set

Special notice conventions that are used in this documentEMC uses the following conventions for special notices:

NOTICE

Addresses practices that are not related to personal injury.

Note

Presents information that is important, but not hazard-related.

Typographical conventionsEMC uses the following type style conventions in this document:

Table 2 Style conventions

Bold Used for names of interface elements, such as names of buttons, fields,tab names, and menu paths (what the user specifically selects orclicks)

Preface


Table 2 Style conventions (continued)

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

Monospace Used for:

l System code

l System output, such as an error message or script

l Pathnames, file names, prompts, and syntax

l Commands and options

Monospace italic Used for variables

Monospace bold Used for user input

[ ] Square brackets enclose optional values

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

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

... Ellipses indicate non-essential information that is omitted from theexample

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

Product informationFor documentation, release notes, software updates, or information about EMC products,go to EMC Online Support at https://support.emc.com.

Technical supportGo to EMC Online Support and click Service Center. Several options for contacting EMCTechnical Support appear on the site. Note that to open a service request, you must havea valid support agreement. Contact your EMC sales representative for details aboutobtaining a valid support agreement or with questions about your account.

Online communitiesGo to EMC Community Network at https://community.emc.com for peer contacts,conversations, and content on product support and solutions. Interactively engage onlinewith customers, partners, and certified professionals for all EMC products.

Your commentsYour suggestions help to improve the accuracy, organization, and overall quality of theuser publications. Send your opinions of this document to [email protected].

Preface


https://support.emc.com

https://community.emc.com

mailto:[email protected]

Preface


CHAPTER 1

Introduction

l Overview............................................................................................................... 14l Requirements........................................................................................................14l Exchange Server-specific tasks..............................................................................19

Introduction 13

OverviewThe EMC® NetWorker® Module for Microsoft (NMM) release 9.0 software providesbackup and recovery support for Microsoft applications. You can use NMM to back upand recover:

l Microsoft SQL Server

l Microsoft SharePoint Server

l Microsoft Exchange Server

l Microsoft Hyper-V Server

Review the following information before installing and using NMM:

l The NMM installation includes Volume Shadow Copy Service (VSS) software. Do notuse a VSS solution other than the one installed with NMM. Data loss can occur if youuse a different VSS solution to delete shadow copies that NMM created. Restoring anapplication with a different VSS solution might prevent the application from beingrestored with NMM.

l After installing the NMM client software, if you perform a save operation and thenmove to a non-NMM client, you cannot browse the save sets created by the NMMclient with the non-NMM client. Use the NMM software to recover backups that wereperformed with NMM. When the NMM software is not installed, the NetWorker Userapplication cannot browse NMM save sets. This is because the NetWorker client canonly recognize the client file index entry format that is created with an NMM clientwhen displayed in NMM.

l Backing up a Microsoft application server with multiple backup products can result inimproper behavior of the products. Do not use other products when using NMM toback up a Microsoft application server.

RequirementsReview the information in this section before continuing with the NMM installation.

The NetWorker client, NetWorker storage node, NetWorker Extended client (if required),and NMM must be installed separately. Install the NetWorker Extended client only whenupgrading from an earlier release.

The EMC NetWorker Installation Guide describes how to install the NetWorker client,NetWorker storage node, and NetWorker Extended client.

Ensure that you have installed the required components in the following sequence on theapplication host:

1. NetWorker client: lgtoclnt-9.0.0.2 or select client from NetWorker-9.0.0.2 in NetWorkerpackage.

2. NetWorker storage node (if applicable): Select storage node from NetWorker-9.0.0.2 inNetWorker package.

3. NetWorker Extended client (if required): Select lgtoxtdclnt-9.0.0.2 in NetWorkerpackage

4. NMM software

NMM is an application client and must not be installed on a NetWorker server.

Introduction


Note

The EMC NetWorker Online Software Compatibility Guide contains the most up-to-dateinformation about NMM compatibility.

Requirement when restoring previous NMM release backupsIf you are using an NMM release earlier than NMM 9.0 (for example NMM 3.0, NMM 8.2SP1, and so on) and plan to recover the existing backups using NMM 9.0, ensure that youhave installed the NetWorker Extended client (select "lgtoxtdclnt-9.0.0.2" from NetWorkerpackage) along with the NetWorker client ("lgtoclnt-9.0.0.2" or select "client" from"NetWorker-9.0.0.2" from NetWorker package) before installing NMM.

Note

The NMM installer gives an error if the NetWorker Extended client is not installed beforethe "Restore previous NMM release backups" option is selected during the installation.

Supported Microsoft Windows systems and featuresThis section lists the various Microsoft Windows versions and Microsoft Windows-relatedfeatures that NMM 9.0 supports.

NMM does not support:

l Windows IA64 editions

l Windows Small Business Server editions

l SS Hardware Provider based proxy backup of Windows dynamic disks

l Single Instance Storage (SIS)

Supported Microsoft .NET Framework versionsThe following table lists the versions of the Microsoft .NET Framework that NMMsupports.

Table 3 NMM supported Microsoft .NET Framework versions

WindowsServer version

Supported .NET versions

NMM 9.0 support NMM 8.2 SP1support

NMM 8.2support

NMM 3.0 SP1support

NMM 3.0support

Windows Server2012 R2

.NET 4.5.1 Yes Yes Yes Yes OS notsupported

Windows Server2012

.NET 4.5.1 Yes Yes Yes Yes Yes

.NET 4.5 Yes Yes Yes Yes Yes

Windows Server2008 and 2008R2

.NET 4.5.1 Yes Yes Yes Yes Yes



Windows Server2003 and 2003R2

.NET 4.0 No No No Yes (SQL VDIonly)

No

Introduction

Requirement when restoring previous NMM release backups 15

For Windows Server 2012 R2, Microsoft supports only .NET 4.5.1. The Microsoftdocumentation provides details about supported Windows Server and .NET Frameworkversions.

Supported NetWorker server and client versionsThe following tables provide the NMM support matrix for NetWorker server and clientversions. Refer to the individual NMM release sections of the EMC NetWorker OnlineSoftware Compatibility Guide for more specific details.

Table 4 NMM support matrix for NetWorker server versions

NetWorker Serverversion

NMM 2.4 NMM 2.4SP1

NMM 3.0 NMM 3.0SP1

NMM 8.2 NMM 8.2SP1

NMM 9.0

NetWorker server 9.0 No No No No Yes Yes Yes

NetWorker server 8.2 SP1 No No No Yes Yes Yes No

NetWorker server 8.2 orlater

No No Yes Yes Yes Yes No


No Yes Yes Yes Yes Yes No


Yes Yes Yes Yes Yes Yes No

Table 5 NMM support matrix for NetWorker client versions

NetWorker client version NMM 2.4 NMM 2.4SP1

NMM 3.0 NMM 3.0SP1

NMM 8.2 NMM 8.2SP1

NMM 9.0

NetWorker client 9.0 No No No No No No Yes

NetWorker client 8.2 SP1 No No No No No Yes No

NetWorker client 8.2 No No No No Yes No No

NetWorker client 8.1 SP1 orlater

No No No Yes No No No

NetWorker client 8.1 No No Yes No No No No

NetWorker client 8.0 orlater

Yes Yes No No No No No

Note the following considerations:

l Later (for example, NetWorker client 8.1 SP1 or later) applies to:

n Service packs that are released after a respective NetWorker server or clientrelease, or NMM release.

n Cumulative releases for various service packs. For example, the cumulativereleases NMM 8.2.1.6, NMM 8.2.1.7, and so on apply for NMM 8.2 SP1 or later.

l The NetWorker client versus NMM release mapping must be the same. For example, ifyou are using NetWorker client 8.2.1.8, then you must use NMM 8.2.1.8.

l For Windows Server 2012 R2 protection, it is strongly recommended that you upgradeto NMM 8.2 SP1 or later, which contains the latest fixes related to Microsoft updatesfor Windows Server.

Introduction


Install the NetWorker software on the host before installing the NMM software. If the hostis a DSN, install the NetWorker Storage node software.

Hardware requirementsThe minimum hardware requirements for the application host where NMM is installedare:

l CPU: 2.0 GHz

l Physical memory: 4 GB

l Host architecture:

n Exchange Server, SharePoint Server, Active Directory, and Hyper-V: x64 systemsonly

n SQL Server: x64 and x86 systems

Exchange server hardware requirementsThis topic describes the additional hardware and system resources that are required forExchange server.

Exchange places additional demands on computer hardware and resources beyond thebase requirements for NMM. Ensure that the computer running Exchange server meets orexceeds Microsoft hardware recommendations.

The following table describes the recommended hardware requirements for Exchangeserver.

Table 6 Exchange server hardware requirements

Requirement Description

Memory (RAM) Exchange server requires additional memory (RAM). Start with 8 GB ofRAM. The amount of additional or total memory that is required dependson current system performance with existing memory:

l If the memory resources are strained and performance is slow withnormal operations of NMM, then add significantly more memory tosupport Exchange operations.

l If the memory performance is adequate with normal operations ofNMM, then additional memory might not be required to supportExchange operations.

Disk staging area Exchange server requires additional disk space for a disk staging area tohold writes to the Exchange database and log files.

Hyper-V requirementsFor optimal performance, ensure that the Hyper-V environment meets the followingsystem requirements.

Hyper-V proxy node in a single proxy environment:

l 1 Gb/s LAN connection to DD, or a minimum 100 MB/s transfer rate

l 1 GHz CPU (single core)

l 512 MB RAM

Hyper-V proxy node in a multi-proxy environment:

Introduction

Hardware requirements 17

l Shared 10 Gb/s LAN connection to DD, or a 400 MB/s transfer rate

l 4 GHz CPU total (or 2 GHz dual core)

l 2 GB RAM

These resources must be available on the Hyper-V proxy node during the backup windowonly for NetWorker/NMM purposes.

When planning and allocation resources, do not exceed 70% utilization of rated capacityof any hardware element (CPU, RAM, backplane, NIC).

License requirementsThis section provides a brief overview of the license requirements for NMM. The EMCNetWorker Licensing Guide provides details.

l For physical server environments, only one NMM license is required to managemultiple instances of supported applications on the same server (physical host).

l For virtual server environments, one NMM license is required for each applicationtype (SQL, Exchange, SharePoint, Hyper-V) per physical host, which can be usedmultiple times and within all the virtual guests on a single physical server for thatapplication type.

l Requires one license per active node in a cluster environment (active-active requirestwo licenses).

l Licenses for NME (Exchange) and NMSQL can be used with NMM. This ensures thatcustomers can upgrade from NME (which is now end-of-sale) to NMM and avoidlicensing changes.

l The reverse is not true. NMM licenses cannot be used with the legacy modules forExchange and SQL.

Authorization requirementsThe configuration and operation of NMM backups and recoveries require authorizedaccess to data for the user who performs the configuration. The EMC NetWorker Module forMicrosoft Administration Guide provides details about the privileges to enable.

Microsoft hotfixesFor NMM to function correctly with each supported Microsoft application, install therequired updates and hotfixes from the Microsoft website.

l Install the latest hotfixes for Microsoft Windows operating system.

l Install the .NET Framework and the following .NET Framework updates:

n KB2604121: http://support.microsoft.com/kb/2604121



n KB2736428: http://support.microsoft.com/kb/KB2736428





n KB2468871: http://support.microsoft.com/kb/2468871Without these updates, backups will fail.

Introduction


http://support.microsoft.com/kb/2604121



http://support.microsoft.com/kb/KB2736428






l Each Microsoft application that is protected by the NMM software. Required MicrosoftHotfixes on page 49 provides the list of specific hotfixes that are required forapplication backup and recovery.

Exchange Server-specific tasksYou must complete certain configuration tasks before you install the NetWorker clientand the NMM software for Exchange Server backup and recovery.

Exchange administrator configuration toolThe Exchange administrator configuration tool enables you to create or reset thepermissions of an account with the necessary privileges to perform backup and recoveryoperation on an Exchange Server. After installing NMM, run the tool to create a newaccount, modify, validate, and update the existing account privileges.

You can use the Exchange administrator configuration tool to perform the following tasks:

l Configure Admin User—Create an NMM Exchange administrator account andconfigure the permissions and memberships to perform an Exchange databaserestore and granular level recovery.

l Update Admin Password—Modify the NMM Exchange administrator accountpassword and update the registry credentials.

l Validate an existing admin—Verify that an existing NMM Exchange administratoraccount is correctly configured.

Note

To use the tool, you must be logged in with Domain Administrator permissions.

The following figure shows the Exchange administrator configuration tool landing page.

Figure 1 Exchange admin configuration tool

To create an NMM Exchange administrator account, the tool performs the following steps:

l Creates an Active Directory user account.

l Creates a custom Exchange security group called EMC NMM Exchange Admin Roles.

l Adds the user account to the groups listed in the following table:

Table 7 Permissions configured by the Exchange administrator configuration tool

User group Exchange Server role

Security group memberships on NMM Clientcomputer

Local Administrator

Introduction

Exchange Server-specific tasks 19

Table 7 Permissions configured by the Exchange administrator configuration tool (continued)

User group Exchange Server role

Security group memberships on DomainController

Backup OperatorsRemote Desktop Users

Exchange Security Group memberships Exchange Servers

EMC NMM Exchange Admin Roles, which includes:

n Exchange Roles:

n Database Copies

n Databases

n Disaster Recovery

n Mailbox Import Export

n Mail Recipient Creation

n Mail Recipients

n View-Only Configuration

n View-Only Recipients

l Assigns the "Mailbox Import Export" management role to the user.

l Creates an Exchange mailbox.

l Assigns Send-As and Receive-As rights.

l Registers the user account for backup and recovery on Exchange servers where NMMis installed.

MAPI client and Collaboration Data ObjectsThis topic describes the Exchange Server 2010 and 2013 requirements for the MicrosoftExchange Server MAPI Client and Collaboration Data Objects 1.2.1 Kit.

For RDB and GLR support, Exchange Server requires the MAPI/CDO 1.2.1 kit. ExchangeServer 2010 requires build 6.5.8244.0. Exchange Server 2013 requires build 6.5.8353.0.Exchange Server 2016 does not support MAPI.

The Exchange Server 2010 and 2013 software does not include the MAPI client librariesand CDO. You can download these applications from Microsoft’s website. For informationon downloading and installing this package, search for “Microsoft Exchange MAPI Clientand Collaboration Data Objects” on the Microsoft Download Center website.

Note

The EMC NetWorker Online Software Compatibility Guide contains information about thelatest version of the MAPI and CDO kit that NMM supports.

Exchange backup prerequisitesThis topic describes the required prerequisites for backup of Exchange server using NMM.

Ensure that the following prerequisites are met before performing backup procedures:

l Install the .NET Framework.

Introduction


l Install the hotfixes and cumulative updates that are listed in the EMC NetWorkerModule for Microsoft Installation Guide.

l Ensure that you use the same version of Exchange Servers, Windows Servers, andservice packs or cumulative updates.

l Install the NetWorker client and NMM software on all Exchange servers that are a partof a backup.

For Restricted Datazones environmentsNMM supports NetWorker Restricted Datazones (RDZ). An RDZ adds an additionalpermission checking layer, which ensures that RDZ administrators accessing areas thathave not been specifically coded for this feature, by default, do not have access to thoseareas.

To perform DAG backups and recoveries in an RDZ, you must configure additionalpermissions and configuration. The EMC NetWorker Module for Microsoft AdministrationGuide provides details about the required permissions and configuration. The EMCNetWorker Administration Guide provides detailed information about the NetWorker RDZfeature.

Introduction

For Restricted Datazones environments 21

Introduction


CHAPTER 2

Supported Network Configurations

l Simple LAN-based environment............................................................................ 24l LAN-free dedicated storage node environment...................................................... 25

Supported Network Configurations 23

Simple LAN-based environmentIn a LAN-based environment, NetWorker stores the production data on a storage areanetwork (SAN) or direct-attached storage (DAS). The data path to the NetWorker storagenode is over a LAN. You install the NMM software on the application server host.

The following figure shows a simple LAN-based storage area network with a supportedNetWorker server, storage node, and clients.

The data moves as follows:

1. The NetWorker server contacts the application server to start the backup process.

2. The application server uses NMM to create a snapshot of the data on the primarystorage volume.The following figure shows example snapshots S1 through S5.

Figure 2 Simple LAN-based environment

LAN

NetWorker storagenode

Primary storage

Traditionalstorage

NetWorker server

Application server(NMM and NetWorker client)

SAN

S1 S2

S3S4

S5

3. The application server transfers the data from the snapshot over the LAN and onto abackup medium such as a file type disk, advanced file type disk, tape, Data Domaindevice, or Avamar deduplication node.

Note

Avamar deduplication nodes are only supported with existing NetWorker 8.2 SP1 orearlier upgrades.For Exchange and Hyper-V setups, only advanced file type disk and Data Domaindevices are supported.



LAN-free dedicated storage node environmentA dedicated storage node (DSN) is a storage node host that can only backup the data thatthe host owns.

You can configure an Application Server as a DSN to support the following operations:

l LAN-free backups without a separate NMM proxy node.

l Backups to the SAN devices attached directly to an NMM client host.

l Backups to the SAN devices attached to an NMM proxy node.

NOTICE

DSN support is available for all applications, however for Exchange Server 2010 DAGa Regular Storage node (RSN) license is required.

DSN support for NMM requires the following:

l A NetWorker storage node device. First install the NetWorker storage node beforeinstalling NMM.

l A NetWorker data protection policy.

l A storage node device on the NetWorker Client resource that uses NetWorker mediapool selection criteria.

l Backup device that is configured on the DSN.

l A backup device on the NetWorker server host, as required for bootstrap data, clientfile indexes, and Cover save set entries.

Note

When not using a DSN device, ensure that you manually create a default device.

The following figure illustrates the data movement in a LAN-free environment with a DSN:


LAN-free dedicated storage node environment 25

Figure 3 LAN-free environment with a DSN

LAN

Primary storage

Traditionalstorage

NetWorker Server

Application server(NMM and NetWorker Storage Node)

SAN

GEN-001500

S1 S2

S3S4

S5

1. The NetWorker server starts the process by contacting the application server. NMMsoftware is installed on the application server, and the application server isconfigured as a NetWorker DSN.

2. The NMM software on the application server, with other software, creates a snapshotof the data on the primary storage volume, and makes the snapshot available to theDSN, which also resides on the application server.The NetWorker server and the application server communicate over the LAN.However, NetWorker does not transfer the data across the LAN because the backupmedium and storage media are connected to the SAN.

3. The DSN stores the snapshot data on a conventional backup medium, such as a filetype disk, advanced file type disk, or tape.The preceding figure shows example snapshots S1 through S5 created on the storagevolume.

Note

If Dedicated Storage Node is set to Yes, the storage node host does not allow any datafrom any other host.



CHAPTER 3

Configuration Checks and Installation

l Accessing the installation files.............................................................................. 28l Running preconfiguration checks and installing the software................................ 28l Installing NMM in MSCS and MSFCS environments................................................31l Installing NMM on Windows Server Core................................................................31l Identifying or diagnosing system configuration issues...........................................32l Uninstalling or changing installation options.........................................................32l Upgrading NMM.................................................................................................... 33

Configuration Checks and Installation 27

Accessing the installation filesYou can access the installation files from a DVD disk or the EMC website.

l To access the NMM software from a local DVD disk:

1. Log in as administrator or equivalent on the NetWorker client.

2. Insert the NMM DVD disk into the DVD drive.

3. Run NWVSS.exe directly from the DVD.

l To access the NMM software from EMC Online Support:

1. Log in as administrator or equivalent on the NetWorker client.

2. Go to EMC Online Support at http://support.emc.com.

3. Browse to the Downloads for NetWorker Module for Microsoft page.

4. Download the NMM software .zip file, either the 32-bit or 64-bit version asappropriate for the system, to a temporary folder that you create.

5. Extract the .zip file to a folder on the client.

Running preconfiguration checks and installing the softwareProcedure

1. Review the Introduction chapter and ensure that the environment meets therequirements.

2. Run NWVSS.exe.

The installation wizard starts. The wizard installs the NMM software in the same pathwhere you installed the NetWorker client or NetWorker storage node software.

3. In the Wizard Welcome page, read the license terms and agreements carefully. Selectthe I agree to the license terms and agreements option and click Next.

The Configuration Checks Option page appears. The System Configuration Checkerverifies that ths setup is correctly configured for backup and recovery.

4. To proceed with the NMM installation process and skip the System ConfigurationChecker, leave the Run System Configuration Checker option unselected. and clickNext.

The Wizard Firewall page appears.

5. To run the System Configuration Checker before the NMM installation process, selectRun System Configuration Checker option.

The Application Host option is selected automatically. The System ConfigurationChecker runs the configuration checks on an application server. These checks arerelated to the operating system, software components, the subsystem, and genericconditions that are required for NMM backup and recovery.

6. Select an application, and then click Check.

l Microsoft Exchange Server

l Microsoft SharePoint Server

l Microsoft SQL Server

l Microsoft Hyper-V Server



http://support.emc.com

The Wizard Progress page appears. The wizard installs the System ConfigurationChecker and performs the configuration checks. This can take some time dependingon your setup.

7. When the wizard completes the configuration checks, click Next.

The Result of Configuration Checks page appears.

8. Review the details on the Result of Configuration Checks page.

This page lists the number of checks that have passed, failed, or have warnings. Youmust correct the checks that have failed and review the ones that have warnings toensure that NMM does not encounter problems during backup and recovery of data.NMM saves this report as results.html in the local temporary folder directory C:\Users\Administrator.NMMEMC\AppData\Local\Temp\2\EmcCfgChk\results.html of the user who is running the NMM installation wizard. NMM alsosaves the configuration check log as cfgchk_log.txt in this folder. Click Opendetailed report to view the saved report.

l To eliminate errors and warnings in the setup, click Back. Make the requiredchanges and click Next to run the System Configuration Checker again.

l To ignore the errors and warnings and continue with the installation process, clickNext. Only choose this option in cases when the configuration checker reports donot relate to your setup or requirements.

The Configure Windows Firewall page appears.

9. Select either of the following and click Next:

l Configure the Windows Firewall - The installer adds exceptions for NMM on theWindows firewall so that NMM can communicate through any Windows firewallthat may be present on the Windows host.

l Do not configure the Windows Firewall - You must manually specify NMMexceptions if you select this option.

The Wizard NMM Options page appears.

10. Select the required options and click Next.

l Restore of NMM 8.2.x and Earlier Backups (VSS workflows) - Select the Restore ofNMM 8.2.x and Earlier Backups (VSS workflows) option if you are upgrading froma previous NMM release, for example NMM 3.0.1 or 8.2, and plan to recoverexisting backups of Exchange Server, SQL Server, SharePoint Server, and Hyper-Vby using NMM 9.0 (VSS workflows).

Note

If you have used Avamar for deduplication with NMM 8.2.x and earlier releases,ensure to install Avamar from the Avamar client package before upgrading to NMM9.0. NMM 9.0 does not support Avamar node backup and recovery.

Selecting the Restore of NMM 8.2.x and Earlier Backups (VSS workflows) option:

n Installs the NMM release 8.2 SP1 binaries, required to perform restoreoperations.

n Installs the Eldos driver.

n Creates a shortcut at the Start menu called Restore previous NMM releasebackups, using which you can start the NMM GUI to recover the older backups.

n Creates an entry in the Registry.


Running preconfiguration checks and installing the software 29

Note

Do not select this option if you are using NMM to backup SQL Server (VDI) and planto upgrade to NMM 9.0.

l SharePoint Granular Recovery - Select the SharePoint Granular Recovery toperform SharePoint granular level recovery.The GLR Options page appears. The NMM installer selects a default path for theWriteCache Location, MountPoint Location, and Hyper-V VHD Mount PointLocation. To change the write cache location or mount point location, click (...),select the location, and click OK.

l SQL SSMS Plug-in - Select the SQL SSMS Plug-in option to perform SQL Server VDIbackup and recovery from the SQL Server Management Studio. Optionally, selectthe Enable Backup Tab for Ad-hoc Backup and Enable Script in Backup Windowoptions.select the SQL SSMS Plug-in option.Selecting the SQL SSMS Plug-in option installs the EMC NetWorker Backup tab inthe SQL Server Management Studio GUI.

l BBB MountPoint Location - NMM uses the Block Based Backup mount pointlocation to mount backed up data from media for granular level recoveries forExchange Server and Hyper-V Server. The NMM installation wizard displays adefault mount point path. To change the Block Based Backup mount pointlocation, click (...), select the location, and click OK. In the installation wizard,click Next.

Note

If either the Restore of NMM 8.2.x and Earlier Backups (VSS workflows) or SharePointGranular recovery option is selected, a reboot of the application server is required.

11. Click Install.

The Wizard Progress page appears and the installation begins. The installation cantake several minutes.

12. For Exchange environments, if you are logged in with Domain Administrator privileges,the NMM Exchange Admin Configuration tool starts. If you are not logged in withDomain Administrator privileges, a message displays prompting you to log in withthese privileges.

Use the NMM Exchange Admin Configuration tool to:

l Create a new administrator account.

l Reset the admin password.

l Register an administrator.

l Validate an existing admin.

Click OK to return to the NMM installation wizard.

The Wizard Completing page appears.

13. On the Wizard Completing page:

l If you did not select the SharePoint Granular Recovery or SQL SSMS Plug-inoption, click Finish to complete the installation and exit the installation wizard.To view the setup log file, click the link in the results area of the page. This file isstored in the NetWorker Module for Microsoft folder in the localtemporary folder directory of the user who is running the NMM installation wizard.



l If you selected the SharePoint Granular Recovery or SQL SSMS plug-in SharePointGranular Recovery or SQL SSMS Plug-in option, click Finish to complete theinstallation.

14. Restart the system.

15. Enable and register the NMM software. The EMC NetWorker Licensing Guide providesdetails.

Installing NMM in MSCS and MSFCS environmentsYou can install the NMM software in Microsoft Cluster Service (MSCS) and MicrosoftFailover Cluster Service (MSFCS) environments.

Procedure

1. If required, ensure that Microsoft Distributed Transaction Coordinator (MSDTC)software is installed and running.

The EMC NetWorker Module for Microsoft Administration Guide provides details aboutwhen the MSDTC software must be installed and running. The EMC Solutions EnablerInstallation Guide provides details about the MSDTC.

2. Install NetWorker client ("lgtoclnt-9.0.0.2" or select "client" from "NetWorker-9.0.0.2"from NetWorker package) on each physical node of the cluster.

3. Install the NMM software on the private disk of each physical node. Runningpreconfiguration checks and installing the software on page 28 provides details.

4. Configure each physical node as a client resource on the NetWorker Server, asdescribed in the application user guide.

5. In the Remote Access attribute of each virtual client resource, type the names of thephysical nodes, as described in the application user guide.

6. Configure privileges for each physical node on the NetWorker server:

a. In the Users attribute of the Application > Administrators user group, add thefollowing values on a separate line for each physical node in the cluster:

user=administrator,host=VSS_cluster_node

user=system,host=VSS_cluster_node

where VSS_cluster_node is the DNS hostname of the physical node.

b. Click OK.

The EMC NetWorker Module for Microsoft Administration Guide provides moreinformation about configuring a clustered client resource.

Installing NMM on Windows Server CoreWhen you install NMM on Windows 2008 SP2, 2008 R2, 2012, or 2012 R2 Server Core,the installation process does not install an NMM GUI.

Procedure

1. Ensure that you installed the NetWorker client ("lgtoclnt-9.0.0.2" or select "client"from "NetWorker-9.0.0.2" from NetWorker package) software on Windows 2008 SP2,2008 R2, 2012 or 2012 R2 Server Core.


Installing NMM in MSCS and MSFCS environments 31

2. Access the NMM installation files as described in Accessing the installation files onpage 28.

If the installation files are on a remote host, do one of the following:

l Use the ncet use command to mount the remote file system.

l Copy the NMM installation files to Windows 2008 SP2, 2008 R2, 2012, or 2012 R2Server Core by using FTP or a general access method.

3. Run NWVSS.exe in the networkr directory to start the NMM installation.

Note

Do not use autorun.exe to install the NMM software.

4. Follow the wizard to install the NMM software.

Running preconfiguration checks and installing the software on page 28 providesdetails.

Identifying or diagnosing system configuration issuesThe NMM installer provides the System Configuration Checker to help identify ordiagnose any configuration or environment issues in the system configuration. Run theSystem Configuration Checker to prevent configuration errors that might lead to failure indata backup or data recovery of:

l Application host (operating system environment)

l Microsoft Exchange

l Microsoft Hyper-V

l Microsoft SharePoint

l Microsoft SQL

Uninstalling or changing installation optionsYou can run the Setup program (NWVSS.exe) in maintenance mode to either remove theNMM software or change the password for the Exchange Server; change the firewallsettings for the client; select the SharePoint granular recovery option; or select the SQLSSMS plug-in option.

NMM is not uninstalled during uninstallation of the NetWorker client. You must firstuninstall the NetWorker client and then uninstall the NMM client.

Procedure

1. On the NMM client, log in as a user with administrative access.

2. Perform one of the following to run the Setup program:

l From the command line, run the NWVSS.exe file.

l From the Microsoft Windows menus:

a. Select Start > Settings > Control Panel > Programs > Programs and Features.

b. Select NetWorker Module for Microsoft.

c. Click Change.



3. In the Welcome to NetWorker Module for Microsoft Maintenance window, click Next.

4. In the Maintenance Type window, select the type of change to perform:

l Select the Change option to change any of the following:

n Password for Exchange Server

n Firewall settings for NMM exceptions

n SharePoint granular recovery option

n SQL SSMS plug-in, including the Backup tab and the Script option in the SSMSGUI.

Note

To add any new feature to SSMS plug-in, for example the script backup tab orrestore tab, you must uninstall and re-install the SSMS plug-in for NMM. Thisdoes not require a restart.

l Select the Remove option to remove the NMM software from the system.

Note

After you uninstall NMM, you can continue to perform traditional backups by usingthe NetWorker software, which is still available on the host.

Upgrading NMMAn NMM upgrade might involve:

l Upgrading from NMM 3.0 or later in a stand-alone environment on page 34

l Upgrading from NMM 3.0 or later in a clustered environment or upgrade from anearlier release in a stand-alone or clustered environment on page 34

l Upgrading from NME or NMSQL on page 35

l Upgrading to NMM with a dedicated storage node on page 35

Note

Perform a full backup after upgrading from a previous NMM release to NMM 9.0.

When upgrading the client operating system from Windows Server 2012 to a laterversion, perform the steps described in the following sections.

Upgrading the client operating system from Windows Server 2012 to a later versionWhen upgrading the client operating system from Windows Server 2012 to a laterversion, perform the following steps:

Procedure

1. Uninstall NMM by performing the steps that are described in Uninstalling or changinginstallation options on page 32.

2. Upgrade Windows Server.

3. Install NMM by performing the steps that are described in Configuration Checks andInstallation on page 27.


Upgrading NMM 33

Upgrading from NMM 3.0 or later in a stand-alone environmentTo upgrade from NetWorker 8.1 SP1 or later client and NMM 3.0 or later, use the ClientPush feature. Client Push provides the ability to distribute software and perform softwareupdates to one or more NetWorker hosts from the NetWorker server. NMM only supportsupgrades from NMM 3.0 or later in stand-alone environments. Client Push is notsupported for clustered environments or for clients earlier than NMM 3.0. Whenupgrading NMM by using Client Push, select both the module and the client, or theupgrade will fail.

Note

If you use Client Push to upgrade the SSMS plug-in, the Backup tab of the SSMS plug-indoes not display and only the Restore tab displays.

EMC NetWorker Updating from a Previous Release Guide and the nsrpush man pagedescribes how to use Client Push to update NetWorker products.

Upgrading from NMM 3.0 or later in a clustered environment or upgrade from anearlier release in a stand-alone or clustered environment

You cannot perform a direct upgrade from an existing installation of an NMM releasebefore NMM 3.0. For example, if you have NMM 2.4 installed in the setup, and now wantto use NMM 3.0 or later, you must first remove the existing installation of NMM andperform a fresh installation of NMM 3.0 or later.

Procedure

1. Perform a full backup by using the existing NMM program.

2. Remove all existing snapshots. To delete shadow copy entries, use vssadmin ordiskshadow.

3. Remove the existing NMM software:

a. Select Start > Control Panel > Programs and Features.

b. Select NetWorker Module for Microsoft.

c. Select Uninstall. Follow the procedure that is provided in Uninstalling or changinginstallation options on page 32.

4. Ensure that a supported version of the NetWorker client or NetWorker storage nodesoftware is installed and running on the application host.

Upgrading to NMM with a dedicated storage node on page 35 provides details.

5. Run the NMM installer and select the Run System Configuration Checker and InstallNetWorker Module for Microsoft (Recommended) option on the Select ConfigurationChecks Option page. Running preconfiguration checks and installing the software onpage 28 provides details.

6. If a system reboot is pending, reboot the system after the NMM installation iscomplete.

7. Perform a full backup of all the data as soon as possible after the upgrade to provideimmediate protection by using NMM.

After you finish

After upgrading to NMM, if you are expecting to recover data that was backed up by usingan older version of NMM, you should consider the following:



l Recover file system data by using NetWorker 3.0 or later. File system data cannot bebrowsed in the NMM GUI.

l Recover system component by using NMM 2.4 SP1.

l Recover application data other than SharePoint Server web application data by usingNMM to perform the recovery.

l Recover SharePoint Server web application data by using NMM 2.4 SP1 to performthe recovery.

Upgrading from NME or NMSQLNMM supports all features of NetWorker Module for Microsoft Exchange Server (NME)software and NetWorker Module for Microsoft SQL Server (NMSQL) software. If you useNME or NMSQL, EMC recommends that you move to NMM.

You cannot install NMM on a system that has NME or NMSQL installed and vice versa. Toupgrade to NMM from NME or NMSQL, you must first uninstall NME or NMSQL and theninstall NMM.

Procedure

1. Perform a full backup of the Exchange or SQL hosts by using the existing NME orNMSQL program.

2. On each NME or NMSQL client host:

a. Run the Setup program in the maintenance mode.

b. Select the Remove option.

Note

Although this procedure removes the existing NME or NMSQL software, theconfiguration information that was created for these products is retained and isreapplied if you reinstall NME or NMSQL.

3. Remove all existing snapshots. To delete shadow copy entries, use vshadow ordiskshadow.

4. If required, install a supported version of NetWorker client or NetWorker storage nodesoftware.

5. Run the NMM installer and use the Run System Configuration Checker and InstallNetWorker Module for Microsoft (Recommended) option in the Select ConfigurationChecks Option page.

NOTICE

After you install NMM, perform a full backup of the Exchange Server or SQL Serverdata. You cannot use NMM to recover data from a backup that was performed by usingNME. You can use NMM to recover data from an NMSQL VDI backup after upgrading toNMM.

Upgrading to NMM with a dedicated storage nodeNMM software supports a DSN deployed on the same host and thus does not need to usea NetWorker storage node that is shared with other hosts and software. This solution is


Upgrading from NME or NMSQL 35

useful for individual high-volume backup clients and can reduce network bandwidthusage.

This solution supports the upgrade from NetWorker 7.6 SP3 or later.

Procedure

1. Uninstall the earlier version of NMM software.

2. Install a supported version of NetWorker storage node on the NMM host.

The EMC NetWorker Installation Guideprovides details.

3. Run the NMM installer and use the Run System Configuration Checker and InstallNetWorker Module for Microsoft (Recommended) option in the Select ConfigurationChecks Option page.

The installation detects the storage node and prompts for permission to dedicate thestorage node to the NMM client data.

4. Click OK and complete the installation.



CHAPTER 4

Silent Installation

l Silent installation of NMM..................................................................................... 38l Silent removal of NMM.......................................................................................... 40l Silent upgrade of NMM..........................................................................................40l Silent modification of NMM................................................................................... 40l Sample scripts for silent installation and removal of NMM.................................... 41l Installing and removing NMM by using an SCCM 2007 Server................................41l Troubleshooting the installation............................................................................42

Silent Installation 37

Silent installation of NMMSilent (unattended) installation is a stand-alone (non-network) method where you specifyall the information that the installation requires either directly in the command line orusing the commands written as scripts in a .cmd file.

Procedure

1. Install the NetWorker client ("lgtoclnt-9.0.0.2" or select "client" from"NetWorker-9.0.0.2" from NetWorker package) or storage node (select "storage node"from "NetWorker-9.0.0.2" from NetWorker package) software on the hosts where youwill install NMM.

The EMC NetWorker Installation Guide describes how to install the NetWorker client orstorage node software.

2. Run the command or script to install NMM.

Commands for silent installation of NMM on page 38 provides the command andexample.

3. Inspect the installation log files to verify the installation. The location of the log filesare specified in the NMM installation. The default location is the temp directory, whichyou can view:

a. Click Start > Run.

b. Type %temp%.

c. Navigate to the parent folder of the %temp% folder.

4. (For Exchange only) After successful silent install, if the Exchange user configurationtool does not start automatically, manually run the tool for successful ExchangeServer backup and recovery.

Commands for silent installation of NMMTo install the NMM software by using the Windows installer, open a command prompt,select the option Run as administrator, and then type the commandNWVSS.exe /s /log "C:\NMM_nw_install_detail.log" InstallLevel=100.

The NMM installer has three basic features:

l NMM: InstallLevel=100

l SSMS: InstallLevel=150

l GLR: InstallLevel=200

These features work in conjunction with other associated variables. If you provideInstallLevel=150, then all the features below this install level will be installed. Forexample, if you provide InstallLevel=150, NMM and the SSMS plug-in are installed.

Installer variablesIn addition to installing the NMM installer features, you can also use variables tocustomize the installation.

Each variable-name pair should be double-quoted if there is embedded whitespace.Variable names are case sensitive. All silent installation switches are supported (forexample, switches such as /v, /s, /q, /l). The following table provides the list of variableswith valid values and defaults.

Silent Installation


Table 8 NMM installer variables

Variable Valid values Default value

EnableSSMS [0|1] 0

EnableSSMSBackupTab [0|1] 0

EnableSSMSScript [0|1] 0

ConfigFirewall [0|1] 1

InstallLevel [100|150|200] -

RebootMachine [0|1] If EnableGLR or EnableRpvNmm are set,the default value is 1. To prevent thereboot, set the value to 0.

EnableGLR [0|1]Installs GLR if you provide"1"

0

EnableRpvNmm [0|1]Installs RpvNmm if youprovide "1".

0

WriteCacheFolder <full path to directory> "C:\Program Files\EMC NetWorker\nsr\tmp\nwfs"

MountPointFolder <full path to directory> "C:\Program Files\EMC NetWorker\nsr\tmp\nwfs\NetWorker Virtual FileSystem"

BBBMountPointFolder <full path to directory> "C:\Program Files\EMC NetWorker\nsr\tmp\BBBMountPoint"

SetupType Install Install

Sample commandsThe following table provides commands to install the three NMM installer features. Thesecommands use the NMM installation command and the installer variables.

Table 9 Commands for NMM installation

Task Command

Install the NMMclient only

NWVSS.exe /s /q /log "C:\NMM_nw_install_detail.log"InstallLevel=100

Install the NMMclient and the SSMSplug-in

NWVSS.exe /s /q /log "C:\NMM_nw_install_detail.log"InstallLevel=150 EnableSSMS=1

Install the NMMclient and the GLRoption

NWVSS.exe /s /q /log "C:\NMM_nw_install_detail.log"InstallLevel=200 RebootMachine=0 EnableGLR=1WriteCacheFolder="C:\Program Files\EMC NetWorker\nsr\tmp\nwfs" MountPointFolder="C:\Program Files\EMCNetWorker\nsr\tmp\nwfs\NetWorker Virtual FileSystem" BBBMountPointFolder="C:\Program Files\EMCNetWorker\nsr\tmp\BBBMountPoint" SetupType=Install

Silent Installation

Commands for silent installation of NMM 39

Table 9 Commands for NMM installation (continued)

Task Command

Install the NMMclient and theRecover fromprevious versionoption

NWVSS.exe /s /q /log "C:\NMM_nw_install_detail.log"InstallLevel=200 RebootMachine=0 EnableRpvNmm=1WriteCacheFolder="C:\Program Files\EMC NetWorker\nsr\tmp\nwfs" MountPointFolder="C:\Program Files\EMCNetWorker\nsr\tmp\nwfs\NetWorker Virtual FileSystem" BBBMountPointFolder="C:\Program Files\EMCNetWorker\nsr\tmp\BBBMountPoint" SetupType=Install

Install the NMMclient, the SSMSplug-in, and the GLRoption

NWVSS.exe /s /q /log "C:\NMM_nw_install_detail.log"InstallLevel=200 RebootMachine=0 EnableGLR=1EnableSSMS=1 WriteCacheFolder="C:\Program Files\EMCNetWorker\nsr\tmp\nwfs" MountPointFolder="C:\ProgramFiles\EMC NetWorker\nsr\tmp\nwfs\NetWorker VirtualFile System" BBBMountPointFolder="C:\Program Files\EMC NetWorker\nsr\tmp\BBBMountPoint "SetupType=Install

Silent removal of NMMThe following command performs silent removal of NMM: NWVSS.exe /uninstall /s.

Silent upgrade of NMMYou cannot perform a direct upgrade from an earlier version of NMM to a new version ofNMM.

Procedure

1. Remove the existing NMM version by using the silent uninstallation process. Silentremoval of NMM on page 40 provides details.

2. Install the NetWorker client software.

3. Follow the steps that are provided in Silent installation of NMM on page 38 to installNMM using the silent installation process.

Silent modification of NMMTo modify installation of NMM, such as to install the SSMS plug-in, you must uninstalland then install NMM with the desired features.

Procedure

1. Remove the existing NMM installation by using the silent uninstallation process. Silent removal of NMM on page 40 provides details.

2. Install the NetWorker client software.

3. Follow the steps that are provided in Silent installation of NMM on page 38 to installNMM using the silent installation process, including the desired features.

Silent Installation


Sample scripts for silent installation and removal of NMMThe following table lists sample scripts that you can use for the silent installation andremoval of the NMM software. All these samples are included in the NMM installationmedia kit in the directory where NWVSS.exe is located. You can modify the sample scriptsto provide custom installations for the environment.

Each sample script creates a log in the %temp% directory, whose base name is the sameas the script base name. The only difference is that the file name extension .cmd isreplaced by .log. For example, the file that is created for theinstall_nmm_silent_sample.cmd script is named install_nmm_silent_sample.log.

You can also use these logs to troubleshoot installation problems.

Table 10 Sample scripts for silent installation

Script name Description

DotNetInstalled.vbs Determines if .NET Framework is installed.

DotNetInst.cmd Installs .NET Framework.

NMMConfigFW.vbs Creates Windows firewall exceptions for NMM. Useful if ConfigFirewall is setto "0" during installation.

Installing and removing NMM by using an SCCM 2007 ServerYou can remotely install or remove the NMM software by using a Microsoft System CenterConfiguration Manager (SCCM) 2007 Server.

Installing NMM using an SCCM 2007 serverInstall NMM from a remote location by using the Microsoft System Center ConfigurationManager (SCCM) 2007 Server.

Procedure

1. Run the New Collection Wizard to specify the client host, where you will install theNMM software.

2. Copy the NMM installation package to the local drive on the SCCM Server and specifya local SCCM hostname as a new distribution point for the distribution package.

3. Run the New Package Wizard to create a software distribution package. Specifygeneral information, data source, distribution settings, and other information for thenew package.

The wizard creates example installation and uninstallation script files in theinstallation kit \networkr directory. Sample scripts for silent installation and removalof NMM on page 41 provides details.

4. Run the New Program Wizard to create an installation program for a softwaredistribution package:

a. To use the install_nmm_silent_sample.cmd file as the source installationfile:

Silent Installation

Sample scripts for silent installation and removal of NMM 41

a. On the SCCM Server, on the General tab, click Browse.

b. Select Show all files.

c. Select install_nmm_silent_sample.cmd file in the /networkerdirectory.

b. In the Environment Wizard window:

Set the administrative rights to Run Mode.

a. Use the default setting for all other options.

b. Click Close to complete the program creation.

5. Run the New Advertisement Wizard to create an advertisement for the installation.Specify the general information, package name, program, and collection to which theadvertisement should be distributed:

a. For the schedule option, select Run as soon as possible.

b. For the delivery method, select Run program from distribution point.

c. For all other options, use the default settings.

d. Complete the New Advertisement Wizard.

Results

After the SCCM server creates the advertisement, the SCCM Server is ready to install thesoftware. Allow 30 minutes or more for the SCCM Server to process the advertisedinstallation. You can view and verify the installation process status in the AdvertisementStatus section in the SCCM Server.

The C:\Windows\temp directory contains the SCCM server installation status log files.For quick access to the temp directory, select Start > Run and then type %SystemRoot%\temp.

Uninstalling NMM using an SCCM 2007 serverTo uninstall the NMM software with an SCCM 2007 Server, run theuninstall_nmm_silent_sample.cmd file. The procedure to uninstall NMM with an SCCM2007 server is the same as the install procedure. Installing NMM using an SCCM 2007server on page 41 provides details.

Troubleshooting the installationYou might have to troubleshoot errors when NMM is not running correctly after a freshinstallation or if moving from a previous release of NMM to a new version of NMM.

The EMC NetWorker Administration Guide provides more details on troubleshooting.

Using non-English characters in installation pathWhen you install the NMM software, during silent or GUI installation, do not use non-English characters in the installation path.

Silent Installation


CHAPTER 5

Configuration Tasks

l Configuring a dedicated storage node for NMM..................................................... 44l Configuring NMM Proxy Recovery Agent for Hyper-V FLR.........................................44l Set up events notifications and find errors............................................................ 45l Removing directives after migrating to NMM..........................................................45l Troubleshooting installation issues.......................................................................46

Configuration Tasks 43

Configuring a dedicated storage node for NMMFor an Exchange Server 2010 DAG, use the workaround provided in the "Configuringbackups to use a remote storage node in a DAG environment section" in the EMCNetWorker Module for Microsoft for Exchange VSS User Guide. To configure a DSN for NMMfor all other applications:

Procedure

1. Install the NetWorker Server or NetWorker Storage Node software.

2. Install the NMM software on the same host.

3. Create a remote backup device on the NetWorker server and on the Device Properties,Configuration tab, set the Dedicated Storage Node attribute to Yes.

A DSN license is required. The EMC NetWorker Administration Guide provides details.

Configuring NMM Proxy Recovery Agent for Hyper-V FLRFor NMM Hyper-V File Level Recovery (FLR) web UI configurations, you must configureNMM Proxy Recovery Agent (RA). NMM Proxy RA allows you to perform recoveries tovirtual machines running on the Hyper-V server.

Before you begin

If NMM Proxy RA is deployed on a different system than the Hyper-V server or cluster, youmust add the NMM RA host to the Backup Operator group of the Hyper-V server or eachnode in the cluster.

NMM ProxyRA requires Windows Server 2012 or later.

NMM Proxy RA requires Windows Server 2008 or later.

Procedure

1. Verify that integration services are up to date for all virtual machines.

2. Verify that all virtual machine hostnames are resolved from the Hyper-V server andvice versa.

3. Install NMM Proxy RA on each virtual machine by using one of the following options:

l The installer NWVSS Proxy Recovery Agent.exe, available as part of NMM9.0 installer kit.

l The ISO image NWVSS Proxy Recovery Agent.iso. Mount the ISO image tothe virtual machine and then access the installer via the CD drive inside the virtualmachine.

4. Make appropriate rules in the firewall for the nsrnmmproxyra.exe process so thatthe Hyper-V server and each virtual machine have proper communication.

Note

nsrnmmproxyra.exe uses port number 50000 for communication.

Configuration Tasks


Set up events notifications and find errorsSet up NetWorker and NMM to send notifications about errors and events. NetWorker cansend notifications to several locations, including log files, SNMP printers, SNMPmanagement console, and email messages.

The EMC NetWorker Administration Guide describes how to set up notifications.

The following table describes several ways that the NetWorker server, NMM, and otherNetWorker features provide information about problems.

Table 11 Notifications and errors

Type Description

Email notification ofa NetWorker event

Configure an Owner Notification for the MM client to send an emailnotification about NetWorker events.

Error messagedetails window

Displays error and event message for NetWorker server activities includingbackup or recovery operations.

NetWorker Monitorwindow

Displays details of current NetWorker server activities, operations that arerelated to devices and libraries, group backup operations, and events thatrequire user intervention.

Event viewer Alerts users that user intervention is required on the NMM host.

Log files NMM creates log files for each operation and process. Separate log filesare available for NetWorker and various features, depending on whatfeatures are installed and in use:

l NMM

l NetWorker Client or Storage Node

l NetWorker Server

The debug level of a save or recover process determines the number ofmessages that operation sends to the log file.

Removing directives after migrating to NMMAfter you migrate to NMM from other modules such as NME and NMSQL, you shouldremove any directives on the application servers that skip database files during a filesystem backup. NME and NMSQL do not process directives to skip database files.However, after the migration, NMM recognizes these migrated directives, skips bothdatabase and log files, and reports a successful backup although no data is backed up.

Configuration Tasks

Set up events notifications and find errors 45

Troubleshooting installation issuesReview and follow the solutions that are provided for various issues that you might facefor NMM installation.

Unable to uninstall NMM after Windows Server upgradeWhen upgrading Windows Server, you must uninstall NMM, upgrade Windows Server,then reinstall NMM. If you do not perform these steps in this order, NMM might becomeunable to uninstall.

Solution

1. Restore the pre-existing version of Windows Server.

2. Uninstall NMM by performing the steps that are described in Uninstalling or changinginstallation options on page 32.

3. Upgrade Windows Server.

4. Upgrade NMM by performing the steps that are described in Configuration Checksand Installation on page 27.

Force cleaning an NMM installation on a client hostYou can resolve errors while uninstalling NMM by force cleaning the NMM installation.

1. Make a copy of the log files in the following directories: nsr\applogs and nsr\logs.

2. Uninstall the NMM Client.

3. Ensure that the NetWorker Power Monitor Service is not running.

4. Uninstall the base NetWorker client.

5. Delete all the files and directories in \Program Files\EMC NetWorker\nsr, but save thelogs from step 1.

6. Delete the following registry keys:

l HKLM\SOFTWARE\EMC and below

l HKLM\SOFTWARE\Legato and below

7. Reinstall the base NetWorker client software.

8. Reinstall the NMM client software.

Note

During installation in an Exchange environment, ensure to provide the correct Exchangecredentials and take care of other requirements specific to Exchange installations.

When you flush the nsr folder (remove the metadata), the nsrladb folder contains thepublic key for the client that is cached in the NetWorker server’s “local hosts” resource.To correct this, you must delete the NSR Peer Information on the backup server for theclient so that the cached public key is updated.

Use this command to delete the peer information:

C:\>nsradmin -p nsrexec -s bv-rcserver NetWorker administration program. Use the "help" command for help. nsradmin> delete type: NSR peer information; name: bv-tlscs.belred.legato.com type: NSR peer information;

Configuration Tasks


administrator: Administrators, "group=Administrators,host=bv-rcserver.belred.legato.com"; name: bv-tlscs.belred.legato.com; peer hostname: bv-tlscs.belred.legato.com; Change certificate: ; certificate file to load: ; Delete? y deleted resource id 8.0.72.7.0.0.0.0.174.29.184.76.0.0.0.0.10.5.220.27(1) nsradmin>

Inconsistent VSS writer state after NetWorker client installationAfter NetWorker client installation, some VSS writers state might become 'Waiting forcompletion'. Since the VSS state is inconsistent, backups fail.

Solution

1. Reboot the client machine.

2. Observe that the VSS writers are now in a consistent state.

3. Retry the backup.

Configuration Tasks

Troubleshooting installation issues 47

Configuration Tasks


APPENDIX A

Required Microsoft Hotfixes

This appendix describes Microsoft hotfix updates required for NMM applications. Thereare no Microsoft hotfix requirements for NMM with SQL Server. For required Hyper-V overCSV hotfixes, please see EMC NetWorker Best Practices for Hyper-V over CSV Cluster DataProtection Using EMC NetWorker Module for Microsoft Technical Notes.

l Hotfix updates required for backup and recovery of all applications...................... 50l Hotfix updates required for VSS backup and recovery............................................51l Hotfix updates required for Exchange Server backup and recovery........................ 52l Hotfix updates required for SharePoint Server backup and recovery...................... 52

Required Microsoft Hotfixes 49

Hotfix updates required for backup and recovery of allapplications

The following table lists the hotfix updates required for general NMM backup andrecovery.

Table 12 Hotfixes required for NMM general backup and recovery

KnowledgeBase articleID

WindowsServer 2008SP2(X32)


WindowsServer 2008R2

WindowsServer 2012


Applies to Description

KB975688 X WindowsServer 2008R2 editions

A snapshotmight becomecorruptedwhen theVolumeShadow CopyService (VSS)snapshotproviders takemore than 10seconds tocreate it on ahost that isrunningWindowsServer 2008R2.

KB978897 X X WindowsServer 2008SP2

On Windows2008, duringNMMbackups,Virtual DiskService (VDS)crashes whileapplyingretentionbecause VDSincorrectlyaccessessomeproviders thatare unloaded,when VDS isin the exitprocess.



Hotfix updates required for VSS backup and recoveryThe following table lists the hotfix updates that NMM requires for VSS backup andrecovery.

Table 13 Hotfixes required for NMMfor VSS backup and recovery





WindowsServer 2012



KB975832 X X VSS You cannotperformcertain disk-relatedoperationsafter a VSShardwareprovider failsto create asnapshot on acomputer thatis runningWindowsServer 2008.

KB2748349 X X VSS When thecurrent size ofthe volumethat youextend is amultiple of 8gigabytes (GB)by a size thatis larger than8 GB or thevolume isfrequentlyextended by amultiple of 8GB, corruptedbackupsmight not bedetected untilyou attempt arecovery.


Hotfix updates required for VSS backup and recovery 51

Hotfix updates required for Exchange Server backup and recoveryThe following table lists the hotfix updates required for NMM for Exchange Server backupand recovery.

Table 14 Hotfixes required for NMM for Exchange Server backup and recovery





WindowsServer 2012



KB2425179 X X X ExchangeServer 2010

To performRecoveryDatabase(RDB) itemlevel recovery,installExchangeServer 2010SP1 Rollup 2on allapplicablehosts.

Hotfix updates required for SharePoint Server backup andrecovery

The following table lists the hotfix updates required for NMM for SharePoint Serverbackup and recovery.

Table 15 Hotfixes required for NMM for SharePoint Server backup and recovery

KnowledgeBase article ID

Windows 2008SP1 R2(X64)

Windows 2008SP2(X64, X86)

WindowsServer 2012



KB2412267 X X SharePointServer 2007 SP3

Cumulativeupdatepackages forMicrosoft OfficeSharePointserver 2007(released inOctober 2010)contain hotfixes.SharePoint 2007VSS backup andrestore fails onnamed instance



Table 15 Hotfixes required for NMM for SharePoint Server backup and recovery (continued)




WindowsServer 2012



if the updatesare not installed.

KB971538

l If you havealreadyinstalledhotfix961755,then alsoinstall hotfix971538.

l If you havenot installedhotfix961755,then installonly hotfix971538.

X SharePointServer 2007

Cumulativeupdatepackages forWindowsSharePointServices 3.0contain hotfixesfor the WindowsSharePointServices 3.0issues that werefixed since therelease ofWindowsSharePointServices 3.0.This build of thecumulativeupdate packageis also known asbuild12.0.6510.5001.Go to theMicrosoftsupport websiteand search forKB971538 -“Description ofthe WindowsSharePointServices 3.0cumulativeupdate serverHotfix Package(WSS server-package): June30, 2009” andfollow thedirections thatare provided onthe website.

KB953334 X SharePointserver 2007

The MicrosoftOffice 2007servers SP2packageprovides the


Hotfix updates required for SharePoint Server backup and recovery 53





WindowsServer 2012



latest updates. Itincludes twomain categoriesof fixes:

l Previouslyunreleasedfixes thatwere madespecificallyfor thisservicepack,includingimprovements instability,performance, andsecurity.

l All thepublicupdates,securityupdates,cumulativeupdates,and hotfixesthat werereleasedthroughFebruary2009.

KB953338 X SharePointServer 2007

WindowsSharePointservices 3.0 SP2provides thelatest updates,including:

l Previouslyunreleasedfixes thatwere madespecificallyfor thisservicepack,including







WindowsServer 2012



improvements instability,performance, andsecurity.

l All thepublicupdates,securityupdates,cumulativeupdates,and hotfixesthat werereleasedthroughFebruary2009.Before youtry to installthis servicepack, readabout howto deploysoftwareupdates forWindowsSharePointServices3.0.

KB981043 SharePointServer 2007

Cumulativeupdatepackages forWindowsSharePointServices 3.0(released in April2010) containhotfixes.SharePoint 2007VSS backup andrestore fails ifthe updates arenot installed.


Hotfix updates required for SharePoint Server backup and recovery 55

emc networker module for microsoft 9.0 installation guide · upgrading the client operating system...

Documents