Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide Release 2.1

Transcription

1 Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide Release 2.1 MK-92HNAS035-04

2 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users. Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at portal.hds.com. Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. Archivas, BlueArc, Dynamic Provisioning, Essential NAS Platform, HiCommand, Hi- Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation. AIX, AS/400, DB2, Domino, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, OS/390, RS6000, S/390, System z9, System z10, Tivoli, VM/ ESA, z/os, z9, zseries, z/vm, z/vse are registered trademarks and DS6000, MVS, and z10 are trademarks of International Business Machines Corporation. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. Microsoft product screen shots are reprinted with permission from Microsoft Corporation. ii Hitachi NAS Storage Replication Adapter

3 Notice Hitachi Data Systems products and services can be ordered only under the terms and conditions of Hitachi Data Systems applicable agreements. The use of Hitachi Data Systems products is governed by the terms of your agreements with Hitachi Data Systems. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit ( Some parts of ADC use open source code from Network Appliance, Inc. and Traakan, Inc. Part of the software embedded in this product is gsoap software. Portions created by gsoap are copyright Robert A. Van Engelen, Genivia Inc. All rights reserved. The software in this product was in part provided by Genivia Inc. and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. The product described in this guide may be protected by one or more U.S. patents, foreign patents, or pending applications. Notice of Export Controls Export of technical data contained in this document may require an export license from the United States government and/or the government of Japan. Contact the Hitachi Data Systems Legal Department for any export compliance questions. Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager iii

4 Document Revision Level Revision Date Description MK-92HNAS July 2013 First publication MK-92HNAS November 2013 Revision 1, replaces and supersedes MK-92HNAS MK-92HNAS January 2014 Revision 2, replaces and supersedes MK-92HNAS MK-92HNAS February 2014 Revision 3, replaces and supersedes MK-92HNAS MK-92HNAS March 2014 Revision 4, replaces and supersedes MK-92HNAS Contact Hitachi Data Systems 2845 Lafayette Street Santa Clara, California North America: iv Hitachi NAS Storage Replication Adapter

5 TOC 5 Contents About this document...7 Intended audience...7 Hitachi NAS Platform reference documentation...7 VMware reference documentation...8 Getting help...8 Comments...8 Chapter 1: Hitachi NAS Storage Replication Adapter overview...9 HNAS SRA overview...10 HNAS SRA requirements...10 Verify sites are ready for HNAS SRA deployment...11 Chapter 2: HNAS SRA deployment prerequisites...13 Configure sites for HNAS SRA deployment - overview...14 Preparing the source (protected) site...14 Preparing the destination (recovery) site...15 Configure sites for HNAS SRA deployment - details...16 Creating file systems...17 Adding NFS exports...17 Adding a rule...18 Adding a file replication policy...20 Creating a replication schedule...21 Enabling NDMP service...22 Chapter 3: Deploying HNAS SRA...23 Configuring SMU permissions...24 Installing HNAS SRA...24 Upgrading SRA software...25 Verifying HNAS SRA installation...25 Configuring array managers...26 Uninstalling HNAS SRA...29 Advanced configuration options...29 Configuring SRA when an HNAS EVS has multiple IP addresses defined (Primary or Secondary)...29 Single policy to protect multiple datastores (NFS exports)...30 Exclude specified datastores (NFS exports) from being replicated...31 Allow SRM and non-srm based replication policies on the same system...31 Exclude unnecessary VM files and/or specific VMs from being replicated...32 Chapter 4: Troubleshooting...35 Checking for general SRM and SRA issues...36 Logging...36 Generating Reports...36 Error Messages...36 Cannot find matching consistency group at remote site for 'FS_name/Export_name'...36 Cannot unmount datastore <datastore_name> which has VMs on it: <VM_name>...37 Creating protection groups error...37 Device cannot be matched to a remote peer device...37

6 TOC 6 Enable button in Array Manager is inactive...38 Failed to update embedded paths in virtual machine file [file_path]...38 File system is syslocked...38 HNAS SRA not displaying in SRM after successful installation...38 Operating system not adequate for running HNAS SRA for SRM...39 SMU user does not have sufficient privilege to execute commands...39 SRA command 'discoverarrays' failed...39 SRA does not display datastore name...40 SRM action timeout...40 Test recovery fails...40 Failed to access file [datastore-name] failed to unregister protected VMs...40 Unable to access file [unspecified filename]...41 VMware Tools timeout...41 Virtual machines 'GuestOS name' that are not protected by this protection group...41 WFS-1 file system not supported by SRA, found a replication policy...41 Appendix A: Open source software copyrights and licenses...43 Perl module Net::SSH Libssh2...46

7 About this document This document provides deployment, implementation, and troubleshooting information for the Hitachi NAS Storage Replication Adapter (HNAS SRA) for VMware Site Recovery Manager. Intended audience This document is intended for VMware and Hitachi NAS Platform storage administrators who are involved in the deployment of the VMware vcenter Site Recovery Manager. Familiarity with the VMware vsphere environments, ESX servers, vcenter Servers, and the vsphere Client is assumed. You also require a working knowledge of storage network technology, specifically with the Hitachi NAS Platform and its interactions with VMware environments. A full analysis to determine the specific bandwidth and redundancy requirements of the environment you intend to replicate must be conducted by HDS Global Solutions Services in its Remote Copy Planning and Design Service. This service provides you with a high-level design for your distance replication solution and a detailed analysis of workload and performance characteristics to help you support potentially expensive bandwidth decisions. Hitachi NAS Platform reference documentation Hitachi NAS Platform Best Practices Guide for NFS with VMware vsphere (MK-92HNAS028) Provides VMware best practices specific to Hitachi NAS Platforms, which supplements Best Practices for Running VMware vsphere on Network-Attached Storage (NAS). Backup Administration Guide (MK-92HNAS007) In PDF format, this guide provides information about configuring the server to work with NDMP, and making and managing NDMP backups. Also includes information about Hitachi NAS Synchronous Image Backup. Replication and Disaster Recovery Administration Guide (MK-92HNAS009) In PDF format, this guide provides information about replicating data using file-based replication and object-based replication, provides information on setting up replication policies and schedules, and using replication features for disaster recovery purposes. System Access Guide (MK-92HNAS014) In PDF format, this guide explains how to log in to the system, provides information about accessing the NAS server/cluster CLI and the SMU CLI, and provides information about the documentation, help, and search capabilities available in the system. Server and Cluster Administration Guide (MK-92HNAS010) In PDF format, this guide provides information about administering servers, clusters, and server farms. Includes information about licensing, name spaces, upgrading firmware, monitoring servers and clusters, the backing up and restoring configurations. Storage System User Administration Guide (MK-92HNAS013) In PDF format, this guide explains user management, including the different types of system administrator, their roles, and how to create and manage these users. Network Administration Guide (MK-92HNAS008) In PDF format, this guide provides information about the server's network usage, and explains how to configure network interfaces, IP addressing, name and directory services. File Services Administration Guide (MK-92HNAS006) In PDF format, this guide explains about file system formats, and provides information about creating and managing file systems, and enabling and configuring file services (file service protocols). Data Migrator Administration Guide (MK-92HNAS005) In PDF format, this guide provides information about the Data Migrator feature, including how to set up migration policies and schedules. Storage Subsystem Administration Guide (MK-92HNAS012) In PDF format, this guide provides information about managing the supported storage subsystems (RAID arrays) attached to the server/cluster. Includes information about tiered storage, storage pools, system drives (SDs), SD groups, and other storage device related configuration and management features and functions. Snapshot Administration Guide (MK-92HNAS011) In PDF format, this guide provides information about configuring the server to take and manage snapshots.

8 About this document 8 Antivirus Administration Guide (MK-92HNAS004) In PDF format, this guide describes the supported antivirus engines, provides information about how to enable them, and how to configure the system to use them. Command Line Reference Describes how to administer the system by entering commands at a command prompt. Hitachi NAS Platform 3080 and 3090 G2 Hardware Reference (MK-92HNAS017) Provides an overview of the first-generation server hardware, describes how to resolve any problems, and replace potentially faulty parts. Release notes Provides the most up-to-date information about the system, including new feature summaries, upgrade instructions, and fixed and known defects. Note: For a complete list of Hitachi NAS open source software copyrights and licenses, see the System Access Guide. VMware reference documentation Note: Links to non-hds web sites are provided for your convenience only and can change without notice. VMware vcenter Site Recovery Manager documentation ( provides the latest VMware documentation. Best Practices for Running VMware vsphere on Network-Attached Storage (NAS) ( resources/techresources/10096 ) Provides considerations and best practices for deployment of vsphere on NFSbased storage. Getting help If it is necessary to contact the Hitachi Data Systems Support Center, make sure to provide as much information about the issue as possible, including: Circumstances surrounding the error or failure. Contents of any error messages displayed by the VMware Site Recovery Manager. Contents of any error messages displayed by the Hitachi NAS Platform System Management Unit (SMU). Diagnostic logs from the source and destination Hitachi NAS Platforms. Diagnostic logs from the SMU. Diagnostic logs from the VMware vcenter Site Recovery Manager. See the Troubleshooting on page 35 section for more information. The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. If you need technical support, please log on to the HDS Support Portal for contact information: Comments Please send us your comments on this document: mailto:hnas_doc_input@hds.com Include the document's title, number, and revision, and refer to specific sections and paragraphs whenever possible. Thank you!

9 Chapter 1 Hitachi NAS Storage Replication Adapter overview Topics: HNAS SRA overview HNAS SRA requirements Verify sites are ready for HNAS SRA deployment This chapter provides an overview of the Hitachi NAS Storage Replication Adapter (referred to as HNAS SRA throughout most of this document), supported Hitachi NAS platforms and operating systems, file replication requirements and recommendations, and deployment prerequisites. HNAS SRA is deployed within a VMware Site Recovery Manager environment using Hitachi NAS Platform-based replication. This document serves as a supplement guide, describing how to deploy Site Recovery Manager for an existing remote replication solution. Terminology HDS and VMware sometimes use different terminology for the same concept. When referring to storage replication, Site A, Primary, Source, and Protected are all terms that refer to the site where the data is located that you want to replicate; and Site B, Secondary, Destination, Protected, Recovery, and Target, are all terms that refer to the site where the data is stored after it has been replicated. This document uses standard HDS terminology of Source for the site from which the data originates and Destination to which the data is replicated.

10 Hitachi NAS Storage Replication Adapter overview 10 HNAS SRA overview Traditionally, complex distance recovery solutions require customized, site-specific scripting. Testing these solutions also often requires multiple, manual steps, executed for each site. Hitachi Data Systems and VMware team up to provide user-friendly site recovery testing and failover for VMware environments with Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager. The HNAS SRA connects VMware Site Recovery Manager to Hitachi NAS Platform-based replication. The SRM is a host-based interface with intelligence regarding: VMware virtual machines and virtual disks. The association of the virtual machines and storage. The following example shows a typical HNAS SRA configuration for disaster recovery. Figure 1: HNAS SRA disaster recovery configuration. HNAS SRA requirements HNAS SRA is designed as a plugin to vcenter so that data recovery tasks can be executed and managed inside the same management tool as other VMware environment administration tasks. General HNAS SRA Requirements This section lists general requirements for the Site Recovery Manager configuration: Two vcenter servers: one per site. Two Site Recovery Manager servers: one per site. Two configured HNAS sites: one as a source site and one as a destination site. Two externally configured HNAS System Management Units (SMUs): one for each HNAS site.

11 Hitachi NAS Storage Replication Adapter overview 11 Additional Hardware and Software Requirements Before deploying HNAS SRA, verify that the following requirements are in place and configured, where appropriate. Table 1: Required hardware and software Item Description HNAS SRA Release 2.1 Supported operating systems Microsoft Windows Server 2003 SP2, Windows Server 2003 R2, and Windows Server 2003 R2 SP2 (64-bits) Microsoft Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2008 SP1, Windows Server 2008 SP2 (64- bits) Microsoft Windows Server 2012 (64-bits) HNAS infrastructure Platforms: Hitachi NAS Platform, Model 3080 Hitachi NAS Platform, Model 3090 Hitachi NAS Platform 4040 Hitachi NAS Platform 4060 Hitachi NAS Platform 4080 Hitachi NAS Platform 4100 Hitachi NAS File Operating System Release 10.2, or later Release 11.x, or later Hitachi NAS File Operating System licenses Replication File Clone External SMUs Version to match corresponding Hitachi NAS File Operating System as listed above. Supported storage arrays Hitachi Adaptable Modular Storage (AMS) 2000 Hitachi Unified Storage (HUS) Hitachi Unified Storage VM (HUS VM) Hitachi Universal Storage Platform (USP-V) Hitachi Virtual Storage Platform (VSP) Protocol NFS VMware infrastructure VMware vcenter Server 5.0, 5.1, or 5.5 VMware vsphere Client 5.0, 5.1, or 5.5 VMware Site Recovery Manager 5.0, 5.1, or 5.5 Verify sites are ready for HNAS SRA deployment This section describes the high-level steps necessary to prepare both the source (protected) site and the destination (recovery) site for deploying HNAS SRA. Confirm that an independent System Management Unit (SMU) is configured for both sites.

12 Hitachi NAS Storage Replication Adapter overview 12 Ensure the SMUs are able to communicate with all admin EVS IP addresses for all Hitachi NAS Platforms involved. From the SMU, go to Home > Server Settings > EVS Management to check status. (See the Server and Cluster Administration Guide for more information.) Open all TCP ports (specifically for the EVS IP addresses involved with replication communication) to allow for multiple replication streams. This is optional, but recommended for optimum intra-site communications. Ensure NDMP services are running on both sites. From the SMU, go to Home > Data Protection > NDMP Configuration to check the status. (See the Backup Administration Guide for more information.) Hitachi NAS Platform NFS and VMware configuration recommendations It is strongly recommended that you review and follow the information in the Best Practices section of Hitachi NAS Platform Best Practices Guide for NFS with VMware vsphere, which contains recommendations on appropriate storage and network configurations for your VMware HDS NFS storage environment.

13 Chapter 2 HNAS SRA deployment prerequisites Topics: Configure sites for HNAS SRA deployment - overview Configure sites for HNAS SRA deployment - details Before deploying HNAS SRA, you must configure each datastore that needs to be protected by the Site Recovery Manager at both the source site and the destination site. The following list outlines typical high-level tasks to add and configure on both sites: Create placeholder file systems Confirm that syslock is disabled Add NFS exports to source and verify they are set to read-write Add NFS exports to target and verify they are set to read-only Mount the NFS exports to the ESXi host Add replication rule (optional) Add replication policies Add replication schedule (on the source site only) Enable the NDMP service Note: It is recommended that you review the current Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Release Notes before proceeding. Refer to the following guides if you need additional information when configuring HNAS: File Services Administration Guide Replication and Disaster Recovery Administration Guide

14 HNAS SRA deployment prerequisites 14 Configure sites for HNAS SRA deployment - overview This section provides high-level tasks that must be completed on both the source and destination sites before deploying HNAS SRA. If you prefer more detailed steps, refer to Configure sites for HNAS SRA deployment - details on page 16. Preparing the source (protected) site Before deploying HNAS SRA, configure the source site as follows: 1. Identify the Hitachi NAS Platform-based datastores mounted on the ESXi host or cluster to be protected on the source site; for example: SiteA-DS-02, a datastore on the source site file system SiteA-FS-1. Use the Hitachi NAS Virtual Infrastructure Integrator plugin to quickly identify these Hitachi NAS Platform-based datastores. See Hitachi NAS Virtual Infrastructure Integrator Administration Guide (MK-92HNAS003) for more information. 2. For each datastore at the source site, create an equivalent datastore (NFS export) on the file system target at the destination (recovery) site ; for example create datastore SiteB-DS-02 on the destination site file system SiteB-FS-1 as the target for the SiteA-DS-02 datastore on the source site file system SiteA-FS-1. Note: Set read-write to Access Configuration on NFS exports. For example: esxi-ip(rw) in NFS exports Access Configuration. 3. Create a file system for the placeholder datastore, and create NFS exports; for example: PHdatastore1. Note: The placeholder datastore is not involved in the file replication process. Note: Only one placeholder file system is required to be configured per SRM server to protect multiple datastores. 4. Mount the PHdatastore1 file system on an ESXi host. 5. Create a replication policy with SiteA-DS-02 as the replication source and SiteB-DS-02, which resides on the destination site, as the target. Use the unmanaged server option as part of the replication policy creation. You will be targeting datastores that are identified in Step 1. See the Replication and Disaster Recovery Administration Guide for more information. 6. Required if the ESXi host datastores are exported from the file system root level: Create a file replication rule to exclude the /.jetapi directory from a replication, and apply the rule to the file replication policy. Note: Generally, best practice is that ESXi datastores are not exported at file system root level.

15 HNAS SRA deployment prerequisites Add the replication schedule for the replication policy by applying the rule, and initiate immediately. Remember: Wait for the replication to complete before preparing the secondary site. 8. Validate that the replication completed successfully. Preparing the destination (recovery) site Before deploying HNAS SRA, configure the destination site as follows: 1. Identify the file systems mounted on the ESXi hosts that store the replicated virtual machine disks (VMDKs) and configuration files. For example: SiteB-DS-02, a datastore on the destination site file system SiteB-DS-02, a datastore on the destination site file system SiteB-FS-1.

16 HNAS SRA deployment prerequisites 16 Note: Disable the syslock mode on the respective file systems. 2. Create a file system for the placeholder datastore, and create NFS exports. For example: PHdatastore2. Note: Set read-only to Access Configuration on NFS exports. For example: esxi-ip(ro) in NFS exports Access Configuration. Another example is when specifying the individual ESXi host(s) that should have access to NFS exports. 3. Mount the PHdatastore2 file system on the ESXi host. Note: Only one placeholder file system is required to be configured per SRM server at the recovery site. 4. For each datastore that is to be protected from the source site (A) to the destination site (B), you create another bidirectional replication policy from the destination site to source site. For example: Create a replication policy with SiteB-DS-02 as the replication source, and SiteA-DS-02 that resides on the source site. 5. Verify that the NDMP service is running; restart, if necessary. 6. If you prefer more detailed steps, go to the next section. If not, skip directly to Deploying HNAS SRA on page 23. Configure sites for HNAS SRA deployment - details This section provides detailed steps for configuring both the source and destination sites to deploy HNAS SRA. If you prefer a high-level overview, refer to Configure sites for HNAS SRA deployment - overview on page 14. The order in which sites are configured is flexible. The source and destination sites can be completely configured one after the other, or each step can be performed on each site before moving on to the next step. The steps in this section take the second approach: they describe each step, first for the source site, then for the destination site.

17 HNAS SRA deployment prerequisites 17 Creating file systems This section describes the high-level steps for creating the file systems. For complete details, see the File Services Administration Guide. These file systems must be created on both the source and destination sites before deploying HNAS SRA. 1. Log into the SMU for the source site. 2. Create two file systems: one referred to as the file system for VMware datastore and the other referred to as the file system for SRM placeholder datastore. For example, you might label the file system for VMware datastore SourceFS and the file system for the placeholder datastore PHdatastore1. Set each file system with the following configuration: The Size Limit of the source file system cannot be less than the size limit on the destination file system. Set the file system to Allocate Now. Optionally, enable the Support and Enable Dedupe option (HNAS OS v11.0 and newer). Set the Block Size. You can select either option, but best practice is to set it to 4 KB. 3. Log into the SMU for the destination site and repeat step 2. On the the destination site you will also have a file system for VMware datastore and a file system for SRM placeholder datastore. For example, you might label the file system for VMware datastore TargetFS and the file system for the placeholder datastore PHdatastore2. Disabling Syslock on a file system All file systems must have Syslock disabled. To verify and change the status: 1. Log in to the SMU for the source site. 2. Navigate to Home > Storage Management > File System to open the File System page. 3. Select the file system from the list and then click Details to display the File System Details page. 4. Check the current status of Syslock. If the status is enabled, click Disable. 5. Click OK. 6. Repeat steps 2-5 to disable Syslock on the destination site. Adding NFS exports This procedure describes the high-level steps to add NFS exports. For more details, see the File Services Administration Guide. In VMware, NFS datastores are NFS exports. For HNAS SRA, ensure that the same exports exist on the source and the destination systems. If you plan to use consistency groups, you must have the equal number of NFS exports at the source file system and at the destination file system. For example, if the source file system has 10 NFS exports, the destination file system must also have 10 NFS exports. 1. Log in to the SMU for the source site. 2. Navigate to Home > File Services > NFS Exports. 3. Make sure you have selected the EVS and file system to which the NFS export is assigned. For example, file system SourceFS. 4. Specify the export name, the path to the source directory for the export, and add read/write permissions in the Access Configuration field. For example, enter /Country in the Export Name field, enter /Country in the Path field, and esxiip(rw) in the Access Configuration field. 5. Continue to add NFS exports as appropriate. For example, enter /JP in the Export Name field, /Country/JP in the Path field, and esxi-ip(rw) in the Access Configuration field. The following NFS export details page shows an example of NFS exports:

18 HNAS SRA deployment prerequisites 18 In the example NFS Details page, eight NFS exports with the following path structure were added: /Country /Country/JP /Country/UK /Country/US /Dept /Dept/HR /Dept/Eng /Dept/Fin 6. Log into the SMU for the destination site and repeat steps 2-5 to add the identical exports. For the destination sites, add *(ro) or esxi-ip(ro) in the Access Configuration field. The esxi-ip(ro) example is used when specifying the individual ESXi host(s), which should have access to NFS exports. Adding a rule You can exclude replicating one or more directories or files when adding a rule and then apply the rule to a policy. This section includes instructions on how to add the following rules: Specify directories or files to exclude Use the #SRMflag exception Adding a rule (specifying exclusions) This procedure describes the high-level steps required to add a rule that excludes a directory or file. 1. Log in to the SMU for the source site. 2. Navigate to Home > Data Protection > File Replication Rules > Add Rule to open the Add Rule page. 3. Enter the rule name and, optionally, a description.

19 HNAS SRA deployment prerequisites In the File to Exclude field, enter one or more directories or files. When specifying a file or directory, enter either: A full path name, relative to the top-level directory specified in the replication path. The path name must begin with a forward slash (/); at the end, an asterisk (*) can be entered as a wildcard character. A terminal file or directory name, which is simply the last element in the path. The name may not contain any characters, but it may start or end with an asterisk (*). A list of files or directories to exclude from a replication. When listing files or directories to exclude from a replication, all items in the list must be separated by a comma. 5. Click OK. 6. Log in to the SMU for the destination site and repeat steps 2-5. Adding a rule (#SRMflag) HNAS SRA introduces new keyword #SRMflag for Files to Exclude field. This keyword can be configured when there are multiple file replication polices on HNAS system, but not all for VMware SRM solution. Apply the rule which has the keyword #SRMflag into the replication policies protected by VMware SRM. HNAS SRA allows for exclusion of specific replication policies using the keyword #SRMflag in the Files To Exclude field. This keyword can be configured when there are multiple file replication policies on an HNAS system, but not all are defined for use with the VMware SRM solution. For configurations such as these, define a rule which uses the #SRMflag keyword and apply this rule to the replication policies in use by VMware SRM. This keyword can be used along with regular directories/files exclusions. 1. Log in to the SMU for the source site. 2. Navigate to Home > Data Protection > File Replication Rules > Add Rule to open the Add Rule page. 3. Enter the rule name and optionally, a description.

20 HNAS SRA deployment prerequisites In the Files To Exclude field, enter #SRMflag. 5. Click OK. 6. Log in to the SMU for the destination site and repeat steps 2-5. Adding a file replication policy This procedure describes the high-level tasks to add a file replication policy. A file replication policy identifies the data source, the replication target, and optionally a replication rule. For complete details on policies, refer to the Replication and Disaster Recovery Administration Guide. 1. Log in to the SMU for the source site. 2. Navigate to Home > Data Protection > File Replication to open the File Replication page and click Add under the Policies section of the page. 3. Choose Not a Managed Server and then click Next. The following image illustrates an example of a policy.

21 HNAS SRA deployment prerequisites Enter the name of the policy. 5. Enter the information specific to the source site: a) The EVS and file system must correspond to the VM file system. b) Choose Directory and then enter the NFS export path. 6. Enter the information specific to the destination site: a) The IP address for the destination host. b) VM file system on the destination site. c) The path. d) The NDMP user name and password. 7. Optionally, select the File Replication rule. For more information on using this rule, see Adding a rule (specifying exclusions) on page 18 and Adding a rule (#SRMflag) on page Log in to the destination site and repeat steps 2-7. Creating a replication schedule Note: schedules are only set on the source site. To apply the schedule to the replication policy: 1. Log into the SMU for the source site. 2. Navigate to Home > Data Protection > File Replication.

22 HNAS SRA deployment prerequisites Click Add under the Schedules section to open the Add Schedule page. 4. Select the Policy. 5. Choose Immediately: Start as soon as the schedule is created. 6. Choose Once, at the scheduled date and time. 7. Click OK to save changes and return to the File Replication page. 8. Under the Schedule section of the page, verify that the schedule completed successfully. This step is done only at the source site. Enabling NDMP service To check that NDMP service is started: 1. Navigate to Home > Data Protection > NDMP Configuration to display the NDMP Configuration page. 2. Check the Current Status in the NDMP Server Status section of the page. Click start if the current status is stopped. 3. Repeat steps 1-2 for the destination site.

23 Chapter 3 Deploying HNAS SRA Topics: This section provides instructions for deploying the HNAS SRA. Configuring SMU permissions Installing HNAS SRA Configuring array managers Uninstalling HNAS SRA Advanced configuration options

24 Deploying HNAS SRA 24 Configuring SMU permissions The HNAS SRA uses file replication features of the Hitachi NAS Platform, and interacts with the HNAS System Management Unit (SMU) to create replication relationships between two sites, and to connect to the HNAS nodes. To allow the HNAS SRA to run the required commands, you must update the /etc/sudoers file on the all SMUs at both the source and destination sites. Note: Updating the /etc/sudoers file on the SMU is only required if you are running SMU v11.2 or earlier. Otherwise, you can skip this section. Do not change /etc/sudoers files on an embedded SMU running in an HNAS node. An embedded SMU is not supported. 1. Using SSH software, log in to the SMU as user manager. 2. Enter su - to acquire root privileges. Note: Changes to the /etc/sudoers file can only be performed by root. 3. Enter chmod 0660 /etc/sudoers to change the permissions for the /etc/sudoers file to Enter cp /etc/sudoers /etc/sudoers_tmp to create a temporary copy of the file. 5. Enter echo manager ALL=(root) NOPASSWD: /usr/bin/smcli, /usr/bin/smclient, /opt/smu/adc_replic/replication_schedule.sh >> /etc/sudoers_tmp Note: The above line should be entered as a single line in the CLI, as it must be a single line in the file /etc/sudoers_tmp. 6. Enter cat /etc/sudoers_tmp to confirm the file is correct. 7. Assuming the file /etc/sudoers_tmp is correct, enter mv -f /etc/sudoers_tmp /etc/sudoers 8. Enter chmod 0440 /etc/sudoers to reset the permissions. 9. Enter exit to exit the root shell. CLI example: [manager@smu01 ~]$su - Password: [root@smu01 ~]# chmod 0660 /etc/sudoers [root@smu01 ~]# cp /etc/sudoers /etc/sudoers_tmp [root@smu01 ~]# echo manager ALL=(root) NOPASSWD: /usr/bin/smcli, /usr/bin/ SMclient, /opt/smu/adc_replic/replication_schedule.sh" >> /etc/sudoers_tmp [root@smu01 ~]# cat /etc/sudoers_tmp [root@smu01 ~]# mv -f /etc/sudoers_tmp /etc/sudoers [root@smu01 ~]# chmod 0440 /etc/sudoers [root@smu01 ~]# exit [manager@smu01 ~]$ Installing HNAS SRA Storage Replication Adapters (SRA) provide an interface to primary storage with replication software. SRAs are vendor-specific, and need to be installed on the Site Recovery Manager (SRM) servers at both the source sites and the destination sites. The HNAS SRA installer is available as a downloadable.msi file from Hitachi Data Systems at portal.hds.com or available from the VMware SRM download site. To begin the installation process:

25 Deploying HNAS SRA Ensure that the SRM is installed. 2. Download the HNAS SRA installer from VMware or the Hitachi Data Systems support portal ( portal.hds.com). 3. Copy and install the.msi file on the SRM servers at both the source site and the destination site. Upgrading SRA software Upgrading from HNAS SRA v2.0 or newer is supported using the.msi file referenced above. If upgrading from an earlier version, uninstall this version first. After executing the.msi installation program, perform the following steps to complete the upgrade process: 1. Download the HNAS SRA installer from VMware or the Hitachi Data Systems support portal ( portal.hds.com). 2. Copy and install the.msi file on the SRM servers at both the source and destination sites. 3. In previous versions, it was required that Syslock be enabled on the destination site file system. Beginning with v2.1, this is no longer necessary. Therefore, ensure that Syslock is disabled on each destination file system. See the topic, Disabling Syslock on a file system on page 17, for details. 4. Refresh the Devices for Array pair in the Devices tab for each configured array manager. The discovery is expected to fail if the destination site file system is in syslock state. Take it out of syslock state make the NFS exports on destination site read only. See the topic, HNAS SRA deployment prerequisites on page 13, for details. 5. Configure array managers. See the topic, Configuring array managers on page 26, for details. Verifying HNAS SRA installation This section describes how to verify the HNAS SRA installation. 1. On the Site Recovery Manager server, locate the following directory: For SRM 5.0: Go to C:\Program Files (x86)\vmware\vmware vcenter Site Recovery Manager\storage\sra For SRM 5.1 and SRM 5.5: Go to C:\Program Files\VMware\VMware vcenter Site Recovery Manager\storage\sra 2. In the Site Recovery Manager GUI, select the SRAs tab to display the currently installed Storage Replication Adapters (SRAs). If no SRAs are listed, click Rescan SRAs. If none are listed, then no SRA was installed on the Site Recovery Manager server. See HNAS SRA not displaying in SRM after successful installation on page 38 for more information.

26 Deploying HNAS SRA 26 Configuring array managers 1. Double-click the VMware vsphere Client icon ( Recovery > Array Managers. ), log in to the vcenter Server, and go to Home > Site 2. In the Array Manager pane, identify the protected site in which you want to configure, right-click, and select Add Array Manager. 3. Enter a display name, select Hitachi NAS Replicator Adapter as the SRA type, and then click Next.

27 4. Enter the System Management Unit (SMU) and admin EVS details, and then click Next. Deploying HNAS SRA 27

28 Deploying HNAS SRA 28 Field/Item SMU OS IP Address SMU OS Username Password Admin EVS IP Address Device Exclude List Admin EVS Username Description Enter the IP address of the SMU. Enter a unique user name, such as manager. Enter a password for the SMU OS user name provided. Note: The user name and password entered might be different from the user name and password that is provided when logging in to Web Manager, the SMU GUI. Enter the IP address of the admin EVS. Enter a comma-separated list of strings in file system names to exclude. Leave this field blank, if you do not want to exclude any volumes. Enter a unique user name.

29 Deploying HNAS SRA 29 Field/Item Password Description Enter a password for the admin EVS user name provided. 5. Repeat these steps on the recovery (secondary) site. Note: After an array pair has been added, ensure you enable it. Uninstalling HNAS SRA This section describes how to uninstall HNAS SRA, if necessary. Uninstall HNAS SRA using the Microsoft Windows Control Panel on both Site Recovery Manager (SRM) servers at the source site and the destination site. 1. From the SRM server at the source site, go to Start > Control Panel > Programs > Uninstall a program. 2. Right-click HNAS SRA, and select Uninstall. 3. Repeat for the destination site. Advanced configuration options This section describes advanced configuration options available to you. Configuring SRA when an HNAS EVS has multiple IP addresses defined (Primary or Secondary) If the datastore on the primary or secondary site is hosted on an HNAS EVS with multiple IP addresses, the steps below must be followed to create a successful array pair during device discovery. If the configuration files are required but are not present, the array pair will be greyed out and have different IP addresses on the protected and recovery site. Note: A unique config.cfg file must be defined at both the primary and the secondary site. Do NOT copy the config.cfg file between the two sites. At both the primary and secondary site, a file name config.cfg must be created. Please note that the config.cfg file name is case sensitive and must consist of all lower case letters. The path for the location of the configuration file is represented by the variable path $Bin/config.cfg. For a typical installation, this path would be C:\Program Files \VMware\VMware vcenter Site Recovery Manager\storage\sra\HNAS-SRA\config.cfg. Each config.cfg file must contain at least one set of values, in the order described below. POLICY_NAME SRC_IP Exact name of the replication policy used to replicate the VMs from the one site to the other site. It is case sensitive and must be the first parameter of the set for each replication policy. Source IP address to be used in the SRA workflow. This must be one of the IP addresses configured on the HNAS EVS hosting the datastore at the source location.

30 Deploying HNAS SRA 30 DEST_IP Destination IP to be used in the SRA workflows. This must be one of the IP addresses configured on the HNAS EVS hosting the datastore at the destination location. Below is an example of the contents of a config.cfg file for a single policy set: #policy 1 POLICY_NAME=repl1 SRC_IP= DEST_IP= Note: The POLICY_NAME, SRC_IP, and DEST_IP will be different between the two sites. Add a set for each replication policy of a datastore used by SRA where the datastore is hosted on an EVS with multiple IP addresses, as outlined in the example above. Note: The config.cfg file is not part of the HDS SRA Installation. If this file is needed, you will need to create it, add the content, and write it using a text editor such as notepad. It is important to match the format exactly including case and only write a text file. Formats other than a text file are not supported. Single policy to protect multiple datastores (NFS exports) This option protects multiple NFS exports on a single HNAS file system using one file replication policy (Consistency Group). The example below protects DS01 and DS02 on FS01 filesystem. Source site 1. Create a file system (for example, FS01). 2. Create an NFS Export on FS01. (NFS Export Name: ROOT, NFS Export Path: / and Access Configuration: esxiip(rw)). 3. Create a second NFS Export on FS01. (NFS Export Name: DS01, NFS Export Path: /DS01 and Access Configuration: esxi-ip(rw)). Note: Use *(rw) if not specifying individual ESXi host(s) with access. 4. Create a third NFS Export on FS01. (NFS Export Name: DS02, NFS Export Path: /DS02 and Access Configuration: esxi-ip(rw)). 5. Create a File Replication Policy (for example, File Replication Policy name is Rep1P). a. Source file system: FS01 b. Source Directory: / c. Destination File System: FS11 d. Destination Directory: / Note: Any directory can be used. 6. Create a File Replication Policy Schedule of Rep1P 7. Mount /DS01 and /DS02 on ESXi Destination site 1. Create a file system (for example, FS11). 2. Create an NFS Export on FS11 (NFS Exports Name: ROOT, NFS Export Path: / and Access Configuration: esxiip(ro)). 3. Create a second NFS Export on FS11 (NFS Exports Name: DS01, NFS Export Path: /DS01 and Access Configuration: esxi-ip(ro)). Note: Use *(ro) if not specifying individual ESXi host(s) with access.

31 Deploying HNAS SRA Create a third NFS Export on FS11 (NFS Export Name: DS02, NFS Export Path: /DS02 and Access Configuration: esxi-ip(ro)). 5. Create a File Replication Policy (for example, File Replication Policy name is Rep1S). a. Source File System: FS11 b. Source Directory: / c. Destination File System: FS01 d. Destination Directory: / Note: No replication schedule is required on the destination. Exclude specified datastores (NFS exports) from being replicated This option protects multiple NFS exports per a single HNAS file system by one File Replication Policy (Consistency Group), but excludes specified NFS exports. This example has three datastores (DS01, DS02, and DS03) on the same file system. This example excludes DS02 from being replicated without creating individual policies. 1. Go to the source site. 2. After creating NFS Exports, create a File Replication Policy Rule (Rule Name: exclusion-ds02 and Files To Exclude: /DS02) and apply the rule to the File Replication Policy. 3. Go to the destination site. 4. After creating NFS Exports, create a File Replication Policy Rule (Rule Name: exclusion-ds02, Files To Exclude: /DS02) and apply the rule to the File Replication Policy. Allow SRM and non-srm based replication policies on the same system In a configuration which has other replication policies that are associated with a non-vmware SRM use case, the following option allows you to identify replication policies that are specifically associated with SRM configuration. In this option, 'DS01' and 'DS02' are used for VMware SRM and 'DS03' has a replication policy not associated with a VMware SRM configuration and/or is possibly not a VMware-specific export. 1. Go to the source site. 2. After creating NFS Exports, create a File Replication Policy Rule (Rule Name: SRM and Files To Exclude: #SRMFlag) and apply the rule to the File Replication Policy.

32 Deploying HNAS SRA Go to the destination site. 4. After creating NFS Exports, create a File Replication Policy Rule (Rule Name: SRM and Files To Exclude: #SRMFlag) and apply the rule to the File Replication Policy. Exclude unnecessary VM files and/or specific VMs from being replicated This option ensures that only pertinent VMware files are replicated and ensuring that non essential VM level files (temp, swap files etc.) are not replicated. Secondly, this can be extended to remove certain VMs from being replicated without forcing those VMs to be relocated to other non-srm datastores. Note that it is required that any VM(s) excluded as part of a replication policy have been replicated at least once to the destination before being excluded via a File Replication Rule. This example protects the datastore DS01 and DS02 by consistency group; however, one of the VMs (VM3) that is present on DS01 is not required to be replicated, ensuring lower overall replication times for the datastore. It also excludes all non-essential VMware files (*.vswp and *.nvram) across all VMs. Note: Ensure at least one replication policy has been completed, which has replicated all VMs on DS01 and DS02 including VM3. 1. Go to the source site. 2. After creating NFS Exports, create File Replication Policy Rule (Rule Name: exclusion-vm3 and Files To Exclude: /DS01/VM3). Note: The image above shows excluding /DS12 datastore and vm-win-largetemp on DS11 being replciated. This is in addition to excluding all *.vswp and *.nvram VMware files from being replicated. 3. Create a File Replication Policy (for example, File Replication Policy name Rep1P) and apply the rule exclusion- VM3. 4. Go to the SRM GUI on the source site. 5. Use the existing Recovery Plan for the protection group.

33 6. From Recovery Plan, configure the VM with the Do not power on setting for the VM(s) that do not need to be managed for failover. Deploying HNAS SRA 33

34

35 Chapter 4 Troubleshooting Topics: Checking for general SRM and SRA issues Logging Generating Reports Error Messages This section provides information and instructions for troubleshooting configuration issues. When diagnosing an issue, review and provide the required logs to Hitachi Data Systems Support Center. For details about the available logs and those required for Hitachi Data Systems Support Center assistance, see Logging on page 36. Note: Ensure you have reviewed the current Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Release Notes for any limitations and workarounds.

36 Troubleshooting 36 Checking for general SRM and SRA issues Refer to the VMware Community ( for more information. Logging This section describes how to use logging for troubleshooting purposes. Locate SRM and SRA logs on source and destination sites in the following locations: Windows 2003: %ALLUSERSPROFILE%\Application Data\VMware\VMware vcenter Site Recovery Manager \Logs\ Windows 2008/2012: C:\VMware\VMware vcenter Site Recovery Manager\Logs\ Log files for SRA 2.1 are in the following subdirectory: For SRM5.0: C:\ Program Files (x86)\vmware\vmware vcenter Site Recovery Manager\storage\sra\HNAS- SRA\log\ For SRM5.1 and SRM5.5: C:\Program Files\VMware\VMware vcenter Site Recovery Manager\storage\sra \HNAS-SRA\log\ Generating Reports This section describes how to generate SRM operation HTML reports. 1. From the vsphere Client, go to Home > Site Recovery > Recovery Plans > History. 2. Identify the operation, and click Export to generate a SRM Operation HTML Report. Error Messages This section lists the error messages you might see. Each topic will have a possible cause for the error and a possible resolution. Cannot find matching consistency group at remote site for 'FS_name/Export_name' The entire error message: "Cannot find matching consistency group at remote site for 'FS_name/Export_name". Possible cause Consistency group is formed for a parent NFS export that has sub-nfs exports acting as datastores. Resolution 1. Exclude the sub-nfs export directory from file replication using a file replication rule setting.