TECHNICAL NOTES. Technical Notes P/N REV 01

Transcription

1 TECHNICAL NOTES EMC NetWorker Module for Microsoft Applications and EMC CLARiiON : Implementing Proxy Node Backups Release 2.4 SP1 Technical Notes P/N REV 01 January 30, 2013 These technical notes contain supplemental information about using EMC NetWorker Module for Microsoft Applications Release 2.4 Service Pack 1 (SP1) with EMC CLARiiON. Topics include: Revision history... 2 Introduction... 3 Advantages of using a proxy client... 3 Operating system and application version information... 4 Examples of configurations using proxy client... 5 Required installations and configurations... 9 Configuring NMM in a VMware ESX guest environment Configuring backups Recovering data Troubleshooting Related documents Troubleshooting and getting help... 29

2 Revision history Revision history Table 1 on page 2 presents the revision history of this document: Table 1 Revision history Revision Date Description 01 January 30, 2013 First release of this document for General Availability (GA) release of EMC NetWorker Module for Microsoft Applications Release 2.4 SP1. 2 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

3 Introduction Introduction These technical notes are for use by a technically trained person who must use EMC NetWorker Module for Microsoft Applications (NMM) to back up the supported Microsoft applications using EMC CLARiiON hardware replication technologies to create copies of production volumes. The NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide provides complete details about all NMM features. Details about CLARiiON features and other information can be found in the CLARiiON documentation. It is assumed that anyone using these technical notes will meet the following criteria: Proficiency using a command line interface (CLI) in a Microsoft command window. Familiarity with the EMC Solutions Enabler command set. Familiarity with the basic EMC CLARiiON architecture and advanced storage feature. Understanding of the compromises that must be made in balancing hardware resource limits against a backup plan. Understanding of the NetWorker and NMM software, and their operation. The scope of this document is to provide functional information for configuring hardware-based snapshot backups with NMM when the application is hosted on EMC CLARiiON storage. It is beyond the scope of these technical notes to cover resource creation on the EMC CLARiiON that can be used with NMM. These technical notes assumes that these resources have been created and are ready configured. Advantages of using a proxy client In a simple LAN-based backup configuration, the server that contains the application that is being backed up, also performs the backup, and sends it over the LAN to backup media services. In this process, the application server does all the work of taking the backup and sending it to storage. With most application servers, the functions of backing up the data while the application performs its regular production duties can slow down both functions. The performance of the application server suffers due to sharing the hardware and resources with the backup functions. The backup jobs are also slowed down. Proxy backup, also known as off-host backup, is a technique that reduces the load on production applications while performing data protection operations. Proxy backups are deployed for application servers that use SAN or iscsi-based storage. Additional hosts may be deployed and zoned so that the backups may occur on a second host that accesses a snapshot copy of the production application data. There are several advantages of using a proxy client: Hardware resources such as the processor, memory, and network can be optimized for serving the client or the user application. The hardware resources of the proxy host can be used for backing up the data to the storage node. EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 3

4 Operating system and application version information The backup window can be increased. The impact to the production host is minimized. NMM supports proxy backup as an option for protecting applications. NMM may be deployed in a proxy backup configuration with EMC and selected non-emc storage platforms. Operating system and application version information Table 2 on page 4 summarizes the NMM requirements for each of these systems. Use the requirements listed in Table 2 on page 4 as a guideline only. The NetWorker Software Compatibility Guide contains additional and the most up-to-date information about NMM support for operating systems, applications, and hardware. Table 2 NetWorker, NMM, and storage node requirements (page 1 of 2) Server NetWorker server version Operating system for application server EMC software for application server Application versions Software supported or required 7.6 SP2 or later and 8.0 or later Windows Server 2012 (x64) Windows Server 2008 R2 (x64) Windows Server 2008 SP2 (x86, x64) NMM 2.4 SP1 EMC VSS hardware provider This includes Solution Enabler 7.3. Navisphere Agent and Navisphere CLI. Use the version that is appropriate for the CLARiiON version that you are using. AdmSnap. Use the version that is appropriate for the CLARiiON version that you are using. NMM client supports backup and recovery of the following Microsoft applications and features: Exchange server 2010 SP1 or later (x64) Exchange server 2007 SP3 or later (x64) SQL Server 2012 (x86, x64) SQL Server 2008 R2 SP1 or later (x86, x64) SQL Server 2008 SP2 or later (x86, x64) SQL Server 2005 SP4 or later (x86, x64) SharePoint Portal Server 2013 (x64) SharePoint Portal Server 2010 SP1 or later (x64) SharePoint Server 2007 SP2 or later (x86, x64) SharePoint Foundation 2010 SP1 or later (x64) Windows SharePoint Services 3.0 SP1 Windows Server 2012 with Hyper-V Windows Server 2008 R2 with Hyper-V Windows volumes and system components Windows Cluster support 4 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

