Users Guide.book

Crosswalk® iGrid 1.5

User’s GuideDocument Number IGRID_UG_1.5

July 12, 2006Crosswalk, Inc.11000 Westmoor Circle, Suite 300Westminster, Colorado 80021-2722Phone: 303.635.7800Toll Free: 1.866.626.5786Fax: [email protected]

DRAFT - Confidential and Proprietary — For internal use onlyDo not disclose or distribute without the express written consent of Crosswalk, Inc.

Copyright © 2005-2006 Crosswalk Inc. All rights reserved.

Crosswalk is a registered trademark of Crosswalk, Inc., 11000 Westmoor Circle, Suite 300, Westminster, CO 80021. All other company and product names may be trademarks of their respective owners.

Published July 12, 2006.

No part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written consent of Crosswalk, Inc.

The information contained in this document is subject to change without notice. Crosswalk, Inc. assumes no responsibility for any errors that may appear.

All computer software programs, including but not limited to microcode, described in this document are furnished under a license, and may be used only in accordance with the terms and conditions of such license. Crosswalk, Inc. either owns or has the right to license the computer software programs described in this document, and retains all rights, title and interest in such computer software programs.

Crosswalk, Inc. makes no warranties, expressed or implied, by operation of law or otherwise, relating to this document, the products or the computer software programs described herein, except as set forth in the license agreement. Crosswalk Inc. DISCLAIMS ALL IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. In no event shall Crosswalk Inc. be liable for (a) incidental, indirect, special, or consequential damages or (b) any damages whatsoever resulting from the loss of use, data or profits, arising out of this document, even if advised of the possibility of such damages.


– TABLE OF CONTENTS –

This User’s Guide and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vIntended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vFormat and Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vOrganization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiGrid Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiRelated Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1 Overview of the iGrid Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1New in iGrid 1.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Overview of iGrid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Grid Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Multi-Protocol Gateway Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4File Access Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Volume Access Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Data Management Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2 Getting Started with Crosswalk iGrid . . . . . . . . . . . . . . . . . . . . . . . . 9Installing the Crosswalk iGrid Client Software on a Windows Machine. . . . . . . . . . . . . . . . . . . . . . 10

License Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Choosing Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Finishing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Installing the Crosswalk iGrid Client Software on a Linux Machine . . . . . . . . . . . . . . . . . . . . . . . . 18Logging In To the Crosswalk iGrid Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Getting Started With iGrid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Manage iGrid Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Add a New User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Edit a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

iGrid Quickstart Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Create a New Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Create a Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Create a File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Export File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

DRAFT - Confidential and Proprietary — For internal use only iDo not disclose or distribute without the express written consent of Crosswalk, Inc.

