You are on page 1of 82

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

4 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Installation Guide

.... 63 Specifying the restore lock type ............................ 65 EMC NetWorker Module for Microsoft Applications Release 2...............................................exe.. 62 Specifying temporary storage location............................................................. 62 Matching NetWorker SharePoint Service credentials with credentials of SharePoint Server administrator .... Contents Changing Replication Manager port settings.............. 61 Configuring NetWorker SharePoint services .. 63 Configuring Windows firewall settings .................2 SP1 Installation Guide 5 .................................................................................................................................. 64 Manually creating NMM firewall exceptions........................ 64 Windows firewall exception error for irccd........................................................................................................

2 SP1 Installation Guide .Contents 6 EMC NetWorker Module for Microsoft Applications Release 2.

2 SP1 Technical Notes ◆ NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing Proxy Node Backups 2.x Multiplatform Version Administration Guide ◆ EMC NetWorker Release 7.5. Audience This guide is part of the EMC NetWorker Module for Microsoft Applications documentation set. please contact your EMC representative.2 SP1 Release Notes ◆ EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Technical Notes ◆ EMC NetWorker Release 7.x Multiplatform Version Installation Guide ◆ EMC NetWorker Release 7.2 SP1 Administration Guide ◆ EMC NetWorker Module for Microsoft Applications Release 2. refer to the product release notes.x Multiplatform Version Release Notes ◆ EMC Information Protection Software Compatibility Guide EMC NetWorker Module for Microsoft Applications Release 2. during installation and setup of the product. such as EMC CLARiiON or Symmetrix. Therefore. Preface As part of its effort to continuously improve and enhance the performance and capabilities of its product lines.5. 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.2 SP1 Installation Guide 7 .2 SP1 Applications Technical Notes for SharePoint and Exchange ◆ NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups 2. It is intended for use by system administrators. For the most up-to-date information on product features. If a product does not function properly or does not function as described in this document.5. EMC periodically releases revisions of its hardware and software. some functions may not be supported by all revisions of the software or hardware currently in use. if used Related Related documents include: documentation ◆ EMC NetWorker Module for Microsoft Applications Release 2.

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

8 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Installation Guide

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

EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Installation Guide 9

Preface

10 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Installation Guide

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

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 12 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1.” provides more information on enablers and licensing. ensure to purchase the NetWorker Client enabler. Chapter 4. This license must be installed on the NetWorker Server. “Licensing and Enabling the Software. Table 1 on page 12 describes the required privilege levels.2 SP1 Installation Guide .Preinstallation information Preinstallation requirements This section describes the preinstallation requirements for NetWorker Module for Microsoft Applications (NMM) 2. 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. 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. You must review and adhere to the checks and requirements described in this section thoroughly before attempting a NMM installation. 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. Privileged user-level access As NMM requires access to protected data and system files. ◆ NetWorker Client enabler Although the NetWorker Client is included with the NMM software.

add Exchange credentials. If proper credentials are not specified then the backup of SharePoint data fails. software. and operating systems for the NetWorker Module for Microsoft Applications software. • A service account for each web application that needs to be backed up. “Match NetWorker SharePoint Service credentials with credentials of SharePoint Server administrator” on page 76 provides details. Data loss may occur if other VSS Requestor backup solutions delete shadowcopies created by the NetWorker Module for Microsoft Applications. do not install or use the NetWorker Module for Microsoft Applications with other vendor’s VSS Requestor backup solutions. Additionally. Preinstallation information 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 EMC Information Protection Software Compatibility Guide provides more information on the supported hardware. Hardware requirements You require the following hardware before the installation: ◆ CPU: 2. During the NMM installation.0 GHz ◆ Physical memory: 1 GB ◆ Host architecture: x86 and x64 systems only Software requirements ! CAUTION To avoid potential data loss. Network domain Windows Domain Administrator Storage node servers Windows Administrator Adding Exchange Server 2007 credentials You must first install Exchange and then NMM. “Installing NMM” on page 34 provides more information about initial setup of Exchange credentials during NMM installation. then ensure that NMM is reinstalled. If you have installed Exchange Server 2007 after installing NMM. • 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. Preinstallation requirements 13 . 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.

exe Replication Manager Client for RMAgentPS rmagentps irccd. ensure that: ◆ The SQL Server VSS Writer service has the startup type as Automatic. Installation services When NMM is installed. ◆ The SQL Server VSS Writer service is running. 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. 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.2 SP1 Installation Guide . Table 2 on page 14 lists the installation services for the NetWorker software.exe 14 EMC NetWorker Module for Microsoft Applications Release 2. the <Drive>:\Program File\Legato\nsr directory is created by default.Preinstallation information Microsoft SQL and SharePoint VSS Writers If NMM is installed on a Microsoft Office SharePoint Server. But you can select a location other than the default one during installation. and EMC PowerSnapTM and Replication Manager services.exe NetWorker PowerSnap Service nsrpsd nsrpsd.

permissions.3 or later server” on page 15 • “Microsoft hotfixes required for NMM 2. that is available at ftp://ftp. which contains these sections: • “Patch for deduplication backup of NMM Client if using NetWorker 7.2 SP1” on page 16 Patch for deduplication backup of NMM Client if using NetWorker 7. and system requirements required before installing NMM 2. As each checklist is completed.1. Table 3 Checklist overview Mark complete Checklist “Patches and hotfixes checklist” on page 15.5. Without this patch.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.3 or later server Ensure to install the patch.2 SP1. Preinstallation information Preinstallation checklist overview Preinstallation checklists provide a quick reference for you to implement the accounts. The following preinstallation checklists are provided in this section.5. 69227:nsrsnap_vss_save:nsrsnap_vss_save: Failed to set value for a key=De-duplication”.5.com/pub/NetWorker/Updates/NMM/NMM22/.legato. indicate it by using the checklist provided in Table 3 on page 15. Expecting '-A key=value'in this format. deduplication backup failure is observed when backups are performed by using a NetWorker 7.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'.1.3 or later server” on page 15 ◆ “Microsoft hotfixes required for NMM 2.5. Preinstallation checklist overview 15 .1.

Keep NMM Client machine current with Microsoft Windows updates for the operating system. 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. 3.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. 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. 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. Download the hotfixes from the Microsoft website.2 SP1 Installation Guide . the operation may fail.2 SP1 In addition to the specific Microsoft Windows updates mentioned in this guide: 1. Note: The EMC Module for Microsoft Applications Release 2.Preinstallation information Microsoft hotfixes required for NMM 2. Keep NMM Client machine current with updates and hotfixes for each installed Microsoft application protected by NMM. 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" 16 EMC NetWorker Module for Microsoft Applications Release 2.

EMC Replication Manager SP1 Patches and hotfixes checklist 17 . When you shut down a computer that is running the Microsoft Storport storage driver (Storport.5 Hotfix Rollup Package 11 for Service Pack Exchange 2007 CCR environments. R2.sys) on Windows Server 2003 Service Pack 2 (SP2). Server 2007 Service Pack 2 KB936008 X X SP1. Preinstallation information Table 4 Hotfixes required for NMM 2. you may receive a “Stop 0x0000009C” error message that resembles the following: “*** STOP: 0x0000009C (parameter1. SP2. KB903081 X X Symmetrix NA Hotfix Storport WindowsServer2003-KB903081-x86-ENU. parameter2. 2 KB971534 X X Exchange NA Update Rollup 1. 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. These versions of Storport incorrectly forward interrupts to the miniport after the PCI bus is in the “device off” state (D3). 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.2 SP1 (page 2 of 5) Windows Windows Windows Windows Included KnowledgeBase 2003 2003 2008 2008 in service article ID (X32) (X64) (X32) (X64) Applies to pack Description KB939315 X X VSS NA Note: Only apply this hotfix if needed. Drivers exe available for Windows Server 2003 configurations running STORport drivers with Symmetrix storage arrays. Microsoft Exchange KB927673 X X Exchange NA Windows Server 2003 Post-Service Pack 1 Server 2007 COM+ 1. 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. Storage arrays KB908980 X X EMC NA For Windows Server 2003 configurations CLARiiON® running STORport drivers with CLARiiON Storport storage arrays.

This hotfix is required because a Windows Server 2003-based computer stops responding when you perform a backup of an Exchange Server database.Preinstallation information Table 4 Hotfixes required for NMM 2. KB891957 X X RM SP1 NA Microsoft hotfix WindowsServer2003-KB891957-x86-ENU. • Installation of Microsoft SQL Server 2005 Service Pack 3 includes this hotfix. SQL Server 2005 Service Pack 2 must be installed. Microsoft SharePoint 18 EMC NetWorker Module for Microsoft Applications Release 2. exe for Replication Manager SP1. unavailable after you install Windows Enterprise x64 Server 2003 Service Pack 1. KB912063 X X RM SP1 NA Microsoft hotfix WindowsServer2003-KB912063-x86-ENU. To apply this hotfix. Server cluster KB898790 X Microsoft NA Volume mount points on disks in a server Windows cluster may intermittently become Server 2003.2 SP1 (page 3 of 5) Windows Windows Windows Windows Included KnowledgeBase 2003 2003 2008 2008 in service article ID (X32) (X64) (X32) (X64) Applies to pack Description KB898790 X X RM SP1 NA Microsoft hotfix WindowsServer2003-KB898790-x86-ENU.2 SP1 Installation Guide . This update fixes various Volume Shadow Copy Service issues in Windows Server 2003. 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. 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. exe for Replication Manager SP1.

• Go to the Microsoft support website and search for KB971538 . 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. Services 3. 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. 2009” and follow the directions provided on the website.0 2 contain hotfixes for the Windows SharePoint Services 3. This provides increased SP2 functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V role.“Description of the Windows SharePoint Services 3. KB951308 X X Microsoft SP2 Apply to each cluster node for cluster Hyper-V deployment.0 Cumulative Update Server Hotfix Package (WSS server-package): June 30.0 • Cumulative update packages for Service Pack Windows SharePoint Services 3.” The reason this message appears is that ASR is unable to obtain disk information for device 3 (Win32 error code 0x2).0 issues that were fixed since the release of Windows SharePoint Services 3. Microsoft Hyper-V KB950050 X X Microsoft NA If this update is not installed prior to Hyper-V recovery.5001. SharePoint then install only hotfix 971538. Patches and hotfixes checklist 19 . KB967560 X X Microsoft SP2 When a scheduled save is started. • If you have not installed hotfix 961755. Preinstallation information Table 4 Hotfixes required for NMM 2. the Hyper-V following error message might appear in the event viewer: “ASR Error: Failed to collect critical information for ASR Backup. 2007. This build of the cumulative update package is also known as build 12.0.0. then install hotfix 971538 also.2 SP1 (page 4 of 5) Windows Windows Windows Windows Included KnowledgeBase 2003 2003 2008 2008 in service article ID (X32) (X64) (X32) (X64) Applies to pack Description KB971538 X Microsoft NA • If you have already installed hotfix SharePoint 961755. the system will not come back after recovery of SYSTEM COMPONENTS.6510.

• The System Center Data Protection Manager 2007 Service Pack 1 download is available from Microsoft website. KB960038 X X Microsoft SP2 Apply to all Hyper-V hosts. Otherwise. 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]. which you might experience when backups are made by using the Hyper-V writer. After performing this update. 20 EMC NetWorker Module for Microsoft Applications Release 2. 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. • VSS application writer provider is moving to a bad state.2 SP1 Installation Guide . replicas may not successfully recover. • If recovery of a virtual machine is failing because it has legacy network adaptors attached. This will require a restart of virtual machine. This update for Hyper-V Windows Server 2008 fixes a crash of the SP2 Hyper-V host server. 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.Preinstallation information Table 4 Hotfixes required for NMM 2.2 SP1 (page 5 of 5) Windows Windows Windows Windows Included KnowledgeBase 2003 2003 2008 2008 in service article ID (X32) (X64) (X32) (X64) Applies to pack Description KB959962 X Microsoft SP2 Hyper-V writer update if the backup fails for Hyper-V one of the following reasons: SP2 • Retryable VSS error.

