Emc Networker Module For Microsoft Applications: Installation Guide

EMC NetWorker Module for Microsoft Applications
Release 2.3
Installation Guide
P/N 300-011-101 REV A03
EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103

1-508-435-1000 www.EMC.com
Copyright 2007 - 2011 EMC Corporation. All rights reserved. Published June, 2011 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. VMware and ESX are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other trademarks used herein are the property of their respective owners.
EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide
Contents
Preface Chapter 1 Preinstallation Information

Installation requirements....................................................................................... License information.......................................................................................... Privileged user-level access............................................................................. Hardware requirements .................................................................................. Config Checker verification ............................................................................ Installation services .......................................................................................... Supported NetWorker versions and hotfixes............................................... Microsoft Windows support ........................................................................... Microsoft hotfixes required for NMM 2.3 ........................................................... Preinstallation checklists........................................................................................ NMM general system checklist ...................................................................... NMM checklists for CLARiiON systems ...................................................... Symmetrix checklist ......................................................................................... Microsoft SQL Server checklist....................................................................... Microsoft SharePoint checklist ....................................................................... Microsoft Exchange Server checklist ............................................................. Supported configurations...................................................................................... Simple LAN-based environment ................................................................... LAN-based environment with a proxy client .............................................. LAN-free environment .................................................................................... LAN-free dedicated storage node environment .......................................... 14 14 14 15 15 15 16 16 18 24 24 27 29 31 31 32 34 34 35 36 37
Chapter 2
Installing the Software

Installing NMM....................................................................................................... Requirements .................................................................................................... Access the installation files ............................................................................. Install the NMM software ............................................................................... Installing NMM in a MSCS environment............................................................ Installing NMM on Windows 2008 server core.................................................. Verifying the installation........................................................................................ Maintaining the installation .................................................................................. Change the password or the authorized server ........................................... 42 42 42 42 44 45 45 45 46
Contents
Upgrading the NMM software.............................................................................. 46 Upgrade from a previous NMM release or NetWorker VSS client ........... 47 Upgrade from the interim solution on Microsoft Exchange Server 2010 . 47 Upgrade from NME or NMSQL ..................................................................... 48 Upgrade to NMM 2.3 with a dedicated storage node ................................. 48 Removing the NMM software............................................................................... 49
Chapter 3
Silent Installation of the Software

Silent installation of NMM..................................................................................... 52 Silent installation of NMM software .............................................................. 52 Silent installation of PowerSnap and Replication Manager ....................... 53 Silent removal of NMM.......................................................................................... 54 Commands for silent removal of NMM ........................................................ 54 Upgrading the software ......................................................................................... 55 Sample scripts for installation and removal of NMM ....................................... 55 The install_nmm_silent_sample.cmd script.................................................. 55 Installing the NMM software by using the default installation path........ 56 Installing and removing NMM by using an SCCM 2007 Server...................... 56 Troubleshooting the installation ........................................................................... 57 Errors in installation of Replication Manager............................................... 58 Using non-English characters in installation path ....................................... 58
Chapter 4
Postinstallation Tasks
Using NMM with a VSS hardware provider....................................................... 60 Configure the hardware array ........................................................................ 60 Configure NMM for hardware provider support........................................ 60 Running a backup with CLARiiON array LUNs ......................................... 61 Configurations specific to CLARiiON ................................................................. 61 Verify that SnapView snapshots and clones are enabled ........................... 61 Update the SYMCFG authorization list......................................................... 62 Configurations specific to Symmetrix.................................................................. 63 Configuring a TimeFinder Mirror .................................................................. 63 Configuring a TimeFinder Snap ..................................................................... 67 Configuring a TimeFinder Clone.................................................................... 72 Configurations specific to a VMware ESX guest environment ........................ 73 Requirements..................................................................................................... 73 Backup with VSS hardware providers for CLARiiON LUNs .................... 73 Backup with VSS hardware providers for Symmetrix LUNs..................... 74 Configure a data mover for an ESX guest virtual machine ........................ 75 Changing Replication Manager port settings ..................................................... 75 Configuring Windows firewall settings............................................................... 76 Windows firewall exception error for irccd.exe ........................................... 76 Configurations specific to Exchange Server........................................................ 77 Update and modify the Exchange Server user identity .............................. 77 Configure Exchange permissions for user accounts .................................... 78 Configure the Exchange Server 2010 Mailbox Server.................................. 78 Configuring a dedicated storage node for NMM............................................... 79 Configuring dedicated web front-end crawling................................................. 79
Figures
Title 1 2 3 4 5 6 7 8 9 10 11
Page 35 36 37 39 65 66 67 69 70 71 71
Simple LAN-based environment ........................................................................................ LAN-based environment with a proxy client ................................................................... LAN-free environment......................................................................................................... LAN-free environment with a dedicated storage node................................................... Output of verify the group command................................................................................ Output of query the mirror state command...................................................................... Output of mirror query rerun command........................................................................... Output of verifying contents in a group............................................................................ Output of querying the snap state command ................................................................... Output of running the snapshot query command again ................................................ Output of second command of running the snapshot query again...............................
Figures
Tables
Title 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Page 14 15 16 16 17 17 18 24 27 28 29 29 31 31 32 53 53 56
Access privileges needed for NMM ................................................................................... Installation services............................................................................................................... NetWorker versions required for NMM client software................................................. NetWorker server hot fixes recommended for NMM ..................................................... Microsoft Windows versions supported by NMM client ............................................... NMM client support for Microsoft Windows features.................................................... Hotfixes required for NMM 2.3 .......................................................................................... NMM general system checklist ........................................................................................... CLARiiON client and proxy checklist................................................................................ NMM 2.3 with Navisphere for CLARiiON ....................................................................... NMM 2.3 with CLARiiON setup ........................................................................................ Symmetrix checklist .............................................................................................................. Microsoft SQL Server checklist ........................................................................................... SharePoint checklist .............................................................................................................. Exchange Server checklist.................................................................................................... Commands for silent installation of NMM ....................................................................... PowerSnap and Replication Manager command line properties .................................. Sample scripts for silent installation ..................................................................................
Tables
Preface
As part of its effort to continuously improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions might not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to the product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC representative. Audience This guide is part of the EMC NetWorker Module for Microsoft Applications documentation set. It is intended for use by system administrators during installation and setup of the product. Readers should be familiar with the following technologies used in backup and recovery:

EMC NetWorker software EMC NetWorker Snapshot management Microsoft Volume Shadow Copy Service (VSS) technology Storage subsystems, such as EMC CLARiiON or Symmetrix, if used
Related documentation
Related documents include:

EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide EMC NetWorker Module for Microsoft Applications Release 2.3 Applications Guide EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes EMC NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups 2.3 Technical Note EMC NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing Proxy Node Backups 2.3 Technical Note EMC NetWorker Cloning Release 7.6 Service 2 Pack 2 Integration Guide EMC Cloning and Recovery of Expired Save Sets for NetWorker Module for Microsoft Applications Technical Note EMC Technical Advisory (ETA) esg121813 EMC NetWorker Procedure Generator (NPG) EMC NetWorker Licensing Guide EMC Information Protection Software Compatibility Guide
9
Preface
EMC NetWorker License Manager Installation and Administration Guide EMC Solutions Enabler Symmetrix CLI Version 6.3 Quick Reference EMC NetWorker Release 7.6 SP1 documentation EMC NetWorker Release 7.6 SP2 documentation
Conventions used in this document
EMC uses the following conventions for special notices.

Note: A note presents information that is important, but not hazard-related.
IMPORTANT An important notice contains information essential to software or hardware operation. 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 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 Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Used for: Specific user input (such as commands) 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
Bold:
Courier:
Courier bold: Courier italic:
<> [] | {} ...
10
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 Powerlink and select Support. On the Support page, you will see several options, including one for making a service request. Note that to open a service request, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to: BSGdocumentation@emc.com If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject that you are addressing.
11
Preface
12
1
Invisible Body Tag
Preinstallation Information
This chapter includes the following sections:

Installation requirements ............................................................................................. Microsoft hotfixes required for NMM 2.3.................................................................. Preinstallation checklists .............................................................................................. Supported configurations ............................................................................................
14 18 24 34
13
Installation requirements
This section describes the version, license, access, and connectivity requirements for installation of EMC NetWorker Module for Microsoft Applications (NMM) 2.3. IMPORTANT After installation, do not use any other Volume Shadow Copy Service (VSS) requester backup solution other than NMM. Data loss may occur if a different VSS solution is used to delete shadow copies created by NMM. Restoring an application with a different VSS solution may prevent the application from being restored with NMM.
License information
The following licenses are required for NetWorker and NMM installations:

NetWorker base enabler. NMM license add-on enabler. The NMM software requires a specific license: NetWorker Module for Microsoft Applications. This license must be installed on the NetWorker server.
NetWorker client enabler. If using a dedicated storage node (DSN), the DSN has its own license enabler. Evaluation, enterprise, and capacity-based enablers support DSN. LAN-free dedicated storage node environment on page 37 provides more details.
Privileged user-level access

NMM requires authorized access to the protected data and system files. Ensure that users who run or configure NMM backups and recoveries have the appropriate level of privileges for all resources that they will access. Table 1 on page 14 describes the required privilege levels.
Table 1
Access privileges needed for NMM (page 1 of 2) Resource NetWorker server Privileges needed Either: NetWorker Administrator NetWorker Backup Operator Either: Windows Administrator Windows Backup Operator Windows Administrator
NetWorker Module for Microsoft Applications client host
All Microsoft applications protected by NMM, such as: Microsoft Windows Server Microsoft Data Protection Manager Microsoft SharePoint Server Microsoft SQL Server Microsoft Exchange Server Microsoft Hyper-V Server
14
Table 1
Access privileges needed for NMM (page 2 of 2) Resource Network domain Storage node servers Privileges needed Windows Domain Administrator Windows Administrator
Hardware requirements
The following minimum hardware is required for installation:

CPU: 2.0 GHz Physical memory: 1 GB Host architecture: x86 and x64 systems only
Config Checker verification

Installation of the NMM 2.2 SP1 or 2.3 software requires that specific software must either be already installed or not installed, and that specific configurations, connections, and conditions are present in the software environment. To verify that your setup is ready for NMM installation, install and run the NMM Config Checker software. Config Checker verifies and captures configuration errors that may lead to failure in the NMM installation, data backup, or data recovery operations for:

NMM application host operating system environment Microsoft SharePoint Microsoft Exchange Microsoft SQL EMC CLARiiON EMC Symmetrix
Note: EMC Solutions Enabler Base component license is required to run checks on Symmetrix systems.
The EMC NetWorker Module for Microsoft Applications Config Checker Supplemental Notes and the EMC Information Protection Software Compatibility Guide provide additional information.
Installation services
Table 2 on page 15 lists the installation services for the NetWorker software, EMC PowerSnap, and Replication Manager services.
Table 2
Installation services Service name (in service control manager) NetWorker PowerSnap Service Replication Manager client for RMAgentPS NetWorker Power Monitor NetWorker Service Service nickname (use with net start) nsrpsd rmagentps nsrpm nsrexecd
Process name nsrpsd.exe irccd.exe nsrpm.exe nsrexecd.exe
15
Supported NetWorker versions and hotfixes

This section describes NetWorker software versions that support the NMM software. Required NetWorker versions Table 3 on page 16 lists NetWorker versions that support the NMM client software.
Table 3
NetWorker versions required for NMM client software NetWorker host NetWorker server Versions required for NMM client support 7.5 SP3 or later 7.6 SP1 or later 7.5 SP3 or later 7.6 SP1 or later 7.5 SP3 or later 7.6 SP1 or later NetWorker server 7.6 SP1 or later NetWorker client 7.6 SP1 or later NetWorker server 7.6 SP2 NetWorker client 7.6 SP2
NetWorker client
NetWorker storage node
NetWorker server and client required for Data Domain backups NetWorker server and client required for Windows Disaster Recovery
Recommended NetWorker cumulative builds Table 4 on page 16 lists in detail the NetWorker versions and specific hotfixes that are recommended for use with NMM software.
Table 4
NetWorker server hot fixes recommended for NMM NetWorker Server and Storage Node Version NetWorker server 7.6.2 NetWorker server 7.6.1 (RTM) NetWorker server 7.6.0 Recommended hot fix or version None Cumulative build NetWorker server 7.6.1.5 or later Either: Cumulative build NetWorker server 7.6.1.5 or later Cumulative build NetWorker server 7.6.0.9 or later Cumulative build NetWorker server 7.5.4.2 or later Either: Cumulative build NetWorker server 7.5.4.2 or later Cumulative build NetWorker server 7.5.3.3 or later
NetWorker server 7.5.4 NetWorker server 7.5.3 and earlier
The Cloning and Recovery of Expired Save Sets for EMC NetWorker Module for Microsoft Applications Technical Note provides more details.
Microsoft Windows support