5 Examples of configurations using proxy client Table 2 NetWorker, NMM, and storage node requirements (page 2 of 2) Server Proxy backup server in a stand-alone configuration Software supported or required The stand-alone proxy backup server: Operating system requirements are the same as those for the application server operating system. EMC software requirements are the same as those for the application server EMC software. Note: The application server and the proxy client must use the same version of NMM. If NMM 2.4 SP1 is installed on either the application server or the proxy client machine, then the other machine must also use NMM 2.4 SP1. Backup and recovery will fail if NMM 2.4 SP1 is used on one of these machines, and an earlier version of NMM is used on the other. Proxy backup server on a NetWorker Storage Node EMC CLARiiON array The proxy backup server running on a NetWorker storage node requires the following EMC software: NetWorker storage node, including any required options NMM 2.4 SP1 EMC VSS Provider This includes Solution Enabler 7.3. EMC CLARiiON CX3, Flare 26 or later and EMC CLARiiON CX4, Flare 28 or later requires the following: SnapView Clones, or SnapView Snapshots Navisphere Agent and Navisphere CLI. Use the version that is appropriate for the CLARiiON version that you are using. AdmSnap. Use the version that is appropriate for the CLARiiON version that you are using. Examples of configurations using proxy client The VSS snapshot creation process This section provides details on how to deploy NMM in a proxy backup configuration with EMC hardware-based storage, EMC CLARiiON: The VSS snapshot creation process on page 5 Client and server functions on page 7 LAN-based configuration with a proxy client on page 7 LAN-free configuration with a proxy client on page 8 Microsoft Volume Shadow Copy Service (VSS) acts as a coordinator among the following three components that create, modify, back up, and recover data: VSS requestors Requestors include backup applications such as NMM. VSS writers Includes writers for operating system data, application databases such as Exchange server or SQL server, and file system volumes such as a D:\ data drive. NMM uses these writers to determine the right type of data to backup on the application server. Microsoft application data is specific to only Microsoft application databases. EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 5

6 Examples of configurations using proxy client VSS providers Providers include the VSS software provider such as Software Shadow Copy Provider or hardware-based providers such as the EMC VSS Provider. In these technical notes, the VSS Provider is used for hardware-based snapshots of EMC CLARiiON. In VSS, NMM is a requestor, which is an application that performs the backup and recovery of applications or services. When NMM performs a backup or recovery, the following occurs: 1. NMM asks VSS to enumerate the writers, and to gather their metadata. 2. The writer provides an XML description of the backup components and then defines the restore method. 3. VSS asks which provider can support a shadow copy for each required volume. 4. NMM asks VSS to create the shadow copies. 5. Each application and service that supports VSS has its own writer, which understands how the application or service works. After the writer signals that it has prepared the data, the following occurs: 1. The VSS software freezes the writers: a. It directs the writer to freeze input/output (I/O) to the selected volumes. b. Queues transactions for later processing. c. Calls a provider to capture the requested data. 2. VSS tells the provider to create the shadow copy of the current state on-disk. 3. The provider does the following: a. Captures the prepared data. b. Creates a snapshot that exists side-by-side with the live volume. 4. After the snapshot is created, VSS thaws the writers: a. The provider signals VSS, this signal tells the writer to resume activity. b. I/O is released to the selected volumes and any queued writes that arrived during the provider's work are processed. 6 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

7 Examples of configurations using proxy client Client and server functions Table 3 on page 7 describes the main client and server functions when using NMM with a proxy client and storage hardware. Table 3 Systems and functions System NetWorker Application server Proxy backup server Storage platform Function Initiates the backup process by contacting the application server. Contains the Microsoft application that is being backed up by NMM, such as Exchange Server, SQL Server, and SharePoint Server. The NMM client is installed. The EMC hardware provider for CLARiiON is installed. Acts as a remote data mover when snapshots are rolled over to storage. Can be a stand-alone Windows server running NMM, or a NetWorker Storage Node with NMM. The EMC hardware provider for CLARiiON is installed. Stores the snapshot created by the NMM client on the application server. In these technical notes, the EMC hardware provider for CLARiiON is installed on the proxy backup server and the application server. The EMC VSS hardware provider is used with an EMC CLARiiON array. LAN-based configuration with a proxy client Figure 1 on page 7 shows a LAN-based configuration with a storage area network and a proxy client. Both the application server and the proxy client have NMM installed. NetWorker Server LAN Application server NMM Proxy client NMM SAN Primary storage (For example, CLARiiON or Symmetrix) S5 S1 S4 S3 S2 NetWorker Storage Node Traditional storage GEN Figure 1 LAN-based configuration with a proxy client EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 7