IPv6 status. Note: Look at Add or Remove Program in Control panel and make sure that no other backup application is installed.2 SP1. PowerSnap. proxy node. is properly configured on the network. NetWorker Client. There are open ports in the firewall to allow NMM to communicate. • If not enabled. DNS lookup of host — Host is reachable and can be looked up in If yes. run the next check. excluding Microsoft DPM 2007 SP1 software. or Replication Manager is installed. Section “Setting up dual-NIC for Exchange backup” in the EMC NetWorker Module for Microsoft Applications Release 2. In case of cluster. fail. check if nodes of virtual server are able to pass this test and the virtual server is reachable. pass. Both forward and reverse DNS lookup should pass. either uninstall them or stop their execution. Generic checklist 21 . • If enabled. remove any that is installed.2 SP1 Administration Guide provides details. Firewall is enabled.Otherwise. Review the following checklist before installing NMM 2. or storage If yes. If IPv6 is enabled.2 SP1. fail. If yes. Otherwise. check with the backup administrator that this machine is not being backed up with some other backup software. DNS. Note: NMM can be installed on NetWorker storage node in case of proxy. pass. and there are no IP conflicts. • 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. Preinstallation information Generic checklist Table 5 on page 21 provides the generic checklist for NMM 2. In case of cluster. Dual-NIC environment. Only Exchange is supported in dual-NIC scenario. Also. Host can connect with NetWorker server. then pass. pass. node hosts and this host is reachable from other hosts. Table 5 Generic checklist (page 1 of 3) Check to see if: Details Supported operating system version and service pack level are Supported: correct. check if nodes of virtual server are able to pass this test and the virtual server is reachable. If the firewall is configured for NMM. If yes. NMM will not work properly.

Correct licenses are installed on NetWorker Server. and later Note: NetWorker Server and storage node version 7. The following command lists the shadow copy storage association for each volume: vssadmin list shadowstorage After running this command. 22 EMC NetWorker Module for Microsoft Applications Release 2.3 and later • Deduplication: NetWorker 7. NetWorker Storage Node. If no. • SharePoint granular: 7. Application host and proxy host have same OS. Otherwise.5.3. After installing NMM.3 or later server” on page 15 • Avamar Axiom 4. will support all features for NMM. SP1 and cumulative update 3 and later. Set client retries to 0. Software and Hardware Providers are being used at the same time. Using both will cause backup to fail.5. • NetWorker Server and Storage Node: version 7. Client retries is set to 0 in group properties. there is enough free space to create shadow Ensure that a maximum area limit has not been set for shadow copies. same service pack.4. BitLocker encryption is enabled. Group inactivity timeout is set to 0. Only English path is supported. and PowerSnap If yes.2 and later • Exchange incremental backup: NetWorker Server 7. Disable BitLocker encryption because Bitlocker encryption is not supported. services.Preinstallation information Table 5 Generic checklist (page 2 of 3) Check to see if: Details VSS Admin List volume — This gives a list of volumes that can be The saveset should only contain these volumes. NMM does not support RAW disks.4.0.1.3 and later and other applications are installed.1. Replication Manager. For Software Provider. Check for writer stability. start the services. pass. Correct versions of NetWorker Server. Replication Manager Exchange interface Service. Install path is English only. Set group inactivity time-out to 0.0.2.1. fail.3 and later • NetWorker Server or NetWorker storage node OS Linux: 7.5 SP1 and later • NetWorker cloning and staging support: NetWorker Server 7.1 and Solution Enabler version 7. If the volume being backed up is one of the list.42 If there are providers other than Microsoft provider. the various “Installation services” on page 14 and “Verifying the installation” on page 37 services are up and running.2 SP1 Installation Guide . If application host and proxy host do not match backups would not work fine same platform. check that the value “Maximum Shadow Copy Storage space:” is set to “UNBOUNDED” for the volume chosen for backup. Use either software provider or Hardware Provider. 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. used for snapshots. Microsoft SharePoint Service Controller (granular). they will be used for the volumes they are associated with. pass. provides details.5 SP1 and “Patch for deduplication backup of NMM Client if using NetWorker 7.5. Any of the disks are RAW. VSS hardware provider version 4. and similar patch levelI. copies for each volume. If yes.

• The release notes for the EMC VSS Common Provider can be found on Powerlink at http://Powerlink. • Windows Unified Data Storage Server (WUDSS) — The Microsoft documentation provides information on access and support.com. Dynamic disks are not supported in an MSCS cluster.EMC. Otherwise. Note: MSDTC is not required for Window 2008 (Exchange). 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. fail. • SP2 and R2 SP2 require Microsoft hotfix described in KnowledgeBase article KB919117.EMC. pass. • Dell/EqualLogic Integration ToolKit for EqualLogic PS Series arrays — The Dell documentation provides information on access and support. • 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. 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. fail. Generic checklist 23 .ibm.com.wss?uid=ssg1S4000372 &rs=555. The appropriate snapshot software for the array is installed and If yes. Otherwise. pass.EMC.com/support/docview. 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. • IBM DS6000 and DS8000 arrays — The IBM System Storage DS Open API Package is available at http://www-1. Preinstallation information Table 5 Generic checklist (page 3 of 3) Check to see if: Details Cluster type and cluster requirements. • EMC Celerra VSS Provider for Celerra arrays — The EMC Celerra VSS Provider is available on Powerlink at http://Powerlink.com.

06.2 (only applies if PowerPath is installed) Note: On ESX server. NaviAgent is recommended on both host and guest. Otherwise. If yes. The PowerPath version installed is correct. pass. authority listing. pass. on ESX server. raw mapping device from the ESX server to the guest virtual machine. In VMware environment. • IP address of CLARiiON must be mentioned in iSCSI Initiator. pass. Otherwise. Host must be visible on CLARiiON. fail. fail. • There is no mention of iSCSI in the Provider Support Matrix: • Replication Manager supports Matrix and supports iSCSI for CLARiiON with the iSCSI initiator.07.2 SP1 Installation Guide . Note: PowerPath is not be required for EMC iSCSI on Windows 2008.2. The target CLARiiON IP addresses are in the SYMAPI If yes. PowerPath is not required.2 SP1. The HBA driver version installed is correct. Otherwise.42 • The version of Solutions Enabler is the one that was provided with the VSS Hardware Provider version. PowerPath is not supported in VMware — VMware has its own path management capability. fail.1. • Version 2. The appropriate Windows VSS/VDS hotfixes are If yes. step 3 provides details about how to verify that the SYMCFG authorization list has been updated correctly. 24 EMC NetWorker Module for Microsoft Applications Release 2. Otherwise.2 SP1. Note: EMC requires “EMC certified” drivers for both Emules and Qlogic Fiber channel cards. 2008. or 2.1. fail. The EMC support matrix carries only the most current and previous version.1 exact or minimum revision level. is installed. Also.Preinstallation information CLARiiON checklist Table 6 on page 24 provides the checklist for CLARiiON for NMM 2.0. fail. In virtual machine environment. EMC PowerPath® is installed.08 is required. The iSCSI Initiator version installed is correct. Otherwise. pass. • EMC FLARE® 26 required • AULA mode required.01 • For Windows 2008: minimum 5. installed. Must be a STORport driver. Solution Enabler version 7. Review the following checklist before installing NMM 2. but iSCSI must be specified as part of the PowerPath install. • For Windows 2003 (and R2) /SP2: Minimum 5. 2. pass. • PowerPath can handle both SAN and iSCSI. The multipathing feature is installed on Windows Server • If multipathing is enabled on Windows 2008. LUNs are assigned as If yes.1. Table 6 CLARiiON checklist (page 1 of 3) Check to see if: Details Client and proxy base-level software requirements • VSS Hardware Provider is installed and meets an VSS Hardware Provider 4. NavihostAgent If yes. PowerPath is not a mandatory requirement. Note: “Update the SYMCFG authorization list” on page 62.

fail. Otherwise.0. • The CLARiiON failover mode or trespassing must be set to 1. Otherwise. fail. • For iSCSI. Otherwise.0. pass. If there are LUNs in the reserved LUN pool. CLARiiON setup The host's NaviCLI version is compatible with CLARiiON • If host NaviCLI version is the same or higher than CLARiiON release version.9. pass.0. Otherwise. then pass. There are LUNs in the reserved LUN pool. pass. username and password are the credentials of ESX.0.7 • For Windows 2003 with FLARE 20: minimum Admsnap 2. fail. If yes.7 • For Windows 2003 with FLARE 22: minimum Admsnap 2.0 • For Windows 2003 and 2008 FLARE 28: minimum Admsnap 2.9. Otherwise. • If host NaviCLI version is lower than CLARiiON release version. fail. The following CLARiiON arrays running FLARE are supported: 19. fail. fail. • For Windows 2003 with FLARE 19: minimum Admsnap 2. Admsnap is installed and its location is in system If installed and in location is in system environment variable. 22. The FLARE operating environment version installed on If the release of the CLARiiON is in the list.2 The SPA and SPB belong to the same CLARiiON. Otherwise. There are clone private LUNs. Preinstallation information Table 6 CLARiiON checklist (page 2 of 3) Check to see if: Details In virtual machine environment. environment variable.7 • For Windows 2003 with FLARE 26: minimum Admsnap 2. pass. pass. The failover mode settings for the CLARiiON are set: If yes.0. pass. or 28 EMC Access Logix™ is active.0. If yes. The array is capable of creating clones. 26. Otherwise. the connectivity is 4. If clones are enabled. SNAPVIEW enabler installed.0. Otherwise.0. Note: Ensure that the number of LUNs in the LUN pool are sufficient to cover the number of snapshots at any given time. If clones are private clones. then pass. fail.0. If enabler is present. Otherwise. fail.0. fail. are in system environment variable. then pass.7 • For Windows 2003 with FLARE 24: minimum Admsnap 2. fail. pass. pass. the authorization has If yes. Otherwise. The Admsnap version installed is correct. 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. 24. fail. CLARiiON. Otherwise.0. the CLARiiON arrays is correct.28. Otherwise.24. fail.9. 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. CLARiiON checklist 25 . pass.9. The specified username and password works for that If yes. array release. fail.0. pass.

