GRIDScaler-WOS Bridge

(1)

Revision A0

March 2015

GRIDScaler-WOS Bridge

Version 1.6.0

(2)

DataDirect Networks GRIDScaler-WOS Bridge V1.6.0 Product Release Notes | 2

Important Information

Information in this document is subject to change without notice and does not represent a commitment on the part of DataDirect Networks, Inc. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose other than the purchaser’s personal use without the written permission of DataDirect Networks, Inc.

DataDirect Networks, the DataDirect Networks logo, DDN, DirectMon, EXAScaler, GRIDScaler, HScaler, IME, Infinite Memory Engine, Information in Motion, In-Storage Processing, NAS Scaler, NoFS, ObjectAssure, ReACT, SFA, SFA 10000 Storage Fusion Architecture, SFA10K, SFA12K, SFX, Storage Fusion Architecture, Storage Fusion Fabric, Storage Fusion Xcelerator, SwiftCluster, WOS, the WOS logo are registered trademarks or trademarks of DataDirect Networks, Inc. All other brand and product names are trademarks of their respective holders.

DataDirect Networks makes no warranties, express or implied, including without limitation the implied warranties of merchantability and fitness for a particular purpose of any products or software. DataDirect Networks does not warrant, guarantee or make any representations regarding the use or the results of the use of any products or software in terms of correctness, accuracy, reliability, or otherwise. The entire risk as to the results and performance of the product and software are assumed by you. The exclusion of implied warranties is not permitted by some jurisdictions; this exclusion may not apply to you.

In no event will DataDirect Networks, their directors, officers, employees, or agents (collectively DataDirect Networks) be liable to you for any consequential, incidental, or indirect damages, including damages for loss of business profits, business interruption, loss of business information, and the like, arising out of the use or inability to use any DataDirect product or software even if DataDirect Networks has been advised of the possibility of such damages by you. Because some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, these limitations may not apply to you. DataDirect Networks liability to you for actual damages from any cause whatsoever, and regardless of the form of the action (whether in contract, tort including negligence, product liability or otherwise), is limited to the sum you paid for the DataDirect product or software.

(3)

1.0 Overview

This document applies to the DataDirect Networks’ GRIDScaler™-WOS Bridge v1.6.0 release.

GRIDScaler-WOS Bridge is a hardware/ software solution designed to enable HSM capabilities (data migration and on demand staging) between DDN GRIDScaler and DDN WOS environments. GRIDScaler-WOS Bridge utilizes the GPFS Data Management API (DMAPI) to manage data migration between GRIDScaler appliances and WOS Storage per customer defined GPFS Policies. The three usage scenarios that GRIDScaler-WOS Bridge is designed to support are as follows:

• Archive - Migrate GRIDScaler files to lower cost WOS storage based on GPFS policies to free up disk space on GPFS.

• Disaster Protection - Copy or move GRIDScaler files to remote WOS Sites for data and disaster protection purposes.

• Collaboration – Federate namespaces and share data across other remote GRIDScaler and WOS Access sites.

The WOS Bridge was designed to interface seamlessly with GPFS, and to function automatically with minimal administration. The archive and migration activities performed by the WOS Bridge are based upon a set of GPFS policies specified by the system administrator. Examples of these policies might be to copy files from the main GPFS storage to the WOS storage when the files reach a certain age, or remain

unmodified for a certain time. The files can be copied to the WOS storage while retaining a copy on the main storage, or the files can be physically moved, leaving a “stub” on the main storage. Should a user access a moved file by performing an operation on the stub, the WOS Bridge will return a copy of the file to the main storage. File renames, deletions, content changes can all be reflected on the copies on the WOS storage.

1.1 Supported Environment

Per above, GRIDScaler-WOS Bridge provides HSM/migration capabilities between DDN GRIDScaler and DDN WOS products, which must already be installed and configured before GRIDScaler-WOS Bridge is added to the configuration. The following versions of GRIDScaler and WOS are supported by GRIDScaler-WOS Bridge v1.6.0.

• GRIDScaler v2.2.3, 3.0.0, and v3.0.1 Standard edition • WOS Core v2.5.2 / WOS7000 & WOS6000 platforms • WOS Access v1.4.2 and v1.4.4

NOTE: GRIDScaler-Embedded SFA solutions are not supported in GRIDScaler-WOS

