Hitachi NAS Storage Replication Adapter for VMware Site Recovery

Hitachi NAS Platform
Hitachi NAS Storage Replication Adapter
for VMware Site Recovery Manager
Deployment Guide
Release 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, electronic
or mechanical, including copying and recording, or stored in a database or retrieval system for
commercial 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 as
an essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used
for archival purposes. Licensee may not make any other copies of the Materials. “Materials” mean
text, data, photographs, graphics, audio, video and documents.
Hitachi reserves the right to make changes to this Material at any time without notice and assumes
no responsibility for its use. The Materials contain the most current information available at the time
of publication.
Some of the features described in the Materials might not be currently available. Refer to the most
recent product announcement for information about feature and product availability, or contact
Hitachi 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 the
applicable Hitachi agreements. The use of Hitachi products is governed by the terms of your
agreements 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; and
2. 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 be
subject to U.S. export control laws, including the U.S. Export Administration Act and its associated
regulations, and may be subject to export or import regulations in other countries. Reader agrees to
comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain
licenses 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 International
Business 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 Vista
are registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen shots are
reprinted with permission from Microsoft Corporation.
All other trademarks, service marks, and company names in this document or website are properties
of their respective owners.
2
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
Contents
1 Overview..........................................................................................9
About Hitachi NAS Storage Replication Adapter........................................................ 10
Terminology...........................................................................................................10
Typical SRA disaster recovery configuration.............................................................. 10
2 System requirements.......................................................................13
3
Deployment prerequisites............................................................... 15
Confirm sites readiness for SRA deployment.............................................................16
Configure sites for SRA deployment - overview.........................................................16
Preparing the source (protected) site................................................................. 16
Preparing the destination (recovery) site............................................................ 19
Configure sites for SRA deployment - details............................................................ 21
Creating file systems ........................................................................................21
Disabling Syslock on a file system.................................................................22
Adding NFS exports.......................................................................................... 22
Adding a rule....................................................................................................24
Adding a rule (specifying exclusions)............................................................ 24
Adding a rule (#SRMflag)............................................................................ 25
Adding a file replication policy........................................................................... 26
Creating a replication schedule.......................................................................... 27
Enabling NDMP service......................................................................................27
4 Deploying SRA ............................................................................... 29
Configuring SRA permissions...................................................................................30
Installing Hitachi NAS Storage Replication Adapter....................................................31
Upgrading SRA software....................................................................................31
Verifying SRA installation ..................................................................................32
Configuring array managers.................................................................................... 32
Uninstalling SRA.....................................................................................................35
Advanced configuration options...............................................................................35
Configuring SRA when an Hitachi NAS EVS has multiple IP addresses defined
(Primary or Secondary)..................................................................................... 35
3
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
Single policy to protect multiple datastores (NFS exports)....................................37
Exclude specified datastores (NFS exports) from being replicated.........................38
Allow SRM and non-SRM based replication policies on the same system................39
Exclude unnecessary VM files and/or specific VMs from being replicated............... 39
5 Troubleshooting.............................................................................. 43
Checking for general SRM and SRA issues................................................................44
Log locations......................................................................................................... 44
Generating Reports................................................................................................ 44
Error Messages...................................................................................................... 44
XCopyFile Failed in CopySRA..............................................................................44
Cannot find matching consistency group at remote site for 'FS_name/Export_name'
....................................................................................................................... 45
Cannot unmount datastore <datastore_name> which has VMs on it: <VM_name>
....................................................................................................................... 45
Creating protection groups error........................................................................ 46
Device cannot be matched to a remote peer device ........................................... 46
Enable button in Array Manager is inactive......................................................... 47
Failed to update embedded paths in virtual machine file [file_path]......................47
File system is syslocked ....................................................................................47
SRA not displaying in SRM after successful installation.........................................48
Operating system not adequate for running SRA for SRM.................................... 48
SMU user does not have sufficient privilege to execute commands....................... 48
SRA command 'discoverArrays' failed................................................................. 48
SRA does not display datastore name ................................................................49
SRM action timeout ..........................................................................................49
Test recovery fails.............................................................................................50
Failed to access file [datastore-name] failed to unregister protected VMs.............. 50
Unable to access file [unspecified filename] .......................................................50
VMware Tools timeout.......................................................................................51
Virtual machines 'GuestOS name' that are not protected by this protection group...
....................................................................................................................... 51
WFS-1 file system not supported by SRA, found a replication policy .....................51
A Open source software copyrights and licenses...................................53
Perl module Net::SSH2........................................................................................... 54
Libssh2..................................................................................................................57
Index..................................................................................................59
4
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
About this document
This document provides deployment, implementation, and troubleshooting
information for the Hitachi NAS Storage Replication Adapter for VMware
vCenter Site Recovery Manager SRA) for Hitachi NAS Storage Replication
Adapter for VMware vCenter™ Site Recovery Manager™.
Intended audience
This document is intended for VMware and Hitachi NAS Platform storage
administrators who are involved in the deployment of the VMware vCenter
Site Recovery Manager. Familiarity with the VMware vSphere environments,
ESX servers, vCenter Servers, and the vSphere Client is assumed. You also
require a working knowledge of storage network technology, specifically with
the Hitachi NAS Platform and its interactions with VMware environments.
A full analysis to determine the specific bandwidth and redundancy
requirements of the environment you intend to replicate must be conducted
by HDS Global Solutions Services in its Remote Copy Planning and Design
Service. This service provides you with a high-level design for your distance
replication solution and a detailed analysis of workload and performance
characteristics to help you support potentially expensive bandwidth decisions.
Hitachi NAS Platform reference documentation
• Hitachi NAS Platform Best Practices Guide for NFS with VMware vSphere
(MK-92HNAS028) Provides VMware best practices specific to Hitachi NAS
Platforms, which supplements Best Practices for Running VMware vSphere
on Network-Attached Storage (NAS).
• Backup Administration Guide (MK-92HNAS007) Provides information about
configuring the server to work with NDMP, and making and managing
NDMP backups.
• Replication and Disaster Recovery Administration Guide (MK-92HNAS009)
Provides information about replicating data using file-based replication and
object-based replication, provides information on setting up replication
policies and schedules, and using replication features for disaster recovery
purposes.
• System Access Guide (MK-92HNAS014) Explains how to log in to the
system, provides information about accessing the NAS server/cluster CLI
and the SMU CLI, and provides information about the documentation, help,
and search capabilities available in the system.
• Server and Cluster Administration Guide (MK-92HNAS010) Provides
information about administering servers, clusters, and server farms.
Includes information about licensing, name spaces, upgrading firmware,
About this document
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
5
•
•
•
•
•
•
•
•
•
•
monitoring servers and clusters, the backing up and restoring
configurations.
Storage Subsystem Administration Guide (MK-92HNAS012) Provides
information about managing the supported storage subsystems (RAID
arrays) attached to the server/cluster. Includes information about tiered
storage, storage pools, system drives (SDs), SD groups, and other storage
device related configuration and management features and functions.
Network Administration Guide (MK-92HNAS008) Provides information
about the server's network usage, and explains how to configure network
interfaces, IP addressing, name and directory services.
File Services Administration Guide (MK-92HNAS006) Explains about file
system formats, and provides information about creating and managing
file systems, and enabling and configuring file services (file service
protocols).
Data Migrator Administration Guide (MK-92HNAS005) Provides information
about the Data Migrator feature, including how to set up migration policies
and schedules.
Storage System User Administration Guide (MK-92HNAS012) Explains user
management, including the different types of system administrator, their
roles, and how to create and manage these users.
Snapshot Administration Guide (MK-92HNAS011) Provides information
about configuring the server to take and manage snapshots.
Antivirus Administration Guide (MK-92HNAS004) Describes the supported
antivirus engines, provides information about how to enable them, and
how to configure the system to use them.
Command Line Reference --The Command Line Reference provides
information on the commands used to manage your system, and includes
relevant information on the operation of your hardware and software.
Depending on the model of your server or cluster node, refer to the
Command 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 server
hardware, describes how to resolve any problems, and replace potentially
faulty parts.
Release notes provide the most up-to-date information about the system,
including new feature summaries, upgrade instructions, and fixed and
known defects.
Note: For a complete list of Hitachi NAS open source software copyrights and
licenses, see the System Access Guide.
VMware reference documentation
Note: Links to non-HDS web sites are provided for your convenience only
and can change without notice.
6
About this document
Hitachi 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 latest
VMware 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 on NFS-based
storage.
Accessing product documentation
Product user documentation is available on Hitachi Data Systems Support
Connect: https://knowledge.hds.com/Documents. Check this site for the
most current documentation, including important updates that may have
been made after the release of the product.
Getting help
Hitachi Support Connect is the destination for technical support of products
and solutions sold by Hitachi. To contact technical support, log on to Hitachi
Support 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 the
destination to get answers, discover insights, and make connections. Join
the conversation today! Go to community.hds.com, register, and complete
your profile.
Comments
Please send us your comments on this document to doc.comments@hds.com.
Include the document title and number, including the revision level (for
example, -07), and refer to specific sections and paragraphs whenever
possible. All comments become the property of Hitachi.
Thank you!
About this document
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
7
8
About this document
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
1
Overview
This chapter provides an overview of the Hitachi NAS Storage Replication
Adapter.
□ About Hitachi NAS Storage Replication Adapter
□ Terminology
□ Typical SRA disaster recovery configuration
Overview
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
9
About Hitachi NAS Storage Replication Adapter
Traditionally, complex distance recovery solutions require customized, sitespecific scripting. Testing these solutions also often requires multiple, manual
steps, executed for each site.
Hitachi and VMware team up to provide user-friendly site recovery testing
and failover for VMware environments with Hitachi NAS Storage Replication
Adapter. 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 as
SRA throughout most of this document.
The SRA software is deployed within a SRM environment using Hitachi NAS
Platform-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.
Terminology
Hitachi and VMware sometimes use different terminology for the same
concept. When referring to storage replication, Site A, Primary, Source, and
Protected are all terms that refer to the site where the data is located that
you want to replicate; and Site B, Secondary, Destination, Protected,
Recovery, and Target, are all terms that refer to the site where the data is
stored after it has been replicated. This document uses standard HDS
terminology of Source for the site from which the data originates and
Destination to which the data is replicated.
Typical SRA disaster recovery configuration
The following figure shows a typical SRA configuration for disaster recovery.
10
Overview
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
Overview
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
11
12
Overview
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
2
System requirements
The SRA product is designed as a plugin to the VMware vCenter product so
that data recovery tasks can be executed and managed inside the same
management tool used for other VMware environment administration tasks.
VMware vCenter Site Recovery Manager ( SRM) configuration
requirements:
• 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 and
configured, where appropriate.
Item
Description
SRA
Release 2.3
Supported operating systems
•
•
NAS Platform infrastructure
•
•
•
•
Microsoft Windows Server 2008 R2, Windows Server 2008
R2 SP1, Windows Server 2008 SP2 (64-bits)
Microsoft Windows Server 2012 (64-bits)
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
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
13
Item
Description
Version to match corresponding Hitachi NAS File
Operating System listed above
Hitachi Virtual Storage Platform (VSP G400, VSP G600, and
VSP G800) fitted with NAS modules
○ Internal or external SMU
○ NAS File OS 12.6 or later
○
•
14
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
System requirements
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
3
Deployment prerequisites
Before deploying Hitachi NAS Storage Replication Adapter, you must
configure each datastore that needs to be protected by the SRM software at
both the source site and the destination site.
The following list outlines typical high-level tasks to add and configure on
both sites:
• Create placeholder file systems
• Confirm that syslock is disabled
• Add NFS exports to source and verify they are set to read-write
• Add NFS exports to target and verify they are set to read-only
• Mount the NFS exports to the ESXi host
• Add replication rule (optional)
• Add replication policies
• Add replication schedule (on the source site only)
• Enable the NDMP service
Note: It is recommended that you review the current Hitachi NAS Storage
Replication Adapter for VMware® vCenter™ Site Recovery Manager™ Release
Notes before proceeding.
Refer to the following guides if you need additional information when
configuring 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
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
15
Confirm sites readiness for SRA deployment
Follow the order of these high-level steps to best prepare both the source
(protected) site and the destination (recovery) site for deploying SRA.
1.
2.
3.
4.
Confirm that an independent SMU is configured for both sites.
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 to
check status. (See the Server and Cluster Administration Guide for more
information.)
Open all TCP ports (specifically for the EVS IP addresses involved with
replication communication) to allow for multiple replication streams. This
is optional, but recommended for optimum intra-site communications.
Ensure NDMP services are running on both sites. From the 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 the
information in the Best Practices section of Hitachi NAS Platform Best
Practices Guide for NFS with VMware vSphere, which contains
recommendations for appropriate storage and network configurations for
your VMware Hitachi NFS storage environment.
Configure sites for SRA deployment - overview
This section provides high-level tasks that must be completed on both the
source 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) site
Before you deploy SRA, configure the source site as follows:
Procedure
16
1.
Identify the Hitachi NAS Platform-based datastores mounted on the ESXi
host or cluster to be protected on the source site. For example: SiteADS-02, a datastore on the source site file system SiteA-FS-1.
2.
Use the Hitachi Virtual Infrastructure Integrator plugin to quickly identify
these Hitachi NAS Platform-based datastores.
See Hitachi Virtual Infrastructure Integrator Administration Guide
(MK-92HNAS003) for more information.
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
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 file
system SiteB-FS-1 as the target for the SiteA-DS-02 datastore on the
source site file system SiteA-FS-1.
Note: Set read-write to Access Configuration on NFS exports. For
example: esxi-ip(rw) in NFS exports Access Configuration.
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 Show
snapshots 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 the
Hitachi NAS Platform-based datastores mounted on the ESXi host or
cluster to be protected on the source site. For example: SiteA-DS-02, a
datastore on the source site file system SiteA-FS-1. on page 16.
See the Replication and Disaster Recovery Administration Guide for more
information.
8.
Required if the ESXi host datastores are exported from the file system
root level: Create a file replication rule to exclude the /.jetapi directory
from a replication, and apply the rule to the file replication policy.
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
17
Note: Generally, best practice is that ESXi datastores are not
exported at file system root level.
9.
Add the replication schedule for the replication policy by applying the
rule, and initiate immediately.
Remember: Wait for the replication to complete before preparing
the secondary site.
18
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
10.
Validate that the replication completed successfully.
Preparing the destination (recovery) site
Before 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.
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
19
Procedure
1.
2.
3.
4.
Identify the file systems mounted on the ESXi hosts that store the
replicated virtual machine disks (VMDKs) and configuration files.
For example: SiteB-DS-02, a datastore on the destination site file
system SiteB-DS-02, a datastore on the destination site file system
SiteB-FS-1.
Disable the syslock mode on the respective file systems.
Create a file system for the placeholder datastore.
For example: PHdatastore2.
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. Another
example is when specifying the individual ESXi host(s) that should
have 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 be
configured per SRM server at the recovery site.
6.
For each datastore that is to be protected from the source site (A) to the
destination site (B), you create another bidirectional replication policy
from the destination site to source site.
Remember: Do not create a File Replication Schedule on the
destination site.
For example: Create a replication policy with SiteB-DS-02 as the
replication source, and SiteA-DS-02 that resides on the source site.
7.
20
Verify that the NDMP service is running; restart, if necessary.
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
8.
If you prefer more detailed steps, go to the next section. If not, skip
directly to Deploying SRA on page 29.
Configure sites for SRA deployment - details
This section provides detailed steps for configuring both the source and
destination sites to deploy SRA.
If you prefer a high-level overview, refer to Configure sites for SRA
deployment - overview on page 16.
The order in which sites are configured is flexible. The source and destination
sites can be completely configured one after the other, or each step can be
performed on each site before moving on to the next step.
The steps in this section take the second approach: they describe each step,
first for the source site, then for the destination site.
Creating file systems
Follow these high-level steps for creating the file systems.
For complete details, see the File Services Administration Guide. These file
systems must be created on both the source and destination sites before
deploying SRA. This section describes the high-level steps for creating the file
systems.
Procedure
1.
2.
Log into the NAS Manager (SMU user interface) for the source site.
Create two file systems: one referred to as the file system for VMware
datastore and the other referred to as the file system for SRM
placeholder datastore. For example, you might label the file system for
VMware datastore SourceFS and the file system for the placeholder
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
21
datastore PHdatastore1. Set each file system with the following
configuration:
• The Size Limit of the source file system cannot be less than the size
limit on the destination file system.
• Set the file system to Allocate Now.
• Optionally, enable the Support and Enable Dedupe option (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 VMware
datastore and a file system for SRM placeholder datastore. For example,
you might label the file system for VMware datastore TargetFS and the
file system for the placeholder datastore PHdatastore2.
Disabling Syslock on a file system
All file systems must have Syslock disabled.
Procedure
1.
2.
3.
4.
5.
6.
To verify and change the status, log in to the NAS Manager (SMU user
interface) for the source site.
Navigate to Home > Storage Management > File System to open the
File System page.
Select the file system from the list and then click Details to display the
File System Details page.
Check the current status of Syslock. If the status is enabled, click
Disable.
Click OK.
Repeat steps 2 - 5 to disable Syslock on the destination site.
Adding NFS exports
Follow 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, ensure
that 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 system
has 10 NFS exports, the destination file system must also have 10 NFS
exports.
• You must have the both the NFS export name and the directory structure
identical at the protected site and at the disaster recovery site.
22
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
Procedure
1.
2.
3.
Log in to the NAS Manager (SMU user interface) for the source site.
Navigate to Home > File Services > NFS Exports.
Make sure you have selected the EVS and file system to which the NFS
export is assigned.
For example, file system SourceFS.
4.
Specify the export name, the path to the source directory for the export,
and add read/write permissions in the Access Configuration field.
For example, enter /Country in the Export Name field, enter /Country
in the Path field, and 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 the
Path field, and esxi-ip(rw) in the Access Configuration field. The
following NFS export details page shows an example of NFS exports:
In the example NFS Details page, eight NFS exports with the following
path structure were added:
• /Country
○ /Country/JP
○ /Country/UK
○ /Country/US
• /Dept
○ /Dept/HR
○ /Dept/Eng
○ /Dept/Fin
6.
Log into the NAS Manager for the destination site and repeat steps 2 - 5
to add the identical exports. For the destination sites, add *(ro) or
esxi-ip(ro) in the Access Configuration field. The esxi-ip(ro)
example is used when specifying the individual ESXi host(s), which
should have access to NFS exports.
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
23
Adding a rule
You can exclude replicating one or more directories or files when adding a
rule and then apply the rule to a policy.
This section includes instructions on how to add the following rules:
• Specify directories or files to exclude
• Use the #SRMflag exception
Adding a rule (specifying exclusions)
Follow these high-level steps that are required to add a rule that excludes a
directory or file.
Procedure
1.
2.
3.
Log in to the NAS Manager (SMU user interface) for the source site.
Navigate to Home > Data Protection > File Replication Rules > Add
Rule to open the Add Rule page.
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 in
the path. The name may not contain any characters, but it may start
or end with an asterisk (*).
24
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
• A list of files or directories to exclude from a replication. When listing
files or directories to exclude from a replication, all items in the list
must be separated by a comma.
5.
6.
Click OK.
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 Exclude
field.
This keyword can be configured when there are multiple file replication
polices on the Hitachi NAS system, but not all for VMware SRM solution.
Apply the rule that has the keyword #SRMflag into the replication policies
protected by VMware SRM.
Hitachi NAS SRA allows for exclusion of specific replication policies using the
keyword #SRMflag in the Files To Exclude field. This keyword can be
configured when there are multiple file replication policies on an Hitachi NAS
system, but not all are defined for use with the VMware SRM solution. For
configurations such as these, define a rule which uses the #SRMflag keyword
and apply this rule to the replication policies in use by VMware SRM.
This keyword can be used along with regular directories/files exclusions.
Procedure
1.
2.
3.
Log in to the NAS Manager (SMU user interface) for the source site.
Navigate to Home > Data Protection > File Replication Rules > Add
Rule to open the Add Rule page.
Enter the rule name and optionally, a description.
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
25
4.
In the Files To Exclude field, enter #SRMflag.
5.
6.
Click OK.
Log in to the NAS Manager for the destination site and repeat steps 2 5.
Adding a file replication policy
This procedure describes the high-level tasks to add a file replication policy.
A file replication policy identifies the data source, the replication target, and
optionally a replication rule. For complete details on policies, refer to the
Replication and Disaster Recovery Administration Guide.
Procedure
1.
2.
3.
4.
5.
26
Log in to the SMU for the source site.
Navigate to Home > Data Protection > File Replication to open the
File Replication page and click Add under the Policies section of the
page.
Choose Not a Managed Server and then click Next.
The following image illustrates an example of a policy.
Enter the name of the policy.
Enter the information specific to the source site:
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
6.
7.
8.
a. The EVS and file system must correspond to the VM file system.
b. Choose Directory and then enter the NFS export path.
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.
Optionally, select the File Replication rule.
For more information on using this rule, see Adding a rule (specifying
exclusions) on page 24 and Adding a rule (#SRMflag) on page 25.
Log in to the destination site and repeat steps 2 - 7.
Creating a replication schedule
To apply the schedule to the replication policy:
Note: Schedules are only set on the source site.
Procedure
1.
2.
3.
4.
5.
6.
7.
8.
Log into the NAS Manager (SMU user interface) for the source site.
Navigate to Home > Data Protection > File Replication.
Click Add under the Schedules section to open the Add Schedule
page.
Select the Policy.
Choose Immediately: Start as soon as the schedule is created.
Choose Once, at the scheduled date and time.
Click OK to save changes and return to the File Replication page.
Under the Schedule section of the page, verify that the schedule
completed successfully.
This step is performed only at the source site.
Enabling NDMP service
To check that NDMP service is started:
Procedure
1.
2.
3.
Navigate to Home > Data Protection > NDMP Configuration to
display the NDMP Configuration page.
Check the Current Status in the NDMP Server Status section of the
page.
Click start if the current status is stopped.
Repeat steps 1-2 for the destination site.
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
27
28
Deployment prerequisites
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
4
Deploying SRA
This chapter provides instructions for deploying the Hitachi NAS Storage
Replication Adapter.
□ Configuring SRA permissions
□ Installing Hitachi NAS Storage Replication Adapter
□ Configuring array managers
□ Uninstalling SRA
□ Advanced configuration options
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
29
Configuring SRA permissions
The SRA software uses the file replication features of the Hitachi NAS
Platform, and interacts with the SMU to create replication relationships
between two sites, and to connect to the nodes. To permit the SRA software
to run the required commands, you must update the /etc/sudoers file on all
of 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 by
root.
3.
Enter chmod 0660 /etc/sudoers to change the permissions for
the /etc/sudoers file to 0660.
4.
Enter cp /etc/sudoers /etc/sudoers_tmp to create a temporary copy
of the file.
Enter
echo "manager ALL=(root) NOPASSWD: /usr/bin/SMcli, /usr/bin/
SMclient,
/opt/smu/adc_replic/replication_schedule.sh" >> /etc/
sudoers_tmp
5.
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.
30
6.
Enter cat /etc/sudoers_tmp to confirm the file is correct.
7.
Assuming the file /etc/sudoers_tmp is correct, enter mv -f /etc/
sudoers_tmp /etc/sudoers
8.
Enter chmod 0440 /etc/sudoers to reset the permissions.
9.
Enter exit to exit the root shell.
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment 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 Hitachi NAS Storage Replication Adapter
The Storage Replication Adapters (SRA) provide an interface to primary
storage with replication software.
The Storage Replication Adapters (SRA) provide an interface to primary
storage with replication software. SRAs are vendor-specific, and need to be
installed on the VMware vCenter Site Recovery Manager ( SRM) servers at
both the source sites and the destination sites. The SRA installer is available
as a downloadable .msi file from Hitachi at portal.hds.com or available
from the VMware SRM download site.
Procedure
1.
2.
3.
Ensure that the SRM is installed.
Download the SRA installer from VMware or the Hitachi support portal
(https://portal.hds.com).
Copy and install the .msi file on the SRM servers at both the source site
and the destination site.
Upgrading SRA software
Upgrading from Hitachi NAS SRA v2.0 or newer is supported using the .msi
file referenced above. If upgrading from an earlier version, uninstall this
version first. After executing the .msi installation program, perform the
following steps to complete the upgrade process:
Procedure
1.
2.
3.
Download the Hitachi NAS SRA installer from VMware or the Hitachi Data
Systems support portal (https://portal.hds.com).
Copy and install the .msi file on the SRM servers at both the source and
destination sites.
In previous versions, it was required that Syslock be enabled on the
destination site file system. Beginning with v2.1, this is no longer
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
31
4.
5.
necessary. Therefore, ensure that Syslock is disabled on each destination
file system. See the topic, Disabling Syslock on a file system on page 22,
for details.
Refresh the Devices for Array pair in the Devices tab for each
configured array manager. The discovery is expected to fail if the
destination site file system is in syslock state. Take it out of syslock state
make the NFS exports on destination site read only. See the topic,
Deployment prerequisites on page 15, for details.
Configure array managers. See the topic, Configuring array managers on
page 32, for details.
Verifying SRA installation
This 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 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 Recovery
Manager server. See SRA not displaying in SRM after successful
installation on page 48 for more information.
Configuring array managers
Follow this procedure to add array managers and arrays.
Procedure
1.
32
Double-click the VMware vSphere Client icon (
), log in to the vCenter
Server, and go to Home > Site Recovery > Array Managers.
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
2.
In the Array Manager pane, identify the protected site in which you
want to configure, right-click, and select Add Array Manager.
3.
Enter a display name, select Hitachi NAS Replicator Adapter as the
SRA type, and then click Next.
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
33
4.
Enter the System Management Unit (SMU) and Controller/Admin EVS
details, 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 be
different from the user name and password that is
provided when logging in to Web Manager, the SMU GUI.
Controller/Admin EVS IP
Enter the IP address of the Controller/Admin EVS.
Address
File System Exclude List
Enter a list of file systems or volumes to exclude separated by a
comma for multiple values. (Optional)
34
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
Field/Item
Description
Controller/Admin EVS
Enter a unique user name.
Username
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 SRA
This section describes how to uninstall the SRA software, if necessary.
Uninstall the SRA software using the Microsoft Windows Control Panel on both
Site Recovery Manager ( SRM) servers at the source site and the destination
site.
Procedure
1.
2.
3.
From the SRM server at the source site, go to Start > Control Panel >
Programs > Uninstall a program.
Right-click SRA, and select Uninstall.
Repeat for the destination site.
Advanced configuration options
This section describes advanced configuration options.
Configuring SRA when an Hitachi NAS EVS has multiple IP addresses
defined (Primary or Secondary)
If the datastore on the primary or secondary site is hosted on an Hitachi NAS
EVS with multiple IP addresses, follow the steps in this section to create a
successful array pair during device discovery. If the configuration files are
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
35
required but are not present, the array pair will be grayed out and have
different IP addresses on the protected and recovery site.
Note: A unique config.cfg file must be defined at both the primary and the
secondary site. Do NOT copy the config.cfg file between the two sites.
At both the primary and secondary site, create a file name config.cfg . Note
that the config.cfg file name is case sensitive and must consist of all lower
case letters. The path for the location of the configuration file is represented
by the variable path $Bin/config.cfg. For a typical installation, this path would
be C:\Program Files\VMware\VMware vCenter Site Recovery Manager
\storage\sra\HNAS-SRA\config.cfg.
Each config.cfg file must contain at least one set of values, in the order
described below.
POLICY_NAME
Exact name of the replication policy used to replicate the VMs from the one
site to the other site. It is case sensitive and must be the first parameter of
the set for each replication policy.
SRC_IP
Source IP address to be used in the SRA workflow. This must be one of the
IP addresses configured on the Hitachi NAS EVS hosting the datastore at the
source location.
DEST_IP
Destination IP to be used in the SRA workflows. This must be one of the IP
addresses configured on the Hitachi NAS EVS hosting the datastore at the
destination location.
The following example shows 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 the
two sites.
Add a set for each replication policy of a datastore used by SRA where the
datastore is hosted on an EVS with multiple IP addresses, as outlined in the
example.
Note: The config.cfg file is not part of the Hitachi SRA Installation. If this file
is needed, you need to create it, add the content, and write it using a text
editor, such as notepad. It is important to match the format exactly including
case and only write a ‘text’ file. Formats other than a ‘text’ file are not
supported.
36
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
Single policy to protect multiple datastores (NFS exports)
This option protects multiple NFS exports on a single Hitachi NAS file system
using one file replication policy (Consistency Group). The example below
protects DS01 and DS02 on FS01 filesystem.
Source site
Note: This option requires that your consistency group have the NFS Export
name and directory structure identical between Source site and Destination
site.
1.
2.
3.
Create a file system (for example, FS01).
Create an NFS Export on FS01. (NFS Export Name: ROOT, NFS Export
Path: / and Access Configuration: esxi-ip(rw)).
Create a second NFS Export on FS01. (NFS Export Name: DS01, NFS
Export Path: /DS01 and Access Configuration: esxi-ip(rw)).
Note: Use *(rw) if not specifying individual ESXi host(s) with
access.
4.
5.
Create a third NFS Export on FS01. (NFS Export Name: DS02, NFS
Export Path: /DS02 and Access Configuration: esxi-ip(rw)).
Create a File Replication Policy (for example, File Replication Policy name
is Rep1P).
a. Source file system: FS01
b. Source Directory: /
c. Destination File System: FS11
d. Destination Directory: /
Note: Any directory can be used.
6.
7.
Create a File Replication Policy Schedule of ‘Rep1P’
Mount ‘/DS01’ and ‘/DS02’ on ESXi
Destination site
1. Create a file system (for example, FS11).
2. Create an NFS Export on FS11 (NFS Exports Name: ROOT, NFS Export
Path: / and Access Configuration: 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)).
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
37
Note: Use *(ro) if not specifying individual ESXi host(s) with
access.
4.
5.
Create a third NFS Export on FS11 (NFS Export Name: DS02, NFS Export
Path: /DS02 and Access Configuration: esxi-ip(ro)).
Create a File Replication Policy (for example, File Replication Policy name
is Rep1S).
a. Source File System: FS11
b. Source Directory: /
c. Destination File System: FS01
d. Destination Directory: /
Note: No replication schedule is required on the destination.
Exclude specified datastores (NFS exports) from being replicated
This option protects multiple NFS exports per a single Hitachi NAS file system
by one File Replication Policy (Consistency Group), but excludes specified NFS
exports.
This example has three datastores (DS01, DS02, and DS03) on the same file
system. This example excludes DS02 from being replicated without creating
individual policies.
1. Go to the source site.
2. After creating NFS Exports, create a File Replication Policy Rule (Rule
Name: exclusion-DS02 and Files To Exclude: /DS02) and apply the rule
to the File Replication Policy.
3. Go to the destination site.
38
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
4.
After creating NFS Exports, create a File Replication Policy Rule (Rule
Name: exclusion-DS02, Files To Exclude: /DS02) and apply the rule to
the File Replication Policy.
Allow SRM and non-SRM based replication policies on the same
system
In a configuration which has other replication policies that are associated with
a non-VMware SRM use case, the following option allows you to identify
replication policies that are specifically associated with SRM configuration.
In this option, 'DS01' and 'DS02' are used for VMware SRM and 'DS03' has a
replication policy not associated with a VMware SRM configuration and/or is
possibly not a VMware-specific export.
1. Go to the source site.
2. After creating NFS Exports, create a File Replication Policy Rule (Rule
Name: SRM and Files To Exclude: #SRMFlag) and apply the rule to the
File Replication Policy.
3.
4.
Go to the destination site.
After creating NFS Exports, create a File Replication Policy Rule (Rule
Name: SRM and Files To Exclude: #SRMFlag) and apply the rule to the
File Replication Policy.
Exclude unnecessary VM files and/or specific VMs from being
replicated
This option ensures that only pertinent VMware files are replicated and
ensures that non-essential VM level files (temp, swap files, and so on) are
not replicated.
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
39
Additionally, the option can be extended to remove certain VMs from being
replicated without forcing those VMs to be relocated to other non-SRM
datastores. However, any VM(s) excluded as part of a replication policy must
have been replicated at least once to the destination before being excluded
via a File Replication Rule.
This example protects the datastore DS01 and DS02 by consistency group;
however, one of the VMs (VM3) that is present on DS01 is not required to be
replicated, ensuring lower overall replication times for the datastore. It also
excludes all non-essential VMware files (*.vswp and *.nvram) across all VMs.
Note: Ensure at least one replication policy has been completed, which has
replicated all VMs on DS01 and DS02 including VM3.
1.
2.
Go to the source site.
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 vmwin-largetemp on DS11 being replicated. This is in addition to
excluding all *.vswp and *.nvram VMware files from being
replicated.
3.
4.
40
Create a File Replication Policy (for example, File Replication Policy name
Rep1P) and apply the rule exclusion-VM3.
Go to the SRM GUI on the source site.
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
5.
Use the existing Recovery Plan for the protection group.
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
41
6.
42
From Recovery Plan, configure the VM with the Do not power on setting
for the VM(s) that do not need to be managed for failover.
Deploying SRA
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
5
Troubleshooting
This chapter provides information and instructions for troubleshooting
configuration issues.
When diagnosing an issue, review and provide the required logs to Hitachi
Data Systems Support Center.
For details about the available logs and those required for Hitachi Data
Systems Support Center assistance, see Log locations on page 44.
Note: Ensure you have reviewed the current Hitachi NAS Storage Replication
Adapter for VMware Site Recovery Manager Release Notes for any limitations
and workarounds.
□ Checking for general SRM and SRA issues
□ Log locations
□ Generating Reports
□ Error Messages
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
43
Checking for general SRM and SRA issues
Refer to the VMware Community for more information.
See http://communities.vmware.com/community/vmtn/vcenter/srm.
Log locations
When issues occur, collect the logs as needed.
Locate the SRM and SRA logs on source and destination sites in the following
location: For Windows 2008 and 2012: C:\ProgramData\VMware\VMware
vCenter Site Recovery Manager\Logs\
Locate the SRA 2.3 log files in the following location: For SRM 5.5, 5.8, and
6.x: <Site Recovery Manager Installation directory>\storage\sra\HNAS-SRA
\log
Generating Reports
This section describes how to generate SRM operation HTML reports.
Procedure
1.
From the vSphere Client, go to Home > Site Recovery > Recovery
Plans > History.
2.
Identify the operation, and click Export to generate a SRM Operation
HTML Report.
Error Messages
This section lists the error messages you might see. Each topic will have a
possible cause for the error and a possible resolution.
XCopyFile Failed in CopySRA
The entire error message: "XCopyFile Failed in CopySRA".
44
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
Possible cause
The user who ran the installer has insufficient permissions to copy the files
into SRM directory.
Resolution
Run the HNAS-Installer by using the local built-in Administrator or perform
the 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 at
remote site for 'FS_name/Export_name".
Possible cause
• Consistency group is formed for a parent NFS export that has sub-NFS
exports acting as datastores.
Resolution
1. Exclude the sub-NFS export directory from file replication using a file
replication rule setting.
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 export
and use the #SRMflag rule setting on protected devices file replication
policy to include it in SRM protection. Hitachi NAS Storage Replication
Adapter detects all valid SRM protected file replication policies using the
replication 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 cause
1. 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 inventoried
under ESXi host.
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
45
Resolution
Remove the VM from protection group in SRM and from the inventory of the
ESXi host.
Creating protection groups error
The error message can vary.
Possible cause
Inventory mappings have not completed.
Resolution
You cannot not create protection groups if the following mappings are not
completed:
• Resource mappings
• Folder mappings
• Network mappings
• Placeholder datastores
Device cannot be matched to a remote peer device
The entire error message: "Device cannot be matched to a remote peer
device" when forming a consistency group even though the export paths are
identical 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 a
properly functioning system.
• The replication policy on either the source or the destination site is
targeting 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 a
consistency group; therefore, the device path name should be of same
case or the device pairing will fail.
• Mount the file systems, and configure the permissions for both sites. See
the File Services Administration Guide for more information.
• Synchronize the sites. See Deployment prerequisites on page 15 for more
information.
46
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
• Review and modify the replication policy, as needed, to target the correct
datastore.
• Configure the replication polices so that bidirectional communication is
supported.
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) on
page 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 by
Hitachi 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 syslocked
The entire error message: "The filesystem [fs_name] is syslocked please
unlock 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 SRA
v2.1.
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
47
SRA not displaying in SRM after successful installation
Possible cause
The Site Recovery Manager ( SRM) cache did not refresh and displays an old
status.
Resolution
Click Rescan SRAs so that the SRM discovers the SRA. You may need to
rescan a few times before the SRA is displayed.
Operating system not adequate for running SRA for SRM
The entire error message: "The operating system is not adequate for running
Hitachi NAS Storage Replication Adapter for VMware vCenter Site Recovery
Manager."
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 commands
The entire error message: "SMU User does not have sufficient privilege to
execute 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 on
page 30.
SRA command 'discoverArrays' failed
The entire error message: "SRA command 'discoverArrays' failed. Storage
arrays have not been configured for replication. Storage array is not properly
configured. Please configure the storage arrays.
Possible cause
1. 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.
48
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
4.
5.
NFS export is not configured properly.
Multiple replication policies exists with non-SRM/VMware without the
#SRMflag setting.
Resolution
1. Create a replication policy for the file systems and devices that are part
of your disaster recovery plan. See the Replication and Disaster Recovery
Administration 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 is
configured on root or root directory where the consistency group is being
formed. If the consistency group is being formed inside sub-NFS exports,
the NFS export for root directory must exist where the replication policy
is created.
5. If multiple replication policies co-exist with policies that are not taking
part in SRM or VMware solutions, all valid SRM policies must have the file
replication rule #SRMflag set. Create a file replication rule with
#SRMflag, in the Files To Exclude setting. Apply the rule to all valid SRM
policies.
Note: : #SRMflag can be added to normal exclusion rules, for
example:/VM1,*.mp3,#SRMflag.
SRA does not display datastore name
SRA discovery does not display the datastore name under Array pair devices
even 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 NFS
export 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 the
Site Recovery Manager (SRM) logs, the SRA seems to be stuck, and
eventually the SRM action times out.
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
49
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 fails
The entire error message is: " Test recovery fails with Error - Cannot
unmount 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 of
the ESXi host.
Failed to access file [datastore-name] failed to unregister protected
VMs
Possible cause
A failover might have occurred if one of the hosts lost connection to a
placeholder 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) to
store small (approximately 1 KB) virtual machine (VM) placeholder files.
Placeholder datastores can be shared by more than one host or cluster, but
each host and cluster that is used for protecting or recovering VMs needs
access to a placeholder datastore.
• On the destination (recovery/protected) site, manually remove any
placeholder VMs created on the host that lost connection to the
placeholder datastore. Remove the VM replication configuration then
reconfigure the replication. Reconfigure VM protection from the protection
group properties.
Unable to access file [unspecified filename]
Possible Cause
The owner/group of the VMware files might have changed during the failover
recovery plan and it caused insufficient permission.
50
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
Resolution
Set either * (no_root_squash) or esxi_ip (no_root_squash) in Access
Configuration 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 this
protection 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 for
all VMs are OK.
WFS-1 file system not supported by SRA, found a replication policy
The entire error message: " WFS-1 Filesystem not supported by SRA, found a
replication 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.
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
51
52
Troubleshooting
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
A
Open source software copyrights and
licenses
This section lists the Open Source software copyrights and licenses for
software used by the Hitachi NAS Storage Replication Adapter product.
□ Perl module Net::SSH2
□ Libssh2
Open source software copyrights and licenses
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
53
Perl module Net::SSH2
Copyright (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 license
document, 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 you
have the freedom to give away or sell copies of free software, that you
receive source code or can get it if you want it, that you can change the
software or use pieces of it in new free programs; and that you know you can
do these things.
To protect your rights, we need to make restrictions that forbid anyone to
deny you these rights or to ask you to surrender the rights. These restrictions
translate to certain responsibilities for you if you distribute copies of the
software, 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, distribute
and/or modify the software.
Also, for each author's protection and ours, we want to make certain that
everyone understands that there is no warranty for this free software. If the
software is modified by someone else and passed on, we want its recipients
to know that what they have is not the original, so that any problems
introduced by others will not reflect on the original authors' reputations.
The precise terms and conditions for copying, distribution and modification
follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND
MODIFICATION
0. This License Agreement applies to any program or other work which
contains a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below, refers
54
Open source software copyrights and licenses
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
to any such program or work, and a "work based on the Program" means
either 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 code
as you receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this General
Public License and to the absence of any warranty; and give any other
recipients of the Program a copy of this General Public License along with the
Program. 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 1
above, provided that you also do the following:
a) cause the modified files to carry prominent notices stating that you
changed the files and the date of any change; and
b) cause the whole of any work that you distribute or publish, that in whole
or in part contains the Program or any part thereof, either with or without
modifications, to be licensed at no charge to all third parties under the terms
of this General Public License (except that you may choose to grant warranty
protection 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 the
simplest and most usual way, to print or display an announcement including
an appropriate copyright notice and a notice that there is no warranty (or
else, saying that you provide a warranty) and that users may redistribute the
program under these conditions, and telling the user how to view a copy of
this General Public License.
d) You may charge a fee for the physical act of transferring a copy, and you
may at your option offer warranty protection in exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the 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 of
Paragraphs 1 and 2 above provided that you also do one of the following:
a) accompany it with the complete corresponding machine-readable source
code, which must be distributed under the terms of Paragraphs 1 and 2
above; or,
b) accompany it with a written offer, valid for at least three years, to give any
third party free (except for a nominal charge for the cost of distribution) a
Open source software copyrights and licenses
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
55
complete machine-readable copy of the corresponding source code, to be
distributed under the terms of Paragraphs 1 and 2 above; or,
c) accompany it with the information you received as to where the
corresponding source code may be obtained. (This alternative is allowed only
for noncommercial distribution and only if you received the program in object
code or executable form alone.)
Source code for a work means the preferred form of the work for making
modifications to it. For an executable file, complete source code means all the
source code for all modules it contains; but, as a special exception, it need
not include source code for modules which are standard libraries that
accompany the operating system on which the executable file runs, or for
standard header files or definitions files that accompany that operating
system.
4. You may not copy, modify, sublicense, distribute or transfer the Program
except as expressly provided under this General Public License. Any attempt
otherwise to copy, modify, sublicense, distribute or transfer the Program is
void, and will automatically terminate your rights to use the Program under
this License. However, parties who have received copies, or rights to use
copies, from you under this General Public License will not have their licenses
terminated so long as such parties remain in full compliance.
5. By copying, distributing or modifying the Program (or any work based on
the Program) you indicate your acceptance of this license to do so, and all its
terms and conditions.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the original
licensor to copy, distribute or modify the Program subject to these terms and
conditions. 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 of
the General Public License from time to time. Such new versions will be
similar in spirit to the present version, but may differ in detail to address new
problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of the license which applies to it and "any later
version", you have the option of following the terms and conditions either of
that version or of any later version published by the Free Software
Foundation. 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 programs
whose distribution conditions are different, write to the author to ask for
permission. For software which is copyrighted by the Free Software
Foundation, write to the Free Software Foundation; we sometimes make
56
Open source software copyrights and licenses
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
exceptions for this. Our decision will be guided by the two goals of preserving
the free status of all derivatives of our free software and of promoting the
sharing and reuse of software generally.
NO WARRANTY
9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS 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 OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE
LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS
OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED
BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Libssh2
Copyright (c) 2004-2007 Sara Golemon sarag@libssh2.org
Copyright (c) 2005,2006 Mikhail Gusarov dottedmag@dottedmag.net
Copyright (c) 2006-2007 The Written Word, Inc.
Copyright (c) 2007 Eli Fant elifantu@mail.ru
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 without
modification, 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.
Open source software copyrights and licenses
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
57
• Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
• Neither the name of the copyright holder nor the names of any other
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
58
Open source software copyrights and licenses
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
Index
A
B
C
D
admin EVS 32
array
add array manager 32
array discovery failure 48
array managers
configuring 32
best practices 16
cannot mount datastore 47
cluster IDs 32
configuration
advanced options 35
allow replication policies 39
exclude unnecessary files or VMs 39
protect multiple datastores 37
protect NFS exports 37
configuring
array managers 32
Controller/Admin EVS 32
datastore
configuration
advanced options
exclude from replication 38
exclude from replication 38
datastore display error 49
datastores 15
deploy SRA 29
Device Exclude List 32
disable Syslok 22
disaster recovery plan 48
discoverArrays failed 48
E
F
G
H
I
L
enable NDMP service 27
error message
cannot mount datastore 45, 46
failover 45, 46
inventory mappings 46
protection group error 46
XCopyFile failed 44
EVS 32
failover error 47, 50
file replication policy 26
file system 21
disable Syslok 22
firmware 13
guest OS 51
high-level preparation steps 16
Hitachi NAS Virtual Infrastructure Integrator 15
HNAS reference documentation 5
HUS 13
install
verify SRA 32
installing SRA 31
license
Libssh2 57
Perl module Net::SSH2 54
logs
location 44
Index
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
59
M
N
O
P
R
60
msi file 31
multiple datastores
policy to protect 37
S
NAS Manager
configuring permissions 30
SMU 30
NDMP 16
NDMP service 27
NFS 13
NFS export
exclude from replication 38
NFS exports 22
policy to protect 37
open source copyrights and licenses 53
operating systems supported 13
peer array set to unknown 32
permissions 30
placeholder datastores 15, 50
policy
protect multiple datastores 37
protect NFS exports 37
replication 26
replication on same system 39
preparing sites for SRA 16
protection group 51
protocol support 13
reference documentation
HNAS 5
VMware 6
replication
exclude
datastores 38
NFS exports 38
exclude files or VMs 39
replication policy 15, 26, 48
replication schedule 15
create 27
rescan SRAs 32
root shell 30
rules 24
add
#SRMflag 25
specify exclusions 24
T
U
V
schedule
replication 27
service
NDMP 27
site configuration details 21
site configuration overview 16
site preparation 16
SMU 16, 32
configuring permissions 30
SMU permissions 30
software
how to upgrade 31
SRA
deploy 29
disaster recovery configuration 10
install 31
overview 9, 10
uninstall 35
verify install 32
SRA inactive 49
SRA install directory path 32
SRA not displaying in SRM 48
SRAs tab 32
SRM action times out 49
SRM cache 48
SRM Operation HTML Report 44
sudoers 30, 49
supported
hardware 13
storage arrays 13
syslock error 47
Syslok
disable 22
TCP 16
temporary files 16
terminology 10
troubleshooting 43
error messages 44
general SRM and SRA issues 44
generating reports 44
logs 44
unable to access file error 50
uninstalling SRA 35
upgrade
software 31
V2I 15
vCenter Server 32
verifying SRA installation 32
Index
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
VM placeholder files 47, 50
VMware reference documentation 6
VMware Tools timeout 51
VSP 13
vSphere Client icon 32
W
WFS-1 error 48, 51
Index
Hitachi NAS Storage Replication Adapter for VMware Site Recovery Manager Deployment Guide
61
62
Index
Hitachi 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