Hitachi NAS Storage Replication Adapter for VMware … VMware Site Recovery Manager Deployment Guide Release 2.3 ... Active Directory, ActiveX, Bing, ... information for the Hitachi

Hitachi NAS Platform

Hitachi NAS Storage Replication Adapterfor VMware Site Recovery Manager

Deployment GuideRelease 2.3

MK-92HNAS035-06

© 2011, 2016 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronicor mechanical, including copying and recording, or stored in a database or retrieval system forcommercial purposes without the express written permission of Hitachi, Ltd., or Hitachi (collectively“Hitachi”). Licensee may make copies of the Materials provided that any such copy is: (i) created asan essential step in utilization of the Software as licensed and is used in no other manner; or (ii) usedfor archival purposes. Licensee may not make any other copies of the Materials. “Materials” meantext, data, photographs, graphics, audio, video and documents.

Hitachi reserves the right to make changes to this Material at any time without notice and assumesno responsibility for its use. The Materials contain the most current information available at the timeof publication.

Some of the features described in the Materials might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi at https://support.hds.com/en_us/contact-us.html.

Notice: Hitachi products and services can be ordered only under the terms and conditions of theapplicable Hitachi agreements. The use of Hitachi products is governed by the terms of youragreements with Hitachi.

By using this software, you agree that you are responsible for:1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from

authorized employees and other individuals to access relevant data; and2. Verifying that data continues to be held, retrieved, deleted, or otherwise processed in

accordance with relevant laws.

Notice on Export Controls. The technical data and technology inherent in this Document may besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility to obtainlicenses to export, re-export, or import the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.

AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON,FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli,z/OS, z9, z10, z13, z/VM, and z/VSE are registered trademarks or trademarks of InternationalBusiness Machines Corporation.

Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo,Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight,SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vistaare registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen shots arereprinted with permission from Microsoft Corporation.

All other trademarks, service marks, and company names in this document or website are propertiesof their respective owners.

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

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

Contents

1 Overview..........................................................................................9About Hitachi NAS Storage Replication Adapter........................................................ 10Terminology...........................................................................................................10Typical SRA disaster recovery configuration..............................................................10

2 System requirements.......................................................................13

3 Deployment prerequisites............................................................... 15Confirm sites readiness for SRA deployment.............................................................16Configure sites for SRA deployment - overview.........................................................16

Preparing the source (protected) site................................................................. 16Preparing the destination (recovery) site............................................................ 19

Configure sites for SRA deployment - details............................................................ 21Creating file systems ........................................................................................21

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

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

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

4 Deploying SRA ............................................................................... 29Configuring SRA permissions...................................................................................30Installing Hitachi NAS Storage Replication Adapter....................................................31

Upgrading SRA software....................................................................................31Verifying SRA installation ..................................................................................32

Configuring array managers....................................................................................32Uninstalling SRA.....................................................................................................35Advanced configuration options...............................................................................35

Configuring SRA when an Hitachi NAS EVS has multiple IP addresses defined(Primary or Secondary)..................................................................................... 35


Single policy to protect multiple datastores (NFS exports)....................................37Exclude specified datastores (NFS exports) from being replicated.........................38Allow SRM and non-SRM based replication policies on the same system................39Exclude unnecessary VM files and/or specific VMs from being replicated............... 39

5 Troubleshooting.............................................................................. 43Checking for general SRM and SRA issues................................................................44Log locations......................................................................................................... 44Generating Reports................................................................................................ 44Error Messages...................................................................................................... 44

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

A Open source software copyrights and licenses...................................53Perl module Net::SSH2........................................................................................... 54Libssh2..................................................................................................................57

Index..................................................................................................59


About this documentThis document provides deployment, implementation, and troubleshootinginformation for the Hitachi NAS Storage Replication Adapter for VMwarevCenter Site Recovery Manager SRA) for Hitachi NAS Storage ReplicationAdapter for VMware 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 vCenterSite 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 to Hitachi NASPlatforms, which supplements Best Practices for Running VMware vSphereon Network-Attached Storage (NAS).

• Backup Administration Guide (MK-92HNAS007) Provides information aboutconfiguring the server to work with NDMP, and making and managingNDMP backups.