Bridge v1.6.0. Support for GRIDScaler-Embedded SFA solutions will be introduced in further versions of GRIDScaler-WOS Bridge.

GRIDScaler-WOS Bridge is available in the following supported configurations:

• GRIDScaler NSD SFX - Software-only self-extracted archive that is designed to be installed on a GRIDScaler NSD server.

• Gateway Appliance - A packaged hardware/software appliance that includes the GRIDScaler-WOS Bridge Software pre-installed on a server/gateway. Up to eight GRIDScaler-WOS Bridge gateways may be added to a GRIDScaler configuration. GRIDScaler-WOS Bridge supports high availability requirements with redundant services in GPFS cluster environment. When service is failed, the remaining nodes attempt to acquire lock on shared GPFS file, one of them becomes new master for service.

GRIDScaler-WOS Bridge v1.6.0 also supports upgrade of existing clusters with GRIDScaler-WOS Bridge v1.5.1 and higher.

(5)

1.2 GS-WOS Bridge Product Compatibility

GS-WOS Bridge

1.2.1 GS-WOS Bridge 1.5.0 GS-WOS Bridge 1.6.0

WOS Access Versions WOS Access 1.2.3 WOS Access 1.2.4 WOS Access 1.2.5 WOS Access 1.4.2 Supported WOS Access 1.4.4 Supported WOS Core Versions

WOS Core 2.2.0 Supported

WOS Core 2.2.2 Supported WOS Core 2.5.0 Supported

WOS Core 2.5.2 Supported

GRIDScaler Versions GRIDScaler 1.5.0 Supported GRIDScaler 2.0.0 Supported GRIDScaler 2.1.0 Supported GRIDScaler 2.1.1 Supported GRIDScaler 2.2.3 Supported GRIDScaler 3.0.0 Supported GRIDScaler 3.0.1 Supported Platforms

WOS 6000 Supported Supported Supported WOS 7000 Supported Supported Supported

Note: Blank cells indicate “not currently supported.”

(6)

2.0 Features

GRIDScaler-WOS Bridge v1.6.0 release brings the following new features:

• Automated upgrade procedure from GRIDScaler-WOS Bridge v1.5.1 and higher to v1.6.0

• ILM rules created in v1.6.0 are applied according to the schedule defined by the user during rule creation. The schedule for the ‘rule add’ command in CLI should be defined with option –t [--schedule]. If no schedule is set for the rule, it can be applied only manually with the gridconman rule shoot command. Rules created in previous versions are still valid and are applied according to the value in G2W_ILM_APPLYING_TIME.

• Administration User Interface for management and monitoring of GRIDScaler-WOS Bridge cluster.

• Automated Backup of file system state, based on a user-defined schedule. • Backup status email notifications.

3.0 Fixed Defects

3.1 /etc/init.d/wos-connector-mover stop [FAILED] when file was copying on

WOS

Features GRIDScaler-WOS Bridge Mover [DE5626: Data mover]

Conditions Copying of large file to WOS is in progress

Result GRIDScaler-WOS Bridge Mover cannot be stopped

3.2 Remote GRIDScaler clusters may keep files already deleted at local

GRIDScaler cluster

Features GRIDScaler-WOS Bridge Namespace Update [DE14839]

Conditions User creates and deletes file with the same name and at the same location in cycle or when deletion of a file with the same name happens very close to deletion of previous file with the same name and at the same location. Result Local file will be removed. Some instances of such file will not be removed

from remote GRIDScaler clusters. User will be getting I/O error trying to read data from such files as underlying WOS Object will be removed.

3.3 Synchronization service log file is rotated on a daily basis and may

consume too much space in verbouse log level mode

Features GRIDScaler-WOS Bridge Namespace Update [DE15048]

Conditions User enables verbose log level for synchronization service

Result Log file may consume too much disk space in between of daily rotations Workaround Enable verbose level only temporarily when it is necessary for issue

(7)

3.4 GRIDScaler-WOS Bridge synchronization service will not start correctly if

DMH service is not running

Features GRIDScaler-WOS Bridge CLI/Administration [DE14618]

Conditions DMH service is down and administrator is trying to shut down wosnas-replication service

Result Services will not stop

Workaround Stop replication service prior to stopping DMH. Or kill wosnas-replication service.

3.5 Incorrect data during FIO

Conditions User runs FIO utility from all GPFS nodes simultaneously Result FIO fails if it is run from three or more nodes in parallel. Workaround Run FIO with two nodes only.

