-WOS Bridge Version 1.6.0 Product Release Notes Revision A0 March 2015
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. 2015 DataDirect Networks, Inc. All rights reserved. DataDirect Networks, the DataDirect Networks logo, DDN, DirectMon, EXAScaler,, 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. DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 2
Table of Contents 1.0 OVERVIEW...4 1.1 Environment... 4 1.2 GS-WOS Bridge Product Compatibility... 5 2.0 FEATURES...6 3.0 FIXED DEFECTS...6 3.1 /etc/init.d/wos-connector-mover stop [FAILED] when file was copying on WOS... 6 3.2 Remote clusters may keep files already deleted at local cluster... 6 3.3 Synchronization service log file is rotated on a daily basis and may consume too much space in verbouse log level mode... 6 3.4 -WOS Bridge synchronization service will not start correctly if DMH service is not running... 7 3.5 Incorrect data during FIO... 7 3.6 If value in G2W_MOUNT_POINT doesn t contain / as last character, it will cause errors during cluster joining or policy applying... 7 4.0 KNOWN ISSUES...7 4.1 User gets IO error instead of data if one DMAPI Delegate Read Handler node cannot connect to WOS... 7 4.2 Changelog writer creates JSON command in POSTLINK event for conflict file( with G2W_CR)... 8 4.3 Sometimes if files are read right after snapshot is deployed, files are read as empty ones... 8 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... 8 4.5 Synchronization changes may get stuck in exception queue as a result of splitting Bridge and environments... 9 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... 9 4.7 -WOS Bridge services will not stop correctly if is in arbitrating mode... 9 4.8 -WOS Bridge Namespace Synchronization Service cannot connect to WOS by hostname... 9 4.9 Issues with Reconfiguration of Namespace Synchronization Cluster... 10 4.10 If user performs UNMIGRATE r action on folder, the folders are left in... 10 4.11 User cannot login to Administration User Interface after password has been changed... 11 4.12 Administration User Interface has incorrect layout, when user opens it via hostname, not IP address, in Internet Explorer browser.... 11 5.0 SUPPORT... 11 DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 3
1.0 Overview This document applies to the DataDirect Networks -WOS Bridge v1.6.0 release. -WOS Bridge is a hardware/ software solution designed to enable HSM capabilities (data migration and on demand staging) between DDN and DDN WOS environments. -WOS Bridge utilizes the GPFS Data Management API (DMAPI) to manage data migration between appliances and WOS Storage per customer defined GPFS Policies. The three usage scenarios that -WOS Bridge is designed to support are as follows: Archive - Migrate files to lower cost WOS storage based on GPFS policies to free up disk space on GPFS. Disaster Protection - Copy or move files to remote WOS Sites for data and disaster protection purposes. Collaboration Federate namespaces and share data across other remote and 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 Environment Per above, -WOS Bridge provides HSM/migration capabilities between DDN and DDN WOS products, which must already be installed and configured before -WOS Bridge is added to the configuration. The following versions of and WOS are supported by -WOS Bridge v1.6.0. v2.2.3, 3.0.0, and v3.0.1 Standard edition WOS Core v2.5.2 / WOS7000 & WOS6000 platforms v1.4.2 and v1.4.4 NOTE: -Embedded SFA solutions are not supported in -WOS Bridge v1.6.0. Support for -Embedded SFA solutions will be introduced in further versions of -WOS Bridge. -WOS Bridge is available in the following supported configurations: NSD SFX - Software-only self-extracted archive that is designed to be installed on a NSD server. Gateway Appliance - A packaged hardware/software appliance that includes the -WOS Bridge Software pre-installed on a server/gateway. Up to eight -WOS Bridge gateways may be added to a configuration. -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. -WOS Bridge v1.6.0 also supports upgrade of existing clusters with -WOS Bridge v1.5.1 and higher. DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 4
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 Versions 1.2.3 1.2.4 1.2.5 1.4.2 1.4.4 WOS Core Versions WOS Core 2.2.0 WOS Core 2.2.2 WOS Core 2.5.0 WOS Core 2.5.2 Versions 1.5.0 2.0.0 2.1.0 2.1.1 2.2.3 3.0.0 3.0.1 Platforms WOS 6000 WOS 7000 Note: Blank cells indicate not currently supported. Additional qualifications can be executed on demand. DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 5
2.0 -WOS Bridge v1.6.0 release brings the following new features: 3.0 Fixed Defects Automated upgrade procedure from -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 - WOS Bridge cluster. Automated Backup of file system state, based on a user-defined schedule. Backup status email notifications. 3.1 /etc/init.d/wos-connector-mover stop [FAILED] when file was copying on WOS -WOS Bridge Mover [DE5626: Data mover] Copying of large file to WOS is in progress -WOS Bridge Mover cannot be stopped 3.2 Remote clusters may keep files already deleted at local cluster -WOS Bridge Namespace Update [DE14839] 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. Local file will be removed. Some instances of such file will not be removed from remote 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 -WOS Bridge Namespace Update [DE15048] User enables verbose log level for synchronization service Log file may consume too much disk space in between of daily rotations Enable verbose level only temporarily when it is necessary for issue tracking. DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 6
3.4 -WOS Bridge synchronization service will not start correctly if DMH service is not running -WOS Bridge CLI/Administration [DE14618] DMH service is down and administrator is trying to shut down wosnasreplication service Services will not stop Stop wosnas-replication service prior to stopping DMH. Or kill wosnasreplication service. 3.5 Incorrect data during FIO -WOS Bridge CLI/Administration [DE16427] User runs FIO utility from all GPFS nodes simultaneously FIO fails if it is run from three or more nodes in parallel. 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 -WOS Bridge CLI/Administration [DE17102] Administrator specifies G2W_MOUNT_POINT value without last / in path, like /mnt/gpfs1. 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. 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 -WOS Bridge Recall [DE7923 [Failover][ DMH]] One of DMAPI Delegate Read Handler loses connection to WOS The I/O error is returned on read User has to stop DMAPI Handler on the offending node to protect applications from receiving intermittent I/O errors on migrated files and let -WOS Bridge migrate the DMAPI Handler role to another node. Alternatively, the user may restore connection to WOS and - DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 7
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) -WOS Bridge Recall [DE8128 [DMH]] User creates hardlink to a file generated by conflict resolution (filex.conflict.y with G2W_CR extended attribute). Hardlink is replicated to remote cluster and remains in the NS Sync exception queue there. Thus, this hardlink will not be restored in remote clusters. 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 -WOS Bridge Administrator s Guide. 4.3 Sometimes if files are read right after snapshot is deployed, files are read as empty ones -WOS Bridge Backup [DE11209 [Backup]] User attempts to read the file that was restored from snapshot immediately after file creation (1-2 seconds) File is empty. Allow three seconds after the file appears on the 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 -WOS Bridge Recall [DE13442] 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. File cannot be read (read returns I/O error) and has zero size after restoration from snapshot. 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. DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 8
4.5 Synchronization changes may get stuck in exception queue as a result of splitting Bridge and environments -WOS Bridge Synchronization with [DE12935] Administrator initiates splitting Bridge and while users actively change federated namespace from side. Some of the changes will not be replicated to as a result of split procedure and will end up in exception queue. Please note, that it does not affect namespace in any way. Split -WOS Bridge and during downtime window (to present namespace activities). Please note, that those exceptions will be clean up by 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 -WOS Bridge CLI/Administration [DE16170] User creates migration rule that is not yet executed by Bridge and calls gridconman health Metrics will be provided, but error will be returned in place of migration rule specific metrics Ignore error. It will disappear once migration rule gets processed by Bridge. 4.7 -WOS Bridge services will not stop correctly if is in arbitrating mode -WOS Bridge CLI/Administration [DE14683] is in arbitrating state and user tries to stop Bridge services Services may not stop Kill GRIScaler-WOS Bridge services manually 4.8 -WOS Bridge Namespace Synchronization Service cannot connect to WOS by hostname -WOS Bridge Namespace Synchronization Service [DE16427] Administrator specifies hostname to WOS in SYNC_WOS_HOST parameter in /opt/ddn/nas/etc/wosnas-cluster.conf. 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. Specify IP address instead of hostname. DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 9
4.9 Issues with Reconfiguration of Namespace Synchronization Cluster -WOS Bridge Namespace Synchronization Service[DE19630, DE19608, DE19526] Administrator splits -WOS Bridge Namespace Synchronization cluster or remove node from it (-WOS Bridge or node). Error is occurred during leaving of node from synchronization cluster, node is still listed as a cluster node. 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 -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 Bridge Namespace Synchronization Service [DE19621] User performs on -WOS Bridge node action UNMIGRATE r for folder in mapped namespace. Folder and its content is unmigrated, but still contains information about hierarchy of folders. Temporarily rename this unmigrated folder on GPFS, then manually remove folder and its subfolders from node. After successful deletion of folder from, rename it back on GPFS. DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 10
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). -WOS Bridge Administration User Interface [DE19632] User changes Administrator password in Administration User Interface to value, containing non-alphanumeric symbols. Changed password doesn't match with user s input. User cannot login using new password. Use only alphanumeric characters for new Administrator password in Administration User Interface. If user cannot login to Administration User Interface, go to -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. -WOS Bridge Administration User Interface[DE19524] User opens -WOS Bridge Administration User Interface in Internet Explorer 10 and 11, using hostname as server address. Administration User Interface looks incorrect, page layout is broken. Use IP address of -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 Web Support Portal Portal Assistance Bulletins Technical Support Bulletins Bulletin Subscriptions support@ddn.com https://portal.ddnsupport.com webportal.support@ddn.com http://www.ddn.com/technical-support-bulletins support-tsb@ddn.com DataDirect Networks -WOS Bridge V1.6.0 Product Release Notes 11
World Headquarters 9351 Deering Avenue Chatsworth, CA 91311 ddn.com Phone: +1.818.700.7600 Fax: +1.818.700.7601