EMA001124-00

DataFRAME® 2112 SAN

Software User’s Guide

DataFRAME® 2112 SAN version 5.1 User Guide

Copyright © 2001-2007 by FalconStor Software. All Rights Reserved.

FalconStor Software, IPStor, TimeView, and TimeMark are either registered trademarks or trademarks of FalconStor Software, Inc. in the United States and other countries.

Linux is a registered trademark of Linus Torvalds.Windows is a registered trademark of Microsoft Corporation.All other brand and product names are trademarks or registered trademarks of their respective owners.

FalconStor Software reserves the right to make changes in the information contained in this publication without prior notice. The reader should in all cases consult FalconStor Software to determine whether any such changes have been made.

Used under license by MPC Computers, LLC.

EMA001124-00, MLW, 10-29-2007

11507.5145

DF2112 User Guide

Contents

IntroductionWhat is DataFRAME® 2112 SAN? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13What makes DataFRAME® 2112 SAN special? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14DF2112 architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15DF2112 components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

InstallationGeneral installation sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Connect DF2112 hardware to your network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17DF2112 Server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18DF2112 Server Console Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Installation on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Installation on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20IInstallation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

DF2112 SAN Client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Pre-installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Windows client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Linux client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Update DF2112 disk ODM fileset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

DataFRAME® 2112 ConsoleStart the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Connect to your DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Configure your DF2112 server using the configuration wizard . . . . . . . . . . . . . . . . . . . .28

Step 1: Enter license keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Step 2: Setup network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Step 3: Set hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Step 4: Configure IPMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

DF2112 Console user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Discover DF2112 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Protect your DF2112 Server’s configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Set Server properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Manage accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Change the root user’s password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Check connectivity between the Server and Console . . . . . . . . . . . . . . . . . . . . . . .46

DF2112 User Guide 1

Contents

Apply software patch updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47System maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Physical Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Physical resource icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Prepare devices to become logical resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Rename a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Rescan adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Import a disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Test physical device throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56SCSI aliasing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Repair paths to a device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Logical Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Logical resource icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Write caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60SAN Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Change the ACSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Grant access to a SAN Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Console options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Create custom menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Storage PoolsManage storage pools and the devices within storage pools . . . . . . . . . . . . . . . . . . . . .66Create storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Set properties for a storage pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

DF2112 Logical ResourcesTypes of SAN Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Virtual devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Direct devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Service enabled devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Create SAN Resources - Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Prepare devices to become SAN Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Create a virtual device SAN Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Create a direct device or service enabled device SAN Resource . . . . . . . . . . . . . .81

Assign a SAN Resource to one or more clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84After client assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89Windows clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Expand a virtual device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Grant access to a SAN Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Unassign a SAN Resource from a client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93Delete a SAN Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

DF2112 ServerStart the DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

DF2112 User Guide 2

Contents

Stop the DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96Log into the DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

telnet access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96Check the DF2112 Server processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Check physical resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98Check activity statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 Uninstall the DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

iSCSI ClientsSupported platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Configuring iSCSI clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Enable iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103Configure your iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103Add your iSCSI client in the DF2112 Console . . . . . . . . . . . . . . . . . . . . . . . . . . . .104Create storage targets for the iSCSI client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Restart the iSCSI initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

Understanding CHAP authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107Windows iSCSI clients and failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Disable iSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Logs and ReportsEvent Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110

Sort information in the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Filter information stored in the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Refresh the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Print/Export Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113Create a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113View a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115Export data from a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Report types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116Server Throughput and Filtered Server Throughput Report . . . . . . . . . . . . . . . . .116Client Throughput Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118SCSI Channel Throughput Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119SCSI Device Throughput Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121SAN Client Usage Distribution Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122SAN Resource Usage Distribution Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Physical Resources Configuration Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124DF2112 Disk Space Usage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Physical Resources Allocation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125Physical Resource Allocation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126SAN Client/Resources Allocation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126SAN Resources Allocation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127Delta Replication Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127FileSafe Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

DF2112 User Guide 3

Contents

SecuritySystem management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130Data access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130Security recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

Storage network topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Physical security of machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132Disable ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

FailoverOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134

Network connectivity failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Storage device path failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Storage device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137DF2112 Server failure (including storage device failure) . . . . . . . . . . . . . . . . . . . .137

Failover overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139Cross mirror failover sample configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

Failover requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142General failover requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142General failover requirements for iSCSI clients . . . . . . . . . . . . . . . . . . . . . . . . . . .143

Failover restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Failover setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146Power Control options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158Check Failover status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161After failover occurs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

Manual recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Special note about Windows client recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162Auto recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Fix a failed server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163

Recover from a cross mirror disk failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164Re-synchronize cross mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164Check resources and swap if possible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164Verify and repair a cross mirror configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

Modify failover configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169Make changes to the servers in your failover configuration . . . . . . . . . . . . . . . . . .169Convert a failover configuration into a mutual failover configuration . . . . . . . . . . .169Exclude physical devices from health checking . . . . . . . . . . . . . . . . . . . . . . . . . . .170Change your failover intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170Convert a failover configuration from Symmetric to Asymmetric mode . . . . . . . . .171Verify physical devices match . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171

Start/stop failover or recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172Force a takeover by a secondary server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172Manually initiate a recovery to your primary server . . . . . . . . . . . . . . . . . . . . . . . .172Suspend/resume failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172

Remove a failover configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173Mirroring and Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174TimeMark/CDP and Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174

DF2112 User Guide 4

Contents

MirroringSynchronous Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175Asynchronous Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176Mirror requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177Mirror setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177Create cache resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184Check mirroring status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185Swap the primary disk with the mirrored copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186Promote the mirrored copy to become an independent virtual drive . . . . . . . . . . . . . .186Recover from a mirroring hardware failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187Replace a disk that is part of an active mirror configuration . . . . . . . . . . . . . . . . . . . . .187Replace a failed physical disk without rebooting your DF2112 Server . . . . . . . . . . . . .188Expand the primary disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Manually synchronize a mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Rebuild a mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189Suspend/resume mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190Change your mirroring configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

Set global mirroring options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Remove a mirror configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191Mirroring and Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

Near-line MirroringBefore you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193Near-line mirroring requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193Near-line mirroring setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194What’s next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202Check near-line mirroring status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203Recover data from a near-line mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204Swap the primary disk with the near-line mirrored copy . . . . . . . . . . . . . . . . . . . . . . . .207Expand the primary disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207Manually synchronize a near-line mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207Rebuild a near-line mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207Suspend/resume near-line mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208Change your mirroring configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208

Set global mirroring options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208Remove a near-line mirror configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209Recover from a mirroring hardware failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210Replace a disk that is part of an active near-line mirror . . . . . . . . . . . . . . . . . . . . . . . .210Replace a failed physical disk without rebooting your DF2112 Server . . . . . . . . . . . . .211

SnapshotCreate a Snapshot Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213Check status of a Snapshot Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220Protect your Snapshot Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220Options for Snapshot Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221

DF2112 User Guide 5

Contents

Use Snapshot to copy a SAN or NAS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222Check Snapshot Copy status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225

Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226Create a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226Groups with TimeMark/CDP enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227Groups with SafeCache enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227Groups with replication enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

Grant access to a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228Add resources to a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229Remove resources from a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

TimeMark/CDPOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233Check TimeMark status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238Check CDP journal status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238Protect your CDP journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240Add a tag to the CDP journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240Add a comment or change priority of an existing TimeMark . . . . . . . . . . . . . . . . . . . . .241Manually create a TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242Copy a TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243Recover data using the TimeView feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244Remap a TimeView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248Roll back or roll forward a drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248Change your TimeMark/CDP policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250Suspend/resume CDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250Delete TimeMarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250Disable TimeMark and CDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251Replication and TimeMark/CDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251

ReplicationOverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252

Remote replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252Local replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252How replication works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253Delta replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253Continuous replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253

Replication configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .254Create a Continuous Replication Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263

Check replication status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265Replication tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Replication object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Delta Replication Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

DF2112 User Guide 6

Contents

Replication performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268Set global replication options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268Tune replication parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268

Assign clients to the replica disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269Switch clients to the replica disk when the primary disk fails . . . . . . . . . . . . . . . . . . . .269Recreate your original replication configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270Use TimeMark/TimeView to recover files from your replica . . . . . . . . . . . . . . . . . . . . .271Change your replication configuration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271Suspend/resume replication schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272Stop a replication in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272Manually start the replication process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272Reverse a replication configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273Reverse a replica when the primary is not available . . . . . . . . . . . . . . . . . . . . . . . . . . .273Relocate a replica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274Remove a replication configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275Expand the size of the primary disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275Replication with other DF2112 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276

Replication and TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276Replication and Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276Replication and Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276

PerformanceSafeCache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277

Configure SafeCache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278Create a cache resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279Check the status of your SafeCache cache resource . . . . . . . . . . . . . . . . . . . . . .282SafeCache properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282Disable your SafeCache cache resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282If a disk has failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282

HotZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283Read Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283Prefetch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284Configure HotZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284Check the status of HotZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289Disable HotZone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290

Disk striping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291Configure Disk Striping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291

Zero Impact BackupConfigure ZeroImpact backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293Back up a DF2112 logical resource using dd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296Restore a volume backed up using ZeroImpact Backup Enabler . . . . . . . . . . . . . . . . .297

IP TrunkingInstalling IP Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299

DF2112 User Guide 7

Contents

Launching the IP Trunking installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .299Installation options and prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300Initial installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300Automatic configuration option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .301Manual configuration option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302Load IP Trunking on boot-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303If you change network configuration or restart network while IP Trunking is loaded 303

Using IP Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304IP Trunking Console - nexcui . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304IP Trunking Java Console – nexjui . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .305Current status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .306Current statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .307Unloading IP Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310Setting the IP Address of the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310Using Nexconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310Navigation keys used in nexconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314Uninstalling IP Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314

MultipathingPath switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316Load distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316Preferred paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316Path management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317Set autopathing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318Set alias list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320Unbind physical devices from SCSI aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321

SNMP IntegrationTraps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322Implement SNMP support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323HP OpenView Network Node Manager 6.1 and 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . .324

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325Statistics in NNM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325

CA Unicenter TNG 2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327View traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328Statistics in TNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328Launch the DF2112 Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328

IBM Tivoli NetView 6.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330Statistics in Tivoli . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .331

BMC Patrol 3.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332

DF2112 User Guide 8

Contents

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332View traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333Statistics in Patrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333

Advanced topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335The snmpd.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335Use an SNMP configuration for multiple DF2112 Servers . . . . . . . . . . . . . . . . . . .335

Command Line InterfaceInstallation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .336Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .336Common arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .337Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338Login/logout to the DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338

Log in to the DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .338Log out from the DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339

Server commands for virtual devices and clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340Create virtual device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .340Get virtual device list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343Get client virtual device list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .343Assign virtual device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .344Unassign virtual device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345Delete virtual device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345Expand virtual device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346Set assigned virtual device properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347Add client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .347Delete client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348Add client protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348Disable client protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349Get virtual device ID by serial number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350

SAN Client commands for virtual devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351Attach to virtual device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351Detach from virtual device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352Rescan devices assigned to client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352Get virtual device attached state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .353Get virtual device status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .353

Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .354Create mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .354Get mirror status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355Sync mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355Swap mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355Promote mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355Remove mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .356Migrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357

Snapshot resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358Create snapshot resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358Delete snapshot resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359Expand snapshot resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359Set snapshot policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360

DF2112 User Guide 9

Contents

Get snapshot policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .360Cache resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361

Create a cache resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361Get cache resource status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361Set cache resource properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362Get cache resource properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362Suspend a cache resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363Resume a cache resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363Delete a cache resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363

Snapshot Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365Create Snapshot Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365Get Snapshot Copy status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366

Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367Create a replica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367Start replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369Stop replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369Suspend replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369Resume replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369Promote the replica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370Remove replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370Get replication status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371Set replication properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371Get replication properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372Relocate replica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373Scan replica . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373

TimeMark/CDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374Enable TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374Create TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376Disable TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376Update TimeMark information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377Delete TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378Copy TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378Select TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379Deselect TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379Rollback TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379Get TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380Set TimeMark properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .380Get TimeMark properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .382Get TimeMark status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .383Create TimeView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .383Remap TimeView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384Suspend CDP journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385Resume CDP journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385Get CDP journal status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385Get CDP journal info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385Create CDP journal tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .386Get CDP journal tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .386

Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .387Enable backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .387

DF2112 User Guide 10

Contents

Disable backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388Set backup properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .388Get backup properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389Stop backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .389

Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390Create a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390Get groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392Delete device from a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392Delete a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393Enable replication for a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .393Disable replication for a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Set group replication properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Get group replication properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Enable TimeMark for a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Disable TimeMark for a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Set group TimeMark properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Get group TimeMark properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Enable backup for a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Disable backup for a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395Set group backup properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .396Get group backup properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .396

Physical devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .397Get physical device information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .397Rescan physical devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .398Import physical device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .398Prepare physical device for DF2112 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .399

X-Ray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .400Get X-Ray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .400

Report data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401Get report data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .401

Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403Get Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403

Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .404Get Failover status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .404

Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .405Save configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .405Restore configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .405

Users and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .406Add user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .406Set user password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .406

iSCSI targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .407Create iSCSI target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .407Set iSCSI target properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .407Get iSCSI target information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .407Assign iSCSI target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .408Unassign iSCSI target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .408Delete iSCSI target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .409

Client properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .410Set iSCSI client properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .410


Contents

Set Fibre Channel client properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .410Get client properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .410

BootIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .411Enable BootIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .411Disable BootIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .411Get BootIP properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .411Set BootIP properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .412

CallHomeConfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .413Modifying CallHome properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .420Script/program trigger information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .421

TroubleshootingSCSI adapters and devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .423Console launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .426Logical resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427Console login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427Network connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .428

Jumbo frames support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .429Client connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .429

Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .430Windows client debug information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .431Clients with SAN/IP or iSCSI protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .432Linux SAN Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .432NetWare SAN Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .433

DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .434X-ray of the DF2112 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .434Specific problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .434

Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .435Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .435TimeMark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .436SafeCache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .436SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .436Command line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .437Service enabled devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .437Snapshot resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .437Physical resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .438Block devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .438Virtual device expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .438

Index


DF2112 User Guide

IntroductionThe explosion of data in today’s networked computing environments stresses the abilities of many Information Technology groups while the demand to store and access data doubles each year.

Since information, and the storage infrastructure that holds it, are critical to a company’s success, the management of the storage becomes a serious issue, where reliability, availability and improved disaster recovery are all key factors.

Documents, databases, web pages, and other sorts of media each have their own rules for accessibility, retention and backup. Estimates of the cost to manage storage range from 5 to 10 times the actual cost of the storage hardware itself.

The Storage Area Network (SAN) is a dedicated network devoted to data storage and is a solution that meets the storage requirements of many businesses today. SANs address many of the reliability and availability issues for data storage. Essentially, SANs apply networking methodologies to the problems of storage, expanding the management possibilities for storage.

What is DataFRAME® 2112 SAN?

DataFRAME® 2112 SAN (DF2112) is an award-winning comprehensive suite of enterprise class storage services, as well as an integrated platform for both SAN and NAS – all under one centralized management interface across multi-vendor and multi-platform environments. With the DF2112, IT managers can build a new storage network or build intelligence into their current infrastructure.

DF2112's flexible design offers unprecedented freedom when architecting networked storage environments. You can pool your storage resources or choose DF2112's Storage Service Enabler option to add enterprise class storage services to new or existing SANs without copying and virtualizing existing data.

Developed by a team of world-class network and storage management experts, DF2112 provides your enterprise applications with the widest array of the most advanced storage services – so that your mission-critical data is always available, quickly accessible, and easily recoverable with point-in-time integrity in the event of anything from small mishaps to major disasters.

With an unprecedented combination of manageability, performance, security, and flexibility, DataFRAME® 2112 SAN takes the complexity and expense out of storage networking and management and maximizes the availability and recoverability of data for all of your business-critical applications.


Introduction

What makes DataFRAME® 2112 SAN special?

DF2112 offers enterprises an easy way to purchase, implement, and support new or existing enterprise SANs, while containing the costs associated with the ownership and management of storage solutions. Building a DF2112 storage network puts enterprise class storage services at your fingertips, allowing you to do more with less.

• Provides total freedom in host/storage connectivity: Fibre Channel, iSCSI, SCSI, JBOD, RAID, Solid state (RAM) disk, tape/library. Because DF2112 scales easily and encompasses all protocols and standards (current and upcoming), it is not just a tool, but an entire future-proof system.

• Reduces management costs by leveraging existing IT infrastructures and know-how.

• Cuts capital investment by consolidating storage resources for maximized utilization and efficiency.

• Dramatically lowers storage administration overhead through centralized, simplified storage management.

• Eliminates requirement for multiple software licenses and individual management of storage software for each server.

• Maximizes performance for high bandwidth applications.• Provides total storage security with key-based authentication.

These benefits are all integrated into the DF2112 Server, an intelligent storage processor capable of supporting high performance storage I/O in a complex data management environment. The DF2112 solution delivers cost-effective, easy-to-use, flexible, rapidly deployable solutions for storing, managing, and migrating data.


Introduction

DF2112 architecture

The DF2112 storage network can be either a dedicated storage network, just like traditional Fibre Channel SANs, or it can be embedded into the existing LAN for small or low impact applications. Although MPC recommends that a separate network segment be dedicated to the Storage Network, this flexibility allows the building and testing of different topologies, the scaling of the Storage Network, and the sharing of networking resources to suit the varied requirements of different computing environments.

This diagram shows the components of the DF2112 system and how they might be connected. Since DF2112 is flexible, you may decide to configure the components differently for your requirements.


Introduction

DF2112 components

The primary components of the DF2112 Storage Network are the DF2112 Server, DF2112 SAN Clients, DF2112 NAS Clients, and the DF2112 Console. These components all sit on the same network segment, the storage network.

Server The DF2112 Server is a dedicated network storage server. The DF2112 Server is attached to the physical SCSI and/or Fibre Channel storage devices on one or more SCSI or Fibre Channel busses.

The job of the DF2112 Server is to communicate data requests between the clients and the logical (SAN and NAS) resources (logically mapped storage devices on the storage network) via Fibre Channel or iSCSI.

SAN Clients DF2112 SAN Clients are the actual file and application servers. MPC calls them DF2112 SAN Clients because they utilize the storage resources via the DF2112 Server.

There are three types of SAN Clients, iSCSI, Fibre Channel, and SAN/IP. You can have all of them on your storage network.

These SAN Clients access their storage resources via iSCSI initiators (for iSCSI), HBAs (for Fibre Channel or iSCSI), or software-emulated virtual adapters (for SAN/IP). The storage resources appear as locally attached devices to the SAN Clients’ operating systems (Windows XP, Windows 2000, Linux, Solaris, etc.) even though the SCSI devices are actually located at the DF2112 Server.

NAS Clients NAS Clients are the Windows/Unix users and groups that access data and storage (if authorized) on the storage network via standard operating system network mapping protocols.

Console The DF2112 Console is the administration tool for the DF2112 storage network. It is a Java application that can be used on a variety of platforms and allows DF2112 administrators to create, configure, manage, and monitor the storage resources and services on the DF2112 storage network.


DF2112 User Guide

Installation

General installation sequence

The installation of the DF2112 storage network involves several steps. They are outlined below:

1. Connect DF2112 hardware to your network.

2. Install the IPStor Server(s).

3. Install the IPStor Console.

4. Install the IPStor SAN Client(s).

Connect DF2112 hardware to your network

The DF2112 components, DF2112 Servers and DF2112 SAN Clients, need to be connected together in an Ethernet network.

For small systems, DF2112 components can be introduced directly onto an existing network. For larger storage networks, they are usually separated from the normal LAN traffic. This separate network segment is referred to as the Storage Area Network (SAN).

Even larger networks can be created using almost any type of Ethernet hardware.

The servers and clients connect through Gigabit Ethernet switches. Please refer to your switches’ and adapters’ documentation for proper configuration of these devices.

If the DF2112 components are on a SAN, the SAN Clients will use separate Ethernet adapters to connect to the rest of your network.

Note: We recommend that all switches and NICs be configured to use jumbo frames (data transfer size of 9000 MTUs) if enhanced network performance is preferred. If compatibility between Ethernet hardware from different manufacturers is more important, non-jumbo frame sizes may be used. Note that jumbo frame sizes do not include overhead, which must be adjusted accordingly based on recommendations from switch and NIC manufacturers.


Installation

DF2112 Server installationThe DF2112 Server is the central component of the DF2112 storage network. It connects to storage devices via industry-standard SCSI adapters and to application servers via standard Ethernet infrastructures.

Pre-installation

Please check the following list for the DF2112 Server requirements, including which operating system is currently supported. While this information is accurate as of the date of its release, you should check the certification matrix on the MPC website for any updates.

Importantinformation

The DF2112 Server’s boot drive can only be used for the DF2112 Server software and activity logs. Storage on this drive cannot be used for logical resources.

Verifyconnection to

network

Before installing the DF2112 Server software, we recommend that you connect the server machine to your Gigabit Ethernet switch so that you can verify that it is physically connected to the network. This procedure will allow you to diagnose and resolve networking issues before you start to configure the DF2112 software.

CPU AMD Opteron and Intel Xeon EM64T are supported.

Memory 1 GB RAM minimum. 4 GB RAM is recommended.

Operating system SUSE Linux Professional 9.3 or Red Hat Linux Advanced Server 4 update 2

Host name (If you are using NAS with an Active Directory server) Due to NetBIOS limitations, the DF2112 Server must have a hostname that is no longer than 15 characters. Refer to http://support.microsoft.com/kb/q188997/ for details on NetBIOS naming. Note that DNS naming restrictions also apply.

SCSI adapter(s) MPC recommends the use of Ultra-160 SCSI adapters, including the Adaptec Ultra160 family of adapters. DF2112 supports all SCSI adapters supported by Linux.

Network card (for SAN/IP Client support)

MPC recommends the use of Gigabit Ethernet network cards. These cards include Alteon Web Systems’ ACENic controllers. DF2112 supports all Ethernet cards supported by Linux.

Hard disk SCSI/IDE hard drive with at least 100 MB disk space available.

CD-ROM drive SCSI or IDE CD-ROM drive.


Installation

DF2112 Server Console Installation

The DF2112 Console is the administrative tool that allows DF2112 administrators to create, configure, manage, and monitor the storage resources on the DF2112 storage network.

The DF2112 Console is a Java application that can be run on many Windows, Linux, and Solaris platforms that support the Java 2 Runtime Environment (JRE) version.

Pre-installation

The computer that runs the Console needs connectivity to the Storage Network segment. This is because it communicates directly with the server and clients to administer and monitor their behavior. The Console may be installed on any number of machines, including the clients themselves, provided that they have a Graphical User Interface.

Memoryrequirement

The Console can be run on computers with 512 MB RAM, but for optimal performance, 1 GB RAM is recommended. When running the Console on Solaris, we recommend that the Solaris machine have 512 MB RAM and a swap size of 512MB.

Installation on Windows

The installation CD includes a setup program for installation on Windows computers.

On Windows 2000, you must be a Power User or Administrator to install the Console.

1. Insert the DF2112 installation CD into your CD-ROM drive.

2. Select Install Products --> Install DF2112 Console.

If the CD Browser does not launch, navigate to the \Console\Windows directory and run ISinstall.exe to launch the DF2112 Console install program.

3. To launch the Console, select Start --> Programs --> DF2112 --> DF2112 Console.

The Console will not launch if the install path contains characters such as !, %, {, }.


Installation

Installation on Linux

For Linux, you will need to manually install the DF2112 Console.

1. To install the Console software, log into your system as the root user.

2. Mount the DF2112 installation CD to an available or newly created directory and copy the files from the /Console/Linux directory on the CD to a temporary directory.

3. Type the following command to install the Console software:

For example:

The Console will be installed in the following location: /user/local/df2112console

4. To launch the Console, execute the following:

The Console will not launch if the install path contains characters such as !, %, {, }.

Note: In order to run the Console on Linux, you must be in the X Windows GUI.

IInstallation verification

You can verify the DF2112 Console installation by running the Console and attempting to connect to an existing DF2112 Server. You will be able to connect to the DF2112 Server by using the root user’s password.

rpm –i <file name from installation CD>

rpm –i df2112console-4.50-0.901.i386.rpm

cd /usr/local/df2112console./df2112console


Installation

DF2112 SAN Client installation

DF2112 SAN Clients access their storage resources via iSCSI initiators (for iSCSI), HBAs (for Fibre Channel or iSCSI), or software-emulated virtual adapters (for SAN/IP). The storage resources appear as locally attached devices to the SAN Clients’ operating systems (Windows XP, Windows 2000, Linux, Solaris, etc.) even though the SCSI devices are actually located at the DF2112 Server.

Pre-installation

DF2112 provides client software for many platforms and protocols. Please check the certification matrix on the MPC website for the versions and the patch levels (if applicable) that are currently supported.

Notes:

• The DF2112 Client should not be installed onto a network drive.• For an iSCSI or Fibre Channel client, you do not need to install any SAN

Client software unless the client is using a MPC snapshot agent or the client is using multiple protocols. If you do need to install SAN Client software for a Fibre Channel client, do not install it until your Fibre Channel configuration is underway. For more information, refer to “Fibre Channel Target Mode”.

• Client software requires network connectivity to the DF2112 Server, preferably on a separate, DF2112-only network. This means that normal LAN traffic does not occur on the adapter(s) dedicated to the DF2112 storage network.

Windows client installation

The Windows Intelligent Management Administrator (IMA)/SAN Disk Manager (SDM) will automatically be installed with a MPC Snapshot Agent and with DiskSafe. It is not required otherwise but it can be installed and used as a management tool directly from the CD. Note that IMA/SDM does not support the SAN/IP protocol.


Installation

Linux client installation

For Linux, the SAN Client software is separated into two components, the user mode and the kernel mode. For Fibre Channel and iSCSI, you only need to install the user mode. This allows the SAN Client software to be independent of the kernel version of the operating system. For SAN/IP, you will have to install both modes because the kernel mode includes a SAN/IP driver.

Note: You should not install the Linux client on a DF2112 Server machine. The DF2112 Server installation includes a local Linux Client to service NAS Resources. If the Linux Client were to be installed on an existing DF2112 Server, all access to NAS Resources would be lost.

1. Make sure that the DF2112 Servers the client will use are all up and running.

2. Prior to installing the DF2112 SAN Client for Linux, assign SAN Resources to the client machine.

To do this, use the Assign a SAN Resource Wizard in the Console. When you are asked to select the SAN Client, click the Add button and type in the name of the Linux machine. The name must match the output of “uname –n” from the client machine.

For more information, refer to the section ‘Assign a SAN Resource to one or more clients’.

3. To install the client software, log into your system as the root user.

4. Mount the DF2112 installation CD to an available or newly created directory and copy the files from the CD to a temporary directory on the machine.

The software packages are located in the /client/linux/ directory off the CD.

5. Type the following command to install the client software:

For example:

The client will be installed to the following location: /usr/local/df2112client

It is important that you install the client to this location. Installing the client to a different location will prevent the client driver from loading.

6. If you will be using the SAN/IP protocol, type the following command to install the SAN/IP driver:

For example:

rpm -i <full path>/df2112client-<version>-<build>.i386.rpm

rpm -i /mnt/cdrom/Client/Linux/df2112client-4.50-0.954.i386.rpm

rpm -i df2112client-driver-<version>-<build>.i386.rpm

rpm -i df2112client-driver-4.50-0.954.i386.rpm


Installation

After installation 1. Log into the client machine as the root user again so that the changes in the user profile will take effect.

2. Add the DF2112 Servers that this client will connect to for storage resources by typing the following command from /usr/local/df2112client/bin:

3. Select Add a DF2112 Server from the menu and enter the DF2112 Server name, login ID and password.

After this server is added, you can continue adding additional servers.

4. To start the Linux client, type the following command from the /usr/local/df2112client/bin directory:

Update DF2112 disk ODM fileset

Delete existingDF2112devices

If you have existing DF2112 devices, they must all be removed before the ODM fileset is updated.

1. Use the following command to check if you have existing DF2112 devices.# lscfg -v

You will see output similar to the following:

You can see from this example that there are two DF2112 devices, hdisk1 and hdisk2.

2. Use the rmdev -l and rmdev -dl commands to remove each of the DF2112 devices.

The rmdev -l command closes the device and the rmdev -dl comand removes the device from ODM. # rmdev -l hdisk1 # rmdev -dl hdisk1

./df2112client monitor

./df2112client start

fscsi1 P1.1-I1/Q1 FC SCSI I/O Controller Protocol Device hdisk1 P1.1-I1/Q1-W210000E08B058C20-L0 Other FC SCSI Disk Drive

Manufacturer................FALCON Machine Type and Model......DF2112 DISK ROS Level and ID............76312E30 Device Specific.(Z0)........000003121F000032

hdisk2 P1.1-I1/Q1-W210000E08B07CEA7-L0 Other FC SCSI Disk Drive

Manufacturer................FALCON Machine Type and Model......DF2112 DISK ROS Level and ID............76312E30 Serial Number...............8UYRRGUU Device Specific.(Z0)........000002122F000032


Installation

# rmdev -l hdisk2# rmdev -dl hdisk2


Installation

Install the ODMfileset

1. Unzip the df2112disk.tar.gz file from the installation CD.# gunzip -dc df2112disk.tar.gz | tar -xvf -

2. Install the ODM fileset with the following command:# installp -ad df2112disk.rte all

3. Rescan the configuration using the following command:# cfgmgr -v

4. Verify the configuration using the following command:# lsdev -Cc disk

The DF2112 disks that originally displayed the name Other FC SCSI Disk Drive will now be displayed as DF2112 Disk Drive:hdisk1 Available 10-68-01 DF2112 Disk Drive


Installation


DF2112 User Guide

DataFRAME® 2112 Console

The DataFRAME® 2112 SAN (DF2112) Console is the administration tool for the DF2112 storage network. It is a Java application that can be used on a variety of platforms and allows DF2112 administrators to create, configure, manage, and monitor the storage resources and services on the DF2112 storage network as well as run/view reports, enter licensing information, and add/delete DF2112 administrators.

Start the ConsoleOn Windows, select Start --> Programs --> DF2112 --> DF2112 Console.

On Linux and other UNIX environments, execute the following:

Notes:

• If your screen resolution is 640 x 480, the splash screen may be cut off while the Console loads.

• The Console might not launch on certain systems with display settings configured to use 16 colors.

• The Console needs to be run from a directory with “write” access. Otherwise, the host name information and message log file retrieved from the DF2112 Server will not be able to be saved to the local directory. As a result, the Console will display event messages as numbers and Console options will not be able to be saved.

Connect to your DF2112 Server1. Discover all DF2112 servers on your storage subnet by selecting Tools -->

Discover DF2112 Servers.

2. Connect to a DF2112 server.

You can connect to an existing DF2112 Server, by right-clicking on it and selecting Connect. Enter a valid user name and password (both are case sensitive).

If you want to connect to a server that is not listed, right-click on the DF2112 Servers object and select Add, enter the name of the server, a valid user name and password.

When you connect to a server for the first time, a configuration wizard is launched.

cd /usr/local/df2112console./df2112console



You may see a dialog box notifying you of new devices attached to the server. Here, you will see all devices that are either unassigned or reserved devices. At this point you can either prepare the device (reserve it for a virtual, direct, or service enabled device) and/or create a logical resource.

Once you are connected to a server, the server icon will change to show that you are connected:

If you connect to a server that is part of a failover configuration, you will automatically be connected to both servers.

Note: Multiple administrators can access a server at the same time. Changes to the server’s configuration are saved on a first-come, first-served basis.

The DF2112 Console remembers the DF2112 Servers to which the Console has successfully connected. If you close and restart the Console, the DF2112 Servers will still be displayed in the tree but you will not be connected to them.

Configure your DF2112 server using the configuration wizardDF2112 provides a convenient wizard that leads you through entering license keycodes and setting up your network configuration. If this is the first time you are connecting to your DF2112 server, you will see one of the following:

Step 1: Enter license keys

Click the Add button and enter your keycodes.

Be sure to enter keycodes for any options you have purchased. Each DF2112 option requires that a keycode be entered before the option can be configured and used. Refer to ‘Licensing’ for more information.

Configuration note: After completing the configuration wizard, if you need to add license keycodes, you can right-click on your DF2112 server appliance and select License.

You will only see step 4 if DF2112 detected IPMI when the server booted up.



Step 2: Setup network

Enter information about your network configuration.

If you need to change DF2112 Server IP addresses, you must make these changes using System Maintenance --> Network Configuration in the Console. Using yast or other third-party utilities will not update the information correctly.

Refer to ‘Network configuration’ for more information.

Configuration note: After completing the configuration wizard, if you need to change these settings, you can right-click on your DF2112 server appliance and select System Maintenance --> Network Configuration.

Step 3: Set hostname

Enter a valid name for your DF2112 appliance.

Valid characters are letters, numbers, underscore, or dash.

You will need to restart the server if you change the hostname.

Note: Do not change the hostname if you are using block devices. If you do, all block devices claimed by DF2112 will be marked offline and seen as foreign devices.

Configuration note: After completing the configuration wizard, if you need to change the name again, you can right-click on your DF2112 server appliance and select System Maintenance --> Set hostname.

Step 4: Configure IPMI

(This step is only available if DF2112 detected IPMI when the server booted up.) Intelligent Platform Management Interface (IPMI) is a hardware level interface that monitors various hardware functions on a server.

You can set IPMI information, including the channel number and IP address that the IPMI connection is using. Click the Setting button to see the current settings. If they are all correct, you do not have to enter anything.

Refer to ‘IPMI’ for more information.

Configuration note: After completing the configuration wizard, if you need to change the IPMI settings, you can right-click on your DF2112 server appliance and select System Maintenance --> IPMI.



DF2112 Console user interface

The DF2112 Console displays the configuration for the DF2112 Servers on your storage network. The information is organized in a familiar Explorer-like tree view.

The tree allows you to navigate the various DF2112 Servers and their configuration objects. You can expand or collapse the display to show only the information that you wish to view. To expand an item that is collapsed, you can click on the symbol next to the item. To collapse an item, click on the symbol next to the item. Double-clicking on the item will also toggle the expanded/collapsed view of the item.

You need to connect to a server before you can expand it.

When you highlight an object in the tree, the right-hand pane contains detailed information about the object. You can select one of the tabs for more information.

The Console log located at the bottom of the window displays information about the local version of the Console. The log features a drop-down box that allows you to see activity from this Console session.

Search forobjects in the

tree

The Console has a search feature that helps you find any physical device, virtual device, or client on any DF2112 Server. To search:

1. Highlight a DF2112 Server in the tree.

2. Select Edit menu --> Find.

3. Select the type of object to search for and the search criteria.

Once you select an object type, a list of existing objects appears. If you highlight one, you will be taken directly to that object in the tree.

Alternatively, you can type the full name, ID, ACSL (adapter, channel, SCSI, LUN), or GUID (Global Unique Identifier). Once you click the Search button, you will be taken directly to that object in the tree.



DF2112 Server

This display shows the configuration and status of the DF2112 Server. Configuration information includes the version of the DF2112 Server software and base operating system, the type and number of processors, amount of physical and swappable memory, supported protocols, and network adapter information.

The Event Log tab displays system events and errors.

Discover DF2112 Servers

DF2112 can automatically discover all DF2112 Servers on your storage subnet.

1. Select Tools --> Discover DF2112 Servers.

2. Enter your network criteria.



Protect your DF2112 Server’s configuration

DF2112 provides several convenient ways to protect your DF2112 configuration. This is useful for disaster recovery purposes, such as when a DF2112 Server is out of commission but you have the storage disks and want to use them to build a new DF2112 Server.

Continuouslysave

configuration

You can create a configuration repository that maintains a continuously updated version of your DF2112 system configuration. This feature works seamlessly with the DF2112 Failover option to provide business continuity in the event that a DF2112 Server fails. For additional redundancy, the configuration repository can be mirrored to another disk. Each configuration repository will be 200 MB in size.

To create a configuration repository:


2. Right-click on the server and select Options --> Enable Configuration Repository.

3. Select how you want to create the repository.

Custom lets you select which physical device(s) to use and lets you designate how much space to allocate from each.

Express automatically creates a repository using any available device.

4. Confirm all information and click Finish to create the repository.

You will now see a Configuration Repository object in the tree under Logical Resources.

To mirror the repository, right-click on it and select Mirror --> Add.

If you are using the DF2112 Failover option and a DF2112 Server fails, the secondary server will automatically use the configuration repository to maintain business continuity and service clients.

If you are not using the DF2112 Failover option, you will need to contact technical support when preparing your new DF2112 Server.

Auto saveconfiguration

You can set your system to automatically replicate your system configuration to an FTP server on a regular basis. Auto Save takes a point-in-time snapshot of the DF2112 configuration prior to replication. To use Auto Save:

1. Right-click on the server and select Properties.

2. Select the Auto Save Config tab and enter information automatically saving your DF2112 system configuration.

For detailed information about this dialog, refer to the ’Auto Save Config’ section.



Manually saveconfiguration as

needed

You can manually save your system configuration any time you make a change in the Console, including any time you add/change/delete a client or resource, assign a client, or make any changes to your failover/mirroring/replication configuration. If you add a server to a client from the Client Monitor (or via command line for Unix clients), you should also re-save your configuration.

To do this:


2. Select File menu --> Save Configuration.

3. Select a filename and location.

Creating a folder only supports single byte characters. For double byte characters, create a folder from Explorer before saving the configuration.

Restoreconfiguration

You can restore a DF2112 Server configuration from a file that was created using the Save Configuration option. This is for disaster recovery purposes and should not be used in day-to-day operation of the server. Changes made since the configuration was last saved will not be included in this restored configuration.

Warning: Restoring a configuration will overwrite existing virtual device and client configurations for that server. DF2112 partition information will not be restored. This feature should only be used if your configuration is lost or corrupted, as lost virtual devices can result in lost data for the clients using those virtual devices.

To restore the configuration:

1. Import the disk(s) that were recovered from the damaged DF2112 Server to your new DF2112 Server.

Refer to ‘Import a disk’ for more information.

2. Highlight the new DF2112 Server in the tree.

Note: Do not make any changes to the server before restoring the configuration. For example, do not enable NAS before restoring, even if this server previously used NAS.

3. Select File menu --> Restore Configuration.

4. Confirm and locate the file that was saved.

The DF2112 Server will be restarted.

5. If any physical or virtual devices were changed after the configuration was saved, you must rescan (right-click on Physical Resources and select Rescan) to update the newly restored configuration.



Licensing

To license DF2112 Server and its options:

1. Obtain your DF2112 keycode(s) from MPC Technical Support.

2. In the Console, right-click on the server and select License.

The License Summary window is informational only and displays a list of the options supported for this server. You can enter keycodes for your purchased options on the Keycode Detail window.

3. Press the Add button on the Keycodes Detail window to enter each keycode.

Note: If multiple administrators are logged into a DF2112 server at the same time, license changes made from one Console will take effect in other Consoles only when the administrator disconnects and then reconnects to the server.

4. If your licenses have not been registered yet, click the Register button on the Keycodes Detail window.

You can register online if you have an Internet connection.

To register offline, you must save the registration information to a file on your hard drive and then email it to MPC’s registration server. When you receive a reply, save the attachment to your hard drive and send it to the registration server to complete the registration.



Set Server properties

To set properties for a specific server:


The tabs you see will depend upon your DF2112 configuration.

2. If you have multiple NICs (network interface cards) in your server, enter the IP addresses using the Server IP Addresses tab.

If the first IP address stops responding, the DF2112 clients will attempt to communicate with the server using the other IP addresses you have entered in the order they are listed.

Notes: • In order for the clients to successfully use an alternate IP address, your

subnet must be set properly so that the subnet itself can redirect traffic to the proper alternate adapter.

• You cannot assign two or more NICs within the same subnet.• The client becomes aware of the multiple IP addresses when it initially

connects to the server. Therefore, if you add additional IP addresses in the Console while the client is running, you must rescan devices (Windows clients) or restart the client (Linux/Unix clients) to make the client aware of these IP addresses.



3. On the Activity Database Maintenance tab, indicate how often the SAN data should be purged.

The Activity Log is a database that tracks all system activity, including all data read, data written, number of read commands, write commands, number of errors etc. This information is used to generate SAN information for the DF2112 reports. To set limits for NAS information, right-click on Windows Clients and select Properties.



4. On the SNMP Maintenance tab, indicate which types of messages should be sent as traps to your SNMP manager.

Five levels are available:• None – (Default) No messages will be sent.• Critical - Only critical errors that stop the system from operating properly

will be sent.• Error – Errors (failure such as a resource is not available or an operation

has failed) and critical errors will be sent. • Warning – Warnings (something occurred that may require maintenance or

corrective action), errors, and critical errors will be sent.• Informational – Informational messages, errors, warnings, and critical error

messages will be sent.



5. On the iSCSI tab, set the iSCSI portal that your system should use as default when creating an iSCSI target.

If you have multiple NICs, when you create an iSCSI target, this IP address will be selected by default for you.

6. If necessary, change settings for mirror resynchronization and replication on the Performance tab.



The settings on this tab affect system performance. The defaults should be optimal for most configurations. You should only need to change the settings for special situations, such as if your mirror is remotely located.

Mirror Synchronization: Use [n] outstanding commands of [n] KB - The number of commands being processed at one time and the I/O size. This must be a multiple of the sector size.

Synchronize Out-of-Sync Mirrors - Determine how often the system should check and attempt to resynchronize active out-of-sync mirrors, how often it should retry synchronization if it fails to complete, and whether or not to include replica mirrors. These setting will only be used for active mirrors. If a mirror is suspended because the lag time exceeds the acceptable limit, that resynchronization policy will apply instead.

Option: QoS - Enable QoS, DF2112’s intelligent I/O management that controls the bandwidth of each iSCSI and/or Fibre Channel client based on priority.

Replication: TCP or RUDP - Select the default protocol to use for replication. If you have a corporate firewall, you may want to select TCP because it allows replication to occur without the need to open any ports. If you want to update the protocol for existing replication jobs or for an entire server, click the Update Protocol button.

Timeout replication after [n] seconds - Timeout after inactivity. This must be the same on both the primary and target replication servers.

Throttle - The maximum amount of bandwidth that will be used for replication. This is a global server parameter and affects all resources using either remote or local replication. Throttle does not affect manual replication scans; it only affects actual replication. It also does not affect continuous replication, which uses all available bandwidth. Leaving the Throttle field set to 0 (zero) means that the maximum available bandwidth will be used. Besides 0, valid input is 10-1,000,000 KB/s (1G).

Enable Microscan - Microscan analyzes each replication block on-the-fly during replication and transmits only the changed sections on the block. This is beneficial if the network transport speed is slow and the client makes small random updates to the disk. This global Microscan option overrides the Microscan setting for each individual virtual device.



7. Select the Auto Save Config tab and enter information automatically saving your DF2112 system configuration.

You can set your system to automatically replicate your system configuration to an FTP server on a regular basis. Auto Save takes a point-in-time snapshot of the DF2112 configuration prior to replication.

The target server you specify in the Ftp Server Name field must have FTP server installed and enabled.

The Target Directory is the directory on the FTP server where the files will be stored. The directory name you enter here (such as DF2112config) is a directory on the FTP server (for example ftp\df2112config). You should not enter an absolute path like c:\df2112config.The Username is the user that the system will log in as. You must create this user on the FTP site. This user must have read/write access to the directory named here.

In the Interval field, determine how often to replicate the configuration. Depending upon how frequently you make configuration changes to DF2112, set the interval accordingly. You can always save manually in between if needed. To do this, highlight your DF2112 Server in the tree, select File menu --> Save Configuration.

In the Number of Copies field, enter the maximum copies to keep. The oldest copy will be deleted as each new copy is added.



8. The Continuous Data Protection tab displays how often the CDP journal will be flushed.

9. On the NAS tab, indicate if you want DF2112 to gather statistics for NAS reports.

Select this to option enable NAS reporting. In addition, if you want to use the "NAS Share Usage Report", "NAS Resources Usage per User Report", or "NAS Resource Usage per User Report" you need to mount NAS resources with the "usrquota" option.



If you change the interval, you will need to go to a command prompt and restart the mgtd module on the DF2112 server. Type the following command to restart the module: df2112 restart mgtd



Manage accounts

Only the root user can manage DF2112 users and groups or reset passwords. You will need to add an account for each person who will have administrative rights in DF2112. You will also need to add a user account for clients that will be accessing DF2112 resources from a host-based application.

To make account management easier, users can be grouped together and handled simultaneously.

To manage users and groups:

1. Right-click on the server and select Accounts.

A list of all existing users and administrators are listed on the Users tab and a list of all existing groups are listed on the Groups tab.

2. Select the appropriate option.

Note: You cannot manage accounts or reset a password when a server is in failover state.



Add a user To add a user:

1. Click the Add button.

2. Enter the name for this user.

The username must adhere to the naming convention of the operating system running on your DF2112 Server. Refer to your operating system’s documentation for naming restrictions.

3. Enter a password for this user and then re-enter it in the Confirm Password field.

For iSCSI clients and host-based applications, the password must be between 12 and 16 characters. The password is case sensitive.

4. Specify the type of account.

DF2112 users and administrators have different levels of permissions in DF2112.• DF2112 Admins can perform any DF2112 operation other than managing

accounts. They are also authorized for DF2112 client authentication.• DF2112 Users can manage virtual devices assigned to them and can

allocate space from the storage pool(s) assigned to them. They can also create new SAN/NAS resources, clients, and groups as well as assign resources to clients, and join resources to groups, as long as they are authorized. DF2112 Users are also authorized for DF2112 client authentication. Any time a DF2112 User creates a new SAN/NAS resource, client, or group, access rights will automatically be granted for the user to that object.

5. (DF2112 Users only) If desired, specify a quota.

Quotas enable the DF2112 administrator to place manageable restrictions on storage usage as well as storage used by groups, users, and/or hosts.

A user quota limits how much space is allocated to this user for auto-expansion. Resources managed by this user can only auto-expand if the user’s quota has not been reached. The quota also limits how much space a host-based application, such as DiskSafe, can allocate.

6. Click OK to save the information.



Add a group To add a group:

1. Select the Groups tab.

2. Click the Add button.

3. Enter a name for the group.

You cannot have any spaces or special characters in the name.

4. If desired, specify a quota.

The quota limits how much space is allocated to each user in this group. The group quota overrides any individual user quota that may be set.

5. Click OK to save the information.

Add users togroups

Each user can belong to only one group.

You can add users to groups on both the Users and Groups tabs.

On the Users tab, you can highlight a single user and click the Membership button to add the user to a group.

On the Groups tab, you can highlight a group and click the Membership button to add multiple users to that group.

You will see this dialogfrom the Users tab.

You will see this dialogfrom the Groups tab.



Set a quota You can set a quota for a user on the Users tab and you can set a quota for a group on the Groups tab.

The quota limits how much space is allocated to each user. If a user is in a group, the group quota will override the user quota.

Reset apassword

To change a password, select Reset Password. You will need to enter a new password and then re-type the password to confirm.

You cannot change the root user’s password from this dialog. Use the Change Password option below.

Change the root user’s password

This option lets you change the root user’s DF2112 password if you are currently connected to a server.

1. Right-click on the server and select Change Password.

2. Enter your old password, the new one, and then re-enter it to confirm.

Check connectivity between the Server and Console

You can check if the Console can successfully connect to the DF2112 server. To check connectivity, right-click on a server and select Connectivity Test.

By running this test, you can determine if your network connectivity is good. If it is not, the test may fail at some point. You should then check with your network administrator to find out what the problem is.



Apply software patch updates

You can apply patches to your DF2112 server through the Console.

Add patch To apply a patch:

1. Download the patch onto the computer where the Console is installed.

2. Highlight a DF2112 server in the tree.

3. Select Tools menu --> Add Patch.

The patch will be copied to the server and installed.

Rollback patch To remove (uninstall) a patch and restore the original files:

1. Highlight a DF2112 server in the tree.

2. Select Tools menu --> Rollback Patch.



System maintenance

The DF2112 Console gives you a convenient way to perform system maintenance for your DF2112 Server.

Note: The system maintenance options are hardware-dependent. Refer to your hardware documentation for specific information.

Networkconfiguration

If you need to change DF2112 Server IP addresses, you must make these changes using Network Configuration. Using yast or other third-party utilities will not update the information correctly.

1. Right-click on a server and select System Maintenance --> Network Configuration.

Domain name - Internal domain name.

Append suffix to DNS lookup - If a domain name is entered, it will be appended to the machine name for name resolution.

DNS - IP address of your DNS server.

Default gateway - IP address of your default gateway.

NIC - List of Ethernet cards in the server.

Enable Telnet - Enable/disable the ability to Telnet into the server.

Enable FTP - Enable/disable the ability to FTP into the server. The DF2112 server must have the "pure-ftpd" package installed in order to use FTP.

Allow root to log in to telnet session - Log in to your telnet session using root.



Network Time Protocol - Allows you to keep the date and time of your DF2112 server in sync with Internet NTP servers. Click Config NTP to enter the IP addresses of up to five Internet NTP servers.

2. Click Config to configure each Ethernet card.

If you select Static, you must add addresses and net masks.

MTU - Set the maximum transfer unit of each IP packet. If your card supports it, set this value to 9000 for jumbo frames.

Note: If the MTU is changed from 9000 to 1500, a performance drop will occur. If you then change the MTU back to 9000, the performance will not increase until the server is restarted.

Set hostname Right-click on a server and select System Maintenance --> Set Hostname to change your hostname. You must restart the server if you change the hostname.

Note: Do not change the hostname if you are using block devices. If you do, all block devices claimed by DF2112 will be marked offline and seen as foreign devices.

Restart DF2112 Right-click on a server and select System Maintenance --> Restart DF2112 to restart the Server processes.

Restart network Right-click on a server and select System Maintenance --> Restart Network to restart your local network configuration.

Reboot Right-click on a server and select System Maintenance --> Reboot to reboot your server.

Halt Right-click on a server and select System Maintenance --> Halt to turn off the server without restarting it.



IPMI Intelligent Platform Management Interface (IPMI) is a hardware level interface that monitors various hardware functions on a server. If IPMI is provided by your hardware vendor, you must follow the vendor’s instructions to configure it.

If DF2112 detects IPMI when the server boots up, you will see several IPMI options on the System Maintenance --> IPMI sub-menu, Config, Monitor, and Filter.

Config - Set IPMI information, including the channel number and IP address that the IPMI connection is using. You can click the Setting button to see the current settings. If they are all correct, you do not have to enter anything.

Monitor - Displays the hardware information that is presented to DF2112. Information is updated every five minutes but you can click the Refresh button to update more frequently.

You will see a red warning icon in the first column if there is a problem with a component.

In addition, you will see a red exclamation mark on the server . An Alert tab will appear with details about the error.



Filter - You can filter out components you do not want to monitor. This may be useful for hardware you do not care about or erroneous errors, such as when you do not have the hardware that is being monitored. You must enter the Name of the component being monitored exactly as it appears in the hardware monitor above.



Physical Resources

Physical resources are the actual devices attached to this DF2112 Server. The SCSI adapters tab displays the adapters attached to this server and the SCSI Devices tab displays the SCSI devices attached to this server. These devices can include hard disks, tape libraries, and RAID cabinets. For each device, the tab displays the SCSI address (comprised of adapter number, channel number, SCSI ID, LUN) of the device, along with the disk size (used and available). If you are using DF2112’s Multipathing, you will see entries for the alternate paths as well.

The Storage Pools tab displays the pools that have been defined.

The Persistent Binding tab displays the binding of each storage port to its unique SCSI ID.

When you highlight a physical device, the Category field in the right-hand pane describes how the device is being used. Possible values are:

• Reserved for virtual device - A hard disk that has not yet been assigned to a SAN/NAS Resource or Snapshot area.

• Used by virtual device(s) - A hard disk that is being used by one or more SAN/NAS Resources or Snapshot areas.

• Reserved for direct device - A SCSI device, such as a hard disk, tape drive or library, that has not yet been assigned as a SAN Resource.

• Used in direct device - A directly mapped SCSI device, such as a hard disk, tape drive or library, that is being used as a direct device SAN Resource.

• Reserved for service enabled device - A hard disk with existing data that has not yet been assigned to a SAN/NAS Resource.

• Used by service enabled device - A hard disk with existing data that has been assigned to a SAN/NAS Resource.

• Unassigned - A physical resource that has not been reserved yet.



• Not available for DF2112 - A miscellaneous SCSI device that is not used by DF2112 (such as a scanner or CD-ROM).

• System - A hard disk where system partitions exist and are mounted (i.e. swap file, file system installed, etc.).

• Reserved for Striped Set - Used in a disk striping configuration.

Physical resource icons

The following table describes the icons that are used to describe physical resources:

Icon Description

The T icon indicates that this is a target port.

The I icon indicates that this is an initiator port.

The V icon indicates that this disk has been virtualized or is reserved for a virtual disk.

The D icon indicates that this is a direct device or is reserved for a direct device.

The S icon indicates that this is a service enabled device or is reserved for a service enabled device.

The a icon indicates that this device is used in the logical resource that is currently being highlighted in the tree.

The red arrow indicates that this Fibre Channel HBA is down and cannot access its storage.

Storage Pool Icons:

The V icon to the left of the device indicates that this storage pool is comprised of virtual devices. An S icon would indicate that it is comprised of service enabled devices and a D icon would indicate that it is comprised of direct devices. The C icon to the right of the device indicates that this storage pool is designated for SafeCache resources.

The G icon to the right of the device indicates that this is a general purpose storage pool which can be used for any type of resource.

The H icon to the right of the device indicates that this storage pool is designated for HotZone resources.

The J icon to the right of the device indicates that this storage pool is designated for CDP journal resources.

The N icon to the right of the device indicates that this storage pool is designated for snapshot resources.

The R icon to the right of the device indicates that this storage pool is designated for continuous replication resources.



Prepare devices to become logical resources

You can use one of DF2112’s disk preparation options to change the category of a physical device. This is important to do if you want to create a logical resource using a device that is currently unassigned.

• The DF2112 Server detects new devices when you connect to it. When they are detected you will see a dialog box notifying you of the new devices. At this point you can highlight a device and press the Prepare Disk button to prepare it.

• At any time, you can prepare a single unassigned device by doing the following: Highlight the device, right-click, select Properties and select the device category. (You can find all unassigned devices under the Physical Resources/Adapters node of the tree view.)

• For multiple unassigned devices, highlight Physical Resources, right-click and select Prepare Disks. This launches a wizard that allows you to virtualize, unassign, or import multiple devices at the same time.

Rename a device

1. To rename a device, right-click on the device and select Rename.

2. Type the new name and press Enter.

Rescan adapters

1. To rescan all adapters, right-click on Physical Resources and select Rescan.

The S icon to the right of the device indicates that this storage pool is designated for SAN and NAS resources and their corresponding replicas.

Failover and Cross Mirror icons:

The physical disk appearing in color indicates that it is local to this server. The V indicates that the disk is virtualized for this server. If there were a Q on the icon, it would indicate that this disk is the quorum disk that contains the configuration repository.

The physical disk appearing in black and white indicates that it is a remote physical disk. The F indicates that the disk is a foreign disk.

Icon Description



If you only want to scan a specific adapter, right-click on that adapter and select Rescan.

2. Determine what you want to rescan.

If you are discovering new devices, set the range of adapters, SCSI IDs, and LUNs that you want to scan.

Use Report LUNs - The system sends a SCSI request to LUN 0 and asks for a list of LUNs. Note that this SCSI command is not supported by all devices.

Stop scan when a LUN without a device is encountered - This option will scan LUNs sequentially and then stop after the last LUN is found. Use this option only if all of your LUNs are sequential.

Auto detect FC HBA SCSI ID scans QLogic HBAs. It ignores the range of SCSI IDs specified and automatically detects the SCSI IDs with persistent binding.

Import a disk

You can import a ‘foreign’ disk into a DF2112 Server. A foreign disk is a virtualized physical device containing DF2112 logical resources previously set up on a different DF2112 server. You might need to do this if a DF2112 Server is damaged and you want to import the server’s disks to another DF2112 Server.

When you right-click on a disk that DF2112 recognizes as ‘foreign’ and select the Import option, DF2112 scans the disk’s partition table. DF2112 then tries to reconstruct the virtual drive out of all of the segments.

If the virtual drive was constructed from multiple disks, you can highlight Physical Resources, right-click and select Prepare Disks. This launches a wizard that allows you to import multiple disks at the same time.



As each drive is imported, DF2112 marks the drive ‘offline’ because it has not yet found all of the segments. Once all of the disks that were part of the virtual drive have been imported, DF2112 re-constructs the virtual drive and marks it ‘online’.

Importing a disk preserves the data that was on the disk but does not preserve the client assignments. Therefore, after importing, you must either reassign clients to the resource or use the File menu --> Restore Configuration option.

Notes:

• The GUID (Global Unique Identifier) is the permanent identifier for each virtual device. When you import a disk, the virtual ID, such as SANDisk-00002, may be different from the original server. Therefore, you should use the GUID to identify the disk.

• If you are importing a disk that can be seen by other DF2112 servers, you should perform a rescan before importing. Otherwise, you may have to rescan after performing the import.

Test physical device throughput

You can test the following for your physical devices:

• Sequential throughput• Random throughput• Sequential I/O rate• Random I/O rate• Latency

To check the throughput for a device:

1. Right-click on the device (under Physical Resources).

2. Select Test from the menu.

The system will test the device and then display the throughput results on a new Throughput tab.

SCSI aliasing

SCSI aliasing works with DF2112’s Multipathing option to eliminate a potential point of failure in your storage network by providing multiple paths to your storage devices using multiple Fibre Channel switches and/or multiple adapters and/or storage devices with multiple controllers. In a multiple path configuration, DF2112 automatically detects all paths to the storage devices. If one path fails, DF2112 automatically switches to another.

Refer to the “Multipathing” chapter for more information.



Repair paths to a device

Repair is the process of removing one or more physical device paths from the system and then adding them back. Repair may be necessary when a device is not responsive which can occur if a storage controller has been reconfigured or if a standby alias path is offline/disconnected.

If a path is faulty, adding it back may not be possible.

To repair paths to a device:

1. Right-click on the device and select Repair.

If all paths are online, the following message will be displayed instead: “There are no physical device paths that can be repaired.”

2. Select the path to the device that needs to be repaired.

If the path is still missing after the repair or the entire physical device is gone from the Console, the path could not be repaired. You should investigate the cause, correct the problem, and then rescan adapters with the Discover New Devices option.



Logical Resources

Logical resources are all of the resources defined on the DF2112 Server, including SAN Resources, NAS Resources, and Groups.

SAN and NASResources

SAN and NAS logical resources consist of sets of storage blocks from one or more physical hard disk drives. This allows the creation of logical resources that contain a portion of a larger physical disk device or an aggregation of multiple physical disk devices.

Clients do not gain access to physical resources; they only have access to logical resources. This means that an administrator must configure each physical resource to one or more logical resources so that they can be assigned to the clients.

When you highlight a SAN or NAS Resource, you will see a small icon next to each device that is being used by the resource.



In addition, when you highlight a SAN or NAS Resource, you will see a GUID field in the right-hand pane.

The GUID (Global Unique Identifier) is the permanent identifier for this virtual device. The virtual ID, SANDisk-00002, is not. You should make note of the GUID, because, in the event of a disaster, this identifier will be important if you need to rebuild your system and import this disk.

Groups Groups are groups of drives (virtual drives and service enabled drives) that will be grouped together for SafeCache or snapshot synchronization purposes. For example, when one drive in the group is to be replicated or backed up, the entire group will be snapped together to maintain a consistent image.

Logical resource icons

The following table describes the icons that are used to show the status of logical resources:

Write caching

You can leverage a third party disk subsystem's built-in caching mechanism to improve I/O performance. Write caching allows the third party disk subsystem to utilize its internal cache to accelerate I/O.

To write cache a resource, right-click on it and select Write Cache --> Enable.

Icon Description

This icon indicates a warning, such as:• Virtual device offline (or has incomplete segments)• Mirror is out of sync• Mirror is suspended• TimeMark rollback failed• Replication failed• One or more supporting resources is not accessible (SafeCache,CDP,

Snapshot resource, HotZone, etc.)

This icon indicates an alert, such as:• Replica in disaster recovery state (after forcing a replication reversal)• Cross mirror need to be repaired• Primary replica is no longer valid as a replica• Invalid replica



Replication

The Incoming and Outgoing objects under the Replication object display information about each server that replicates to this server or receives replicated data from this server. If the server’s icon is white, the partner server is "connected" or "logged in". If the icon is yellow, the partner server is "not connected" or "not logged in".

When you highlight the Replication object, the right-hand pane displays a summary of replication to/from each server.

For each replica disk, you can promote the replica or reverse the replication. Refer to the “Replication” chapter for more information about using replication.



SAN Clients

DF2112 SAN Clients are the actual file and application servers that utilize the storage resources via the DF2112 Server.

These SAN Clients access their storage resources via software-emulated virtual adapters (for SAN/IP), iSCSI initiators (for iSCSI) or HBAs (for Fibre Channel or iSCSI). The storage resources appear as locally attached devices to the SAN Clients’ operating systems (Windows, Linux, Solaris, etc.) even though the devices are actually located at the DF2112 Server.

When you highlight a specific SAN client, the right-hand pane displays the Client ID, type, and authentication status, as well as information about the client machine.

The Resources tab displays a list of SAN Resources that are allocated to this client. The adapter, SCSI ID and LUN are relative to this DF2112 SAN client only; other clients that may have access to the SAN Resource may have different adapter SCSI ID and LUN information.

Change the ACSL

You can change the ACSL (adapter, channel, SCSI, LUN) for a SAN Resource assigned to a SAN client if the device is not currently attached to the client. To change, right-click on the SAN Resource under the SAN Client object (you cannot do this from the SAN Resources object) and select Properties. You can enter a new adapter, SCSI ID, or LUN.

Notes for Windows clients:



• One SAN Resource for each client must have a LUN of 0. Otherwise, the operating system will not see the devices assigned to the SAN client. In addition, for the Linux OS, the rest of the LUNs must be sequential.

Grant access to a SAN Client

By default, only the root user and DF2112 admins can manage SAN/NAS resources, groups, or clients. While DF2112 users can create new SAN Clients, if you want a DF2112 user to manage an existing SAN Client, you must grant that user access. To do this:

1. Right-click on a SAN Client and select Access Control.

2. Select which user can manage this SAN Client.

Each SAN Client can only be assigned to one DF2112 user. This user will have rights to perform any function on this SAN Client, including assigning, adding protocols, and deletion.



Console options

To set options for the Console:

1. Select Tools --> Console Options.

2. Make any necessary changes.

Remember password for session - If the Console is already connected to a server, when you attempt to open a second, third, or subsequent server, the Console will use the credentials that were used for the last successful connection. If this option is unchecked, you will be prompted to enter a password for every server you try to open.

Automatically time out servers after nn minute(s) - The Console will collapse a server that has been idle for the number of minutes you specify. If you need to access the server again, you will have to reconnect to it. The default is 10 minutes. Enter 00 minutes to disable the timeout.

Update statistics every nn second(s) - The Console will update statistics by the frequency you specify.

Automatically refresh the event log every nn second(s) - The Console will update the event log by the frequency you specify, only when you are viewing it.

Console Log Options - The Console log (df2112console.log) is kept on the local machine and stores information about the local version of the Console. The Console log is displayed at the very bottom of the Console screen. The options affect how information for each Console session will be maintained:Overwrite log file - Overwrite the information from the last Console session when you start a new session.Append to log file - Keep all session information.Do not write to log file - Do not maintain a Console log.



Create custom menu

You can create a menu in the DF2112 Console from which you can launch external applications. This can add to the convenience of DF2112’s centralized management paradigm by allowing your administrators to start all of their applications from a single place. The Custom menu will appear in your Console along with the normal menu (between Tools and Help).

To create a custom menu:

1. Select Tools --> Set up Custom Menu.

2. Click Add and enter the information needed to launch this application.

Menu Label - The application title that will be displayed in the Custom menu.

Command - The file (usually an.exe) that launches this application.

Command Argument - An argument that will be passed to the application. If you are launching an Internet browser, this could be a URL.

Menu Icon - The graphics file that contains the icon for this application. This will be displayed in the Custom menu.


DF2112 User Guide

Storage PoolsA storage pool is a group of one or more physical devices.

Creating a storage pool enables you to provide all of the space needed by your clients in a very efficient manner. You can create and manage storage pools in a variety of ways, including:

• Tiers - Performance levels, cost, or redundancy• Device categories - Virtual, service enabled, direct• Types - Primary storage, Journal, CDR, Cache, HotZone, virtual headers,

Snapshot, and configuration.• Specific application use.

For example, you can classify your storage by tier (low-cost, high-performance, high-redundancy, etc.) and assign it based on these classifications. Using this example, you may want to have your business critical applications use storage from the high-redundancy or high-performance pools while having your less critical applications use storage from other pools.

Storage pools work with all automatic allocation mechanisms in DF2112. When storage is needed for a specific use, it is automatically allocated from the specified pool.

As your storage needs grow, you can easily extend your storage capacity by adding more devices to a pool and then creating more logical resources or allocating more space to your existing resources. The additional space is immediately and seamlessly available.


Storage Pools

Manage storage pools and the devices within storage pools

There are three types of administrators who can manage storage pools.

DF2112 Users can create virtual devices and allocate space from the storage pools assigned to them but they cannot create, delete, or modify storage pools.

Only the root user and the DF2112 Administrator have full privileges for storage pools. The root user or the DF2112 Administrator must create the pools first and then the DF2112 Users can manage them.

The rights of each are summarized in the table below:

Type of Administrator

Create/Delete Pools

Add/Remove Storage from

a Pools

Assigns Rights to DF2112

Users

Create/Modify/Delete Logical

Resources

Assign Storage to

Clients

Root x x x x x

DF2112 Administrator

x x x x x

DF2112 User x - DF2112 Users can only modify/delete logical resources that they created.

x


Storage Pools

Create storage pools

Physical devices must be prepared (virtualized, service enabled, or reserved for a direct device) before they can be added into a storage pool.

Each storage pool can only contain the same type of physical devices. Therefore, a storage pool can contain only virtualized drives or only service-enabled drives or only direct devices. A storage pool cannot contain mixed types.

Physical devices that have been allocated for a logical resource can still be added to a storage pool.

To create a storage pool:

1. Right-click on Storage Pools and select New.

2. Enter a name for the storage pool.

3. Indicate which type of physical devices will be in this storage pool.

Each storage pool can only contain the same type of physical devices.

4. Select the devices that will be assigned to this storage pool.

Physical devices that have been allocated for any logical resource can still be added to a storage pool.

5. Click OK to create the storage pool.


Storage Pools

Set properties for a storage pool

To set properties:

1. Right-click on a storage pool and select Properties.

On the General tab you can change the name of the storage pool and add/delete devices assigned to this storage pool.

2. Select the Type tab to designate how each storage pool should be allocated.

The type affects how each storage pool should be allocated. When you are in a DF2112 creation wizard, the applicable storage pool(s) will be presented for selection. However, you can still select from another storage pool type if needed.- All Types can be used for any type of resource.


Storage Pools

- Storage is the preferred storage pool to create SAN and NAS resources and their corresponding replicas.

- Snapshot is the preferred storage pool for snapshot resources.- Cache is the preferred storage pool for SafeCache resources.- HotZone is the preferred storage pool for HotZone resources.- Journal is the preferred storage pool for CDP resources and CDP resource

mirrors.- CDR is the preferred storage pool for continuous data replicas.- VirtualHeader is the preferred storage pool for the virtual header that is

created for a service enabled device SAN Resource.- Configuration is the preferred storage pool to create the configuration

repository for failover.

3. Select the Tag tab to set a tag string that will limit client side applications to specific storage pools.

When an application requests storage with a specific tag string, only the storage pools with the same tag can be used. It is also possible to have your own internal application that has been programmed to use a tag.


Storage Pools

4. Select the Security tab to designate which DF2112 users and administrators can manage this storage pool.

Each storage pool can be assigned to one or more DF2112 Users or Groups.

The assigned users can create virtual devices and allocate space from the storage pools assigned to them but they cannot create, delete, or modify storage pools.


DF2112 User Guide

DF2112 Logical ResourcesOnce you have physically attached your physical SCSI/Fibre Channel devices to your DF2112 Server you are ready to create Logical SAN and NAS Resources to be used by your DF2112 clients. This configuration can be done entirely from the DF2112 Console.

Logical Resources are logically mapped devices on the DF2112 Server. They are comprised of physical storage devices, known as Physical Resources in DF2112. Physical resources are the actual SCSI and/or Fibre Channel devices (such as hard disks, tape drives, and RAID cabinets) attached to the server.

Clients do not have access to physical resources; they have access only to Logical Resources. This means that physical resources must be defined as Logical Resources first, and then assigned to the clients so they can access them.

• SAN Resources provide storage for file and application servers (called SAN Clients). When a SAN Resource is assigned to a SAN client, a virtual adapter is defined for that client. The SAN Resource is assigned a virtual SCSI ID on the virtual adapter. This mimics the configuration of actual SCSI storage devices and adapters, allowing the operating system and applications to treat them like any other SCSI device.

• NAS Resources allow users (called NAS Clients) to access data and storage via a network interface using protocols including NFS (Network File System) and CIFS (Common Internet File System). Refer to the NAS chapter for more information about configuring and using DF2112 NAS.

Understanding how to create and manage Logical Resources is critical to a successful DF2112 storage network. Please read this section carefully before creating and assigning Logical Resources.


DF2112 Logical Resources

Types of SAN Resources

There are three types of SAN Resources: virtual devices, direct devices, and service enabled devices.

Virtual devices

DF2112 has the ability to aggregate multiple physical storage devices (such as JBODs and RAIDs) of various interface protocols (such as SCSI or Fibre Channel) into logical storage pools. From these storage pools, virtual devices can be created and provisioned to application servers and end users. This is called storage virtualization.

Virtual devices are defined as sets of storage blocks from one or more physical hard disk drive. This allows the creation of virtual devices that can be a portion of a larger physical disk drive, or an aggregation of multiple physical disk drives.

Virtual devices offer the added capability of disk expansion. Additional storage blocks can be appended to the end of existing virtual devices without erasing the data on the disk.

Virtual devices can only be assembled from hard disk storage. It does not work for CD-ROM, tape, libraries, or removable media.

When a virtual device is allocated to an application server, the server thinks that an actual SCSI storage device has been physically plugged into it.

Virtual devices are assigned to virtual adapter 0 (zero) when mapped to a client. If there are more than 15 virtual devices, a new adapter will be defined.

Note: We do not recommend storing system files, page files, swap files, etc. on DF2112 virtual devices.



Virtualizationexamples

The following diagrams show how physical disks can be mapped into virtual devices.

The diagram above shows a virtual device being created out of two physical disks. This allows you to create very large virtual devices for application servers with large storage requirements. If the storage device needs to grow, additional physical disks may be added to increase the size of a virtual device. Note that this will require that the client application server resize the partition and file system on the virtual device.

The example above shows a single physical disk split into two virtual devices. This is useful when a single large device exists, such as a RAID, which could be shared among multiple client application servers.

Virtual devices can be created using various combining and splitting methods, although you will probably not create them in this manner in the beginning. You may end up with devices like this after growing virtual devices over time.

Adapter = 1SCSI ID = 4sectors 0-

9999


9999Adapter = 0SCSI ID = 1sectors 0-

19999

Physical Devices

SAN Resources

Virtual Device:SCSI ID = any.Adapter number does not need to match.Sectors are mapped, combining sectors from multiple physical disks.

SANResources

PhysicalDevices

Virtual Disk:SCSI ID = anyAdapter number does not need tomatchSectors are mapped, a singlephysical device maps to multiplevirtual devices

Adapter = 2SCSI ID = 3

sectors 5000-9999


4999


4999


4999



Direct devices

Direct devices are directly mapped SCSI devices. Because they are not virtualized, direct devices cannot take advantage of DF2112’s advanced storage management options, such as mirroring, failover, replication, or snapshot copy.

Direct devices use fixed SCSI IDs that cannot be changed.

Designating a hard drive as a direct device can be useful for data migration into DF2112. Data on an existing disk can be brought into DF2112 as a direct device. The data can then be copied using Linux’s dd command to a virtualized disk that does not contain any data or have any clients attached so that it can take advantage of DF2112’s virtualization and advanced storage management options.

Service enabled devices

Service enabled devices are hard drives with existing data that can be accessed by DF2112 to make use of all key DF2112 storage services (mirroring, snapshot, etc.), without any migration/copying, without any modification of data, and with minimal downtime. Service enabled devices are used to migrate existing drives into the SAN.

Because service enabled devices are preserved intact, and existing data is not moved, the devices are not virtualized and cannot be expanded. Service enabled devices are all maintained in a one-to-one mapping relationship (one physical disk equals one logical device). Unlike virtual devices, they cannot be combined or split into multiple logical devices.



Create SAN Resources - Procedures

SAN Resources are created in the DF2112 Console.

Note: After you make any configuration changes, you may need rescan or restart the client in order for the changes to take effect. After you create a new virtual device, assign it to a client, and restart the client (or rescan), you will need to write a signature, create a partition, and format the drive so that the client can use it.

Prepare devices to become SAN Resources

You can use one of DF2112’s disk preparation options to change the category of a device. This is important to do if you want to create a logical resource using a device that is currently unassigned.

• The DF2112 Server detects new devices when you connect to it (or when you execute the Rescan command). When they are detected you will see a dialog box notifying you of the new devices. At this point you can highlight a device and press the Prepare Disk button to prepare it.

• At any time, you can prepare a single unassigned device by doing the following: Highlight the device, right-click, select Properties and select the device category. (You can find all unassigned devices under the Physical Resources/Adapters node of the tree view.)

• For multiple unassigned devices, highlight Physical Resources, right-click and select Prepare Disks. This launches a wizard that allows you to virtualize, unassign, or import multiple devices at the same time.



Create a virtual device SAN Resource

Note: Each DF2112 Server supports a maximum of 1024 SAN Resources.

1. Right-click on SAN Resources and select New.

2. Select Virtual Device.

3. Select the storage pool or physical device(s) from which to create this SAN Resource.



You can create a SAN Resource from any single storage pool. Once the resource is created from a storage pool, additional space (automatic or manual expansion) can only be allocated from the same storage pool.

You can select List All to see all storage pools, if needed.

4. Select how you want to create this virtual device.


Express lets you designate how much space to allocate and then automatically creates a virtual device using an available device.

Batch lets you create multiple SAN Resources at one time. These SAN Resources will all be the same size.



If you select Custom, you will see the following windows:Select either an entirely unallocated or partially unallocated device.

Only one device can be selected at a time from this dialog. To create a virtual device SAN Resource from multiple physical devices, you will need to add the devices one at a time. After selecting the parameters for the first device, you will have the option to add more devices.

Indicate how much space to allocate from this device.

Click Add More if you want to add another physical device to this SAN Resource.If you select to add more devices, you will go back to the physical device selection screen where you can select another device.



If you select Batch, you will see the following window:

Indicate how to name each resource. The SAN Resource Prefix is combined with the starting number to form the name of each SAN Resource. You can uncheck the Use default ID for Starting Number option to restart numbering from one.

In the Resource Size field, indicate how much space to allocate for each resource.

Indicate how many SAN Resources to create in the Number of Resources field.



5. (Express and Custom only) Enter a name for the new SAN Resource.

The name is not case sensitive.

6. Confirm that all information is correct and then click Finish to create the virtual device SAN Resource.

7. (Express and Custom only) Indicate if you would like to assign the new SAN Resource to a client.

If you select Yes, the Assign a SAN Resource Wizard will be launched.

Note: After you assign the SAN Resource to a client, you may need to restart the client. You will also need to write a signature, create a partition, and format the drive so that the client can use it.



Create a direct device or service enabled device SAN Resource

1. Right-click on SAN Resources and select New.

2. Select Direct Device or Service Enabled Device.

If you are creating a Service Enabled Device, determine if you want to preserve the physical device’s inquiry string. Preserving it treats the physical device as the original physical disk instead of treating it as a DataFRAME® 2112 device. This can be useful for vendors who only recognize their own storage devices.

3. Select how you want to create this device.

Custom lets you select one physical device(s) to use.

Batch lets you create multiple SAN Resources at one time.

4. Select the device that you want to make into a direct/service enabled device.

A list of the storage pools and physical resources that have been reserved for this purpose are displayed. For direct devices, both hard disk and non-hard disk devices are shown.



5. (Service enabled devices only) Select the physical device(s) for the service enabled device’s virtual header.

Even though service enabled devices are used as is, a virtual header is created on another physical device to allow DF2112’s storage services to be supported.



6. Enter a name for the new SAN Resource.


7. Confirm that all of the information is correct and then click Finish to create the SAN Resource.

8. Indicate if you would like to assign the new SAN Resource to a client.

If you select Yes, the Assign a SAN Resource Wizard will be launched.



Assign a SAN Resource to one or more clients

You can assign a SAN Resource to one or more clients or you can assign a client to one or more SAN Resources. While the wizard is initiated differently, the outcome is the same.

Note: (For AIX Fibre Channel clients running DynaPath) If you are re-assigning SAN Resources to the same LUN, you must reboot the AIX client after unassigning a SAN Resource.

1. Right-click on a SAN Resources object and select Assign.

The wizard can also be launched from the Create SAN Resource wizard.

Alternatively, you can right-click on a SAN Client and select Assign.

2. If this server has multiple protocols enabled, select the type of client to which you will be assigning this SAN Resource.

3. Select the client to be assigned and determine client access rights.

If you initiated the wizard by right-clicking on a SAN Client instead of a SAN Resource, you will need to select the SAN Resource(s) instead.

Read/Write - Only one client can access this SAN Resource at a time. All others (including Read Only) will be denied access. This is the default.

Read/Write Non-Exclusive - Two clients can connect at the same time with both read and write access. You should be careful with this option because if you have multiple clients writing to a device at the same time, you have the potential to corrupt data. This option should only be used by clustered servers, because the cluster itself prevents multiple clients from writing at the same time.



Read Only - This client will have read only access to the SAN Resource. This option is useful for a read-only disk.

Notes: - In a Fibre Channel environment, we recommend that only one DF2112

Client be assigned to a SAN Resource (with Read/Write access). If two or more Fibre Channel clients attempt to connect to the same SAN Resource, error messages will be generated each time the second client attempts to connect to the resource.

- If multiple Windows 2000 clients are assigned read-only access to the same virtual or direct device, the only partition format they can read from is FAT.

For Fibre Channel clients, you will see the following screen:



For iSCSI clients, you will see the following screen:

You must have already created a target for this client. Refer to ‘Create storage targets for the iSCSI client’ for more information.

For SAN/IP clients, you will see the following screen:

If the SAN/IP client that you want to assign to the SAN Resource does not appear on the list, click the Add button.

You can add any application server, even if it is currently offline.

Note: You must enter the client’s name, not an IP address.



4. If this is a Fibre Channel client and you are using Multiple Data Path software (such as DF2112’s DynaPath), enter the World Wide Port Name (WWPN) mapping.

This WWPN mapping is similar to Fibre Channel zoning and allows you to provide multiple paths to the DF2112 Server to limit a potential point of network failure. You can select how the client will see the virtual device in the following ways:

One to One - Limits visibility to a single pair of WWPNs. You will need to select the client’s Fibre Channel initiator WWPN and the server’s Fibre Channel target WWPN.

One to All - You will need to select the client’s Fibre Channel initiator WWPN.

All to One - You will need to select the server’s Fibre Channel target WWPN.

All to All - Creates multiple data paths. If ports are ever added to the client or server, they will automatically be included in the WWPN mapping.



5. If this is a Fibre Channel client and you selected a One to n option, select which port to use as an initiator for this client.

6. If this is a Fibre Channel client and you selected an n to One option, select which port to use as a target for this client.

7. Confirm all of the information and then click Finish to assign the SAN Resource to the client(s).



The SAN Resource will now appear under the SAN Client in the configuration tree view:

After client assignment

Depending upon the operating system of the client, you may be required to reboot the client machine in order to be able to use the new SAN Resource.

Windows clients

If an assigned SAN Resource is larger than 3GB, formatting the resource as a FAT partition will not format properly.

Creating a file system on a disk managed by the DF2112 software:

Warning: Make sure to choose the correct raw device when creating a file system. If in doubt, check with an administrator.

1. To create a new file system, execute the following command:

newfs /dev/rdsk/c2t0d0s2where c2t0d0s2 is the name of the raw device.

2. To create a mount point for the new file system, execute the following command:

mkdir /mnt/df21121where /mnt/df21121 is the name of the mount point you are creating.

3. To mount the disk managed by the DF2112 software, execute the following command:

mount /dev/dsk/c2t0d0s2 /mnt/df21121where /dev/dsk/c2t0d0s2 is the name of the block device and /mnt/df21121 is the name of the mount point you created.

For further information, refer to the man pages.

Virtual devicefrom a different

server

When assigning a virtual device from a different DF2112 Server, the SAN Client software must be restarted in order to add the virtual device to the client machine.

The reason for this is that when virtual devices are added from other DF2112 Servers, a new virtual SCSI adapter gets created on the client machine. Since Solaris does not allow new adapters to be added dynamically, the DF2112 Client software needs to be restarted in order for the new adapter and device to be added to the system.



Expand a virtual deviceSince virtual devices do not represent actual physical resources, they can be expanded as more storage is needed. The virtual device can be increased in size by adding more blocks of storage from any unallocated space from the same server.

Note that you will still need to repartition the virtual devices and adjust/create/resize any file-systems on the partition after the virtual device is expanded. Since partition and file-system formats are specific to the operating system that the client is running, the administrator must perform these tasks directly from the client. You can use tools like Partition Magic, Windows 2000 Dynamic Disk, or Veritas Volume Manager to add more drives to expand existing volume on-the-fly in real time (without application down time).

Notes:

• We do not recommend expanding a virtual device (SAN or NAS) while clients are accessing the drives. However, when expanding an XFS resource, NAS clients can remain connected.

• At the end of this section is important information about Windows 2000 dynamic disks, Solaris clients, AIX clients, and Fibre Channel clients.

1. Right-click on a virtual device (SAN or NAS) and select Expand.

2. Select how you want to expand the virtual device.


Express lets you designate how much space to allocate and then automatically creates a virtual device using an available device.



The Size to Allocate is the maximum space available on all available devices. If this drive is mirrored, this number will be half the full amount because the mirrored drive will need an equal amount of space.

If you select Custom, you will see the following windows:

Select either an entirely unallocated or partially unallocated device.

Only one device can be selected at a time from this dialog. To expand a virtual device from multiple physical devices, you will need to add the devices one at a time. After selecting the parameters for the first device, you will have the option to add more devices.

Indicate how much space to allocate from this device. Note: If this drive is mirrored, you can only select up to half of the available total space (from all available devices). This is because the mirrored drive will need an equal amount of space.

Click Add More if you want to select space from another physical device.



3. Confirm that all information is correct and then click Finish to expand the virtual device.

Windows 2000Dynamic disks

Expansion of dynamic disks using the Expand SAN Resource Wizard is not supported for clients using Fibre Channel. Due to the nature of dynamic disks, it is not safe to alter the size of the virtual device. However, dynamic disks do provide an alternative method to extend the dynamic volume.

To extend a dynamic volume using SAN Resources, use the following steps:

1. Create a new SAN Resource and assign it to the DF2112 Client. This will become an additional disk which will be used to extend the dynamic volume.

2. Use Disk Manager to write the disk signature and upgrade the disk to "Dynamic”.

3. Use Disk Manager to extend the dynamic volume.

The new SAN Resource should be available in the list box of the Dynamic Disk expansion dialog.

Solaris clients The following procedure is valid for clients using Fibre Channel and SAN/IP:

1. Use expand.sh to get the new capacity of the disk.

This will automatically label the disk.

2. Use the format utility to add a new partition or, if your file system supports expansion, use your file system’s utility to expand the file system.

Windowsclients (Fibre

Channel)

For Windows 2000 and 2003 clients, after expanding a virtual device you should rescan the physical devices from the Computer Manager to see the expanded area.

Linux clients(Fibre Channel)

1. Use rmmod qla2x00 to remove the module.

2. Use insmod qla2x00 to install the module back again.

3. Use fdisk/dev/sda to create a second partition.

The a in sda refers to the first disk. Use b, c, etc. for subsequent disks.

AIX clients Expanding a DF2112 virtual disk will not change the size of the existing AIX volume group. To expand the volume group, a new disk has to be assigned and the extendvg command should be used to enlarge the size of the volume group.



Grant access to a SAN Resource

By default, only the root user and DF2112 admins can manage SAN/NAS resources, groups, or clients. While DF2112 users can create new SAN Resources, if you want a DF2112 user to manage an existing SAN Resource, you must grant that user access. To do this:

1. Right-click on a SAN Resource and select Access Control.

2. Select which user can manage this SAN Resource.

Each SAN Resource can only be assigned to one DF2112 user. This user will have rights to perform any function on this SAN Resource, including assigning, configuring for storage services, and deletion.

Note that if a SAN Resource is already assigned to a client, you cannot grant access to the SAN Resource if the user is not already assigned to the client. You will have to unassign the SAN Resource first, change the access for both the client and the SAN Resource, and then reassign the SAN Resource to the client.

Unassign a SAN Resource from a client

1. Right-click on the client or client protocol and select --> Unassign.

2. Select the resource(s) and click Unassign.

Note that when you unassign a Linux client connected, the client may be temporarily disconnected from the server. If the client has multiple devices offered from the same server, the temporary disconnect may affect these devices. However, once I/O activities from those devices are detected, the reconnection will be restored automatically and transparently.

Delete a SAN Resource

1. (AIX and HP-UX clients) Prior to removing a DF2112 device, make sure any logical volumes that were built on top have been removed.

If the DF2112 device is removed while logical volumes exist, you will not be able to remove the logical volumes and the system will display error messages.

2. (Windows 2000/2003, Linux, Unix clients) You should disconnect/umount the client from the SAN Resource(s) prior to deleting the SAN Resource.

3. Detach the SAN Resource from any client that is using it. - For non-Windows clients, type ./df2112client stop from /usr/local/

df2112client/bin.

4. In the Console, highlight the SAN Resource, right-click and select Delete.


DF2112 User Guide

DF2112 ServerThe DF2112 Server is a storage server designed to require little or no maintenance.

All day-to-day DF2112 administrative functions can be performed through the DF2112 Console. However, there may be situations when direct access to the Server is required, particularly during initial setup and configuration of physical storage devices attached to the Server or for troubleshooting purposes.

If access to the Server’s operating system is required, it can be done either directly or remotely from computers on the SAN.

Start the DF2112 Server

Execute the following commands to start the DF2112 Server processes:

If the server is already started, you can use ./df2112 restart to stop and then start the processes.

When you start the server, you will see the processes start. It will similar to the following:

cd /usr/local/df2112/bin./df2112 start


DF2112 Server

Starting df2112 SNMPD Module [OK]Starting df2112 Configuration Module [OK]Starting df2112 Base Module [OK]Starting df2112 HBA Module [OK]Starting df2112 Initiator Module [OK]Starting Idf2112 Control Module [OK]Starting df2112 Authentication Module [OK]Starting df2112 Block Device Module [OK]Starting df2112 Server (Compression) Module [OK]Starting df2112 Server (FSNBase) Module [OK]Starting df2112 Server (Upcall) Module [OK]Starting df2112 Server (Transport) [OK]Starting df2112 Server (Event) Module [OK]Starting df2112 Server (Path Manager) Module [OK]Starting df2112 Server (Application) [OK]Starting df2112 Advanced Backup Module [OK]Starting df2112 Target Module [OK]Starting df2112 iSCSI Target Module [OK]Starting df2112 iSCSI (Daemon) [OK]Starting df2112 Communication Module [OK]Starting df2112 CLI Proxy Module [OK]Starting df2112 Logger Module [OK]Starting df2112 Local Client (VBDI) [OK]Starting df2112 SANBridge Daemon [OK]Starting df2112 Anti Virus Daemon [OK]Starting df2112 NAS MGTD Module [OK]Starting df2112 NAS WINBINDD Module [OK]Starting df2112 NAS NMBD Module [OK]Starting df2112 NAS SMBD Module [OK]Starting df2112 NAS MOUNTD Module [OK]Starting df2112 NAS NFSD Module [OK]Starting df2112 Self Monitor Module [OK]Starting df2112 Failover Module [OK]

You will only seethese processes if

NAS is enabled.

You will only see thisprocess if Failover is

enabled.


iSCSI Target Mode isenabled.


DF2112 Server

Stop the DF2112 Server

Warning: Stopping the DF2112 Server processes will shut down all access to the storage resources managed by the Server. This can halt processing on your application servers, or even cause them to crash, depending upon how they behave if a disk is unexpectedly shut off or removed. It is recommended that you make sure your application servers are not accessing the storage resources when you stop the DF2112 Server processes.

To shut down the DF2112 Server processes, execute the following commands:

You should see the processes stopped.

Log into the DF2112 Server

You can log in directly from a keyboard/display connected directly to the Server. There is no graphical user interface (GUI) shell required.

By default, the root user is the only user that has login privileges to the operating system. Other DF2112 administrators do not.

To log in, enter the username and the password for the root user.

Warning: You should not allow login access to your DF2112 Server to anyone except your most trusted system or storage administrators. Administrators with login access to the Server have the ability to modify, damage or destroy data managed by the Server.

telnet access

By default, DF2112 administrators do not have telnet access to the Server. The Server is configured to deny all TCP/IP access, including telnet.

(Linux Server only) To grant telnet access to another computer on the network:

1. Log into the Server directly (on the local console keyboard and display).

2. Change the etc/passwd file.

For the appropriate administrator, change the line that looks like:

To:

Where Username is an actual administrator name and homedirectory is the actual home directory.

cd /usr/local/df2112/bin./df2112 stop

:/dev/null:/dev/null

Username:/homedirectory:/bin/bash


DF2112 Server

Note: For a more secure session, you may want to use the program ssh, which is supplied by some versions of the Linux operating system. Please refer to the Linux manual that came with your operating system for more details about configuration.

Check the DF2112 Server processes

You can type the following command from the shell prompt to check the DF2112 Server processes:

You should see something similar to the following:

cd /usr/local/df2112/bin./df2112 status

Status of DF2112 SNMPD Module [RUNNING]Status of DF2112 Authentication Module [RUNNING]Status of DF2112 Block Device Module [RUNNING]Status of DF2112 Server (Compression) Module [RUNNING]Status of DF2112 Server (FSNBase) Module [RUNNING]Status of DF2112 Server (Upcall) Module [RUNNING]Status of DF2112 Server (Transport) [RUNNING]Status of DF2112 Server (Event) Module [RUNNING]Status of DF2112 Server (Path Manager) Module [RUNNING]Status of DF2112 Server (Application) [RUNNING]Status of DF2112 Advanced Backup Module [RUNNING]Status of DF2112 Communication Module [RUNNING]Status of DF2112 CLI Proxy Module [RUNNING]Status of DF2112 Central Client Manager Module [RUNNING]Status of DF2112 Logger Module [RUNNING]Status of DF2112 Self Monitor Module [RUNNING]


Fibre Channel TargetMode is enabled with

LSI HBAs.You will only see the

HBA Module forQLogic HBAs.


DF2112 Server

Check physical resources

When adding physical resources or testing to see if the physical resources are present, the following command can be executed from the shell prompt in Linux:

These commands display the SCSI devices attached to the DF2112 Server. For example, you will see something similar to the following:

lsscsi

[0:0:0:0] disk 3ware Logical Disk 0 1.2 /dev/sda[0:0:1:0] disk 3ware Logical Disk 1 1.2 /dev/sdb[2:0:1:0] disk IBM-PSG ST318203FC !# B324 -[2:0:2:0] disk IBM-PSG ST318203FC !# B324 -[2:0:3:0] disk IBM-PSG ST318304FC !# B335 -


DF2112 Server

Check activity statistics

There is a utility that installs with DF2112 and runs on the DF2112 server that allows you to view activity statistics for virtual and physical devices as well as for Fibre Channel target ports.

To run this utility, type the following command on the DF2112 server:

This command displays all virtual resources (SAN, NAS, Snapshot, etc.) for this DF2112 server. For each resource, the screen shows its size, amount of reads/writes in KB/second, and number of read/write commands per second.

Information on the screen is automatically refreshed every five seconds.

You can change the information that is displayed or the way it is sorted. The following options are available by pressing the appropriate key on your server:

ismon

Option Description

c Toggle incremental/cumulative mode

v Display information for virtual devices

p Display information for physical devices. You can launch ismon -p at the command prompt to view this information directly.

t Display information for each FC target mode. You can launch ismon -t at the command prompt to view this information directly.

u Page up

d Page down

V Sort by virtual device ID

R Sort by KB read

r Sort by read SCSI command

o Sort by other SCSI command

A Sort by ACSL

S Sort by virtual device size

W Sort by KB written

w Sort by write SCSI command

E Sort by SCSI command error

N Sort by virtual device name

P Sort by WWPN


DF2112 Server

m Display Max value fields (incremental mode only)

l Start logging

k Reload virtual device name alias

K Edit virtual device name alias

h View help page

q Quit

Option Description


DF2112 Server

Uninstall the DF2112 Server

To uninstall a DF2112 Server:

1. Execute the following command:

This command removes the installation of the DF2112 Server but leaves the /df2112 directory and its subdirectories.

2. To remove the /df2112 directory and its subdirectories, execute the following command from the /usr/local directory:

NOTE: We do not recommend deleting the DF2112 Server files without using rpm –e. However, to re-install the DF2112 Server software if the DF2112 Server was removed without using the rpm utility, or to install over an existing DF2112 Server installation, the following command should be executed:

To determine the package name, check the Server directory on the DF2112 CD.

This will force a re-installation of the software.

Refer to the rpm man pages for more information.

rpm –e df2112

rm –rf df2112

rpm –i - - force package name


DF2112 User Guide

iSCSI ClientsiSCSI clients are the file and application servers that access DF2112 SAN Resources using the iSCSI protocol.

Just as the DF2112 Server supports different types of storage devices (such as SCSI, Fibre Channel, and iSCSI), the DF2112 Server is protocol-independent and supports multiple outbound target protocols, including iSCSI Target Mode.

iSCSI builds on top of the regular SCSI standard by using the IP network as the connection link between various entities involved in a configuration. iSCSI inherits many of the basic concepts of SCSI. For example, just like SCSI, the entity that makes requests is called an initiator, while the entity that responds to requests is called a target. Only an initiator can make requests to a target; not the other way around. Each entity involved, initiator or target, is uniquely identified.

By default, when a client machine is added as an iSCSI client of a DF2112 Server, it becomes an iSCSI initiator. The initiator name is important because it is the main identity of an iSCSI initiator.

This chapter provides an overview for configuring iSCSI clients with DF2112.

Supported platformsiSCSI target mode is supported for the following platforms:

• Windows• NetWare• Linux• Solaris• HP-UX• AIX

RequirementsThe following requirements are valid for all iSCSI clients regardless of platform:

• You must install an iSCSI initiator on each of your client machines. iSCSI initiator software/hardware is available from many sources and needs to be installed and configured on all clients that will access shared storage. Refer to the MPC certification matrix for a list of supported iSCSI initiators.

• You should not install any DF2112 client software on the client unless you are using a snapshot agent.


iSCSI Clients

Configuring iSCSI clients

The following sections provide an overview for configuring iSCSI clients with DF2112. You will need to refer to the documentation provided by your iSCSI initiator for detailed instructions about functions performed there.

Enable iSCSI

In order to add a client using the iSCSI protocol, you must enable iSCSI for your DF2112 Server. To do this, in the DF2112 Console, right-click on your DF2112 Server and select Options --> Enable iSCSI.

As soon as iSCSI is enabled, a new SAN client called Everyone_iSCSI is automatically created on your DF2112 Server. This is a special SAN client that does not correspond to any specific client machine. Using this client, you can create iSCSI targets that are accessible by any iSCSI client that connects to the DF2112 Server.

Before an iSCSI client can be served by a DF2112 Server, the two entities need to mutually recognize each other. The following sections take you through this process.

Configure your iSCSI initiator

You need to register your iSCSI client as an initiator to your DF2112 Server. This enables the DF2112 Server to see the initiator.

To do this, you must launch the iSCSI initiator on the client machine and identify your DF2112 Server as the target server. You will have to enter the IP address or name (if resolvable) of your DF2112 Server.

Refer to the documentation provided by your iSCSI initiator for detailed instructions about how to do this.

Afterwards, you may need to start, or restart the initiator if it is a Unix client.


iSCSI Clients

Add your iSCSI client in the DF2112 Console

1. Right-click on SAN Clients and select Add.

2. Enter the name of the client, select the operating system, and indicate whether or not the client machine is part of a cluster.

Note: It is very important that you enter the correct client name.

3. Click Find to locate the client machine.

The IP address of the machine with the specified host name will be automatically filled in if the name is resolvable.

4. Indicate if you want to enable persistent reservation.

This option allows clustered SAN Clients to take advantage of Persistent Reserve/Release to control disk access between various cluster nodes.

5. Select iSCSI and determine if the client is a mobile client.

Stationary iSCSI clients corresponds to specific iSCSI client initiators, and consequently, the client machine that owns the specific initiator names. Only a client machine with a correct initiator name can connect to the DF2112 Server to access the resources assigned to this stationary client.

A mobile client is simply a username and CHAP password that a user can use to authenticate to the DF2112 Server from any iSCSI client machine. If you ever need to change the password or username for a mobile client, you will have to delete the mobile client and re-create it. Alternatively, you can change the password, but not the username, by right-clicking on iSCSI --> Properties on a stationary iSCSI client and going to User Access. For more information about CHAP authentication, refer to ‘Understanding CHAP authentication’.

6. Select the initiator that this client uses.

If the initiator does not appear, you may need to rescan. You can also manually add it, if necessary.

7. Add/select users who can authenticate for this client.

Click Add to add users. You will have to enter a name and password for each.

For unauthenticated access, select Allow Unauthenticated Access. With unauthenticated access, the DF2112 Server will recognize the client as long as it has an authorized initiator name. With authenticated access, an additional check is added that requires the user to type in a username and password. More than one username/password pair can be assigned to the client, but they will only be useful when coming from the machine with an authorized initiator name.

8. Confirm all information and click Finish.


iSCSI Clients

Create storage targets for the iSCSI client

1. In the DF2112 Console, right-click on the iSCSI protocol object for an iSCSI client and select Create Target.

2. Enter a new target name for the client or accept the default.

Note: The Microsoft iSCSI initiator can only connect to an iSCSI target if the target name is no longer than 221 characters. It will fail to connect if the target name is longer than this.

3. Select the IP address(es) of the DF2112 Server to which this client can connect.

You can select multiple IPs if your iSCSI initiator has multipathing support (such as the Microsoft initiator version 2.0).

If you specified a default portal (in Server Properties), that IP address will be selected for you.

4. Select an access mode.

Read/Write - Only one client can access this SAN Resource at a time. All others (including Read Only) will be denied access.

Read/Write Non-Exclusive - Two or more clients can connect at the same time with both read and write access. You should be careful with this option because if you have multiple clients writing to a device at the same time, you have the potential to corrupt data. This option should only be used by clustered servers, because the cluster itself prevents multiple clients from writing at the same time.

Read Only - This client will have read only access to the SAN Resource. This option is useful for a read-only disk.

5. Select the SAN Resource(s) to be assigned to the client.

If you have not created any SAN Resources yet, you can assign them at a later time. You may need to restart the iSCSI initiator afterwards.

6. Use the default starting LUN.


iSCSI Clients

Once the iSCSI target is created for a client, LUNs can be assigned under the target using available SAN Resources.


Restart the iSCSI initiator

In order for the client to be able to access its storage, you must restart the iSCSI initiator on Unix clients or log the client onto the target (Windows and NetWare).

It may be desirable to have a persistent target. Refer to the documentation provided by your iSCSI initiator for detailed instructions about how to do this.


iSCSI Clients

Understanding CHAP authentication

CHAP authentication can be used for stationary clients and is mandatory for mobile iSCSI clients so that they can authenticate to the DF2112 Server to access their storage.

When used, the same CHAP username and password must be entered in the iSCSI initiator and into the DF2112 Console.

If you want to use mutual CHAP, you will need to enter the mutual CHAP password in your iSCSI initiator. Enter the same password as your CHAP password but append the letter 'm' to the end (for example, if your password is mychappassword, your mutual password should be mychappasswordm). However, if your CHAP password is 16 characters long, the password is the same as the CHAP password minus the last character (for example, if your password is thisismypassword, your mutual password should be thisismypasswor).


iSCSI Clients

Windows iSCSI clients and failover

The Microsoft iSCSI initiator has a default retry period of 60 seconds. You must change it to 300 seconds in order to sustain the disk for five minutes during failover so that applications will not be disrupted by temporary network problems. This setting is changed through the registry.

1. Go to Start --> Run and type regedit.2. Find the following registry key:

HKEY_LOCAL_MACHINE\system\CurrentControlSet\control\class\4D6E97B-xxxxxxxxx\<iscsi adapter interface>\parameters\

where iscsi adapter interface corresponds to the adapter instance, such as 0000, 0001, .....

3. Right-click Parameters and select Export to create a backup of the parameter values.

4. Double-click MaxRequestHoldTime.5. Pick Decimal and change the Value data to 300.6. Click OK.7. Reboot Windows for the change to take effect.


iSCSI Clients

Disable iSCSI

To disable iSCSI for a DF2112 Server, right-click on the server node in the DF2112 Console, and select Options --> Disable iSCSI.

Note that before disabling iSCSI, all iSCSI initiators and targets for this DF2112 Server must be removed.


DF2112 User Guide

Logs and ReportsThe DF2112 Server retains information about the health and behavior of the physical and virtual storage resources on the Server. It maintains an Event Log to record system events and errors. The Server also maintains performance data on the individual physical storage devices and SAN Resources. This data can be filtered to produce various reports through the DF2112 Console.

Event Log

The Event Log details significant occurrences during the operation of the DF2112 Server. The Event Log can be viewed in the DF2112 Console when you highlight a Server in the tree and select the Event Log tab in the right pane.

The following is a sample log display:


Logs and Reports

The columns displayed are:

Sort information in the Event Log

When you initially view the Event Log, all information is displayed in chronological order (most recent at the top). If you want to reverse the order (oldest at top) or change the way the information is displayed, you can click on a column heading to re-sort the information. For example, if you click on the ID heading, you can sort the events numerically. This can help you identify how often a particular event occurs.

Filter information stored in the Event Log

By default, all informational system messages, warnings, and errors are displayed. To filter the information that is displayed:

1. Right-click on a Server and select Event Log --> Filter.

Type I: This is an informational message. No action is required.W: This is a warning message that states that something occurred that may require maintenance or corrective action. However, the DF2112 system is still operational.E: This is an error that indicates a failure has occurred such that a resource is not available, an operation has failed, or a licensing violation. Corrective action should be taken to resolve the cause of the error.C: This is a critical error that stops the system from operating properly.

Date The date on which the event occurred.

Time The time at which the event occurred.

ID This is the message number.

Event Message

This is a text description of the event describing what has occurred.


Logs and Reports

Refresh the Event Log

You can refresh the current Event Log display by right-clicking on the Server and selecting Event Log --> Refresh.

Print/Export Event Log

You can print the Event Log to a printer or save it as a text file. These options are available (once you have displayed the Event Log) when you right-click on the Server and select the Event Log options.

Select which messagetypes you want to

include.

Specify the maximumnumber of lines to

display.

Search for records thatcontain/do not contain

specific text.

Select a time or daterange for messages.


Logs and Reports

Reports

DF2112 provides reports that offer a wide variety of information:

• Performance and throughput - By SAN Client, SAN Resource, SCSI channel, and SCSI device.

• Usage/allocation - By SAN Client, SAN Resource, NAS Resource, NAS user, NAS share, Physical Resource, and SCSI adapter.

• System configuration - Physical Resources.

Reports are viewed from the Reports object in the Console.

Note: For reports with NAS data, you must enable NAS statistics gathering for this server. To do this, right-click on the server and select Properties --> NAS tab. In addition, if you want to use the "NAS Share Usage Report", "NAS Resources Usage per User Report", or "NAS Resource Usage per User Report" you need to mount NAS resources with the "usrquota" option.

Create a report

1. To create a report, right-click on the Reports object and select New.

2. Select a report.

Depending upon which report you select, additional windows appear to allow you to filter the information for the report. Descriptions of each report appear on the following pages.


Logs and Reports

3. If applicable, set the date or date range for the report and indicate which SAN Resources and Clients to use in the report.

Selecting Past 30 Days, or Past 7 Days will create reports that generate data relative to the time of execution.

Include All SAN Resources and Clients – Includes all current and previous configurations for this Server (including SAN Resources and Clients that you may have changed or deleted).

Include Current Active SAN Resources and Clients Only – Includes only those SAN Resource and Clients that are currently configured for this Server.

The Delta Replication Status report has a different dialog that lets you specify a range by selecting starting and ending dates.

4. If applicable, select the objects necessary to filter the information in the report.

Depending upon which report you selected, you may be asked to select from a list of DF2112 Servers, SCSI adapters, SCSI devices, NAS Resources, NAS shares, SAN Clients, SAN Resources, or replica resources.


Logs and Reports

5. Enter a name for the report.

6. Confirm all information and click Finish to create the report.

View a report

When you create a report, it is displayed in the right-hand pane and is added beneath the Reports object in the configuration tree.

Expand the Reports object to see the existing reports available for this Server.

When you select an existing report, it is displayed in the right-hand pane.

Export data from a report

You can save the data from the server and device throughput and usage reports. The data can be saved in a comma delimited (.csv) or tab delimited (.txt) text file. To export information, right-click on a report that is generated and select Export.


Logs and Reports

Report types

A description of each report follows.

Server Throughput and Filtered Server Throughput Report

The Server Throughput Report displays the overall throughput of the Server.

The Filtered Server Throughput Report takes a subset of Clients and/or SAN Resources and displays the throughput of that subset.

When creating the Filtered Server Throughput Report, you can specify which SAN Resources and which Clients to include.

When these reports are created, there are several tabs of information.

The SAN Resource tab displays a graph showing the throughput of the Server. The horizontal axis displays the time segments. The vertical axis measures the total data transferred in each time segment for both reads and writes. For example:

The System tab displays the CPU and memory utilization for the same time period as the main graph:


Logs and Reports

This helps the DF2112 administrator identify time periods where the load on the Server is greatest. Combined with the other reports, the specific device, Client, or SAN Resource that contributes to the heavy usage can be identified.

The Data tab shows the tabular data that was used to create the graphs:


Logs and Reports

The Configuration Information tab shows which SAN Resources and Clients were included in this report.

Client Throughput Report

The SAN Resource tab of the Client Throughput Report displays the amount of data read/written between this Client and SAN Resource. To see information for a different SAN Resource, select a different Resource Name from the drop-down box in the lower right hand corner.

The Data tab shows the tabular data that was used to create the graphs.

The following is a sample page from a Client Throughput Report:


Logs and Reports

SCSI Channel Throughput Report

The SCSI Channel Throughput Report shows the data going through each SCSI channel on the Server. This report can be used to determine which SCSI bus is heavily utilized and/or which bus is under utilized. If a particular bus is too heavily utilized, it may be possible to move one or more devices to a different or new SCSI adapter.

Some SCSI adapters have multiple channels. Each channel is measured independently.

During the creation of the report, you select which SCSI channel to include in the report.

When this report is created, there are three tabs of information.

The SAN Resource tab displays a graph showing the throughput of the channel. The horizontal axis displays the time segments. The vertical axis measures the total data transferred through the selected SCSI channel, in each time segment for both reads and writes.

The System tab displays the CPU and memory utilization for the same time period as the main graph.



Logs and Reports

The following is a sample SCSI Channel Throughput Report:


Logs and Reports

SCSI Device Throughput Report

The SCSI Device Throughput Report shows the utilization of the physical SCSI storage device on the Server. This report can show if a particular device is heavily utilized or under utilized.

During the creation of the report, you select which SCSI device to include.

The SAN Resource tab displays a graph showing the throughput of the SCSI device. The horizontal axis displays the time segments. The vertical axis measures the total data transferred through the selected SCSI device, in each time segment for both reads and writes.

The System tab displays the CPU and memory utilization for the same time period as the main graph.


The following is a sample SCSI Device Throughput Report:


Logs and Reports

SAN Client Usage Distribution Report

The Read Usage tab of the SAN Client Usage Distribution Report displays a bar chart that shows the amount of data read by Clients of the current Server. The chart shows three bars, one for each Client.

The Read Usage % tab displays a pie chart showing the percentage for each Client.

The Write Usage tab displays a bar chart that shows the amount of data written to the Clients. The chart shows three bars, one for each active Client.

The Write Usage % tab displays a pie chart showing the percentage for each Client.

The following is a sample page from a SAN Client Usage Distribution Report:


Logs and Reports

SAN Resource Usage Distribution Report

The Read Usage tab of the SAN Resource Usage Distribution Report displays a bar chart that shows the amount of data read from each SAN Resource associated with the current Server. The chart shows six bars, one for each SAN Resource (in order of bytes read).

The Read Usage % tab displays a pie chart showing the percentage for each SAN Resource.

The Write Usage tab displays a bar chart that shows the amount of data written to the SAN Resources.

The Write Usage % tab displays a pie chart showing the percentage for each SAN Resource.

The following is a sample page from a SAN Resource Usage Distribution Report:


Logs and Reports

Physical Resources Configuration Report

This report lists all of the physical resources on this Server, including each physical adapter and physical device.

The following is a sample Physical Resources Configuration Report:

DF2112 Disk Space Usage Report

This report shows the amount of disk space being used by each SCSI adapter.

The DF2112 Disk Space Usage tab displays a pie chart showing the amount of allocated vs. free disk space.


Logs and Reports

The Physical Resources Allocation tab breaks down the disk space information for each physical device.

Physical Resources Allocation Report

This report shows the disk space usage and layout for each physical device.

The following is a sample Physical Resources Allocation Report:


Logs and Reports

Physical Resource Allocation Report

This report shows the disk space usage and layout for a specific physical device.

The following is a sample Physical Resource Allocation Report:

SAN Client/Resources Allocation Report

For each Client selected, this report displays information about the resources assigned to the Client, including disk space assigned, type of access, and breakdown of physical resources.

The following is a sample SAN Client / Resources Allocation Report:


Logs and Reports

SAN Resources Allocation Report

This report displays information about the resources assigned to each Client, including disk space assigned, type of access, and breakdown of physical resources.

The following is a sample SAN Resources Allocation Report:

Delta Replication Status Report

This report displays information about replication activity. It provides a centralized view for displaying real-time replication status for all disks enabled for replication. It can be generated for an individual disk, multiple disks, source server or target server, for any range of dates. This report is useful for administrators managing multiple servers that either replicate data or are the recipients of replicated data.

The report can display information about existing replication configurations only or it can include information about replication configurations that have been deleted or promoted (you must select to view all replication activities in the database).


Logs and Reports

The following is a sample Delta Replication Status Report:

FileSafe Report

This report shows detailed replication job summary information from one or more FileSafe clients. This includes:

• Job number and name• Client name• Number of sessions in the job• Source and destination for each session• Start and end time for each session and job• Total number of errors in each session and job• Total number of files and subdirectories that were processed• Total KB processed• Number of files that were skipped because they had not changed.


Logs and Reports

The following sample report shows a single job with eight sessions. Each session represents a separate source that was included for replication.

You will note that there is a status for the job and a separate status for each session. Possible status settings are:

Status Session Level Job Level

Completed The session has been executed and all files have been processed. If some files could not be replicated, you may see a number in the Errors field, but the session is still considered complete.

All sessions are complete.

Failed The session started but could not be completed due to a problem: the source could not be opened/found, the des-tination disk could not be found, or the destination disk was full. If the source could not be opened/found, the session failed but the job continued and subsequent sessions were started.If the destination disk could not be found or was full, the session failed and subsequent sessions did not start.

All sessions have failed.

Cancelled The user stopped a session in progress. All sessions were can-celled or the job was can-celled.

Not Started The session was not executed because the job was can-celled.

Not applicable


DF2112 User Guide

SecurityDF2112 utilizes strict authorization policies to ensure proper access to storage resources on the DF2112 storage network. Since applications and storage resources are now separated, and it is possible to transmit storage traffic over a non-dedicated network, extra measures have been taken to ensure that data is only accessible to those authorized to use it.

To accomplish this, DF2112 safeguards the areas of potential vulnerability:

• System management – allowing only authorized administrators to modify the configuration of the DF2112 system.

• Data access – authenticating and authorizing the Clients who access the storage resources.

System management

DF2112 protects your system by ensuring that only the proper administrators have access to the system’s configuration. This means that the administrator’s user name and password are always verified against those defined on the DF2112 Server before access to the configuration is granted.

While the Server verifies the administrator’s login, the root user is the only one who can add or delete DF2112 administrators. The root user can also change other administrator’s passwords and has privileges to the operating system. Therefore, the Server’s root user is the key to protecting your Server and the root user’s password should always be closely guarded. It should never be revealed to other administrators.

In addition, it is important that DF2112 administrator accounts are limited to only those administrators that you trust to modify the Server configuration and these administrator accounts should be kept secret. Improper modifications of the Server configuration can result in lost data if SAN Resources are deleted or modified.

Data access

Just as DF2112 protects your system configuration by verifying each administrator as they login, DF2112 protects storage resources by ensuring that only the proper computer systems have access to the system’s resources.

For access by application servers, two things must happen, authentication and authorization.


Security

Authentication is the process of establishing the credentials of a Client and creating a trusted relationship (shared-secret) between the Client and Server. This prevents other computers from masquerading as the Client and accessing storage that it does not have rights to.

Authentication occurs the first time a Server is successfully added to a Client. Authentication only needs to be done once per Client-to-Server relationship. Subsequent access to a Server from a Client uses the authenticated shared secret to verify the Client. Credentials do not need to be re-established unless the software is re-installed.

The authentication process uses the authenticated Diffie-Hellman protocol. The password is never transmitted through the network, not even in encrypted form. Therefore the security credentials are not vulnerable to network sniffing, man-in-the-middle, or any other types of known attacks.

Authorization is the process of granting storage resources to a Client. This is done through the Console by a DF2112 administrator or the Server’s root user. The Client will only be able to access those storage resources that have been assigned to it.

Security recommendations

In order to maintain a high level of security, a DF2112 installation should be configured and used in the following manner:

Storage network topology

For performance reasons, DF2112 does not encrypt the actual storage data that is transmitted between the Server and Clients. Encrypting and decrypting every block of data transferred would incur heavy CPU overhead for both the Server and Clients. Since DF2112 transmits data over potentially shared network channels instead of a computer’s local bus, the storage data traffic can be exposed to monitoring by other computers on the same network. For this reason, a totally separate segment should be used for the storage network if a completely secure storage system is required. Only the DF2112 Clients and DF2112 Servers should be on this storage network segment.

If the configuration of your storage network does not maintain a totally separate segment for the storage traffic, it is still possible to maintain some level of security by using encryption or secure file systems on the host computers running the DF2112 Client. In this case, data written to storage devices is encrypted, and cannot be read unless you have the proper decryption tool. This is entirely transparent to the DF2112 system; these tools can only be used at the DF2112 Client as the DF2112 Server treats the data as block storage data.


Security

Physical security of machines

Due to the nature of computer security in general, if someone has physical access to a server or client, the security of that machine is compromised. By compromised, we mean that a person could copy a password, decipher DF2112 or system credentials, or copy data from that computer. Therefore, we recommend that your servers and clients be maintained in a secure computer room with limited access.

This is not necessary for the Console, because the Console does not leave any shared-secret behind. Therefore, the Console can be run from any machine, but that machine should be a "safe", non-compromised machine, specifically one that you are sure does not have a Trojan horse-like program hidden that may be monitoring or recording key strokes. Such a program can collect your password as you type, thereby compromising your system’s security. Of course, this is a general computer security concern which is not unique to DF2112. In addition, you should be aware that there is no easy way to detect the presence of such malicious programs, even by using anti-virus software. Unfortunately, many people with programming knowledge are capable of creating these types of malicious programs, which will not have a signature that anti-virus software can identify. Therefore, you should never type in your password, or any password, in an environment you cannot trust 100%.

Disable ports

Disable all unnecessary ports. The only ports required by DF2112 are:

• TCP port 11576 – Used for SAN Client and DF2112 Console to DF2112 Server management communication.

• UDP port 11577 – Used for SAN Client to DF2112 Server data access communication.

• TCP port 11580 – Used for communication between a failover pair. • TCP port 11762 – Used for DF2112 Console and DF2112 Server to SAN

Client management communication.• TCP/UDP ports 11578 – Used for DF2112 internal use.• TCP/UDP ports 11579 – Used for DF2112 internal use.• UDP port 161 – Used for SNMP traps.• TCP port 161 – Used for SNMP traps.• UDP port 137 – Used for Samba NetBios Name Service.• UDP port 138 - Used for Samba NetBios Datagram.• TCP port 139 - Used for Samba NetBios session.• TCP port 111 - Used for NFS.• UDP port 111 - Used for NFS.

• NFS port usage is assigned through the SUNRPC protocol. The ports vary, so it is not possible or convenient to keep checking them and reprogramming a firewall. Most firewalls have a setting to "Enable NFS" upon which they will change the settings if the ports themselves change.

• TCP port 3260 – Used for iSCSI.


Security

The following ports are required for BBMR only:

• UDP port 67 – DHCP port• UDP port 68 – DHCP port• UDP port 69 – TFTP port • UDP port 4011 – PXE port• UDP port 6910 – Windows boot driver login port• UDP port 6911 – Data channel between I/O server and Windows boot driver• UDP port 10703 – Heartbeat channel between login server and Windows

boot driver

Although you may temporarily open some ports during initial setup of the DF2112 Server, such as the telnet port (23) and FTP ports (20 and 21), you should shut them down after you have done your work.


DF2112 User Guide

FailoverOverview

To support mission-critical computing, DataFRAME® 2112 SAN (DF2112) provides high availability for the entire storage network, protecting you from a wide variety of problems, including:

• Network connectivity failure• Storage device path failure• Storage device failure• DF2112 Server failure (including storage device failure)

The following illustrates a basic DF2112 configuration with potential points of failure and a high availability configuration, where DF2112’s high availability options work with redundant hardware to eliminate the points of failure:


Failover

Storagedevice

IPStor Server

Ethernet Switch

Basic IPStor ConfigurationWith Points of Failure

SAN Client

IPStor Serverhardware/

software failure

Networkconnectivity

failures

Storage deviceconnectivity failure

SAN Client

Storage devicefailure

High-Availability IPStorConfiguration

(No Points of Failure)SAN

Clients

EthernetSwitches

IPStorServers

Fibre ChannelSwitches

StorageDevices

Heartbeat

Mirrored


Failover

Network connectivity failure

A network connectivity failure can occur due to a NIC, Fibre Channel HBA, cable, or switch/router failure.

You can eliminate this potential point of failure by providing multiple paths to the DF2112 Server with multiple NICs, HBAs, cables, switches/routers.

The client always tries to connect to the server with its original IP address (the one that was originally set in the client when the server was added to the client). However, for SAN/IP Clients you can add alternate network adapters to provide alternate routes to the server. DF2112 allows you to re-direct traffic to an alternate adapter by permitting you to specify the alternate IP addresses for the DF2112 Server. This can be done in the Console (right-click on the server and select Properties --> Server IP Addresses tab).

When you set this up, your DF2112 clients will attempt to communicate with the server using an alternate IP address if the original IP address stops responding.

Notes:

• In order for DF2112 to fail over when a failure occurs, the device driver must promptly report the failure. Make sure you have the latest driver available from the manufacturer. Refer to the DF2112 Release Notes for our recommendations for “tweaking” the drivers.

• In order for the clients to successfully use an alternate IP address, your subnet must be set properly so that the subnet itself can redirect traffic to the proper alternate adapter.

• The client becomes aware of the multiple IP addresses when it initially connects to the server. Therefore, if you add additional IP addresses in the Console while the client is running, you must rescan devices (Windows clients) or restart the client (Unix clients) to make the client aware of these IP addresses. In addition, if you recover from a network path failure, you will need to restart the client so that it can use the original IP address.

Storage device path failure

(Shared storage failover) A storage device path failure can occur due to a cable or switch/router failure.

You can eliminate this potential point of failure by providing a multiple path configuration, using multiple Fibre Channel switches, and/or multiple adapters, and/or storage devices with multiple controllers. In a multiple path configuration, DF2112 automatically detects all paths to the storage devices. If one path fails, DF2112 automatically switches to another. DF2112 allows you to select the primary path and the order for using the other paths. This can be done in the Console (right-click on the device and select Alias).

Note: Fibre Channel switches can demonstrate different behavior in a multiple path configuration. Before using this configuration with DF2112, you must verify that the configuration can work on your server without the DF2112 software. To verify:


Failover

1. Use the hardware vendor’s utility or Linux’s lsscsi command to see the devices after the driver is loaded.

2. Use the hardware vendor’s utility or Linux’s hdparm command to access the devices.

3. Unplug the cable from one device and use the utilities listed above to verify that everything is working.

4. Repeat the test by reversing which device is unplugged and verify that everything is still working.

Storage device failure

DF2112’s Mirroring and Cross Mirror Failover options provides high availability for DF2112 operations by minimizing the down time that can occur if a physical disk fails.

With mirroring, each time data is written to a designated disk, the same data is also written to another disk. This disk maintains an exact copy of the primary disk. In the event that the primary disk is unable to read/write data when requested to by a SAN Client, DF2112 seamlessly swaps data functions to the mirrored copy disk.

DF2112 Server failure (including storage device failure)

DF2112’s Failover overview option provides high availability for DF2112 operations by eliminating the down time that can occur should a DF2112 Server (software or hardware) fail.

In the DF2112 failover design, a DF2112 Server is configured to monitor another DF2112 Server. In the event that the server being monitored fails to fulfill its responsibilities to the clients it is serving, the monitoring server will seamlessly take over its identity so the clients will transparently fail over to the monitoring server.

DF2112 uses a unique monitoring system to ensure the health of the DF2112 Servers. This system includes a self-monitor and an intelligent heartbeat monitor.

The self-monitor is part of all DF2112 Servers, not just the servers configured for failover and provides continuous health status of the server. It is part of the process that provides operational status to any interested and authorized parties, including the Console and supported network management applications through SNMP. The self-monitor checks the DF2112 processes and connectivity to the server’s storage devices.

In a failover configuration, DF2112’s intelligent heartbeat monitor continuously monitors the primary server through the same network path that the server uses to serve its clients.

When the heartbeat is retrieved, the results are evaluated. There are several possibilities:


Failover

• All is well and no failover is necessary.• The self-monitor detects a critical error in the DF2112 Server processes that

is determined to be fatal, yet the error did not affect the network interface. In this case, the secondary will inform the primary to release its DF2112 identity and will take over serving the failed server’s clients.

• The self-monitor detects a storage device connectivity failure but cannot determine if the failure is local or applies to the secondary also. In that case the device error condition will be reported through the heartbeat.The secondary will check to see if it can successfully access the storage. If it can, it attempts to access all devices. If it can successfully access all devices, the secondary initiates a failover. If it cannot successfully access all devices, no failover occurs. If you are using DF2112’s Cross Mirror feature, a swap will occur.

Because the heartbeat uses the same network path that the server uses to serve its clients, if the heartbeat cannot be retrieved, the secondary server knows that the clients cannot access the server. This is considered a Catastrophic failure because the server or the network connectivity is incapacitated. In this case the secondary will immediately initiate a failover.


Failover

Failover overview

DF2112’s failover option provides high availability for DF2112 operations by eliminating the down time that can occur should a DF2112 Server (software or hardware) or a storage device fail. DF2112 offers two modes of failover:

• Shared storage failover - Uses a two-node failover pair to provide node level redundancy. This model requires a shared storage infrastructure and is typically Fibre Channel based.

• Non-shared storage failover (Cross mirror failover) - Provides high availability without the need for shared storage. Used with appliances containing internal storage. Mirroring is facilitated over a dedicated, direct IP connection.

Primary/Secondary

DF2112Servers

DF2112’s Primary and Secondary servers are separate, independent DF2112 Servers that each have their own assigned clients. The Primary DF2112 Server is the server that is being monitored by the Secondary DF2112 Server. In the event the primary fails, the secondary takes over. This is referred to as Active-Passive Failover.

The terms Primary and Secondary are purely from the client’s perspective since these servers may be configured to monitor each other. This is referred to as Mutual Failover or Active-Active Failover. In that case, each server is primary to its own clients and secondary to the other’s clients. Each server normally services its own clients. In the event one server fails, the other will take over and serve the failed server’s clients.

Failover/Takeover

Failover/takeover is the process that occurs when the secondary server takes over the identity of the primary. In the case of cross mirroring, failover occurs when all disks are swapped to the secondary server. Failover will occur under the following conditions:

• One or more of the DF2112 processes goes down.• There is a network connectivity problem, such as a defective NIC or a loose

network cable.• (Shared storage failover) There is a storage path failure.• The heartbeat cannot be retrieved.• There is a power failure.• One or more Fibre Channel targets is down.

Swap Swap is the process that occurs with cross mirroring when data functions are moved from a failed disk on the primary server to the mirrored disk on the secondary server. The disks are also swapped back after the problem has been fixed.

Recovery/Failback

Recovery/Failback is the process that occurs when the secondary server releases the identity of the primary to allow the primary to restore its operation. Once control has returned to the primary server, the secondary server returns to its normal monitoring mode.


Failover

After recovering from a cross mirror failure, the secondary server swaps disks back to the primary server after the disks are re-synchronized.

Asymmetricmode

(Fibre Channel only) Asymmetric failover mode requires standby ports on the secondary server in case a target port on your primary server fails.

Symmetricmode

(Fibre Channel only) Symmetric failover mode presents the same virtual disks concurrently from the target ports on both DF2112 appliances, delivering high availability without the need for standby ports.

Target paths from the primary DF2112 server are referred to as Active/Preferred paths. Target paths from the secondary DF2112 server are referred to as Active/Standby paths.

These paths are presented to the operating system as active paths that enable the operating system to recognize the device and the paths. In the event of a DF2112 appliance failure, the data path from the failed appliance is switched to the secondary appliance providing users continuous access to data without the need to swap port IDs.

Due to differences in operating systems, Symmetric failover can provide a simpler configuration for HP-UX and AIX clients.

Cross mirror failover sample configuration

This diagram illustrates a DF2112 cross mirror failover configuration. While both servers have their own storage, the number of physical disks on each machine must match. Each server has virtual disks assigned to itself and also has virtual disks that act as mirrors of disks on the other server. When a disk or storage path fails, the

Client

IPStorServers

Switch

A A’

O C

Client

IPStorServers

Switch

A A’

O C


Failover

disks are swapped and data functions are moved from the primary server to the secondary server. In the case of failover, all disks are swapped to the secondary server.


Failover

Failover requirements

The following are the requirements for setting up a failover configuration:

General failoverrequirements

• You must have two DF2112 Servers. The failover pair should be installed with identical Linux operating system versions.

• Both servers must reside on the same network segment, because in the event of a failover, the secondary server must be reachable by the clients of the primary server. This network segment must have at least one other device that generates a network ping (such as a router, switch, or server). This allows the secondary server to detect the network in the event of a failure.

• Each NIC in the primary server needs to be on its own subnet. If multiple NICs are in the same subnet, only the first IP address will be used for failover. All other IP addresses in the same subnet will be ignored.

• You need to reserve an IP address for each network adapter in your primary failover server. The IP address must be on the same subnet as the secondary server and is used by the secondary server to monitor the primary server's health. In a mutual failover configuration, these IP addresses are used by the servers to monitor each other's health. The health monitoring IP address remains with the server in the event of failure so that the server’s health can be continually monitored. Note: DF2112 clients and the Console cannot use the health monitoring IP address to connect to a server.

• You must use static IP addresses for your failover configuration. We also recommend that the IP addresses of your servers be defined in a DNS server so they can be resolved.

• If you will be using Fibre Channel target mode or iSCSI target mode, you must enable it on both the primary and secondary servers before creating your failover configuration.

• The first time you set up a failover configuration, the secondary server must not have any NAS resources or Replica resources.

• You must have at least one device reserved for a virtual device on each primary server with enough space to hold the 200 MB configuration repository that will be created. The main repository should be established on a RAID5 or RAID1 filesystem for ultimate reliability.

• We strongly recommend that you use some type of power control option for failover servers.

• If you are using an external hardware power controller for your failover pair, you should set it up before creating your failover configuration. Refer to ‘Power Control options’ for more information.


Failover

General failoverrequirements

for iSCSI clients

(Window iSCSI clients) The Microsoft iSCSI initiator has a default retry period of 60 seconds. You must change it to 300 seconds in order to sustain the disk for five minutes during failover so that applications will not be disrupted by temporary network problems. This setting is changed through the registry.

1. Go to Start --> Run and type regedit.2. Find the following registry key:

HKEY_LOCAL_MACHINE\system\CurrentControlSet\control\class\4D6E97B-xxxxxxxxx\<iscsi adapter interface>\parameters\





Failover

Cross mirrorfailover

requirements

• Each server must have identical internal storage.• Each server must have at least two network ports (one for the required

crossover cable). The network ports must be on the same subnet. • Only one dedicated cross mirror IP address is allowed for the mirror. The IP

address must be 192.168.n.n. • Only virtual devices can be mirrored. Service-enabled devices, direct

devices, and system disks cannot be mirrored.• The number of physical disks on each machine must match and the disks

must have matching ACSLs (adapter, channel, SCSI ID, LUN). • An iSCSI initiator is required to be installed on the DF2112 server and is

included on DF2112 cross mirror appliances. If you are not using a DF2112 cross mirror appliance, you must install the iSCSI initiator RPM from the Linux CD before running the df2112install installation script. The script will update the initiator.

• When failover occurs, both servers may have partial storage. To prevent a possible dual mount situation, we strongly recommend that you use a hardware power controller, such as IPMI. Refer to ‘Power Control options’ for more information.

• Prior to configuration, virtual resources can exist on the primary server as long as the identical ACSL is unassigned or unowned by the secondary server. After configuration, pre-existing virtual resources will not have a mirror. You will need to use the Verify & Repair option to create the mirror.


Failover

Failover restrictions

The following information is important to be aware of when configuring failover:

• There is no failover of direct devices. If a client is accessing a direct device when a failover occurs, the client will lose its connection to the device. After recovery, once the client is restarted, it will be reconnected to the direct device. In addition, if you create a direct device and assign it to a client while in a failover state, after recovery, the same problem will occur.

• JBODs are not recommended for failover. If you use a JBOD as the storage device for a DF2112 server (configured in Fabric Loop), certain downstream failover scenarios, such as SCSI Aliasing, might not function properly. If a Fibre connection on the DF2112 server is broken, the JBOD might hang and not respond to SCSI commands. SCSI Aliasing will attempt to connect using the other Fibre connection; however, since the JBOD is in an unknown state, the DF2112 server cannot reconnect to the JBOD, causing DF2112 clients to disconnect from their resources.


Failover

Failover setup

Note: You will need to know the IP address(es) of the primary server (and the secondary server if you are configuring a mutual failover scheme). You will also need the health monitoring IP address(es). It is a good idea to gather this information and find available IP addresses before you begin the setup.

1. In the Console, right-click on an expanded server and select Failover --> Failover Setup Wizard.

You will see a screen similar to the following that shows you a status of options on your server.

Any options enabled/installed on the primary DF2112 server must also be enabled/installed on the secondary DF2112 server.

2. If you have recently made device changes, rescan the server’s physical adapters.

Before a failover configuration can be created, the DF2112 system needs to know the ownership of each physical device for the selected server. Therefore, we recommend you allow the wizard to rescan the server’s devices.

If you have recently used the Rescan option to rescan the selected server's physical adapters, you can skip the server scanning process.


Failover

3. Select whether or not you want to use the Cross Mirror feature.

4. (Fibre Channel only) Select the type of failover configuration you want to use.

Asymmetric - Asymmetric failover requires standby ports on the secondary server in case a target port on your primary server fails.

Symmetric - Symmetric failover presents the same virtual disks concurrently from the target ports on both DF2112 appliances, delivering high availability without the need for standby ports.

Note: If you have been using Symmetric failover and you switch to Asymmetric failover, you will need to remove the extraneous paths from the client. Refer to ‘Convert a failover configuration from Symmetric to Asymmetric mode’ for more information.


Failover

5. Select the secondary server and determine if the servers will monitor each other.

If you are using DF2112 NAS and you get an error message that there is a conflict with user/group IDs on the secondary server, you should right-click on the Windows Client object (under NAS Clients) and select Properties to determine what range of user/group IDs is being used on the primary server. You should then go to the appropriate system file on the server that will become the secondary server and manually resolve the conflicting user/group IDs:

- /etc/passwd - for UIDs.- /etc/group - for GIDs.

Required for Symmetricmode. For Asymmetric

mode, select if you wantboth servers to monitor

each other.

Shared storagefailover

Click Find or manuallyenter IP address for thesecondary server. BothIP addresses must start

with 192.168.

Cross mirror failover(non-shared storage)


Failover

6. (Cross mirror only) Select the disks that will be used for the primary server.

System disks will not be listed.

The disks you select will be used as storage by the primary server. The ones that are not selected will be used as storage by the secondary server.

7. (Cross mirror only) Confirm the disks that will be used for the secondary server.


Failover

8. (Cross mirror only) Confirm the physical device allocation.

9. Follow the wizard to create a configuration repository on this server.

The configuration repository maintains a continuously updated version of your DF2112 system configuration. For additional security, after your failover configuration is complete, you can enable mirroring on the configuration repository. Be sure to use a different physical drive for the mirror.

10. Determine if there are any conflicts with the server you have selected.

If physical disks, preexisting virtual disks, or service enabled disks cannot be seen by both primary and secondary DF2112 servers, you will be alerted.

If there are conflicts, you will see a window similar to the following:

You will see mismatched devices listed here. For example, if you have a RAID array and one server sees all eight devices and the other server sees only four devices, you will see the devices listed here as mismatched.


Failover

You must resolve the mismatch before continuing. For example, the QLogic driver may not have loaded on one server and you will have to load it before going on.

Note that you can exclude physical devices from failover consideration, if desired.

11. Determine if you need to rescan this server’s physical adapters.

If you fixed any mismatched devices in the last step, you will need to rescan before the wizard can continue.

If you are re-running the Failover wizard because you made a change to a physical device on one of the servers, you should rescan before continuing.

If you didn’t have any conflicts and you have recently used the Rescan option to rescan the selected server's physical adapters, you can skip the scanning process.

Note: If this is the first time you are setting up a failover configuration, you will get a warning message if there are any NAS resources or Replica resources on the secondary server. You will need to remove them and then restart the failover wizard.

12. If this is a mutual failover configuration, follow the wizard to create a configuration repository on the secondary server.

13. Select the subnet to use for the heartbeat.

If there are multiple subnets, set the order for which the heartbeat will be checked.

By re-ordering the subnet list, failover can be avoided due to a failure on eth0.

If you are using the Cross mirror feature, you will not see the 192.168... cross mirror link that you entered earlier listed here.


Failover

14. Indicate if you want to use this network adapter.

Select the IP addresses that clients will use to access the DF2112 servers when using SAN/IP, iSCSI, replication and for Console communication.

Notes: • If you change the Server IP addresses while the Console is connected using

those IP addresses, then the Failover wizard will not be able to successfully create the configuration.

• If you uncheck the Include this Network Adapter for failover box, the wizard will display the next card it finds. You must choose at least one.

• For SAN Resources, because failover can occur at any time, you should use only those IP addresses that are configured as part of the failover configuration to connect to the server. For NAS Resources, clients will only be permitted to map to those IP addresses that are configured as part of the failover configuration.

This is the window you will see for a non-mutual failover.

Mutual failover configuration.


Failover

15. Enter the health monitoring IP address you reserved for the selected network adapter.

The health monitoring IP address remains with the server in the event of failure so that the server’s health can be continually monitored.

We recommend that you use static IP addresses.

Select health monitoring “heartbeat” addresses which will be used exclusively by the DF2112 servers to monitor each other’s health. These addresses must not be used for any other purpose.

16. If you want to use additional network adapter cards, repeat the steps above.

This is the window you will see for a non-mutual failover.

You have to enter IP addresses for both servers in a mutual failover configuration.


Failover

17. (Asymmetric mode only) For Fibre Channel failover, select the initiator on the secondary server that will function as a standby in case the target port on your primary server fails.

For QLogic HBAs, you will need to select a dedicated standby port for each target port used by clients. You should confirm that the adapter shown is not the initiator on your secondary server that is connected to the storage array, and also that it is not the target adapter on your secondary server. You can only pick a standby port once.

For LSI HBAs, select an existing initiator WWPN to use as a standby target port for the Primary DF2112 Server. Be careful not to designate the same port as a standby port multiple times.

If you are configuring a mutual failover, you will need to set up the standby adapter for the secondary server as well.

Note that a pop-up window will appear as a reminder if you used hard zoning. You must verify that standby ports are also zoned with client initiators (just like target ports).


Failover

18. Select which Power Control option the primary server is using.

Power Control options force the primary server to release its resources after a failure. Refer to ‘Power Control options’ for more information.

HP iLO - This option will power down the primary server in addition to forcing the release of the server’s resources and IP address. In order to use HP iLO, several packages must be installed on the server and you must have configured the controller’s IP address to be accessible from the DF2112 servers. In this dialog, enter the HP iLO port’s IP address. Refer to ‘HP iLO’ for more information.

RPC100 - This option will power down the primary server in addition to forcing the release of the server’s resources and IP address. RPC100 is an external power controller available in both serial and parallel versions. Select the correct port, depending upon which version you are using. Refer to ‘RPC100’ for more information.

SCSI Reserve/Release - (Not available for cross mirror configurations) This option prevents two DF2112 servers from accessing the same physical storage device simultaneously. This option is only available on those storage devices that support SCSI Reserve & Release. Refer to ‘SCSI Reserve/Release’ for more information.

IPMI - This option will reset the power of the primary server, forcing the release of the server’s resources and IP address. In order to use IPMI, you must have created an administrative user via your IPMI configuration tool. The IP address cannot be the virtual IP address that was set for failover. Refer to ‘IPMI’ for more information.

APC PDU - This option will reset the power of the primary server, forcing the release of the server’s resources and IP address. The APC PDU external hardware power controller must be set up before you can use it. In this dialog, enter the IP address of the APC PDU, the community name that was given Write+ access, and the port(s) that the failover partner is physically plugged into


Failover

on the PDU. Use a space to separate multiple ports. Refer to ‘APC PDU’ for more information.

19. Select which Power Control option the secondary server is using.

20. Confirm all of the information and then click Finish to create the failover configuration.

Once your configuration is complete, each time you connect to either server in the Console, you will automatically be connected to the other as well.

After configuring cross mirror failover, you will see all of the disks listed in the tree, similar to the following:

Note: If the setup fails during the setup configuration stage (for example, the configuration is written to one server but then the second server is unplugged while the configuration is being written to it), use the Remove Failover Configuration option to delete the partially saved configuration. You can then create a new failover configuration.

These are local physicaldisks for this server. The

V indicates the disk isvirtualized for this server

and an F indicates aforeign disk. The Q

indicates a quorum diskcontaining the

configuration repository.

These are remotephysical disks for this

server.


Failover

21. (Symmetric mode only) From each client machine, you must rescan devices in order to discover the passive paths.

After a failover occurs, if a client machine is rebooted while either of the failover servers is powered off, the client must rescan devices once the failover server is powered back on, but before recovery occurs. If this is not done, the client machine will need to be rebooted in order to discover the newly restored paths.


Failover

Power Control options

At times, a server may become unresponsive, but, because of network or internal reasons, it may not release its resources or its IP address, thereby preventing failover from occurring. To allow for graceful failover, you can use the Power Control options to force the primary server to release its resources after a failure.

Power Control options are used to prevent clusters from competing for access to the same storage. They are triggered when a secondary server fails to communicate with the primary server over both the network and the quorum drive. When this occurs, the secondary server triggers a forceful take over of the primary server and triggers the selected Power Control option.

Power Control is set during failover configuration. To change options, right-click on either failover server and select Failover --> Power Control.

HP iLO This option will power down the primary server in addition to forcing the release of the server’s resources and IP address. HP iLO is available on HP servers with the ILO (Integrated Lights Out) option. In order to use HP iLO, you must have configured the controller’s IP address to be accessible from the DF2112 servers. The console will prompt you to enter the HP iLO port’s IP address of the server. Note that the HP iLO power control option depends on DF2112 being able to access the HP iLO port through its regular network connection. If the HP iLO port is inaccessible, this option will not function.

For Red Hat Advanced Server, you will need to install the following packages on each server in order to use HP iLO power control:

• perl-IO-Socket-SSL-1.01-1.el4.rf.noarch.rpm - You can download from: http://rpmfind.net/linux/RPM/dag/redhat/el4/x86_64/perl-IO-Socket-SSL-1.01-1.el4.rf.noarch.html

• perl-Net-SSLeay-1.25-3.2.el4.rf.x86_64.rpm - You can download from:http://rpmfind.net/linux/RPM/dag/redhat/el4/x86_64/perl-Net-SSLeay-1.25-3.2.el4.rf.x86_64.html

For SUSE servers, you will need to install the following packages on each server in order to use HP iLO power control. You can find them on the SUSE Linux installation CD.

• perl-Net_SSLeay-1.25-31.x• perl-URI-1.35-3.x86_64.rpm• perl-HTML-Tagset-3.04-3.x86_64.rpm• perl-HTML-Parser-3.45-3.x86_64.rpm• perl-libwww-perl-5.803-3.x86_64.rpm• perl-IO-Socket-SSL-0.96-4.x86_64.rpm

RPC100 This option will power down the primary server in addition to forcing the release of the server’s resources and IP address. RPC100 is an external power controller available in both serial and parallel versions. The console will prompt you to select the serial or parallel port, depending upon which version of the RPC100 you are using. Note that the RPC100 power controller only controls one power connection. If the DF2112 server has multiple power supplies there will be a need for a special power cable to connect them all.


Failover

SCSI Reserve/Release

(Not available for cross mirror configurations) This option is not an actual Power Control option, but a storage solution to prevent two DF2112 servers from accessing the same physical storage device simultaneously. Note that this option is only available on those storage devices that support SCSI Reserve & Release. This option will not force a hung DF2112 server to reboot and will not force the hung server to release its IP addresses or bring down its FC targets. The secondary server will simply reserve the primary server’s physical resources, thereby preventing the possibility of a double mount. If the primary server is not actually hung and is only temporarily unable to communicate with the secondary server through normal means, the triggering of the SCSI reserve/release from the secondary server will trigger a reservation conflict on the primary server. At this point the primary server will release both its IP addresses and FC targets so the secondary can successfully take over. If this occurs the primary server will need to be rebooted before the reservation conflict can be resolved. The commands, df2112 restart and df2112 restart all will NOT resolve the reservation conflict.

IPMI This option will reset the power of the primary server, forcing the release of the server’s resources and IP address. Intelligent Platform Management Interface (IPMI) is a hardware level interface that monitors various hardware functions on a server. If IPMI is provided by your hardware vendor, you must follow the vendor’s instructions to configure it and you must create an administrative user via your IPMI configuration tool. The IP address cannot be the virtual IP address that was set for failover.

If you are using IPMI, you will see several IPMI options on the server’s System Maintenance menu, Config, Monitor, and Filter. Refer to ‘System maintenance’ for more information.

You should check the MPC certification matrix for a current list of DF2112 appliances and server hardware that has been certified for use with IPMI.

APC PDU This option will reset the power of the primary server, forcing the release of the server’s resources and IP address. The APC PDU is an external hardware power controller that must be set up before you can use it.

For RedHat servers, you will need to install the following packages on each server in order to use the APC PDU power controller for failover: You can find them on the RedHat Linux installation CD. The packages listed below are in the order that they should be installed.

• net-snmp-libs-5.1.2-11.EL4.6.i386.rpm• lm_sensors-2.8.7-2.40.3.x86_64.rpm• net-snmp-5.1.2-11.EL4.6.x86_64.rpm• net-snmp-utils-5.1.2-11.EL4.6.x86_64.rpm

To set up the APC PDU power controller:

1. Connect the APC PDU to your network.

2. Via the COM port on the unit, set an IP address that is accessible from the DF2112 servers.


Failover

3. Launch the APC PDU user interface from the COM port or the Web.

4. Enable SNMP on the APC PDU.

This can be found under Network.

5. Add or edit a Community Name and give it Write+ access.

You will use this Community Name as the password for configuration of the power control option. For example, if you want to use the password apc, you have to create a Community Name called apc or change the default Community Name to apc and give it a Write+ access.

6. Connect the power plugs of your DF2112 servers to the APC PDU.

Be sure to note which outlets are used for each server.


Failover

Check Failover status

You can see the current status of your failover configuration, including all settings, by checking the Failover Information tab for the server.

In addition, you will see a colored dot next to a server to indicate the following conditions:

• Red dot - The server is currently in failover mode and has been taken over by the secondary server.

• Green dot - The server has taken over the primary server's resources.• Yellow dot - The user has suspended failover on this server. The current

server will NOT take over the primary server's resources even it detects abnormal condition from the primary server.

Failover events are also written to the primary server's Event Log, so you can check there for status and operational information, as well as any errors. You should be aware that when a failover occurs, the Console will show the failover partner’s Event Log for the server that failed.

For troubleshooting issues pertaining to failover, refer to the ‘Failover Troubleshooting’ section.

Failover settings, including which IP addresses are being monitored for failover.

Current status of failover configuration.


Failover

After failover occurs

When a failed server is restarted, it communicates with the acting primary server and must receive the okay from the acting primary server in order to recover its role as the primary server. If there is a communication problem, such as a network error, and no notification is received, the failed server remains in a 'ready' state but does not recover its role as the primary server. After the communication problem has been resolved, the DF2112 server will then be able to recover normally.

If failover is suspended on the secondary server, or if the failover module is stopped, the primary will not automatically recover until the df2112sm.sh recovery command is entered.

If both failover servers go offline and then only one is brought up, type the df2112sm.sh recovery command to bring DF2112 back online.

Manual recovery

Manual recovery is the process when the secondary server releases the identity of the primary to allow the primary to restore its operation. Manual recovery can be triggered by selecting the Stop Takeover option from the DF2112 console.

If the primary server is not ready to recover, you will be prompted to confirm the Stop Takeover request.

Special note about Windows client recovery

(Symmetric failover mode only) If a client machine was rebooted while either of the failover servers was powered off, the client must rescan devices once the failover server is powered back on, but before recovery occurs. If this is not done, the client machine will need to be rebooted in order to discover the newly restored paths.


Failover

Auto recovery

You can enable auto recovery by changing the Auto Recovery option after failover, when control is returned to the primary server once the primary server has recovered. Once control has returned to the primary server, the secondary server returns to its normal monitoring mode.

Fix a failed server

If the primary server fails over to the secondary and hardware changes are made to the failed server, the secondary server will not be aware of these changes. When failback occurs, the original configuration parameters will be returned to the primary server.

To ensure that both servers become synchronized with the new hardware information, you will need to issue a physical device rescan for the machine whose hardware has changed as soon as the failback occurs.


Failover

Recover from a cross mirror disk failureRe-synchronize cross mirror

After recovering from a cross mirror failure, the disks will be automatically re-synchronized. However, disks will need to be manually re-synchronized if the disk is offline for more than 20 minutes.

Right-click on the server and select Cross Mirror --> Synchronize to manually re-synchronize the disks.

Check resources and swap if possible

Swapping takes place when data functions are moved from a failed disk on the primary server to the mirrored disk on the secondary server. Afterwards, the system automatically checks every hour to see if the disks can be swapped back.

If the disk has been replaced/repaired and the cross mirror has been synchronized, you can force a swap to occur now.

To do this, select Cross Mirror --> Check & Swap. The system will check that the local mirror disk is usable and that the cross mirror is synchronized. If they are, the system will swap disks. You can check the Layout tab for the SAN resource afterwards to see the status.

Verify and repair a cross mirror configuration

Use the Verify & Repair option for the following situations:

• A physical disk used by the cross mirror has been replaced• A mirror resource was offline when auto expansion occurred • Create a mirror for virtual resources that existed on the primary server prior

to configuration• View the storage exception information that cannot be repaired and requires

further assistance.

When replacing local or remote storage, if a mirror needs to be swapped first, a swapping request will be sent to the server to trigger the swap. Storage can only be replaced when the damaged segments are part of the mirror, either local or remote. New storage has to be available for this option.

Note: If you have replaced disks, you should perform a rescan on both servers before using the Verify & Repair option.

To use the Verify & Repair option:

1. Log into both cross mirror servers.

2. Right-click on the primary server and select Cross Mirror --> Verify & Repair.

3. Click the button for any issue that needs to be corrected.

You will only be able to select a button if that is the scenario where the problem occurred. The other buttons will not be selectable.


Failover

Resources If everything is working correctly, this option will be labelled Resources and will not be selectable. The option will be labelled Incomplete Resources for the following scenarios:

• The mirror resource was offline when auto expansion (i.e. Snapshot resource or CDP journal) occurred but the device is now back online.

• You need to create a mirror for virtual resources that existed on the primary server prior to cross mirror configuration.

1. Right-click on the server and select Cross Mirror --> Verify & Repair.

2. Click the Incomplete Resources button.

3. Select the resource to be repaired.

4. When prompted, confirm that you want to repair this resource.


Failover

RemoteStorage

If everything is working correctly, this option will be labelled Remote Storage and will not be selectable. The option will be labelled Damaged or Missing Remote Storage when a physical disk being used by cross mirroring on the secondary server has been replaced.

1. Right-click the primary server and select Cross Mirror --> Verify & Repair.

2. Click the Damaged or Missing Remote Storage button.

3. Select the remote device to be repaired.


Failover

Local Storage If everything is working correctly, this option will be labelled Local Storage and will not be selectable. The option will be labelled Damaged or Missing Local Storage when a physical disk being used by cross mirroring is damaged on the primary server and has been replaced.

Note: You must suspend failover before replacing the storage.

1. Right-click the primary server and select Cross Mirror --> Verify & Repair.

2. Click the Damaged or Missing Local Storage button.

3. Select the local device to be replaced.

4. Confirm that this is the device to replace.


Failover

Storage andComplete

Resources

If everything is working correctly, this option will be labelled Storage and Complete Resources and will not be selectable. The option will be labelled Resources with Missing segments on both Local and Remote Storage when a virtual device spans multiple physical devices and one physical device is offline on both the primary and secondary server. This situation is very rare and this option is informational only.

1. Right-click on the server and select Cross Mirror --> Verify & Repair.

2. Click the Resources with Missing segments on both Local and Remote Storage button.

You will see a list of failed devices. Because this option is informational only, no action can be taken here.


Failover

Modify failover configuration

Make changes to the servers in your failover configuration

The first time you set up your failover configuration, the secondary server cannot have any NAS resources or Replica resources.

In order to make any changes to a mutual failover configuration, you must be running the Console with write access to both servers. DF2112 will automatically "log on" to the failover pair when you attempt any configuration on the failover set. While it is not required that both servers have the same username and password, the system will try to connect to both servers using the same username and password. If the servers have different usernames/passwords, it will prompt you to enter them before you can continue.

Changephysical device

If you make a change to a physical device (such as if you add a network card that will be used for failover), you will need to re-run the Failover wizard. Be sure to scan both servers during the wizard.

At that point, the secondary server is permitted to have NAS resources and Replica resources. This makes it easy for you to upgrade you failover configuration.

Change subnet If you switch IP segments for an existing failover configuration, the following needs to be done:

1. Remove failover from both DF2112 Servers.

2. Delete the current failover servers from the DF2112 Console.

3. Make network modifications to the DF2112 Servers (i.e. change IP segments).

4. Add the DF2112 Servers back to the DF2112 Console.

5. Configure failover using the new IP segment.

Convert a failover configuration into a mutual failover configuration

Right-click on the server and select Failover --> Setup Mutual Failover to convert your failover configuration into a mutual failover configuration where both servers monitor each other.

Note: If there is no configuration repository on the current secondary server, you will have to remove the failover configuration and then configure mutual failover.


Failover

Exclude physical devices from health checking

You can create a storage exception list that will exclude one or more specific physical devices from being monitored. Devices on this list will not prompt the system to fail over, even if the device stops functioning.

This is useful when using less reliable storage (for asynchronous mirroring or local replication), whose temporary loss will not be critical.

When removing failover, this list is reset and cleaned up.

To exclude devices, right-click on the server and select Failover --> Storage Exception List.

Change your failover intervals

Right-click on the server and select Failover --> View/Update Failover Options to change the intervals (heartbeat, self-checking, and auto recovery) for this configuration.

Note: We recommend keeping the Self-checking Interval and Heartbeat Interval set to the default values. Changing the values can result in a significantly longer failover and recovery process.

The Self-checking Interval determines how often the primary server will check itself.

The Heartbeat Interval determines how often the secondary server will check the heartbeat of the primary server.

If enabled, Auto Recovery determines how long to wait before returning control to the primary server once the primary server has recovered.


Failover

Convert a failover configuration from Symmetric to Asymmetric mode

If you have been using Symmetric failover and you switch to Asymmetric failover, you will need to remove the extraneous paths from the client. The commands to do this depend on the operating system of the client.

Note: Rebooting the client machine may be necessary if the devices cannot be removed using the commands below.

AIX rmdev – dl <disk device>

HPUX: rmsf –H <hardware path of the SCSI disk device>

Linux (2.4kernel)

echo “scsi remove-single-device A:C:S:L” > /proc/scsi/scsi

A C S L stands for: Adapter, Channel, SCSI, and LUN.

Linux (2.6kernel)

echo "1" > /sys/class/scsi_device/DeviceID/device/delete

Where DeviceID is obtained from ls /sys/class/scsi-device

For example:

echo "1" > /sys/class/scsi_device/1:0:0:0/device/delete

NetWare Scan all devices

Solaris SUN StorEdge SCSI devices:

cfgadm –c unconfigure <ap_id>

Basic SCSI devices:

devfsadm –Cv sd

Windows 1. Right click on My Computer.

2. Select Manage.

3. Under Computer Management window, click Device Manager.

4. Right-click on Disk drives.

5. Select Scan for hardware changes.

Verify physical devices match

The Check Consistency tool (right-click on the server and select Failover --> Check Consistency) helps verify that both nodes can still see the same LUNs or the same number of LUNs. This is useful when physical storage devices need to be added or removed. After suspending failover and removing/adding storage to both nodes, you would first perform a rescan of the resources on both sides to pick up the changes in configuration. After verifying storage consistency between the two nodes, failover can be resumed without risking a failover trigger.


Failover

Start/stop failover or recovery

Force a takeover by a secondary server

On the secondary server, select Failover --> Start Takeover <servername> to initiate a failover to the secondary server. You may want to do this if you are taking your primary server offline, such as when you will be performing maintenance on it.

Once failover is complete, a failover message will blink in red at the bottom of the Console and you will be disconnected from the primary server.

Manually initiate a recovery to your primary server

Select Failover --> Stop Takeover if your failover configuration was not set up to use DF2112’s Auto Recovery feature and you want to force control to return to your primary server or if you manually forced a takeover and now want to recover to your primary server.

Once failback is complete, you will be logged off from the virtual primary server.

Suspend/resume failover

Select Failover --> Suspend Failover to stop monitoring its partner server.

In the case of Active-Active failover, you can suspend from either server. However, the server that you suspend from will stop monitoring its partner and will not take over for that partner server in the event of failure. It can still fail over itself. For example, server A and server B are configured for Active-Active failover. If you go to server B and suspend failover, server A will no longer fail over to server B. However, server B can still fail over to server A.

Select Failover --> Resume Failover to restart the monitoring.

Notes:

• If the cross mirror link goes down, failover will be suspended. Use the Resume Failover option when the cross mirror link comes back up. The disks will automatically be re-synced.

• If you stop the DF2112 processes on the primary server after suspending failover, you must do the following once DF2112 has been restarted:1. At a Linux command prompt, type sms to determine if the system is in a ready state. 2. As soon as it becomes ready, type the following: df2112sm.sh recovery


Failover

Remove a failover configuration

Right-click on one of your failover servers and select Failover --> Remove Failover Server to remove the selected server from the failover configuration. In a one-way failover configuration, this eliminates the configuration and returns the servers to independent DF2112 Servers.

If this is a mutual failover configuration and you want to eliminate the failover relationship from both sides, select the Remove Mutual Failover option.

If this is a mutual failover configuration, and you do not select the Remove Mutual Failover option, this server (the one you right-clicked on) becomes the secondary server in a non-mutual configuration.

If you are using Symmetric mode, you must remove failover from both servers.

If everything is checked, this eliminates the failover relationship and removes the health monitoring IP addresses from the servers and restores the Server IP addresses. If you uncheck the IP address(es) for a server, the health monitoring address becomes the Server IP address.

Note: If you are using cross mirror failover, after removal the cross mirror relationship will be gone but the configuration of your iSCSI initiator will remain and the disks will still be presented to both primary and secondary servers.

Required for Symmetricmode. For Asymmetric

mode, select if you wantto eliminate the failover

relationship from bothsides.


Failover

Mirroring and Failover

(Shared storage failover) If a physical drive contains only a mirrored resource and the physical drive fails, the server will not fail over. If the physical drive contained a primary mirrored resource, the mirror will swap roles so that its mirrored copy becomes the primary disk. If the physical drive contained a mirrored copy, nothing will happen to the mirror because there is no need for the mirror to swap. If there are other virtual devices on the same physical drive and the other virtual devices are not mirrored resources, the server will fail over. Swapping will only occur if all of the virtual devices on the physical drive contain mirrored resources.

TimeMark/CDP and Failover

Clients may not be able to access TimeViews during failover.


DF2112 User Guide

MirroringMirroring provides high availability for DF2112 operations by minimizing the down time that can occur if a physical disk fails. The mirror can be defined with disks that are not necessarily identical to each other in terms of vendor, type, or even interface (SCSI, FC, iSCSI).

With mirroring, the primary disk is the disk that is used to read/write data for a SAN Client and the mirrored copy is a copy of the primary. Both disks are attached to a single DF2112 Server and are considered a mirrored pair. If the primary disk fails, the disks swap roles so that the mirrored copy becomes the primary disk.

DF2112 has two Mirroring options, Synchronous Mirroring and Asynchronous Mirroring.

Synchronous Mirroring

DF2112’s Synchronous Mirroring option offers the ability to define a synchronous mirror for any DF2112 managed disk (virtualized or service-enabled).

In the Synchronous Mirroring design, each time data is written to a designated disk, the same data is simultaneously written to another disk. This disk maintains an exact copy of the primary disk. In the event that the primary disk is unable to read/write data when requested to by a SAN Client, DF2112 seamlessly swaps data functions to the mirrored copy disk.

M irroring O peration

IP S tor

P RIM AR Y M IR RO R

IP S tor

PR IM ARY M IRRO R

After Physical D isk Failure

ApplicationS erver

ApplicationS erver


Mirroring

Asynchronous Mirroring

DF2112’s Asynchronous Mirroring Option offers the ability to define a near real-time mirror for any DF2112-managed disk (virtual or service-enabled) over long distances between data centers.

When you configure an asynchronous mirror, you create a dedicated cache resource and associate it to a DF2112-managed disk. Once the mirror is created, DF2112 synchronizes the primary and secondary disks. This process does not involve the application server. After the synchronization is complete, all write-requests from the associated application server are sequentially delivered to the dedicated cache resource. This data is then committed to both the primary and its mirror as a separate background process. For added protection, the cache resource can also be mirrored.

1 2 3 4 5

6 7 8 9

1

2

3

4

5 6

7

8

9

STAGING AREA

PRIMARY DISK

1

2

3

4

5 6

7

8

9

MIRROR DISK

For read operations, thecache resource ischecked first in case anewly written block hasnot yet been moved to thedata disk.

Blocks are moved to the primarydisk and mirror disk (random write)as a secondary operation, afterwrites have been acknowledgedfrom the cache resource.

Data blocks arewritten sequentially tothe cache resource toprovide enhancedwrite performance.

IPStor

PRIMARY

STAGINGAREA

MIRROR

Primary Site Remote Site

WRITES ACKNOWLEDGEMENT


Mirroring

Mirror requirements

The following are the requirements for setting up a mirroring configuration:

• The mirrored devices must be composed of one or more hard disks. • The mirrored devices must both be accessible from the same DF2112

Server.• The mirrored devices must be the same size. If you try to expand the

primary disk, DF2112 will also expand the mirrored copy to the same size.

Mirror setup

You can enable mirroring for a single SAN or NAS Resource or you can use the batch feature to enable mirroring for multiple SAN or NAS Resources. You can also enable mirroring for an existing snapshot resource, cache resource, or incoming replica resource.

Note: For asynchronous mirroring, if you want to preserve the write order of data that is being mirrored asynchronously, you should create a group for your SAN/NAS Resources and enable SafeCache for the group. This is useful for large databases that span over multiple devices. In such situations, the entire group of devices is acting as one huge device that contains the database. When changes are made to the database, it may involve different places on different devices, and the write order needs to be preserved over the group of devices in order to preserve database integrity. Refer to ‘Groups’ for more information about creating a group.

1. For a single SAN or NAS Resource, right-click on the resource and select Mirror --> Add.

For multiple SAN or NAS Resources, right-click on the SAN Resources or NAS Resources object and select Mirror --> Add.

For an existing snapshot resource or cache resource, right-click on the SAN or NAS Resource and select Snapshot Resource or Cache Resource --> Mirror --> Add.


Mirroring

2. (SAN or NAS Resources only) Select the type of mirrored copy you are creating.

3. Select the storage pool or physical device(s) from which to create the mirror.


Mirroring

4. Select how you want to create this mirror.


Express automatically creates the Mirrored Copy using the criteria you select:

- Select different drive - DF2112 will look for space on another hard disk.

- Select drives from different adapter/channel - DF2112 will look for space on another hard disk only if it is on a separate adapter/channel.

- Select any available drive - DF2112 will look for space on any disk, including the original. This option is useful if you have mapped a device (such as a RAID device) that looks to DF2112 like a single physical device.


Mirroring


Select either an entirely unallocated or partially unallocated disk.

Only one disk can be selected at a time from this dialog. To create a mirrored disk from multiple physical disks, you will need to add the disks one at a time. After selecting the parameters for the first disk, you will have the option to add more disks.

Indicate how much space to allocate from this disk.

Click Add More if you need to add more space to this mirrored disk.If you select to add more disks, you will go back to the physical device selection screen where you can select another disk.


Mirroring

5. (SAN or NAS Resources only) Indicate if you want to use synchronous or asynchronous mirroring.

If a cache resource already exists, mirroring will automatically be set to asynchronous mode.

If no cache resource exists, you can use either synchronous or asynchronous mode. However, if you select asynchronous mode, you will need to create a cache resource. The wizard will guide you through creating it.

If you select synchronous mode for a resource without a cache and later create a cache, the mirror will switch to asynchronous mode.

Note: If you are enabling asynchronous mirroring for multiple resources that are being used by the same application (for example, your Oracle database spans three disks), to ensure write order consistency you must first create a group. You must enable SafeCache for this group and add all of the related resources to it before enabling asynchronous mirroring for each resource. By doing this, all of the resources will share the same read/write cache and will be flushed at the same time, thereby guaranteeing the consistency of the data.


Mirroring

6. Determine if you want to monitor the mirroring process.

If you select to monitor the mirroring process, DF2112 will check the I/O performance to decide if I/O to the mirror disk is lagging beyond an acceptable limit. If it is, mirroring will be suspended so it does not impact the primary storage.

Monitor mirroring process every n seconds - Specify how frequently the system should check the lag time (delay between I/O to the primary disk and the mirror). Checking more or less frequently will not impact system performance. On systems with very low I/O, a higher number may help get a more accurate representation.

Maximum lag time for mirror I/O - Specify an acceptable lag time.

Suspend mirroring when the failure threshold reaches n% - Specify what percentage of I/O must pass the lag time test. For example, you set the percentage to 10% and the maximum lag time to 15 milliseconds. During the test period, 100 I/O occurred and 20 of them took longer than 15 milliseconds to update the mirror disk. With a 20% failure rate, mirroring would be suspended.

Note: If a mirror becomes out of sync because of a disk failure or an I/O error (rather than having too much lag time), the mirror will not be suspended. Because the mirror is still active, re-synchronization will be attempted based on the global mirroring properties that are set for the server. Refer to ‘Set global mirroring options’ for more information.


Mirroring

7. If mirroring is suspended, specify when re-synchronization should be attempted.

Re-synchronization can be started based on time (every n minutes/hours) and/or I/O activity (when I/O is less than n KB/MB). If you select both, the time will be applied first before the I/O activity level. If you do not select either, the mirror will stay suspended until you manually synchronize it.

If you select one or both re-synchronization methods, you must also specify how many times the system should retry the re-synchronization if it fails to complete.

When the system initiates re-synchronization, it does not check lag time and mirroring will not be suspended if there is too much lag time.

If you manually resume mirroring, the system will monitor the process during synchronization and check lag time. Depending upon your monitoring policy, mirroring will be suspended if the lag time gets above the acceptable limit.

Note: If DF2112 is restarted or the server experiences a failover while attempting to re-synchronize, the mirror will remain suspended.

8. Confirm that all information is correct and then click Finish to create the mirroring configuration.


Mirroring

Create cache resource

The cache resource wizard will be launched automatically when you configure Asynchronous Mirroring but you do not have a cache resource. You can also create a cache resource by right-clicking on a SAN or NAS Resource and selecting SafeCache --> Enable. For multiple SAN or NAS Resources, right-click on the SAN Resources or NAS Resources object and select SafeCache --> Add.

1. Select how you want to create the cache resource.

Note that the cache resource cannot be expanded. Therefore, you should allocate enough space for your SAN/NAS resource, taking into account future growth. If you “outgrow” your cache resource, you will need to disable it and then recreate it.


Express automatically creates the cache resource using the criteria you select:




2. Confirm that all information is correct and then click Finish to create the cache resource.

You can now mirror your cache resource by highlighting the SAN or NAS Resource and selecting SafeCache --> Mirror --> Add.


Mirroring

Check mirroring status

You can see the current status of your mirroring configuration by checking the General tab for a mirrored resource.

• Synchronized - Both disks are synchronized. This is the normal state.• Not synchronized - A failure in one of the disks has occurred or

synchronization has not yet started. If there is a failure in the Primary Disk, DF2112 swaps the Primary Disk with the Mirrored Copy.

• If the synchronization is occurring, you will see a progress bar along with the percentage that is completed.

Note: In order to update the mirror synchronization status, refresh the Console screen (View --> Refresh).

Current status ofmirroring configuration.


Mirroring

Swap the primary disk with the mirrored copy

Right-click on the SAN or NAS Resource and select Mirror --> Swap to reverse the roles of the primary disk and the mirrored copy. You will need to do this if you are going to perform maintenance on the primary disk or if you need to remove the primary disk.

Promote the mirrored copy to become an independent virtual drive

Right-click on the mirrored drive and select Mirror --> Promote to break the mirrored pair and convert the mirrored copy into an independent virtual drive. The new virtual drive will have all of the properties of a regular virtual drive.

This feature is useful as a “safety net” when you perform major system maintenance or upgrades. Simply promote the mirrored copy and you can perform maintenance on the primary disk without worrying about anything going wrong. If there is a problem, you can use the newly promoted virtual drive to serve your clients.

Notes: • Before promoting a mirrored drive, all clients should first detach or unmount from the drive. Promoting a drive while clients are attached or mounted may cause the file system to become corrupt on the promoted drive.

• If you are copying files over in Windows to a SAN Resource that has a mirror, you need to wait for the cache to flush out before promoting the mirrored drive on the SAN Resource. If you do not wait for the cache to flush, you may see errors in the files.

• If you are using asynchronous mirroring, you can promote the mirror only when the SafeCache option is suspended and there is no data in the cache resource that needs to be flushed.

• When you promote the mirror of a replica resource, the replication configuration is maintained.

• Depending upon the replication schedule, when you promote the mirror of a replica resource, the mirrored copy may not be an identical image of the replication source. In addition, the mirrored copy may contain corrupt data or an incomplete image if the last replication was not successful or if replication is currently occurring. Therefore, it is best to make sure that the last replication was successful and that replication is not occurring when you promote the mirrored copy.

• After promoting a mirror of a NAS Resource, the folder(s) of the promoted NAS Resource may not be displayed. To display the folder(s), right-click on the specific NAS Resource and select Refresh.


Mirroring

Recover from a mirroring hardware failure

Replace afailed disk

If one of the mirrored disks has failed and needs to be replaced:

1. Right-click on the SAN or NAS Resource and select Mirror --> Remove to remove the mirroring configuration.

2. Physically replace the failed disk.

The failed disk is always the Mirrored Copy because if the Primary Disk fails, DF2112 swaps the Primary Disk with the Mirrored Copy.

Important: To replace the disk without having to reboot your DF2112 Server, refer to ‘Replace a failed physical disk without rebooting your DF2112 Server’.

3. Run the Create SAN Resource Mirror Wizard to create a new mirroring configuration.

Fix a minor diskfailure

If one of the mirrored disks has a minor failure, such as a power loss:

1. Fix the problem (turn the power back on, plug the drive in, etc.).

2. Right-click on the SAN or NAS Resource and select Mirror --> Synchronize.

This re-synchronizes the disks and restarts the mirroring.

Replace a disk that is part of an active mirror configuration

If you need to replace a disk that is part of an active mirror configuration:

1. If you need to replace the Primary Disk, right-click on the SAN or NAS Resource and select Mirror --> Swap to reverse the roles of the disks and make it a Mirrored Copy.

2. Select Mirror --> Remove to cancel mirroring.

3. Replace the disk.


4. Run the Create SAN Resource Mirror Wizard to create a new mirroring configuration.


Mirroring

Replace a failed physical disk without rebooting your DF2112 Server

Do the following if you need to replace a failed physical disk without rebooting your DF2112 Server.

1. If you are not sure which physical disk to remove, execute the following to access the drive and cause the disk’s light to blink:

where ‘#’ represents a,b,c,d, … depending on the order of the disks.

2. You MUST remove the SCSI device from the Linux OS.

Type the following for Linux (2.4 kernel):echo “scsi remove-single-device A:C:S:L” > /proc/scsi/scsi

A C S L stands for: Adapter, Channel, SCSI, and LUN. This can be found in the Console.

Type the following for Linux (2.6 kernel):echo "1" > /sys/class/scsi_device/DeviceID/device/delete


For example:echo "1" > /sys/class/scsi_device/1:0:0:0/device/delete

3. Execute the following to re-add the device so that Linux can recognize the drive:

where x x x x stands for A C S L numbers: Adapter, Channel, SCSI, and LUN number

4. Rescan the adapter to which the device has been added.

In the Console, right-click on AdaptecSCSI Adapter.x and select Rescan, where x is the adapter number the device is on.

hdparm -t /dev/sd#

echo "scsi add-single-device x x x x">lsscsi


Mirroring

Expand the primary disk

The mirrored devices must be the same size. If you want to enlarge the primary disk, you will need to enlarge the mirrored copy to the same size. When you use the Expand SAN Resource Wizard, it will automatically launch the Create SAN Resource Mirror Wizard so that you can enlarge the Mirrored Copy as well.

Note: As you expand the primary disk, the wizard will only show half the available disk space as available because it has reserved an equal amount of space for the mirrored drive.

Manually synchronize a mirror

The Synchronize option re-synchronizes a mirror and restarts the mirroring process once it is synchronized. This is useful if one of the mirrored disks has a minor failure, such as a power loss.


2. Right-click on the resource and select Mirror --> Synchronize.

During the synchronization, the system will monitor the process and check lag time. Depending upon your monitoring policy, mirroring will be suspended if the lag time gets above the acceptable limit.

Rebuild a mirror

The Rebuild option rebuilds a mirror from beginning to end and starts the mirroring process once it is synchronized. This is useful if the mirror disk you want to synchronize is from a different DF2112 server.

This would be necessary if your disaster recovery site has been servicing clients due to some type of problem, like a storm or power outage, at your primary data center. After the problem is resolved, the mirror is out of sync. Because the mirror disk is located remotely, on a different DF2112 server, the local DF2112 server cannot determine how to synchronize it and must rebuild the mirror from beginning to end.

Before you rebuild a mirror, you would need to stop client activity. After rebuilding the mirror, you would swap the mirror so that the primary data center could service clients again.

1. Right-click on a resource and select Mirror --> Rebuild.

You can see the current settings by checking the Mirror Synchronization Status field on the General tab of the resource.


Mirroring

Suspend/resume mirroring

You can suspend mirroring for an individual resource or for multiple resources. When you manually suspend a mirror, the system will not attempt to re-synchronize, even if you have a re-synchronization policy. You will have to resume the mirror in order to synchronize.

When you resume mirroring, the mirror is synchronized before mirroring is resumed. During the synchronization, the system will monitor the process and check lag time. Depending upon your monitoring policy, mirroring will be suspended if the lag time gets above the acceptable limit.

To suspend/resume mirroring for an individual resource:

1. Right-click on a resource and select Mirror --> Suspend (or Resume).


To suspend/resume mirroring for multiple resources:

1. Right-click on the SAN Resources object and select Mirror --> Suspend (or Resume).

2. Select the appropriate resources.

3. If the resource is in a group, select the checkbox to include all of the group members enabled with mirroring.


Mirroring

Change your mirroring configuration options

Set globalmirroring

options

You can set global mirroring options that affect system performance during mirroring. While the default settings should be optimal for most configurations, you can adjust the settings for special situations.

To set global mirroring properties for a server:


2. Select the Performance tab.

Use [n] outstanding commands of [n] KB - The number of commands being processed at one time and the I/O size. This must be a multiple of the sector size.

Synchronize Out-of-Sync Mirrors - Determine how often the system should check and attempt to re-synchronize active out-of-sync mirrors, how often it should retry synchronization if it fails to complete, and whether or not to include replica mirrors. These settings will only be used for active mirrors. If a mirror is suspended because the lag time exceeds the acceptable limit, that re-synchronization policy will apply instead.

Changeproperties for a

specificresource

You can change the following mirroring configuration for a resource:

• Policy for monitoring the mirroring process• Conditions for re-synchronization

To change the configuration:

1. Right-click on the primary disk and select Mirror --> Properties.

2. Make the appropriate changes and click OK.

Remove a mirror configuration

Right-click on the SAN or NAS Resource and select Mirror --> Remove to delete the mirrored copy and cancel mirroring. You will not be able to access the mirrored copy afterwards.

Mirroring and Failover

If mirroring is in progress during failover/recovery, after the failover/recovery the mirroring will restart from where it left off.

If the mirror is synchronized but there is a Fibre disconnection between the server and storage, the mirror may become unsynchronized. It will re-synchronize automatically after failover/recovery.

A synchronized mirror will always remain synchronized during a recovery process.


DF2112 User Guide

Near-line MirroringNear-line mirroring allows production data to be synchronously mirrored to a protected disk that resides on a second DataFRAME® 2112 SAN (DF2112) server.

With near-line mirroring, the primary disk is the disk that is used to read/write data for a SAN Client and the mirrored copy is a copy of the primary. Each time data is written to the primary disk, the same data is simultaneously written to the mirror disk. TimeMark or CDP can be configured on the near-line server to create recovery points. The near-line mirror can also be replicated for disaster recovery protection.

If the primary disk fails, you can initiate recovery from the near-line server and roll back to a valid point-in-time.

IPStor

Service Enabled Disk

Synchronous Mirror

Synchronous Mirror

Production Nearline

Application Servers

IPStor


Near-line Mirroring

Before you begin

Enable option Before you can use near-line mirroring, you must obtain the appropriate server and console patches from MPC and you must enable the option. To do this:

1. Edit the DF2112Console.cfg file.

This file can be found in the \Program Files\MPC\DF2112\Console\Bin directory.

2. Scroll down to the bottom of the file and locate the following statements:Console.supportProtectedDisk=falseConsole.protectDiskRescanAttempts=1Console.secondsBeforeRescanRetry=1

3. Set the first statement to true.

4. Set the last two statements to 3.

FC protocol If you are using the FC protocol for your near-line mirror, zone the appropriate initiators on your primary server with the targets on your near-line server. For recovery purposes, zone the appropriate initiators on your near-line server with the targets on your primary server.

iSCSI protocol If you are using the iSCSI protocol for your near-line mirror, on the primary server edit the \etc\iscsi.conf file and add the IP address of the near-line server. For recovery purposes, on the near-line server, add the IP address of the primary server.

If you are using the iSCSI protocol for your near-line mirror, you should start the iSCSI initiator on the primary server before DF2112 is started. The instructions below explain how to automatically start the iSCSI initiator on the primary server. Note that for recovery purposes, you will need to do the same thing on the near-line server.

1. Create a file "vi /etc/rc.d/init.d/iscsi_start".

2. Add the following line to this file: "/etc/init.d/iscsi start".

3. Save the file.

4. Make the file executable by typing the following at a command prompt:

chmod +x /etc/init.d/iscsi start5. Create a symbolic link:

ln -s /etc/rc.d/init.d/iscsi_start /etc/rc.d/rc3.d/S98iscsi

ln -s /etc/rc.d/init.d/iscsi_start /etc/rc.d/rc5.d/S98iscsi

Near-line mirroring requirements

The following are the requirements for setting up a near-line mirroring configuration:

• The primary server cannot be configured to replicate to the near-line server.• At least one protocol (FC or iSCSI) must be enabled on the near-line server.


Near-line Mirroring

Near-line mirroring setup

You can enable near-line mirroring for a single SAN Resource.

1. Right-click on the resource and select Near-line Mirror --> Add.

2. Specify if you want to enable near-line mirroring for the primary disk or just prepare the near-line disk.

When you create a near-line disk, the primary server performs a rescan to discover new devices. If you are configuring multiple near-line mirrors, the scans can become time consuming. Instead, you can select to prepare the near-line disk now and then manually rescan physical resources and discover new resources on the primary server. Afterwards, you will have to re-run the wizard and select the existing, prepared disk.


Near-line Mirroring

3. Select the storage pool or physical device(s) for the near-line mirror’s virtual header information.

4. Select the server that will contain the near-line mirror.

5. Add the primary server as a client of the near-line server.

You will go through several screens to add the client:


Near-line Mirroring

• Confirm or specify the IP address the primary server will use to connect to the near-line server as a client. This IP address is used for iSCSI; it is not used for Fibre Channel.

• Determine if you want to enable persistent reservation for the client (primary server). This allows clustered clients to take advantage of Persistent Reserve/Release to control disk access between various cluster nodes.

• Select the client’s protocol(s). If you select iSCSI, you must indicate if this is a mobile client.

• (FC protocol) Select or add WWPN initiators for the client. • (FC protocol) Specify if you want to use Volume Set Addressing (VSA) and/

or QoS. VSA is used primarily for addressing virtual buses, targets, and LUNs. If your storage devices use VSA, you must enable it. QoS controls the quality of service for each target port based on priority.

• (iSCSI protocol) Select the initiator that this client uses. If the initiator does not appear, you may need to rescan. You can also manually add it, if necessary.

• (iSCSI protocol) Add/select users who can authenticate for this client. • (iSCSI protocol) Specify which QoS level to use to control the quality of

service for each target port based on priority.

6. Confirm the IP address of the primary server.

Confirm or specify the IP address the near-line server will use to connect to the primary server when a TimeMark is created, if snapshot notification is used. If needed, you can specify a different IP address from what you used when you added the primary server as a client of the near-line server.


Near-line Mirroring

7. Determine if you want to monitor the mirroring process.

If you select to monitor the mirroring process, DF2112 will check the I/O performance to decide if I/O to the mirror disk is lagging beyond an acceptable limit. If it is, mirroring will be suspended so it does not impact the primary storage.

Monitor mirroring process every n seconds - Specify how frequently the system should check the lag time (delay between I/O to the primary disk and the mirror). Checking more or less frequently will not impact system performance. On systems with very low I/O, a higher number may help get a more accurate representation.

Maximum lag time for mirror I/O - Specify an acceptable lag time.

Suspend mirroring when the failure threshold reaches n% - Specify what percentage of I/O must pass the lag time test. For example, you set the percentage to 10% and the maximum lag time to 15 milliseconds. During the test period, 100 I/O occurred and 20 of them took longer than 15 milliseconds to update the mirror disk. With a 20% failure rate, mirroring would be suspended.

Note: If a mirror becomes out of sync because of a disk failure or an I/O error (rather than having too much lag time), the mirror will not be suspended. Because the mirror is still active, re-synchronization will be attempted based on the global mirroring properties that are set for the server. Refer to ‘Set global mirroring options’ for more information.


Near-line Mirroring

8. If mirroring is suspended, specify when re-synchronization should be attempted.

Re-synchronization can be started based on time (every n minutes/hours) and/or I/O activity (when I/O is less than n KB/MB). If you select both, the time will be applied first before the I/O activity level. If you do not select either, the mirror will stay suspended until you manually synchronize it.

If you select one or both re-synchronization methods, you must also specify how many times the system should retry the re-synchronization if it fails to complete.

When the system initiates re-synchronization, it does not check lag time and mirroring will not be suspended if there is too much lag time.

If you manually resume mirroring, the system will monitor the process during synchronization and check lag time. Depending upon your monitoring policy, mirroring will be suspended if the lag time gets above the acceptable limit.

Note: If DF2112 is restarted or the server experiences a failover while attempting to resynchronize, the mirror will remain suspended.


Near-line Mirroring

9. Indicate if you want to use the throughput control option.

This controls synchronization performance on the near-line mirror side. It is primarily meant for the initial synchronization or for rebuilding the mirror.

Check resource throughput after synchronization in progress for - Specify how long synchronization should run before the system pauses to check throughput.

10. If enabled, set the throughput control policy that should be used to monitor the synchronization process..


Near-line Mirroring

Check resource throughput every - Specify how long to pause for before checking whether to resume synchronization.

Resume Synchronization - Re-synchronization can be started based on I/O activity, either when the number of I/O is less than or equal to a specified number or when I/O per second is less than or equal to n MB/KB per second.

Maximum checking attempts before resuming synchronization - Synchronization will resume when I/O activity is lower than or equal to the limit set above. Specify how many times to check this limit. After this number of times, synchronization will restart, regardless of throughput.

11. Select how you want to create this near-line mirror resource.

Custom lets you select which physical device(s) and which segments to use and lets you designate how much space to allocate from each.

Express lets you select which physical device(s) to use and automatically creates the near-line resource from the available hard disk segments.

Select existing lets you select an existing virtual device that is the same size as the primary or a previously prepared (but not yet created) near-line mirror resource. (The option to only prepare a near-line disk appeared on the first Near-line Mirror wizard dialog.)


Near-line Mirroring

12. Enter a name for the near-line resource.

13. (iSCSI protocol) Select the iSCSI targets to assign.


Near-line Mirroring

14. Confirm that all information is correct and then click Finish to create the near-line mirroring configuration.

What’s next?

Near-line disksare prepared

but not created

If you prepared one or more near-line disks and you are ready to create near-line mirrors, you must manually rescan physical resources and discover new devices on the primary server. Afterwards, you must re-run the Near-line Mirror wizard for each primary disk and select the existing, prepared disk. This will create a near-line mirror without re-scanning the primary server.

Near-line mirroris created

After creating your near-line mirror, you should enable TimeMark or CDP on the near-line server. This way your data will have periodic snapshots and you will be able to roll back your data when needed.

For disaster recovery purposes, you can also enable replication for a near-line disk to replicate the data to another location.


Near-line Mirroring

Check near-line mirroring status

You can see the current status and properties of your mirroring configuration by checking the General tab for a mirrored resource.

Current status andproperties of

mirroringconfiguration.


Near-line Mirroring

Recover data from a near-line mirror

The following is required before recovering data from a near-line mirror:

• If you are using the FC protocol, zone the appropriate initiators on your near-line server with the targets on your primary server.

• If you are using the iSCSI protocol, on the near-line server edit the \etc\iscsi.conf file and add the IP address of the primary server.

• If you are using the iSCSI protocol, the iSCSI initiator must be started on the near-line server before DF2112 is started. If needed, refer to the ‘Near-line mirroring requirements’ for more details about how to do this.

• You must unassign the primary disk from its client(s).• If enabled, disable mirroring for the near-line disk.• If enabled, suspend replication for the near-line disk.• All SAN resources must be online and accessible.• If you have been using CDP and want to rollback to a specific point-in-time,

you may want to create a TimeView first and view it to make sure it contains the appropriate data that you want.

Recovery is done in the console from the near-line resource.

1. Right-click on the near-line resource and select Near-line Mirror Resource --> Start Recovery.

You can also start recovery by selecting TimeMark --> Rollback.

2. Add the near-line server as a client of the primary server.

You will go through several screens to add the client:• Confirm or specify the IP address the near-line server will use to connect to

the primary server as a client. This IP address is used for iSCSI; it is not used for Fibre Channel.

• Determine if you want to enable persistent reservation for the client (near-line server). This allows clustered clients to take advantage of Persistent Reserve/Release to control disk access between various cluster nodes.

• Select the client’s protocol(s). If you select iSCSI, you must indicate if this is a mobile client.

• (FC protocol) Select or add WWPN initiators for the client. • (FC protocol) Specify if you want to use Volume Set Addressing (VSA) and/

or QoS. VSA is used primarily for addressing virtual buses, targets, and LUNs. If your storage devices use VSA, you must enable it. QoS controls the quality of service for each target port based on priority.

• (iSCSI protocol) Select the initiator that this client uses. If the initiator does not appear, you may need to rescan. You can also manually add it, if necessary.

• (iSCSI protocol) Add/select users who can authenticate for this client. • (iSCSI protocol) Specify which QoS level to use to control the quality of

service for each target port based on priority.


Near-line Mirroring

3. Select the point-in-time to which you want to roll back.

Rollback restores your drive to a specific point in time, based on an existing TimeMark or your CDP journal. After rollback, your drive will look exactly like it did at that point in time.

You can select to roll back to any TimeMark. If this resource has CDP enabled and you want to select a specific point-in-time, type in the exact time.

4. Type Yes to confirm.

Once you type Yes, the system will roll back the near-line mirror to the specified point-in-time and will then synchronize the data back to the primary server. When the process is completed, your screen will look similar to the following:

5. When the Mirror Synchronization Status shows the status as Synchronized, you can select Near-line Mirror Resource --> Resume Config to resume the configuration of the near-line mirror.


Near-line Mirroring

This re-sets the original near-line configuration so that the primary server can begin mirroring to the near-line mirror.

6. Re-assign your primary disk to its client(s).


Near-line Mirroring

Swap the primary disk with the near-line mirrored copy

Right-click on the primary SAN Resource and select Near-line Mirror --> Swap to reverse the roles of the primary disk and the mirrored copy. You will need to do this if you are going to perform maintenance on the primary disk or if you need to remove the primary disk.

Expand the primary disk

The mirrored devices must be the same size. If you want to enlarge the primary disk, you will need to enlarge the mirrored copy to the same size. When you use the Expand SAN Resource Wizard, it will automatically lead you through expanding the near-line mirror disk first.

Manually synchronize a near-line mirror

The Synchronize option re-synchronizes a mirror and restarts the mirroring process once it is synchronized. This is useful if one of the mirrored disks has a minor failure, such as a power loss.


2. Right-click on the primary resource and select Near-line Mirror --> Synchronize.

During the synchronization, the system will monitor the process and check lag time. Depending upon your monitoring policy, mirroring will be suspended if the lag time gets above the acceptable limit.

Rebuild a near-line mirror

The Rebuild option rebuilds a mirror from beginning to end and starts the mirroring process once it is synchronized.

After rebuilding the mirror, you would swap the mirror so that the primary server could service clients again.

1. Right-click on a primary resource and select Near-line Mirror --> Rebuild.



Near-line Mirroring

Suspend/resume near-line mirroring

When you manually suspend a mirror, the system will not attempt to re-synchronize, even if you have a re-synchronization policy. You will have to resume the mirror in order to synchronize.

When you resume mirroring, the mirror is synchronized before mirroring is resumed. During the synchronization, the system will monitor the process and check lag time. Depending upon your monitoring policy, mirroring will be suspended if the lag time gets above the acceptable limit.

To suspend/resume mirroring for a resource:

1. Right-click on a primary resource and select Near-line Mirror --> Suspend (or Resume).


Change your mirroring configuration options

Set globalmirroring

options

You can set global mirroring options that affect system performance during all types of mirroring (near-line, synchronous, or asynchronous). While the default settings should be optimal for most configurations, you can adjust the settings for special situations.

To set global mirroring properties for a server:



Use [n] outstanding commands of [n] KB - The number of commands being processed at one time and the I/O size. This must be a multiple of the sector size.

Synchronize Out-of-Sync Mirrors - Determine how often the system should check and attempt to resynchronize active out-of-sync mirrors, how often it should retry synchronization if it fails to complete, and whether or not to include replica mirrors. These settings will only be used for active mirrors. If a mirror is suspended because the lag time exceeds the acceptable limit, that re-synchronization policy will apply instead.

Changeproperties for aspecific primary

resource

You can change the following near-line mirroring configuration for a primary resource:

• Policy for monitoring the mirroring process• Conditions for re-synchronization • Throughput control policies



Near-line Mirroring

1. Right-click on a primary resource and select Near-line Mirror --> Properties.


Changeproperties for a

specific near-line resource

For a near-line mirroring resource, you can only change the IP address that is used by the near-line server to connect to the primary server.


1. Right-click on a near-line resource and select Near-line Mirror Resource --> Properties.

2. Make the appropriate change and click OK.

Remove a near-line mirror configuration

You can remove a near-line mirror configuration from the primary or near-line mirror resource.

Removing a near-line mirror configuration deletes the mirrored copy and cancels mirroring. You will not be able to access the mirrored copy afterwards.

From the primary server, right-click on the primary resource and select Near-line Mirror --> Remove.

From the near-line server, right-click on the near-line resource and select Near-line Mirror Resource --> Remove.


Near-line Mirroring

Recover from a mirroring hardware failure

Replace afailed disk

If one of the mirrored disks has failed and needs to be replaced:

1. Right-click on the resource and select Near-line Mirror --> Remove to remove the mirroring configuration.

2. Physically replace the failed disk.


3. Re-run the Near-line Mirroring wizard to create a new mirroring configuration.

If both disks fail If a disaster occurs at the site where the primary and near-line server are housed, it is possible to recover both disks if you had replication configured for the near-line disk to a remote location.

In this case, after removing the mirroring configuration and physically replacing the failed disks, you can perform a role reversal to replicate all of the data back to the near-line disk.

Afterwards, you can recover the data from the near-line mirror back to the primary disk.

Fix a minor diskfailure

If one of the mirrored disks has a minor failure, such as a power loss:


2. Right-click on the primary resource and select Near-line Mirror --> Synchronize.

This re-synchronizes the disks and restarts the mirroring.

Replace a disk that is part of an active near-line mirror

If you need to replace a disk that is part of an active near-line mirror:

1. If you need to replace the primary disk, right-click on the primary resource and select Near-line Mirror --> Swap to reverse the roles of the disks.

2. Select Near-line Mirror --> Replace Primary Disk.

3. Replace the disk.


4. Swap the disks to reverse their roles.


Near-line Mirroring

Replace a failed physical disk without rebooting your DF2112 Server

Do the following if you need to replace a failed physical disk without rebooting your DF2112 Server.

1. If you are not sure which physical disk to remove, execute the following to access the drive and cause the disk’s light to blink:

where ‘#’ represents a,b,c,d, … depending on the order of the disks.

2. You MUST remove the SCSI device from the Linux OS.

Type the following for Linux (2.4 kernel):echo “scsi remove-single-device A:C:S:L” > /proc/scsi/scsi

A C S L stands for: Adapter, Channel, SCSI, and LUN. This can be found in the Console.

Type the following for Linux (2.6 kernel):echo "1" > /sys/class/scsi_device/DeviceID/device/delete


For example:echo "1" > /sys/class/scsi_device/1:0:0:0/device/delete



4. Rescan the adapter to which the device has been added.

In the Console, right-click on AdaptecSCSI Adapter.x and select Rescan, where x is the adapter number the device is on.

hdparm -t /dev/sd#



DF2112 User Guide

Snapshot

The concept of performing a snapshot is similar to taking a picture. When we take a photograph, we are capturing a moment in time and transferring this moment in time to a photographic medium, even while changes are occurring to the object we focused our picture on. Similarly, a snapshot of an entire device allows us to capture data at any given moment in time and move it to either tape or another storage medium, while allowing data to be written to the device.

The basic function of the snapshot engine is to allow point-in-time, “frozen” images to be created of data volumes (virtual drives) using minimal storage space. The snapshot initially uses no disk space. As new data is written to the source volume, the old data blocks are moved to a temporary snapshot storage area. By combining the snapshot storage with the source volume, the data can be recreated exactly at it appeared at the time the snapshot was taken. For added protection, a snapshot resource can also be mirrored through DF2112.

A trigger is an event that tells DF2112 when it is time to perform a snapshot of a virtual device. DF2112’s Replication, TimeMark/CDP, Snapshot Copy, and ZeroImpact Backup options all trigger snapshots.


Snapshot

Create a Snapshot Resource

Each SAN and NAS Resource can have one Snapshot Resource. The Snapshot Resource is shared by all of the DF2112 options that use Snapshot (Replication, TimeMark/CDP, Snapshot Copy, and ZeroImpact backup).

Each snapshot initially uses no disk space. As new data is written to the source volume, the old data blocks are moved to the Snapshot Resource. Therefore, it is not necessary to have 100% of the size of the SAN/NAS Resource reserved as a Snapshot Resource. The amount of space initially reserved for each Snapshot Resource is calculated as follows:

Using the table above, if you create a 10 GB SAN Resource, your initial Snapshot Resource will be 2 GB but you can set the Snapshot Resource to expand automatically, as needed.

If you create a SAN or NAS Resource that is less than 500 MB, the amount of space reserved for the Snapshot Resource will be 100% of the virtual drive size. This is because a smaller-sized volume can overfill quickly, leaving no time for the auto-expansion to take effect. By reserving a Snapshot Resource equal to 100% of the SAN/NAS Resource, the snapshot is able to free up enough space so normal write operations can continue.

If you do not create a Snapshot Resource for your SAN/NAS Resource, when you configure Replication, TimeMark/CDP, Snapshot Copy, or backup, the Snapshot wizard will launch first, allowing you to create it.

You can create a snapshot resource for a single SAN or NAS Resource or you can use the batch feature to create snapshot resources for multiple SAN or NAS Resources:

1. For a single SAN or NAS Resource, right-click on the resource and select Snapshot Resource --> Create.

For multiple SAN or NAS Resources, right-click on the SAN Resources or NAS Resources object and select Snapshot Resource --> Create.

Size of SAN/NAS Resource Reserved for Snapshot Resource

Less than 500 MB 100%

500 MB or more but less than 2 GB 50%

2 GB or more 20%


Snapshot

2. Select the storage pool or physical device that should be used to create this Snapshot Resource.

3. Select how you want to create this Snapshot Resource.


Express lets you designate how much space to allocate and then automatically creates a Snapshot Resource using an available device.


Snapshot





Snapshot


4. Verify the physical devices you have selected.

Select either an entirely unallocated or partially unallocated device.

Indicate how much space to allocate from this device.

Click Add More if you need to add another physical disk to this Snapshot Resource.You will go back to the physical device selection screen where you can select another disk.


Snapshot

5. Determine whether DF2112 should expand your Snapshot Resource if it runs low and how it should be expanded.

If you want DF2112 to automatically expand the Snapshot Resource when space is running low, set the threshold level and make sure the option Automatically allocate more space for the Snapshot Resource is selected.

Then, determine the amount of space to be allocated for each expansion. You can set this to be a specific size (in MB) or a percentage of the size of the Snapshot Resource. There is no limit to the number of times a Snapshot Resource can be expanded.

Once the low space threshold is triggered, the system will attempt to expand the resource by allocating additional space. The time required to accomplish this may be in milliseconds or even seconds, depending on how busy the system is.

If expansion fails, old TimeMarks will be deleted until enough space is reclaimed so that the Snapshot Resource does not run out of space.

To prevent this from happening, we recommend that you allow enough time for expansion after the low space threshold is reached. We recommend that your safety margin be at least five seconds. This means that from the time the low space threshold is reached, while data is being written to the drive at maximum throughput, it will take a minimum of five seconds to fill up the rest of the drive. Therefore, if the maximum throughput is 50 MB/s, the threshold should be set for when the space is below 250 MB. Of course if the throughput is lower, the allowance can be lower accordingly.

Note: If you do not select automatic expansion, old TimeMarks will be deleted to prevent the Snapshot Resource from running out of space.


Snapshot

6. Configure what DF2112 should do if your Snapshot Resource runs out of space.

This will only occur if you have reached the maximum allowable size for your Snapshot Resource or if you have chosen not to expand it.

If you select Delete the earlier TimeMarks automatically, once the maximum is reached, the earliest TimeMarks will be deleted depending upon priority. Low priority TimeMarks are deleted first, followed by Medium, High, and then Critical. When a TimeMark is deleted, journal data is merged together with a previous TimeMark (or a newer TimeMark, if no previous exist).

If a Snapshot Resource is associated with a member of a group enabled with TimeMark, the earliest TimeMark will be deleted for all of the resources.

If you select Stop writing data, the system will prevent any new writes from getting to the disk once the Snapshot Resource runs out of space and it cannot allocate any more. As a result, clients can experience write errors. If the client is a production machine, this may not be desirable.

You might want to use this option if the virtual disk is not being used for production data such as when the disk is a mirror disk. Since its function is to act as a backup of a production disk, you may want to retain earlier TimeMarks rather than losing them in the event the Snapshot resource is full or inaccessible.


Snapshot

7. Determine if you want to use Snapshot Notification.

Snapshot Notification works with the DF2112 Snapshot Agents to initiate a snapshot request to a SAN client. When used, the system notifies the client to quiet activity on the disk before a snapshot is taken. Using Snapshot Notification guarantees that you will get a transactionally consistent image of your data.

8. Confirm that all information is correct and then click Finish.

You will now see a new Snapshot tab for this SAN/NAS Resource.


Snapshot

Check status of a Snapshot Resource

You can see how much of your Snapshot Resource is currently being used and your expansion methods by checking the Snapshot tab for a SAN or NAS Resource.

Because Snapshot Resources record block-level changes, not file-level, you may not see the Usage Percentage decrease when you delete files. This is because deleted files really still exist on the disk.

Note that Snapshot resources will be marked off-line if the physical resource they have been created from is disconnected from a single server in a failover set prior to a failing over to the secondary server.

Protect your Snapshot Resources

If the physical disk that contains a snapshot resource fails, you will still be able to access your SAN/NAS Resource, but the snapshot data already in the snapshot resource will become invalid. This means that you will not be able to roll back to a point-in-time image of your data.

However, you can protect your snapshot resources by using DF2112’s Mirroring option. With Mirroring, each time data is written to the snapshot resource, the same data is also written to another disk which maintains an exact copy of the snapshot resource. If the primary snapshot resource disk fails, DF2112 seamlessly swaps to the mirrored copy.

To mirror a snapshot resource, right-click on the SAN or NAS Resource and select Snapshot Resource --> Mirror --> Add.

Refer to the ‘Mirroring’ section for more information.


Snapshot

Options for Snapshot Resources

When you right-click on a logical resource that has a Snapshot Resource, you will see a Snapshot Resource menu with the following options:

Reinitialize Reinitialize allows you to reclaim space for your Snapshot Resource. You will only need to reinitialize your Snapshot Resource if you are not mirroring it and it has gone offline but is now back online.

Expand Expand allows you to manually expand the size of your Snapshot Resource.

Shrink Shrink allows you to reduce the size of your Snapshot Resource. This is useful if your snapshot resource does not need all of the space currently allocated to it.

Note: Be sure to stop all I/O to the source resource before starting this operation. Based on current usage, when you select the Shrink option, the system calculates the maximum amount of space that can be used to shrink the Snapshot Resource. If you have I/O occurring during the shrinking process, the space used for the Snapshot Resource may increase and the operation may fail.

Delete Delete allows you to delete the Snapshot Resource for this logical resource.

Properties Properties allows you to change your automatic expansion and snapshot notification policies.

Mirror Mirror allows you to protect your Snapshot Resource by creating a mirror of it.


Snapshot

Use Snapshot to copy a SAN or NAS resource

DF2112’s Snapshot Copy option allows you to create a duplicate, independent point-in-time copy of a SAN or NAS resource without impacting application servers. The entire resource is copied to another drive, overwriting any data on the target drive.

The source must have a Snapshot Resource in order to create a Snapshot Copy. If it does not have one, you will be prompted to create one. Refer to Create a Snapshot Resource for more information.

1. Right-click on the SAN or NAS resource that you want to copy and select Copy.

Note: We recommend that if a Snapshot Copy is being taken of a large database without the use of a DF2112 Snapshot Agent, the database should reside on a journaling file system (JFS). Otherwise, under heavy I/O, there is a slight possibility that the file system could be changed, resulting in the need to run a file system check (fsck) in order to repair the file system.

2. Select how you want to create the target resource.


Express automatically creates the target for you from available hard disk segments.

Select Existing lets you select an existing resource. There are several restrictions as to what you can select:

- The target must be the same type (SAN or NAS) as the source.- The target must be the same size as the source. - The target cannot have any clients assigned or attached.


Snapshot

Note: All data on the target will be overwritten.


Only one disk can be selected at a time from this dialog. To create a target resource from multiple physical disks, you will need to add the disks one at a time. After selecting the parameters for the first disk, you will have the option to add more disks. You will need to do this if the first disk does not have enough space.


Click Add More if you need to add another physical disk to this target resource.You will go back to the physical device selection screen where you can select another disk.


Snapshot

If you selected Select Existing in step 2, you will see the following window from which you can select an existing resource:

3. Enter a name for the target resource.


4. Confirm that all information is correct and then click Finish to perform the Snapshot Copy.

Note: If a failover or recovery occurs when snapshot copy is taking place, the snapshot copy will fail. You must resubmit the snapshot copy afterwards.


Snapshot

5. Assign the snapshot copy to a client.

Note: If you attempt to assign a snapshot copy of a virtual disk multiple times to the same Windows SAN Client, the snapshot copy will fail to import. This is because the import of the foreign disk uses the same disk group name as that of the current computer's disk group. This is a problem with Dynamic Disks; Basic Disks will not have this issue.

Check Snapshot Copy status

You can see the current status of your Snapshot Copy by checking the General tab of both the virtual drive you copied from or copied to.

Snapshot Copy events are also written to the server’s Event Log, so you can check there for status information, as well as any errors.


Snapshot

GroupsThe Group feature allows virtual drives and service enabled drives to be grouped together. Groups can be created for different reasons, for CDP purposes, for snapshot synchronization, for organizational purposes, or for caching with DF2112’s SafeCache option.

Snapshot synchronization builds on DF2112’s snapshot technology, which ensures point-in-time consistency for data recovery purposes. Snapshots for all resources in a group are taken at the same time whenever a snapshot is triggered. Working in conjunction with the database-aware Snapshot Agents, groups ensure transactional integrity for database or messaging files that reside on multiple disks.

When you create a group, you can configure TimeMark/CDP, Backup, Replication, and SafeCache (and, indirectly, asynchronous mirroring) for the entire group. All members of the group will get configured the same way.

Create a group

To create a group:

1. In the DF2112 Console, right-click on Groups and select New.

Depending upon which options you enable, the subsequent screens will let you set group policies for those options. Refer to the appropriate section(s) (Replication, Zero Impact Backup, TimeMark/CDP, or SafeCache) for details on configuration.

Note that you cannot enable CDP and SafeCache for the same group.

2. Indicate if you would like to add SAN/NAS Resources to this group.

Refer to the following sections for limitations as to which SAN/NAS Resources can/cannot join a group.


Snapshot

Groups with TimeMark/CDP enabled

The following notes affect groups configured for TimeMark/CDP:

• You cannot add a resource to a group configured for either TimeMark or CDP if the resource is already configured for CDP.

• You cannot add a resource to a group configured for CDP if the resource is already configured for SafeCache.

• CDP can only be enabled for an existing group if members of the group do not have CDP or SafeCache enabled.

• TimeMark can be enabled for an existing group if members of the group have TimeMark enabled.

• The group will have only one CDP journal. You will not see a CDP tab for the individual resources.

• If you want to remove a resource from a group with CDP enabled, you must first suspend the CDP journal for the entire group and wait until it finishes flushing.

Groups with SafeCache enabled

The following notes affect groups configured for SafeCache:

• You cannot add a resource to a group configured for SafeCache if the resource is already configured for SafeCache.

• SafeCache can only be enabled for an existing group if members of the group do not have CDP or SafeCache enabled.

• The group will have only one SafeCache resource. You will not see a SafeCache tab for the individual resources.

• If you want to remove a resource from a group with SafeCache enabled, you must first suspend SafeCache for the entire group.

Groups with replication enabled

The following notes affect groups configured for replication:

• When you create a group on the primary server, the target server gets a group also.

• When you add resources to a group configured for replication, you can select any resource that is already configured for replication on the target server or any resource that does not have replication configured at all. You cannot select a resource if it is configured for replication to a different server.

• If a watermark policy is used for replication, the retry delay value configured affects each group member individually rather than the group as a whole. For example, if replication starts for the group and a group member fails during the replication process, the retry delay value will take effect. In the meantime, if another resource in the group reaches its watermark, a group replication will be triggered for all group members and the retry delay will become irrelevant.


Snapshot

• If you are using continuous replication, the group will have only one Continuous Replication Resource.

• If a group is configured for continuous replication, you cannot add a resource to the group if the resource has continuous replication enabled. Similarly, continuous replication can only be enabled for an existing group if members of the group do not have continuous replication enabled.

• If you add a resource to a group that is configured for continuous replication, the system switches to periodic replication mode until the next regularly-scheduled replication takes place.

Grant access to a group

By default, only the root user and DF2112 admins can manage SAN/NAS resources, groups, or clients. While DF2112 users can add new groups, if you want a DF2112 user to manage an existing group, you must grant that user access. To do this:

1. Right-click on a group and select Access Control.

2. Select which user can manage this group.

Each group can only be assigned to one DF2112 user. This user will have rights to perform any function on this group, including assigning, joining, and configuring storage services.


Snapshot

Add resources to a group

Each group can be comprised of multiple SAN or NAS Resources. Each resource can only join one group and you cannot have both types of resources in the same group.

Note: There is a limit of 128 resources per group. If the group is enabled for replication, the recommended limit is 50. We recommend not having more than 10 NAS resources in the same group.

There are several ways to add resources to a group. After you create a group, you will be prompted to add resources. At any time afterwards, you can:

1. Right-click on any group and select Join.

You can also right-click on any SAN or NAS Resource and select Group --> Join.

2. Select the type of resources that will join this group, SAN or NAS.

If this is a group with existing members, you will see a list of members instead.

3. Determine if you want to use Express Mode.

If you select Express Mode, you will be able to select multiple resources to join this group at one time. After you finish selecting resources, they will automatically be synchronized with the options and settings configured for the group.

If you do not select Express Mode, you will need to select resources one-by-one. For each resource, you will be taken through the applicable Replication and/or Backup wizard(s) and you will have to manually configure each option. (TimeMark is always configured automatically.)

4. Select resources to join this group.


Snapshot

If you started the wizard from a SAN/NAS Resource instead of from a group, you will see the following window and you will select a group, instead of a resource:

When you click Next, you will see the options that must be activated. You will be taken through the applicable Replication and/or Backup wizard(s) so you can manually configure each option. (TimeMark is always configured automatically.)

5. Confirm all information and click Finish to add the resource(s) to the group.

Each resource will now have a tab for each configured option except CDP and SafeCache which share a CDP journal or SafeCache resource as a group.

By default, group members are not automatically assigned to clients. You must still remember to assign your group members to the appropriate client(s).


Snapshot

Remove resources from a group

Note that if you want to remove a resource from a group with CDP or SafeCache enabled, you must first suspend the CDP journal for the group and wait for it to finish flushing or suspend SafeCache. To suspend the CDP journal, right-click on the group and select TimeMark/CDP --> CDP Journal --> Suspend. Afterwards, you will need to resume the CDP journal. To suspend SafeCache, right-click on the group and select SafeCache --> Suspend.

To remove resources from a group:

1. Right-click on any group and select Leave.

2. Select resources to leave this group.

For groups enabled with Backup or Replication, leaving the group does not disable Backup or Replication for the resource.


DF2112 User Guide

TimeMark/CDPOverview

DF2112’s TimeMark/CDP option protects your mission critical data, enabling you to recover data back from a previous point-in-time.

TimeMarks are point-in-time images of any SAN or NAS virtual drive. Using DF2112’s Snapshot technology, TimeMarks track multiple virtual images of the same disk marked by "time". If you need to retrieve a deleted file or "undo" data corruption, you can recreate/restore the file instantly based on any of the existing TimeMarks.

While TimeMark allows DF2112 to track changes to specific points in time, with Continuous Data Protection (CDP) you can roll back data to any point-in-time.

TimeMark/CDP guards against soft errors, non-catastrophic data loss, including the accidental deletion of files and software/virus issues leading to data corruption. TimeMark/CDP protects where high availability configurations cannot, since in creating a redundant set of data, high availability configurations also create a duplicate set of soft errors by default. TimeMark/CDP protects data from your slip-ups, from the butter fingers of employees, unforeseen glitches during backup, and from the malicious intent of viruses.

The TimeMark/CDP option also provides an "undo button" for data processing. Traditionally, when an administrator performed operations on a data set, a full backup was required before each “dangerous” step, as a safety net. If the step resulted in undesirable effects, the administrator needed to restore the data set and start the process all over again. With DF2112's TimeMark/CDP option, you can easily rollback (restore) a drive to its original state.

DF2112’s TimeView feature is an extension of the TimeMark/CDP option and allows you to mount a virtual drive as of a specific point-in-time. Deleted files can be retrieved from the drive or the drive can be assigned to multiple application servers for concurrent, independent processing, all while the original data set is still actively being accessed/updated by the primary application server. This is useful for “what if” scenarios, such as testing a new payroll application on your actual, but not live, data.


TimeMark/CDP

Setup

You need a Snapshot Resource for the logical resource you are going to configure. If you do not have one, you will create it through the wizard. Refer to Create a Snapshot Resource for more information.

1. Right-click on a SAN or NAS Resource, incoming replica resource, or a Group and select TimeMark/CDP --> Enable.

For multiple SAN or NAS Resources, right-click on the SAN Resources or NAS Resources object and select TimeMark/CDP --> Enable.

2. Indicate if you want to enable CDP.

CDP enhances the benefits of using TimeMark by recording all changes made to data, allowing you to recover to any point in time.

It is not selected by default. Click the checkbox in order to enable it.


TimeMark/CDP

3. (CDP only) Select the storage pool or physical device that should be used to create the CDP journal.

4. (CDP only) Select how you want to create the CDP journal.

The minimum size required for the journal is 1 GB, which is the default size.


Express lets you designate how much space to allocate and then automatically creates a CDP journal using an available device.



TimeMark/CDP



5. (CDP only) Set expansion policies for the CDP journal.

If you do not want the CDP journal to be able to expand, uncheck the checkbox.

Note: Currently the maximum size for the CDP journal is 2 TB. Refer to the DF2112 Release Notes for any updates to the maximum size.

Continuous coverage period - Indicate the minimum period of time that the journal should protect.

Journal expansion trigger - Enter the percent of journal usage that should trigger expansion.

Amount to allocate when triggered - Enter the amount to expand by when the trigger is reached.

Maximum journal size - If desired, specify a maximum size for the journal. This can affect the continuous coverage period because the maximum size could be reached before the minimum coverage period.

Advanced button - If desired, determine how aggressively the CDP journal should be flushed.


TimeMark/CDP

6. Determine how often TimeMarks should be created.

Regardless of whether or not you are using CDP, DF2112 allows you to schedule periodic TimeMarks. For example, if you are not using CDP, scheduling a TimeMark to be created every hour gives you the ability to restore the disk content back to a known good state with hourly granularity. If you are using CDP, the TImeMarks will be points within the CDP journal.

In order for a TimeMark to be created, you must select Create an initial TimeMark on... policy. Otherwise, you will have enabled TimeMark, but not created any. You will then need to manually create them using TimeMark/CDP --> Create.

If you are configuring TimeMark for an incoming replica resource, you cannot select the Create an initial TimeMark on... policy. Instead, a TimeMark will be created after each scheduled replication job finishes.

Depending upon the version of your system, the maximum number of TimeMarks that can be maintained is 255. The maximum does not include the snapshot images that are associated with TimeView resources. Once the maximum is reached, the earliest TimeMarks will be deleted depending upon priority. Low priority TimeMarks are deleted first, followed by Medium, High, and then Critical. When a TimeMark is deleted, journal data is merged together with a previous TimeMark (or a newer TimeMark, if no previous exist).

The first TimeMark that is created when CDP is used will have a Medium priority. Subsequent TimeMarks will have a Medium priority by default, but it can be changed manually. Refer to ‘Add a comment or change priority of an existing TimeMark’ for more information.

The minimum number of TimeMarks required for CDP is four. To ensure continuous coverage, you should maintain the total number of TimeMarks to be the continuous coverage period divided by the scheduled interval plus 1. For example, if the coverage period is 24 hours and the interval is every hour, you would need a minimum of 25 TimeMarks (24 / 1 + 1). If the coverage period is 24


TimeMark/CDP

hours, and the interval is 30 minutes, you would need a minimum of 49 TimeMarks (24 / .5 + 1).

Snapshot Notification works with the DF2112 Snapshot Agents to initiate a snapshot request to a SAN client. When used, the system notifies the client to quiet activity on the disk before a snapshot is taken. Using snapshot notification guarantees that you will get a transactionally consistent image of your data.

This might take some time if the client is busy. You can speed up processing by skipping snapshot notification if you know that the client will not be updating data when a TimeMark is taken. Use the Trigger snapshot notification for every n scheduled TimeMark(s) option to select which TimeMarks should use snapshot notification.

7. Confirm that all information is correct and then click Finish to enable TimeMark/CDP.

You will now have a TimeMark tab for this resource or group. If you enabled CDP, you will have a separate CDP tab too.


TimeMark/CDP

Check TimeMark status

You can see a list of TimeMarks for this virtual drive, along with your TimeMark policies, by checking the TimeMark tab.

To re-order the list of TimeMarks, click on a column heading to sort the list.

The Quiescent column indicates whether or not snapshot notification occurred when the TimeMark was created. If you are looking at this tab for a replica resource, the status will be carried from the primary resource. For example, if the TimeMark created on the primary virtual device used snapshot notification, Quiescent will be set to Yes for the replica.

Right-click on the virtual drive and select Refresh to update the information on this tab.

To see how much space TimeMark is using, check the Snapshot tab.

Check CDP journal status

You can see the current size and status of your CDP journal, including all policies, by checking the CDP tab.


TimeMark/CDP


TimeMark/CDP

Protect your CDP journal

You can protect your CDP journal by using DF2112’s Mirroring option. With Mirroring, each time data is written to the journal, the same data is also written to another disk which maintains an exact copy of the journal. If the primary journal disk fails, DF2112 seamlessly swaps to the mirrored copy.

To mirror a journal, right-click on the SAN or NAS Resource and select TimeMark/CDP --> CDP Journal --> Mirror --> Add.

Add a tag to the CDP journal

You can manually add a tag to the CDP journal. The tag will be used to notate the journal when the next I/O occurs. Adding a tag with a meaningful comment is useful for marking special situations, such as system maintenance or software upgrades.

With these tags, it is easy to find the point just prior to when the system maintenance or software upgrade began, making rollback easy and accurate.

1. Highlight a SAN or NAS Resource and select TimeMark/CDP --> CDP Journal --> Add tag.

2. Type in a tag and click OK.


TimeMark/CDP

Add a comment or change priority of an existing TimeMark

You can add a comment to an existing TimeMark to make it easy to identify later. For example, you might add a “known good recovery point”, such as an application checkpoint to identify a TimeMark for easy recovery.

You can also change the priority of a TimeMark. Priority eases long term management of TimeMarks by allowing you to designate importance, aiding in the preservation of critical point-in-time images.

Priority affects how TimeMarks will be deleted once the maximum number of TimeMarks to keep has been reached. Low priority TimeMarks are deleted first, followed by Medium, High, and then Critical.

1. Right-click on the TimeMarked SAN or NAS resource that you want to update and select TimeMark/CDP --> Update

2. Click in the Comment or Priority field to make/change entries.

3. Click Update when done.


TimeMark/CDP

Manually create a TimeMark

1. To create a TimeMark that is not scheduled, select TimeMark/CDP --> Create.

2. If desired, add a comment for the TimeMark that will make it easily identifiable later if you need to locate it.

3. Set the priority for this TimeMark.

Once the maximum number of TimeMarks to keep has been reached, the earliest TimeMarks will be deleted depending upon priority. Low priority TimeMarks are deleted first, followed by Medium, High, and then Critical.

4. Indicate if you want to use Snapshot Notification for this TimeMark.

Snapshot Notification works with the DF2112 Snapshot Agents to initiate a snapshot request to a SAN client. When used, the system notifies the client to quiet activity on the disk before a snapshot is taken. Using snapshot notification guarantees that you will get a transactionally consistent image of your data.

This might take some time if the client is busy. You can speed up processing by skipping snapshot notification if you know that the client will not be updating data when this TimeMark is taken.

The use of this option overrides the Snapshot Notification setting in the snapshot policy.


TimeMark/CDP

Copy a TimeMark

The Copy feature works similarly to DF2112’s Snapshot Copy option. It allows you to take a TimeMark image of a drive (for example, how your drive looked at 9:00 this morning) and copy the entire drive image to another virtual drive. The virtual drive can then be assigned to Clients for use and configured for any of DF2112’s storage services.

1. Right-click on the TimeMarked SAN or NAS resource that you want to copy and select TimeMark/CDP --> Copy.

Note: Do not initiate a TimeMark Copy while replication is in progress. Doing so will result in the failure of both processes.

2. Select the TimeMark image that you want to copy.

3. Select how you want to create the target resource.


Express automatically creates the target for you from available hard disk segments. You will only have to select the storage pool or physical device that should be used to create the copy.


- The target must be the same type (SAN or NAS) as the source.- The target must be the same size as the source. - The target cannot have any Clients assigned or attached.


4. Enter a name for the target resource.

5. Confirm that all information is correct and then click Finish to perform the TimeMark Copy.

You can see the current status of your TimeMark Copy by checking the General tab of either virtual drive. You can also check the server’s Event Log for status information.


TimeMark/CDP

Recover data using the TimeView feature

TimeView allows you to mount a virtual drive as of a specific point-in-time, based on your existing TimeMarks or your CDP journal.

Use TimeView if you need to restore individual files from a drive but you do not want to rollback the entire drive to a previous point in time. Simply use TimeView to mount the virtual drive and then copy the files you need back to your original virtual drive.

TimeView also enables you to perform “what if” scenarios, such as testing a new payroll application on your actual, but not live, data. After mounting the virtual drive, it can be assigned to an application server for independent processing without affecting the original data set. A TimeView cannot be configured for any of DF2112’s storage services.

Why should you use TimeView instead of Copy? Unlike Copy, which creates a new virtual drive and requires disk space equal to the original disk, a TimeView does not require any disk space to mount. It is also quicker to create a TimeView than to copy data to a new virtual drive.

1. Highlight a SAN or NAS Resource and select TimeMark/CDP --> TimeView.

If this resource has CDP enabled, the top section contains a graph with marks that represent TimeMarks.

The graph is a relative reflection of the data changing between TimeMarks within the available journal range. The vertical y axis represents data usage per TimeMark; the height of each mark represents the Used Size of each TimeMark. The horizontal x axis represents time. Each mark on the graph indicates a single TimeMark. You will not see TimeMarks that have no data.

Move the slider to selectany point in time. You

can also type in the dateand time down to the

millisecond andmicrosecond.

Zoom In to see greater detail for the selected time period.

Click to select a CDP journal tag that was manually added.


TimeMark/CDP

Because the graph is a relative reflection of data, and the differences in data usage can be very large, the proportional height of each TimeMark might not be very obvious.

For example, if you have one TimeMark with a size of 500 MB followed by several much smaller TimeMarks, the 500 MB TimeMark will be much more visible.

Similarly, if the maximum number of TimeMarks has been reached and older TimeMarks have been deleted to make way for newer ones, journal data is merged together with a previous TimeMark (or a newer TimeMark, if no previous exist). Therefore, it is possible that you will see one large TimeMark containing all of the merged data.

Also, since the length of the x axis can reflect a range as small as one hour to 30 days, the location of an actual data point is approximate. Zooming in and using the Search button will allow you to get a more accurate location of a particular data point.

If CDP is enabled, you can use the visual slider to create a TimeView from any point in the CDP journal or you can create a TimeView from a scheduled TimeMark.

You can also click the Select Tag button to select a CDP journal tag that was manually added or was automatically added by DF2112 after a rollback occurred. Note that you will only see the tags for which there was subsequent I/O.

If CDP is not enabled, you will only be able to create a TimeView from a scheduled TimeMark.

2. To create a TimeView from a scheduled TimeMark, select Create TimeView from TimeMark Snapshots, highlight the correct TimeMark, and click OK.

If this is a replica server, the timestamp of a TimeMark is the timestamp of the source (not the replica’s local time).

3. To create a TimeView from the CDP journal, use the slider or type in an approximate time.

For example, if you are trying to find a deleted file, select a time prior to when the file was deleted. If this was an active file, aim for a time just prior to when the file was deleted so that you can recover the most up-to-date version.

If you are positive that the time you selected is correct, you can click OK to create a TimeView. If you are unsure of the exact time, you can zoom into an approximate time period to see greater detail, such as seconds, milliseconds, and even microseconds.


TimeMark/CDP

4. If you need to see greater detail, click Zoom In.

You can see the I/O that occurred during this five minute time frame displayed in seconds.

If you zoomed in and don’t see what you are looking for, you can click the Scroll button. It will move forwards or backwards by five minutes within the period of this TimeMark.

You can also click the Search button to locate data or a period with limited or no I/O.

At any point, if you know what time you want to select, you can click OK to return to the main dialog so that you can click OK to create a TimeView. Otherwise, you can zoom in further to see greater detail, such as milliseconds and microseconds.

TimeMark periodFive minute range within

this TimeMark


TimeMark/CDP

You can then use the slider to select a time just before the file was deleted.

It is best to select a quiet time without I/O to get the most stable version of the file.

5. After you have selected the correct point in time, click OK to return to the main dialog and then click OK to create a TimeView.

6. Enter a name for the TimeView and click OK to finish.

7. Assign the TimeView to a client.

The client can now recover any files needed.

Note: Clients may not be able to access TimeViews during failover.


TimeMark/CDP

Remap a TimeView

TimeViews allow you to mount a virtual drive as of a specific point-in-time, based on your existing TimeMarks or your CDP journal.

If you are finished with a TimeView but need to create another for the same virtual device, you can remap the TimeView to another point-in-time. When you remap, a new TimeView is created. All of the client connections are retained. The original TimeView is deleted and all changes to it are gone.

Note: We recommend disabling the TimeView from the client before remapping it. This is done from the Device Manager on Windows machines.

To remap a TimeView:

1. Right-click on an existing TimeView and select Remap.

You must have at least one additional TimeMark available.

2. Select a TimeMark or a point in the CDP journal.

3. Enter a name for the new TimeView and click Finish.

Roll back or roll forward a drive

Rollback restores your drive to a specific point in time, based on your existing TimeMarks, TimeViews, or your CDP journal. After rollback, your drive will look exactly like it did at that point in time.

After rolling a drive back, TimeMarks made after that point in time will be deleted but all of the CDP journal data will be available, if CDP is enabled. Therefore it is possible to perform another rollback and select a journal date ahead of the previous time, essentially rolling forward.

If you have a group, you will need to roll back each member of the group separately. Because groups share a cache, you must suspend the CDP journal for the group before rolling back. To do this, right-click on the group and select TimeMark/CDP --> CDP Journal --> Suspend. After rolling back, you will need to resume the CDP journal.

In order to keep the group’s image consistent, you cannot roll back while there is uncommitted journal data. You must wait for the data to flush before rolling back.

1. Detach the Client(s) from the virtual drive before rollback.

For non-Windows Clients, type ./df2112client stop from /usr/local/df2112client/bin.

Note: To avoid the need to reboot a Windows 2000/2003 client, unassign the SAN resource from the client now and then reassign it just before re-attaching your client using the DF2112 console.


TimeMark/CDP

2. Right-click on the virtual drive and select TimeMark/CDP --> Rollback.

If this resource has replication enabled, you must suspend it before rolling back. Make sure there is no replication taking place at the time of the rollback.

Do not initiate a TimeMark rollback to a raw device while data is currently being written to the raw device. The rollback will fail because the device will fail to open.

If you have already created a TimeView from the CDP journal and want to roll back your virtual device to that point in time, right-click on the TimeView and select Rollback to.

3. Select a specific point in time or select the TimeMark to which you want to rollback.

If CDP is enabled and you have previously rolled back this drive, you can select a future journal date.

Note: If you are rolling back a member of a group, it is very important that you roll back each member of the group to the exact same point in time.

If you selected a TimeView in the previous step, you will not have to select a point in time or a TimeMark.

4. Confirm that you want to continue.

A TimeMark will be taken automatically at the point of the rollback and a tag will be added into the journal. The TimeMark will have the description !!XX-- POST CDP ROLLBACK --XX!! This way, if you later need to create a TimeView, it will contain data from the new TimeMark forward to the TimeView time. This means you will see the disk as it looked at the point of the rollback plus any data written to the disk after the rollback occurred until the time of the TimeView.

5. When done, re-attach your Client(s).

Note: If DynaPath is running on a Windows client, reboot the machine after rollback.


TimeMark/CDP

Change your TimeMark/CDP policiesYou can change your TimeMark schedule, enable/disable CDP, change CDP journal expansion policies.

To change a policy:

1. Right-click on the virtual drive and select TimeMark/CDP --> Properties.


Note: If you uncheck the Enable Continuous Data Protection box, this will disable CDP and will delete the CDP journal. It will not delete TimeMarks. If you want to disable TimeMark and CDP, refer to the ‘Disable TimeMark and CDP’ section below.

Suspend/resume CDP

You can suspend/resume CDP for an individual resource if mirroring or replication is enabled for the virtual device.

If the resource is in a group, you can suspend/resume CDP at the group level.

Suspending CDP does not delete the CDP journal and it does not delete any TimeMarks.

When CDP is resumed, data resumes going to the journal.

To suspend/resume CDP, right-click on the resource or group and select TimeMark/CDP --> CDP Journal --> Suspend (or Resume).

Delete TimeMarksThe Delete option lets you delete one or more TimeMark images for a virtual drive. Depending upon which TimeMark(s) you delete, this may or may not free up space in your Snapshot Resource. For example, if you have multiple TimeMarks and you delete the latest one, DF2112 will merge all of its data back to previous TimeMarks and will not free up Snapshot Resource space. However, if you delete the first TimeMark, nothing will be merged and you will free up Snapshot Resource space. A general rule is that you will only free up Snapshot Resource space if a large percentage of disk changes were made after the deleted TimeMark image.

1. Right-click on the virtual drive and select TimeMark/CDP --> Delete.

2. Highlight one or more TimeMarks and click Delete.

3. Type yes to confirm and click OK to finish.


TimeMark/CDP

Disable TimeMark and CDP

If you ever need to disable TimeMark and CDP, you can select TimeMark/CDP --> Disable. In addition to disabling TimeMark and CDP, this will delete the CDP journal and all existing TimeMarks.

If you only want to disable CDP and delete the CDP resource, refer to the ‘Change your TimeMark/CDP policies’ section above.

Replication and TimeMark/CDP• In DF2112 version 5.1 and above, the timestamp of a TimeMark on a replica

is the timestamp of the source. In DF2112 5.0 and below, the timestamp was the replica’s local time.

• You cannot manually create any TimeMarks on the replica, even if you enable CDP on the replica.

• If you are using TimeMark with CDP, you must use Continuous Mode replication (not Delta Mode).


DF2112 User Guide

ReplicationOverview

Replication is the process by which a SAN or NAS resource maintains a copy of itself either locally or at a remote site. The SAN or NAS resource being replicated is known as the primary disk. The changed data is transmitted from the primary to the replica disk so that they are synchronized. Under normal operation, clients do not have access to the replica disk.

If a disaster occurs and the replica is needed, the administrator can promote the replica to become a SAN or NAS resource so that clients can access it. Replica disks can be configured for DF2112 storage services, including backup, mirroring, or TimeMark/CDP, which can be useful for viewing the contents of the disk or recovering files.

Replication can be set to occur continuously or at set intervals (based on schedule or watermark). For performance purposes and added protection, data can be compressed or encrypted during replication.

Remotereplication

Remote replication allows fast, data synchronization of storage volumes from one DF2112 Server to another over the IP network.

With remote replication, the replica disk is located on a separate DF2112 Server, called the target server.

Localreplication

Local replication allows fast, data synchronization of storage volumes within one DF2112 Server. It can be used within metropolitan area Fibre Channel SANs, or can be used with IP-based Fibre Channel extenders.


Replication

With local replication, the replica disk is connected to the DF2112 Server via a gateway using edge routers or protocol converters. Because there is only one DF2112 Server, the primary and target servers are the same server.

How replication worksReplication works by transmitting changed data from the primary disk to the replica disk so that the disks are synchronized. How frequently replication takes place depends on several factors.

Deltareplication

With standard, delta replication, a snapshot is taken of the primary disk at prescribed intervals based on the criteria you set (schedule and/or watermark value).

Continuousreplication

With DF2112’s Continuous Replication, data from the primary disk is continuously replicated to a secondary disk unless the system determines it is not practical or possible, such as when there is insufficient bandwidth. In these types of situations the system automatically switches to delta replication. After the next regularly-scheduled replication takes place, the system automatically switches back to continuous replication.

For continuous replication to occur, a Continuous Replication Resource is used to stage the data being replicated from the primary disk. Similar to a cache, as soon as data comes into the Continuous Replication Resource, it is written to the replica disk. The Continuous Replication Resource is created during the replication configuration.

There are several events that will cause continuous replication to switch back to delta replication, including when:

• The Continuous Replication Resource is full due to insufficient bandwidth• The DF2112 Server is restarted• After failover occurs• You perform the Replication --> Scan option• You add a resource to a group configured for continuous replication• Continuous Replication Resource is offline• The target server IP address is changed


Replication

Replication configuration

Requirements

The following are the requirements for setting up a replication configuration:

• (Remote replication) You must have two DF2112 Servers.• (Remote replication) You must have write access to both Servers.• You must have enough space on the target server for the replica and for the

Snapshot Resource. • Both clocks should be synchronized so that the timestamp matches.

Setup

You can enable replication for a single SAN or NAS Resource or you can use the batch feature to enable replication for multiple SAN or NAS Resources.

You need Snapshot Resources for the primary and replica disks. If you do not have them, you can create them through the wizard. Refer to Create a Snapshot Resource for more information.

1. For a single SAN or NAS Resource, right-click on the resource and select Replication --> Enable.

For multiple SAN or NAS Resource, right-click on the SAN Resources or NAS Resources object and select Replication --> Enable.

Each primary disk can only have one replica disk.

If you do not have a Snapshot Resource, the wizard will take you through the process of creating one.

Note: If you are replicating a NAS Resource, you must have NAS running on the target server. It will also need to be running any time future replication occurs or if you promote or remove a replica disk.


Replication

2. Select the server that will contain the replica.

For local replication, select the Local Server.

For remote replication, select any server but the Local Server.

If the server you want does not appear on the list, click the Add button.

3. (Remote replication only) Confirm/enter the target server’s IP address.


Replication

4. Specify if you want to use Continuous Replication..

Continuous Mode - Select if you want to use DF2112’s Continuous Replication. After the replication wizard completes, you will be prompted to create a Continuous Replication Resource for the primary disk.

Delta Mode - Select if you want replication to occur at set intervals (based on schedule or watermark).

Note: If you are using TimeMark with CDP, you must use Continuous Mode replication.

Use existing TimeMark - Determine if you want to use the most current TimeMark on the primary server when replication begins or if the replication process should create a TimeMark specifically for the replication. Using an existing TimeMark may be convenient for NAS resources, because XFS freezes momentarily when a TimeMark is created.

In addition, using an existing TimeMark reduces the usage of your Snapshot Resource. However, the data being replicated may not be the most current.

For example, Your replication is scheduled to start at 11:15 and your most recent TimeMark was created at 11:00. If you have selected Use Existing TimeMark, the replication will occur with the 11:00 data, even though additional changes may have occurred between 11:00 and 11:15.

Therefore, if you select Use Existing TimeMark, you must coordinate your TimeMark schedule with your replication schedule.

Even if you select Use Existing TimeMark, a new TimeMark will be created under the following conditions:

- The first time replication occurs.


Replication

- Each existing TimeMark will only be used once. If replication occurs multiple times between the creation of TimeMarks, the TimeMark will be used once; a new TimeMark will be created for subsequent replications until the next TimeMark is created.

- The most recent TimeMark has been deleted, but older TimeMarks exist.- After a manual rescan.

Preserve Replication TimeMark - If you did not select the Use Existing TimeMark option, a temporary TimeMark is created when replication begins. This TimeMark is then deleted after the replication has completed. Select Preserve Replication TimeMark to create a permanent TimeMark that will not be deleted when replication has completed (if the TimeMark option is enabled). This is convenient way to keep all of the replication TimeMarks without setting up a separate TimeMark schedule.

5. Configure how often, and under what circumstances, replication should occur.

You must select at least one policy but you can have multiple. You must specify a policy even if you are using continuous replication. This way, if the system switches to delta replication, it can automatically switch back to continuous replication after the next regularly-scheduled replication takes place.

Note: Any number of continuous replication jobs can run concurrently. However, by default, only five delta replication jobs can run, per server, at any given time. If an additional job is ready to run, pending jobs will wait until one of the current replication jobs finish. Contact Technical Support for information about changing this value but note that additional replication jobs will increase the load and bandwidth usage of your servers and network and may be limited by individual hardware specifications.

Start replication when the amount of new data reaches - If you enter a watermark value, when the value is reached, a snapshot will be taken and


Replication

replication of that data will begin. If additional data (more than the watermark value) is written to the disk after the snapshot, that data will not be replicated until the next replication. If a replication that was triggered by a watermark fails, the replication will be re-started based on the retry value you enter, assuming the system detects any write activity to the primary disk at that time. Future watermark-triggered replications will not start until after a successful replication occurs.

If you are using continuous replication and you set a watermark value, make sure that it is a value that can actually be reached; otherwise snapshots will rarely be taken. Continuous replication does not take snapshots, but you will need a recent, valid snapshot if you ever need to rollback the replica to an earlier TimeMark during promotion.

If you are using DF2112 SafeCache, replication is triggered when the watermark value of data is moved from the cache resource to the disk.

Start an initial replication on mm/dd/yyyy at hh:mm and then every n hours/minutes thereafter - Indicate when replication should begin and how often it should be repeated.

If a replication is already occurring when the next time interval is reached, the new replication request will be ignored.

Note: if you are using the DF2112 Snapshot Agent for Microsoft Exchange 5.5, the time between each replication should be longer than the time it takes to stop and then re-start the database.

6. Select whether you want to use TCP or RUDP as the protocol for this replication.

If you have a corporate firewall, you may want to select TCP because it allows replication to occur without the need to open any ports.


Replication

7. Indicate which options you want to use for this device.

The Compression option provides enhanced throughput during replication by compressing the data stream. This reduces the size of the transmission, thereby maximizing network bandwidth.

Note: Compression requires 64K of contiguous memory. If the memory in the DF2112 server is very fragmented, it will fail to allocate 64K. When this happens, replication will fail.

The Encryption option provides an additional layer of security during replication by securing data transmission over the network. Initial key distribution is accomplished using the authenticated Diffie-Hellman exchange protocol. Subsequent session keys are derived from the master shared secret, making it very secure.

Enable Microscan - Microscan analyzes each replication block on-the-fly during replication and transmits only the changed sections on the block. This is beneficial if the network transport speed is slow and the client makes small random updates to the disk. If the global Microscan option is turned on, it overrides the Microscan setting for an individual virtual device. Also, if the virtual devices are in a group configured for replication, group policy always overrides the individual device’s policy.


Replication

8. Select how you want to create the replica disk.


Express automatically creates the replica for you from available hard disk segments. You will only have to select the storage pool or physical device that should be used to create the replica resource.


- The target must be the same type (SAN or NAS) as the primary.- The target must be the same size as the primary. - The target can have Clients assigned to it but they cannot be connected during the replication configuration. Since DF2112 cannot detect users connected to NAS resources, you must make sure NAS users are not connected during the replication configuration. Otherwise, once the configuration is created, they will be disconnected.



Replication


Only one disk can be selected at a time from this dialog. To create a replica disk from multiple physical disks, you will need to add the disks one at a time. After selecting the first disk, you will have the option to add

more disks. You will need to do this if the first disk does not have enough space for the replica.


Click Add More if you need to add another physical disk to this replica disk.You will go back to the physical device selection screen where you can select another disk.

Indicate the type of replica disk you are creating.

Select the storage pool or device to use to create the replica resource.


Replication

9. Enter a name for the replica disk.


10. Confirm that all information is correct and then click Finish to create the replication configuration.

Important notes: - Once you create your replication configuration, you should not change the

hostname of the source (primary) server. If you do, you will need to recreate your replication configuration.

- After the configuration is complete, the primary server will be added as a client on the replica server. We do not recommend assigning any resources to this client since its purpose is to be used for replication only.

When willreplication

begin?

If you have configured replication for an individual resource, the system will begin synchronizing the disks immediately after the configuration is complete.

If you have configured replication for a group, synchronization will not start until one of the replication policies (time or watermark) is triggered.

If youconfiguredcontinuousreplication

If you are using continuous replication, you will be prompted to create a Continuous Replication Resource for the primary disk and a Snapshot Resource for the replica disk. If you are not using continuous replication, the wizard will only ask you to create a Snapshot Resource on the replica.

Because old data blocks are moved to the Snapshot Resource as new data is written to the replica, the Snapshot Resource should be large enough to handle the amount of changed data that will be replicated. Since it is not always possible to know how much changed data will be replicated, it is a good idea for you to enable expansion on the target server’s Snapshot Resource. You then need to decide what to do if your Snapshot Resource runs out of space (reaches


Replication

the maximum allowable size or does not have expansion enabled). The default is to stop writing data, meaning the system will prevent any new writes from getting to the disk once the Snapshot Resource runs out of space and it cannot allocate any more.

Protect yourreplica

resource

For added protection, you can mirror or TimeMark an incoming replica resource by highlighting the replica resource and right-clicking on it.

Create a Continuous Replication Resource

This is needed only if you are using continuous replication.

1. Select the storage pool or physical device that should be used to create this Continuous Replication Resource.


Replication

2. Select how you want to create this Continuous Replication Resource.


Express lets you designate how much space to allocate and then automatically creates the resource using an available device.

Note: The Continuous Replication Resource cannot be expanded. Therefore, you should allocate enough space for the resource. By default, the size will be 256 MB or 5% of the size of your primary disk (or 5% of the total size of all members of this group), whichever is larger. If the primary disk regularly experiences a large number of writes, or if the connection to the target server is slow, you may want to increase the size, because if the Continuous Replication Resource should become full, the system switches to delta replication mode until the next regularly-scheduled replication takes place. If you “outgrow” your resource, you will need to disable continuous replication and then re-enable it.

3. Verify the physical devices you have selected, confirm that all information is correct, and then click Finish.

On the Replication tab, you will notice that the Replication Mode is set to Delta. Replication must be initiated once before it switches to continuous mode. You can either wait for the first scheduled replication to occur or you can right-click on your SAN/NAS resource and select Replication --> Synchronize to force replication to occur.


Replication

Check replication statusThere are several ways to check replication status:

• The Replication tab on the primary disk displays information about a specific resource.

• The Incoming and Outgoing objects under the Replication object display information about all replications to or from a specific server.

• The Event Log displays a list of replication information and errors.• The Delta Replication Status Report provides a centralized view for

displaying real-time replication status for all drives enabled for replication.

Replication tabThe following are examples of what you will see by checking the Replication tab for a primary disk:

With ContinuousReplication enabled

With DeltaReplication


Replication

All times shown on the Replication tab are based on the primary server’s clock.

Accumulated Delta Data is the amount of changed data. Note that this value will not display accurate results after a replication has failed. The information will only be accurate after a successful replication.

Replication Status / Last Successful Sync / Average Throughput - You will only see these fields if you are connected to the target server.

Transmitted Data Size is based on the actual size transmitted after compression or with Microscan performed.

Delta Sent represents the amount of data sent (or processed) based on the uncompressed size.

If compression and Microscan are not enabled, the Transmitted Data Size will be the same as Delta Sent and the Current/Average Transmitted Data Throughput will be the same as Instantaneous/Average Throughput.

If compression or Microscan is enabled and the data can be compressed or blocks of data have not changed and will not be sent, the Transmitted Data Size is going to be different from Delta Sent and both Current/Average Transmitted Data Throughput will be based on the actual size of data (compressed or Micro-scanned) sent over the network.

Event Log

Replication events are also written to the primary server’s Event Log, so you can check there for status and operational information, as well as any errors.

Replication object

The Incoming and Outgoing objects under the Replication object display information about each server that replicates to this server or receives replicated data from this server. If the server’s icon is white, the partner server is "connected" or "logged in". If the icon is yellow, the partner server is "not connected" or "not logged in".


Replication

Delta Replication Status Report

The Delta Replication Status Report can be run from the Reports object. It provides a centralized view for displaying real-time replication status for all drives enabled for replication. It can be generated for an individual drive, multiple drives, source server or target server, for any range of dates. This report is useful for administrators managing multiple servers that either replicate data or are the recipients of replicated data.

The report can display information about existing replication configurations only or it can include information about replication configurations that have been deleted or promoted (you must select to view all replication activities in the database).

The following is a sample Delta Replication Status Report:


Replication

Replication performance

Set globalreplication

options

You can set global replication options that affect system performance during replication. While the default settings should be optimal for most configurations, you can adjust the settings for special situations.

To set global replication properties for a server:



Default Protocol - Select the default protocol to use for replication jobs.

Timeout replication after [n] seconds - Timeout after inactivity. This must be the same on both the primary and target replication servers.

Throttle - The maximum amount of bandwidth that will be used for replication. Changing the throttle allows you to limit the amount of bandwidth replication will use. This is useful when the WAN is shared among many applications and you do not want replication traffic to dominate the link. This parameter affects all resources using either remote or local replication. Throttle does not affect manual replication scans; it only affects actual replication. It also does not affect continuous replication, which uses all available bandwidth. Leaving the Throttle field set to 0 (zero) means that the maximum available bandwidth will be used. Besides 0, valid input is 10-1,000,000 KB/s (1G).

Enable Microscan - Microscan analyzes each replication block on-the-fly during replication and transmits only the changed sections on the block. This is beneficial if the network transport speed is slow and the client makes small random updates to the disk. This global Microscan option overrides the Microscan setting for each individual virtual device.

Tune replicationparameters

You can run a test to discover maximum bandwidth and latency in order to optimize remote replication.

1. Right-click on a server under Replication --> Outgoing and select Replication Parameters.

2. Click the Test button to find the maximum bandwidth and latency numbers.

If you know the numbers, you can manually enter them. These values are used to automatically set internal parameters that will optimize replication.

These parameters will take effect for the next new replication session.


Replication

Assign clients to the replica diskYou can assign Clients to the replica disk in preparation for promotion or reversal. Clients will not be able to connect to the replica disk and the Client’s operating system will not see the replica disk until after the promotion or reversal. After the replica disk is promoted or a reversal is performed, you can restart the SAN Client to see the new information and connect to the promoted disk.

To assign Clients:

1. Right-click on an incoming replica resource under the Replication object and select Assign.

2. Select the Client to be assigned and assign the appropriate access rights.

If the Client you want to assign does not appear in the list, click the Add button.

3. Confirm all of the information and then click Finish to assign the Client.

Switch clients to the replica disk when the primary disk failsBecause the replica disk is used for disaster recovery purposes, clients do not have access to the replica. If a disaster occurs and the replica is needed, the administrator can promote the replica to become the primary disk so that clients can access it. The Promote option promotes the replica disk to a usable resource. Doing so breaks the replication configuration. Once a replica disk is promoted, it cannot revert back to a replica disk.

You must have a valid replica disk in order to promote it. For example, if a problem occurred (such as a transmission problem or the replica disk failing) during the first and only replication, the replicated data would be compromised and therefore could not be promoted to a primary disk. If a problem occurred during a subsequent replication, DF2112 will use the data from the Snapshot Resource to recreate the replica from its last good state.

Notes: • You cannot promote a replica disk while a replication is in progress. • If you are using continuous replication, you should not promote a replica

disk while write activity is occurring on the replica.• If you just need to recover a few files from the replica, you can use the

TimeMark/TimeView option instead of promoting the replica. Refer to ‘Use TimeMark/TimeView to recover files from your replica’ for more information.

To promote a replica:

1. In the Console, right-click on an incoming replica resource under the Replication object and select Replication --> Promote.

If the primary server is not available, you will be prompted to roll back the replica to the last good TimeMark, assuming you have TimeMark enabled on the replica. When this occurs, the wizard will not continue with the promotion and you will have to check the Event Log to make sure the rollback completes successfully. Once you have confirmed that it has completed successfully, you need to re-select Replication --> Promote to continue.


Replication

2. Confirm the promotion and click OK.

After promoting a replica of a NAS Resource, the folder(s) of the promoted NAS Resource may not be displayed. To display the folder(s), right-click on the specific NAS Resource and select Refresh.

3. Assign the appropriate clients to this resource.

4. Rescan devices or restart the client to see the promoted resource.

Recreate your original replication configuration

Your original primary disk became unusable due to a disaster and you have promoted the replica disk to a primary disk so that it can service your clients. You have now fixed, rebuilt, or replaced your original primary disk. Do the following to recreate your original replication configuration:

1. From the current primary disk, run the Replication Setup wizard and create a configuration that replicates from the current resource to the original primary server.

Make sure a successful replication has been performed to synchronize the data after the configuration is completed. If you select the Scan option, you must wait for this to complete before running another scan or replication.

2. Assign the appropriate clients to the new replica resource.

3. Detach all clients from the current primary disk.- For Unix clients, type ./df2112client stop from /usr/local/df2112client/bin.- For NAS clients, unmount the resource from the Console.

4. Right-click on the appropriate primary resource or replica resource and select Replication --> Reversal to switch the roles of the disks.

Afterwards, the replica disk becomes the new primary disk while the original primary disk becomes the new replica disk. The existing replication configuration is maintained but clients will be disconnected from the former primary disk.

For more information, refer to ‘Reverse a replication configuration’.


Replication

Use TimeMark/TimeView to recover files from your replica

While the main purpose of replication is for disaster recovery purposes, DF2112 TimeMark allows you to access individual files on your replica without needing to promote the replica. This can be useful when you need to recover a file that was deleted from the primary disk. You can simply create a TimeView of the replica, assign it to a client, and copy back the needed file.

Using TimeMark with a replica is also useful for “what if” scenarios, such as testing a new application on your actual, but not live, data.

In addition, using HyperTrac Backup with Replication and TimeMark allows you to back up your replica at your disaster recovery site without impacting any application servers.

For more information about using TimeMark and HyperTrac, refer to your HyperTrac Backup Accelerator User Guide.

Change your replication configuration options

You can change the following for your replication configuration:

• Static IP address of a remote target server • Policies that trigger replication (watermark, interval, time)• Replication protocol • Use of compression, encryption, or microscan• Replication mode


1. Right-click on the primary disk and select Replication --> Properties.


Notes: - If you are using continuous replication and you enable or disable

encryption, the change will take effect after the next delta replication.- If you are using continuous replication and you change the IP address of

your target server, replication will switch to delta replication mode until the next regularly-scheduled replication takes place.


Replication

Suspend/resume replication schedule

You can suspend future replications from automatically being triggered by your replication policies (watermark, interval, time) for an individual virtual device. Once suspended, all of the device’s replication policies will be put on hold, preventing any future policy-triggered replication from starting. This will not stop a replication that is currently in progress and you can still manually start the replication process while the schedule is suspended.

When replication is resumed, replication will start at the normally scheduled interval based on the device’s replication policies.

To suspend/resume replication:

1. Right-click on the primary disk and select Replication --> Suspend (or Resume).

You can see the current settings by checking the Replication Schedule field on the Replication tab of the primary disk.

Stop a replication in progress

You can stop a replication that is currently in progress. To stop a replication:

1. Right-click on the primary disk and select Replication --> Stop.

Manually start the replication process

To force a replication that is not scheduled, select Replication --> Synchronize.

Notes:

• If replication is already occurring, this request will fail.• If you are replicating a NAS Resource, you must have NAS running on the

target server.


Replication

Reverse a replication configurationReversal switches the roles of the replica disk and the primary disk; The replica disk becomes the new primary disk while the original primary disk becomes the new replica disk. The existing replication configuration is maintained. After the reversal, clients will be disconnected from the former primary disk.

To perform a role reversal, right-click on the appropriate primary resource or replica resource and select Replication --> Reversal.

Notes:

• The primary and replica must be synchronized in order to reverse a replica. If needed, you can manually start the replication from the Console and re-attempt the reversal after the replication is completed.

• If you are using continuous replication, you have to disable it before you can perform the reversal.

• If you are reversing replication for a NAS Resource, NAS must be running on both servers.

• If you are performing a role reversal on a group, we recommend that the group have 40 or fewer resources. If there are more than 40 resources in a group, we recommend that multiple groups be configured to accomplish this task.

Reverse a replica when the primary is not availableReplication can be reversed from the replica server side even if the primary server is offline or is not accessible. When you reverse this type of replica, the replica disk will be promoted to become the primary disk and the replication configuration will be removed.

Afterwards, when the original primary server becomes available, you must repair the replica in order to re-establish a replication configuration.

Notes: • If a primary disk is in a group but the group doesn’t have replication

enabled, the primary resource should leave the group first before the repair replica can be performed.

• If you have CDP enabled on the replica and you want to perform a rollback, you can roll back before or after reversing the replica.

To force a reversal:

1. To perform the role reversal, right-click on the appropriate replica resource and select Replication --> Reversal.

The system will attempt to log into the primary server, but will fail.

2. Click Cancel to exit from the login dialog.

3. Type YES to confirm the operation and then click OK.


Replication

If the replica is not in a valid state, the system will prompt you to roll back to the last good TimeMark, assuming you have TimeMark enabled on the replica. If you also have CDP enabled, you will need to suspend CDP before continuing with the reversal.

If you are using continuous replication and you have CDP enabled on the replica, when you perform a rollback you will have to check the status of the rollback from the Event Log to make sure the rollback completes successfully. Once you have confirmed that it has completed successfully, you can re-select select Replication --> Reversal to reverse the replica. You can then ignore the message that reports that the replica disk is not in a valid state.

4. Afterwards, right-click on the appropriate resource on the current primary and select Replication --> Repair.

5. Confirm the IP address and click OK.

The current primary disk remains as the primary disk and begins replicating to the recovered server.

If you want to recreate your original replication configuration, you will need to perform another reversal so that your original primary becomes the primary disk again.

Relocate a replica

The Relocate feature allows replica storage to be moved from the original replica server to another server while preserving the replication relationship with the primary server. Relocating reassigns ownership to the new server and continues replication according to the set policy. Once the replica storage is relocated to the new server, the replication schedule can be immediately resumed without the need to rescan the disks.

Before you can relocate the replica, you must import the disk to the new DF2112 Server. Refer to ‘Import a disk’ if you need more information.

Once the disk has been imported, open the source server, highlight the virtual resource that is being replicated, right-click and select Relocate.

Notes:

• You cannot relocate a replica that is part of a group.• If you are using continuous replication, you must disable it before relocating

a replica. Failure to do so will keep replication in delta mode, even after the next manual or scheduled replication occurs. You can re-enable continuous replication after relocating the replica.


Replication

Remove a replication configuration

Right-click on the primary disk and select Replication --> Disable. This allows you to remove the replication configuration on the primary and either delete or promote the replica disk on the target server at the same time.

Expand the size of the primary disk

The primary disk and the replica disk must be the same size. If you expand the primary disk, you will enlarge the replica disk to the same size.

Note: You should not attempt to expand the primary disk while replication is occurring. If you do, the disk will expand but the replication will fail.


Replication

Replication with other DF2112 features

Replication and TimeMark

In DF2112 version 5.1 and above, the timestamp of a TimeMark on a replica is the timestamp of the source. In DF2112 5.0 and below, the timestamp was the replica’s local time. If you enable CDP on the replica side, you cannot create any TimeMarks.

Replication and Failover

If replication is in progress and a failover occurs at the same time, the replication will stop. After failover, replication will start at the next normally scheduled interval. This is also true in reverse, if replication is in progress and a recovery occurs at the same time.

Replication and Mirroring

When you promote the mirror of a replica resource, the replication configuration is maintained.

Depending upon the replication schedule, when you promote the mirror of a replica resource, the mirrored copy may not be an identical image of the replication source. In addition, the mirrored copy may contain corrupt data or an incomplete image if the last replication was not successful or if replication is currently occurring. Therefore, it is best to make sure that the last replication was successful and that replication is not occurring when you promote the mirrored copy.


DF2112 User Guide

PerformanceDataFRAME® 2112 SAN (DF2112) offers several options that can dramatically increase the performance of your SAN.

• SafeCache - Allows the DF2112 Server to make use of high-speed storage devices as a read/write staging area, thereby improving the overall performance.

• HotZone - Offers two methods to improve performance, Read Cache and Prefetch.

• Disk striping - Provides software RAID-0 for improved performance using standard disk drives.

SafeCache

The DF2112 SafeCache option improves the overall performance of DF2112-managed disks (virtual and/or service-enabled) by making use of high-speed storage devices, such as RAM disk, NVRAM, or solid-state disk (SSD), as a persistent (non-volatile) read/write cache.

In a centralized storage environment where a large set of database servers share a smaller set of storage devices, data tends to be randomly accessed. Even with a RAID controller that uses cache memory to increase performance and availability, hard disk storage often cannot keep up with application servers’ I/O requests.

SafeCache, working in conjunction with high-speed devices (RAM disk, NVRAM or SSDs) to ‘front’ slower real disks, can significantly improve performance. Since these high-speed devices are 100% immune to random access, SafeCache can write data blocks sequentially to the cache and then move (flush) them to the data disk (random write) as a separate process once the writes have been acknowledged, effectively accelerating the performance of the slower disks.

Regardless of the type of high-speed storage device being used as persistent cache (RAM disk, NVRAM, or SSD), the persistent cache can be mirrored for added protection using the DF2112 Mirroring option. In addition, SSDs and NVRAM have a built-in power supply to minimize potential downtime.


Performance

SafeCache is fully compatible with the DF2112 Failover option, which allows one DF2112 Server to automatically fail over to another without any data loss and without any cache write coherency problems.

Configure SafeCache

To set up SafeCache for a SAN or NAS Resource you must create a cache resource. You can create a cache resource for a single SAN or NAS Resource or you can use the batch feature to create cache resources for multiple SAN or NAS Resources.

Note: If you want to preserve the write order across SAN/NAS Resources, you should create a group and enable SafeCache for the group. This is useful for large databases that span over multiple devices. In such situations, the entire group of devices is acting as one huge device that contains the database. When changes are made to the database, it may involve different places on different devices, and the write order needs to be preserved over the group of devices in order to preserve database integrity. Refer to ‘Groups’ for more information about creating a group.

WRITES READS

1 2 3 4 5

6 7 8 9

1

2

3

4

5 6

7

8

9

PERSISTENT CACHE(High-speed storage devices)

DATA DISK

Data blocks are writtensequentially to the cacheto provide enhanced writeperformance.

For read operations, thecache is checked first incase a newly written blockhas not yet been moved tothe data disk.

Blocks are moved tothe data disk (randomwrite) as a secondaryoperation, after writeshave beenacknowledged from thecache.

IPStor Server

MOVE

MOVE

PersistentCache

DATADISK

ACKNOWLEDGEMENT


Performance

Create a cache resource

1. For a single SAN or NAS Resource, right-click on a SAN or NAS Resource and select SafeCache --> Enable.

For multiple SAN or NAS Resources, right-click on the SAN Resources or NAS Resources object and select SafeCache --> Enable.

2. Select how you want to create the cache resource.

Note that the cache resource cannot be expanded. Therefore, you should allocate enough space for your SAN/NAS resource, taking into account future growth. If you “outgrow” your cache resource, you will need to disable it and then recreate it.


Express automatically creates the cache resource using the criteria you select:





Performance


Select either an entirely unallocated or partially unallocated disk.

Only one disk can be selected at a time from this dialog. To create a cache resource from multiple physical disks, you will need to add the disks one at a time. After selecting the parameters for the first disk, you will have the option to add more disks.


Click Add More if you need to add more space to this cache resource.If you select to add more disks, you will go back to the physical device selection screen where you can select another disk.


Performance

3. Configure when and how the cache should be flushed.

These parameters can be used to further enhance performance. Flush cache when data reaches n% of threshold - Indicate what percentage of the cache resource can be used before DF2112 begins to flush the cache. The default value is 50%.Flush cache after n milliseconds of inactivity - Specify how many milliseconds of inactivity should pass before DF2112 begins to flush the cache even if the threshold from above is not met. The default value is 3000 milliseconds.Flush cache n outstanding commands at a time - Specify the number of outstanding commands to flush at a time. The default value is 6.Skip Duplicate Write Commands - Prevents the system from writing more than once to the same block during the cache flush. Therefore, when the cache flushes data to the underlying virtual device, if there is more than one write to the same block, it skips all of them except the most recent write. This option is on by default. Uncheck it if you are using asynchronous mirroring through a WAN or an unreliable network.

4. Confirm that all information is correct and then click Finish to create the cache resource.You can now mirror your cache resource by highlighting the SAN or NAS Resource and selecting SafeCache --> Mirror --> Add.Note: If you take a snapshot manually (via the Console or the command line) of a SafeCache-enabled resource, the snapshot will not be created until the cache has been flushed. If failover should occur before the cache is empty, the snapshot will not be created. You will need to re-take the snapshot once the server has failed over.


Performance

Check the status of your SafeCache cache resource

You can see the current status of your cache resource by checking the SafeCache tab for a cached resource.

Unlike a snapshot resource that continues to grow, the cache resource is cleared out after data blocks are moved to the data disk. Therefore, you can see the Usage Percentage decrease, even return to 0% if there is no write activity.

For troubleshooting issues pertaining to SafeCache operations, refer to the ‘SafeCache Troubleshooting’ section.

SafeCache properties

You can update the parameters that control how and when data will get flushed from the cache resource to the DF2112-managed disk. To update these parameters:

1. Right-click on a SAN or NAS Resource that has SafeCache enabled and select SafeCache --> Properties.

2. Type a new value for each parameter you want to change.

Refer to the SafeCache configuration section for more details about these parameters.

Disable your SafeCache cache resource

The SafeCache --> Disable option causes the write cache to be flushed, and once completely flushed, removes the cache resource.

Because there is no dynamic free space expansion when the cache resource is full, you can use this option to disable your current cache resource and then manually create a larger one.

If you want to temporarily suspend the SafeCache, use the SafeCache --> Suspend option instead. You will then need to use the SafeCache --> Resume option to begin using the SafeCache again.

If a disk has failed

If a disk containing a cache resource for a NAS Resource has failed (for example, the cable was unplugged), you must perform File System Checking on the cache resource once it has been restored. To do this, right-click on the NAS resource enabled with SafeCache --> File System Checking.

Note that File System Checking should only be initiated once the cache is restored; Otherwise the checking will fail with the message "Failed to Check File System".


Performance

HotZone

The DF2112 HotZone option offers two methods to improve performance, Read Cache and Prefetch.

Read Cache

Read Cache is an intelligent, policy-driven, disk-based staging mechanism that automatically remaps "hot" (frequently used) areas of disks to high-speed storage devices, such as RAM disks, NVRAM, or Solid State Disks (SSDs). This results in enhanced read/write performance for the applications accessing the storage. It also allows you to manage your storage network with a minimal number of high-speed storage devices by leveraging their performance capabilities.

When you configure the Read Cache method, you must divide your virtual or service enabled disk into “zones” of equal size (e.g., 32 MB). DF2112 then automatically creates HotZone storage on the specified high-speed disk. This HotZone storage is divided into zones equal in size to the zones on the virtual or service-enabled disk (e.g.,32 MB), and is provisioned to the disk.

DF2112 monitors reads/writes to each zone on the virtual or service enabled disk. Based on the statistics collected, DF2112 determines the most frequently accessed zones and re-maps the data from these “hot disk segments” to the HotZone storage (located on the high-speed disk) resulting in enhanced read/write performance for the application accessing the storage. Using the continually collected statistics, if

Fibre ChannelOR

Gigabit SAN

Database ApplicationServer

IPStor

The less accessed disk segmentsremain in traditional storage

BD

E

D

C

B

A

E

D

C

B

A

IPStor relocates "hot" disksegments to SAN-based

high-speed disks based onaccess patterns.


Performance

DF2112 determines that the corresponding “hot disk segment” is no longer “hot”, the data from the high performance disk is moved back to its original zone on the virtual or service-enabled disk.

Prefetch

Prefetch enables pre-fetching of data for clients. This allows clients to read ahead consecutively, which can result in improved performance because DF2112 will have the data ready from the anticipatory read as soon as the next request is received from the client. This will reduce the latency of the command and improve the sequential read benchmarks in most cases.

Prefetch may not be helpful if the client is already submitting sequential reads with multiple outstanding commands. However, the stop-and-wait case (with one read outstanding) can often be improved dramatically by enabling Prefetch.

Prefetch does not affect writing, or random reading.

Applications that copy large files (i.e. video streaming) and applications that back up files are examples of applications that read sequentially and might benefit from Prefetch.

Configure HotZone

1. Right-click on a SAN or NAS Resource and select HotZone --> Enable.

For multiple SAN or NAS Resources, right-click on the SAN Resources or NAS Resources object and select HotZone --> Enable.

2. Select the HotZone method to use.


Performance

3. (Prefetch only) Set Prefetch properties.

These properties control how the prefetching (read ahead) is done. While you may need to adjust the default settings to enhance performance, MPC has determined that the defaults shown here are best suited for most disks/applications.

Maximum prefetch chains - Number of locations from the disk to read from.

Maximum read ahead - The maximum per chain. This can override the Read ahead option.

Read ahead - How much should be read ahead at a time. No matter how this is set, you can never read more than the Maximum read ahead setting allows.

Chain Timeout - Specify how long the system should wait before freeing up a chain.

4. (Read Cache only) Select the storage pool or physical device(s) from which to create this HotZone.


Performance

5. (Read Cache only) Select how you want to create the HotZone.

Note that the HotZone cannot be expanded. Therefore, you should allocate enough space for your SAN/NAS resource, taking into account future growth. If you “outgrow” your HotZone, you will need to disable it and then recreate it.


Express automatically creates the HotZone storage using the criteria you select:





Performance

6. (Read Cache only) Select the disk to use for the HotZone storage.

If you selected Custom, you can piece together space from one or more disks.

7. (Read Cache only) Enter configuration information about the zones.


Performance

Size of each zone - Indicate how large each zone should be. DF2112 monitors reads/writes to each zone on the disk. Based on the statistics collected, DF2112 determines the most frequently accessed zones and re-maps the data from these “hot zones” to the HotZone storage. You should check with your application server to determine how much data is read/written at one time. The block size used by the application should ideally match the size of each zone.

Minimum stay time - Indicate the minimum amount of time data should remain in the HotZone before being moved back to its original zone once DF2112 determines that the zone is no longer “hot”.

8. (Read Cache only) Enter configuration information about zone access.

Access type - Indicate whether the zone should be monitored for reads, writes, or both.

Access intensity - Indicate how DF2112 should determine if a zone is “hot”. Number of IOs performed at the site uses the amount of data transferred (read/write) as a determining factor for each zone.

9. Confirm that all information is correct and then click Finish to enable HotZone.


Performance

Check the status of HotZone

You can see the current status of your HotZone by checking the HotZone tab for a configured resource.

Note that if you manually suspend HotZone from the Console when the device configured with the HotZone option is running normally, the status on the HotZone tab will display 'Not Accessible (Offline)'.

You can also see statistics about the zone by checking the HotZone Statistics tab:


Performance

The information displayed is initially for the current interval (hour, day, week, or month). You can go backward (and then forward) to see any particular interval. You can also view multiple intervals by moving backward to a previous interval and then clicking the Play button to see everything from that point to the present interval.

Click the Detail View button to see more detail. There you will see the information presented more granularly, for smaller amounts of the disk.

If HotZone is being used in conjunction with Fibre Channel or iSCSI failover and a failover has occurred, the HotZone Statistics will not be displayed while in a failover state. The reason for this is because the server that took over does not contain the failed server’s information on the HotZone Statistics. As a result, the Console will display empty statistics for the primary server while the secondary has taken over. Once the failed server is restored, the statistics will display properly. This does not affect the functionality of the HotZone option while in a failover state.

Disable HotZone

The HotZone --> Disable option permanently stops HotZone for the specific SAN/NAS resource.

Because there is no dynamic free space expansion when the HotZone is full, you can use this option to disable your current HotZone and then manually create a larger one.

If you want to temporarily suspend HotZone, use the HotZone --> Suspend option instead. You will then need to use the HotZone --> Resume option to begin using HotZone again.


Performance

Disk stripingThe DF2112 Disk Striping option provides software RAID 0 for improved performance using standard disk drives.

Disk striping uses a set of disks. Data written to the set is broken down into user-defined chunks and written, chunk by chunk, to each drive in the set. The chunks can be thought of as forming stripes across each drive; hence the term disk striping.

For example, with a two-drive set and a 64 KB chunk size, writing 192 KB of data to the set would result in the data being written in three 64 KB chunks to the following drives:

• The first 64 KB would be written to the first drive, into the first chunk.• The second 64 KB would be written to the second drive, into the second

chunk.• The last 64 KB would be written to the first drive, into the second chunk.

While disk striping does not provide any redundancy, it greatly improves I/O by spreading the I/O load across all drives in the set, making it ideal for applications that require high throughput.

Configure Disk Striping

In order to use disk striping, you must have the following:

• At least two (max. 32) identical SCSI addressable disks with the same vendor ID, product ID, and size

• These disks must be Unassigned (i.e., not Reserved for Virtual Device)

Notes:

• Disk striping is intended for aggregating JBOD storage devices only; it is not supported for RAID systems, even if the RAID system is configured as a JBOD.

• Striped disks should not be enabled for multipathing.


Performance

1. Expand Physical Resources --> Physical Devices --> right-click on Striping Devices --> select Create Disk.

2. Enter information about the striped set and select which devices will be part of the striped set.

Chunk Size - Amount of data that will be written to each disk at a time.

SCSI ID and LUN - Set the SCSI ID and LUN for the new drive that will be created (comprised of the identical SCSI disks).

3. Click OK when done.

A new disk called FALCON:RAIDDISK-MFFN00 will be created under the Striping Devices object.

The size of this new disk is about equal to the size of the selected devices combined.

The Category for devices that were selected to become part of the striped set will now show Used in Striped Set.

4. Create a SAN Resource to access the striped set.

Be sure to select the Custom creation method so that you can select the FALCON:RAIDDISK-MFFN00 disk.


DF2112 User Guide

Zero Impact BackupDF2112’s ZeroImpact Backup Enabler allows you to perform a local raw device tape backup/restore of your virtual drives.

A raw device backup is a low-level backup or full copy request for block information at the volume level. Linux’s dd command generates a low-level request.

Examples of Linux applications that have been tested with DF2112 to perform raw device backups include BakBone’s NetVault version 7.42 and Symantec Veritas NetBackup version 6.0.

Using DF2112’s ZeroImpact Backup Enabler with raw device backup software eliminates the need for the application server to play any role in backup and restore operations. Application servers on the SAN benefit from performance increases and the elimination of overhead associated with backup/restore operations because the command and data paths are rendered exclusively local to the DF2112 Server. This results in the most optimal data transfer between the disks and the tape, and is the only way to achieve net transfer rates that are limited only by the disk’s or tape’s engine. The backup process automatically leverages DF2112’s snapshot engine to guarantee point-in-time consistency.

To ensure full transactional integrity, this feature integrates with DF2112’s Snapshot Agents and the Group Snapshot feature.

Configure ZeroImpact backup

You must have a Snapshot Resource for each virtual device you want to back up. If you do not have one, you will be prompted to create one. Refer to Create a Snapshot Resource for more information.

1. Right-click on the SAN or NAS resource that you want to back up and select Backup --> Enable.

Note: There is a maximum of 256 virtual devices that can be enabled for ZeroImpact backup.


Zero Impact Backup

2. Enter a raw device name for the virtual device that you want to back up.

3. Configure the backup policy.

Use an existing TimeMark snapshot - (This option is only valid if you are using DF2112’s TimeMark option on this SAN/NAS resource.) If a TimeMark exists for this virtual device, that image will be used for the backup. It may or may not be a current image at the time backup is initiated. If a TimeMark does not exist, a snapshot will be taken.

Create a new snapshot - A new snapshot will be created for the backup, ensuring the backup will be made from the most current image.


Zero Impact Backup

4. Determine how long to maintain the backup session.

Each time a backup is requested by a third-party backup application, DF2112 creates a backup session. Depending upon the snapshot criteria you set on the previous window, a snapshot may be taken at the start of the backup session. (If the resource is part of a group, snapshots for all resources in the group will be taken at the same time.) Subsequently, each raw device is opened for backup and then closed. Afterwards, your backup application may verify the backup by comparing the data on tape with that of the snapshot image that was created for this session. For this reason, it is important to maintain the backup session until the verification is complete. Because DF2112 cannot tell how long your backup application needs to rewind the tape and compare the data, you must select an option on this screen to tell DF2112 how long to maintain the session. Note that the session length only applies to backups (reading from a raw device), not restores (writing to a raw device), and the actual session will end within 60 seconds of the session length you specify.

Absolute session length - This option maintains the backup session for a set period of time from the start of the backup session. Use this option when you know approximately how long your backup should take. You can also use this option to limit the length of time that the backup can run.

Relative session length - This option maintains the backup session for a period of time after the backup has completed (the last raw device has been opened and closed). This is more flexible than the absolute session length since it may be difficult to estimate how long it takes to back up all devices. With relative time, you only need to estimate how long to wait after the last device is backed up. If there is a problem during the backup (for example, such as when a tape is full), and the backup cannot complete, the Inactivity timeout tells DF2112 how long to wait before ending the backup session.

5. Confirm all information and click Finish to enable backup.


Zero Impact Backup

Back up a DF2112 logical resource using dd

Below are procedures for using Linux’s dd command to perform a raw device backup. Refer to the documentation that came with your backup software if you are using a backup application to perform the backup.

1. Determine the raw device name of the virtual device that you want to back up.

You can find this name from the DF2112 Console. It is displayed on the Backup tab when you highlight a specific SAN or NAS resource.

2. Execute the following command on the DF2112 Server:

where kisdev# refers to the raw device name of the DF2112 logical resource.

st0 is the tape device. If you have multiple tape devices, substitute the correct number in place of the zero. You can verify that you have selected the right tape device by using the command: tar -xvf /dev/st0 where 0 is a variable.

bs=65536 sets the block size to 64K to achieve faster performance.

Note: When performing a Linux dd to a direct device, the target device can be any device recognized by the system. However, we recommend using caution when doing this, because the target device may contain data that will be overwritten. Should you select a DF2112 SAN Resource as the target, we recommend that it does not contain any data or have any Clients attached. This way, after the dd is complete, the data will be available to Clients from the SAN Resource.

You can also back up a logical resource to another logical resource. Prior to doing that, all target logical resources (which are receiving data) must be detached from the DF2112 Client machine(s). Instead of specifying st0 for the tape device, specify the raw device name of the target logical resource

When the back up is finished, you will only see one logical resource listed in the Console. This is caused by the fact that when you reserve a hard drive for use as a virtual device, DF2112 writes partition information to the header and the Console uses this information to recognize the hard drive. Since a Linux dd will do an exact copy of the hard drive, this partition information will exist on the second hard drive, will be read by the Console, and only one drive will be shown. If you need to make a usable copy of a virtual drive, you should use DF2112’s Snapshot Copy option.

dd if=/dev/isdev/kisdev# of=/dev/st0 bs=65536


Zero Impact Backup

Restore a volume backed up using ZeroImpact Backup Enabler

You will need to do the following in order to restore an entire volume that was backed up with the ZeroImpact Backup Enabler.

1. Unassign the volume you will be restoring from the SAN client to which it attaches.

This ensures that the client cannot change data while the restore is taking place.

2. Before you start the restore, suspend replication and disable TimeMark.

These can hamper the performance of the restore. Before you disable TimeMark be sure to record the current policies. This can be done by right-clicking on the virtual drive and select TimeMark/CDP --> Properties.

3. Once the restore is complete, resume replication and re-enable TimeMark, if necessary.


DF2112 User Guide

IP TrunkingIP Trunking is a load balancing/path redundancy application that enables your DF2112 Server to load balance network traffic across two or more network connections creating redundant data paths throughout the network.

IP Trunking offers a new level of data accessibility and improved performance for storage systems by eliminating the point of failure represented by a single input/output (I/O) path between servers and storage systems and permits I/O to be distributed across multiple paths.

IP Trunking will automatically group up to four network interface cards into a single group. Think of this group as a single virtual adapter that is actually made up of two to four physical adapters. To the system and the network, it appears as a single interface with one IP address. However, throughput is increased by a factor equal to the number of adapters in the group. Also, IP Trunking detects faults anywhere from the NIC out into the network and provides dynamic failover in the event of a failure.

Note: The DF2112 server network cards being used for IP Trunking must be on the same physical network in order to work correctly. For example: nic1 and nic2 are grouped together on a DF2112 server, but nic1 is on one Ethernet switch while nic2 is on another. If nic1 fails, IP Trunking will switch to nic2. But since nic2 is on the other Ethernet switch, clients may not be able to reach the server on that switch if they are not attached to it or are on different IP segments. This is particularly true for failover servers using IP Trunking.


IP Trunking

Installing IP Trunking

MPC provides a script file to install IP Trunking.

Notes:

• Before installation, the network hotplug policy agent needs to be disabled by renaming /etc/hotplug/net.agent to /etc/hotplug/net.agent.orig. This will prevent the network interface from reverting back to its original IP address, which would cause a conflict.

• RedHat 4 update 2 - The Red Hat default gcc Java does not work with nexjui. Install JRE 5.0 update 8 from: https://sdlc5b.sun.com/ECom/EComActionServlet;jsessionid=E052EEF8E8CA94925154D8A2FA2D9E9FRun the following command to switch to JRE 5.0:# alternatives --install /usr/bin/java java /usr/java/jre1.5.0_08/bin/java 1508

• RedHat 4 and SUSE 9 - IPv6 tunneling is not supported. To disable it, open the file /etc/modprobe.conf and add the following line: alias net-pf-10 offIf the line alias net-pf-10 ipv6 appears, modify that line instead of adding a new line. Reboot your machine afterwards for the change to take effect.

Launching the IP Trunking installer

1. Insert the DF2112 CD in your CD ROM drive.

2. Copy the self-extracting installation file, IPTrunking.bin, located on the DF2112 CD to your Linux system.

The file can be found in one of the following directories, depending upon which version of Linux you are using:\\Server\Linux-2.6.9-22.EL.smp\\Server\Linux-2.6.11.4-21.7-smp

3. Make the IPTrunking.bin file executable by entering the command chmod +x IPTrunking.bin and then execute the IPTrunking.bin file.

This self-extracting install script will validate your current kernel configuration to determine if it is configured correctly for IP Trunking, extract its files, then install IP Trunking. Follow the installation steps to set up and install IP Trunking for Linux. You are provided with the option to load the product immediately or instructions on how to install at a later time.

Upon launching IPTrunking.bin, the following files are extracted and installed to the /usr/local/IPTrunking directory:

File Description

/modules Directory containing the per kernel drive modules.

nexload Used to load IP Trunking. Refer to the next section for details.

nexunload Used to unload IP Trunking


IP Trunking

After IPTrunking.bin extracts the files, the IP Trunking installer is launched. The loader will prompt you with a series of questions. The next section will step you through running nexload and its installation options.

Installation options and prompts

The IP Trunking installer performs the following tasks during installation:

1. Displays license agreement and asks for acceptance.

2. Prompts user asking to view the readme file.

3. Determines if the system's kernel version is supported.

4. Prompts user to choose Automatic or Manual configuration method.

5. Prompts user if they would like to start IP Trunking after install and add the command to the system's startup script.

The following covers each step of the installation process.

Initial installation options

A) After the Installer presents the license agreement and option to view the Readme file, the Installer checks the systems kernel version.

If your current kernel is not supported, the Installer will terminate and you will need to update your kernel before continuing.

B) Next, the Installer will give you an choice to use the Automatic configuration option or the Manual configuration method. The Automatic option will configure all available adapters in a single group (nex0). The Automatic method will use

nexcui Console based user interface. Refer to ‘IP Trunking Console - nexcui’ for details on using nexcui.

nexjui Java based user interface. Requires the Java Runtime Environment (JRE) from Sun Microsystems. Refer to ‘IP Trunking Java Console – nexjui’ for details on using nexjui.

nexconfig Console utility used to create groups, assign adapters to the groups, and configure advanced settings.

/UI Directory with all of the files required to run the Java user interface.

License The license agreement file.

Readme The IP Trunking readme file.

File Description


IP Trunking

the adapter eth0 as the primary adapter and use eth0's IP address for that of the group. The Manual option gives you the choice to create multiple groups and manually configure options such as load balancing.

If you choose the Automatic method continue with the Automatic configuration option section below. For more information on the manual method, refer to the section ‘Manual configuration option’.

Automatic configuration option

A) If you chose the Automatic configuration option, the next few prompts from the installer are used to configure IP Trunking. The first prompt is for an external IP address to be used by IP Trunking to test for failover conditions. If a default gateway is configured for the system, the Installer will provide you with a choice to use its IP address or allow you to input an alternate address. If a link goes down, IP Trunking will use this IP address to ping and verify which port to take down. Also, the test address is used to help determine that the port is functioning properly when the link is reestablished. This value can be edited later by running the nexconfig utility.

B) The Installer will next prompt to enable load balancing or not. If load balancing is not enabled, all traffic will normally flow through the primary adapter (eth0). If the primary port were to fail, traffic will then failover to the secondary port. With load balancing enabled, connections will be assigned to each adapter in a round robin fashion and traffic will be load balanced across all adapters in the group. With load balancing enabled, you have the benefits of both increasing throughput to the server and dynamic failover in the event of a failure.

C) After the install script is finished configuring IP Trunking, it will prompt whether or not to load IP Trunking automatically upon startup. If you answer yes, the installer will add the following command to the end of your /etc/rc.d/rc.local file:

/usr/local/IPTrunking/nexload

If you choose no, you can load IP Trunking manually at anytime by using the nexload command. Symbolic links have been created for nexload so it can be executed from any directory.

You have now successfully installed and configured IP Trunking for Linux. Proceed to the ‘Using IP Trunking’ section for details on the two UI utilities used to monitor IP Trunking.


IP Trunking

Manual configuration option

If the manual configuration option was selected, the install script will load the configuration console utility called nexconfig. The following nexconfig console screen should now be displayed:

Follow the steps below to manually configure the adapter groups and assign the adapters to each group:

1. With the cursor in the Number of Groups box, input the number of groups (arrays) you would like to create.

The cursor should now be in the first box of the first adapter (eth0).

2. For all adapters listed, select the group number (0 through n) the adapter should be assigned to.

For example, if you entered 2 for the number of groups then you would enter 0 (group 1) or 1 (for group 2).

3. In the second box, designate the adapter as either Primary (p) or Secondary (s).

For eth0, input the group number it should be assigned to and either P for primary or S for secondary.

4. Repeat for the remaining adapters.

Make sure that you have assigned at least one adapter as primary. The group will use the IP address of the Primary adapter for the group's IP address.

IP Trunking v1.2 Configuration Utility Number of Groups: [ ]

Adapters: [ ] [ ] eth0

[ ] [ ] eth1

[ ] [ ] eth2

[ ] [ ] eth3

Groups (Devices):

[ ] Load Balancing Disabled

<Save> <Cancel> <Help>

Enter the number of groups needed or ? for field help.


IP Trunking

5. For each group listed, input an external IP address to be used by IP Trunking to test for failover conditions.

If a default gateway is configured for the system, we recommend you use its IP address as the test address. Make sure that test IP address chosen for each group is reachable from the IP address assigned to that group. If a link goes down, IP Trunking will use this IP address to ping and verify which port to take down. Also, the test address is used to help determine that the port is functioning properly when the link is reestablished. This value can be edited later by running the nexconfig utility.

6. In the final box, determine if you want to leave the load balancing function turned on or disabled.

If you only want failover functionality, place an X in this box. If you want to load balance traffic across the adapters, leave this box blank.

7. Use the arrow keys to select the <Save> option and hit Enter to save your configuration.

Load IP Trunking on boot-up

After the Installer is finished configuring IP Trunking, it will prompt whether or not to load IP Trunking automatically upon startup. If you answer yes, the Installer will add the following command to the end of your /etc/rc.d/rc.local file:

/usr/local/IPTrunking/nexload

If you choose no, you can load IP Trunking manually at anytime by using the nexload command. Symbolic links have been created for nexload and it can be executed from any directory location.

You have now successfully installed and configured IP Trunking for Linux. Proceed to the ‘Using IP Trunking’ section for details on the two UI utilities used to monitor IP Trunking.

Note: If the DF2112 Server is configured to use jumbo frames (MTU = 9000) you must configure each of your NICs the same way before loading IP Trunking. If you have not configured them, you must manually execute the ifconfig command to load the nex driver with mtu size = 9000 each time IP Trunking is restarted.

If you change network configuration or restart network while IP Trunking is loaded

If you change your network configuration or restart your network while IP Trunking is active, you will need to perform the following steps:

1. Unload IP Trunking using the nexunload command.

2. Restart Linux network services using the command "rcnetwork restart".

3. Load IP Trunking using nexload command.


IP Trunking

Using IP Trunking

MPC has provided two UI utilities to monitor the IP Trunking product. The first is a console interface called nexcui. The other interface is called nexjui and is a graphical interface written in Java. The next two sections cover the use of these two interfaces to monitor IP Trunking.

IP Trunking Console - nexcui

IP Trunking console interface is accessed by launching nexcui. Symbolic links have been created for nexcui and it can be executed from anywhere. This text-based, console interface will show the current status of the IP Trunking group, the NICs and their statistics. A sample output from the console can be seen below:

The first column shows the IP Trunking group's device name. In the above example there is one group (nex0). The second column lists the Ethernet adapters that are assigned to the group. In the above example eth0 and eth1. The third column displays the current status of each adapter. IP Trunking keeps track of five adapter states listed in the table below.

In addition to device status, two columns of throughput statistics are collected for each device, the groups, and totals for the system. If you would like to see the statistics continuously updated, use the -c command line option:

nexcui -c

The default update interval is once per second. If you need to change this use the –i command line option:

Status Values Definitions

Up Normal State. Adapter functioning properly.

Down Adapter is currently down for the first time.

Up-DwnPr Adapter is currently up, however it has failed at least once since last reboot.

DwnMulti Adapter is currently down and has been down multiple times.

Disabled Adapter is has been permanently removed from the group.


IP Trunking

nexcui -c -i sec

Where sec is the amount of time in seconds for the update interval. For example, nexcui -c -i 5 will update every five seconds.

To exit the console interface, press Ctrl-C.

IP Trunking Java Console – nexjui

IP Trunking also has a graphical interface called nexjui that can be launched by entering the command nexjui from within an XTerm window. Symbolic links have been created for nexjui and it can be executed from any directory. This Java-based, graphical interface will show the current status of the IP Trunking group, the NICs and their statistics.

(IP Trunking for Linux only) Since the standard Linux distributions do not include Java, you must install the Java Runtime Environment (JRE) from Sun Microsystems. The JRE can be found in the /Console/Linux directory on the DF2112 CD. For more information on installing the JRE, refer to ‘DF2112 Server Console Installation’ in chapter 2. The installation should place all Java files in the /usr/java/jre1.3.1_03/ directory. To launch the java interface from a command line, execute the shell script called nexjui. Once loaded, you should see console similar to the one below.


IP Trunking

With the Java console loaded, you should see a familiar tree view on the left hand side representing the device list showing the current status of each device. The right hand side is broken out into three sections. The top displays the current selection, the middle section list throughput details for the selected device. The last section provides breakout of statistics by device or protocol. Also note that the Statistics section will be blank until you select a device on the left-hand side to monitor.

Current status

The Current Status section of the console located on the left-hand side provides an at-a-glance view of the IP Trunking system and all devices. Here you can see the current state of each adapter and whether the adapter has currently failed, or has failed in the past. The top layer of the Tree is the system host followed by the list of IP Trunking groups and finally each adapter contained within each group. You may notice all of the Icons for system hosts, groups and adapters are color coded to provide an at-a-glance view of the health of all device being managed. A complete list of Icons and their meanings is provided below:

Server Icons

Normal State. Server up and running with no errors.

Server has one or more failed adapters.

Group Icons

Normal State. All adapters in the group are functioning properly.

One or more adapters in the group have failed.

Group down. All adapters in the group have failed.

Communication to group was lost.

Adapter Icons

Normal State. Adapter functioning properly.

Adapter is currently down for the first time.

Adapter is currently up, however it has failed at least once since last reboot.

Adapter is currently down and has been down multiple times.


IP Trunking

Current statistics

To view statistics for a specific device, first select the device (either the system, group or adapter) from the Current Status tree on the left side of the console. Statistics for the selected device are displayed in three sections on the right side of the console. The first section provides a real-time bar graph of the currently selected device. Next, device totals are broken out for both incoming and outgoing data. The device details section at the bottom shows further data broken out by protocol or device. The following topics will describe each section in detail.

CurrentSelection bar

The Current Selection bar, located at the top of the right-hand side, identifies the current device that throughput statistics are being generated on. To change the current device, simply select a server, group or adapter from the tree in the left side of the console. Notice how the Current Selection bar changes depending on if a server, group, or adapter is selected to identify the device being monitored.

Device Totals The heading of this section provides a detailed description of the device currently being monitored and is located just above the bar graph. This heading changes to Server Totals:, Group Totals:, or Adapter Totals:, followed by the description of the device depending on what type of device is being monitored.

The Device Totals section is broken down into two sections. First, a bar graph shows total throughput in real-time for the device broken out by protocol. Below the bar chart, total throughput is broken out in tabular form. Each of these sections will be described in more detail.

Adapter is has been permanently removed from the group.

Communication to adapter was lost.


IP Trunking

Bar Graph The bar graph at the top of the Device Totals section provides a real-time graphical representation of network traffic through the device (a server, group or adapter depending on what is selected on the left of the console). The maximum value on the scale is fixed and determined by the number of adapters and their media speed. For instance, if a group consisting of two 100Mbit adapters is selected the scale will show the maximum theoretical throughput of 200Mbsec and represent the actual throughput of the group in relation to the 200 Mbits maximum.

ThroughputTotals

Directly below the Bar Chart, the total throughput for the device is displayed in both Mbits per second or Packets/sec. The totals are also broken out by incoming and outgoing data. Optionally you can choose to view cumulative totals for the device measured in either packets or bytes. There are two buttons located under the Device Totals table to set the time interval that data is updated as well as the format or scale used to display the data. The following section will describe how to change both the Interval and format of the data.

ChangingInterval

The time interval in which data is updated can be easily changed by selecting the Interval button under the Device Total table in the middle of the console. The default setting is every second. However the interval can be changed to every 5, 10, 30 or 60 seconds.

Note: Changing this setting affects all data collected in the console.

Changingformat

The format of data displayed can easily be changed for the device totals. The format can be switched from a per second basis to cumulative data for the device. Also note that the scale of the data can is changed from Bytes to Mbits/second if on a per second basis.


IP Trunking

DeviceBreakout

The Device Breakout section provides detailed breakout of throughput data for the currently selected device. You can choose between the breakout of the data by Protocol or by device. Furthermore, the format of the data can be changed as well.

Changing the Breakout Details

You can compare throughput data in a number of ways for the currently selected device. Options include breakout by protocol, by group or adapter. To change the type of breakout detail displayed, select the Details button and choose the desired selection. The following describes each selection in detail:

• Protocol - The Protocol option will breakout data by protocol with statistics gathered for IP based traffic. All other protocol data is listed under Other. In addition, broadcast and multicast traffic detail is provided.

• Group - This option will contrast the device totals above with each group (array) total on the server.

• Adapter - This will provide details for each of the adapters in a group (array). If the current selection is a group it will display breakout for each of the adapters in that group.

Changing Format

The format of the data can easily be changed for the device breakout section. First, the format can be switched between cumulative Bytes, cumulative Packets, Mbits per second, and Packets per second. Each option is described below.

• Bytes - This option provides cumulative data displayed in Bytes This option shows the total bytes sent or received since the server was last rebooted.


IP Trunking

• Packets - This option provides cumulative data displayed in packets. This option shows the total packets that were received since the server was last rebooted.

• Mbits/sec - This option displays incoming , outgoing and total data for each component in Mbits/Sec.

• Packets/sec - This option displays incoming, outgoing and total data for each component in packets/sec.

Unloading IP Trunking

To unload the IP Trunking driver, run nexunload. Nexunload will unload the IP Trunking virtual device and restore the IP address bindings back to the original physical adapters. Symbolic links have been created for nexunload and it can be executed from any directory.

Note: (For Linux) When a group has two or more NICs assigned to it, the last NIC in the group will lose it IP address after issuing the nexunload command. In order to add the IP address back to eth1, you will need to restart the Linux network services.

Setting the IP Address of the Server

To change the IP address of the server with IP Trunking loaded, you will need to modify the IP information for the nex0 device. To re-address the nex0 device, use the ifconfig utility on Linux as you would with any other Ethernet device. IP Trunking supports all ifconfig requests. For example to change the IP address of the server to 66.139.25.28 with a subnet mask of 255.255.255.192 you would use the following command:

ifconfig nex0 66.139.25.28 netmask 255.255.255.192

Using Nexconfig

The nexconfig utility is used to modify the IP Trunking configuration. Use nexconfig to create groups, assign adapters to the groups, select the default gateway/failover detection host, and enable or disable load balancing. Symbolic links have been


IP Trunking

created for nexcui and it can be executed from any directory. If you installed IP Trunking with the automatic configuration option, the configuration screen will look like the example below.

In this example, a Linux system contains four network cards. To reconfigure adapter assignments or other configuration options in nexconfig, perform the following steps:

1. If no groups were defined, enter the number of groups (1 to 4) you wish to create.

Each group you create will need at least one adapter assigned to it. In the example below, two groups were created. Note that the console screen is updated with the two groups (nex0 and nex1) listed below the adapter list.

The maximum number of groups that can be created in this example is four. Creating four groups means one network interface per group. However, load balancing and fault tolerance will not function since there is only one interface in the group. There must be at least two network cards per group in order to use load balancing and fault tolerance capabilities. For load balancing and fault

IP Trunking v1.2 Configuration Utility Number of Groups: [ ]


[ ] [ ] eth1

[ ] [ ] eth2

[ ] [ ] eth3

Groups (Devices):





IP Trunking

tolerance to function correctly all network interfaces within a group must be connected on the physical segment.

2. For each adapter (eth0 through eth3), input the group number you want the adapter assigned to in the first box.

For example, to assign eth0 to group nex0, input "0" in the first box on the eth0 line. In the second box, assign either primary or secondary status for the adapter. Type a 'P' for primary or 'S' for secondary status. There can be only one primary adapter per group. The IP address of the primary will be the address assigned to that group number. Also, only one adapter can be chosen as primary.

3. Repeat step 2 for each adapter.

4. For each group listed, input an external host IP address to be used by IP Trunking to test for failover conditions.

If a default gateway is configured for the system, we recommend you use its IP address as the test address. Make sure that test IP address chosen for each group is reachable from the IP address assigned to that group. If a link goes down, IP Trunking will use this IP address to ping and verify which port to take down. Also, the test address is used to help determine that the port is functioning properly when the link is reestablished.

In the example below, 66.137.8.1 was assigned as the test address for nex0 and 192.44.69.1 was assigned for nex1.

IP Trunking for Linux v1.2 Configuration Utility

Number of Groups: [2]


[ ] [ ] eth1

[ ] [ ] eth2

[ ] [ ] eth3

Groups (Devices): (0) nex0 DefGw: [ ]

(1) nex1 DefGw: [ ]



Enter the group/device number to assign the device to or ? for field help.


IP Trunking

5. If you only want failover functionality and have the load balancing function turned off, place an X in the final box.

If you want to load balance traffic across the adapters, leave this box blank.

6. Arrow down to the <Save> button to save the current configuration and exit.

IP Trunking for Linux v1.2 Configuration Utility

Number of Groups: [2]

Adapters: [0] [P] eth0

[0] [S] eth1

[1] [P] eth2

[1] [S] eth3

Groups (Devices): (0) nex0 DefGw: [66.137.8.1 ] <IP Addr: 66.137.8.6>

(1) nex1 DefGw: [192.44.69.1 ] <IP Addr: 192.44.69.96>





IP Trunking

Navigation keys used in nexconfig

Uninstalling IP Trunking

1. Unload the IP Trunking nex driver by executing nexunload on the console.

2. Remove the /usr/local/IPTrunking directory using the command rm -rf /usr/local/IPTrunking.

3. Remove IP Trunking start-up links by removing the nexload command in the /etc/rc.d/rc. (SUSE) or /etc/init.rd/nex (Red Hat) local file.

? Field specific help

Tab Move to the next field

Left arrow Move to the previous field or previous character

Right arrow Move to the next field or next character

Up arrow Move to the previous field

Down arrow Move to the next field

Backspace Delete previous character

^M <CR> Execute button or move to next field

^H Help text

^S Save and exit

^X Clear entire field

^C Abort and exit


DF2112 User Guide

MultipathingNote: This option may not be available in all DF2112 versions. Check with your vendor to determine the availability.

The MultiPathing option allows the DF2112 Server to intelligently distribute I/O traffic across multiple Fibre Channel (FC) ports to maximize efficiency and enhance system performance.

Because it uses parallel active storage paths between the DF2112 Server and storage arrays, DF2112 can transparently reroute the I/O traffic to an alternate storage path to ensure business continuity in the event of a storage path failure.

Multipathing is possible due to the existence of multiple HBAs in the DF2112 server and/or multiple storage controllers in the storage systems that can access the same physical LUN.

The multiple paths cause the same LUN to have multiple instances in the DF2112 server.

Storage System IPStor Server

Fibre Channel Switch

Lun 0

HBA 0

HBA 1

Lun 0

Lun 0

Lun 1

Lun 0

Lun 1

Lun 1

Lun 1

0 0 0

0 1 0

1 0 0

1 1 0

0 0 1

0 1 1

1 0 1

1 1 1

HBA Target LUNTwo physical LUNs inside a storage system are connected to two controllers

Server is connected to the storage via the FC switch by two HBAs FC switch - not zoned

Each LUN is seen four times from the server. Each controller is treated as a separate target by each HBA in the server. Each target contains two LUNs. Each HBA in the server sees the same for LUNs.

LUN 0Controller 0

Controller 1 LUN 1


Multipathing

Path switchingDF2112 automatically and transparently switches to a standby path if the primary storage path fails. Path switching is an important fault tolerance function of mission-critical systems that rely on high availability.

If the switching is caused by a connectivity interruption, when the connectivity is restored, DF2112 will automatically switch back to the original active path.

If the switching is caused by a manual change of the active path, either through the DF2112 console or the storage management console, DF2112 will not automatically switch back to the preferred path.

Load distributionAutomatic load distribution allows for two or more storage paths to be simultaneously used for read/write operations, enhancing performance by automatically and equally dispersing data access across all of the available active paths.

An Autopathing feature is provided to automatically assign optimized paths to each LUN.

Preferred pathsSome storage systems support the concept of preferred paths, which means the system determines the preferred paths and provides the means for DF2112 to discover them.

DF2112’s Autopathing feature detects and follows the preferred paths set by the storage console on supported systems and uses them as DF2112’s preferred paths.

Storage System

IPStorServer

Fibre Channel Switch

LUN 0

LUN 1HBA 0

HBA 1

Lun 0

Controller 0

Controller 1

0 0 0 0 1 0 1 0 0 1 1 0

HBA Target Lun

LUN 2

LUN 3

Lun 0Lun 0

Lun 0

Lun 1Lun 1

Lun 1Lun 1

Lun 2Lun 2

Lun 2Lun 2

Lun 3Lun 3

Lun 3Lun 3

0 0 1 0 1 1 1 0 1 1 1 1

0 0 2 0 1 2 1 0 2 1 1 2

0 0 3 0 1 3 1 0 3 1 1 3

When multiple paths are available, IPStor will evenly distribute the load-independent paths among the LUN’s.

Default Path

Default Path

Default Path

Default Path


Multipathing

Path managementFrom the DF2112 console, you can configure active paths automatically using the Autopathing feature or manually by defining each LUN’s Alias List.

Changes to the active path configuration become effective immediately, but are not saved permanently until you use the System Preferred Path --> Save option. If you do not use the Save option and the DF2112 server is restarted, the saved System Preferred paths are restored and activated.

The saved System Preferred paths can be restored anytime. Restoring means all active paths are reset back to the last saved system preferred paths.

You can see multipathing information from the console by checking the Alias tab for a LUN (under Fibre Channel Devices). For each device, you see the following:

• Current or standby path• Active vs. passive path - A passive path cannot be used until the LUN is

trespassed, meaning the passive path becomes active and the formally-active path becomes passive.

• Current connectivity status• Preferred path


Multipathing

Set autopathingAutopathing will automatically determine the paths to use based on criteria you set in the configuration wizard.

Autopathing assigns optimized paths to each LUN, utilizing the available bandwidth provided by these load-independent paths in an evenly distributed manner, therefore optimizing the system throughput.

Autopathing is dependent upon the proper persistent binding of physical resources. If new storage device(s) have recently been added to the DF2112 server, you must make sure the HBAs have been reloaded, which sets persistent binding for the device. You can reload HBAs by restarting DF2112 with the df2112 restart all command.

1. Right-click on the Fibre Channel Devices object and select Autopath.

2. Select the multipathing method you want to use.

Storage Preferred - Detects and follows the preferred paths for each LUN as they are set by the storage controller on supported systems and uses them as DF2112’s preferred paths. If the storage controller does not have a storage preferred path, DF2112 uses the Active Path. This can cause paths to trespass (switch) unless you also select the sub-option.

Use active path for devices that do not support the Storage Preferred concept - For storage controllers that do not have storage preferred paths. If you select this sub-option, DF2112 will not trigger paths to trespass.

Active Path - DF2112 determines the currently active paths and uses them.


Multipathing

No Preference - DF2112 balances across all available independent paths. This can cause paths to trespass.

3. Select any adapter(s) you want to exclude.

Any adapter you select will not be included in the multipathing calculation. You may need to do this if you have a specific path that you want to maintain. In that case, you would exclude the adapter, SCSI ID, and LUN for that path. You can also do this if you have a single adapter that you do not want used for load distribution.

4. Select any SCSI IDs (ports) to exclude.

5. Select any LUNs to exclude.


The path configuration becomes effective immediately, but is not saved permanently. If you are satisfied with the multipathing results, you should now save them. To do this, right-click on the Fibre Channel Devices object and select System Preferred Path --> Save.

If you want to tweak the active paths, you can manually configure them by defining each LUN’s Alias List. Refer to the next section for more details.


Multipathing

Set alias listThis feature lets you manually configure the active paths for each LUN. When a currently active path becomes unavailable, DF2112 automatically switches to the next available alternate path as defined in the LUN’s Alias list.

1. Right-click on a Fibre Channel LUN and select Alias.

2. Highlight any path and then use the up and down arrow keys to change the priority order.

3. Click OK when done.

Changes to the active path configuration become effective immediately, but are not saved permanently until you use the System Preferred Path --> Save option. If you do not use the Save option and the DF2112 server is restarted, the saved System Preferred paths will be restored and activated.


Multipathing

Unbind physical devices from SCSI aliasesYou can unbind physical devices from their SCSI aliases.

You can unbind any unassigned resource, any service-enabled device, or any direct device. A device reserved for use as a virtual storage can not be un-bound. If you virtualize an unbound resource, upon a rescan of the physical resources, the device will be rebound.

To unbind:

1. Right-click on a device and select Unbind.

For multiple devices, you can right-click on Physical Resources and select Unbind.

2. Select the aliases to unbind and click OK.


DF2112 User Guide

SNMP IntegrationIn addition to the DF2112 Console that provides end-to-end management of your system, DF2112 provides SNMP support to integrate DF2112 management into an existing enterprise management solution such as HP OpenView, CA Unicenter, IBM Tivoli NetView, and BMC Patrol.

DF2112 uses a MIB (Management Information Base) to determine what data can be monitored. The following are the three major areas of management:

• Accounting management (including discovery)Locates all DF2112 Servers and Windows clients. It shows how all the resources are aggregated, virtualized, and provisioned, including the number of adapters, physical devices, and virtual devices attached to a Server. Most of the information comes from DF2112’s configuration file (df2112.conf).

• Performance management (including statistics)Shows information about your DF2112 Servers and Clients, including the number of Clients being serviced by a Server, Server memory used, CPU load, and the total KB transferred. Most of the information comes from the /proc/df2112 directory on the Servers or the Client Monitor on the Clients. For more information about each of the statistics, please refer to the DF2112-MIB.txt file that is in the Server’s /usr/local/df2112/etc/snmp/mibs directory.

• Fault managementThis allows a trap to be generated when certain conditions occur.

Traps

The following processDownTrap traps are currently defined and are triggered when a DF2112 component is down.

DF2112 Component Description

sanidmgr Responsible for Client authentication to SAN Resources. Controls whether Clients will be able to access SAN Resources.

df2112comm Allows the Console to access the Servers.

df2112log Provides the logging function for DF2112 reports.

df2112sm DF2112’s self-monitoring module.

kdf2112 Manages I/O between Clients and storage devices.

krudp Manages communication between Servers and Clients.


SNMP Integration

DF2112 EventLog messages

In addition to the processDownTrap traps, DF2112 Event Log messages can be sent to your SNMP manager. By default, Event Log messages (informational, warnings, errors, and critical errors) will not be sent. From the DF2112 Console, you can determine which type of messages should be sent. To select the Trap level:

1. Right-click on the server and select Properties --> SNMP Maintenance --> Trap Level.

2. After selecting a Trap Level, click Add to enter the name of the server receiving the traps (or IP address if the name is not resolvable), and a Community name.

Five levels are available:• None – (Default) No messages will be sent.• Critical - Only critical errors that stop the system from operating properly

will be sent.• Error – Errors (failure such as a resource is not available or an operation

has failed) and critical errors will be sent. • Warning – Warnings (something occurred that may require maintenance or

corrective action), errors, and critical errors will be sent.• Informational – Informational messages, errors, warnings, and critical error

messages will be sent.

Implement SNMP support

The DF2112 SNMP software is installed on the Server and Windows clients during the DF2112 installation.

Note: DF2112 installs an SNMP module that stops the native SNMP agent on the DF2112 Server. The DF2112 SNMP module is customized for use with your SNMP manager. If you do not want to use the DF2112 SNMP module, you can stop it by executing: ./df2112 stop snmpd. However, the next time the server is rebooted, it will start again. Contact technical support if you do not want it to restart on boot up.

To complete the implementation, you must install software on your SNMP manager machine and then configure the manager to support DF2112.

Since this process is different for each SNMP manager, please refer to the appropriate section below.

df2112smbddf2112nmbddf2112nassmgtdportmapnfsdrpc.mounteddf2112clntdredirector

Specific to NAS. These components are required for NAS and can only be monitored if NAS is enabled.

DF2112 Component Description


SNMP Integration

HP OpenView Network Node Manager 6.1 and 6.2

Installation

The DF2112 installation CD includes software that must be installed on your HP OpenView Network Node Manager (NNM) machine. This software adds several DF2112 menu options into your NNM and adds a DF2112 MIB tree so that you can set traps.


If autorun is enabled for your CD-ROM drive, the CD Browser will launch and allow you to select the programs to install.

2. Select Install Products --> Install SNMP for HP OpenView.

If the CD Browser does not launch, navigate to the \SNMP\OpenView directory and run setup.exe to launch the SNMP install program.

3. Start the NNM when the installation is finished.

Under the Tools menu you will see a new DF2112 menu option.


SNMP Integration

Configuration

You need to define which hosts will receive traps from your DF2112 Server(s) and determine which DF2112 components to monitor. To do this:

1. In the NNM, highlight a DF2112 Server and select Tools --> SNMP MIB Browser.

2. In the tree, expand private --> enterprises --> df2112 --> df2112Server --> trapReg and highlight trapSinkSettingTable.

The default read-only community is “public”. The default read-write community is “falcon”.• Set the Community name to "falcon" so that you will be allowed to change

the configuration.• Click the Start Query button to query the configuration.• From the MIB values field, select a host to receive traps. You can set up to

five hosts to receive traps. If the value is ‘0’, the host is invalid or not set.• In the SNMP set value field, enter the IP address or machine name of the

host that will receive traps.• Click the Set button to save the configuration in snmpd.conf.

3. In the SNMP MIB Browser, select private --> enterprises --> df2112 --> df2112Server --> alarmTable.• Click the Start Query button to query the alarms.• In the MIB values field, select which DF2112 components to monitor. You

will be notified any time the component goes down. A description of each is listed in the ‘Traps’ section.

• In the SNMP set value field, enter ‘enable’ or ‘1’ to enable.• Click the Set button to enable the trap you selected.

Statistics in NNM

In addition to monitoring DF2112 components and receiving alerts, you can view DF2112 statistics in NNM. There are two ways to do this:

DF2112 menu 1. Highlight a DF2112 Server or Client and select Tools --> DF2112.

2. Select the appropriate menu option.

These reports are provided by DF2112 as a convenient way to view statistical information without having to go through the MIB browser.

You can add your own reports to the menu by selecting Options --> MIB Application Builder: SNMP. Refer to OpenView’s documentation for details on using the MIB Application Builder.


SNMP Integration

MIB browser 1. Highlight a DF2112 Server or Client and select Tools --> SNMP MIB Browser.

2. In the tree, expand private --> enterprises --> df2112 --> df2112Server.

If this is a Client, select df2112Client.From here you can view information about this DF2112 Server. If you run a query at the df2112Server level, you will get a superset of all of the information from all of the sub-categories.

For more specific information, expand the sub-categories.

For more information about each of the statistics, you can click the Describe button or refer to the DF2112-MIB.txt file that is in your \\OpenView\snmp_mibs directory.


SNMP Integration

CA Unicenter TNG 2.2

Installation

The DF2112 installation CD includes software that must be installed on your CA Unicenter TNG 2.2 machine. This software creates a DF2112SNMP class in Unicenter and adds a DF2112 MIB tree so that you can set traps.



2. Select Install Products --> Install SNMP for CA Unicenter.

If the CD Browser does not launch, navigate to the \SNMP\Unicenter directory and run setup.exe to launch the SNMP install program.

Configuration


1. Run Unicenter’s Auto Discovery.

If you have a repository with existing machines and then you install the DF2112 Server software, Unicenter will not automatically re-classify the machine and mark it as a DF2112 Server.

2. If you need to re-classify a machine, open the Unicenter TNG map, highlight the machine, select Reclassify Object, select Host --> DF2112 SNMP and then change the Alarmset Name to DF2112Alarm.

If you want to re-align the objects on the map after re-classification, select Modes --> Design --> Folder --> Arrange Objects and then the appropriate network setting.

3. Restart the Unicenter TNG map.

4. To define hosts, right-click on DF2112 Server --> Object View.

5. Click Object View, select Configure Toolbar, set the Get Community and Set Community to falcon, and set the Model to df2112.mib.

falcon is the default community name (password). If it was changed in the snmpd.conf file (on the DF2112 Server), enter the appropriate community name here.

6. Expand Vendor Information and highlight trapSinkSettingEntry.

7. To define a host to receive traps, highlight the trHost field of an un-defined host, right-click and select Attribute Set.


SNMP Integration

You can set up to five hosts to receive traps.

8. In the New Value field, enter the IP address or machine name of the host that will receive traps (such as your Unicenter TNG server).

Your screen will now show that machine.

9. Highlight alarmEntry.

10. Highlight the alarmStatus field for a component, right click and select Attribute Set.

11. Set the value to enable for on or disable for off.

View traps

1. From your Start --> Programs menu, select Unicenter TNG --> Enterprise Management --> Enterprise Managers.

2. Double-click on the Unicenter machine.

3. Double-click on Event.

4. Double-click on Console Logs.

Statistics in TNG

You can view statistics about DF2112 directly from the ObjectView screen.

To do this, highlight a category in the tree and the DF2112 information will be displayed in the right pane.

Launch the DF2112 Console

If the DF2112 Console is installed on your Unicenter TNG machine, you can launch it directly from the Unicenter map by right-clicking on a DF2112 Server and selecting Launch DF2112 Console.


SNMP Integration

IBM Tivoli NetView 6.0.1

Installation

The DF2112 installation CD includes software that must be installed on your Tivoli NetView machine. This software adds several DF2112 menu options into NetView and adds a DF2112 MIB tree so that you can set traps.



2. Select Install Products --> Install SNMP for IBM Tivoli.

If the CD Browser does not launch, navigate to the \SNMP\Tivoli directory and run setup.exe to launch the SNMP install program.

3. Start NetView when the installation is finished.

You will see a new DF2112 menu option on NetView’s main menu.


SNMP Integration

Configuration

You need to define which hosts will receive traps from your DF2112 Server(s). To do this:

1. In NetView, highlight a DF2112 Server on the map and click the Browse MIBs button.

2. In the tree, expand enterprises --> df2112 --> df2112Server --> trapReg --> trapSinkSettingTable --> trHost.

The default read-only community is “public”. The default read-write community is “falcon”.

3. Set the Community Name so that you will be allowed to change the configuration.

4. Click the Get Values button.

5. Select a host to receive traps. You can set up to five hosts to receive traps. If the value is ‘0’, the host is invalid or not set.

6. In the New Value field, enter the IP address or machine name of the Tivoli host that will receive traps.

7. Click the Set button to save the configuration in snmpd.conf.


SNMP Integration

Statistics in Tivoli

In addition to monitoring DF2112 components and receiving alerts, you can view DF2112 statistics in NetView. There are two ways to do this:

DF2112 menu 1. Highlight a DF2112 Server or Client and select DF2112 from the menu.

2. Select the appropriate menu option.

For a Server, you can view:• Memory used• CPU load• SCSI commands• KB read/written• Read/write errors

For a Client, you can view:• SCSI commands• Error report


You can add your own reports to the menu by using NetView’s MIB builder. Refer to NetView’s documentation for details on using the MIB builder.

MIB browser 1. Highlight a DF2112 Server or Client and click Tools --> MIB --> Browser.

2. In the tree, expand private --> enterprises --> df2112 --> df2112Server.

If this is a Client, select df2112Client.

3. Select a category.

4. Click the Get Values button.

The information is displayed in the bottom section of the dialog.


SNMP Integration

BMC Patrol 3.4.0

Installation

The DF2112 installation CD includes software that must be installed on your BMC Patrol machine. This software adds several DF2112 icon options into Patrol and adds several DF2112 MIB items so that you can retrieve information and set traps.



2. Select Install Products --> Install SNMP for BMC Patrol.

If the CD Browser does not launch, navigate to the \SNMP\Patrol directory and run setup.exe to launch the SNMP install program.

3. Start Patrol when the installation is finished.

4. Click Hosts --> Add on the Patrol main menu and enter the Host Name (IP preferred), Username (Patrol administrator name of the DF2112 Server), Password (Patrol administrator password of the DF2112 Server), and Verify Password fields to add the DF2112 Server machine.

5. Click Hosts --> Add on the Patrol main menu and input the Host Name, Username (administrator name of the Patrol machine), Password (administrator password of the Patrol machine), and Verify Password fields to add the Patrol Console machine.

6. Click File --> Load KM on the Patrol main menu and load the DF2112_MODULE.kml module.

7. Click File --> Commit KM --> To All Connected Hosts on the Patrol main menu to send changed knowledge (DF2112_MODULE.kml) to all connected agents, including the DF2112 Server machine and Patrol Console machine.

8. Expand the DF2112 Server machine tree.

You will see three new DF2112 sub-trees with several icons on the Patrol console.

Configuration


1. In the Patrol Console, on the Desktop tab, right-click the ServerInfo item in the IPS_Server subtree of one DF2112 Server and select KM Commands --> trapReg --> trapSinkSettingEntry.


SNMP Integration

The default read-only community is “public”. The default read-write community is “falcon”.

2. Select a host to receive traps. You can set up to five hosts to receive traps. If the value is '0', the host is invalid or not set.

3. In the Host fields, enter the IP address or machine name of the host that will receive traps.

4. In the Community fields, enter the community.

5. Click the Set button to save the configuration in snmpd.conf.

6. In the Patrol Console, on the Desktop tab, right-click the ServerInfo item in the IPS_Server subtree of one DF2112 Server and select KM Commands --> alarmTable --> alarmEntry.

Set the status value to enable(1) for on or disable(0) for off.

View traps

1. In the Patrol Console, on the Desktop tab, right-click the IPS_Trap_Receiver --> SNMPTrap_Receiver of the Patrol Console machine and select KM Commands --> Start Trap Receiver to let the Patrol Console machine start receiving traps.

2. After turning the trap receiver on, you can double-click the SNMP_Traps icon in the SNMPTrap_Receiver subtree of the Patrol Console machine to get the results of the traps that have been received.

Statistics in Patrol

In addition to monitoring DF2112 components and receiving alerts, you can view DF2112 Server statistics in Patrol. There are two ways to do this:

DF2112 icon 1. Highlight a DF2112 Server and totally expand the IPS_ProcessMonitor subtree and the IPS_Server subtree from the DF2112 Server.

2. Select the appropriate icon option.

For a Server, you can view:

- Processes Status (Authentication Process, Communication Process, Logger Process, SelfMonitor Process, SNMPD Process, etc.).

To monitor more processes, you can change to KM tab on the Patrol Console and right-click one process from Knowledge Module --> Application Classes --> IPS_ProcessMonitor --> Global --> Parameters and click the Properties item on the menu. You can check the “Active” option to let the specified process to be monitored. After, change to Desktop tab and you can see the specified process is visible in the IPS_ProcessMonitor subtree.

- Server Status (ipsLaAvailLoad, ipsMemAvailSwap and ipsMemAvaiReal)


SNMP Integration


MIB browser 1. Highlight a DF2112 Server and right-click ServerInfor from IPS_Server subtree and select KM commands.

In KM commands, several DF2112 integrated MIB items are inside.

2. Click one of the MIB items to retrieve the information related to the DF2112 Server.


SNMP Integration

Advanced topics

This information applies to all SNMP managers.

The snmpd.conf file

The snmpd.conf file is located in the /usr/local/df2112/etc/snmp directory of the DF2112 Server and contains SNMP configuration information, including the DF2112 community name and the network over which you are permitted to use SNMP (the default is the network where your DF2112 Server is located).

If your SNMP manager resides on a different network, you will have to modify the snmpd.conf file before you can implement SNMP support through your SNMP manager.

In addition, you can modify this file if you want to limit SNMP communication to a specific subnet or change the community name. The default read-write community is “falcon”. This is the only community you should change.

Note: If you modify the snmpd.conf file you will need to restart your DF2112 Server in order for the change to take effect.

Use an SNMP configuration for multiple DF2112 Servers

To re-use your SNMP configuration for multiple DF2112 Servers, go to /usr/local/df2112/etc/snmp and copy the following files to the same directory on each DF2112 Server.

• snmpd.conf - contains trapSinkSettings• DF2112SNMP.conf - contains trapSettings

Note: In order for the configuration to take effect, you must restart the SNMPD module on each DF2112 Server to which you copied these files.


DF2112 User Guide

Command Line InterfaceThe Command Line Interface (CLI) is a simple interface that allows client machines to perform some of the more common functions currently performed by the DF2112 Console. Administrators can use the CLI to automate many tasks, as well as integrate DF2112 with their existing management tools.

Installation and configurationThe CLI is installed as part of the DF2112 Client installation. Once installed, a path must be set up for Windows clients in order to be able to use the CLI. The path can be set up from the Windows Desktop by doing following:

1. Right-click My Computer and select Properties --> Advanced tab --> Environment Variables button.

2. Highlight the Path variable in the System Variables box, click the Edit button and add the following to the end of the existing path. ;c:\Program Files\MPC\DF2112\Client

3. Click OK to save and exit.

For Linux, Solaris, AIX, and HP-UX clients, the path is automatically set during the Client installation. In order to use the CLI, Linux, Solaris, AIX, and HP-UX client users must have exited the current shell to set the new environment at least once after installing the client software.

Using the CLINote: You should not have a Console connected to your DF2112 server when you run CLI commands; you may see errors in the syslog if a Console is connected.

Type iscli at a command line to display a list of the existing commands.

For example: c:\iscli

These commands must be combined with the appropriate long or short arguments (ex. Long: --server-name servername Short: -s servername).

If you type the command name (for example, c:\iscli getvdevlist), a list of arguments will be displayed for that command.


Command Line Interface

Common argumentsThe following arguments are used throughout the CLI. For each, a long and short variation is included. You can use either one. The short arguments ARE case sensitive. For arguments that are specific to each command, refer to the section for that command.

Note: You only need to use the --server-username (-u) and --server-password (-p) arguments when you log into a server. You do not need them for subsequent commands on the same server during your current session.

Short Argument Long Argument Value/Description

-s --server-name DF2112 Server Name (hostname or IP address). In order to use the hostname, the server name has to be resolvable on the client side and server side.

-u --server-username DF2112 Server Username

-p --server-password DF2112 Server User Password

-S --target-name DF2112 Target Server Name (hostname or IP address)

-U --target-username DF2112 Target Server Username (for replication commands)

-P --target-password DF2112 Target Server User Password (for replication commands)

-c --client-name DF2112 Client Name

-v --vdevid DF2112 Virtual Device ID

-v --source-vdevid DF2112 Source Virtual Device ID

-V --target-vdevid DF2112 Target Virtual Device ID

-a --access-mode Client Access Mode to Virtual Device

-f --force Force the deletion of the virtual device

-n --vdevname Virtual device name

-X <rpc-timeout> --rpc-timeout=<rpc-timeout> Specify a number between 1 and 30000 seconds for the RPC timeout. The default is 30 seconds if not specified.



Commands

Below is a list of commands you can use to perform DF2112 functions from the command line. You should be aware of the following as you enter commands:

• Type each command on a single line, separating arguments with a space.• You can use either the short or long arguments (as described above).• Variables are listed in <> after each argument. • Arguments listed in brackets [ ] are optional.• The order of the arguments is irrelevant.• Arguments separated by | are choices. Only one can be selected.• For a value entered as a literal, it is necessary to enclose the value in

quotes (double or single) if it contains special characters such as *, <, >, ?, |, %, $, or space. Otherwise, the system will interpret the characters with a special meaning before it is passed to the command.

• Literals cannot contain leading or trailing spaces. Leading or trailing spaces enclosed in quotes will be removed before the command is processed.

• In order to use the hostname of the DF2112 Server instead of its IP address, the server name has to be resolvable on the client side and server side.

Login/logout to the DF2112 Server

Log in to the DF2112 Server

iscli login [-s <server-name> -u <user-name> -p <password>|-e] [-X <rpc-timeout>]

iscli login [--server-name=<server-name> --server-username=<user-name> --server-password=<password>|--environment] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to log into the specified DF2112 Server with a given username and password. Once successfully logged into the server, -u (--server-username) and –p (--server-password) are not necessary for the other CLI commands with optional –u and –p arguments. If you do not specify any parameters with this command, you will be prompted for a server name, user name, and password.

In order to use the -e (--environment) parameter, you must set the following three environment variables:

• ISSERVERNAME• ISUSERNAME• ISPASSWORD

After setting these variables, the environment parameter can be used in the login command in place of -s <server-name> -u <user-name> -p <password>. Therefore, you could type the following to log in: iscli login -e

To set these environment variables in the bash shell, you must set three variables as follows:

• export ISSERVERNAME=10.1.1.1



• export ISUSERNAME=root• export ISPASSWORD=password

To set these environment variables on a Windows machine, you must right-click My Computer and select Properties --> Advanced tab --> Environment Variables button. Add three new user variables as follows:

• ISSERVERNAME=10.1.1.1• ISUSERNAME=root• ISPASSWORD=password

Log out from the DF2112 Server

iscli logout -s <server-name> [-X <rpc-timeout>]

iscli logout --server-name=<server-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to log out from the specified DF2112 Server. If the server was not logged in or you have already logged out from the server when this command is issued, error 0x0902000f will be returned. After logging out from the server, the -u and –p arguments will not be optional for the server commands.



Server commands for virtual devices and clientsCreate virtual device

iscli createvdev -s <server-name> [-u <username> -p <password>] [-C <category>] [-R <resource-type>] [-F <file-system> [-b <block-size>] [-i <io-mode>] [-j <journal-mode>] [-N]] [-n <vdevname>] [[-m <#(MB)>|-r <sectors>|-l <lun-type>][-I <ACSL>[-sp <storage-pool-id>|-SP <storage-pool-name>]| -sp <storage-pool-id>|-SP <storage-pool-name>]| -M <custom-mode>|-L <custom-layout>] [-q][-W [-c [-a <date-time>]] [-T] [-h <on|off>] [-t <cdp-coverage-period>] [-k <lock-policy>] [-d <on|off>]] [-f] [-X <rpc-timeout>]

iscli createvdev --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--category=<category>][--resource-type=<resource-type>] [--file-system=<file-system> [--block-size=<block-size>] [--io-mode=<io-mode>] [--journal-mode=<journal-mode>][--no-logging]] [--vdevname=<vdevname>] [[--size-mb=<#(MB)>|--sectors=<sectors>|--lun-type=<lun-type>] [--scsiaddress=<ACSL> [--storage-pool-id=<storage-pool-id>|--storage-pool-name=<storage-pool-name>]| --storage-pool-id=<storage-pool-id>|--storage-pool-name=<storage-pool-name>]| --custom-method=<custom-mode>|--custom-layout=<custom-layout>] [--reserve-inquiry-string] [--enable-worm[--use-compliance-clock [--set-compliance-time=<date-time>]] [--use-last-access-time][--lock-file-with-hash=<on|off>] [--retention-period=<retention-period>][--lock-file-policy=<lock-policy>] [--delete-after-retention=<on|off>]][--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to create a SAN or NAS Resource on the specified server. A SAN Resource can be created in one of three categories: virtual, service-enabled, or direct. The default category is virtual if the category is not specified. A NAS Resource can only be created as a virtual device.

Use the -q (--reserve-inquiry-string) option for service-enabled devices to reserve the physical device inquiry string.

<resource-type> is one of the values:

• SAN (default)• NAS

Additional options can be specified for the NAS file system. The default file system type will be determined by the NAS configuration.

<file-system> is one of the following values:

• EXT2• EXT3• XFS

<block-size> is in KB. It is 1, 2, 4 for EXT2 and EXT3. It is 4 for XFS.

<io-mode> is one of the following values:

• async (default)• sync

<journal-mode> is one of the following values when the <file-system> is EXT3:



• journal• ordered (default)• writeback

-m (--size-mb) is the size in MB. -r (--sectors) is the size in sectors. If neither option is specified, the total available space will be allocated. The minimum size for NAS resource is 8MB. The minimum size for SAN resources is 1MB.

Use the -n (--vdevname) option to specify the virtual device name. The maximum length is 64. Leading and trailing spaces will be removed. Enclose the name in double quotes to ensure the proper name.

The following characters are invalid for the SAN Resource name: <>"&$/\'

The following characters are invalid for the NAS Resource name: <>"&$/\'():;|*?`

-I (--scsiaddress) is required for direct devices and service enabled devices, but it is an option for a virtual devices to specify a specific physical device to allocate the space. ACSL=#:#:#:# (adapter:channel:id:lun)

-sp (storage-pool-id) or -SP (storage-pool-name) can be specified to allocate the space from the physical devices in the storage pool for the virtual device when the -I option is not specified. Or, it can be specified for the virtual header of service enabled devices.

The <custom-mode> and <custom-layout> options are for specific physical segments. It can be a list or a file enclosed in <> containing physical segment in each line. The format of the physical segment for <custom-mode> is: adapter:channel:scsi-id:lun:first-sector:size-in-MB

The format for <custom-layout> is: adapter:channel:scsi-id:lun:first-sector:last-sector

You can use the -W (--enable-worm) option for NAS resource. The feature is only supported by XFS file systems. The following WORM policies can be set when WORMLock is enabled.

Use the -a (--set-compliance-time) option to specify a date/time to be used as a compliance time instead of the server system time when -c (--use-compliance-clock) is specified. The compliance time can only be specified once and cannot be modified.

If the server is configured as failover server, the compliance clock will be set for the failover partner server as well.

-T (--use-last-access-time) can be specified to use the last access time instead of the modified time for file expiration time calculation. This option cannot be modified afterward. <retention-period> and <lock-policy> cannot be specified when this option is specified.

<retention-period> can be specified in the format of <duration><unit> where the unit and range for each unit are as follows:

• Y: (Y)ears (duration range: 1-60)• N: mo(N)ths (duration range: 1-11)• D: (D)ays (duration range: 1-29)• H: (H)ours (duration range: 1-23)• M: (M)inutes (duration range: 1-59)

For example: 1Y, 4N

If the retention period is unlimited, specify 0 without any unit, which is the default if not specified.

<lock-policy> can be specified to lock the files automatically in the format of <interval><unit>-<start-time> where the unit and valid intervals for each unit are as follows:



• H: (H)ours (intervals: 1,2,3,4,6,8,12,24)• M: (M)inutes (intervals: 1,2,3,4,5,6,10,12,15,20,30)

The range of the <start-time> is between 0 and the specified interval minus 1. For example: 2H-0, 2H-1, 15M-0, 15M-14

Use the -h (--lock-file-with-hash) option to set a digital signature to each locked file in one of the values:

• on• off (default)

Use the -d (--delete-after-retention) option to unlock and delete files automatically after the retention period expired in one of the values:


If the server supports Emulex Target Mode, the -l (--lun-type) option can be specified with one of the following Types to create the virtual disk for an AS400 client.

This option cannot be specified with -m, -I, -M option.

Use the -X (--rpc-timeout) option to specify a number between 1 and 30000 in seconds for the RPC timeout. The default RPC timeout is 30 seconds if it is not specified.

Type Type AS400 Disk Size Actual Disk Size

1 2105 A01 (DPY) 8.589 GB 9000 MB

2 2105 A02 (DPY) 17.548 GB 18000 MB

5 2105 A05 (DPY) 35.165 GB 36000 MB

3 2105 A03 (DPY) 36.003 GB 37000 MB

4 2105 A04 (DPY) 70.564 GB 71000 MB

81 2105 A01 8.589 GB 9000 MB

82 2105 A02 17.548 GB 18000 MB

85 2105 A05 35.165 GB 36000 MB

83 2105 A03 36.003 GB 37000 MB

84 2105 A04 70.564 GB 71000 MB



Get virtual device listiscli getvdevlist -s <server-name> [-u <username> -p <password>] [-l [-v <vdevid> | -n <vdevname>] [-a|-A][-c|-C]] [-X <rpc-timeout>]

iscli getvdevlist --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--longlist [--vdevid=<vdevid> | --vdevname=<vdevname>] [--client-list|--long-client-list] [--physical-layout|--long-physical-layout]] [--rpc-timeout=<rpc-timeout>]

Description:

This command retrieves and displays information about all virtual devices or a specific virtual device from the specified server.

Use the -l(--longlist) option to display the long format.

Use the -v(--vdevid) or -n(--vdevname) option to display only the specified virtual device information when -l(--longlist) is specified.

Use the -a(--physical-layout) or -A(--long-physical-layout) option to display the physical layout when -l(--longlist) is specified.

Use the -c(--client-list) or -C(--long-client-list) option to display the assigned client list when -l(--longlist) option is specified.


Get client virtual device listiscli getclientvdevlist -s <server-name> [-u <username> -p <password>]-c <client-name> [-t <client-type>] [-l[-a|-A]] [-T] [-X <rpc-timeout>]

iscli getclientvdevlist --server-name=<server-name> [--server-username=<username> --server-password=<password>] --client-name=<client-name>[--client-type=<client-type>] [--longlist[--physical-layout|--long-physical-layout]][--iscsi-target-list] [--rpc-timeout=<rpc-timeout>]

Description:

This command retrieves and displays information about all virtual devices assigned to the client from the specified server.

<client-name> is the name of the SAN client, or * for all the clients.

<client-type> is the type of the client protocol to be retrieved with one of the following values:

• SANIP• FC• ISCSI

The client name is required, but the client type is optional. If the client type is not specified, all of the supported client protocols will be included.

Be aware that on some platforms you are required to enclose the "*" in double quotes to take it as a literal.



Use the -l(--longlist) option to display the long format.

Use the -a(--physical-layout) or -A(--long-physical-layout) option to display the physical layout when -l(--longlist) is specified.

-T (--iscsi-target-list) is an additional option for the iSCSI protocol when <client-type> is specified as ISCSI to display the assigned devices in iSCSI target and virtual devices hierarchy.


Assign virtual device

iscli assignvdev -s <server-name> [-u <username> -p <password>] -v <vdevid> | -g <group-id> | -G <group-name> -r <iscsi-target-id> | -R <iscsi-target-name> -c <client-name> -a <access-mode> [-t <adapter-no> -d <scsi-id> -l <lun>][-I <initiatorWWPN|*>] [-T <targetWWPN|*>] [-l <lun>] [-L <client-protocol>] [-X <rpc-timeout>]

iscli assignvdev --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> --group-id=<group-id> | --group-name=<group-name> --iscsi-target-id=<iscsi-target-id> | --iscsi-target-name=<iscsi-target-name> --client-name=<client-name> --access-mode=<access-mode> [--adapter-no=<adapter-no> --scsi-id=<scsi-id> --lun=lun][--initiatorWWPN=<initiatorWWPN|*>] [--targetWWPN=<targetWWPN|*>] [--lun=<lun>]--client-protocol=<client-protocol> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to assign a virtual device on a specified server to a SAN client or group.

If the client supports more one protocol, the protocol can be specified with -L (--client-protocol) option with one of the values: SANIP, FC, or ISCSI. If this option is not specified, a default protocol will be chosen from the configured client protocols in the following order: SANIP, FC, ISCSI.

Virtual device and group (ID or name) can be specified for all the protocols. iSCSI target (ID or name) is an additional option for iSCSI protocol assignment.

Specify iSCSI target ID or name if the iSCSI target is to be assigned for iSCSI protocol. Specify virtual device ID if the virtual device is not in a group. Specify group ID or group name to assign the virtual devices that are in a group to the client. All the virtual devices in the same group will be assigned to the client. The values for <access-mode> are: Readonly, ReadWrite, ReadWriteNonExclusive. The values for the short format are: R / W / N.

<adapter-no>, <scsi-id> and <lun> can be specified for a SAN/IP protocol assignment.

InitiatorWWPN and TargetWWPN are options for the Fibre Channel Client. The initiatorWWPN or targetWWPN is a 16-byte hex value or * for all. For example, 13af35d2f4ea6fbc. The default is * if it is -I or -T option or is not specified.

<lun> can be specified for Fibre Channel protocol. It can also be specified for iSCSI protocol if it is not for an iSCSI target assignment.



Unassign virtual device

iscli unassignvdev -s <server-name> [-u <username> -p <password>] -v <vdevid> | -r <iscsi-target-id> | -R <iscsi-target-name> -c <client-name> [-f] [-X <rpc-timeout>]

iscli unassignvdev --server-name=<server-name> [--server-username=<username>] [--server-password=<password>] --vdevid=<vdevid> | --iscsi-target-id=<iscsi-target-id> | --iscsi-target-name=<iscsi-target-name> --client-name=<client-name> [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to unassign a virtual device on the specified server from a SAN client. If the client is an iSCSI client, iSCSI target should be specified. Otherwise, virtual device should be specified.

-f (--force) option can be specified when the virtual device is in a group. An error will be returned when the force option is not specified to unassign a virtual device that is in a group.

-f (--force) option is also required to unassign the virtual device when the client is connected and the virtual device is attached. An error will be returned if the force option is not specified.

Delete virtual device

iscli deletevdev -s <server-name> [-u <username> -p <password>] -v <vdevid> [-f] [-X <rpc-timeout>]

iscli deletevdev --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to delete a SAN or NAS Resource, or a SAN or NAS TimeView Resource on the specified server. If the resource is assigned to a SAN client, the assignment(s) will be removed first. If a Snapshot Resource is created for the virtual device, it will be removed.

The resource cannot be deleted if one of the following conditions applies:

• The resource is a SAN resource and SAN clients are currently connected and attached to the resource.• The resource is a replica disk.• There are TimeView resources associated with this resource.

The force option is required to delete the resource if any of the following conditions applies:

• The resource is in a group.• The resource is a primary replication disk.• The virtual device is a snapshot copy source device or a snapshot copy target device and the snapshot

copy is still in progress.• The Backup option is enabled.• The TimeMark option is enabled.• The resource is a TimeMark copy source device or TimeMark copy target device and the TimeMark copy

is still in progress.• A TimeMark rollback is in progress for this virtual device.

When the resource is a primary replication disk and the force option is specified, the replica will be promoted if it is in a valid state. Otherwise, it will be deleted.



Expand virtual device

iscli expandvdev -s <server-name> [-u <username> -p <password>] -v <vdevid> -m <#(MB)>[-U <target-username> -P <target-password>] [-b] [--target-username=<target username> --target-password=<target password>] [-b] [-X <rpc-timeout>]

iscli expandvdev --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> --additional-mb=<#(MB)> [--target-username=<target username> --target-password=<target password>] [--verbose][--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to expand the size of a virtual device on the specified server. Both SAN and NAS resources can be expanded but not a replica disk by itself or a TimeView resource.

If the virtual device is configured with a mirror, or is a primary replication disk, the mirror disk and the replica disk, with or without a mirror, will be expanded as well. The maximum size allowed for the expansion is the total size available on the specified server if there is no mirror configured for the virtual device. If a mirror disk is configured, only half of the total available size is allowed. If the virtual device is a primary replication disk, the total available size will be the smallest available size of the two servers.

When the virtual device is a primary replication disk, both the primary server and target server have to be connected in order for the expansion to proceed. If the username and password of the target server are not specified, the login information from the login command will be retrieved against the target server first. If the login information for the target server cannot be found, the username and password for the primary server will be used.

If the virtual device is not a primary replication disk, the –U (--target-username) and –P (target-password) will be ignored.

Different error conditions can be returned from either the local operations or the server options depending on the configuration of the virtual device. The most common error codes are for the availability of the physical devices and disk space on both the primary server and the target server:

0x09010002 There is not enough space available for allocation.0x09010004 There are no physical devices available for allocation.0x09010017 There are no physical devices available on the replication target server.0x09010018 There is not enough space available on the replication target server for allocation.

The maximum number of physical segments for a virtual device is 64. The following error codes can be returned before or during the expansion as the result of exceeding this limit:

0x0901003d Total number of physical segments of virtual device already reaches the maximum: 64.0x0901003e Total number of physical segments of the virtual device will exceed the maximum: 64 for the expansion.0x0901003f Total number of physical segments of mirror disk already reaches the maximum: 64.0x09010040 Total number of physical segments of the mirror disk will exceed the maximum: 64 for the expansion.0x09010041 Total number of physical segments of replica disk already reaches the maximum: 64.0x09010042 Total number of physical segments of the replica disk will exceed the maximum: 64 for the expansion.0x09010043 Total number of physical segments of replica mirror disk already reaches the maximum: 64.0x09010044 Total number of physical segments of the replica mirror disk will exceed the maximum: 64 for the expansion.



When the error is from a server operation, the error message will include the operation. For example:

Sync Mirror on Server: Cannot open file when trying to synchronize mirror for virtual device

Set assigned virtual device properties

iscli setassignedvdevprop -s <server-name> [-u <username> -p <password>] -v <vdevid>-c <client-name> | -r <iscsi-target-id> | -R <iscsi-target-name> [-t <adapter-no>] [-c <scsi-id>] [-l <lun>] [-I <initiatorWWPN|*>] [-T <targetWWPN|*>] [-X <rpc-timeout>]

iscli setassignedvdevprop --server-name=<server-name> [--server-username=<username>--server-password=<password>] --vdevid=<vdevid> --client-name=<client-name> |--iscsi-target-id=<iscsi-target-id> | --iscsi-target-name=<iscsi-target-name>[--adapter-no=<adapter-no>] [--scsi-id=<scsi-id>] [--lun=<lun>] [--targetWWPN=<targetWWPN|*>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to set properties for assigned virtual devices. Device properties can only be changed when the client is not connected.

Specify the iSCSI target ID or iSCSI target name if the virtual device is assigned to an iSCSI target. Specify the client name if the virtual device is assigned a Fibre Channel client. For a SAN/IP client, adapter, SCSI ID, and LUN can be specified. For a device assigned to an iSCSI target, the LUN can be changed.

For devices assigned to a Fibre Channel client, the initiator WWPN, target WWPN, and LUN can be changed.

Add client

iscli addclient -s <server-name> [-u <username> -p <password>] -c <client-name> [-t <client-type>] [[-A][-M -P <mobile-user-password>]] [-X <rpc-timeout>]

iscli addclient --server-name=<server-name> [--server-username=<username> --server-password=<password>] --client-name=<client-name> [--client-type=<client-type>] [[--enable-AS400] | [--mobile-client --mobile-user-password <mobile-user-password>]][--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to add a client to the specified server. Use the <client-type> option to specify the type of the client protocol to be supported by this client. The default client protocol is SANIP if it is not specified. <client-type> is one or more of the following values: SANIP, FC, and/or ISCSI. Separate the protocol by comma if more than one protocol is specified. The client name has to be unique on the specified server. The maximum length of the client name is 64. The following characters are invalid for a client name: <>\"&$/\\'

Use the -A (--enable-AS400) option with the Fibre Channel protocol to support an AS400 client.

Use the -M (--mobile-client) option with the ISCSI protocol. Mobile iSCSI clients can access the authorized iSCSI targets from any client as long as it has the proper authentication credentials. Mobile clients can only use their iSCSI user names as display names. -P (--mobile-user-password) is required for a mobile iSCSI client. The length of the password has to be between 12 and 16 characters.

You can only add a Fibre Channel or iSCSI client if that option is enabled on the specified server.



Delete client

iscli deleteclient -s <server-name> [-u <username> -p <password>] -c <client-name>[-X <rpc-timeout>]

iscli deleteclient --server-name=<server-name>[--server-username=<username> --server-password=<password>] --client-name=<client-name>[--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to delete a client. <client-name> is the client to be deleted.

Use the -f (--force) option to delete the client forcefully when any virtual device or iscsi target is assigned to the client.


Add client protocol

iscli enableclientprotocol -s <server-name> [-u <username> -p <password>]-c <client-name> [-t <client-type>] [-I <initiator-wwpn-list>] [-a <on|off>] [-A <on|off>] [-M -P <mobile-user-password> | [-i <initiator-list>] [-U <user-list>] ][-X <rpc-timeout>]

iscli enableclientprotocol --server-name=<server-name>[--server-username=<username> --server-password=<password>] --client-name=<client-name>[--client-type=<client-type>] [--initiator-wwpn-list=<initiator-wwpn-list>][--enable-VSA=<on|off>] [--enable-AS400=<on|off>] [--mobile-client --mobile-user-password=<mobile-user-password> | [--initiator-list=<initiator-list>] [--user-list=<user-list>] ] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to add a protocol to a client.

<client-name> is the name of client.

<client-type> is required to specify the additional client protocol to be supported by this client. It can have one or more of the following values:


Separate the protocols with commas if more than one protocol is specified.

You can use the -I (--initiator-wwpn-list), -a (--enable-VSA), and -A (--enable-AS400) options for Fibre Channel clients (client type is FC).

Use the -I (--initiator-wwpn-list) option to set initiator WWPNs. An initiator WWPN is a 16-byte Hex value. Separate initiator WWPNs with a comma if more than one is specified. For example: 13af35d2f4ea6fbc,13af35d2f4ea6fad

Use the -a (--enable-VSA) option for Volume Set Addressing with one of the following values:




Use the -A (--enable-AS400) option to support IBM iSeries Server with one of the following values:


This option cannot be set if this client is already assigned to virtual devices.

Use the -M (--mobile-client) option for the ISCSI protocol. A mobile iSCSI client can access the authorized iSCSI targets from any host as long as it has the proper authentication credentials. Mobile clients can only use their iSCSI user names as display names. -P (--mobile-user-password) is required for a mobile iSCSI client. The length of the password has to be between 12 and 16 characters.

Use the <user-list> and <initiator-list> options with the iSCSI protocol. They cannot be used with the -M option.

<user-list> is in the following format: user1,user2,user3

<initiator-list> is in the following format: initiator1,initiator2,initiator3


Disable client protocol

iscli disableclientprotocol -s <server-name> [-u <username> -p <password>]-c <client-name> [-t <client-type>] [-f] [-X <rpc-timeout>]

iscli disableclientprotocol --server-name=<server-name>[--server-username=<username> --server-password=<password>] --client-name=<client-name>[--client-type=<client-type>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to remove a protocol from a client.

<client-name> is the name of client.

<client-type> is required to specify the client protocol to be removed from this client. It can have one or more of the following values:


Separate the protocols with commas if more than one protocol is specified.

Use the -f (--force) option to disable the client protocol forcefully when any virtual device or iSCSI target is assigned to the client.




Get virtual device ID by serial number

iscli getvidbyserialno -s <server-name> [-u <username> -p <password>]-n <serial-number> [-X <rpc-timeout>]

iscli getvidbyserialno --server-name=<server-name>[--server-username=<username> --server-password=<password>] --serial-no=<serial-number>[--rpc-timeout=<rpc-timeout>]

Description:

<serial-number> is a 12-character long alphanumeric string required to get the corresponding virtual device ID.




SAN Client commands for virtual devicesThe following commands are SAN client commands for virtual device operations, not server commands.

A server name is required for each command so that the SAN client knows which server the command is for. Server username and password are not required because the command can only be executed on the client machine and authentication is already established.

A common error for the client commands is that the specified server is not added to the client. In this case, the following message will be displayed:

The DF2112 server is not added to the client. Error: 0x09020031

If this occurs, you have to add the server from the client monitor before any client commands can be issued against the server.

Attach to virtual device

iscli attachvdev -s <server-name> -v <vdevid> [-W <wait-for-device-status>] [-X <rpc-timeout>]

iscli attachvdev --server-name=<server-name> --vdevid=<vdevid> [--wait-for-device-status=<wait-for-device-status>] [--rpc-timeout=<rpc-timeout>]

Description:

This command is sent to the SAN client on the machine executing this command to attach the virtual device on the specified server. Server name and virtual device ID are required.

If the virtual device is already attached, the following message will be displayed and the virtual device will not be attached again:

The requested Virtual Device is already attached.Error: 0x09020008

When the attachment request is issued, the server will return information to the SAN client to indicate if the attachment is successful. However, it will take some time for the device to become ready even when it is attached successfully. The -W (--wait-for-device-status) option allows you to specify the number of seconds to wait and check the device status before returning from the command. One of three device statuses will be displayed when all operations are successful:

The virtual device <vdevid> is ready.The virtual device <vdevid> is not ready.The virtual device <vdevid> is not available.

The first two can be displayed when the device is attached. The third will be displayed when the device is not attached. Otherwise, an error message will be displayed and the device status will be irrelevant.

You can choose to issue a attachvdev command without the –W option and issue another getdevicestatus command separately in a loop from a script to achieve the same result.

When a virtual device is just assigned to the client either through console or CLI, the client will not recognize it unless you rescan the devices with the CLI rescanclientdevices command. The following error will be displayed if the virtual device is assigned to the client but not recognized by the client yet:

The virtual device is not assigned to the client.Error: 0x0902002a



Detach from virtual device

iscli detachvdev -s <server-name> -v <vdevid> [-W <wait-for-device-status>] [-X <rpc-timeout>]

iscli detachvdev --server-name=<server-name> --vdevid=<vdevid> [--wait-for-device-status=<wait-for-device-status>] [--rpc-timeout=<rpc-timeout>]

Description:

This command is sent to the SAN client on the machine executing this command to detach the virtual device from the specified server.

If the virtual device is already detached, the following error will be displayed and the virtual device will not be detached again:

The requested Virtual Device is already detached.Error: 0x09020030

When the detachment request is issued, the server will return information to the SAN client to indicate if the detachment is successful. However, it will take some time for the device to become unavailable even when it is detached successfully. The -W (--wait-for-device-status) option allows you to specify the number of seconds to wait and check the device status before returning from the command. Since the purpose of this command is to detach the virtual device and find out if it is detached, only two statuses will be displayed when all of the operations are successful:

The virtual device <vdevid> is detached.The virtual device <vdevid> is detaching.

The first will be displayed when the device is detached and is not available. The second will be displayed when the device is either attached or still available. Otherwise, an error message will be displayed and the device status will be irrelevant.

You can choose to issue a detachvdev command without –W option and issue another getattachvdev and/or getdevicestatus command separately in a loop from a script to achieve the same result.

Rescan devices assigned to client

iscli rescanclientdevices -s <server-name> [-N] [-X <rpc-timeout>]

iscli rescanclientdevices --server-name=<server-name> [--no-connect] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to rescan the devices on the specified server assigned to the client. The default is to request the client to connect to the server and rescan the devices assigned to the client. All devices will be rescanned and attached as the result of this command, and the connection between the client and the server will be kept. If you only want to refresh the list of the devices, without re-attaching all devices, use the -N (--no-connect) option. In this case, the list of the devices will be refreshed, but the connection will not be kept and the detached devices will not be re-attached.

Error codes:

0x09020001 Invalid Parameter. The usage for rescanclientdevices command will be displayed instead of the error message.0x09020006 Connecting to SAN client failed.0x0902000a Disconnecting from SAN client failed.0x09020031 The DF2112 server is not added to the client.0x0902002f Rescanning devices failed.



Get virtual device attached state

iscli getattachstate -s <server-name> -v <vdevid> [-r | -R] [-X <rpc-timeout>]

iscli getattachstate --server-name=<server-name> --vdevid=<vdevid> [--rescan-devices | --rescan-only] [--rpc-timeout=<rpc-timeout>]

Description:

This command shows whether a virtual device on the specified server is attached or detached if the virtual device is assigned to the client and is recognized by the client. The –r (--rescan-devices) and –R (rescan-only) options are provided for convenience purposes after the virtual device is assigned or unassigned. The –r option will request the client to keep the connection to the server after rescanning the devices. –R will request and update the device information from the server without changing the connection status.

This command can be issued at any time to check the attachment state of any virtual device assigned to the client.

Get virtual device status

iscli getdevicestatus -s <server-name> -v <vdevid> [-X <rpc-timeout>]

iscli getdevicestatus --server-name=<server-name> --vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command shows if the virtual device is ready, not ready, or not available. When the device is attached, the status is either ready or not ready. When the device is not attached, the status is not available. The actual message displayed from CLI are:

The virtual device <vdevid> is ready.The virtual device <vdevid> is not ready.The virtual device <vdevid> is not available.

This command can be issued at any time when you want to know the device status of a virtual device on the specified server. Or, you can issue this command in a loop for a set period of time in a script after the attachvdev command to check if the device is ready.

Error codes:

0x09020001 Invalid Parameter. The usage for getdevicestatus command will be displayed instead of the error message.0x0901000a Invalid Virtual Device ID0x09020006 Connecting to SAN client failed.0x0902000a Disconnecting from SAN client failed.0x0902002a The virtual device is not assigned to the client.0x0902200c Failed to get device status from client.0x09020031 The DF2112 server is not added to the client.



Mirroring

Create mirror

iscli createmirror -s <server-name> [-u <username> -p <password>] -v <vdevid>[-t <selection-criteria>] [-I <ACSL> | -sp <storage-pool-id> | -SP <storage-pool-name> |-M <custom-method> | -L <custom-layout>] [-X <rpc-timeout>]

iscli createmirror --server-name=<server-name>[--server-username=<username> --server-password=<password>] --vdevid=<vdevid>[--selectioncriteria=<selection criteria>] [--scsiaddress=<ACSL> |--storage-pool-id=<storage-pool-id> | --storage-pool-name=<storage-pool-name> |--custom-method=<custom-method> | --custom-layout=<custom-layout>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to create a mirror for the specified virtual device. The virtual device can be a SAN, NAS, or Replica resource.

<selection-criteria> is one of the values:

• different-adapter• different-drive• any-drive.

Use the -I (--scsiaddress) option to specify a specific physical device to be used to create the virtual device. ACSL=#:#:#:# (adapter:channel:id:lun)

-sp (storage-pool-id) or -SP (storage-pool-name) can be specified to allocate the space from the physical devices in the storage pool for the virtual device when the -I option is not specified.

The <custom-mode> and <custom-mode> options are for specific physical segments. It can be a list or a file enclosed in <> containing physical segment in each line. The format of the physical segment for <custom-mode> is: adapter:channel:scsi-id:lun:first-sector:size-in-MB


If none of the above options is specified, the system will allocate the storage for the mirror with the default criteria in the following order:

1. the storage from different adapter(s)2. the storage from different drive(s)3. the storage from any drive(s)




Get mirror status

iscli getmirrorstatus -s <server-name> [-u <username> -p <password>] [-X <rpc-timeout>]

iscli getmirrorstatus --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command shows the mirror status of a virtual device. The resource name, ID and synchronization status will be displayed if there is a mirror disk configured for the virtual device:

Resource Name (ID): VirtualDisk-2 (2)Synchronization Status: in-sync (100 %)

Sync mirror

iscli syncmirror -s <server-name> [-u <username> -p <password>] -v <vdevid> [-X <rpc-timeout>]

iscli syncmirror --server-name=<server-name> [--server-username=<username>--server-password=<password>] --vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command synchronizes the mirrored disks.

Swap mirror

iscli swapmirror -s <server-name> [-u <username> -p <password>] -v <vdevid> [-X <rpc-timeout>]

iscli swapmirror --server-name=<server-name> [--server-username=<username>--server-password=<password>] --vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command reverse the roles of the primary disk and the mirrored copy.

Promote mirror

iscli promotemirror -s <server-name> [-u <username> -p <password>] -v <vdevid> [-n <vdevname>] [-f] [-X <rpc-timeout>]

iscli promotemirror --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--vdevname=<vdevname>] [--force][--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to promote a mirror disk to a regular virtual device. The mirror cannot be promoted if the synchronization is in progress or when it is out-of-sync and the force option is not specified. The following errors will be displayed:

Mirror synchronization is in progress.



Error: 0x0901001b

Mirror is out of sync.Error: 0x0901003b

An out-of-sync mirror can be promoted with the force option for the following reasons:

• The primary disk is physically defective or becomes unavailable.• The mirror disk is imported without the primary disk.

Note: The force option should only be used when it is absolutely necessary.

If the virtual device is a NAS resource or a NAS replica resource and the NAS option is not enabled, the mirror cannot be promoted. The following error will be displayed:

NAS Option is not enabled.Error: 0x0901001f

A specific virtual device name can be specified through the –n (--vdevname) option. The maximum length of the virtual device name is 64. If the length of the name exceeds 64, the usage will be displayed.

If the virtual device name is specified and it is a duplicate name of another virtual device, the following error will be displayed:

Duplicate Virtual Device name. Error: 0x09010022

If the primary virtual device is a SAN resource or a SAN replica resource and the name contains any of these characters: < > " & $ / \ ‘, the following error will be displayed:

Invalid Virtual Device name. Error: 0x0901001e

If the primary virtual device is a NAS resource or a NAS replica resource and the name contains any of these characters: < > " & $ / \ ' ( ) % # : ; | * ? `, the following error will be displayed:

Invalid Virtual Device name.Error: 0x0901001e

If the virtual device name is not specified, a default virtual device name will be generated for the new virtual device. The default name is “SANDisk-#” or “NASDisk-#” depending on the type of resource, where # is the actual virtual device ID. If, for any reason, the default virtual device name is a duplicate name of another virtual device, an additional suffix will be added to the default name. For example: SANDisk-00001.1.

Please be aware that most of the systems interpret special characters differently before the program receives it. Avoid using special characters if possible. If the name contains any spaces, enclose it with double quotes. Although spaces can be used for the SAN resource name, leading and trailing spaces will be removed.

Remove mirror

iscli removemirror -s <server-name> [-u <username> -p <password>] -v <vdevid> [-X <rpc-timeout>]

iscli removemirror --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to remove a mirror for the specified virtual device.



Migrate

iscli migrate -s <server-name> [-u <username> -p <password>] -v <vdevid>[-t <selection-criteria>] [-I <ACSL> | -sp <storage-pool-id> | -SP <storage-pool-name> |-M <custom-method> | -L <custom-layout>] [-X <rpc-timeout>]

iscli migrate --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid>[--selectioncriteria=<selection criteria>] [--scsiaddress=<ACSL> |--storage-pool-id=<storage-pool-id> | --storage-pool-name=<storage-pool-name> |--custom-method=<custom-method> | --custom-layout=<custom-layout>][--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to copy a virtual device without a snapshot. The original virtual device becomes a new virtual device with a new virtual device ID. The original virtual device name and ID will be kept, but with segments allocated from different storage. If the virtual device does not have mirror, it will create a mirror, sync the mirror, swap the mirror, then promote the mirror. If the virtual device already has mirror, it will swap the mirror, sync the mirror, promote the mirror, then re-create the mirror for the original VID.

<selection-criteria> is one of the values:


Use the -I (--scsiaddress) option to specify a specific physical device to be used to create the virtual device. ACSL=#:#:#:# (adapter:channel:id:lun)

-sp (storage-pool-id) or -SP (storage-pool-name) can be specified to allocate the space from the physical devices in the storage pool for the virtual device when the -I option is not specified.

The <custom-mode> and <custom-mode> options are for specific physical segments. It can be a list or a file enclosed in <> containing a physical segment on each line. The format of the physical segment for <custom-mode> is: adapter:channel:scsi-id:lun:first-sector:size-in-MB


If none of the above options are specified, the system will allocate the storage for the mirror with the default criteria in the following order:

1. the storage from different adapter(s)2. the storage from different drive(s)3. the storage from any drive(s)




Snapshot resource

Create snapshot resource

iscli createsnapshotresource -s <server-name> [-u <username> -p <password>]-v <source-vdevid> [[-m <sizeMB] [-t <selection-criteria>][-I <ACSL>|-sp <storage-pool-id>|-SP <storage-pool-name>] | -M <custom-mode>|-L <custom-layout>] [-h <threshold>] [-c <increment> [-Z <max-size-mb>]][-A | -O] [-n <snapshot-notification>] [-X <rpc-timeout>]

iscli createsnapshotresource --server-name=<server-name>[--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> [[--size-mb=<#(MB)>] [--selectioncriteria=<device selection criteria>] [--scsiaddress=<ACSL> |--storage-pool-id=<storage-pool-id> | --storage-pool-name=<storage-pool-name>] |--custom-method=<custom-mode>| --custom-layout=<custom-layout>] [--threshold=<threshold>] [--increment=<increment> [--max-size=<max-size-mb>]][--auto-delete | --stop-write] [--snapshot-notification=<snapshot-notification>][--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to create a snapshot resource for a virtual device. A snapshot resource is required in order for a virtual device to be enabled with the TimeMark or Backup options. It is also required for replication, snapshot copy, and when joining a group.

If the size of Snapshot Resource is not specified with the -m (--size-mb) option, the default size will be determined by the size of the source virtual device as follows:

• < 500MB -> 100%• >= 500 MB and < 2GB -> 50%• >= 2GB -> 20%

-I (--scsiaddress), -sp (--storage-pool-id), and -SP (storage-pool-name) can be specified to determine the physical devices for allocation.

Use the -M (--custom-method) and -L (--custom-layout) options for specific physical layout. Refer to the usage of the createvdev command for details.

The <custom-method> and <custom-layout> options cannot be specified when the -m or -I option is specified.

<selection-criteria> can be one of the following values:

• different-adapter• different-drive• any-drive

<threshold> is a percentage of the space used to trigger the automatic expansion. The default is 50% if it is not specified. The threshold range is between 50% and 95%. You can specify the threshold value with or without %.

Use the <increment> option for the amount to allocate when the threshold is reached. It can be either percentage or size in MB. e.g. 10% or 100MB. The default is 20% if it is not specified. Specify either 0MB or 0% if you do not want to set the automatic expansion.



Use the <max-size-mb> option for the maximum size allowed to be allocated for the Snapshot Resource in MB. It only takes effect when auto-expansion is performed and should only be specified when the increment size was configured.

Use the <auto-delete> and <stop-write> options to determine what to do when the space of the Snapshot Resource runs out. The default policy is <auto-delete> if neither one is specified.

As of DF2112 5.0, the stop write option is no longer supported and <auto-delete> will always be the policy.

Use the <snapshot-notification> option to enable/disable snapshot notification to the client before a snapshot is taken. It can be one of the following values:

• on• off


Delete snapshot resource

iscli deletesnapshotresource -s <server-name> [-u <username> -p <password>] -v <source-vdevid> [-X <rpc-timeout>]

iscli deletesnapshotresource --server-name=<server-name> [--server-username=<username> --server-password=<password>] <--source-vdevid=<source-vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

A snapshot resource is not needed if the virtual device is not enabled for the TimeMark or Backup options, is configured for replication or is in a group. You can delete the snapshot resource to free up space when it is not needed.

Snapshot resource cannot be deleted when one of the following conditions applies:

• Resource is in a group.• Resource is enabled with the TimeMark option.• Resource is enabled with the Backup option.• Resource is configured with replication or is a replica disk.

Expand snapshot resource

iscli expandsnapshotresource -s <server-name> [-u <username> -p <password>] -v <source-vdevid> -m <#(MB)> [-X <rpc-timeout>]

iscli expandsnapshotresource --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> --additional-mb=<#(MB)>[--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to expand the snapshot resource on demand. The maximum size allowed that is specified in the snapshot policy only applies to the automatic expansion. The size limit does not apply when the snapshot resource is expanded on demand.



Set snapshot policy

iscli setsnapshotpolicy -s <server-name> [-u <username> -p <password>] -v <source-vdevid>[-h <threshold>] [-c <increment> [-Z <max-size-mb>]] [-A | -O] [-n <snapshot-notification>] [-X <rpc-timeout>]

iscli setsnapshotpolicy --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> [--threshold=<threshold>][<--increment=<increment> [--max-size=<max-size>]] [--auto-delete | --stop-write] [--snapshot-notification=<snapshot-notification>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to modify the existing snapshot policy for the specified resource. The new policy will take effect with the next snapshot operation.

Get snapshot policy

iscli getsnapshotpolicy -s <server-name> [-u <username> -p <password>] -v <source-vdevid> [-X <rpc-timeout>]

iscli getsnapshotpolicy --server-name=<server-name> [--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to view the snapshot policy settings for the specified resource.



Cache resourcesCreate a cache resourceiscli createcacheresource -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [[-m <sizeMB] [-t <selection-criteria>] [-I <ACSL>|-sp <storage-pool-id>|-SP <storage-pool-name>] |-M <custom-mode>| -L <custom-layout>] [-X <rpc-timeout>]

iscli createcacheresource --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[[--size-mb=<#(MB)>] [--selectioncriteria=<device selection criteria>][--scsiaddress=<ACSL> | --storage-pool-id=<storage-pool-id> |--storage-pool-name=<storage-pool-name>] | --custom-method=<custom-mode>|--custom-layout=<custom-layout>] [--rpc-timeout=<rpc-timeout>]

Description:

This command creates a cache resource for a virtual device or a group.

If the size of Cache Resource is not specified with the -m (--size-mb) option, it will default to 20% of the size of the virtual device or 100MB if it is for a group. If the default size is greater than the total available space, the total available size will be the default size.




<selection-criteria> can be one of the values:



Get cache resource statusiscli getcacheresourcestatus -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli getcacheresourcestatus --server-name=<server-name>[--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--rpc-timeout=<rpc-timeout>]

Description:

This command gets the status of a cache resource.




Set cache resource propertiesiscli setcacheresourceprop -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name>[-h <cache-data-threshold>] [-i <cache-inactivity>] [-c <cache-commands>][-k <skip-duplicate-write>] [-X <rpc-timeout>]

iscli setcacheresourceprop --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--cache-data-threshold=<cache-data-threshold>] [--cache-inactivity=<cache-inactivity>][--cache-commands=<cache-commands>] [--skip-duplicate-write=<skip-duplicate-write>][--rpc-timeout=<rpc-timeout>]

Description:

This command sets the properties of a cache resource.

Use the <cache-data-threshold> option to set a percentage of the threshold to start flushing the data.

Use the <cache-inactivity> option to specify a number (in milliseconds) to start flushing data after a specified time of inactivity when the data is below the threshold.

Use the <cache-commands> option to specify the maximum number of commands at a time to flush the cache data.

Use the <skip-duplicate-write> option to skip the pending write commands target for the same block. The value is one of the following values:

• on• off

At least one of the four options should be specified for this command.


Get cache resource properties

iscli getcacheresourceprop -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli getcacheresourceprop --server-name=<server-name>[--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--rpc-timeout=<rpc-timeout>]

Description:

This command displays the properties of a cache resource.




Suspend a cache resource

iscli suspendcacheresource -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli suspendcacheresource --server-name=<server-name> [--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--rpc-timeout=<rpc-timeout>]

Description:

This command suspends a cache resource. After the cache resource is suspended, no more new data will be written to it. The data on the cache resource will be flushed to the source resource.


Resume a cache resource

iscli resumecacheresource -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli resumecacheresource --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--rpc-timeout=<rpc-timeout>]

Description:

This command resumes a suspended cache resource.


Delete a cache resource

iscli deletecacheresource -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-W <wait-for-device-status> [-b]] [-f] [-X <rpc-timeout>]

iscli deletecacheresource --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--wait-for-device-status=<wait-for-device-status> [--verbose]] [--force][--rpc-timeout=<rpc-timeout>]

Description:

This command deletes a cache resource. The data on the cache resource has to be flushed before the cache resource can be deleted. The system will suspend the cache resource first if it is not already suspended.

Use the <wait-for-device-status> option to wait up to the specified number of seconds for the data to be flushed. The default is not to wait. If the data is not flushed, the cache resource will not be deleted.



Use the -b (--verbose) option to display the cache flushing status before the cache resource is deleted when the <wait-for-device-status> option is specified.

The -f (--force) option can be specified to delete the cache resource without flushing the cache data if you are sure that the data integrity will not be jeopardized.




Snapshot CopyCreate Snapshot Copyiscli snapcopy -s <server-name> [-u <username> -p <password>] -v <source vdevid>[-o [-ss <snapshot-storage-pool-id>| -SS <snapshot-storage-pool-name>]] [-V <target vdevid> | [-n <vdevname>] [-I <ACSL>|-sp <storage-pool-id>|-SP <storage-pool-name>] | -M <custom-mode>|-L <custom-layout>]] [-X <rpc-timeout>]

iscli snapcopy --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source vdevid> [--create-snapshot-resource[--snapshot-storage-pool-id=<snapshot-storage-pool-id>|--snapshot-storage-pool-name=<snapshot-storage-pool-name>]] [--target-vdevid=<target vdevid> | [--vdevname=<vdevname>] [--scsiaddress=<ACSL> |--storage-pool-id=<storage-pool-id> | --storage-pool-name=<storage-pool-name>] |--custom-method=<custom-mode>| --custom-layout=<custom-layout>]] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to issue a snapshot copy between two virtual devices of the same size.

Use the -o (--create-snapshot-resource) option to allow the system to create the snapshot resource for the source disk when it is not created yet.

Use the -ss (--snapshot-storage-pool-id) and -SS (--snapshot-storage-pool-name) options to specify the storage pool to allocate space for the snapshot resource.

If <target vdevid> is not specified, a new virtual device will be created with either the default name or the virtual device name specified with -n option. The maximum length of the virtual device name is 64. The following characters are invalid for the SAN Resource name: <>"&$/\'

The following characters are invalid for the NAS Resource name: <>"&$/\'():;|*?`

Be aware that these characters are special characters that most of the systems interpret them with a different meaning before the program receives it. Spaces are allowed for the SAN Resource name, but leading and trailing spaces will be removed. If the SAN Resource name contains any spaces, it is necessary to enclose the name with double quotes.







Get Snapshot Copy statusiscli getsnapcopystatus -s name -v virtualid [-X <rpc-timeout>]

iscli getsnapcopystatus --server-name=name --source-vdevid=virtualid [--rpc-timeout=<rpc-timeout>]

Description:

Here are some examples of the output:

Example 1:

Virtual device 10 copied to virtual device 11 in progress.Snapshot copy Start Time: 07/09/2001 14:27:06Data copied (MB): 63 (6%)Command: getsnapcopystatus executed successfully.

Example 2:

Virtual device 10 copied to virtual device 11 successfully.Command: getsnapcopystatus executed successfully.



ReplicationCreate a replicaiscli createreplication -s <server-name> [-u <username> -p <password>] -v <source-vdevid>[-o [-ss <snapshot-storage-pool-id>| -SS <snapshot-storage-pool-name>]]-S <target-name> [-U <target-username> -P <target-password>] [-V <target-vdevid> [-O]][-sp <replica-storage-pool-id>| -SP <replica-storage-pool-name>][-rs <replica-snapshot-storage-pool-id>| -RS <replica-snapshot-storage-pool-name>][-w <watermark(MB)> [-r <watermark-retry>]] [[-I <initial-time>] -i <#[H|M]>][-c <on|off>] [-e <on|off>] [-N] [-M] [-x <on|off>] [-k <on|off>] [-l <replication-protocol>] [-f] [-X <rpc-timeout>]

iscli createreplication --server-name=<server-name>[--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> [--create-snapshot-resource[--snapshot-storage-pool-id=<storage-pool-id> | --snapshot-storage-pool-name=<storage-pool-name>]] | --target-name=<target-name>[--target-username=<target-username> --target-password=<target-password>][--target-vdevid=<target-vdevid>[--no-scan-for-existing-disk]][--replica-storage-pool-id=<storage-pool-id> | --replica-storage-pool-name=<storage-pool-name>][--replica-snapshot-storage-pool-id=<storage-pool-id> |--replica-snapshot-storage-pool-name=<storage-pool-name>] [--watermark=<watermark(MB)>[--watermark-retry=<watermark-retry>]] [[--initial-time=<initial-time>] --interval=<#[H|M]>][--compression=<on|off>] [--encryption<on|off>] [--no-scan-disk] [--mark-in-sync][--use-existing-timemark=<on|off>] [--preserve-timemark=<on|off>][--replication-protocol=<replication-protocol>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to set up a replication configuration.

Use the -o (--create-snapshot-resource) option to allow the system to create the snapshot resource for the primary disk if it is not created yet.

Use the -ss (--snapshot-storage-pool-id) and -SS (--snapshot-storage-pool-name) options for snapshot resource allocation.

Replication will kick off based on one or more of the following policies:

• Watermark in MB (watermark retry in minutes, default: 30)• Replication interval in Hours(H) or Minutes(M). For example, 2H or 120M (minimum interval is 10 minutes)

Use the <initial-time> option to specify the initial date and time in the format of MM-DD-YYYY hh:mm to start the first interval. Enclose the initial time with double quotes, e.g. "07-27-2005 12:00".

The -T (--replication-time) option is no longer supported. It can be replaced with an initial date/time and a 24-hour interval.

You have to choose at least one replication policy. The default policy is to replicate at 12:00 every day if no policy is specified.

Use the -c (--compression) option to enable/disable compression with one of the following values:

• on• off



Use the -e (--encryption) option to enable/disable encryption with one of the following values:

• on• off

Use the -N(--no-scan-disk) option to turn off the scan disk option if the replica disk is to be created. The default is to scan the disk after the replication setup to get the synchronization status of the primary and replica disk.

-O(--no-scan-for-existing-disk) is an additional option to turn off the scanning option when an existing disk is selected as a replica disk.

Use the -M (--mark-in-sync) option to mark the disks in-sync. This option should only be set when the disks are in-sync or when both primary disk and replica disk are brand new. When this option is specified, the scan disk option will be turned off.

Use the -l (--replication-protocol) option to set the protocol with one of the following values:

• rudp (default)• tcp

This is valid if the version of the target server is 5.0 or later and the replication is not configured for continuous mode. Starting from 5.1, the TCP protocol is supported for continuous mode.

<target-vdevid> is the existing virtual device on the target server to be selected as the replica disk instead of creating a new one.

Use the -sp (--storage-pool-id) and -SP (--storage-pool-name) options for new replica disk allocation.

Use the -rs (--replica-snapshot-storage-pool-id) and -RS (--replica-snapshot-storage-pool-name) options for replica snapshot resource allocation.

Use the -x (--use-existing-timemark) option to use an existing TimeMark for replication if one already exists. This option can have one of the following values:


Use the -k (--preserve-timemark) option to preserve the replication TimeMark after replication is completed if the TimeMark option is enabled. This option can have one of the following values:





Start replicationiscli startreplication -s <server-name> [-u <username> -p <password>] -v <vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli startreplication --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> | --group-id=<group-id> | --group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to start replication on demand for a virtual device or a group. You can only specify one identifier, -v <vdevid>, -g <group-id>, or -G <group-name>.

Stop replication

iscli stopreplication -s <server-name> [-u <username> -p <password>] -v <vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli stopreplication --server-name=<server-name> [--server-username=<username> --server-password=<password>] -vdevid=<vdevid> | --group-id=<group-id> | --group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

This command allows you to stop the replication that is in progress for a virtual device or a group. If a group is specified, and the group is enabled with replication, the replication for all resources in the group will be stopped. If replication is not enabled for the group, but some of the resources in the group are configured for replication, replication for the resources in the group will be stopped.

Suspend replication

iscli suspendreplication -s <server-name> [-u <username> -p <password>] -v <vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli suspendreplication --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> | --group-id=<group-id> | --group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to suspend scheduled replications for a virtual device or a group that will be triggered by your replication policy. It will not stop a replication that is currently in progress.

Resume replication

iscli resumereplication -s <server-name> [-u <username> -p <password>] -v <vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli resumereplication --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> | --group-id=<group-id> | --group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to resume replication for a virtual device or a group that was suspended by the suspendreplication command. The replication will then be triggered by the replication policy once it is resumed.



Promote the replica

iscli promotereplica -s <server-name> -v <vdevid> |-S <target-name> -v <replicaid> [-u <username> -p <password>] -U <target-username> -P <target-password>][-f] [-X <rpc-timeout>]

iscli promotereplica --server-name=<server-name> --vdevid=<vdevid> | --target-name=<target-name> --replicaid=<replicaid> [--server-username=<username> --server-password=<password>] [--target-username=<target-username> --target-password=<target-password>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to promote a replica to a regular virtual device if the primary disk is available and the replica disk is in a valid state.

The replica disk cannot be promoted if one of the following conditions applies:

• The resource (both primary disk and replica disk or either one) is in a group. • The replica disk is a NAS replica resource and the NAS option is not enabled on the target server.

The replica disk can be promoted with the force option if one of the following conditions applies. An error will be returned if the force option is not specified and the replica will not be promoted:

• The replica disk is in an invalid state and the primary disk is still available. The replica disk should be synchronized with the primary disk first before it is promoted. The replica disk is considered invalid when the replica disk has never been replicated, is being scanned or replicated, or failed in a scanning or replication operation.

• The primary disk is physically defective or becomes unavailable even when the configuration information for the primary disk is still valid. You may choose to promote the replica disk as if the primary disk is not available. The force option should only be used when it is absolutely necessary in this case.

• The primary disk is no longer available and the replica disk is in a valid or invalid state.• The replica disk is imported.

Remove replication

iscli removereplication -s <server-name> -v <vdevid> | -S <target-name> -v <replicaid> [-u <username> -p <password>] [-U <target-username> -P <target-password>] [-f] [-X <rpc-timeout>]

iscli removereplication --server-name=<server-name> --vdevid=<vdevid> | --target-name=<target-name> --replicaid=<replicaid> [--server-username=<username> --server-password=<password>] [--target-username=<target-username> --target-password=<target-password>] [--force] [--rpc-timeout=<rpc-timeout>]

This command allows you to remove the replication configuration from the primary disk on the primary server and delete the replica disk on the target server. Either a primary server with a primary disk or a target server with a replica disk can be specified.

If the target server no longer exists, cannot be connected to, or is no longer available, only the replication configuration on the primary server will be removed. If the primary server no longer exists, cannot be connected to, or when the primary disk is no longer available, only the replica disk will be deleted. The -f (--force) option has to be specified when either the primary server or the target server no longer exists, cannot be connected to, or when the primary disk or the replica disk is no longer available.



Get replication status

iscli getreplicationstatus -S <target-name> [-U <username> -P <password>]-v <replicaid>[-X <rpc-timeout>]

iscli getreplicationstatus --target-name=<target-name> [--target-username=<username>--target-password=<password>] --replicaid=<replicaid> [--rpc-timeout=<rpc-timeout>]

Description:

This command shows the replication status. The target server name and the replica disk ID are required to get the replication status. Depending upon the stage of replication, some or all of the following will be displayed:

• Replication status - Scanning, Idle, New, Failed, or In Progress• Last replication time - in mm/dd/yyyy hh:mm format or n/a• Replication start time - (if available) in mm/dd/yyyy hh:mm format• Total delta (KB) - (if available) the delta in Kbytes• Delta transferred - (if available) the percentage of the delta sent against the total delta

Set replication properties

iscli setreplicationproperties -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-w <watermark(MB)> [-r <watermark-retry>]] [[-I <initial-time>]-i <#[H|M]>][-c <on|off>] [-e <on|off>] [-x=<on|off>] [-k=<on|off>] [-l <replication-protocol>][-U <target-username> -P <target-password>] [-X <rpc-timeout>]

iscli setreplicationproperties --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--watermark=<watermark(MB)> [--watermark-retry=<watermark-retry>]][[--initial-time=<initial-time>] --interval=<#[H|M]>] [--compression<on|off>] [--encryption<on|off>] [--use-existing-timemark=<on|off>] [--preserve-timemark=<on|off>][--replication-protocol=<replication-protocol>] [--target-username=<target-username>--target-password=<target-password>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to set the replication policy for a virtual device or group configured for replication.

Replication will kick off based on one or more of the following policies:

• Watermark in MB (watermark retry in minutes, default: 30)• Replication interval in Hours(H) or Minutes(M). For example, e.g. 2H or 120M (minimum interval is 10

minutes)


The -T (--replication-time) option is no longer supported. It can be replaced with an initial date/time and a 24-hour interval. It can be replaced with an initial date/time and a 24-hour interval.

You have to choose at least one replication policy.

To unset the watermark, specify 0 for the watermark.



To unset the initial time, specify NA instead of the time.

To unset the interval, specify 0 for the interval.

The watermark retry value will be ignored if the watermark is not set.


• on• off

Use the -e (--encryption) option to enable/disable encryption with one of the following values:

• on• off

Replication properties can be updated for the resource or the group. All the resources in the group will also be updated with the specified properties if a group is specified.






Get replication properties

iscli getreplicationproperties -s <server-name> [-u <username> -p <password>] -v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli getreplicationproperties --server-name=<server-name> [--server-username=<username>--server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> |--group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to get the replication properties for a virtual device or group configured for replication.

Specify <source-vdevid> to get the replication properties of the virtual device, or <group-id> or <group-name> to get the replication properties for the group.




Relocate replica

iscli relocate -s <server-name> [-u <username> -p <password>]-v <source-vdevid> -S <target-name> [-U <target-username> -P <target-password>]-V <target-vdevid> [-X <rpc-timeout>]

iscli relocate --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> --target-name=<target-name>[--target-username=<target-username> --target-password=<target-password>]--target-vdevid=<target-vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command relocates a replica after the replica disk has been physically moved to a different server.


Scan replica

iscli scanreplica -s <server-name> [-u <username> -p <password>] -v <source-vdevid>[-X <rpc-timeout>]

iscli scanreplica --server-name=<server-name>[--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command scans a replica server.




TimeMark/CDPEnable TimeMarkiscli enabletimemark -s <server-name> [-u <username> -p <password>] -v <source-vdevid>[-o [-ss <storage-pool-id>|-SS <storage-pool-name>]] | -g <group-id> | -G <group-name>[-E] [-C <max-timemark-count>] [-A <automatic-timemark-schedule>[[-I <initial-time>] -i <#[H|M]>] [-q <frequency>]] [-D <on|off> [[-m <sizeMB] [-t <selection-criteria>] [-I <ACSL>|-sp <storage-pool-id>|-SP <storage-pool-name>]|-M <custom-mode>| -L <custom-layout>] [-h <threshold>] -c <increment> [-Z <max-size-mb>][-R <cdp-coverage-period>] [-F <performance-level>]] [-X <rpc-timeout>]

iscli enabletimemark --server-name=<server-name>[--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> [--create-snapshot-resource [--snapshot-storage-pool-id=<storage-pool-id> |--snapshot-storage-pool-name=<storage-pool-name>]] | --group-id=<group-id> | --group-name=<group-name> [--enable-resource-option][--max-timemark-count=<max-timemark-count>] [--automatic-timemark-schedule=<automatic-timemark-schedule> [[--initial-time=<initial-time>] --timemark-interval=<#[H|M]>] [--notification-frequency=<frequency>]] [--cdp-option=<on|off> [[--size-mb=<#(MB)>][--selectioncriteria=<device selection criteria>] [--scsiaddress=<ACSL>|--storage-pool-id=<storage-pool-id>| --storage-pool-name=<storage-pool-name>]|--custom-method=<custom-mode>| --custom-layout=<custom-layout>][--threshold=<threshold> --increment=<increment> [--max-size=<max-size-mb>]][--cdp-preferred-duration=<cdp-coverage-period>] [--cdp-performance-level=<performance-level>]] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to enable the TimeMark option for an individual resource or for a group. TimeMark can be enabled for a resource as long as it is not yet enabled.

The -o (--create-snapshot-resource) option allows the system to create a snapshot resource before enabling TimeMark.

-ss (--snapshot-storage-pool-id) and -SS (--snapshot-storage-pool-name) can be specified to determine the physical devices for snapshot resource allocation.

TimeMark can only be enabled for a group when all the resources in the group are enabled for TimeMark. The -E (--enable-resource-option) option allows the system to enable the non-eligible resources with the TimeMark option first before enabling the group TimeMark option.

<max-timemark-count> is the maximum number of TimeMarks to keep before purging. The range is between 1 and 255.

A TimeMark can be taken automatically at a specified interval starting from the default or a specified initial date/time.

<automatic-timemark-schedule> can be one of the following values:

• on• off

Set <automatic-timemark-schedule> to on to schedule TimeMark creation automatically.

<timemark-interval> is the option for a specified interval in Hours(H) or Minutes(M). e.g. 2H, 120M. The minimum interval is 10 minutes (10M). <start-time> is no longer supported, but the system will not generate the error if the option is specified to be backward compatible.



The <initial-time> option can be used to specify the initial date and time in the format of MM-DD-YYYY hh:mm to start the first interval. Enclose the initial time with double quote, e.g. "07-27-2005 12:00". If <initial-time> is not set with the interval, it will default to midnight today.

Note that the -T (--timemark-time) option is no longer supported. It has been replaced with an initial date/time and a 24-hour interval.

Set <automatic-timemark-schedule> to off if you do not want to schedule the automatic TimeMark creation. <initial-time> and <timemark-interval> will be ignored if <automatic-timemark-schedule> is set to off.

Use the -q (--notification-frequency) option to specify how often to trigger the snapshot notification for the scheduled TimeMarks when snapshot notification is enabled in the snapshot policy.

The -D (--cdp-option) option is for Continuous Data Protection (CDP) with the following values:


A CDP journal resource has to be created when CDP is enabled. The minimum size required for the CDP journal is 1 GB. If the size of the CDP journal resource is not specified with the -m (--size-mb) option, the default size is 1 GB (1024 MB).



<selection-criteria> is one of the following values:


The CDP journal resource can be expanded automatically when space is running low. The following properties can be specified for auto-expansion:

<threshold> is a percentage of the space used to determine if more space is needed. The default is 50% if it is not specified. The threshold range is between 50% and 75%. You can specify the threshold value with or without a %.

Use the -R (--cdp-coverage-period) option in conjunction with threshold to trigger auto-expansion when data kept in the journal hasn't exceeded the coverage period yet. Specify the number of days between 1 and 30 days or number of hours between 1 and 24 hours. For example, 7D is 7 days, 5H is 5 hours. The default cdp-coverage-period is 1 day.

The earlier journal will be deleted if neither auto-expansion policy is specified.

-c (--increment) can be either percentage or size in MB e.g. 10% or 100MB. The default is 20% if it is not specified. Specify either 0MB or 0% if you do not want to set the automatic expansion.

Use the <max-size-mb> option for the maximum size allowed to be allocated for the CDP journal resource in MB. It only takes effect when auto-expansion is performed and should only be specified when the increment size is configured.

The minimum number of TimeMarks required for CDP is 4. To ensure continuous coverage, you should maintain the total number of TimeMarks to be: continuous coverage period / scheduled interval plus 1.




Create TimeMark

iscli createtimemark -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-c <comment>] [-o <priority>][-X <rpc-timeout>]

iscli createtimemark --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--comment=<comment>] [--timemark-priority=<timemark-priority>][-n <snapshot-notification>] [--snapshot-notification=<snapshot-notification>][--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to create a TimeMark for a virtual device or a group. A timestamp will be associated with each TimeMark. A notification will be sent to the SAN client to stop writing data to its virtual devices before the TimeMark is created. The new TimeMark is not immediately available after a successful createtimemark command. The TimeMark creation status can be retrieved with the gettimemarkstatus command. The TimeMark timestamp information can be retrieved with the gettimemark command.

When the virtual device is in a group, a TimeMark cannot be created for the virtual device alone. The same TimeMark has to be created for all resources in a group. A group ID or group name is required to create a TimeMark for all resources in a group.

Use <comment> to add an optional description to be associated with the TimeMark. The maximum length is 32. Be sure to enclose the comment in " when there are spaces.

<timemark-priority> is only available in version 5.1 or later and can be set to one of the following values:

• low (default)• medium• high• critical

Specify <source-vdevid> to create a TimeMark of a virtual device, <group-id> or <group-name> to create a TimeMark for all the resources in the group.

Use the <snapshot-notification> option to enable/disable the snapshot notification to the client before snapshot is taken for this snapshot only regardless what the setting is in the snapshot policy. It can have one of the following values:

• on• off


Disable TimeMarkiscli disabletimemark -s <server-name> [-u <username> -p <password>] -v <source-vdevid> |-g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli disabletimemark --server-name=<server-name> [--server-username=<username> --server-password=<password>] <--source-vdevid=<source-vdevid> | --group-id=<group-id> |--group-name=<group-name> [--rpc-timeout=<rpc-timeout>]



Description:

This command allows you to disable the TimeMark option for a virtual device or a group.

TimeMark cannot be disabled for a resource if the resource is in a group enabled with TimeMark or when there is any TimeView resource associated with the resource.

The group’s TimeMark can be disabled as long as there is no group activity using the snapshot resource. Individual resources in the group will remain TimeMark-enabled after the group’s TimeMark is disabled.

Update TimeMark information

iscli updatetimemarkinfo -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> -t <timemark-timestamp>[-c <comment> | -r] [-o <priority>] [-X <rpc-timeout>]

iscli updatetimemarkinfo --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>--timemark-timestamp=<timemark-timestamp> [--comment=<comment> | --remove-comment][--timemark-priority=<timemark-priority>] [--rpc-timeout=<rpc-timeout>]

Description:

This command is only available in version 5.1 or later and lets you add a comment or change the priority of an existing TimeMark. A TimeMark timestamp is required to update the TimeMark information.

To modify the comment, specify a new <comment> up to 32 characters or -r <--remove-comment> option to remove the comment.

<timemark-priority> of the TimeMark can be set to one of the following values:

• low (default)• medium• high• critical

Specify <source-vdevid> to update the TimeMark information for the virtual device. Both <comment> and <timemark-priority> can be updated when the virtual device is not in a TimeMark group. Only <comment> can be updated for a virtual device if it is in a TimeMark group.

Specify <group-id> or <group-name> to update the TimeMark priority for all the resources in the TimeMark group.

Either <comment>, <remove-comment> or <timemark-priority> option has to be specified for update.




Delete TimeMark

iscli deletetimemark -s <server-name> [-u <username> -p <password>] -v <source-vdevid> | -g <group-id> | -G <group-name> -t <timemark-timestamp> | -c <comment> [-D][-X <rpc-timeout>]

iscli deletetimemark --server-name=<server-name>[--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>--timemark-timestamp=<timemark-timestamp> | --comment=<comment> [--delete-all-outdated-timemarks] [--rpc-timeout=<rpc-timeout>]

Description:

A TimeMark can be deleted for a virtual device or a group. <timemark-timestamp> is the TimeMark timestamp to be selected for the deletion in the following format: YYYYMMDDhhmmss

<comment> is an alternative for specifying the TimeMark timestamp. Either <timemark-timestamp> or <comment> has to be specified.

Use the -D option to delete all the outdated TimeMarks up to and including the timestamp specified. If this option is not specified, only the specified TimeMark will be deleted.

If there is any TimeView virtual device associated with the TimeMark to be deleted, an error will be returned.

Specify <source-vdevid> to delete the TimeMark for the virtual device, <group-id> or <group-name> to delete the TimeMark for all the resources in the group.


Copy TimeMark

iscli copytimemark -s <server-name> [-u <username> -p <password>] -v <source-vdevid>-t <timemark-timestamp> | -c <comment> [-V <target vdevid> | [-n <vdevname>][-I <ACSL>|-sp <storage-pool-id>|-SP <storage-pool-name>] | -M <custom-mode>|-L <custom-layout>]] [-X <rpc-timeout>]

iscli copytimemark --server-name=<server-name>[--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> --timemark-timestamp=<timemark-timestamp> | --comment=<comment> [--target-vdevid=<target vdevid> | [--vdevname=<vdevname>][--scsiaddress=<ACSL> | --storage-pool-id=<storage-pool-id> | --storage-pool-name=<storage-pool-name>] | --custom-method=<custom-mode>|--custom-layout=<custom-layout>]] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to copy the specified TimeMark to an existing or newly created virtual device with the same size. The copying status can be retrieved with the gettimemarkstatus command.

<timemark-timestamp> is the timestamp of the TimeMark to be copied from in the following format: YYYYMMDDhhmmss




-I (--scsiaddress), -sp (--storage-pool-id), -SP (storage-pool-name) can be specified to determine the physical devices for allocation.

Use the -M (--custom-method) and -L (--custom-layout) options for specific physical layout. Refer to the usage of createvdev command for details.



Select TimeMark

iscli selecttimemark -s <server-name> [-u <username> -p <password>] -v <source-vdevid>-t <timemark-timestamp> | -c <comment> [-X <rpc-timeout>]

iscli selecttimemark --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> --timemark-timestamp=<timestamp> | --comment=<comment> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to select a TimeMark and create a raw device on the server to be accessed directly. Only one raw device can be created per TimeMark. The corresponding delselecttimemark command should be issued to release the raw device when the raw device is no longer needed.

Deselect TimeMark

iscli deselecttimemark -s <server-name> [-u <username> -p <password>] -v <source-vdevid> [-X <rpc-timeout>]

iscli deselecttimemark --server-name=<server-name> [--server-username=<username>--server-password=<password>] --source-vdevid=<source-vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to release the raw device associated with the TimeMark previously selected via the selecttimemark command.

Rollback TimeMark

iscli rollbacktimemark -s <server-name> [-u <username> -p <password>] -v <source-vdevid>-t <timemark-timestamp> | -c <comment> | -T <data-timestamp-sec> -m <data-timestamp-usec>[-X <rpc-timeout>]

iscli rollbacktimemark --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> --timemark-timestamp=<timemark-timestamp> |--comment=<comment> | --data-timestamp-sec=<data-timestamp-sec>--data-timestamp-usec=<data-timestamp-usec> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to rollback a virtual device to a specific point-in-time. The rollback status can be retrieved with the gettimemarkstatus command.



TimeMark rollback is not allowed for replica disks.

<timemark-timestamp> is the timestamp of the TimeMark to rollback to in the following format: YYYYMMDDhhmmss


If a TimeView exists for the TimeMark that will be removed as the result of the rollback, an error will be returned.

Use <data-timestamp-sec> + <data-timestamp-usec> to specify the timestamp up to the microsecond instead of the TimeMark timestamp, if CDP is enabled for the virtual device or the group, if the virtual device is in a TimeMark group enabled with CDP.

The format for <data-timestamp-sec> is YYYYMMDDhhmmss and the value for <data-timestamp-usec> is a number between 0 and 999999. The available time range for the CDP journal can be retrieved with the getcdpjournalinfo command.

A TimeMark prior to the specified data timestamp has to be available to rollback the data to.

Specify <source-vdevid> to rollback the TimeMark of the virtual device.


Get TimeMark

iscli gettimemark -s <server-name> [-u <username> -p <password>] -v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli gettimemark --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> --group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to enumerate the TimeMarks and view the TimeMark information for a virtual device or for a group.

Set TimeMark properties

iscli settimemarkproperties -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-C <max-timemark-count>][-A <automatic-timemark-schedule> [[-I <initial-time>] -i <#[H|M]>]] [-q <frequency>]][-D <on|off> [[-m <sizeMB] [-t <selection-criteria>][-I <ACSL>|-sp <storage-pool-id>|-SP <storage-pool-name>]| -M <custom-mode>|-L <custom-layout>]] [-z <min-size-mb-to-expand> -c <increment> [-Z <max-size-mb>][-R <cdp-coverage-period>] [-F <performance-level>] [-X <rpc-timeout>]

iscli settimemarkproperties --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> --group-name=<group-name>[--max-timemark-count=<max-timemark-count>][--automatic-timemark-schedule=<automatic-timemark-schedule>[[--initial-time=<initial-time>] --timemark-interval=<#[H|M]>]][--notification-frequency=<frequency>]] [--cdp-option=<on|off> [[--size-mb=<#(MB)>][--selectioncriteria=<device selection criteria>] [--scsiaddress=<ACSL>|--storage-pool-id=<storage-pool-id>| --storage-pool-name=<storage-pool-name>]|



--custom-method=<custom-mode>| --custom-layout=<custom-layout>]][--min-size-mb-to-expand=<min-size-mb-to-expand> --increment=<increment> [--max-size=<max-size-mb>]][--cdp-preferred-duration=<cdp-coverage-period>] [--cdp-performance-level=<performance-level>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to change the TimeMark properties, such as the automatic TimeMark creation schedule and maximum TimeMarks allowed for a virtual device or a group.

When the virtual device is in a group, the TimeMark properties can only be set for the group.

You can set a schedule to create the TimeMark for a virtual device or for all resources in a group automatically at a set interval or at a specific time. You can also limit the total number of TimeMarks that can be created.

<max-timemark-count> is the maximum number of TimeMarks to keep before purging. The range is between 1 and 255. The default is 65 if it is not specified. The total number of TimeMarks does not include the TimeMarks associated with any TimeView resources.

TimeMarks can be taken automatically at a specified interval starting from the default or specified initial date/time.

<automatic-timemark-schedule> is one of the following values:

• on• off

Set <automatic-timemark-schedule> to on to schedule TimeMark creation automatically.

<timemark-interval> is the option for a specified interval in Hours(H) or Minutes(M). e.g. 2H, 120M. The minimum interval is 10 minutes (10M). <start-time> is no longer supported, but the system will not generate the error if the option is specified to be backward compatible.

Use the <initial-time> option to specify the initial date and time in the format of MM-DD-YYYY hh:mm to start the first interval. Be sure to enclose the initial time with double quotes, e.g. "07-27-2005 12:00". If <initial-time> is not set with the interval, it will be the default to midnight of today.

The -T (--timemark-time) option is no longer supported. It is replaced with an initial date/time and a 24-hour interval.

Set <automatic-timemark-schedule> to off if you do not want to schedule the automatic TimeMark creation. <initial-time> and <timemark-interval> will be ignored if <automatic-timemark-schedule> is set to off.

Use the -q (--notification-frequency) option to specify how often to trigger the snapshot notification for the scheduled TimeMarks when snapshot notification is enabled in the snapshot policy.

Use the -D (--cdp-option) option to set CDP with the following values:


A CDP journal resource has to be created when CDP option is enabled. The minimum size required for CDP journal is 1GB. If the size of CDP journal Resource is not specified with -m (--size-mb) option, the default size is 1 GB (1024 MB).




Use the -M (--custom-method) and -L (--custom-layout) options for specific physical layout. Refer to the usage of createvdev command for details.

<selection-criteria> is one of the following values:


The CDP journal resource can be expanded automatically when space is running low. The following properties can be specified for auto-expansion:

<threshold> is a percentage of the space used to determine if more space is needed. The default is 50% if it is not specified. The threshold range is between 50% and 75%. You can specify the threshold value with or without %.

Use the -R (--cdp-coverage-period) option in conjunction with threshold to trigger auto-expansion when data kept in the journal hasn't exceeded the coverage period yet. Specify a number of days between 1 and 30 days, or number of hours between 1 and 24 hours. e.g. 7D is 7 days, 5H is 5 hours. The default cdp-coverage-period is 1 day.

Earlier journal will be deleted if neither auto-expansion policy is specified.

-c (--increment) can be either percentage or size in MB. e.g. 10% or 100MB. The default is 20% if it is not specified.Specify either 0MB or 0% if you do not want to set the automatic expansion.

<max-size-mb> is the option for the maximum size allowed to be allocated for the CDP journal Resource in MB. It only takes effect when auto-expansion is performed and should only be specified when the increment size is configured.

The minimum number of TimeMarks required for CDP is 4. To ensure continuous coverage, you should maintain the total number of TimeMarks to be: continuous coverage period / scheduled interval plus 1.


Get TimeMark properties

iscli gettimemarkproperties -s <server-name> [-u <username> -p <password>] -v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli gettimemarkproperties --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> --group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to view the current TimeMark properties associated with a virtual device or a group. When the virtual device is in a group, the TimeMark properties can only be retrieved for the group.

Specify <source-vdevid> to get the TimeMark policy of the virtual device, or <group-id> or <group-name> to get the TimeMark policy for the group.




Get TimeMark status

iscli gettimemarkstatus -s <server-name> [-u <username> -p <password>] -v <vdevid>[-X <rpc-timeout>]

iscli gettimemarkstatus --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This commands allows you to retrieve the TimeMark creation state and TimeMark rollback or copying status.

Create TimeView

iscli createtimeview -s <server-name> [-u <username> -p <password>] -v <source-vdevid>-t <timemark-timestamp> | -c <comment> | -T <data-timestamp-sec> -m <data-timestamp-usec> | -A <cdp-journal-tag> [-n <vdevname>] [-i <guid>] [-o <mount-option>] [-X <rpc-timeout>]

iscli createtimeview --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<vdevid>--timemark-timestamp=<timemark-timestamp> | --comment=<comment> | --data-timestamp-sec=<data-timestamp-sec> --data-timestamp-usec=<data-timestamp-usec> |--cdp-journal-tag=<cdp-journal-tag> [--vdevname=<vdevname>] [--guid=<guid>] [--nas-mount-option=<mount-option>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to create a TimeView virtual device associated with specified virtual device and TimeMark.

A resource name can be specified for the TimeView resource. Refer to the createvdev command for the naming convention rules.

<timemark-timestamp> is the timestamp of the TimeMark for creating the TimeView from in the following format: YYYYMMDDhhmmss

<comment> is an alternative for specifying the TimeMark timestamp. Either <timemark-timestamp> or <comment> has to be specified to create a TimeView without the CDP option.

Use <data-timestamp-sec> + <data-timestamp-usec> to specify the timestamp up to the microsecond instead of the TimeMark timestamp if CDP is enabled for the virtual device or the group, if the virtual device is in a TimeMark group enabled with CDP.

The format for <data-timestamp-sec> is YYYYMMDDhhmmss and the value for <data-timestamp-usec> is a number between 0 and 999999. The available time range for the CDP journal can be retrieved using the getcdpjournalinfo command.

<cdp-journal-tag> is the tag created through the createcdpjournaltag command. The timestamp associated with the tag will be used when a valid tag is specified.

A TimeMark prior to the specified data timestamp has to be available in order to create the TimeView.

-n (--vdevname) is the option to specify the TimeView device name. The maximum length of the TimeView device name is 64.



Use the <guid> option to specify a unique GUID (Global Unique Identifier) to be used for the TimeView resource in the following format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

For example, c0a80166-0000-25ad-43f7-dfe975f563e8

Use the -o (--nas-mount-option) option for NAS TimeView to set the mount option to one of the following values:

• rw• ro


Remap TimeView

iscli remaptimeview -s <server-name> [-u <username> -p <password>] -v <vdevid>-t <timemark-timestamp> | -c <comment> | -T <data-timestamp-sec> -M <data-timestamp-usec>-A <cdp-journal-tag> [-n <vdevname>] [-X <rpc-timeout>]

iscli remaptimeview --server-name=<server-name>[--server-username=<username> --server-password=<password>] --vdevid=<vdevid>--timemark-timestamp=<timemark-timestamp> | --comment=<comment> |--data-timestamp-sec=<data-timestamp-sec> --data-timestamp-usec=<data-timestamp-usec>]--cdp-journal-tag=<cdp-journal-tag> [--vdevname=<vdevname>] [--rpc-timeout=<rpc-timeout>]

Description:

This command remaps a TimeView associated with a specified virtual device and TimeMark. The original TimeView is deleted and all changes to it are gone. A new TimeView is created with the new TimeMark using the same TimeView device ID. All of the connection assignments are retained.

<vdevid> is the ID of the TimeView to be remapped. <timemark-timestamp> is the new timestamp of the TimeMark to remap the TimeView to in the following format: YYYYMMDDhhmmss

<comment> is an alternative for specifying the TimeMark timestamp. Either <timemark-timestamp> or <comment> has to be specified to create a TimeView without the CDP option.

Use <data-timestamp-sec> + <data-timestamp-usec> to specify the timestamp up to the microsecond instead of the TimeMark timestamp if CDP is enabled for the virtual device or the group.

The format for <data-timestamp-sec> is YYYYMMDDhhmmss and the value for <data-timestamp-usec> is a number between 0 and 999999. The available time range for the CDP journal can be retrieved with the getcdpjournalinfo command.

<cdp-journal-tag> is the tag created through the createcdpjournaltag command. The timestamp associated with the tag will be used when a valid tag is specified.

-n (--vdevname) is the option to specify the new TimeView device name. The maximum length of the TimeView device name is 64.




Suspend CDP journal

iscli suspendcdpjournal -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli suspendcdpjournal --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--rpc-timeout=<rpc-timeout>]

This option suspends CDP. After the CDP journal is suspended, data will not be written to it until it is resumed.


Resume CDP journal

iscli resumecdpjournal -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli resumecdpjournal --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--rpc-timeout=<rpc-timeout>]

This option resumes CDP after it has been suspended.


Get CDP journal status

iscli getcdpjournalstatus -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli getcdpjournalstatus --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--rpc-timeout=<rpc-timeout>]

This command gets the current size and status of your CDP journal, including all policies.


Get CDP journal info

iscli getcdpjournalinfo -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name>[-M <journal-summary>] [-T <data-timestamp-sec>] [-X <rpc-timeout>]

iscli getcdpjournalinfo --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--journal-summary=<journal-summary] [--data-timestamp-sec=<data-timestamp-sec>][--rpc-timeout=<rpc-timeout>]



Specify -M (--journal-summary) option to get summary information for the CDP journal.

Specify the data timestamp with -T (--data-timestamp-sec) to get the updated data information.

At least one option has to be specified.


Create CDP journal tag

iscli createcdpjournaltag -s <server-name> [-u <username> -p <password>]-v <vdevid> | -g <group-id> | -G <group-name> -A <cdp-journal-tag> [-X <rpc-timeout>]

iscli createcdpjournaltag --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>--cdp-journal-tag=<cdp-journal-tag> [--rpc-timeout=<rpc-timeout>]

This command lets you manually add a tag to the CDP journal. The -A (--cdp-journal-tag) tag can be up to 64 characters long and serves as a bookmark in the CDP journal. Instead of specifying the timestamp, the tag can be used when creating a TimeView.

Specify -v (--vdevid) for a CDP journal enabled for single virtual device. Specify -g (--group-id) or -G (--group-name) for a CDP journal enabled for group.


Get CDP journal tags

iscli getcdpjournaltags -s <server-name> [-u <username> -p <password>]-v <source-vdevid> | -g <group-id> | -G <group-name> [-T <data-timestamp-sec> -m <data-timestamp-usec>] [-X <rpc-timeout>]

iscli getcdpjournaltags --server-name=<server-name>[--server-username=<username> --server-password=<password>]--source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name>[--data-timestamp-sec=<data-timestamp-sec> --data-timestamp-usec=<data-timestamp-usec>][--rpc-timeout=<rpc-timeout>]

Use the <data-timestamp-sec> + <data-timestamp-usec> options to specify the timestamp after which the CDP journal tags should be collected.

The format for <data-timestamp-sec> is YYYYMMDDhhmmss and the value for <data-timestamp-usec> is a number between 0 and 999999.

The available time range for the CDP journal can be retrieved with the getcdpjournalinfo command.




BackupEnable backupiscli enablebackup -s <server-name> [-u <username> -p <password>] -v <source-vdevid>[-o [-ss <storage-pool-id> | -SS <storage-pool-name>]] | -g <group-id> | -G <group-name>[-E] [-r <raw-device-name>] <[-t <inactivity-timeout>] [-c <closing-grace-period>]> |[-l <#[H|M]>] [-n <timemark-selection-criteria>] [-X <rpc-timeout>]

iscli enablebackup --server-name=<server-name>[--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> [--create-snapshot-resource[--snapshot-storage-pool-id=<storage-pool-id> | --snapshot-storage-pool-name=<storage-pool-name>]] | --group-id=<group-id> | --group-name=<group-name> [--enable-resource-option] [--raw-device-name=<raw-device-name>] <[--inactivity-timeout=<inactivity-timeout>][--closing-grace-period=<closing-grace-period>]> | [--backup-life-span=<#[H|M]>][--timemark-selection-criteria=<timemark-selection-criteria>][--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to enable the backup option for an individual resource or for a group. Backup can be enabled for a resource as long as it is not already enabled.

Use the -o (--create-snapshot-resource) is option to allow the system to create a snapshot resource for the resource (if it is not yet created) before enabling the backup option.

-ss (--snapshot-storage-pool-id) and -SS (--snapshot-storage-pool-name) can be specified to determine the physical devices for snapshot resource allocation.

Backup can only be enabled for a group when all the resources in the group are enabled for backup.

Use the -E (--enable-resource-option) option to allow the system to enable the non-eligible resources with the backup option first before enabling the group backup option.

<raw-device-name> will be used to create a raw device for the backup session. If the raw device name is not specified, a default raw device name will be generated by the system.

Use the <timemark-selection-criteria> option to specify how a snapshot should be taken for the backup session with one of the following values:

• use-existing• create

The raw device will be backed up within the specified window.

Use the <inactivity-timeout> option to specify the timeout value (in minutes) that should end the backup session when there is inactivity. The range is from 1 to 1440 (one day).

Use the <closing-grace-period> option to specify the grace period (in minutes) to wait before closing the backup session after the backup has finished. The range is from 0 to 1440 (one day).

Use the -l (--backup-life-span) option to set the maximum duration of a backup session in Hours(H) or Minutes(M). For example, 2H for 2 hours, 30M for 30 minutes. The maximum value is 9999. The backup session will be closed automatically when the backup session open time reaches the duration regardless of whether the backup process is completed or not.



<inactivity-timeout> and <closing-grace-period> cannot be specified with the -l (--backup-life-span) option.


Disable backup

iscli disablebackup -s <server-name> [-u <username> -p <password>] -v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli disablebackup --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> |--group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to disable backup for a virtual device or a group.

Backup of a resource cannot be disabled if the resource is in a group enabled for backup.

A group’s backup can be disabled as long as there is no group activity using the snapshot resource. Individual resources in the group will remain backup-enabled after the group’s backup is disabled

Set backup properties

iscli setbackupproperties -s <server-name> [-u <username> -p <password>] -v <source-vdevid> | -g <group-id> | -G <group-name> [-r <raw-device-name>] <[-t <inactivity-timeout>] [-c <closing-grace-period>]> | [-l <#[H|M]>] [-n <TimeMark-selection-criteria>] [-X <rpc-timeout>]

iscli setbackupproperties --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name> [-r <raw-device-name>] <[--inactivity-timeout=<inactivity-timeout>] [--closing-grace-period=<closing-grace-period>]> | [--backup-life-span=<#[H|M]] [--TimeMark-selection-criteria=<TimeMark-selection-criteria>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to change the backup properties, such inactivity timeout, closing grace period, backup window, and backup life span, for a virtual device or a group.

When the virtual device is in a group, the backup properties can only be set for the group.

To remove the inactivity timeout or backup life span, specify 0 as the value.



Get backup properties

iscli getbackupproperties -s <server-name> [-u <username> -p <password>] -v <source-vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli getbackupproperties --server-name=<server-name> [--server-username=<username> --server-password=<password>] --source-vdevid=<source-vdevid> | --group-id=<group-id> | --group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to view the current backup properties associated with a virtual device or a group enabled for backup. When the virtual device is in a group, the backup properties can only be retrieved for the group.

Stop backup

iscli stopbackup -s <server-name> [-u <username> -p <password>] -v <vdevid> | -g <group-id> | -G <group-name> [-X <rpc-timeout>]

iscli stopbackup --server-name=<server-name> [--server-username=<username> --server-password=<password>] -vdevid=<vdevid> | --group-id=<group-id> | --group-name=<group-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to stop the backup activity for a virtual device or a group.

If a group is specified and the group is enabled for backup, the backup activity for all resources in the group will be stopped. If the backup option is not enabled for the group, but some of the resources in the group are enabled for backup, the backup activity for the resources in the group will be stopped.



Groups

Create a group

iscli createsnapshotgroup -s <server-name> [-u <username> -p <password>] -G <group-name>[-R [-t <target-group-name>] -S <target-name> [-U <target-username> -P <target-password>]] [-T] [-B] [-C [-m <sizeMB>][<storage-pool-id>|-SP <storage-pool-name>]] [-n <snapshot-notification>][-X <rpc-timeout>]

iscli createsnapshotgroup --server-name=<server-name>[--server-username=<username> --server-password=<password>]--group-name=<group-name>[--enable-replication [--target-group-name=<target-group-name>] --target-name=<target-name> [--target-username=<target-username>--target-password=<target-password>]] [--enable-timemark] [--enable-backup][--enable-cache [--size-mb=<#(MB)>] [--storage-pool-id=<storage-pool-id> |--storage-pool-name=<storage-pool-name>]] [--snapshot-notification=<snapshot-notification>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to create a group, where <group-name> is the name for the group.

The maximum length for the group name is 64. The following characters are invalid for the group name: <>"&$/\

There are four options that can be enabled for the group:

• Replication• TimeMark• Backup• SafeCache

Use the -R option to enable the Replication for this group. If Replication is enabled, a group for the replica disks will be created on the target server. You can specify the <target-group-name> or use the default. The default is to use the same group name for both groups. The target server must be specified if replication is enabled.

Use the -T option to enable TimeMark option for the group.

Use the -B option to enable the Backup option for the group.

Use the -C option to enable the SafeCache for the group.

-sp (--storage-pool-id) and -SP (storage-pool-name) can be specified to determine the physical devices for cache resource allocation.

Use the <snapshot-notification> option to enable/disable snapshot notification to the client before a snapshot is taken. It can be one of the following values:

• on• off

The four options can be enabled/disabled through the following commands after creation of the group:

• enablereplication / disablereplication



• enabletimemark / disabletimemark• enablebackup / disablebackup• createcacheresource / deletecacheresource

The default properties for TimeMark, Backup, and Replication (if enabled) will be set for the new group. The properties of the enabled option can be updated or retrieved through the following commands after creation:

• setreplicationproperties / getreplicationproperties• settimemarkproperties / gettimemarkproperties• setbackupproperties / getbackupproperties• setcacheresourceprop / getcacheresourceprop


Join a group

iscli joinsnapshotgroup -s <server-name> [-u <username> -p <password>] -v <vdevid>-g <group-id> | -G <group-name> [-U <target-username> -P <target-password>][-Y [-ss <snapshot-storage-pool-id>| -SS <snapshot-storage-pool-name>][-sp <replica-storage-pool-id>| -SP <replica-storage-pool-name>][-rs <replica-snapshot-storage-pool-id>| -RS <replica-snapshot-storage-pool-name>]][-N] [-X <rpc-timeout>]

iscli joinsnapshotgroup --server-name=<server-name>[--server-username=<username> --server-password=<password>] --vdevid=<vdevid>--group-id=<group-id> | --group-name=<group-name> [--target-username=<target-username>--target-password=<target-password>] [--sync-resource-to-join[--snapshot-storage-pool-id=<storage-pool-id> | --snapshot-storage-pool-name=<storage-pool-name>]] [--no-group-client-assignment][--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to add a virtual device to the specified group. <vdevid> is the virtual device to join the group.

Either <group-id> or <group-name> can be specified for the group.

Use the -Y (--sync-resource-to-join) option to allow the system to update the resource when it is possible to synchronize all the required options for the resource to join the selected group.


If group replication is enabled, use the -sp (--storage-pool-id) and -SP (--storage-pool-name) options for new replica disk allocation.





Get groups

iscli getsnapshotgroups -s <server-name> [-u <username> -p <password>] [<-g <group-id> |-G <group-name>>] [-l [-a|-A][-c|-C]] [-X <rpc-timeout>]

iscli getsnapshotgroups --server-name=<server-name> [--server-username=<username> --server-password=<password>] [<--group-id=<group-id> | --group-name=<group-name>>][--longlist [--client-list|--long-client-list] [--physical-layout|--long-physical-layout]] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to retrieve group information for all groups or a specific group on the specified server.

The default output format is a list of groups and a list of group members in each group.

Example of the list output:

Group Name=SANGroupGroup ID=1Replication=DisabledBackup=DisabledTimeMark=DisabledNumber of Resources in the Group=2Resource Type=SAN

Virtual Device Name ID Size(MB) State Mirror Replica-------------------------------------------------------------------------------SANDisk-00010 10 100 on offSANDisk-00009 9 100 on off

Additional options are provided to display more detail information, including the physical device layout and client assignments for the resources in the group.

Delete device from a group

iscli leavesnapshotgroup -s <server-name> [-u <username> -p <password>] -v <vdevid> [-g <group-id> | -G <group-name>] [-U <target-username> -P <target-password>] [-f] [-X <rpc-timeout>]

iscli leavesnapshotgroup --server-name=<server-name> [--server-username=<username> --server-password=<password>] --vdevid=<vdevid> [--group-id=<group-id> | --group-name=<group-name>] [--target-username=<target-username> --target-password=<target-password>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to delete a virtual device from a group.

If the group is configured for replication, both the primary and target servers need to be available because the system will remove the primary disk from the group on the primary server and the replica disk from the group on the target server.

You can use the force option to allow the primary disk to leave the group on the primary server without connecting to the target server, or allow the replica disk to leave the group on the target server without connecting to the primary server. The force option should only be used when either the primary disk is not in the primary group anymore or when the replica disk is not in the replica group anymore.



Delete a group

iscli deletesnapshotgroup -s <server-name> [-u <username> -p <password>] <-g <group-id> |-G <group-name>> [-U <target-username> -P <target-password>] [-f] [-X <rpc-timeout>]

iscli deletesnapshotgroup --server-name=<server-name> [--server-username=<username> --server-password=<password>] --group-id=<group-id> | --group-name=<group-name>[--target-username=<target-username> --target-password=<target-password>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to delete a group. A group can only be deleted when there are no group members in it.

If the group is configured for replication, both the primary group and replica group have to be deleted. The force option is required if one of the following conditions applies:

• Deleting the replica group on the target server when the primary server is not available.• Deleting the primary group on the primary server when the target server is not available.

An error will be returned if the force option is not specified for these conditions.

Enable replication for a groupiscli enablereplication -s <server-name> [-u <username> -p <password>]-g <group-id> | -G <group-name> [-E [-ss <snapshot-storage-pool-id>|-SS <snapshot-storage-pool-name>] [-sp <replica-storage-pool-id>|-SP <replica-storage-pool-name>] [-rs <replica-snapshot-storage-pool-id>|-RS <replica-snapshot-storage-pool-name>]] [-t <target-group-name>]-S <target-name> [-U <target-username> -P <target-password>][-w <watermark(MB)> [-r <watermark-retry>]] [[-I <initial-time>] -i <#[H|M]>][-c <on|off>] [-e <on|off>] [-x <on|off>] [-k=<on|off>] [-l <replication-protocol>][-X <rpc-timeout>]

iscli enablereplication --server-name=<server-name>[--server-username=<username> --server-password=<password>]--group-id=<group-id> | --group-name=<group-name>[--enable-resource-option [--snapshot-storage-pool-id=<storage-pool-id> |--snapshot-storage-pool-name=<storage-pool-name>] [--replica-storage-pool-id=<storage-pool-id> |--replica-storage-pool-name=<storage-pool-name>] [--replica-snapshot-storage-pool-id=<storage-pool-id> |--replica-snapshot-storage-pool-name=<storage-pool-name>]] --target-name=<target-name>[--target-username=<target-username> --target-password=<target-password>][--target-group-name=<target-group-name>] [--watermark=<watermark(MB)>[--watermark-retry=<watermark-retry>]] [[--initial-time=<initial-time>] --interval=<#[H|M]>][--compression<on|off>] [--encryption<on|off>] [--use-existing-timemark=<on|off>][--preserve-timemark=<on|off>] [--replication-protocol=<replication-protocol>][--rpc-timeout=<rpc-timeout>]

Description:

<group-id> or <group-name> can be specified for the group that should have replication enabled. All of the resources in the group have to be configured with replication in order for the group to be enabled for replication.

Use the -E (--enable-resource-option) option to allow the system to configure the non-eligible resources with replication first before enabling the group replication option.



A target server must be specified. A group for the replica disks will be created on the target server. You can specify the <target-group-name> or use the default. The default is to use the same group name.


Use the -sp (--storage-pool-id) and -SP (--storage-pool-name) options for new replica disk allocation.


The replication policy can be specified to schedule the replication based on watermark, or at a set interval starting from the specified initial date/time.


The -T (--replication-time) option is no longer supported. It can be replaced with an initial date/time and a 24-hour interval.


• on• off

-Use the e (--encryption) option to enable/disable encryption with one of the following values:

• on• off





Use the -l (--replication-protocol) option to set the protocol with one of the following values:

• rudp (default)• tcp

This is valid if the version of the target server is 5.0 or later and the replication is not configured for continuous mode. Starting from 5.1, the TCP protocol is supported for continuous mode.




Disable replication for a group

iscli disablereplication -s <server-name> [-u <username> -p <password>] -g <group-id> | -G <group-name> [-U <target-username> -P <target-password>] [-X <rpc-timeout>]

iscli disablereplication --server-name=<server-name> [--server-username=<username>--server-password=<password>] --group-id=<group-id> | --group-name=<group-name>[--target-username=<target-username> --target-password=<target-password>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to disable replication for a group. All replica disks will leave the replica group and the replica group on the target server will be deleted. The replication configuration of all resources in the group will remain the same, but TimeMarks will not be taken for all resources together anymore. All replication operations will be applied to the individual resource only.

Set group replication properties

Refer to ‘Set replication properties’ for the group options.

Get group replication properties

Refer to ‘Get replication properties’ for the group options.

Enable TimeMark for a group

Refer to ‘Enable TimeMark’ for the group options.

Disable TimeMark for a group

Refer to ‘Disable TimeMark’ for the group options.

Set group TimeMark properties

Refer to ‘Set TimeMark properties’ for the group options.

Get group TimeMark properties

Refer to ‘Get TimeMark properties’ for the group options.

Enable backup for a group

Refer to ‘Enable backup’ for the group options.

Disable backup for a group

Refer to ‘Disable backup’ for the group options.



Set group backup properties

Refer to ‘Set backup properties’ for the group options.

Get group backup properties

Refer to ‘Get backup properties’ for the group options.



Physical devices

Get physical device information

iscli getpdevinfo -s <server-name> [-u <username> -p <password>][-F [-M | -C <category>]] | [[-a] [-A] [-I <ACSL>]] [-o <output-format>][-L <list-by-storage-pool>] [-sp <storage-pool-id> | -SP <storage-pool-name>][-X <rpc-timeout>]

iscli getpdevinfo --server-name=<server-name> [--server-username=<username> --server-password=<password>][--config [--include-system-info | --category=<category>]] | [[--allocated-list] [--available-list] [--scsiaddress=<ACSL>]] [--output-format=<output-format>][--list-by-storage-pool] [--storage-pool-id=<storage-pool-id> | --storage-pool-name=<storage-pool-name>] [--rpc-timeout=<rpc-timeout>]

Description:

This command provides you with physical device information.

Use the -F (--config) option to get the physical device configuration information. The default is to exclude the system device information. Use the -M (--include-system-info) option to include the system device information.

Use the <category> option as a filter to get the configuration information for the specified category. It can have one of the following values:

• virtual (default)• service-enabled• direct

The -M (--include-system-info) and <category> options are mutually exclusive.

<output-format> for the -F (--config) option is one of the following values:

• list• detail• guid• scsi

Use the -a (--allocated-list) option to get the allocated physical device information. Use the -A (--available-list) option to get the available physical device information.

<ACSL> is the SCSI address to be specified as a device filter in the following format: <ACSL>=#:#:#:# (adapter:channel:id:lun)

<output-format> for the -a (--allocated-list) and the -A (--available-list) options is one of the following values:

• list• detail• size-only

-F (--config) and (-a (--allocated-list) and/or -A (--available-list)) are mutually exclusive. You can either get the configuration information or get the allocation information. When getting the allocation information, you can specify either -a (--allocated-list), or -A (--available-list) or both. The default is to display both the device allocation and availability information if none of the options is specified.



Use the -L (--list-by-storage-pool) option to list the physical device information by storage pool.

Storage pools can also be specified to get the physical device information for the storage pool.

If <ACSL> is specified, the storage pool information will be ignored.


Rescan physical devices

iscli rescandevices -s <server-name> [-u <username> -p <password>] [-a <adapter>] [-i <scsi-range>] [-l <lun-range>] [-L] [-X <rpc-timeout>]

iscli rescandevices --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--adapter=<adapter>] [--scsi-range=<scsi-range>] [--lun-range=<lun-range>] [--sequential] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to rescan the physical resource(s) on the specified server to get the proper physical resource configuration.

The adapter number can be specified to rescan only the devices on that adapter. If an adapter is not specified, all adapters will be rescanned. In addition to the adapter number, you can also specify the SCSI range to be rescanned. If the range is not specified, all SCSI IDs of the specified adapter(s) will be rescanned. Furthermore, the LUN range can be specified to narrow down the rescanning range. The range is specified in this format: #-#, e.g. 1-10.

If you want the system to rescan the device sequentially, you can specify the –L ([--sequential) option. The default is not to rescan sequentially.

Import physical device

iscli importdisk -s <server-name> [-u <username> -p <password>] -i <guid> | -I <ACSL> [-X <rpc-timeout>]

iscli importdisk --server-name=<server-name> [--server-username=<username> --server-password=<password>] --scsiaddress=<ACSL> | --guid=<guid> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to import a foreign disk to the specified server. A foreign disk is a virtualized physical device containing DF2112 logical resources previously set up on a different DF2112 server.

If the previous server is no longer available, the disk can be set up on a new DF2112 server and the resources on the disk can be imported to the new server to make them available to clients. Either the GUID or SCSI address can be specified for the physical device to be imported. This information can be retrieved through the getpdevinfo command.



Prepare physical device for DF2112 server

iscli preparedisk -s <server-name> [-u <username> -p <password>] [-U <target-username> -P <target-password>] -i <guid> | -I <ACSL> -C <category> [-X <rpc-timeout>]

iscli preparedisk --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--adapter=<adapter>] [--target-username=<username> --target-password=<password>] --scsiaddress=<ACSL> | --guid=<guid> --category=<category> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to prepare a physical device to be used by a DF2112 server or reserve a physical device for other usage.

The <guid> is the unique identifier of the physical device. <ACSL> is the SCSI address of the physical device in this format: #:#:#:# (adapter:channel:scsi id:lun). You can specify either the <guid> or <ACSL> for the disk to be prepared.

There are four categories the disk can be set to:

• unassigned - The device is not reserved and cannot be used by the DF2112 server until the category is changed.

• virtual - The device will be used to create virtual devices. The data on the device will be not be reserved.• direct - Use for a direct-mapped SCSI device, such as a hard disk, tape drive or library. The data on the

device will be reserved. • service-enabled - Use for hard drives with existing data. The device will be prepared for use as is. A virtual

device header will be created on another physical device to allow DF2112’s storage services to be supported. The data on this device will be reserved.

If the server is configured for failover, the failover partner has to be rescanned after the disk is prepared to synchronize the physical device information on both servers. The <target-username> and <target-password> options specify the username and password for the failover partner.



X-Ray

Get X-Ray

iscli getxray -s name [-l [#, all, YYMMDDhhmm-YYMMDDhhmm]] [-M] [-o filename] [-f] [-X <rpc-timeout>]

iscli getxray --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--get-log=<#|all|YYMMDDhhmm-YYMMDDhhmm>] [--get-storage-message-only] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to get X-ray information from the DF2112 Server for diagnostic purposes. Each X-ray contains technical information about your server, such as server messages and a snapshot of your server's current configuration and environment. You should not create an X-ray unless you are requested to do so by your Technical Support representative.

The default is to get all information, and the last day’s log messages, and save to an output file on the client machine. The default file name is as follows:

Xray-YYYY-MM-DD-hh-mm-server name.tar.gz

Additional filters can be specified with the –l (--get-log) option to reduce the size of the output file.

• -l # gets the last # of lines only.• -l all gets all log messages.• -l YYMMDDhhmm-YYMMDDhhmm gets the log within the date/time range.• -M (--get-df2112-message-only) gets DF2112 messages only instead of all messages.• -o (output-file) allows you to specify an output filename instead of using the default output filename.

Specify the -f (--force) option if you want to overwrite the existing file, if one already exists. Otherwise, an error will be returned.



Report data

Get report data

iscli getreportdata -s <server-name> [-u <username> -p <password>] [-d <date>] [-I #[D|W|M]] [-C <clientList>] [-R <resourceList>] [-N] [-o <outputFilename>] [-F <fileFormat>] [-H] [-f] [-X <rpc-timeout>]

iscli getreportdata --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--date=<date>] [--units=#[<D|W|M>]] [--client-list=<clientList>] [--resource-list=<resourceList>] [--No-system-info][--output-file=<outputFilename>] [--file-format=<fileFormat>] [--include-heading] [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to get report data from the specified server and save the data to an output file in csv or text file format.

The ending date can be specified but the default is today if it is not specified. The total time units is specified as total passed time units ending with the end of day of the specified date. For example: if the ending date is 07/26/2001 and the time units is 2D (2 days), then the date/time range will be 07/25/2001, 00:00:00 to 07/26/2001, 23:59:59.

The time units can be specified in three different units, by Day, Week or Month. When the unit is by Day, the data interval will be every 30 minutes in 48 points per day. When the unit is by Week, the statistics interval will be every four hours in 42 points per week. When the unit is by Month, the statistics interval will be everyday in 30 points per month.

A list of resources can be specified for the report data or * for all resources. The list can be specified as a list of virtual device IDs separated by commas or through a text file where each virtual device is on a separate line. The file name should be enclosed in <> to indicate that it is a file name.

Example 1: -R 1,3,5,10

Example 2: -R "<res_id_file.txt>"

A list of clients can be specified for the report data or * for all clients. The list can be specified as a list of client names separated by commas or through a text file where each client name is on a separate line. The file name should be enclosed in <> to indicate that it is a file name.

Example 1: -C 1,3,5,10

Example 2: -C "<client_id_file.txt>"

System information includes Memory and CPU usage information on the server. The default is to include the system information. -N (--No-system_info) allows you to exclude the information.

If the output file name is not specified, the default file name is: ServerThroughputYYYY-MM-DD[.#][.#] is the additional suffix when there is a duplicate.

The file format is either csv (comma delimited) or txt (tab delimited).

The -H (--include-heading) option includes the data heading.

The data format is as follows:



<StartTime>, <EndTime>, <DataReadKB>, <DataWrittenKB>, <MemoryKB>, <CPU%>

Examples:

05/01/2001 00:00:00, 05/01/2001 00:29:59, 134342233, 133343334, 23423, 54

05/01/2001 00:30:00, 05/01/2001 00:59:59, 124342233, 323343334, 23403, 54

Specify the -f (--force) option if you want to overwrite the existing report file, if one already exists. Otherwise, an error will be returned.



Event Log

Get Event Log

iscli geteventlog -s <server-name> [-u <username> -p <password>] [-D <date-range>] [-F <fileFormat>] [-o <filename>] [-H] [-f] [-X <rpc-timeout>]

iscli geteventlog --server-name=<server-name> [--server-username=<username> --server-password=<password>] [--date-range=<date-range>] [--file-format=<fileFormat>][--output-file=<filename>] [--include-heading] [--force] [--rpc-timeout=<rpc-timeout>]

Description:

The date range can be specified to get the event log for a specific range. The default is to get all of the event log messages if a date range is not specified. The date range format can be one of the following:

• YYYYMMDDhhmmss-YYYYMMDDhhmmss - The starting date/time and ending date/time are specified in this case.

• YYYYMMDDhhmmss - Only the starting date/time is specified. The ending date/time will be the date/time of the latest event log message.

The file format is either csv (comma delimited) or txt (tab delimited).

If the output filename is not specified, the default filename is: eventlogYYYY-MM-DD-hh-mm-servername[.#]

[.#] is the additional suffix when there is a duplicate.

The -H (--include-heading) option includes the data heading.

The data format is the same as the event log data exported from the Console. The data in csv format is as follows:

<EventType>, <Date>, <Time>, <MessageID>, <MessageText>

Examples:

I,07/25/2001,22:59:43,11223,Console (root - 10.1.1.245 ): Logged in with read/write privileges.

I,07/25/2001,22:59:42,11304,User root at IP address 10.1.1.245 authenticated.

I,07/25/2001,17:00:36,11225,Console (root - 10.1.1.49 ): Logged out.

The data in text format will be the same except that the comma will be replaced with a tab.

The Event Type in the event log data is mapped to one of the following:

• I = Information• E = Error• W = Warning• C = Critical

Specify the -f (--force) option if you want to overwrite the existing log file, if one already exists. Otherwise, an error will be returned.



Failover

Get Failover status

iscli getfailoverstatus -s <server-name> [-u <username> -p <password>] [-X <rpc-timeout>]

iscli getfailoverstatus --server-name=<server-name> [--server-username=<username>--server-password=<password>] [--rpc-timeout=<rpc-timeout>]

Description:

This command shows you the current status of your failover configuration. It also shows all Failover settings, including which IP addresses are being monitored for failover.



Server configuration

Save configuration

iscli saveconfig -s <server-name> [-u <username> -p <password>] [-o <filename>] [-f] [-X <rpc-timeout>]

iscli saveconfig --server-name=<server-name> [--server-username=<username>--server-password=<password>] [--output-file=<filename>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command saves the configuration of your DF2112 Server. You should save the configuration any time you change it, including any time you add/change/delete a client or resource, assign a client, or make any changes to your failover/mirroring/replication configuration.

The default output filename is: config-YYYY-MM-DD-hh-mm-<servername>.tar.gz

Specify the -f (--force) option if you want to overwrite the existing file when the output file already exists. Otherwise, an error will be returned.

Restore configuration

iscli restoreconfig -s <server-name> [-u <username> -p <password>] <filename> [-X <rpc-timeout>]

iscli restoreconfig --server-name=<server-name> [--server-username=<username>--server-password=<password>] [--input-file=<filename>] [--rpc-timeout=<rpc-timeout>]

Description:

This command restores the configuration of your DF2112 Server. Specify the configuration file name that was saved with saveconfig command.

Restoring a configuration overwrites existing virtual device and client configurations for that server. DF2112 partition information will not be restored. This feature should only be used if your configuration is lost or corrupted.



Users and passwords

Add user

iscli adduser -s <server-name> [-u <username> -p <password>]-t <user-type>] -N <new-username> -W <new-password> [-q <quota>] [-X <rpc-timeout>]

iscli adduser --server-name=<server-name> [--server-username=<username> --server-password=<password>] --user-type=<user-type> --username=<new-username>--password=<new-password> --quota=<quota> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to add a DF2112 user. You must log in to the server as "root" in order to perform this operation.

<user-type> is required with one of the following values:

• A (for Administrator)• S (for User)

For iSCSI users, the password length has to be between 12 and 16.

<quota> is the quota available for a new user. Specify 0 for unlimited or enter the size of the quota in MB.


Set user password

iscli setuserpassword -s <server-name> [-u <username> -p <password>] -N <df2112-username> -W <new-password> -O <old-password> [-X <rpc-timeout>]

iscli setuserpassword --server-name=<server-name> [--server-username=<username>--server-password=<password>] --username=<df2112-username> --password=<new-password>--old-password=<old-password> [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to change a DF2112 user’s password. You must log in to the server as "root" in order to perform this operation if the user is not an iSCSI user.

For iSCSI users, the password length must be between 12 and 16.



iSCSI targetsCreate iSCSI target

iscli createiscsitarget -s <server-name> [-u <username> -p <password>] -c <client-name>[-R <iscsi-target-name>] -I <ip-address> -a <access-mode> [-l <starting-lun>] [-X <rpc-timeout>]

iscli createiscsitarget --server-name=<server-name> [--server-username=<username>--server-password=<password>] --client-name=<client-name> [--iscsi-target-name=<iscsi-target-name>] --ip-address=<ip-address>--access-mode=<access-mode> [--starting-lun=<starting-lun>] [--rpc-timeout=<rpc-timeout>]

Description:

This command creates an iSCSI target. <client-name>, <ip-address>, and <access-mode> are required. A default iSCSI target name will be generated if <iscsi-target-name> is not specified.

The values for <access-mode> are: Readonly, ReadWrite, ReadWriteNonExclusive. The values for the short format are: R / W / N.

The <starting-lun> can also be specified in the range of 0 - 254. The default starting LUN is 0 if it is not specified.

Set iSCSI target properties

iscli setiscsitargetprop -s <server-name> [-u <username> -p <password>] -r <iscsi-target-id> [-R <iscsi-target-name>] [-I <ip-address>] [-a <access-mode>] [-l <starting-lun>] [-X <rpc-timeout>]

iscli setiscsitargetprop --server-name=<server-name> [--server-username=<username> --server-password=<password>]--iscsi-target-id=<iscsi-target-id> [--iscsi-target-name=<iscsi-target-name>][--ip-address=<ip-address>] [--access-mode=<access-mode>] [--starting-lun=<starting-lun>] [--rpc-timeout=<rpc-timeout>]

Description:

This command sets the iSCSI target properties. Refer to Create iSCSI target above for details about the options.

Get iSCSI target information

iscli getiscsitargetinfo -s <server-name> [-u <username> -p <password>][-r <iscsi-target-id> | -R <iscsi-target-name>] [-l [-c <client-list>] | [-C <long-client-list>] [-e <resource-list>] | [-E <long-resource-list>]] [-X <rpc-timeout>]

iscli getiscsitargetinfo --server-name=<server-name>[--server-username=<username> --server-password=<password>][--iscsi-target-id=<iscsi-target-id> | --iscsi-target-name=<iscsi-target-name>][ [--longlist [--client-list=<client-list> | --long-client-list=<long-client-list>] [--resource-list=<resource-list> | --long-resource-list=<long-resource-list>]]

[--rpc-timeout=<rpc-timeout>]



Description:

This command gets iSCSI target information. The iSCSI target ID or iSCSI target name can be specified to get the specific iSCSI target information. The default is to get the information for all of the iSCSI targets.

-c(--client-list) or -C(--long-client-list) is the option to display the assigned client list when -l(--longlist) option is specified.

-r(--resource-list) or -R(--long-resource-list) is the option to display the assigned resource list when -l(--longlist) option is specified.

Assign iSCSI target

iscli assigntoiscsitarget -s <server-name> [-u <username> -p <password>]-v <vdevid> | -g <group-id> | -G <group-name>-r <iscsi-target-id> | -R <iscsi-target-name> [-l <lun>] [-X <rpc-timeout>]

iscli assigntoiscsitarget --server-name=<server-name> [--server-username=<username>--server-password=<password>] --vdevid=<vdevid> | --group-id=<group-id> | --group-name=<group-name> --iscsi-target-id=<iscsi-target-id> | --iscsi-target-name=<iscsi-target-name> [--lun=<lun>] [--rpc-timeout=<rpc-timeout>]

Description:

This command assigns a virtual device or group to an iSCSI target. A virtual device or group (either ID or name) and iSCSI target are required. All virtual devices in the same group will be assigned to the specified iSCSI target if group is specified. If a virtual device ID is specified and it is in a group, an error will be returned.

LUN is optional for a single virtual device and can be used if you want to set a specific LUN. The default is to set the LUN to the next available LUN. It is not a valid option if group is specified.

Unassign iSCSI target

iscli unassignfromiscsitarget -s <server-name> [-u <username> -p <password>] -v <vdevid>-r <iscsi-target-id> | -R <iscsi-target-name> [-f] [-X <rpc-timeout>]

iscli unassignfromiscsitarget --server-name=<server-name> [--server-username=<username>--server-password=<password>] --vdevid=<vdevid> [--iscsi-target-id=<iscsi-target-id> | [--iscsi-target-name=<iscsi-target-name>] [--force] [--rpc-timeout=<rpc-timeout>]

Description:

This command unassigns a virtual device or group from an iSCSI target. Virtual device and iSCSI target are required. -f (--force) option is required when the iSCSI target is assigned to the client and the client is connected or when the virtual device is in a group. An error will be returned if the client is connected and the force option is not specified.

All virtual devices in the same group as the specified virtual device will be unassigned if the force option is specified. An error will be returned if the force option is not specified and the virtual device is in a group.



Delete iSCSI target

iscli deleteiscsitarget -s <server-name> [-u <username> -p <password>]-c <client-name> -R <iscsi-target-name> [-f] [-X <rpc-timeout>]

iscli deleteiscsitarget --server-name=<server-name>[--server-username=<username> --server-password=<password>]--client-name=<client-name> --iscsi-target-name=<iscsi-target-name> [--force][--rpc-timeout=<rpc-timeout>]

Description:

This command deletes an iSCSI target. <client-name> and <iscsi-target-name> are required.

The -f (--force) option is required when the virtual device is assigned to the iSCSI target and the client is connected to the virtual device through the iSCSI target. An error will be returned if the force option is not specified.




Client properties

Set iSCSI client properties

iscli setiscsiclientprop -s <server-name> [-u <username> -p <password>]-c <client-name> [-U <user-list>] [-I <initiator-list>] [-X <rpc-timeout>]

iscli setiscsiclientprop --server-name=<server-name> [--server-username=<username>--server-password=<password>] --client-name=<client-name> [--user-list=<user-list>][--initiator-list=<initiator-list>] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to set iSCSI client properties. <user-list> is in the following format: user1,user2,user3

Specify NONE if you want to remove all of the users that were assigned to the client. e.g.-U NONE

<initiator-list> is in the following format: initiator1,initiator2,initiator3

Set Fibre Channel client properties

iscli setfcclientprop -s <server-name> [-u <username> -p <password>] -c <client-name> [-I <initiator-wwpns>] [-a] [-A] [-X <rpc-timeout>]

iscli setfcclientprop --server-name=<server-name> [--server-username=<username>--server-password=<password>] --client-name=<client-name> [--initiator-wwpns=<initiator-wwpns>] [--enable-VSA] [--enable-AS400] [--rpc-timeout=<rpc-timeout>]

Description:

This command allows you to set Fibre Channel client properties. <client-name> is required.

Use the -a (--enable-VSA) option for Volume Set Addressing.

Use the -A (--enable-AS400) option with the Fibre Channel protocol to support an AS400 client. This option cannot be set if this client is already assigned to virtual devices.

Use the -I (--initiator-wwpns) option to set the initiator WWPNs for the client. An initiator WWPN is a 16-byte hex value. Separate initiator WWPNs with a comma if more than one is specified.

Get client properties

iscli getclientprop -s <server-name> [-u <username> -p <password>] -c <client-name> [-l] [-X <rpc-timeout>]

iscli getclientprop --server-name=<server-name> [--server-username=<username>--server-password=<password>] --client-name=<client-name> [-longlist] [--rpc-timeout=<rpc-timeout>]

Description:

This command gets client properties.



BootIP

Enable BootIP

iscli enablebootip -s <server-name> [-u <username> -p <password>] -c <client-name> -m <mac-address> [-S <0|1 -i <ip-address>>] -b <default-boot> -v <vdevid> [-X <rpc-timeout>]

iscli enablebootip --server-name=<server-name> [--server-username=<username>--server-password=<password>] --client-name=<client-name> --mac-address=<mac-address>[--use-static-ip=<0|1 --ip-address=<ip-address>>] --default-boot=<default-boot>--vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command enables BootIP. <default-boot> must be one of the following values: 0 / 1 / 2

0 = Local boot1 = Windows boot2 = Linux boot

<client-name> is the client that wants to be enabled for the BootIP option.

Use the -S(--use-static-ip) option for static DHCP IP. If its value is 1, <ip-address> is needed and this client will have a static IP from the DHCP service.

<mac-address> is the full hardware address of the network interface card in the client machine. For example:"00:0E:31:25:98:09"

<vdevid> should be the ID of one of the virtual devices assigned to the BootIP client.

Disable BootIP

iscli disablebootip -s <server-name> [-u <username> -p <password>] -c <client-name> [-X <rpc-timeout>]

iscli disablebootip --server-name=<server-name> [--server-username=<username>--server-password=<password>] --client-name=<client-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command disables BootIP. Specify the client name that wants to be disabled.

Get BootIP properties

iscli getbootipproperties -s <server-name> [-u <username> -p <password>] -c <client-name> [-X <rpc-timeout>]

iscli getbootipproperties --server-name=<server-name> [--server-username=<username>--server-password=<password>] --client-name=<client-name> [--rpc-timeout=<rpc-timeout>]

Description:

This command gets BootIP properties. Specify which client to display.



Set BootIP properties

iscli setbootipproperties -s <server-name> [-u <username> -p <password>] -c <client-name> -m <mac-address> [-S <0|1 -i <ip-address>>] -b <default-boot> -v <vdevid> [-X <rpc-timeout>]

iscli setbootipproperties --server-name=<server-name> [--server-username=<username>--server-password=<password>] --client-name=<client-name> --mac-address=<mac-address>[--use-static-ip=<0|1 --ip-address=<ip-address>>] --default-boot=<default-boot>--vdevid=<vdevid> [--rpc-timeout=<rpc-timeout>]

Description:

This command sets BootIP properties. <default-boot> is one of the following values: 0 / 1 / 2

0 = Local boot1 = Windows boot2 = Linux boot

<client-name> is the client that wants to be enabled for the BootIP option.

Use the -S(--use-static-ip) option for static DHCP IP. If its value is 1, <ip-address> is needed and this client will have a static IP from the DHCP service.

<mac-address> is the full hardware address of the network interface card in the client machine. For example:"00:0E:31:25:98:09"

<vdevid> should be the ID of one of the virtual devices assigned to the BootIP client.


DF2112DF2112 User Guide

CallHomeCallHome is a unique DF2112 customer support utility that proactively identifies and diagnoses potential system or component failures and automatically notifies system administrators via email.

Using pre-configured scripts (called triggers), CallHome monitors a set of pre-defined, critical system components (SCSI drive errors, offline device, etc.). With its open architecture, administrators can easily register new elements to be monitored by these scripts.

When an error is triggered, CallHome uses the built-in DF2112 X-ray feature to capture the appropriate information, including the DF2112 event log, as well as a snapshot of the DF2112 appliance’s current configuration and environment. The technical information needed to diagnose the reported problem is then sent to a system administrator.

With CallHome, system administrators are able to take corrective measures within the shortest amount of time, ensuring optimum service uptime and IT efficiency.

ConfigurationTo configure CallHome:

1. In the Console, right-click on your DF2112 server and select Options --> Enable CallHome.

2. Enter general information for your CallHome configuration.

DF2112DF2112 User Guide 413

CallHome

SMTP Server - Specify the mail server that CallHome should use to send out notification emails.

SMTP Port - Specify the mail server port that CallHome should use.

SMTP Username/Password - Specify the user account that will be used by CallHome to log into the mail server.

User Account - Specify the email account that will be used in the “From” field of emails sent by CallHome.

Target Email - Specify the email address of the account that will receive emails from CallHome. This will be used in the “To” field of emails sent by CallHome.

CC Email - Specify any other email accounts that should receive emails from CallHome.

Subject - Specify the text that should appear on the subject line.

Interval - Specify the time period between each activation of CallHome.

3. Enter the contact information that should appear in each CallHome email.


CallHome

4. Set the triggers that will cause CallHome to send an email.

Triggers are the scripts/programs that perform various types of error checking when CallHome activates. By default, MPC includes scripts/programs that check for low system memory, changes to the DF2112 XML configuration file, and relevant new entries in the system log.

The following are the default scripts that are provided:

chkcore.sh 10 (Core file check) - This script checks to see if a new core file has been created by the operating system in the bin directory of DF2112. If a core file is found, CallHome compresses it, deletes the original, and sends an email report but does not send the compressed core file (which can still be large). If there are more than 10 (variable) compressed core files, they will all be deleted.

mdcheck.sh (Software RAID array check) - This script checks to see if the Linux RAID-1 array has failed. If it has failed, CallHome sends an email report.

kfsnmem.sh 10 (DF2112 memory management check) - This script checks to see if the maximum number of memory pages has been set. If not, CallHome sends an email report. If it is set, the script checks the available memory pages. If the percentage is lower than specified percentage (default is 10), CallHome sends an email report.

memchk.sh 5 (Memory check) - This script takes in a percentage as the parameter and checks whether the available system memory is below this percentage. If yes, CallHome sends an email report.

df2112syslogchk.sh (System log check) - This script looks at the system log for specific entries that it needs to report on. This is determined by information specified on the System Log Check and System Log Ignore dialogs. (You will see these dialogs later in this wizard. Once CallHome is enabled, you can


CallHome

modify the information by right-clicking on your DF2112 server and selecting CallHome.) If matches are found, CallHome sends an email report.

df2112ckcfg check df2112.conf (DF2112 configuration check) - This script checks for any changes made to the XML configuration file for DF2112, df2112.conf. If no previous version exists, the script creates a duplicate of the current df2112.conf so that next time the script is run, a comparison can be made. If there is already a file for comparison, the script goes ahead and checks for changes. If changes are found, they are recorded in a file called df2112conf.diff and an email report is sent. The next time changes are found, df2112conf.diff will be renamed to df2112conf.diff.001, and the new changes will replace the content in df2112conf.diff. This process repeats each time new changes are found, with the number at the end of older diff filename incremented.

diskusagechk.sh / 95 (Disk usage check) - This script checks the disk space usage of the root file system. If the percentage is over the specified percentage (default is 95), CallHome sends an email report. You can add multiple diskusagechk.sh triggers for different mount points (for example, /home could be used in another trigger).

defaultipchk.sh eth0 10.1.1.1 (NIC IP address check) - This script checks that the IP address for the specified NIC matches what is specified here. If it does not, CallHome sends an email report. You can add multiple defaultipcheck.sh triggers for different NICs (for example eth1 could be used in another trigger). Be sure to specify the correct IP address for each NIC.

df2112status.sh (DF2112 status check) - This script calls “df2112 status” and checks if any module of DF2112 has stopped. If so, CallHome sends an email report.

If you need to modify an existing script or create a new script/program, refer to ‘Script/program trigger information’ for more information.


CallHome

5. Select the components that will be included in the X-ray.

Note: Because of its size (minimum of 2 MB), the X-ray file is not sent by default with each notification email. It will, however, be available, should the system administrator require it.

System Information - When this option is selected, the X-ray creates a file called info which contains information about the entire system, including: host name, disk usage, operating system version, mounted file systems, kernel version, CPU, running processes, IOCore information, and memory.

DF2112 Configuration - This information is retrieved from the /usr/local/df2112/etc/<hostname> directory. All configuration information (df2112.conf, df2112.dat, DF2112SNMP.conf, etc.), except for shared secret information, is collected.

SCSI Devices - SCSI device information. This information is included in the info file.

DF2112 Virtual Device - Virtual device information. This information is included in the info file.

Fibre Channel - Fibre Channel information.

Log File - The Linux system message file, messages, is located in the /var/log directory. All DF2112 Server messages, including status and error messages, are stored in this file.

Loaded Kernel - Loaded kernel modules. This information is included in the info file.

Network Configuration - Network configuration information is included in the info file.


CallHome

Kernel Symbols - This information is collected in the event it will need to be used for debugging purposes.

Core File - The /usr/local/df2112 path will be searched for any core files that might have been generated to further help in debugging reported problems.

DF2112 NAS Mount Path - This information is included in the info file.

Scan Physical Devices - Physical devices will be scanned and information about them will be included.

6. Indicate the terms that should be tracked in the system log by CallHome.

The system log records important events or errors that occur in the system, including those generated by DF2112.

This dialog allows you to rule out entries in the system log that have nothing to do with DF2112, and to list the types of log entries generated by DF2112 that CallHome needs to examine. Entries that do not match the entries entered here will be ignored, regardless of whether or not they are relevant to DF2112.

The trigger for monitoring the system log is df2112syslogchk.sh. To inform the trigger of which specific log entries need to be captured, you can specify the general types of entries that need to be inspected by CallHome. On the next dialog, you can enter terms to ignore, thereby eliminating entries that match these general types, yet can still be disregarded. The resulting subset contains all entries for which CallHome needs to send out email reports.

Each line is a regular expression. The regular expression rules follow the pattern for AWK (a standard Unix utility).

Note: By default, the system log file is included in the X-ray file which is not sent with each notification email.


CallHome

7. Indicate which categories of internal messages should not be included.

By default, all categories are ignored. If a category is checked you will still receive error messages but will not receive detailed internal messages.

Select the Customized System Log Ignore tab to exclude system log entries that were included on the previous dialog. You can enter terms to ignore, thereby eliminating entries that will cause CallHome to send out email reports.

Each line is a regular expression. The regular expression rules follow the pattern for AWK (a standard Unix utility).

8. Confirm all information and then click Finish to enable CallHome.


CallHome

Modifying CallHome properties

Once CallHome is enabled, you can modify the information by right-clicking on your DF2112 server and selecting CallHome.

Click on the appropriate tab to update the desired information.


CallHome

Script/program trigger information

CallHome uses script/program triggers to perform various types of error checking. By default, MPC includes several scripts/programs that check for low system memory, changes to the DF2112 XML configuration file, and relevant new entries in the system log.

Custom emaildestination

You can specify an email address to override the default Target Email or a text subject to override the default Subject. To do this:

1. Right-click on your DF2112 server and select CallHome --> Trigger tab.

2. For an existing trigger, highlight the trigger and click Edit.

For a new trigger, click Add.

Note: If you specify an email address, it overrides the return code. Therefore, no attachment will be sent, regardless of the return code.

New script/program

The trigger can be a shell script or a program (Java, C, etc.). If you create a new script/program, you must add it in the Console, so that CallHome knows of its existence.

To do this:

1. Right-click on your DF2112 server and select CallHome --> Trigger tab.

2. Click Add.

Return codes Return codes determine what happens as a result of the script’s/program’s execution. The following return codes are valid:

• 0: No action is required and no email is sent.• 1: CallHome attaches all files in $ISHOME/etc and $ISHOME/log to the

email.• 2: CallHome sends the X-ray file as an attachment (which includes all files in

$ISHOME/etc and $ISHOME/log). Because of its size (minimum of 2 MB), we do not recommend attaching the X-ray file with each notification email.

• 3: CallHome sends email without any attachments.

The $ISHOME/etc directory contains a DF2112 configuration file (containing virtual device, physical device, HBA, NAS, database agent, etc. information). The $ISHOME/log directory contains CallHome logs (containing events and output of triggers).

Output fromtrigger

In order for a trigger to send useful information in the email body, it must redirect its output to the environment variable $DF2112CLHMLOG.


CallHome

Sample script The following is the content of the DF2112 status check trigger, df2112status.sh:

#!/bin/shRET=0if [ -f /etc/.is.sh ]then . /etc/.is.shelse echo Installation is not complete. Environment profile is missing in /etc. echo exit 0 # don't want to report error here so have to exit with error code 0fi$ISHOME/bin/df2112 status | grep STOPPED >> $DF2112CLHMLOGif [ $? -eq 0 ] ; then RET=1fiexit $RET

If any DF2112 module has stopped, this trigger generates a return code of 1 and sends an attachment of all files under $ISHOME/etc and $ISHOME/log.


DF2112 User Guide

TroubleshootingThis section helps you through some common problems and issues you may encounter when you set up and run the DF2112 storage network.

SCSI adapters and devices

Since DF2112 relies on SCSI devices for storage, it is often helpful to be able to discover the state of the SCSI adapters and devices locally attached to the DF2112 Server. Verification requires that the administrator be logged into the DF2112 Server. Refer to ‘Log into the DF2112 Server’.

To verify the SCSI adapters and verify that the DF2112 Server is up, run the lsmod utility. lsmod displays all loaded modules, including the SCSI device drivers. If your DF2112 Server is up, you should see the kdf2112 (DF2112 kernel module) and krdup modules listed. You will also see the number of drives attached to each module.

If you do not see the appropriate driver for your SCSI adapter, it may not have been loaded properly or it may have been unloaded.

Once it is determined that the SCSI adapter and driver are properly installed, the next step is to check to see if the individual SCSI devices are accessible on the SCSI bus. To check to see what devices are recognized by the DF2112 Server, execute the following command on a DF2112 Server.

These commands display the SCSI devices attached to the DF2112 Server. For example, you will see something similar to the following:

If the operating system cannot see a device, it may not have been installed properly or it may have been replaced while the DF2112 Server was running. If the Server was not rebooted, Linux will not recognize the drive because it does not have “plug-and-play” capabilities. Instead, you must do the following:

lsscsi

[0:0:0:0] disk 3ware Logical Disk 0 1.2 /dev/sda[0:0:1:0] disk 3ware Logical Disk 1 1.2 /dev/sdb[2:0:1:0] disk IBM-PSG ST318203FC !# B324 -[2:0:2:0] disk IBM-PSG ST318203FC !# B324 -[2:0:3:0] disk IBM-PSG ST318304FC !# B335 -


Troubleshooting

Replace aphysical disk

1. You MUST remove the SCSI device from the Linux OS by executing:




Linux SANClient

To ensure that the SCSI drivers are loaded on a Linux machine, type the following command for Turbo Linux:

For example: modprobe aic7xxx

For Caldera Open Linux, type:

LUNs greaterthan zero

By default, Linux will not automatically discover devices with LUNs greater than zero. You must either manually add these devices or you can edit your modules.conf file to automatically scan them. To do this:

1. Type the following command to edit the modules.conf file:

2. If necessary, add the following line to modprobe.conf:

where x is the LUN number that you want the server to scan up to.

3. After exiting from vi, make a new image file.

For Red Hat, use:mkinitrd newimage.img X

where 'X' is the kernel version (such as 2.4.21-df2112) and ‘newimage’ can be any name.

For SUSE, use:mkinitrd -k vmlinuz file -i newimage.img

where vmlinuz is the kernel image for which the initrd file is created (the vmlinuz file is located in /boot).

4. Make a new entry to point to the new .img file you created in the step above and make this your default.

For Red Hat, use /boot/grub/grub.conf

echo "scsi remove-single-device x x x x">lsscsi


modprobe <SCSI card name>

insmod scsi_mod

vi /etc/modprobe.conf

option scsi_mod max_luns=x


Troubleshooting

For SUSE, use /boot/grub/menu.lst

5. Save and close the file.

6. Reboot the machine so that the scan will take place.

7. Verify that all LUNs have been scanned.

For Red Hat, use cat /proc/scsi/scsiFor SUSE, use lsscsi


Troubleshooting

Console launch

The Console might not launch under the following conditions:

• Systems with display settings configured to use 16 colors. • The install path contains characters such as !, %, {, }. • “Font specified in font.properties not found” message is displayed. This

indicates that the jdk font.properties file is not properly set for the Linux operating system. To fix this, change the font.properties files to get the correct symbol font name. To do this, replace all lines containing “--symbol-medium-r-normal--*-%d-*-*-p-*-adobe-fontspecific” with “--standard symbols l-medium-r-normal--*-%d-*-*-p-*-urw-fontspecific”.

• The Console needs to be run from a directory with “write” access. Otherwise, the host name information and message log file retrieved from the DF2112 Server will not be able to be saved to the local directory. As a result, the Console will display event messages as numbers and Console options will not be able to be saved.


Troubleshooting

Logical resources

The following table describes the icons that are used to show the status of logical resources:

If you see one of these icons, check through the tabs to see what the specific problem is.

Event Log

If the Event Log displays event messages as numbers rather than text, check to make sure that there is at least 5 MB of free space on the file system to which the Console is installed. If not, free up some space.

Console login

Verify that the operating system on your DF2112 appliance is using either the MD5 or DES algorithm for the user password hash. This should have been set during your installation. If you are using the Blowfish algorithm, you need to change it. To do this, use the YaST program (Security and Users --> Security settings --> Next --> Password Encryption Method --> MD5 --> Finish). Be sure to use the passwd command to reset the root password.

If you still have difficulty connecting to a DF2112 Server from a Console, you must establish that the two machines have connectivity through the Ethernet network. To do this, right-click on a server and select Connectivity Test.

By running this test, you can determine if your network connectivity is good. If it is not, the test may fail at some point. You should then check with your network administrator to find out what the problem is. Refer to ‘Network connectivity’ below.

Icon Description

This icon indicates a warning, such as:• Virtual device offline (or has incomplete segments)• Mirror is out of sync• Mirror is suspended• TimeMark rollback failed• Replication failed• One or more supporting resources is not accessible (SafeCache, CDP,

Snapshot resource, HotZone, etc.)

This icon indicates an alert, such as:• Replica in disaster recovery state (after forcing a replication reversal)• Cross mirror need to be repaired• Primary replica is no longer valid as a replica• Invalid replica


Troubleshooting

Network connectivity

DF2112 Servers, Clients and Consoles are all attached to one another through an Ethernet network. In order for all of the components to work properly together, their network connectivity should be configured properly.

To test connectivity between machines (Servers, Clients and Consoles,) there are several things that can be done. This example shows a user testing connectivity from a Client or Console to a Server named “knox”.

To test connectivity from one machine to the DF2112 Server, you can execute the ping utility from a command line prompt. For example, if your DF2112 Server is named “knox”, execute:

If the DF2112 Server is running and attached to the network, you should receive a response like this:

If the Server is not available, you may get a response like this:

This means that either the machine is not running, or is not properly attached to the network.

If you get a response like this:

ping knox

Pinging knox [10.1.1.99] with 32 bytes of data:

Reply from 10.1.1.99: bytes=32 time<10ms TTL=255Reply from 10.1.1.99: bytes=32 time<10ms TTL=255Reply from 10.1.1.99: bytes=32 time<10ms TTL=255Reply from 10.1.1.99: bytes=32 time<10ms TTL=255

Ping statistics for 10.1.1.99: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging knox [10.1.1.99] with 32 bytes of data:

Request timed out.Request timed out.Request timed out.Request timed out.Ping statistics for 10.1.1.99: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

Unknown host knox.


Troubleshooting

This means that your machine cannot find the DF2112 Server by name. There could be two reasons for this. First, it may be that the DF2112 Server is not running or connected to the network, and therefore has not registered itself to the name service on your network.

Second, it may be that the DF2112 Server is running, but is not known by name, possibly because the name service, such as DNS, is not running, or your machine is not referring to the proper name service.

Please refer to your network’s reference material on how to configure your network’s name service.

If your DF2112 Server is available, you can execute the following command on the Server to verify that the DF2112 ports are both up:

Both ports 11576 and 11577 should be listed. In addition, port 11576 should be “listening”.

Linux SANClient

You may see the following message when executing ./df2112client start or ./df2112client restart if the Linux Client cannot locate the DF2112 Server on the network:

Creating DF2112 Client Device [FAILED]Failed to connect to DF2112 Server 0, -1

To resolve, restart the services on both the DF2112 Server and the Linux Client.

Jumbo frames support

To determine if a machine supports jumbo frames, use the ping utility from a command line prompt to ping with the pack size. If your DF2112 Server is named “knox”, execute one of the following commands:

On Linux systems:

On Windows 2000 systems:

Client connectivity

Problems connecting Clients to their SAN Resources may occur due to several causes, including network configuration and DF2112 Server configuration.

netstat –a |more

ping –s 8000 knox

ping –l 8000 knox


Troubleshooting

• Check the General Info tab for the Client in the Console to see if the Client has been authenticated. In order for a Client to be able to access storage, you must establish a trusted relationship between the Client and Server and you must assign storage resources to the Client.

• If you make any Client configuration changes in the Console, you must restart the Client in order for the changes to take effect.

• Clients may not achieve the maximum throughput when writing over gigabit. If you are noticing slower than expected speeds when writing over gigabit, you can do the following:• Turn on TCP window scaling on the DF2112 server: /proc/sys/net/ipv4/tcp_window_scaling

1 is on. 0 is off.

By default, it should be 1 for SUSE 9.3. But if it is not, you can edit /etc/sysctl.conf and add:net.ipv4.tcp_window_scaling = 1

• On Windows, go to Run and type regedit. Add the following:[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]"Tcp1323Opts"=dword:00000001"GlobalMaxTcpWindowSize"=dword:01d00000"TcpWindowSize"=dword:01d00000

To see if the DF2112 Client has connectivity to the DF2112 Server over the Ethernet network, refer to ‘Network connectivity’.

Windows Client

Problem Cause/Resolution

You get a message “Cannot stop client service” or “There was a problem deleting the server” in the Client Monitor.

The storage was not removed properly from the server and you attempted to stop the Client or delete the Server from the Client. Restart the Server and, if necessary, delete it from the tree.

You can see the assigned SAN Resources in the Client Monitor, but the disks do not get mounted or connected.

One SAN Resource for each Windows SAN client must have a LUN of 0. Otherwise, the Client Monitor will display the assigned resource(s) but the operating system will not see the devices assigned to the SAN client.

You cannot see a newly assigned device. If you reassign a different device with the same LUN, you must restart the Client Monitor in order to access the newly assigned device.

The SAN Client hangs when the DF2112 storage containing its virtual disk goes offline.

To prevent the DF2112 Client from hanging when there is a storage problem on the DF2112 server, change the default I/O error response sense key from "medium error" to "unit not ready" by the running the following command: echo "df2112 set-parameter default-io-error-sense-key 2 4 0" > /proc/df2112/df2112


Troubleshooting

Windows client debug information

You can configure the amount of detail about the DF2112 Client’s activity and performance that will be written to the Windows Event Viewer.

In addition, you can enable a system tracer. When enabled, the trace information will be logged to a file called FSNTrace.log located in the \DataFRAME® 2112\Logs directory.

1. To filter the events and/or configure the tracer, select Tools --> Options.

2. To filter the events being written to the Event Viewer, select one of the levels in the Log Level field.

Note that regardless of which level you choose, there are several events that will always be written to the Event Viewer (driver not loaded, service failed to start, service started, service stopped).

Five levels are available for use:• Off – No activity will be recorded. • Errors only – Only errors will be recorded.• Brief – Errors and warnings will be recorded.• Detailed – (Default) Errors, warnings and informational messages will be

recorded.• Trace – This is the highest level of activity tracing. Debugging messages will

be written to the trace log. In addition, all errors, warnings and informational messages will be recorded in the Event Viewer.

3. If you select the Trace level, specify which portions of the DF2112 Client will be traced.

Warning: Adjusting these parameters can impact system performance. They should not be adjusted unless directed to do so by MPC technical support.


Troubleshooting

Clients with SAN/IP or iSCSI protocol

Linux SAN Client


(SAN/IP and/or iSCSI protocol) After rebooting, the client loses its file shares.

This is a timing issue. To reconnect to shares:Open a command prompt and type the following for commands:net stop browsernet stop servernet start servernet start browserYou may want to create a batch file to do this.

(iSCSI protocol) Intermittent iSCSI disconnections on the client. or The client cannot see the disk after failover.

The Microsoft iSCSI initiator has a default retry period of 60 seconds. Changing it to 300 seconds will sustain the disk for five minutes during network disconnection events, meaning applications will not be disrupted by temporary network problems (such as during a failover or recovery). This setting is changed through the registry. 1. Go to Start --> Run and type regedit.2. Find the following registry key:HKEY_LOCAL_MACHINE\system\CurrentControlSet\control\class\4D6E97B-xxxxxxxxx\<iscsi adapter interface>\parameters\




The Microsoft iSCSI initiator fails to connect to a target.

The Microsoft iSCSI initiator can only connect to an iSCSI target if the target name is no longer than 221 characters. It will fail to connect if the target name is longer than this.


You see the following message when viewing the Client's current configuration: On command 12 data received 36 is not equal to data expected 256.

This is an informational message and can be ignored.


Troubleshooting

NetWare SAN Client

The following tools are available for troubleshooting problems with the NetWare SAN Client:

• ISCMD command log: Run the ISCMD command with option DEBUG=2. The debugging message will be written to the log file ISCMD.LOG located in the directory SYS:\SYSTEM. For example: ISCMD Start Server=serverIPAddress Debug=2

• DF2112 SAN client trace log: Run the command SANDRV +debug +ip3 on the NetWare System Console. The trace log will be written to the log file TRACELOG.XML located in the directory SYS:\SYSTEM.

You see the following message when executing ./df2112client start or ./df2112client restart:Creating DF2112 Client Device [FAILED]Failed to connect to DF2112 Server 0, -1

The DF2112 SAN Client cannot locate the DF2112 Server on the network. To resolve this, restart the services on both the DF2112 Server and the Linux Client.

You see the following message continuously:SCSI: Aborting due to timeout: PID ######…..

You cannot un-assign devices while a Linux client is accessing those devices (i.e. mounted partitions).



Perform an iscmd addserver server= and it shows that it connects and is communicating, but when an iscmd start server= is performed an error message is received that the server is not authenticated and it will NOT start. Performing an iscmd showserver shows it’s not connected to the server.

1. Stop the client service with # sanoff2. On the NetWare server, run # regedit to enter the registry editor.3. # cd Software4. # rd DataFRAME5. Go to the DF2112 Console to unassign the devices from the client and delete the client.6. Add the client to the server with the # iscmd addserver command. If the client can not be authenticated even if a correct password is used, you need to reset it with passwd command in Linux.7. Assign devices to the client using the exact same LUN order as before.8. Connect to the server from the NetWare client.


Troubleshooting

DF2112 Server

X-ray of the DF2112 Server

X-ray is a diagnostic tool used by your Technical Support team to help solve system problems. Each X-ray contains technical information about your server, such as server messages and a snapshot of your server's current configuration and environment. You should not create an X-ray unless you are requested to do so by your Technical Support representative.

To create the X-ray file:

1. In the Console, right-click on the Server and select X-ray.

2. Based on the discussion with your Technical Support representative, select the options you want to include and set the file name.

Specific problems

Filter out and includeonly DF2112 messagesfrom the System Event

Log.


After using rpm –e to uninstall the DF2112 Server, the /df2112 directory and its subdirectories remain.

In order to remove them, execute the following command from the /usr/local directory:rm –rf df2112

You changed DF2112 Server IP addresses using yast or another third-party utility and it did not update the information correctly.

If you need to change DF2112 Server IP addresses, you must make these changes through the Console using System Maintenance --> Network Configuration.


Troubleshooting

Failover

Replication


After restarting failover servers, DF2112 starts but will not come back online.

This can happen if: • There was a communication problem (i.e.network

error) between the servers• Both failover servers were down and then only one is

brought up• If failover was suspended and you restart one of the

serversTo resolve this:1. At a Linux command prompt, type sms to determine if the system is in a ready state. 2. As soon as it becomes ready, type the following: df2112sm.sh recovery

After failover, when you connect to the newly-promoted primary server, the failover status is not correct.

You are connecting to the server with an IP address that is not part of the failover configuration or with the heartbeat IP address and you are seeing the status from before the failover. You should only use those IP addresses that are configured as part of the failover configuration to connect to the Server in the Console.

The following error message appears in the log for an ext3 NAS resource after failover/failback: “JBD: barrier-based sync failed on vbdi8 -disabling barriers”

The Journaling Block Device (JBD) provides generic filesystem journaling functions for Linux. This message is a kernel warning that means your disk does not support barriers. The action is retried with barriers disabled. No action is necessary as long as the retry action succeeds.


Replication is set to use compression but replication fails. You may see error messages in the syslog like this:__alloc_pages: 4-order allocation failed (gfp=0x20/0)IOCORE1 expand_deltas, cannot allocate for 65536 bytesIOCORE1 write_replica, error expanding deltas, return -EINVALIOCORE1 replica_write_parser, server returned -22IOCORE1 replica_read_post, stopping because status is -22

Compression requires 64K of contiguous memory. If the memory in the DF2112 server is very fragmented, it will fail to allocate 64K. When this happens, replication will fail.

You perform a role reversal and get the following error:"The group for replica disks on the target server is no longer valid. Reversal cannot proceed".

If you attempt to perform a role reversal on a resource that belongs to a non-replication group, the action will fail. To resolve this issue, remove the resource from the group and perform the role reversal.

Replication fails. Do not initiate a TimeMark copy while replication is in progress. Doing so will result in the failure of both processes.


Troubleshooting

TimeMark

SafeCache

SNMP


TimeMark rollback of a raw device fails. Do not initiate a TimeMark rollback to a raw device while data is currently being written to the raw device. The rollback will fail because the device will fail to open.

TimeMark copy fails. Do not initiate a TimeMark copy while replication is in progress. Doing so will result in the failure of both processes.


A disk containing a cache resource for a NAS Resource has failed (for example, the cable was unplugged).

If a disk containing a cache resource for a NAS Resource has failed, you must perform File System Checking on the cache resource once it has been restored. To do this, right-click on the NAS resource enabled with SafeCache --> File System Checking.Note that File System Checking should only be initiated once the cache is restored; Otherwise the checking will fail with the message "Failed to Check File System".

A physical resource has failed (for example, the disk was unplugged or removed) but the resources in the SafeCache group are not marked offline.

If a physical resource has failed prior to the cache being flushed, the resources in the SafeCache group will not be marked offline until after a rescan has been performed.

The primary resource has failed and you attempt to disable the cache, but the cache is unable to flush data back to the primary resource. A dialogue box displays “N/A” as the number of seconds needed to flush the cache.

The cache is unable to flush the data due to a problem with data transfer from the cache to the primary resource.

The SafeCache resource has failed and you attempted to resume the SafeCache. The resume appears to be successful, however, the client cannot write to the virtual device.

The client can only write to the virtual device when the SafeCache resource is restored. However, the SafeCache remains in a suspended state. You should suspend and resume the cache from the Console to return the cache status to normal and operational.


The trap, ucdShudown, appears as a raw message at the management console.

When stopping the SNMP daemon, the daemon itself will issue a trap, ucdShudown. You can ignore the extra trap.


Troubleshooting

Command line interface

Service enabled devices

Snapshot resources


Failed to resolve DF2112 server to a valid IP address.Error: 0x09022004

The DF2112 Server hostname is not resolvable on both the client side and the server side. Add the server name to the hosts file to make it resolvable or use the IP address in commands.


An unassigned physical device does not show the "Service Enabled Device" option when you try to set the device category.

If you see that the GUID for this device is “fa1cff00...”, the device cannot be supported as a service enabled device. This is because the device does not support the mandatory SCSI page codes that are used to determine the actual GUID for the device.

A Service enabled device (SED) is marked "Incomplete" on the primary server and the client that normally connects to the SED resource has lost access to the disk.

In a failover configuration, you should not change the properties of a SED used by a primary server to "Unassigned" on the secondary server. If this occurs, you should do the following:1. Delete the offline SAN resource.2. Service-enable the physical disk.3. Re-create the SAN resource.4. Re-assign the SAN resource back to the client.


Snapshot resources are marked off-line. Snapshot resources will be marked off-line if the physical resource they have been created from is disconnected from a single server in a failover set prior to a failing over to the secondary server.


Troubleshooting

Physical resources

Block devices

Virtual device expansion


A physical disk becomes inaccessible or is offline. While it shows up in the operating system device list, it cannot be used with DF2112.

If a physical disk configured with any of the following resources (SafeCache, Snapshot, CDP, CDR or HotZone) becomes inaccessible or is offline, it may show up in the operating system device list. In order to use it with DF2112, you need to restart DF2112 once you have corrected the storage problem. A rescan alone is not sufficient.


You changed the hostname of the DF2112 Server and all block devices are marked offline and seen as foreign devices

You cannot change the hostname of the DF2112 Server if you are using block devices.


A virtual device fails to expand. If a user has a set quota and he allocates a disk greater than his quota and then enables any type of feature that uses auto-expansion, such as Snapshot Resource or CDP, those specific resources will not expand, because the quota has been exceeded.


DF2112 User Guide

IndexAAccess control

Groups 228SAN Client 62SAN Resources 93Storage pools 70

Access rightsGroups 228IPStor Admins 44IPStor Users 44SAN Client 62SAN Resources 93

AccountsManage 43

ACSLChange 61

Activity Log 36Adapters

Rescan 54Administrator

Management 43After client assignment 89AIX Client

Delete SAN Resource 93Expand virtual device 92SAN Resource re-assignment 84

Alias 56, 136APC PDU 155, 159Architecture 15Authentication 131Authorization 131Auto Save 32, 40

BBackup

Command Line Interface 387dd command 296To tape drive 296ZeroImpact 293

Bandwidth 39Block devices

Troubleshooting 438BMC Patrol

SNMP integration 332Statistics 333View traps 333

BootIP

Command Line Interface 411

CCA Unicenter TNG

Launch IPStor Console 328SNMP integration 327Statistics 328View traps 328

CacheCache resource 279Write 59

Cache resourceCreate 279Disable 282Enlarge 282Suspend 282

CallHome 413Configuration 413Exclude system log entries 419Include system log entries 418Modifying properties 420Signature 414System log check 418System log ignore 419Triggers 415, 421

Custom email destination 421New script 421Output 421Return codes 421Sample script 422

X-ray 417CDP

Properties 41CDP journal

Add tag 240Expansion policies 235Mirror 240Protect 240Recover data 244Status 238Tag 240, 245Visual slider 244

CHAP passwordChange 104

CLITroubleshooting 437

Client


Index

AddiSCSI 104

AIXDelete SAN Resource 93Expand virtual device 92SAN Resource re-assignment 84

AssignmentSolaris 89Windows 89

Bandwidth 39Definition 16HP-UX

Delete SAN Resource 93Installation 21

Linux 22Windows 21

iSCSI 102Linux

Expand virtual device 92NetWare

Install 26Pre-installation 21QoS 39Solaris 89

Expand virtual device 92Troubleshooting 429Windows 89

Expand virtual device 92Command Line Interface 336, 397

Backup 387BootIP 411Cache resources 361Client properties 410Commands 338Common arguments 337Event Log 403Failover 404Group 390Installation and configuration 336iSCSI targets 407Login/logout IPStor Server 338Mirroring 354Physical devices 397Replication 367Report Data 401Server configuration 405Snapshot Copy 365Snapshot Resource 358TimeMark 374Usage 336

Users and passwords 406Virtual devices

SAN Client commands 351Server commands 340

X-ray 400Community name

Changing 335Compression

Replication 259Configuration repository 32, 150

Mirror 150Configuration wizard 28Connectivity 46Console

Administrator Management 43Change password 46Connect to server after failover 152Connectivity 46Custom menu 64Definition 16Discover IPStor Servers 27, 31Import a disk 55Installation 19

Installation verification 20Linux 20Solaris 20Windows NT, XP, or 2000 19

IPStor Server 31Log 63Logical Resources 58NAS Clients 63Options 63Physical Resources 52Pre-installation 19Replication 60Rescan adapters 54SAN Clients 61Save/restore configuration 32Search 30Server properties 35Start 27System maintenance 48Troubleshooting 426User interface 30

Continuous replication 253, 262Enable 256Resource 263

Cross mirrorCheck resources & swap 164Configuration 147


Index

Recover from disk failure 164Requirements 144Re-synchronize 164Sample configuration 140Swap 139Verify & repair 164

DData access 130Data migration 74Data protection 212dd command 296Debugging 431Devices

Failover 137Scan LUNs greater than zero 424

Direct devices 74Creating 75, 81, 399

Disaster recoveryImport a disk 55, 398Replication 252Save/restore configuration 32

DiskForeign 55, 398Import 55, 398Replace a physical disk 188, 211System 53

Disk stripingConfiguration 291Requirements 291

EEncryption

Replication 259Event Log 31, 110

Command Line Interface 403Export 112Filter information 111Print 112Refresh 112Sort information 111Troubleshooting 427

Expand virtual device 90Linux clients 92Solaris clients 92Troubleshooting 438Windows 2000 Dynamic disks 92Windows clients 92

Export data

From reports 115

FFailover 134, 139

And Mirroring 174, 191And NAS 174Asymmetric 140, 147Auto Recovery 162, 170Auto recovery 163Check Consistency 171Client recovery 162Command Line Interface 404Configuration 142Connect to primary after failover 152Consistency check 171Convert to mutual failover 169Cross mirror

Check resources & swap 164Configuration 147Recover from disk failure 164Requirements 144Re-synchronize 164Sample configuration 140Swap 139Verify & repair 164

Exclude physical devices 170Fix failed server after failover 163Force a takeover 172Heartbeat monitor 137Intervals 170Manually initiate a recovery 172Mutual failover 139Network connectivity failure 136Paths 140Physical device change 169Power control 158

APC PDU 155, 159HP iLO 155, 158IPMI 155, 159RPC100 155, 158SCSI Reserve/Release 155, 159

Primary/Secondary Servers 139Recovery 139, 162, 170Remove configuration 173Replication note 276Requirements 142

Clients 143Cross mirror 144General 142


Index

Shared storage 144Self-monitor 137Server changes 169Server failure 137Setup 146Status 161Storage device failure 137Storage device path failure 136Subnet change 169Suspend/resume 172Symmetric 140, 147TimeViews 174Troubleshooting 435Verify physical devices match 171

Foreign disk 55, 398

GGlobal options 268Group

Command line interface 390Groups 226

Access control 228Add resources 229Create 226Replication 227

GUID 56, 59

HHalt server 49High availability 134Hostname

Change 29, 49HotZone 283

Configure 284Disable 290Prefetch 284Read Cache 283Status 289Suspend 290

HP iLO 155, 158HP OpenView

SNMP integration 324HP-UX Client

Delete SAN Resource 93

IIBM Tivoli NetView

SNMP integration 329Import

Disk 55, 398Inquiry string

Service enabled devices 81Installation

Connect IPStor hardware 17General installation sequence 17IPStor Console 19

Installation verification 20Linux 20Pre-installation 19Solaris 20Windows NT, XP, or 2000 19

IPStor SAN Client 21Linux 22Pre-installation 21Windows 21

IPStor Server 18Pre-installation 18

SNMPBMC Patrol 332CA Unicenter TNG 327HP OpenView 324IBM Tivoli NetView 329

IP Trunking 298Bar Graph 308Changing Breakout Details 309Changing Format 309Changing format 308Changing Interval 308Console 304Current Selection bar 307Current statistics 307Current status 306Device Breakout 309Device Totals 307Installing

Linux 299Java Console 305Jumbo frames 303Load on boot-up 303nexconfig 310

Navigation keys 314nexcui 304nexjui 305Setting IP Address of Server 310Throughput Totals 308Uninstalling 314Unloading 310Using 304

IPMI 29, 50, 155, 159


Index

Config 50Filter 51Monitor 50

IPStorArchitecture 15Benefits 14Components 16Console 16Console installation 19, 20Licensing 34NAS Client 16SAN Client 16SAN Client installation 21, 22Server 16Server installation 18What is? 13

IPStor AdminsAccess rights 44

IPStor ServerAuthentication 131Authorization 131Checking physical resources 98Checking processes 97Connect in Console 27Definition 16Discover 27, 31Import a disk 55, 398Logging into 96Network configuration 48Properties 35Save/restore configuration 32, 405Scan LUNs greater than zero 424Starting 94Statistics 99telnet access 96Troubleshooting 434Uninstalling 101X-ray 434

IPStor UsersAccess rights 44

ipstorconsole.log 63iSCSI Client

Failover 108, 143Troubleshooting 432

iSCSI Target Mode 102CHAP logon

Change 104Initiators 102Targets 102

WindowsAdd iSCSI client 104Disable 109Enable 103Mobile client 104Stationary client 104

ismonStatistics 99

JJumbo frames 17, 49, 429

IP Trunking 303

KKeycodes 34

LLicensing 28, 34Linux Client

Expand virtual device 92Troubleshooting 432

Local Replication 252Logical Resources 58

Expand 90Logical resources

Icons 59, 427Status 59, 427

Logs 110Activity log 36Console 63Event log refresh 63ipstorconsole.log 63

LUNScan LUNs greater than zero 424

MMenu

Customize Console 64Microscan 39, 259, 268Migrate

Data 74Drives 74

Mirroring 175And Failover 174, 191CDP journal 240Command Line Interface 354Configuration 177Configuration repository 150Expand primary disk 189


Index

Fix minor disk failure 187Global options 191Monitor 182Performance 38, 191Promote the mirrored copy 186Properties 191Rebuild 189Recover from failure 187Remove configuration 191Replace a physical disk 188Replace disk in active configuration 187Replace failed disk 187Replication note 276Requirements 177Resume 190Resynchronization 39, 183, 191Setup 177Snapshot resource 220Status 185Suspend 190Swap 186Synchronize 189

MTU 49Multipathing 315

Aliasing 56, 320Autopathing 318Load distribution 316Path management 317Path switching 316Persistent binding 318Preferred paths 316SCSI aliasing 320

NNAS

And Failover 174Troubleshooting 435Windows clients cannot access shares 435

NAS ClientDefinition 16

NAS Clients 63Near-line mirroring 192

After configuration 202Configuration 193Expand primary disk 207Fix minor disk failure 210Global options 208Monitor 197Overview 192

Performance 208Properties 208, 209Rebuild 207Recover data 204Recover from failure 210Remove configuration 209Replace a physical disk 211Replace disk in active mirror 210Replace failed disk 210Requirements 193Resume 208Re-synchronization 198, 208Rollback 205Setup 194Status 203Suspend 208Swap 207Synchronize 207Throughput control 199

NetViewSNMP integration 329Statistics 331

NetWare ClientInstallation 26Troubleshooting 433

Network configuration 29, 48Network connectivity 428

Failure 136NNM

SNMP integration 324Statistics 325

PPasswords

Add/delete administrator password 43Change administrator password 43, 46

PatchApply 47Rollback 47

Path failure 136Performance 277

Mirror 38Mirroring 191Near-line mirroring 208Replication 38, 268

Persistent bindingAutopathing 318

Physical devicePrepare 54


Index

Rename 54Repair 57Test throughput 56

Physical resources 52, 71, 399Checking 98Icons 53Troubleshooting 438

Ports 132Prefetch 284Prepare disks 54, 75

QQoS 39Quality of service 39Quota

Group 45, 46User 44, 46

RRAID 0 291Reboot server 49Recover data with TimeView 244Remote Replication 252Rename

Physical device 54Repair

Paths to a device 57Replica resource

Protect 263Replication 268

Assign clients to replica disk 269Change configuration options 271Command Line Interface 367Compression 259Configuration 254Console 60Continuous 253Continuous replication resource 263Delta 253Encryption 259Expand primary disk 275Failover note 276First replication 262Force 272How it works 253Local 252Microscan 39, 259, 268Mirroring note 276Performance 38, 268

Parameters 268Policies 257Primary disk 252Promote 269Recover files 271Recreate original configuration 270Relocate replica 274Remote 252Remove configuration 275Replica disk 252Requirements 254Resume schedule 272Reversal 270, 273Setup 254Start manually 272Status 265Stop in progress 272Suspend schedule 272Switch to replica disk 269Throttle 39, 268TimeMark note 276TimeMark/TimeView 271Timeout 39, 268Troubleshooting 435

Reports 113Client Throughput 118Command Line Interface 401Creating 113Disk Space Usage 124Export data 115Filtered Server Throughput 116NAS Resources Usage 124Physical Resource Allocation 126Physical Resources Allocation 125Physical Resources Configuration 124SAN Client Usage Distribution 122SAN Client/Resources Allocation 126SAN Resource Usage Distribution 123SAN Resources Allocation 127SCSI Channel Throughput 119SCSI Device Throughput 121Server Throughput 116Types 116Viewing 115

RescanAdapters 54

RPC100 155, 158


Index

SSafeCache 277

Cache resource 279Configure 278Disable 282Disk failure 282Enlarge 282File system checking 282Properties 282Status 282Suspend 282Troubleshooting 436

SAN Client 61Access control 62Add

iSCSI 104Assign SAN Resources 84Definition 16Installation 21

Linux 22Windows 21

iSCSI 102NetWare

Install 26Pre-installation 21Solaris 89Windows 89

SAN Resources 72Access control 93Assign to Clients 84Create direct device 81Create service enabled device 81Create virtual device 76Creating 75Direct devices 74Physical resources 72Service enabled devices 74Virtual devices 72Virtualization examples 73

SAN/IPClientTroubleshooting 432

SCSIAliasing 56, 136Troubleshooting adapters/devices 423

Security 130Authentication 131Authorization 131Data access 130Disable ports 132

Physical security of machines 132Recommendations 131Storage network topology 131System management 130

ServerAuthentication 131Authorization 131Checking physical resources 98Checking processes 97Definition 16Discover 27, 31Import a disk 55, 398Installation 18Logging into 96Network configuration 48Pre-installation 18Properties 35Save/restore configuration 32, 405Scan LUNs greater than zero 424Starting 94Statistics 99telnet access 96Troubleshooting 434Uninstalling 101X-ray 434

Service enabled devices 74Creating 75, 81, 399Inquiry string 81Troubleshooting 437

Snapshot 212Resource 358

Check status 220Delete 221Expand 221Mirror 220, 221Options 221Properties 221Protect 220Reinitialize 221Shrink 221Troubleshooting 437

Setup 213Snapshot Copy 222

Command Line Interface 365Status 225

Snapshot notification 219SNMP

Advanced topics 335BMC Patrol 332CA Unicenter TNG 327


Index

Changing the community name 335HP OpenView 324IBM Tivoli NetView 329Implementing 323Integration 322Limit to subnetwork 335Manager on different network 335Traps 37, 322Troubleshooting 436Using a configuration for multiple IPStor Serv-

ers 335snmpd.conf 335Software updates

Add patch 47Rollback patch 47

Solaris ClientExpand virtual device 92Troubleshooting 434Virtual devices 89

Statisticsismon 99

Storage device path failure 136Storage pools 65

Access control 70Administrators 66Create 67Manage 66Properties 68Security 70Set access rights 70Tag 69Type 68

Storage quota 44Striping

Disk striping 291System

Disk 53Management 130

System maintenance 48Halt 49IPMI 50Network configuration 48Reboot 49Restart IPStor 49Restart network 49Set hostname 49

TThrottle 39, 268

ThroughputTest 56

TimeMarkCommand Line Interface 374Replication note 276Troubleshooting 436

TimeMark/CDP 232Add comment 241Change priority 241Copy 243Create manually 241Delete 250Disable 251Failover 174Free up storage 250Maximum reached 218, 236Policies 250Priority 218, 236, 242Replication 251Resume CDP 250Roll forward 248Rollback 248Scheduling 236Setup 233Status 238Suspend CDP 250TimeView 232, 244

TimeView 232Command Line Interface 374Recover data 244Remap 248

TivoliSNMP integration 329

Traps 322Troubleshooting 423

Block devices 438CLI 437Client

Connectivity 429Windows 430

Console launch 426Console login 427Debugging 431Event log 427Failover 435IPStor Server 434iSCSI Client 432Jumbo frame support 429Linux Client 429, 432


Index

NAS 435NetWare SAN Client 433Network connectivity 428Physical resources 438Replication 435SafeCache 436SAN/IP Client 432SCSI adapters and devices 423

Linux Client 424Service enabled devices 437Snapshot resources 437SNMP 436Solaris Client 434TimeMark 436Virtual device expansion 438Windows client 430

VVirtual devices 72

Creating 75, 76, 399Expand 90

Virtualization 72Examples 73

WWindows 2000 Dynamic disks

Expand virtual device 92Windows Client

Expand virtual device 92Virtual devices 89

Windows clientTroubleshooting 430

Write caching 59

XX-ray 434

CallHome 417Command Line Interface 400

ZZeroImpact backup 293
