EMC NetWorker Module for Microsoft Applications

Transcription

1 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide P/N REV A02 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright EMC Corporation. All rights reserved. Published May, 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. All other trademarks used herein are the property of their respective owners. 2 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

3 Contents Preface Chapter 1 Chapter 2 Preinstallation Information Preinstallation requirements License information Privileged user-level access Hardware requirements Software requirements Installation services Supported NetWorker server hosts Windows operating system support Microsoft hotfixes required for NMM Preinstallation checklists Generic checklist CLARiiON checklist Symmetrix checklist SQL checklist Microsoft SharePoint checklist Microsoft Exchange checklist Supported configurations Simple LAN-based configuration LAN-based configuration with a proxy client LAN-free configuration LAN-free dedicated storage node configuration Installing the Software Installing NMM Prerequisites Access the installation files Install the software Installing NMM in a MSCS environment Installing NMM on Windows 2008 server core Verifying the installation Maintaining the installation Change the password or changing to a different authorized server EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide 3

4 Contents Removing the software Upgrading the software Moving from an existing NetWorker VSS client or NMM setup to the NMM 2.3 release Moving from NetWorker support for Microsoft Exchange 2010 interim solution to the NMM 2.3 release Upgrading to NMM 2.3 storage node Installing Microsoft Office SharePoint Server service pack Chapter 3 Chapter 4 Silent Installation of the Software Overview Silent installation of NMM Commands for silent installation of NMM PowerSnap and Replication Manager command line properties Sample command for silent installation of NMM Silent removal of NMM Commands for silent removal of NMM Upgrading the software Sample scripts for installation and removal of NMM The install_nmm_silent_sample.cmd script Installing the NMM software using the default installation path Installing and removing NMM by using SCCM 2007 Server Troubleshooting the installation Errors in installation of Replication Manager Using non-english characters in installation path Postinstallation Tasks Using NMM with a VSS hardware provider Hardware array configuration NMM configuration for hardware provider support Configurations specific to PowerSnap Adding username for account that is logged in the server Running a backup with CLARiiON array LUNs Configurations specific to CLARiiON CLARiiON SnapView snapshots and clones Updating the CLARiiON configuration file Updating the SYMCFG authorization list Updating the Navisphere Privileged Users list Configuring NMM backup settings in a virtual machine Configurations specific to Symmetrix Setting up the TimeFinder/Mirror (BCV) configuration for Symmetrix. 72 Setting up the TimeFinder/Snap (VDEV) configuration for Symmetrix. 77 Setting up the TimeFinder/Clone configuration for Symmetrix Configurations specific to VMware ESX guest environment Prerequisites Configuring NMM backups with EMC VSS hardware providers for CLARiiON LUNs Configuring NMM backups with EMC VSS hardware providers backups for Symmetrix LUNs Configuring data mover between the ESX guest virtual machine and a physical windows host EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

5 Contents Changing Replication Manager port settings Configuring NetWorker SharePoint services Matching NetWorker SharePoint Service credentials with credentials of SharePoint Server administrator Specifying temporary storage location Specifying the restore lock type Updating SharePoint credentials Configuring Windows firewall settings Windows firewall exception error for irccd.exe Configurations specific to Exchange server Updating and modifying Exchange credentials Setting up Exchange permissions for user accounts Configuring IIS settings on Exchange 2010 Mailbox Server before performing backup Configuring a storage node as a dedicated storage node Configuring dedicated web front-end crawling Index EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide 5

6 Contents 6 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

7 Figures Title Page 1 Simple LAN-based configuration LAN-based configuration with a proxy client LAN-free configuration LAN-free configuration 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 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide 7

8 Figures 8 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

9 Tables Title Page 1 Access privileges needed for NMM Installation services Hotfixes required for NMM Checklist overview Generic checklist CLARiiON checklist Symmetrix checklist SQL checklist SharePoint checklist Exchange checklist Commands for silent installation of NMM PowerSnap and Replication Manager command line properties Sample scripts for silent installation EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide 9

10 Tables 10 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

11 Preface As part of its effort to continuously improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to the product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC representative. Audience Related documentation 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 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 NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups 2.3 Technical Note NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing Proxy Node Backups 2.3 Technical Note EMC NetWorker Licensing Guide EMC Information Protection Software Compatibility Guide 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 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide 11

12 Preface 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.! CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment. Typographical conventions EMC uses the following type style conventions in this document: Normal Used in running (nonprocedural) text for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, filenames, functions, utilities URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, notifications Bold: Used in running (nonprocedural) text for: Names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system call, man pages Used in procedures for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) What user specifically selects, clicks, presses, or types Italic: Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis (for example a new term) Variables Courier: Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Courier bold: Used for: Specific user input (such as commands) Courier italic: Used in procedures for: Variables on command line User input variables < > Angle brackets enclose parameter or variable values supplied by the user [ ] Square brackets enclose optional values Vertical bar indicates alternate selections - the bar means or { } Braces indicate content that you must specify (that is, x or y or z)... Ellipses indicate nonessential information omitted from the example 12 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

13 Preface Where to get help Your comments 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: 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 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: [email protected] 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide 13

14 Preface 14 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

15 Invisible Body Tag 1 Preinstallation Information This chapter includes the following sections: Preinstallation requirements Microsoft hotfixes required for NMM Preinstallation checklists Supported configurations Preinstallation Information 15

16 Preinstallation Information Preinstallation requirements This section describes the preinstallation requirements for EMC NetWorker Module for Microsoft Applications (NMM) 2.3. Ensure to review and adhere to the checks and requirements described in this section thoroughly before attempting a NMM installation. Failure to adhere to these checks and requirements will result in failure to successfully protect the application data and will require significant effort to troubleshoot and resolve. This section provides the following information: License information on page 16 Privileged user-level access on page 16 Hardware requirements on page 17 Software requirements on page 17 Installation services on page 17 Supported NetWorker server hosts on page 18 Windows operating system support on page 18 IMPORTANT Do not use any other VSS requester when NMM is installed. Data loss may occur if other VSS requestor backup solutions delete shadowcopies created by NMM. Additionally, restoring an application by using another vendor s VSS requestor backup solution may prevent the same 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 The EMC NetWorker Licensing Guide provides more information about licensing. Privileged user-level access NMM requires access to the protected data and system files. Hence, ensure that users who run or configure NMM backups and recoveries have the appropriate level of privileges for all resources that they will access. 16 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

17 Preinstallation Information Table 1 on page 17 describes the required privilege levels. Table 1 Access privileges needed for NMM Resource Privileges needed NetWorker server NetWorker Administrator or NetWorker Backup Operator NetWorker Module for Microsoft Applications client machine Windows Administrator or Windows Backup Operator All Microsoft applications protected by NMM, such as: Windows server Data Protection Manager SharePoint server SQL server Exchange server Hyper-V server Network domain Storage node servers Windows Administrator Windows Domain Administrator Windows Administrator Hardware requirements You require the following hardware before installation: CPU: 2.0 GHz Physical memory: 1 GB Host architecture: x86 and x64 systems only Software requirements Preinstallation checklists on page 26 and the EMC Information Protection Software Compatibility Guide provide information on the software requirements for NMM 2.3. Installation services Table 2 Table 2 on page 17 lists the installation services for the NetWorker software, and EMC PowerSnap TM and Replication Manager services. Installation services Service names (in service control manager) Service nicknames (use with the net start command) Process names NetWorker PowerSnap Service nsrpsd nsrpsd.exe Replication Manager client for RMAgentPS rmagentps irccd.exe NetWorker Power Monitor nsrpm nsrpm.exe Preinstallation requirements 17

18 Preinstallation Information Supported NetWorker server hosts The NMM client is supported with: NetWorker server: 7.5 SP3 or later 7.6 SP1 or later NMM client: 7.5 SP3 or later 7.6 SP1 or later NetWorker storage node: 7.5 SP3 or later 7.6 SP1 or later The NetWorker server and NetWorker client that are required for Data Domain: NetWorker server 7.6 SP1 or higher NetWorker client 7.6 SP1 or higher The NetWorker server and NetWorker client that are required for Windows Disaster Recovery: NetWorker server 7.6 SP2 NetWorker client 7.6 SP2 The EMC Information Protection Software Compatibility Guide provides the latest information. Windows operating system support NMM client supports the following versions of Windows and Windows-related features: Windows server 2008 R2 (x64), Web, Standard, Enterprise, and DataCenter Editions, including server core installation options Windows server 2008 SP2 (x86, x64), 2008 SP1 (x86, x64) Standard, Enterprise, DataCenter Editions, including server core installation options Windows server 2003 SP2 R2 (x86, x64), 2003 SP2 (x86, x64), 2003 R2 (x86, x64), 2003 (x86, x64) Standard, Enterprise, DataCenter Editions Windows storage server 2003, 2003 SP2, and 2003 R2 System state recovery, file servers, and operating system roles including Active Directory, DHCP, and Terminal Services GUID Partition Table disks: No disk size limit on Windows environments with EMC CLARiiON storage (EMC SnapView clone, EMC SnapView snap, and EMC SAN Copy technologies only) Disk size limit of less than 2 TB on Windows environments with EMC Symmetrix storage Note: Windows IA64 editions and Windows server 2008 R2 Foundation edition are not supported. 18 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

19 Preinstallation Information In addition, the following Windows features are not supported: BitLocker encryption LAN-based proxy client or LAN-free backups, if dynamic disks are used 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. Microsoft hotfixes required for NMM 2.3 In addition to the specific Microsoft Windows updates mentioned in this guide: 1. Keep NMM client machine current with Microsoft Windows updates for the operating system. 2. Keep NMM client machine current with updates and hotfixes for each installed Microsoft application protected by NMM. 3. Download the hotfixes from the Microsoft website. Table 3 on page 19 lists the hotfixes required for NMM 2.3. Table 3 Hotfixes required for NMM 2.3 (page 1 of 8) KnowledgeBase article ID Windows 2003 (X32) Windows 2003 (X64) Windows 2008 (X32) Windows 2008 (X64) Windows 2008 R2 Applies to Description Volume shadowcopy service (VSS) KB 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 KB VSS VSS update rollup package for Windows server 2003 to resolve some VSS snapshot issues. KB VSS VSS-based backup operations may fail if VSS tracing is enabled on a Windows server 2003-based computer that has hotfix applied. KB VSS 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. KB VSS 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" Microsoft hotfixes required for NMM