8 Examples of configurations using proxy client 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 with the NMM software creates a snapshot of the data on the storage volume. In Figure 1 on page 7, snapshots are represented by S1 through S5. 3. The snapshot becomes visible to the proxy client. LAN-free configuration with a proxy client 4. The proxy client uses a snapshot in primary storage to transfer the data over the LAN and into traditional storage such as a file type disk, advanced file type disk, or tape. Figure 2 on page 8 shows a LAN-free configuration with a storage area network. The NMM software is installed on the application server. The proxy client is installed on the NetWorker storage node. NetWorker server LAN Application server NMM Proxy client NetWorker storage node SAN Primary storage (For example, CLARiiON or Symmetrix) S5 S1 S4 S3 S2 Traditional storage GEN Figure 2 LAN-free configuration with a proxy client You can set up the following NetWorker storage node 7.6 SP2 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. 8 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

9 Required installations and configurations Install the proxy client software by using the NMM software package. Configuring proxy node or proxy storage for use with a CLARiiON array on page 23 provides detailed steps for configuring the proxy client and NetWorker server. 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 with the NMM software creates a snapshot of the data on the storage volume. In Figure 2 on page 8, snapshots are represented by S1 through S5. 3. The snapshot is made visible to the proxy client. 4. The proxy client, which in this case is also 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, 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. Required installations and configurations The following tasks provide a high-level installation and configuration roadmap of NMM and EMC CLARiiON. Configuration checklist for CLARiiON systems on page 9 Provisioning CLARiiON storage for data protection on page 15 Installing the NMM software on page 18 Configuring NMM for a VSS hardware provider on page 19 Configuring NMM for CLARiiON on page 20 Configuration checklist for CLARiiON systems You must have already configured the CLARiiON storage for application data for the application host. This section provides a configuration checklist to ensure proper configuration of CLARiiON systems for NMM: Checking the setup configuration on page 11 Creating a storage array descriptor file on page 11 Installing EMC storage software on page 12 Software required to enable EMC VSS hardware provider for CLARiiON on page 12 Setting the NaviCli path on page 13 Configuring Navisphere security on page 13 Configuring SYMCLI security on page 13 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 9

10 Required installations and configurations Creating the MSDTC resource on page 14 Validating Solutions Enabler connectivity on page 14 Verifying that the EMC VSS Provider is registered on page EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

11 Required installations and configurations Checking the setup configuration The following prerequisites and configurations are required for CLARiiON setup: Ensure that the storage processor ports for production data are zoned to the Windows production machine. At least one port per storage processor should be zoned. When assigning LUNs to a Windows machine, ensure both storage processors, SPa and SPb are presented, visible to the SCSI bus on the system, to the Windows machine using CLARiiON storage groups. Otherwise, backups may fail with a configuration error. Verify that both the production host and the proxy host can access the same CLARiiON. They cannot be in the same storage group. For the proxy mount host, ensure that at least one LUN from each CLARiiON, if multiple are used, is permanently zoned to the Windows machine. This is required for reliable import/deport of snapshots. Complete the following tasks on both the production and proxy machines: Creating a storage array descriptor file Download and install the latest drivers from the OEM hardware manufacturer. Consult EMCE-Labs for the latest recommendations. Download and install Windows hotfixes. Consult the NetWorker Software Compatibility Guide and EMC E-Labs for the latest recommendations. A storage array descriptor file, sa.ini, contains information about the storage arrays connected to the proxy client Data Mover. The sa.ini file is created with the nsr_sa_ini.exe utility and placed in the nsr\res directory on the NMM client host. nsr_sa_ini.exe prompts you for information about the storage arrays connected to the proxy client. You must provide an array username and password. When you complete the entries for a CLARiiON sa.ini file, the password string is encrypted when you save the file. A sample sa.ini file for a CLARiiON storage array would look similar to the following: [Storage_Array] Storage_Array_Count=2 Storage_Array_1=APM [APM ] Array_Type=CLARiiON Array_model=CX500 Array_user=sbarma Array_pass=**** Array_pass_confirm=**** Array_SPA= Array_SPB= To create a storage array descriptor file: 1. At the command line, type: nsr_sa_ini.exe 2. Follow the prompts to provide the array information. EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 11