Chapter 3 iGrid Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Authentication and Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Management Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45CIFS Shares Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Quota Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Lock Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Virtual IP Address Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Event Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Filtered Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Load Balancing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Create a Load Balancing Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Assign a Load Balancing Policy to a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Delete a Load Balancing Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Forcing a Load Balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 4 iGrid Storage Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Logical Unit Numbers (LUNs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

LUN Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58LUN Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Available LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Remove a LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Pool Semantics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Display Current Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Create a New Storage Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Expand a Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Delete a Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Display Current Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Create a Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Expand a Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Delete a Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Mount a File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Create a File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Managing Exported File Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Map a CIFS Share to Two Windows Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Managing Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Create a New Snapshot Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Suspend or Resume a Snapshot Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Export a Snapshot Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Export an Individual Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

NetVault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

ii DRAFT - Confidential and Proprietary — For internal use onlyDo not disclose or distribute without the express written consent of Crosswalk, Inc.

Chapter 5 iGrid User Interface Features and Functions . . . . . . . . . . . . . . . . . . 95iGrid Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Viewing Node Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Viewing IP Address Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Viewing Drive (LUN) Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Viewing Storage Pool Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Viewing File System Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

iGrid Node Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Maintaining Minimum Node Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Viewing All Nodes On the Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Connecting to Another Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Leave the Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Rejoin a Node to a Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Remove a Node from a Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Shut Down All Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Chapter 6 iGrid Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . 113Command Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Introduction to CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115CLI Help Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Command Set Help Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117about Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118availableluns Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119cluster Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121events Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123exports Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125lbpolicies Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132nodes Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134ipswitches Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141quotas Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150snapshots Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153storagepools Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157users Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161volumes Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

DRAFT - Confidential and Proprietary — For internal use only iiiDo not disclose or distribute without the express written consent of Crosswalk, Inc.

Appendix A Using BakBone’s® NetVault™ with Crosswalk iGrid . . . . . . . . . 171Installing BakBone’s NetVault Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Configuring a Linux Machine for NetVault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Configuring a Windows 2000/2003 Machine for NetVault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Set Up NetVault in iGrid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Create a Virtual Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Backing Up with Crosswalk iGrid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Network Data Management Protocol (NDMP) – Configure Job. . . . . . . . . . . . . . . . . . . . . . . . . 186Create Backup Job/Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Invoke NetVault Client (Agent) on a Node To Be Backed Up . . . . . . . . . . . . . . . . . . . . . . . . . . 216Installation of NetVault Backup Client Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218NetVault Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Restoring with Crosswalk iGrid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Restore Window Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Server Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Restore Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Performing A Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Appendix B Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Index of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

iv DRAFT - Confidential and Proprietary — For internal use onlyDo not disclose or distribute without the express written consent of Crosswalk, Inc.

This User’s Guide and Support

This User’s Guide describes how to set up, configure, and use Crosswalk iGrid. The tasks described in this User’s Guide are not intended to present a fully comprehensive description of everything the Crosswalk iGrid system is capable of; but rather, the features and functions described here are those most likely to be of use to people using Crosswalk iGrid.

This guide does not include installation and initial configuration instructions, which will be performed by trained Crosswalk personnel. It assumes that Crosswalk has installed and tested your iGrid system with site-specific data, assigned VIP and node IP addresses, and established a basic set of LUNs.

Intended Audience

This User’s Guide is intended for system, network, and storage administrators; IT managers; professional services personnel; system engineers; storage network designers and architects; asset management personal, and others who install, configure, use, and manage networks, systems, system backups, load balancing, assets, and perform other storage tasks and functions. Some familiarity with Grid Computing technology is helpful.

Format and Assumptions

This User’s Guide is process- and procedure-oriented; it focuses on the functions, tasks, and steps necessary to set up, configure, and use Crosswalk iGrid. This Guide describes what to do and what happens when you do it; the graphics show you exactly what you should expect to see on your screen. The text also contains some explanatory notes, cautions and warnings. The content level was written based on the assumption that you are familiar with Grid Computing technologies, as well as storage, server, network, system and database administration.

Crosswalk iGrid

v

Organization

Organization

This User’s Guide is organized, as much as possible, to reflect the logical way that the user interface will appear on your monitor. The User’s Guide contains the following chapters, sections, and other parts.

• Chapter 1, Overview of the iGrid Product, provides an overview of the functionality, features, capabilities, and uses of Crosswalk iGrid, as well as what is new in the current version.

• Chapter 2, Getting Started with Crosswalk iGrid, describes how to install, set up, and configure Crosswalk iGrid. It includes a quick start guide for creating and exporting shared volumes.

• Chapter 3, Administration, covers many of the transparent administration and ‘housekeeping’ functions of iGrid.

• Chapter 4, Crosswalk iGrid Storage Manager, describes how to use LUNs, pools, and volumes as building blocks for creating and exporting file systems.

• Chapter 5, Crosswalk iGrid Features and Functions, describes how Crosswalk iGrid can help you reduce expenses and increase efficiency in managing your storage resources.

• Chapter 6, Command Line Interface, describes the CLI commands available to users of iGrid.

• Appendix A, Using BakBone’s® NetVault™ with Crosswalk iGrid, describes how to use BakBone’s NetVault backup and restore functionality with Crosswalk iGrid.

• Appendix B, Glossary

• Index

Crosswalk iGrid

vi

iGrid Support

iGrid Support

Crosswalk provides both telephone and on-line support.

Website: www.crosswalkinc.com Email: [email protected] Phone: 303.635.7900 Toll Free: 1.866.626.5786 Fax: 303.635.7801

Related Documentation

The following other documents provide additional information for using Crosswalk iGrid.

• BakBone Software NetVault Administrators’ Guide, which can be obtained from BakBone Software, Inc. The BakBone Web site is at http://www.bakbone.com/

• BakBone Software NetVault Implementation Guide for the NDMP APM and Network Appliance, which can be obtained from BakBone Software, Inc. The BakBone Web site is at http://www.bakbone.com/

• The Dictionary of Storage Networking Technology, which can be obtained from the Storage Networking Industry Association (SNIA) Web site at http://www.snia.org/

Crosswalk iGrid

vii

Related Documentation

Crosswalk iGrid

viii

– CHAPTER 1 –

Overview of the iGrid Product

This chapter provides an overview of the functionality, features, and capabilities of Crosswalk iGrid, as well as new features and improvements to the product in Version 1.5.

New in iGrid 1.5

• The most visible change in the Crosswalk iGrid product is the Graphical User Interface (GUI). Tasks have been logically organized in a multi-windows environment which allows for the user to organize open windows as cascading, tiled or hidden.

• Procedures for contacting and getting Crosswalk support have been added to the Introduction on page vii.

• Snapshot capabilities have been expanded to include export of a complete snapshot schedule, in addition to exporting a single instance.

• Crosswalk now offers both internal and external methods of authentication and authorizing users for the iGrid system. See the Chapter 3, iGrid Administration, for more details.

• Improved lock management assures that multiple nodes cannot obtain conflicting lock information. Refer to Chapter 3, iGrid Administration, on page 48.

• Quota management is now available via both the graphical user interface and CLI commands. Refer to Chapter 3, iGrid Administration, on page 46.

• The addition of Command Line Interface (CLI) command sets provides an alternative to grid management via the GUI. Refer to the iGrid Command Line Interface (CLI) chapter on page 113.

• Improved statistics and methods to access statistical information has been added to GUI. Refer to Chapter 5, iGrid User Interface Features and Functions, on page 95.

• The Windows standard ability to position windows in tiles, cascading or full screen.


1

Overview of the iGrid Product Overview of iGrid

Overview of iGrid

iGrid is a scalable, clustered platform that provides a complete range of file access to data and pooled storage resources within a networked environment.

The iGrid Graphical User Interface (GUI) is the primary management method for communicating with the nodes in a grid. Crosswalk iGrid is a Java application that runs on any operating system that supports Java.

iGrid features and functionality are divided into the following basic areas:

• Grid platform capabilities, including load balancing, high-availability features, scalability and integration within the network environment.

• Multi-protocol gateway services, including the protocols that initiate and terminate requests within iGrid.

• File access services, including types of file systems supported, types of client access, user and group access controls, and administrative capabilities pertaining to the file space.

• Volume access services, including control over storage resources underneath the file services and remote client access to shared storage pools where iGrid acts as a logical storage device or target within a networked environment.

• Data management services, including data copying, replication, migration, backup, and restore.

• Monitoring, Management, and Control, including how the system is measured, how critical events are defined and accessed, how resources are configured and installed, and how external applications interact with iGrid during installation, maintenance, upgrade, and operation.


2

Grid Platform Overview of the iGrid Product

Grid Platform

iGrid currently supports grid (clustered) configurations from a minimum of two nodes to as many as eight nodes. Future versions of iGrid will support configurations beyond the current maximum node limit. A grid is accessed as a single resource, typically with a single IP address.

• The iGrid system presents multiple Virtual IP Addresses (VIPs) on the data network from which every NFS export and CIFS share is accessible.

• A grid supports effective load balancing so that run-time load demands cause workloads to shift to other nodes such that each node’s performance and throughput conforms to its user-specified load balancing policy.

• All nodes in a grid have simultaneous, shared access to all file systems and all volumes.

• A grid supports active-active failover for file access. Since all nodes are in an active mode servicing requests, any node can potentially recover from a failure of another node.

• iGrid’s high availability aspects benefit any third-party applications whose data is serviced by iGrid.

• Control over load balancing and failover is handled within the grid itself. However, it might be necessary to rely on external load-balancing devices in front of the grid, such as a load balancing IP switch.


3

Overview of the iGrid Product Multi-Protocol Gateway Services

Multi-Protocol Gateway Services

iGrid uses the following network protocols and connectivity:

• GigE connectivity, including TCP/IP and User Datagram Protocol (UDP), used for front-end and heartbeat networks.

• Fiber Channel (FC) connections for back-end storage access.

iGrid supports separate management Local Area Network (LAN) connections from the client data-access LANs and back-end networks.

iGrid supports the following services:

• Network Time services and integration

• Active Directory Services and integration

• Kerberos 5 for CIFS authentication


4

File Access Services Overview of the iGrid Product

File Access Services

The primary purpose of utilizing Grid Computing capability is to allow centralized management and control over network-based file systems. Therefore, iGrid can support a large number of mounted file systems simultaneously, with a scalable level of performance and throughput for a large number of host-server clients. Although new file protocols are evolving and future protocols are anticipated, iGrid currently supports the following common file protocols to date:

• iGrid supports multiple file systems of NFS v3 and CIFS.

• Every NFS export and CIFS share is accessible through each iGrid node.

• iGrid controls access to files at the export level via file and directory permissions on a user and group basis.

• iGrid supports commands and controls to allow administrators and users to create new file systems, delete existing file systems, export file systems, control access, and monitor IP traffic and grid load.

• The file systems within iGrid can be dynamically expanded through the volume management layer.

• iGrid file systems and files are accessible through all nodes within the grid.


5

Overview of the iGrid Product Volume Access Services

Volume Access Services

Because a major goal of iGrid is to enable flexible sharing of pooled storage resources with simple centralized management, volume management capabilities are critical to iGrid. The volume management layer is the main point for delivering value-added services and capabilities. Use it to allow volumes to be fully accessible across all iGrid nodes and be expanded dynamically.

Volume elements can reside across any heterogeneous physical devices including multi-vendor arrays, different storage technology, such as Serial Advanced Technology Attachment (SATA), and JBODs.


6

Storage Manager Overview of the iGrid Product

Storage Manager

• The Storage Manager manages storage pools that group Logical Unit Numbers (LUNs) together.

• The Storage Manager manages both physical (LUNs) and logical volume elements (volumes) and handles volume types uniformly.

• The Storage Manager can define stripe sets or levels of volumes, across heterogeneous volume elements so that each volume can reside on a different type of device, and each volume can be allocated across a volume set.


7

Overview of the iGrid Product Data Management Services

Data Management Services

In addition to providing file access, iGrid is a platform for common value-added data management operations. iGrid supports the following data management services:

• Backup and restore functions. iGrid integrates well with Bakbone’s NetVault, which Crosswalk personnel are trained to configure, and also supports Tivoli Storage Manager, VERITAS NetBackup, and Arkeia Smart Backup/Network Backup.

• Point-in-time snapshots of volumes and time-based incremental copies of volume changes (deltas)

• Scheduled event notification to a distribution list


8

– CHAPTER 2 –

Getting Started with Crosswalk iGrid

This chapter describes how to install, set up, and configure Crosswalk iGrid. It includes instructions for setting up users and groups, as well as a quickstart guide to help you get up and running iGrid as soon as possible.

This chapter is organized as follows:

• Installing the Crosswalk iGrid Client Software on a Windows Machine on page 10

• Installing the Crosswalk iGrid Client Software on a Linux Machine on page 18

• Logging In To the Crosswalk iGrid Client Software on page 23

• Getting Started With iGrid on page 25

• iGrid Quickstart Guide on page 29


9

Getting Started with Crosswalk iGrid Installing the Crosswalk iGrid Client Software on a Windows Machine

Installing the Crosswalk iGrid Client Software on a Windows Machine

This section describes how to install and log in to the Crosswalk iGrid client application software on a Microsoft Windows system. To start the installation process, do the following.

1. Place the Crosswalk iGrid installation disk in the CD drive.

2. Open the AutoInstaller file by double-clicking the icon (as seen below) or selecting File -> Open from the Explorer window.

Figure 2-1 Run iGrid Installer

• The installation preparation begins running.

Figure 2-2 Installation Progress Bar


10

License Agreement Getting Started with Crosswalk iGrid

• After the installation process begins, the Introduction dialog box appears.

Figure 2-3 Introduction

3. Click Next

• The License Agreement dialog box appears. The default option is I do NOT accept the terms of the License Agreement.

License Agreement

This section describes how to accept the license agreement. First, read the entire license agreement. Use the scroll bar on the right side to reveal the license agreement text in its entirety.

The installation will terminate if the terms are not agreed to and accepted. In summary, the agreement states that the user is entitled to install and use the agreed upon number of licenses for the iGrid software, and details the warranty and support services offered by Crosswalk.

To decline the license agreement, do the following:

1. To terminate the installation process, click Cancel.

2. In the Installation Not Complete dialog box, click Quit.

• The License Agreement dialog box closes.

• The installation process terminates.

To accept the license agreement and continue the installation process, do the following:


11

Getting Started with Crosswalk iGrid License Agreement

1. Read the license agreement.

The I accept the terms of the license agreement option is available only after you have reached the end of the text.

2. Select I accept the terms of the license agreement.

The Next button becomes active.

3. Click Next.

The Choose Install Folder dialog box appears.


12

Choosing Installation Options Getting Started with Crosswalk iGrid

Figure 2-4 Choose Install Folder

Choosing Installation Options

This section describes how to choose the folder in which to install iGrid and where to place the program shortcut.

Choose the Installation Destination

To maintain the integrity of the iGrid application and to ensure compatibility with other Crosswalk applications, Crosswalk recommends accepting the default destination, C:\Program Files\Crosswalk\iGrid Client.

• To accept the default installation destination, click Next.

• To choose another destination, do the following:

1. Type the destination path in the Where Would You Like to Install? text box.

2. Click Next.

The Choose Shortcut Folder dialog box appears.


13

Getting Started with Crosswalk iGrid Choosing Installation Options

Figure 2-5 Choose Shortcut Folder

Choose a Shortcut Option

This section describes how to choose whether or not to create a shortcut, where the installation process creates the shortcut, and whether to create shortcuts for all users.

You can select only one location for creating an iGrid shortcut. You can also choose to not create a shortcut; however, Crosswalk recommends that you create a shortcut to facilitate starting the application. The default selection is In a new Program Group. When this is the initial installation of Crosswalk iGrid, Crosswalk recommends accepting the default selection to facilitate finding the icon and starting the product.

Crosswalk also recommends creating shortcut icons for all users.

• To create a shortcut, do the following:

1. To accept the default shortcut location, click Next.

The Pre-Installation Summary dialog box appears.

• To create a shortcut in another program group, do the following:

1. Select In an existing Program Group.

2. Choose the program group from the drop-down list.

3. Click Next.



14

Choosing Installation Options Getting Started with Crosswalk iGrid

• To create the shortcut on the start menu, select In the Start Menu.

• To create the shortcut on the desktop, select On the Desktop.

• To create the shortcut on the Quick Launch Bar, select In the Quick Launch Bar.

• To create the shortcut in another location, to the following:

1. Select Other.

2. Type the location path in the Other text box.

Alternatively, you can click Choose and navigate to the location.

3. Click Next.


• To not create a shortcut, do the following:

1. Select Don’t create icons.

2. Click Next.


Figure 2-6 Pre-Installation Summary

Review the product information before continuing.


15

Getting Started with Crosswalk iGrid Finishing the Installation

Finishing the Installation

To finish the installation, do the following:

1. In the Pre-Installation Summary dialog box, if all information is correct, click Install.

• The Installing iGrid Client window shows the installation progress until complete.

Figure 2-7 Crosswalk iGrid 1.0 Installation - Progress Bar

• When the installation is complete, the Install Complete dialog box appears.


16

Finishing the Installation Getting Started with Crosswalk iGrid

Figure 2-8 Install Complete

Note: The Cancel and Previous buttons are inactive and cannot be activated. At this stage of the installation, you can neither cancel the installation nor go back to a previous dialog box.

2. To finish the installation, click Done.

The installation process is complete.

The Install Finished dialog box closes.

If you chose to create a shortcut on your desktop, the iGrid shortcut icon appears on the desktop, but not in the Start menu.

Figure 2-9 Crosswalk IGrid Icon

If you elected to include the Crosswalk iGrid startup command on the start menu, the startup command does not appear on the desktop.


17

Getting Started with Crosswalk iGrid Installing the Crosswalk iGrid Client Software on a Linux Machine

Installing the Crosswalk iGrid Client Software on a Linux Machine

This section describes how to install and log into the Crosswalk iGrid client application software on a Linux machine. To start the installation process, log in as root and do the following:

1. Place the Crosswalk iGrid installation disk in the CD drive.

2. Execute the iGridClientInstaller.bin file from the Disk1/InstData/VM/ directory of the CD.

3. The installation process begins and you are presented with the Introduction screen. Click Next.


18

Installing the Crosswalk iGrid Client Software on a Linux Machine Getting Started with Crosswalk iGrid

The License Agreement dialog box appears. The default option is I do NOT accept the terms of the License Agreement.

To terminate the installation process at this point, click Cancel. In the Installation Not Complete dialog box, click Quit. The installation process terminates.

To continue the installation process you must read and scroll to the bottom of the license agreement and select I accept the terms of the License Agreement and proceed to step 4. For a summary of this agreement see the License Agreement section on page 11.

4. Click Next.

The Choose Install Folder dialog box appears.


19


5. Select a destination install folder.

a. To accept the default destination, click Next.

b. To choose another destination, type the destination path in the Where Would You Like to Install? text box or browse to the folder path by clicking the Choose... button.

6. Click Next.

The Chose Link Folder dialog box appears.

7. Select a destination link folder.

a. To accept the default link location, click Next.


20

Installing the Crosswalk iGrid Client Software on a Linux Machine Getting Started with Crosswalk iGrid

b. To create a link in another location, select the Other radio button and enter the path where you wish to place a link, or click Choose to browse your computer.

8. Click Next.


9. Review the product information before continuing with the install.


21


10. Proceed with the installation by clicking Install on the Pre-Installation Summary page.

The Installing iGrid Client window will show the progress of the install.

When the installation is complete, the Install Complete window appears.

11. To finish the installation, click Done. The installation is now complete.


22

Logging In To the Crosswalk iGrid Client Software Getting Started with Crosswalk iGrid

Logging In To the Crosswalk iGrid Client Software

This section describes how to log in to the Crosswalk iGrid client software. The IP Address drop-down list is populated as users connect to IP addresses. It does not initially come with IP addresses populated.

All iGrid features and functionality are based on user names or permissions.

1. To open Crosswalk iGrid, click on the iGrid icon or select iGrid from the All Programs list in the Start menu..

The Crosswalk iGrid Login dialog box appears.

2. In the Login text box, type your user name. User names should correspond with the way they are set up on your servers.

Figure 2-10 Crosswalk iGrid Login

3. In the Password text box, type your password.

4. Enter the management VIP address, one of two ways.

• In the Address text box, type the management VIP address of the Crosswalk iGrid server.

• Select the VIP Address from the Addresses drop-down list. Only addresses that have been used to log into the system in the past will be listed in the drop-down list.

5. Click Ok.


23

Getting Started with Crosswalk iGrid Logging In To the Crosswalk iGrid Client Software

The main Crosswalk iGrid window defaults to a list of nodes installed on the grid and the VIPs for selected nodes.

Allow several seconds for all node data to fully populate and appear in the window.

iGrid operates in a multi-window environment which are configurable to cascade or tile by using the Windows menu.

• To manage exports, volumes, pools and LUNs, and quotas, use the Storage menu.

• Manage nodes through the Cluster menu.

• View node, IP address, LUN, pool and export statistics from the Statistics menu.

• Users, events, and load balancing polices are handled from the Tools menu.

• At the Windows menu, the multi-window environment is managed and open windows may be tiled, cascaded or hidden.

• From the Help menu, you can get information about your version of iGrid, access on-line help and the Crosswalk website.


24

Getting Started With iGrid Getting Started with Crosswalk iGrid

Getting Started With iGrid

Manage iGrid Users

Users are managed in the GUI under the Tools menu. Users may also be managed via the /users command set in the Command Line Interface. Please refer to the Users section in Chapter 6, iGrid Command Line Interface (CLI), on page 161.

Select the Tools menu at the top of the iGrid GUI to add, delete and edit iGrid users. Names, E-mail addresses, alerts, cluster and storage management privileges can all be edited once a user has been created.

Add a New User

When you choose the Tools menu option in the iGrid GUI, click on Users to bring up the User’s window.

Figure 2-11 Users


25

Getting Started with Crosswalk iGrid Add a New User

Figure 2-12 User’s Window


26

Add a New User Getting Started with Crosswalk iGrid

To add a new user:

1. Click the New... button at the bottom of the Users window.

Figure 2-13 Create New User

2. Enter the new User Name.

Note: Whether managing users through your active directory server, Kerberos server, or internally via the GUI, the user name you choose must exactly match the user name on your servers.

3. Enter user password and verify.

4. Enter new user’s email address.

5. Set which alerts the user shall be notified of: Fatal, Error, Warning, Audit, Threshold, Information.

Alerts are sent to users via email.

6. Choose the radio buttons which match the permissions the user will have for cluster and storage management. None is not available for Cluster management.

7. Click OK and the user is added to iGrid.


27

Getting Started with Crosswalk iGrid Edit a User

Edit a User

To edit an existing user in the GUI, follow these instructions:

1. Choose from the list of user’s and select the one you wish to edit.

2. Click on the Edit button in the User’s window and the Edit window opens.

Figure 2-14 Edit User

3. Change information in any of the available user fields: E-Mail Address, Alert Severities, Cluster Management or Storage Management. User Name is not editable.

4. Click OK when done and the user information will be updated for that iGrid user.


28

iGrid Quickstart Guide Getting Started with Crosswalk iGrid

iGrid Quickstart Guide

This quickstart guide provides a basic procedural outline for what is required to get an exported file system up and running. It covers creation of a pool from existing LUNs, a volume from a pool and a file system from a volume. When complete, you will have accomplished the following:

• A new pool is created with a new name.

• A new volume is created with a new name.

• A shareable file system on the volume is created with a new name.

• The newly created volume is exported.

• A file system is created and mounted from the export.

To get an iGrid file system up and running, follow the steps in this section.


29

Getting Started with Crosswalk iGrid Create a New Storage Pool

Create a New Storage Pool

1. Use the Storage menu and select Storage Pools.

2. The Storage Pools window opens to list all created pools, their assigned LUNs and your options for them.

Figure 2-15 Storage Pools


30

Create a New Storage Pool Getting Started with Crosswalk iGrid

3. Click New... at the bottom of the storage pool listing.

The Create New Pool dialog box appears.

Figure 2-16 Create New Pool

4. Type a name in the Storage Pool field. If you type a name that is already in use, an error message appears.

Note: Naming conventions suggest you to use only alphanumeric characters and these three special characters: _s, -s, and .s.

5. From the Extent (in KB) drop-down list select the extent size for the pool. 128 Kb is Crosswalk’s standard recommendation.


31

Getting Started with Crosswalk iGrid Create a New Storage Pool

6. Select the LUNs to assign to this pool. Hold the Shift key down to select multiple LUNs in the list. use the left and right arrow buttons to move LUNs from Available to Selected.

As long as the default stripe width is unchanged, a pool may be created with any available LUNs, rather than only LUNs of the same size.

CAUTION—A pool should always be created with a minimum of two LUNs, as a volume cannot be created from a pool with less than two LUNs assigned to it.

7. After selecting the LUNs, click Ok.

The new pool will appear in the list after a few moments.


32

Create a Volume Getting Started with Crosswalk iGrid

Create a Volume

1. Use the Storage menu on the GUI and select Volumes.

2. A list of volumes on this grid and your options for them will appear in the Volumes window.


33

Getting Started with Crosswalk iGrid Create a Volume

3. Click New... at the bottom of the page. The Create Volume window appears.

Figure 2-17 Create New Volume

Note: The Create Volume window shows the reserved and available space for volume creation.

4. Type a name in the Volume field and select the newly created pool from the Storage Pool drop down menu.

Note: For volumes, the names “snapshot” and “nvbackup” are reserved for system use and may not be used.

5. Select the desired stripe width. Crosswalk suggests leaving the Stripe Width at the default value, which is the number of LUNs used in this volume.


34

Create a Volume Getting Started with Crosswalk iGrid

6. Choose GB or TB units from the Total Size dropdown menu and enter the total size.

The total size must be a percent of the free space and be at least 2.1GB.

When you attempt to create a volume that exceeds the remaining pool availability, a message appears that tells you to try a smaller volume size.

Note: When adding a file system, the journals take up an additional 2GB of file space. For example, a volume created at 6GB and labelled 6GB will actually have 4GB of free space.

7. Click OK. The new volume is created. Rebuilding the volume list with the new volume added may take a few minutes.


35

Getting Started with Crosswalk iGrid Create a File System

Create a File System

1. From the Volume menu, select the new volume you just created (or a volume already created) and click on Create File System at the bottom of the screen.

2. The Create New File System dialog box opens and you are required to confirm your choice. Leave the Mount box checked (default).

3. Once confirmed, a new file system will be created.

4. Once the file system is created, you will notice that the Status column in the Volume list has changed.


36

Export File System Getting Started with Crosswalk iGrid

Export File System

1. Using the Storage menu, choose Exports and a list of all exported file systems will appear.

Figure 2-18 Exports

2. Click New... from the option buttons at the bottom of the window. The New CIFS/NFS window opens.

From the Type field, choose which export is being created: CIFS or NFS.


37

Getting Started with Crosswalk iGrid Export File System

The following describes the procedure to create a new CIFS export.

1. If you select CIFS as the Type, the New CIFS dialog box will appear.

Figure 2-19 New CIFS

2. Select a volume from the drop down menu provided.

3. Enter a name for the export in the Export Name field.

4. Choose a Destination Directory from the directory tree using the Browse... button. This will be where all data for this export is stored. This field is optional. If left blank, any data written to this share will be stored in the root directory.

5. Create a list of users who can access the CIFS share by entering the user name exactly as it appears in the active directory or Kerberos server.


38


Enter the user name in the field provided and use the Add button to add them to list of approved users. You may also use the Remove button to take them off of the list.

Figure 2-20 CIFS Users

6. Use the drop down menus to select permissions for Everybody, Group and User. You may wish to select Read but not write if you want a Unix client to read the same data as a Windows server, but not be able to write to it, and vice versa.

Figure 2-21 Set CIFS Permissions

7. Click OK.

The “Creating share [share name]” message appears on the screen while the share is being built.

8. When the share is created, it will be listed in Exports window.

The iGrid system is now set up with an exported volume.


39


The following describes the procedure to create a new NFS export.

1. If you select NFS as the Type, the New NFS dialog box will appear.

Figure 2-22 New NFS





40


Figure 2-23 NFS Permissions and Hosts

5. Choose the Squash Setting. The squash setting is a security function used to block certain users by assigning them an anonymous user ID (nfsnobody).

• None - Users and root are mapped to themselves and use their default privileges.

• Root - Root is squashed and mapped to the nfsnobody ID.

• All - Both users and root are mapped to the nfsnobody ID.

6. Add hosts by entering host names or IP addresses (preferable) using the Add button. Hosts may also be deleted from the list using the Remove button.

7. Use the drop down menu to select permissions for Everybody. You may wish to select Read but not write if you want a Unix client to read the same data as a Windows server, but not be able to write to it, and vice versa.

8. Click OK.





41



42

– CHAPTER 3 –

iGrid Administration

iGrid offers many administrative functions that keep the grid system running efficiently..


• Authentication and Authorization on page 44

• Quota Management on page 46

• Lock Management on page 48

• Event Notification on page 50

• Load Balancing on page 52

• Backups on page 56


43

iGrid Administration Authentication and Authorization

Authentication and Authorization

Within iGrid there are two types of users: Management and CIFS.

Management administrative users require a user account so that managers may log into both the GUI and the Command Line Interface (CLI). CIFS users who are mapping CIFS shares from the grid into a Windows environment have the option of being created internally (via the GUI) or externally (i.e., Kerberos or ADS).

During installation of iGrid, you will be asked whether user authentication will be managed internally (via the GUI) or externally. If external, you will be prompted to enter configuration information that will point to the server where management will take place. See the Crosswalk document, iGrid Installation and Configuration, for details or speak with Crosswalk support personnel.

If user administration is performed internally, all permissions are assigned to users in the iGrid GUI under the Tools menu by choosing the Users window. It has the advantage of centralizing management of authentication information.

During installation, if the “internal” option for maintaining users is chosen, each user must be added in the user interface before they can map to a CIFS share. As a rule, Crosswalk suggest that CIFS users be managed externally on your active directory server. However, if there are only a few CIFS users, ‘internal’ management is suggested as a best practice.

Management users should always be managed internally via the GUI.

CAUTION—Once installation is complete and a determination has been made to manage users via the GUI or the server, this decision cannot be undone without reinstalling iGrid.


44

Management Users iGrid Administration

Management Users

The list of management users is shown under the Tools menu of the GUI. When Users is selected, they are displayed in the Users window. The following information is provided for each user:

• Name

• E-mail Address

• Alert Severities

• Storage Management

• Cluster Management

From the Management User’s window, you can add new users, edit existing users and change management user passwords. Refer to Chapter 2, Getting Started with Crosswalk iGrid, Manage iGrid Users on page 25 for information on entering and editing management-level users in iGrid.

CIFS Shares Users

The list of CIFS Shares Users is shown under the Tools menu of the GUI, if ‘internal’ was chosen during system configuration. If ‘external’ management of CIFS users was chosen during configuration, this option will not be visible in the GUI.

When “CIFS User Management” is selected, CIFS users are displayed in the editing window. The following information is provided for each user:

• User name

From the CIFS User’s window, you can add new users and change user passwords.

Adding a New CIFS Share User

To add a new CIFS user, do the following:

1. Click on New in the CIFS User Management window. The Create New User dialog box opens.

2. Enter the User Name. Crosswalk suggests it be limited to 16 alphanumeric characters.

3. Enter and confirm a password.

4. Click OK to accept and create a new CIFS user.

Changing CIFS User Password

The only editing that can be done to a CIFS user, once created, is to change the password. To do this, select a user from the list and click on Change Password... on the CIFS User Management window.


45

iGrid Administration Quota Management

Quota Management

Disk usage quotas may be implemented and managed using either the GUI or the Command Line Interface (CLI). For detailed instructions and more information about using the CLI, refer to Chapter 6, iGrid Command Line Interface (CLI) on page 150.

Quota Management provisions and guidelines are as follows:

• Quotas may be associated with one or more file system.

• Quotas are optional and by default will not be associated with any file systems.

• Quotas do not track the number of files, only the total space.

• Quotas can track both soft and hard limits on file system usage. An iGrid event is generated when a soft limit is violated. The pending I/O operation will fail with an error when a hard limit is violated.

• Quota statistics are calculated every 60 seconds.

To manage quotas via the user interface, do the following:

1. In the Storage menu, select Quotas to open the Quotas window.

Figure 3-1 Quotas


46

Quota Management iGrid Administration

2. Click New... to open the New Quota dialog box.

3. Select the Volume you wish to place a Quota on from the drop down menu.

4. Select the type of quota: User or Group.

5. Enter the Quota ID Number.

6. Choose the increment in which the limits will be entered: KB, MB, GM, TB.

7. Enter the Soft Limit and Hard Limit parameters. The soft limit signifies at what point the user will receive a warning, but the system continues to operate as normal. When the hard limit is reached, all IO activity ceases.

8. Click OK to create the new quota.

Once a quota is created, only the soft and hard limits are editable. Click the Edit button to change them.

To created a quota filter for viewing, do the following:

1. Click the Create Quota Filter button at the bottom of the Quota window.

2. Indicate which volumes or types you wish to filter.

3. Click Ok to create the new filter.

To list all quotas again, simply click on Clear Quota Filter.


47

iGrid Administration Lock Management

Lock Management

Lock management does not require user interface. This section has been provided for information purposes.

Lock management is a feature that is necessary for customer installations where multiple (two or more) client machines may attempt to simultaneously open a single file for writing. Many installations don’t require this kind of functionality. For those that do, iGrid has distributed, grid-wide lock management to provide the needed support.

The Distributed Lock Manager (DLM) module within iGrid provides grid-wide seamless lock management support for all file systems exported via NFS. This assures that multiple clients accessing these NFS file systems cannot obtain conflicting lock information. More specifically, NFS clients are assured that any locks obtained are guaranteed to be exclusive locks across the entire grid, regardless of which VIP they use to mount the shared NFS file systems, and regardless of which node in the iGrid is servicing that VIP.

iGrid also supports lock management for CIFS filesystems, but with a few rules.

For clients accessing the same CIFS filesystem that need locking support (i.e., each client could possibly open a file for writing at the same time), the following rules must be adhered to:

• All such clients must mount the CIFS file system through the same VIP.

• The VIPs used should be configured not to be subject to load balancing.

Adhering to these rules assures that lock management functionality will work properly for CIFS.

In addition, for environments where there are both NFS and CIFS writers to a single file, lock management does not currently support automatic coordination between both NFS and CIFS.

Load balancing policies may also be managed via the /lbpolicies command set in the Command Line Interface. Please refer to the Lbpolicies section found in Chapter 6, iGrid Command Line Interface (CLI), on page 132


48

Virtual IP Address Locks iGrid Administration

Virtual IP Address Locks

VIPs move from node to node due to load balancing (controlled) or failover (uncontrolled). Either way, the lock state for an NFS client is maintained during the movement of a virtual IP address.

When a ‘graceful’ (i.e., load balancing) move is made, the iGrid node which the VIP is moved to begins processing lock requests for all NFS clients communicating over that VIP.

When a failure occurs, all VIPs on the failed iGrid node are reassigned to a new node by the cluster manager. At this point the Distributed Lock Management module enters the Recovery state for all nodes within the cluster.

The Recovery state places all locks for the failed node in a “Failed Lock” state on every iGrid node in the cluster. Each of these locks is assigned a configurable ‘lease time’ (default is five minutes), during which the Lock Manager on each iGrid node monitors the NFS client lock requests. When a lock request is received from one of these NFS clients, the iGrid node takes ownership. Once the lease time expires, any unclaimed locks are released.


49

iGrid Administration Event Notification

Event Notification

Events are occurrences that happen in the system asynchronously from specific management activity. Examples of events are VIP migration due to load balancing, storage failover and node failover. As an event occurs, it is shown in the status bar at the bottom of the iGrid user interface screen.

Events are e-mailed to management users according to their preferences and privileges for event notification.

To view the event log in the user interface, do the following:

1. Select Events from the Tools menu.

iGrid will build the events log and display it.

Figure 3-2 Events Log


50

Filtered Events iGrid Administration

Filtered Events

If you wish to display only a specified set of events in the user interface, you can create filters by either clicking on the Filter Events button at the bottom of the Events window or choosing Filter Events... from the Events menu.

Figure 3-3 Event Filter

1. Check the alert severity boxes for the events you wish to display.

2. Enter the Description and Component information in the text boxes provided.

3. Enter the time sequence covered for the events you wish to display.

4. Select the time increment from the dropdown list.

5. Click Ok.

Events may also be listed and filtered via the /events command set in the Command Line Interface. Please refer to the Events section in Chapter 6, iGrid Command Line Interface (CLI), on page 123.


51

iGrid Administration Load Balancing

Load Balancing

This section describes how to create a load balancing policy for a node and set the policy’s minimum and maximum loads.

Load balancing exists on the grid so that run-time load demands cause workloads to shift to other nodes such that each node’s performance and throughput conform to its user-specified load balancing policy. Load balancing with compare the current CPU load against the ‘active’ policy (depending on time of day) and move the load (VIPs), as needed, between nodes.

However, peak activity may affect performance or create throughput bottlenecks over short time periods until the load is re-allocated.

Automatic load balancing occurs at regular intervals throughout the day. Every one hundred (100) seconds, load balancing averages the last five (5) minutes of CPU load values, which are read every ten (10) seconds. This will be used to determine if the load should be moved or not.

Current policies appear in a table on the Load Balancing page. With the iGrid Load Balancing feature, you can create an unlimited number of named load balancing policies for establishing low and high thresholds. You can establish load-balancing policies and associate them with individual iGrid nodes, and you can delete and create new policies for individual nodes. The Load Balancing page shows the policies created for each iGrid node.

Load balancing policies may also be managed via the /lbpolicies command set in the Command Line Interface.

Create a Load Balancing Policy

A load balancing policy affects all nodes in the grid. To create a policy in the iGrid GUI, do the following:

1. Under the Tools menu select Policies to view existing load balancing policies.

The Policies window opens, showing the LB policy name, its minimum, maximum, and the nodes which are assigned to it.


52

Create a Load Balancing Policy iGrid Administration

Figure 3-4 Load Balancing Policies

2. In the Policies window, click New....

The New Policy dialog box appears.

Figure 3-5 New Policy


53

iGrid Administration Assign a Load Balancing Policy to a Node

3. Type a name in the Policy Name field. Crosswalk recommends that the policy name be confined to 16 or less alphanumeric characters, with no blank spaces.

4. On the Minimum slider bar, move the arrow to the desired minimum load setting.

5. On the Maximum slider bar, move the arrow to the desired maximum load setting. This is the CPU load figure which must be passed before loads will be moved.

6. Click Ok.

The new policy is added to the Load Balancing Policies table.

Assign a Load Balancing Policy to a Node

To set a policy for a node from the Policies window, do the following:

1. Select the policy to which you wish to assign nodes.

1. Click Set Node Policy at the bottom of the window and a dialog box will appear listing all nodes.

Figure 3-6 Set Policy

2. From the list of nodes, choose the node to which this policy will apply. Multiple nodes may be chosen by holding down the Shift key when you select.

3. Click Ok.

4. The node is moved to that LB policy line in the table.

Figure 3-7


54

Delete a Load Balancing Policy iGrid Administration

Delete a Load Balancing Policy

To delete a policy, do the following:

1. In the Policies window, select the policy to delete.

2. Click Delete.

The deletion Yes or No? confirmation dialog box appears.

3. Click Yes.

The policy is deleted from the Policies table and the iGrid node.

Forcing a Load Balance

When you manually force load balancing, the grid attempts to immediately reallocate available resources across all available nodes, according to the user-specified load balancing policy for each node, rather than waiting for the system-generated load balancing process to occur.

Note: CIFS shares and management IPs do not participate in load balancing. Crosswalk strongly recommends that CIFS shares be assigned to non-load balanced VIPs or your session could be lost during load balancing.

To force load balancing, do the following:

1. Use the Cluster menu in the iGrid GUI and select Force Load Balancing.

2. All nodes will be balanced based on the minimum and maximum loads set up in the Load Balancing Policy.


55

iGrid Administration Backups

Backups

Crosswalk’s iGrid uses Bakbone’s NetVault to backup server volumes. See Appendix A, Using BakBone’s® NetVault™ with Crosswalk iGrid for detailed information on installing and configuring NetVault with the iGrid user interface.


56

– CHAPTER 4 –

iGrid Storage Functions

Volumes, pools, and Logical Unit Numbers (LUNs) are building blocks you can manipulate to create and export file systems. Crosswalk iGrid facilitates the way you use industry-wide best practices to optimize your storage resources and become more cost efficient. The Storage feature in iGrid gives you all the information you need to efficiently manage your system resources.

The iGrid Storage menu lets you manage LUNS, storage pools, volumes from existing pools and add more storage from the pools the volumes were created from. Exported file systems are also managed through this menu.

The iGrid Snapshot feature is also found under the Storage menu and allows you to take ‘pictures’ of your storage files system at pre-determined times.

Quotas may also be created from the Storage menu and are explained in Chapter 3, Administration, on page 46.


• Logical Unit Numbers (LUNs) on page 58

• Pools on page 60

• Volumes on page 68

• Mount a File System on page 74

• Managing Exported File Systems on page 76

• Snapshots on page 82


57

iGrid Storage Functions Logical Unit Numbers (LUNs)

Logical Unit Numbers (LUNs)

The Crosswalk Logical Unit Number (LUN) management feature allows you to view the volume LUN and which LUNs are currently available for you to use – that is, what storage is associated with your grid.

LUN Rules

• Each LUN has a unique Universal Unique IDentifier (UUID).

• Stripe width may be revised by removing all associated volumes and creating a volume with a different number of LUNs.

• There is a 256-LUN limit on the back-end of the Grid system.

• Specific circumstances may cause a failure to file systems, such as failure of the array or presenting a new LUN to the grid, causing the array to signal a failure for one or more LUNs already being used. To recover file systems:

1. Restore path to lost LUN.

2. Unmount the file system on every node where the paths were lost.

3. Remount the file system on every node where the paths were lost.

LUN Optimization

For optimitzed performance, iGrid assumes an even-odd configuration of available LUNs. By adding LUNs in the order listed, the pool is able to balance striping across the LUNs in the most efficient way. For example, for a one-array grid, LUNs are striped across array controllers to maximize the throughput of each controller.

If you choose not to optimize LUNs when adding or editing, they will be re-ordered to your specification.

For details on optimizing LUNs, see Chapter 6, iGrid Command Line Interface (CLI), storagepools Commands on page 157.

Available LUNs

Available LUNs may be viewed via the /availableluns command set in the Command Line Interface. Please refer to the AvailableLuns section in Chapter 6, iGrid Command Line Interface (CLI), on page 119.


58

Remove a LUN iGrid Storage Functions

They may also be viewed in the GUI under the Storage menu.

Remove a LUN

CAUTION—Removing a LUN requires a system reboot and disruption of service.

Removing a LUN is done outside of the user interface. To remove a LUN from the grid, follow these steps:

1. Verify the LUN is listed on the Available LUN window. From the Storage menu, choose Available LUNs

2. Use your storage management software to manually remove the LUN.

3. Reboot each node on the iGrid system, one at a time.


59

iGrid Storage Functions Pools

Pools

This section describes how to manage storage pools in the iGrid GUI. You can carve pools into volumes for export as CIFS or NFS file systems. You can see the pools that are currently available for you to use – that is, which LUNs are used to build the pools. You can create additional pools, and you can add any available LUNs that have not already been consumed to existing pools. This allows you to export file systems of a specific size that can later be extended as more storage becomes available.

Storage pools may be managed via the user interface, outlined in this chapter, or by the /storagepools command set in the Command Line Interface. Refer to the Storagepools section of Chapter 6, iGrid Command Line Interface (CLI), on page 157.

Pool Semantics

• Pools are constructed only from LUNs.

• Pools should have grid-unique names.

• Pools must have extents that range in powers of 2 from 23 to 224 inclusive – that is, from 8 to 16,777,216.

• All volumes referred to here will be represented by stripe sets. Initially, any number of LUNs may be added to a pool, until the pool is locked.

• When one or more volumes have been created from a given pool, the base number of LUNs is considered to be locked with a value of N where N = the number of LUNs in the pool at the time it was locked. This value will never change for the life of the pool unless all volumes in that pool have been deleted. When a pool is locked with value N, LUNs may only be added to the pool in multiples of N.

For example, if N = 5, you may add another 5, 10, or 15 LUNs and so on.

• By default, every volume created from this pool will be striped evenly across N LUNs, even if the pool contains 2N, 3N… LUNs.

• A pool may be deleted only if there are no volumes associated with it. Volumes may be deleted from a pool. A LUN may never be removed from a pool after it is locked (until the pool is deleted, that is).


60

Display Current Pools iGrid Storage Functions

Display Current Pools

To view the current iGrid storage pools, do the following:

1. In the iGrid user interface, select the Storage menu and click on Storage Pools.

The Storage Pools window will open, listing all existing pools. It may take a few seconds for the pool list to build.



61

iGrid Storage Functions Create a New Storage Pool

From the Storage Pools window you can add new pools, expand existing pools and delete storage pools. By selecting a pool from the list, you can also see which LUNs are assigned to each pool.

Create a New Storage Pool

1. Use the Storage menu and select Storage Pools.

2. The Storage Pools window opens to list all created pools, their assigned LUNs and your options for them.


62

Create a New Storage Pool iGrid Storage Functions



63

iGrid Storage Functions Create a New Storage Pool

3. Click New... at the bottom of the storage pool listing.

The Create New Pool dialog box appears.

Figure 4-3 Create New Pool

4. Type a name in the Storage Pool field. If you type a name that is already in use, an error message appears.

Note: Naming conventions suggest you to use only alphanumeric characters and these three special characters: _s, -s, and .s.

5. From the Extent (in KB) drop-down list select the extent size for the pool. 128 Kb is Crosswalk’s standard recommendation.


64

Create a New Storage Pool iGrid Storage Functions

6. Select the LUNs to assign to this pool. Hold the Shift key down to select multiple LUNs in the list. use the left and right arrow buttons to move LUNs from Available to Selected.

As long as the default stripe width is unchanged, a pool may be created with any available LUNs, rather than only LUNs of the same size.

CAUTION—A pool should always be created with a minimum of two LUNs, as a volume cannot be created from a pool with less than two LUNs assigned to it.

7. After selecting the LUNs, click Ok.

The new pool will appear in the list after a few moments.


65

iGrid Storage Functions Expand a Pool

Expand a Pool

To expand a pool, do the following:

1. In the Storage Pools window, select the pool you wish to expand and click the Expand button at the bottom of the screen or choose Expand from the Storage Pools drop down menu. The Expand dialog box will open.

2. Select from the Available LUNs to expand the pool. Hold the Shift key down to select multiple LUNs at once. Use the arrow buttons to move the available LUNs to the Selected LUNs side.

3. Click Ok to save the expanded pool.


66

Delete a Pool iGrid Storage Functions

A message will appear verifying the expansion.

Delete a Pool

To delete a pool:

4. Select a storage pool from those listed in the Storage Pool window.

5. Click the Delete button at the bottom of the window or from the Storage Pools drop down menu.

Note: Once a volume is created on a specific pool, that pool is “locked.” It becomes unlocked once all associated volumes are removed from it. Thus, if you try to delete a pool attached to a volume, you will receive a warning message. You must delete the volume used by the pool first.

The deletion Yes or No? confirmation dialog box appears.

6. Click Yes.


67

iGrid Storage Functions Volumes

Volumes

This section describes how to manage all aspects of volumes. The Storage Manager menu selection in the iGrid GUI is used to view and manage volumes. New volumes can also be created from existing pools, and you can add more volume storage via the pools the volumes were created from. You can prepare volumes to be exported as NFS or CIFS share file systems.

Volumes may also be managed via the /volumes command set in the Command Line Interface. Please refer to the Volumes section in Chapter 6, iGrid Command Line Interface (CLI), on page 165.

Display Current Volumes

To view the current iGrid volumes, do the following:

1. From the Storage menu, select Volumes.

2. The Volume window opens, listing all the current volumes in the grid system.


68

Create a Volume iGrid Storage Functions

Create a Volume

1. Use the Storage menu on the GUI and select Volumes.

2. A list of volumes on this grid and your options for them will appear in the Volumes window.


69

iGrid Storage Functions Create a Volume

3. Click New... at the bottom of the page. The Create Volume window appears.

Figure 4-4 Create New Volume

Note: The Create Volume window shows the reserved and available space for volume creation.

4. Type a name in the Volume field and select the newly created pool from the Storage Pool drop down menu.

Note: For volumes, the names “snapshot” and “nvbackup” are reserved for system use and may not be used.

5. Select the desired stripe width. Crosswalk suggests leaving the Stripe Width at the default value, which is the number of LUNs used in this volume.

6. Choose GB or TB units from the Total Size dropdown menu and enter the total size.

The total size must be a percent of the free space and be at least 2.1GB.


70

Expand a Volume iGrid Storage Functions

When you attempt to create a volume that exceeds the remaining pool availability, a message appears that tells you to try a smaller volume size.

Note: When adding a file system, the journals take up an additional 2GB of file space. Therefore, for example, a volume created at 6GB and labelled 6GB will actually have 4GB of free space.

7. Click OK. The new volume is created. Rebuilding the volume list with the new volume added may take a few minutes.

Expand a Volume

To expand a volume, do the following:

1. In the Volumes window, click on the Expand button or choose Expand from the Volumes drop down menu.

The Expand Volume properties box appears. This is also the method used to show volume usage.

Figure 4-5 Expand a Volume

2. In the Expand volume dialog box, type the additional size to which you want to increase the volume. You must leave at least 2GB of file space for journals.

3. Select GB or TB unit from the drop-down list.

4. Click OK.


71

iGrid Storage Functions Delete a Volume

Delete a Volume

You cannot delete a volume that has associated shares. Before deleting a volume, ascertain whether the volume has associated shares and delete them from the volume.

WARNING — Any data residing on this volume will be lost. Back up prior to deletion.

To delete a volume, do the following:

1. In the Volume window, select the volume you wish to delete.

Figure 4-6 Delete a Volume

2. Click on the Delete button at the bottom of the page or select Delete from the Volume menu.

• When you attempt to delete a volume with associated shares, the iGrid Storage Manager message notifies you that the volume has associated shares.


72

Delete a Volume iGrid Storage Functions

• When the Information message appears and indicates the volume has associated shares, remove the shares. After deleting all shares, you can delete the volume.

3. On the deletion Yes or No? confirmation dialog box, click Yes.

The Volume is deleted from the grid.


73

iGrid Storage Functions Mount a File System

Mount a File System

Before you attempt to create a shareable file system, confirm that the Exportable column in the table shows false to show that the volume is not already shared.

There are some guidelines that should be kept in mind when creating shareable file systems.

• iGrid supports the ability to mount the same file system as both CIFS and NFS clients, depending on Active Directory, Kerberos or Unix Services for Windows setup.

• Files created by CIFS users will only be writable on NFS by the same NFS user. Other NFS users will have read-only permissions.

• CIFS shares are mounted on Virtual IPs that are not subject to load-balancing. Data to identify and record which Virtual IPs are used for load-balancing is collected during system installation and configuration. They should be named using alphanumeric characters rather than the IP addresses used for non-load-balanced CIFS shares.

Create a File System

1. From the Storage menu in the main window, navigate to the Volume window and select the volume and click on Create File System at the bottom of the screen.

Figure 4-7 New File System


74

Create a File System iGrid Storage Functions

2. The Create New File System dialog box opens and you are required to confirm your choice. Leave the Mount box checked (default).

3. Once confirmed, a new file system will be created.

4. Once the file system is created, you will notice that the Status column in the Volume list has changed.


75

iGrid Storage Functions Managing Exported File Systems

Managing Exported File Systems

1. Using the Storage menu, choose Exports and a list of all exported file systems will appear.

Figure 4-8 Exports

2. Click New... from the option buttons at the bottom of the window. The New CIFS/NFS window opens.

From the Type field, choose which export is being created: CIFS or NFS.


76

Managing Exported File Systems iGrid Storage Functions

The following describes the procedure to create a new CIFS export.

1. If you select CIFS as the Type, the New CIFS dialog box will appear.

Figure 4-9 New CIFS




5. Create a list of users who can access the CIFS share by entering the user name exactly as it appears in the active directory or Kerberos server.


77


Enter the user name in the field provided and use the Add button to add them to list of approved users. You may also use the Remove button to take them off of the list.

Figure 4-10 CIFS Users

6. Use the drop down menus to select permissions for Everybody, Group and User. You may wish to select Read but not write if you want a Unix client to read the same data as a Windows server, but not be able to write to it, and vice versa.

Figure 4-11 Set CIFS Permissions

7. Click OK.





78

Managing Exported File Systems iGrid Storage Functions

The following describes the procedure to create a new NFS export.

1. If you select NFS as the Type, the New NFS dialog box will appear.

Figure 4-12 New NFS





79


Figure 4-13 NFS Permissions and Hosts

5. Choose the Squash Setting. The squash setting is a security function used to block certain users by assigning them an anonymous user ID (nfsnobody).

• None - Users and root are mapped to themselves and use their default privileges.

• Root - Root is squashed and mapped to the nfsnobody ID.

• All - Both users and root are mapped to the nfsnobody ID.

6. Add hosts by entering host names or IP addresses (preferable) using the Add button. Hosts may also be deleted from the list using the Remove button.

7. Use the drop down menu to select permissions for Everybody. You may wish to select Read but not write if you want a Unix client to read the same data as a Windows server, but not be able to write to it, and vice versa.

8. Click OK.





80

NFS Mounting Options iGrid Storage Functions

NFS Mounting Options

The following are the recommended methods to mount NFS file systems on the external client.

UDP:

mount -t nfs -o \ async,rw,bg,vers=3,proto=udp,hard,nointr,timeo=6,rsize=32768,wsize=32768, \

nolock,nocto,noatime 192.168.252.34:/export/vol1 /v/fs1

TCP:

mount -t nfs –o \ async,rw,bg,vers=3,proto=tcp,hard,nointr,timeo=60,rsize=32768,wsize=32768, \

nolock,nocto,noatime 192.168.252.34:/export/vol1 /v/fs1

CAUTION—Crosswalk recommends that VIPs mounted via TCP should not be subject to load balancing. UDP is recommended for NFS.

Map a CIFS Share to Two Windows Systems

To map a CIFS share to two Windows systems, do the following:

1. On Windows system #1, open an Explorer window.

2. On the Tools menu, select Map Network Drive.

3. Select the desired drive from the list.

4. Click on the Folder text box and type \\<DNS Name>\<share>.

5. Click Finish.

6. On Windows system #2, open an Explorer window and repeat steps b through e.

7. On system #1, save a file to the share.

8. On system #2, open the file you saved in the previous step.

9. Edit the file and save the changes to the share.

10. Close the file.

11. On system #1, open the file you saved in the previous step and verify the changes made to the file.

12. Close the file.

13. Delete the file from system #2.

• The CIFS share is mapped to multiple Windows systems.

• You can create, read, write, modify, and delete files on the share.


81

iGrid Storage Functions Snapshots

Snapshots

This section describes how to use the iGrid Snapshots feature to schedule periodic copies of your data, of which a user-specified maximum number of copies are kept. The snapshots are made in such a way that the first snapshot is a full copy, then only files that have been added/deleted/changed are copied in subsequent snapshots. Unchanged files maintain a hard link to the full snapshot.

Note: The oldest remaining snapshot will always be a full copy of what was on the source at the time the snapshot was taken. Everything from the oldest snapshot will be deltas of that. If you wish to maintain a particular snapshot for backup or restore purposes, Crosswalk suggests you copy those files and do not rely on the snapshot function.

The following formula provides an approximate idea of how much space will be required on the target drive. Estimated Space Req. = (Used) + [(Used) * (% data changed) * (# of snapshots kept - 1)]

Figure 4-14 Volume Space Used

Example: Using the volume usage above, 50% changed data, and keeping four copies of snapshots, the following equation would determine your estimated space requirements:12G + [12G * 50% * (4-1)] = 30G estimated space required for snapshots

If the percentage of changed data is 100%, then the size of a full snapshot multiplied by the number of copies maintained is the maximum space required.


82

Managing Snapshots iGrid Storage Functions

Managing Snapshots

In the Snapshots window, you can see what schedules are currently in effect and which snapshots already exist for each schedule. You can show individual snapshot properties, suspend and resume a snapshot and delete schedules and/or existing snapshots.

Figure 4-15 Snapshots

Snapshots may also be managed via the /snapshots command set in the Command Line Interface (CLI). Please refer to the Snapshots section of Chapter 6, iGrid Command Line Interface (CLI), on page 153.


83

iGrid Storage Functions Managing Snapshots

Crosswalk provides the following information and recommendations for best practices when creating and scheduling snapshots:

• Assure that there is sufficient space in the target volume to store the snapshot data. That means that there must be enough space to contain a full snapshot and as many change copies as your system will require based on user input. The more the data base changes, the more room will be required.

• Make certain to leave enough time between snapshots to allow each one to complete. Remember that the less snapshots taken, the more efficient your system will run.

• Assure that multiple different schedules do not schedule multiple snapshots to occur at the same time. This can overly load the system and cause snapshots to take an excessive amount of time to complete.

• Smaller exports make for faster snapshots, tying up less resources.

• Ensure that the first snapshot in any schedule is set to occur sufficiently far enough into the future so that it will not be missed. For example., do not create a schedule to begin its first snapshot five minutes after creation. It could possibly be missed, causing subsequent snapshots not to execute.

• Assure that no snapshot schedule is using the same source and destination volumes as any other active snapshot schedule at the same time.

• Once a snapshot schedule takes # copies of snapshots (# is defined when the snapshot schedule is created), iGrid’s snapshot function deletes the oldest snapshot each time a new one is taken. If a snapshot copy in rotation for deletion has been exported, the schedule will suspend when it gets to that copy. The export must be deleted in order for the schedule to resume normal activity.

• Whole snapshot schedules, as well as snapshot instances, may be exported.

• Snapshots may not be made more frequently than once per minute.

• Once created, snapshot schedules may not be edited. To change a schedule, you must delete all exports of that schedule, delete all upcoming snapshots for that schedule, delete the schedule itself and recreate it.

Note: If there are snapshots from this schedule you wish to preserve, move them to a non-snapshot area before deleting and recreating your new snapshot schedule.


84

Create a New Snapshot Schedule iGrid Storage Functions

Create a New Snapshot Schedule

You can create snapshots only for volumes with file systems established in iGrid. For more information on creating file systems, refer to Create a File System on page 74. To create a new snapshot schedule, do the following:

1. From the Storage menu in the iGrid GUI, choose Snapshot Schedules..

The Snapshots window opens.

2. Click on the New... button at the bottom of the page or choose New from the Snapshot menu.


85

iGrid Storage Functions Create a New Snapshot Schedule

The New Snapshot dialog box appears.

Figure 4-16 New Snapshot

3. In the Schedule Name text box, type a name for the new snapshot schedule. Crosswalk recommends that the snapshot name be confined to 16 or less alphanumeric characters, using no blank spaces.

4. From the Source Volume drop-down list, choose the volume to create the snapshot of.

5. From the Destination Volume drop-down list, choose the volume to send the snapshot to.

Note: The snapshot of the source volume should always be smaller than the destination volume. Creating a snapshot larger in size than the target volume will result in file system errors.

6. Choose the path of the volume you are creating the new snapshot of.

a. Click Browse.


86

Create a New Snapshot Schedule iGrid Storage Functions

The Select a Path dialog box appears.

b. Click on the node name under the volume name.

The Node ID appears in the Path field at the top of the dialog box.

c. Enter a new folder name. Crosswalk recommends that the folder name be confined to 16 or less alphanumeric characters.

7. Click Ok to accept the new path name.

8. Specify the schedule day, month, and year.

a. From the month drop-down list, select a starting date month or use the up and down arrows adjacent to the text box to select a month.


87

iGrid Storage Functions Create a New Snapshot Schedule

b. Type the year in the text box or use the up and down arrows adjacent to the text box to select a year.

c. Click on the day in the snapshot calendar to designate the start date for the new snapshot schedule.

Figure 4-17 Snapshot Schedule Setup

9. Designate the snapshot schedule times.

a. Choose a start time from the drop down Starting Time box. Times are listed in increments on the half hour, i.e., 12:00 AM, 12:30 AM, 1:00 AM...

CAUTION—The failure or shutdown of a node may cause the snapshot schedule to skew. Snapshots are normally scheduled to run at a specified interval, beginning at a specified time from node 1. If that node is removed, the schedule will continue to run from the next node, without knowledge of when the last snapshot ran. Subsequent snapshots will continue to run at the specified interval, but will again be skewed if node 1 is returned to the grid.

10. Specify the snapshot frequency.

a. Choose minutes, hours, days or weeks from the drop down menu.

b. Type a number representing the frequency in the Run Every box.

• Make certain to leave enough time between snapshots to allow each one to complete.

• Assure that the first snapshot in any schedule is set to occur sufficiently far enough into the future so that it will not be missed, possibly causing subsequent snapshots not to execute.

11. Enter the number of copies to keep in the Number of Copies box. Remember that this means the first full snapshot taken is included in the total number.


88

Suspend or Resume a Snapshot Schedule iGrid Storage Functions

12. Click Ok.

iGrid creates the snapshot schedule.

Suspend or Resume a Snapshot Schedule

If you wish to suspend or resume an entire schedule for some reason, the user interface gives you the ability to do that quickly and simply.

To suspend a snapshot schedule, do the following:

1. Choose a snapshot schedule from the list provided in the Snapshots window.

2. Click on the Suspend button at the bottom of the schedule list and you will be asked to confirm the suspension.

3. Click Yes to continue and you will notice the Status for that snapshot schedule will change from Active to Suspended.

To resume activity on a schedule that has been suspended, do the following:

1. Choose a snapshot schedule from the list provided in the Snapshots window.

2. Click on the Resume button at the bottom of the schedule list and you will be asked to confirm the resume.

3. Click Yes to continue and you will notice the Status for that snapshot schedule will change from Suspended to Active.


89

iGrid Storage Functions Export a Snapshot Schedule

Export a Snapshot Schedule

Crosswalk now offers an option to export an entire snapshot schedule’s worth of data. This differs from the previous option of exporting an individual snapshot because you are now able to save every snapshot created for a given schedule, making it possible to have an entire history of snapshots available.

To export a snapshot schedule, do the following:

1. Select the snapshot schedule you wish to export from the list displayed in the Snapshot Schedule window.

2. At the bottom of the snapshot schedule list, click Export... and the Export Snapshot Schedule: [name] dialog box will appear.

3. Enter a name for the directory you wish to export in the Schedule Name field.

4. Choose the type of export: CIFS or NFS.

5. Click Ok.


90

Export an Individual Snapshot iGrid Storage Functions

Export an Individual Snapshot

To export individual snapshots to the destination directory, do the following:

1. Select a snapshot schedule from in the Snapshots window and all of the snapshots taken for that schedule will be displayed at the bottom of the window in the Snapshot Instance list.

2. Click the Export... button at the bottom of the Snapshot Instance portion of the window. The Export Snapshot dialog box will open.

3. Enter a name for this exported instance.

4. Select whether this instance is an NFS or CIFS type snapshot.

5. Click Ok. The export will be created in the destination directory you set up when the snapshot schedule was created.


91

iGrid Storage Functions NetVault

NetVault

To launch the NetVault backup application, use the Storage menu and select NetVault.


92

– CHAPTER 5 –

iGrid User Interface Features and Functions

By being able to monitor, maintain and effect system traffic, Crosswalk iGrid gives you the ability to reduce expenses and increase efficiency in managing your storage resources.


• iGrid Statistics on page 95

• iGrid Node Maintenance on page 108

iGrid Statistics

This section describes how the Statistics menu can be used to monitor performance of the nodes and their ports in a grid. Crosswalk iGrid statistics provide information that allows users to make informed decisions about adding or upgrading equipment and troubleshooting performance issues.

Statistics are available for nodes, IP addresses, LUNs, storage pools and file systems.


95

iGrid User Interface Features and Functions iGrid Statistics

When any of these six statistics windows is opened, you will always have the option to adjust how your view them. Simply right-click within the chart plotting area of the statistics window to select your options.

In addition to viewing options, by using the View menu, you can customize the polling rate of all statistics.

Note: Crosswalk recommends a polling rate of no less than ten seconds so that statistic refresh will not adversely affect your system’s performance.

Legends are use liberally throughout iGrid’s Statistics functionality. The following is a guideline to interpret its usage.

File System Utilization:

• Low (less than 10%) - blue

• OK (20% use) - green

• Warning (70% use) - yellow

• Risky (80% use) - orange

• Fatal (90% use) - Red

Node Status:

• Active - green

• Inactive - grey


96

Viewing Node Statistics iGrid User Interface Features and Functions

In addition, each node, IP address, pool, volume or file system is assigned a colored shape to represent it in the reporting window.

Crosswalk recommends the following best practices for statistics usage:

• The suggested statistic polling rate is five seconds.

• Because iGrid uses a multi-window environment, each time you choose to view statistics, a new window opens. Crosswalk suggests you simply be aware of the load on your system as each of these statistics polls for new information while open.

When viewing statistics of any kind, data is captured as long as the Statistics window is open. The information shown on each chart is a point-in-time representation of activity on the system.

Viewing Node Statistics

1. From the Statistics menu on the user interface, select Node Statistics.

The Node Statistics window will open.

Figure 5-1 Node Status

2. Click on the icon next to the statistic you wish to view for a specific node. A usage chart will appear beneath the Nodes Statistics window.


97

iGrid User Interface Features and Functions Viewing Node Statistics

Figure 5-2 Node Statistics


98

Viewing IP Address Statistics iGrid User Interface Features and Functions

• Multiple statistical information may be used simultaneously. The charts will simply stack.

Viewing IP Address Statistics

This section describes how to view statistics for an IP address associated with a node. To view IP address statistics, do the following:

1. From the Statistics menu on the user interface, select IP Statistics.

The IP Statistics window will open

Figure 5-3 IP Status


99

iGrid User Interface Features and Functions Viewing IP Address Statistics

2. Click on the icon next to the statistic you wish to view for a specific node. A usage chart will appear beneath the IP Statistics window.


100

Viewing Drive (LUN) Statistics iGrid User Interface Features and Functions


Viewing Drive (LUN) Statistics

1. From the Statistics menu on the user interface, select LUN Statistics.

The LUN Statistics window will open.

Figure 5-4 LUN Status


101

iGrid User Interface Features and Functions Viewing Drive (LUN) Statistics

2. Click on the icon next to the statistic you wish to view for a specific node. A usage chart will appear beneath the Drive Statistics window.

Figure 5-5 LUN Statistics


102

Viewing Storage Pool Statistics iGrid User Interface Features and Functions


Viewing Storage Pool Statistics

1. From the Statistics menu on the user interface, select Storage Pool Statistics.

The Storage Pool Statistics window will open.

Figure 5-6 Storage Pool Status


103

iGrid User Interface Features and Functions Viewing Storage Pool Statistics

2. Click on the icon next to the statistic you wish to view for a specific node. A usage chart will appear beneath the Storage Pool Statistics window.

Figure 5-7 Storage Pool Statistics


104

Viewing File System Statistics iGrid User Interface Features and Functions


Viewing File System Statistics

1. From the Statistics menu on the user interface, select File System Statistics.

The File System Statistics window will open.

Figure 5-8 File System Status


105

iGrid User Interface Features and Functions Viewing File System Statistics

2. Click on the icon next to the statistic you wish to view for a specific node. A usage chart will appear beneath the File System Statistics window.

Figure 5-9 File System Statistics


106

Viewing File System Statistics iGrid User Interface Features and Functions



107

iGrid User Interface Features and Functions iGrid Node Maintenance

iGrid Node Maintenance

This section describes how to configure and maintain node settings for a grid.

Maintaining Minimum Node Function

The iGrid software has minimum node requirements that must be considered when setting up or changing node configuration in the grid. If these minimums are not met, iGrid services could be suspended or shut down.

The following table provides guidelines for the minimum number of nodes that must remain operative for iGrid to function properly.

Table 5-1 Node Guidelines

Total Nodes in iGrid Minimum Nodes to Maintain

Maximum Nodes That Can Go Down

1 1

2 1

3 1

3 2

4 2

4 3

5 3

2

3

4

5

6

7

8


108

Viewing All Nodes On the Grid iGrid User Interface Features and Functions

Viewing All Nodes On the Grid

The default view upon logging into the iGrid GUI is a list of all nodes that are part of the grid. By selecting a node from the list, you can use the buttons at the bottom of the window to edit, join grid, leave grid or restart the node.

These options are also available under the Cluster menu.


109

iGrid User Interface Features and Functions Connecting to Another Node

Connecting to Another Node

This section describes how to connect to and log in to another node after initially logging in to iGrid. It may be necessary to re-login to the GUI should a node go down and the management VIP fails over. Crosswalk suggests that you always be logged into a VIP.

To connect and log into another node, do the following:

1. With a node selected from the main iGrid page, use the Cluster menu in the user interface and select Connect... from the list of options. This will open a new iGrid login dialog box.

2. Log in to the same management VIP with User Name and Password.

• The VIP will automatically fail over to the next node in the grid.

• The GUI is now connected to the next available node.

Leave the Grid

Leaving the grid does not shut down the node. It simply removes the node from the grid configuration until it is rejoined, if necessary.

To make a node leave the grid, do the following:

1. Select a node to leave the grid from the main menu.

2. From the Cluster menu, choose Leave Grid.

If you only have two nodes, you will receive a warning message, as it not recommended that a node leave the grid when there are only two.

3. If you choose Yes, the node will be disconnected from the grid until you have reconnected it.


110

Rejoin a Node to a Grid iGrid User Interface Features and Functions

Rejoin a Node to a Grid

The following describes how to rejoin an existing node to a grid.

1. Select a node to rejoin from the main iGrid window.

2. From the Cluster menu, choose Join Grid.

Remove a Node from a Grid

After a node is removed from a grid, all exported file systems can be accessed from the nodes remaining in the grid.

If communications between nodes in a two-node grid is lost due to network or other failure, it is possible that either one or both nodes will be automatically shut down.

Selecting to leave the grid does not shut down the node. It stops iGrid services, but the operating system is still running. However, removing the node and/or shutting down the node will automatically cause the node to leave the grid.

1. Select a node from the main iGrid window.

2. Using the Cluster menu choose Remove Node or click on Remove from the buttons at the bottom of the window.

A confirmation message will appear which you must acknowledge to proceed.

3. Click Yes. The node shuts down.


111

iGrid User Interface Features and Functions Shut Down All Nodes

WARNING — If you shut down a node that is part of a two-node grid, you will get a warning message, as redundancy of data will be lost if you proceed. You cannot remove one node from a two-node grid.

4. Turn off the power to the node that was shut down on the front panel.

CAUTION—The failure or shutdown of a node may cause the snapshot schedule to skew.

Shut Down All Nodes

The primary purpose to shut all nodes down would be to power down the system and relocate equipment. To shut down all nodes, do the following:

1. From the Cluster menu, choose Shut Down All Nodes.

2. Confirm your choice by clicking Yes.

3. Power down all nodes.


112

– CHAPTER 6 –

iGrid Command Line Interface (CLI)

This chapter defines and describes the supported iGrid command line interface commands and their output.


• Command Groups on page 113

• Introduction to CLI on page 115

• CLI Help Commands on page 116

Command Groups

The commands provided by the iGrid CLI are divided into several command groups. The command groups are:

• about Commands on page 118 display information about iGrid.

• availableluns Commands on page 119 manage available LUNs.

• cluster Commands on page 121 manage cluster-wide commands.

• events Commands on page 123 view and filter iGrid events.

• exports Commands on page 125 manage NFS exports and CIFS shares.

• lbpolicies Commands on page 132 manage load balancing policies.

• nodes Commands on page 134 manage nodes within the cluster.

• ipswitches Commands on page 141 manage IP switches.

• quotas Commands on page 150 manage volume quotas.

• snapshots Commands on page 153 manage volume snapshots.

• storagepools Commands on page 157 manage the pools in volumes.

• users Commands on page 161 manage iGrid users.

• volumes Commands on page 165 manage storage volumes.


113

iGrid Command Line Interface (CLI) Command Groups

The CLI is an alternative to the GUI for accessing iGrid functionality. It is accessible to any registered iGrid management user via SSH.

Note: CLI does not failover upon node failure.

The CLI provides the following general capabilities:

• List all elements in the iGrid.

• Show individual devices.

• Provide functionality identical to that in the iGrid User Interface.


114

Introduction to CLI iGrid Command Line Interface (CLI)

Introduction to CLI

The iGrid CLI shell is accessed by any iGrid user via SSH.

The following illustrates a typical session with the iGrid CLI (including log on):

At the # prompt:ssh admin@[full data management VIP]

You will be prompted to enter your password.

Once connected to the CLI shell, you will be presented with the iGrid prompt and are ready to enter a command.

Example:iGrid> aboutabout> get 0

Product: iGridServer Version: 1.0.53Copyright: Crosswalk, Inc. 2004-2005Company: Crosswalk, Inc.Address: 11000 Westmoor Circle, Suite 300Westminster, CO 80021Support: 1-866-626-5786 or 1-303-635-7900Website: http://www.crosswalkinc.com

about> logout*** GOODBYE ***


115

iGrid Command Line Interface (CLI) CLI Help Commands

CLI Help Commands

While at the iGrid> prompt, typing a question mark (?) will provide a list of all commands available in the CLI environment.

To view the menu structure of each command set, type /[command] and click on the Return key. For example, /cluster <return> will provide a list of all options for the cluster command set.

Note: As long as all commands are under the same parent, you may use a string of commands. E.g., iGrid>about get 0 may be typed on one line instead of typing ‘about’, hitting Return, then typing ‘get 0’ and hitting Return again.


116

Command Set Help Menus iGrid Command Line Interface (CLI)

Command Set Help Menus

Throughout the rest of this document, iGrid CLI commands are explained, including examples and parameter details, if any. There are also universal commands that may be used from anywhere inside the CLI shell:

• exit

• where

• logout

• cli-settings

• history

• tree

• usage

• previous_module

• exec-replay

• set-timeout


117

iGrid Command Line Interface (CLI) about Commands

about Commands

The following commands may be used to obtain general information about iGrid. All iGrid-related commands are grouped under the /about command set. The following commands are supported:

• get - Display information about iGrid.

about/get

This command displays general information about iGrid.

Usage: about> get <detailLevel>

Parameters:

• detailLevel – The level of detail for iGrid information to display.

0 = basic

1 = details.

Example: about> get 0

Product: iGridServer Version: 1.0.53Copyright: Crosswalk, Inc. 2004-2005Company: Crosswalk, Inc.Address: 11000 Westmoor Circle, Suite 300Westminster, CO 80021Support: 1-866-626-5786 or 1-303-635-7900Website: http://www.crosswalkinc.com

about>


118

availableluns Commands iGrid Command Line Interface (CLI)

availableluns Commands

The following commands may be used to manage available LUNs. The availableluns commands are grouped under the /availableluns command set. The following commands are supported:

• list - List all available LUNs.

• get - Show the properties of an available LUN.

• rescan - Scan system for new available LUNs.

availableluns/list

This command lists all available LUNs.

Usage: availableluns> list

Example:availableluns> listLUN Name: 200600a0b81848c0:2 UUID: 600a0b8000183c90000002174405910a Array WWN: 200600a0b81848c0 LUN #: 2 Desc: LSI:INF-01-00 Size: 0005.0 GBLUN Name: 200600a0b81848c0:3 UUID: 600a0b8000183c900000021844059144 Array WWN: 200600a0b81848c0 LUN #: 3 Desc: LSI:INF-01-00 Size: 0005.0 GBLUN Name: 200600a0b81848c0:4 UUID: 600a0b8000183c900000021944059172 Array WWN: 200600a0b81848c0 LUN #: 4 Desc: LSI:INF-01-00 Size: 0005.0 GBavailableluns>

availableuns/get

This command shows the properties of an available LUN.

Usage: availableluns> get <lunName>

Parameters:

• lunName – The name of the available LUN whose properties will be displayed.


119

iGrid Command Line Interface (CLI) availableluns Commands

Example:availableluns> get hrLUNLUN Name: 200600a0b81848c0:4 Total Size: 0005.0 GB Description: LSI:INF-01-00 Device ID: /dev/md4availableluns>

availableluns/rescan

This command scans the system for new available LUNs.

Usage: availableluns> rescan

Example:availableluns> rescan

LUN rescan starting....LUN rescan complete.

availableluns>


120

cluster Commands iGrid Command Line Interface (CLI)

cluster Commands

The following commands may be used to manage the entire cluster. All cluster related commands are grouped under the /cluster command set. The following commands are supported:

• nodeJoinGrid - Rejoin a node with the grid.

• nodeLeaveGrid - Temporarily remove a node from the grid (e.g., for maintenance).

• forceLoadBalancing – Redistribute load across grid nodes now.

cluster/nodeJoinGrid

This command rejoins a node to the cluster (after it has been temporarily removed using nodeLeaveGrid).

Usage: cluster> nodeJoinGrid <nodeName>

Parameters:

• nodeName – The name of the node to rejoin in the cluster.

Example:cluster> nodeJoinGrid igrid_node2

Node ‘igrid_node2’ joined to grid.cluster>

cluster/nodeLeaveGrid

This command has the node leave the grid temporarily (e.g., for maintenance).

Usage: cluster> nodeLeaveGrid <nodeName>

Parameters:

• nodeName – The name of the node to leave the cluster.

Example:cluster> nodeLeaveGrid igrid_node2

Node ‘igrid_node2’ removed from grid.cluster>

cluster/forceLoadBalancing

This command does immediate load balancing across node clusters.

Usage: cluster> forceLoadBalancing


121

iGrid Command Line Interface (CLI) cluster Commands

Example:cluster> forceLoadBalancing

Apply loadbalancing across all grid nodes now? (y/n) y Applying loadbalancing... Load balancing applied.

cluster>


122

events Commands iGrid Command Line Interface (CLI)

events Commands

The following commands may be used to view iGrid events. All event-related commands are grouped under the /events command set.

The following commands are supported:

• list - List all iGrid events

• filter - List filtered iGrid events

events/list

This command shows the following properties for all iGrid events:

• Time

• Severity

• Component

• Description

Usage: events> list

Example:events> list Time: Thu Apr 27 09:50:32 2006 Severity: INFO Component: cgnmd Description: iGrid service <loadbal> exits/terminates <407>Time: Thu Apr 27 09:50:27 2006 Severity: INFO Component: cgnmd Description: iGrid service <loadbal> restartingevents>

events/filter

This command shows iGrid events filtered by time, severity, component, or description.

Usage: vents> filter <filterType> <filterValue>

Parameters:

• filterType – The event property to filter on: time, severity, component, or description.

• filterValue – The value to filter.

Example:


123

iGrid Command Line Interface (CLI) events Commands

events> filter severity WARNING Time: Thu Apr 27 09:50:47 2006 Severity: WARNING Component: cgnmd Description: iGrid service <loadbal> exits/terminates <897> Time: Thu Apr 27 09:50:42 2006 Severity: WARNING Component: cgnmd Description: iGrid service <loadbal> restartingevents>


124

exports Commands iGrid Command Line Interface (CLI)

exports Commands

The following commands may be used to manage NFS exports, CIFS shares, and iSCSI targets. All export-related commands are grouped under the /exports command set. The following commands are supported:

• browsetool - Browse or modify the directories on a volume for export.

• create - Create NFS, CIFS, or iSCSI exports.

• set - Change properties of an existing export (NFS, CIFS, or iSCSI).

• list - List all exports on the grid.

• get - Show the properties of an export.

• remove - Delete an export.

exports/browsetool

The following commands may be used to browse or modify a volume’s exported directories. The browsetool commands are grouped under the /exports/browsetool command set.

The following commands are supported:

• createDir - Create a new directory on a volume.

• deleteDir - Delete a directory from a volume.

• listDir - List the contents of a directory on a volume.

exports/browsetool/createDir

This command creates a new directory on a volume.

Usage: browsetool> createDir <volumeName> <dirPath>

Parameters:

volumeName – The name of the volume on which to create the new directory.

dirPath - Full path to the directory to be created.

Example:browsetool> createDir hrvol /mnt/hr_files

Directory ‘/mnt/hr_files’ created.browsetool>

exports/browsetool/deleteDir

This command deletes a directory from a volume.

Usage: browsetool> deleteDir <volumeName> <dirPath>


125

iGrid Command Line Interface (CLI) exports Commands

Parameters:

• volumeName – The name of the volume which contains the directory to be deleted.

• dirPath - Full path to the directory to be deleted.

Example:browsetool> deleteDir hrvol /mnt/hr_files

Directory ‘/mnt/hr_files deleted.browsetool>

exports/browsetool/listDir

This command lists the contents of a directory on a volume.

Usage: browsetool> listDir <volumeName> <dirPath>

Parameters:

• volumeName – The name of the volume the directory is on.

• dirPath - Full path to the directory whose contents should be listed.

Example:browsetool> listDir hrvol /mnt/hr_files

Folders: /foo /hrfolderFiles:

About.txtContacts.doc

browsetool>

exports/create

The following commands may be used to create NFS exports and CIFS shares. The create commands are grouped under the /exports/create command set. The following commands are supported:

• cifs - Create a CIFS share.

• nfs - Create an NFS export.


126


exports/create/cifs

This command creates a new CIFS share.

Usage: create> cifs <shareName> <volumeName> <path> <writeFlag> <accessList>

Parameters:

• shareName – The name of the CIFS share.

• volumeName – The name of the volume on which to create the new directory.

• path - Path to the directory you wish to export, bracketed with single-quote marks (since spaces are allowed in CIFS paths, e.g., '/Program Files/Windows NT'.) If the exact path is not known, use the 'exports/browsetool' command to browse the directory structure on the volume.

• everybodyPermissions - Create permissions for everybody. 0=Node, 1=Read, 2=Read/Write

• groupPermissions - Create permissions for groups. 0=Node, 1=Read, 2=Read/Write

• userPermissions - Create permissions for the user. 0=Node, 1=Read, 2=Read/Write

• accessList - A list of users (comma-separated, no spaces).

Example:create> cifs hr_data hrvol /mnt/hr_files 0 asanchez,psmith

Share ‘/mnt/hr_files’ created.create>

exports/create/nfs

This command creates a new NFS export.

Usage: create> nfs <exportName> <volumeName> <path> <writeFlag> <accessList> <squashSetting>

Parameters:

• exportName – The name of the new export.

• volumeName – The name of the volume on which the export should be created.

• path – The UNIX path to the directory you wish to export (e.g., /usr/local/bin). If the exact path is not known, use the 'exports/get’ command to browse the directory structure on the volume.

• writeFlag – Write permissions for the export, 0 = ReadOnly, 1 = Read/Write.

• accessList - A list of IP addresses which can access this export (comma-separated list, no spaces, ranges and wildcarding allowed).

• squashSetting - Valid for NFS exports only, 0 = None, 1 = Root, 2 = All.


127


Example:create> nfs nfs_hr_folder hrvol /nfs/hr_folder 0

10.250.0.103-109,10.250.1.* 2Export ‘nfs_hr_folder’ created.

create>

exports/set

The following commands may be used to change the properties of an existing NFS export or CIFS share. The set commands are grouped under the /exports/set command set. The following commands are supported:

• cifsAddUsers - Add users to the access list of an existing CIFS share.

• cifsRemoveUsers - Remove users from the access list of an existing CIFS share.

• nfsAddHosts - Add hosts to access list of an existing NFS export.

• nfsRemoveHosts - Remove hosts from access list of an existing NFS export.

• nfsSquashing - Set the squash setting for an existing NFS export.

• nfsInsecure - Set the NFS insecure option to allow mount browsing from Mac clients.

exports/set/cifsAddUsers

This command adds users to the access list of an existing CIFS share.

Usage: set> cifsAddUsers <shareName> <userList>

Parameters:


• userList – List of users to add to access list (comma-separated, no spaces).

Example:set> cifsAddUsers hr_share msannes;jscoops

Access list modified for share ‘hr_share’.set>

exports/set/cifsRemoveUsers

This command removes users from the access list of an existing CIFS share.

Usage: set> cifsRemoveUsers <shareName> <userList>

Parameters:


• userList – List of users to remove from the access list (comma-separated, no spaces).


128


Example:set> cifsRemoveUsers hr_share msannes;jscoops

Access list modified for share ‘hr_share’.set>

exports/set/nfsAddHosts

This command adds hosts to the access list of an existing NFS export.

Usage: set> nfsAddHosts <exportName> <hostList>

Parameters:

• exportName – The name of the NFS export.

• hostList – New IP addresses or hostnames to add to the access list (comma-separated list, no spaces, wildcarding allowed on IP addresses).

Example:set> nfsAddHosts hr_export 10.250.0.109,10.250.0.104

Access list modified for share ‘hr_export’.set>

exports/set/nfsRemoveHosts

This command removes hosts from the access list of an existing NFS export.

Usage: set> nfsRemoveHosts <exportName> <hostList>

Parameters:


• hostList – IP addresses or hostnames to remove from the access list (comma-separated list, no spaces, wildcarding allowed on IP addresses).

Example:set> nfsRemoveHosts hr_export 10.250.0.109,10.250.0.104

Access list modified for share ‘hr_export’.set>

exports/set/nfsSquashing

This command sets the squash setting for an existing NFS export.

Usage: set> nfsSquashing <exportName> <squashSetting>

Parameters:


• squashSetting – The squash setting for this NFS export. (0 = None, 1 = Root, 2 = All).


129


Example:set> nfsSquashing hr_export 1

Squashing set for share ‘hr_export’.set>

exports/set/nfsInsecure

This command sets the NFS insecure option to allow mount browsing from Mac clients.

Usage: set> nfsInsecure <exportName> <insecure>

Parameters:

• exportName - The name of the NFS export.

• insecure - The insecure setting for this NFS export. (0=Secure, 1=Insecure)

Example:set> nfsInsecure hr_export 1

Insecure/secure set for share ‘hr_export’set>

exports/list

This command lists all exports on the grid.

Usage: exports> list

Example:exports> list

Export Names: nfsExportexports>

exports/get

This command shows the properties of an export.

Usage: exports> get <exportName>

Parameters:



130


Example:exports> get nfsExport

Export Name: nfsExport Volume: zvol Path: /etc/opt Type: NFS Access Rights: N/A Squash Setting: Root

Access List: 10.250.0.*exports>

exports/remove

This command deletes an export.

Usage: exports> remove <exportName>

Parameters:

• exportName – The name of the NFS export to delete.

Example:exports> remove nfsExport

Delete export 'nfsExport' now? (y/n) yExport ‘nfsExport’ deleted.

exports>


131

iGrid Command Line Interface (CLI) lbpolicies Commands

lbpolicies Commands

The following commands may be used to manage load balancing policies. All load balancing related commands are grouped under the /lbpolicies command set. The following commands are supported:

• list - List all defined load balancing policies.

• get - Show the properties of a load balancing policy.

• set - Apply a load balancing policy to a node.

• create - Create a load balancing policy.

• remove - Delete a load balancing policy.

lbpolicies/list

This command lists all defined load balancing policies in the grid.

Usage: lbpolicies> list

Example:lbpolicies> list

20to80lbpolicies>

lbpolicies/get

This command shows the properties of a load balancing policy.

Usage: lbpolicies> get <lbPolicyName>

Parameters:

• lbPolicyName – The name of load balancing policy whose properties will be displayed.

Example:lbpolicies> get 20to80

Policy Name: 20to80 low: 20 high: 80

Nodes with this policy applied: wolf01lbpolicies>


132

lbpolicies Commands iGrid Command Line Interface (CLI)

lbpolicies/set

This command applies a load balancing policy to a node.

Usage: lbpolicies> set <nodeName> <lbPolicy>

Parameters:

• nodeName – The name of node to apply the policy to.

• lbPolicy – The load balancing policy to apply to the node.

Example:lbpolicies> set wolf01 20to80

Load balancing policy applied.lbpolicies>

lbpolicies/create

This command creates a load balancing policy.

Usage: lbpolicies> create <lbPolicy> <minLoad> <maxLoad>

Parameters:

• lbPolicy – The name of the new load balancing policy.

• minLoad – The percent load level below which a node will 'pull' processes from other nodes.

• maxLoad – The percent load level above which a node will 'push' processes to other nodes.

Example:lbpolicies> create 10to90 10 90

New load policy '10to90' created.lbpolicies>

lbpolicies/remove

This command deletes a load balancing policy.

Usage: lbpolicies> remove <lbPolicy>

Parameters:

• lbPolicy – The name of the load balancing policy to be deleted.

Example:lbpolicies> remove 10to90

Load policy '10to90' removed.lbpolicies>


133

iGrid Command Line Interface (CLI) nodes Commands

nodes Commands

The following commands may be used to manage nodes within the cluster. All node related commands are grouped under the /nodes command set. The following commands are supported:

• list - List all nodes in the cluster.

• get - Show the properties of a node.

• set - Apply a load balancing policy to a node.

• reboot - Reboot a node.

• rebootAll - Reboot all nodes in cluster.

• shutdown - Shutdown a node.

• shutdownAll - Shutdown all nodes in cluster now.

• stats - Show performance statistics for the grid.

nodes/list

This command lists all nodes in the cluster.

Usage: nodes> list

Example:nodes> list

wolf01wolf02

nodes>

nodes/get

This command shows the properties of a node.

Usage: nodes> get <nodeName>

Parameters:

• nodeName – The name of node whose properties will be displayed.


134

nodes Commands iGrid Command Line Interface (CLI)

Example:nodes> get wolf01

Gathering data on node 'wolf01'...

NODE NAME: wolf01 Status: Active Load Policy: 20to80 Provider Version: 1.2.3.1 *(1/19/06 11:52 AM) Management IP: 10.250.0.124 Service IPs: 10.250.0.125

nodes>

nodes/set

This comment applies a load balancing policy to a node.

Usage: nodes> set <nodeName> <lbPolicy>

Parameters:

• nodeName – The name of node to apply the policy to.

• lbPolicy – The load balancing policy to apply to the node.

Example:nodes> set wolf01 20to80

Load balancing policy applied.nodes>

nodes/reboot

This command reboots the specified node.

Usage: nodes> reboot <nodeName>

Parameters:

• nodeName – The name of node to reboot.


135


Example:nodes> reboot wolf01

Reboot node 'wolf01' now? (y/n) yChecking quorum constraints...Reboot command issued to node 'wolf01'.

nodes>

nodes/shutdown

This command shuts down the specified node.

Usage: nodes> shutdown <nodeName>

Parameters:

• nodeName – The name of node to shutdown.

Example:nodes> shutdown wolf01

Shutdown node 'wolf01' now? (y/n) yChecking quorum constraints...Shutdown command issued to node 'wolf01'.

nodes>

nodes/shutdownAll

This command shuts down all nodes in the cluster.

Usage: nodes> shutdownAll

Example:nodes> shutdownAll

Shutdown all nodes in the cluster? (y/n) yShutdown command issued to all cluster nodes.

nodes>


136


nodes/stats

The following commands may be used to display real-time statistics for nodes, IP addresses, FC ports, file systems, and physical volumes. The stats commands are grouped under the /nodes/stats command set. The following commands are supported:

• node - List statistics for the specified node.

• pv - List statistics for all physical volumes on the specified node.

• fs - List statistics for all file systems in the grid.

• ip - List statistics for all IP addresses in the grid.

• fcport - List statistics for all FC ports on the specified node.

nodes/stats/node

This command shows performance statistics for a node, including machine uptime, iGrid Provider uptime, load averages, CPU utilization, total and free memory, and the iGrid load balancing value.

Usage: stats> node <nodeName>

Parameters:

• nodeName – The name of the node whose statistics will be displayed or ‘all’ for statistics from all nodes.


137


Example:stats> node wolf01

Node: wolf01

System Uptime: 7786.220000iGrid Provider Uptime: 2537.564000

Load Avg 1: 0.230000Load Avg 5: 0.260000Load Avg 15: 0.220000

CPU 1:Non-Idle Time: 704.13Percent Utilization: 3.04

CPU 2:Non-Idle Time: 747.10Percent Utilization: 3.23

LB Value: 1LB Lower Threshold: 1LB Upper Threshold: 50

Total Memory: 1049686016Free Memory: 594268160

stats>

nodes/stats/pv

This command shows performance statistics for all physical volumes (resource LUNs) on a node, including the number of read and write IOs per second and KBs read and written per second.

Usage: stats> pv <nodeName>

Parameters:



138


Example:stats> pv wolf01

Node Name: wolf01Physical Volume: 600a0b8000183c90000002164405888aDevice UUID: 600a0b8000183c90000002164405888a

Device Name: /dev/md1 Reads/s: 0.000000 Writes/s: 0.000000 KB Read/s: 0.000000 KB Written/s: 0.000000stats>

nodes/stats/fs

This command shows performance statistics for all file systems in the grid, including the total and free capacities of the file systems.

Usage: stats> fs <fileSystem>

Parameters:

• fileSystem – The name of the file system whose statistics will be displayed or ‘all’ for statistics for all file systems.

Example:stats> fs /mnt/hr_data

File System: /mnt/hr_data

Capacity: 345763847Free Space: 432907

stats>

nodes/stats/fcport

Note: This command has not been implemented in iGrid v2.0.

This command shows performance statistics for all FC ports on a node, including bytes transmitted and received, packets transmitted and received, CRC errors and link failures.

Usage: stats> fcport <nodeName>

Parameters:



139


Example:stats> fcport all

This CLI command not yet implemented.stats>

nodes/stats/ip

This command shows performance statistics for all IP addresses, including bytes transmitted and received.

Usage: stats> ip <ipAddress>

Parameters:

• ipAddress – The IP address whose statistics will be displayed or ‘all’ for statistics from all IP addresses.

Example:stats> ip 10.250.0.189

IP Address: 10.250.0.189Bytes Received: 1978297Bytes Transmitted: 1679138

stats>

nodes/stats/setInterval

This command sets the collection interval for iGrid statistics. The default interval is five seconds for all statistics.

Usage: stats> setInterval <statistics> <interval>

Parameters:

• statistics – The statistics whose collection interval will be set.

• interval – The new collection interval (in seconds) of the statistics.

Example:stats> setInterval node 10

This CLI command not yet implemented.stats>


140

ipswitches Commands iGrid Command Line Interface (CLI)

ipswitches Commands

The following commands may be used to manage IP switches and their connections to VIPs (virtual IP addresses) and node network interfaces. All IP switch related commands are grouped under the /ipswitches command set. The following commands are supported:

• listSwitches - List IP switches configured in the Grid.

• getSwitch - Show the properties of an IP switch and its connections.

• listInterfaces - List network interfaces configured in the Grid.

• listVips - List virtual IP addresses configured in the Grid.

• getVip - Show the properties of a virtual IP address, including its client connections.

• showConfig - Show the current front-end IP switch, virtual IP address, and network interface configuration.

• editConfig - Edit the front-end IP switch, virtual IP address, and network interface configuration.

ipswitches/listSwitches

This command lists all IP switches configured in the Grid.

Usage: ipswitches> listSwitches

Example:ipswitches> listSwitches igrid_frontend_1 igrid_frontend_2ipswitches>

ipswitches/getSwitch

This command shows the properties of an IP switch, including its configured VIPs and network interfaces.

Usage: ipswitches> getSwitch <switchId>

Parameters:

• switchId – The ID of the IP switch.


141

iGrid Command Line Interface (CLI) ipswitches Commands

Example:ipswitches> getSwitch igrid_frontend_1

Switch ID: igrid_frontend_1Assigned VIPs:IP Address: 10.250.1.138

Interface: serval01.eth0Connected Interfaces:Interface: serval01.eth0

MAC Address: 00:00:1a:1a:03:68 NIC: Intel Corporation 82546EB Gigabit Ethernet Controller NIC Port: 1

Interface: serval01.eth1 MAC Address: 00:00:1a:1a:03:67 NIC: Intel Corporation 82546EB Gigabit Ethernet Controller NIC Port: 2ipswitches>

ipswitches/listInterfaces

This command lists all network interfaces configured in the Grid.

Usage: ipswitches> listInterfaces

Example:ipswitches> listInterfacesInterface: serval01.eth5 MAC Address: 00:04:23:b2:91:43Interface: serval01.eth3 MAC Address: 00:04:23:b2:91:41Interface: serval02.eth6 MAC Address: 00:04:23:b2:91:43Interface: serval02.eth0 MAC Address: 00:00:1a:1a:03:68ipswitches>


142


ipswitches/listVips

This command lists all virtual IP addresses configured in the Grid.

Usage: ipswitches> listVips

Example:ipswitches> listVipsVirtual IP Address: 10.250.1.138 Interface: serval01.eth0 Speed: 131072000Virtual IP Address: 10.250.1.139 Interface: serval01.eth2 Speed: 131072000ipswitches>


143


ipswitches/getVip

This command shows the properties of a virtual IP address, including its client connections.

Usage: ipswitches> getVip <vip>

Parameters:

• vip - The virtual IP address whose properties will be displayed.

Examplesipswitches> getVip 10.250.1.138

Virtual IP Address: 10.250.1.138Netmask: 255.255.0.0Interface: serval01.eth0Speed: 131072000IP Switch: ig_frontend_sw1

Clients:NFS:TCP:192.168.2.34192.168.2.36UDP:192.168.4.123192.168.2.12192.168.6.195SAMBA:TCP:192.168.2.34192.168.2.36TCP:10.254.0.18910.254.0.190 UDP:<none>

ipswitches>


144


ipswitches/showConfig

This command shows the current front-end IP switch, virtual IP address, and network interface configuration.

Usage: ipswitches> showConfig

Example:ipswitches> showConfigSwitch ID: igrid_frontend_1VIPs:

10.250.1.13510.250.1.136

Interfaces:serval01.eth0serval01.eth1serval02.eth0serval02.eth1

Switch ID: igrid_frontend_2VIPs:

10.250.1.11510.250.1.116

Interfaces:serval01.eth5serval01.eth6serval02.eth5serval02.eth6

ipswitches>

ipswitches/editConfig

The following commands may be used to edit the front-end IP switch, virtual IP address, and network interface configuration. The commands are grouped under the /ipswitches/editConfig command set. The following commands are supported:

• createSwitch - Create a new IP switch.

• removeSwitch - Remove an IP Switch.

• assignInterface - Assign a network interface to an IP switch.

• removeInterface - Remove a network interface from an IP switch.

• assignVip - Assign a virtual IP address to an IP switch.


145


• removeVip - Remove a virtual IP address from an IP switch showModifiedConfig - Show the modified front-end IP switch, virtual IP address, and network interface configuration.

• clear - Clear any configuration changes.

• commit - Commit the configuration changes.

ipswitches/editConfig/createSwitch

This command is used to create a new IP switch.

Usage: editConfig> createSwitch <switchId>

Parameters:

• switchId – The unique ID of the new IP switch.

Example:editConfig> createSwitch igrid_frontend_3

IP switch ‘igrid_frontend_3’ created.editConfig>

ipswitches/editConfig/removeSwitch

This command deletes an IP switch.

Usage: editConfig> removeSwitch <switchId>

Parameters:


Example:editConfig> removeSwitch igrid_frontend_3 IP switch ‘igrid_frontend_3’ removed.editConfig>

ipswitches/editConfig/assignInterface

This command assigns a network interface to an IP switch.

Usage: editConfig> assignInterface <switchId> <interface>

Parameters:

• switchId – The ID of the IP switch

• interface - The network interface to assign to the IP switch. The format is node.intfc, where node is the node name and intfc is the interface name, e.g., ig_node1.eth0.


146


Example:editConfig> assignInterface igrid_frontend_3 ig_node1.eth0

Network interface ‘ig_node1.eth0’ assigned to IP switch‘igrid_frontend_3’.

editConfig>

ipswitches/editconfig/removeInterface

This command deletes a network interface from an IP switch.

Usage: editConfig> removeInterface <switchId>

Parameters:


Example:editConfig> removeInterface igrid_frontend_3 IP switch ‘igrid_frontend_3’ removed.editConfig>

ipswitches/editConfig/assignVip

This command assigns a VIP to an IP switch.

Usage: editConfig> assignVip <switchId>

Parameters:


Example:editConfig> assignVip igrid_frontend_3 IP switch ‘igrid_frontend_3’ removed.editConfig>

ipswitches/editConfig/removeVip

This command deletes an assigned VIP from an IP switch.

Usage: editConfig> removeVip <switchId>

Parameters:


Example:editConfig> removeVip igrid_frontend_3 IP switch ‘igrid_frontend_3’ removed.editConfig>


147


ipswitches/editConfig/showModifiedConfig

This command shows the configuration changes made since the last commit/clear.

Usage: editConfig> showModifiedConfig

Example:editConfig> showModifiedConfig Switch ID: igrid_frontend_1 VIPs: 10.250.1.136 10.250.1.137 Interfaces: serval01.eth0 serval01.eth1 serval02.eth0 serval02.eth1 Switch ID: igrid_frontend_2 VIPs: 10.250.1.118 10.250.1.119 Interfaces:

serval01.eth5serval01.eth6serval02.eth5serval02.eth6

editConfig>

ipswitches/editConfig/clear

This command clears any configuration changes and resets to the current configuration.

Usage: editConfig> clear

Example:editConfig> clearFront-end IP configuration changes cleared and reset to the current config-

uration.editConfig>


148


ipswitches/editConfig/commit

This command commits the front-end IP configuration changes to the Grid.

Usage: editConfig> commit

Example:editConfig> commit Front-end IP configuration committed.editConfig>


149

iGrid Command Line Interface (CLI) quotas Commands

quotas Commands

The following commands may be used to manage volume quotas for users and groups. All quota-related commands are grouped under the /quotas command set. The following commands are supported:

• list - List quotas

• get - Show the properties of a quota

• create - Create a quota on a volume

• remove - Remove a quota

A detailed description of each command is provided below.

quotas/list

This command lists all quotas or those for a specific volume.

Usage: quotas> list <volumeName>

Parameters:

* volumeName – The name of the volume or ‘all’ for all quotas.

Example:quotas> list hr_vol Volume: hr_vol Type: User UID: 123

Volume: hr_vol Type: Group GID: 987

quotas>

quotas/get

This command shows the properties of a quota.

Usage: quotas> get <type> <id> <volumeName>

Parameters:

type – The quota type: user or group.

id – Either the UID or GID for the quota.

volumeName – The name of the volume.


150

quotas Commands iGrid Command Line Interface (CLI)

Example:quotas> get user 123 hr_vol Volume: hr_vol Type: User UID: 123 Soft Limit: 8 Hard Limit: 20 Usage: 0

quotas>

quotas/create

This command creates or modifies a new user or group quota.

Usage: quotas> create <type> <id> <volumeName> <softLimit> <hardLimit>

Parameters:

• type – The quota type: user or group.

• id – Either the UID or GID for the quota.

• volumeName – The name of the volume.

• softLimit – The soft-limit in KB or 0 for no soft limit.

• hardLimit – The soft-limit in KB or 0 for no hard limit.

Example:quotas> create user 123 hr_vol 1000 1100 Quota created on volume 'hr_vol'.quotas>


151

iGrid Command Line Interface (CLI) quotas Commands

quotas/remove

This command deletes a user or group quota.

Usage: quotas> remove <type> <id> <volumeName>

Parameters:

• type – The quota type: user or group.

• id – Either the UID or GID for the quota.

• volumeName – The name of the volume.

Example:quotas> remove user 123 hr_vol Quota removed from volume 'hr_vol'.quotas>


152

snapshots Commands iGrid Command Line Interface (CLI)

snapshots Commands

The following commands may be used to manage volume snapshot. All snapshot related commands are grouped under the /snapshots command set. The following commands are supported:

• schedule - Manage snapshot schedules.

• list - List all snapshots associated with a snapshot schedule.

• export - Export a snapshot.

snapshots/schedule

The following commands may be used to manage snapshot schedules. The schedule commands are grouped under the /snapshots/schedule command set. The following commands are supported:

• list - List all defined snapshot schedules.

• get - Show the properties of a snapshot schedule.

• set - Enable or Disable a snapshot schedule.

• create - Create a snapshot schedule.

• remove - Delete a snapshot schedule.

snapshots/schedule/list

This command lists all defined snapshot schedules.

Usage: schedule> list

Example:schedule> list

snapperquicksnap

schedule>


153

iGrid Command Line Interface (CLI) snapshots Commands

snapshots/schedule/get

This command shows the properties of a snapshot schedule.

Usage: schedule> get <scheduleName>

Parameters:

• scheduleName – The name of schedule whose properties will be displayed.

Example:schedule> get snapper

Schedule Name: snapper Start Time: Mon Jan 23 15:30:00 2006 Interval: Every 10 mins Source: zvol Destination: zvol Status: Activeschedule>

snapshots/schedule/set

This command enables or disables a snapshot schedule.

Usage: schedule> set <scheduleName> <enable>

Parameters:

• scheduleName – The name of schedule to enable or disable.

• enable – Enable or disable the schedule (1 = enable, 0 = disable).

Example:schedule> set snapper 1

Snapshot schedule 'snapper' enabled.schedule>

snapshots/schedule/create

This command creates a snapshot schedule.

Usage: schedule> create <scheduleName> <srcVolName> <destVolName> <srcPath> <startDate> <startTime> <snapshotInterval> <intervalUnits> <snapshotKeepNum>

Parameters:

• scheduleName – The name of new snapshot schedule.

• srcVolName – The source volume name.

• destVolName – The destination volume name.


154

snapshots Commands iGrid Command Line Interface (CLI)

• srcPath - Path on source volume to snapshot. If path is not known, use the ‘exports/browsetool’ command to browse the source volume.

• startDate – The date to start taking snapshots (format: YYYY.MM.DD, where MM = 01-12 and DD = 01-31).

• startTime – The time to take first snapshot (format: HH:MM, where HH = 00-23 and MM = 00-59).

• snapshotInterval – The time between snapshots. This must be given in a round number of weeks, days, hours or minutes. Enter the numerical value in this parameter, and in the next parameter enter the units being used (weeks, days, hours or minutes).

• intervalUnits – The units in which the snapshotInterval value was given (1 = minutes, 2 = hours, 3 = days, 4 = weeks).

• snapshotKeepNum – The number of snapshots to keep before overwriting.

Example:schedule> create hr_snapshot_sched hr_vol hr_snap_vol /mnt/hr_data

2006.01.01 00:01 7 3 10Snapshot schedule ‘hr_snapshot_sched’ created.

schedule>

snapshots/schedule/remove

This command deletes a snapshot schedule.

Usage: schedule> remove <scheduleName>

Parameters:

• scheduleName – The name of the snapshot schedule to be deleted.

Example:schedule> remove hr_snap_sched

Snapshot schedule ‘hr_snap_sched’ removed.schedule>

snapshots/schedule/export

This command exports a schedule directory (i.e., all snapshots for a schedule).

Usage: schedule> export <scheduleName> <exportName> <exportType>

Parameters:

• scheduleName - The name of the schedule to export.

• exportName - The name of the new export to be created.

• exportType - The file system type of the export to be created (0=NFS, 1=CIFS).


155

iGrid Command Line Interface (CLI) snapshots Commands

Example:schedule> export snapper hr_export 0

New export ‘hr_export’ created.schedule>

snapshots/list

This command lists all snapshots associated with a snapshot schedule.

Usage: snapshots> list <scheduleName>

Parameters:

• scheduleName – The name of the schedule whose snapshots will be displayed.

Example:snapshots> list snapper

Snapshots associated with snapshot schedule 'snapper':Snapshot Instance Time ----------------- ---- snapper:zvol.115 Tue Jan 24 10:30:01 2006 snapper:zvol.116 Tue Jan 24 10:40:01 2006 snapper:zvol.117 Tue Jan 24 10:50:02 2006 snapper:zvol.118 Tue Jan 24 11:00:01 2006 snapper:zvol.119 Tue Jan 24 11:10:02 2006

snapshots>

snapshots/export

This command exports a snapshot.

Usage: snapshots> export <snapshotName> <exportName> <exportType>

Parameters:

• snapshotName– The name of the snapshot to export.

• exportName – The name of the new export to be created.

• exportType – The file system type of the export to be created (0 = NFS, 1 = CIFS).

Example: snapshots> export snapper:zvol.115 hr_export 0

New export 'hr_export' createdsnapshots>


156

storagepools Commands iGrid Command Line Interface (CLI)

storagepools Commands

The following commands may be used to manage storage pools. All storage pool related commands are grouped under the /storagepools command set. The following commands are supported:

• list - List all storage pools on grid.

• get - Show the properties of a storage pool.

• set - Change properties of an existing storage pool (enlarge).

• create - Create a storage pool.

• remove - Delete a storage pool.

storagepools/list

This command lists all storage pools on the grid.

Usage: storagepools> list

Example:storagepools> list

Storage Pools: vg_igrid_01storagepools>

storagepools/get

This command shows the properties of a storage pool.

Usage: storagepools> get <poolName>

Parameters:

• poolName – The name of the storage pool whose properties will be displayed.


157

iGrid Command Line Interface (CLI) storagepools Commands

Example:storagepools> get vg_igrid_01 Storage Pool: vg_igrid_01 Total Size: 15.0 GB Free Space: 15.0 GB Extent Size: 4.0 MB Assigned LUNs: LUN Name: 200600a0b81848c0:3 UUID: 600a0b8000183c900000021844059144 Array WWN: 200600a0b81848c0 LUN #: 3 Desc: LSI:INF-01-00 Size: 0005.0 GB LUN Name: 200600a0b81848c0:2 UUID: 600a0b8000183c90000002174405910a Array WWN: 200600a0b81848c0 LUN #: 2 Desc: LSI:INF-01-00 Size: 0005.0 GB LUN Name: 200600a0b81848c0:4 UUID: 600a0b8000183c900000021944059172 Array WWN: 200600a0b81848c0 LUN #: 4 Desc: LSI:INF-01-00 Size: 0005.0 GBstoragepools>


158

storagepools Commands iGrid Command Line Interface (CLI)

storagepools/set

This command changes properties of an existing storage pool (enlarge).

Usage: storagepools> set <poolName> <newLuns> <optimize>

Parameters:

• poolName – The name of the storage pool that will be enlarged.

• newLuns – The new LUNs to add to the storage pool (comma-separated list, no spaces). Obtain the LUNs using the command 'resourceluns list’.

• optimize – Optimize the order of the LUNs when expanding the storage pool (0=no, 1=yes).

Example:storagepools> set vg_igrid_01 200600a0b81848c0:2,200600a0b81848c0:3 1

Storage pool 'vg_igrid_01' expanded.storagepools>

storagepools/create

This command creates a new storage pool.

Usage: storagepools> create <poolName> <extentSize> <LUNs> <optimize>

Parameters:

• poolName – The name of the new storage pool.

• extentSize – The pool extent size (in KB, powers of 2, 8KB to 16GB).

• LUNs – The LUNs to add to the new storage pool (comma-separated list, no spaces).

• optimize – Optimize the order of the LUNs when creating the storage pool (0=no, 1=yes).

Example:storagepools> create dev_pool 1000 200600a0b81848c0:2,200600a0b81848c0:3 1

Storage pool 'dev_pool' created.storagepools>


159

iGrid Command Line Interface (CLI) storagepools Commands

storagepools/remove

This command deletes a storage pool.

Usage: storagepools> remove <poolName>

Parameters:

• poolName – The name of the storage pool to be deleted.

Example:storagepools> remove dev_pool

Storage pool 'dev_pool' removed.storagepools>


160

users Commands iGrid Command Line Interface (CLI)

users Commands

The following commands may be used to manage users of the grid. All users-related commands are grouped under the /users command set. The following commands are supported:

• set - Manage iGrid users.

• list - List all users defined on the grid.

• get - Show the properties of a user.

• create - Create a user.

• remove - Delete a user.

users/set

The following commands may be used to manage existing users of the grid. All set-related commands are grouped under the /users/set command set. The following commands are supported:

• emailAddress - Set the email address for a user.

• noticeLevels - Set the notice level for a user.

• password - Set the password for a user.

• permissions - Set the cluster and storage management permissions for a user.

set/emailAddress

This command sets the email address for a user.

Usage: set> emailAddress <userName> <emailAddress>

Parameters:

• userName – The name of the user whose email address will be set.

• emailAddress – The new email address for the user.

Example:set> emailAddress jimi [email protected]

Email changed for user 'jimi'.set>


161

iGrid Command Line Interface (CLI) users Commands

set/noticeLevels

This command sets the notice level for a user.

Usage: set> noticeLevels <userName> <noticeLevels>

Parameters:

• userName – The name of the user whose notice levels will be set.

• noticeLevels – The event severity levels for which user should be notified by email (comma-separated list, no spaces). The severity levels are: 1 = fatal, 2 = error, 3 = warning, 4 = audit, 5 = threshold, 6 = info.

Example:set> noticeLevels jimi 6

Notice levels changed for user 'jimi'.set>

set/password

This command sets the password for a user.

Usage: set> password <userName> <oldPassword> <newPassword> <confirmNewPassword>

Parameters:

• userName – The name of the user whose password will be set.

• oldPassword – Enter the user’s old password (if you are changing your own password). If you are a management user changing another user's password, enter your own (management-level) password here.

• newPassword – The new password for the user.

• confirmNewPassword – Re-enter the new password.

Example:set> password jimi jimipwd newpwd newpwd

Password changed for user 'jimi'.set>


162

users Commands iGrid Command Line Interface (CLI)

set/permissions

This command sets the cluster and storage management permissions for a user.

Usage: set> permissions <userName> <clusterPermissions> <storageMgmtPermissions>

Parameters:

• userName - The name of the user whose password will be set.

• clusterPermissions - The new cluster management permissions for the user. (0=Read, 1=Read/Modify, 2=None)

• storageMgmtPermissions - The new storage management permissions for the user. (0-Read, 1=Read/Modify, 2=None)

Example:set> permissions jimi 1 1

Permissions changed for user ‘jimi’.set>

users/list

This command lists all users defined on the grid.

Usage: users> list

Example:users> list

foo2 cwsupport jimi adminusers>

users/get

This command shows the properties of a user.

Usage: users> get <userName>

Parameters:

• userName – The name of the user whose properties will be displayed.


163

iGrid Command Line Interface (CLI) users Commands

Example:users> get jimi

User Name: jimi E-mail Address: [email protected] Alert Severities: infousers>

users/create

This command creates a new user.

Usage: users> create <userName> <password> <userType>

Parameters:

• userName – The name of the new user.

• password – The password for the new user.

• userType – The type of user to create (0 = Management, 1 = CIFS, 2 = Both).

Example:users> create foo foospasswd 2

New user 'foo' created.users>

users/remove

This command deletes a user.

Usage: users> remove <userName>

Parameters:

• userName – The name of the user to be deleted.

Example:users> remove ox

Do you really want to delete user 'ox'? (y/n) yUser 'ox' deleted.

users>


164

volumes Commands iGrid Command Line Interface (CLI)

volumes Commands

The following commands may be used to manage storage volumes. All volumes-related commands are grouped under the /volumes command set. The following commands are supported:

• set - Modify properties of existing storage volumes.

• list - List all volumes on the grid.

• get - Show the properties of a volume.

• create - Create a volume.

• remove - Delete a volume.

• copy - Copy a system file to another volume.

• copyIn - Copy a remote file system to a local volume.

• copyOut - Copy a local file system to a remote node.

volumes/set

The following commands may be used to manage existing storage volumes. All set-related commands are grouped under the /volumes/set command set. The following commands are supported:

• createFileSystem - Create a filesystem on an existing volume.

• expand - Expand an existing volume.

• mount - Mount an existing volume.

• unmount - Unmount an existing volume.

volumes/createFileSystem

This command creates a file system on an existing volume.

Usage: set> createFileSystem <volumeName>

Parameters:

• volumeName – The volume on which the file system will be created.

Example:set> createFileSystem hr_vol

Creating file system...(Please be patient. This may take some time.)File system created on volume 'hr_vol'.

set>


165

iGrid Command Line Interface (CLI) volumes Commands

volumes/expand

This command expands an existing volume.

Usage: set> expand <volumeName> <spacetoAdd>

Parameters:

• volumeName – The volume to expand.

• space To Add – The amount of space to add to the volume (in MB). This value must be less than the free space available in this volume's storage pool.

Example:set> expand hr_vol 100

Volume ‘hr_vol’ expanded.set>

volumes/mount

This command mounts an existing volume.

Usage: set> mount <volumeName>

Parameters:

• volumeName – The volume to mount.

Example:set> mount hr_vol

Volume ‘hr_vol’ mounted.set>

volumes/unmount

This command unmounts an existing volume.

Usage: set> expand <volumeName> <spacetoAdd>

Parameters:

• volumeName – The volume to unmount.

Example:set> unmount hr_vol

Volume ‘hr_vol’ unmounted.set>


166


volumes/list

This command lists all volumes on the grid.

Usage: volumes> list

Example:volumes> list

Volumes: crosswalk zvolvolumes>

volumes/get

This command shows the properties of a volume.

Usage: volumes> get <volumeName>

Parameters:

• volumeName – The name of the volume whose properties will be displayed.

Example:volumes> get hr_vol

Volume ID: hr_vol Available Size: 8.0 GB Stripe Size: 64.0 KB Stripe Width: 2 Storage Pool: vg_igrid_01 Exportable: true Type: Stripe Set volumes>


167


volumes/create

This command creates a new volume.

Usage: volumes> create <volumeName> <poolName> <volumesize> <stripeWidth> <stripeSize>

Parameters:

• volumeName – The name of the new volume.

• poolName – The storage pool the new volume will be created in.

• volumeSize – The size of the new volume (in GB). The minimum size is 2GB and it cannot exceed the free space left in the storage pool.

• stripeWidth - The width of the new volume (0 for a volume set and 1 for a stripe set).

• stripeSize – The stripe size of the new volume (in KB, power of 2, 4KB to 512KB).

Example:volumes> create dev_vol lsi_pool 5000 4 128

Volume 'dev_vol' createdvolumes>

volumes/remove

This command deletes a volume.

Usage: volumes> remove <volumeName>

Parameters:

• volumeName – The name of the volume to be deleted.

Example:volumes> remove dev_vol

Do you really want to delete volume 'dev_vol'? (y/n) yVolume 'dev_vol' deleted.

volumes>

volumes/copy

This command copies a file system on one volume to another volume.

Usage: volumes> copy <sourceVolume> <sourcePath> <targetVolume> <targetPath>

Parameters:

• sourceVolume – The name of the source volume.

• sourcePath – The path to copy from on the source volume.

• targetVolume – The name of the target volume.


168


• targetPath – The path to copy to on the target volume.

Example:volumes> copy dev_vol /alldev dev_backup_vol /alldev_19june2006

File system 'dev_vol:/alldev' copied to ev_backup_vol:/alldev_19june2006’.

volumes>


169


volumes/copyIn

This command copies a remote file system to a local volume.

Usage: volumes> copyIn <targetVolume> <targetPath> <user> <password> <host> <sourcePath>

Parameters:

• targetVolume – The name of the target volume.


• user – The name of the user on the remote node.

• password – The password of the user on the remote node.

• host – The host name (or IP address) of the remote node


Example:volumes> copyIn dev_vol /alldev igadmin ******** ignode2 /alldev_19june2006

Remote file system ‘ignode2:/alldev_19june2006’ copied to ‘dev_vol:/alldev’.

volumes>

volumes/copyOut

This command copies a local file system to a remote node.

Usage: volumes> copyOut <sourceVolume> <sourcePath> <user> <password> <host> <targetPath>

Parameters:

• sourceVolume – The name of the source volume.


• user – The name of the user on the remote node.

• password – The password of the user on the remote node.

• host – The host name (or IP address) of the remote node


Example:volumes> copyOut dev_vol /alldev igadmin ****** ignode2 /alldev_19june2006

Local file system 'dev_vol:/alldev' copied to ‘ignode2:/alldev_19june2006’.

volumes>


170

– APPENDIX A –

Using BakBone’s® NetVault™ with Crosswalk iGrid

This Appendix describes how to use BakBone’s NetVault backup and restore application with Crosswalk iGrid. The NetVault server application itself, running on iGrid in a high availability configuration, is used for backing up and restoring data.


• Installing BakBone’s NetVault Client on page 172

• Configuring a Linux Machine for NetVault on page 172

• Configuring a Windows 2000/2003 Machine for NetVault on page 175

• Set Up NetVault in iGrid on page 182

• Create a Virtual Library on page 185

• Backing Up with Crosswalk iGrid on page 186

• Network Data Management Protocol (NDMP) – Configure Job on page 186

• Create Backup Job/Schedule on page 199

• Invoke NetVault Client (Agent) on a Node To Be Backed Up on page 216

• Installation of NetVault Backup Client Agent on page 218

• NetVault Failover on page 221

• Restoring with Crosswalk iGrid on page 222

• Restore Window Buttons on page 222

• Server Selection on page 223

• Restore Window on page 224

• Performing A Restore on page 234

Crosswalk iGrid

171

Using BakBone’s® NetVault™ with Crosswalk iGrid Installing BakBone’s NetVault Client

Installing BakBone’s NetVault Client

This Section describes how to install, set up, and configure the NetVault client on both Windows and Linux machines for use with Crosswalk iGrid. The following lists the installation requirements, regardless of operating system:

• Sufficient disk space to install and use the software

• A TCP/IP Network

• Minimum graphic display resolution of 800 x 600 pixels displaying 256 colors

• Permissions granted for users to install components

• Minimum 128 Mb

For other important points to consider when installing the NetVault Client, refer to the NetVault Administrator’s Guide for version 7.3 at the BakBone website, http://www.bakbone.com.

Configuring a Linux Machine for NetVault

This section describes how to run the NetVault client installation files.To run the NetVault client installation files, do the following:

1. Obtain the NetVault distribution tar file.netvault-R2004NOV05-73-Linux.tar.gz

2. At the command prompt, type tar -xzf netvault-R2004NOV05-73-Linux.tar.gz to uncompress and untar the file into the netvault directory under your current directory.

3. At the command prompt, type the following commands:cd /netvault./install

The installation script appears in the window. The following is output from the install script, with the appropriate answers in bold red. Respond to each question and press Enter after each response.

Crosswalk iGrid

172

Configuring a Linux Machine for NetVault Using BakBone’s® NetVault™ with Crosswalk iGrid

./installThe installation process is invoked in /var/tmp/netvaultUsing default /tmp as the temporary directoryExpanding distribution file

NetVaultCopyright (c) BakBone Software Inc. 2000-2003

Have you read and agreed to the terms of the license?(y = yes, n = no, d = display license) (y n d) [d] : yShould a client or server version of NetVault be installed? (c s) [c] : cWhere should NetVault be installed? /usr/netvaultWhere should NetVault database be installed? /usr/netvault/dbPlease enter a NetVault machine nameusing A-Z, a-z, _ and 0-9 <type the hostname here>

Install Script Echo

The following information is echoed from the install script. Respond to each question and press Enter after each response

Please enter the NetVault password for this machine: <type your password here>

Please enter the NetVault password for this machine: <type your password here>

Please confirm password: checkinstall running

CHOSEN_CLASSES=core server dataplugin devicectl gui onlinehelp

PKG_BASE=/usr

preinstall running

Installing core

Installing server

Installing dataplugin

Installing devicectl

Installing gui

Installing onlinehelp

postinstall running

HOST_OS=Linux

NV_UPGRADE=

Creating database directory /usr/netvault/db

Crosswalk iGrid

173

Using BakBone’s® NetVault™ with Crosswalk iGrid Configuring a Linux Machine for NetVault

Installing libraries

libnv6audit.so

libnv6cli.so

libnv6db.so

libnv6gui.so

libnv6jobs.so

libnv6ndmp.so

libnv6plugin.so

libnv6reports.so

libnv6scsi.so

libnv6.so

libnv6stats.so

libnv6xctl.so

libnv6xpm.so

Creating symbolic links

Setting reports/stats paths

License installed: 'TRUE'

Installing base npk's

Successfully installed '/mnt/nvdata/n1b/packages/nty1110.npk'

Successfully installed '/mnt/nvdata/n1b/packages/rpt1210.npk'

Checking for components in /mnt/nvdata/n1b/packages

Installing additional npk's

Successfully installed '/mnt/nvdata/n1b/packages/hlp1000.npk'

Successfully installed '/mnt/nvdata/n1b/packages/raw2110.npk'

Successfully installed '/mnt/nvdata/n1b/packages/dvy4900.npk'

Successfully installed '/mnt/nvdata/n1b/packages/ver1110.npk'

Successfully installed '/mnt/nvdata/n1b/packages/dvx4900.npk'

Successfully installed '/mnt/nvdata/n1b/packages/dvz4900.npk'

Successfully installed '/mnt/nvdata/n1b/packages/ddv2210.npk'

Crosswalk iGrid

174

Configuring a Windows 2000/2003 Machine for NetVault Using BakBone’s® NetVault™ with Crosswalk iGrid

Successfully installed '/mnt/nvdata/n1b/packages/dup1110.npk'

Successfully installed '/mnt/nvdata/n1b/packages/nvf5a10.npk'

Checking for components in /mnt/nvdata/n1b/serverpackages

Installing server npk's

Successfully installed '/mnt/nvdata/n1b/serverpackages/nvd4110.npk'

Successfully installed '/mnt/nvdata/n1b/serverpackages/con3310.npk'

Successfully installed '/mnt/nvdata/n1b/serverpackages/cpy2310.npk'

Checking for extra components in /mnt/nvdata/n1b/extrapackages

Copying non-installable additional npk's

Setting NetVault machine password

Not an upgrade - installing NetVault Services

Will link to '/usr/etc/startup.sh'

Starting NetVault Services

Copying uninstallation scripts

Installation completed successfully

Verify the Installation

To verify the installation, type ps -aux |grep nv at the command prompt.

Configuring a Windows 2000/2003 Machine for NetVault

Prior to installing NetVault on a Microsoft Windows 2000/2003 machine, it is necessary to configure the operating system in order to allow certain functions of NetVault to run properly.

Devices or libraries being added to a Windows 2000/2003 operating system cannot be under the control of the Windows 2000/2003 Remote Storage Manager. To remove the library from the Remote Storage Manager control, follow the steps below:

1. Boot the Windows 2000/2003 machine and log in as an Administrator-level user.

2. From the desktop, after successful boot, right-click on the My Computer icon and choose the Manage command from the pop-up menu that appears in order to access the Computer Management window.

3. Navigate through each level of the tree until the desired device is displayed.

4. Right-click on the device and choose Properties from the pop-up menu.

Crosswalk iGrid

175

Using BakBone’s® NetVault™ with Crosswalk iGrid Configuring a Windows 2000/2003 Machine for NetVault

5. In the Properties dialog box, with the General tab selected, click on the Enable library checkbox in order to de-select it.

Figure A-1 Disable Library

6. Click Apply to set the change, and then OK to exit the dialog box.

It is now possible to install the NetVault Software on a Windows 2000/2003 machine.

Run the Installation file

This section describes how to install the NetVault client on a Windows 2000/2003 server. All files referenced may be downloaded from http://www.bakbone.com.

Note: On a Windows 2003 Server running in Terminal Services mode, an additional Installation Wizard window may launch when attempting to install NetVault. A Windows 2003 Server in this state has a concept of an “install mode” and an “execute mode.” Therefore, when attempting an installation of software, the Server attempts to both “execute” and “install,” resulting in two installation wizards running simultaneously. This is considered normal behavior and one of the wizards can simply be ignored (and closed).

To run the NetVault client installation files, do the following:

1. Obtain the NetVault distribution zip file.netvault-R2004NOV06-DAATAA-Windows.zip

2. Uncompress the file into a directory of your choice, intuitively named, i.e., c:\temp\netvault.

3. Run the NetVault setup file one of two ways:

Crosswalk iGrid

176


• Double-click the Setup.exe file in the directory where the files were uncompressed.

• Go to the Start menu, choose Run and type the path and Setup.exe file name, i.e., c:\temp\netvault\setup.exe. Click OK.

The NetVault Setup Wizard will start.

4. Read and agree to the NetVault License Agreement to proceed. Click Next.

5. Choose your installation type. Crosswalk recommends Server, so that other servers may be remotely managed.

Crosswalk iGrid

177


6. Name the server machine. Crosswalk suggests taking the default name.

7. Enter a password of your choice. Retype it to verify.

8. The next screen will ask you for an installation folder. Crosswalk suggests taking the default path.

Crosswalk iGrid

178


9. Select a folder for the NetVault database. Crosswalk strongly suggests taking the default path.

10. Confirm and begin the installation by clicking the Next button. The Installing NetVault screen will appear showing a progress bar for the installation.

Crosswalk iGrid

179


11. When the Installation Complete screen appears, declaring a successful installation, click the Close button.

12. The NetVault software is now installed.

Add the BIN Directory Variable

In order to launch the NetVault software from the iGrid User Interface, you must add the NetVault bin folder to your path.

1. Right-click on the My Computer icon on your desktop or under the start menu. Select Properties and the System Properties window will pop up.

2. Select the Advanced tab and click on the Environment Variables button at the bottom of the window.

Crosswalk iGrid

180


3. In the Environment Variables window a list of system variables is displayed in the bottom half of the page. Scroll down to Path, select it and click the Edit button.

4. Append the NetVault bin directory path to the existing path variables by typing a semi-colon (;) at the end of the current Variable Value and then typing the path for the NetVault bin directory. If you used the default path as in the example above, it will read:

C:\Program Files\BakBone Software\NetVault\bin\

5. Click the OK buttons throughout the windows until you are back to your Windows desktop. You must now reboot your machine to finalize the addition of the bin path.

Crosswalk iGrid

181

Using BakBone’s® NetVault™ with Crosswalk iGrid Set Up NetVault in iGrid

Set Up NetVault in iGrid

This section will detail the steps involved to set up NetVault Domain Management in Crosswalk iGrid. To configure NetVault, do the following:

1. Open and log into the iGrid user interface.

2. Select the Backups tab from the top of the page. The Backups page opens.

3. Click Launch NetVault.

4. The NetVault interface appears.

If the NetVault interface does not appear, verify that Java JRE is in the default path entered when you installed NetVault.

5. Select the Administration menu.

Crosswalk iGrid

182

Set Up NetVault in iGrid Using BakBone’s® NetVault™ with Crosswalk iGrid

6. From the Administration menu, choose Domain Management. The Domain Management configuration page appears.

7. Enter the iGrid NetVault server name, if using DNS, or the management VIP used during installation, e.g., “nvGRIDNAME01.” In the above illustration, the name is nvpikes01.

8. Click Find.

Crosswalk iGrid

183

Using BakBone’s® NetVault™ with Crosswalk iGrid Set Up NetVault in iGrid

9. The server name will now appear in the Available NetVault Servers window.

10. Double-click the server name in the list. You will be prompted to enter your password. Enter the password you chose when installing NetVault.

Crosswalk iGrid

184

Create a Virtual Library Using BakBone’s® NetVault™ with Crosswalk iGrid

The server name will move to the Controlled Servers side of the window.

11. Right-click on the server name and select Make Default.

12. iGrid will begin reading and backing up the volumes for this server.

Create a Virtual Library

Once NetVault is installed in iGrid, create a Virtual Library (VTL) for backup storage.

1. Set up a Volume using the iGrid GUI, per the instructions in Chapter 3.

2. In NetVault, refer to the path as /mnt/iGrid/<volume name> for the library location.

Crosswalk iGrid

185

Using BakBone’s® NetVault™ with Crosswalk iGrid Backing Up with Crosswalk iGrid

Backing Up with Crosswalk iGrid

This Section describes how to use Crosswalk iGrid to back up your network and system configurations

Network Data Management Protocol (NDMP) – Configure Job

This section describes how to configure NDMP APM jobs. Configure devices for use with the NDMP APM the same way you configure any other devices used with NetVault.

NDMP-enabled NAS devices appear in the Add Device window of NetVault as though they are connected to all clients. However, it is only necessary to add the device to one client. For maximum transfer performance, NetVault recommends that you add the device to the client with the most data to be transferred to the drives.

Backing Up Data with the NDMP APM

This section describes how to use the NDMP APM to back up data. To back up data, do the following:

Selections

1. Do either of the following to open the NetVault Backup window:

• On the NetVault Backup toolbar, click Backup.

• On the NetVault Backup menu, do the following:

a. Click File

b. Click Open.

c. Click Operations Backup.

Under the Selections tab, the NetVault Backup window displays the list of clients.

2. To display the list of clients, do the following:

a. Right-click on the NDMP APM.

A popup menu opens.

b. Right-click Open.

Crosswalk iGrid

186

Network Data Management Protocol (NDMP) – Configure Job Using BakBone’s® NetVault™ with Crosswalk iGrid

Figure A-2 NetVault Backup

If this is the first time the plugin has been opened, the NDMP server dialog box opens and the server information must be supplied. Ensure that the NDMP server has been installed. To configure the NDMP server, do the following:

3. Right-click on the NDMP server.

A pop-up menu opens.

4. On the pop-up menu, click Open.

The NDMP Backup Request dialog box opens.

Figure A-3 NDMP Backup Request

5. Enter required information.

a. In the Directory text box, type the complete path name of the data tree to be backed up.

Crosswalk iGrid

187

Using BakBone’s® NetVault™ with Crosswalk iGrid Network Data Management Protocol (NDMP) – Configure Job

• You can back up only full volumes, not individual directories or files.

• You can type only one directory path in the Directory text box.

• You cannot type the full path to an individual file; that is, you cannot back up a single file.

WARNING — Attempting to back up a single file causes the backup job to fail.

b. From the Dump Level drop-down list, select the backup interval:

• Level 0 designates a full backup.

• Levels 1 through 9 designate incremental backups. The Dump Levels section on page 189 describes the incremental backup dump levels.

6. Select optional configurations:

• To activate updating the /etc/dumpdates file after a successful dump, check the /etc/dumpdates box.

• By default the /etc/dumpdates box is checked.

• For full updates, the box can be either checked or unchecked; however, when conducting incremental updates, this box must be checked.

• To back up all files and directories outside of all qtrees of the specified volume, check the Backup Non-Quota Tree Data box. The NAS filer documentation describes dump option q in more detail.

• To back up the ACLs of all files, check the Backup ACLS box.

By default, the Backup ACLS box is checked.

• If you are running Data ONTAP version 6 or later, choose whether or not to conduct a direct backup.

• To conduct a direct backup, check the Do Direct Backup if Possible box.

• When the Do Direct Backup if Possible box is unchecked, an indirect backup is performed.

• To save file information. check the Save File Information box.

• By default the Save File Information box is checked.

• When the Save File Information box is checked, single items contained within a backup can be individually restored.

• When the Save File Information box is unchecked, single items within a backup cannot be individually restored. Instead, a single backup item must be fully restored.

• To exclude files from a backup, type the file names in the Exclude text box.

• Separate multiple files with a comma.

• You can use no more than two wild cards per file, and wild card characters can only be used at the beginning or end of a file name.

Crosswalk iGrid

188


• To write the backup index to the backup media, check the Write Index to Backup Media box.

• By default the Write Index to Backup Media box is checked.

• When the Write Index to Backup Media box is checked, a backup index is created and stored on the media where the data was backed up.

• When the Write Index to Backup Media box is unchecked, no backup index is created.

• To use direct access restore, the Write Index to Backup Media box must be checked.

7. Click OK to accept the selections and return to the NetVault Backup window.

Backup Options

No backup options are available with this APM. The Backup Options tab is inactive.

Schedule Options

The Schedule options tab selections function the same as a standard NetVault backup.

Target Options

The Target options tab selections function the same as a standard NetVault backup.

Advanced Options

The Advanced options tab selections function the same as a standard NetVault backup.

Job Title

To designate a job title, do the following:

1. Type a descriptive job title in the Job Title text box.

2. To start the backup job, click on the Submit button.

Figure A-4 Job Title

Dump Levels

This section describes how to designate dump levels in the Dump Level drop-down list in the NDMP Backup Request dialog box. Dump levels identify the type of backup:

• Dump Level 0 is the default level. This level executes a full backup.

• Dump Level 1 executes an incremental backup of data new since the last full backup performed at Dump Level 0.

Crosswalk iGrid

189


• Dump Level 2 executes an incremental backup of data new since the last incremental backup performed at Dump Level 1.

• Dump Level 3 executes an incremental backup of data new since the last incremental backup performed at Dump Level 2.

• Subsequent dump levels 4 through 9 execute incremental backups of data new since the previous dump level backup.

• Only one dump at each level is retained in memory. For example, if the dump level is set to 0 to conduct a full backup, all previous dump levels are no dropped.

Restoring Data with the NDMP APM

This section describes how to use the NDMP APM to restore backed-up data. To restore backed-up data, click Restore on the toolbar to open the NetVault Restore window.

The NetVault Restore window opens and displays a list of clients that have restorable data.

Select a Client to Restore

To select a client to restore do the following:

1. Right-click on the desired client.


2. Click Open

A list appears of plugins that have data available to be restored.

3. Right-click on the NDMP APM

The NDMP APM opens and displays the backup savesets on the selected NDMP client.

4. Double-click on the backup saveset.

5. Click on the data items to be restored.

Crosswalk iGrid

190


Figure A-5 Restore Selections

Note: If the Save File Information box was unchecked before the backup was completed, you can select only a complete backup saveset to restore.

Choose Restore Options

To choose the restore options, do the following:

1. To display the options available for use with the NDMP APM, click on the Restore Options tab.

Figure A-6 Restore Options

Crosswalk iGrid

191


2. Designate the NDMP server.

• The NDMP Server text box contains the preassigned NetVault name for the NDMP server. By default the NDMP Server text box shows the name of the server the data was backed up from.

• To accept the default NDMP server, no action is necessary.

• To redirect the restore to another server, type the other server’s name in the NDMP Server text box. To redirect the restore to another server, ensure that the server has been successfully added.

3. Select the direct access restore method.

• To use direct access restore if possible, select Use Direct Access Restore if Possible.

• To use direct access restore by recovering individual files, select Use Direct Access Restore by Recovering Individual Files.

• To perform a direct access-only restore, select Only Do Direct Access Restore.

• To never perform a direct access restore, select Never Do Direct Access Restore.

4. Choose whether or not to do an incremental restore.

• Check the Incremental Restore box to perform an incremental restore.

• Uncheck the box to perform a complete restore.

• Refer to the Network Appliance documentation for information on restore options r and x.

5. Choose whether or not the restore ACLs.

• By default, the Restore ACLs box is checked.

• When the Restore ACLs box is checked, the ACLs pertaining to the backup are restored if they had been selected for the original backup.

• When the Restore ACLs box is unchecked, the ACLs pertaining to the backup are not restored.

• Refer to the Backing Up Data with the NDMP APM section on page 189.

Crosswalk iGrid

192


Target Client

The Target Client tab selections function the same as a standard NetVault restore.

Schedule

The Schedule tab selections function the same as a standard NetVault restore.

Advanced Options

The Advanced Options tab selections function the same as a standard NetVault restore.

Job Title

To designate a job title, do the following:

1. Type a descriptive job title in the Job Title text box.

2. To start the restore job, click on the Submit button.


Renaming a Restore Backup Saveset

This section describes how to rename a restore job when restoring it with the NDMP APD. With a non-direct restore, you can rename only the root directory in a backup. For example, only directories can be renamed. Individual items must retain their existing names.

To rename a backup saveset when restoring it, do the following:

1. On the NetVault Restore window, click on the Selections tab.

2. Double-click on the backup saveset to open it.

3. Right-click on the item.

A popup menu opens.

4. Click Rename.

The Restore Rename dialog box opens.

Crosswalk iGrid

193


Figure A-8 Restore Rename

5. Check the Rename to box.

6. In the Rename to text box, type a new path and file name.

7. Click OK to save the change and return to the NetVault Restore window.

• The new name appears under the Selections tab in the NetVault Restore window.

Figure A-9 Renamed Restore Job

8. Continue selecting restore options.

9. Click Submit to submit the renamed job.

Crosswalk iGrid

194


Direct Access Restores

This section describes how to conduct a direct access restore (DAR). A DAR allows you to more quickly locate an individual item and recover it. The DAR seeks out the specific file to be restored without reading the entire saveset at read speed, which can be slow.

• You can run direct access restores only from backup savesets that were set for Do Direct Backup if Possible from the backup menu.

• Direct access restore is available only for filers running OPTAP version 6.x and later.

• You can select only standard files for recovery when employing a direct access restore. Directory permissions and special files such as symbolic links are not restored.

• Only 1024 files can be specified in a direct access restore; therefore, NetVault batches the restores into groups of 1024 files at a time.

To run a Direct Access Restore, do the following:

1. Right-click on the desired client.


2. Click Open

A list appears of plugins that have data available to be restored.

3. Right-click on the NDMP APM

The NDMP APM opens and displays the backup savesets on the selected NDMP client.

4. Double-click on the backup saveset.

5. Click on the data items to be restored.

Crosswalk iGrid

195


Figure A-10 Restore Selections

Note: If the Save File Information box was unchecked before the backup was completed, you can select only a complete backup saveset to restore.

6. From the Restore Options window, set items as desired in regards to NDMP server, Incremental Restore and Restore ACLs.

7. In the Direct Access Restore Method area, choose one of the following direct access restore options.

Figure A-11 Direct Access Restore

• Choose Use Direct Access Restore if Possible when the backup was direct and the mover and the data server can complete a direct access restore. If the mover and data server cannot complete a direct access restore, a non-direct restore will occur.

• Choose Use Direct Access Restore by Recovering Individual Files to allow the direct access restore of a specific Directory. Note that this is the only option to achieve this and it is not default selected.

• Choose Only Do Direct Access Restore to perform a direct access restore.

Crosswalk iGrid

196


• Only Do Direct Access Restore must be selected if any items have been marked as omitted under the Selections tab. The restore will fail if items are omitted and Only Do Direct Access Restore was selected.

• When Only Do Direct Access Restore is selected, the backup being restored must be a direct backup, and a capable mover and data server must be available. The restore will fail if the backup was not a direct backup or a capable mover or data server are not available.

• Choose Never Do Direct Access Restore to perform only non-direct access restores. For Data ONTAP 5.X and earlier versions, you must choose Never Do Direct Access Restore.

Renaming and/or Relocating a Direct Access Restore

This section describes how to rename and relocate any item from a DAR. To rename or relocate a DAR, you must have selected Direct Access Restore by Recovering Individual Files.

• When Direct Access Restore by Recovering Individual Files is not selected, you can rename only the root item in a backup; that is, a directory can be renamed, but individual items must retain their existing names and directories and files cannot be relocated.

• Renaming or relocating a direct access restore is not available to ONTAP 5.x and earlier versions.

To rename or relocate an item from a DAR, do the following:

1. On the NetVault Restore window, click on the Selections tab.

2. Double-click on the backup saveset to open it.

3. Right-click on the item to be renamed or relocated.

4. Click on the Restore Options tab.

5. Click on Use Direct Access Restore by Recovering Individuals tab.

6. Click on the Selections tab.


7. Click Rename.

The Restore Rename dialog box opens.

Crosswalk iGrid

197


Figure A-12 NetVault Restore

8. Check Rename to.

9. In the Rename to text box, type the new restore origination path.

10. Check Relocate to.

11. In the Relocate to text box, type the new restore destination path.

12. Click OK to save the changes and return to the NetVault Restore window.

• The new name appears under the Selections tab in the NetVault Restore window.

Figure A-13 Renamed or Relocated Restore

Crosswalk iGrid

198

Create Backup Job/Schedule Using BakBone’s® NetVault™ with Crosswalk iGrid

Create Backup Job/Schedule

This section describes how to create a NetVault backup window. Accessed through one of the ways shown below, the Backup window of NetVault is where all aspects of a backup are controlled.

Figure A-14 Backup Operations

NetVault Backup is the name given to the transfer of data from a NetVault client to a backup device. The media held in this device stores the data, where it can be recovered by NetVault as required. In essence, a NetVault server machine issues commands to a NetVault client on the network which in turn backs up data therein to the media contained in the device. The NetVault server can also act as a NetVault client to itself, allowing for a backup of its own data.

Most backups are very easy to create and submit. The NetVault Backup window provides access to a number of control functions, including many that can be used for special circumstances.

Data can be backed up in a variety of ways, including:

• A NetVault Server can back up its data to itself as a NetVault Client.

• Data can be backed up to devices across a network.

• Backed up data can be placed on more than one type of media.

• Backups can be scheduled to run automatically.

• Data can be backed up completely or incrementally.

The Backup Window - A Brief Overview

The NetVault Backup window provides facilities for creating, editing and submitting backup jobs for any NetVault client controlled by the selected NetVault server. This Section covers the functions of all of the commands found in this window as well as the process involved in performing a simple NetVault backup.

Crosswalk iGrid

199

Using BakBone’s® NetVault™ with Crosswalk iGrid Create Backup Job/Schedule

NetVault Backup Window Basics

This section details the basic features that are consistent among the various tab selections throughout the NetVault Backup window. This generally includes the top section of the window itself, just above the tab selections.

Figure A-15 NetVault Backup Window

The Menu Bar

The Backup window menu bar is composed of the following commands:

• File

• View

• Accept

• Help

The following table briefly illustrates the commands found under each Menu Bar item in the Backup window.

Crosswalk iGrid

200


Table A-1 Backup Menu Commands and Results

The Backup window buttons shown below allow for access to the following options:

Figure A-16 Backup Window Buttons

Crosswalk iGrid

201


Table A-2 Backup Window Buttons

Server selection

The server selection text box allows for the selection of the NetVault server desired to control the current process. The list displays all controlling NetVault servers for each NetVault domain that has been added via the NetVault Domain Management window.

Figure A-17 Server Selection

Job Title

This text box allows the user to input a relevant title for the backup job. After a job is submitted, this title is saved along with the job. This allows for recognizing the job in the logs or when loading a previously run job. Any value can be input in this text box.


When a new job starts, this text box defaults to No Title. Failure to type a job title results in the job being named No Title when the job is either saved or run.

Crosswalk iGrid

202


Backup Window Tabs

The NetVault Backup window contains five tabbed sections that allow for various backup settings. The five tabs are as follows:

• Selections

• Target

• Backup Options

• Advanced Options

• Schedule

The Selections Tab

The default tab selection in the Backup window, this tab is used to select data for a backup. This is done through the use of one of the NetVault plugins, provided as part of the standard installation or with one of the many Application Plugin Modules (APMs). These are available separately and must be installed for use.

Figure A-19 Selections

The Selections tab is broken down into two areas:

• Selection

• Backup Selection Set

The Selection Window

Here, data items are selected for inclusion in a backup job. When a NetVault Server is opened (by double-clicking on it or by right-clicking and selecting Open from the pop-up menu), the plugins and APMs installed will be revealed. At default, with a server installation of the software, the following plugins are included and will be displayed.

• Consolidate File System Backups T Data Copy

• File System T Raw Device

• NetVault Databases

Crosswalk iGrid

203


Selecting Data for a Backup

This section details how data is selected for a backup. For the sake of this example, NetVault's File System plugin is being used.

It is only possible to select items from a single plugin (or APM) with any given backup. If backups are required using other plugins, they must be done separately.

The method detailed in this section for selecting data for a backup is the same regardless of the plugin or APM being used. However, some restrictions apply in regards to the types of selections that are possible, based on the APM or plugin being used.

To select data for a backup, do the following:

1. With the Backup window open and the Selections tab active, double-click on the desired NetVault server to open it (or right-click on it and select Open from the popup menu).

Figure A-20 File Systems

2. Double-click on a plugin or APM (e.g., the File System plugin) to open it (or right-click and select Open).

• Items that can be selected for a backup are now displayed. Select an item by clicking in the box to the left of the desired item. Once selected, the item will contain a large, green check (i.e., the Fixed Drives item shown in the example above.

• Some items can be opened further to allow for the selection of individual items contained within. Prior to selecting an item, double-click on it to open it and display its contents. When an individual item is selected, it is marked with the same large, green check, but the root item is marked with a grey box containing a smaller, green check.

Figure A-21 Selected Drives

• If the root item is selected (either before or after opening it) all items contained within will be selected as well. The root item is then marked with a large, green check and each item contained within is marked with a smaller, green check.

Crosswalk iGrid

204


Figure A-22 Additional Selected Drives

3. At this point, it is possible to omit items from a selection. With a root item selected and opened, click in the box to the left of a desired sub-item to mark it as omitted. Omitted items are marked with a red cross and the root item is marked with a grey box containing a smaller, green check.

The following figure shows example forms of selections.

Figure A-23 Example Backup Selections

The Backup Selection Set

A Backup Selection Set allows the user to save often used selections that are made in the Selections window into a complete set that can be retrieved for later use.

The Backup Options Tab

This tab displays various options pertaining to a backup, based on the plugin or APM in use. This window is not accessible unless items are first selected for a backup in the Selections window.

Crosswalk iGrid

205


Figure A-24 NetVault Backup

Crosswalk iGrid

206


Backup Options Set

A Backup Options Set allows the user to save often used selections that are made in the Backup Options tab into a composite set that can be retrieved for later use.

Not all NetVault plugins and APMs offer Backup Options, therefore only those that do allow for the creation of a Backup Options Set.

The Schedule Tab

The Schedule tab is used to set the time that a job is to be run. Jobs can be scheduled to run immediately, at a later date or time, or when triggered by a command line or script command. Options are also available to set a job to run once or repeat.

Schedule Set

A Schedule Set allows the user to save often used selections that are made in the Schedule tab into a composite Selection Set that can be retrieved for later use.

The Target Tab

The Target tab allows the user to set the destination for backed up data. From this window, it is possible to target specific media or devices as well as set various parameters for such. The Target tab is broken down into four areas.

Figure A-25 Target Tab

Crosswalk iGrid

207


• Device Options

This dialog box allows a user to specify the device that the backup is to target. The following options are available.

• Any Device (Default) - Using an advanced algorithm, NetVault will send backup data to the most suitable device setup available.

• Specify Device - When this item is selected, all devices available to the NetVault Server will be displayed in the window. At default all devices will be selected.

• NetVault will only list devices that have been properly added (or identified through Automatic Device Configuration).

• To de-select a device, simply click in the check box to the left to remove the check mark.

Figure A-26 Specify Device

• Media Options

This dialog box allows the user to set various options pertaining to media contained in a targeted device. The following options are available.

• Target Media By:

• Any not in a group (Default) - When selected, NetVault will use an advanced algorithm to back up selected data, using the most suitable media available, which is not in a group.

Note: If all available media have been allocated to a group, the backup will halt with a message stating, “Waiting for Media.”

• Any - Using another advanced algorithm, NetVault will backup data to the most suitable media available when this item is selected.

• MID -When selected, this option will activate a pull-down menu (to the right of the item) which allows the user to select a specific type of media based on its Media Identifier (or Media Label. Only this media are used for the backup.

Figure A-27 The MID and Group Label

Crosswalk iGrid

208


• Group Label - When selected, this option will activate a pull-down menu which allows the user to select a specific group of media based on its Group Label. Only media within this group will be used for the backup.

• Label Media:

• Automatically label blank media (default selected) - With this option selected, NetVault will automatically label and use any blank media, when no other media are available for the job.

Figure A-28 Automatically Label Blank Media

• Reuse Media:

• Never (Default) - With this set, no media will marked for re-use will be used with the backup.

• Any - With this option selected, any media previously marked for re-use will be considered for use in the backup.

• With same group label as the target. This option is only available if the Group Label item is selected and a valid group is selected in from the pull-down menu. Once selected, any media containing the group label specified, that has been previously marked for re-use will be considered for use in the backup.

Figure A-29 Group Tool

• General Options

This dialog box allows the user to administer and protect media.

• Specify minimum space required on media before backup - With this option selected, the M Bytes option is made available. This field allows for the setting of the minimum amount of space that a piece of media must have available before it is to be used.

Figure A-30 General Options

Crosswalk iGrid

209


• Protect media from further writes after backup - When selected, the target media will be protected, allowing no further backups to be placed on it.

• Ensure this backup is the first on the media - With this item selected, NetVault will ensure that the backup performed is the first to occur on the targeted piece of media.

• Media Request Timeout - When selected, the accompanying fields can be used to set an amount of time that the job will continue to wait for a piece of media before the job returns a status of “failed” in which case the job will be stopped. When a job span multiple pieces of media (i.e., media spanning), a request input in this field applies to all media requests the job may require.

• Target Set

A Target Set allows the user to save often used selections that are made in the Target tab into a composite set that can be retrieved for later use.

Figure A-31 Job Submitted Successfully

Example Event Set Up in the Backup Window

As previously noted, three options available in the Advanced Options tab of the Backup window can be used in order to set an event to occur based on the ending status of a backup job. This section offers an example of the procedure necessary to setup an event to occur for a specific backup job.

Backup job events are set on a per job basis. Once set for a specific backup job, these events will only be raised if their conditions are met while the job they were set for are run. (i.e., if events are desired for each job they must be individually created using the process explained above or previous created events can be used).

Once an event's notification method(s) are properly set up in the Global Notification Profile (and the profile is saved), it is not necessary to return to the Global Notification window while creating further backup jobs, unless a new event/notification method is desired. The event can simply be selected from the pull-down menu for future use (e.g., if a backup job has an event initially created called “Failed” that is configured to send an e-mail as a job fails, it will only be necessary to select the event entitled “Failed” from the pull-down menu in the Advanced Options tab for future jobs).

If using a Sysop E-mail notification method for a backup job event, it is necessary to configure the Notification tab of the NetVault Configurative in order to successfully receive e-mail messages.

New events set in the Advanced Options tab of the Backup window will not appear in the Global Notification window until the backup job they are affiliated with is saved.

Not only Canned Reports are given a Job Identification number. As custom report jobs are created and run, they too, are assigned a Job Identification number which can be used for this process.

Crosswalk iGrid

210


This section offers an example of setting up events to occur when Job fails/ warnings are generated. This example is set up so that an E-mail will be sent to an Administrator if this backup job fails. Also, if the job completes successfully, he would like a report to be run displaying statistics pertaining to the system's media usage. To do so, the following was performed:

1. A backup job was created, with the following taken into consideration:

Do Not Submit the Backup Job Once it has been Created - In order for this process to work properly, the job must be created (and saved, once this process is complete) but not submitted. Certain actions are required in NetVault's Global Notification window before set events will occur.

2. The Advanced Options tab was then accessed.

3. From the Events area in the Advanced Options tab, the Raise Event if Job is Successful item was selected to activate the accompanying field and the value “Run Report” was input in order to create a new event for use.

Figure A-32 Events

Note: After a new event is set in any of these fields it will then be available for future selection (in any of these fields).

The newly created events reveled in the Global Notification window with a desired method of notification selected for each

4. The same procedure was duplicated for the Raise Event if Job Fails item, and the value “Backup Job Failed” was input to create a new event.

5. The backup job was then scheduled to run at a desired point in time (i.e., via the Schedule tab).

6. The job was then saved (but not submitted) in order to incorporate these settings, which in turn, activated the events for set up (i.e., in the Global Notification window). A dialog box is launched confirming the save and offering the Job Identification number of the newly saved backup job.

7. The Backup window was left open and the Global Notification window was then accessed (via the command available from the Administration pull-down menu in the main GUI).

8. With the new events set and the backup job saved, the Global Notification window was updated to reveal a new event class folder entitled, Job - User Defined. The folder was double-clicked to open it and reveal its events.

9. Both items were opened (by double-clicking on them) to reveal the notification methods available for selection, and based on the desired type of notification, the following were selected:

Crosswalk iGrid

211


Figure A-33 Job Saved with Jobid

• Backup Job Failed - This event was set up to represent a failed backup job. For this example it was decided that an e-mail message should be sent when this occurs, so the Sysop E-mail notification method was selected.

• Run Report -This event was set up to run after the successful completion of a backup job. For this example it was decided that a specific report job is to run which can be viewed at a later time via NetVault's Reports window. To accomplish this, the Job ID associated with the specific report job must be provided. To accomplish this the following steps were followed:

Figure A-34 Global Notification Profile

a. The Reports window of NetVault was accessed (via the Reports command available in the Operation pull-down menu from the main GUI) and the canned report Media Utilization was located from the Jobs tab. Each canned report is pre-assigned its own Job ID (as displayed in a column to the right of the report's title).

Figure A-35 Jobs

Crosswalk iGrid

212


b. With the correct Job ID noted, the Reports window was closed and the Global Notification window re-accessed. With the Run a Job notification method selected, it was then right-clicked on the access the pop-up menu and select the About/Extra Variables command.

c. In the Notification Method Description dialog box that appeared, the line “JOBID=13” was input (i.e., “13” being the desired report job's pre-assigned Job ID number).

d. With the proper syntax input in the Setting Variables window, OK was clicked to commit the input and the dialog box was closed.

Figure A-36 Notification Method Information

10. With notification methods properly selected, the Global Notification profile was saved (e.g., via the Save Global Notification Profile button) and the window was closed to return to the Policy Management window.

Returning to the Backup window, the job was then submitted. With this, when (and if) the defined situations occur, the events set for them will be raised sending an e-mail as the job fails and generating the set report as it succeeds. This results of this report can then be viewed in the Status tab of the Reports window.

Figure A-37 NetVault Backup Submitted

Managing the NetVault Database

Prior to working with the various tools offered for this purpose, it is important to have a basic understanding of the breakdown of the NetVault Database (NVDB), including its indexes and how they

Crosswalk iGrid

213


are recorded. Therefore, this section offers some brief descriptions of the NVDB structure in regards to a backup as well as a prioritized list of which tools should be used to maintain the NVDB.

About Index Entries and the NetVault Database

As a backup job is performed, an amount of information, referred to as an index entry is created in the NVDB. This index contains specific information pertaining to the job, which is required by NetVault to later restore this backed up data. In addition to recording this index entry to the NVDB, it is also copied to the actual piece of media which contains the backed up data.

NetVault Database Index Entry Size Limitations

As briefly covered in the preceding section, a single NVDB index entry is generated for each NetVault backup job created/submitted. It is important to note that NetVault must adhere to a maximum size requirement of two Gigabytes (2 GB) for each of these individual index entries. This only applies to very large jobs (i.e., an index entry of this size can result from a backup job that contains a few million files and directories). If a backup job is run that requires an index entry larger than this maximum, it will most likely fail. Therefore it is recommended that large jobs requiring the backup of a few million files be broken down into multiple jobs to avoid this.

Available Tools for Managing the NetVault Database

As new backup jobs are performed, the NVDB will continue to grow in size and occupy more and more valuable hard drive space, requiring some means to control its growth. Multiple tools are offered by NetVault to regulate the overall size this database. Below, a prioritized list of these options is offered, and it is recommended that a backup and restore strategy be developed using these tools in the order given to most easily maintain the NetVault Database.

Phase 1: Setting a Backup Life

Through the use of the Discard After... tools available in the Backup Life area in the Advanced Options tab of this window, an amount of time can be given to a backup job before NetVault will “retire” it. Once the set period of time elapses, the backup job will be retired and the index entry pertaining to the job will be removed from the NVDB, reducing its overall size.

Phase 2: Index Compression

Through tools available in the Selections tab of the Restore window, the index entries referencing completed backup jobs can be manually compressed to reduce their size. Additionally, options are available in the NetVault Configurator that can be set to have Netvault automatically compress these indexes, based on time values input.

While compressing indexes reduces the size of the NVDB and keeps it in check, the process used to decompress these indexes (in order to restore associated backup savesets) may slow down the overall process. That is why this is recommended as a secondary course of action in regulating the size of the NVDB.

Crosswalk iGrid

214


Phase 3: Offline Indexes

If the NVDB is reaching an unmanageable size, even after the previous two tools are put to use, the next possible solution is to utilize NetVault's ability to take an index offline. Through the final tool available in the Backup Life area in the Advanced Options tab, Offline Index After, a variable can be input that will serve as a point of time expressed as days, weeks, or years, that must elapse before the index entry referencing this backup job will be removed from the NVDB. This value is set on a per job basis, prior to initiating a backup.

• Since these same index entries are copied to the actual media during the backup, the necessary point of reference required for the recovery of this backup is still accessible, making this removal from the NVDB feasible.

• When the point in time comes that it is necessary to recover a backup whose index has been taken offline, the actual piece of media must be referenced to load the index back into the NVDB so that the backup saveset can be accessed.

• This is controlled through tools available in the Selections tab of the Restore window.

• If an index is removed from the NetVault Database in this manner, the piece of media containing the duplicate index information must be preserved. If the media containing this index information is lost or corrupted, it will not be possible for NetVault to recover the backup. Therefore it is recommended that all other forms of NVDB size management (e.g., Backup Life and Index Compression) be utilized first.

Example Use of the Offline Index Option

In the following example, the Offline Index After option is used in order to take the index entry for a backup job offline after four (4) days have passed.

1. With the desired data chosen for a backup job from the Selections tab, the Advanced Options tab was selected.

2. In the Backup Life area of this tab, the Offline Index option was located and its check box selected to access its associated fields.

Figure A-38 Offline Index After

3. In the value field, the value “4” was input, and the Days radial button was selected.

4. The job was then submitted and the backup completed.

5. After four days passed (based on the time of day the backup was launched), the index entry for the job was removed from the NetVault Database (i.e., taken “offline”). As a result of this, the overall size of the NVDB was reduced.

6. At a later point in time, when it becomes necessary to restore this particular backup, the index files taken offline would be reloaded via the Selections tab of the Restore window.

Crosswalk iGrid

215

Using BakBone’s® NetVault™ with Crosswalk iGrid Invoke NetVault Client (Agent) on a Node To Be Backed Up

Invoke NetVault Client (Agent) on a Node To Be Backed Up

This section describes how to install the NetVault client agent on a node to be backed up. To install the NetVault client agent, do the following:

1. On the Crosswalk iGrid User Interface page, click Backups.

The Backup page opens.

Figure A-39 Backup

2. Click on the NetVault link.

The NetVault start page opens.

Note: There might be a short delay before the NetVault start page opens. During the delay, several small windows flash open on your monitor and immediately disappear. These windows are normal and expected.

Crosswalk iGrid

216

Invoke NetVault Client (Agent) on a Node To Be Backed Up Using BakBone’s® NetVault™ with Crosswalk iGrid

Figure A-40 NetVault Start Screen

Crosswalk iGrid

217

Using BakBone’s® NetVault™ with Crosswalk iGrid Installation of NetVault Backup Client Agent

Installation of NetVault Backup Client Agent

This section describes the NetVault install client agent procedure for the Linux OS. If you need backups for computers running other operating systems, please refer to the NetVault Administrator’s Guide and the Bakbone, Inc. Web site at http://www.bakbone.com/.

Storage requirements

This section describes storage requirements.

1. Acquire the NetVault distribution tar file called: netvault-R2004NOV05-73-Linux.tar.gz

2. run tar -xzf netvault-R2004NOV05-73-Linux.tar.gz

• This will uncompress and untar the file into a directory called netvault under your current directorycd netvaultrun ./install

• The following is output from the install script, with the appropriate answers in bold../installInstaller invoked in /var/tmp/netvaultUsing default /tmp as the temporary directoryExpanding distribution file

NetVaultCopyright (c) BakBone Software Inc. 2000-2003

Have you read and agreed to the terms of the license?

(y = yes, n = no, d = display license) (y n d) [d] : y

Should a client or server version of NetVault be installed? (c s) [c] : c

Where should NetVault be installed? /usr/netvault

Where should NetVault database be installed? /usr/netvault/db

Please enter a NetVault machine name

using A-Z, a-z, _ and 0-9 “hostname” (input the hostname here)

this is echoed from the install script.

Please enter the NetVault password for this machine: xxxxxx (root password)

Please enter the NetVault password for this machine: xxxxxx (root password)

Please confirm password: checkinstall running

CHOSEN_CLASSES=core server dataplugin devicectl gui onlinehelp

PKG_BASE=/usr

Crosswalk iGrid

218

Installation of NetVault Backup Client Agent Using BakBone’s® NetVault™ with Crosswalk iGrid

preinstall running

Installing core

Installing server

Installing dataplugin

Installing devicectl

Installing gui

Installing onlinehelp

postinstall running

HOST_OS=Linux

NV_UPGRADE=

Creating database directory /usr/netvault/db

Installing libraries

libnv6audit.so

libnv6cli.so

libnv6db.so

libnv6gui.so

libnv6jobs.so

libnv6ndmp.so

libnv6plugin.so

libnv6reports.so

libnv6scsi.so

libnv6.so

libnv6stats.so

libnv6xctl.so

libnv6xpm.so

Creating symbolic links

Setting reports/stats paths

License installed: 'TRUE'

Installing base npk's

Crosswalk iGrid

219

Using BakBone’s® NetVault™ with Crosswalk iGrid Installation of NetVault Backup Client Agent

Successfully installed '/mnt/nvdata/n1b/packages/nty1110.npk'

Successfully installed '/mnt/nvdata/n1b/packages/rpt1210.npk'

Checking for components in /mnt/nvdata/n1b/packages

Installing additional npk's

Successfully installed '/mnt/nvdata/n1b/packages/hlp1000.npk'

Successfully installed '/mnt/nvdata/n1b/packages/raw2110.npk'

Successfully installed '/mnt/nvdata/n1b/packages/dvy4900.npk'

Successfully installed '/mnt/nvdata/n1b/packages/ver1110.npk'

Successfully installed '/mnt/nvdata/n1b/packages/dvx4900.npk'

Successfully installed '/mnt/nvdata/n1b/packages/dvz4900.npk'

Successfully installed '/mnt/nvdata/n1b/packages/ddv2210.npk'

Successfully installed '/mnt/nvdata/n1b/packages/dup1110.npk'

Successfully installed '/mnt/nvdata/n1b/packages/nvf5a10.npk'

Checking for components in /mnt/nvdata/n1b/serverpackages

Installing server npk's

Successfully installed '/mnt/nvdata/n1b/serverpackages/nvd4110.npk'

Successfully installed '/mnt/nvdata/n1b/serverpackages/con3310.npk'

Successfully installed '/mnt/nvdata/n1b/serverpackages/cpy2310.npk'

Checking for extra components in /mnt/nvdata/n1b/extrapackages

Copying non-installable additional npk's

Setting NetVault machine password

Not an upgrade - installing NetVault Services

Will link to '/usr/etc/startup.sh'

Starting NetVault Services

Copying uninstallation scripts

Installation completed successfully

verify by ps -aux |grep nv

Crosswalk iGrid

220

NetVault Failover Using BakBone’s® NetVault™ with Crosswalk iGrid

NetVault Failover

This section describes the reasons and sequence for NetVault to perform a failover. NetVault is configured in the cluster as an active/passive application. The instance will initially be running on node one, and the second node will be in standby in case of a failure of the first node. The cluster service will automatically fail the Netvault services (daemons) over to the second node if a failure occurs. The following are some possible causes for a node failure:

Loss of heartbeat, which can be caused by:

• Loss of primary power on a single node

• Software failures

Although node failures are extremely rare, in the case that a node fails

1. Node 1 will initially fail to node 2.

2. The following failure methodology will be in play for all future failure scenarios. The service will perform a round-robin failover for all subsequent failovers.

• Node 1 --' Node 2 (1st failure)

• Node 2 --' Node 1 (2nd failure) after repair of Node 1

• Node 1 --' Node 2 (3rd failure) after repair of Node 2

The Netvault management interface will be available through the Crosswalk iGrid UI on the second node -by connecting the UI client to the second node.

Crosswalk iGrid

221

Using BakBone’s® NetVault™ with Crosswalk iGrid Restoring with Crosswalk iGrid

Restoring with Crosswalk iGrid

This chapter describes how to use the NetVault restore function.

Restore Window Buttons

The Restore window buttons allow for access to the following options:

Figure A-41 Restore buttons

Crosswalk iGrid

222

Server Selection Using BakBone’s® NetVault™ with Crosswalk iGrid

Table A-3 Restore Buttons and Results

Server Selection

The Server Selection text box allows for the selection of the NetVault server desired to control the current process. The drop-down list shows all controlling NetVault servers for each NetVault domain that have been added via the NetVault Domain Management window.

Job Title

This text box allows the user to type a descriptive title for the restore job. When a new job starts, the default title is No Title. When the job is saved, the job title is saved. This allows for recognizing the job in the logs or when loading a previously run job. Any value can be input in this text box. If a descriptive title is not entered, the job is saved and run as No Title.

Crosswalk iGrid

223

Using BakBone’s® NetVault™ with Crosswalk iGrid Restore Window

Restore Window

The NetVault Restore window is broken down into five tabbed sections that allow for various settings in regards to a restore. They are broken down as follows and are covered in complete detail in this section.

• Selections

• Restore Options

• Target Client

• Schedule

• Advanced Options

Selections

The default tab selection in the Restore window, this tab is used to select data for a restore. Previously backed up data is stored in Backup Savesets. These Savesets are marked in the Selections window by a small grey cylinder. Each Saveset is titled with specific information pertaining to it (e.g., The Job Title assigned to the backup, the Saveset Number assigned by NetVault as well as the time and date the backup was performed). As well, other option areas are accessible.


a. Selection Method

b. Filter Options

c. Selection window

d. The Restore Selection Set Area

Crosswalk iGrid

224

Restore Window Using BakBone’s® NetVault™ with Crosswalk iGrid

Selection Methods

The Selection Method pull-down menu allows for the changing of the display in the Restore Selections window and provides the following options:

Figure A-43 Selection Methods

• Plugin (default) – When selected, the Restore Selection list appears in plugin, or APM, sequence.

• Backup Set – When selected, the Restore Selection list appears in Backup Set sequence.

• Job – When selected, the Restore Selection list appears in Job sequence.

Filter Options

Filter options can be set to customize how data appears in the Restore Selections window. If no filter options are selected, all backed-up data appear in the Restore Selections window according to the Selection Methods settings.

Figure A-44 File Options

The following options are available:

• By Date Range – Check By Date Range to activate this filter. Only backup savesets generated within the date range are shown. The default setting is the current date plus the last two days. To change dates, type new dates in the From and To text boxes.

• Show On-line Status – When the Show On-line Status box is checked, only currently on-line media appear.

• Click on Apply Filter.

• Items in the Restore Selections window sort according to the selected filter options.

Selection Window

Upon first accessing the Selection window, added NetVault servers that have completed successful backup appear. If no successful backups have occurred, no NetVault servers appear in this window.

Crosswalk iGrid

225


These servers can be opened to reveal the various NetVault plugins and APMs that have completed these backups. Contained within these are the individual backup savesets in which the individual data items, selectable for a restore, are located.

Figure A-45 Selection Levels

Note: Depending on the APM or Plugin that data is being restored from, it may be possible to open further down in order to select other data items for a restore.

Selecting Data for a Restore

This section describes how to select data to restore. The methods detailed in this section for selecting data for a restore is the same regardless of the plugin or APM. However, some restrictions apply to the types of selections that are possible, based on the APM or plugin. It is possible to select items from a single backup saveset per NetVault restore. If restores of other backup savesets are necessary, they must be done separately.

1. With the Restore window open and the Selections tab active, double-click on the desired NetVault Server to open it (or right-click and select Open from the pop-up menu).

2. A list of plugins (or APMs) that have been used to complete a backup appear. Double-click on the desired plugin to open it (right-click and select Open).

3. The Backup Savesets generated with the selected Plugin or APM appears. In order to access the data contained within, double-click on the desired saveset.

Figure A-46 Backup Savesets

Note: At this level of the tree, it is no longer possible to right-click on an item to reveal a pop-up menu (no Open command is accessible). Therefore, it is only possible to open items by double-clicking on them.

• With the Backup Saveset open, root data items included in the backup appears. It is possible to select a root item (or all of them), or open the item to reveal its individual content.

Crosswalk iGrid

226


• When selected, an item will contain a green check, marking it as selected. To open a root item simply double-click on it. With the root item selected and open, all items contained within will also be selected (marked by a smaller green check). If the root item is not selected and opened the items contained within will still be revealed, but can then be individually selected as desired.

• With the root item selected and open, it is possible to omit items contained within. Simply click in the box to the left of a desired sub-item to mark it as omitted. Omitted items are marked with a red cross and the root item will then be marked with a grey box containing a large green check.

Figure A-47 Selected Root Items

• The following examples show various forms of selection:

Figure A-48 Example Restore Selections

Search Facility

The Search Facility allows for searching from various levels of the Restore Selections window for specific items saved in the previous backup. The example shown here uses the File System Plugin for the Search command.

Figure A-49 Files System Plugin

Crosswalk iGrid

227


The command works the same for all plugins and APMs. To use this facility, do the following:

1. Right-click on a specific level of the Restore Selections window, such as the plugin level in the example above.

2. Select Search from the popup menu.

3. The Restore Search dialog box appears.

4. To find a specific item contained in a previous backup, type a search term in the Search String text box.

The following wildcards can be used in the Search String field:

• A question mark represents a single alphanumeric character in the wildcard position in the search string.

• An asterisk represents one or more alphanumeric characters in the wildcard position in the search string.

Figure A-50 Restore Search

5. Choose a search method.

• Regular expressions are shorthand terms for abbreviating patterns of text. To perform a search using regular expressions, check the Regular Expression Search box.

• When the Case Sensitive box is checked, the search will search for items based on the case typed in the Case Sensitive box.

6. Click Search.

• The search results appear in the Restore Selections window.

• The window opens to the directory level that shows the items meeting the search parameters.

Crosswalk iGrid

228


Figure A-51 Search Results

7. Select one or more items to restore.

Media Tool List

Any backup saveset in the Selections tab of the Restore window can be right-clicked on to access the Media List command offered in the popup menu. This command will launch a window that contains detailed information about all media used for the selected backup job. The window is broken down into at least two entries, one of which details the actual backed up data while the other offers details about the media location of the NetVault Database index. If multiple pieces of media were used for a selected job, all of them appear in this window as well.

• The window contains the following information:

• Backup is X Bytes - The Overall Size of the Backup

• Media Containing Data - the name of the piece of media housing the backup

• From/To - These fields show the starting byte number (From) and the ending byte number (To) for the backed up data.

• New - This field gives a Yes or No answer which indicates the new or old status of the backup.

• Online - This field gives a Yes or No answer which indicates the online or offline status of the media required for this job. If a piece of media that is required for the selected backup job is not available – that is, it is not currently present in a device accessible to the NetVault Server – it is marked as offline and must be made accessible to perform a restore or browse the backup saveset. The Online field is the only information given in reference to a NetVault index entry for a selected backup.

• In the case of a duplicated backup (set up via the Duplicate option in the Advanced Options tab of the Backup window), all media containing the various parts of the backup appears in this window.

Compressed and Offline Indexes in the Selections Tab

This section provides a brief description of how index manipulation can affect how items appear in the Selections tab of the Restore window.

The NetVault Database (NVDB) exists on the machine acting as the NetVault Server and is used to maintain all forms of information pertaining to that installation of NetVault. All of this information is

Crosswalk iGrid

229


housed in individual files referred to as Indexes. The most abundant form of index contained in the NVDB pertain to completed jobs (e.g., backup jobs).

As increasing amounts of backup jobs are performed, larger amounts of index entries are recorded in the NVDB, increasing its overall size and consuming valuable hard drive space. To address the need to regulate the size of the NVDB, NetVault has made tools available:

• Compression/Decompression - Index entries related to completed backup jobs can be compressed and decompressed through commands offered in the Selections tab of the Restore window.

• Offline Indexes - Index entries can be removed – taken offline – from the NVDB after a predetermined period of time. These options are offered at the time of backup via the Backup window.

As indexes are compressed or taken offline, their backup savesets, revealed in the Selections tab of the Restore window are marked accordingly. The following table shows how backup icons reflect the various available forms of index manipulation:

Table A-4 Backup Icons for Index Manipulation

Restore Selection Set

Restore Selection Set allows a user to save often-used selections that are made with the Selections tab into a composite Selection Set that can be retrieved for later use.

Figure A-52 Restore Selection Set

Restore Options

Restore Options shows various options about a restore, based on the plugin or APM being used. This tab is accessible only to plugins and APMs that offer Restore Options. Regardless of APM or plugin in use,

Crosswalk iGrid

230


if Restore Options are offered, the Restore Options tab is not accessible unless items are first selected for a restore in the Selections tab.

Figure A-53 Restore Options

Target Client

The Target Client tab is used to specify the NetVault client the data is being restored to.Only clients that have been added via the Client Management window appears in this window for selection.

WARNING — Use this option with caution. If a client is not configured properly, the restore might fail.

It is possible to target any client in the NetVault domain of the selected NetVault server. The uppermost client revealed will always be the NetVault server acting as a NetVault client.

When no clients are selected, all restores are targeted to the client that the data selected in the Selections tab was originally backed up from.

Figure A-54 Target Client

Crosswalk iGrid

231


To target a specific clients, check the box next to the client name. Selecting a client deactivates all other clients and makes them unavailable for selection. A selected client must be deselected before another client can be selected.

Schedule

Schedule is used to set the time that a job is to be run. Jobs can be scheduled to run immediately, at a later date or time, or when triggered by a command line or script command. Options are also available to set a job to run once or repeat.

Figure A-55 Schedule

Schedule Set

The Schedule Set allows the user to save often-used selections that are made in the Selections tab into a composite Selection Set that can be retrieved for later use.

The Advanced Options Tab

The Advanced Options tab provides options used for functions including Compression and the use of pre- and post-scripts, and is shown in the example below.

Crosswalk iGrid

232


Figure A-56 Advanced Options

a. Compression

b. Pre and Post Scripts

c. Advanced Options Set

Compression

Network Compression can be enabled here in order to reduce bandwidth on a network when files are being transferred from one client to another that has an attached device. When the option in this frame is selected, Network Compression (during a Backup) occurs. Backup Saveset data is pulled from the media in the device attached to the Client housing it and then compressed on that Client. This data then traverse the network until they reach the Target Client for restore where the data are then decompressed.

Figure A-57 Network Compression

Pre- and Post-Scripts

It is possible to run a pre-designed script file (generated outside of NetVault) either before or after a restore job.

• Scripts must be an executable file for the operating system being used. For example, when using Microsoft Windows 2000, use script files of type filename.exe, filename.bat, and filename.com.

• All scripts must be located in the.../netvault/scripts directory. If this directory does not exist, it must be created and all scripts must be stored there.

• In either Script field, do not input the exact path to the script, unless the scripts are located in a manually created directory residing in the.../netvault/scripts directory. For example, to organize scripts in this directory, a user has to create his own directory.

• In either Script field, the entire script name including the extension must be input. Wildcards are not supported.

Crosswalk iGrid

233

Using BakBone’s® NetVault™ with Crosswalk iGrid Performing A Restore

• In either User Parameter field, whatever is input is passed to the script itself via an Environmental Variable known as NV_USER_ARG. The value input can only be to the maximum length allowed by the current Operating System. Quotation marks and escape characters are not supported.

• Pre Script - This script runs before a NetVault job. For example, a script could be written that executes a command to disable virus protection software to ensure that no conflicts with the software will occur during the restore).

• Post Script -This script runs after the NetVault job completes. Fore example a script could be written that executes a command to start a process. This script can be used as a post script in order to re-start any processes that may have been closed down by a pre scrip. The following options are available for running pre- and post-scripts.

Use Pre Script

Select the check box to the left of this item to activate the fields below.

• Use Pre Script - Input the exact script name (including the extension) to be used as the Pre Script in this field.

• User Parameter - If the pre script refers to a specific item, input it in this field (e.g., the Pre Script issues a command to shut down a database, name the database to be shut down in this field).

Use Post Script

Select the check box to the left of this item to activate the fields below.

• Use Post Script - Input the exact script name (including the extension) to be used as the Post Script in this field.

• User Parameter - If the post script refers to a specific item, input it in this field (e.g., the Post Script issues a command to re-activate a database, name the database in this field).

NetVault Environmental Variables

Environmental variables pertain to certain NetVault specifics and offer a form of shortcut for the input of these specifics into a script.

Advanced Options Set

The Advanced Options Set allows the user to save often used selections that are made in the Advanced Options tab into a composite Selection Set that can be retrieved for later use.

Performing A Restore

The following section details a simple restore procedure. A backup was performed using the File System Plugin on a Windows 2000 machine. This example shows how to restore this backup.

1. From the NetVault Server, launch NetVault.

Crosswalk iGrid

234

Performing A Restore Using BakBone’s® NetVault™ with Crosswalk iGrid

2. Click on the Restore button in the main GUI (or select Restore from the Operations pull-down menu).

3. Under the Selections tab in the Restore window, locate the desired client that the original backup was performed from, and double-click on it to open it (or right-click and select Open from the pop-up menu).

4. A list of plugins that were used to complete successful backups appears. Double-click on the desired plugin in order to open it (the File System plugin was selected in the example at right) As above, it is also possible to right-click on the Plugin and select Open from the pop-up menu to accomplish this.


The Backup Savesets created with this Plugin appears.

5. Double-click on the desired saveset to open it.

• Items available for selection and inclusion in a restore appear.

• This root item can be selected or opened further (by double clicking on it) to reveal its contents (in this example, the root item was opened in order to view its contents and select them individually).

6. Select the desired item(s) to include in the restore by clicking the box to the left of it (for this example the Plugin Index directory was selected). Note that some items can be further opened to reveal additional items available for selection and omission.

7. The Restore Options tab contains several possible settings to be used in conjunction with items selected in the Selections window. As well, these options vary based on the Plugin or APM used to conduct the Backup. For the sake of this example, they are left at default.

8. Select the Target Client tab. This job is to be restored to its original location (where it was originally backed up from). Therefore, ensure that no other NetVault Clients are selected (all clients represented in this window should be de-selected).

Crosswalk iGrid

235


Figure A-59 Target Clients

9. Select the Schedule tab. This job is to be performed as soon as possible, so the Immediate item is selected.

Figure A-60 Schedule

For this example, a Post Script generated in order to alert the user that the restore has completed is used with this restore. From the Advanced Options tab, click the check box to the left of Use Post Script and input the script name (completion.bat).

Figure A-61 Use Post Script

10. Type a descriptive title for the job in the Job Title text box.

Figure A-62 Restore Job Title

11. Begin the job by clicking on the Submit button.

With the Job submitted, NetVault will assign a job number to the backup. This number will vary based on the succession of jobs.

• The job input will now run.

• To check the status of the job, access the Status button from the main GUI (or select Status from the Operations pull-down menu on the main GUI) and reference the job title and the job number.

Crosswalk iGrid

236


Figure A-63 Successful Job Run

Renaming and Relocating Data During a Restore

Various NetVault plugins and APMs allow a user to rename and relocate data items during a restore.However, not every NetVault plugin and APM provides data renaming and relocating functionality. Access to the renaming and relocating functionality varies with each NetVault core plugin and APM.

Figure A-64 Restore Rename to

Data items can be right-clicked on the Selections tab in the Restore window in order to access the Rename command. After the Restore Rename dialog box is selected, it starts to allow a user to type a new name and relocation destination for the selected data item. The data item is marked with its new name and destination in the Selections tab. The selected item is renamed and relocated during the restore process.

NetVault Database Management and Restore

NetVault allows the manipulation of index entries that refer to backup saveset information it order to manage the overall size of the NetVault database (NVDB). Both complete and partial use of some of these options is controlled in the Selections tab of the Restore window. This section provides a brief overview of them as well as complete details on the use of these forms of index manipulation.

Crosswalk iGrid

237


Compressing and Decompressing Index Entries

Tools have been made available in the Selections tab that make it possible for a user to manually compress and decompress NetVault database index entries.

• Backup savesets whose indexes are compressed do not need to have them manually decompressed in order to include them in a restore job. When a backup saveset of this type is accessed for a restore, index entries are automatically decompressed by NetVault to a temporary location in order to access necessary information. Launched in this manner, restore jobs may be delayed as the indexes are extracted.

• The previous note also applies to the browsing of backup savesets containing compressed indexes.

• If using the Search command on a backup saveset containing compressed indexes, NetVault will need to decompress each index individually when looking for a specified item, so a delay may occur when searching.

• The temporary directory to which indexes are decompressed is deleted after the operation that required the information has completed and the original NVDB index will remain compressed.

• As noted previously, decompressing an index for any purpose (e.g., browsing a saveset, for a restore or to search) may take a short amount of time and delay the desired operation. Therefore it is recommended that index compression only be used on backup savesets that are not regularly used.

• In addition to the manual compression control offered in the Restore window, options are available in the NetVault Configurator for the set up of automatic compression of these indexes.Decompression of indexes that are automatically compressed via these options is still accomplished in the Restore window.

Compressing an Index

1. From the Restore window, with the Selections tab active, open the desired NetVault Client by double-clicking on it.

2. A list of Plugins and APMs that have been used to perform successful backups appears. Locate the desired one and double-click on it to reveal the list of backup savesets generated.

3. Right-click on the desired backup saveset and select Compress from the pop-up menu that appears.

4. The index entries pertaining to this specific backup saveset will be compressed in the NVDB, reducing its overall size, and its backup saveset icon is marked with an amber light icon in the Selections tab.

Figure A-65 Compressing and Index

Crosswalk iGrid

238


Decompressing an Index

To decompress the index entries contained in a backup saveset, perform the steps below. After these index entries have been successfully decompressed, it is possible to open a backup saveset to view its contents or perform a restore of the data contained within.



3. Compressed backup savesets is marked with an amber light icon. Locate the desired backup saveset marked in this manner, and right-click on it.

4. From the pop-up menu that appears, select the Uncompress command. The backup saveset’s corresponding index entry is decompressed. Its icon returns the standard format).

Offline Indexes in the Selection Window

As backups are performed, the index entry that is created in the NetVault Database (NVDB) that corresponds to this job is also copied to the piece of media which actually contains the backed up data. This allows for the use of NetVault’s Offline Indexing tool. The Offline Indexing tool makes it possible to remove an index entry from the NVDB, after a pre-determined amount of time has elapsed, because it can be recovered from the actual media.

To enable this functionality, the user must set it up prior to a backup via the Advanced Options tab of the Backup window After an index has been taken offline, the Restore window is used to bring it back for the purpose of restoring the data or to browse its backup saveset. To recover an offline index, perform the following steps:

5. Ensure that the piece of media used to perform the backup is in a library or drive that is accessible to the NetVault Server (preferably the device used for the original backup).



8. Any backup saveset whose index is currently offline is marked with a red cross. Right-click on a saveset of this type and select Load Index from the pop-up menu (or simply double-click on the backup saveset).

9. A window opens to show the Days to Keep Index dialog box. Type the number of days that the index is to exist in the NetVault Database for the selected backup saveset. After this time period has elapsed, the index is removed – taken offline – again from the NVDB.

Crosswalk iGrid

239


Figure A-66 Days to Keep Index

10. To continue, click OK.

The red cross is removed from the backup saveset’s icon. The backup saveset can now be successfully browsed or included in a restore.

Crosswalk iGrid

240

– APPENDIX B –– APPENDIX B –

Glossary

This Glossary contains terms and definitions as they apply to and are used in the Crosswalk iGrid User’s Guide and GUI. Some of the terms and definitions might vary slightly from the way they are stated elsewhere. The Glossary Bibliography at the end of this Glossary identifies the sources the standard definitions were derived from.

Aaccess

The ability and means necessary to store data in, to retrieve data from, to transfer data into, to communicate with, or to make use of any resource of a storage product, a system, or area such as random access memory (RAM) or a register.

adapter

A printed circuit assembly which transmits user data (I/Os) between the host system’s internal bus and the external Fibre Channel link and vice versa. Also called an I/O adapter, host adapter, or FC adapter.

address

1. To refer to a product or an item of data by its address.

2. The location in a computer where data is stored.

3. In data communication, the unique code assigned to each product or computer connected to a network.

4. The identifier of a location, source, or destination.

address name

Synonym for port name.

agent

Software that processes queries on behalf of an application and returns replies.


241

Glossary

alarm

1. A notification of an abnormal condition within a system that provides an indication of the location or nature of the abnormality to either a local or remote alarm indicator.

2. A simple network management protocol (SNMP) message notifying an operator of a network or product problem.

alias

A nickname representing a world-wide name (WWN).

American National Standard Code for Information Interchange

ASCII. A standard character set consisting of 7-bit coded characters (8-bit including parity check) used for information exchange between systems and equipment (D).

American National Standards Institute

ANSI. A national organization consisting of producers, consumers, and general interest groups that establishes procedures by which accredited organizations create and maintain industry standards in the United States (A).

ANSI

See American National Standards Institute.

API

See application program interface.

application

1. The use to which a data processing system is put, for example, a payroll application, an airline reservation application, or a network application.

2. A collection of software components used to perform specific types of work on a computer (D).

application client

The source object of the small computer system interface (SCSI) commands and destination for the command responses.

application program

1. A program that is specific to the solution of an application problem. Synonymous with application software.

2. A program written for or by a user that applies to the user’s work, such as a program that does inventory control or payroll.

3. A program used to connect and communicate with stations in a network, enabling users to perform application-oriented activities (I).

DRAFT - Confidential and Proprietary — For internal use onlyDo not disclose or distribute without the express written consent of Crosswalk, Inc.242

Glossary

application program interface

API. A set of programming functions and routines that provides access between protocol layers, such as between an application and network services.

application-specific integrated circuit

ASIC. An asynchronous transfer mode (ATM) local area network/ wide area network (LAN/WAN) circuit using cell relay transport technology. ASICs are designed for a specific application or purpose, such as implementing the lower-layer Fibre Channel protocol (FC-0). They are particularly suited to sending video and audio information, as well as text. ASICs differ from general-purpose products such as memory chips or microprocessors.

arbitration

Process of selecting one product from a collection of products that request service simultaneously.

archive

1. To copy files to a long-term storage medium for backup.

2. Removing data, usually old or inactive files, from a system and permanently storing the data on removable media to reclaim system hard disk space.

area

The second byte of the node port (N_Port) identifier.

array

Two or more disk drives connected to a host, and connected and configured such that the host perceives the disk drives to be one disk.

ASCII

See American National Standard Code for Information Interchange.

ASIC

See application-specific integrated circuit.

attribute

In FICON management style, the connection status of the address on a configuration matrix: allowed, blocked, or prohibited.

Audit Log

Log summarizing actions (audit trail) made by the user.

Director or switch Audit Log. Log displayed through the Element Manager application that provides a history of all configuration changes made to an individual director or switch from the respective Element Manager application, a simple network management protocol (SNMP) management workstation, a


243

Glossary

FICON or open systems host, or the maintenance port. This information is useful for administrators and users.

availability

The accessibility of a computer system or network resource.

Bb

See bit.

B

See byte.

backup

To copy files to a second medium (disk or tape) as a precaution in case the first medium fails.

backup field-replaceable unit

Backup FRU. When an active FRU fails, an identical backup FRU takes over operation automatically (failover) to maintain director or switch and Fibre Channel link operation.

backup FRU

See backup field-replaceable unit.

bandwidth

1. The amount of data that can be sent over a given circuit.

2. A measure of how fast a network can move information, usually measured in Hertz (Hz).

baud

The unit of signaling speed, expressed as the maximum number of times per second the signal can change the state of the transmission line or other medium. The units of baud are seconds to the negative 1 power. Note: With Fibre Channel scheme, a signal event represents a single transmission bit.

BB_Credit

See buffer-to-buffer credit.

beaconing

Use of light-emitting diodes (LEDs) on ports, port cards, field-replaceable units (FRUs), and directors to aid in the fault-isolation process. When enabled, active beaconing will cause LEDs to flash in order for the user to locate field-replaceable units (FRUs), switches, or directors in cabinets or computer rooms.


Glossary

ber

See bit error rate.

bidirectional

In Fibre Channel protocol, the capability to simultaneously communicate at maximum speeds in both directions over a link.

bit

Abbreviated as b.

1. Binary digit, the smallest unit of data in computing, with a value of zero or one (D).

2. A bit is the basic data unit of all digital computers. It is usually part of a data byte or data word; however, a single bit can be used to control or read logic ON/OFF functions.

3. A bit is a single digit in a binary number. Bits are the basic unit of information capacity on a computer storage product. Eight bits equals one byte.

bit error rate

Abbreviated as ber. Ratio of received bits that contain errors to total of all bits transmitted.

blocked connection

In FICON management style, in a director or switch, the attribute that, when set, removes the communication capability of a specific port. A blocked address is disabled so that no other address can be connected to it. A blocked attribute supersedes a dedicated or prohibited attribute on the same address. Contrast with; unblocked connection. See connectivity attribute. See also dynamic connection; dynamic connectivity.

blocked port

In a director or switch, the attribute that when set, removes the communication capability of a specific port. A blocked port continuously transmits the offline sequence.

boot

1. To start or restart a computer.

2. Loading the operating system.

B_Port

See bridge port.

bps

Bits per second.


245

Glossary

Bps

Bytes per second.

bridge

1. An attaching product that connects two local area network (LAN) segments to allow the transfer of information from one LAN segment to the other. A bridge can connect the LAN segments directly by network adapters and software in a single product, or can connect network adapters in two products through software and use of a telecommunication link between the two adapters (D).

2. A functional unit that connects two LANs that use the same logical link control protocol, but may use different media access control protocols (T). Contrast with router.

3. A product that connects and passes packets between two network segments that use the same communications protocol.

bridge group

A bridge and the collection of products connected to it.

bridge port

B_Port.

1. In Fibre Channel protocol, a fabric inter-element port used to connect bridge products with E_Ports on a switch. B_Ports provide a subset of E_Port functionality.

2. Physical interface between the fabric (switch) and a bridge product. The interface is identical to an expansion port (E_Port), but it does not participate in full expansion port protocols. As such, it does not assign domain IDs or participate in routing protocol. See also expansion port; fabric loop port; fabric port; generic port; hub port; node loop port; node port; segmented expansion port.

broadcast

A method of sending an SNMP request for information to all the products on a subnet that uses a single special request. Because of its efficiency, the SANavigator application sets its default method of discovery to broadcast. However, a network administrator may disable this method on the network router.

buffer

Storage area for data in transit. Buffers compensate for differences in processing speeds between products.


Glossary

buffer-to-buffer credit

BB_Credit.

1. The maximum number of receive buffers allocated to a transmitting node port (N_Port) or fabric port (F_Port). Credit represents the maximum number of outstanding frames that can be transmitted by that N_Port or F_Port without causing a buffer overrun condition at the receiver.

2. The maximum number of frames a port can transmit without receiving a receive ready signal from the receiving product. BB_Credit can be adjustable to provide different levels of compensation.

bus

The path that carries data between the computer (microprocessor) and peripheral products. An IDE interface cable and a small computer system interface (SCSI) cable are both examples.

bypassed port

If a port is bypassed, all serial channel signals route past the port. A product attached to the port cannot communicate with other products in the loop.

byte

Abbreviated as B. A byte generally equals eight bits, although a byte can equal from four to ten bits.

Ccache

Random access memory (RAM) that is used by the redundant array of independent disks (RAID) controller to increase I/O throughput. If write-back caching is enabled, this RAM can contain data that is not yet written to the disks in the array. In normal circumstances, this data is flushed from the RAM to the disk drives in the array with a maximum latency of 64 ms. If power fails to the subsystem (preventing the data from being written to the disk drives in the array), the battery holds the data for approximately 72 hours. If power is restored within that period, the data is flushed into the array and operation continues normally. If power has not been restored within 72 hours the data is lost.

cache memory

A memory subsystem that stores recently used instructions and data for fast access. The larger the cache, the more information that can be stored, and the fewer time-consuming memory accesses a central processing unit (CPU) must make to complete a task. Cache is very fast memory, typically static random access memory (SRAM.

capacity

The amount of information, measured in bytes, that can be stored on a hard drive.


247

Glossary

cascade

Linking two or more Fibre Channel switches to form a larger switch or fabric. The switched link through fiber cables attached between one or more expansion ports (E)_Ports). See also expansion port.

cell

In FICON management style, in a port address matrix, a cell is the intersection point between a horizontal port address and a vertical port address. A selected cell is indicated by the cell cursor.

central memory module card

CMM. In the ED-5000 Director, a circuit card that provides the storage area for Fibre Channel ports to deposit and retrieve Fibre Channel frames. Each port is allocated a portion of this memory divided into a fixed number of frame buffers.

central processing unit

CPU. The heart of the computer, this is the component that actually executes instructions.

chained

Two directors or switches that are physically attached.

channel wrap test

A diagnostic procedure that checks S/390 host-to-director or host-to-switch connectivity by returning the output of the host as input. The test is host-initiated and transmits Fibre Channel frames to a director or switch port. A director or switch port enabled for channel wrapping echoes the frame back to the host.

Class 2 Fibre Channel service

Provides a connectionless (not dedicated) service with notification of delivery or nondelivery between two node ports (N_Ports).

Class 3 Fibre Channel service

Provides a connectionless (not dedicated) service without notification of delivery or nondelivery between two node ports (N_Ports). Synonymous with datagram.

Class F Fibre Channel service

Used by switches to communicate across interswitch links (ISLs) to configure, control, and coordinate a multi-switch fabric.

Class of Fibre Channel service

Defines the level of connection dedication, acknowledgment, and other characteristics of a connection.

client

A node that requests network services from a server. Typically the node is a personal computer (PC).


Glossary

client/server computing

Architectural model that functionally divides that execution of a unit of work between activities initiated by an end user or program (client) and those maintaining data (servers. Originally thought to make mainframes obsolete.

cluster

A group of processors interconnected by a high-speed network (typically dedicated) for increased reliability and scalability. Clusters are groupings of multiple servers in which information is shared among systems. When a server in a cluster fails, one of the other servers in the cluster assumes the responsibility of the failed server, thereby ensuring server, application, and data availability.

CMM

See central memory module card.

command

1. A character string from an external source to a system that represents a request for system action.

2. A request from a terminal to perform an operation or execute a program.

3. A value sent through an I/O interface from a channel to a control unit that specifies the operation to be performed (D). A selection on a dialog box or elsewhere in the user interface that causes the SANavigator application to perform a task.

community name (SNMP)

A name that represents an simple network management protocol (SNMP) community that the agent software recognizes as a valid source for SNMP requests. A product recognizes a management station as a valid recipient for trap information when the station’s community names are configured.

community profile

Information that specifies which management objects are available to what management domain or simple network management protocol (SNMP) community name.

community (SNMP)

A relationship between a simple network management protocol (SNMP) agent and a set of SNMP managers that defines authentication, access control, and proxy characteristics.

community strings

The community name that is contained in each SNMP message. It is not secure and there is no way to keep the contents private or to determine if a message has been changed or replayed. The community string value is not encrypted.

component

1. Hardware or software that is part of a functional unit.


249

Glossary

2. A functional part of an operating system; for example, the scheduler or supervisor (D).

computer

A programmable machine that responds to a specific set of instructions in a well-defined manner and executes a prerecorded list of instructions (a program). Computers are both electronic and digital and are made up of both hardware (the actual machine-wires, transistors, and circuits) and software (instructions and data).

concurrent firmware upgrade

Firmware is upgraded without disrupting switch operation.

configuration data

The collection of data that results from configuring product and system operating parameters. For example, configuring operating parameters, SNMP agent, and port configurations through the Element Manager application, results in a collection of configuration data. Configuration data includes: identification data, port configuration data, operating parameters, and SNMP configuration.

connectivity

The ability of products to link together.

connectivity attribute

In FICON management style, the characteristic that determines port address status for the director or switch. See; blocked connection; connectivity control; dynamic connection; dynamic connectivity; unblocked connection.

connectivity capability

The capability that allows attachment of a product to a system without requiring physical reconfiguration of either the product or the interconnections. (D).

connectivity control

In FICON management style, in a director or switch, the method used to change port address connectivity attributes and determine the communication capability of the link attached to the port (D). See also; connectivity attribute.

connector

Synonym for optical fiber connector.

console

See personal computer; segmented loop port.

context menu

See shortcut menu.


Glossary

control processor card

CTP card. Circuit card that contains the director or switch microprocessor. The CTP card also initializes hardware components of the system after power-on. The card may contain an RJ-45 twisted pair connector.

control unit port

CUP. An internal director or switch port on the control processor (CTP) card (labelled FE) that communicates with channels to report error conditions and link initialization (D).

CRC

See cyclic redundancy check.

credit

See buffer-to-buffer credit.

CTP card

See control processor card.

CUP

See control unit port.

cyclic redundancy check

CRC. System of error checking performed at both the sending and receiving station using the value of a particular character generated by a cyclic algorithm. When the values generated at each station are identical, data integrity is confirmed.

DDASD

See direct access storage device.

database

A collection of data with a given structure for accepting, storing, and providing on-demand data for multiple users (T).

data center

A collection of servers and data storage products, usually in one location, administered by an information technology/information services (IT/IS) manager.


251

Glossary

data integrity

Refers to the validity of data. Data integrity can be compromised in a number of ways including human errors when data is entered, errors that occur when data is transmitted from one computer to another, software bugs or viruses, hardware malfunctions (disk crashes), and natural disasters (fires and floods). There are many ways to minimize these threats to data integrity such as backing up data regularly, controlling access to data via security mechanisms, designing user interfaces that prevent the input of invalid data, and using error detection and correction software when transmitting data.

data recovery

Salvaging data stored on damaged media, such as magnetic disks and tapes. There are a number of software products that can help recover data damaged by a disk crash or virus. Of course, not all data is recoverable, but data recovery specialists can often restore a surprisingly high percentage of the data on damaged media.

datagram

Synonym for Class 3 Fibre Channel service.

default

Pertaining to an attribute, value, or option that is assumed by a system when none is explicitly specified (D, I).

default zone

A zone that contains all attached products that are not members of a separate active zone.

destination

A point or location, such as a processor, director or switch, or server, to which data is transmitted (D).

destination address

D_ID. An address identifier that indicates the targeted destination of a data frame.

device

1. Product, connected to a managed director or switch. See also node.

2. Mechanical, electrical, or electronic hardware with a specific purpose. (D).

device number

In a channel subsystem, four hexadecimal digits that uniquely identify an I/O product (D).

device type

Identifier used to place products in the Physical Map (i.e. switch, hub, storage).

diagnostics

1. The process of investigating the cause or nature of a problem in a product or system.


Glossary

2. Procedures or tests used by computer users and service personnel to diagnose hardware or software problems (D).

dialog box

A pop-up window in the user interface with informational messages or fields to be modified or completed with desired options.

D_ID

See destination address.

digital transmission

Information is converted to binary computer code (a series of 0s and 1s). The information is sent in this format and then converted into its original format when it reaches its destination.

direct access storage device

DASD.

1. Generic classification for a storage peripheral that can respond directly to random requests for information. Usually refers to a disk drive.

2. A storage product that provides direct access to data, and in which access time is independent of data location.

director

An intelligent, highly-available, Fibre Channel switch providing any-to-any port connectivity between nodes (end devices) on a switched fabric. The director sends data transmissions (data frames) between nodes in accordance with the address information present in the frame headers of those transmissions.

disaster recovery

A program that is designed to help companies get back to normal activities after a catastrophic interruption. Through failover to a parallel system, or by restoration of the failed system, disaster recovery restores the system to its normal operating mode.

discovery

The process by which the SANavigator application detects products in a SAN. The user can configure the application to perform in-band or out-of-band discovery. See also in-band discovery or out-of-band discovery.

diskette

A thin magnetic disk enclosed in a plastic jacket, which is removable from a computer and is used to store and transport data (D).


253

Glossary

diskette drive

The hardware mechanism by which a computer reads data from and writes data to removable diskettes (D).

disk operating system

DOS. The computer program that controls the organization of data, files, and processes on the computer.

DNS name

Domain name system or domain name service. Host or node name for a managed product that is translated to an Internet protocol (IP) address through a domain name server.

domain

A Fibre Channel term describing the most significant byte in the node port (N_Port) identifier for the Fibre Channel product. It is not used in the Fibre Channel small computer system interface (FC-SCSI) hardware path ID. It is required to be the same for all SCSI targets logically connected to a Fibre Channel adapter.

domain ID

Domain identifier. A number that uniquely identifies a switch in a multiswitch fabric. A distinct domain ID is automatically allocated to each switch in the fabric by the principal switch. The preferred domain ID is the domain ID value that a switch requests from the principal switch. If the value has not been allocated to another switch in the fabric, it will be granted by the principal switch and will become the requesting switch’s active domain ID. The active domain ID is the domain ID that has been assigned by the principal switch and that a switch is currently using.

domain name server

In transmission control protocol/Internet protocol (TCP/IP), a server program that supplies name-to-address translation by mapping domain name to internet addresses (D).

DOS

See disk operating system.

drop-down menu

A menu that appears when a heading in a navigation bar is clicked on with the mouse. The objects that appear in the drop-down menus are organize by their headings in the navigation bar.

dump

The file that is created when the director detects a software fault. It contains various data fields that, when extracted, assist in the debugging of software.

dynamic connection

A connection between two ports, established or removed by the directors and that, when active, appears as one continuous link. See connectivity attribute. See also dynamic connectivity.


Glossary

dynamic connectivity

The capability that allows connections to be established and removed at any time.

dynamic random access memory

DRAM. Random access memory that resides in a cell comprised of a capacitor and transistor. DRAM data deteriorates (that is, is dynamic) unless the capacitor is periodically recharged by the controlling microprocessor. DRAM is slow, but relatively inexpensive (D). Contrast with dynamic random access memory.

Eelectronic data interchange

EDI. The electronic transfer of preformatted business documents, such as purchase orders and bills of lading, between trading partners.

Electronic Industries Association

EIA. The governing body that publishes recommended standards for physical products and associated interfaces. For example, RS-232 is the EIA standard that defines computer serial port connectivity (D).

electronic mail

E-mail. Any communications service that permits the electronic transmission and storage of messages and attached or enclosed files.

Element Manager application

Application that implements the management user interface for a director or switch. In your SAN management application, the software component that provides a graphical user interface for managing and monitoring switch products. When a product instance is opened from your SAN management application, the corresponding Element Manager application is invoked.

e-mail

See electronic mail.

enhanced availability feature

EAF. A backup field-replaceable unit (backup FRU) that is ordered and installed to provide redundancy and reduce disruption in case of failure (D).

enterprise

The entire storage system. The series of computers employed largely in high-volume and multi-user environments such as servers or networking applications; may include single-user workstations required in demanding design, engineering and audio/visual applications.


255

Glossary

Enterprise Systems Architecture

ESA™. A computer architecture introduced by IBM in 1988 as ESA/370. The architecture added access registers to improve virtual memory management and increase storage from 2 gigabyte to 6 terabytes. The architecture was enhanced with the introduction of ESA/390 in 1990 (D).

Enterprise Systems Connection

ESCON™. An IBM architecture, technology, and set of products and services introduced in 1990 that provides a dynamically connected environment using fiber-optic cables as the data transmission medium (D).

Enterprise Systems Connection Director

ESCON™ Director. A device that provides connectivity capability and control for attaching any two links to each other through the ESON channel. Specifically, any of the hardware products provided for interconnecting IBM-compatible mainframe equipment through the proprietary ESCON channel connection. IBM’s model numbers for ESCON directors include the 9031 and 9033.

E_Port

See expansion port.

erase

To remove electrically or magnetically stored data, leaving the space where the data was stored unoccupied (D).

error-detect time-out value

E_D_TOV. The time the switch waits for an expected response before declaring an error condition.

error log

See master log.

error message

Indication that an error has been detected (D). See also information message; warning message.

ESA™

See Enterprise Systems Architecture.

ESCON™

See Enterprise Systems Connection.

ESCON™ Director

See Enterprise Systems Connection Director.


Glossary

Ethernet

A widely implemented local area network (LAN) protocol that uses a bus or star topology and serves as the basis for the Institute of Electrical and Electronics Engineers (IEEE) 802.3 standard, which specifies the physical and software layers.

Ethernet hub

A product used to connect a server and the switches it manages.

event code

A three-digit number that specifies the exact event that occurred. This code provides information on system failures, such as hardware failures, failure locations, or general information on normal system events.

event log

Displays errors related to SAN management, such as SNMP traps or Client-Server communications.

event notification

A process by which the SANavigator application informs remote users and workstations of certain classes of events that occur on the system. E-mail notification and the configuration of simple network management protocol (SNMP) trap recipients are two examples of remote notification programs that can be implemented through the application.

exchange

A term that refers to one of the Fibre Channel protocol “building blocks,” composed of one or more nonconcurrent sequences.

expansion port

E_Port. Physical interface on a Fibre Channel switch within a fabric, that attaches to an E_Port on another Fibre Channel switch through an interswitch link (ISL) to form a multiswitch fabric. See also fabric loop port; fabric port; hub port; node loop port; node port.

explicit fabric login

The process by which a node port (N_Port) learns the characteristics of the fabric to which it is attached by sending a fabric login command (FLOGI) frame to the fabric port (F_Port) address FFFFFE (hexadecimal.

extended distance feature

XDF. A means to extend the propagation distance of a fiber-optic signal.


257

Glossary

Ffabric

Entity that is capable of routing (switching) Fibre Channel frames, using the destination ID information in the Fibre Channel frame header accompanying the frames.

fabric element

Any active director, switch, or node in a switched fabric.

fabric group

A collection of interconnected SAN devices discovered by the SAN Manager application. Fabric groups appear with a blue background on the Physical Map.

fabric login

The process by which node ports (N_Ports) establish their operating parameters. During fabric login, the presence or absence of a fabric is determined, and paths to other N_Ports are mapped. Specific operating characteristics for each port, such as buffer-to-buffer credit (BB_Credit) and data frame size, are also established.

fabric login command

FLOGI. The command that establishes the initial operating parameters and topology for a fabric. The command is accepted by a fabric port (F_Port) (D).

fabric loop port

FL_Port. A fabric port (F_Port) that contains arbitrated loop (AL) functions associated with the Fibre Channel arbitrated loop (FC-AL) topology. The access point of the fabric for physically connecting an arbitrated loop of node loop ports (NL_Ports). See also expansion port; fabric port; hub port; node loop port; node port.

fabric mode

See interoperability mode.

fabric port

F_Port. Physical interface within the fabric that connects to a node port (N_Port) through a point-to-point full duplex connection. See also expansion port; fabric loop port; hub port; node loop port; node port.

fabric services

The services that implement the various Fibre Channel protocol services that are described in the standards. These services include the fabric controller (login server), name server, and server platform.


Glossary

fabric switches

A product that allows communication between multiple products using Fibre Channel protocols. A fabric switch enables the sharing bandwidth and end-nodes using basic multiplexing techniques.

failover

Automatic and nondisruptive transition of functions from an active field-replaceable unit (FRU) that has failed to a backup FRU.

FC

See Fibre Channel.

FC-0

The Fibre Channel layer that describes the physical link between two ports, including the transmission media, transmitter and receiver circuitry, and interfaces (D). This consists of a pair of either optical fiber or electrical cables (link media) along with transceiver circuitry which work together to convert a stream of bits at one end of the link to a stream of bits at the other end.

FC-1

Middle layer of the Fibre Channel physical and signaling interface (FC-PH) standard, defining the 8B/10B encoding/decoding and transmission protocol.

FC-2

The Fibre Channel layer that specifies the signaling protocol, rules, and mechanisms required to transfer data blocks. The FC-2 layer is very complex and provides different classes of service, packetization, sequencing, error detection, segmentation, and reassembly of transmitted data (D).

FC-3

The Fibre Channel layer that provides a set of services common across multiple node ports (N_Ports) of a Fibre Channel node. The services are not commonly used and are essentially reserved for Fibre Channel architecture expansion (D).

FC-4

The Fibre Channel layer that provides mapping of Fibre Channel capabilities to upper level protocols (ULP), including Internet protocol (IP) and small computer system interface (SCSI) (D).

FCA

See Fibre Channel Association.

FC-AL

See Fibre Channel arbitrated loop.


259

Glossary

FC adapter

Fibre Channel adapter. See host bus adapter.

FCC

Federal Communications Commission.

FCC-IOC

See Fibre Channel I/O controller.

FCFE

See Fibre Channel fabric element.

FCFE-MIB

See Fibre Channel fabric element management information base.

FCIA

See Fibre Channel Industry Association.

FC IP

See Fibre Channel IP address.

FCMGMT

See Fibre Channel management framework integration.

FC-PH

See Fibre Channel physical and signaling interface.

feature key

A unique key to enable additional product features. This key is entered into the Configure Feature Key dialog box in the Element Manager application to activate optional hardware and software features. When you purchase a new feature, you will receive a feature key.

fiber

The fiber-optic cable made from thin strands of glass through which data in the form of light pulses is transmitted. It is used for high-speed transmissions over medium (200 m) to long (10 km) distances.

fiber-optic cable

Synonym for optical cable.

fibre

A generic Fibre Channel term used to cover all transmission media types specified in the Fibre Channel Physical Layer (FC-PH) standard such as optical fiber, copper twisted pair, and copper coaxial cable.


Glossary

Fibre Channel

FC. Integrated set of standards recognized by American National Standards Institute (ANSI) which defines specific protocols for flexible information transfer. Logically, a point-to-point serial data channel, structured for high performance.

Fibre Channel adapter

FC adapter. See host bus adapter.

Fibre Channel address

A 3-byte node port (N_Port) identifier which is unique within the address domain of a fabric. Each port may choose its own identifier, or the identifier may be assigned automatically during fabric login.

Fibre Channel arbitrated loop

FC-AL. A high-speed (100 Mbps) connection which is a true loop technology where ports use arbitration to establish a point-to-point circuit. Data can be transferred in both directions simultaneously, achieving a nominal transfer rate between two products of 200 Mbps.

Fibre Channel Association

FCA. The FCA is a non-profit corporation consisting of over 150 members throughout the world. Its mission is to nurture and help develop the broadest market for Fibre Channel products through market development, education, standards monitoring, and fostering interoperability among members’ products.

Fibre Channel fabric element

FCFE. Any product linked to a fabric.

Fibre Channel fabric element management information base

FCFE-MIB. A table of variables available to network management stations and resident on a switch or director. Through the simple network management protocol (SNMP) these pointers can be manipulates to monitor, control, and configure the switch or director.

Fibre Channel Industry Association

FCIA. A corporation consisting of over 100 computer industry-related companies. Its goal is to provide marketing support, exhibits, and tradeshows for its member companies. The FCIA complements activities of the various standards committees.

Fibre Channel I/O controller

FCC-IOC. In a director, the integrated controller on the control processor (CTP) card dedicated to the task of managing the embedded Fibre Channel port. In a director or switch, the FCC-IOC controls the embedded Fibre Channel port and configures the ports’ application-specific integrated circuits (ASICs).


261

Glossary

Fibre Channel IP address

FC IP. The default FC IP on a new switch is a temporary number divided by the switch’s world-wide name (WWN). The system administrator needs to enter a valid IP address.

Fibre Channel management framework integration

FCMGMT. A standard defined by the Fibre Alliance to provide easy management for Fibre Channel-based products such as switches, hubs, and host-bus adapters.

Fibre Channel physical and signaling interface

FC-PH. The American National Standards Institute (ANSI) document that specifies the FC-0 (physical signaling), FC-1 (data encoding), and FC-2 (frame construct) layers of the Fibre Channel protocol (D).

Fibre Channel protocol for SCSI (FCP)

FCP defines a high-level Fibre Channel mapping layer (FC-4) that uses lower-level Fibre Channel (FC-PH) services to transmit SCSI command, data, and status information between a SCSI initiator and a SCSI target across the FC link using FC frame and sequence formats.

Fibre Channel standard

American National Standards Institute (ANSI) standard that provides a common, efficient data transport system that supports multiple protocols. The architecture integrates both channel and network technologies, and provides active, intelligent interconnection among products. All data transmission is isolated from the control protocol, allowing use of point-to-point, arbitrated loop, or switched fabric topologies to meet the needs of an application.

Fibre Connection

FICON. An IBM set of products and services introduced in 1999 that is based on the Fibre Channel Standard. FICON technology uses fiber-optic cables as the data transmission medium, and significantly improves I/O performance (including one Gbps bi-directional data transfer). FICON is designed to coexist with ESCON™ channels, and FICON-to-ESCON control unit connections are supported (D).

fibre port module

FPM. A 1 gigabit-per-second module that contains four generic ports (DePorts).

FICON

See Fibre Connection.

FICON Management Server

An optional feature that can be enabled on the director or switch or switch through the Element Manager application. When enabled, host control and management of the director or switch or switch is provided through an S/390 Parallel Enterprise or 2/Series Server attached to a director or switch or switch port.


Glossary

FICON management style

The management style that is most useful when attaching to IBM S/390 Enterprise Servers. See also open systems management style; management style.

field-replaceable unit

FRU. Assembly removed and replaced in its entirety when any one of its components fails (D).

file server

A computer that stores data centrally for network users and manages access to that data.

file transfer protocol

FTP. A TCP/IP-based client/server protocol used to transfer files to and from a remote host. Does not perform any conversion or translation.

firmware

Embedded program code that resides and runs on, for example, directors, switches, and hubs.

firewall

A networking product that blocks unauthorized access to all or parts of a network.

firewall zoning

Hardware enforced access between F_Ports enforced at the source port. The hardware verifies the destination port against the zone defined for the source port.

firmware

Embedded program code that resides and runs on, for example, directors, switches, and hubs.

FLASH memory

Reusable nonvolatile memory that is organized as segments for writing, and as bytes or words for reading. FLASH memory is faster than read-only memory, but slower than random access memory (D).

FLOGI

See fabric login command.

FL_Port

See fabric loop port.

FPM

See fibre port module.

F_Port

See fabric port.


263

Glossary

frame

A variable-length packet of data that is transmitted in frame relay technology.

FRU

See field-replaceable unit.

FTP

See file transfer protocol.

GGb/s

Acronym for gigabits per second.

gateway address

3. In transmission control protocol/Internet protocol (TCP/IP), a product that connects two systems that use the same or different protocols.

4. In TCP/IP, the address of a router to which a product sends frames destined for addresses not on the same physical network (for example, not on the same Ethernet) as the sender. The hexadecimal format for the gateway address is nnn.nnn.nnn.nnn.

Gb

Acronym for gigabits.

GB

Acronym for gigabyte.

GbIC

See gigabit interface converter.

Gbps

Acronym for gigabits per second.

GHz

Acronym for gigahertz.

generic port

G_Port. Physical interface on a director or switch that can function either as a fabric port (F_Port) or an expansion port (E_Port), depending on the port type to which it connects. See also bridge port;


Glossary

expansion port; fabric loop port; fabric port; hub port; node loop port; node port; segmented expansion port.

generic port module card

GPM card. A port card that implements four generic ports (G_Ports) and provides the physical connection point for links to Fibre Channel products.

gigabit

Gb. A unit of measure for data storage, equal to approximately 134,217,728 bytes. Approximately one eighth of a gigabyte.

gigabit interface converter

GbIC. A removable module that converts an electrical serial data stream to an optical or amplified electrical serial data stream. Contains connector for attaching fiber-optic cable.

gigabyte

GB. A unit of measure for data storage, equal to 1,073,741,824 bytes. Generally approximated as one billion bytes (D).

gigahertz

GHz. One billion cycles per second (Hertz) (D).

GPM card

See generic port module card.

G_Port

See generic port.

graphical user interface

GUI. A visually oriented interface where the user interacts with representations of real-world objects displayed on the computer screen. Interactions with such objects produce actions that are intuitive to the user (D).

GSM card

A generic port (G_Port) module card containing shortwave laser ports for multimode fiber-optic cables.

GUI

See graphical user interface.


265

Glossary

HH_Port

See hub port.

hard drive

An electromechanical product used for information storage and retrieval, incorporating one or more rotating disks on which data is recorded, stored, and read magnetically.

Hardware Log

Director or switch Hardware Log. Log displayed through the Element Manager application that provides a history of FRU removals and replacements (insertions) for an individual director or switch. The information is useful to maintenance personnel for fault isolation and repair verification. See also Audit Log; master log; Link Incident Log; Threshold Alert Log.

hardware

Physical equipment (director, switch, or personal computer) as opposed to computer programs or software.

hardware management console

The console runs the Hardware Management console application (HWMCA), and is the operations and management personal computer (PC) platform for S/390 and z/Series servers.

HBA

See host bus adapter.

heterogeneous fabric

A fabric containing open-fabric-compliant products from various vendors. Contrast with homogeneous fabric.

hexadecimal

A numbering system with base of sixteen; valid numbers use the digits 0 through 9 and characters A through F, where A represents 10 and F represents 15 (D).

homogeneous fabric

A fabric consisting of only one vendor’s products. Contrast with heterogeneous fabric.

hop

1. Data transfer from one node to another node.

2. Describes the number of switches that handle a data frame from its origination point through it’s destination point.


Glossary

hop count

The number of hops a unit of information traverses in a fabric.

host

The computer that other computers and peripherals connect to.

host bus adapter

HBA. Logic card that provides a link between the server and storage subsystem, and that integrates the operating systems and I/O protocols to ensure interoperability.

host group

The collection of HBAs and NASs in a fabric discovered by the SANavigator application. Host groups appear with a yellow background on the Physical Map.

host processor

1. A processor that controls all or part of a user application network (T).

2. In a network, the processing unit in which resides the access method for the network (D).

hot spare

An extra disk that is currently running in the RAID, but is there for backup. If a working disk fails, its data can be reconstructed from the remaining disks and written to the hot spare.

HTTP

See hypertext transport protocol.

hub

In Fibre Channel protocol, a product that connects nodes into a logical loop by using a physical star topology.

hub port

H_Port. In arbitrated loop products, a port that uses arbitrated loop protocols. The physical interface that attaches to a loop product, either an end product or another loop interconnect product (hub).

hyperlink

A predefined link for jumping from one location to another, within the same computer or network site or even to a location at a completely different physical location. Commonly used on the world wide web for navigation, reference, and depth where published text will not suffice.

hypertext transport protocol

HTTP. A simple protocol that allows world wide web pages to be transferred quickly between web browsers and servers.


267

Glossary

IID

See identifier.

identifier

ID.

1. One or more characters used to identify or name a data element and possibly to indicate certain properties of that data element (D, T).

2. A sequence of bits or characters that identifies a program, device, or system to another program, device, or system. See also port name.

IEEE

See Institute of Electrical and Electronics Engineers.

IML

See initial machine load.

in-band

Transmission of management protocol over the Fibre Channel transport. See also out-of-band.

in-band discovery

The process through which the SANavigator Server gathers data about the in-band data flow and LUNs from the HBA driver. The HBA driver must support the Fibre Alliance HBA API in order for in-band discovery to work properly. See also out-of-band discovery.

in-band management

Management of the director or switch through Fibre Channel. An interface connection to a port card. Contrast with out-of-band management.

industry standard architecture

ISA. Bus architecture designed for personal computers (PCs) that use an Intel 80386, 80486, or Pentium microprocessor. ISA buses are 32 bits wide and support multiprocessing.

information message

Message notifying a user that a function is performing normally or has completed normally. See also error message; warning message.

information services

IS. IS is the name of the department responsible for computers, networking, and data management. See also information technology.


Glossary

information technology

IT. The broad subject concerned with all aspects of managing and processing information, especially within a large organization or company. Because computers are central to information management, computer departments within companies and universities are often called IT departments. See also information services.

initial machine load

IML. Hardware reset for all installed control processor (CTP) cards on the director or switch. This reset does not affect other hardware. It is initiated by pushing the IML button on a director’s or switch’s operating panel.

initial program load

IPL. The process of initializing the product and causing the operating system to start. An IPL may be initiated through a menu option or a hardware button.

initial program load configuration

IPL configuration. In FICON management style, information stored in a director or switch’s nonvolatile memory that contains default configurations. The director or switch loads the file for operation when powered on.

input/output

I/O.

1. Pertaining to a device whose parts can perform an input process and an output process at the same time (I).

2. Pertaining to a functional unit or channel involved in an input process, output process, or both, concurrently or not, and to the data involved in such a process.

3. Pertaining to input, output, or both (D).

4. An operation or product that allows input and output.

Institute of Electrical and Electronics Engineers

IEEE. An organization of engineers and technical professionals that promotes the development and application of electronic technology and allied sciences.

interface

1. A shared boundary between two functional units, defined by functional, signal, or other characteristics. The concept includes the specification of the connection of two products having different functions (T).

2. Hardware, software, or both, that link systems, programs, or products (D).


269

Glossary

Internet protocol

IP. Network layer for the transmission control protocol/Internet protocol (TCP/IP) protocol used on Ethernet networks. IP provides packet routing, fragmentation, and reassembly through the data link layer (D).

Internet protocol address

IP address. Unique string of numbers (in the format nnn.nnn.nnn.nnn) that identifies a product on a network.

interoperability

Ability to communicate, execute programs, or transfer data between various functional units over a network.

interoperability mode

Interpol mode. A management style set through management software that allows products to operate in homogeneous or heterogeneous fabrics.

interop mode

See interoperability mode.

interrupt

A signal sent by a subsystem to the central processing unit (CPU) that signifies a process has either completed or could not be completed.

interswitch link

ISL. Physical expansion port (E_Port) connection between two directors in a fabric.

intranet

A private version of the Internet that provides a cost-effective way to publicize critical information and provide an interactive communication path for heterogeneous systems. Internal to a specific organizational structure and secured from or disconnected from the global Internet.

I/O

See input/output.

IOPS

Input/output operations per second.

IP

See Internet protocol.


Glossary

IP address

See Internet protocol address.

IS

See information services.

IPL

See initial program load.

IPL configuration

See initial program load configuration.

ISL

See interswitch link.

ISL hop

Interswitch link hop. See hop.

isolated E_Port

Isolated expansion port.

isolated expansion port

Isolated E_Port.

isolated group

A collection of isolated devices not connected to the SAN but discovered by the SANavigator application. The isolated group appears with a gray background near the bottom of the Physical Map.

IT

See information technology.

JJava

An object-oriented programming language derived from C++ that produces code that is platform independent. Developed by Sun Microsystems designed for distribution and distributable applications development. Java applications require a program called the Java Virtual Machine (JVM) to execute. JVMs have been developed for many of the mainstream platforms and operating systems.


271

Glossary

JBOD

See just a bunch of disks.

just a bunch of disks

JBOD. Refers to a rack of disks without data redundancy or striping.

KKb

See kilobit.

KB

See kilobyte.

kilobit

Kb. A unit of measure for data storage, equaling 1,024 bits, or two to the tenth power. Kilobits are generally approximated as being one thousand bits.

kilobyte

KB. A unit of measure for data storage, equaling 1,024 bytes, or two to the tenth power. Kilobytes are generally approximated as being one thousand bytes.

Llabel

A discovered or user-entered property value that appears below each product on the Physical Map, or topology.

LAN

See local area network.

laser

Laser is an acronym for light amplification by stimulated emission of radiation. A product that produces a very powerful narrow beam of coherent light of a single wavelength by simulating the emissions of photons from atoms, molecules, or ions.

latency

Amount of time elapsed between receipt of a data transmission at a switch’s incoming fabric port (F_Port) from the originating node port (N_Port) to retransmission of that data at the switch’s outgoing


Glossary

F_Port to the destination N_Port. The amount of time it takes for data transmission to pass through a switching product. The time it takes for data to go from an HBA to a product’s LUN and back to the HBA.

LCD

Liquid crystal display.

light-emitting diode

LED. A semiconductor chip that emits visible or infrared light when electricity passes through it. LEDs are used on switch or director field-replaceable units (FRUs) and the front bezel to provide visual indications of hardware status or malfunctions.

LIN

See link incident.

link

Physical connection between two products on a switched fabric. A link consists of two conductors, one used for sending and the other for receiving, thereby providing a duplex communication path.

link incident

LIN. Interruption to link due to loss of light or other causes. See also link incident alerts.

link incident alerts

A user notification, such as a graphic symbol in the Element Manager application Hardware View that indicates that a link incident has occurred. See also link incident.

Link Incident Log

Director or switch Link Incident Log. Log displayed through the Element Manager application that provides a history of Fibre Channel link incidents (with associated port numbers) for an individual director or switch. The information is useful to maintenance personnel for isolating port problems (particularly expansion port [E_Port] segmentation problems) and repair verification. See also Audit Log; master log; Hardware Log; Threshold Alert Log.

LIP

See loop initialization primitive.

load balancing

Ability to evenly distribute traffic over multiple interswitch links within a fabric. Load balancing on directors and switches takes place automatically.


273

Glossary

local area network

LAN. A computer network in a localized geographical area (for example, a building or campus), whose communications technology provides a high-bandwidth medium to which many nodes are connected (D). See also metropolitan area network; storage area network; wide area network.

logical port address

In a director or switch, the address used to specify port connectivity parameters and to assign link addresses for the attached channels and control units.

logical switch number

LSN. A two-digit number used by the I/O configuration program (IOCP) to identify a director or switch (D).

logical unit number

LUN. In Fibre Channel addressing, a logical unit number is a number assigned to a storage product which, in combination with the storage product’s node port’s world-wide name, represents a unique identifier for a logical product on a storage area network. Peripherals use LUNs to represent addresses. A small computer system interface (SCSI) product’s address can have up to eight LUNs.

login server

Entity within the Fibre Channel fabric that receives and responds to login requests.

loop

A loop is a configuration of products connected to the fabric via a fabric loop port (FL_Port) interface card.

loop address

In Fibre Channel protocol, a term indicating the unique ID of a node in Fibre Channel loop topology, sometimes referred to as a loop ID.

loop group

A collection of SAN devices that are interconnected serially in a single loop circuit. Loop groups discovered by SAN Manager appear with a gray background on the Physical Map.

loop initialization primitive

LIP. In an arbitrated loop product, a process by which devices connected to hub ports (H_Ports) on the arbitrated loop device notify other devices and the switch of the presence in the loop by sending LIP sequences and subsequent frames through the loop. This process allows linked arbitrated loop devices to perform fabric loop port (FL_Port) arbitration as they link through hub ports.

loop master

In an arbitrated loop device, a reference to the loop master World Wide Name (WWN) field in the Loop View, the loop master is the arbitrated loop device that is responsible for allocating arbitrated loop


Glossary

physical addresses (AL-PAs) on the loop. An arbitrated loop device becomes the loop master through arbitration when there are multiple arbitrated loop devices on the loop. The arbitrated loop device with the lowest WWN becomes the loop master.

loop switches

Loop switches support node loop port (NL_Port) Fibre Channel protocols. Switches sold as loop support but upgradeable to fabric switches recounted as loop switches.

loop port

L_Port. Synonym for hub port.

loopback plug

In a fiber optic environment, a type of duplex connector used to wrap the optical output signal of a device directly to the optical input. Synonymous with wrap plug.

loopback test

Test that checks attachment or control unit circuitry, without checking the mechanism itself, by returning the output of the mechanism as input.

L_Port

Loop port. Synonym for hub port.

LSN

See logical switch number.

LUN

See logical unit number.

MMAC address

See media access control address.

mainframe

A powerful multi-user computer capable of supporting many hundreds or thousands of users simultaneously.

MAN

See metropolitan area network.


275

Glossary

maintenance port

Connector on the director or switch where a PC running an American National Standard Code for Information Interchange (ASCII) terminal emulator can be attached or dial-up connection made for specialized maintenance support.

management information base

MIB. Related set of software objects (variables) containing information about a managed device and accessed via simple network management protocol (SNMP) from a network management station.

management session

A session that exists when a user logs on to your SAN management application. Your SAN management application can support multiple concurrent management sessions. The user must specify the network address of your SAN management application’s server at logon time.

management style

In directors or switches, in managed products, a selection between FICON and open systems management style. See also open systems management style; FICON management style.

manager

A management application, such as SAN Manager.

master log

Record of significant events that have occurred on the SAN, including configuration and discovery events.

Mb

Megabit.

MB

See megabyte.

Mbps

Megabits per second.

MBps

Megabytes per second.

media access control address

MAC address. Hardware address of a node (device) connected to a network.


Glossary

megabyte

MB. A unit of measure for data storage, equal to 1,048,576 bytes. Generally approximated as one million bytes.

memory

A device or storage system capable of storing and retrieving data.

menu

A list of items displayed on a monitor from which a user can make a selection.

menu bar

The menu bar is located across the top of a window. Pull-down menus are displayed by clicking on the menu bar option with the mouse, or by pressing ALT with the underlined letter of the name for the menu bar option (D).

metropolitan area network

MAN. A network capable of high-speed communications over distances up to about 100 kilometers. See also local area network; storage area network; wide area network.

MIB

See management information base.

microsecond

μs.

mirroring

The writing of data to pairs of drives in an array, creating two exact copies of the drive contents. This procedure provides a backup of data in case of a failure.

model

The model identification assigned to a device by its manufacturer.

modem

Modem is an abbreviation for modulator/demodulator. A communication device that converts digital computer data to signals and signals to computer data. These signals can be received or transmitted by the modem via a phone line or other method of telecommunication.

ms

Millisecond.

multimedia

A simultaneous presentation of data in more than one form, such as by means of both visual and audio.


277

Glossary

multiswitch fabric

Fibre Channel fabric created by linking more than one director or fabric switching device within a fabric.

Nname server

3. In TCP/IP, see domain name server.

4. In Fibre Channel protocol, a server that allows node ports (N_Ports) to register information about themselves. This information allows N_Ports to discover and learn about each other by sending queries to the name server.

name server zoning

Node port (N_Port) access management that allows N_Ports to communicate if and only if they belong to a common name server zone.

NAS

See network-attached storage.

network

An arrangement of hardware, software, nodes, and connecting branches that comprises a data communication system. The International Organization for Standardization (ISO) seven-layer specification partitions a computer network into independent modules from the lowest (physical) layer to the highest (application) layer (D).

network address

Name or address that identifies a device on a transmission control protocol/Internet protocol (TCP/IP) network. The network address can be either an IP address in dotted-decimal notation (composed of four three-digit octets in the format nnn.nnn.nnn.nnn) or a domain name (as administered on a customer network).

network-attached storage

NAS. Storage connected directly to the network, through a processor and its own operating system. Lacks the processor power to run centralized, shared applications.

network interface card

NIC. An expansion board inserted into a computer so the computer can be connected to a network. Most NICs are designed for specific types of networks, protocols, and medias, although some can serve multiple networks.


Glossary

network management

The broad subject of managing computer networks. There exists a wide variety of software and hardware products that help network system administrators manage a network. Network management covers a wide area, including security, performance, and reliability.

never principal

The setting that prevents the product from becoming the principal switch for a fabric.

nickname

Alternate name assigned to a world-wide name for a node, director or switch in the fabric.

NL_Port

See node loop port.

node

In Fibre Channel protocol, an end device (server or storage device) that is or can be connected to a switched fabric. See also device.

node loop port

NL_Port. A physical interface within an end device (node) that participates in a loop containing one or more fabric loop ports (FL_Ports) or other NL_Ports). See also expansion port; fabric loop port; fabric port; hub port; node port.

node port

N_Port. Physical interface within an end device that can connect to an fabric port (F_Port) on a switched fabric or directly to another N_Port (in point-to-point communications). See also expansion port; fabric loop port; fabric port; hub port; node loop port.

node port identifier

N_Port ID. In Fibre Channel protocol, a unique address identifier by which an N_Port is uniquely known. It consists of a domain (most significant byte), an area, and a port, each 1 byte long. The N_Port ID is used in the source identifier (S_ID) and destination identifier (D_ID) fields of a Fibre Channel frame.

nonvolatile random access memory

NV-RAM. RAM that retains its content when the device power is turned off.

N_Port

See node port.

N_Port ID

See node port identifier.


279

Glossary

NV-RAM

See nonvolatile random access memory.

Ooctet

An 8-bit quantity, often called a byte or word. An octet can equal a byte as long as the byte equals eight bits. See also byte.

OEM

See original equipment manufacturer.

offline

Referring to data stored on a medium, such as tape or even paper, that is not available immediately to the user.

offline sequence

OLS.

1. Sequence sent by the transmitting port to indicate that it is attempting to initialize a link and has detected a problem in doing so.

2. Sequence sent by the transmitting port to indicate that it is offline.

offline state

When the switch or director is in the offline state, all the installed ports are offline. The ports transmit an offline sequence (OLS) and they cannot accept a login got connection from an attached device. Contrast with online state.

OLS

See offline sequence.

online

Referring to data stored on the system so it is available immediately to the user.

online diagnostics

Diagnostics that can be run by the customer engineer while the operational software is running. These diagnostics do not impact user operations.

online state

When the switch or director is in the online state, all of the unblocked ports are allowed to log in to the fabric and begin communicating. Devices can connect to the switch or director if the port is not blocked


Glossary

and can communicate with another attached device if both devices are in the same zone, or if the default zone is enabled. Contrast with online state.

Open Systems Architecture

OSI. A model that represents a network as a hierarchical structure of functional layers. Each layer provides a set of functions that can be accessed and used by the layer above. Layers are independent, in that implementation of a layer can be changed without affecting other layers (D).

open systems management server

OSMS. An optional feature that can be enabled on the director or switch through the Element Manager application. When enabled, host control and management of the director or switch are provided through an Open System Interconnection (OSI) device attached to a director or switch port.

open systems management style

The mode that is used for open fabrics. See also management style; FICON management style.

operating system

OS. Software that controls execution of applications and provides services such as resource allocation, scheduling, I/O control, and data management. Most operating systems are predominantly software, but partial hardware implementations are possible (D, T).

Operating System/390

OS/390™. An integrated, open-enterprise server operating system developed by IBM that incorporates a leading-edge and open communications server, distributed data and file services, parallel Sysplex™ support, object-oriented programming, distributed computing environment, and open application interfaces (D).

original equipment manufacturer

OEM. A company that has a special relationship with computer producers. OEMs buy components and customize them for a particular application. They sell the customized computer under their own name. OEMs may not actually be the original manufacturers. They usually customize and market the product.

OS

See operating system.

OS/390™

See Operating System/390.

OSI

See open systems management server.

OSMS

See open systems management server.


281

Glossary

out-of-band

Transmission of management protocols outside of the Fibre Channel network, typically over Ethernet. See also in-band.

out-of-band discovery

The process through which the SAN Manager application connects to the switches via the IP network. Device information is copied from the SNMP server to the Server. See also in-band discovery.

out-of-band management

Transmission of management information, using frequencies or channels other than those routinely used for information transfer.

Ppacket

In Fibre Channel protocol, Logical unit of information (usually in the form of a data frame) transmitted on a network. It contains a header (with all relevant addressing and timing information), the actual data, and a trailer (which contains the error checking function, usually in the form of a cyclic redundancy check), and frequently user data.

panel

A logical component of the interface window. Typically, a heading and/or frame marks the panel as an individual entity of the window. Size and shape of the panel and its data depend upon the purpose of the panel and may or may not be modified.

partition

A way to logically divide a hard drive so that an operating system treats each partition as a separate hard drive. Each partition has a unique drive letter.

PC

See personal computer.

persistent binding

A form of server-level access control that uses configuration information to bind a server to a specific Fibre Channel storage volume (or logical device), using a unit number.

personal computer

PC. A computer that consists of a system unit, monitor, keyboard, mouse, one or more diskette drives, and internal fixed-disk storage (D).


Glossary

physical map

The map of the topology that appears when you select the View tab on the main window of the SANavigator application. The Physical Map displays devices and their connections and ports.

point-to-point

A Fibre Channel protocol topology that provides a single, direct connection between two communication ports. The director or switch supports only point-to-point topology (D).

polling delay

The time in seconds between successive discovery processes during which discovery is inactive.

port

Receptacle on a device to which a cable leading to another device can be attached. Ports provide Fibre Channel connections (D).

port address name

A user-defined symbolic name of 24 characters or less that identifies a particular port address.

port authorization

Feature of the password definition function that allows an administrator to extend operator-level passwords to specific port addresses for each director or switch definition managed by a personal computer (PC. Port authorization affects only operator-level actions for active and saved matrices (D.

port card

Field-replaceable hardware component that provides the port connections for fiber cables and performs specific device-dependent logic functions.

port card map

Map showing port numbers and port card slot numbers inside a hardware cabinet.

port name

Name that the user assigns to a particular port through the Element Manager application. See also identifier. Synonymous with address name.

POST

See power-on self-test.

power-on self-test

POST. Series of diagnostic tests that are run automatically by a device when the power is turned on


283

Glossary

preferred domain ID

Configured value that a switch will request from the Principal Switch. If the preferred value is already in use, the Principal Switch will assign a different value.

principal switch

In a multiswitch fabric, the switch that allocates domain IDs to itself and to all other switches in the fabric. There is always one principal switch in a fabric. If a switch is not connected to any other switches, it acts as its own principal switch.

private device

A loop device that cannot transmit a fabric login command (FLOGI) command to a switch or director, nor communicate with fabric-attached devices. Contrast with public device.

private loop

A freestanding Arbitrated Loop with no fabric attachment.

product list

The list of SAN products, groups, and ports, which appears on the left side of the main window in the application.

product name

User-configurable identifier assigned to a managed product. Typically, this name is stored on the product itself. A director or switch product name can also be accessed by a simple network management protocol (SNMP) manager as the system name.

prohibited port connection

In a director or switch, in FICON management style, an attribute that removes dynamic connectivity capability.

protocol

1. Set of semantic and syntactic rules that determines the behavior of functional units in achieving communication.

2. In systems network architecture, the meanings of and sequencing rules for requests and responses for managing the network, transferring data, and synchronizing network component states.

3. A specification for the format and relative timing of data exchanged between communicating devices (D, I).

public device

A loop device that can transmit a fabric login command (FLOGI) to a switch, receive acknowledgement from the switch’s login server, register with the switch’s name server, and communicate with fabric-attached devices. Public devices communicate with fabric-attached devices through the switch’s bridge port (B_Port) connection to a director or switch. Contrast with private device.


Glossary

public loop

A public loop is connected to a switched fabric (through the switch bridge port [B_Port]), and the switch has an active embedded fabric loop port (FL_Port) that is user transparent. All devices attached to the loop can communicate with each other, and public devices attached to the loop can communicate with fabric-attached devices.

pull-down menu

See drop-down menu.

RRAID

See redundant array of independent disks.

RAM

See random access memory.

R_A_TOV

See resource allocation time-out value.

random access memory

RAM. A group of computer memory locations that is numerically identified to allow high-speed access by the controlling microprocessor. A memory location is randomly accessed by referring to its numerical identifier (D). Contrast with read-only memory.

read-only memory

ROM. An information storage chip with permanent memory. Stored information cannot be changed or deleted except under special circumstances (D). Contrast with random access memory.

redundancy

Performance characteristic of a system or product whose integral components are backed up by identical components to which operations will automatically failover in the event of a component failure. Redundancy is a vital characteristic of virtually all high-availability (24 hours/7 days per week) computer systems and networks.

redundant array of independent disks

RAID. Grouping of hard drives in a single system to provide greater performance and data integrity. RAID systems have features that ensure data stored on the drives are safe and quickly retrievable.


285

Glossary

remote computer running client software

Workstation, such as a personal computer (PC) or UNIX workstation, running SAN management and Element Manager client application software that can access the server platform over a local area network (LAN) connection.

remote notification

See event notification.

rerouting delay

An option that ensures that frames are delivered in order through the fabric to their destination.

resource allocation time-out value

R_A_TOV. R_A_TOV is a value used to time-out operations that depend on the maximum possible time that a frame could be delayed in a fabric and still be delivered.

right-click menu

See shortcut menu.

ROM

See read-only memory. Contrast with random access memory.

router

An attaching device that connects two local area network (LAN) segments, which use similar or different architectures, at the reference model network layer (D). Contrast with bridge.

SSAN

See storage area network.

SAN Manager Server

The computer that is hosting the SAN Manager application. Multiple client systems can log in to the server to utilize the SANavigator application.

SAN Manager Software

SAN Manager software provides easy, centralized management of a SAN and quick access to all device configuration applications.

SA OS/390™

See System Automation for Operating System/390.


Glossary

SBAR

See serial crossbar assembly.

segment

A fabric segments when one or more switches cannot join the fabric because of various reasons. The switch or switches remain as separate fabrics.

segmented E_Port

See segmented expansion port.

segmented expansion port

Segmented E_Port. E_Port that has ceased to function as an E_Port within a multiswitch fabric due to an incompatibility between the fabrics that it joins. See also bridge port; fabric loop port; fabric port; generic port; hub port; node loop port; node port.

segmented loop port

Allows you to divide a Fibre Channel private loop into multiple segments. Each segment can pass frames around as an independent loop and can connect through the fabric to other segments of the same loop.

serial crossbar assembly

SBAR. The assembly is responsible for Fibre Channel frame transmission from any director or switch port to any other director or switch port. Connections are established without software intervention.

serial port

A full-duplex channel that sends and receives data at the same time. It consists of three wires: two that move data one bit at a time in opposite directions, and a third wire that is a common signal ground wire.

server

A computer that provides shared resources, such as files and printers, to the network. Used primarily to store data, providing access to shared resources. Usually contains a network operating system.

server/device events

Events occurring on the server or a designated device that meet criteria set by the user.

Server Platform

A server platform shipped with the product or supplied by the customer for the purpose of running the SAN management and Element Manager server applications.

SFP transceivers

See small form factor pluggable transceivers.


287

Glossary

shared mode

If a director or switch is in shared mode, all devices on the loop share the 100MB bandwidth available on the loop. In shared mode, only one end device can communicate with another device through the fabric loop port (FL_Port) on the director or switch.

shortcut menu

The menu that appears when you right-click an icon or the background.

simple mail transfer protocol

SMTP. A transmission control protocol/Internet protocol (TCP/IP) protocol that allows the user to create, send, and receive text messages. SMTP protocols specify how messages are passed across a link from one system to another. They do not specify how the mail application accepts, presents, or stores the mail.

simple network management protocol

SNMP. A transmission control protocol/Internet protocol (TCP/IP)-derived protocol governing network management and monitoring of network devices.

simple network management protocol community

SNMP community. Also known as SNMP community string. SNMP community is a cluster of managed products (in SNMP terminology, hosts) to which the server or managed product running the SNMP agent belongs.

simple network management protocol community name

SNMP community name. The name assigned to a given SNMP community. Queries from an SNMP management station to a device running an SNMP agent will only elicit a response if those queries are addressed with the correct SNMP community name.

simple network management protocol management station

SNMP management station. An SNMP workstation personal computer (PC) used to oversee the SNMP network.

SL_Port

See segmented loop port.

small form factor pluggable transceivers

SFP transceivers. Laser-based optical transceivers for a wide range of networking applications requiring high data rates. The transceivers, which are designed for increased densities, performance, and reduced power, are well-suited for Fibre Channel applications.

SMTP

See simple mail transfer protocol.


Glossary

SNMP

See simple network management protocol.

SNMP community

See simple network management protocol community.

SNMP community name

See simple network management protocol community name.

SNMP management station

See simple network management protocol management station.

SNMP time-out

The maximum amount of time the SANavigator application will wait for a device to respond to a request. The specified time applies to one retry only.

SNMP trap events

SNMP is based on a manager/agent model. SNMP includes a limited set of management commands and responses. The management system issues messages telling an agent to retrieve various object variables. The managed agent sends a Response message to the management system. That message is an event notification, called a trap, that identifies conditions, such as thresholds, that exceed a predetermined value.

state

The state of the switch or director. Possible values include online, offline, testing, and faulty. See offline state; online state.

static random access memory

SRAM. SRAM is microprocessor-cache random access memory. It is built internal to the microprocessor or on external chips. SRAM is fast, but relatively expensive (D). Contrast with dynamic random access memory.

storage area network

SAN. A high-performance data communications environment that interconnects computing and storage resources so that the resources can be effectively shared and consolidated. See also local area network; metropolitan area network; wide area network.

stored addresses

In FICON management style, a method for configuring addresses.


289

Glossary

subnet

A portion of a network that shares a common address component. On transmission control protocol/Internet protocol (TCP/IP) networks, subnets are defined as all devices whose IP addresses have the same prefix. Dividing a network into subnets is useful for both security and performance reasons. IP networks are divided using a subnet mask.

subnet mask

A mask used by a computer to determine whether another computer with which it needs to communicate is located on a local or remote network. The network mask depends upon the class of networks to which the computer is connecting. The mask indicates which digits to look at in a longer network address and allows the router to avoid handling the entire address. Subnet masking allows routers to move the packets more quickly. Typically, a subnet may represent all the machines at one geographic location, in one building, or on the same local area network.

sweep method

A method of sending SNMP requests for information to all the devices on a subnet by sending the request to every device on the network. Sweeping an entire network can take a half an hour or more. If broadcast has been disabled, the recommended method is to enter the individual IP addresses of the SAN devices into the SANavigator application. This method produces good results without unnecessarily using time to wait for responses from every IP address in the subnet, especially for IP addresses where no devices are present. There may, however, be times when a full subnet sweep will produce valuable diagnostic information about the network or a device's configuration.

switch

A device that connects, filters and forwards packets between local area network (LAN) segments or storage area network (SAN) nodes or devices.

switch group

A switch and the collection of devices connected to it that are not in other groups. Switch groups discovered by SAN Manager appear with a gray background on the Physical Map.

switched mode

If the arbitrated loop device is in switched mode, each pair of communicating ports on the arbitrated loop device can share the 100MB bandwidth. In switched mode, up to three pairs of loop devices can communicate with each other simultaneously. Or, a public device on the loop can communicate with another device on the fabric while up to two pairs of loop devices can communicate simultaneously.

switchover

Changing a backup field-replaceable unit (FRU) to the active state, and the active FRU to the backup state.

switch priority

Value configured into each switch in a fabric that determines its relative likelihood of becoming the fabric’s principal switch. Lower values indicate higher likelihood of becoming the principal switch. A


Glossary

value of 1 indicates the highest priority; 225 is the lowest priority. A value of 225 indicates that the switch is not capable of acting as the principal switch. The value 0 is illegal.

System Automation for Operating System/390

SA OS/390™. IBM licensed software that provides System/390 Parallel Sysplex™ management, automation capabilities, and integrated systems and network management. SA OS/390 manages host, remote processor, and I/O operations. SA OS/390 integrates the functions of Automated Operations Control for Multiple Virtual Storage (MVS™), ESCON™ Manager, and Target System Control Facility (D).

TTB

See terabyte.

TCP/IP

See transmission control protocol/Internet protocol.

technical support

Single point of contact for a customer when assistance is needed in managing or troubleshooting a product. Technical support provides assistance 24 hours a day, seven days a week, including holidays. The technical support number is 866.626.5786.

telnet

The Internet standard protocol for remote terminal connection over a network connection.

terabyte

TB. One thousand (1,000) gigabytes; one terabyte of text on paper would consume 42,500 trees. At 12 characters per inch, 1 TB of data in a straight line would encircle the earth 56 times and stretch some 1.4 million miles equalling nearly three round trips from the earth to the moon.

text box

A box in a dialog box into which you can type data.

Threshold Alert Log

Director or switch Threshold Alert Log. Log displayed through the Element Manager application that provides details of threshold alert notifications for an individual director or switch. The log shows the date and time an alert occurred, and shows details about the alert as configured for the product. The information is useful to maintenance personnel for fault isolation and repair verification. See also Audit Log; master log; Hardware Log; Link Incident Log.


291

Glossary

TL_Port

See translated loop port.

topology

Logical and/or physical arrangement of devices on a network.

transfer rate

The speed with which data can be transmitted from one device to another. Data rates are often measures in megabits (Mbps) or megabytes (MBps) per second, or gigabits (Gbps) or gigabytes per second (GBps.

transmission control protocol/Internet protocol

TCP/IP. A layered set of protocols (network and transport) that allows sharing of applications among devices on a high-speed local area network (LAN) communication environment (D). See also Internet protocol.

trap

Unsolicited notification of an event originating from a simple network management protocol (SNMP) managed device and directed to an SNMP network management station.

trap host

Simple network management protocol (SNMP) management workstation that is configured to receive traps.

translated loop port

Connects to a private loop and allows connectivity between the private loop devices and “off loop” devices (devices not connected to that particular TL_Port).

trap recipient

Receiver of a forwarded SNMP trap. Specifically, a trap receiver is defined by an IP address and port to which traps will be sent. Presumably, the actual recipient is a software application running at the IP address and listening to the port.

trap recipient

In simple network management protocol (SNMP), Receiver of a forwarded SNMP trap. Specifically, a trap receiver is defined by an IP address and port to which traps will be sent. Presumably, the actual recipient is a software application running at the IP address and listening to the port.

UUDP

See user datagram protocol.


Glossary

unblocked connection

In a director or switch, the absence of the blocked attribute for a specific port. Contrast with blocked connection. See connectivity attribute. See also; dynamic connection; dynamic connectivity.

unblocked port

Devices communicating with an unblocked port can login to the director or switch and communicate with devices attached to any other unblocked port (assuming that this is supported by the current zoning configuration).

uniform resource locator

URL. A URL is the address of a document or other resource on the Internet.

universal port module

UPM. A flexible 1 gigabit-per-second or 2 gigabit-per-second module that contains four generic ports (G_Ports).

UNIX

A popular multi-user, multitasking operating system originally designed to be a small, flexible system used exclusively by programmers. UNIX was one of the first operating systems to be written in a high-level programming language, namely C. This meant that it could be installed on virtually any computer for which a C compiler existed. Due to its portability, flexibility, and power, UNIX has become the leading operating system for workstations. Historically, it has been less popular in the personal computer market, but the emergence of a new version called Linux is revitalizing UNIX across all platforms.

UPM

See universal port module.

upper level protocol

ULP. Protocols that map to and run on top of the Fibre Channel FC-4 layer. ULPs include Internet protocol (IP) and small computer system interface (SCSI) (D).

URL

See uniform resource locator.

user action events

Actions taken by the user (for example, changes in the SAN, changed settings). Each such action is considered a user action event.

user datagram protocol

UDP. A connectionless protocol that runs on top of Internet protocol (IP) networks. User datagram protocol/Internet protocol (UDP/IP) offers very few error recovery services, instead providing a direct


293

Glossary

way to send and receive datagrams over an IP network. UDP/IP is primarily used for broadcasting messages over an entire network.

Vvendor

Developer or manufacturer of software or hardware.

virtual machine

VM®.

1. A virtual data processing system that appears to be at the exclusive disposal of a single user, but whose functions are accomplished by sharing the resources of a real data processing system.

2. A functional simulation of a computer system and its associated devices, multiples of which can be controlled concurrently by one operating system (D, T).

VM®

See virtual machine.

WWAN

See wide area network.

warning message

A message that indicates a possible error has been detected. See also error message; information message.

wide area network

WAN. A network capable of transmission over large geographic areas that uses transmission lines provided by a common-carrier. See also local area network; metropolitan area network; storage area network.

window

The main window for the SANavigator application. All management and monitoring functions are performed through the SANavigator window.

Windows

A graphical user interface and windowing system introduced by Microsoft Corporation in 1985. Windows runs on top of the MS-DOS operating system (D).


Glossary

workstation

A terminal or microcomputer usually connected to a network or mainframe at which a user can perform applications.

world-wide names

WWN. Eight-byte string that uniquely identifies a Fibre Channel entity (that is, a port, a node, a switch, a fabric), even on global networks.

wrap plug

Synonym for loopback plug.

wrap test

A test that checks attachment or control unit circuitry, without checking the mechanism itself, by returning the output of the mechanism as input. A wrap test can transmit a specific character pattern through a system and compare the pattern received with the pattern transmitted (D).

write authorization

Permission for an simple network management protocol (SNMP) management station with the proper community name to modify writable management information base (MIB) variables.

WWN

See world-wide names.

XXDF

See extended distance feature.

Zzone

Set of devices that can access one another. All connected devices may be configured into one or more zones. Devices in the same zone can see each other. Those devices that occupy different zones cannot. See also zone set; zoning.

zone library

Zoning data that includes zones and zone sets for a fabric.


295

Glossary

zone member

Specification of a device to be included in a zone. A zone member can be identified by the port number of the director or switch to which it is attached or by its port world-wide name (WWN). In multiswitch fabrics, identification of end-devices or nodes by WWN is preferable.

zone set

A collection of zones that may be activated as a unit. See also; zone.

zoning

Grouping of several devices by function or by location. All devices connected to a connectivity product, such as the director or switch, may be configured into one or more zones.

Glossary BibliographyAmerican National Standard Dictionary for Information Systems (ANSI X3.172-1990), copyright 1990 by the American National Standards Institute (ANSI). Copies can be purchased from the American National Standards Institute, 25 West 42nd Street, New York, NY 10036. Definitions from this text are identified by (A).

ANSI/EIA Standard - 440A: Fiber Optic Terminology, copyright 1989 by the Electronic Industries Association (EIA). Copies can be purchased from the Electronic Industries Association, 2001 Pennsylvania Avenue N.W., Washington, D.C. 20006. Definitions from this text are identified by (E).

IBM Dictionary of Computing (ZC20-1699). Definitions from this text are identified by (D).

Information Technology Vocabulary, developed by Subcommittee 1 (SC1), Joint Technical Committee 1 (JTC1), of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). Definitions of published parts of this vocabulary are identified by (I). Definitions taken from draft international standards, committee drafts, and working papers developed by ISO/IEC SC1/JTC1 are identified by (T), indicating that final agreement has not been reached among the participating national bodies of SC1.


– Index –

Index of TermsAActive Directory Services 4Add A Policy dialog box 51Adding a New CIFS Share User 43Authentication 42Authorization 42Automatic Load Balancing 50Available LUNs 56

CChanging CIFS User Password 43CIFS Shares Users 43CLI 105

availableluns 111cluster 113events 115exports 117ipswitches 133lbpolicies 124nodes 126quotas 142snapshots 145storagepools 149users 152volumes 156

CLI Help 108Cluster menu

Force Load Balance 53Nodes 100

Command Line Interface 42, 105Connect to a Node 101Create New Pool 60

DData Management Services 8Destination Volume 80Distributed Lock Management 47

EEvent Log 48

Events 48filter 48log 48

Export Snapshot Schedule 83Exportable 69Extent 60

FFilter Events 49Force a Load Balance 53

GGrid

leave 101Grid Computing 5

IiGrid 3iGrid installation on Linux 18iGrid installation on Windows 10iGrid shortcut icon 17iGrid Support viiiGrid Users 25Installation Options 13IP Address Statistics 90

JJournal Space 35, 65

KKerberos Server 4

LLicense Agreement 11Load Balance

forcing 53Load Balancing 50

automatic 50thresholds 50

Load Balancing Policyassign 52

User’s Guide Crosswalk Storage Manager 297

Index

create 50delete 53

Lock Management 46Logging In 23Logical Unit Number 56LUN 56

available 56limit 56optimization 56remove 57statistics 92

MManagement Users 43Mount a File System 69multi-window environment 24, 88

Nnaming considerations

folder name 80snapshot 80

NetVault 85backups 54

Nodeconnect to another 101

nodefailure 103

Node Maintenance 99Node statistics 89, 94, 96Nodes

add 102configure 99leave grid 101remove 102view 100

nodesshut down all 103

Oon-line support vii

PPerformance 87Phone Support viipool

delete 62expand 61

Pool Semantics 58Pools 30

create new 31display 59

poolsadd 58

Preferences 88

QQuickstart Guide 29Quota Management 44

RRejoin a Node 102Remove a Node 102

Sschedule

snapshot 75Serial Advanced Technology Attachment 6Shareable File System 69Snapshot

export 83snapshot

best practices 76create 79

snapshot frequency 81snapshot schedule

create 79Snapshots 75

create 79Destination Volume 80resume 82Source Volume 80suspend 82

Snapshots page 76Source Volume 80Squash Setting 73Statistics

File System Utilization 88polling rate 88

Statistics menu 87File System 96IP Address 90LUN 92Node 89Storage Pools 94

Storage Manager 7, 30Storage menu 55

Available LUNs 56Create File System 69

298 Crosswalk Storage Manager User’s Guide

Index

Exports 71NetVault 85Quotas 44Snapshots 79Storage Pools 59Volumes 63

Storage Pools window 59Support vii

TTools menu

CIFS Shares Users 43Events 48Load Balancing Policies 50Users 25, 43

Two-Node Grid 102types of users 42

UUniversal Unique IDentifier 56

Users 25Add New 25edit 28

UUID 56

VView menu 88View Nodes 100VIP Locks 47Volume

create 64delete 67expand 67show usage 66

volumeexpand 67

Volumesnew 34, 65

User’s Guide Crosswalk Storage Manager 299

Index

300 Crosswalk Storage Manager User’s Guide

Documents

Users Guide.book