20 Preinstallation Information Table 3 Hotfixes required for NMM 2.3 (page 2 of 8) KnowledgeBase article ID Windows 2003 (X32) Windows 2003 (X64) Windows 2008 (X32) Windows 2008 (X64) Windows 2008 R2 Applies to Description KB VSS Note: Only apply this hotfix if needed. When you shut down a computer that is running the Microsoft Storport storage driver (Storport.sys) on Windows server 2003 SP2, you may receive a Stop 0x C error message that resembles the following: *** STOP: 0x C (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 These versions of Storport incorrectly forward interrupts to the miniport after the PCI bus is in the device off state (D3). Exchange KB Exchange server 2007 KB Exchange server 2007 SP2 KB Exchange server 2007 SP2 KB Windows server 2003 SP1, when used with Windows server 2003 x32 or Windows server 2003, Enterprise x64 Edition. KB Windows server 2003 x32 and x64 edition If encountering VSS_E_WRITERERROR_RETRYABLE errors, take corrective action documented in this knowledgebase article. Windows server 2003 Post-SP1 COM+ 1.5 Hotfix Rollup Package 11 for Exchange 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 an extended functionality when you use the maintenance mode to perform administrative and maintenance tasks in a clustered environment. A hotfix is available that adds support for GUID partition table (GPT) volumes that are larger than 2 terabytes on a Windows server 2003-based server cluster. 20 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

21 Preinstallation Information Table 3 Hotfixes required for NMM 2.3 (page 3 of 8) KnowledgeBase article ID Windows 2003 (X32) Windows 2003 (X64) Windows 2008 (X32) Windows 2008 (X64) Windows 2008 R2 Applies to Description Storage arrays KB EMC CLARiiON Storport Drivers For Windows server 2003 configurations running STORport drivers with CLARiiON storage arrays. Note: This hotfix is part of SP2 and need not be installed separately. KB EMC Symmetrix /CLARiiON Hotfix for any host running Windows server 2003/SP1 or Windows server 2003/R2 and connected to Symmetrix or CLARiiON storage. Note: This hotfix are part of SP2 and need not be installed separately. KB Symmetrix Storport Drivers Hotfix Windowsserver2003-KB x86-ENU.e xe available for Windows server 2003 configurations running STORport drivers with Symmetrix storage arrays. Note: This hotfix are part of SP2 and need not be installed separately. Replication Manager SP1 KB RM SP1 Microsoft hotfix Windowsserver2003-KB x86-ENU.e xe for Replication Manager SP1. This hotfix is required because the volume mount points on disks in a server cluster may intermittently become unavailable after you install Windows server 2003 SP1. KB RM SP1 Microsoft hotfix WindowsServer2003-KB x86-ENU. exe for Replication Manager SP1. This hotfix is required because a Windows server 2003-based computer stops responding when you perform a backup of an Exchange server database. KB RM SP1 Microsoft hotfix WindowsServer2003-KB x86-ENU. exe for Replication Manager SP1. This update fixes various Volume Shadow Copy Service issues in Windows server Microsoft hotfixes required for NMM

22 Preinstallation Information Table 3 Hotfixes required for NMM 2.3 (page 4 of 8) KnowledgeBase article ID Windows 2003 (X32) Windows 2003 (X64) Windows 2008 (X32) Windows 2008 (X64) Windows 2008 R2 Applies to Description Server cluster KB Windows server 2003, Enterprise x64 edition or Windows server 2003 SP1 on a server cluster KB Windows server 2003 x86 SP2 (SP2) KB Windows server 2003 x86 (32-bit architecture) and x64 SP1 (SP1) and Service pack 2 (SP2) Volume mount points on disks in a server cluster may intermittently become unavailable after you install Windows server 2003 SP1. A new physical disk resource does not successfully move to another cluster node on a Windows server 2003-based server cluster A hotfix is available that adds support for GUID partition table (GPT) volumes that are larger than 2 terabytes on a Windows server 2003-based server cluster. SQL server KB SQL server 2005 SP2 KB SQL server 2005 SP 3 To take a writer-level backup of SQL server 2005 SP2 that has a SQL snapshot, install the cumulative update package 10 for Knowledgebase article KB To take a writer-level backup of SQL server 2005 SP 3 that has a SQL snapshot, install the SQL 2005 Cumulation Update from Knowledgebase article KB Note: The article KB contains a number of downloads. Ensure to install all. KB SQL server 2005 KB SQL server 2005 (64-bit), Version KB SQL server 2005 Install SQL hotfix KB 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. 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. 22 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

23 Preinstallation Information Table 3 Hotfixes required for NMM 2.3 (page 5 of 8) KnowledgeBase article ID Windows 2003 (X32) Windows 2003 (X64) Windows 2008 (X32) Windows 2008 (X64) Windows 2008 R2 Applies to Description SharePoint KB SharePoint 2007; SharePoint Services 3.0 SP2 KB SharePoint server 2007 KB Windows SharePoint Services 3.0 If you have already installed hotfix , then install hotfix also. If you have not installed hotfix , then install only hotfix 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 Go to the Microsoft support website and search for KB 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 2007 Microsoft Office servers SP2 package gives customers the latest updates to the 2007 Office server products. This service pack includes two main categories of fixes: Previously unreleased fixes that were made specifically for this service pack. In addition to providing general product fixes, SP2 includes improvements in stability, in performance, and in security. All the public updates, security updates, cumulative updates, and hotfixes that were released through February Windows SharePoint services 3.0 SP2 gives customers the latest updates to Windows SharePoint services 3.0. This update includes two main categories of fixes: Previously unreleased fixes that were made specifically for this service pack. In addition to general product fixes, this includes improvements in stability, in performance, and in security. All the public updates, security updates, cumulative updates, and hotfixes that were released through February Before you try to install this service pack, ensure that you read the information about how to deploy software updates for Windows SharePoint Services 3.0. Microsoft hotfixes required for NMM

24 Preinstallation Information Table 3 Hotfixes required for NMM 2.3 (page 6 of 8) KnowledgeBase article ID Windows 2003 (X32) Windows 2003 (X64) Windows 2008 (X32) Windows 2008 (X64) Windows 2008 R2 Applies to Description KB Windows SharePoint services KB Office SharePoint services Cumulative update packages for Windows SharePoint Services 3.0 (released in April 2010) contain hotfixes for the Windows SharePoint Services 3.0 issues that were fixed since the release of Windows SharePoint Services 3.0. SharePoint 2007 VSS backup and restore fails if the update is not installed. Cumulative update packages for Microsoft Office SharePoint server 2007(released in April 2010) contain hotfixes for the Office SharePoint server 2007 issues that were fixed since the release of Office SharePoint server SharePoint 2007 VSS backup and restore fails if the KBs are not installed in the machine. Hyper-V KB Hyper-V If this update is not installed prior to recovery, the system will not come back after recovery of SYSTEM COMPONENTS. KB Hyper-V When a scheduled save is started, the following error message might appear in the event viewer: ASR Error: Failed to collect critical information for ASR Backup. The reason this message appears is that ASR is unable to obtain disk information for device 3 (Win32 error code 0x2). KB Hyper-V SP2 KB Hyper-V SP2 KB Hyper-V SP2 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 role. When the Hyper-V writer seems to be missing due to the presence of corrupt virtual machine configuration files in the Hyper-V server. When virtual machine files are saved on a volume mounted on a failover cluster using a volume GUID. 24 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

25 Preinstallation Information Table 3 Hotfixes required for NMM 2.3 (page 7 of 8) KnowledgeBase article ID Windows 2003 (X32) Windows 2003 (X64) Windows 2008 (X32) Windows 2008 (X64) Windows 2008 R2 Applies to Description KB Hyper-V SP2 KB Hyper-V SP2 KB Hyper-V SP2 Hyper-V writer update if the backup fails for one of the following reasons: Retryable VSS error. VSS application writer provider is moving to a bad state. If recovery of a virtual machine is failing because it has legacy network adaptors attached. After performing this update, you must update the integration services on each of the virtual machines running on the server by inserting the Integration Services Disk from the Action menu in the virtual machine's management console. This will require a restart of virtual machine. Apply to all Hyper-V hosts. This update for Windows server 2008 fixes a crash of the Hyper-V host server, which you might experience 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] Data Protection Manager KB 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. KB DPM 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. General KB Windows server 2003 Service Pack 1 or Windows server 2003 Service Pack 2 The Virtual Disk Service 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. Microsoft hotfixes required for NMM

26 Preinstallation Information Table 3 Hotfixes required for NMM 2.3 (page 8 of 8) KnowledgeBase article ID Windows 2003 (X32) Windows 2003 (X64) Windows 2008 (X32) Windows 2008 (X64) Windows 2008 R2 Applies to Description KB Windows server 2003 SP1, SP2, R2, and R2 SP2 KB Windows server 2008 SP2 KB Windows server 2003 SP2 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, 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. 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. Preinstallation checklists You can manually check if your setup for backing up and restoring an application is configured correctly. This section provides the preinstallation checklists that you can refer to either before or after installing NMM 2.3. As each checklist is completed, indicate it by using the checklist provided in Table 4 on page 26. Table 4 Checklist overview Mark complete Checklist Generic checklist on page 27 CLARiiON checklist on page 30 Symmetrix checklist on page 32 SQL checklist on page 34 Microsoft SharePoint checklist on page 35 Microsoft Exchange checklist on page EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

27 Preinstallation Information Generic checklist Table 5 on page 27 provides the generic checklist for NMM 2.3. Review the following checklist before installing NMM 2.3. Table 5 Generic checklist (page 1 of 3) Check to see if: Supported operating system version and service pack level are correct. Required hotfixes are installed. Other backup software is installed and running. 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 mentioned in Microsoft hotfixes required for NMM 2.3 on page 19. If yes, either uninstall the other backup software or stop their execution. Note: Look at Add or Remove Program in Control Panel and ensure that no other backup application is installed. Also, check with the backup administrator that this machine is not being backed up with any backup software, other than DPM 2007 SP1 software. PowerSnap or Replication Manager is installed. If yes, remove any that is installed. Note: NMM can be installed on NetWorker client and NetWorker storage node 7.5 SP3 or 7.6 SP1 or later. Firewall is enabled. If not enabled, pass. If enabled, run the next check. There are open ports in the firewall to allow NMM to communicate. IPv6 status. Host can connect with NetWorker server, proxy node, or storage node hosts and this host is reachable from other hosts. In case of cluster, check if nodes of virtual server are able to pass this test and the virtual server is reachable. DNS lookup of host Host is reachable and can be looked up in DNS, is properly configured on the network, and there are no IP conflicts. Both forward and reverse DNS lookup should pass. In case of cluster, check if nodes of virtual server are able to pass this test and the virtual server is reachable. If the firewall is configured for NMM, then pass. If IPv6 is enabled, NMM will not work properly. Disable IPv6 for the NetWorker adapter. If yes, pass.otherwise, fail. Preinstallation checklists 27

28 Preinstallation Information Table 5 Generic checklist (page 2 of 3) Check to see if: Multihomed (Multiple NIC) environment: Each NIC should be configured with only one IP address. Each IP belonging to any specific NIC must reside in a separate subnet or VLAN. Each IP on any host must always resolve to one unique hostname. Details VSS Admin List volume This gives a list of volumes that can be used for snapshots. If the volume being backed up is one of the list. Any of the disks are RAW. Check for writer stability. Version of VSS hardware provider currently installed and running. For software provider, there is enough free space to create shadow copies for each volume. After installing NMM, Replication Manager, and PowerSnap services, and the various services are up and running. If the machine is an Exchange server, after installing NMM, Replication Manager, and PowerSnap services, the Replication Manager Exchange interface service, the various services are up and running. To support Hyper-V backups in Windows 2008, OS service pack 2 is required. Hyper-V Integration Services version requirement. Correct versions of NetWorker server, NetWorker storage node, and other applications are installed. The saveset should only contain these volumes. NMM does not support RAW disks. Ensure that all writers on the system are in stable state by using the command: vssadmin list writers VSS hardware provider version and Solution Enabler version If there are providers other than Microsoft provider, they will be used for the volumes they are associated with. Ensure that a maximum area limit has not been set for shadow copies. The following command lists the shadow copy storage association for each volume: vssadmin list shadowstorage After running this command, check that the value Maximum Shadow Copy Storage space: is set to UNBOUNDED for the volume chosen for backup. If yes, pass. If no, start the services. Installation services on page 17 and Verifying the installation on page 50 provides details. Check if integration services version or later is installed on all virtual machines for online backup. NMM 2.3 can be installed on NetWorker client or storage node: 7.5 SP3 and later 7.6 SP1 and later 7.6 SP2 and later For Data Domain support: NetWorker server 7.6 SP1 and later with NMM 2.3 installed on NetWorker client or storage node 7.6 SP1 and later. For Windows Disaster Recovery support: NetWorker server 7.6 SP2 and later with NMM 2.3 installed on NetWorker client or storage node 7.6 SP2 and later Note: NetWorker server and storage node 7.6 SP2 and later will support all features. Correct licenses are installed on NetWorker server. BitLocker encryption is enabled. Disable BitLocker encryption because Bitlocker encryption is not supported. Group inactivity timeout is set to 0. Set group inactivity time-out to EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

29 Preinstallation Information Table 5 Generic checklist (page 3 of 3) Check to see if: Details Client retries is set to 0 in group properties. Set client retries to 0. Software and hardware providers are being used at the same time. Install path is English only. Application host and proxy host have same OS, same service pack, same platform, and similar patch level. Cluster type and cluster requirements. Use either software provider or hardware provider. Using both will cause backup to fail. Only English path is supported. If application host and proxy host do not match backups would not work fine When hardware provider is used If MSDTC is required or not: SQL 2005 on Windows 2003 Cluster: Yes SQL 2005 on Windows 2008 Cluster: No SQL 2008 on Windows 2008 Cluster: Yes Windows 2003 (32-bit and 64-bit) MSCS cluster: SP1 and R2 require Microsoft hotfixes described in KnowledgeBase articles KB and KB SP2 and R2 SP2 require Microsoft hotfix described in KnowledgeBase article KB Note: MSDTC is not required for Window 2008 (Exchange). Dynamic disks are not supported in an MSCS cluster. The appropriate snapshot software for the array is installed and licensed: For EMC CLARiiON: EMC SnapView Clone EMC SnapView Snapshots For EMC Symmetrix DMX TM : EMC TimeFinder /Mirror EMC TimeFinder/Snap Configurations specific to Symmetrix on page 72 provides details. For EMC Celerra: Celerra Snapshots For Dell EqualLogic PS Series: EqualLogic Snapshots For IBM System Storage DS6000/DS8000: IBM FlashCopy The appropriate VSS hardware provider on the Windows server hosting the application is installed: EMC VSS Common Provider for EMC Symmetrix and CLARiiON arrays: The EMC VSS Common Provider is available on Powerlink at The release notes for the EMC VSS Common Provider can be found on Powerlink at EMC Celerra VSS Provider for Celerra arrays The EMC Celerra VSS Provider is available on Powerlink at Dell/EqualLogic Integration ToolKit for EqualLogic PS Series arrays The Dell documentation provides information on access and support. IBM DS6000 and DS8000 arrays The IBM System Storage DS Open API Package is available at the IBM support website. Windows Unified Data Storage Server (WUDSS) The Microsoft documentation provides information on access and support. Preinstallation checklists 29

30 Preinstallation Information CLARiiON checklist Table 6 on page 30 provides the checklist for CLARiiON for NMM 2.3. Review the following checklist before installing NMM 2.3. Table 6 CLARiiON checklist (page 1 of 3) Check to see if: Details Client and proxy base-level software requirements VSS hardware provider is installed and meets an exact or minimum revision level. The version of Solutions Enabler is the one that was provided with the VSS hardware provider version. The target CLARiiON IP addresses are in the SYMAPI authority listing. VSS hardware provider Solution Enabler version Note: Updating the SYMCFG authorization list on page 70, step 3 provides details about how to verify that the SYMCFG authorization list has been updated correctly. EMC PowerPath is installed. Note: PowerPath is not be required for EMC iscsi on Windows Also, PowerPath is not supported in VMware VMware has its own path management capability. The PowerPath version installed is correct. For Windows 2003 (and R2) /SP2: Minimum 5.01 For Windows 2008: minimum (only applies if PowerPath is installed) Note: On ESX server, PowerPath is not required. NaviAgent is recommended on both host and guest. The multipathing feature is installed on Windows server If multipathing is enabled on Windows 2008, PowerPath is not a mandatory requirement. EMC FLARE 26 required AULA mode required. The iscsi Initiator version installed is correct. Version 2.06, 2.07, or 2.08 is required. There is no mention of iscsi in the Provider Support Matrix: Replication Manager supports Matrix and supports iscsi for CLARiiON with the iscsi initiator. PowerPath can handle both SAN and iscsi, but iscsi must be specified as part of the PowerPath install. IP address of CLARiiON must be mentioned in iscsi Initiator. Host must be visible on CLARiiON. The HBA driver version installed is correct. Must be a STORport driver. Note: EMC requires EMC certified drivers for both Emulex and QLogic Fiber Channel cards. The EMC Support Matrix carries only the most current and previous version. The appropriate Windows VSS/VDS hotfixes are installed. In VMware environment, on ESX server, NavihostAgent is installed. In virtual machine environment, LUNs are assigned as raw mapping device from the ESX server to the guest virtual machine. 30 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

31 Preinstallation Information Table 6 CLARiiON checklist (page 2 of 3) Check to see if: In virtual machine environment, the authorization has been provided by using the following commands in the guest virtual machine: C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u <username> -p <password> -s <esx_network_address> [-force]] where, username and password are the credentials of ESX. Details Client or proxy resident EMC Navisphere software for CLARiiON configurations NaviCLI and NaviSecCLI are installed and their location are in system environment variable. Admsnap is installed and its location is in system environment variable. If installed and in location is in system environment variable, then pass. Otherwise, fail. If installed and in location is in system environment variable, then pass. Otherwise, fail. The Admsnap version installed is correct. For Windows 2003 with FLARE 19: minimum Admsnap For Windows 2003 with FLARE 20: minimum Admsnap For Windows 2003 with FLARE 22: minimum Admsnap For Windows 2003 with FLARE 24: minimum Admsnap For Windows 2003 with FLARE 26: minimum Admsnap For Windows 2003 and 2008 FLARE 28: minimum Admsnap For Windows 2003, 2008 and 2008 R2 FLARE 29: minimum Admsnap For Windows 2003, 2008 and 2008 R2 FLARE 30: minimum Admsnap The SPA and SPB belong to the same CLARiiON. The FLARE operating environment version installed on the CLARiiON arrays is correct. The following CLARiiON arrays running FLARE are supported: 19, 22, 24, 26, 28, 29 or 30 EMC Access Logix is active. SNAPVIEW enabler installed on CLARiiON If the release of the CLARiiON is in the list, then pass. Otherwise, fail. If enabler is present, pass. Otherwise, fail. CLARiiON setup The host's NaviCLI version is compatible with CLARiiON array release. There are LUNs in the reserved LUN pool. If host NaviCLI version is the same or higher than CLARiiON release version, pass. If host NaviCLI version is lower than CLARiiON release version, fail. If there are LUNs in the reserved LUN pool, pass. Otherwise, fail. Note: Ensure that the number of LUNs in the LUN pool are sufficient to cover the number of snapshots at any given time. The array is capable of creating clones. There are clone private LUNs. The failover mode settings for the CLARiiON are set: The CLARiiON failover mode or trespassing must be set to 1. For iscsi, the connectivity is 4. The specified username and password works for that CLARiiON. If clones are enabled, pass. Otherwise, fail. If clones are private clones, pass. Otherwise, fail. Preinstallation checklists 31

