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: BSGdocumentation@emc.com If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject that you are addressing. 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