12 Required installations and configurations IMPORTANT Even though the utility appears to allow you to type credentials for more than one storage array, only the first one will be used by NMM. You must create a separate sa.ini for each storage array. When you have completed typing the array information, the file is saved to the nsr\res directory on the NMM client host. Do not edit the sa.ini file with a text editor to make changes in the array parameters. Using a text editor can corrupt the file, or compromise the password entries. Use the nsr_sa_ini.exe tool to edit the sa.ini file if you need to make changes after you create it. Installing EMC storage software The Windows VSS System Provider is a host-based provider that works with any type of storage hardware. Proxy node backups require the use of VSS hardware providers which allow transporting application server snapshots to a proxy node for backup. For example, the EMC VSS Provider supports EMC CLARiiON disk arrays. NMM supports multiple VSS hardware providers. Software required to enable EMC VSS hardware provider for CLARiiON Install the EMC software on both the application host and proxy host as listed in Table 4 on page 12. Table 4 EMC software on application and production hosts Software EMC VSS Provider This includes Solution Enabler. Navisphere Agent Navisphere CLI Admsnap NMM 2.4 SP1 client Default location C:\Program Files\EMC C:\Program Files (x86)\emc\navisphere Agent C:\Program Files (x86)\emc\navisphere CLI C:\Program Files (x86)\emc\navisphere Admsnap C:\Program Files\Legato\ To configure the EMC VSS hardware provider on Windows, you must install the following software on the client machine: EMC VSS hardware provider with Solutions Enabler IMPORTANT Install the most recent VSS patches and hotfixes from Microsoft. AdmSnap NaviSuite 12 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

13 Required installations and configurations Setting the NaviCli path Complete this task on both the production and proxy machines. To set the NaviCli path: 1. In Windows, select Start > My Computer > Properties > Advanced > Environment Variables > System variables > Path. 2. Add the Navi installation path to the PATH variable. For example, if NaviCli was installed in C:\Program Files (x86)\emc\navisphere CLI, add this to the path. During installation, you can use an option in the Navicli software installation wizard to automatically set the NaviCli path. Configuring Navisphere security Configuring SYMCLI security Complete this tasks on both the production and proxy machines. 1. If Flare 24 or later is used, run the navseccli command: C:\Program Files\EMC\Navisphere CLI >NaviSECCli -user username -Scope 0 -address CLARiiON_IP -AddUserSecurity 2. After running this command, a prompt appears for the password. Use the CLARiiON password. 3. Run the navseccli command with the second CLARiiON IP. 4. When prompted, provide the CLARiiON password for the second CLARiiON IP. 5. After running this command, a prompt appears for the password. Use the CLARiiON password. Complete this task on both the production and proxy machines. 1. Configure SYMCLI Security to enable the Solutions Enabler software to communicate with Navisphere on the CLARiiON. 2. Update the SYMCFG Authorization list. Run the following once for each storage processor: C:\Program Files\EMC\SYMCLI\bin>symcfg authorization add -host Clarion_IP -user clarion_username -password Clarion_password 3. Verify the symcfg authorization. Run the following: C:\Program Files\EMC\SYMCLI\bin>symcfg auth list The list should display as follows: Hostname Username Namespace Port user user EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 13