32 Preinstallation Information Table 6 CLARiiON checklist (page 3 of 3) Check to see if: The CLARiiON using NaviCLI (classic) interface to see if "system@<host_id> is in the privileged user list on the CLARiiON. The Solutions Enabler is licensed. Saveset has one partition per LUN. Is the base ESX registered on the guest virtual machine of both proxy and application host. Orphaned snapshot or snap session for particular storage group is present. Host is registered with both SPA and SPB. At least one CLARiiON LUN is visible to the proxy. The appropriate host-based EMC storage software, such as PowerPath and EMC Navisphere for EMC CLARiiON host-based utilities, as required by the supporting array and customer environment are installed. Details If there are privileged users and the system@<host_id> is on the list, then pass. If there are privileged users and system@<hostid> is not in the list, then fail. If the privileged user list was empty, then unknown. The authorization must be provided by using the following commands in the guest virtual machine: C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u <username> -p <password> -s <esx_network_address> [-force]] where, username and password are the credentials of ESX. If yes, then delete them. Symmetrix checklist Table 7 on page 32 provides the checklist for Symmetrix for NMM 2.3. Review the following checklist before installing NMM 2.3. Table 7 Symmetrix checklist (page 1 of 3) Check to see if: VSS hardware provider is installed and meets an exact or minimum revision level. Details VSS hardware provider Solution Enabler version Note: The version of Solutions Enabler is the one that was provided with the VSS hardware provider version. EMC PowerPath is installed. Note: PowerPath is not supported in VMware. The PowerPath version installed is correct. For Windows 2003, 2003 R2 or 2003 SP2: Minimum 5.01 For Windows 2008: Minimum (only applies if PowerPath is installed) Note: On ESX server, PowerPath is not required. 32 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

33 Preinstallation Information Table 7 Symmetrix checklist (page 2 of 3) Check to see if: The HBA driver version installed is correct. Details Must be a STORport driver. Note: EMC requires EMC certified drivers for both Emulex and QLogic Fiber Channel cards. The EMC Support Matrix carries only the most current and previous version. In virtual machine environment, LUNs are assigned as raw mapping device from the ESX server to the guest virtual machine. In virtual machine environment, the authorization has been provided by using the following commands in the guest virtual machine: C:\Program Files\EMC\SYMCLI\shlib> vicfg setup [-u <username> -p <password> -s <esx_network_address> [-force]] where, username and password are the credentials of ESX. The Solutions Enabler is licensed. Save set has one partition per LUN. Ensure that appropriate front-end ports are zoned to the production machine and to the proxy host. At least two ports to the host should be zoned. Note: PowerPath is required for dual zoning. When assigning LUNs to a Windows machine, ensure that both front-end ports are presented (visible to the SCSI bus on the system) to the Windows. Otherwise, backups may fail with a configuration error. For the proxy mount host, ensure that at least one LUN from each Symmetrix (if multiple are used) is permanently zoned and masked to the machine. This is required for reliable import/deport of snapshots. When using the EMC VSS Provider with Symmetrix storage arrays, enable these flags on all the directors to which the VSS host is connected: VCM director flag, which enables the Volume Logix software on Symmetrix so that the VSS Provider can perform device masking. Failure to enable this flag results in the VSS Provider failing to create and import snapshots, due to the lack of device masking capabilities. SPC-2 director flag, which forces Symmetrix to report its device identifiers in a way that VSS recognizes. Note: Failure to enable this flag results in the VSS service failing all snapshots before the EMC VSS Provider is called. If PowerPath software is installed, launch PowerPath and verify that all Symmetrix LUNs are displayed with the state Alive. Verify Solutions Enabler connectivity by running SYMCLI command symcfg discover. Ensure to assign GateKeeper devices to the production and proxy nodes. Note: It is recommended that the number of gatekeepers for a single host with few applications running be kept as 8. However, the minimum is 6. Preinstallation checklists 33

34 Preinstallation Information Table 7 Symmetrix checklist (page 3 of 3) Check to see if: Verify that the device groups and associated snapshot devices for TimeFinder Mirror/Snap/Clone are configured properly. Details Note: Configuring more than one snapshot technology with STD devices is not recommended. If TimeFinder/Mirror is configured, ensure that at least one BCV device is in Not Ready, Synchronized, or SyncInProg state, before taking backup. Note: If the snapshot policy used deletes a snapshot at the time when the next backup is run, no action is required. If TimeFinder/Clone is configured, ensure that at least one clone target device is in Not Ready, Created, or Recreated state, before taking backup. Note: If the snapshot policy used deletes a snapshot at the time when the next backup is run, no action is required. If TimeFinder/Snaps is configured, ensure that at least one VDEV target device to be in Not Ready, Created, Recreated state before taking backup. Note: If the snapshot policy used deletes a snapshot at the time when the next backup is run, no action is required. SQL checklist Table 8 on page 34 provides the checklist for SQL for NMM 2.3. Review the following checklist before installing NMM 2.3. Table 8 SQL checklist Check to see if: Check if SQL instance version for each instance installed: SQL 2005 needs SP4 SQL 2008 SP1 SQL 2008 R2 Check if SQL virtual server is online in case of clustered instance. Check if SQL services for each instance are up and running: SQL server SQL browser Check if SQL server writer status is stable. Is SQL server running in single user mode? Details If yes, fail. 34 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