This section describes the Microsoft Windows operating systems and features that are supported by the NMM 2.3 client software. Microsoft Windows operating system supported Table 5 on page 17 lists Microsoft Windows versions and related features that support NMM client.
16
Note: Windows IA64 editions and Windows Server 2008 R2 Foundation Edition are not supported.
Table 5
Microsoft Windows versions supported by NMM client Supported versions Windows Server 2008 R2 (x64) Includes server core installation options Details Web Edition Standard Edition Enterprise Edition Datacenter Edition
Windows Server 2008 SP2 (x86, x64) Includes server core installation options
Standard Edition Enterprise Edition Datacenter Edition Standard Edition Enterprise Edition Datacenter Edition
Windows Server 2003 (x86, x64) SP2 R2 SP2 R2 Windows Storage Server: 2003 2003 SP2 2003 R2
Microsoft Windows features supported Table 5 on page 17 lists Microsoft Windows features that NMM client does and does not support.
Table 6
NMM client support for Microsoft Windows features Microsoft Windows features supported NMM client supports: System state recovery File servers Operating system roles: - Active directory - Dynamic host configuration protocol (DHCP) - Terminal services) EMC CLARiiON storage: no disk size limit in Windows environments, specifically for: - EMC SnapView clone - EMC SnapView snap - EMC SAN Copy EMC Symmetrix storage: disk size limit is less than 2 TB in Windows environments Microsoft Windows features not supported NMM client does not support: BitLocker encryption LAN-based proxy client or LAN-free backups, if dynamic disks are used Volume Shadow Copy Service (VSS) hardware providers with Windows dynamic disks Software Shadow Copy provider to perform persistent snapshots of clustered disks Windows Automated System Recovery (ASR) Single Instance Storage (SIS)
The EMC Information Protection Software Compatibility Guide contains additional and the most up-to-date information about NMM compatibility.
17
Microsoft hotfixes required for NMM 2.3

In addition to the specific Microsoft Windows updates mentioned in this guide:
Install current Microsoft Windows operating system updates on NMM client hosts. Install current updates and hotfixes for each Microsoft application protected by the NMM software.
Download the updates and hotfixes from the Microsoft website. Table 7 on page 18 lists the hotfixes required for NMM 2.3.
Table 7
Hotfixes required for NMM 2.3 (page 1 of 7) Windows 2003 / Windows 2003 R2 2008 (X64) (X32)
Knowledge Base article ID
Windows 2003 / 2003 R2 (X32)
Windows 2008 (X64)
Windows 2008 R2
Applies to
Description
Volume Shadow Copy Service (VSS) KB975832 VSS You cannot perform certain disk-related operations after a VSS hardware provider fails to create a snapshot on a computer that is running Windows Server 2008. VSS update rollup package for Windows Server 2003 to resolve some VSS snapshot issues. VSS-based backup operations may fail if VSS tracing is enabled on a Windows Server 2003-based computer that has hotfix 940349 applied. When VSS tries to delete hardware support snapshots on a computer that is running Windows Server 2003 or an x64 version of Windows XP, the operation may fail. This hotfix corrects the error displayed by the IOCTL_SCSI_GET_INQUIRY_DATA operation on a Windows Server 2003-based computer: "STATUS_INVALID_DEVICE_REQU EST"
KB940349
VSS
KB951568
VSS
KB949391
VSS
KB943545
VSS
18
Table 7
Knowledge Base article ID KB939315
Windows 2003 / 2003 R2 (X32)
Windows 2008 (X64)
Windows 2008 R2
Applies to VSS
Description Note: Apply this hotfix only if needed. When you shut down a computer that is running the Microsoft Storport storage driver (Storport.sys) on Windows Server 2003 SP2, you may receive a Stop 0x0000009C error message such as: *** STOP: 0x0000009C (parameter1, parameter2, parameter3, parameter4) MACHINE_CHECK_EXCEPTION This error occurs because of a problem in the version of Storport that is included in Windows Server 2003 SP2 and in update 932755. These versions of Storport incorrectly forward interrupts to the miniport after the PCI bus is in the device off state (D3).
Exchange Server KB2425179 Exchange Server 2010 Exchange Server 2007 To perform Recovery Database (RDB) item level recovery, install Exchange Server 2010 SP1 Rollup 2 on all applicable hosts. If encountering VSS_E_WRITERERROR_RETRYABLE errors, take corrective action documented in this knowledge base article. Windows Server 2003 Post-SP1 COM+ 1.5 Hotfix Rollup Package 11 for Exchange Server 2007 CCR environments. Microsoft has released Update Rollup 1 for Exchange Server 2007 Service Pack 2 (SP2). Extended maintenance mode functionality for cluster physical disk resources in Windows Server 2003.This update provides extended functionality when you use the maintenance mode to perform administrative and maintenance tasks in a clustered environment.
KB930800
KB927673
Exchange Server 2007 SP2 Exchange Server 2007 SP2 Windows Server 2003 SP1, when used with Windows Server 2003 x32 or Windows Server 2003, Enterprise x64 Edition.
KB971534
KB903650
19
Table 7
Windows 2003 / 2003 R2 (X32)
Windows 2008 (X64)
Windows 2008 R2
Applies to Windows Server 2003 x32 and x64 edition
Description A hotfix is available that adds support for GUID partition table (GPT) volumes that are larger than 2 TB on a Windows Server 2003-based server cluster.
Storage arrays KB916048 EMC Symmetrix /CLARiiON Hotfix for any host that is running Windows Server 2003/SP1 or Windows Server 2003/R2, and is connected to Symmetrix or CLARiiON storage. Note: This hotfix is part of SP2 and need not be installed separately. Replication Manager SP1 KB891957 RM SP1 Microsoft hotfix WindowsServer2003-KB891957-x86-ENU.e xe for Replication Manager SP1. This update fixes various VSS issues in Windows Server 2003.
Server cluster KB932465 Windows A new physical disk resource does not Server 2003 successfully move to another cluster node x86 SP2 (SP2) on a Windows Server 2003-based server cluster Windows Server 2003 x86 (32-bit architecture) and x64 SP1 (SP1) and Service pack 2 (SP2) A hotfix is available that adds support for GUID partition table (GPT) volumes that are larger than 2 TB on a Windows Server 2003-based server cluster.
KB919117
SQL Server KB956854 SQL Server 2005 SP2 To take a writer-level backup of SQL Server 2005 SP2 that has a SQL Server snapshot, install the cumulative update package 10 for KB956854. To take a writer-level backup of SQL Server 2005 SP 3 that has a SQL Server snapshot, install the SQL Server 2005 Cumulation Update from KB983329. Note: The KB983329 article contains a number of downloads. Ensure to install all.
KB983329
SQL Server 2005 SP 3
20
Table 7
Windows 2003 / 2003 R2 (X32)
Windows 2008 (X64)
Windows 2008 R2
Applies to SQL Server 2005
Description Install SQL Server hotfix KB934396 on the client to successfully backup and restore SQL Server 2005 data. To apply this hotfix, SQL Server 2005 SP2 must be installed. Installation of SQL Server 2005 SP 3 includes this hotfix. Provides information about the bugs that were fixed in SQL Server 2005 SP 3.
KB955706
SQL Server 2005 (64-bit), Version 9.3.4035 SQL Server 2005
KB959195
Cumulative update 1 for SQL Server 2005 SP 3 contains only hotfixes that were released in cumulative update 10 for SQL Server 2005 SP2 and cumulative update 11 for SQL Server 2005 SP2.
SharePoint Server KB2412267 KB971538 SharePoint Server 2007; SharePoint Services 3.0 SP2 Install this knowledge base solution in SharePoint Server 2007 server farm. If you have already installed hotfix 961755, then also install hotfix 971538. If you have not installed hotfix 961755, then install only hotfix 971538. Cumulative update packages for Windows SharePoint Services 3.0 contain hotfixes for the Windows SharePoint Services 3.0 issues that were fixed since the release of Windows SharePoint Services 3.0. This build of the cumulative update package is also known as build 12.0.6510.5001. Go to the Microsoft support website and search for KB971538 - Description of the Windows SharePoint Services 3.0 cumulative update server Hotfix Package (WSS server-package): June 30, 2009 and follow the directions provided on the website. The Microsoft Office 2007 servers SP2 package provides the latest updates. It includes two main categories of fixes: Previously unreleased fixes that were made specifically for this service pack, including improvements in stability, performance, and security. All the public updates, security updates, cumulative updates, and hotfixes that were released through February 2009.
KB953334
SharePoint server 2007
21
Table 7
Windows 2003 / 2003 R2 (X32)
Windows 2008 (X64)
Windows 2008 R2
Applies to Windows SharePoint Services 3.0
Description Windows SharePoint services 3.0 SP2 provides the latest updates, including: Previously unreleased fixes that were made specifically for this service pack, including improvements in stability, performance, and security. All the public updates, security updates, cumulative updates, and hotfixes that were released through February 2009. Before you try to install this service pack, read about how to deploy software updates for Windows SharePoint Services 3.0. Cumulative update packages for Windows SharePoint Services 3.0 (released in April 2010) contain hotfixes. SharePoint 2007 VSS backup and restore fails if the updates are not installed. Cumulative update packages for Microsoft Office SharePoint server 2007 (released in April 2010) contain hotfixes. SharePoint 2007 VSS backup and restore fails if the updates are not installed.
KB981043
Windows SharePoint services
KB981042
Office SharePoint services
Hyper-V Server KB950050 Hyper-V Server Hyper-V Server If this update is not installed before recovery, the system will not run after recovery of SYSTEM COMPONENTS. When a scheduled save is started, the event viewer might display: ASR Error: Failed to collect critical information for ASR Backup. The ASR is unable to obtain disk information for device 3 (Win32 error code 0x2). Apply to each cluster node for cluster deployment. This provides increased functionality and virtual machine control in the Windows Server 2008 Failover Cluster Management console for the Hyper-V Server role. Applies when the Hyper-V Writer seems to be missing due to the presence of corrupt virtual machine configuration files in the Hyper-V Server. Applies when virtual machine files are saved on a volume mounted on a failover cluster using a volume GUID.
KB967560
KB951308
Hyper-V Server SP2
KB956697
Hyper-V Server SP2 Hyper-V Server SP2
KB958184
22
Table 7
Windows 2003 / 2003 R2 (X32)
Windows 2008 (X64)
Windows 2008 R2
Applies to Hyper-V Server SP2
Description Updates Hyper-V Writer to fix backup failure for any of the following reasons: Retry operations elicit VSS error. VSS Application Writer Provider is moving to a bad state. If recovery of a virtual machine is failing because it has legacy network adaptors attached. After performing this update, insert the Integration Services Disk and from the Action menu in each virtual machines management console, update the integration services. Restart the virtual machine. Apply to all Hyper-V hosts. This update for Windows Server 2008 fixes a crash of the Hyper-V host server. A crash can occur when backups are made by using the Hyper-V Writer. Apply when you back up a Windows Server 2003-based virtual machine on a Windows Server 2008 Hyper-V-based computer and get the following message: GetWriterStatus FAILED for Selected writer [Microsoft Hyper-V VSS Writer], writer is in state [9] [VSS_WS_FAILED_AT_FREEZE]
KB960038
Hyper-V Server SP2
KB959978
Hyper-V Server SP2
Data Protection Manager (DPM) KB959605 DPM DPM support in NMM requires the installation of System Center Data Protection Manager 2007 SP1. Otherwise, replicas may not successfully recover. The System Center Data Protection Manager 2007 SP1 download is available from Microsoft website. This update should be installed on the DPM server and DPM client. This VSS update rollup package for Windows Server 2003 resolves some VSS snapshot issues.
KB940349
DPM
General KB948699 Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 The Virtual Disk Service (VDS) crashes when it tries to close on a Windows Server 2003-based computer. To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) installed.
23
Table 7
Windows 2003 / 2003 R2 (X32)
Windows 2008 (X64)
Windows 2008 R2
Applies to Windows Server 2003 SP1, SP2, R2, and R2 SP2
Description Volume GUIDs become invalid in Windows Server 2003 when the disk layout changes outside the context of the Virtual Disk Service and of the APIs. On Windows 2008, during NMM backups, VDS crashes while applying retention because VDS incorrectly accesses some providers that are unloaded, when VDS is in the exit process. Apply this Microsoft hotfix to resolve the issue. On Windows 2003, during NMM backups, Virtual Disk Service (VDS) crashes while applying retention because VDS incorrectly accesses some providers that are unloaded, when VDS is in the exit process. Apply this Microsoft hotfix to resolve the issue.
KB978897
Windows Server 2008 SP2
KB949001
Windows Server 2003 SP2
Preinstallation checklists
Before installing NMM 2.3, use the checklists in this section to verify that your system is correctly configured to back up and restore applications.
NMM general system checklist

