Hitachi NAS Storage Replication Adapter for … · Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide Release 2.2 ... //portal.hds.com

Hitachi NAS Platform

Hitachi NAS Storage Replication Adapterfor VMware Site Recovery Manager

Deployment GuideRelease 2.2

MK-92HNAS035-05

© 2011-2015 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by anymeans, electronic or mechanical, including photocopying and recording, or stored in adatabase or retrieval system for any purpose without the express written permission ofHitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time withoutnotice and assumes no responsibility for its use. This document contains the mostcurrent information available at the time of publication. When new or revised informationbecomes available, this entire document will be updated and distributed to all registeredusers.

Some of the features described in this document might not be currently available. Referto the most recent product announcement for information about feature and productavailability, or contact Hitachi Data Systems Corporation at https://portal.hds.com.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms andconditions of the applicable Hitachi Data Systems Corporation agreements. The use ofHitachi, Ltd., products is governed by the terms of your agreements with Hitachi DataSystems Corporation.

2Deployment Guide

https://portal.hds.com

Hitachi Data Systems products and services can be ordered only under the terms andconditions of Hitachi Data Systems’ applicable agreements. The use of Hitachi DataSystems products is governed by the terms of your agreements with Hitachi DataSystems.

By using this software, you agree that you are responsible for:

a) Acquiring the relevant consents as may be required under local privacy laws orotherwise from employees and other individuals to access relevant data; and

b) Verifying that data continues to be held, retrieved, deleted, or otherwise processedin accordance with relevant laws.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and othercountries. Hitachi Data Systems is a registered trademark and service mark ofHitachi, Ltd., in the United States and other countries.

Archivas, Dynamic Provisioning, Essential NAS Platform, HiCommand, Hi-Track,ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy,Universal Star Network, and Universal Storage Platform are registered trademarks ofHitachi 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 orwebsite are properties of their respective owners.

Microsoft product screen shots are reprinted with permission from MicrosoftCorporation.