14 Required installations and configurations Creating the MSDTC resource Validating Solutions Enabler connectivity Complete this task on the production machine. When installing the NMM software in a Microsoft Cluster Server (MSCS) environment, if you plan to use CLARiiON with EMC VSS hardware provider: 1. Ensure that the 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. 2. Ensure that MSDTC is running. The Solutions Enabler requires that MSDTC be running. The EMC Solutions Enabler Installation Guide on EMC Online Support ( provides details about installing and running Solutions Enabler. Complete this task on both the production and proxy machines. Perform the following to validate connectivity: 1. Run the following command to determine if the configuration is successful: symcfg discover -clariion Note: This task should be done on both the application and proxy nodes. 2. Resolve a mounted CLARiiON file system. The following is a sample command: symrslv fs M:\ClariionLUN M:\ContentDB10>symrslv fs data Absolute Path : M:\CONTENTDB10\DATA\ Resolved Object Type : File System Resolved Object Size : m Number of Trailing Bytes : 0 Extent byte offset to data : 0 Number of Physical Devices : 1 File System Mount Point : M:\CONTENTDB10\DATA\ File System Device Name : \\.\PHYSICALDRIVE13 Number of Mirrors for object (1):{ 1) Mirror Name :Mirror Physical Extents (1):{ Size Array Dev Offset PPdevName Offset Attr m k Volume{d85191d d* 0b (C) } Mirror Physical Devices (1): { Array Dev PPdevName PdevName Attributes \\?\Volume{d85191d1-52* \\.\PHYSICALDRIVE13(C)} } Legend for the Attribute of Devices: (C): CLARiiON Device. (S): Symmetrix Device. (M): Symmetrix Device Meta Head. (m): Symmetrix Device Meta member. 14 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

15 Required installations and configurations Verifying that the EMC VSS Provider is registered Complete this task on both the production and proxy machines: 1. After installing Solution Enabler: a. Ensure that the hardware provider is registered and installed as a service. b. Check the list of services for the EMC VSS Provider service. 2. To verify that the hardware is registered, at the command line, type: C:\>vssadmin list providers This command displays information similar to the following: 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: The Microsoft Software Shadow Copy provider will be registered by default when the operating system is installed. Provisioning CLARiiON storage for data protection The following sections describe how to provision CLARiiON storage for data protection. Before you begin: Determine what CLARiiON technology will be used for data protection. Determine how many persistent snapshots are required. The options are CLARiiON SnapView clones and CLARiiON SnapView snapshots: CLARiiON SnapView clones are appropriate for data protection scenarios where you want to retain the snapshot as a backup copy that may be used to restore. CLARiiON SnapView snapshots 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 determination of the backup being a snapshot or clone, is based on the SnapView configuration of source LUNs: If the source LUNs are configured with SnapView clones, then the backup is done for clones. Setting up SnapView clone configuration in CLARiiON on page 16 provides more information. If the SnapView snapshots are configured, then the VSS Provider uses SnapView snapshot. Setting up SnapView snapshot configuration in CLARiiON on page 18 provides more information. EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 15

16 Required installations and configurations Setting up SnapView clone configuration in CLARiiON EMC CLARiiON uses split mirror, one of the technology options available to perform snapshot-based data protection. It is implemented through EMC CLARiiON SnapView clones by having every write request to the original data automatically duplicated to other mirrors or copies of that data. This mirror is redundant and is not a frozen image or snapshot. Mirrors create a snapshot of the data with the split capability. Note: SnapView clones are acceptable for both temporary snapshots, and backup to disk or tape. To set up SnapView clone configuration: 1. Create the SnapView clone group for the source LUN. The source LUN should correspond to one of the LUNs on the application server that contains the data to be protected. Figure 3 on page 16 shows the selections used to create a clone group in EMC Navisphere. Figure 3 Selections to create a clone group 2. Select the target LUN: a. Ensure that the target LUN is the same size as the source disk. b. Add the LUN in the clone group. c. Ensure that the target LUN is empty because data will be lost while adding the target LUN. d. If the target LUN is currently assigned to a CLARiiON storage group, remove the LUN from that CLARiiON storage group as well. 16 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

17 Required installations and configurations Do not add the EMC CLARiiON clone LUN to any storage group as part of the setup procedures. The EMC VSS Provider manages assigning and removing the clone LUNs from EMC CLARiiON storage groups. Do not allocate a clone LUN from the same raid group that contains the clone s source LUN. A clone may impact performance for the source LUN while synchronizing. Performance may also be affected if the source LUN is under heavy use. Performance is restored when the LUNs are fractured. Figure 4 on page 17 shows the selections to add a clone group. Figure 4 Selections to add a clone 3. Select initial synchronization. The clone configuration is ready. The VSS hardware provider release notes for the supported clone LUN states provides details. 4. If your data protection plan requires multiple persistent snapshots, add more clones until the desired number of clones are present for the source LUN. 5. Repeat step 1 to step 4 for each LUN that contains application data. For example, if you are protecting an Exchange storage group with database and log files on two separate LUNs, you must allocate the necessary SnapView clone resources for each LUN. EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 17

18 Required installations and configurations Setting up SnapView snapshot configuration in CLARiiON EMC CLARiiON uses copy on first write as one of the technology options to perform snapshot technology. It is implemented through EMC CLARiiON SnapView snapshots by having every write request to the original data automatically duplicated to LUNS in the CLARiiON reserved LUN pool. Installing the NMM software SnapView snapshots are only acceptable if the VSS snapshots are backed up to disk or tape, and then resyncronized after the backup job completes. If the VSS snapshots are to be persistent then they should be created through SnapView clones. If using CLARiiON snapshots: 1. Ensure that there is sufficient space in the reserved LUN pool. The space of the reserved LUN pool depends on the following: The size of the source LUN. How much data you anticipate will change on the volume after the CLARiiON snapshot is taken and before it is deleted. 2. Before taking the snap: a. Ensure the reserve LUN pool is not full. b. Check in Navisphere that all reserved LUN pools are not allocated. c. When creating the zoning for the host for both the production host and data mover, ensure that the HBA adapter is registered to both processors of CLARiiON SPa and SPb. The NMM client must be installed on several machines: Application host Install the NMM client on the Windows server that hosts the application. Proxy host Install the NMM client on the Windows server that will serve as the proxy mount host. Proxy storage node Install the NMM client on the Windows server that is a NetWorker Storage Node. The following NMM documents provide complete details and steps for installing and configuring the software: The NetWorker Module for Microsoft Applications Release 2.4 SP1 Installation Guide describes the hardware requirements, as well as the installation, licensing, and enabling process. The NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide describes how to configure NMM backups and run recoveries. The procedures are different for each supported Microsoft application and version. Separate sections are provided for Windows System, Active Directory, Exchange Server, SharePoint Server, and SQL Server. 18 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

19 Required installations and configurations Configuring NMM for a VSS hardware provider The NMM software can work with a VSS hardware provider to create persistent snapshots or off-host backups of production data. This requires the following configurations: Configure the VSS hardware array to work with NMM on page 19 Configure NMM to work with the VSS hardware provider on page 19 Configure the VSS hardware array to work with NMM To configure the VSS hardware array to work with NMM software: 1. Plan your network snapshot or off-host backup configuration, as described in the NetWorker Module for Microsoft Applications Release 2.4 SP1 Installation Guide. 2. Configure the CLARiiON SnapView clone or Snapview snapshots 3. Run the vssadmin list providers command on the application server to verify that the VSS hardware provider is available for use. 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: Configure NMM to work with the VSS hardware provider To configure the NMM software for VSS hardware provider support: 1. Ensure that NMM client software is installed on the Windows server that hosts the application. 2. Configure an NMM client scheduled backup as needed for the application: a. Configure a snapshot policy to match the application requirements. b. Configure a backup group that uses the snapshot policy. c. Configure a client resource as required for the application, including NetWorker User Group values. d. Configure a proxy client if required, including NetWorker User Group values. 3. If backups are run in a proxy configuration with a VSS hardware provider that is not an EMC product, set the following environment variable in the NMM proxy host. EMC_ERM_NO_SYMAPI=Yes 4. Test-run the NMM scheduled backup. EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 19

20 Required installations and configurations Configuring NMM for CLARiiON Data gathered by the NMM host may be copied to a CLARiiON storage array with the EMC SnapView software package. SnapView can perform a point-in-time snapshot view, or multiple views, of a logical unit (LUN). For example, a snapshot session may be made of active LUNs on the NMM production host and copied to reserved LUNs on the CLARiiON array for backup or cloning with minimal impact to the production host. To configure the NMM application host for snapshot views on a CLARiiON array: 1. Ensure that a licensed version of SnapView software is installed on the CLARiiON array. 2. On the NMM host, edit the clarcnfg file to ensure that there is only one entry that points to the CLARiiON array you want to use: If there are multiple entries in the clarcnfg file, then Replication Manager uses only the first entry. If the clarcnfg file is not current, the first entry might point to a CLARiiON array that is no longer connected to the system. 3. On the NMM host, use the following commands to add the authorized user to enable PowerSnap to use CLARiiON storage processors A and B: naviseccli -h Storage_Processor_A_IP -addusersecurity -user CLARiiON_USER - password CLARiiON_USER_PASSWORD -Scope 0 naviseccli -h Storage_Processor_B_IP -addusersecurity -user CLARiiON_USER - password CLARiiON_USER_PASSWORD -Scope 0 4. On the NMM host, update the SYMCFG authorization list with the authorized user to enable the VSS provider to use CLARiiON storage processors A and B, identified by their IP addresses, for example: %ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization add -host username gadmin -password rdc4xyz %ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization add -host username gadmin -password rdc4xyz 5. On the NMM host, verify that the SYMCFG authorization list has been correctly updated for the authorized user. For example: %ProgramFiles%\EMC\SYMCLI\bin>symcfg authorization list Hostname Username gadmin gadmin 6. Configure NMM with VSS hardware providers for CLARiiON LUNs on page 21, if required. 20 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

21 Configuring NMM in a VMware ESX guest environment Configuring NMM in a VMware ESX guest environment Requirements The following sections provide configuration information for NMM backups in a VMware ESX guest environment: Requirements on page 21 Configure NMM with VSS hardware providers for CLARiiON LUNs on page 21 Configure a data mover for an ESX guest virtual machine on page 22 Ensure the following requirements are met before you start the configuration: The SSH network protocol must be enabled on the VMware ESX server system. The VMware knowledge base article Enabling root SSH login on an ESX host provides details and is available at The latest Microsoft Windows service pack updates must be installed on all NMM clients. VMware tools must be installed with the complete option on the ESX guest virtual machine. VSS Provider must be installed with the complete option. Configure NMM with VSS hardware providers for CLARiiON LUNs To configure an NMM backup with an EMC VSS hardware provider for CLARiiON logical units (LUNs): 1. Install NaviHost agent on the ESX server host system. The NaviHost agent version must be same as the CLARiiON storage version that runs FLARE assigned to ESX host system. 2. Add LUNs to the NMM client as RAW devices mapped in physical compatibility mode. The virtual compatibility mode is not supported by EMC VSS Provider. 3. Set VICLIENT_DISABLE_CACHE=1 in the system environment variables on the ESX guest virtual machine. 4. Install VSS Provider. Select the complete installation and activate the required license. 5. Install NaviAgent, NaviCLI, and ADAM snap. Provide the required authorization to the Windows client. The NaviAgent and NaviCLI versions must be the same as the CLARiiON storage version that runs FLARE assigned to the ESX host system. 6. Add NaviSecCli.exe to the installation path in the System Variables Path entry. For example: C:\Program Files\EMC EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 21

22 Configuring NMM in a VMware ESX guest environment 7. Authorize Solutions Enabler to access the CLARiiON storage array with 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 Add the authorization for each of the CLARiiON storage processors. 8. Add NaviSECCli security credentials to the 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 the password when prompted. Add the NaviSECCli security credentials for each of the CLARiiON storage processors. 9. Use the 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]] 10. Install the NMM client on the ESX guest virtual machine. 11. Restart the ESX guest virtual machine. Configure a data mover for an ESX guest virtual machine To configure the data mover between the production client (ESX guest virtual machine) and the proxy client (physical Windows host): 1. Ensure that the LUNs for the proxy client are configured from the same array as the production client. 2. Ensure that the hardware providers backup is working for the following clients: Production clients Proxy clients 3. In the Application Information window of the production client, type the following: NSR_DATA_MOVER = proxy.domain.com In standalone data mover setups, ensure not to use both the NSR_VSS_FORCE_SYSTEM_PROVIDER=yes and NSR_DATA_MOVER=clientname.domain.com parameters in the Application Information field, otherwise NMM backup will fail. 22 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