Otherwise. Otherwise. 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.2 SP1 Installation Guide . • If the privileged user list was empty. fail. Orphaned snapshot or snap session for particular storage If yes. Otherwise.0 with SP2. Ensure that the services are started. Microsoft SharePoint checklist Table 7 on page 26 provides the checklist for SharePoint for NMM 2. • Microsoft Office Server Search Writer for Microsoft Office Server search — If not running. Server. NMM granular backup. fail.0 with SP2. such If yes. then it is a warning to check if role is enabled.2 SP1. Otherwise. pass. pass. pass if cluster in healthy. username and password are the credentials of ESX. Host is registered with both SPA and SPB. If yes. fail. pass. Enterprise editions with SP2 or later and Windows SharePoint Services 3. Otherwise. pass. fail. then fail. The Solutions Enabler is licensed. fail. then it is a warning to check if role is enabled. 26 EMC NetWorker Module for Microsoft Applications Release 2. "system@<host_id>” is in the “privileged user” list on the • If there are privileged users and system@<hostId> is not in the list. Ensure that the services are started. pass. Otherwise. as PowerPath and Navisphere for EMC CLARiiON host-based utilities. or Enterprise editions with SP2 is installed. At least one CLARiiON LUN is visible to the proxy. If yes. pass. Cluster is installed. All essential SharePoint services are up and running: If yes. Saveset has one partition per LUN. • Microsoft SharePoint Server 2003 (for x86) Standard or Enterprise editions with SP2 and Windows SharePoint Services 2. KB971538 for Microsoft Office SharePoint Server 2007 (for x86 and x64) Standard If yes. Review the following checklist before installing NMM 2. fail. as required by the supporting array and customer environment are installed. pass. then delete them. The appropriate host-based EMC storage software. then pass. Otherwise. then unknown. machine: C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u <username> -p <password> -s <esx_network_address> [-force]] where. pass. group is present. CLARiiON.2 SP1. fail. then check the state of the cluster service for SQL Virtual For WSFC or MSCS. Table 7 SharePoint checklist (page 1 of 2) Check to see if: Details • Microsoft Office SharePoint Server 2007 (for x86 and x64) Standard or If yes. Otherwise. • 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. fail. If yes. NMM Client is installed on all machines participating in a farm in web front-end for If yes.Preinstallation information Table 6 CLARiiON checklist (page 3 of 3) Check to see if: Details The CLARiiON using NaviCLI (classic) interface to see if • If there are privileged users and the system@<host_Id> is on the list.

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

Otherwise. later for Exchange 2007. backup. If appropriate privileges are present. Credentials of user of Exchange Server are correct. Otherwise. which means a maximum of 32 storage groups. if If yes. pass. If yes. Otherwise. pass. pass. The writer for both the active node and passive node in the CCR environment is stable. Otherwise. Otherwise. fail. fail. the health of CCR before taking If yes. The saveset contains only Exchange writer and that no other writer is included during backup. pass. • System path and the log path are in the same location. The group are properly mounted. that is. If yes.2 SP1 Installation Guide . pass.1 or If yes. then check the state of the cluster service. pass. installed. else the whole backup will fail.2. pass. Exchange management tools are installed on proxy client. fail. fail. fail. • In hardware scenario. fail. pass. pass.Preinstallation information Table 8 Exchange checklist Check to see if: Details • Microsoft Exchange Server 2003 (for x86) Standard and Enterprise editions with SP2 or later is If yes. Message API (MAPI) and Collaboration Data Object (CDO) kits are installed and are version 1. Cluster is installed. Otherwise. • 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. The CCR of active node and passive node is consistent. NSR_EXCHANGE_LIMIT_SG=yes. 28 EMC NetWorker Module for Microsoft Applications Release 2. fail. Exchange server is a part of domain. fail. If yes. pass if cluster in healthy. Otherwise. If yes. the system files and log files are in different LUNs. • In normal backup of Exchange. the maximum limit is governed by a limit of 64 snapshots. Otherwise. fail. Backup is grouped with not more than ten storage groups at a time. pass. Essential Exchange Services are up and running: If yes. pass. Exchange storage groups locale should be the same as the Exchange server locale. fail. For WSFC or MSCS. • Microsoft Exchange Server 2007 (for x64) Standard and Enterprise Edition with SPI or later is installed. If yes. fail. Otherwise. pass. pass. If yes. Otherwise. Otherwise. fail. Otherwise. Otherwise. the database files and transaction log files are in different volumes.

3 or later. 2. Preinstallation information 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. Supported configurations 29 .3 or later. In a LAN-based configuration. Note: In Figure 1 on page 30. The data path to the NetWorker storage node devices is over a LAN. Figure 2 on page 31. or tape. initiates the process by contacting the application server where the NMM software is installed. the production data is stored on a storage area network (SAN) or direct-attached storage (DAS). and Figure 3 on page 32 is given as 7. 3. use NetWorker Storage Node release 7. The application server that is being protected has the NMM installed.3.3.3. Simple LAN-based configuration Figure 1 on page 30 shows a simple LAN-based configuration with a storage area network. which must be release 7.x. advanced file type disk. The NetWorker Server. The application server with the NMM software creates a snapshot of the data on the storage volume. 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. snapshots are represented by S1 through S5. The data moves as follows: 1.

it is known as a serverless backup. The NetWorker server initiates the process by contacting the application server where the NMM software is installed.3 or later LAN Application server NetWorker Module for Microsoft Applications NetWorker Traditional SAN Storage storage Node 7. A proxy client is a host that acts as a remote data mover (DM) when snapshots are rolled over to a conventional backup medium. Backup and recovery will fail if NMM 2.2 SP1 is installed on either the application server or the proxy client machine. Both the application server and the proxy client have the NMM installed. The application server with the NMM software creates a snapshot of the data on the storage volume. 30 EMC NetWorker Module for Microsoft Applications Release 2. 2.Preinstallation information NetWorker Server 7. A proxy client frees resources on the application server. and an earlier version of NMM is used on the other. then the other machine must also use NMM 2.3. snapshots are represented by S1 through S5. Install the proxy client software by using the NMM software package.2 SP1.2 SP1 is used on one of these machines. When a backup operation uses a proxy client. Note: In Figure 2 on page 31.2 SP1. 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.2 SP1 Installation Guide . NetWorker Module for Microsoft Applications release 2.3. If NMM 2.x Primary storage S4 (For example. Note: The application server and the proxy client must use the same version. The data moves as follows: 1.

3. The snapshot is made visible to the proxy client. or tape. The NetWorker Server initiates the process by contacting the application server where the NMM software is installed.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. S5 S3 CLARiiON or Symmetrix) 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. Preinstallation information 3.x (For example.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. The NMM is installed on the application server. 4. NetWorker Server 7. Network traffic is avoided because both the conventional backup device and the snapshot are directly attached to the storage node. The application server with the NMM software creates a snapshot of the data on the storage volume.3. The snapshot is made visible to the proxy client.3. The data moves as follows: 1. 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. snapshots are represented by S1 through S5. The proxy client is installed on the NetWorker storage node. 3. 2. Note: In Figure 3 on page 32. You can set up a NetWorker storage node release 7. Supported configurations 31 .

The proxy client. The NetWorker Server and the application server communicate through the LAN. or tape.x SAN Traditional Primary storage S4 storage (For example. S5 S3 CLARiiON or Symmetrix) S1 S2 GEN-000750 Figure 3 LAN-free configuration 32 EMC NetWorker Module for Microsoft Applications Release 2. However.3 or later LAN Application server Proxy client NetWorker Module for NetWorker Storage Microsoft Applications Node 7.3. in this case the storage node.2 SP1 Installation Guide .Preinstallation information 4.3. 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. NetWorker Server 7. the data itself is not transferred across the LAN because the conventional backup medium is attached directly to the NetWorker storage node.

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

and you are not required to install a NetWorker Client before installing the NMM software.The Welcome to NetWorker Module for Microsoft Applications Installation wizard appears. you are ready to begin the installation. The License Agreement dialog box appears. only the NetWorker Storage Node should be installed. Read the license agreement. The NetWorker Client is included with the NMM software. 3.com. except if you want to use the LAN-free configuration. Install the software Once you have accessed the NMM software files. 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. click the NetWorker Module for Microsoft Applications Release 2.exe) to start the installation wizard. Log in as administrator or equivalent on the NetWorker Server. 2. In the table of NetWorker Module Software Downloads. 4. 5. The Installation Location dialog box appears. Go to http://Powerlink. Type the name and organization information and click Next. 3.2 SP1 Installation Guide . Run setup. From a DVD To access the NMM software from a local DVD: 1.EMC. To install the NMM software on a Microsoft Windows computer. To install NMM: 1. Select Support > Software Downloads and Licensing > Downloads J-O > NetWorker Module. To accept.exe directly from the DVD. Click Next. 3. From the EMC website To access the evaluation version of the NMM software from the EMC Support website: 1. To choose an alternate location for the installation folder: 34 EMC NetWorker Module for Microsoft Applications Release 2. 2. Run the Setup program (setup.Installing the Software Installing NMM ! CAUTION Remove all previous installations of NetWorker before installing NMM. In the LAN-free configuration. and click Next. The Customer Information dialog box appears. 2. select the I accept the terms in the license agreement option.2 SP1. Insert the NMM DVD into the DVD drive.

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

PowerSnap services.host=VSS_cluster_node user=system. Note: EMC Solutions Enabler will be present only when using EMC VSS Provider.” provides detailed instructions. The EMC NetWorker Module for Microsoft Applications Release 2. Install the NMM software on the private disk of each physical node. “Configuring the Software. 36 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide provides details about installing and running Solutions Enabler. The EMC Solutions Enabler Version 6. To install the NMM software in a MSCS environment: 1. if you plan to use CLARiiON or Symmetrix hardware with EMC VSS Provider. 4. In the NetWorker Module for Microsoft Applications Setup Complete window. and the NMM software. The Microsoft website provides information about deploying Microsoft Exchange Server 2003 in a cluster.” provides detailed instructions. 3. Installing NMM in a MSCS environment When installing the NMM software in a Microsoft Cluster Server (MSCS) environment.host=VSS_cluster_node where VSS_cluster_node is the DNS hostname of the physical node.2 SP1 Installation Guide . In the Remote Access attribute of each virtual client resource. 13. or Programs and Features in Microsoft Windows Server 2008. appear as separate entries under Add/Remove Programs in Microsoft Windows Server 2003. 2. “Licensing and Enabling the Software. Configure each physical node as a client resource on the NetWorker Server. type the names of the physical nodes. Chapter 4. Configure privileges for each physical node on the NetWorker Server: c. • The Replication Manager. Configure the setup according to instructions in Chapter 5. and Solutions Enabler requires that MSDTC be running. Click OK. click Finish to complete the installation and exit the installation wizard. In the Users attribute of the Administrators user group.Installing the Software b.2 SP1 Administration Guide provides more information about configuring a clustered client resource. Add each value on a separate line: user=administrator. The EMC VSS Provider will install EMC Solutions Enabler. 12. add the following values for each physical node in the cluster. d. Enable and register the NMM software. Click OK. 11. During the NMM installation: • Replication Manager and PowerSnap services are installed along with the NMM software. ensure that first Microsoft Distributed Transaction Coordinator (MSDTC) is installed and running before installing the EMC VSS Provider.