• Replication and Disaster Recovery Administration Guide (MK-92HNAS009)Provides information about replicating data using file-based replication andobject-based replication, provides information on setting up replicationpolicies and schedules, and using replication features for disaster recoverypurposes.

• System Access Guide (MK-92HNAS014) Explains how to log in to thesystem, provides information about accessing the NAS server/cluster CLIand the SMU CLI, and provides information about the documentation, help,and search capabilities available in the system.

• Server and Cluster Administration Guide (MK-92HNAS010) Providesinformation about administering servers, clusters, and server farms.Includes information about licensing, name spaces, upgrading firmware,

About this document 5Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

monitoring servers and clusters, the backing up and restoringconfigurations.

• Storage Subsystem Administration Guide (MK-92HNAS012) Providesinformation about managing the supported storage subsystems (RAIDarrays) attached to the server/cluster. Includes information about tieredstorage, storage pools, system drives (SDs), SD groups, and other storagedevice related configuration and management features and functions.

• Network Administration Guide (MK-92HNAS008) Provides informationabout the server's network usage, and explains how to configure networkinterfaces, IP addressing, name and directory services.

• File Services Administration Guide (MK-92HNAS006) Explains about filesystem formats, and provides information about creating and managingfile systems, and enabling and configuring file services (file serviceprotocols).

• Data Migrator Administration Guide (MK-92HNAS005) Provides informationabout the Data Migrator feature, including how to set up migration policiesand schedules.

• Storage System User Administration Guide (MK-92HNAS012) Explains usermanagement, including the different types of system administrator, theirroles, and how to create and manage these users.

• Snapshot Administration Guide (MK-92HNAS011) Provides informationabout configuring the server to take and manage snapshots.

• Antivirus Administration Guide (MK-92HNAS004) Describes the supportedantivirus engines, provides information about how to enable them, andhow to configure the system to use them.

• Command Line Reference --The Command Line Reference providesinformation on the commands used to manage your system, and includesrelevant information on the operation of your hardware and software.Depending on the model of your server or cluster node, refer to theCommand Line Reference that is appropriate for your system.

• Hitachi NAS Platform 3080 and 3090 G2 Hardware Reference(MK-92HNAS017) Provides an overview of the second-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.

VMware reference documentation

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

6 About this documentHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

• 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) providesconsiderations and best practices for deployment of vSphere on NFS-basedstorage.

Accessing product documentationProduct user documentation is available on Hitachi Data Systems SupportConnect: https://knowledge.hds.com/Documents. Check this site for themost current documentation, including important updates that may havebeen made after the 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!

About this document 7Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment 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://knowledge.hds.com/Documents

https://knowledge.hds.com/



https://community.hds.com/welcome

https://community.hds.com/welcome

mailto:[email protected]

8 About this documentHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

1Overview

This chapter provides an overview of the Hitachi NAS Storage ReplicationAdapter.

□ About Hitachi NAS Storage Replication Adapter

□ Terminology

□ Typical SRA disaster recovery configuration

Overview 9Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

About Hitachi NAS Storage Replication AdapterTraditionally, complex distance recovery solutions require customized, site-specific scripting. Testing these solutions also often requires multiple, manualsteps, executed for each site.

Hitachi and VMware team up to provide user-friendly site recovery testingand failover for VMware environments with Hitachi NAS Storage ReplicationAdapter. The SRA product connects VMware vCenter Site Recovery Manager( SRM) product to Hitachi NAS Platform-based replication.

Note: The Hitachi NAS Storage Replication Adapter product is referred to asSRA throughout most of this document.

The SRA software is deployed within a SRM environment using Hitachi NASPlatform-based replication. This document serves as a supplement guide,describing how to deploy SRM for an existing remote replication solution.

The SRM is a host-based interface with intelligence regarding:• VMware virtual machines and virtual disks.• The association of the virtual machines and storage.

TerminologyHitachi and VMware sometimes use different terminology for the sameconcept. When referring to storage replication, Site A, Primary, Source, andProtected are all terms that refer to the site where the data is located thatyou want to replicate; and Site B, Secondary, Destination, Protected,Recovery, and Target, are all terms that refer to the site where the data isstored after it has been replicated. This document uses standard HDSterminology of Source for the site from which the data originates andDestination to which the data is replicated.