35 Preinstallation Information Microsoft SharePoint checklist Table 9 on page 35 provides the checklist for SharePoint for NMM 2.3. Review the following checklist before installing NMM 2.3. Table 9 SharePoint checklist Check to see if: 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. All essential SharePoint services are up and running: SQL server Writer (running and set to automatic) for SQL databases SharePoint Services Writer (running and set to automatic) for SharePoint 2007 and SharePoint SharePoint Search Writer for SharePoint 2007 or SharePoint 2010 Search If not running, then it is a warning to check if role is enabled. Ensure that the services are started. Details Note: The service should be running only if the role is enabled. Microsoft Office Server Search Writer for Microsoft Office Server search If not running, then it is a warning to check if role is enabled. Ensure that the services are started. Note: The service should be running only if the role is enabled. NMM client is installed on all machines participating in a farm for VSS backup. SharePoint VSS writer is registered on at least one web front-end within a farm. If yes, pass. If no, run stsadm -o registerwsswriter. Else, it is a warning. Either SQL server writer or MSDE writer-sql2000 is enabled for SharePoint server The SharePoint environment is stable or not using the SharePoint server Administration tool. Staging area space requirements are fulfilled. Note: More free space may be required if the staging is slow. SharePoint 2007 Shared Service Provider (SSP) is properly configured or not. For SharePoint 2007 and SharePoint 2010, the user should have administrator rights for SharePoint, that is, the user should be the SharePoint administrator. If all components of Sharepoint are on the same machine, the machine might not be part of a domain. If it is distributed than system should be part of domain. Check SharePoint, OSearch, SPSearch, SQL writers are in stable state. Verify whether SharePoint VSS Writer is running under SharePoint farm administrator account. Otherwise, the writer will not be able to connect to the configuration database to obtain list of SharePoint components, and consequently SharePoint VSS backup will fail. In SharePoint 2010, if SPSearch is enabled in multiple servers of a farm, Sharepoint services and search writers are not reported. In SharePoint 2010, check if SharePoint self privilege is enabled in configured database. If not enabled the SharePoint writer reports GUID instead of Search application name. If requirements are fulfilled, pass. For optimized backup The number of processors on web front-end must be the size of largest site-collection. If a distributed farm is in domain, pass. Otherwise, fail. If SharePoint VSS writer is running under SharePoint farm administrator account, pass. Otherwise, fail. If SPSearch is enabled only on a single server in the farm, pass. Otherwise, fail. If SharePoint self privilege is enabled in configured database, pass. Otherwise, fail. Preinstallation checklists 35

36 Preinstallation Information Microsoft Exchange checklist Table 10 on page 36 provides the checklist for Exchange for NMM 2.3. Review the following checklist before installing NMM 2.3. Table 10 Exchange checklist (page 1 of 2) Check to see if: Exchange server 2003 (for x86) Standard and Enterprise editions with SP2 or later is installed. Exchange server 2007 (for x64) Standard and Enterprise Edition with SP3 with Rollup1 or later is installed. Exchange Server 2010 (for x64) Standard and Enterprise Edition with SP1 Rollup 2 or later is installed. Cluster is installed, then check the state of the cluster service. Message API (MAPI) and Collaboration Data Object (CDO) kits are installed and are version or later for Exchange 2007 and Exchange Credentials of user of Exchange server are correct. Exchange server is a part of domain. Essential Exchange Services are up and running: Exchange Information Store Exchange Attendant Exchange Resource Agent Message Transfer Agent (MTA) Replication Service for cluster environment Details For WSFC or MSCS, pass if cluster in healthy. The entered credentials must be that of Exchange administrator or the user who will start the backup. Otherwise, fail. Note: No services are checked for Exchange Following conditions are met: System path and the log path are in the same location. In normal backup of Exchange, the database files and transaction log files are in different volumes. In hardware scenario, the database files and log files are in different LUNs. For Exchange 2007 The writer for both the active node and passive node in the CCR environment is stable. For Exchange 2010 DAG Exchange IS writer and Exchange replication writer are healthy. For Exchange 2007 Exchange storage groups locale should be the same as the Exchange server locale. The save set contains only Exchange writer and that no other writer is included during backup. The group are properly mounted, else the whole backup will fail. For Exchange 2007 The CCR of active node and passive node is consistent, that is, check the health of CCR before taking backup. For Exchange 2010 Ensure that the databases under the DAG are healthy and mounted state before running the backup. Backup is grouped with not more than ten storage groups at a time, if NSR_EXCHANGE_LIMIT_SG=yes. Otherwise, the maximum limit is governed by a limit of 64 snapshots, which means a maximum of 32 storage groups. Note: Not applicable for Exchange EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

37 Preinstallation Information Table 10 Exchange checklist (page 2 of 2) Check to see if: Exchange management tools are installed on proxy client. For Exchange 2010 In IIS Manager console, Windows Authentication should be enabled. For Exchange 2010 ensure that the Kernel Mode Authentication is clear. Go to IIS Manager > Expand Your Host > Expand Sites > Expand Default Web Site >Powershell: 1. On the right hand side pane, double-click on Authentication and Enable Windows Authentication. 2. On Windows Authentication, right-click and check if Kernel Mode authentication is clear. For Exch2010 Ensure that the client resource created for DAG is with FQDN. For Exchange 2010 During recovery in DAG, check whether the database is mounted in only the active node and recovery is taking place only in active node. The database, which is restored is in mounted state. Passive copies of the databases are in suspended state. For Exchange 2010 Ensure that the Logged in user has a mailbox for RDB recovery. For Exchange 2010 During recovery in DAG environment, replication should be in suspended state. For Exchange 2010 Check if user can ping DAG name. For Exchange 2010 Check if the database to be restored is in overwritable state. For Exchange 2010 Check that the user credential entered for Exchange has send-as and receive-as permissions to browse RSG and RDB mailbox. 1. On the Exchange Server, select the 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 Before starting backup ensure that the path provided for NSR_ALT_PATH is valid. For Exchange 2007 and Exchange 2010 For RSG or RDB item level browsing, at least one public folder database is needed. Details Preinstallation checklists 37

38 Preinstallation Information Supported configurations This section describes the basic configurations in which the NMM is supported: Simple LAN-based configuration on page 38 LAN-based configuration with a proxy client on page 39 LAN-free configuration on page 40 LAN-free dedicated storage node configuration on page 41 Simple LAN-based configuration Figure 1 on page 38 shows a simple LAN-based configuration with a storage area network. In a LAN-based configuration, the production data is stored on a storage area network (SAN) or direct-attached storage (DAS). The data path to the NetWorker storage node devices is over a LAN. The application server that is being protected has the NMM installed. The data moves as follows: 1. The NetWorker server, which must be release 7.5 SP3 or later, 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, using the NMM software. Note: In Figure 1 on page 38, snapshots are represented by S1 through S5. 3. The application server with the NMM software uses a snapshot in primary storage to transfer the data over the LAN and into a conventional backup medium such as a file type disk, advanced file type disk, tape, or Data Domain device. NetWorker Server or LAN Application server (NMM 2.3 and NetWorker client or 7.6.1) SAN NetWorker Storage Node or Traditional storage Primary storage (CLARiiON or Symmetrix) S5 S1 S4 S3 S2 GEN Figure 1 Simple LAN-based configuration 38 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

39 Preinstallation Information LAN-based configuration with a proxy client Figure 2 on page 39 shows a LAN-based configuration with a storage area network and a proxy client. Both the application server and the proxy client have the NMM installed. Install the proxy client software by using the NMM software package. Note: The application server and the proxy client must use the same NMM version, operating system version, NetWorker version, and VSS Provider version. If NMM 2.3 is installed on either the application server or the proxy client machine, then the other machine must also use NMM 2.3. Backup and recovery will fail if NMM 2.3 is used on one of these machines, and an earlier version of NMM is used on the other. A proxy client is a host that acts as a remote data mover (DM) when snapshots are rolled over to a conventional backup medium. A proxy client frees resources on the application server. When a backup operation uses a proxy client, it is known as a serverless backup. 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 39, snapshots are represented by S1 through S5. 3. The snapshot is made visible to the proxy client. 4. The proxy client uses a snapshot in primary storage to transfer the data over the LAN and into a conventional backup medium such as a file type disk, advanced file type disk, tape, or Data Domain device. NetWorker Server or LAN Application server (NMM 2.3 and NetWorker client or 7.6.1) Proxy client (NMM 2.3 and NetWorker client or 7.6.1) SAN Primary storage (CLARiiON or Symmetrix) S5 S1 S4 S3 S2 NetWorker Storage Node or Traditional storage GEN Figure 2 LAN-based configuration with a proxy client Supported configurations 39

40 Preinstallation Information LAN-free configuration Figure 3 on page 40 shows a LAN-free configuration with a storage area network. The NMM is installed on the application server. The proxy client is installed on the NetWorker storage node. You can set up a NetWorker storage node 7.5 SP3 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, using the NMM software. Note: In Figure 3 on page 40, snapshots are represented by S1 through S5. 3. The snapshot is made visible to the proxy client. 4. The proxy client, in this case the storage node, uses a snapshot in primary storage to transfer the data into a conventional backup medium such as a file type disk, advanced file type disk, tape, or Data Domain device. 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 proxy node, which has NetWorker storage node software and backup media configured. The NMM proxy node acts as a NetWorker storage node. NetWorker Server or LAN Application server (NMM 2.3 and NetWorker client or 7.6.1) Proxy client (NMM 2.3 and NetWorker Storage Node or 7.6.1) SAN Primary storage (CLARiiON or Symmetrix) S5 S1 S4 S3 S2 Traditional storage GEN Figure 3 LAN-free configuration 40 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

41 Preinstallation Information LAN-free dedicated storage node configuration A dedicated storage node (DSN) is a storage node that acts as a dedicated backup device for a local NMM host. A DSN only allows data from the local host to be backed up to its devices. The NMM 2.3 support for dedicated storage node allows you to perform the following: LAN-free backups without configuring a separate NMM proxy node, or deploying a 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 a NMM proxy node. DSN has it own license enabler. The NetWorker Licensing Guide provides more information about licensing. The following are the licensing details of DSN: Evaluation license supports DSN Enterprise license supports DSN Capacity-based license or NetWorker Source Capacity Data Zone Enabler supports DSN Business edition does not support Storage Node/DSN Work group edition does not support Storage Node/DSN Install the following to facilitate NMM 2.3 support for dedicated storage node: Note: To facilitate NMM 2.3 support for dedicated storage node, a valid NetWorker license for dedicated storage node is required. The NetWorker Licensing Guide provides more information about the dedicated storage node license. NetWorker server 7.5 SP3 or NetWorker 7.6 SP1 or later NetWorker Storage node 7.5 SP3 or NetWorker Storage node 7.6 SP1 or later on the application server host NetWorker client software 7.5 SP3 or NetWorker client software 7.6 SP1 or later NMM 2.3 Configuring a storage node as a dedicated storage node on page 91 provides information about configuring a storage node as a dedicated storage node: NMM 2.3 dedicated storage node supports backup and recovery of all applications supported by NMM 2.3. For example, DPM, Active Directory, Hyper-V, SharePoint, Exchange, SQL, and file system backups. Note: If you do not want to configure a DSN and prefer to use NMM 2.3 as a client: NetWorker traditional backups will not be supported after the installation of NMM 2.3 client software. NetWorker traditional backups already taken before NMM 2.3 client installation can be recovered using NMM 2.3 GUI only. Supported configurations 41

42 Preinstallation Information Ensure that you configure the following to facilitate NMM 2.3 support for dedicated storage node: A storage node device that uses the NetWorker Management Console, which is hosted by the NMM 2.3 client. If required, an additional device can be configured on the storage node to cover save set entries. 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 using the selected snapshot policy. NMM client resource A storage node device in the client resource using media pool selection criteria Note: If you are not using a DSN device, ensure to manually create or setup a default device. The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides application-specific information about dedicated storage node configurations for all the Microsoft applications. Figure 4 on page 42 shows a LAN-free configuration with a dedicated storage node. NetWorker Server or LAN Application server (NMM 2.3 and NetWorker Storage Node or 7.6.1) SAN Primary storage (CLARiiON or Symmetrix) S5 S1 S4 S3 S2 Traditional storage GEN Figure 4 LAN-free configuration with a dedicated storage node 42 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