Verifying the installation Ensure that the following services are up and running: ◆ For NetWorker — nsrexecd. or • Select Start > Settings > Control Panel > Add/Remove Programs. Note: Do not use autorun. There is no GUI when NMM is installed on 2008 Server Core. 2. This installation wizard is the same wizard that is started while installing NMM on other OS. by using FTP or general access method. Log in as administrator on the client server. To run the Setup program in maintenance mode: 1. however the NMM installation wizard starts. Copy the NMM binaries to the 2008 Server Core. 2.exe in the networkr directory and press Enter to start NMM installation. 3.exe ◆ For PowerSnap — nsrpsd. Use the net use command to access remote machines from the 2008 Server Core. Access the NMM binaries as described in “Access the installation files” on page 34. Installing NMM on Windows 2008 Server Core 37 . 1.exe to install the NMM software. Access setup. To run the Setup program in maintenance mode. Installing the Software Installing NMM on Windows 2008 Server Core To install the NMM software on Windows 2008 Server Core: 1. perform one of the following: • Run the setup.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. The Welcome to NetWorker Module for Microsoft Applications Maintenance dialog box appears. Click Next.exe ◆ For Replication Manager — irccd. The Setup program detects the existing NMM installation and displays the Maintenance Type dialog box. Select the NetWorker Module for Microsoft Applications and click Change. you may run the Setup program in maintenance mode to change or remove the existing client installation.exe file.

Click Update List to browse for all the available servers. “Removing the software” on page 38 provides more information.Installing the Software 4. select Change and click Next. 5. 4. 2. the default server is used to back up the data on the client. Click Next. “Maintaining the installation” on page 37 provides more information. b. Start the Setup program in the maintenance mode. In the Maintenance Type dialog box. and click Add to add a server to the Available Servers list.2 SP1 Installation Guide . 5. Type a server name in the Enter a server name field. d. 3. Click Next. The Ready to Change dialog box appears. Select the type of maintenance to perform: • Use the Change option to change: – The configuration settings of the NetWorker SharePoint Service Configuration dialog box. – To a different authorized NetWorker Server. “Maintaining the installation” on page 37 provides more information. ! CAUTION If an authorized server list is used together with a proxy server. Note: The selected NetWorker Server is used to back up the data on the client. 38 EMC NetWorker Module for Microsoft Applications Release 2. Changing the password or changing to a different authorized server To change the password or change to a different authorized server: 1. In the Ready to Change dialog box. Select a server from the Available Servers list and click to move the server to the Selected Servers list. • Use the Remove option to remove the NMM software from the system. do any of the following: a. select Remove and then click Next. In the Maintenance Type dialog box. click Change to proceed. c. then the proxy server must also authorize the production server. Start the Setup program in the maintenance mode. 2. If you have not selected an alternate server. Removing the software To remove the NMM software: 1. and the production server authorize the proxy server. Select a server from the Selected Servers list and click to return it to the Available Servers list. – The password for Exchange Server by using nwexinfo. In the NetWorker Server Selection dialog box. “Changing the password or changing to a different authorized server” on page 38 provides more information.

log files. select the Remove NetWorker Module for Microsoft Applications Metadata option to remove the existing metadata. Delete PowerSnap entries using the PowerSnap Client SnapManager or nsrnapadmin. This metadata. Upgrading the software A direct upgrade of an existing installation of NMM or NetWorker VSS Client to NMM 2. Note: You may decide to keep the existing metadata for installation of NMM 2. Upgrading to NMM storage node NMM supports upgrading NetWorker 7. for example the media database. and the Legato and RMService registry entries are removed. and select EMC Solutions Enabler. 3. client file indexes. • NMM creates and maintains several types of metadata in the course of operation. Note: Removing NMM. Before installing NMM release 2. • To keep the existing metadata for reinstallation of NMM.2 SP1. then leave the Remove NetWorker Module for Microsoft Applications Metadata option clear. In the Ready to Remove dialog box. Select the Remove option. Removing previous installation of Solutions Enabler 39 . Installing the Software 3. Stop the Solutions Enabler services before uninstalling the Solutions Enabler software by using the following command: net stop storapid 2. Removing previous installation of Solutions Enabler To uninstall Solutions Enabler: 1. Click Remove.3 or later to NMM storage node.3.2 SP1: ◆ Remove any existing version of NMM or NetWorker VSS Client by running the Setup program in maintenance mode. Click Remove. also removes the PowerSnap and Replication Manager services. “Removing the software” on page 38 provides more information. The three entries for these programs are removed from under Add/Remove Programs in the Control Panel. Ensure that PowerSnap snapshot entries are deleted before reinstallation.2 SP1 cannot be done. ◆ Remove all existing snapshots. 4. the Legato and rmagentps directories. Select Start > Settings > Control Panel > Add/Remove Programs.

When the Proceed message box is displayed. This could lead to a user creating an invalid saveset. but do not click OK to proceed on the web front end yet. click OK on all remote clients. a message window appears. It states that an existing NetWorker storage node installation has been detected. When installing SP1 on a SharePoint farm. 4.2 SP1 Installation Guide . and then click OK to proceed with installation on the web front end. “Installing NMM” on page 34 provides more information. Start the SharePoint configuration wizard. 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. Go to the Microsoft website and search for “Microsoft Office SharePoint Server 2007 Service Pack 1 (SP1). Ensure that you have installed the NetWorker storage node on the server. no further action is required for NMM.5. Once it is installed. 3. After installation completes on all remote clients. 40 EMC NetWorker Module for Microsoft Applications Release 2. Note: When the NMM installation detects that a NetWorker storage node is already installed on the server. 2.Installing the Software 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. 3. Installing Microsoft Office SharePoint Server service pack Microsoft Office SharePoint Server Service Pack 1 (SP1 or later) must be installed.” Download and install this service pack on all machines in the SharePoint Server farm.x Multiplatform Version Installation Guide provides information about installing the NetWorker storage node. click OK on all remote clients. Without this fix installed on SharePoint machines. the NMM storage node cannot be used as the NMM Client. Click OK to upgrade to NMM storage node. Start the SP1 installation on all machines at the same time. ! IMPORTANT Although the PowerSnap service and Replication Manager service binaries are installed on the existing storage node during the upgrade procedure. and backup or recovery failure. 2. Microsoft recommends installing it in a specific order: 1. and asks if you want to install the NetWorker Module for Microsoft Applications Client as the storage node. Install the NMM software. The EMC NetWorker Release 7. The NMM storage node is installed.

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