3.6 If value in G2W_MOUNT_POINT doesn’t contain / as last character, it will

cause errors during cluster joining or policy applying

Features GRIDScaler-WOS Bridge CLI/Administration [DE17102]

Conditions Administrator specifies G2W_MOUNT_POINT value without last / in path, like /mnt/gpfs1.

Result Synchronization service will not be able to get attributes for

synchronization of mountpoints between nodes in cluster and node will not join in cluster.

Dispatcher service cannot run rule for incorrectly configured mountpoint folder.

Workaround Add / as a latest character in G2W_MOUNT_POINT value, like /mnt/gpfs1/. Example of command:

gridconman config set G2W_MOUNT_POINT /mnt/gpfs1/

4.0 Known Issues

4.1 User gets IO error instead of data if one DMAPI Delegate Read Handler

node cannot connect to WOS

Features GRIDScaler-WOS Bridge Recall [DE7923 [Failover][ DMH]]

Conditions One of DMAPI Delegate Read Handler loses connection to WOS Result The I/O error is returned on read

Workaround User has to stop DMAPI Handler on the offending node to protect

applications from receiving intermittent I/O errors on migrated files and let GRIDScaler-WOS Bridge migrate the DMAPI Handler role to another node. Alternatively, the user may restore connection to WOS and

(8)

GRIDScaler-DataDirect Networks GRIDScaler-WOS Bridge V1.6.0 Product Release Notes | 8

WOS Bridge will resume processing I/O requests automatically.

4.2 Changelog writer creates JSON command in POSTLINK event for conflict

file( with G2W_CR)

Features GRIDScaler-WOS Bridge Recall [DE8128 [DMH]]

Conditions User creates hardlink to a file generated by conflict resolution (fileX.conflict.Y with G2W_CR extended attribute).

Result Hardlink is replicated to remote GRIDScaler cluster and remains in the NS Sync exception queue there. Thus, this hardlink will not be restored in remote GRIDScaler clusters.

Workaround Avoid creating hardlinks and performing other namespace operations on conflict files, follow the conflict recovery procedure defined in section “Conflict Detection and Resolution”of the GRIDScaler-WOS Bridge

Administrator’s Guide.

4.3 Sometimes if files are read right after snapshot is deployed, files are read

as empty ones

Features GRIDScaler-WOS Bridge Backup [DE11209 [Backup]]

Conditions User attempts to read the file that was restored from snapshot immediately after file creation (1-2 seconds)

Result File is empty.

Workaround Allow three seconds after the file appears on the GRIDScaler site before accessing it. If the file is empty on the first attempt, sleep one second or more and read the file again.

4.4 If user creates GPFS snapshot and then migrates file, file could not be read

from GPFS snapshot (EIO) and has zero size after mmrestorefs

Features GRIDScaler-WOS Bridge Recall [DE13442]

Conditions User creates GPFS snapshot with mmcrsnapshot before migration of file and tries to read file from the .snapshot folder or to restore data with mmrestorefs.

Result File cannot be read (read returns I/O error) and has zero size after restoration from snapshot.

Workaround Append random symbol, for example ‘ ’ (space), to migrated file file with

echo ' ' >> file

This action will change DMAPI events on migrated file. After that, file could be read and restored successfully.

(9)

4.5 Synchronization changes may get stuck in WOS Access exception queue

as a result of splitting Bridge and WOS Access environments

Features GRIDScaler-WOS Bridge Synchronization with WOS Access [DE12935]

Conditions Administrator initiates splitting Bridge and WOS Access while users actively change federated namespace from WOS Access side.

Result Some of the changes will not be replicated to GRIDScaler as a result of split procedure and will end up in exception queue. Please note, that it does not affect WOS Access namespace in any way.

Workaround Split GRIDScaler-WOS Bridge and WOS Access during downtime window (to present namespace activities). Please note, that those exceptions will be clean up by WOS Access itself after certain timeout.

4.6 gridconman health will return error along with health checks if there is at

least one migration rule that has not been executed before

Conditions User creates migration rule that is not yet executed by Bridge and calls gridconman health

Result Metrics will be provided, but error will be returned in place of migration rule specific metrics

Workaround Ignore error. It will disappear once migration rule gets processed by Bridge.

4.7 GRIDScaler-WOS Bridge services will not stop correctly if GRIDScaler is in

arbitrating mode