43 Preinstallation Information The data in a LAN-free configuration with a dedicated storage node moves as follows: 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 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 42, 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. The NetWorker server and the application server communicate through the LAN. However, the data itself is not transferred across the LAN because the conventional backup medium is attached directly to the NetWorker storage node. Supported configurations 43

44 Preinstallation Information 44 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

45 2 Installing the Software This chapter includes the following sections: Installing NMM Installing NMM in a MSCS environment Installing NMM on Windows 2008 server core Verifying the installation Maintaining the installation Removing the software Upgrading the software Upgrading to NMM 2.3 storage node Installing Microsoft Office SharePoint Server service pack Installing the Software 45

46 Installing the Software Installing NMM This section provides the following information: Prerequisites on page 46 Access the installation files on page 46 Install the software on page 47 Prerequisites Ensure that the following requirements are taken care of before starting the NMM installation: 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 backup and recovery, NetWorker client 7.6 SP2 is installed. NetWorker server version used for backup operations is the same as the NetWorker client or storage node version installed on NMM 2.3 machine. 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 Server. 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 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 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

47 Installing the Software Install the software After you have accessed the NMM software files, you are ready to begin the installation. Note: NMM is installed in the same path where NetWorker client or NetWorker storage node is installed. To install NMM: 1. Run the Setup program (setup.exe) to start the installation wizard. The Welcome to NetWorker Module for Microsoft Applications Installation wizard appears. 2. Click Next. The Customer Information dialog box appears. 3. Type the name and organization information and click Next. The License Agreement dialog box appears. 4. Read the license agreement. To accept, select the I accept the terms in the license agreement option, and click Next. The Installation Location dialog box appears. 5. For Control Port and Data Port: Specify two different port number values that will be used by the Replication Manager client service. For most installations, the values supplied will be satisfactory.! CAUTION EMC Replication Manager is also sold as a separate product. If you have purchased Replication Manager as a separate product, do not attempt to run the product on the same system as NMM. You can change the Replication Manager port settings from the command line after the installation is complete. Changing Replication Manager port settings on page 85 provides more information. Note: Occasionally, an error message is displayed that installation was unable to create a Windows firewall exception for irccd.exe. Windows firewall exception error for irccd.exe on page 88 provides steps to manually add the exception. 6. This step is applicable only if Exchange Server 2007 or 2010 is installed. If Exchange Server 2007 or 2010 is installed on the same installation machine, type the following details in the new dialog box: a. Type the Exchange Server domain information: Domain Username Password b. Click OK. The Ready to Install dialog box appears. Installing NMM 47

48 Installing the Software 7. In the Ready to Install dialog box, click Next to start the NMM installation: Note: The installation may take several minutes. If Exchange Server is installed on the same installation machine, the nwexinfo.exe is started at the end of the NMM installation. In the nwexinfo dialog box: a. Type the Exchange Server domain information for Domain, Username, and Password. b. Click OK. If Microsoft Office SharePoint Server 2007 host is installed on the same installation machine, the nwmossinst.exe is started at the end of the NMM installation. In the NetWorker SharePoint Service Configuration dialog box: a. Type the following to complete the configuration required to perform Office SharePoint Server backup and recovery: Domain user name Password Temporary storage location Lock type b. Click OK. 8. 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 Enable and register the NMM software. 10. Configure the setup according to instructions in Chapter 4, Postinstallation Tasks. Installing NMM in a MSCS environment When installing the NMM software in a Microsoft Cluster Server (MSCS) environment, if you plan to use CLARiiON or Symmetrix hardware with EMC VSS Provider, ensure that first Microsoft Distributed Transaction Coordinator (MSDTC) is installed and running before installing the EMC VSS Provider. The EMC VSS Provider will install EMC Solutions Enabler, and Solutions Enabler requires that MSDTC be running. The EMC Solutions Enabler Version 6.3 Installation Guide provides details about installing and running Solutions Enabler. Note: EMC Solutions Enabler will be present only when using EMC VSS Provider. 48 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

49 Installing the Software Install NetWorker client 7.5 SP3 or 7.6 SP1 or later and follow the steps to install NMM. To install the NMM software in a MSCS environment: 1. Install the NMM software on the private disk of each physical node. 2. Configure each physical node as a client resource on the NetWorker Server. 3. In the Remote Access attribute of each virtual client resource, type the names of the physical nodes. 4. Configure privileges for each physical node on the NetWorker Server: 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. Installing NMM on Windows 2008 server core Install NetWorker client 7.5 SP3 or 7.6 SP1 or later and follow the steps to install NMM. To install the NMM software on Windows 2008 server core: 1. Access the NMM binaries as described in Access the installation files on page 46. Use the net use command to access remote machines from the 2008 server core. 1. Copy the NMM binaries to the 2008 server core by using FTP or general access method. 2. Access setup.exe in the networkr directory and press Enter to start NMM installation. Note: Do not use autorun.exe to install the NMM software. There is no GUI when NMM is installed on 2008 server core. However, the NMM installation wizard starts. This installation wizard is the same wizard that is started while installing NMM on other OS. Installing NMM on Windows 2008 server core 49

50 Installing the Software Verifying the installation Ensure that the following services are up and running: For PowerSnap nsrpsd.exe For Replication Manager irccd.exe If NMM detects SharePoint during installation NetWorker SharePoint Service Controller If NMM detects Exchange during installation Replication Manager Exchange Interface Maintaining the installation After installing the NMM software, you may run the Setup program in maintenance mode to change or remove the existing client installation. To run the Setup program in maintenance mode: 1. Log in as administrator on the client server. 2. To run the Setup program in maintenance mode, perform one of the following: Run the setup.exe file. or Select Start > Settings > Control Panel > Add/Remove Programs. Select the NetWorker Module for Microsoft Applications and click Change. The Welcome to NetWorker Module for Microsoft Applications Maintenance dialog box appears. 3. Click Next. The Setup program detects the existing NMM installation and displays the Maintenance Type dialog box. 4. Select the type of maintenance to perform: Use the Change option to change: The configuration settings of the NetWorker SharePoint Service Configuration dialog box. The password for Exchange Server by using nwexinfo. To a different authorized NetWorker Server. Change the password or changing to a different authorized server on page 51 provides more information. Use the Remove option to remove the NMM software from the system. Removing the software on page 51 provides more information. 5. Click Next. 50 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

51 Installing the Software Change the password or changing to a different authorized server To change the password or change to a different authorized server: 1. Start the Setup program in the maintenance mode. Maintaining the installation on page 50 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, perform any of the following: a. Click Update List to browse for all the available servers, and click Add to add a server to the Available Servers list. b. Select a server from the Available Servers list and click to move the server to the Selected Servers list. c. Select a server from the Selected Servers list and click to return it to the Available Servers list. d. Type a server name in the Enter a server name field.! CAUTION If an authorized server list is used together with a proxy server, then the proxy server must also authorize the production server, and the production server authorize the proxy server. 5. Click Next. Note: The selected NetWorker server is used to back up the data on the client. If you have not selected an alternate server, the default server is used to back up the data on the client. Removing the software To remove the NMM software: 1. Start the Setup program in the maintenance mode. Maintaining the installation on page 50 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 software 51

52 Installing the Software Upgrading the software This section provides the following information: Moving from an existing NetWorker VSS client or NMM setup to the NMM 2.3 release on page 52 Moving from NetWorker support for Microsoft Exchange 2010 interim solution to the NMM 2.3 release on page 52 Moving from an existing NetWorker VSS client or NMM setup to the NMM 2.3 release A direct upgrade of an existing installation of NMM or NetWorker VSS client to NMM 2.3 cannot be done. You must first remove the existing installation of NetWorker VSS client or NMM, and then install NMM 2.3. Before installing NMM 2.3: 1. Remove any existing version of NMM or NetWorker VSS client by running the Setup program in maintenance mode. Select the Remove option. 2. Remove all existing snapshots. Ensure that PowerSnap snapshot entries are deleted before reinstallation of NMM 2.3. Delete PowerSnap entries by using the PowerSnap client SnapManager or nsrnapadmin. Note: When the existing NMM software is removed, the metadata that was created during the installation process does not get deleted. The metadata consists of the configuration information created during a NMM installation. Moving from NetWorker support for Microsoft Exchange 2010 interim solution to the NMM 2.3 release If you are currently using the NetWorker support for Microsoft Exchange interim solution and want to move to NMM 2.3, follows these steps: 1. Using the interim solution, perform a full backup before any changes are made. 2. Install the appropriate version of NetWorker. 3. Install NMM Now, by using NMM 2.3, perform a full back up of the Exchange data. 52 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

53 Installing the Software Upgrading to NMM 2.3 storage node NMM supports upgrading NetWorker 7.3 SP3 or later to NMM 2.3 storage node. To upgrade to NMM 2.3 storage node: 1. If using NMM 2.2 SP1 and earlier, uninstall NMM. 2. Install the appropriate version of NetWorker storage node on the server. The EMC NetWorker Release 7.6 SP1 Installation Guide provides information about installing the NetWorker storage node. You will require an additional NetWorker storage node license to install the NetWorker storage node. 3. Install the NMM software. Installing NMM on page 46 provides more information. When the NMM installation detects that a NetWorker storage node is already installed on the server, a message window appears. It states that an existing NetWorker storage node installation has been detected, and asks if you want to install the NMM client as the storage node. 4. Click OK to upgrade to NMM storage node. The NMM storage node is installed. Installing Microsoft Office SharePoint Server service pack Note: Install the Microsoft Office SharePoint Server service pack only if you have SharePoint on your machine. Microsoft Office SharePoint Server SP2 or later must be installed. Without this fix installed on SharePoint machines, NMM might incorrectly list the presence of the SharePoint Help Search Writer (SPSearch Writer) on a SharePoint machine that does not actually have the writer. This could lead to a user creating an invalid saveset, and backup or recovery failure. Go to the Microsoft website and search for Office SharePoint Server 2007 SP2. Download and install this service pack on all machines in the SharePoint Server farm. After it is installed, no further action is required for NMM. When installing SP2 on a SharePoint farm, Microsoft recommends installing it in the following order: 1. Start the SP2 installation on all machines at the same time. 2. When the Proceed message box is displayed, click OK on all remote clients, but do not click OK to proceed on the web front end yet. 3. After installation completes on all remote clients, click OK on all remote clients, and then click OK to proceed with installation on the web front end. 4. Start the SharePoint configuration wizard. Upgrading to NMM 2.3 storage node 53

54 Installing the Software 54 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

55 3 Silent Installation of the Software This chapter includes the following sections: Overview 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 SCCM 2007 Server Troubleshooting the installation Silent Installation of the Software 55

56 Silent Installation of the Software Overview This release of NMM 2.3 provides support for: Silent (unattended) installation and removal of the software on a standalone server. Silent installation of NMM on page 56 and Silent removal of NMM on page 59 provide more information. Remote installation and removal of the software by using Microsoft System Center Configuration Manager 2007 (SCCM) Server. Installing and removing NMM by using SCCM 2007 Server on page 61 provides more information. Silent installation of NMM Silent installation of NMM 2.3 is a standalone method that uses the command line and scripts. Note: Install NetWorker client 7.5 SP3 or 7.6 SP1 or later before you install NMM 2.3. In the silent installation process, all the information that is required for a successful installation is gathered by the Setup file (setup.exe) from the command line, which makes any GUI dialog boxes unnecessary. You may type full setup.exe commands directly in the command line, or may include such commands in scripts and save it as a.cmd file. In a basic silent installation, first the NetWorker client or the storage node software is installed, and then the PowerSnap and Replication Manager services. The silent (unattended) installation status log files are available in the client computer s temp directory. For fast access to the temp directory: 1. Click Start > Run. 2. Type %temp%. Commands for silent installation of NMM Table 11 on page 56 lists the commands for silent installation of NMM 2.3. Table 11 Commands for silent installation of NMM (page 1 of 2) Option setup /s /v"/qb" Description Silent installation with progress bar. Note: Ensure that there is space between: setup and /s /s and /v /qb 56 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