Typical SRA disaster recovery configurationThe following figure shows a typical SRA configuration for disaster recovery.

10 OverviewHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

Overview 11Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

12 OverviewHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

2System requirements

The SRA product is designed as a plugin to the VMware vCenter product sothat data recovery tasks can be executed and managed inside the samemanagement tool used for other VMware environment administration tasks.

VMware vCenter Site Recovery Manager ( SRM) configurationrequirements:• Two vCenter servers: one per site• Two SRA servers: one per site• Two configured Hitachi NAS Platform sites: one as a source site and one as

a destination site• Two externally configured System Management Unit s (SMUs): one for

each NAS Platform site

Additional Hardware and Software Requirements

Before deploying SRA, verify that the following requirements are in place andconfigured, where appropriate.

Item Description

SRA Release 2.3

Supported operating systems • Microsoft Windows Server 2008 R2, Windows Server 2008R2 SP1, Windows Server 2008 SP2 (64-bits)

• Microsoft Windows Server 2012 (64-bits)

NAS Platform infrastructure • Gateway:○ Hitachi NAS Platform, Model 3080○ Hitachi NAS Platform, Model 3090○ Hitachi NAS Platform 4040○ Hitachi NAS Platform 4080○ Hitachi NAS Platform 4100

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

• Hitachi NAS File Operating System licenses○ Replication○ File Clone

• External SMU

System requirements 13Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

Item Description

○ Version to match corresponding Hitachi NAS FileOperating System listed above

• Hitachi Virtual Storage Platform (VSP G400, VSP G600, andVSP G800) fitted with NAS modules○ Internal or external SMU○ NAS File OS 12.6 or later

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 G400, VSP G600,

VSP G800, and VSP G1000)

Protocol NFS

VMware infrastructure • VMware vCenter Site Recovery Manager 5.5, 5.8, 6.0, 6.1,or 6.5

14 System requirementsHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

3Deployment prerequisites

Before deploying Hitachi NAS Storage Replication Adapter, you mustconfigure each datastore that needs to be protected by the SRM software atboth the source site and the destination 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 Hitachi NAS:• File Services Administration Guide• Replication and Disaster Recovery Administration Guide

□ Confirm sites readiness for SRA deployment

□ Configure sites for SRA deployment - overview

□ Configure sites for SRA deployment - details

Deployment prerequisites 15Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment 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



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

1. Confirm that an independent SMU is configured for both sites.2. Ensure the SMUs are able to communicate with all admin EVS IP

addresses for all Hitachi NAS Platforms involved. From the SMU interface,NAS Manager, go to Home > Server Settings > EVS Management tocheck status. (See the Server and Cluster Administration Guide for moreinformation.)

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 NAS Manager,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

Important: Hitachi strongly recommends that you review and follow theinformation in the Best Practices section of Hitachi NAS Platform BestPractices Guide for NFS with VMware vSphere, which containsrecommendations for appropriate storage and network configurations foryour VMware Hitachi NFS storage environment.

Configure sites for SRA deployment - overviewThis section provides high-level tasks that must be completed on both thesource and destination sites before deploying SRA.

If you prefer more detailed steps, refer to Configure sites for SRA deployment- details on page 21.

Preparing the source (protected) siteBefore you deploy 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.See Hitachi Virtual Infrastructure Integrator Administration Guide(MK-92HNAS003) for more information.

16 Deployment prerequisitesHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment 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

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 Identify theHitachi NAS Platform-based datastores mounted on the ESXi host orcluster to be protected on the source site. For example: SiteA-DS-02, adatastore on the source site file system SiteA-FS-1. on page 16.

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) siteBefore you deploy SRA, configure the destination site as follows:

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


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 SRA on page 29.

Configure sites for SRA deployment - detailsThis section provides detailed steps for configuring both the source anddestination sites to deploy SRA.

If you prefer a high-level overview, refer to Configure sites for SRAdeployment - overview on page 16.

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 systemsFollow these high-level steps for creating the file systems.

For complete details, see the File Services Administration Guide. These filesystems must be created on both the source and destination sites beforedeploying SRA. This section describes the high-level steps for creating the filesystems.