exe commands directly in the command line.2 SP1 provides support for: ◆ Silent (unattended) installation and removal of the software on a standalone server. The silent (unattended) installation status log files are available in the client computer’s temp directory. “Silent installation of NMM” on page 42 and “Silent removal of NMM” on page 46 provide more information. You may type full setup. In a basic silent installation. “Installing and removing NMM by using SCCM 2007 Server” on page 48 provides more information. or may include such commands in scripts and save it as a . ◆ Remote installation and removal of the software by using Microsoft System Center Configuration Manager 2007 (SCCM) Server. which makes any GUI dialog boxes unnecessary. In this process. and then the PowerSnap and Replication Manager services.exe) from the command line. first the NetWorker software is installed.Silent Installation of the Software Overview This release of NMM 2. 2. all the information that is required for a successful installation is gathered by the Setup file (setup.cmd file. 42 EMC NetWorker Module for Microsoft Applications Release 2. Silent installation of NMM Silent installation of NMM 2. Type %temp%.2 SP1 Installation Guide . Click Start > Run.2 SP1 is a standalone method that uses the command line and scripts. ! IMPORTANT Silent installation of NMM as a storage node is not supported. For fast access to the temp directory: 1.

The log file is created in the %temp% /s and /v”/l*v directory. which is an engine for the installation.2 SP1. Ensure to use triple quotes in the command /v”/l*v and \"%temp%\mylog.log""" Silent installation of NMM 43 . Note: Ensure that there is space between: This command is useful for troubleshooting installation setup and /s problems. \"%temp%\mylog. 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. and removal of software on modern Microsoft Windows systems: setup /s /v" qn /L*v """%temp%\filename.log\" and /qb Note: The following command opens the Windows Installer. maintenance. Silent Installation of the Software Commands for silent installation of NMM Table 9 on page 43 lists the commands for silent installation of NMM 2.log\" /qb Installs NMM and creates a MSI log file. Table 9 Commands for silent installation of NMM Option Description setup /s /v" /qb" Silent installation with progress bar.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. Note: Ensure that there is space between: setup and /s /s and /v” /v” and /qn” setup /s /v"/l*v \"%temp%\mylog.log\" in case the %temp% path contains spaces.

Host. The use of triple quotes when specifying one server is optional. set value to 1. To create the SERVERS file with a list of NetWorker servers to back up the NMM Client. Table 10 NetWorker NMM command line properties Property Value Description INSTALLDIR default = %SystemDrive%\Program Files\Legato\nsr Changes the installation directory for NMM. NW_REMOVEMETADATA {0|1}default = 0 (leave metadata) When removing NMM.Silent Installation of the Software NetWorker NMM command line properties Table 10 on page 44 lists the command line properties that are recognized for NetWorker NMM. use the following syntax: INSTALLDIR="""c:\program files\legato""" Note: Ensure to use triple quotes in the syntax. the metadata is removed. if the value is set to 1. NW_SERVERS default = <no NW servers name specified> By default. otherwise set value to 0. Always set value to 1. VSS. 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. and VSS Features to be installed for x64. Host. To specify a pathname that contains spaces. RMDPORT default = 6729 Specify Replication Manager data port. VSSREG 0 Always set value to 0. use the following syntax: SERVERS="""srv1 srv2""" Note: Ensure to use triple quotes when specifying more than one server. ADDLOCAL (x64) Proxy. All values must be specified. 44 EMC NetWorker Module for Microsoft Applications Release 2. RMCPORT default = 6728 Specify Replication Manager control port. and EMCRecoverPoint Features to be installed for x86. DORMINST 1 Install Replication Manager. DORMINST_EXCH {1|0} To install Exchange.2 SP1 Installation Guide . the \res\server file is blank when the servers command is not used or no name is used after the server command. DORMINST_VSS 1 Always set value to 1. ADDLOCAL (x86) Proxy. Always set value to S. REBOOT S Suppress Reboot. Table 11 PowerSnap and Replication Manager command line properties Property Value Description ALLUSERS 1 Always set value to 1. All values must be specified.

Silent Installation of the Software Sample commands for silent installation of NMM This section contains sample commands that you can use for silent installation of NetWorker. For PowerSnap/Replication Manager silent install for nt86: \networkr\ps\setup.Host. and Replication Manager. In this sample command: ◆ The NetWorker software is installed in the C:\Legato\nsr directory.exe /s /v"/qb ALLUSERS=1 VSSREG=0 REBOOT=S RMCPORT=6728 RMDPORT=6729 DORMINST=1 DORMINST_EXCH=0 DORMINST_VSS=1 ADDLOCAL=Proxy.log directory.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.log ””” INSTALLDIR="""c:\Legato\nsr"""NW_SERVERS= """server1 server2""" " / w Note: Ensure that there is space between: setup and /s /s and /v" /v" and /qn /qn and /L*v /L*v and ”””%temp%\NMMinstall11.EMCRecoverPoint"/ w For PowerSnap/Replication Manager silent install for ntx64: \networkr\ps\setup. PowerSnap. ◆ None of the properties are optional.Host.log is created in %temp%\filename. the Replication Manager service is also installed. Sample 1 This sample command contains all the properties that can be passed from the command line for NetWorker.VSS"/ w Silent installation of NMM 45 . ◆ A MSI log file NMMinstall11. ◆ A SERVERS file contains the server names server1 and server2.VSS.log””” ”””%temp%\NMMinstall11. \networker\setup /s /v" /qn /L*v ”””%temp%\NMMinstall11. ◆ When the PowerSnap service is installed. These properties are optional.exe /s /v"/qb ALLUSERS=1 VSSREG=0 REBOOT=S RMCPORT=6728 RMDPORT=6729 DORMINST=1 DORMINST_EXCH=0 DORMINST_VSS=1 ADDLOCAL=Proxy.

and remove the metadata: \networkr\setup.log""" \NMMuninstall.cmd is replaced by .cmd.cmd script is the master script.exe is located. For example.cmd script is used for the silent installation of the NMM 2.2 SP1 installation media kit.2 SP1 Installation Guide .log""" and " " and /x ◆ Use the following command to remove NetWorker. and executes all the scripts in Table 12 on page 47. When the PowerSnap service is removed.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. create a MSI log file.log.log""" /L*v """%temp%\PSuninstall. 46 EMC NetWorker Module for Microsoft Applications Release 2.log""" NW_REMOVEMETADATA=1" /x Note: Ensure that there is space between: \networkr\setup. whose name is the same as the script.exe and /s /s and /v /v and "/qn "/qn and /L*v """%temp%\NMMuninstall.2 SP1 software.Silent Installation of the Software Silent removal of NMM In a silent removal of NMM 2.exe /s /v "/qn /L*v """%temp%\NMMuninstall.exe and /s /s and /v /v and "/qn "/qn and /L*v """%temp%\PSuninstall. Commands for silent removal of NMM ◆ Use the following command to remove PowerSnap and Replication Manager services: \networkr\ps\setup. the Replication Manager service is also removed.log.log""" " /x Note: Ensure that there is space between: \networkr\ps\setup. first the PowerSnap service is removed and then the NetWorker software.exe /s /v "/qn /L*v """%temp%\PSuninstall. Each sample script creates a log in the %temp% directory.cmd is named install_nmm_silent_sample. the log for install_nmm_silent_sample. in the directory where setup. These logs can be used to troubleshoot installation problems. The install_nmm_silent_sample. the only difference being that the file extension . All of these samples are included in the NMM 2. except for uninstall_nmm_silent_sample.2 SP1. The install_nmm_silent_sample.

Checks if NMM or NetWorker is installed. uninstall_nmm_silent_sample.2 SP1 software.0.cmd Silently removes the NMM 2. Configures the Windows firewall.0. Installs the Microsoft VC80 side-by-side redistributable DLLs. DotNetInst. 4. NMMInstalled.log""" and " " and / / and w Sample scripts for installation and removal of NMM 47 . You can modify these sample scripts to provide correct installations for your environment.cmd Installs Microsoft . This sample script can be modified by the customer. Table 12 Sample scripts for silent installation Script name Description install_nmm_silent_sample. Installs the PowerSnap and Replication Manager services.NET Framework 2. DotNetInstalled. 3.NET Framework 2. 5.2 SP1 software.log""" " / w Note: Ensure that there is space between: %~dp0\setup and /s /s and /v"/qn /v"/qn and /L*v /L*v and """%temp%\NMMinstall.log""" """%temp%\NMMinstall.vbs Configures the Windows firewall for NMM.vbs Determines if NMM or NetWorker is currently installed.cmd Silently installs the NMM 2.vbs Determines if Microsoft . 2.cmd script performs the following: 1.cmd script uses the following command to install NMM. 6.cmd script The install_nmm_silent_sample. if it is not installed. How to install the NMM software using the default installation path The install_nmm_silent_sample. NMMConfigFW. the script exits. Silent Installation of the Software The install_nmm_silent_sample.0 is currently installed. Installs NetWorker. Installs the Microsoft . and uses the default installation path and leaves res\server file blank: %~dp0\setup /s /v"/qn /L*v """%temp%\NMMinstall. This sample script can be modified by the customer. If either is installed.NET Framework 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. Copy the NMM 2. use the following command: @rem %~dp0\setup /s /v"/qn /L*v """%temp%\nmminstall. b. and other information for the new package.log""" """%temp%\nmminstall. 48 EMC NetWorker Module for Microsoft Applications Release 2. b.2 SP1 Installation Guide .2 SP1 software is to be installed. distribution settings. • In Environment Wizard window: a. “Sample scripts for installation and removal of NMM” on page 46 provides details about the scripts’ function. 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. Installing and removing NMM by using SCCM 2007 Server To install NMM 2. the install_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. Start the New Program Wizard. where the NMM 2. 2.log""" and INSTALLDIR="""c:\Legato"""NW_SERVERS="""serv1 INSTALLDIR="""c:\Legato"""NW_SERVERS="""serv1 and serv2""" serv2""" and " " and / / and w By default.cmd file in /networker directory.cmd file as a source installation file in SCCM Server: a. Use the New Package Wizard to create a software distribution package. 4. 3. Click Browse in the General Tab. Use the default setting for all other options.2 SP1 by using the Microsoft System Center Configuration Manager (SCCM) 2007 server: 1.Silent Installation of the Software 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. this command is disabled by rem in install_nmm_silent_sample. Use the New Collection Wizard to specify the client machine. Ensure that the administrative rights are set to Run Mode. data source.cmd and uninstall_nmm_silent_sample. select Show all files. Specify general information.log""" INSTALLDIR="""c:\Legato"""NW_SERVERS="""serv1 serv2""" " / w Note: Ensure that there is space between: @rem and %~dp0\setup %~dp0\setup and /s /s and /v"/qn /v"/qn and /L*v /L*v and """%temp%\nmminstall. • To use the Install_nmm_silent_sample.cmd file. and then select the install_nmm_silent_sample.

use Run program from distribution point. 2. For fast access to the temp directory. or Programs and Features in Microsoft Windows Server 2008. If NMM. package name. The Replication Manager entry appears as RMagentPS: a. b. Replication Manager service 2. or you get an error about a service not starting. Check Add/Remove Programs in Microsoft Windows Server 2003. or if NMM is not running correctly after a fresh installation. PowerSnap service 3. Specify general information. Troubleshooting the installation This section provides tips to troubleshoot errors that may appear during installation. If all the three programs appear to be installed but not running. Troubleshooting the installation 49 . 1.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. PowerSnap service or Replication Manager service is missing. the SCCM Server is set up to install the software. The NMM software. For schedule option. remove all. It may take more than 30 minutes for the SCCM Server to process the advertised installation. The Advertisement Status section in SCCM Server can be used to check the installation process status. a problem in the installation is due to errors in the installation of Replication Manager services. select Run as soon as possible. Use the New Advertisement Wizard to create an advertisement. use uninstall_nmm_silent_sample. c. For delivery method. Remove the programs in the following order: 1. verify that the services for NMM. and the collection to which the advertisement should be distributed: a. Errors in installation of Replication Manager Most frequently. 5. and then reinstall.cmd file. when moving from a previous release of NMM or NetWorker VVS Client to NMM 2. PowerSnap. program. ◆ Instead of using the install_nmm_silent_sample.2 SP1. Silent Installation of the Software c. To remove NMM 2. Click Close to complete program creation. NMM software b. For all other options. Reinstall. use default setting to complete New Advertisement Wizard. and Replication Manager are running. and Replication Manager and PowerSnap services should appear installed. Once the advertisement is created. The SCCM server installation status log files are available in the client computer’s C:\Windows\temp directory. select Start > Run and then type %SystemRoot%\temp.cmd file.

remove and reinstall all of the programs as described in step a .exe and nsrpsd. ensure not to use non-English characters in the installation path because although NetWorker seems to be installed properly. 50 EMC NetWorker Module for Microsoft Applications Release 2.Silent Installation of the Software • If any of the services is not running.exe is not running. Using non-English characters in installation path During silent or GUI installation. • If irccd. but nsrexecd. then manually install the Replication Manager service from the following directory networkr\ps\rmc\setup.exe. the installation of PowerSnap service and Replication Manager service fail and an error message appears.2 SP1 Installation Guide .exe are running.

........................................................................................................ 54 ◆ Update enablers.............. 58 Licensing and Enabling the Software 51 ........................................................................................................................................................................................ 52 ◆ The evaluation process .............................................................................................. 4 Licensing and Enabling the Software This chapter includes the following sections: ◆ NMM client software licensing ................................. 53 ◆ The licensing process ................................... 57 ◆ Managing EMC licenses .....................

Each installation of NMM client must be licensed with an enabler that activates the software and allows you to use the software. Without these codes. The enabler name for NMM may vary depending on which version of NetWorker is installed. and in what order it was installed or upgraded: ◆ If an NMM add-on enabler is installed on NetWorker 7. Add-on enablers allow a broader scope of features. 52 EMC NetWorker Module for Microsoft Applications Release 2. All licensing takes place on the server. Base enablers come in different editions. The steps in this chapter assume that all of the software and hardware requirements have been met and the NMM client software is installed. which enable varying degrees of functionality. Even though both names are present. 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. with an add-on enabler that uses the old name. the enablers will be combined and used correctly as different client systems claim them. and the server enforces the licensing.Licensing and Enabling the Software NMM client software licensing The NetWorker software is installed in evaluation mode. ◆ If an NMM add-on enabler is installed on NetWorker prior to release 7. the add-on enabler is displayed as NetWorker Module for Microsoft Applications.4 SP2 or later. the existing add-on enabler is still displayed under the old VSS license name Volume Shadowcopy Service for Windows. and then a new NMM add-on enabler is installed. the add-on enabler is displayed under the old VSS license name Volume Shadowcopy Service for Windows. is upgraded to NetWorker Server 7. The licenses are typed and stored on the server. If the same NetWorker Server is then upgraded to NetWorker 7. The licensing of NetWorker software means entry of enabler and authorization codes on the server for the NetWorker environment. ◆ If an older version of NetWorker Server. the software or added features will not run beyond the evaluation period.2 SP1 Installation Guide .4 SP2 or later.4 SP2. Add-on enabler names The specific add-on enabler for the NMM client is NetWorker Module for Microsoft Applications. whether NetWorker Server has been upgraded.4 SP2 or later.

d. Typing a temporary enabler code ! CAUTION The temporary enabler code is valid on only one computer in a network. From the Enterprise menu. Start the NetWorker Management Console software. Launch the Administration window: a. If you type the same code on more than one computer in a network. By the end of the evaluation period. “Typing a temporary enabler code” on page 53 provides information about how to type the temporary enabler code. depending on the edition of the base enabler. you might need to purchase the NMM client add-on enabler. Licensing and Enabling the Software 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. click Launch Application. 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. you must purchase. “The licensing process” on page 54 provides instructions. To continue to use the modules and features that were available with the evaluation software. From the Console window. type. type. 2. c. To type the temporary enabler code: 1. you can evaluate it with all the modules and features for 30 days free without typing any codes. a copy protection violation error occurs and the NMM client software is disabled on all NetWorker Servers with duplicate enablers. The evaluation process 53 . By the end of the evaluation period. and authorize the corresponding license enablers to continue to use modules or features evaluated by you. 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. From the left pane. select the application. select a NetWorker Server in the Enterprise list. The temporary enabler is valid for 45 days. The base enabler is the license that enables the edition purchased. you must purchase. click Enterprise. The Administration window is launched as a separate application. From the right pane. b. and authorize a base enabler to continue to use the NMM client software to restore data.

From the left pane. From the Enterprise menu. In the left pane.2 SP1 Installation Guide . From the Console window. Click OK. type the enabler code. This licensing process is the same for all editions of software as well as for individual modules and features. In the Enabler Code attribute. type the base enabler last. select Registrations. The Create Registration dialog box appears. d. To type the license enabler code: 1. Start the NetWorker Management Console software. 5. Launch the Administration window: a. 54 EMC NetWorker Module for Microsoft Applications Release 2. (Optional) In the Comment attribute. 3. click the application. as a registration period. 4. From the Administration window. 4. and then authorize it. click a NetWorker Server in the Enterprise list. or on the Enabler Certificate you receive when you purchase a software license. select New. 5. From the File menu. 9. type the enabler code. select Launch Application. devices that do not yet have licenses typed may be disabled. 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. you must purchase and type a license enabler code. From the File menu. In the Name attribute. From the right pane. The licensing process To permanently use NMM client software. 7. In the Administration window. c. In the Enabler Code attribute. once a base enabler is typed. Those devices would have to be reenabled manually after their licenses are installed. 2. Otherwise. click Configuration. The license enabler code that you purchase is valid for 45 days. select New. b. click Configuration. 6. The Administration window is launched as a separate application. you must obtain and type a corresponding authorization code. 6. In the left pane. Note: To save time when typing multiple licenses.Licensing and Enabling the Software 3. This depends on whether the software purchased is a first-time purchase or an updated or upgraded version. 8. type the name of the license. During the registration period. select Registration. click Enterprise. type a description of the license.

select Launch Application. click the application.com.com. Licensing and Enabling the Software 7. go to the EMC CustomerNet portal at http://Powerlink. Start the NetWorker Management Console software. Click the Customer Information tab and complete your contact information. 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. 5.EMC. 3. 7. Repeat the procedure to add any additional enabler codes. you have 45 days as a registration period to authorize the NMM client software. Using the EMC website Register products and obtain authorization codes online by completing a registration form on the EMC website at http://Powerlink. Email your registration information. After you type a license enabler code.EMC. From the Enterprise menu. click Enterprise. 8. For contact information. From the Console window. 2. The Properties dialog box appears. The licensing process 55 . From the File menu. d. In the Name attribute. 9. type a description of the license. 7 days a week. In the left pane. 6. From the right pane. From the left pane. Web registration takes just a few minutes and is available 24 hours a day. click Configuration. b. the NMM client function or feature is disabled. The Administration window is launched as a separate application. select the NetWorker Server. type the name of the license. An authorization code that permanently enables the updated NetWorker software is sent to you. Launch the Administration window: a. 4. Click OK. In the Administration window. The new license is added and appears in the right pane. select Properties. Obtain an authorization code Registration of NMM client software takes place by obtaining an authorization code. select a NetWorker Server in the Enterprise list. c. (Optional) In the Comment attribute. Using email To register the software and obtain an authorization code by email: 1. An authorization code that permanently enables the NetWorker license is sent by email.

Licensing and Enabling the Software Type the authorization code To complete the licensing process. From the right pane. The host ID appears in the server’s Registration window. 4. select a license. You need the host ID of the original server as well as the new server. Start the NetWorker Management Console software. From the left pane.” If the authorization is not verified in this way.com. In the left pane. 6. click Enterprise. type the authorization code for the product (the authorization code assigned to the specified permanent enabler or update enabler code). c. The license is now permanently enabled. 7. or to change the network address of a computer after the software is installed. if you move the NMM client software from one computer to another. In the right pane. ◆ Install and configure the License Manager software. From the Enterprise menu. 5. From the File menu. d. select Registration.EMC. select Properties. To avoid an interruption in restores. The Administration window is launched as a separate application. Launch the Administration window: a. 2. select Launch Application.2 SP1 Installation Guide . the expiration date for the license displays “Authorized . From the Console window. 8. select a NetWorker Server in the Enterprise list. perform one of the following: ◆ Obtain a new authorization code. 56 EMC NetWorker Module for Microsoft Applications Release 2.No expiration date. click Configuration. In the Administration window. If the authorization process is successful. 3. In the Auth Code attribute. “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: 1. click the application. contact http://Powerlink. b. you must type the unique authorization code on the NetWorker Server within 45 days of typing the license enabler code. Click OK.

0 or later. as described in “Cluster clients” on page 57 or “Managing EMC licenses” on page 58. you must purchase a Cluster Client Connection. a one-year update agreement might be included. After one year. To use the License Manager. For example. even the NetWorker Server. Licensing and Enabling the Software Update enablers To update existing NMM client software to a major release (one that introduces important new features). NetWorker application modules NetWorker application modules are licensed on the basis of one enabler per database type host. including the current NetWorker release. The EMC NetWorker Release 7. even if the two hosts are backed up by the same server. Cluster clients For each physical node in a cluster. to back up the Exchange database on two hosts. two NetWorker module for Exchange enablers are required. With a first-time purchase of NMM client software. Update enablers are required for any major NetWorker software update. A cluster client or NDMP data server requires a special type of client connection license. an update enabler is necessary. Client connection licenses Every computer to be restored in a NetWorker datazone requires a client connection license. if multiple database instances are running on a NetWorker Client host. the NetWorker Server must be release 5. The client connection license may be one of the licenses supplied with the base enabler or purchased separately. 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. which takes the place of one standard client connection. However. Update enablers 57 .5. only one NetWorker module enabler is required for that one host.x Multiplatform Version Administration Guide provides more information on licensing computers in a cluster.

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

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

Configure a client resource as required for the application. 3. Ensure that NMM Client is installed on the Windows Server hosting the application.exe in Windows Server 2003 or DISKSHADOW. 60 EMC NetWorker Module for Microsoft Applications Release 2. Ensure that you have first reviewed the “Supported configurations” on page 29. Setting up a proxy server for rapid backups of VSS snapshots To be able to take rapid backups of VSS snapshots created by NMM. Configure a proxy client if required. 3. Configure a NetWorker Client scheduled backup as needed for the application: a. c. b. including NetWorker User Group entries. NMM configuration for hardware provider support To configure NMM for hardware provide support: 1.2 SP1 Administration Guide provides more information. Configure a snapshot policy to match application requirements. The storage node acts as the proxy client in a SAN-based storage node configuration. d. you can set up the NMM software or the NMM storage node to act as the proxy client. Configure a backup group. Test if the hardware provider is functioning properly by using VSHADOW. Verify that the VSS Hardware Provider is available for use: a. b. Run and test the NMM scheduled backup. referencing the snapshot policy.Configuring the Software Using NMM with a VSS Hardware Provider NMM can use a VSS Hardware Provider for persistent snapshots or off-host backups. Configure the EMC CLARiiON snapshot or clones. Run vssadmin list providers on the application server. including NetWorker User Group entries. 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. To enable these to work together.exe in Windows Server 2008 to validate creation of hardware snapshots. EMC Symmetrix BCV mirrors or snapshots or EMC Celera snapshots as required. The EMC NetWorker Module for Microsoft Applications Release 2. 2.2 SP1 Installation Guide . 2.

Edit the clarcnfg file so that there is only entry. pointing to the current CLARiiON you want to use. Set the PowerSnap NetWorker security by using NMC (from Configuration > User Groups). “Update the CLARiiON configuration file” on page 62 2.com • For proxy host: user=system. add the username for the account that is logged in to the server: 1.belred. If the clarcnfg file is not current. the first entry may be pointing to a CLARiiON that is no longer connected to the system.com Running a backup with CLARiiON array LUNs For PowerSnap to run a successful backup with CLARiiON array LUNs. Additionally. “Update the SYMCFG authorization list” on page 62 3.host=<fqdn> For example: • For production host: user=system. “Update the Navisphere Privileged Users list” on page 63 If a CLARiiON array is migrated.emc. This step is required only when CLARiiON FLARE 19 is used. Add the following values to the Administrators User Group for the production host and proxy host: user=Administrator. Configurations specific to PowerSnap 61 .host=qe2. If there is more than one entry in the CLARiiON clarcnfg file. Replication Manager only uses the first entry.host=bv-clsrv. rollback may fail.emc.belred. run the following command: naviseccli -h "HOST" -addusersecurity -user "CLARiiON_ARRAY_USER" . or the information in the CLARiiON configuration is not up-to-date. ensure that the following configuration tasks are performed: 1. 2. Configuring the Software Configurations specific to PowerSnap Review the following sections for configuration information specific to PowerSnap.password "CLARiiON_ARRAY_USER_PASSWORD" -Scope 0 Configurations specific to CLARiiON The CLARiiON documentation provides information about how to configure CLARiiON storage arrays. Adding username for account that is logged in the server If you do not have administrative rights and are running programs.

and password for storage processor B. 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.133 Update the SYMCFG authorization list The SYMCFG authorization list must be updated to support the EMC VSS Provider.221.5. and password for storage processor A. To load # information about CLARiiON systems. 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.221.221.132 10. CLARAPI must be able to # communicate with the Navisphere Agent that administers them.Configuring the Software Update the CLARiiON configuration file To support Replication Manager. In the following example.5. username.5.132 -username gadmin -password rdc4xyz 2. Use the following example to update the SYMCFG authorization list for your configuration.133 gadmin 62 EMC NetWorker Module for Microsoft Applications Release 2. # CLARAPI Discovery depends on valid entries in this file.5. Update the SYMCFG authorization list with the hostname IP address. For example: %ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization add -host 10.132 gadmin 10.133 -username gadmin -password rdc4xyz 3.221. For example: %ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization add -host 10. -------------------- 10. Update the SYMCFG authorization list with the hostname IP address. # # CLARiiON Arrayname Storage Processor A Storage Processor B # XXXXXXXXXXXX losat246 losat247 APM00052211461 10. username.2 SP1 Installation Guide . Verify that the SYMCFG authorization list has been updated correctly.5. the two hostname IP addresses identify the two storage processors that exist on each CLARiiON machine: 1. For example: %ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization list Hostname Username ------------------. Use the following sample configuration file template as a guide when adding values to your CLARiiON configuration file.5.221. The clarcnfg file is located in the %ProgramFiles%\EMC\SYMAPI\config\clarcnfg directory.221.

Configurations specific to Symmetrix 63 . it is assumed that two snapshots a day are going to be created. The initialization of Symmetrix for these two technologies is quite different. EMC Navisphere is a software that enables the management of CLARiiON storage systems. ◆ TimeFinder/Snap. Before you begin. Configuring the Software Update the Navisphere Privileged Users list In addition to the information provided in this section. 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. Update the EMC Navisphere Privileged Users list with the DNS hostname or IP address of the CLARiiON storage processors (SPA and SPB). which are being backed up with VDEVs. To create a secure environment: 1. Further. 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. Note: If both BCVs and VDEVs are available for use with an STD. Configurations specific to Symmetrix The following sections describe how to set up Symmetrix for data protection. 2. determine the Symmetrix technology that you will be using for data protection and the number of persistent snapshots that will be required. For the following discussion. The two primary options are: ◆ TimeFinder/Mirror. 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. 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. These configurations are done when setting up CLARiiON and are carried out by the CLARiiON administrator. review The EMC Navisphere Manager Administrator’s Guide for more information about adding entries to the Privileged Users list. it is assumed that Symmetrix volumes 8B and 8C are being backed up by using BCVs and Symmetrix volumes 7D and 7E.

The relationship between a BCV and a STD can be thought of as permanent until the BCV is mirrored to a different STD. Solutions Enabler's SYMCLI is used to do this work. complete the following tasks: 1. The SYMCLI is very flexible and in many cases there is more than one way to accomplish a given task. and so on).Configuring the Software 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. it becomes a point-in-time copy of the STD. A device group is a SYMCLI object created on hosts. use the following command: symdg create <device group name> For example: symdg create mgrp 2. The STDs is assigned a logical name based on the order in which they are entered. use the -help option with any SYMCLI command. and B8 and B9 to volume 8C. the BCV volumes are B6. In the example. B8 and B9.3 Product Guide provides more information about using the -help option. 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. the tracks that were changed on STD are copied to the BCV. 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. When the BCV is disconnected from the STD.2 SP1 Installation Guide . The procedures described in this section reflect the simplest steps whenever possible. also know as split. To create a device group. referred to as a STandard Device (STD). The example establishes B6 and B7 to volume 8B. 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 two are reestablished. To add a STD device to the device group. B7. 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. Add devices to the device group. Once fully synchronized and split the Symmetrix tracks change to either the STD and BCV. Create a device group. While being established. For all other options. The EMC Solutions Enabler Symmetrix CLI Version 6. 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 64 EMC NetWorker Module for Microsoft Applications Release 2. VDEVs. 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. It is a logical grouping of production volumes (STDs) and copy volumes (BCVs. To set up the device group.3 Quick Reference or EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 6.

To check what is in a group. Configuring the Software 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. use the following command: symdg show <group name> For example: symdg show mgrp Figure 4 on page 66 displays the output. Configurations specific to Symmetrix 65 . Verify the group. to add a BCV to the device group. After the STD device is added. 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 symbcv -sid 829 -g mgrp add dev b7 symbcv -sid 829 -g mgrp add dev b8 symbcv -sid 829 -g mgrp add dev b9 3.

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. use the following command: symmir -g <device group name> query -multi For example: symmir -g mgrp query -multi Figure 5 on page 66 displays the output. 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. For the initial establish of the STDs to their partner BCVs.Configuring the Software Figure 4 Output of verify the group command 4. Do not initiate a backup until the BCVs are fully synchronized. Query the mirror state.2 SP1 Installation Guide . Perform the initial device establish. 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> 66 EMC NetWorker Module for Microsoft Applications Release 2. 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 symmir -g mgrp establish DEV001 bcv ld BCV002 -full symmir -g mgrp establish DEV002 bcv ld BCV003 -full symmir -g mgrp establish DEV002 bcv ld BCV004 -full 6. To check the state of the mirrors.

Rerun the mirror query after the backup. When the BCVs are synchronized the EMC VSS Provider then splits them and the actual backup starts. all the BCVs will most likely be seen to be in the split state. 7. it is useful to rerun the mirror query command. These are the copies that were used to make the backup. During subsequent backups. Figure 6 Output of mirror query rerun command Notice that one BCV for each production volume is split from its STD. Once the BCVs are established with an STD. What happens is that when a backup is requested the EMC VSS Provider establishes BCV to each of the production volumes. Configuring the Software For example: symmir -g mgrp split DEV001 bcv ld BCV001 symmir -g mgrp split DEV001 bcv ld BCV002 symmir -g mgrp split DEV002 bcv ld BCV003 symmir -g mgrp split DEV002 bcv ld BCV004 At this point another pair of BCVs can be established to the STDs and synchronized. Figure 6 on page 67 displays the output. the BCVs are rotated by the EMC VSS Provider as needed. Configurations specific to Symmetrix 67 . Once the backup is complete.

when a terminate operation is done to a VDEV. The pairing is done by creating a session between the STD and VDEV.2 SP1 Installation Guide . Note: The VDEV is really a block of logical pointers that are initially set to point to the STD. Symmetrix VDEVs DF -> EE then uses the SDEVs from the default pool for persistent storage. complete the following tasks: 1. The logical pointer on the VDEV for that data region is then updated to point to the old data on the SDEV. commit 2." commit For example: symconfigure -sid 829 -cmd "ADD DEV F7:107 TO POOL DEFAULT_POOL TYPE=SNAP MEMBER_STATE=ENABLE. It is provided for completeness. When a session between a STD and VDEV is created the pool for the SDEVs must be specified. The default pool is named DEFAULT_POOL. In the examples used in the following tasks.Configuring the Software Setting up the TimeFinder/Snap (VDEV) configuration for Symmetrix The TimeFinder/Snap technology is a copy-on-write technology. Create a device group. To add SDEVs to a pool. Preparing for backups with NMM is only necessary to create the initial sessions between a STD and the VDEVs that are used as snapshots. where a virtual device (VDEV) is connected paired to a STD (production volume). the STD volumes being backed up are Symmetrix devices 7D and 7E. 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. To create a device group. To set up the TimeFinder Snap configuration for Symmetrix.". Add SDEVs to a pool. In the example. use the following command: symdg create <group name> For example: symdg create sgrp 68 EMC NetWorker Module for Microsoft Applications Release 2. the STD volumes that are backed up are Symmetrix devices 7D and 7E. its relationship to a particular STD stops and the SDEVs connected with that VDEV are freed. use the following command: symconfigure -sid <Symm Id> -cmd "ADD DEV <sdev device range> TO POOL DEFAULT_POOL TYPE=SNAP MEMBER_STATE=ENABLE. Symmetrix VDEVs DF -> EE use the SDEVs from the default pool for persistent storage. Note: This step might not be necessary depending on how the Symmetrix has been configured. NMM currently is limited by underlying technology to using the default pool. 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. Unlike a BCV. SDEVs are allocated to named pools.

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 symsnap -g sgrp create -svp DEFAULT_POOL DEV001 vdev ld VDEV002 -nop symsnap -g sgrp create -svp DEFAULT_POOL DEV002 vdev ld VDEV003 -nop symsnap -g sgrp create -svp DEFAULT_POOL DEV002 vdev ld VDEV004 -nop Configurations specific to Symmetrix 69 . to add the VDEV devices. Next add the STDs to the device group. Configuring the Software 3. To create initial sessions. Create the initial sessions. Add devices to the device group. To check what is in a group. After the STD volumes are added. The STDs will be assigned a logical name based on the order in which they are entered. use the following command: symdg show <group name> For example: symdg show sgrp 5. 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 symld -sid 829 -g sgrp add dev e1 -vdev symld -sid 829 -g sgrp add dev e2 -vdev 4. Verify the group. 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.

Configuring the Software Figure 7 on page 70 displays the output. Figure 7 Output of initial sessions 6. The state of the snapshots is done with the following command. symsnap -g <group> query -multi For example: symsnap -g sgrp query -multi 70 EMC NetWorker Module for Microsoft Applications Release 2. Query the snap state.2 SP1 Installation Guide .

Figure 9 on page 71 displays the output. Figure 9 Output of running the snapshot query command again Configurations specific to Symmetrix 71 . Configuring the Software Figure 8 on page 71 displays the output. At this point the system is ready to be used for NMM backups. run the following commands: a. Once the backup is complete. Running snapshot againquery after the backup. Figure 8 Output of querying the snap state command 7. Run the snapshot query again.

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. and not just the ones that are yours. The VMware KnowledgeBase article “Enabling root SSH login on an ESX host“provides details about how to enable SSH on VMware host.do?language=en_US&cm d=displayKC&externalId=8375637 ◆ Latest windows service pack updates must be applied on all NMM clients. This article can be found at: http://kb.Configuring the Software b. The second command is a similar view.com/selfservice/microsites/search. ◆ During installation of VMware tools on ESX guest virtual machine.2 SP1 Installation Guide . symsnap -svp <pool> list For example: symsnap -svp DEFAULT_POOL list Figure 10 on page 72 displays the output.vmware. but is done by pool. Note that this command displays all the sessions that are using SDEVs in the pool. 72 EMC NetWorker Module for Microsoft Applications Release 2. select the "complete" installation option.

193. use the SYMCLI symcfg command. Add LUNs to NMM client as RAW device mapping in physical compatibility mode. 3. Note: The NaviAgent and NaviCLI versions must be the same as the CLARiiON storage flare version assigned to ESX host system. Add NaviSECCli security credentials on ESX guest virtual machine.23. to add authorization for a CLARiiON storage processor with IP address 172. Install NaviHost agent on ESX Server Host system. It is necessary to add NaviSECCli security credentials for each of the CLARiiON storage processors.2. and ADAM snap. to add NaviSECCli security credentials for a CLARiiON storage processor with IP address 172. 9. 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. The virtual compatibility mode is not supported by EMC VSS Provider. For example. Note: The NaviHost agent version must be same as the CLARiiON storage flare version assigned to ESX Host system. type: symcfg authorization add -host 172. 5. Use the vicfg commands to authorize access to ESX server from the ESX guest virtual machine.23.193. For example: C:\Program Files\EMC\Navisphere CLI\NaviSECCli. NaviCLI. type: NaviSECCli -user clariion -Scope 0 -address 172. Install NaviAgent. 6.86.86.1. To authorize Solutions Enabler access to the CLARiiON storage array.23. 4.2. Provide the required authorization to the Windows client.193. 2. Configuring the Software ◆ During installation of VSS Provider version 4.exe as the installation path in System Variables Path entry. select the "complete" installation option.86 -username clariion -password clarpass It is important to add the authorization for each of the CLARiiON storage processors. For example. Configurations specific to VMware ESX guest environment 73 . Select complete installation and provide the required license.23.86 -AddUserSecurity Provide password when prompted. username clariion and password clarpass.exe 7. Add NaviSecCli. username clariion and password clarpass. Install VSS Provider version 4. Set VICLIENT_DISABLE_CACHE=1 as system environment variable in ESX guest virtual machine.193. 8.1. ◆ Install PowerPath on the physical machine that is used as the data mover.

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

For example: irccd –p <control_channel_port> -P <data_channel_port> Updating NMM settings with Exchange username. password. Run the utility again if: ◆ The Exchange Server is installed after the NMM is installed. For example: net stop rmagentps 2.domain. ◆ The COM registration associated with that Replication Manager-supplied Exchange 2007 Service for NMM. 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. stop the rmagentps service. double-click the file from the %ProgramFiles%\Legato\nsr\bin directory. This utility updates the NMM software with the Exchange username. password. Changing Replication Manager port settings The Replication Manager port settings are specified during the NMM installation. or domain 75 . Update Exchange Service account information in NMM for Exchange Server 2007 When changes are made to the Exchange Services account in Exchange Server 2007. Update account information in NMM for Exchange Server 2003 When NMM is installed on an Exchange Server 2003. password. To change the Replication Manager port settings: 1.com 5. run the irccd command to change the port settings. or domain changes after the NMM is installed. the utility runs as part of the NMM installation. From the %Program Files%\Legato\nsr\rmagentps\client\bin directory. and domain. the username and account information must be updated in: ◆ The Replication Manager-supplied Exchange 2007 Service for NMM. The steps for updating the Exchange username or account information in NMM are different for Exchange Server 2003 and Exchange Server 2007. or domain If changes are made to the Microsoft Exchange Services account. From the command line. password. changes may be necessary in the NMM settings to continue NMM access to the account. However. you can use the following procedure to change the Replication Manager port settings after NMM is installed. Configuring the Software NSR_DATA_MOVER = proxy. To run the utility. ◆ The username.

Start the rmagentps service. To view the NetWorker SharePoint Service Configuration dialog box after the installation is complete. and change the temporary storage location and the restore lock type for SharePoint granular back even after completing the NMM installation. 76 EMC NetWorker Module for Microsoft Applications Release 2. 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. The NetWorker SharePoint Service Configuration dialog box provides fields to specify the Domain/User Name and Password for SharePoint Service credentials. 4. From the %ProgramFiles%\Legato\nsr\res directory. If you do not fill in the fields to specify the same credentials as those of the SharePoint Server administrator. If proper credentials are not specified then backup of SharePoint data fails.res.exe. 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. Control Port: <control_channel_port> Data Port: <data_channel_port> For example: type: RM Service Ports.2 SP1 Installation Guide . Control Port: 6728. the NetWorker SharePoint Service Configuration dialog box appears. edit rmps. Data Port: 6729. backup of SharePoint data fails with a Windows E_ACCESSDENIED error. For example: net start rmagentps Configuring NetWorker SharePoint services During NMM installation.Configuring the Software 3. The NetWorker SharePoint Service Configuration dialog box appears. For example: type: RM Service Ports. type the following command at the command line: C:\Program Files\Legato\nsr\bin\nwmossinst.

exe –u <site collection URL> If no error messages appear. The temporary storage location is a temporary staging area and is reclaimed after recovery. Click OK to save your changes. Sharepoint service picks the data from this area and updates the Sharepoint databases. your credentials are probably specified correctly.exe –w <web application name> nsr_moss_save. 2. specify the password you use for your Microsoft SharePoint Server administrator account. Configuring NetWorker SharePoint services 77 . This area is used to: ◆ Temporarily store the backup data going to the NetWorker Server during backup. In Password and Confirm Password. Configuring the Software If you have already completed installation and want to test whether your credentials are correct. But if you get error messages or failures with SharePoint backups. 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. you can update the NetWorker SharePoint Service credentials. 3. you can run the following commands at the command line on the SharePoint machine: nsr_moss_save. To update or correct SharePoint credentials by using the NetWorker SharePoint Service Configuration dialog box: 1.exe –w nsr_moss_save. specify the path for the staging area for SharePoint granular backups. In Temporary Storage Location. 2. The Temporary Storage Location must be a valid drive. To specify the staging area for SharePoint granular backups by using the NetWorker SharePoint Service Configuration dialog box: 1. In the Domain\User Name field. ◆ Temporarily store the data coming from the NetWorker Server during restore.exe –f nsr_moss_save. Specify temporary storage location You can browse and select the temporary storage location in the NetWorker SharePoint Service Configuration dialog box. The NetWorker SharePoint Service Configuration saves the staging location to the Windows Registry. specify the domain and username you use for your Microsoft SharePoint Server administrator account. Click OK to save your changes.

click Next. Select Start > Control Panel > Add or Remove Programs. 78 EMC NetWorker Module for Microsoft Applications Release 2. 7. Click Start. select Configure the Windows Firewall.2 SP1 Installation Guide . 2. 4. The option specified here is used as the default setting throughout. 5. and then saving the SCW settings to the configuration file NetWorkerEXT. required running the SCW.” If this occurs. and then click Change. the following error message appears during installation: “Unable to create a Windows Firewall exception for C:\Program Files\Legato\nsr\rmagentps\client\bin\irccd. and then click Control Panel. File not found. configure the firewall setting manually. 3. The options are: ◆ Read unlocked/Write unlocked ◆ Read unlocked/Write locked ◆ Read locked/Write unlocked ◆ Read locked/Write locked After restore. In the Windows Firewall window. Windows firewall exception error for irccd. In the Welcome to NetWorker Module for Microsoft Applications Maintenance dialog box. depending on the option selected.2 SP1 Administration Guide provides details about the Recovery Options tab.exe. the option can be changed from the NMM GUI using the Recovery Options tab just before restore. which is no longer needed. To configure the firewall: 1. and then validate the configuration.xml. Click Next until you finish the configuration wizard. There is no need to run the Security Configuration Wizard to create firewall exceptions for the NMM client.Configuring the Software Specify the restore lock type You can specify the restore lock type in the NetWorker SharePoint Service Configuration dialog box. Select NetWorker Module for Microsoft Applications. The previous version of NMM. Open Windows Firewall. NMM settings can also be modified after installation: 1. Click Start > Control Panel > Add or Remove Programs. Configuring Windows firewall settings NMM automatically configures Windows firewall settings during installation. 2. NetWorker VSS Client. However. the read/write locks are enabled for restored site collections. and then click Change. 8. Click the Exceptions tab. Select NetWorker Module for Microsoft Applications. The EMC NetWorker Module for Microsoft Applications Release 2.exe Occasionally. 6.

b. Type C:\Program Files\Legato\nsr\rmagentps\client\bin\irccd. Configuring the Software 9. select it. • If there is no entry for EMC Replication Manager Client for RMAgentPS. Click OK. c. In the Programs and Services list. d. Configuring Windows firewall settings 79 .exe as needed. specify the correct path to irccd.exe. Click Add Program. verify that EMC Replication Manager Client for RMAgentPS appears and is selected: • If the checkbox is not selected. If NMM was installed on an another drive letter other than C:\. Click Browse. manually add it: a.

and then select Control Panel and Add or Remove Programs.exe. This option is not provided by the installer.exe To manually add the exceptions: 1. click Exceptions.exe EMC NetWorker Client Configuration Server nsrcscd. 5. backups fail. NMM firewall exceptions are not created. Click Add Program.exe EMC NetWorker User winworkr. All programs are located in C:\Program Files\Legato\nsr\bin. Select NetWorker Module for Microsoft Applications. 4. 3. the pathname for: • winworkr. If you are using Windows firewall and installing NMM 2. For example. click Allow a program through Windows Firewall.exe.exe.exe EMC NetWorker NSRSnapBwrAgent process nsrsnapbwragent. • For Windows Server 2003.exe EMC NetWorker PowerSnap SnapCopy Agent nsrbragent. and then click Change.exe EMC NetWorker VSS Client Recover Process nsrsnap_vss_recover.exe EMC NetWorker VSS Client Save Process nsrsnap_vss_save. When the Welcome to NetWorker Module for Microsoft Applications Maintenance dialog box appears.exe is C:\Program Files\Legato\nsr\bin\winworkr. which is located in C:\Program Files\Legato\nsr\rmagentps\client\bin. For both Windows Server 2008 and Windows Server 2003. except for irccd.exe EMC Replication Manager Client for RMAgentPS irccd.Configuring the Software Manually creating NMM firewall exceptions When NMM is installed on a NetWorker storage node. click Next.2 SP1 on an existing storage node.exe is C:\Program Files\Legato\nsr\rmagentps\client\bin\irccd. Table 13 Windows firewall exceptions Display name Program name EMC NetWorker PowerSnap Service nsrpsd. 2.2 SP1 Installation Guide . In the Windows Firewall window: • For Windows Server 2008. create and manually add the firewall exceptions listed in Table 13 on page 80. 6.exe EMC NetWorker PowerSnap Mover Agent nsrsnapagent. 80 EMC NetWorker Module for Microsoft Applications Release 2. type the pathname of the program. When the NetWorker Client is used as a data mover. Select Start. • irccd.

cmd 35 I utility 60 install_nmm_silent_sample. 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.2 SP1 Installation Guide 81 .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 EMC NetWorker Module for Microsoft Applications Release 2.

2 SP1 Installation Guide .Index 82 EMC NetWorker Module for Microsoft Applications Release 2.