Conditions GRIDScaler is in arbitrating state and user tries to stop Bridge services Result Services may not stop

Workaround Kill GRIScaler-WOS Bridge services manually

4.8 GRIDScaler-WOS Bridge Namespace Synchronization Service cannot

connect to WOS by hostname

Features GRIDScaler-WOS Bridge Namespace Synchronization Service [DE16427]

Conditions Administrator specifies hostname to WOS in SYNC_WOS_HOST parameter in /opt/ddn/nas/etc/wosnas-cluster.conf.

Result Synchronization service will not be able to connect to WOS and will be adding the following errors into log file: “ovfs_mb: [0xbc56e0][consumer] ERROR: can't connect to WOS. Will retry in 16 seconds”.

(10)

4.9 Issues with Reconfiguration of Namespace Synchronization Cluster

Features GRIDScaler-WOS Bridge Namespace Synchronization Service[DE19630, DE19608, DE19526]

Conditions Administrator splits GRIDScaler-WOS Bridge Namespace Synchronization cluster or remove node from it (GRIDScaler-WOS Bridge or WOS Access node).

Result Error is occurred during leaving of node from synchronization cluster, node is still listed as a cluster node.

Workaround Repeat split procedure or procedure of node removing. If node is still listed in output of rabbitmqctl cluster_status, for example nodes br1 and br2

below:

# rabbitmqctl cluster_status

Cluster status of node wosnfs1@wa1 ... [{nodes,[{disc,[wosgs2a@br1,wosgs3a@br2, wosnfs1@wa1]}]}, {running_nodes,[wosnfs1@wa1]}, {cluster_name,<<"wosnfs1@wa1">>}, {partitions,[]}] ...done.

Then from one of the remaining cluster nodes (wa1 in example above) perform command:

rabbitmqctl forget_cluster_node <node>

To remove GRIDScaler-WOS Bridge nodes from the node list. <node> should correspond to the name of a node, listed in output of rabbitmqctl

cluster_status command, for example:

rabbitmqctl forget_cluster_node wosgs2a@br1 rabbitmqctl forget_cluster_node wosgs3a@br2

4.10 If user performs UNMIGRATE –r action on folder, the folders are left in

WOS Access

Features GRIDScaler-WOS Bridge Namespace Synchronization Service [DE19621]

Conditions User performs on GRIDScaler-WOS Bridge node action UNMIGRATE –r for folder in mapped namespace.

Result Folder and its content is unmigrated, but WOS Access still contains information about hierarchy of folders.

Workaround Temporarily rename this unmigrated folder on GPFS, then manually remove folder and its subfolders from WOS Access node. After successful deletion of folder from WOS Access, rename it back on GPFS.

(11)

4.11 User cannot login to Administration User Interface after password has

been changed

Description User cannot login to Administration User Interface after password has been changed in Administration User Interface to value that contains special characters (space, semi-colon, and so on).

Features GRIDScaler-WOS Bridge Administration User Interface [DE19632]

Conditions User changes Administrator password in Administration User Interface to value, containing non-alphanumeric symbols.

Result Changed password doesn't match with user’s input. User cannot login using new password.

Workaround Use only alphanumeric characters for new Administrator password in Administration User Interface. If user cannot login to Administration User Interface, go to GRIDScaler-WOS Bridge node via ssh as root user and change password for admin user:

# passwd admin

4.12 Administration User Interface has incorrect layout, when user opens it via

hostname, not IP address, in Internet Explorer browser.

Features GRIDScaler-WOS Bridge Administration User Interface[DE19524]

Conditions User opens GRIDScaler-WOS Bridge Administration User Interface in Internet Explorer 10 and 11, using hostname as server address. Result Administration User Interface looks incorrect, page layout is broken. Workaround Use IP address of GRIDScaler-WOS Bridge node for access to

Administration User Interface in Internet Explorer or use an alternative browser such as Chrome or Firefox.

5.0 Support

Please contact DataDirect Networks Support at any time for assistance. Support can be reached by these methods:

Telephone

DDN Worldwide Directory http://www.ddn.com/support/contact-support

Email

Support Email [email protected]

Web

Support Portal https://portal.ddnsupport.com Portal Assistance [email protected]

Bulletins

Technical Support Bulletins http://www.ddn.com/technical-support-bulletins Bulletin Subscriptions [email protected]

(12)

GRIDScaler-WOS Bridge