Procedure

1. Log into the NAS Manager (SMU user interface) 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 placeholder


datastore 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 (Hitachi

NAS OS v11.0 and later).• Set the Block Size. You can select either option, but best practice is

to set it to 4 KB.3. Log into the NAS Manager for the destination site and repeat step 2.

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

Procedure

1. To verify and change the status, log in to the NAS Manager (SMU userinterface) for the source site.

2. Navigate to Home > Storage Management > File System to open theFile System page.

3. Select the file system from the list and then click Details to display theFile System Details page.

4. Check the current status of Syslock. If the status is enabled, clickDisable.

5. Click OK.6. Repeat steps 2 - 5 to disable Syslock on the destination site.

Adding NFS exportsFollow these high-level steps to add NFS exports.

For more details, see the File Services Administration Guide.

In VMware, NFS datastores are NFS exports. For Hitachi NAS SRA, ensurethat the same 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 NAS Manager (SMU user interface) 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 NAS Manager for the destination site and repeat steps 2 - 5to add the identical exports. For the destination sites, add *(ro) oresxi-ip(ro) in the Access Configuration field. The esxi-ip(ro)example is used when specifying the individual ESXi host(s), whichshould have access 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)Follow these high-level steps that are required to add a rule that excludes adirectory or file.

Procedure

1. Log in to the NAS Manager (SMU user interface) 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 NAS Manager for the destination site and repeat steps 2 -

5.