This product includes software developed by the OpenSSL Project for use in theOpenSSL Toolkit (http://www.openssl.org/). Some parts of ADC use open source codefrom Network Appliance, Inc. and Traakan, Inc.

Part of the software embedded in this product is gSOAP software. Portions created bygSOAP are copyright 2001-2009 Robert A. Van Engelen, Genivia Inc. All rightsreserved. The software in this product was in part provided by Genivia Inc. and anyexpress or implied warranties, including, but not limited to, the implied warranties ofmerchantability and fitness for a particular purpose are disclaimed. In no event shallthe author be liable for any direct, indirect, incidental, special, exemplary, orconsequential damages (including, but not limited to, procurement of substitutegoods or services; loss of use, data, or profits; or business interruption) howevercaused 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.

3Deployment Guide

Notice of Export Controls

Export of technical data contained in this document may require an export license fromthe United States government and/or the government of Japan. Contact the Hitachi DataSystems Legal Department for any export compliance questions.

4Deployment Guide

5Deployment Guide

Contents

About this document..............................................................................8Intended audience................................................................................................... 8Hitachi NAS Platform reference documentation...........................................................8VMware reference documentation........................................................................... 10Accessing product documentation........................................................................... 10Getting help...........................................................................................................10Comments.............................................................................................................10

1 Hitachi NAS Storage Replication Adapter overview..................................12HNAS SRA overview............................................................................................... 13

2 HNAS SRA requirements.......................................................................14

3 HNAS SRA deployment prerequisites..................................................... 16Verify sites are ready for HNAS SRA deployment.......................................................17Configure sites for HNAS SRA deployment - overview............................................... 17

Preparing the source (protected) site................................................................. 17Preparing the destination (recovery) site............................................................ 21

Configure sites for HNAS SRA deployment - details...................................................22Creating file systems ........................................................................................23

Disabling Syslock on a file system.................................................................23Adding NFS exports.......................................................................................... 24Adding a rule....................................................................................................25

Adding a rule (specifying exclusions)............................................................ 25Adding a rule (#SRMflag)............................................................................ 26

Adding a file replication policy........................................................................... 27Creating a replication schedule.......................................................................... 29Enabling NDMP service......................................................................................29

6Deployment Guide

4 Deploying HNAS SRA........................................................................... 30Configuring SMU permissions.................................................................................. 31Installing HNAS SRA...............................................................................................32

Upgrading SRA software....................................................................................32Verifying HNAS SRA installation ........................................................................ 33

Configuring array managers....................................................................................33Uninstalling HNAS SRA........................................................................................... 37Advanced configuration options...............................................................................37

Configuring SRA when an HNAS EVS has multiple IP addresses defined (Primary orSecondary).......................................................................................................38Single policy to protect multiple datastores (NFS exports)....................................39Exclude specified datastores (NFS exports) from being replicated.........................40Allow SRM and non-SRM based replication policies on the same system................41Exclude unnecessary VM files and/or specific VMs from being replicated............... 42

5 Troubleshooting...................................................................................46Checking for general SRM and SRA issues................................................................47Logging.................................................................................................................47Generating Reports................................................................................................ 47Error Messages...................................................................................................... 47

Cannot find matching consistency group at remote site for 'FS_name/Export_name'.......................................................................................................................48Cannot unmount datastore <datastore_name> which has VMs on it: <VM_name>.......................................................................................................................48Creating protection groups error........................................................................ 48Device cannot be matched to a remote peer device ........................................... 49Enable button in Array Manager is inactive......................................................... 49Failed to update embedded paths in virtual machine file [file_path]......................50File system is syslocked ....................................................................................50HNAS SRA not displaying in SRM after successful installation............................... 50Operating system not adequate for running HNAS SRA for SRM........................... 50SMU user does not have sufficient privilege to execute commands....................... 51SRA command 'discoverArrays' failed................................................................. 51SRA does not display datastore name ................................................................52SRM action timeout ..........................................................................................52Test recovery fails.............................................................................................52Failed to access file [datastore-name] failed to unregister protected VMs..............53Unable to access file [unspecified filename] .......................................................53VMware Tools timeout.......................................................................................53Virtual machines 'GuestOS name' that are not protected by this protection group..........................................................................................................................54WFS-1 file system not supported by SRA, found a replication policy .....................54

A Open source software copyrights and licenses....................................... 56Perl module Net::SSH2........................................................................................... 57Libssh2..................................................................................................................60

Index..................................................................................................62

7Deployment Guide

About this documentThis document provides deployment, implementation, and troubleshootinginformation for the Hitachi NAS Storage Replication Adapter (HNAS SRA) forVMware® vCenter™ Site Recovery Manager™.

Intended audienceThis document is intended for VMware and Hitachi NAS Platform storageadministrators 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 alsorequire a working knowledge of storage network technology, specifically withthe Hitachi NAS Platform and its interactions with VMware environments.

A full analysis to determine the specific bandwidth and redundancyrequirements of the environment you intend to replicate must be conductedby HDS Global Solutions Services in its Remote Copy Planning and DesignService. This service provides you with a high-level design for your distancereplication solution and a detailed analysis of workload and performancecharacteristics 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 toHitachi NAS Platforms, which supplements Best Practices for RunningVMware vSphere on Network-Attached Storage (NAS).

• Backup Administration Guide (MK-92HNAS007)—In PDF format, this guideprovides information about configuring the server to work with NDMP, andmaking and managing NDMP backups.

• Replication and Disaster Recovery Administration Guide (MK-92HNAS009)—In PDF format, this guide provides information about replicating datausing file-based replication and object-based replication, providesinformation on setting up replication policies and schedules, and usingreplication features for disaster recovery purposes.

• System Access Guide (MK-92HNAS014)—In PDF format, this guideexplains how to log in to the system, provides information about accessingthe NAS server/cluster CLI and the SMU CLI, and provides informationabout the documentation, help, and search capabilities available in thesystem.

• Server and Cluster Administration Guide (MK-92HNAS010)—In PDF format,this guide provides information about administering servers, clusters, andserver farms. Includes information about licensing, name spaces,

8 About this documentDeployment Guide

upgrading firmware, monitoring servers and clusters, the backing up andrestoring configurations.

• Storage System User Administration Guide (MK-92HNAS013)—In PDFformat, this guide explains user management, including the different typesof system administrator, their roles, and how to create and manage theseusers.

• Network Administration Guide (MK-92HNAS008)—In PDF format, thisguide provides information about the server's network usage, and explainshow to configure network interfaces, IP addressing, name and directoryservices.

• File Services Administration Guide (MK-92HNAS006)—In PDF format, thisguide explains about file system formats, and provides information aboutcreating and managing file systems, and enabling and configuring fileservices (file service protocols).

• Data Migrator Administration Guide (MK-92HNAS005)—In PDF format, thisguide provides information about the Data Migrator feature, including howto set up migration policies and schedules.

• Storage Subsystem Administration Guide (MK-92HNAS012)—In PDFformat, this guide provides information about managing the supportedstorage subsystems (RAID arrays) attached to the server/cluster. Includesinformation about tiered storage, storage pools, system drives (SDs), SDgroups, and other storage device related configuration and managementfeatures and functions.

• Snapshot Administration Guide (MK-92HNAS011)—In PDF format, thisguide provides information about configuring the server to take andmanage snapshots.

• Antivirus Administration Guide (MK-92HNAS004)—In PDF format, thisguide describes the supported antivirus engines, provides informationabout how to enable them, and how to configure the system to use them.

• Command Line Reference—Opens in a browser, and describes thecommands used to administer the system.

• Hitachi NAS Platform 3080 and 3090 G2 Hardware Reference(MK-92HNAS017)—Provides an overview of the first-generation serverhardware, describes how to resolve any problems, and replace potentiallyfaulty parts.

• Release notes—provide the most up-to-date information about the system,including new feature summaries, upgrade instructions, and fixed andknown defects.

Note: For a complete list of Hitachi NAS open source software copyrights andlicenses, see the System Access Guide.

About this document 9Deployment Guide

VMware reference documentation

Note: Links to non-HDS web sites are provided for your convenience onlyand can change without notice.

• VMware vCenter Site Recovery Manager documentation (http://www.vmware.com/support/pubs/srm_pubs.html)—provides the latestVMware documentation.

• Best Practices for Running VMware vSphere on Network-Attached Storage(NAS) (http://www.vmware.com/resources/techresources/10096 )—Provides considerations and best practices for deployment of vSphere onNFS-based storage.

Accessing product documentationProduct documentation is available on Hitachi Support Connect: https://support.hds.com/en_us/documents.html. Check this site for the most currentdocumentation, including important updates that may have been made afterthe release of the product.

Getting helpHitachi Support Connect is the destination for technical support of productsand solutions sold by Hitachi. To contact technical support, log on to HitachiSupport Connect for contact information: https://support.hds.com/en_us/contact-us.html.

Hitachi Community is a global online community for HDS customers,partners, independent software vendors, employees, and prospects. It is thedestination to get answers, discover insights, and make connections. Jointhe conversation today! Go to community.hds.com, register, and completeyour profile.

CommentsPlease send us your comments on this document to [email protected] the document title and number, including the revision level (forexample, -07), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi.

Thank you!

10 About this documentDeployment Guide

http://www.vmware.com/support/pubs/srm_pubs.html

http://www.vmware.com/support/pubs/srm_pubs.html

http://www.vmware.com/resources/techresources/10096

https://support.hds.com/en_us/documents.html

https://support.hds.com/en_us/documents.html

https://support.hds.com/en_us/contact-us.html



https://community.hds.com/welcome

https://community.hds.com/welcome

mailto:[email protected]

About this document 11Deployment Guide

1Hitachi NAS Storage Replication

Adapter overviewThis chapter provides an overview of the Hitachi NAS Storage ReplicationAdapter (referred to as HNAS SRA throughout most of this document),supported Hitachi NAS platforms and operating systems, file replicationrequirements and recommendations, and deployment prerequisites. HNASSRA is deployed within a VMware Site Recovery Manager environment usingHitachi NAS Platform-based replication. This document serves as asupplement guide, describing how to deploy Site Recovery Manager for anexisting 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 Protectedare all terms that refer to the site where the data is located that you want toreplicate; and Site B, Secondary, Destination, Protected, Recovery, andTarget, are all terms that refer to the site where the data is stored after ithas been replicated. This document uses standard HDS terminology ofSource for the site from which the data originates and Destination to whichthe data is replicated.

□ HNAS SRA overview

12 Hitachi NAS Storage Replication Adapter overviewDeployment Guide

HNAS SRA overviewTraditionally, complex distance recovery solutions require customized, site-specific scripting. Testing these solutions also often requires multiple, manualsteps, executed for each site.

Hitachi Data Systems and VMware team up to provide user-friendly siterecovery testing and failover for VMware environments with Hitachi NASStorage Replication Adapter for VMware® vCenter™ Site RecoveryManager™. The HNAS SRA connects VMware Site Recovery Manager toHitachi 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 disasterrecovery.

Figure 1 HNAS SRA disaster recovery configuration.

Hitachi NAS Storage Replication Adapter overview 13Deployment Guide

2HNAS SRA requirements

HNAS SRA is designed as a plugin to vCenter so that data recovery tasks canbe executed and managed inside the same management tool as otherVMware environment administration tasks.

General HNAS SRA Requirements

This section lists general requirements for the Site Recovery Managerconfiguration:• 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.

Additional Hardware and Software Requirements

Before deploying HNAS SRA, verify that the following requirements are inplace and configured, where appropriate.

Table 1 Required hardware and software

Item Description

HNAS SRA Release 2.2

Supported operating systems • Microsoft Windows Server 2008 R2, Windows Server 2008R2 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, Model 4040○ Hitachi NAS Platform, Model 4080○ Hitachi NAS Platform, Model 4100

• Hitachi NAS File Operating System○ Release 10.2 or later○ Release 11.x or later○ Release 12.x or later

14 HNAS SRA requirementsDeployment Guide

Item Description

• 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.5, 5.8, or 6.0• VMware vSphere Client 5.5, 5.8, or 6.0• VMware Site Recovery Manager 5.5, 5.8, or 6.0

HNAS SRA requirements 15Deployment Guide

3HNAS SRA deployment prerequisites

Before deploying HNAS SRA, you must configure each datastore that needsto be protected by the Site Recovery Manager at both the source site and thedestination site.

The following list outlines typical high-level tasks to add and configure onboth 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 StorageReplication Adapter for VMware® vCenter™ Site Recovery Manager™ ReleaseNotes before proceeding.

Refer to the following guides if you need additional information whenconfiguring HNAS:• File Services Administration Guide• Replication and Disaster Recovery Administration Guide

□ Verify sites are ready for HNAS SRA deployment

□ Configure sites for HNAS SRA deployment - overview

□ Configure sites for HNAS SRA deployment - details

16 HNAS SRA deployment prerequisitesDeployment Guide

https://hcpanywhere.hds.com/mobile/links/public/file/Hitachi%20NAS%20Storage%20Replication%20Adapter%20for%20VMware%20Site%20Recovery%20Manager%20Release%20Notes%202.1.pdf?token=H3fMzNhed2tdnXYXPZZVXw4-lp19lJ33l-knz2fOF9XJsgWWE2sN2mWqajIHss3knbmW25rO-xfDyOy1jXflXSN5i50Wf9xTBk9lcvr0nXEwUa0v7yZQnjnvnx2adff8



Verify sites are ready for HNAS SRA deploymentFollow the order of these high-level steps to best prepare both the source(protected) site and the destination (recovery) site for deploying HNAS SRA.

1. Confirm that an independent System Management Unit (SMU) isconfigured for both sites.

2. Ensure the SMUs are able to communicate with all admin EVS IPaddresses for all Hitachi NAS Platforms involved. From the SMU, go toHome > Server Settings > EVS Management to check status. (See theServer and Cluster Administration Guide for more information.)

3. Open all TCP ports (specifically for the EVS IP addresses involved withreplication communication) to allow for multiple replication streams. Thisis optional, but recommended for optimum intra-site communications.

4. Ensure NDMP services are running on both sites. From the SMU, go toHome > Data Protection > NDMP Configuration to check the status. (Seethe Backup Administration Guide for more information.)

Hitachi NAS Platform NFS and VMware configuration recommendations

Important: Hitachi Data Systems strongly recommends that you review andfollow the information in the Best Practices section of Hitachi NAS PlatformBest Practices Guide for NFS with VMware vSphere, which containsrecommendations for appropriate storage and network configurations foryour VMware HDS NFS storage environment.

Configure sites for HNAS SRA deployment - overviewThis section provides high-level tasks that must be completed on both thesource and destination sites before deploying HNAS SRA. If you prefer moredetailed steps, refer to Configure sites for HNAS SRA deployment - details onpage 22.

Preparing the source (protected) siteBefore deploying HNAS SRA, configure the source site as follows:

Procedure

1. Identify the Hitachi NAS Platform-based datastores mounted on the ESXihost 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.

2. Use the Hitachi Virtual Infrastructure Integrator plugin to quickly identifythese Hitachi NAS Platform-based datastores.

HNAS SRA deployment prerequisites 17Deployment Guide

https://hcpanywhere.hds.com/mobile/links/public/file/Hitachi%20NAS%20Platform%20Best%20Practices%20Guide%20for%20NFS%20with%20VMware%20vSphere.pdf?token=fE5uRHCPfGR6S0d0if2nz5gyfMZsyhhsyHgdC1BZZ50vao1aEWEdEWm12CeoO4bHsPQB__xYKJhCAMAIchNqCBWygiFeYOLeRNTXt3w6Gcwytaq9caOnanW0CTV7GgKh

https://hcpanywhere.hds.com/mobile/links/public/file/Hitachi%20NAS%20Platform%20Best%20Practices%20Guide%20for%20NFS%20with%20VMware%20vSphere.pdf?token=fE5uRHCPfGR6S0d0if2nz5gyfMZsyhhsyHgdC1BZZ50vao1aEWEdEWm12CeoO4bHsPQB__xYKJhCAMAIchNqCBWygiFeYOLeRNTXt3w6Gcwytaq9caOnanW0CTV7GgKh

See Hitachi NAS Virtual Infrastructure Integrator Administration Guide(MK-92HNAS003) for more information.

3. 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 filesystem SiteB-FS-1 as the target for the SiteA-DS-02 datastore on thesource site file system SiteA-FS-1.

Note: Set read-write to Access Configuration on NFS exports. Forexample: esxi-ip(rw) in NFS exports Access Configuration.

4. Create a file system for the placeholder datastore.

Note:• The placeholder datastore is not involved in the file replication

process.• Only one placeholder file system is required to be configured

per SRM server to protect multiple datastores.

5. Create an NFS export, setting Hide and Allow Access to Showsnapshots on NFS exports.For example: PHdatastore1.

6. Mount the PHdatastore1 file system on an ESXi host.7. Create a replication policy with the following steps:

a. Enter SiteA-DS-02 as the replication source.b. Enter SiteB-DS-02, which resides on the destination site, as the

target.c. Use the unmanaged server option as part of the replication policy

creation.You will be targeting datastores that are identified in Step 1 on page 17.

See the Replication and Disaster Recovery Administration Guide for moreinformation.


8. Required if the ESXi host datastores are exported from the file systemroot level: Create a file replication rule to exclude the /.jetapi directoryfrom a replication, and apply the rule to the file replication policy.

Note: Generally, best practice is that ESXi datastores are notexported at file system root level.


9. Add the replication schedule for the replication policy by applying therule, and initiate immediately.

Remember: Wait for the replication to complete before preparingthe secondary site.

10. Validate that the replication completed successfully.


Preparing the destination (recovery) site

Important: Do not create a File Replication Schedule on destination site;this schedule is not required on the destination (disaster recovery) site.

Before deploying HNAS SRA, configure the destination site as follows:

Procedure

1. Identify the file systems mounted on the ESXi hosts that store thereplicated virtual machine disks (VMDKs) and configuration files.For example: SiteB-DS-02, a datastore on the destination site filesystem SiteB-DS-02, a datastore on the destination site file systemSiteB-FS-1.

2. Disable the syslock mode on the respective file systems.3. Create a file system for the placeholder datastore.

For example: PHdatastore2.4. Create NFS exports with the following steps:

a. Set read-only to Access Configuration on NFS exports.For example: esxi-ip(ro) in NFS exports Access Configuration. Anotherexample is when specifying the individual ESXi host(s) that shouldhave access to NFS exports.

b. Set Hide and Allow Access to Show snapshots on NFS exports.5. Mount the PHdatastore2 file system on the ESXi host.

Note: Only one placeholder file system is required to beconfigured per SRM server at the recovery site.


6. For each datastore that is to be protected from the source site (A) to thedestination site (B), you create another bidirectional replication policyfrom the destination site to source site.

Remember: Do not create a File Replication Schedule on thedestination site.

For example: Create a replication policy with SiteB-DS-02 as thereplication source, and SiteA-DS-02 that resides on the source site.

7. Verify that the NDMP service is running; restart, if necessary.

8. If you prefer more detailed steps, go to the next section. If not, skipdirectly to Deploying HNAS SRA on page 30.

Configure sites for HNAS SRA deployment - detailsThis section provides detailed steps for configuring both the source anddestination sites to deploy HNAS SRA. If you prefer a high-level overview,refer to Configure sites for HNAS SRA deployment - overview on page 17.

The order in which sites are configured is flexible. The source and destinationsites can be completely configured one after the other, or each step can beperformed 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.

Creating file systemsThis section describes the high-level steps for creating the file systems. Forcomplete details, see the File Services Administration Guide. These filesystems must be created on both the source and destination sites beforedeploying HNAS SRA.

Procedure

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 SRMplaceholder datastore. For example, you might label the file system forVMware datastore SourceFS and the file system for the placeholderdatastore PHdatastore1. Set each file system with the followingconfiguration:• 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 VMwaredatastore and a file system for SRM placeholder datastore. For example,you might label the file system for VMware datastore TargetFS and thefile system for the placeholder datastore PHdatastore2.

Disabling Syslock on a file systemAll file systems must have Syslock disabled. To verify and change the status:

Procedure

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 exportsThis procedure describes the high-level steps to add NFS exports. For moredetails, see the File Services Administration Guide.

In VMware, NFS datastores are NFS exports. For HNAS SRA, ensure that thesame exports exist on the source and the destination systems.

If you plan to use consistency groups, consider the following:• You must have an equal number of NFS exports at the source file system

and at the destination file system. For example, if the source file systemhas 10 NFS exports, the destination file system must also have 10 NFSexports.

• You must have the both the NFS export name and the directory structureidentical at the protected site and at the disaster recovery site.

Procedure

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 /Countryin the Path field, and esxi-ip(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 thePath field, and esxi-ip(rw) in the Access Configuration field. Thefollowing NFS export details page shows an example of NFS exports:

In the example NFS Details page, eight NFS exports with the followingpath 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 addthe identical exports. For the destination sites, add *(ro) or esxi-ip(ro) in the Access Configuration field. The esxi-ip(ro) example isused when specifying the individual ESXi host(s), which should haveaccess to NFS exports.

Adding a ruleYou can exclude replicating one or more directories or files when adding arule 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 thatexcludes a directory or file.

Procedure

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.

4. 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 inthe path. The name may not contain any characters, but it may startor end with an asterisk (*).

• A list of files or directories to exclude from a replication. When listingfiles or directories to exclude from a replication, all items in the listmust 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. Thiskeyword can be configured when there are multiple file replication polices on


HNAS system, but not all for VMware SRM solution. Apply the rule which hasthe keyword #SRMflag into the replication policies protected by VMware SRM.

HNAS SRA allows for exclusion of specific replication policies using thekeyword #SRMflag in the Files To Exclude field. This keyword can beconfigured when there are multiple file replication policies on an HNASsystem, but not all are defined for use with the VMware SRM solution. Forconfigurations such as these, define a rule which uses the #SRMflag keywordand apply this rule to the replication policies in use by VMware SRM.

This keyword can be used along with regular directories/files exclusions.

Procedure

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.

4. 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 policyThis procedure describes the high-level tasks to add a file replication policy. Afile replication policy identifies the data source, the replication target, andoptionally a replication rule. For complete details on policies, refer to theReplication and Disaster Recovery Administration Guide.


Procedure

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 thepage.

3. Choose Not a Managed Server and then click Next.The following image illustrates an example of a policy.

4. 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 (specifyingexclusions) on page 25 and Adding a rule (#SRMflag) on page 26.

8. Log in to the destination site and repeat steps 2 - 7.


Creating a replication scheduleNote: schedules are only set on the source site.

To apply the schedule to the replication policy:

Procedure

1. Log into the SMU for the source site.2. Navigate to Home > Data Protection > File Replication.3. 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 serviceTo check that NDMP service is started:

Procedure

1. Navigate to Home > Data Protection > NDMP Configuration todisplay the NDMP Configuration page.

2. Check the Current Status in the NDMP Server Status section of thepage.Click start if the current status is stopped.

3. Repeat steps 1-2 for the destination site.


4Deploying HNAS SRA

This section provides instructions for deploying the HNAS SRA.

□ Configuring SMU permissions

□ Installing HNAS SRA

□ Configuring array managers

□ Uninstalling HNAS SRA

□ Advanced configuration options

30 Deploying HNAS SRADeployment Guide

Configuring SMU permissionsThe HNAS SRA uses file replication features of the Hitachi NAS Platform, andinteracts with the HNAS System Management Unit (SMU) to create replicationrelationships between two sites, and to connect to the HNAS nodes. To allowthe 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.

Procedure

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 byroot.

3. Enter chmod 0660 /etc/sudoers to change the permissions forthe /etc/sudoers file to 0660.

4. Enter cp /etc/sudoers /etc/sudoers_tmp to create a temporary copyof the file.

5. Enterecho “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/sudoers8. Enter chmod 0440 /etc/sudoers to reset the permissions.9. Enter exit to exit the root shell.

Deploying HNAS SRA 31Deployment Guide

Result

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 SRAStorage Replication Adapters (SRA) provide an interface to primary storagewith replication software. SRAs are vendor-specific, and need to be installedon the Site Recovery Manager (SRM) servers at both the source sites and thedestination sites. The HNAS SRA installer is available as a downloadable .msifile from Hitachi Data Systems at portal.hds.com or available from theVMware SRM download site.

To begin the installation process:

Procedure

1. Ensure that the SRM is installed.2. Download the HNAS SRA installer from VMware or the Hitachi Data

Systems support portal (https://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 softwareUpgrading from HNAS SRA v2.0 or newer is supported using the .msi filereferenced above. If upgrading from an earlier version, uninstall this versionfirst. After executing the .msi installation program, perform the followingsteps to complete the upgrade process:

Procedure

1. Download the HNAS SRA installer from VMware or the Hitachi DataSystems support portal (https://portal.hds.com).

2. Copy and install the .msi file on the SRM servers at both the source anddestination sites.

3. In previous versions, it was required that Syslock be enabled on thedestination site file system. Beginning with v2.1, this is no longer


https://portal.hds.com

necessary. Therefore, ensure that Syslock is disabled on each destinationfile system. See the topic, Disabling Syslock on a file system on page 23,for details.

4. Refresh the Devices for Array pair in the Devices tab for eachconfigured array manager. The discovery is expected to fail if thedestination site file system is in syslock state. Take it out of syslock statemake the NFS exports on destination site read only. See the topic, HNASSRA deployment prerequisites on page 16, for details.

5. Configure array managers. See the topic, Configuring array managers onpage 33, for details.

Verifying HNAS SRA installationThis section describes how to verify the HNAS SRA installation.

Procedure

1. On the Site Recovery Manager server, locate the following directory: C:\Program Files\VMware\VMware vCenter Site Recovery Manager\storage\sra

2. In the Site Recovery Manager GUI, select the SRAs tab to display thecurrently installed Storage Replication Adapters (SRAs).

3. If no SRAs are listed, click Rescan SRAs.If none are listed, then no SRA was installed on the Site RecoveryManager server. See HNAS SRA not displaying in SRM after successfulinstallation on page 50 for more information.

Configuring array managers


Procedure

1. Double-click the VMware vSphere Client icon ( ), log in to the vCenterServer, and go to Home > Site Recovery > Array Managers.

2. In the Array Manager pane, identify the protected site in which youwant to configure, right-click, and select Add Array Manager.


3. Enter a display name, select Hitachi NAS Replicator Adapter as theSRA type, and then click Next.


4. Enter the System Management Unit (SMU) and admin EVS details, andthen click Next.

Field/Item Description

SMU OS IP Address Enter the IP address of the SMU.

SMU OS Username Enter a unique user name, such as manager.

Password Enter a password for the SMU OS user name provided.

Note: The user name and password entered might bedifferent from the user name and password that is providedwhen logging in to Web Manager, the SMU GUI.


Field/Item Description

Admin EVS IP

Address

Enter the IP address of the admin EVS.

Device Exclude List 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.

Admin EVS

Username

Enter a unique user name.

Password Enter a password for the admin EVS user name provided.

5. Repeat these steps on the recovery (secondary) site.

Postrequisites

Note: After an array pair has been added, ensure you enable it.

Uninstalling HNAS SRAThis section describes how to uninstall HNAS SRA, if necessary.

Uninstall HNAS SRA using the Microsoft Windows Control Panel on both SiteRecovery Manager (SRM) servers at the source site and the destination site.

Procedure

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 optionsThis section describes advanced configuration options.


Configuring SRA when an HNAS EVS has multiple IP addressesdefined (Primary or Secondary)

If the datastore on the primary or secondary site is hosted on an HNAS EVSwith multiple IP addresses, the steps below must be followed to create asuccessful array pair during device discovery. If the configuration files arerequired but are not present, the array pair will be greyed out and havedifferent IP addresses on the protected and recovery site.

Note: A unique config.cfg file must be defined at both the primary and thesecondary 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 becreated. Please note that the config.cfg file name is case sensitive and mustconsist of all lower case letters. The path for the location of the configurationfile is represented by the variable path $Bin/config.cfg. For a typicalinstallation, this path would be C:\Program Files\VMware\VMware vCenterSite Recovery Manager\storage\sra\HNAS-SRA\config.cfg.

Each config.cfg file must contain at least one set of values, in the orderdescribed below.

POLICY_NAME Exact name of the replication policy used to replicate the VMs from the onesite to the other site. It is case sensitive and must be the first parameter ofthe set for each replication policy.

SRC_IP Source IP address to be used in the SRA workflow. This must be one of theIP addresses configured on the HNAS EVS hosting the datastore at thesource location.

DEST_IP Destination IP to be used in the SRA workflows. This must be one of the IPaddresses configured on the HNAS EVS hosting the datastore at thedestination 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=10.55.22.2• DEST_IP=10.55.82.10

Note: The POLICY_NAME, SRC_IP, and DEST_IP will be different between thetwo sites.

Add a set for each replication policy of a datastore used by SRA where thedatastore is hosted on an EVS with multiple IP addresses, as outlined in theexample above.


Note: The config.cfg file is not part of the HDS SRA Installation. If this file isneeded, you will need to create it, add the content, and write it using a texteditor such as notepad. It is important to match the format exactly includingcase and only write a ‘text’ file. Formats other than a ‘text’ file are notsupported.

Single policy to protect multiple datastores (NFS exports)This option protects multiple NFS exports on a single HNAS file system usingone file replication policy (Consistency Group). The example below protectsDS01 and DS02 on FS01 filesystem.

Source site

Note: To use this option, your consistency group must have the NFS Exportname and directory structure identical between Source site and Destinationsite.

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: esxi-ip(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) withaccess.

4. Create a third NFS Export on FS01. (NFS Export Name: DS02, NFSExport Path: /DS02 and Access Configuration: esxi-ip(rw)).

5. Create a File Replication Policy (for example, File Replication Policy nameis Rep1P).a. Source file system: FS01b. Source Directory: /c. Destination File System: FS11d. 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 site1. Create a file system (for example, FS11).


2. Create an NFS Export on FS11 (NFS Exports Name: ROOT, NFS ExportPath: / and Access Configuration: esxi-ip(ro)).

3. Create a second NFS Export on FS11 (NFS Exports Name: DS01, NFSExport Path: /DS01 and Access Configuration: esxi-ip(ro)).

Note: Use *(ro) if not specifying individual ESXi host(s) withaccess.

4. Create a third NFS Export on FS11 (NFS Export Name: DS02, NFS ExportPath: /DS02 and Access Configuration: esxi-ip(ro)).

5. Create a File Replication Policy (for example, File Replication Policy nameis Rep1S).a. Source File System: FS11b. Source Directory: /c. Destination File System: FS01d. Destination Directory: /

Note: No replication schedule is required on the destination.

Exclude specified datastores (NFS exports) from being replicatedThis option protects multiple NFS exports per a single HNAS file system byone File Replication Policy (Consistency Group), but excludes specified NFSexports. This example has three datastores (DS01, DS02, and DS03) on thesame file system. This example excludes DS02 from being replicated withoutcreating individual policies.1. Go to the source site.


2. After creating NFS Exports, create a File Replication Policy Rule (RuleName: exclusion-DS02 and Files To Exclude: /DS02) and apply the ruleto 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 tothe File Replication Policy.

Allow SRM and non-SRM based replication policies on the samesystem

In a configuration which has other replication policies that are associated witha non-VMware SRM use case, the following option allows you to identifyreplication policies that are specifically associated with SRM configuration.

In this option, 'DS01' and 'DS02' are used for VMware SRM and 'DS03' has areplication policy not associated with a VMware SRM configuration and/or ispossibly 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 theFile Replication Policy.

3. 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 theFile Replication Policy.


Exclude unnecessary VM files and/or specific VMs from beingreplicated

This option ensures that only pertinent VMware files are replicated andensuring that non essential VM level files (temp, swap files, and so on) arenot replicated. Secondly, this can be extended to remove certain VMs frombeing replicated without forcing those VMs to be relocated to other non-SRMdatastores. Note that it is required that any VM(s) excluded as part of areplication policy have been replicated at least once to the destination beforebeing 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 bereplicated, ensuring lower overall replication times for the datastore. It alsoexcludes all non-essential VMware files (*.vswp and *.nvram) across all VMs.

Note: Ensure at least one replication policy has been completed, which hasreplicated 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 replicated. This is in addition toexcluding all *.vswp and *.nvram VMware files from beingreplicated.


3. Create a File Replication Policy (for example, File Replication Policy nameRep1P) 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.


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



5Troubleshooting

This section provides information and instructions for troubleshootingconfiguration issues. When diagnosing an issue, review and provide therequired logs to Hitachi Data Systems Support Center.

For details about the available logs and those required for Hitachi DataSystems Support Center assistance, see Logging on page 47.

Note: Ensure you have reviewed the current Hitachi NAS Storage ReplicationAdapter for VMware Site Recovery Manager Release Notes for any limitationsand workarounds.

□ Checking for general SRM and SRA issues

□ Logging

□ Generating Reports

□ Error Messages

46 TroubleshootingDeployment Guide

https://hcpanywhere.hds.com/mobile/links/public/file/Hitachi%20NAS%20Storage%20Replication%20Adapter%20for%20VMware%20Site%20Recovery%20Manager%20Release%20Notes.pdf?token=eJpgeO6q9B8W5r4k5KdlbI4imWI6DJvIqwkp2UfnSZU3sp5yOZqSkfOxRToS8HQCRv5FSYIuPUwXYAlQ_6teIT4c6paH8pX9Fj6tmm932v4KNhk6lpTyqJp2BLVUipdM

https://hcpanywhere.hds.com/mobile/links/public/file/Hitachi%20NAS%20Storage%20Replication%20Adapter%20for%20VMware%20Site%20Recovery%20Manager%20Release%20Notes.pdf?token=eJpgeO6q9B8W5r4k5KdlbI4imWI6DJvIqwkp2UfnSZU3sp5yOZqSkfOxRToS8HQCRv5FSYIuPUwXYAlQ_6teIT4c6paH8pX9Fj6tmm932v4KNhk6lpTyqJp2BLVUipdM

Checking for general SRM and SRA issuesRefer to the VMware Community (http://communities.vmware.com/community/vmtn/vcenter/srm) for more information.

LoggingThis section describes how to use logging for troubleshooting purposes.

Locate SRM and SRA logs on source and destination sites in the followinglocations:• 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 ReportsThis section describes how to generate SRM operation HTML reports.

Procedure

1. From the vSphere Client, go to Home > Site Recovery > RecoveryPlans > History.

2. Identify the operation, and click Export to generate a SRM OperationHTML Report.

Error MessagesThis section lists the error messages you might see. Each topic will have apossible cause for the error and a possible resolution.

Troubleshooting 47Deployment Guide

http://communities.vmware.com/community/vmtn/vcenter/srm

http://communities.vmware.com/community/vmtn/vcenter/srm

Cannot find matching consistency group at remote site for'FS_name/Export_name'

The entire error message: "Cannot find matching consistency group atremote 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.

Resolution1. Exclude the sub-NFS export directory from file replication using a file

replication rule setting.2. If the directory needs to be replicated by file replication but not protected

by SRM, create a separate file replication policy for the sub-NFS exportand use the #SRMflag rule setting on protected devices file replicationpolicy to include it in SRM protection. HNAS SRA detects all valid SRMprotected file replication policy using the replication rule #SRMflagsetting.

Cannot unmount datastore <datastore_name> which has VMs on it:<VM_name>

The entire error message: "Error - Cannot unmount datastore<datastore_name> which has VMs on it: <VM_name> ."

Possible cause1. If a VM is not replicated by storage or it is excluded from the file

replication policy, but is protected under protection group in SRM.2. If a VM is not replicated by storage or it is excluded from the file

replication policy, and not configured for protection, but is inventoriedunder ESXi host.

Resolution

Remove the VM from protection group in SRM and from the inventory of theESXi host.

Creating protection groups error

Possible cause

Inventory mappings have not completed.

Resolution

You cannot not create protection groups if the following mappings are notcompleted:


• Resource mappings• Folder mappings• Network mappings• Placeholder datastores

Device cannot be matched to a remote peer deviceThe entire error message: "Device cannot be matched to a remote peerdevice” when forming a consistency group even though the export paths areidentical on both sites.

Possible cause• Incorrect case (uppercase/lowercase) used in export path names.• The file systems that are used as datastores are not mounted at either of

the sites.• The initial synchronization from the source (protected) site to the

destination (recovery) site was not completed, which was necessary for aproperly functioning system.

• The replication policy on either the source or the destination site istargeting an incorrect datastore.

• Bidirectional replication polices are not configured.

Resolution• Even though the export paths are identical on both sites, the exports name

must be identical. SRM validation is case-sensitive when forming aconsistency group; therefore, the device path name should be of samecase or the device pairing will fail.

• Mount the file systems, and configure the permissions for both sites. Seethe File Services Administration Guide for more information.

• Synchronize the sites. See HNAS SRA deployment prerequisites on page16 for more information.

• Review and modify the replication policy, as needed, to target the correctdatastore.

• Configure the replication polices so that bidirectional communication issupported.

Enable button in Array Manager is inactive

Possible causes• A single SMU might be used for both sites.• The array manager is configured on only one site.• An EVS on the primary and/or secondary site has more than 1 IP Address

associated with the EVS.

Resolutions• Each site requires an independent SMU.


• Ensure the array manager is configured on both sites. See Configuringarray managers on page 33 for more information.

• Additional configuration is necessary. See Configuring SRA when an HNASEVS has multiple IP addresses defined (Primary or Secondary) on page 38for instructions.

Failed to update embedded paths in virtual machine file [file_path]

Possible Cause

Failover recovery plan tries to update a file on .snapshot directory used byHNAS SRA and it does not have sufficient access permission for others.

Resolution

Select Hide and Allow Access n Show snapshots of NFS export.

File system is syslockedThe entire error message: "The filesystem [fs_name] is syslocked pleaseunlock the filesystem, omitting the devices for this policy."

Possible cause• HNAS SRA v2.1 is upgraded from HNAS SRA v2.0.• The file system on either site is syslocked.

Resolution• In HNAS SRA v2.0 you were required to enable syslock on the destination

site file system. This is no longer required in HNAS SRA v2.1.

HNAS SRA not displaying in SRM after successful installation

Possible cause

The Site Recovery Manager (SRM) cache did not refresh and displays an oldstatus.

Resolution

Click Rescan SRAs so that the SRM discovers the Hitachi NAS StorageReplication Adapter (HNAS SRA). You may need to rescan a few times beforethe SRA is displayed.

Operating system not adequate for running HNAS SRA for SRMThe entire error message: "The operating system is not adequate for runningHitachi NAS Storage Replication Adapter for VMware® vCenter™ SiteRecovery Manager™."


Possible cause• You are trying to install HNAS SRA on a non-supported operating system.

Resolution• Install HNAS SRA on a supported Windows server operating system. See

HNAS SRA requirements on page 14 for details.

SMU user does not have sufficient privilege to execute commandsThe entire error message: "SMU User does not have sufficient privilege toexecute commands on SMU."

Possible cause• SMU user is not added to /etc/sudoers in the SMU or does not have the

necessary permission to execute the requested command.

Resolution• If using SMU v11.2 or older, add SMU user to /etc/suoders file. Add the

necessary permissions as described in Configuring SMU permissions onpage 31.

SRA command 'discoverArrays' failedThe entire error message: "SRA command 'discoverArrays' failed. Storagearrays have not been configured for replication. Storage array is not properlyconfigured. Please configure the storage arrays.

Possible cause1. The replication policy is not set on either side.2. Schedule for the Replication policy on source site is not set.3. File system is in syslock state on either site.4. NFS export is not configured properly.5. Multiple replication policies exists with non-SRM/VMware without the

#SRMflag setting.

Resolution1. Create a replication policy for the file systems and devices that are part

of your disaster recovery plan. See the Replication and Disaster RecoveryAdministration Guide for more information.

2. Create a schedule for the source device.3. Disable Syslock for the file system.4. If forming a consistency group, ensure that both sites have identical NFS

exports and that they exist at both sites. The file replication policy isconfigured on root or root directory where the consistency group is beingformed. If the consistency group is being formed inside sub-NFS exports,the NFS export for root directory must exist where the replication policyis created.


5. If multiple replication policies co-exist with policies that are not takingpart in SRM or VMware solutions, all valid SRM policies must have the filereplication rule #SRMflag set. Create a file replication rule with#SRMflag, in the Files To Exclude setting. Apply the rule to all valid SRMpolicies.

Note: : #SRMflag can be added to normal exclusion rules, forexample:/VM1,*.mp3,#SRMflag.

SRA does not display datastore nameSRA discovery does not display the datastore name under Array pair deviceseven if they are mounted on the ESXi.

Possible cause• NFS Exports are added to ESXi using export path instead of export name.

Resolution• SRA discovers NFS exports that are added to ESXi using the export name

as required by SRM and not by export path. Unmount and add the NFSexport again with the export name. Then, refresh the array pairing in SRA.

SRM action timeout

Possible cause

The Storage Replication Adapter (SRA) seems to be nonfunctioning. In theSite Recovery Manager (SRM) logs, the SRA seems to be stuck, andeventually the SRM action times out.

Resolution

The SRA permissions in /etc/sudoers are not modified or are incorrect. See Configuring SMU permissions on page 31 for more information.

Test recovery failsThe entire error message is: " Test recovery fails with Error - Cannotunmount datastore <datastore_name> which has VMs on it: <VM_name> ."

Possible Cause

A VM has been excluded in File replication policy.

Resolution

Remove the VM from protection the group in SRM and from the inventory ofthe ESXi host.


Failed to access file [datastore-name] failed to unregister protectedVMs

Possible cause

A failover might have occurred if one of the hosts lost connection to aplaceholder datastore, or the datastore is not presented to all ESXi hosts.

Resolutions• Placeholder datastores are required at both the source and destination

sites. These datastores are used by the Site Recovery Manager (SRM) tostore small (approximately 1 KB) virtual machine (VM) placeholder files.Placeholder datastores can be shared by more than one host or cluster, buteach host and cluster that is used for protecting or recovering VMs needsaccess to a placeholder datastore.

• On the destination (recovery/protected) site, manually remove anyplaceholder VMs created on the host that lost connection to theplaceholder datastore. Remove the VM replication configuration thenreconfigure the replication. Reconfigure VM protection from the protectiongroup properties.

Unable to access file [unspecified filename]

Possible Cause

The owner/group of the VMware files might have changed during the failoverrecovery plan and it caused insufficient permission.

Resolution

Set either * (no_root_squash) or esxi_ip (no_root_squash) in AccessConfiguration of the NFS export and re-run the recovery plan.

VMware Tools timeout

Possible cause

VMware Tools is not installed, or is not started on the guest OS.

Resolution

Install or start VMware Tools, as needed.


Virtual machines 'GuestOS name' that are not protected by thisprotection group...

Possible cause

The virtual machines (VMs) in a protection group are not configured properly.

Resolution

Configure the VMs in a protection group, and ensure the protection status forall VMs are OK.

WFS-1 file system not supported by SRA, found a replication policyThe entire error message: " WFS-1 Filesystem not supported by SRA, found areplication policy [<policy name>] for filesystem, [<filesystem name>],formatted as WFS-1 ".

Possible cause• Datastores are configured on a non-supported file system.

Resolution• HNAS SRA does not support WFS-1 file system. Use a file system that is

formatted as WFS-2 type.



AOpen source software copyrights and

licenses

□ Perl module Net::SSH2

□ Libssh2

56 Open source software copyrights and licensesDeployment Guide

Perl module Net::SSH2Copyright (C) 2005 - 2010 by David B. Robins; all rights reserved.http://www.sisyphusion.tk/ppm/Net-SSH2.ppd

GNU GENERAL PUBLIC LICENSE

Version 1, February 1989

Copyright (C) 1989 Free Software Foundation, Inc.

59 Temple Place, Suite 330, Boston, MA 02111-1307, USA

Everyone is permitted to copy and distribute verbatim copies of this licensedocument, but changing it is not allowed.

Preamble

When we speak of free software, we are referring to freedom, not price.Specifically, the General Public License is designed to make sure that youhave the freedom to give away or sell copies of free software, that youreceive source code or can get it if you want it, that you can change thesoftware or use pieces of it in new free programs; and that you know you cando these things.

To protect your rights, we need to make restrictions that forbid anyone todeny you these rights or to ask you to surrender the rights. These restrictionstranslate to certain responsibilities for you if you distribute copies of thesoftware, or if you modify it.

We protect your rights with two steps: (1) copyright the software, and (2)offer you this license which gives you legal permission to copy, distributeand/or modify the software.

Also, for each author's protection and ours, we want to make certain thateveryone understands that there is no warranty for this free software. If thesoftware is modified by someone else and passed on, we want its recipientsto know that what they have is not the original, so that any problemsintroduced by others will not reflect on the original authors' reputations.

The precise terms and conditions for copying, distribution and modificationfollow.

GNU GENERAL PUBLIC LICENSE

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION ANDMODIFICATION

0. This License Agreement applies to any program or other work whichcontains a notice placed by the copyright holder saying it may be distributedunder the terms of this General Public License. The "Program", below, refers

Open source software copyrights and licenses 57Deployment Guide

http://www.sisyphusion.tk/ppm/Net-SSH2.ppd

to any such program or work, and a "work based on the Program" meanseither the Program or any work containing the Program or a portion of it,either verbatim or with modifications. Each licensee is addressed as "you".

1. You may copy and distribute verbatim copies of the Program's source codeas you receive it, in any medium, provided that you conspicuously andappropriately publish on each copy an appropriate copyright notice anddisclaimer of warranty; keep intact all the notices that refer to this GeneralPublic License and to the absence of any warranty; and give any otherrecipients of the Program a copy of this General Public License along with theProgram. You may charge a fee for the physical act of transferring a copy.

2. You may modify your copy or copies of the Program or any portion of it,and copy and distribute such modifications under the terms of Paragraph 1above, provided that you also do the following:

a) cause the modified files to carry prominent notices stating that youchanged the files and the date of any change; and

b) cause the whole of any work that you distribute or publish, that in wholeor in part contains the Program or any part thereof, either with or withoutmodifications, to be licensed at no charge to all third parties under the termsof this General Public License (except that you may choose to grant warrantyprotection to some or all third parties, at your option).

c) If the modified program normally reads commands interactively when run,you must cause it, when started running for such interactive use in thesimplest and most usual way, to print or display an announcement includingan appropriate copyright notice and a notice that there is no warranty (orelse, saying that you provide a warranty) and that users may redistribute theprogram under these conditions, and telling the user how to view a copy ofthis General Public License.

d) You may charge a fee for the physical act of transferring a copy, and youmay at your option offer warranty protection in exchange for a fee.

Mere aggregation of another independent work with the Program (or itsderivative) on a volume of a storage or distribution medium does not bringthe other work under the scope of these terms.

3. You may copy and distribute the Program (or a portion or derivative of it,under Paragraph 2) in object code or executable form under the terms ofParagraphs 1 and 2 above provided that you also do one of the following:

a) accompany it with the complete corresponding machine-readable sourcecode, which must be distributed under the terms of Paragraphs 1 and 2above; or,

b) accompany it with a written offer, valid for at least three years, to give anythird party free (except for a nominal charge for the cost of distribution) a


complete machine-readable copy of the corresponding source code, to bedistributed under the terms of Paragraphs 1 and 2 above; or,

c) accompany it with the information you received as to where thecorresponding source code may be obtained. (This alternative is allowed onlyfor noncommercial distribution and only if you received the program in objectcode or executable form alone.)

Source code for a work means the preferred form of the work for makingmodifications to it. For an executable file, complete source code means all thesource code for all modules it contains; but, as a special exception, it neednot include source code for modules which are standard libraries thataccompany the operating system on which the executable file runs, or forstandard header files or definitions files that accompany that operatingsystem.

4. You may not copy, modify, sublicense, distribute or transfer the Programexcept as expressly provided under this General Public License. Any attemptotherwise to copy, modify, sublicense, distribute or transfer the Program isvoid, and will automatically terminate your rights to use the Program underthis License. However, parties who have received copies, or rights to usecopies, from you under this General Public License will not have their licensesterminated so long as such parties remain in full compliance.

5. By copying, distributing or modifying the Program (or any work based onthe Program) you indicate your acceptance of this license to do so, and all itsterms and conditions.

6. Each time you redistribute the Program (or any work based on theProgram), the recipient automatically receives a license from the originallicensor to copy, distribute or modify the Program subject to these terms andconditions. You may not impose any further restrictions on the recipients'exercise of the rights granted herein.

7. The Free Software Foundation may publish revised and/or new versions ofthe General Public License from time to time. Such new versions will besimilar in spirit to the present version, but may differ in detail to address newproblems or concerns.

Each version is given a distinguishing version number. If the Programspecifies a version number of the license which applies to it and "any laterversion", you have the option of following the terms and conditions either ofthat version or of any later version published by the Free SoftwareFoundation. If the Program does not specify a version number of the license,you may choose any version ever published by the Free Software Foundation.

8. If you wish to incorporate parts of the Program into other free programswhose distribution conditions are different, write to the author to ask forpermission. For software which is copyrighted by the Free SoftwareFoundation, write to the Free Software Foundation; we sometimes make


exceptions for this. Our decision will be guided by the two goals of preservingthe free status of all derivatives of our free software and of promoting thesharing and reuse of software generally.

NO WARRANTY

9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NOWARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLELAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHTHOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRERISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITHYOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OFALL NECESSARY SERVICING, REPAIR OR CORRECTION.

10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO INWRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAYMODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BELIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE ORINABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSSOF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINEDBY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATEWITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTYHAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Libssh2Copyright (c) 2004-2007 Sara Golemon [email protected]

Copyright (c) 2005,2006 Mikhail Gusarov [email protected]

Copyright (c) 2006-2007 The Written Word, Inc.

Copyright (c) 2007 Eli Fant [email protected]

Copyright (c) 2009 Daniel Stenberg

Copyright (c) 2008, 2009 Simon Josefsson

All rights reserved.http://www.libssh2.org/

Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:• Redistributions of source code must retain the above copyright notice, this

list of conditions and the following disclaimer.





http://www.libssh2.org/

• Redistributions in binary form must reproduce the above copyright notice,this list of conditions and the following disclaimer in the documentationand/or other materials provided with the distribution.

• Neither the name of the copyright holder nor the names of any othercontributors may be used to endorse or promote products derived fromthis software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED 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 IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


IndexSymbols

#SRMflag rule 26

Aadmin EVS 33array discovery failure 51array managers

configuring 33

Bbest practices 17

Ccannot mount datastore 48–50cluster IDs 33configuring

array managers 33SMU permissions 31

Ddatastore display error 52datastores 16Device Exclude List 33disaster recovery plan 51discoverArrays failed 51

EEVS 33

Ffailover 48, 49failover error 50, 53file system 23firmware 14

Gguest OS 53, 54

Hhigh-level preparation steps 17Hitachi NAS Virtual Infrastructure Integrator 16HNAS reference documentation 8HUS 14

Iinstalling SRA 32inventory mappings 48

Mmsi file 32

NNDMP 17NFS 14NFS exports 24

Ooperating systems supported 14

Ppeer array set to unknown 33permissions 31placeholder datastores 16, 53preparing sites for SRA 17protection group 54protection group error 48protocol support 14

62 IndexDeployment Guide

Rreference documentation

HNAS 8reference documentation®

VMware 10replication policy 16, 51replication schedule 16rescan SRAs 33root shell 31rules 25

Ssite preparation 17SMU 17, 33

configuring permissions 31software

how to upgrade 32SRA inactive 52SRA install directory path 33SRA not displaying in SRM 50SRAs tab 33SRM action times out 52SRM cache 50SRM Operation HTML Report 47sudoers 31, 52supported

hardware 14storage arrays 14

syslock error 50

TTCP 17temporary files 17troubleshooting 46

Uunable to access file error 53uninstalling SRA 37upgrade

software 32

VV2I 16vCenter Server 33verifying SRA installation 33VM placeholder files 50, 53VMware reference documentation 10VMware Tools timeout 53VSP 14vSphere Client icon 33

WWFS-1 error 50, 51, 54

Index 63Deployment Guide

Deployment Guide

MK-92HNAS035-05

Documents

Hitachi NAS Storage Replication Adapter for … · Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide Release 2.2 ... //portal.hds.com