57 Silent Installation of the Software Table 11 Commands for silent installation of NMM (page 2 of 2) Option setup /s /v"/qn" Description Basic installation with no progress bar. Note: Ensure that there is space between: setup and /s /s and /v /qn setup /s /v"/l*v \"%temp%\mylog.log\" /qb Note: 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 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. Ensure to use triple quotes in the command in case the %temp% path contains spaces. Note: The following command opens the Windows Installer, which is an engine for the installation, maintenance, and removal of software on modern Windows systems: setup /s /v" qn /L*v """%temp%\filename.log""" Ensure that there is space between: setup and /s /s and /v" /v" and qn qn and /L*v /L*v and """%temp%\filename.log""" PowerSnap and Replication Manager command line properties Table 12 on page 57 lists the command line properties that are recognized for PowerSnap and Replication Manager. Table 12 PowerSnap and Replication Manager command line properties Property Value Description ALLUSERS 1 Always set value to 1. VSSREG 0 Always set value to 0. REBOOT S Suppress Reboot. Always set value to S. ADDLOCAL (x86) Proxy, Host, VSS, and EMCRecoverPoint Features to be installed for x86. All values must be specified. ADDLOCAL (x64) Proxy, Host, and VSS Features to be installed for x64. All values must be specified. DORMINST 1 Install Replication Manager. Always set value to 1. DORMINST_VSS 1 Always set value to 1. DORMINST_EXCH {1 0} To install Exchange, set value to 1, otherwise set value to 0. RMCPORT default = 6728 Specify Replication Manager control port. RMDPORT default = 6729 Specify Replication Manager data port. Silent installation of NMM 57