Table 8 on page 24 provides the general checklist for NMM 2.3, applicable to all supported platforms.
Table 8
NMM general system checklist (page 1 of 4) Details Supported: Windows 2003 SP2 Windows 2003 R2 SP2 Windows 2008 SP2 Windows 2008 R2 Not supported: Windows 2003 SP1 Windows Vista Windows 7 Windows 2000 Windows XP Review the hotfixes described in Microsoft hotfixes required for NMM 2.3 on page 18. Either uninstall other backup software or prevent it from running. Verify with the backup administrator that no software other than DPM 2007 SP1 is used to back up this host.
Verify The host operating system is supported.
Required hotfixes are installed. No other backup application is installed or used.
24
Table 8
NMM general system checklist (page 2 of 4) Details Remove if installed. Note: NMM could be installed on NetWorker client or storage node 7.5 SP3 or later, or 7.6 SP1 or later.
Verify PowerSnap or Replication Manager are not installed.
The firewall is properly configured if used. IPv6 is not enabled.
If enabled, the firewall is configured with open ports to allow NMM to communicate. If enabled, NMM will not work properly. Disable IPv6 for the NetWorker adapter on which the backup operations are configured. For Exchange item level recovery, the registry must be disabled. The host can connect with NetWorker server, proxy node, or storage node hosts and this NetWorker host is reachable from other hosts. For cluster configurations, verify that the nodes of the virtual server are reachable. The host is properly configured and reachable on the network, with no IP conflicts. For cluster configurations, verify that the nodes of the virtual server are reachable. Ensure: Each NIC is configured with only one IP address. Each IP for any specific NIC resides in a separate subnet or VLAN. Each IP on any host always resolves to one unique hostname. The VSS Admin List volume command lists the volumes that may be used for snapshots. NMM does not support RAW disk sectors. NMM does not support backup of CSVs. The vssadmin list writers command lists the state of all writers on the system EMC VSS Hardware Provider version 4.4.0.1 and Solution Enabler version 7.2.0.1-1108 are installed and running. If there are providers other than Microsoft Provider, they should be used for the volumes they are associated with. The vssadmin list shadowstorage command lists the shadow copy storage available for each volume. Ensure the Maximum Shadow Copy Storage space: value is set to UNBOUNDED for the volume chosen for backup. Active services: rmagentps (Replication Manager Client for RMAgentPS) nsrexecd (NetWorker Remote Exec Service) nsrpsd (NetWorker PowerSnap Service) rm_exchangeinterface (RM Exchange Interface Service) Installation services on page 15 and Verifying the installation on page 45 provides details. Hyper-V Server backups require Windows 2008 OS SP2. Ensure that the latest version is installed on all virtual machines to be used for online backups.
The host can connect with all required NetWorker hosts.
The host is reachable by forward and reverse DNS lookup.
The multihomed (multiple NIC) environment is properly configured if used.
The saveset contains only volumes listed for snapshots. No disks have RAW access. No Cluster Shared Volumes (CSVs) will be backed up. All writers on the system are in stable state. A supported version of VSS hardware provider is running.
The software provider has enough space to create shadow copies of each volume. NMM, Replication Manager, and PowerSnap software are installed and running their services. If the host is also an Exchange Server, then the Replication Manager Exchange interface service is also running.
Hyper-V Server is supported on the operating system. Hyper-V Integration Services version is up-to-date.
25
Table 8
NMM general system checklist (page 3 of 4) Details NetWorker server and storage node 7.6 SP2 and later supports all NMM 2.3 features. Otherwise, NMM 2.3 may be installed on a NetWorker client or storage node with either 7.5 SP3 or later, or 7.6 SP1 or later. Additionally, if used: Data Domain: NetWorker server 7.6 SP1 and later with NMM 2.3 installed on NetWorker client or storage node 7.6 SP1 and later. Windows Disaster Recovery: NetWorker server 7.6 SP2 and later with NMM 2.3 installed on NetWorker client or storage node 7.6 SP2 and later. Verify required licenses. Bitlocker encryption is not supported. In Group properties, set group inactivity timeout to 0. In Group properties, set client retries to 0.
Verify The NetWorker client, server, or storage node versions are supported.
Correct licenses are installed on the NetWorker server. BitLocker encryption is disabled. Group inactivity timeout is set to 0. Client retries is set to 0.
Software and hardware providers are not used simultaneously. Use either a software provider or hardware provider. Using both will cause backups to fail. The NMM 2.3 install path is English only. The application host and proxy host have the same OS, service pack, platform, and similar patch level. The applicable MSDTC or MSCS cluster requirements are met. Only an English path is supported. If the application and proxy hosts do not match, backups will be impaired. MSDTC is not required for Windows 2008 (Exchange Server) and dynamic disks are not supported in an MSCS cluster. Otherwise the following requirements apply: The hardware provider may require MSDTC support as follows: SQL Server 2005 on Windows 2003 Cluster: Yes SQL Server 2005 on Windows 2008 Cluster: No SQL Server 2008 on Windows 2008 Cluster: No SQL Server 2008 R2 on Windows 2008 R2 Cluster: No Windows 2003 (32-bit and 64-bit) may require MSCS cluster hotfixes: SP1 and R2 require Microsoft hotfixes described in Knowledge Base articles KB903650 and KB919117. SP2 and R2 SP2 require Microsoft hotfix described in Knowledge Base article KB919117. Verify the following snapshot requirements: CLARiiON: EMC SnapView Clone EMC SnapView Snapshots EMC Symmetrix DMX: EMC TimeFinder/Mirror EMC TimeFinder/Snap EMC Time Finder/Clone Configurations specific to Symmetrix on page 63 provides details. EMC Celerra: Celerra Snapshots Dell EqualLogic PS Series: EqualLogic Snapshots IBM System Storage DS6000/DS8000: IBM FlashCopy
The appropriate snapshot software for the array is installed and licensed.
26
Table 8
NMM general system checklist (page 4 of 4) Details Verify as appropriate: EMC VSS Common Provider for Symmetrix and CLARiiON arrays The EMC VSS Common Provider and release notes are available on EMC Powerlink. EMC Celerra VSS Provider for Celerra arrays The EMC Celerra VSS Provider is available on Powerlink. Dell/EqualLogic Integration ToolKit for EqualLogic PS Series arrays The Dell documentation provides information on access and support. IBM DS6000 and DS8000 arrays The IBM System Storage DS Open API Package is available from the IBM support website. Windows Unified Data Storage Server (WUDSS) The Microsoft documentation provides information on access and support.
Verify The appropriate VSS hardware provider is installed on the Windows Server that hosts the application.
NMM checklists for CLARiiON systems

Use the appropriate checklists to verify your NMM with CLARiiON installation:

NMM with CLARiiON client and proxy on page 27 NMM with Navisphere for CLARiiON on page 28 NMM with CLARiiON setup on page 29
NMM with CLARiiON client and proxy Table 9 on page 27 provides the checklist for NMM 2.3 with CLARiiON client and proxy base-level software.
Table 9
CLARiiON client and proxy checklist (page 1 of 2) Details Supported versions are: EMC VSS Common Hardware Provider 4.4.0.1 or later Solution Enabler 7.2.0.1-1108 or later Update the SYMCFG authorization list on page 62 provides details. Required versions are: Windows 2003 (and R2) SP2: 5.0.1 or later Windows 2008: 5.1.2 or later (applies only if PowerPath is installed) PowerPath is not be required for: EMC iSCSI on Windows 2008. VMware, which has its own path management capability. VMware ESX server, although NaviAgent is recommended on both the host and guest.
Verify The EMC VSS Hardware Provider and the Solutions Enabler supplied with it are installed.
The target CLARiiON IP addresses are listed in the SYMAPI authorization. EMC PowerPath is installed if required.
The multipathing feature is installed and enabled on Windows Server 2008 if used.
If multipathing is used on this platform, PowerPath is not required, although the following are required: EMC FLARE AULA mode
27
Table 9
CLARiiON client and proxy checklist (page 2 of 2) Details Requirements: iSCSI 2.06, 2.07, or 2.08 Replication Manager supports the Provider Support Matrix and supports iSCSI on CLARiiON with the iSCSI Initiator. PowerPath handles both iSCSI and SAN if iSCSI is specified during the PowerPath installation. The CLARiiON IP address must be listed in the iSCSI Initiator and the host must be visible on CLARiiON Both Emulex and QLogic Fiber Channel cards require EMC certified drivers. The EMC Support Matrix lists the supported driver versions. Microsoft hotfixes required for NMM 2.3 on page 18 provides details. NavihostAgent is installed on ESX server. Logical unit numbers (LUNs) must be configured for raw device mapping from the ESX server to the guest virtual machine. Provide credentials with the following command on the guest virtual machine: C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u username -p password -s esx_network_address [-force]] where username and password are the credentials used for the ESX server.
Verify A supported version of iSCSI Initiator is installed.
HBA Storport driver is installed, if required. Required Windows VSS/VDS hotfixes are installed. The VMware environment is correctly configured if used. The virtual machine environment is correctly configured and authorized if used.
NMM with Navisphere for CLARiiON Table 10 on page 28 provides the checklist for NMM 2.3 with Navisphere software for CLARiiON configurations.
Table 10
NMM 2.3 with Navisphere for CLARiiON Details The locations must be configured in the system environment variable. The location must be configured in the system environment variable: For Windows 2003 with FLARE 19: Admsnap 2.9.0.0.7 or later For Windows 2003 with FLARE 20: Admsnap 2.9.0.0.7 or later For Windows 2003 with FLARE 22: Admsnap 2.9.0.0.7 or later For Windows 2003 with FLARE 24: Admsnap 2.9.0.0.7 or later For Windows 2003 with FLARE 26: Admsnap 2.24.0.0.0 or later For Windows 2003 and 2008 with FLARE 28: Admsnap 2.28.0.0.2 or later For Windows 2003, 2008 and 2008 R2 with FLARE 29: Admsnap 2.29.0.0.0-1 or later For Windows 2003, 2008 and 2008 R2 with FLARE 30: Admsnap 2.29.0.0.0-1 or later The same location (IP address) on the same CLARiiON system must be assigned to the SPA and the SPB processors. CLARiiON arrays with FLARE versions19, 22, 24, 26, 28, 29 and 30 are supported. Ensure it is active. Ensure it is installed.
Verify The NaviCLI and NaviSecCLI software and their locations are properly installed. The supported Admsnap software and its location is properly installed.
The SPA and SPB storage processors on the CLARiiOn system are properly configured. A supported version of the FLARE operating environment is installed on the CLARiiON array. EMC Access Logix is active. SNAPVIEW enabler is installed on CLARiiON
28
NMM with CLARiiON setup Table 11 on page 29 provides the checklist for the NMM 2.3 with CLARiiON setup.
Table 11
NMM 2.3 with CLARiiON setup Details The host NaviCLI version must match or be later than the CLARiiON array version. The number of LUNs in the reserved LUN pool must be sufficient to cover the number of snapshots at any given time. Cloning must be enabled if clone snapshots will be performed. The clones must be private. Ensure the following: The CLARiiON failover or trespassing mode must be set to 1. The connectivity for iSCSI must be set to 4. The specified username and password must work for the CLARiiON array. Run the NaviCLI to display the privileged users. The system@host_id must be listed for all privileged users. A hardware provider license is not required for CLARiiON or Symmetrix. Backups of save sets specified from multiple partitions on the same LUN will fail. Use the following command on the guest virtual machine to provide credentials: C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u username -p password -s esx_network_address [-force]] where username and password are appropriate credentials for the ESX. Remove all snapshot or snap sessions from the storage group. Ensure that both SPA and SPB storage processors are registered. Ensure a LUN is properly configured. Install the appropriate software such as PowerPath or EMC Navisphere.
Verify The host NaviCLI version is compatible with the CLARiiON array version. Logical unit numbers (LUNs) are available in the reserved LUN pool. The array is capable of creating clones. There are private clone LUNs. The failover mode settings for the CLARiiON array are properly set.
The CLARiiON array accepts the user credentials. The CLARiiON privileged user list contains the system@host_id. The Solutions Enabler is licensed. The specified save set uses one partition per LUN. The base ESX server is registered on the guest virtual machine for the proxy and application hosts.
The storage group to be used contains no orphaned snapshot or snap sessions. The NMM host is registered with both SPA and SPB. At least one CLARiiON LUN is visible to the proxy. The host-based EMC storage software appropriate for the CLARiiON host-based utilities has been installed as required by the supporting array and customer environment.
Symmetrix checklist
Table 12 on page 29 provides the checklist for EMC Symmetrix for NMM 2.3.
Table 12
Symmetrix checklist (page 1 of 2) Details Supported versions are: VSS Hardware Provider 4.4.0.1 or later Solution Enabler 7.2.0.1-1108 or later Required versions are: Windows 2003, 2003 R2 or 2003: SP25.0.1 or later Windows 2008: 5.1.2 or later (required only if PowerPath is installed) PowerPath is not required for VMware ESX server.
Verify The VSS Hardware Provider and the Solutions Enabler supplied with it are installed and the Solutions Enabler is licensed.
PowerPath is installed.
29
Table 12
Symmetrix checklist (page 2 of 2) Details Both Emulex and QLogic Fiber Channel cards require EMC certified drivers. The EMC Support Matrix lists the supported driver versions. LUNs must be configured for raw device mapping from the ESX server to the guest virtual machine. Provide credentials with the following command on the guest virtual machine: C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u username -p password -s esx_network_address [-force]] where username and password are the credentials used for the ESX server. Backups of save sets specified from multiple partitions on the same LUN will fail. At least two ports to the host must be zoned. Dual zoning requires PowerPath. Otherwise, backups may fail with a configuration error. This is required for reliable import and export of snapshots. Enable: VCM director flag, which enables the Volume Logix software on Symmetrix so that the VSS Provider can perform device masking. SPC-2 director flag, which forces Symmetrix to report its device identifiers in a way that VSS recognizes. If these flags are not enabled snapshots cannot be processed by the EMC VSS Provider. Required for PowerPath. Run the symcfg discover SYMCLI command to verify. The number of gatekeepers for a single host with few applications running should be eight. However, the minimum is six. Configuring more than one type of snapshot application with STD devices is not recommended. If the snapshot policy deletes a snapshot at the time when the next backup is run, no action is required. If the snapshot policy deletes a snapshot at the time when the next backup is run, no action is required. If the snapshot policy deletes a snapshot at the time when the next backup is run, no action is required.
Verify HBA Storport driver is installed if required. Logical unit numbers (LUNs) for the virtual machine environment are correctly configured and authorized if used.
The save set uses one partition per LUN. The appropriate front-end ports are zoned to the production machine and to the proxy host. For LUNs assigned to a Windows host, both front-end ports must be presented to the Windows system (visible to the SCSI bus on the system). For the proxy mount host, at least one LUN from each Symmetrix host used must be permanently zoned and masked to its host. For Symmetrix storage arrays that use EMC VSS Provider, the required flags are enabled on all of the directors to which the VSS host is connected.
If PowerPath software is installed, run it and verify that all Symmetrix LUNs are displayed in Alive state. Connectivity to Solutions Enabler. Gatekeeper devices are assigned to the production and proxy nodes. Verify that the device groups and associated snapshot devices for TimeFinder Mirror/Snap/Clone are properly configured. If TimeFinder/Mirror is configured, ensure that at least one BCV device is in Not Ready, Synchronized, or SyncInProg state, before running a backup. If TimeFinder/Clone is configured, ensure that at least one clone target device is in Not Ready, Created, or Re-created state, before running a backup. If TimeFinder/Snaps is configured, ensure that at least one VDEV target device to be in Not Ready, Created, Re-created state before taking backup.
30
Microsoft SQL Server checklist