23 Configuring backups Configuring backups 4. Perform the authorization command on both the production client and proxy client: vicfg setup [-u username -p password -s esx_network_address [-force]] This section provides the information required for: Limit the number of snapshots for a volume with the EMC VSS Provider on page 23 Configuring proxy node or proxy storage for use with a CLARiiON array on page 23 Configuring a proxy server and a storage node for use with a CLARiiON array on page 25 Validating the backup on page 27 Limit the number of snapshots for a volume with the EMC VSS Provider You can create a maximum of eight shadow copies for a single LUN on an EMC CLARiiON machine. The VSS framework also limits the number of shadow copies per volume, for example 64. This limit also applies to all VSS providers, including the VSS software provider. Configuring proxy node or proxy storage for use with a CLARiiON array This section describes how to configure a proxy node or a proxy storage backup. The minimum configurations for proxy node and proxy storage node for backups with CLARiiON hardware provider are the same. When performing a hardware backup of a SharePoint Server 2007 farm, ensure that the SQL and the SharePoint application data are placed on the CLARiiON LUN. Otherwise, the backup will use a software snapshot. Mixing hardware and software providers causes backups to fail. Perform the following configuration steps: 1. Ensure that the proxy node host and the production host have LUNs from the same CLARiiON box. 2. Ensure that the NMM client is installed on both the proxy node and the production host. 3. Install the following software on both the proxy host and production host: EMC Solution Enabler with the symapi_licenses.dat file copied in C:\ProgramFiles\EMC\symapi\config NaviAgent The version of the NaviAgent must match that of FLARE on the CLARiiON. NaviCli EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 23

24 Configuring backups When installing NaviCLi, you are prompted to provide the CLARiiON credentials. Ensure that you provide the correct CLARiiON login details. Admsnap 4. Perform the following steps on both the production host and the proxy host: a. Add both the IPs of CLARiiON, by running this command: C:\Program Files\EMC\SYMCLI\bin> symcfg authorization add -host <CLARiiON IP> -user <CLARiiON Username> -password <CLARiiON Password> For example: symcfg authorization add -host user user -password password symcfg authorization add -host user user -password password b. Add security privileges for the user for both the CLARiiON IPs by running the following command: C:\Program Files\EMC\Navisphere CLI>NaviSECCli -user <Username> -Scope 0 -address <CLARiiON IP> -AddUserSecurity For example: NaviSECCli -user user -Scope 0 -address AddUserSecurity NaviSECCli -user user -Scope 0 -address AddUserSecurity Each time you will be prompted for a password. Ensure to use the CLARiiON password. 5. For both the production host and the proxy host: a. Add the NaviSECCli.exe entry under environmental variables: For example: C:\ProgramFiles (X86)\EMC\Navisphere CLI\NaviSECCli.exe b. Reboot the host. 6. Perform the following NetWorker server side configuration for proxy backup: a. Create client resources for both the production host and the proxy host. The NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide provides the steps for configuring a client resource. 24 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

25 Configuring backups b. After creating client resources for both the production host and the proxy host, add the following information on both the production host client resource and proxy host client resource properties: Select Production Client Resource properties > Globals(2 of 2) > Remote Access > host name. Select Proxy Client Resource properties > Globals(2 of 2) > Remote Access > host name c. Specify the following attributes in Application Information field of the production host client resource to perform proxy backup: NSR_SNAP_TYPE=vss NSR_DATA_MOVER=<Proxy host name> NSR_DATA_MOVER=<Proxy host name> NSR_ALT_PATH=<temporary path> [specify the path here, for example C:\mount] Configuring a proxy server and a storage node for use with a CLARiiON array With the NMM client installed on an application server, you can configure a hardware snapshot of CLARiiON with a proxy host: 1. Before taking a hardware snapshot, the proxy host and the NetWorker server must be configured for use with a CLARiiON. 2. To configure the proxy server, install the NMM client on the NetWorker storage node. This NMM client installation now acts as the storage node and can be used as proxy host to mount snapshots and clones. This NMM client installation now acts as the storage node and can be used as proxy host to mount snapshots and clones. Task 1: Configure the NetWorker server to use a proxy client To configure the NetWorker server to use a proxy client: 1. Configure a backup pool for snapshot operations. 2. Configure a snapshot policy to match: The data protection plan The CLARiiON Storage allocated for data protection. The number of snapshots specified in the NetWorker Snapshot Policy must equal or be less than the number of EMC CLARiiON clones. 3. Configure a backup schedule. 4. Configure a backup group that references the snapshot policy. EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 25

26 Configuring backups Task 2: Configure a client resource Task 3: Use the proxy client Configure a client resource as required for the application on the NetWorker Server by using the NetWorker Management Console. Make sure to include NetWorker User Group entries. The NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide outlines specific steps for each supported application. After configuring the client resource with application-specific settings, complete the following steps to use a proxy client by using the NetWorker Management Console: 1. Click the Global (2 of 2) tab: a. In the Storage nodes attribute, add the proxy machine name with the fully qualified domain name. b. Click Devices on the taskbar and select New. c. In the Name attribute, replace the default name with the path and name of the device. If the device is configured on a remote storage node, the name must indicate that the storage node is remote, by including rd= and the name of the remote storage node in the device path. For example, if the remote storage node is neptune, then the device path might be rd=neptune:c:\tmp\d0. 2. Click the Apps & Modules tab: a. In the Backup Command tab, type: nsrsnap_vss_save b. In the Application information attribute: a. Specify the data mover and snap type. b. For Exchange backup configuration only, type the proxy control port. NSR_DATA_MOVER=proxy host name where: The proxy host name is the fully qualified name of the machine that was just configured as the proxy host. The port required is the RM data port that was configured during the NMM installation on the proxy client. The default is 6728, which is specified as: NSR_DM_PORT=6728 c. Specify the VSS snap type: NSR_SNAP_TYPE=vss 26 EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes

27 Recovering data Validating the backup Recovering data Use the following procedure to validate the backup: 1. Determine whether the backup type is going through a software or hardware provider. 2. Use the DiskShadow command: DISKSHADOW> list shadows all Example output: DISKSHADOW> list shadows all Querying all shadow copies on the computer... * Shadow copy ID = {70d6a e95-bbc253ca7134} <No Alias> - Shadow copy set: {3c740c ebe-9ce3-feb90ba0ff4b} <No Alias> - Original count of shadow copies = 2 - Original volume name: \\?\Volume{d85191bc dd-bf42-001e4f1737c2}\ [volume not on this machine] - Creation time: 1/28/2009 7:04:37 PM - Shadow copy device name: \\?\Volume{4c6849cd-ed5a-11dd-b b210d81b5} - Originating machine: TCE-SP-r sharepoint.com - Service machine: TCE-SP-r sharepoint.com - Not exposed - Provider ID: {04aaf00b-f ae63-e8ac935a102c} - Attributes: Transportable No_Auto_Release Persistent Hardware Imported * Shadow copy ID = {571cef4d-d961-4e03-9b39-acee5d778773} <No Alias> - Shadow copy set: {3c740c ebe-9ce3-feb90ba0ff4b} <No Alias> - Original count of shadow copies = 2 - Original volume name: \\?\Volume{d85191d dd-bf42-001e4f1737c2}\ [volume not on this machine] - Creation time: 1/28/2009 7:04:37 PM - Shadow copy device name: \\?\Volume{4c6849ce-ed5a-11dd-b b210d81b5} - Originating machine: TCE-SP-r sharepoint.com - Service machine: TCE-SP-r sharepoint.com - Not exposed - Provider ID: {04aaf00b-f ae63-e8ac935a102c} - Attributes: Transportable No_Auto_Release Persistent Hardware Imported NMM provides the commands and user interface to perform recoveries. Depending on the application being recovered, a number of recovery options may be available: Granular recovery Disaster recovery Directed recovery The following guides provide detailed steps for the granular, disaster, and directed recovery options available for each application: NetWorker Module for Microsoft Applications Release 2.4 SP1 Administration Guide NetWorker Module for Microsoft Applications Release 2.4 SP1 Application Guide EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Technical Notes 27