Adding a rule (#SRMflag)The SRA product includes the keyword #SRMflag for the Files to Excludefield.

This keyword can be configured when there are multiple file replicationpolices on the Hitachi NAS system, but not all for VMware SRM solution.Apply the rule that has the keyword #SRMflag into the replication policiesprotected by VMware SRM.

Hitachi NAS 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 Hitachi NASsystem, 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 NAS Manager (SMU user interface) 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 NAS Manager 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.

A file 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 24 and Adding a rule (#SRMflag) on page 25.

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

Creating a replication scheduleTo apply the schedule to the replication policy:

Note: Schedules are only set on the source site.

Procedure

1. Log into the NAS Manager (SMU user interface) 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 performed 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 SRA

This chapter provides instructions for deploying the Hitachi NAS StorageReplication Adapter.

□ Configuring SRA permissions

□ Installing Hitachi NAS Storage Replication Adapter

□ Configuring array managers

□ Uninstalling SRA

□ Advanced configuration options

Deploying SRA 29Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

Configuring SRA permissionsThe SRA software uses the file replication features of the Hitachi NASPlatform, and interacts with the SMU to create replication relationshipsbetween two sites, and to connect to the nodes. To permit the SRA softwareto run the required commands, you must update the /etc/sudoers file on allof the 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

Hitachi NAS node. An embedded SMU is not supported.

Procedure

1. Using SSH software, log in to the NAS Manager 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.

30 Deploying SRAHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

ResultCLI 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 Hitachi NAS Storage Replication AdapterThe Storage Replication Adapters (SRA) provide an interface to primarystorage with replication software.

The Storage Replication Adapters (SRA) provide an interface to primarystorage with replication software. SRAs are vendor-specific, and need to beinstalled on the VMware vCenter Site Recovery Manager ( SRM) servers atboth the source sites and the destination sites. The SRA installer is availableas a downloadable .msi file from Hitachi at portal.hds.com or availablefrom the VMware SRM download site.

Procedure

1. Ensure that the SRM is installed.2. Download the SRA installer from VMware or the Hitachi 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 Hitachi NAS SRA v2.0 or newer is supported using the .msifile referenced above. If upgrading from an earlier version, uninstall thisversion first. After executing the .msi installation program, perform thefollowing steps to complete the upgrade process:

Procedure

1. Download the Hitachi NAS 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 22,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, Deployment prerequisites on page 15, for details.

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

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

Procedure

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

2. In the SRMGUI, select the SRAs tab to display the currently installedStorage 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 SRA not displaying in SRM after successfulinstallation on page 48 for more information.

Configuring array managersFollow this procedure to add array managers and arrays.

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 Controller/Admin EVSdetails, and then click Next.

Field/Item Description

SMU IP Address Enter the IP address of the SMU.

SMU 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 isprovided when logging in to Web Manager, the SMU GUI.

Controller/Admin EVS IP

Address

Enter the IP address of the Controller/Admin EVS.

File System Exclude List Enter a list of file systems or volumes to exclude separated by a

comma for multiple values. (Optional)


Field/Item Description

Controller/Admin EVS

Username

Enter a unique user name.

Password Enter a password for the Controller/Admin EVS user name

provided.

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

Next steps

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

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

Uninstall the SRA software using the Microsoft Windows Control Panel on bothSite Recovery Manager ( SRM) servers at the source site and the destinationsite.

Procedure

1. From the SRM server at the source site, go to Start > Control Panel >Programs > Uninstall a program.

2. Right-click SRA, and select Uninstall.3. Repeat for the destination site.

Advanced configuration optionsThis section describes advanced configuration options.

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

If the datastore on the primary or secondary site is hosted on an Hitachi NASEVS with multiple IP addresses, follow the steps in this section to create asuccessful array pair during device discovery. If the configuration files are


required but are not present, the array pair will be grayed 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, create a file name config.cfg . Notethat the config.cfg file name is case sensitive and must consist of all lowercase letters. The path for the location of the configuration file is representedby the variable path $Bin/config.cfg. For a typical installation, this path wouldbe 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 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 Hitachi NAS 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 Hitachi NAS EVS hosting the datastore at thedestination location.

The following example shows the contents of a config.cfg file for a singlepolicy 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.

Note: The config.cfg file is not part of the Hitachi SRA Installation. If this fileis needed, you 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 Hitachi NAS file systemusing one file replication policy (Consistency Group). The example belowprotects DS01 and DS02 on FS01 filesystem.

Source site

Note: This option requires that your consistency group 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 Export

Path: / and Access Configuration: esxi-ip(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) 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 Hitachi NAS file systemby one File Replication Policy (Consistency Group), but excludes specified NFSexports.

This example has three datastores (DS01, DS02, and DS03) on the same filesystem. This example excludes DS02 from being replicated without creatingindividual 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 ruleto the File Replication Policy.

3. Go to the destination site.


4. After creating NFS Exports, create a File Replication Policy Rule (RuleName: 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 andensures that non-essential VM level files (temp, swap files, and so on) arenot replicated.


Additionally, the option can be extended to remove certain VMs from beingreplicated without forcing those VMs to be relocated to other non-SRMdatastores. However, any VM(s) excluded as part of a replication policy musthave been replicated at least once to the destination before being excludedvia 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 chapter provides information and instructions for troubleshootingconfiguration issues.

When diagnosing an issue, review and provide the required logs to HitachiData Systems Support Center.

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

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

□ Log locations

□ Generating Reports

□ Error Messages

Troubleshooting 43Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment 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 for more information.

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

Log locationsWhen issues occur, collect the logs as needed.

Locate the SRM and SRA logs on source and destination sites in the followinglocation: For Windows 2008 and 2012: C:\ProgramData\VMware\VMwarevCenter Site Recovery Manager\Logs\

Locate the SRA 2.3 log files in the following location: For SRM 5.5, 5.8, and6.x: <Site Recovery Manager Installation directory>\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.

XCopyFile Failed in CopySRAThe entire error message: "XCopyFile Failed in CopySRA".

44 TroubleshootingHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

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

Possible cause

The user who ran the installer has insufficient permissions to copy the filesinto SRM directory.

Resolution

Run the HNAS-Installer by using the local built-in Administrator or performthe following steps for a user with Domain Administrator permissions:1. Login to the system with a user who is a part of Administrators domain.2. Right-click the installer.3. Select the Compatibility tab.4. Check Run this program in compatibility mode for.5. Select Previous version of Windows.

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. Hitachi NAS Storage ReplicationAdapter detects all valid SRM protected file replication policies using thereplication rule #SRMflag setting.

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 errorThe error message can vary.

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 Deployment prerequisites on page 15 for moreinformation.


• 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 Configuring

array managers on page 32 for more information.• Additional configuration is necessary. See Configuring SRA when an Hitachi

NAS EVS has multiple IP addresses defined (Primary or Secondary) onpage 35 for 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 byHitachi NAS 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• Hitachi NAS SRA v2.1 is upgraded from Hitachi NAS SRA v2.0.• The file system on either site is syslocked.

Resolution• In Hitachi NAS SRA v2.0 you were required to enable syslock on the

destination site file system. This is no longer required in Hitachi NAS SRAv2.1.


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 SRA. You may need torescan a few times before the SRA is displayed.

Operating system not adequate for running SRA for SRMThe entire error message: "The operating system is not adequate for runningHitachi NAS Storage Replication Adapter for VMware vCenter Site RecoveryManager."

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

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

requirements on page 13 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 SRA permissions onpage 30.

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 SRA permissions on page 30 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• SRA does not support WFS-1 file system. Use a file system that is

formatted as WFS-2 type.



AOpen source software copyrights and

licensesThis section lists the Open Source software copyrights and licenses forsoftware used by the Hitachi NAS Storage Replication Adapter product.

□ Perl module Net::SSH2

□ Libssh2

Open source software copyrights and licenses 53Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment 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

54 Open source software copyrights and licensesHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment 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.


IndexA

admin EVS 32array

add array manager 32array discovery failure 48array managers

configuring 32

Bbest practices 16

Ccannot mount datastore 47cluster IDs 32configuration

advanced options 35allow replication policies 39exclude unnecessary files or VMs 39protect multiple datastores 37protect NFS exports 37

configuringarray managers 32

Controller/Admin EVS 32

Ddatastore

configurationadvanced options

exclude from replication 38exclude from replication 38

datastore display error 49datastores 15deploy SRA 29Device Exclude List 32disable Syslok 22disaster recovery plan 48discoverArrays failed 48

Eenable NDMP service 27error message

cannot mount datastore 45, 46failover 45, 46inventory mappings 46protection group error 46XCopyFile failed 44

EVS 32

Ffailover error 47, 50file replication policy 26file system 21

disable Syslok 22firmware 13

Gguest OS 51

Hhigh-level preparation steps 16Hitachi NAS Virtual Infrastructure Integrator 15HNAS reference documentation 5HUS 13

Iinstall

verify SRA 32installing SRA 31

Llicense

Libssh2 57Perl module Net::SSH2 54

logslocation 44

Index 59Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

Mmsi file 31multiple datastores

policy to protect 37

NNAS Manager

configuring permissions 30SMU 30

NDMP 16NDMP service 27NFS 13NFS export

exclude from replication 38NFS exports 22

policy to protect 37

Oopen source copyrights and licenses 53operating systems supported 13

Ppeer array set to unknown 32permissions 30placeholder datastores 15, 50policy

protect multiple datastores 37protect NFS exports 37replication 26replication on same system 39

preparing sites for SRA 16protection group 51protocol support 13

Rreference documentation

HNAS 5VMware 6

replicationexclude

datastores 38NFS exports 38

exclude files or VMs 39replication policy 15, 26, 48replication schedule 15

create 27rescan SRAs 32root shell 30rules 24

add#SRMflag 25specify exclusions 24

Sschedule

replication 27service

NDMP 27site configuration details 21site configuration overview 16site preparation 16SMU 16, 32

configuring permissions 30SMU permissions 30software

how to upgrade 31SRA

deploy 29disaster recovery configuration 10install 31overview 9, 10uninstall 35verify install 32

SRA inactive 49SRA install directory path 32SRA not displaying in SRM 48SRAs tab 32SRM action times out 49SRM cache 48SRM Operation HTML Report 44sudoers 30, 49supported

hardware 13storage arrays 13

syslock error 47Syslok

disable 22

TTCP 16temporary files 16terminology 10troubleshooting 43

error messages 44general SRM and SRA issues 44generating reports 44logs 44

Uunable to access file error 50uninstalling SRA 35upgrade

software 31

VV2I 15vCenter Server 32verifying SRA installation 32

60 IndexHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

VM placeholder files 47, 50VMware reference documentation 6VMware Tools timeout 51VSP 13vSphere Client icon 32

WWFS-1 error 48, 51

Index 61Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

62 IndexHitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide

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

MK-92HNAS035-06