Table 13 on page 31 provides the checklist for Microsoft SQL Server for NMM 2.3.
Table 13
Microsoft SQL Server checklist Details Supported: SQL Server 2005 SP4 SQL Server 2008 SP2 SQL Server 2008 R2 Microsoft SQL Server virtual server is online. Verify: SQL Server Server SQL Server Browser SQL Server Writer Verify whether stable. Single user mode is not supported.
Verify Microsoft SQL Server version and service pack level for each installed instance is supported.
Cluster instances are enabled, if used. Microsoft SQL Server services are running for each instance:
Microsoft SQL Server VSS Writer status is stable. Microsoft SQL Server instance is not running in single user mode.
Microsoft SharePoint checklist

Table 14 on page 31 provides the checklist for Microsoft SharePoint for NMM 2.3.
Table 14
SharePoint checklist (page 1 of 2) Details Supported: SharePoint server 2010 RTM. Microsoft Office SharePoint Server 2007 (for x86 and x64) Standard or Enterprise editions with SP2 or later and Windows SharePoint Services 3.0 with SP2. SharePoint server 2003 (for x86) Standard or Enterprise editions with SP2 and Windows SharePoint Services 2.0 with SP2. Role must be enabled before some of the service can start: SQL Server Writer (running and set to automatic) for SQL Server databases SharePoint Services Writer (running and set to automatic) for SharePoint 2007 and SharePoint 2010 SharePoint Search Writer for SharePoint 2007 or SharePoint 2010 Search Microsoft Office Server Search Writer for Microsoft Office Server search NetWorker client 7.6.3 or 7.6.1 is required. Register with the stsadm -o registerwsswriter command: SharePoint VSS Writer must be registered on at least one web front-end server within a server farm for SharePoint 2007 For SharePoint 2010, SharePoint VSS Writer must be registered on all web front-end servers. Enable. Enable.
Verify Supported SharePoint server versions and updates installed.
All essential SharePoint services are running:
In a server farm, NetWorker client is installed on all hosts for VSS backup. SharePoint VSS Writer is registered.
SQL Server Writer is enabled for SharePoint server 2003, if used. SharePoint 2007 Shared Service Provider (SSP) is properly configured.
31
Table 14
SharePoint checklist (page 2 of 2) Details Provide administrative rights. Ensure these are stable. The Writer must have access to the list of SharePoint components in the configuration database, required for SharePoint VSS backups.
Verify User is SharePoint administrator for SharePoint 2007 or 2010 and has administrative rights on the installation host. SharePoint, OSearch, SPSearch, and SQL Server Writers are in stable state. VSS Writer is running under a SharePoint server farm administrator account.
For SharePoint 2010, if SPSearch is enabled on multiple servers of a SPSearch must be enabled only on a single server in a server farm. server farm, SharePoint services and search writers are not reported. For SharePoint 2010, the SharePoint_Shell_Addess database role membership is enabled in the configuration database. SharePoint self privilege must be enabled in the configured database. If not enabled, the SharePoint Writer reports the GUID instead of the Search application name.
Microsoft Exchange Server checklist

Table 15 on page 32 provides the checklist for Exchange Server for NMM 2.3. Review the following checklist before installing NMM 2.3.
Table 15
Exchange Server checklist (page 1 of 3) Details Supported: Exchange Server 2003 (for x86) Standard and Enterprise editions with SP2 or later. Exchange Server 2007 (for x64) Standard and Enterprise Edition with SP3 with Rollup1 or later. Exchange Server 2010 (for x64) Standard and Enterprise Edition with SP1 Rollup 2 or later. For WSFC or MSCS, the cluster must be healthy. MAPI and CDO version 1.2.1 or later is supported.
Verify A supported Exchange Server is installed:
The Cluster is installed and the cluster service is in the proper state. Supported Message API (MAPI) and Collaboration Data Object (CDO) kits are installed on Exchange Server 2007 and Exchange Server 2010. Credentials of user of Exchange Server are correct. The Exchange Server is a part of the domain. The Exchange Services are running:
The entered credentials must be that of Exchange Server administrator. Otherwise, fail. Required. Essential services are: Exchange Information Store Exchange Attendant Exchange Resource Agent Message Transfer Agent (MTA) Replication Service for cluster environment Locations: System path and the log path are in the same location. In normal backup of Exchange Server, the database files and transaction log files are in different volumes. In a hardware scenario, the database files and log files are in different LUNs. For Exchange Server 2010, the mail box data base and logs must be in different volumes.
Log files are properly located.
32
Table 15
Exchange Server checklist (page 2 of 3) Details Ensure: On an Exchange Server 2007, the writer for both the active node and passive node in the CCR environment is stable. On an Exchange Server 2010, the Database Availability Group (DAG) Exchange IS Writer and Exchange Replication Writer are healthy. The Exchange Server storage groups locale should be the same as the Exchange Server locale. No other writer is permitted for backups. Required for backups. Ensure: On an Exchange Server 2007, the active and passive CCR nodes are consistent. The copy status of Storage Groups is healthy. On an Exchange Server 2010, the databases under the DAG are mounted and healthy. If yes, a backup may be grouped with no more than ten storage groups at a time. Otherwise, the maximum number of storage groups is 32, as determined by the 64 snapshot limit. Storage groups and limits do not apply to Exchange Server 2010.
Verify The Exchange Server writer is stable and healthy.
On Exchange Server 2007, the Exchange Server storage groups use the proper locale. The save set contains only Exchange Writer. The storage group mailbox databases are properly mounted. The Exchange Server Storage Groups and databases are in healthy state.
On Exchange Server 2007, is NSR_EXCHANGE_LIMIT_SG=yes?
Exchange Server management tools are installed on the proxy client. Required. On Exchange Server 2010, Windows Authentication for Powershell should be enabled in the IIS Manager console. On Exchange Server 2010, ensure that the Kernel Mode Authentication is clear. Enable. Go to IIS Manager > Expand Your Host > Expand Sites > Expand Default Web Site >Powershell: 1. In the right pane, double-click Authentication and Enable Windows Authentication. 2. In Windows Authentication, right-click to verify if Kernel Mode Authentication is not selected. Use the fully qualified domain name only. Recovery must be performed from the DAG member server with an active mailbox database status. The restored databases must be in active state. Passive copies of these databases must be in suspended state. If they are not, then you must manually suspend passive copies before a recovery may be performed. Ensure. Ensure. Ensure.
On Exchange Server 2010, ensure that the Client resource was created for a Database Availability Group (DAG) by using it FQDN. For Exchange Server 2010, the database recovery node and state are correct.
For Exchange Server 2010, the user is logged in and has a mailbox for RDB recovery. For Exchange Server 2010, the user can ping the DAG name. For Exchange Server 2010, the database to be restored is in overwritable state.
33
Table 15
Exchange Server checklist (page 3 of 3) Details 1. On the Exchange Server, select Start > All Programs > Exchange Management Shell. 2. Enable Send-As and Receive-As permissions. For example: get-ExchangeServer Exchange_Server_name | Add-AdPermission -user username -extendedrights Receive-As, Send-As 3. In the registry, disable IPV6. Before performing the backup, ensure that a path is provided for NSR_ALT_PATH and the system is rebooted. If a folder path has not been created, then NMM will automatically create a path during the backup. At least one public folder database is provided for RSG or RDB item level browsing.
Verify For Exchange Server 2010, the user for Exchange Server should have send-as and receive-as permissions to browse RSG and RDB mailboxes.
Ensure that NSR_ALT_PATH is properly configured.
On Exchange Server 2007 and Exchange Server 2010, RSG or RDB are enabled.
Supported configurations
This section describes the basic network environments supported by NMM:

Simple LAN-based environment on page 34 LAN-based environment with a proxy client on page 35 LAN-free environment on page 36 LAN-free dedicated storage node environment on page 37
Simple LAN-based environment

In a LAN-based environment, the production data is stored on a storage area network (SAN) or direct-attached storage (DAS). The data path to the NetWorker storage node is over a LAN. The NMM software is installed on the application server host. Figure 1 on page 35 shows a simple LAN-based storage area network with a NetWorker 7.5 SP3 or later, or 7.6 SP1 or later server, plus storage node and clients. The data moves as follows: 1. The NetWorker server initiates the process by contacting the application server where the NMM software is installed. 2. The application server creates a snapshot of the data on the storage volume by using the NMM software. Figure 1 on page 35 shows snapshots, represented by S1 through S5. 3. The application server with the NMM software uses a snapshot in primary storage to transfer the data over the LAN and into a conventional backup medium such as a file type disk, advanced file type disk, tape, Data Domain device, or Avamar deduplication node.
34
NetWorker Server 7.5.3 or 7.6.1
LAN
Application server (NMM 2.3 and NetWorker client 7.5.3 or 7.6.1) NetWorker Storage Node 7.5.3 or 7.6.1 Traditional storage
SAN
Primary storage (CLARiiON or Symmetrix)
S5 S1
S4
S3 S2
GEN-001497
Figure 1
Simple LAN-based environment
LAN-based environment with a proxy client

Figure 2 on page 36 shows a LAN-based environment with a SAN and a proxy client with a NetWorker 7.5 SP3 or later, or 7.6 SP1 or later server plus storage node and clients. Both the application server and the proxy client have the NMM software installed. Install the proxy client software by using the NMM software package.
Note: The application server and the proxy client must use the same version of operating system, NMM software, NetWorker software, and VSS Provider. If NMM 2.3 is installed on either the application server or the proxy client host, then the other host must also use NMM 2.3. Backup and recovery fail if NMM 2.3 is used on one of these hosts, and an earlier version of NMM is used on the other.
A proxy client is a remote host that acts as a data mover (DM) to rollover the snapshot to a conventional backup medium. A proxy client frees resources on the application server. When a backup operation uses a proxy client, it is known as a serverless backup. The data moves as follows: 1. The NetWorker server initiates the process by contacting the application server where the NMM software is installed. 2. The application server creates a snapshot of the data on the storage volume by using the NMM software.
Note: In Figure 2 on page 36, snapshots are represented by S1 through S5.
3. The snapshot is made visible to the proxy client.
35
4. The snapshot is mounted in the proxy client. The data is then moved from the proxy client over the LAN to a backup medium such as a file type disk, advanced file type disk, tape, or Data Domain device.
NetWorker Server
7.5.3 or 7.6.1
LAN
Application server (NMM 2.3 and NetWorker client 7.5.3 or 7.6.1)
Proxy client (NMM 2.3 and NetWorker client 7.5.3 or 7.6.1)
SAN
Primary storage (CLARiiON or Symmetrix)
S4 S5 S1 S3 S2
NetWorker Traditional Storage Node storage 7.5.3 or 7.6.1
GEN-001498
Figure 2
LAN-based environment with a proxy client
LAN-free environment
Figure 3 on page 37 shows a LAN-free environment with a storage area network with NetWorker 7.5 SP3 or later, or 7.6 SP1 or later server, storage node, and clients. The NMM is installed on the application server. The proxy client is installed on the NetWorker storage node. You can set up a NetWorker storage node 7.5 SP3 or later, or 7.6 SP1 or later as a proxy client to avoid the network traffic that is generated when a snapshot is rolled over to a conventional backup medium. Network traffic is avoided because both the conventional backup device and the snapshot are directly attached to the storage node. The data moves as follows: 1. The NetWorker server initiates the process by contacting the application server where the NMM software is installed. 2. The application server creates a snapshot of the data on the storage volume by using the NMM software. In Figure 3 on page 37, snapshots are represented by S1 through S5. 3. The snapshot is made visible to the proxy client. 4. The snapshot is mounted in the proxy client. The data is then moved from the proxy client over the LAN to a backup medium such as a file type disk, advanced file type disk, tape, or Data Domain device.
36
The NetWorker server and the application server communicate through the LAN. However, the data itself is not transferred across the LAN. The conventional backup medium is attached directly to the NMM proxy node, which has NetWorker storage node software and backup media configured. The NMM proxy node acts as a NetWorker storage node.
LAN
Application server (NMM 2.3 and NetWorker client 7.5.3 or 7.6.1)
Proxy client (NMM 2.3 and NetWorker Storage Node 7.5.3 or 7.6.1)
SAN
Primary storage CLARiiON or Symmetrix)
S4 S5 S1 S3 S2
Traditional storage
GEN-001499
Figure 3
LAN-free environment
LAN-free dedicated storage node environment

A dedicated storage node (DSN) is a storage node allows only the data from the local host to be backed up to its devices. An NMM 2.3 host with DSN support enables you to perform the following operations:
LAN-free backups without configuring a separate NMM proxy node, or deploying an NMM proxy server or a proxy node for VSS hardware provider-based backups. Backups to the SAN devices attached directly to NMM client host. Backups to the SAN devices attached to an NMM proxy node.
An NMM 2.3 system with DSN supports backup and recovery of all applications that are normally supported by NMM 2.3, for example: DPM, Active Directory, Hyper-V Server, SharePoint, Exchange Server, SQL Server, and file system backups. Figure 4 on page 39 shows a LAN-free environment with a dedicated storage node. License requirements A valid NetWorker license for the dedicated storage node is required. Other licenses may also be required:

Evaluation license supports DSN. Enterprise license supports DSN. Capacity-based license or NetWorker Source Capacity Data Zone Enabler supports DSN.
37
Business edition does not support Storage Node/DSN. Work group edition does not support Storage Node/DSN.
The EMC NetWorker Licensing Guide provides more information.
Software requirements The following software is required to enable DSN support for NMM:

NetWorker server 7.5 SP3 or later, or 7.6 SP1 or later NetWorker storage node 7.5 SP3 or later, or 7.6 SP1 or later on the application server host NetWorker client software 7.5 SP3 or later, or 7.6 SP1 or later
Configuration requirements DSN support for NMM 2.3 requires the following configurations:

A storage node device that is hosted on the NMM 2.3 client by using NMC. A backup device on the NetWorker server host. This is required for bootstrap data, client file indexes, and for Cover Save set entries. A valid snapshot policy, for example: Number of Snapshot= 2, Retain Snapshot= 1, Backup =Last
A save group resource that uses the selected snapshot policy. The NMM client resource. A storage node device in the client resource that uses media pool selection criteria. The backup device must be configured as a dedicated storage node. In the Device Properties, on the Configuration tab, Dedicated Storage Node must be selected.
Note: If you do not use a DSN device, manually create or configure a default device.
Configuring a dedicated storage node for NMM on page 79 provides details. The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide and the EMC NetWorker Administration Guide provide further details. Data flow in a DSN environment Figure 4 on page 39 illustrates the data movement in a LAN-free environment with a dedicated storage node: 1. The NetWorker server initiates the process by contacting the application server, where the NMM software and the NetWorker Storage Node 7.5 SP3 or later, or 7.6 SP1 or later, is installed. 2. The application server creates a snapshot of the data on the storage volume by using the NMM software. In Figure 4 on page 39, snapshots are represented by S1 through S5. 3. The snapshot is made visible to the NMM host, which resides in the application server. 4. The storage node on the application server uses a snapshot in primary storage to transfer the data over the LAN and into a conventional backup medium such as a file type disk, advanced file type disk, or tape.
38
The NetWorker server and the application server communicate through the LAN. However, the data itself is not transferred across the LAN because the conventional backup medium is attached directly to the NMM host.
LAN
Application server (NMM 2.3 and NetWorker Storage Node 7.5.3 or 7.6.1)
SAN
Traditional storage Primary storage (CLARiiON or Symmetrix) S5 S1 S4 S3 S2

GEN-001500
Figure 4
LAN-free environment with a dedicated storage node
39
40
2

Installing NMM ............................................................................................................. Installing NMM in a MSCS environment .................................................................. Installing NMM on Windows 2008 server core ........................................................ Verifying the installation .............................................................................................. Maintaining the installation......................................................................................... Upgrading the NMM software ................................................................................... Upgrade to NMM 2.3 with a dedicated storage node ............................................. Removing the NMM software.....................................................................................
42 44 45 45 45 46 48 49
41
Installing NMM
This section provides the following information for installing NetWorker Module for Microsoft Applications (NMM) software:

Requirements on page 42 Access the installation files on page 42 Install the NMM software on page 42
Requirements
Ensure that the following requirements met before installing the NMM software:

NetWorker client 7.5 SP3 or later, or 7.6 SP1 or later is installed. For NMM 2.3 dedicated storage node support, NetWorker storage node of 7.5 SP3 or later, or 7.6 SP1 or later is installed. For Windows Disaster Recovery, NetWorker client 7.6 SP2 is installed. The NetWorker server version used for backup operations is the same as the NetWorker client or storage node version installed on NMM 2.3 host. NMM Config Checker has been installed and run on the NMM host, and has verified the configuration requirements for NMM software installation. Config Checker verification on page 15 provides details.
Access the installation files

Access the installation files from a DVD or the EMC website:
From a DVD To access the NMM software from a local DVD: a. Log in as administrator or equivalent on the NetWorker client. b. Insert the NMM DVD into the DVD drive. c. Run setup.exe directly from the DVD.
From the EMC website To access the evaluation version of the NMM software from the EMC Support website: a. Go to http://Powerlink.EMC.com. b. Select Support > Software Downloads and Licensing > Downloads J-O > NetWorker Module. c. In the table of NetWorker Module Software Downloads, click NetWorker Module for Microsoft Applications Release 2.3.
Install the NMM software

Install NMM in the same path where the NetWorker client or NetWorker storage node is installed: 1. Install and run the NMM Config Checker software to verify that the required software and conditions necessary for NMM installation have been met. Config Checker verification on page 15 provides details.
42
2. In the Networkr directory, run the Setup program (setup.exe) to start the installation wizard. The Welcome to NetWorker Module for Microsoft Applications Installation wizard appears. 3. Click Next. The Customer Information dialog box appears. 4. Type the name and organization information and click Next. The License Agreement dialog box appears. 5. Read the license agreement. Select the I accept the terms in the license agreement option, and click Next. 6. Review the Configure the Windows Firewall settings and configure any exceptions that are necessary for your environment. 7. For Control Port and Data Port: Specify two different port number values that will be used by the Replication Manager client service. For most installations, the default values will be satisfactory. IMPORTANT EMC Replication Manager is also sold as a separate product. If you have purchased Replication Manager as a separate product, do not attempt to run the product on the same system as NMM. (Optional) Change the Replication Manager port settings from the command line after the installation is complete. Changing Replication Manager port settings on page 75 provides more information.
Note: Occasionally, an error message indicates that installation was unable to create a Windows firewall exception for irccd.exe. Windows firewall exception error for irccd.exe on page 76 provides steps to manually add the exception.
8. If Exchange Server 2007 or 2010 is installed on the same installation machine, then type the requested Exchange Server domain information in the new dialog box and click OK: Domain Username Password 9. In the Ready to Install dialog box, click Next to start the NMM installation. The installation may take several minutes. 10. If Exchange Server 2003 is installed on the same installation machine, the nwexinfo.exe program runs at the end of the NMM installation. Type the requested Exchange Server domain information in the dialog box and click OK: Domain Username Password
Installing NMM
43
11. In the NetWorker Module for Microsoft Applications Setup Complete window, click Finish to complete the installation and exit the installation wizard. During the NMM installation: Replication Manager and PowerSnap services are installed along with the NMM software. The Replication Manager, PowerSnap services, and the NMM software, appear as separate entries under Add/Remove Programs in Windows Server 2003, or Programs and Features in Windows Server 2008 or 2008 R2. 12. Enable and register the NMM software. 13. Configure the setup according to instructions in Chapter 4, Postinstallation Tasks.
Installing NMM in a MSCS environment

The EMC Solutions Enabler Installation Guide provides details. To install the NMM software in a MSCS environment: 1. Ensure that Microsoft Distributed Transaction Coordinator (NSDTC) software is installed and running, if required. MSDTC is required is you plan to use the NMM software in a Microsoft Cluster Server (NSCS) environment with CLARiiON or Symmetrix hardware and EMC VSS Provider software. VSS Provider installs EMC Solutions Enabler software, which requires MSDTC to be running. The EMC Solutions Enabler Installation Guide provides details. 2. Ensure that NetWorker client 7.5 SP3 or later, or 7.6 SP1 or later, is installed on each physical node of the cluster. 3. Install the NMM software on the private disk of each physical node. Install the NMM software on page 42 provides details. 4. Configure each physical node as a client resource on the NetWorker Server. 5. In the Remote Access attribute of each virtual client resource, type the names of the physical nodes. 6. Configure privileges for each physical node on the NetWorker Server: a. In the Users attribute of the Administrators user group: Add the following values for each physical node in the cluster. Add each value on a separate line:
user=administrator,host=VSS_cluster_node user=system,host=VSS_cluster_node
where VSS_cluster_node is the DNS hostname of the physical node. b. Click OK. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides more information about configuring a clustered client resource. The Microsoft website provides information about deploying Exchange Server 2003 and 2007 in a cluster.
44
Installing NMM on Windows 2008 server core

To install the NMM software on Windows 2008 server core: 1. Install NetWorker client 7.5 SP3 or later software on the server core. 2. Access the NMM binaries as described in Access the installation files on page 42. Use the net use command to access remote machines from the 2008 server core. 3. Copy the NMM binaries to the 2008 server core by using FTP or general access method. 4. Run setup.exe in the networkr directory and press Enter to start the NMM installation.
Note: Do not use autorun.exe to install the NMM software.
There is no GUI when NMM is installed on 2008 server core. However, the NMM installation wizard starts. This installation wizard is the same wizard that is started while installing NMM on other OS.
Verifying the installation

Ensure that the following services are running:

For PowerSnap nsrpsd.exe For Replication Manager irccd.exe
Replication Manager Exchange should be available in manual startup mode.
Maintaining the installation

After installing the NMM software, you may run the Setup program in maintenance mode to change or remove the existing client installation. To run the Setup program in maintenance mode: 1. Log in as administrator on the client server. 2. Perform one of the following: Run the setup.exe file. or Select Start > Settings > Control Panel > Add/Remove Programs. Select the NetWorker Module for Microsoft Applications and click Change. The Welcome to NetWorker Module for Microsoft Applications Maintenance dialog box appears. 3. Click Next. The Setup program detects the existing NMM installation and displays the Maintenance Type dialog box. 4. Select the type of maintenance to perform: Use the Change option to change: The password for Exchange Server by using nwexinfo
Installing NMM on Windows 2008 server core
45
Firewall settings for NMM exceptions The authorized NetWorker Server Change the password or the authorized server on page 46 provides more information. Use the Remove option to remove the NMM software from the system. Removing the NMM software on page 49 provides more information. 5. Click Next.
Change the password or the authorized server

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

This section provides the following information:

Upgrade from a previous NMM release or NetWorker VSS client on page 47 Upgrade from the interim solution on Microsoft Exchange Server 2010 on page 47 Upgrade from NME or NMSQL on page 48 Upgrade to NMM 2.3 with a dedicated storage node on page 48
46
Upgrade from a previous NMM release or NetWorker VSS client

To upgrade to NMM 2.3 from an existing NMM installation or NetWorker VSS client:
Note: Unlike previous versions of NMM and NetWorker VSS client, NMM 2.3 is not bundled with NetWorker client software. The NetWorker client, or NetWorker storage node if you want to configure a dedicated storage node for the client, must be installed separately.
1. Perform a full backup of the NMM or NetWorker VSS client host by using the existing backup program. 2. On the existing NMM or NetWorker VSS client host, run the Setup program in maintenance mode. 3. Select the Remove option. Removing the NMM software on page 49 provides details.
Note: When the existing NMM software is removed, the configuration information that was created during the previous NMM installation is retained and applied to the new installation.
4. Remove all existing snapshots. To delete PowerSnap entries, use the PowerSnap client SnapManager or nsrnapadmin. 5. Ensure that a supported version of NetWorker client or NetWorker storage node software is installed and running on the NMM host. Upgrade to NMM 2.3 with a dedicated storage node on page 48 provides details. 6. Install the NMM 2.3 software. Installing NMM on page 42 provides details.
Upgrade from the interim solution on Microsoft Exchange Server 2010

To upgrade to NMM 2.3 from the NetWorker interim (plug-in) solution for Microsoft Exchange Server 2010: 1. Perform a full backup of the Exchange Server 2010 host by using the interim solution. 2. Ensure that a supported version of NetWorker client or NetWorker storage node software is installed and running on the Exchange Server host. Upgrade to NMM 2.3 with a dedicated storage node on page 48 provides details. 3. Install the NMM 2.3 software on the Exchange Server host. Installing NMM on page 42 provides details. 4. Perform a full back up of the Exchange Server host with the NMM 2.3 software.
Note: The interim solution software remains active on the Exchange Server host in order to enable recovery of the legacy data.
Upgrading the NMM software
47
Upgrade from NME or NMSQL

The NMM2.3 supports all the features of existing versions of NetWorker for Microsoft Exchange (NME) software and some of the basic features of existing NMSQL software. To upgrade to NMM 2.3 from an existing NME or NMSQL installation: 1. Perform a full backup of the NME or NMSQL hosts by using the existing backup program. 2. On each NME or NMSQL client host, run the Setup program in maintenance mode and select the Remove option.
Note: Although the existing NME or NMSQL software is removed in this procedure, the configuration information that was created for these products is retained and will be reapplied if you need to reinstall NME or NMSQL.
3. Remove all existing snapshots. To delete PowerSnap entries, use the PowerSnap client SnapManager or nsrnapadmin. 4. Ensure that a supported version of NetWorker client or NetWorker storage node software is installed and running on the NMM host. Upgrade to NMM 2.3 with a dedicated storage node on page 48 provides details. 5. Install the NMM 2.3 software. Installing NMM on page 42 provides details. 6. On any hosts that might require recovery of legacy NME or NMSQL data, reinstall the NME or NMSQL software.
Upgrade to NMM 2.3 with a dedicated storage node

NMM 2.3 software can support a dedicated storage node deployed on the same host and thus does not need to use a NetWorker storage node that is shared with other hosts and software. This solution is useful for individual high-volume backup clients and can reduce network bandwidth usage. This solution supports the upgrade from NetWorker 7.3 SP3 or later to NetWorker 7.5 SP3 or later.
Note: An additional NetWorker storage node requires a storage node license.
To upgrade to NMM 2.3 with a dedicated storage node: 1. Uninstall the earlier version of NMM software. 2. Install a supported version of NetWorker storage node on the NMM host. The EMC NetWorker Installation Guide provides details. 3. Install the NMM software. Installing NMM on page 42 provides details. The installation will detect the storage node and prompt for permission to dedicate the storage node to the NMM client data.
48
4. Click OK and complete the installation.
Removing the NMM software

To remove the NMM software: 1. Start the Setup program in the maintenance mode. Maintaining the installation on page 45 provides more information. 2. In the Maintenance Type dialog box: a. Select Remove. b. Click Next. 3. Click Remove. NMM software is removed. Removing NMM, also removes the PowerSnap and Replication Manager services. The three entries for these programs are removed from under Add/Remove Programs in the Control Panel.
Note: Although NMM software is removed, you can perform a traditional backup by using NetWorker because the NetWorker client is still available on your machine. The latest copy of the EMC NetWorker Release 7.6 SP1 Installation Guide provides information about uninstalling NetWorker.
Removing the NMM software
49
50
3

Silent installation of NMM........................................................................................... Silent removal of NMM................................................................................................ Upgrading the software ............................................................................................... Sample scripts for installation and removal of NMM ............................................. Installing and removing NMM by using an SCCM 2007 Server............................ Troubleshooting the installation .................................................................................
52 54 55 55 56 57
51
Silent installation of NMM

Silent (unattended) installation is a stand-alone method that may be used for push installation of NMM 2.3 software to one or many hosts. All the information required for a NMM software installation is entered either directly in the command line, or by the use of the commands written as scripts in a .cmd file. To install the NMM software: 1. Install the NetWorker client or storage node software.
Note: NetWorker client 7.5 SP3 or later is required for silent NMM 2.3 installation.
The EMC NetWorker Installation Guide provides details. 2. Run the command or script to install the NMM software.
Note: Silent installation of NMM 2.3 does not install PowerSnap and Replication Manager software, which must be installed separately.
Silent installation of NMM software on page 52 provides details. 3. Run the command or script to install the PowerSnap and Replication Manager services.
Note: Installation of the PowerSnap service also installs the Replication Manager service.
Silent installation of PowerSnap and Replication Manager on page 53 provides details. 4. Verify the installation in the installation status log files, which are available at the location specified in the NMM installation. The default location is the temp directory, which may be access as follows: a. IClick Start > Run. b. Type %temp%.
Silent installation of NMM software

NMM 2.3 installation can be performed by the Windows Installer utility with the following command:
setup /s /v"qn /L*v """%temp%\filename.log"""
Table 16 on page 53 describes the commands. Example An MSI log file, for example NMMinstall11.log, is created in the %temp% directory:
\networker\setup /s /v"/qn /L*v """%temp%\NMMinstall11.log """ "
Ensure that there is space between:

setup and /s /s and /v/qn /v"/qn and /L*v /L*v and %temp%\NMMinstall11.log %temp%\NMMinstall11.log and and
52
Table 16
Commands for silent installation of NMM Option setup /s /v"/qb" Ensure that there is space between: setup and /s /s and /v/qb setup /s /v"/qn" Ensure that there is space between: setup and /s /s and /v/qn setup /s /v"/l*v \"%temp%\mylog.log\" /qb Ensure that there is space between: setup and /s /s and /v/l*v /v/l*v and \"%temp%\mylog.log\" \"%temp%\mylog.log\" and /qb Description Perform a silent installation with progress bar.
Basic installation with no progress bar.
Installs NMM and creates a MSI log file. This command is useful for troubleshooting installation problems. The log file is created in the %temp% directory. Use triple quotes in the command in case the %temp% path contains spaces.
Silent installation of PowerSnap and Replication Manager

The examples in this section provide the commands and format to install the PowerSnap and Replication Manager services, which are installed together. Table 17 on page 53 lists the command line property parameters, all of which are required to install PowerSnap and Replication Manager.
Note: Ensure that all of the property parameters are entered. None are optional.
Examples
The installation must use the appropriate command for the host system:
On nt86 systems:
\networkr\ps\setup.exe /s /v"/qb ALLUSERS=1 VSSREG=0 REBOOT=S RMCPORT=6728 RMDPORT=6729 DORMINST=1 DORMINST_EXCH=0 DORMINST_VSS=1 ADDLOCAL=Proxy,Host,VSS,EMCRecoverPoint"
On ntx64 systems:
\networkr\ps\setup.exe /s /v"/qb ALLUSERS=1 VSSREG=0 REBOOT=S RMCPORT=6728 RMDPORT=6729 DORMINST=1 DORMINST_EXCH=0 DORMINST_VSS=1 ADDLOCAL=Proxy,Host,VSS"
Table 17
PowerSnap and Replication Manager command line properties (page 1 of 2) Property ALLUSERS VSSREG REBOOT ADDLOCAL (x86) Value 1 0 S Proxy, Host, VSS, and EMCRecoverPoint Description Always set value to 1. Always set value to 0. Suppress Reboot. Always set value to S. Features to be installed for x86. All values must be specified.
Silent installation of NMM
53
Table 17
PowerSnap and Replication Manager command line properties (page 2 of 2) Property ADDLOCAL (x64) DORMINST DORMINST_VSS DORMINST_EXCH RMCPORT RMDPORT Value Proxy, Host, and VSS 1 1 {1|0} default = 6728 default = 6729 Description Features to be installed for x64. All values must be specified. Install Replication Manager. Always set value to 1. Always set value to 1. To install Exchange, set value to 1, otherwise set value to 0. Specify Replication Manager control port. Specify Replication Manager data port.
Silent removal of NMM

In a silent removal of NMM 2.3, first the PowerSnap service and Replication Manager services must be removed before NMM is removed. After NMM software is removed, you can still perform a traditional backup by using NetWorker because the NetWorker client exists on your machine. IMPORTANT However, if you want to remove NMM and NetWorker from your machine, uninstall NMM 2.3 before you uninstall NetWorker.
Commands for silent removal of NMM

This section discusses the commands used for silent removal of NMM:
Use the following command to remove PowerSnap and Replication Manager services:
\networkr\ps\setup.exe /s /v"/qn /L*v """%temp%\PSuninstall.log""" " /x
Ensure that there is space between: \networkr\ps\setup.exe and /s /s and /v"/qn /v"/qn and /L*v /L*v and """%temp%\PSuninstall.log""" """%temp%\PSuninstall.log""" and " " and /x
Use the following command to remove NMM, create a MSI log file, and remove the metadata:
\networkr\setup.exe /s /v "/qn /L*v """%temp%\NMMuninstall.log""" " /x
Ensure that there is space between: \networkr\setup.exe and /s /s and /v /v"/qn and /L*v """%temp%\NMMuninstall.log""" \NMMuninstall.log""" and " " and /x
54
Upgrading the software

To upgrade from NMM 2.2 SP1 or earlier to NMM 2.3 by using silent installation and uninstallation: 1. Uninstall the existing version of the NMM software by using silent uninstallation process. Silent removal of NMM on page 54 provides details. 2. Install the appropriate version of NetWorker. 3. Install NMM 2.3 using silent installation process. Silent installation of NMM on page 52 provides details.
Sample scripts for installation and removal of NMM

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

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

The install_nmm_silent_sample.cmd script uses the following command to install NMM, and uses the default installation path and leaves res\server file blank:
%~dp0\setup /s /v"/qn /L*v """%temp%\NMMinstall.log""" " /w
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.log""" and " " and /w
Installing and removing NMM by using an SCCM 2007 Server

To install or remove NMM 2.3 software remotely by using the Microsoft System Center Configuration Manager (SCCM) 2007 Server: 1. Use the New Collection Wizard to specify the client machine, where the NMM 2.3 software is to be installed. 2. Copy the NMM 2.3 installation package to the local drive on SCCM Server and specify a local SCCM machine name as a new distribution point for the distribution package. 3. Use the New Package Wizard to create a software distribution package. Specify general information, data source, distribution settings, and other information for the new package.
56
4. Use the New Program Wizard to create a installation program for a software distribution package:
Note: To simplify the source installation command used by SCCM Server, the install_nmm_silent_sample.cmd and uninstall_nmm_silent_sample.cmd files containing all the necessary scripts to install and remove NMM respectively are created as examples in the installation kit \networkr directory. Sample scripts for installation and removal of NMM on page 55 provides details about the scripts function.
To use the Install_nmm_silent_sample.cmd file as a source installation file in SCCM Server: a. Start the New Program Wizard. b. Click Browse in the General Tab, select Show all files, and then select the install_nmm_silent_sample.cmd file in /networker directory. In Environment Wizard window: a. Ensure that the administrative rights are set to Run Mode. b. Use the default setting for all other options. c. Click Close to complete program creation. 5. Use the New Advertisement Wizard to create an advertisement. Specify general information, package name, program, and the collection to which the advertisement should be distributed: a. For schedule option, select Run as soon as possible. b. For delivery method, use Run program from distribution point. c. For all other options, use default setting to complete New Advertisement Wizard. After the advertisement is created, the SCCM Server is set up to install the software. The Advertisement Status section in SCCM Server can be used to check the installation process status. It may take more than 30 minutes for the SCCM Server to process the advertised installation. The SCCM server installation status log files are available in the client computers C:\Windows\temp directory. For fast access to the temp directory, select Start > Run and then type %SystemRoot%\temp. The steps to remove NMM by using the SCCM Server are the same as that of installing NMM on the SCCM Server. To remove NMM 2.3 by using the SCCM 2007 Server, use the uninstall_nmm_silent_sample.cmd file, instead of using the install_nmm_silent_sample.cmd file.
Troubleshooting the installation

This section provides tips to troubleshoot errors that may appear during installation, when moving from a previous release of NMM or NetWorker VSS client to NMM 2.3, or if NMM is not running correctly after a fresh installation.
Troubleshooting the installation
57
The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides more details on troubleshooting.
Errors in installation of Replication Manager

Most often, installation problems are due to errors in the installation of Replication Manager services: 1. Verify that the NMM, Replication Manager (RMagentPS), and PowerSnap software are installed: For Windows Server 2003, run Add/Remove Programs. For Windows Server 2008, run Programs and Features. 2. If any of these programs are missing, remove all of them in the following order and then reinstall them in the same order: a. Replication Manager service b. PowerSnap service c. NMM software 3. If all three programs appear to be installed but are not running, or do not start but elicit an error message, verify that the NMM, PowerSnap, and Replication Manager services are running: If any of the services are not running, remove and reinstall all of the programs as described in step 2. If irccd.exe is not running, but nsrexecd.exe and nsrpsd.exe are running, then manually install the Replication Manager service from the following directory, networkr\ps\rmc\setup.exe.
Using non-English characters in installation path

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

Using NMM with a VSS hardware provider............................................................. Configurations specific to CLARiiON ....................................................................... Configurations specific to Symmetrix........................................................................ Configurations specific to a VMware ESX guest environment .............................. Changing Replication Manager port settings ........................................................... Configuring Windows firewall settings..................................................................... Configurations specific to Exchange Server.............................................................. Configuring a dedicated storage node for NMM..................................................... Configuring dedicated web front-end crawling.......................................................
60 61 63 73 75 76 77 79 79
59
Using NMM with a VSS hardware provider

NetWorker Module for Microsoft Applications (NMM) can use a VSS hardware provider for persistent snapshots or off-host backups. To enable these to work together, use the following processes to configure the hardware array and NMM:

Configure the hardware array on page 60 Configure NMM for hardware provider support on page 60
Configure the hardware array

To configure the hardware array: 1. Ensure that you have first reviewed the Supported configurations on page 34. 2. Configure the following as required: CLARiiON snapshot or clones Celerra snapshots Symmetrix TimeFinder Snap, mirrors, or clones 3. Run vssadmin list providers on the application server to verify that the VSS hardware provider is available for use. For example:
C:\>vssadmin list providers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Provider name: 'EMC VSS Hardware Provider' Provider type: Hardware Provider Id: {04aaf00b-f272-4449-ae63-e8ac935a102c} Version: 4.2.1.1 Provider name: 'Microsoft Software Shadow Copy provider 1.0' Provider type: System Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5} Version: 1.0.0.7
Configure NMM for hardware provider support

To configure NMM for hardware provider support: 1. Ensure that NMM client is installed on the Windows Server that is hosting the application. 2. Configure an NMM client scheduled backup as needed for the application: a. Configure a snapshot policy to match application requirements. b. Configure a backup group, referencing the snapshot policy. c. Configure a client resource as required for the application, including NetWorker User Group entries. d. Configure a proxy client if required, including NetWorker User Group entries. 3. Run and test the NMM scheduled backup.
60
IMPORTANT When using non EMC VSS hardware provider, backups will fail if the backups are run in proxy configuration. Set the following environment variable in the NMM proxy host for backups to complete successfully: EMC_ERM_NO_SYMAPI=Yes
Running a backup with CLARiiON array LUNs

For PowerSnap to run a successful backup with CLARiiON array LUNs, run the following command for both the CLARiiON Storage Processor A IP address and the Storage Processor B:
naviseccli -h Storage_Processor_A_IP -addusersecurity -user CLARiiON_ARRAY_USER - password CLARiiON_ARRAY_USER_PASSWORD -Scope 0 naviseccli -h Storage_Processor_B_IP -addusersecurity -user CLARiiON_ARRAY_USER - password CLARiiON_ARRAY_USER_PASSWORD -Scope 0
Configurations specific to CLARiiON

The CLARiiON documentation provides information about how to configure CLARiiON storage arrays. Additionally, ensure that the following configuration tasks are performed: 1. Verify that SnapView snapshots and clones are enabled on page 61 2. Update the SYMCFG authorization list on page 62 3. Backup with VSS hardware providers for CLARiiON LUNs on page 73, if required. Running a backup with CLARiiON array LUNs on page 61 provides more information about PowerSnap backup with CLARiiON array LUNs.
Note: Install a licensed version of SnapView software on CLARiiON.
If a CLARiiON array is migrated, or the information in the CLARiiON configuration is not up-to-date, rollback may fail. If there are multiple entries in the CLARiiON clarcnfg file, Replication Manager uses only the first entry. If the clarcnfg file is not current, the first entry may be pointing to a CLARiiON array that is no longer connected to the system. Edit the clarcnfg file so that there is only one entry that points to the CLARiiON array you want to use.
Verify that SnapView snapshots and clones are enabled

Ensure that CLARiiON array has a licensed version of EMC SnapView software installed. SnapView enables you to create a point-in-time view or multiple views of a LUN. These views or snapshots are virtual copies of a LUN on a storage system. They can be made accessible to another host or held as a copy, and can be used for independent data analysis or backup. Snapshots do not copy data at the time of creation. A snapshot is considered to be frozen because it does not change unless you write it. SnapView snapshots use a pointer-and-copy based design. A memory map keeps track of chunks of data. As write requests are made to the active LUN (the source LUN), the chunks are copied to a reserved area, consisting of nonvolatile space on private LUNs (the reserved LUN
Configurations specific to CLARiiON
61
pool). The memory map is updated with the new location of each of these chunks. This is referred to as copy on first writer. It occurs only when the first write request is made to any chunk on the source LUN. Once the original data is safely copied to the reserved LUN, multiple writes can be made to the same chunk without losing the original view of the data. The original view is available by deactivating the changed snapshot. Snap View clones are fully populated point-in-time copies of LUNs (logical units) that allow incremental synchronization between the source and destination LUNs. Because clones are fully protected copies of data, they offer a higher level of availability and can withstand array reboots or failures, as well as failure of source LUN. When combined with SnapView snapshots, clones provide fully populated, point-in-time copies, which maximize users flexibility in using their storage environment. The point-in-time copy allows users to perform additional storage management tasks with minimal impact to the production data. These tasks include:

Backup recovery Application testing Warehousing Data movement
All these tasks can use the point-in-time copy of the data to minimize impact on the production server.
Update the SYMCFG authorization list

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

Before you configure a Symmetrix array, determine the technology you will use for data protection and the number of persistent snapshots you will need. The initialization of Symmetrix is quite different for each of the primary options described in the following sections:
Configuring a TimeFinder Mirror on page 63 Symmetrix Business Continuance Volumes (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.
Configuring a TimeFinder Snap on page 67 Clone technology is used to create a usable stand-alone copy. Configuring a TimeFinder Clone on page 72 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.
In the examples in each of the following sections, it is assumed that Symmetrix volumes 8B and 8C will be backed up by using BCVs and Symmetrix volumes 7D and 7E will be backed up with VDEVs. It is assumed that two snapshots a day will be created.
Note: If both BCVs and VDEVs are available for use with an STD, then the prioritization of the backup being a Copy-On-Write copy (snapshot) or a full copy (BCV) is made by the EMC VSS Provider.
Configuring a TimeFinder Mirror

The TimeFinder/Mirror technology is a full copy technology where a Business Continuance Volume (BCV) is mirrored or established to a production volume, referred to as a Standard Device (STD). While being established, the BCV synchronizes with the STD. After it is fully synchronized, any new writes to the STD are copied to the BCV as well. When the BCV is disconnected (split) from the STD, it becomes a point-in-time copy of the STD. The relationship between a BCV and an STD can be thought of as permanent until the BCV is mirrored to a different STD. Once fully synchronized and split, the Symmetrix tracks change to either the STD and BCV. When the two are reestablished, the tracks that were changed on STD are copied to the BCV. Any tracks that have changed on the BCV is refreshed from the STD so that the BCV is once again a full mirror of the STD. Preparation of TimeFinder/Mirror for use with a proxy consists of the establishing one or more BCVs to the production volume (STD) and waiting for them to become synchronized.
Note: If more than two BCVs are required, then the first BCVs must be split after they have become synchronized in order to allow new BCVs to be synchronized.
Solutions Enabler's SYMCLI is used to do this work. The SYMCLI is very flexible and in many cases there is more than one way to accomplish a given task.
63
Configure the device group and mirrors with BCVs on Symmetrix This section contains instructions for setting up the device group and establishing mirrors with BCVs on Symmetrix. A device group is a SYMCLI object created on hosts. It is a logical grouping of production volumes (STDs) and copy volumes (BCVs, VDEVs, and so on). The -help option with any SYMCLI command provides information on alternative configurations. The EMC Solutions Enabler Symmetrix CLI Quick Reference or EMC Solutions Enabler Symmetrix TimeFinder Family CLI Product Guide provides details. In the following procedure, the BCV volumes are B6, B7, B8 and B9. The example establishes B6 and B7 to volume 8B, and B8 and B9 to volume 8C. To set up the device group: 1. Create a device group. To create a device group, use the following command:
symdg create device_groupname
For example:
symdg create mgrp
2. Add devices to the device group. The STDs are assigned a logical name based on the order in which they are entered. To add an STD device to the device group, use the following command:
symld -sid Symm_ID -g group add dev Symm_STD_device
where Symm_ID is typically based on the last digits of the Symmetrix serial number. For example:
symld -sid 829 -g mgrp add dev 8b symld -sid 829 -g mgrp add dev 8c
After the STD device is added, to add a BCV to the device group, use the following command:
symbcv -g device_groupname -sid Symm_id add dev Symm_BCV_devicename
For example:
symbcv symbcv symbcv symbcv -sid -sid -sid -sid 829 829 829 829 -g -g -g -g mgrp mgrp mgrp mgrp add add add add dev dev dev dev b6 b7 b8 b9
3. Verify the group. To check what is in a group, use the following command:
symdg show group name
For example:
symdg show mgrp
Figure 5 on page 65 displays the output.
64
Figure 5
Output of verify the group command
4. Use the attach command to relate the STD device with respective BCV:
symmir -g groupname attach STD_DEV_ID bcv dev bcv_DEV_ID
Examples:
symmir symmir symmir symmir -g -g -g -g mgrp mgrp mgrp mgrp attach attach attach attach 8b 8b 8c 8c bcv bcv bcv bcv dev dev dev dev b6 b7 b8 b9
5. Establish the initial device. To initially establish the STDs to their partner BCVs, use the following command:
symmir -g device_groupname 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
65
symmir -g mgrp establish DEV002 bcv ld BCV004 -full
6. Query the mirror state. Do not initiate a backup until the BCVs are fully synchronized. To check the state of the mirrors, use the following command:
symmir -g device_groupname query -multi
For example:
symmir -g mgrp query -multi
Figure 6
Output of query the mirror state command
When at least one BCV for each production volume is synchronized, the system is ready to be used for NMM backups. If more BCVs are needed to cover the number of snapshots, then the currently synchronized BCVs must be manually split with the following command:
symmir -g group split logical_device bcv ld logical_device
For example:
symmir symmir symmir symmir -g -g -g -g mgrp mgrp mgrp mgrp split split split split DEV001 DEV001 DEV002 DEV002 bcv bcv bcv bcv ld ld ld ld BCV001 BCV002 BCV003 BCV004
At this point, another pair of BCVs can be established to the STDs and synchronized. After the BCVs are established with an STD, the BCVs are rotated by the EMC VSS Provider as needed. 7. Rerun the mirror query after the backup. After the backup is complete, it is useful to rerun the mirror query command. Figure 7 on page 67 displays the output.
66
Figure 7
Output of mirror query rerun command
Notice that one BCV for each production volume is split from its STD. These are the copies that were used to make the backup. During subsequent backups, all the BCVs will most likely be seen to be in the split state. When a backup is requested, the EMC VSS Provider establishes BCV to each of the production volumes. When the BCVs are synchronized, the EMC VSS Provider then splits them and the actual backup starts. IMPORTANT The number of BCV devices to be associated with STD device depends on the snapshot policy, configured for retaining the snapshot. For example, if you have configured a snapshot policy of 2, 2, All, ensure that the minimum number of BCV devices to be associated with the STD device is not less than 2. After installing the VSS Provider, add or modify the following registry key under HKLM\Software\EMC\ShadowCopy:
DefaultToClone=False
NMM does not verify the registry entry before TimeFinder Mirror backup. TimeFinder Mirror backups will fail if the DefaultToClone value is set to True.
Configuring a TimeFinder Snap

The TimeFinder Snap configuration uses a copy-on-write technology, where a virtual device (VDEV) is paired to an STD (production volume). The pairing is done by creating a session between the STD and VDEV. Once paired with an STD, the VDEV can be activated, at which moment it becomes a copy-on-write snapshot of the STD for that point-in-time.
Note: The VDEV is really a block of logical pointers that are initially set to point to the STD. As new writes are made to the STD, the old data is first copied to a persistent Save Device (SDEV) that backs up the VDEV. The logical pointer on the VDEV for that data region is then updated to point to the old data on the SDEV.
67
SDEVs are allocated to named pools. The default pool is named DEFAULT_POOL. When a session between an STD and VDEV is created, the pool for the SDEVs must be specified. NMM currently is limited by underlying technology to using the default pool. Unlike a BCV, when a terminate operation is done to a VDEV, its relationship to a particular STD stops and the SDEVs connected with that VDEV are freed. In the example, the STD volumes being backed up are Symmetrix devices 7D and 7E. Symmetrix VDEVs DF to E2 use the SDEVs from the default pool for persistent storage. Preparing for backups with NMM is only necessary to create the initial sessions between an STD and the VDEVs that are used as snapshots. In the examples used in the following tasks, the STD volumes that are backed up are Symmetrix devices 7D and 7E. Symmetrix VDEVs DF to E2 then uses the SDEVs from the default pool for persistent storage. To set up the TimeFinder Snap configuration for Symmetrix: 1. If necessary, depending on how the Symmetrix has been configured, add SDEVs to a pool with the following command:
symconfigure -sid Symm_Id> -cmd "ADD DEV sdev_device_range> TO POOL DEFAULT_POOL TYPE=SNAP MEMBER_STATE=ENABLE;" commit
For example:
symconfigure -sid 829 -cmd "ADD DEV F7:107 TO POOL DEFAULT_POOL TYPE=SNAP MEMBER_STATE=ENABLE;", commit
2. Create a device group. To create a device group, use the following command:
symdg create groupname
For example:
symdg create sgrp
3. Add devices to the device group. The STDs will be assigned a logical name based on the order in which they are entered. To add a device to the device group, use the following command:
symld -sid Symm_ID> -g group add dev Symm_device
where Symm_ID is typically based on the last digits of the Symmetrix serial number. For example:
symld -sid 829 -g sgrp add dev 7d symld -sid 829 -g sgrp add dev 7e
After the STD volumes are added, to add the VDEV devices, use the following command:
symld -sid Symm_ID -g group add dev Symm_device -vdev
68
For example:
symld symld symld symld -sid -sid -sid -sid 829 829 829 829 -g -g -g -g sgrp sgrp sgrp sgrp add add add add dev dev dev dev df e0 e1 e2 -vdev -vdev -vdev -vdev
4. Verify the group with the following command:

symdg show groupname
For example:
symdg show sgrp
Figure 8
Output of verifying contents in a group
5. Create the initial sessions. To create initial sessions, use the following command:
symsnap -g group create -svp pool_name STD_logical_name vdev ld VDEV_logical_name -nop
69
For example:
symsnap symsnap symsnap symsnap -g -g -g -g sgrp sgrp sgrp sgrp create create create create -svp -svp -svp -svp DEFAULT_POOL DEFAULT_POOL DEFAULT_POOL DEFAULT_POOL DEV001 DEV001 DEV002 DEV002 vdev vdev vdev vdev ld ld ld ld VDEV001 VDEV002 VDEV003 VDEV004 -nop -nop -nop -nop
6. Query the snap state: The state of the snapshots is done with the following command.
symsnap -g group query -multi
For example:
symsnap -g sgrp query -multi
Figure 9
Output of querying the snap state command
7. Running snapshot query again after the backup. At this point, the system is ready to be used for NMM backups. After the backup is complete, run the following commands: a. Run the snapshot query again. Figure 10 on page 71 displays the output.
70
Figure 10
Output of running the snapshot query command again
b. The second command provides a similar view, but is done by pool. Note that this command displays all the sessions that use SDEVs in the pool, and not just the ones that are yours:
symsnap -svp pool list
For example:
symsnap -svp DEFAULT_POOL list
Figure 11
Output of second command of running the snapshot query again
71
After installing the VSS Provider, add or modify the following registry key under HKLM\Software\EMC\ShadowCopy:
DefaultToClone=False
NMM does not check the registry entry before TimeFinder Mirror backup. TimeFinder Snap backups will fail if the DefaultToClone value is set to True.
Configuring a TimeFinder Clone

TimeFinder/Clone functionality is available with:

NMM 2.3 VSS Provider 4.4.0.1 or later
To set up the TimeFinder Clone functionality, configure clones with production volumes.
Note: Initially, STD and clone devices should be in CREATED state.
The VSS Provider applies the appropriate rotation policy in the subsequent backup, as it does for TimeFinder/Mirror. To create a TimeFinder clone: 1. Use the following command to create TimeFinder clone replications:
symdg create group symclone -g group create -copy -differential source_device sym ld target_device symdg create group symclone -g group create -precopy -differential source_device sym ld target_device
For example:
symdg create CloneGrp symclone -g CloneGrp create -copy -differential SRC sym ld TGT symdg create CloneGrp symclone -g CloneGrp create -precopy -differential SRC sym ld TGT
where SRC and TGT are the device names used as source and target in clone relationship. The target device can be STD or BCV volume, but not the VDEV.
Note: If a device has associated BCVs, a single source device may have 16 clone copies. However, copy sessions created by using the -copy option to create full data copies are limited to eight concurrent sessions.
2. If the target device is not set to not_ready, and the replication session is in copied state (same as split mirror), re-create is not performed and creation of the snapshot fails. 3. After installing the VSS Provider, add or modify the following registry key under HKLM\Software\EMC\ShadowCopy:
RetainCloneSession = TRUE DefaultToClone = TRUE
72
NMM does not check the registry entry before TimeFinder Mirror backup. TimeFinder Clone backups will fail if the RetainCloneSession or DefaultToClone values are set to False.
Configurations specific to a VMware ESX guest environment

The following sections provide information about:

Requirements on page 73 Backup with VSS hardware providers for CLARiiON LUNs on page 73 Backup with VSS hardware providers for Symmetrix LUNs on page 74 Configure a data mover for an ESX guest virtual machine on page 75
Requirements
Review the following requirements before starting the configuration:
SSH must be enabled on the ESX server system. The VMware knowledge base article Enabling root SSH login on an ESX host provides details about how to enable SSH on a VMware host at http://kb.vmware.com. Latest windows service pack updates must be applied on all NMM clients. During installation of VMware tools on ESX guest virtual machine, the complete installation option must be selected. During installation of VSS Provider version 4.4.0.1, the complete installation option must be selected. PowerPath must be installed on the physical machine that is used as the data mover.
Backup with VSS hardware providers for CLARiiON LUNs

To configure an NMM backup with EMC VSS hardware provider for CLARiiON LUNs: 1. Install NaviHost agent on ESX Server Host system.
Note: The NaviHost agent version must be same as the CLARiiON storage version running FLARE assigned to ESX Host system.
2. Add LUNs to NMM client as RAW device mapping in physical compatibility mode. The virtual compatibility mode is not supported by EMC VSS Provider. 3. Set VICLIENT_DISABLE_CACHE=1 as system environment variable in ESX guest virtual machine. 4. Install VSS Provider version 4.4.0.1. Select complete installation and provide the required license. 5. Install NaviAgent, NaviCLI, and ADAM snap. Provide the required authorization to the Windows client.
Note: The NaviAgent and NaviCLI versions must be the same as the CLARiiON storage version running FLARE assigned to ESX host system.
Configurations specific to a VMware ESX guest environment
73
6. Add NaviSecCli.exe as the installation path in System Variables Path entry. For example: C:\Program Files\EMC\Navisphere CLI\NaviSECCli.exe 7. To authorize Solutions Enabler access to the CLARiiON storage array, use the SYMCLI symcfg command. For example, to add authorization for a CLARiiON storage processor with IP address 172.23.193.86, username clariion and password clarpass, type:
symcfg authorization add -host 172.23.193.86 -username clariion -password clarpass
It is important to add the authorization for each of the CLARiiON storage processors. 8. Add NaviSECCli security credentials on ESX guest virtual machine. For example, to add NaviSECCli security credentials for a CLARiiON storage processor with IP address 172.23.193.86, username clariion and password clarpass, type:
NaviSECCli -user clariion -Scope 0 -address 172.23.193.86 -AddUserSecurity
Provide password when prompted. It is necessary to add NaviSECCli security credentials for each of the CLARiiON storage processors. 9. Use the vicfg commands to authorize access to ESX server from the ESX guest virtual machine. For example:
C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u username -p password -s esx_network_address [-force]]
10. Install the NMM client on the ESX guest virtual machine. 11. Restart the ESX guest virtual machine. This is required to save the environment variables settings that are added during the installation.
Backup with VSS hardware providers for Symmetrix LUNs

To configure an NMM backup with EMC VSS hardware provider for Symmetrix LUNs: 1. Add STD, BCV, VDEVs, gatekeeper LUNs to NMM client as RAW device mapping in physical compatibility mode. Virtual compatibility mode is not supported by EMC VSS Provider. 2. Install VSS Provider v4.4.0.1. Select complete installation and provide the required license. 3. By using the Symmetrix configuration tools, create suitable device group and synchronize the STD and BCV LUNs. For backup operations, provide the STD device save set or application save sets, as applicable. 4. Set VICLIENT_DISABLE_CACHE=1 as system environment variable in ESX guest virtual machine. 5. Use vicfg commands to authorize access to the ESX server from the ESX guest virtual machine.
74
For example:
C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u username -p password -s esx_network_address [-force]]
6. Install the NMM client on the ESX guest virtual machine. 7. Restart the ESX guest virtual machine. This is required to save the environment variables settings that are added during the installation.
Configure a data mover for an ESX guest virtual machine

To configure the data mover between the production client (ESX guest virtual machine) and the proxy client (physical Windows host): 1. Ensure that the LUNs for the proxy client are configured from the same array as the production client. 2. Ensure that the hardware providers backup is working for the following clients: Production clients Proxy clients 3. For Symmetrix, ensure that the standard (STD) from the production client is paired with the BCV from the proxy client. 4. In the Application Information window of the production client, type the following:
NSR_DATA_MOVER = proxy.domain.com
5. Perform the following command on both the production client and proxy client:
vicfg setup [-u username -p password -s esx_network_address [-force]]
Changing Replication Manager port settings

The Replication Manager port settings are specified during the NMM installation. However, you can use the following procedure to change the Replication Manager port settings after NMM is installed. To change the Replication Manager port settings: 1. From the command line, stop the rmagentps service. For example:
net stop rmagentps
2. From the %Program Files%\Legato\nsr\rmagentps\client\bin directory, run the irccd command to change the port settings. For example:
irccd p control_channel_port -P data_channel_port
3. From the %ProgramFiles%\Legato\nsr\res directory, edit the following values in rmps.res: control port data port
Changing Replication Manager port settings
75
Note: The values set in step 2 by running the irccd command and the values set in step 3 while editing rmps.res should match. type: RM Service Ports; Control Port: <control_channel_port> Data Port: <data_channel_port>
For example:
type: RM Service Ports; Control Port: 6728; Data Port: 6729;
4. Start the rmagentps service. For example:

net start rmagentps
Configuring Windows firewall settings

NMM 2.3 software automatically configures its Windows firewall settings during installation. There is no need to run the Security Configuration Wizard (SCW) to create firewall exceptions for the NMM client. NMM settings can also be modified after installation: 1. Click Start > Control Panel > Add or Remove Programs. 2. Select NetWorker Module for Microsoft Applications, and then click Change.
Windows firewall exception error for irccd.exe

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

The following sections provides information about configurations related to Exchange Server 2003, 2007, and 2010:

Update and modify the Exchange Server user identity on page 77 Configure Exchange permissions for user accounts on page 78 Configure the Exchange Server 2010 Mailbox Server on page 78
Update and modify the Exchange Server user identity

The user name, password, and domain for Exchange Server 2003, 2007, or 2010 are copied into the NMM software during NMM installation. The user information will be incorrect if either of the following has occurred:

The Exchange Server is installed after NMM is installed. The username, password, or domain is changed after NMM is installed.
To update the NMM software with the correct user information, you must do one of the following:

Reinstall the NMM software. Manually update NMM with user identity by running the nwexinfo.exe utility in the %ProgramFiles%\Legato\nsr\bin directory.
Note: Without the proper user identity, backups fail, even if they do not include Exchange Server data.
If the user identity changes on an Exchange Server 2007 or 2010, then the username and account password must also be updated as follows: 1. Select Start > Administrative Tools > Component Services. 2. Select Computers > My Computer > DCOM Configuration. 3. Right-click Replication Manager Exchange Interface and select Properties from the context menu. 4. Select the Identity tab. 5. Update the domain user account or password, or both, and then click OK.
Configurations specific to Exchange Server
77
Configure Exchange permissions for user accounts

Configure the appropriate Exchange permissions. Exchange Server 2010 To configure Exchange Server 2010 permissions for user accounts:
Stand-alone servers: Domain user account with the Databases role:

New-ManagementRoleAssignment -Role "Databases" -User user_account Note: Alternatively, you may add the user to the Server Manager group instead of adding the roles.
Database Availability Group (DAG) servers: Domain user account with the Database, Database Copies, and Database Availability Group roles:
New-ManagementRoleAssignment -Role "Databases" -User user_account New-ManagementRoleAssignment -Role "Database Copies" -User user_account New-ManagementRoleAssignment -Role "Database Availability Groups" -User user_account Note: Alternatively, you may add the user to the Server Manager group instead of adding the roles.
Mount hosts: Provide a domain user account that is a member of the local administrators group.
Exchange Server 2007 During installation of NMM for Exchange Server 2007, specify a domain account with local administrator rights and Exchange Full Administration privileges. Exchange Server 2003 During installation of NMM for Exchange Server 2003, specify a domain account with local administrator rights and Exchange Full Administration privileges.
Note: The Exchange Server view-only administrator permission provides read-only access to the Exchange organization. You can see the contents and settings of an Exchange organization, but not modify them.
Configure the Exchange Server 2010 Mailbox Server

For Exchange Server 2010 Mailbox Server backups, Windows Authentication must be selected and the Kernel Mode Authentication unselected. This applies whether the Mailbox Server is stand alone or part of the Database Availability Group (DAG). To enable Windows Authentication: 1. Select IIS Manager > Your Host > Sites > Default Web Site > Powershell. 2. Double-click Authentication and enable Windows Authentication. 3. On the Windows Authentication window, right-click and ensure that the Kernel Mode Authentication option is clear.
78
Configuring a dedicated storage node for NMM

Separate licenses are required for the following storage node environments:
A standard storage node license allows the storage node to be shared among all connected NetWorker clients in a datazone. A dedicated storage node license allows backup and restore operations on only a single host, in this case the NMM host on which the storage node is installed.
Note: Microsoft Exchange Server 2010 does not support dedicated storage nodes.
To configure a dedicated storage node for NMM: 1. Install a NetWorker 7.5 SP3 or later, or 7.6 SP1 or later, storage node.
Note: This step is required before installing the NMM 2.3 software.
The EMC NetWorker Installation Guide that is appropriate for the NetWorker version installed provides details. 2. For a dedicated storage node, install the NMM 2.3 software on the same host. Installing NMM on page 42 provides details. 3. Create a remote backup device on the NetWorker server and on the Device Properties, Configuration tab, set the Dedicated Storage Node attribute to Yes. The EMC NetWorker Administration Guide that is appropriate for the NetWorker version installed provides details.
Configuring dedicated web front-end crawling

NMM 2.3 supports dedicated web front-end crawling. To configure a dedicated web front-end by using the SharePoint Central Administration: 1. First, back up the existing host file. 2. By using SharePoint Central Administration, configure dedicated web front-end crawling. When the configuration is complete, a new host file is created by SharePoint Central Administration. 3. Append the host file information from backed-up host file to the new host file. 4. Configure NMM backup.
Configuring a dedicated storage node for NMM
79
80

Emc Networker Module For Microsoft Applications: Installation Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Emc Networker Module For Microsoft Applications: Installation Guide

Uploaded by

Copyright:

Available Formats

EMC NetWorker Module for Microsoft Applications

EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103

Preface Chapter 1 Preinstallation Information

Installing the Software

Silent Installation of the Software

Related documents include:

Conventions used in this document

EMC uses the following conventions for special notices.

Courier bold: Courier italic:

Where to get help

This chapter includes the following sections:

Privileged user-level access

NetWorker Module for Microsoft Applications client host

Config Checker verification

Process name nsrpsd.exe irccd.exe nsrpm.exe nsrexecd.exe

Supported NetWorker versions and hotfixes

NetWorker storage node

NetWorker server 7.5.4 NetWorker server 7.5.3 and earlier

Microsoft Windows support

Microsoft hotfixes required for NMM 2.3

Knowledge Base article ID

Windows 2003 / 2003 R2 (X32)

Windows 2008 (X64)

Knowledge Base article ID KB939315

Windows 2003 / 2003 R2 (X32)

Windows 2008 (X64)

Microsoft hotfixes required for NMM 2.3

Knowledge Base article ID KB919117

Windows 2003 / 2003 R2 (X32)

Windows 2008 (X64)

Applies to Windows Server 2003 x32 and x64 edition

SQL Server 2005 SP 3

Knowledge Base article ID KB934396

Windows 2003 / 2003 R2 (X32)

Windows 2008 (X64)

Applies to SQL Server 2005

SQL Server 2005 (64-bit), Version 9.3.4035 SQL Server 2005

SharePoint server 2007

Microsoft hotfixes required for NMM 2.3

Knowledge Base article ID KB953338

Windows 2003 / 2003 R2 (X32)

Windows 2008 (X64)

Applies to Windows SharePoint Services 3.0

Windows SharePoint services

Office SharePoint services

Hyper-V Server SP2

Hyper-V Server SP2 Hyper-V Server SP2

Knowledge Base article ID KB959962

Windows 2003 / 2003 R2 (X32)

Windows 2008 (X64)

Applies to Hyper-V Server SP2

Hyper-V Server SP2

Hyper-V Server SP2

Microsoft hotfixes required for NMM 2.3

Knowledge Base article ID KB936008

Windows 2003 / 2003 R2 (X32)

Windows 2008 (X64)

Applies to Windows Server 2003 SP1, SP2, R2, and R2 SP2

Windows Server 2008 SP2

Windows Server 2003 SP2

NMM general system checklist

Verify The host operating system is supported.