58 Silent Installation of the Software Sample command for silent installation of NMM This section contains sample commands that you can use for silent installation of NMM, PowerSnap, and Replication Manager.! IMPORTANT Silent installation of NMM 2.3 does not install PowerSnap and Replication Manager. Install them separately. Sample 1 This sample command contains all the properties that can be passed from the command line for NMM. These properties are optional. In this sample command: The NMM software is installed in the C:\Legato\nsr directory. A MSI log file NMMinstall11.log is created in %temp%\filename.log directory. A SERVERS file contains the server names server1 and server2. \networker\setup /s /v" /qn /L*v """%temp%\nmminstall11.log """ " / w Note: 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 and / / and w Sample 2 Use these sample commands for installing the PowerSnap and Replication Manager services: All the properties in the samples must be passed from the command line when installing the PowerSnap and Replication Manager services. None of the properties are optional. When the PowerSnap service is installed, the Replication Manager service is also installed. For PowerSnap/Replication Manager silent install for nt86: \networkr\ps\setup.exe /s /v"/qb ALLUSERS=1 VSSREG=0 REBOOT=S RMCPORT=6728 RMDPORT=6729 DORMINST=1 DORMINST_EXCH=0 DORMINST_VSS=1 ADDLOCAL=Proxy,Host,VSS,EMCRecoverPoint"/w For PowerSnap/Replication Manager silent install for ntx64: \networkr\ps\setup.exe /s /v"/qb ALLUSERS=1 VSSREG=0 REBOOT=S RMCPORT=6728 RMDPORT=6729 DORMINST=1 DORMINST_EXCH=0 DORMINST_VSS=1 ADDLOCAL=Proxy,Host,VSS"/w 58 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

59 Silent Installation of the Software Silent removal of NMM In a silent removal of NMM 2.3, first the PowerSnap service and Replication Manager services are removed and then NMM 2.3. Although NMM software is removed, you can 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, ensure that you uninstall NMM 2.3 first and then 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 Note: 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""" /L*v """%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 Note: 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 Silent removal of NMM 59

60 Silent Installation of the Software Upgrading the software To upgrade from NMM 2.2 SP1 or earlier to NMM 2.3 using silent installation and uninstallation: 1. Uninstall the existing version of the NMM software using silent uninstallation process. Silent removal of NMM on page 59 provides details. 2. Install the appropriate version of NetWorker. 3. Install NMM 2.3 using silent installation process. Silent installation of NMM on page 56 provides details. Sample scripts for installation and removal of NMM Table 13 on page 61 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 being that the file extension.cmd is replaced by.log. For example, the log for install_nmm_silent_sample.cmd is named install_nmm_silent_sample.log. These logs can be used to troubleshoot installation problems. The install_nmm_silent_sample.cmd script is used for the silent installation of the NMM 2.3 software. The install_nmm_silent_sample.cmd script is the master script, and executes all the scripts in Table 13 on page 61, except for uninstall_nmm_silent_sample.cmd. The install_nmm_silent_sample.cmd script The install_nmm_silent_sample.cmd script performs the following: 1. Checks if NMM or NetWorker is installed. If either is installed, the script exits. 2. Installs the Microsoft.NET Framework 2.0, if it is not installed. 3. Installs the Microsoft VC80 side-by-side redistributable DLLs. 4. Installs NMM. 5. Installs the PowerSnap and Replication Manager services. 6. Configures the Windows firewall. 60 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

61 Silent Installation of the Software You can modify these sample scripts to provide correct installations for your environment. Table 13 Sample scripts for silent installation Script name install_nmm_silent_sample.cmd uninstall_nmm_silent_sample.cmd NMMInstalled.vbs DotNetInstalled.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. DotNetInst.cmd Installs.NET Framework 2.0. NMMConfigFW.vbs Configures the Windows firewall for NMM. Installing the NMM software using the default installation path The install_nmm_silent_sample.cmd script uses the following command to install NMM, and uses the default installation path and leaves res\server file blank: %~dp0\setup /s /v"/qn /L*v """%temp%\nmminstall.log""" " /w Note: Ensure that there is space between: %~dp0\setup and /s /s and /v"/qn /v"/qn and /L*v /L*v and """%temp%\nmminstall.log""" """%temp%\nmminstall.log""" and " " and /w Installing and removing NMM by using SCCM 2007 Server To install NMM 2.3 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. Installing and removing NMM by using SCCM 2007 Server 61

62 Silent Installation of the Software 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 60 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 computer s 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. 62 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

63 Silent Installation of the Software 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. The Troubleshooting chapter in the EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides more details on troubleshooting. Errors in installation of Replication Manager Most frequently, a problem in the installation is due to errors in the installation of Replication Manager services: 1. Check Add/Remove Programs in Windows Server 2003, or Programs and Features in Windows Server The NMM software, and Replication Manager and PowerSnap services should appear installed. The Replication Manager entry appears as RMagentPS: a. If NMM, PowerSnap service or Replication Manager service is missing, remove all, and then reinstall. Remove the programs in the following order: 1. Replication Manager service 2. PowerSnap service 3. NMM software b. Reinstall. 2. If all the three programs appear to be installed but not running, or you get an error about a service not starting, verify that the services for NMM, PowerSnap, and Replication Manager are running: If any of the services is not running, remove and reinstall all of the programs as described in step a. If irccd.exe is not running, but nsrexecd.exe and nsrpsd.exe are running, then manually install the Replication Manager service from the following directory, networkr\ps\rmc\setup.exe. Using non-english characters in installation path During silent or GUI installation, ensure not to use non-english characters in the installation path because although NetWorker seems to be installed properly, the installation of PowerSnap service and Replication Manager service fail and an error message appears. Troubleshooting the installation 63

64 Silent Installation of the Software 64 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

65 4 Postinstallation Tasks This chapter includes the following sections: Using NMM with a VSS hardware provider Configurations specific to PowerSnap Configurations specific to CLARiiON Configurations specific to Symmetrix Configurations specific to VMware ESX guest environment Changing Replication Manager port settings Configuring NetWorker SharePoint services Configuring Windows firewall settings Configurations specific to Exchange server Configuring a storage node as a dedicated storage node Configuring dedicated web front-end crawling Postinstallation Tasks 65

66 Postinstallation Tasks Using NMM with a VSS hardware provider NMM can use a VSS hardware provider for persistent snapshots or off-host backups. To enable these to work together, use the following processes to configure the hardware array and NMM: Hardware array configuration on page 66 NMM configuration for hardware provider support on page 67 Hardware array configuration Perform the following steps for hardware array configuration: 1. Ensure that you have first reviewed the Supported configurations on page Configure the EMC CLARiiON snapshot or clones, EMC Symmetrix BCV mirrors or snapshots or EMC Celera snapshots, EMC Symmetrix TimeFinder snapshots (vdev), TimeFinder Mirror or TimeFinder clones as required. 3. Verify that the VSS hardware provider is available for use: a. Run vssadmin list providers on the application server. For example: C:\>vssadmin list providers vssadmin Volume Shadow Copy Service administrative command-line tool (C) Copyright Microsoft Corp. Provider name: 'EMC VSS Hardware Provider' Provider type: Hardware Provider Id: {04aaf00b-f ae63-e8ac935a102c} Version: Provider name: 'Microsoft Software Shadow Copy provider 1.0' Provider type: System Provider Id: {b b9f-4925-af80-51abd60b20d5} Version: b. Check if the created snapshot is a hardware snapshot by using the following tools: VSHADOW.exe in Windows Server 2003 DISKSHADOW.exe in Windows Server 2008 R2 For example: DISKSHADOW> list shadows all Querying all shadow copies on the computer... * Shadow copy ID = {162cd9f3-408b-42e bb39cbc18720} <No Alias> - Shadow copy set: {cc70c024-9f4e-4d8c-b6e4-f524d48dc067} <No Alias> - Original count of shadow copies = 1 - Original volume name: \\?\Volume{f0b1dd3b-ccee-11df-a c }\ [G:\] - Creation time: 10/11/ :33:39 PM - Shadow copy device name: \\?\Volume{6afff2c9-d20e-11df-ac51-000c } - Originating machine: RAJWIN2K8X64R2.becp.com - Service machine: RAJWIN2K8X64R2.becp.com - Not exposed - Provider ID: {04aaf00b-f ae63-e8ac935a102c} - Attributes: No_Auto_Release Persistent Hardware No_Writers * Shadow copy ID = {a9fa e-4d ac4ce013} <No Alias> 66 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

67 Postinstallation Tasks - Shadow copy set: {2afdd359-2f85-461b-b5a3-259ec5737db4} <No Alias> - Original count of shadow copies = 1 - Original volume name: \\?\Volume{f0b1dd35-ccee-11df-a c }\ [F:\] - Creation time: 10/13/2010 5:18:31 PM - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2 - Originating machine: RAJWIN2K8X64R2.becp.com - Service machine: RAJWIN2K8X64R2.becp.com - Not exposed - Provider ID: {b b9f-4925-af80-51abd60b20d5} - Attributes: No_Auto_Release Persistent No_Writers Differential Number of shadow copies listed: 2 NMM configuration for hardware provider support To configure NMM for hardware provider support: 1. Ensure that NMM client is installed on the Windows server hosting the application. 2. Configure a 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.! 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 Using NMM with a VSS hardware provider 67

68 Postinstallation Tasks Configurations specific to PowerSnap Review the following sections for configuration information specific to PowerSnap. Adding username for account that is logged in the server If you do not have administrative rights and are running programs, add the username for the account that is logged in to the server: 1. Set the PowerSnap NetWorker security by using NMC (from Configuration > User Groups). 2. Add the following values to the Administrators User Group for the production host and proxy host: user=administrator, host=<fqdn> For example: For production host: user=system,host=bv-clsrv.belred.emc.com For proxy host: user=system,host=qe2.belred.emc.com Running a backup with CLARiiON array LUNs For PowerSnap to run a successful backup with CLARiiON array LUNs, run the following command: naviseccli -h "HOST" -addusersecurity -user "CLARiiON_ARRAY_USER" - password "CLARiiON_ARRAY_USER_PASSWORD" -Scope 0 Configurations specific to CLARiiON The CLARiiON documentation provides information about how to configure CLARiiON storage arrays. Additionally, ensure that the following configuration tasks are performed: 1. This step is required only when CLARiiON FLARE 19 is used Updating the CLARiiON configuration file on page Updating the SYMCFG authorization list on page Updating the Navisphere Privileged Users list on page This step is required only when you are working on a virtual machine Configuring NMM backup settings in a virtual machine on page 71 Running a backup with CLARiiON array LUNs on page 68 provides more information about PowerSnap running a successful backup with CLARiiON array LUNs. Note: Install a licensed version of SnapView software on CLARiiON. 68 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

69 Postinstallation Tasks 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 only uses the first entry. If the clarcnfg file is not current, the first entry may be pointing to a CLARiiON that is no longer connected to the system. Edit the clarcnfg file so that there is only entry, pointing to the current CLARiiON you want to use. CLARiiON SnapView snapshots and clones Ensure that CLARiiON has a licensed version of EMC SnapView software installed. EMC SnapView enables you to create a point-in-time view or multiple views of a logical unit number (LUN). These views or snapshots can be made accessible to another host or simply held as a copy. These snapshots can be used for independent data analysis or backup. A SnapView snapshot is a virtual copy of LUN on a storage system. These snapshots are created instantly and remain frozen unless you write it. 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 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, which provide users point-in-time views of data, clones provide fully populated, point-in-time copies, maximizing 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. Configurations specific to CLARiiON 69

70 Postinstallation Tasks Updating the CLARiiON configuration file To support Replication Manager, edit the CLARiiON configuration file (clarcnfg) with the CLARiiON array name and the IP addresses or DNS hostnames of the two storage processors that exist in each CLARiiON machine. The clarcnfg file is located in the %ProgramFiles%\EMC\SYMAPI\config\clarcnfg directory. Use the following sample configuration file template as a guide when adding values to your CLARiiON configuration file. Obtain the values from the CLARiiON array configuration: ########################################################### # CLARiiON CONFIGURATION FILE TEMPLATE # This CLARiiON configuration file provides network addresses # (hostnames or IP addresses) for the two Storage Processors on # each CLARiiON which can be seen by this host. To load # information about CLARiiON systems, CLARAPI must be able to # communicate with the Navisphere Agent that administers them. # CLARAPI Discovery depends on valid entries in this file. # # CLARiiON Arrayname Storage Processor A Storage Processor B # XXXXXXXXXXXX losat246 losat247 APM Updating 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 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 username gadmin -password rdc4xyz 3. Verify that the SYMCFG authorization list has been updated correctly. For example: %ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization list Hostname Username gadmin gadmin 70 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

71 Postinstallation Tasks Updating the Navisphere Privileged Users list In addition to the information provided in this section, review The EMC Navisphere Manager Administrator s Guide for more information about adding entries to the Privileged Users list. EMC Navisphere is a software that enables the management of CLARiiON storage systems. These configurations are done when setting up CLARiiON and are carried out by the CLARiiON administrator. To create a secure environment: 1. Update the EMC Navisphere Privileged Users list with the DNS hostname or IP address of the CLARiiON storage processors (SPA and SPB). 2. Type values in the Privileged Users list in the following format: system@hostname_spa system@hostname_spb where hostname_spa and hostname_spb are the DNS hostnames or IP addresses of the CLARiiON storage processors. Configuring NMM backup settings in a virtual machine To configure a NMM backup with EMC VSS hardware provider for CLARiiON LUNs: 1. Install VSS Provider version Select complete installation and provide the required license. 2. Install NaviAgent, NaviCLI, and ADAM snap. Provide the required authorization to the Windows client. Note: The NaviAgent and NaviCLI versions must be the same as the CLARiiON storage flare version assigned to ESX host system. 3. Add NaviSecCli.exe as the installation path in System Variables Path entry. For example: C:\Program Files\EMC\Navisphere CLI\NaviSECCli.exe 4. 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 , username clariion and password clarpass, type: symcfg authorization add -host username clariion -password clarpass It is important to add the authorization for each of the CLARiiON storage processors. 5. Add NaviSECCli security credentials on ESX guest virtual machine. For example, to add NaviSECCli security credentials for a CLARiiON storage processor with IP address , username clariion and password clarpass, type: NaviSECCli -user clariion -Scope 0 -address AddUserSecurity Configurations specific to CLARiiON 71

72 Postinstallation Tasks Provide password when prompted. It is necessary to add NaviSECCli security credentials for each of the CLARiiON storage processors. 6. For SnapView clone configuration, create CLARiiON clone by using CLARiiON Navisphere Management user interface. 7. Restart the ESX guest virtual machine. This is required to save the environment variables settings that are added during the installation. Configurations specific to Symmetrix The following sections describe how to set up Symmetrix array for data protection. Before you begin, determine the Symmetrix technology that you will be using for data protection and the number of persistent snapshots that will be required. The primary options are: TimeFinder/Mirror, based on Symmetrix BCVs Symmetrix BCVs are appropriate for data protection scenarios where you want to retain the snapshot as a backup copy for a full volume restore or rollback. TimeFinder/Clone, based on Symmetrix BCVs Symmetrix BCVs are appropriate for data protection scenarios where you want to retain the snapshot as a backup copy for a full volume restore or rollback. TimeFinder/Snap, based on Symmetrix VDEVs Symmetrix VDEVs are appropriate for temporary snapshot data protection scenarios where the snapshot is only used to create the backup copy to disk or tape and then deleted. The initialization of Symmetrix for these technologies is quite different. For the following discussion, it is assumed that Symmetrix volumes 8B and 8C are being backed up by using BCVs and Symmetrix volumes 7D and 7E, which are being backed up with VDEVs. Further, it is assumed that two snapshots a day are going to be created. Note: If both BCVs and VDEVs are available for use with an STD, then the prioritization of the backup being a Copy-On-Write copy (snapshot) or a full copy (BCV) is made by the EMC VSS Provider. Setting up the TimeFinder/Mirror (BCV) configuration for Symmetrix The TimeFinder/Mirror technology is a full copy technology where a Business Continuance Volume (BCV) is mirrored or established to a production volume, referred to as a STandard Device (STD). While being established, the BCV synchronizes with the STD and once fully synchronized any new writes to the STD are copied to the BCV as well. When the BCV is disconnected from the STD, also know as split, it becomes a point-in-time copy of the STD. The relationship between a BCV and a STD can be thought of as permanent until the BCV is mirrored to a different STD. Once fully synchronized and split, the Symmetrix tracks change to either the STD and BCV. When the two are reestablished, the tracks that were changed on STD are copied to the BCV. Any tracks that have changed on the BCV is refreshed from the STD so that the BCV is once again a full mirror of the STD. Preparation of TimeFinder/Mirror for use with a proxy consists of the establishing one or more BCVs to the production volume (STD) and waiting for them to become synchronized. 72 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

73 Postinstallation Tasks Note: If more than two BCVs are required then the first BCVs will need to be split after they have become synchronized in order to allow new BCVs to be synchronized. Solutions Enabler's SYMCLI is used to do this work. The SYMCLI is very flexible and in many cases there is more than one way to accomplish a given task. The procedures described in this section reflect the simplest steps whenever possible. In the example, the BCV volumes are B6, B7, B8 and B9. The example establishes B6 and B7 to volume 8B, and B8 and B9 to volume 8C. Setting up the device group and establishing mirrors with BCVs on Symmetrix This section contains instructions for setting up the device group and establishing mirrors with BCVs on Symmetrix. A device group is a SYMCLI object created on hosts. It is a logical grouping of production volumes (STDs) and copy volumes (BCVs, VDEVs, and so on). For all other options, use the -help option with any SYMCLI command. The EMC Solutions Enabler Symmetrix CLI Version 6.3 Quick Reference or EMC Solutions Enabler Symmetrix TimeFinder Family CLI Version 6.3 Product Guide provides more information about using the -help option. To set up the device group, complete the following tasks: 1. Create a device group. To create a device group, use the following command: symdg create device_groupname For example: symdg create mgrp 2. Add devices to the device group. The STDs is assigned a logical name based on the order in which they are entered. To add a STD device to the device group, use the following command: symld -sid Symm_ID -g group add dev Symm_STD_device For example: symld -sid 829 -g mgrp add dev 8b symld -sid 829 -g mgrp add dev 8c The Symmetrix ID is typically the last digits of Symmetrix's serial number to make it unique if there is more than one Symmetrix that can be seen by the host. After the STD device is added, to add a BCV to the device group, use the following command: symbcv -g device_groupname -sid Symm_id add dev Symm_BCV_devicename For example: symbcv -sid 829 -g mgrp add dev b6 symbcv -sid 829 -g mgrp add dev b7 symbcv -sid 829 -g mgrp add dev b8 symbcv -sid 829 -g mgrp add dev b9 3. Verify the group. To check what is in a group, use the following command: symdg show group name Configurations specific to Symmetrix 73

74 Postinstallation Tasks For example: symdg show mgrp Figure 5 on page 74 displays the output. 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 For example: symmir -g mgrp attach 8b bcv dev b6 5. Perform the initial device establish. For the initial establish of the STDs to their partner BCVs, use the following command: symmir -g device_groupname establish STD_logical_device bcv ld BCV_logical_device 74 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

75 Postinstallation Tasks For example: symmir -g mgrp establish DEV001 bcv ld BCV001 -full symmir -g mgrp establish DEV001 bcv ld BCV002 -full symmir -g mgrp establish DEV002 bcv ld BCV003 -full symmir -g mgrp establish DEV002 bcv ld BCV004 -full 6. 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 on page 75 displays the output. 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 -g mgrp split DEV001 bcv ld BCV001 symmir -g mgrp split DEV001 bcv ld BCV002 symmir -g mgrp split DEV002 bcv ld BCV003 symmir -g mgrp split DEV002 bcv ld BCV004 At this point, another pair of BCVs can be established to the STDs and synchronized. 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. Configurations specific to Symmetrix 75

76 Postinstallation Tasks Figure 7 on page 76 displays the output. 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. What happens is that when a backup is requested the EMC VSS Provider establishes BCV to each of the production volumes. When the BCVs are synchronized the EMC VSS Provider then splits them and the actual backup starts.! 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 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 check the registry entry before TimeFinder Mirror backup. The backup will fail if above entry is True when performing TimeFinder Mirror backups. 76 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

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

78 Postinstallation Tasks 3. Add devices to the device group. Next add the STDs to the device group. The STDs will be assigned a logical name based on the order in which they are entered. To add a device to the device group, use the following command: symld -sid Symm_ID> -g group add dev Symm_device For example: symld -sid 829 -g sgrp add dev 7d symld -sid 829 -g sgrp add dev 7e The Symmetrix ID is typically enough last digits of Symmetrix's serial number to make it unique if there is more than one Symmetrix that can be seen by the host. After the STD volumes are added, to add the VDEV devices, use the following command: symld -sid Symm_ID -g group add dev Symm_device -vdev For example: symld -sid 829 -g sgrp add dev df -vdev symld -sid 829 -g sgrp add dev e0 -vdev symld -sid 829 -g sgrp add dev e1 -vdev symld -sid 829 -g sgrp add dev e2 -vdev 4. Verify the group. To check what is in a group, use the following command: symdg show groupname For example: symdg show sgrp 78 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

79 Postinstallation Tasks Figure 8 on page 79 displays the output. 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 For example: symsnap -g sgrp create -svp DEFAULT_POOL DEV001 vdev ld VDEV001 -nop symsnap -g sgrp create -svp DEFAULT_POOL DEV001 vdev ld VDEV002 -nop symsnap -g sgrp create -svp DEFAULT_POOL DEV002 vdev ld VDEV003 -nop symsnap -g sgrp create -svp DEFAULT_POOL DEV002 vdev ld VDEV004 -nop 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 Configurations specific to Symmetrix 79

80 Postinstallation Tasks Figure 9 on page 80 displays the output. 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 80 displays the output. Figure 10 Output of running the snapshot query command again 80 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

81 Postinstallation Tasks b. The second command is a similar view, but is done by pool. Note that this command displays all the sessions that are using SDEVs in the pool, and not just the ones that are yours: symsnap -svp pool list For example: symsnap -svp DEFAULT_POOL list Figure 11 on page 81 displays the output. Figure 11 Output of second command of running the snapshot query again 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. The backup will fail if above entry is True when performing TimeFinder Snap backups. Setting up the TimeFinder/Clone configuration for Symmetrix TimeFinder Clone functionality is available with: NMM 2.3 VSS Provider 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. Configurations specific to Symmetrix 81

82 Postinstallation Tasks Consider the following during the creation of TimeFinder clone: 1. Use the following command to create TimeFinder clone replications: symclone -g group create -copy -differential source_device sym ld target_device symclone -g group create -precopy -differential source_device sym ld target_device For example: symclone -g CloneGrp create -copy -differential SRC sym ld TGT symclone -gclonegrp 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), recreate is not performed and create snapshot fails. After installing the VSS Provider, add or modify the following registry key under HKLM\Software\EMC\ShadowCopy: RetainCloneSession = TRUE DefaultToClone = TRUE NMM does not check the registry entry before TimeFinder Mirror backup. The backup will fail if above entry is False when performing TimeFinder Clone backups. Configurations specific to VMware ESX guest environment The following sections provide information about: Prerequisites on page 82 Configuring NMM backups with EMC VSS hardware providers for CLARiiON LUNs on page 83 Configuring NMM backups with EMC VSS hardware providers backups for Symmetrix LUNs on page 84 Configuring data mover between the ESX guest virtual machine and a physical windows host on page 84 Prerequisites Review the following prerequisites before starting the configuration: Ensure that you have SSH enabled on ESX server system. The VMware KnowledgeBase article Enabling root SSH login on an ESX host provides details about how to enable SSH on VMware host. This article can be found at: d=displaykc&externalid= Latest windows service pack updates must be applied on all NMM clients. 82 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

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

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

85 Postinstallation Tasks 3. For Symmetrix, pair standard from the production client with the BCV from the proxy client. 4. In application information window of the production client, type the following: NSR_DATA_MOVER = proxy.domain.com 5. Perform the following command on both the production client and proxy client: vicfg setup [-u username -p password -s esx_network_address [-force]] 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 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 Changing Replication Manager port settings 85

86 Postinstallation Tasks Configuring NetWorker SharePoint services During NMM installation, the NetWorker SharePoint Service Configuration dialog box appears. You can do the following tasks: Matching NetWorker SharePoint Service credentials with credentials of SharePoint Server administrator on page 86 Specifying temporary storage location on page 86 Specifying the restore lock type on page 87 Updating SharePoint credentials on page 87 Matching NetWorker SharePoint Service credentials with credentials of SharePoint Server administrator The NetWorker SharePoint Service credentials specified in the NetWorker SharePoint Service Configuration dialog box must match the user and password credentials used for SharePoint Server administration. If proper credentials are not specified, then backup of SharePoint data fails. The NetWorker SharePoint Service Configuration dialog box provides fields to specify the Domain, User Name, and Password for SharePoint Service credentials. If you do not fill in the fields to specify the same credentials as those of the SharePoint Server administrator, backup of SharePoint data fails with a Windows E_ACCESSDENIED error. Test NetWorker SharePoint credentials If you have already completed installation and want to test whether your credentials are correct, you can run the following commands at the command line on the SharePoint machine: nsr_moss_save.exe f nsr_moss_save.exe w nsr_moss_save.exe w web application name nsr_moss_save.exe u site collection URL If no error messages appear, your credentials are probably specified correctly. But if you get error messages or failures with SharePoint backups, you can update the NetWorker SharePoint Service credentials. Specifying temporary storage location You can browse and select the temporary storage location in the NetWorker SharePoint Service Configuration dialog box. The temporary storage location is a temporary staging area and is reclaimed after recovery. This area is used to: Temporarily store the backup data going to the NetWorker Server during backup. Temporarily store the data coming from the NetWorker Server during restore. Sharepoint service picks the data from this area and updates the Sharepoint databases. 86 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

87 Postinstallation Tasks Specifying the restore lock type You can specify the restore lock type in the NetWorker SharePoint Service Configuration dialog box. The options are: Read unlocked/write unlocked Read unlocked/write locked Read locked/write unlocked Read locked/write locked After restore, depending on the option selected, the read/write locks are enabled for restored site collections. The option specified here is used as the default setting throughout. However, the option can be changed from the NMM GUI by using the Recovery Options tab just before restore. The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides details about the Recovery Options tab. Updating SharePoint credentials To view the NetWorker SharePoint Service Configuration dialog box after the installation is complete, type the following command at the command line: C:\Program Files\Legato\nsr\bin\nwmossinst.exe The NetWorker SharePoint Service Configuration dialog box appears. To update or correct SharePoint credentials by using the NetWorker SharePoint Service Configuration dialog box: 1. In the Domain\User Name field, specify the domain and username. Note: Use the Sharepoint Server administrator account details. 2. In Password and Confirm Password, specify the password. 3. Click OK to save your changes. Configuring Windows firewall settings NMM automatically configures Windows firewall settings during installation. There is no need to run the Security Configuration Wizard to create firewall exceptions for the NMM client. The previous version of NMM, NetWorker VSS client, required running the SCW, and then saving the SCW settings to the configuration file NetWorkerEXT.xml, which is no longer needed. NMM settings can also be modified after installation: 1. Click Start > Control Panel > Add or Remove Programs. 2. Select NetWorker Module for Microsoft Applications, and then click Change. Configuring Windows firewall settings 87

88 Postinstallation Tasks 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. 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. 88 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

89 Postinstallation Tasks Configurations specific to Exchange server You must first install Exchange and then NMM. If you have installed Exchange server 2003, 2007, or 2010 after installing NMM, then ensure that NMM is reinstalled. During the NMM installation, add Exchange credentials. The following sections provides information about configurations related to Exchange Server 2003, 2007, and 2010: Updating and modifying Exchange credentials on page 89 Setting up Exchange permissions for user accounts on page 90 Configuring IIS settings on Exchange 2010 Mailbox Server before performing backup on page 91 Updating and modifying Exchange credentials Exchange credentials are configured during NMM installation. So, ensure that you install Exchange and then NMM. However, if you have installed Exchange Server 2003, 2007, or 2010 after installing NMM, ensure that NMM is reinstalled and the Exchange credentials are added during the NMM installation. Usually, you will have a specific account for running Exchange Services. If Exchange Server is installed after NMM is installed, or if the Exchange credentials have changed, NMM must be updated with the new credential information. The nwexinfo utility is used to update Exchange Server credentials. When NMM is installed on Exchange Server 2003, 2007, or 2010, the utility runs as part of the NMM installation. This utility updates the NMM software with the Exchange username, password, and domain. Note: When installing NMM or when running the nwexinfo utility, type the correct credentials. Otherwise, backup of client resource fails, even when the backup does not include Exchange data. To run the utility, double-click nwexinfo.exe from the %ProgramFiles%\Legato\nsr\bin directory. Run the utility again if: The Exchange Server is installed after NMM is installed. The username, password, or domain changes after NMM is installed. However, for changes made in Exchange Server 2007 and 2010, the username and account information must also be updated in: The Replication Manager-supplied Exchange 2007 or 2010 Service, RM_ExchangeInterface, for NMM. The COM registration associated with RM_ExchangeInterface. Configurations specific to Exchange server 89

90 Postinstallation Tasks Use the following procedure to change the user account, account information, and password information: 1. Start component services. 2. Expand 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. Modify either the domain user account or password, or both and click OK. Setting up Exchange permissions for user accounts Perform the following steps to set up the Exchange permissions for user accounts: Setting up Exchange permissions for Exchange 2010: a. Perform the steps outlined in the first two bullets below, or alternatively perform the step in the third bullet: On Exchange 2010 stand-alone servers: Domain user account with the Databases role: New-ManagementRoleAssignment -Role "Databases" -User <user account> On Exchange 2010 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> or The customer can add the user to the Server Manager group instead of adding the Roles. b. On Exchange 2010 mount hosts, provide a Domain user account that is a member of the local Administrators group. Setting up Exchange permissions for Exchange 2007 During installation with Exchange 2007, you need to specify credentials for domain account that is both a member of the local Administrators group and the Exchange Server Administrator role. Setting up Exchange permissions for Exchange 2003 During application set creation with Exchange 2003, you need to specify a domain account with local Administrator rights and Exchange Full Administrator privileges. Note: The Exchange view-only administrator permission provides read-only access to the Exchange organization. It is possible to see the contents and settings of an Exchange organization, but not modify them. 90 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

91 Postinstallation Tasks Configuring IIS settings on Exchange 2010 Mailbox Server before performing backup Before performing Exchange 2010 Mailbox Server backup, ensure that Windows Authentication is enabled and the Kernel Mode Authentication check is cleared. This should be done for both the Mailbox Server that is standalone or part of Database Availability Group (DAG). If the IIS setting is not configured, Exchange 2010 backup fails with COM error. Perform the following steps: 1. Go to IIS Manager > Your Host > Sites > Default Web Site > Powershell. 2. Double-click Authentication and enable Windows Authentication. 3. On Windows Authentication, right -click and ensure that the Kernel Mode Authentication option is clear. Configuring a storage node as a dedicated storage node To configure a storage node as a dedicated storage node: 1. Install NetWorker 7.5 SP3, 7.6 SP1, or later as a storage node. The latest copy of the EMC NetWorker Release 7.6 SP1 Installation Guide provides information about installing the NetWorker storage node. 2. Install NMM 2.3. Installing NMM on page 46 provides information about installing NMM. Note: Ensure that you install NetWorker 7.5 SP3, 7.6 SP1, or later as a storage node before installing the NMM Create a remote backup device on the NetWorker server. The latest copy of the EMC NetWorker Release 7.6 SP1 Administration Guide provides information about creating a remote backup device. 4. Set the Dedicated Storage Node attribute. The latest copy of the EMC NetWorker Release 7.6 SP1 Administration Guide provides information about configuring the dedicated storage node. In NetWorker 7.0 and later, all the devices remote to the server, created on storage nodes include the Dedicated Storage Node attribute. You can set this attribute to one of the following values, while creating devices on a storage node: Yes Requires a dedicated storage node license. Setting this attribute makes the storage node a dedicated storage node. No Requires a standard storage node license. Note: For Exchange 2010, do not use the No option. Configuring a storage node as a dedicated storage node 91

92 Postinstallation Tasks 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. 3. Once the configuration is complete, a new host file is created by SharePoint Central Administration. 4. Append the host file information from backed-up host file to the new host file. 5. Configure NMM backup. 92 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide

93 Index Symbols %TEMP% directory 60 A Advertisement Status section 62 B BCVs 73 C checklist for CLARiiON 30 checklist for Exchange 36 checklist for SharePoint 35 checklist for SQL 34 checklist for Symmetrix 32 CLARiiON array configuration 70 CLARiiON configuration file 70 Commands for silent installation of NMM 56 create device group 73 D dedicated storage node 91 device group 73 E establishing mirrors 73 Exchange server 89 G generic checklist 27 H -help option 73 hotfixes required for NMM I install_nmm_silent_sample.cmd 60 installation scripts 61 installation status log files 62 irccd.exe 63 M Microsoft System Center Configuration Manager 2007 server 61 N NMC 68 nsrexecd.exe 63 nsrpsd.exe 63 nwexinfo.exe utility 89 P Powersnap and RM command line properties 57 PowerSnap NetWorker security 68 preinstallation checklists 26 production host 68 proxy host 68 R Replication Manager port settings 85 rmagentps service 85 S sample configuration file 70 stand-alone method 56 SYMCLI 73 T troubleshooting installation problems 60 U uninstall_nmm_silent_sample.cmd 62 W web front-end crawling 92 Windows E_ACCESSDENIED error 86 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide 93

94 Index 94 EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide