systemwalker/storagemgr operator's guide -...

SystemWalker/StorageMGR Operator's Guide

10.0

-Solaris-

Preface

++ Purpose

This manual describes the operations on SystemWalker/StorageMGR.

SystemWalker is a generic term for operation management products for distributed systems provided by Fujitsu Limited.

++ Intended Readers

This manual is intended for a system administrator who performs storage management using SystemWalker/StorageMGR.

++ Organization

This manual has the following chapters:

+ Chapter 1 Overview of SystemWalker/StorageMGR

This chapter describes the overview of SystemWalker/StorageMGR.

+ Chapter 2 Starting and Stopping a Service

This section describes starting and stopping a service provided by SystemWalker/StorageMGR.

+ Chapter 3 Security Operation Using Authentication Feature

This chapter describes the security operation on SystemWalker/StorageMGR.

+ Chapter 4 Backup Operation

This chapter describes the backup operation.

+ Chapter 5 Backup Operation in the SP Series

This chapter describes the backup operation in the SP series.

+ Chapter 6 Replication Operation

This chapter describes the replication operation.

+ Chapter 7 SAN Resources Management Operation

This chapter describes the SAN resources management operation.

+ Chapter 8 Space Management Operation

This chapter describes the space management operation.

+ Chapter 9 Operation Maintenance

This chapter describes maintaining a database, performing troubleshooting, and other maintenance methods in the operation.

+ Chapter 10 Commands

This chapter describes commands.

+ Chapter 11 Notes on Operations

This chapter describes notes on the operations.

+ Appendix A Preprocessing and Postprocessing of Backup and Restoration

This appendix describes shell scripts used for preprocessing and postprocessing for backup and restoration.

+ Appendix B Sample Scripts

This appendix describes sample scripts for SystemWalker/StorageMGR.

+ Appendix C Cooperation with SQL Server

This appendix describes the procedure in the case of performing backup employment of the database of SQL Server by SystemWalker/StorageMGR.

+ Appendix D Replication Scripts

This appendix describes replication scripts used by SystemWalker/StorageMGR.

+ Appendix E Upgrading from Previous Versions

i

ii

This appendix describes how to upgrade from previous versions.

Related Manuals

The following shows the manual system of SystemWalker/StorageMGR. · SystemWalker/StorageMGR Installation Guide

Describes installing SystemWalker/StorageMGR. · SystemWalker/StorageMGR Operator's Guide (This Manual)

Describes operating SystemWalker/StorageMGR. · SystemWalker/StorageMGR User's Guide

Describes operating the Web-GUI on SystemWalker/StorageMGR. · SystemWalker/StorageMGR Messages

Describes messages output by SystemWalker/StorageMGR and action required for them. You are recommended to read this manual first to have overall understanding before reading other manuals.

++ Conventions · Microsoft(R) Windows NT(R) Server network operating system Version 4.0 and Microsoft(R) Windows NT(R)

Workstation operating system Version 4.0 are abbreviated as WindowsNT. · Microsoft(R) Windows(R) 95 operating system is abbreviated as Windows95. · Microsoft(R) Windows(R) 98 operating system is abbreviated as Windows98. · Microsoft(R) Windows(R) 2000 Professional, Microsoft(R) Windows(R) 2000 Server, and Microsoft(R)

Windows(R) 2000 Advanced Server are abbreviated as Windows2000. · Microsoft(R) Windows(R) Millennium Edition is abbreviated as Windows Me. · SystemWalker/StorageMGR that runs on Solaris is abbreviated as SystemWalker/StorageMGR for Solaris. · Manager of SystemWalker/StorageMGR is abbreviated as SystemWalker/StorageMGR-M or StorageMGR-M. · Agent of SystemWalker/StorageMGR is abbreviated as SystemWalker/StorageMGR-A or StorageMGR-A. ++ Trademarks

Windows, WindowsNT, SQL Server, and Internet Explorer are registered trademarks of Microsoft Corporation in the U.S.A. and elsewhere.

The Netscape logo and the Netscape product and service names are trademarks or registered trademarks of Netscape Communications Corporation in the U.S.A. and elsewhere.

Solaris,Java and all the other trademarks and logos related to Java are trademarks or registered trademarks of Sun Microsystems, inc. in the U.S.A. and elsewhere.

UNIX is a registered trademark exclusively licensed by X/Open Company Limited in the U.S.A. and elsewhere.

ORACLE is a registered trademark of Oracle Corporation.

Chapter 1 Overview of SystemWalker/StorageMGR

This chapter describes the overview of SystemWalker/StorageMGR.

1.1 Overview of SystemWalker/StorageMGR

1.1.1 What is SystemWalker?

The IT (Information Technology) environment is evolving from host-intensive processing to a distributed server environment or a client-server system, then to a mixed environment including network computing via the Internet. On the other hand, investment on the IT is becoming an important factor in terms of corporate strategies, an IT department must play the role as an information system office associated with corporate management. In response to such environmental changes, the operation management requires not only reduction of Total Cost of Ownership (TCO) but also exploitation of productivity improvement by enhancing the serviceability of operations for user departments as well as management of an information system based on management strategies.

As a concept to deal with such challenges, Fujitsu proposes Policy-based Systems Management (PSM). As a group of products to realize the PSM, Fujitsu provides the SystemWalker series.

1.1.2 What is Policy-based Systems Management (PSM)?

The PSM, a concept of SystemWalker, provides the following management functions to deal with challenges that will be important in terms of IT strategies. · Policy management

Intended to manage the information system based on management strategies. Manages an information system to meet the system operation conditions (policies) defined by an administrator.

· Service management Intended to enhance the serviceability of operations. Provides various services according to policies, specialized in different fields.

· Life cycle management Intended to reduce the operation management costs. Assures the IT resources including hardware, OS, networks, applications and users according to their life cycles (installation and setup, monitoring, recovery, and evaluation).

These three management functions ensure efficient operations of an entire distributed system according to policies defined by an administrator.

1.2 What is SystemWalker/StorageMGR?

SystemWalker/StorageMGR, among the SystemWalker series, is a product that realizes storage management in an open system and provides the following solutions.

1.2.1 SAN basis

A SAN (Storage Area Network) is a network dedicated to storage that connects servers, Fibre Channel switches, Fibre Channel hubs, and storage devices over a high-speed fibre channel. The next generation management system, Fibre Channel has a transfer rate of 100 MB/s and an effective connection length of 10 km. It enables storage to be shared by heterogeneous servers, and reduces management workload and costs because storage resources are centralized.

SystemWalker/StorageMGR supports these new storage management systems and provides operations management for centralizing SAN resource devices from different vendors.

1.2.2 High-speed backup (24-hour basis)

A hardware function [Advanced Copy Function (OPC,EC)] of Fujitsu's disk array units (GR720, GR730, and GR740) is used to back up data fast. The advanced copy function, being a fast data copy function independent of a data size, can always maintain fixed backup time even if the data to be backed up increases. Thus, the backup time does not increase even if the data amount increases.

This function can drastically reduce the time in which work must be stopped to perform backup.

In addition, since operations management is linked to the following DBMS, high-speed backup can be performed without interruption to daily work. · Oracle

1

· SymfoWARE If work uses a database other than Oracle or uses a general file system, the time that work is interrupted is still significantly reduced.

In addition, operations management can be used as a remote copy function for remote sites to create remote copies between Fujitsu disk array units on a LAN-WAN-LAN connection. Remote copying can also provide a disaster recovery solution because disk arrays containing backup data can be stored in an earthquake-resistant location.

1.2.3 Non-stopped operating backup [database]

By using SystemWalker/StorageMGR, the database of Oracle and SQL Server can be backed up by no operating stopping. Please refer to an Appendix B "Sample Shell script for Backup Operations" about the backup method of the database of Oracle.

Moreover it can back up in SystemWalker/StorageMGR, without cooperating with SynfinityDISK and stopping SynfinityDISK also under mirror volume (SDX object) environment.

1.2.4 Space management

SystemWalker/StorageMGR Space Manager manages the space for storage devices distributed on a network. This function manages the storage space for each job (multiple disks grouped by usage) and monitors the usage to prevent the system from running short of disk space.

In addition, since the trend report function can be used to check changes in disk usage graphically, a disk expansion plan and storage system design can be made efficiently.

1.2.5 High-speed replication

The hardware function (advanced copy function [OPC/EC]) of the Fujitsu disk array unit (GR720, GR730, or GR740) enables data to be used for purposes other than the original purpose and replicated data (copy) to be collected as a protection against data corruption.

If recovery from a disaster is necessary, replication (copying) can be performed for disk array units located at a remote site that has an SAN environment. (:EE)

1.3 Product Configuration of SystemWalker/StorageMGR

1.3.1 Edition

SystemWalker/StorageMGR V10.0 is available in two editions: a Standard Edition (SE) and an Enterprise Edition (EE). Functionality is different for the two editions. EE includes all functions of SE, as shown in the following figure.

[Figure 1.1 Functions in each edition]

1.3.2 Product system

SystemWalker/StorageMGR consists of the following two products:

2

[Table 1.1 Products]

Product name Description

SystemWalker/StorageMGR-M SE 10.0

Manager of SE. operates on the Storage management server, and two or more Storage servers are managed. manages, the SAN management, manages space, and the replication of the backup is managed.

SystemWalker/StorageMGR-A SE 10.0

Agent of SE. operates on the Storage server with which the storage device is connected. manages, the SAN management, manages space, and the replication of the backup is managed.

SystemWalker/StorageMGR-M EE 10.0

Manager of EE. operates on the Storage management server, and two or more Storage servers are managed. The replication between servers for the cluster in addition to the SystemWalker/StorageMGR-M SE function is done.

SystemWalker/StorageMGR-A EE 10.0

Agent of EE. operates on the Storage server with which the storage device is connected. The cluster in addition to the SystemWalker/StorageMGR-A SE function corresponds.

· This product, which is included as a component of the SP500 Basic Package, enables integrated backup in

the SP series. For more information on the SP series, see the Storage Management Processor Operator's Manual.

· The Manager product includes the Agent function.

3

[Figure 1.2 Product configuration of SystemWalker/StorageMGR (backup management)]

4

[Figure 1.3 Product configuration of SystemWalker/StorageMGR (replication management)]

5

[Figure 1.4 Product configuration of SystemWalker/StorageMGR (replication management: EE)]

6

[Figure 1.5 Product configuration of SystemWalker/StorageMGR (SAN management)]

7

[Figure 1.6 Product configuration of SystemWalker/StorageMGR (space management)]

1.3.3 System configuration

The system configuration of SystemWalker/StorageMGR is shown below.

8

[Figure 1.7 System configuration used when the storage management server runs on WindowsNT/2000]

9

[Figure 1.8 System configuration used when the storage management server runs on Solaris]

1.3.4 Combinations of products

There are the following combinations of SystemWalker/StorageMGR products on other platforms.

Table 1.2 Combinations of products

Storage server type

Windows Solaris HP Storage management server type

StorageMGR-A SE

StorageMGR-A EE

StorageMGR-A SE

StorageMGR-A EE

StorageMGR-A SE

StorageMGR-M SE Yes No Yes No Yes

Windows StorageMGR-M EE Yes Yes Yes Yes Yes

Solaris StorageMGR-M SE Yes No Yes No Yes

10

StorageMGR-M EE Yes Yes Yes Yes Yes

Yes: Permitted; No: Not permitted

About connections between SystemWalker/StorageMGR V5.1 and SystemWalker/StorageMGR V10.0 · A connection between SystemWalker/StorageMGR-M V10.0 and SystemWalker/StorageMGR-A V5.1 is

allowed. · A connection between SystemWalker/StorageMGR-A V10.0 and SystemWalker/StorageMGR-M V5.1 is not

allowed. · A connection between the same editions of SystemWalker/StorageMGR or a connection between

SystemWalker/StorageMGR-M EE and SystemWalker/StorageMGR-A SE is allowed.

1.4 Function Overview of SystemWalker/StorageMGR

1.4.1 What is the backup function?

The backup function of SystemWalker/StorageMGR provides operation management for high-speed backup by using the OPC (One Point Copy) function of a Fujitsu disk array unit (GR720, GR730, or GR740) and the ROPC (Remote One Point Copy), EC (Equivalent Copy), and REC (Remote Equivalent) functions of a GR740.

This function realizes the following backup operation:

+High-speed backup operation

The advanced copy function (OPC/EC function) of the disk array unit is used to perform high-speed backup between volumes regardless of volume capacities. This function drastically reduces the length of time that work is inevitably interrupted during backup.

+Backup operation in the SP series

SP series products work closely with GR series disk array units in the management and operation of storage that is independent of the server.

With SystemWalker/StorageMGR, a backup/restore function linked to the backup function of the SP series is provided so that SP series disks can be integrated in the same way that volumes of other GR series disk array. This function is in addition to the management of SP series disks already available in the SP series.

+Backup operations in linkage with SymfoWARE-DB

High-speed copying to create backups is possible for databases constructed with SymfoWARE during the course of business.

+Cooperation with ISV software (sample scripts)

Sample scripts with the following functions are provided. These scripts consist of SystemWalker/StorageMGR commands, a DBMS, and backup software commands. · Acquisition of DBMS (Oracle) resource information · Synchronization with a DBMS (Oracle), copying of volumes, and saving of copy destination volumes to tape

(NetBackup, NetWorker, TivoliStorageManager) Additionally, the following functions allow you to manage the backup operation.

+Policy management function

The policy management function manages the number of preservation generations of backup and the number of interval days in which backup should be performed (displays the delay when displaying information) for a volume to be backed up.

+Storage configuration management function

The storage configuration management function manages the configurations of volumes to be backed up and volumes to which a backup should be saved.

On SystemWalker/StorageMGR, a volume to be backed up is called a transaction volume; a volume to which a backup should be saved is called a backup volume.

11

+Backup and restore functions

The backup and restore functions back up and restore a specified volume.

· The backup function with ROPC/REC is available only for backup disk array units on the same storage server.

+History information management function

The history information management function manages, out of the information that has been backed up in the past, the information in preservation generations as history.

+Consistency recovery function

The consistency recovery function resolves inconsistencies in the SystemWalker/StorageMGR backup management information caused by a system or other type of failure.

1.4.2 What is the replication function?

The replication function of SystemWalker/StorageMGR provides operation management of replications by using the OPC (One Point Copy) function of a Fujitsu disk array unit (GR720, GR730, or GR740) and the ROPC (Remote One Point Copy), EC (Equivalent Copy), and REC (Remote Equivalent) functions of the GR740.

As a result, the following replication operations become possible.

+High-speed replication operation

The advanced copy function (OPC/EC function) of the disk array unit is used to perform high-speed replication between volumes regardless of volume capacities. This function drastically reduces the length of time that work is inevitably interrupted during replication.

Since this function, unlike the backup function, does not manage histories, it is suitable for temporary backup. In addition, when the replication function is used with EC, this kind of replication can also be used as an update (incremental) backup operation.

+Consistency recovery function

The consistency recovery function resolves inconsistencies in the SystemWalker/StorageMGR replication management information caused by a system or other type of failure.

1.4.3 SAN resource management function

+About SAN

Traditionally, a parallel SCSI interface has been the main interface used between servers and storage devices to establish a connection between one server and one storage device. Fibre Channel technology, which is replacing the SCSI interface, enables the connection of multiple nodes, like connections in a LAN (local area network), and high-speed data transfer. With SAN, it is also possible to connect multiple servers and multiple storage devices. A network that uses SAN technology for connectivity is called a SAN (Storage Area Network).

+Solutions available with the SystemWalker/StorageMGR SAN resource management function

SystemWalker/StorageMGR with the SAN resource management function provides the following solutions. a. Device management by automatic recognition

The status of supported SAN device and Fibre Channel connections is displayed on the window after automatic recognition via a LAN. (The devices on the same subnet are automatically recognized.) Since devices displayed on the window can be relocated, the relationship with the actual layout is easily understood. In addition, a device that is not automatically recognized can be included manually and managed.

b. Total management of access paths Automatic management and automatic setting are achieved through the integrated management of the security functions ion servers, Fibre Channel switches, and storage devices. The binding/zoning information already specified for devices can be used to automatically recognize and indicate an access path. In an environment where WWPN binding is used, an access path can also be diagnosed.

12

In addition, since access paths are totally managed, an abnormal condition can be detected even though the physical fiber cable, which is the route on a SAN configured from access paths, is broken. For access paths managed by the SAN Resource Manager, manual modification of a configuration for a device can be made as well as automatic modification by the SAN Resource Manager. When manual modification is done, the SAN Resource Manager can check whether the changes have been done properly.

c. Corrective action for a fault The GUI drill-down function can be used to indicate a faulty location and to identify a faulty part in detail. In addition, the extent of the work affected can be correctly identified by indicating the access paths on which the faulty location has an effect. A fault report can be efficiently transmitted through linkage with a shell or batch file that can be edited by SystemWalker/CentricMGR or the user. These functions reduce the time needed to recover from a fault.

d. Performance management The performance of a device supported by the SAN Resource Manager whose performance is subject to performance management can be obtained over a LAN and displayed graphically. Performance can be used to obtain the current load states of devices and to assist in construction of an optimum operation environment. For a switch, CRC error on a Fibre Channel path can be checked.

e. CIM (Common Information Model) CIM is an industry-standard data model used to manage network resources and enterprise resources. CIM was proposed by the DMTF (Distributed Management Task Force) and is recommended as a storage device management tool by the SNIA (Storage Network Industry Association), an organization that is promoting the standardization of storage area network management. The configuration of the SAN resource management function with CIM is shown in Figure 1.9 Figure 1.9 SAN resource management configuration of SystemWalker/StorageMGR

1.4.4 Space management function

The space management function indicates the status of space on a disk array unit so that resources can be efficiently used. · Managing administrator information

Job managers are managed based on the StorageMGR authentication information, maintaining security for space management function. In addition, StorageMGR can perform integrated management of privileges for managers.

· Grouping storage devices Storage devices are grouped into jobs by usage or attribute to ensure efficient use.

· Policy management

13

The operating policy of space management for each job or device can be set. Space is managed and used based on the specified operating policy operation. Flexibility is provided because a policy can be set for the entire system, for each job, or for each device.

· Centralized management of the space use status Total capacity and amount of used space for storage device in the storage system is listed. The devices without enough space (those that have exceeded the policy threshold) are displayed in a different color so that problem devices can be easily detected.

· Monitoring of the amount of used space and automatic notification if a shortage occurs If space is insufficient, mail is sent to the manager of the job to which the corresponding device belongs. In addition, when there is not enough space, a warning is sent to CentricMGR, which is linked, so that CentricMGR can monitor the situation.

· Acquisition and analysis of detailed information regarding space Detailed information about a file in a device is retrieved as an aid in investigating a space shortage or in analyzing use.

· Report on space usage trends Information about space usage is periodically output to a report file that can be used to design efficient storage operations.

1.4.5 Authentication feature function

In relation to the backup function, SAN management function, and Space Manager provided by SystemWalker/StorageMGR, this function manages users who have acquired access rights, providing security controls in the identification of function users. For more information, see Chapter 3, "Security Operation Using Authentication Feature". Note also that the replication function is not a target of the authentication feature.

1.5 Operating Environment of SystemWalker/StorageMGR 10.0

1.5.1 Hardware requirements

One of the following hardware devices is required to perform backup management or replication management. · GR720 disk array unit · GR730 disk array unit · GR740 disk array unit · GR840 disk array unit

[Table 1.3 Servers supported by SAN Manager]

Product name HBA Verified version number

Support level Remarks

GP7B8FC1 Driver (Fujitsu PCI FiberChannel 2.0 or later)

Qlogic QLA2200 QLogic QLA2200 driver Rev3.07

Emulex LP7000/8000/9000

Emulex LightPulse FC SCSI/IP Host Bus Adapter driver Release4.02d/4.10g

Solaris2.6/7/8 machine

PRIMEPOWER/GP-S/S/Star Fire/SUN Enterprise/SUN

SN10-FC01 or JNI FC64-1063

JNI FibreChannel SCSI/IP HBA driver (FCW-1064) v2.4.1/2.5/2.5.9

Load state/setting of access path

14

GP5-CF101/102(GP5000)

PG-CF102(PRIMERGY)

QLA2100F/2200

GP5-FC101 V1.1L10(Driver 6.17) GP5-FC102 V1.0L10(Driver 7.05.05) PG-FC102 V1.2L10(Driver 8.00.08) QLA2100(Driver 7.05.05 or later) QLA2200(Driver 8.00.08 or later)

WINDOWS NT/2000 machine

PRIMERGY/GP5000/other companies

Emulex LP7000/8000/9000

SCSI Miniport Driver v4-4.52.a7(NT) v5-4.52.a7(2000)

Load state/setting of access path (However, there is no server setting)

AIX,HP, LINUX etc There is no specification Manual building in

[Table 1.4 Fibre Channel switches supported by SAN Manager (see Table 1.9 for support levels)]

Model name Version number


SN200 model 10/20/30/40, Brocade Silkworm 2800/2400/20*0/22*0

Fabric OS 2.1.* to 2.4.*

(* The value is not asked)

A

The beacon function is since version number 2.2. Please inquire the supports of the number of versions other than the following.

SN200 model240, Brocade Silkworm3800

Fabric OS 3.0.*

(* The value is not asked)

A Please inquire the supports of the number of versions other than the following.

[Table 1.5 Fibre Channel hubs supported by SAN Manager (see Table 1.9 for support levels)]

Model name Verified version number Support level Remarks

GP-FCH2/GP-FCH3, Gadzoox Gibraltar GS/GL Agent:04.00-g06/Controller:0400g05 C

A LAN port for management is required.

Products other than the above (including the GP-FCH1 and GP5-FCH1)

J

[Table 1.6 Array disks supported by SAN Manager (see Table 1.9 for support levels)]

Model name Version number


GR710 V10L22 or later B

GR720,730,740,820,840 All version numbers A

Please inquire the number of GR740 of firmware versions from V11L30 of the revitalization composition reflection function of GR720,730.

F649x/Spectris/Platinum series All version numbers H

15

Hitachi SANRISE 1000/2000 (DF400/500, RAID300/400) E SNMP needs to be supported.

EMC

Symmetrix 3000/5000/ESP/8000

E EMC Control Center Agent is required.

Products other than the above J

[Table 1.7 Libraries and tapes supported by SAN Manager (see Table 1.9 for support levels)]

Model name Version number Support level Remarks

LT300N Consult Fujitsu sales personnel. F

LT120, HP Surestore Tape Library

Consult Fujitsu sales personnel. G


[Table 1.8 Fibre Channel array disks supported by SAN Manager (see Table 1.9 for support levels)]

Model name Version number Support level Remarks

Crossroads 4150,4250,4450 Version1.0 2001 or later I


[Table 1.9 Explanation of SAN Manager support levels]

Support level

Representative device name

Device detection

Fault management

For management window

state reading

Drawing in FC connection line

Configuration management related to SAN

Performance management

A GR(710 is excluded), SN200

Automatic operation

Automatic operation

Automatic operation

Automatic operation

Automatic operation Yes Yes

B GR710 Automatic operation

Automatic operation

Automatic operation

Automatic operation

Automatic operation Yes -

C GP-FCH Automatic operation

Automatic operation - Automatic

operationManual operation - -

E SANRISE, Symmetrix

Automatic operation

Automatic operation *1

Manual operation

Automatic operation

Automatic operation - -

F LT300 Manual operation

Automatic operation *1

Automatic operation - Manual

operation - -

G LT120 Manual operation

Automatic operation *1 - - Manual

operation - -

H F6495 Automatic operation - - - Automatic

operation - -

I Crossroads Automatic operation - Automatic

operation Automatic operation

Automatic operation - -

J Except the above

Manual operation *2 Manual

operation - Manual operation - -

*1. SNMPTRAP settings for devices must be made individually.

*2. For an SNMPTRAP support device, manual management is allowed.

16

1.5.2 Software requirements

1.5.2.1 SystemWalker/StorageMGR-M

The following table lists the software requirements for SystemWalker/StorageMGR-M

[Table 1.10 Software requirements for SystemWalker/StorageMGR-M]

Product name Requirement Remarks

Solaris 2.6,Solaris 7,Solaris 8 Required Support OS

Sun WebServer 1.0 or later Apache 1.3 or later InfoProviderPro 2.0 or later

Required Web server

SynfinityCLUSTER 1.0 or later

Conditionally required

For cluster operation with SystemWalker/StorageMGR-M EE

1.5.2.2 SystemWalker/StorageMGR-A

[Table 1.11 Software requirements for SystemWalker/StorageMGR-A]


Solaris 2.6,Solaris 7,Solaris 8 Required Support OS

SymfoWARE Advancrd Backup Control 3.2.1


For backup operations in linkage with SymfoWARE

SynfinityCLUSTER 1.0 or later Conditionally required

For cluster operation with SystemWalker/StorageMGR-A EE

Multipath disk control (MPHD) 2.0 or later

Conditionally required For multipath disk control

Multipath disk control load balance option (MPLB) 2.0 or later


For multipath disk control and path load balancing

1.5.2.3 Web Browser

[Table 1.12 Software requirements for Web browsers]


Microsoft(R) Internet Explorer 4.0 or later Netscape Communicator 4.04 or later Required Web Browser

Java Plugin 1.3.1_01 or later Required Java Plugin

1.6 Managing a Device on SystemWalker/StorageMGR

The following devices are supported in backup management and replication management. · Sd driver resources · Hddv driver resources · MPHD resources · MPLB resources Moreover, the unit of management is a disk partition (slice) unit.

17

Chapter 2 Starting and Stopping Daemons

This chapter explains how to activate and stop different daemons provided by SystemWalker/StorageMGR.

For more information on how to activate and stop the daemons described in this chapter, see chapter 11.5.8, "Starting and stopping StorageMGR daemons."

2.1 Daemons that Configure SystemWalker/StorageMGR

SystemWalker/StorageMGR-M is configured with the following daemons:

[Table 2.1 Types of daemons that configure SystemWalker/StorageMGR-M]

Daemon type Description

The communication daemon Communicates with the Storage server

The RMI daemon Manages the GUI display

The RDB daemon Accesses the repository

The CIMOM daemon Performs SAN management

The SNMP trap monitoring daemon

Handles the SNMP traps of SAN management

The space management daemon Performs space management

The authentication daemon Manages the authentication feature

SystemWalker/StorageMGR-A is configured with the following daemons:

[Table 2.2 Types of daemons that configure SystemWalker/StorageMGR-A]

Daemon type Description

The communication daemon Communicates with the Storage server

The space management daemon Performs space management

2.2 Starting a Daemons

Daemons must be activated on the Storage management server, Storage server, and SP server.

Normally, they are automatically activated. However, if activation fails or the daemon is stopped, activate the daemon on each server by executing the following command:

# /opt/swstorage/bin/sstoragemgr

2.3 Stopping a Daemons

Stop daemons from the Storage server. Normally, they are automatically stopped when the system stops.

To stop a daemon on a server, execute the following command on the server:

# /opt/swstorage/bin/pstoragemgr

19

Chapter 3 Security Operation Using Authentication Feature

This chapter describes the security operation using the authentication feature provided by SystemWalker/StorageMGR.

3.1 Overview

SystemWalker/StorageMGR provides features for backup management, SAN management, space management, and replication management or operation. If any of the features is incorrectly used, the operation may stop.

Thus, SystemWalker/StorageMGR provides a function of setting access permissions for each user on the backup operation (authentication feature). Use this function to realize security of the backup operation.

On SystemWalker/StorageMGR, you can use only a user who: · Each user name consists of two to eight alphanumeric characters. (The colon symbol cannot be used.) · The password for the user name consists of 28 alphanumeric characters.

3.2 Access Permission

Table 3.1 shows access permissions that can be specified on SystemWalker/StorageMGR.

[Table 3.1 Access permissions on SystemWalker/StorageMGR]

Access permission Description

Write permission

Allows you to change the operation information (such as policy information) and perform a series of storage operations. A write permission includes execute and read permissions.

Execute permission

Allows you to perform a series of storage operations and read information. An execute permission includes a read permission.

Read permission Allows you only to read information.

Table 3.2 shows the operations on the initial window, made available due to each of the access permissions.

[Table 3.2 Operations on the initial window made available due to access permissions]

Operation name Write permission

Execute permission

Read permission

Displaying server information Yes Yes Yes

Displaying device information Yes Yes Yes

Displaying partition information Yes Yes Yes

Changing in Displayed Item of Device Yes Yes Yes

Updates to Latest Information Yes Yes Yes

Addition of server Yes No No

Change of server Yes No No

Deletion of server Yes No No

Acquisition and reflection of information on all the devices Yes No No

Acquisition and reflection of information on specific device Yes No No

Deleting device information Yes No No

Yes: Enabled No: Disabled

21

· Access permission for backup management or space management is required to access the initial window. Table 3.3 shows the backup management operations made available due to each of the access permissions.

[Table 3.3 Backup management operations made available due to access permissions]


Execute permission

Read permission

Window display Yes Yes Yes

Backup Yes Yes No

Restoration Yes Yes No

Recovery Yes Yes No

Delete History Yes Yes No

Start Backup Synchronization processing Yes Yes No

Cancel Backup synchronization processing Yes Yes No

Match Resources Yes Yes No

Set Backup Policy Yes No No

Delete Backup Policy Yes No No

Set Device Information Yes No No

Set Storage Server Configuration Information Yes No No


In space management, the access permissions specified by the authentication feature are applied as follows.

[Table 3.4 Space management operations available for each access permission]


Execute permission

Read permission

Setting a mail server Yes No No

Setting an administrator Yes No No

Registering, updating, and deleting a job Yes No No

Setting a system policy Yes No No

Registering and updating a job policy and inheriting a higher-level policy Yes No No

Registering and updating a device policy and inheriting a higher-level policy Yes No No

Checking space Yes Yes No

Customizing a display item Yes Yes Yes

Trend report graph Yes Yes Yes


In SAN management, the access permissions specified by the authentication feature are applied as follows.

[Table 3.5 SAN management operations available for each access permission]


Execute permission

Read permission

Setting a SAN management policy Yes Yes Yes

22

Moving an icon Yes Yes Yes

Searching for a device Yes No No

Adding a device Yes No No

Deleting a device Yes No No

Setting an access path Yes No No

Deleting an access path Yes No No

Diagnosing an access path Yes No No

Automatic inheritance of an access path Yes No No

Displaying a URL Yes Yes Yes

Displaying a property Yes Yes Yes

Displaying version information Yes Yes Yes

Displaying Help Yes Yes Yes

Displaying the SAN configuration Yes Yes Yes

Manual operation built-in function Yes No No


3.3 Setup Procedure

This section describes how to perform the security operation on SystemWalker/StorageMGR.

3.3.1 Flow of setup

The following shows the flow of setup procedure.

3.3.2 Setup work details

The following shows the operation work details. For description, operation methods, and notes on each window, see Chapter 2, "Operating the Authentication Feature Window" in the "SystemWalker/StorageMGR User's Guide". 1. Specify the URL of the initial window of SystemWalker/StorageMGR to display the initial window. 2. After the following login window is displayed, specify a root user name and the password for the root user, and

then click the [OK] button.

23

3. The initial window of SystemWalker/StorageMGR will be displayed.

4. Select [Edit] from the initial window authentication feature menu. The following setup window will be displayed.

5. From the operation menu, select [Add user]. The following window will be displayed.

24

From the User list, select a user to be added to move it to the User list to be added. From the combo box, select an access permission and click the [OK] button. You can add either a specific user or multiple users. After you have set the access permission, click the [OK] button. The addition of a user and the setup of an access permission for this user will be completed.

· The displayed user name is one that is registered on the Storage management server. · A user name already registered on one of the management systems will not be displayed in the user name list

dialog. · If no user to be added exists, the following warning dialog will be output and you will be sent back to the

authentication feature management window.

25

Chapter 4 Backup Operations (Normal Transaction Volumes)

This chapter explains backup operations for normal transaction volumes of SystemWalker/StorageMGR.

4.1 Overview

This chapter describes the backup and restore functions of SystemWalker/StorageMGR.

SystemWalker/StorageMGR performs high-speed backup between volumes, regardless of the volume capacities, using the advanced copy function (OPC or EC function) of a disk array unit.

Backup that uses the One Point Copy (OPC) or Remote One Point Copy (ROPC) function of a GR series disk array unit is called snapshot fast backup. Backup that uses the Equivalent Copy (EC) or Remote Equivalent Copy (REC) function is called synchronized high-speed backup.

Automatic snap shot backup can be scheduled without first estimating the time required because it does not require backup synchronous processing. Note, however, that when the save number is 1, a state in which there is no backup data may occur, because a snap shot backup deletes the history prior to copy processing.

Because synchronized high-speed backup deletes the history after the completion of backup processing, there is no status in which backup data does not exist even though the generation number is 1. However, synchronized high-speed backup requires one more backup volume than snapshot fast backup. Synchronized high-speed backup also requires synchronized backup processing before the backup execution command is entered. Therefore, execution of automatic synchronized high-speed backup must be scheduled so that the time required for synchronized processing is estimated in advance. Synchronized backup processing is then started based on the estimated time, and the backup execution command is entered after equivalency maintain status has been achieved.

SystemWalker/StorageMGR automatically manages and selects a medium to be used for backup (a backup volume).

SystemWalker/StorageMGR also manages the backup carriers and generations and allows you to restore data from the latest or other past generations.

[Figure 4.1 Managing a backup volume]

4.1.1 Snapshot backup processing

The OPC function of the disk array unit GR series is used to copy data from a transaction volume to an unused backup volume.

The snapshot fast backup performs processing as follows: 1. Execute the backup execution command ((1) in Figure 4.2). The following processing will be performed: - If backup volumes under generation management exist for all the generations, the oldest backup

volume will be assumed as an unused backup volume. - An unused backup volume will be acquired from the unused backup volume management area.

27

2. Data on the transaction volume will be copied to the acquired unused backup volume ((2) to (4) in Figure 4.2). 3. Backup carrier information will be set.

[Figure 4.2 Snapshot fast backup processing]

The snapshot fast backup is completed as soon as you specify to execute backup. The actual data copying will be internally performed by the OPC function of the disk array unit GR series.

If all generations of backup volumes are managed, and if no backup volume can be obtained from the unused region in the backup volume management area, backup copies cannot be created.

4.1.2 Synchronized high-speed backup processing

The Equivalent Copy (EC) function of the GR series of disk array units is used to copy data from a transaction volume to an unused backup volume.

Synchronized high-speed backup performs processing as follows: 1. Execute the synchronized backup processing start command ((1) in Figure 4.3). An unused backup volume

having the same capacity as the transaction volume is selected from the unused backup management area, and the synchronized backup processing starts.

2. The transaction and backup volumes are both placed in equivalence status. From this point on, equivalence between the transaction volume and backup volume is maintained. This status is referred to as equivalency maintain status ((3) in Figure 4.3).

3. Execute the backup execution command ((4) in Figure 4.3). The backup synchronization processing stops and the backup history information is set.

4. If the backup data exceeds the number of generations when backup has been completed, the oldest backup volume is treated as an unused backup volume.

28

The backup execution command cannot be executed before the transaction and backup volumes have become equivalent.

[Figure 4.3 Backup using the synchronized high-speed backup function]

All backup volumes are subject to generation management. If a backup volume cannot be obtained from the unused backup volume management area, backup cannot be executed.

4.1.3 Restoration processing

This chapter describes restoring data on SystemWalker/StorageMGR.

The restoration operation refers to restoring data from a backup volume managed by the backup carrier information to a transaction volume.

The restoration operation from a backup volume refers to using the OPC function provided by the disk array unit to restore data from a backup volume to a transaction volume.

If the data on a backup volume under carrier management is restored to a transaction volume, the carrier management information will not change.

If transaction volume contents are rewritten in the period between collection of the latest backup

29

volume and a subsequent restore operation, rewritten data is not assured.

[Figure 4.4 Notes on restore operations in SystemWalker/StorageMGR]

4.2 Operation Design

This chapter describes the backup operation on SystemWalker/StorageMGR.

Design a backup operation as follows: · Deciding a server on which the backup operation should be performed · Deciding a backup target · Deciding a backup policy · Preparing a backup volume · Preparing the automatic backup operation

4.2.1 Deciding a server on which the backup operation should be performed

The backup operation can be performed on one of the following servers. · Storage management server

Multiple storage servers are managed and operated on a unified and centralized basis. A storage management server can also serve as a storage server.

· Storage server SystemWalker/StorageMGR can be operated.

The locale of the internal code system (code system specified when installing SystemWalker/StorageMGR on the Storage management server) used by SystemWalker/StorageMGR must be installed on all Storage servers.

30

[Figure 4.5 Configuration of servers on which the backup operation should be performed]

4.2.2 Deciding a backup target

SystemWalker/StorageMGR backs up data in units of slices. A slice that stores work data is called a transaction volume. A transaction volume to be backed up must be placed on the disk array unit GR series.

For information on setting up a transaction volume, see Chapter 4.4.8, "Setting the operation type for a device".

Slices must be allocated for transaction volumes in the following manner:

· Create slices so that no VTOC is contained in them. · No slice may be duplicated on the same disk.

For backup targets, do not select slices in which a system is stored or SystemWalker/StorageMGR is installed.

For any slice that defines an entire volume, do not register it as a transaction volume.

No file system of SafeFILE consisting of multiple slices can be processed. When backing up or

31

restoring a file system of SafeFILE consisting of multiple slices, handle the multiple slices at the same time while they are unmounted.

4.2.3 Deciding a backup policy

To setup a backup policy on a transaction volume, set the following items:

+Number of preservation generations

The number of preservation generations refers to how many generations of backup data should be kept.

Fujitsu recommends backing up on tapes too, as explained in Appendix B, "Sample Shell Script in Backup Operations".

The snapshot fast backup first releases the oldest generation from the generation management. If a system failure or any other failure occurs while the backup is running, there may not be as many generations of backup data as required. In such a case, you are recommended to perform backup immediately again.

A synchronous high-speed backup operation releases the oldest generation from generation management after backup of the latest generation is completed. Thus, backup volumes for (number of backup generations + 1) are necessary.

+Interval days

The interval days refers to an interval at which backup should be performed.

The delay of backup is displayed if more days than the specified number of interval days have passed after the last backup date.

Note that backup is not performed periodically even if you have specified the interval days.

For information on setting a backup policy, see Chapter 4.4.10, "Setting a backup policy".

4.2.4 Preparing a backup volume

Prepare the backup volume.

The backup unit of SystemWalker/StorageMGR is a slice. In SystemWalker/StorageMGR, the slice in which the transaction data used as the candidate for backup is stored is called transaction volume.A backup volume must be placed on the disk array unit GR series.

The backup volume size must equal the transaction volume size. The number of backup volumes used for snapshot-type high-speed buffer operations and that for synchronous high-speed buffer operations are listed below:

Backup Number of required backup volumes

For snapshot fast backup Number of backup generations

For synchronized high-speed backup Number of backup generations + 1

When backup policies have already been set for multiple transaction volumes, the registration of a backup policy for a newly registered transaction volume requires that the following number of backup volumes be registered beforehand:

Backup Number of required backup volumes

For snapshot fast backup

Total number of backup generations in the registered backup policies + number of generations in the new backup policy being set

For synchronized high-speed backup

Total number of backup generations in the registered backup policies + number of registered transaction volumes + number of generations in the new backup policy being set + 1

Slices must be allocated for backup volumes in the following manner:

· Create slices so that no VTOC is contained in them. · No slice may be duplicated on the same disk. In a backup volume, there is no need to create a

slice that indicates a whole volume, such as slice2. For information on setting a backup volume, see Chapter 4.4.8, "Setting the operation type for a device".

32

4.2.5 Preparing the automatic backup operation

The backup operation of SystemWalker/StorageMGR can be automated using SystemWalker/OperationMGR, etc.

+Automatic snapshot fast backup

Automatic snapshot fast backup can be executed in one of the following two ways. · Start the backup command in a job net of a batch job every time when a backup should be collected.

· Start the backup command at the specified time.

+Automatic synchronized high-speed backup

For synchronized high-speed backup, the transaction and backup volumes must be in equivalency maintain status at the scheduled time for backup.

For this reason, if synchronized high-speed backup is automated, the synchronized backup processing start command and the backup execution command must be started separately, as described below.

+Starting the synchronized backup processing start command

At first, theoretically calculate the time required for the synchronized backup processing. Execute the synchronized backup processing start command by specifying the time obtained by subtracting that theoretical time or more from the time that the backup execution command is to start. The transaction and backup volumes will then be in equivalency maintain status when backup is executed.

The time between the start of synchronized backup processing and the transition to equivalency maintain status depends on the capacity of the volume to be copied.

+Starting the backup execution command

Use either of the following methods to automatically execute the backup execution command: · Start the backup execution command in a job net of a batch job at the same time at which the backup data is

to be collected.

33

If there are other jobs (jobs A and B in the figure) to be executed before the backup execution command in the job net, the start time of the backup execution command cannot be determined. Assume that the start time of the backup execution command is the time obtained by adding the shortest time required for jobs A and B to the job net start time. Determine the start time of the synchronized backup processing start command by subtracting the estimated time from the start time of the backup execution command.

· Start the backup execution command with the time specified.

4.3 Flow of Operation

The following shows the flow of backup operation on a regular transaction volume.

34

4.4 Preparations

The following preparations are required before the backup operation is started.

4.4.1 Activating daemons

Before starting a backup operation, daemons on the Storage management server and Storage servers must be activated. Normally, they are automatically activated when the system starts.

If activation fails or the daemon is temporarily stopped, activate the daemon on each server by executing the following command:

35


4.4.2 Setting an access permission

To set an access permission on the backup operation management window, see Chapter 3, "Security Operation Using Authentication Feature".

4.4.3 Starting the initial window

Specify the following URL to start the initial window of SystemWalker/StorageMGR.

http://storage-management-server-address(:port-number)/swstorage/index.html

The following GUI (server list view) will be started.

4.4.4 Registering a storage server

The storage management server registers the storage server to be managed. To register a storage server on the GUI, select the Operation menu, select Addition of Server. The following window will be displayed.

For a storage server to be added, specify a server name, IP address, and port number required for communications. If the Storage server operates in a cluster, specify the inherited IP address of the Storage server allocated for StorageMGR as its IP address.

The port number is specified as the "communications service port number", when SystemWalker/StorageMGR-A was installed.

36

4.4.5 Fetching device information on a storage server

Before the backup management can be performed, device information on a storage server must be temporarily stored to the repository. To acquire information on a device on the storage manager server, select [Acquisition/Reflection of Information of All Devices]. The following window will be displayed.

Check the server from which device information should be acquired and then press the OK button.

After device information is acquired from each server, the following dialog will be displayed.

The new devices detected will be displayed in the uppermost list box. Move a device to be managed to the list box on the left. The second list box displays devices currently under management but not detected. Move a device that you no longer want to manage to the list box on the right. The lowermost list box displays devices whose device information has been updated (e.g., the mount point name has been changed).

After performing the above operations, press the OK button to reflect the configuration information.

37

The time required for this operation is proportional to the total number of devices defined on the Storage server. If the number of devices is large, perform this operation while the CPU load and I/O load are low.

As a guideline for reference, each operation takes about 0.5 s per device (partition) in a state without load.

4.4.6 Displaying the backup management window

On the server list view, select the [File] menu and then [Backup Management]. The server list view for the backup management will be displayed.

4.4.7 Setting the environment for a backup operation server

Set the environment for each storage server. From the Backup Management window, select backup management in the tree displayed on the left side. Then, select the storage server in a list panel displayed on the right side of the window. Finally, select Set Server Information from the Operations menu. The following setup window will be displayed.

After completing the input of necessary items, click the [OK] button.

You need to make this environment setting also on the storage management server if it serves also as a storage server. This step is not required if the environment setting has already been made on the storage servers.

You can also make this environment setting also using the storage server configuration information setting command.

4.4.8 Setting the operation type for a device

Execute a device information setting command and set up the following device operation type, before backing up in a

38

storage server. · Define the volume to be backed up as a transaction volume. · Prepare backup volumes. Prepare as many partitions, each of which has the same size as the transaction

volume, as the number required for the backup type, and define them as the backup volumes: Backup Number of required backup volumes

Snapshot fast backup Number of backup generations

Synchronized high-speed backup Number of backup generations + 1

Set an operation type on the server list view. On the server list view, select a storage server and select the [Operation] menu and then [Set Device Information]. The following setup window will be displayed.

A volume displayed in "Other volume" field has no specified device operation type. Set a device operation type as follows: · Setting as a "transaction volume"

After selecting a target volume, click the [<] button on the "Transaction volume" side. The target volume will be moved to the "Transaction volume" field.

· Setting as a "backup volume" After selecting a target volume, click the [<] button on the "Backup volume" side. The target volume will be moved to the "Backup volume" field.

After making settings for all the volumes, click the [OK] button.

You can make this setting also using the device information setting command (swstdevinfoset).

For any slice that defines an entire volume, do not register it as a transaction volume.

If the slice configuration of a transaction volume is changed, delete the volume from the registered transaction volumes. Next, after following the process of Fetching device information on a Storage server again, re-register the volume by executing the device information setting command.

39

If the slice configuration of a backup volume is changed, delete the volume from the registered backup volumes. Then, after following the process of Fetching device information on a Storage server again, re-register the volume by executing the device information setting command.

You can check what has been registered as follows: · Checking on a GUI window

You can view information on a transaction volume on the transaction volume list view or information on a backup volume on the backup volume list view. For more information on each of these views, see the "SystemWalker/StorageMGR User's Guide".

· Checking using a command You can view information on a registered transaction volume or backup volume using the device usage status display command.

4.4.9 Setting options

Set options when performing backup to a backup volume in a cabinet that is not the same as the cabinet containing the transaction volume.

Create the following files to set options:

For normal operation (non-cluster)

/etc/opt/FJSVswsts/data/DEFAULT/check.ini

For cluster operation

/etc/opt/FJSVswsts/<logical-node-name(*1)>/data/DEFAULT/check.ini

(*1) Logical node name of StorageMGR specified during setting up of a cluster.

Code as follows:

[check]

RemoteCopy=Yes

If the option settings file is changed after operation starts, backup may not be able to continue. For this reason, do not change the option settings file after the start of operation.

To change the option settings file, you must set the backup policy again.

4.4.10 Setting backup policies

For a transaction volume registered on a storage server, set the following backup policy: · Number of preservation generations

Means how many generations of backup data should be kept. · Interval days

Means the number of days before next backup should be performed. If the specified number of days is exceeded, you will be prompted to perform backup on the GUI window of SystemWalker/StorageMGR.

To set a backup policy on the server list view, you display storage servers in a tree view on the server list view. The list of transaction volumes and backup volumes on this storage server will be displayed. After selecting a transaction volume for which you want to set a backup policy, click the right mouse button. From the popup menu, select [Set Backup Policy]. The following setup window will be displayed.

40

On this window, specify the number of interval days and the number of preservation generations and click the [OK] button. Perform this procedure on all the transaction volumes. You can set a backup policy also using the backup policy setting command (swstbkpolset).

· Even if the number of interval days has been specified, SystemWalker/StorageMGR does not automatically

collect backup. This value is used only to prompt the user to perform backup when the number of backup interval days is exceeded.

· When you set a backup policy, there must be as many registered backup volumes as required to perform backup according to the specified backup policy. For information on the necessary number of backup volumes, see Chapter 4.2.4, "Preparing a backup volume".

· Even though the number of backup volumes required for the backup may not have been registered beforehand when backup policies for synchronized high-speed backup were set, the number required can be set if the number of backup volumes that are required for snapshot fast backup have been registered. However, synchronized high-speed backup may not be able to be executed.

You can check what has been defined as follows: · Checking on a GUI window

You can view information on a backup policy on the transaction volume list view. For more information on the view, see the "SystemWalker/StorageMGR User's Guide".

· Checking using a command You can view information on a defined backup policy using the backup policy display command (swstbkpoldisp).

4.4.11 Preparing a device map file

In the backup operation on SystemWalker/StorageMGR, a backup volume with the same capacity as a transaction volume is automatically selected from the registered backup volumes.

If the backup volume is recognized in a "device map file", i.e., a file defining the correspondence between transaction and backup volumes, it must be created.

Create a device map file anywhere on the storage server that performs backup. If you specify this file while performing backup, an operation in recognition of the backup destination is enabled.

4.4.11.1 Describing a device map file

The following shows a description example of a device map file.

41

The following lists rules for creating a device map file. · Describe a transaction volume and a corresponding target backup volume in one line. Separate a transaction

volume and a backup volume with one or more "half-size blank or tab characters". One or more "half-size blank or tab characters" may be included between the beginning of a line and a transaction volume name or between the end of a backup volume name and the end of a line (newline character).

· A blank line ("half-size blank or tab characters") may be included in a file. · The portion from the symbol "#" to the end of a line is assumed as a comment. · You cannot specify more than one target backup volumes for one work disk in one device map file. In such a

case, the information in the line first found will be valid. While a device map file is read, the system will not detect such a redundant line.

· A device map file may include descriptions of transaction volumes other than the processing target (Device-Name or Log-Group-Name). (See the description example provided in the beginning of this chapter.)

4.5 Operation

This chapter describes the backup operation on SystemWalker/StorageMGR.

Before performing the backup operation, make environment settings required for the backup operation according to Chapter 4.4, "Preparations".

SystemWalker/StorageMGR has two kinds of backup operation as follows. · Snapshot fast backup operations · Synchronous high-speed backup operations

4.5.1 Performing the snapshot fast backup

Perform the snapshot fast backup as follows: 1. Before backing up a general file system, stop work. 2. Display the transaction volume list view and select a volume to be backed up.

42

3. From the Operation menu, select [Backup] to display the following window.

4. Check the displayed server names and transaction volume names and perform the following: - To use a volume automatically selected by SystemWalker/StorageMGR a backup volume:

Click the [OK] button. - To use a specific volume as a backup volume:

Specify a device map file created on the storage server that performs backup (e.g., /home/usr1/devmap1) and then click the [OK] button.

5. After the backup is completed, the following window will be displayed. Click the [OK] button and you will be

sent back to the transaction volume list view.

6. This completes backup. Now you can restart work. At this point, however, the physical copying of a volume is

not completed at the back end. To check the status of physical copying, do as follows: 7. Display the transaction volume list view and check the [Status] field of a target transaction volume. You can

check the current copying status because this field displays the progress status of copying processing.

43

8. To check the latest copying status, either: - Click the [PF5] key, or - Select [Refresh] from the View menu. 9. If you have stopped work in Step 1, restart the work.

· You can perform backup also using the backup execution command. · You can check the backup status also using the backup execution status display command.

4.5.2 Performing the synchronized high-speed backup

Perform the synchronized high-speed backup for a transaction volume as follows: 1. Display the transaction volume list view and select a volume to be backed up.

2. On the Operation menu, select [Begin Synchronized backup processing] to display the following window.

3. Check the displayed server name and transaction volume name, and perform one of the following operations: - To use a volume automatically selected by SystemWalker/StorageMGR as a backup volume:

44

Click the [OK] button. - To use a specific volume as a backup volume:

Specify a device map file name created on the storage server (e.g., /home/usr1/devmap1) for which backup will be performed and then click the [OK] button.

4. When the synchronized backup processing is completed, the window shown below appears. Click the [OK]

button to return to the transaction volume list view.

5. Physical copying from the transaction volume to backup volume now starts. To check the status of the physical

copying, do the following: 6. Display the transaction volume list view and check the [Status] field of the target transaction volume. This field

displays the progress of the coping processing. Use it to check the current status of the copying. 7. To check the latest copying status, perform one of the following operations: - Click the [PF5] key. - Select [Refresh] from the View menu. 8. The transaction and backup volumes enter equivalency maintain status when the [Status] field indicates

[Backup Preparation Completed]. 9. To create a backup history, select the target transaction volume from the transaction volume list view and

select [Backup] from the Operation menu. The following window appears.

10. Check the displayed server name and transaction volume name, and click the [OK] button. 11. When the backup is completed, the window shown below appears. Click the [OK] button to return to the

45

transaction volume list view.

The backup execution command causes an error if it is executed before the transaction and backup volumes have entered equivalence status.

The device map cannot be specified during backup.

· Backup can also be executed with the backup execution command. · The backup status can also be checked with the backup execution status display command.

4.5.3 Performing restoration

This chapter describes restoring a volume or data that has been backed up.

4.5.3.1 Restoring an entire volume

Restore all the data in a volume, which has been backed up in the snapshot fast backup as follows: 1. Stop work if you want to perform restoration on a general file system. 2. Display the transaction volume list view. Select a volume to be restored.

3. From the Operation menu, select [Restore] to display the following window. As the restore source volume, the

latest backup destination volume for the concerned transaction volume will be selected.

46

4. Check the name of volume to restore.

As the name of volume to restore, a transaction volume name selected in the transaction volume list view will be displayed. Click the [OK] button to restore data to this transaction volume. To change the restore destination, mark the Name of volume to restore checkbox, and then click the [...] button. The following window will be displayed.

Select a volume to which you want to restore data and then click the [OK] button. You will be sent back to the restore window. Check that the name of volume to restore is correct and then click the [OK] button on the [Restore Window].

5. The following window will appear when the restoration is completed. Click the [OK] button and you will be sent back to the transaction volume list view.

6. This completes restoration. Now you can restart the work. At this point, however, the physical copying of a

volume is not completed at the back end. To check the status of physical copying, do as follows: 7. Display the transaction volume list view and check the [Status] field of a target transaction volume. You can

check the current restoration (physical copying) status because this field displays the progress status of copying processing.

47

8. To check the latest information, either: - Click the [PF5] key, or - Select [Refresh] from the View menu. 9. If the transaction was stopped in 1, restart it.

· You can perform restoration also using the restore execution command. · You can check the restore status also using the restore execution status display command (swstbackstat). · See the SystemWalker/StorageMGR User's Guide for restoration in which absolute generations and relative

generations are indicated in the backup data that is subject to history management. (For absolute generations, 1 is assigned to the data backed up first and the number increases sequentially. For relative generations, 1 is assigned to the latest data, and the number increases as the data becomes older.)

4.5.3.2 Restoring an individual file

Restore an individual file as shown below. Note that you cannot restore an individual file on the GUI window. 1. Mount backup volume. To check backup volume by the history list view or executing history information display

command. 2. Copy files to restore by the cp command. 3. Unmount backup volume.

4.5.4 Managing a backup history

Display backup history information to check backup volume names, backup date, etc. of backup data under generation management for a transaction volume.

· Backup history information is used to manage only information stored on a backup volume. · Any backup history information exceeding the number of preservation generations defined in a backup policy

will be automatically deleted.

4.5.4.1 Displaying a backup history

You can display a backup history on the backup history list view. To display the backup history list view, first access the server list view, display a storage server in a tree view, and select a transaction volume on the storage server.

48

You can display a backup history also using the history information display command.

4.5.4.2 Deleting a backup history

Delete a backup history on the server list view. If you display a storage server in a tree view on the server list view, a list of transaction volumes on this storage server will be displayed. After selecting a transaction volume for which you want to delete a backup history, click the right mouse button and, from the popup menu, select [Delete History]. The following setup window will be displayed.

Carefully check the displayed server name and transaction volume name and click the [OK] button.

You can delete a backup history also using the history information delete command.

4.6 Changing the setting information

You need to change the setting information of SystemWalker/StorageMGR if any change is made on a storage server or device used in the backup operation. This chapter describes changing the setting information when various changes are made.

4.6.1 Adding a device

After a device is added to any storage server, incorporate it in the backup operation of SystemWalker/StorageMGR as follows: 1. Display the initial window. For more information, see Chapter 4.4.3, "Starting the initial window". 2. Fetch all the device information for a storage server. When device information is fetched, a newly added

device will be detected. Move it to the [Device to be added] field. For information on fetching device information, see Chapter 4.4.5, "Fetching device information on a storage server".

49

3. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup management window".

4. Set the operation type for a device that has been added. For more information, see Chapter 4.4.8, "Setting the operation type for a device".

5. If the added device has been defined as a transaction volume, set a backup policy for it. For more information, see Chapter 4.4.10, "Setting backup policies".

4.6.2 Deleting a device

This chapter describes deleting a device depending on the device type.

4.6.2.1 Deleting a transaction volume

To delete a transaction volume, follow the steps shown below. 1. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup

management window". 2. Delete a backup history for the transaction volume to be deleted. For more information, see Chapter 4.5.4.2,

"Deleting a backup history". 3. Delete a backup policy for the transaction volume to be deleted.

If you display a storage server in a tree view, a list of transaction volumes on this storage server will be displayed. After selecting the transaction volume for which you want to delete, select delete backup policy. You can click the right mouse button or from the popup menu, select [Delete backup policy]. The following setup window will be displayed.


4. Delete device information for a transaction volume to be deleted. After selecting a storage server, select [Set Device Information] from the [Operation] menu. The following setup window will be displayed.

50

Move a target transaction volume displayed in the "Transaction Volume" field to the "Other Volume" field. Click the [>] button to move a transaction volume.

4.6.2.2 Deleting a backup volume

To delete a backup volume follow the steps as shown below. 1. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup

management window". 2. Send the backup volume to be deleted into the unused status.

When a volume is unused, this volume does not exist in a backup history. If the volume exists in a backup history, delete the backup history. If the volume is already unused, skip to the next step.

3. Delete device information for the backup volume to be deleted. After selecting a storage server, select [Set Device Information] from the [Operation] menu. Then, the following setup window will be displayed.

51

Move a target backup volume displayed in the "Backup Volume" field to the "Other Volume" field. Click the [>] button to move a transaction volume.

If a backup volume is deleted, an already defined backup policy may no longer be met (e.g., the number of backup volumes is less than the number of preservation generations). In such a case, the backup operation can no longer be continued. To avoid such a status, be sure to check already defined backup policies before deleting a backup volume.

If only an insufficient number of backup volumes exist as described earlier, first register a backup volume and then delete the target backup volume.

4.6.3 Adding a storage server

Add a storage server to the backup operation as follows: 1. Display the initial window. For more information, see Chapter 4.4.3, "Starting the initial window. 2. Register a storage server. For more information, see Chapter 4.4.4, "Registering a storage server". 3. Fetch all the information of devices connected to the added storage server. For more information, see Chapter

4.4.5, "Fetching device information on a storage server". 4. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup

management window". 5. Set the information for the storage server. For more information, see Chapter 4.4.7, "Setting the environment

for a backup operation server". 6. Set the operation type for a device whose information has been fetched in Step 3. For more information, see

Chapter 4.4.8, "Setting the operation type for a device". 7. Set a backup policy for all the transaction volumes registered in Step 5. For more information, see Chapter

4.4.10, "Setting a backup policy".

4.6.4 Deleting a storage server

To delete a storage server follow the steps as shown below. 1. Display the backup management window. For more information, see Chapter 4.4.6, "Displaying the backup

management window". 2. Delete the backup history for all the transaction volumes on the storage server to be deleted. For more

information, see Chapter 4.5.4.2, "Deleting a backup history". 3. Delete the backup policy for all the transaction volumes on the storage server to be deleted.

If you display a storage server in a tree view, a list of transaction volumes on this storage server will be

52

displayed. After selecting a transaction volume for which you want to delete, delete the backup policy. Click the right mouse button and from the popup menu, select [Delete backup policy]. The following setup window will be displayed.


4. Delete device information on the storage server to be deleted. After selecting a storage server, select [Set Device Information] from the [Operation] menu. The following setup window will be displayed.

Move all the volumes displayed in the "Transaction Volume" and "Backup Volume" fields to the "Other Volume" field. Click the [>] button to move volumes.

5. Display the initial window. For more information, see Chapter 4.4.3, "Starting the initial window". 6. Delete a storage server.

Select a storage server and select [Deletion of Server] from the Operation menu. The following window will be displayed.

53

Carefully check the server name and click the [OK] button.

4.7 Stopping the Operation

To stop a backup operation, stop daemons on the Storage server. Normally, they are automatically stopped when the system stops.

To stop a daemon on a server, execute the following command on the server:


When the daemons stop, all functions of StorageMGR running on the storage server stop.

Stop daemons on a storage management server only after checking that all the storage servers that it manages are stopped.

54

Chapter 5 Backup Operations (SymfoWARE)

[Deleted]

55

Chapter 6 Backup with the SP Series

This chapter describes backup with the SP Series.

6.1 Overview

In backup management, the volumes that are backed up with linkage to models of the SP series are managed as transaction volumes under control of the SP series models.

At the time of performing backup/restore, these volumes are backed up/restored with models of the SP series.

See the Storage Management Processor Administrator's Guide for details on how to back up/restore these volumes.

[Figure 6.1 Backup management configuration ]


Design/set up the backup operation as described below: 1. Determining the server to perform backup 2. Determining the backup target 3. Determining a backup policy 4. Preparing a backup volume

6.2.1 Determining the server to perform backup

Determine the server that will be used to perform backup.

The following servers can be used to perform backup: · Storage management server

This server performs central management and operation of multiple Storage servers. The Storage management server can also act as a Storage server

· Storage server

57

This server controls SystemWalker/StorageMGR.

The C locale must be installed on all Storage servers.

58

[Figure 6.2 Example of Storage management server and Storage server configuration]

6.2.2 Determining the backup target

To perform backup management in linkage with models of the SP series, define the backup target as a transaction volume of the SP series.

59

Because the device to be backed up must be managed by a model of the SP series, system design and setup with respect to the SP series models must be performed first. See the Storage Management Processor Administrator's Guide and Storage Management Processor Installation Guide for details on how to perform system design and setup with respect to the devices of the SP series.

Specify the devices for which backup is to be performed with the device information setting command. The setting status with respect to the devices for which backup is to be performed can be referenced by the device usage status display command.

6.2.3 Determining a backup policy

Set a backup policy for the transaction volume controlled by the SP series. Do not use SystemWalker/StorageMGR. Instead, use the SP series GUI.

See the Direct Backup User's Guide for details on how to set the backup policy via the SP series GUI.

Because the policy for the transaction volume operated by the SP series must be set by the SP series GUI, the following commands cannot be executed for a transaction volume controlled by the SP series:

· Backup policy setting command · Backup policy display command · Backup policy deletion command

6.2.4 Preparing a backup volume

In backup/restore linking with the SP series, a backup volume is managed by the SP series. When you design/setup the backup volume, do not use SystemWalker/StorageMGR. Instead, use the SP series GUI. For more information about the SP-series GUI, see the Direct Backup User's Guide.

6.3 Flow of Operation

The following figure shows the flow of backup with the SP series.

60

6.4 Preparations

Before the start of backup, the following preparations are required.

6.4.1 Activating daemons

Before starting a backup operation, daemons on the Storage management server, Storage servers, and SP servers must be activated. Normally, they are automatically activated.

However, if the daemon failed to start for some reason or has stopped, execute the following command and start the daemons on each server.


The SystemWalker/StorageMGR service must be started on the storage management server, storage server and SP server when these servers are Windows servers. In general, the service is automatically started at system startup. However, if the service failed to start for some reason or has stopped, it must be started on each server. For information about starting the service, see Chapter 2, "Starting and Stopping a Service." in the SystemWalker/StorageMGR Operator's Guide (Windows version)

6.4.2 Setting an access permission

Set the access permission for the backup operation management window. For details of the setting, see Chapter 3, "Security Operation Using Authentication Feature".

6.4.3 Starting the initial window

Use the following URL to start the SystemWalker/StorageMGR initial window:

61

http://storage-management-server-address(:port-number)/swstorage/index.html

The following GUI (server list view) starts.

6.4.4 Registering Storage server and SP server

Register the Storage server and SP server to be managed.

Register them from the GUI. Select [Addition of Server] from the Operation menu. The following window appears.

Specify the server name, IP address, and port required for communication with the Storage server to be added. If the Storage server is being operated as part of a cluster, specify the inherited IP address of the Storage server that is defined for StorageMGR as the IP address

For the port number, specify the port number specified for the stgxfws service on the Storage server or SP server.

When the SP server is registered, the SystemWalker/StorageMGR server list view appears, as shown below

62

The Storage management server need not be registered because it is registered during repository setup.

6.4.5 Fetching device information on a storage server

To perform backup management, information on the devices of each Storage server must be stored in the repository. To fetch information on the devices of each Storage server, choose "Acquisition and reflection of information on all devices" from the Operation menu. The following window opens. Information about the hardware of the SP server need not be acquired because the SP server is not managed by StorageMGR.

Confirm the server for which you want to fetch device information, and then click the OK button.

After device information is fetched from each server, the following dialog box opens.

63

The uppermost list box is displayed when a new device is detected. Move the entries for devices to be managed into the left box. The second list box displays currently managed devices that cannot be detected at this time. When you want to exclude a device from management, move the device entry into the right-hand box. The lowermost list box displays devices for which information has been updated (those, for example, for which the mount point name has been changed).

After performing the above operation, click the OK button to reflect the configuration information. For an explanation on the SystemWalker/StorageMGR device name, see Chapter 1.6, "Managing a Device on SystemWalker/StorageMGR", in the SystemWalker/StorageMGR Operator's Guide (Windows version).

It takes the time proportional to the total of the device defined in the selected Storage server for this operation. Please execute CPU load and the I/O load low when there are a lot of numbers of devices.

It takes about 0.5 seconds a device (partition) as a standard with there no load, and refer, please.

6.4.6 Displaying the backup management window

When [Backup Management] is selected from the [File] menu of the server list view, the backup management server list view appears.

64

6.4.7 Setting the environment for a backup operation server

Set the environment for each storage server. When [Set Server Information] is selected from the Operation menu while the storage server is selected on the backup management window, the following setting window appears.

When the storage management server used as a storage server, this environment setting is also required. This work is not needed when the storage server environment has already been set. · This environment setting can also be performed for the storage server configuration information setting

command.

6.4.8 Setting the operation type for a device

Before performing backup, set the operation type of the device as follows: · Define each volume to be backed up as a transaction volume. · Define each backup destination volume as a backup volume.

+Defining the transaction volume

Before performing backup with the Storage server, define the device to be backed up as a transaction volume in linkage with the SP series model by executing the device information setting command.

Because the device to be backed up must be managed by a model of the SP series, system design

65

and setup must have been performed with respect to the SP series. See the Storage Management Processor Administrator's Guide and Storage Management Processor Installation Guide for details on the method of design and setup with respect to the SP series.

The setting status of the device to be backed up can be referenced with the device usage status display command.

+Defining the backup volume

For backup/restore in linkage with a model of the SP series, the backup volume specified as the backup destination is managed by the SP series model and system design and setup of the backup volume is to be performed via the SP series GUI. See the Direct Backup User's Guide for details on the SP series GUI.

6.4.9 Setting backup policies

Set the backup policy for the transaction volume under control of the SP series model by using the SP series GUI.

See the Direct Backup User's Guide for details on the SP series GUI.

Because the backup policy for the transaction volume controlled by the SP series model is set by the SP series model, the following commands cannot be executed for the transaction volume operated by the SP series model:

· Backup policy setting command · Backup policy display command · Backup policy deletion command

6.5 Operation

This chapter describes how to perform backup with models of the SP series.

Before performing backup, set up the environment needed for backup, as described in Chapter 6.4 "Preparations".

The same operations as performed by the commands used for backup can also be performed via the SP series GUI. See the Direct Backup User's Guide for details on the SP series GUI.

6.5.1 Executing backup

Perform backup in linkage with models of the SP series with the backup execution command.

Because the SP series manages disks for backup in linkage with the SP series, confirm the backup status by using the SP series GUI. See the Direct Backup User's Guide for details on the SP series GUI.

+Snap shot backup

To perform snap shot backup, use the backup execution command.

+Synchronous high-speed backup

Perform synchronous high-speed backup as described below: 1. Start backup synchronous processing by executing the backup synchronous processing start command. To

cancel backup synchronous processing, use the backup synchronous processing cancel command. 2. Execute the backup execute command.

66

6.5.2 Executing restore

Perform restore in linkage with models of the SP series by using the restore execution command. To stop restore operations, and to terminate restore operations that cannot be terminated even if an error occurs, use the GUI of the SP series.

For information about the GUI of the SP series, refer to the Direct Backup User's Guide.

Contents of a transaction volume cannot be used if a restore operation for the volume has been canceled.

In linkage with models of the SP series, the SP series models manage the disks for restore. Therefore, confirm the restore status by using the SP series GUI. See the Direct Backup User's Guide for details on the SP series GUI.

6.5.3 Managing backup histories

In linkage with models of the SP series, the SP series models manage the history of backups.

Therefore, the backup history cannot be displayed or deleted using SystemWalker/StorageMGR.

Use the SP series GUI to display or delete the backup history. See the Direct Backup User's Guide for details on the SP series GUI.

6.6 Stopping Backup

To stop the backup, stop the service on the storage server. In general, the service stops when the system stops.

To stop the daemon on the SP server for some reason, use the following command on the server:


In order to stop a backup operation where the OS of the Storage management server or Storage server is Windows, stop the service on the Storage server. Normally, the service is automatically stopped when the system stops. If the service must be stopped, it can be stopped on individual servers. For more information, see Chapter 2, "Starting and Stopping Service," in the SystemWalker/StorageMGR Operator's Guide (Windows version).

When the service stops, all functions of StorageMGR running on the Storage server stop.

Before stopping the service or daemon running on the Storage management server, confirm that the operations on all managed Storage servers have stopped.

6.7 Steps for Increases/Decreases in the Number of GR Cabinets to Be Managed

In SystemWalker/StorageMGR, information about GR cabinets managed by devices of the SP series is stored in a repository. When adding GR cabinets to or removing GR cabinets from those managed by devices of the SP series, these changes must be reflected in the repository.

6.7.1 Reflecting changes

After starting the Web GUI of SystemWalker/StorageMGR, refer to Chapter 1.2.6.5, "Changing GR cabinet management information of the SP series," in the SystemWalker/StorageMGR User's Guide, to perform the operation to reflect changes.

67

Chapter 7 Replication Operation

This chapter explains SystemWalker/StorageMGR replication in a Solaris system. SystemWalker/StorageMGR uses a slice as the replication unit. In this manual, the term "volume" is used instead of "slice."

7.1 Overview

This chapter explains the SystemWalker/StorageMGR replication function.

Using the advanced copy function (OPC or EC function) of a disk array unit, the SystemWalker/StorageMGR replication function performs high-speed replication between volumes, regardless of the volume capacities.

Replication that uses the One Point Copy (OPC) or Remote One Point Copy (ROPC) function of a GR series disk array unit is called snapshot replication. Replication that uses the Equivalent Copy (EC) or Remote Equivalent Copy (REC) function is called synchronized replication.

The replication function creates copies so that the information at a certain point of time can be used for some other purpose than the original one. It can be used independently of or combined with the backup function.

7.1.1 Snapshot replication processing

Replicas are created by copying from an original volume to a replica volume using the OPC or ROPC function of a GR series disk array unit.

The snapshot replication performs the following two types of processing: 1. When a copy is created, the snapshot processing (OPC or ROPC) from the original volume to the replica

volume is executed with the replication creation command (swsrpmake). The replication creation command dismounts or mounts the original volume. This processing determines the original data (for details, see Appendix C, "Replication Script"). ((1) to (4) in Figure 7.1)

2. If the user wants to re-create a replica, only the replication creation command is required. If the previous snapshot processing is in progress, it is stopped and new snapshot processing is started.

69

[Figure 7.1 Snapshot replication processing]

Snapshot replication is completed when the replication creation command is issued. The actual data is internally copied by the OPC or ROPC function of the GR series disk array unit.

· The GR740 unit is required when snapshot replication uses the ROPC function of a GR series disk array unit.

7.1.2 Synchronized replication processing

Replicas are created by copying from the original volume to the replica volume using the EC or REC function of a GR series disk array unit.

Synchronized replication uses two methods to create a copy: full copying and incremental copying. (In full copying, the original volume is completely copied; it is not partially copied. In incremental copying, only the data from the previous copy that has been updated is copied.) · Creating replicas with full copying

Use this method to create the first copy in a replication. · Creating copies with incremental copying

Use this method to create later copies once a previous replica already exists. Copies are created by reflecting the data that has been updated after a previous has been made (full copying and incremental copying).

The following is the procedure for synchronized replication: 1. Upon starting synchronized processing from the original volume to the replica volume, using the synchronous

processing start command (swsrpstartsync) , full copying, likewise, starts. ((1) in Figure 7.2)

70

2. Full copying is complete. The original volume and replica volume both enter equivalence status. From this point on, updating of the original volume is sequentially reflected in the replica volume so that data equivalence is always maintained (equivalency holding state). (States in (2) and (3) in Figure 7.2)

3. Synchronized processing is temporarily stopped with the replication creation command (swsrpmake) to create a copy of the original volume. The replication creation command dismounts or mounts the original volume. This processing determines the original data (for details, see Appendix C, "Replication Script"). After execution of the replication creation command, the replica volume can be accessed (copy established status). (States in (3) and (4) in Figure 7.2)

4. To create another copy, the synchronized processing that has been temporarily stopped is restarted with the synchronous processing start command. For this copy, only the updated data (incremental) on the original volume since the previous copy was made until the restart of synchronized processing is copied to the replica volume. ((4) in Figure 7.2)

5. When copying of the incremental data has been completed, the status returns to equivalency holding state again. (States in (5) and (6) in Figure 7.2)

6. When this status has been set, the copy is re-created with the replication creation command. ((6) in Figure 7.2)

[Figure 7.2 Synchronized replication processing]

· The GR740 is required to use the EC or REC function of a GR series disk array unit for synchronized

replication. · The replication creation command cannot be executed unless both the original volume and replica volume are

in equivalence status.


This chapter explains the operation of SystemWalker/StorageMGR replication.

Design replication with the following procedure:

71

· Determine the server that performs replication. · Determine the replication target.

7.2.1 Determining the server that performs replication

Determine the server that performs replication.

The following servers are used to perform replication: · Storage management server

Multiple storage servers are unified and operated centrally. The storage management server can also be used as a storage server.

· Storage server SystemWalker/StorageMGR operations are performed.

[Figure 7.3 Configuration of the servers that perform replication]

The following requirements apply when box-tobox replication is performed using the remote copying function (ROPC or REC) of a GR series disk array unit: · The ROPC or REC function must be installed in both boxes. · Both boxes must already be connected using an FC remote adapter (FCRA). In a connection that uses an

FCRA, data flows only from INIT side to TARG side. For bi-direction copying, at least two FCRA connections are required.

7.2.2 Determining a replication target

Determine the original volume and replica volume to be used in the replication. · The original volume is the volume on which the data to be copied is stored. · The replica volume is the volume on which a copy of the data on the original volume is stored. In addition, determine the following attributes to be assigned to the original volume and replica volume: 1. Copy direction

Determine the direction of copying used in replication. Specify one of the following directions: - bi-direction: Copying is bidirectional between the original volume and replica volume. - uni-direction: Copying is done only from the original volume to the replica volume. During this operation,

72

copying from the replica to the original volume is to be disabled. 2. Operation servers (used only for server-to-server replication)

For server-to-server replication, replication of the target original volume or replica volume can be performed only with either the original sever or replica server.

- Original server: Storage server to which the original volume is connected - Replica server: Storage server to which the replica volume is connected

[Figure 7.4 Servers used in performing replication]

In this manual, a storage server used to perform replication is called the operation server. An original server or replica server is specified as the operation server.

An operation server can use all of the replication functions. In contrast, any other type of server can use only the information display function and operation release function.

SystemWalker/StorageMGR Standard Edition (SE) and Enterprise Edition (EE) have the replication functions listed below.

Product Replication functions provided

Standard Edition(SE) Intraserver replication function

Enterprise Edition(EE)

Server-to-server replication function

Supports replication between different OSs. (Solaris, Windows)

Note: Support of replication between different OSs means that data can be copied between different OSs. It does not mean that a replica server can access the data of a different OS.

· When Windows is an original server and Solaris is a replica server, the replica sever can access the replica volume as a raw partition.

· When Solaris is an original server and Windows is a replica server, the replica server cannot access the replica volume.

SystemWalker SE and EE can both use the box-to-box copy function (ROPC and REC).

73

[Figure 7.5 Replication function provided with each SystemWalker/StorageMGR]

7.3 Flow of Operations

The following figure shows the flow of the replication operations.

7.4 Preparations

The following preparations are required before replication can start.

7.4.1 Starting a daemon

Before replication is started, the SystemWalker/StorageMGR daemon must be started on the storage management

74

server and storage server. In general, the daemon is automatically started at system startup. However, if the daemon failed to start for some reason or has stopped, both servers must restart the daemon by following command.


7.4.2 Starting the initial screen

Use the following URL to start the SystemWalker/StorageMGR initial screen:

http:// storage-management-server-address(:port-number)/swstorage/index.html

The following GUI (server list screen) will be started.


On the storage management server, register the storage server to be managed. Register it from the GUI. Select [Addition of Server] from the Operation menu. The following screen appears.

Specify the name and IP address of the storage server to be added and the port number required for communication.

Specify as the port number the "communication-service-port-number" specified when SystemWalker/StorageMGR-A was installed.

7.4.4 Fetching device information from a storage server

As part of replication management, device information on a storage server must first be stored in the repository. To a storage server device, select [Acquisition and Reflection of information on all devices] on the Operation menu. The following screen appears.

75

After checking the server from which device information should be acquired , click the [OK] button.

After the device information has been obtained from each server, the following dialog box appears.

There are 5 list boxes in the dialog box: the top list box, which is displayed when a new device is detected; the second list box, which lists the devices not currently detected from the devices being managed; the bottom list box, which lists the devices whose information has been updated(for example, the mount point name was changed); the left list box; and the right list box. Move the device to be managed to the left list box , wehereas, move the device to be excluded from the management to the right list box.

After the above operations, click the [OK] button to accept the configuration information.

7.4.5 Setting the original volume and replica volume

Use the replication volume information setting command (swsrpsetvol) to set the original volume and replica volume that will be used in the replication. The information on the registered original volume and replica volume can be checked with the replication volume information display command (swsrpvolinfo).

When specifying the volume of another storage server in server-to-server replication, specify the volume in the format "volume-name@storage-server-name."

76

7.5 Operations

This chapter explains SystemWalker/StorageMGR replication.

Before performing backup, see Chapter 7.4, "Preparations," to set up the environment required for replication.

7.5.1 Executing snapshot replication

Use the replication creation command (swsrpmake) to perform snapshot replication.

· The opration of replicationi is provided only with the above CLI(Command Line Interface).

It isn't provided with GUI(Graphical User Interface).

7.5.2 Executing synchronized replication

Perform synchronized replication using the following procedure: 1. Start synchronized processing using the synchronous processing start command (swsrpstartsync). Use the

replication cancellation command (swsrpcancel) to cancel synchronized processing that has already started. 2. After making sure that equivalency holding state has been established with the operation status display

command, temporarily stop synchronized processing with the replication creation command (swsrpmake) to create a replica of the original volume.

3. To copy the updated (incremental) data, restart synchronized processing with the synchronous processing start command.

· The opration of replicationi is provided only with the above CLI(Command Line Interface).

It isn't provided with GUI(Graphical User Interface).

7.5.3 Backup and restoration using the replication function

Data can be restored from the replica volume to the original volume if a volume pair has been defined bi-direction copying with the replication volume information setting command (swsrpsetvol).

In contrast to executing replication, restoration can also be performed by specifying the original volume and replica volume in the replication creation command (swsrpmake).

7.6 Changing the Setting Information

When a storage server or device required in the replication operation has been changed, the information set in SystemWalker/StorageMGR must be changed. This chapter explains how to change the information set in SystemWalker/StorageMGR.

7.6.1 Changing an original volume or replica volume

To change the attributes (copy direction, operation servers of server-to-server replication) of the otihinsl volume and replica volume that are set, delete the information with the replication volume information deletion command (swsrpdelvol) and then reexecute the replication volume information setting command (swsrpsetvol).

7.6.2 Deleting an original volume or replica volume

To delete the original volume or replica volume that are set, use the replication volume information deletion command (swsrpdelvol).

7.7 Stopping the Operation

To stop the replication processing, that is in progress, or to change the snapshot replication into the synchronized replication, use the replication cancellation command (swsrpcancel).

To stop replication operation, stop the daemon on the storage server. In general, the daemon stops when the system stops.

To stop the daemon on the storage server for some reason, use the following command on the server:


77

When the daemon stops, all functions of StorageMGR running on the storage server stop.

Before stopping the storage management server daemon, make sure that operations on all storage servers under management have stopped.

78

Chapter 8 SAN Resource Management Operation

This chapter describes operation of SAN Resource Management.

8.1 Flow Of SAN Resource Management Operation

The SAN Resource Management function performs integrated management on existing storage systems and those that will be installed in the future. (SAN device integrated management does not place any limitations on device operation. After a device is defined as a device under management of the SAN Resource Management function, manual setup and setup with other tools can be made as usual for the device.)

Since the range of support for the SAN Resource Management function has been repleted for the SAN function, this chapter mainly describes operation for a storage system in a SAN configuration based on Fibre Channel. Even for a storage system that does not use a Fibre Channel switch, functions such as reading and display of device configuration, failure and performance management, management screen linkage are available. So, it is possible to centralize management with this software.

8.1.1 Check Items Before Operation

1. Support hardware and support level The functionality supported by the SAN Resource Management for support hardware and current support software is described in Chapter 1.5, "Hardware Requirements." The description in that chapter is based on this support level.

2. Recommendation of the doubled Fibre Channel (cascaded) switch Since at present the zoning information of a Fibre Channel switch cannot be restored from the SAN Management database, multiple Fibre Channel switches need to be cascaded so that the zoning information stored in a Fibre Channel switch is not deleted. Because each of the cascaded Fibre Channel switches holds the zoning information, the zoning information is preserved if any of the Fibre Channel switches fails.

8.1.2 Flow Of Operation

When building or rebuilding a SAN, build an environment according to the procedure as follows.

After you install SAN Resource Management and register a device, when starting SAN Management Server without starting a client window (SAN Management window), it performs processing at the time of obstacle surveillance/obstacle for a registered device. And securing performance information is continued also to device while carrying out performance management.

79

[Figure 8.1 Flow of SAN Resource Management operation]

8.2 Description And Setup Of Devices To Be Managed

In general, the SAN Resource Management manages devices directly by using the LAN interface of each device.

80

However, there is a device not having a LAN interface, in this case the device is managed via the LAN by using the device's management program installed on the server. The following figure shows which path is used by the SAN Resource Management to communicate with each device and perform management.

This chapter describes how to manage each device. It also covers configurations required for management by the SAN Resource Management as well as notes on these configurations.

8.2.1 Solaris Server

The SAN Resource Management provides two management methods. These are managing with and without installing the SAN Management agent (StorageMGR-A).

When the SAN Management agent is installed, automatic device detection/automatic configuration incorporation/failure and state monitoring of Fujitsu's multipath disk control feature/setup of an access path including binding (storage affinity) of the HBA of the server are enabled for the SAN Resource Management. When the SAN Management agent is not installed, the method is equivalent to the one described in Chapter 8.2.3, "Other Servers".

Notes on building a system in a SAN environment that uses Fibre Channel are provided as follows. 1. Installation of a Fibre Channel host bus adapter (HBA)

Install a Fibre Channel host bus adapter before starting the server. 2. N port setup

When a SAN is built with an HBA directly connected to the Fibre Channel switch, the port type of the Fibre Channel host bus adapter (HBA) of the server must be N port. The method of changing the port of HBA into N port changes with kinds of HBA. Each method is described as follows.

a. GP7B8FC1 (FJPFCA) driver In the /kernel/drv/fjpca.conf file, provide the following port type description for each instance name (adapter) of fjpfca: port=

"fjpfca0:nport",

"fjpfca1:nport"; b. SN10-FC01, FC64-1063 (FCAW driver) from JNI Corporation

Set the fca_nport parameter of the /kernel/drv/fcaw.conf file to 1, as follows. # Configuration flagfca_nport

# Type: boolean; default: 0(false)

# If false(0), then fca initializes on a loop

81

# If true(1), then fca initializes as an N_Port

# and fabric operation is enabled

fca_nport=1; Moreover, the following setup is required to enable access path binding. (The setup below enables the setup of binding to be reflected in the FCAW driver.) # Configuration flag def_hba_binding

# Type: string; default: "fcaw*" (means all target/lun instances will be

# initialized by all fcainstances)

# Sets the default HBA binding for every target/lun instance which does not

# explicitly define one.

# -A "*" following an hba name indicate all instances of that hba driver

# * See technot for details on hba bindings

def_hba_binding="nonjni"; c. LP7000/8000/9000 (LPFC driver)

Set the topology parameter of the /kernel/drv/lpfc.conf file to 2, as follows. # topology: link topology for initializing the Fibre Channel connection.

# 0 = attempt loop mode, if it fails attempt point-to-point mode

# 2 = attempt point-to-point mode only

# 4 = attempt loop mode only

# 6 = attempt point-to-point mode, if it fails attempt loop mode

# Set point-to-point mode if you want to run as an N_Port.

# Set loop mode if you want to run as an NL_Port.

topology=2; d. QLA2200 (QLA2200 driver)

Set the hba0-connection-options parameter of the /kernel/drv/qla2200.conf file to 1, as follows. # Connection options

# 0 = loop only

# 1 = point-to-point only

# 2 = loop preferred, otherwise point-to-point

hba0-connection-options=1;

The following restrictions apply when a Solaris server is managed with the SAN Management agent. 1. The WWNN and PID binding (storage affinity) setups of an HBA are not supported.

The SAN Resource Management performs automatic access path management by using a WWPN (World Wide Port Name). Therefore, if WWNN (World Wide Node Name), PID, and TID binding setups have already been made with the host bus adapter (HBA) on the server side, the setup needs to be changed to WWPN binding before SAN Resource Management registration. Those servers that have WWNN, PID, and TID binding setups cannot be registered in the SAN Resource Management.

2. When an HBA (SN10-FC01, FC64-1063 of JNI Corporation) binding setup has not been made When an SN1.0-FC01 or FC64-1063 from JNI Corporation is used in an environment where an HBA binding setup has not been made, the value of def_hba_binding of /kernel/drv/fcaw.conf must be set to "fcaw*". (When the value is set to "nonjni", the previous configuration may no longer be visible.) When the value is set to "fcaw*", the access path from the HBA of the server can be displayed but cannot be managed by the SAN Resource Management.

82

8.2.2 Windows NT/2000 Server

The SAN Resource Management provides two management methods. In one method, the SAN Management agent (StorageMGR-A) is installed for the Windows server. In the other method, management is performed without installing the SAN Management agent.

When the SAN Management agent is installed, automatic device detection/automatic configuration incorporation/failure and state monitoring of Fujitsu's multipath disk control feature/setup of an access path including binding (storage affinity) of the HBA of the server are enabled for the SAN Resource Management. When the SAN Management agent is not installed, the method is equivalent to the one described in Chapter 8.2.3, "Other Servers".

Notes on building a system in a SAN environment that uses Fibre Channel are provided as follows. 1. Installation of a Fibre Channel host bus adapter (HBA)

Install a Fibre Channel host bus adapter before starting the server. 2. Editing of the SAN Management agent setup file

The WWPN (World Wide Port Name) of the HBA being installed needs to be defined in the SAN Management agent setup file (wwpn.dat). This work is not required when building environment by methods other than these. The procedure for editing is described below. * GP5-FC101 V1.1L10(Driver 6.17) * Emulex LP7000/8000/9000

a. Obtaining the WWPN of the HBA and logical HBA number being installed. In the case of GP5-FC 101V1.1L10 (Driver 6.17) It is possible to get from the "Fast!UTIL" utility indicated by "HardWare Installation Guide" of HBA attachment. Although an acquisition procedure is described as follows, the details of a utility should refer to readme.txt of this writing or driver attachment. * Reboot the Windows system which carried HBA. * When the following message is displayed, go into the "Fast!UTIL" view by ALT-Q. Press <Alt-Q> for Fast!UTIL * WWPN is acquired from "Configuration Setup"-"Host Adapter Setup" view. * When two or more HBA are carried, HBA is chosen by "Select Host Adapter" and WWPN is acquired. Moreover, keep in mind that a henceforth needed logic HBA number assigns from 0 in accordance with each turn of HBA displayed by "Select Host Adapter. * Escape from "Fast!UTIL" by repeating ESC and reboot a system. In the case of LP7000/8000/9000 Emulex It is acquirable from Miniport Driver Utility"LightPulse Utility" (c:¥winnt¥system32¥lputilnt.exe) of HBA attachment. Even if you use this utility, when WWPN is unknown, or when the usage of a utility is unknown, please ask the selling agency of HBA.

b. Edit the wwpn.dat which is a setup file located under the installation folder of SystemWalker/StorageMGR-A/M with a text editor according to the example as follows. [¥etc¥san¥wwpn.dat is the example of description in the environment definition directory]

#/* */

#/* HBA WWN setup */

#/* Emulex : lpfcY */

#/* */

#/* 0 10 20 30 40 50 */

#/* +---------+---------+---------+---------+---------+---------+ */

#/* xxxxX =XXXXXXXXXXXXXXXX */

#/* xxxxY =YYYYYYYYYYYYYYYY */

#/* wwwwW =WWWWWWWWWWWWWWWW */

#/* zzzzZ =ZZZZZZZZZZZZZZZZ */

lpfc0 = 10000000c920d31b;

lpfc1 = 10000000c920d446;

83

c. Define WWPN with the form of lpfcY for every HBA, and please be sure to start a new line by ";". d. Y in lpfcY represents a logical HBA number. To obtain a logical HBA number, use the lputil driver utility

available from Emulex Corporation. When the set value of a WWPN is incorrect, the SAN Resource Management cannot display the target HBA.

3. Set up a HBA topology with the N port The connection topology to a Fibre Channel needs to be explicitly specified in the driver parameter in the registry. If this operation is not performed, unpredictable operation can occur in the fabric environment. Please perform this operation when a connection is to be made to a switch. The procedure for setup the topology is described as follows.

a. Open the registry editor. Choose [Start]-[Run] from the task bar, then run the following program: regedit.exe

b. Open the following registry keyword, and change the value of Topology to 1: HKEY_LOCAL_MACHINE¥

SYSTEM¥

CurrentControlSet¥

Services¥

[driver-name]¥

Parameters¥

Device¥

"DriverParameter" Topology=1

· The DriverParameter value depends on the version of the driver. There may be no Topology WORD depending

on the number of versions. In this case, add it. For more information, see the readme file provided with the driver, or contact the HBA vendor.

· [driver-name] of the registry key is lp6nds35 for Windows NT4.0. For Windows 2000, it is lpxnds. · When multiple Emulex HBAs are installed and used in Fibre Channel connections with different topologies,

perform this operation for each HBA. For more information, see the readme file provided with the driver, or contact the HBA vendor.

· When an Emulex HBA is added to a Windows 2000 system, note that the previous registry value may be initialized. When Windows 2000 recognizes a new device, Windows 2000 automatically installs the driver. Therefore, when Windows 2000 recognizes a different model HBA, the driver may be reinstalled. Accordingly, when adding a different model HBA, be sure to perform this operation.

· This procedure modifies the registry. Note that if the contents of the registry are destroyed by an operator error

84

or by some unknown operation, the Windows system may not start. Always be careful when performing this operation.

· The Emulex HBA driver that can be used with Windows 2000 is not the same as that of with Windows NT. So, if the OS is changed, the drivers must also be changed.

· When a QLA2200 from QLogic Corporation is used, the driver version 8.00.08 or above is recommended. With version 7.05.05, an access path deletion is not performed correctly.

8.2.3 Other Servers (Such As AIX/HP/Linux, Or Solaris Or Windows Without The Agent)

SAN Resource Management provides the method of manual management for server that does not support the SAN Management agent (StorageMGR-A) or for server where this agent is not installed.

Although the status of reading automatic configuration into a device cannot be monitored, the device can be displayed on the screen of the SAN Resource Management, and the configuration can be manually edited.

8.2.4 SN200 and Silkworm Fibre Channel Switches

SAN Resource Management supports the SN200/Silkworm switch and the GR740D switch as fibre channel switch.

The following is the explanation about items which should be set up directly to the machine in advance when you control the SN200/Silkworm/GR740D switch on SAN Resource Management. For more information about these items, see the manual supplied with the device. 1. IP address, subnet mask, gateway address (Mandatory)

Set the IP address, subnet mask, and gateway address of the LAN. If the Fibre Channel switch has an operation panel, it can be used to set these items. If the Fibre Channel switch has a serial port, these items can be set through the serial port using the ipAddrSet command.

2. User name and password for Fibre Channel switch control (Recommended) A user name and password that have the ADMIN authority security level are required for Fibre Channel switch control. The factory setups are the user name "admin" and the password "password."

3. Domain name (Mandatory for a cascaded connection) This item is required when Fibre Channel switches are cascaded. Set unique values in the Fibre Channel switches to be cascaded. If the Fibre Channel switch has an operation panel, it can be used to set these items. If the Fibre Channel switch has a serial port or if network setups already made for the Fibre Channel switch, this item can be set using the configure command after logging on to the Fibre Channel switch.

4. SysName (Recommended) Register a switch name for Fibre Channel switch management. The SAN Management uses a registered switch name as a SysName. A SysName that does not duplicate other names used by the SAN Management is recommended. If the Fibre Channel switch has an operator panel, it can be used to set this item. If the Fibre Channel switch has a serial port or if network setups already made for the Fibre Channel switch, this item can be set using the switchName command after logging on to the Fibre Channel switch.

5. Zoning setup (Recommended, but it is necessary in the case the switch is GR740D.) Because zoning on a Fibre Channel switch is not set at the factory, if a Fibre Channel switch is connected to a server and storage without a zoning set, no security is defined (the switch will be visible from all servers). To prevent storage data from being damaged by unauthorized access, make sure that access that allows writing from a server to storage with a command such as the format command is disabled until access paths have been defined with the SAN Resource Management. If write access is not disabled, and unauthorized data access to storage occurs, all access paths of the switch can be shut down by creating a temporary zoning with telnet as follows. After setting up, connect each server and storage to the switch, and set access paths with the SAN Resource Management. When a switch is cascaded with a switch for which zoning has already been set, the zoning information is copied. In this case, no setup is required. Nor is a setup required if the switch will used without a zoning setup. zoneCreate"SNM_0001","00:0B:00:00:0E:00:00:00;00:0C:00:00:0E:00:00:00" cfgCreate"SNM_BCSI","SNM_0001" cfgEnable"SNM_BCSI" cfgSave

The SAN Resource Management basically sets and removes access paths (logical paths) based on one-to-one WWPN (World Wide Port Name) zoning of Fibre Channel switches. However the SAN Resource Management supports other types of zoning setups on each level. For each of these, the SAN Resource Management provides function support as follows. 1. No zoning set (SAN Resource Management calls it "No Security state")

There is no zoning setup. It is in the state where access was permitted among all the ports of a Fiber Channel switch. This is the factory setup for each Fibre Channel switch. When a Fibre Channel switch is cascaded with a switch for which zoning already been set, and cascaded connection communication is established, the

85

zoning setup is copied. The SAN Resource Management can normally manage switches that have no zoning set. When a switch is registered with the SAN Resource Management, whether to set zoning when access paths are set from the SAN Resource Management can choose. When zoning is not set, security management is left to the binding and affinity functions of the server and storage.

2. Zoning setup by WWPN (World Wide Port Name) Zoning setup by WWPN is a method by which zoning is set based on the WWPN of a Fibre Channel port. For each Fibre Channel port, a worldwide unique value is defined. Even though the port connection location of a switch is changed, an incorrect access path cannot be created. All access path control functions of the SAN Resource Management operate for an access path defined by WWPN zoning on a one-to-one basis. Access paths defined by WWPN zoning that have not been set except the above-mentioned connection can be read and displayed on the display, but cannot be deleted. To delete an access path, use zoning information of the switch property or the switch management screen or use the telnet function of the switch.

3. Zoning setup by port Zoning setup by port is a method of zoning definition by which a Fibre Channel switch port location is specified. If the port connection location of a switch is changed, port zoning must be set again. With the access path control functions of the SAN Resource Management, access paths that have been set by port zoning can be read and displayed on the screen, and their states can be managed. However, they cannot be deleted. To delete an access path, use zoning information of the switch property or the switch management screen or use the telnet function of the switch.

4. Zoning setup by WWNN (World Wide Node Name) Zoning setup by WWNN is a method of zoning that is based on the WWNN of a Fibre Channel port. A WWNN is common to several Fibre Channel ports, but its definition varies from one company to another. The access path control function of the SAN Resource Management cannot display and delete access paths that have been set by WWNN zoning, but device failure management of a switch is possible.

More than one type of zoning can be set for a Fibre Channel switch. However, for the SAN Resource Management to ensure complete zoning security management, it is recommend that that the current zoning be replaced by WWPN zoning setup on a one-to-one basis. A WWPN is indicated with a blue circle in Member Selection List on the zone administration screen of the Fibre Channel WEBTOOLS. A WWNN is indicated with a folder icon above each blue circuit.

The switch of GR740D is already set port zoning at factory shipment. SAN resource control is also possible to control the access path to the GR740D(including switch). But the switch of GR740D is impossible to connect with cascade to other switch.

86

· With an SN200/Silkworm Fibre Channel switch, six monitoring device addresses (SNMPTRAP send

destinations) can be set. In addition, different community names can be set. As a community name, the SAN Resource Management uses the entry "public" community. Therefore, if this entry is being used, the SAN Resource Management overwrites it.

· An SN200/Silkworm Fibre Channel switch uses the QuickLoop function to emulate a FC-AL hub. However, the SAN Resource Management does not support a Fibre Channel switch for which this function is enabled.

· SAN Resource Management can also control the access path of GR740D (switch is carried). In addition, the cascade connection of the switch of GR740D cannot be carried out to other switches.

8.2.5 Fibre Channel Hub GP-FCH2/3, Gibraltar

The SAN Resource Management supports automatic device detection and failure/state management functions via the LAN for the GP-FCH Fibre Channel hub and Gibraltar from Gadzoox Networks, Inc. A LAN port therefore needs to be installed on a device.

The physical line between a Fibre Channel hub and each device cannot be automatically displayed because the Fibre Channel hub does not have connection information. However, a physical line can be created manually.

Since GP-FCH1 does not have a LAN port, see Chapter 8.2.13 Other Fibre Channel Hub/Array Disk/Library/Bridge Device

8.2.6 GR (Array Disk) Series Setup

The SAN Resource Management supports all functions of the GR710 and later.

When managing GR series units with the SAN Resource Management, note the following points regarding setups on the GR side.

* For more information about setup, see the GRmgr user's guide, such as the GR710/GR720/GR730-GRmgr User's Guide and the GR740-GRmgr User's Guide, supplied with the device GRmgr. GRmgr must be purchased be purchased for the GR820/840. When a GR is managed with GRSC instead of GRmgr, see the GRSC manual.

+[When GRmgr is used for management]

1. Root password setup Set the root password used to log on to GRmgr.

2. RAID setup Set RAID-related information such as RAID group information.

3. Storage zone setup (Only for the GR740/820/840) Set a zone setup common to the inside of storage from a zone setup menu.

4. Host connection setup - host interface setup Set an N port as the FC-CA port, and set LU Mapping (logic unit)/zone information. * Setup method with GR710/720/730GRmgr First, select an FC-CA to be used with the SAN. Next, select fabric connection (N port setup) from [Type of FC connection]. Then, select the Zone setup function or the Host-Zone setup (recommended) function from [Addressing mode], and set LUN Mapping. A value need not be required because the value of [Authorized hosts only] (HBA WWPN setup) is automatically set by the access path setup of the SAN Resource Management. (When the Zone setup function is selected, this value is automatically set only if [Authorized hosts only] is enabled.) * Setup method with GR740/820/840GRmgr From the CA setup menu, select an FC-CA to be used with the SAN. Next, disable loop connection (recommended), then enable the security function (recommended). Loop-ID does not need to be set. The SAN Resource Management automatically creates the HostWWN and Host-Zone definitions.

5. Community setup in the SNMP (agent) environment setups The SAN Resource Management communicates with a GR by using the community name "public." Therefore, the community name on the GR side needs to be one of the setups below.

a. No community setup (default) b. The community name "public" is explicitly set.

In this case, specify the operation management server on which the SAN Resource Management is installed, or specify 0.0.0.0 (all hosts) in the IP address specification.

6. Trap setup in the SNMP (agent) environment setups When a device is registered, the SAN Resource Management automatically adds the IP address of the operation management server to the device as the destination for sending traps. However, if the maximum allowable number of trap send destinations have already been set, no additional IP address can be set. Therefore, the number of trap send destinations must be the maximum allowable number of trap destinations

87

less 1 or more. 7. Device name (SysName) in the SNMP (agent) environment setups

Register an alias for storage management. The SAN Resource Management uses this value as SysName. 8. Network environment setups

If the operation management server with the SAN Resource Management exists beyond the IP address, subnet mask, gateway, and subnet, the subnet of the operation management server must be specified as a destination network address.

9. Log off After completing the setups with GRmgr, be sure to log off from GRmgr. Data set (device registration and access path set) in GRmgr can be performed from the SAN Resource Management without log on to GRmgr.

+[When GRSC is used for management]

1. Logging on to GRSC Log on to GRSC as a user who has security level 3 privilege or higher.

2. Setup of Configuration-RAID Management Set RAID-related information, such as RAID group information.

3. Setup of Configuration-Host, Interface Management-Set Mode Set a mode for the FC-CA port to be used with the SAN. Select an FC-CA , and select Fabric on Host Connection Mode. Also set Security Mode to On.

4. Setup of Configuration-Host Interface Management-Host Affinity Set Channel Group. Since WWN, which is a host data item, is automatically set when access path setups are made with the SAN Resource Management, WWN need not be set here.

5. Setup of Configuration-SystemSettings-Set SNMP Agent <Community setup> Because the SAN Resource Management communicates with a GR by using the community name "public," the community name on the GR side needs to be one of the setups below.

a. No community setup (default) b. The community name "public" is explicitly set.

In this case, specify the operation management server on which the SAN Resource Management is installed, or specify 0.0.0.0 (all hosts) in the IP address specification. <Trap setup> When a device is registered, the SAN Resource Management automatically adds the IP address of the operation management server to the device as the destination for sending traps. However, if the maximum allowable number of trap send destinations have already been set, no additional IP address can be set. Therefore, the number of trap send destinations must be the maximum allowable number of trap destinations less 1 or more. <Device information setup> In the name item, set an alias for storage management. The SAN Resource Management uses this value as SysName.

6. Setup of Configuration-SystemSettings-Set Network Environment (Only for GR730) If the operation management server with the SAN Resource Management exists beyond the subnet, set the gateway and destination network address here. For this setup, log on to GRSC as a user who has security level 4 privilege or higher.

7. Log off After completing setups with GRSC, be sure to log off GRSC. Data setups (device registration and access path setup) in GRSC can be performed from the SAN Resource Management without log on to GRSC.

1. When the SAN Resource Management cannot detect a GR740/820/840 check the following items. - Check if GRG (GRGateway) has been started on the maintenance PC. If GRG has not been started,

register GRG.exe in the startup procedure of the maintenance PC, then start GRG. - If the version of MACS installed on the maintenance PC is 3.1.3 or earlier, all GRmgr SNMP setups

must be made. Use a later version of MACS or complete all SNMP setups.

8.2.7 F649x, Spectris, Plutinum (When An FCA Is Connected)

When the Fibre Channel interface (FCA) of an F649x, Spectris, or Plutinum is connected to a Fibre Channel switch and managed, the SAN Resource Management automatically reads and displays the connection configuration.

Because these devices do not have a LAN port, the SAN Resource Management cannot perform failure management.

8.2.8 SANRISE1000/2000 Of Hitachi, Ltd. The SAN Resource Management supports Hitachi's SANRISE1000/2000 series and DF400/500 RAID300/400. However, a LAN port must be installed, and SNMP must be set to an operable state.

88

There is no automatic device detection function for SANRISE, but a device can be detected using the IP address. In addition, the device configuration reading, state reading, failure monitoring, and automatic physical connection line write functions are performed by defining one LAN port.

If the one defined LAN port cannot operate, the state of the device cannot be recognized.

* For the details of SANRISE setups, contact Hitachi. 1. LAN port for management

Connect all LAN ports to the network to enable management by the SAN Resource Management. 2. Device SNMPTRAP setup

Set the device side so that SNMPTRAP can be sent from a LAN port connected to the network. 3. Detailed management within SANRISE

The SAN Resource Management identifies the SANRISE status and part of the SANRISE physical configuration, and displays this information on the screen. However, use the SANRISE management software for physical setups, logical setups, and reading. If the management software is installed on the client device on which the SAN Resource Management is started, a direct call can be made from the SAN Resource Management with the SANRISE icon. After registering machine, you can select the button of [Device Management Software], and set machine control software by program name as follows.

- The case of DF400 "C:¥PROGRA~1¥DAMANA~1¥startmgr.bat" (Disk array control program) - The case of RAID400 "C:¥HIRMC¥exe¥R40cnsl.exe /S" (Remote Console)

You should modify the file of setup security to initiate it. You should refer to the usage manual 1.2.12.2 and set the absolute path as follows. (¥ becomes ¥¥. You can't set a blank.)

4. Notes about setup up SANRIZE2000 series SNMP Agent When you set up SNMP Agent, if you specify IP address of manager, add IP address of SAN resource control server without fail. But, it is unnecessary to add it if you don't specify IP address of manager.

8.2.9 Symmetrix 3000/5000/ESP/8000 Of EMC Corporation

For management of EMC's Symmetrix, the device needs to be managed with the EMC Control Center (ECC) Agent. A LAN port installed on a Symmetrix device is not usable.

There is no automatic device detection function for Symmetrix, but a device can be detected by entering the IP address of the ECC Agent. In addition, the device configuration reading, state reading, failure monitoring, and automatic physical connection line write functions are performed by defining one LAN port.

* For the details of the ECC Agent setups, contact EMC Corporation. 1. Connection of ECC Agent to Symmetrix

Connect ECC Agent and the management target Symmetrix machine so that ECC Agent can manage the Symmetrix. In composition of that between ECC Agent and Symmetrix is connected via SAN, it is necessary to carry out an access path setup between ECC Agent and Symmetrix manually beforehand.

2. ECC Agent SNMP port setup Information for Symmetrix to be communicated via SNMP, set the ECC Agent itself and the LAN for the server where the ECC Agent is installed. The SAN Resource Management supports only 161 (first candidate of the ECC Agent) or 30727 (second candidate of the ECC Agent) as a port number used by the ECC Agent for SNMP. By default, the ECC Agent uses these port numbers. Note, however, that when the SAN Resource Management cannot detect the ECC Agent, these port numbers may be used by other applications.

3. Setup the ECC Agent SNMPTRAP send destination Set the SNMPTRAP send destination for the ECC Agent at the IP address of the storage management server on which the SAN Resource Management is started. If a cluster of storage management servers is defined, the logical IP address of the cluster must be set. You should add the sending address to the item of the "trap_client_registration (ip-port):" of the following file.

- /usr/emc/ECC/data/config [unix version] - C:¥Program Files¥EMC¥EMC ControlCenter¥data¥config [Windows version]

ex) trap_client_registration(ip-port) : 10.20.30.40 You should reinitiate ECC Agent after setup. /usr/emc/ECC/eccagents stop /usr/emc/ECC/eccagents start

4. Detailed management within Symmetrix The SAN Resource Management identifies the Symmetrix status and part of the Symmetrix physical configuration, and displays this information on the screen. However, use the Symmetrix management software for physical setups, logical setups, and reading. If the management software is installed on the client device on which the SAN Resource Management is started, a direct call can be made from the SAN Resource Management with the Symmetrix icon. After registering machine, you can select the button of [Device Management Software], and set program name to the machine control software as follows.

- "C:¥PROGRA~1¥EMC¥EMCCON~1¥symmconsole.exe" (EMC ControlCenter Console(Two Tier component))

89

"http://xx.xx.xx.xx:40727/emc-cc.html" (ECC Web version (Three Tier component) 40727 is a default port number(selecting at install). Recommending JRE1.1.7b)

- You should modify the security setup file of the client to boot application. You should refer to the usage manual 1.2.12.2 and set the absolute path as follows. (¥ becomes ¥¥. You can't set a blank.) "C:¥¥PROGRA~1¥¥EMC¥¥EMCCON~1¥¥symmconsole.exe"

8.2.10 Tape Library Device LT300N

The SAN Resource Management performs failure management and management screen linkage for the LT300N tape library device. The connection configuration is edited on the SAN resource screen.

In order to manage LT300N with the SAN Resource Management, LMF Server 1.0.X is required. About setups of the SAN Resource Management and of the LMF server to manage LT300N with the SAN Resource Management, refer to the manual supplied with the LMF server.

8.2.11 Tape Library Device LT120

The SAN Resource Management performs failure management and management screen linkage for the LT120 tape library device. The connection configuration is edited on the SAN resource screen. 1. Network connection

Connect the LT120 to the network by making the necessary setups. For details of how to make the setups, refer to the manual supplied with the LT120.

2. SNMPTRAP setup Using the LT120 Web base management tool, set the SNMPTRAP send destination to be the IP address of the storage management server on which the SAN Resource Management is started. If a cluster of storage management servers is defined, the logical IP address of the cluster must be set.

3. Detailed setups on the LT120 The SAN Resource Management identifies the overall status of the LT120 and displays this information on the screen. Use the LT120 Web base management tool for device management, including checking the detailed device state and making setups. The Web base management tool can be called directly from the SAN Resource Management with the LT120 icon. (A definition of calling must be made beforehand.)

8.2.12 Bridge Device Crossroads

For the Crossroads bridge device, the SAN Resource Management supports the automatic device recognition, state management, management screen linkage, and automatic connection drawing functions. The SAN Resource Management supports only "initiator mode". 1. Network connection a. Network environment setups

Set an IP address, subnet mask, and gateway address according to the user's manual supplied with the device.

b. User name and password for bridge device control The user name "root" and the password "password" are set at the factory. Modify these values if necessary. A user name and password are required for [Add] of [Device] menu on the SAN Management screen.

c. Community setup in the SNMP environment setups Set "public" as the community name (GET).

2. SNMPTRAP setup There is no SNMPTRAP setup function.

3. Detailed setups on the bridge device The SAN Resource Management identifies the device status and part of the physical configuration of the device, and displays this information on the screen. Use the Web base management tool for detailed device management. The Web base management tool can be called directly from the SAN Resource Management with the bridge device icon.

8.2.13 Other Fibre Channel Hub/Array Disk/Library/Bridge Device

By performing manual inclusion to the Fibre Channel Hub/Array Disk/Library/Bridge besides support and these devices that do not make LAN connection, SAN resource management is displayed on a screen and can manage a physical connection relation.

8.3 Starting Of Service

It is necessary to be started the following services to the SAN Resource Management. During StorageMGR package installation processing, however, a setup can be made to automatically start the service at the time the server is rebooted.

90

8.3.1 Starting Of The Storage Server Service

When a storage server is an object to SAN management, start the service according to the setup method described in chapter 5 of the installation guide.

8.3.2 Starting Of The Storage Management Server Service

Because the SAN Resource Management function operates on CIMOM, the CIMOM service must be started. This service is usually started when a device is started, but it can also be started to start SystemWalker/StorageMGR CIM service.

For monitoring device failure, a SNMP trap monitoring service that accepts an SNMPTRAP event of a device must also be started. This service is usually started automatically when a device is started, but it can also be started to start SystemWalker MpWksttr service.

8.4 SAN Resource Configuration Management

The SAN Resource Management detects a device and registers it on a screen. And it is possible to register by manual to the machine which can't be recognized by automatic.

8.4.1 SAN Resource Detection

To manage devices with the SAN Resource Management, firstly devices must be detected, then the devices to be managed must be displayed on the SAN Resource Management screen. Two methods for detecting devices, described below, are provided. The status of a detected icon, which blinks on the screen, is device unregistered. Once detection has occurred, the icon is stored in the SAN Resource Management database in unregistered status. To delete the icon, please perform processing written to "8.4.10 Deleting A Registered SAN Resource".

If a GR under GRSC management exists, refer to Chapter 8.11, "SAN Resource Management Definition Files," in this manual and make sure to edit the "GRSC_GR" parameter in the definition file. 1. A device in the same subnet as the storage management server is automatically detected.

Select [Detect Device in Subnet(B)] from the [File (F)] menu, or press the [F5] key while holding down the Shift key. This operation displays the icon of an automatically detected device supported by the SAN Resource Management to be automatically displayed on the screen. Internally, the SNMP broadcast process is performed, and the icon is automatically displayed for a device supported by the SAN Resource Management. If the SAN Resource Management definition file is modified, devices in other subnets can be detected automatically. (Chapter 8.11, "SAN Resource Management Definition Files," in this manual) Note that this

91

function is supported only in an environment where the broadcast process passes through to the remote subnet side. It is impossible to recognize the agent of SAN control against SANRISE, Symmetrix and StorageMGR 5.1 automatically. You should be recognized it by specified IP address as follows.

2. Specify the IP address and detect the device. Select [Find (F)] from [Device] on the [Operation (C)] menu. Alternatively, right-click within the view map display, and then select [Find] from [Device] on the popup menu. The device find screen shown below appears. Enter an IP address such as "10.10.10.10" and click the [OK] button. - When finding a server(cluster environment etc.) which has both of logical IP address and physical IP address, enter logical IP address. - For SANRISE, specify the IP address of the LAN port connected to the low-order controller number. - For Symmetrix, enter the IP address of the ECC Agent.

3. However, if a GR array disk device is managed using GRSC, click [Search GRSC Device] button. The

following screen appears. Enter the IP address of the GRSC server in the top box and enter the IP address of the GR in the bottom box. When GRSC is changed after registering GR which is controlled by GRSC to SAN resource control, you should delete the GR information from SAN resource control and recognize and register it by using new information of GRSC.

8.4.2 SAN Resource Registration (From Icon Flashing Status To Lit Status)

Before a device can be managed by the SAN Resource Management function, the flashing icon of the unregistered device must be registered in the SAN Resource Management function. 1. Left-click the device icon to select it, and select [Add (A)] from [Device] on the [Operation (C)] menu.

Alternatively, right-click the device icon to select it, and select [Add(A)] from [Device] on the popup menu. When the device addition confirmation dialog box appears, select the OK button.

2. The user name and password input screen for the target device management appears for the appropriate device type. Enter the required information. (Not required for the server. For the Fibre Channel switch, a ADMIN security level user name and password are required. For a GR series machine, the root account password is required. For Crossroads, an account for user registration account and a password are required. Not required for the F649x/Spectris/Platinum/SANRISE/Symetrix/LT300/LT120

92

3. The device is registered when you select [OK]. And it shows a message like the following figures in the case of

server, so carry out as the message. If a message [Host environment error detected. detail: 2006:IP couldn't be changed info host name] is shown and unusual end occurred, it is in the state which cannot get device name from IP address in a server side. You should register IP address to hosts file in a server side or DNS and carry out resource registration. If there is physical/logical IP address in a server side, refer to 8.11 SAN Resource Management Definition Files and set logical IP address to LOGICAL_MANAGER_IP and select [Re-read Definition File] button from [Option(O)] of [View(V)] of menu and restart resource registration.

4. The following screen appears when incorporating a switch(No Security state) for which no zoning has been set.

When [Continue the operation] is selected, the operation begins without any security. In this condition, the switch zoning will not be set even though an access path is set from the SAN Resource Management. When [Set WWPN_Zoning when you set up an access path later.] is selected, WWPN Zoning is set up from the SAN Resource Management when an access path is setting up. Consideration of the security of a switch recommends [Set WWPN_Zoning when you set up an access path later.].

If the target device cannot be accessed or if the device is in the following state, the device cannot be registered because the SAN Resource Management function is not included in the support. 1. Server - The SAN Management agent has not started.

Action: Start the SAN Management agent. - [Solaris version agent]The server name of the SAN Resource Management of the operation monitor

host is not correctly set up in /etc/init.d/init.snmpdx.acl. Action: Check the setup.

93

- Storage affinity is set to World Wide Node Name (WWNN), PID, TID binding. Action: Set the storage affinity again to binding that uses the World Wide Port Name (WWPN).

2. Fibre Channel switch - Logon to the target device was by telnet.

Action: Execute after logging out. 3. GR series - Logon was to GRmgr/GRSC of the target device.

Action: Execute after logging out. When the switch connected to the device to be registered is logged on to with telnet, the physical line between the switch and the device to be registered cannot be displayed because information cannot be obtained from the switch. In this case, execute "Refresh" after logout.

8.4.3 Manual Embedding An SAN Resource

Manual incorporation function is used to register a device that is not supported by the SAN Resource Management and the LT300/120 in the SAN Resource Management. 1. Select [Manual Embedding(U)] from [File (F)] of the complete view menu to display the manual incorporation

frame. 2. Select [Create New Device(N)] from [Operation (C)] of the manual incorporation frame menu.

3. Next, the product type input dialog box appears. Select the product type. If none of the choices applies, select

[Besides]. An example of selecting storage as the device type is shown below.

94

4. The device information input dialog box appears. The storage type, which is an important key for internal

processing, must be input. The icon that will be displayed on the SAN Resource Management screen can be selected from the [Display Icon Setup].

a. "Embedding Information (Required)" · In "Device Name", specify a unique name for device management. The SAN Resource

Management uses this value as the key for identifying the device. For this reason, the name must be unique for SAN resources.

· [For storage type] In "Storage Type," select the storage type from the selection frame (Disk/Tape/Array/Robot).

· [For hub type] In "Number of ports," specify the number of hub ports. · [For bridge type] You should set SCSI bus number connecting to the bridge of "Number of Scsi

bus" and select "SCSI Bus Setup". It shows a dialog of swsag2504 when you select "Number of Scsi bus". You should put the initiator number of the bridge of SCSI bus. It shows a dialog of swsag2506 when you select "OK" after setup. You should set information of the machine connecting SCSI bus to the part of SCSI ID/LUN. After setup, select "OK". If you set more than two of SCSI bus, the same way from swsag2504 is repeated the same number of times as the number of buses.

b. "Option" · In "Manufacturer Name", "Product Name", "Serial number" (Only for storage type), "OS version"

(Only for server type), specify the information for each device. The information is displayed as property information in SAN resource management.

· In "IP Address," specify the IP address when the device is connected to the LAN. If the device supports the SNMP TRAP transmission function, displaying the IP address here enables SAN resource management to receive the vendor-unique SNMP TRAP from the device and to display the contents of the event log and device event information (in the device property).

· You should add the method of controlling the software which can control the target machine to "Device Management Software". It is possible to call the software directly from the property of the machine icon on the console of SAN Resource Management. When the management software can be started from a web client, specify a URL that begins with http://. When the

95

management software is an application that operates on the client side, specify the executable file as the full path name. (Example: c:¥test¥test.exe) For operation on the client-side, a security setup file must be created. For details, see Chapter 1.2.12.2 in the Installation Guide.

c. "Display Icon Setup" · Select an icon for the device. 5. The icon of the incorporated device is displayed in a thin color. 6. Quit the manual incorporation frame.

Select [Exit (X)] from [File (F)]. 7. After termination of the manual incorporation frame, the [Do you want to update the SAN management

information to the latest one?] dialog box appears. Select the [OK] button to update the information.

8.4.4 SAN Resource Configuration Display

The SAN Resource connection status is automatically analyzed and physical connection lines and access paths are displayed. Executing [Refresh (R)] from [Device(D)] will read the latest SAN status from all the devices, and update and display the information. After addition, deletion, or movement of an SAN device or modification of its contents, execute [Refresh] to check the status from the SAN Resource Management. Also execute it to check whether the cables are connected correctly.

+All View

The following is a sample display of the SAN management all view. In all view, two physical Fibre Channel cables that connect the devices are simplified to a single cable. Each device icon can be placed anywhere, it should be placed in a location that is easy to manage.

+Server View

In all view, double-click the server icon or select the server icon in the tree displayed at the left. This action calls the server view that allows storage for which an access path has been set up and its connection status to be checked from the selected server.

+Switch/Hub View

In all view, double-click the Fibre Channel switch/hub icon or select the Fibre Channel switch in the tree displayed at the left. This action calls the Fibre Channel switch/hub view that shows all the devices that are physically connected to the Fibre Channel switch/hub.

+Storage/Library/Bridge View

In all view, double-click the storage/library/bridge icon or select the storage icon from the tree displayed at the left. This action calls the storage view that shows the server whose access path is defined in the selected storage/library/bridge and its connection status.

8.4.4.1 Device Icon Display

[Table 8.1 Device status display]

Icon status Color Description of status Action

Normal Green Operating normally None

Warning Yellow A warning-level error is detected. The warning level depends on the device type.

Replace the faulty part, and execute recovery processing. -> 8.6.3 Screen display when fault occurs and action to be taken

Failure Red An error was detected.

Replace the faulty part and execute recovery processing. -> 8.6.3 Screen display when fault occurs and action to be taken

Unregistered Blinking Status in which the device is not registered in the SAN Resource Management

Register the device. -> 8.4.2 SAN Resource Registration

Communication Grey Status in which the device is already registered in Device power may not be

96

disabled the SAN Resource Management or cannot be identified by the SAN Resource Management. The device property has the value previously assigned when the device was identified. However, if the Fibre Channel switch enters this status, the Fibre Channel physical lines under the Fibre Channel switch will be deleted. All the access paths that use the Fibre Channel switch will have an access path error.

on, the SAN Management agent may not be active, or a problem on the LAN may have occurred. -> Check the device status and execute [Refresh].

[Table 8.2 Server host bus adapter (HBA) status display]

Icon status Color Description of status Action to be taken

Normal Green The server has an HBA. None

Warning Yellow All access paths in the HBA are shut down.

Replace the faulty part and execute recovery processing. -> 8.6.3 Screen display when fault occurs and action to be taken

Communication disabled Grey A previously identified HBA

cannot be identified.

When the status is not communication disabled, check whether the HBA is correctly installed in the device. If the HBA has been removed from the device, select the HBA and execute [HBA deletion].

Access path inheritance required

Yellow

The SAN Resource Management function detected an HBA replacement. (HBAs of different WWPN are mounted in the same server slot.)

Reconfigure the access path according to the new HBA WWPN. -> 8.5.5 Inheriting an access path

[Table 8.3 Storage GA (channel adapter)/Fibre Channel switch port status display]

Icon status Color Description of status Action to be taken

Normal GreenStorage has a CA. Alternatively, the Fibre Channel switch has a port.

None

Failure Red Degraded

Replace the faulty part and execute recovery processing. -> 8.6.3 Screen displayed when fault occurs and action to be taken

Communication disabled Grey A previously identified CA

cannot be identified.

When the device status is communication disabled, device power may not be on or a problem on the LAN may have occurred.

8.4.4.2 Display Of Physically Connected Fibre Channel Line

The status of the device-Fibre Channel physical connection status, such as between a server and a Fibre Channel switch or between a Fibre Channel switch and storage, is automatically analyzed and displayed.

The following items are currently subject to automatic connection line display.

[Table 8.6 Whether automatic reading is available for Fibre Channel physical connection line]

HBA Solaris GP7B8FC1

Solaris SN10-FC01,FC64-1063,LP-7000/8000/9000 QLA2200

Windows LP-7000/8000 QLA-2100/2200GP5-FC101/102PG-FC102

Fibre Channel switch Yes Yes Yes

Fibre Channel hub Yes(*1) No No

Point-to-point connection (FC-AL topology) Yes No No

*1 Converted to multiple HBA-CA connection lines.

97

8.4.5 Setup Of A Device Management Name

After the SAN Resource Management function detects a device, selects a unique device name for the device using the SAN Resource Management, and uses the device name as a device management identifier. The value of SNMP SysName, if set on the device side, becomes the device name. Moreover, any device name can be set for the SAN Resource Management. The device name set in GR can be used as the common GR name of the Fujitsu product "Direct Backup".

Select the device icon from the SAN Resource Management function device icons, and execute [Change Device Management Name] from [Device] of the menu. The device name registration dialog box for the SAN Resource Management appears. Specify a name unique among the SAN Resources with up to 24 characters. The same device management name cannot be specified for another SAN Resource.

The device name set here is used only for management by the SAN Resource Management; it has no effect on the actual device.

If the device name is used as the common GR name for direct backup from the mainframe, specify the name using characters that can be input from the mainframe.

8.4.6 Editing Of The Physical Line For A Manual Embedding Device

This Chapter explains how to edit the lines that connect a manually incorporated device. 1. Display the manual incorporation frame.

Select [Manual Embedding (U)] from the [File(F)] menu in all view. All switches/bridges/hubs are displayed. 2. To incorporate a switch port into a manually incorporated device:

In the manual incorporation frame, if destination information for a port connection that cannot be identified from the switch port exists, the port is displayed as an unknown port. Drag the unknown port to manually incorporated device. (This operation is disabled in physical line edit mode.) A dialog box that enables the port information to be entered appears. Enter as much information as possible, including information for the dialog box options. In the following, the left figure shows the status before an unknown switch port is dropped in manually incorporated test device, and the right figure shows the status after dropping.

3. To incorporate a switch port into library or bridge (including a bridge-library connection)

Drag the unknown switch port to the library (upper FC port Chapter of the LT series) or bridge device. (This operation is disabled in physical line edit mode.) A dialog box that enables the port information to be entered appears. Enter as much information as possible to recognize, including information for the dialog box options. To connect a bridge and a library, drag device icons such as robots and tapes displayed in the bridge to the library.

98

The following two figures show an example of dropping the unknown port of switch Boston port 1 in LT120 library unit aa and an example of dropping the unknown port of switch Boston port 11 in the bridge boulder. The robot icons and tape icons of the bridge boulder are have then been dropped in the library golden.

4. To cancel only a manually incorporated unknown port:

To restore the original unknown port status, right-click the setup port/adapter, select and execute [Delete] of

99

[Display device] from the popup menu. The original state is restored. 5. Quit the manual incorporation frame.

Select [Exit (X)] from [File (F)]. 6. After terminating of the manual incorporation frame, the [Do you want to refresh the SAN management

information?] dialog box appears. Select the [OK] button to refresh the information.

8.4.7 Hub/One-to-one Connection Physical Line Editing

In almost all of the one-to-one connections of a Fibre Channel hub and FC-AL, the SAN Resource Management function cannot automatically obtain the connection information. A function that edits and manages physical lines for such connections is therefore provided. Do this editing in the manual incorporation frame. Because the conditions for enabling the connection are that each device port has been identified and that the manual incorporation frame is displayed, a manually incorporated server and manually incorporated storage cannot be connected without a switch. 1. Display the manual incorporation frame.

Select [Manual Embedding(U)] from the [File (F)] menu in overall view. All switches/bridges/hubs are displayed.

2. Display the devices related to the work in the manual incorporation frame. Select [Add (A)] of [View Device] from the [Operation (C)] menu. The device display dialog box appears. The devices registered in the SAN Resource Management are listed on the left. After selecting of the target device, click the [>>] button to move the device to be displayed to the right-side frame.

3. Enlarge the work target device icon so that the entire port is displayed.

Select the icon, and on the popup menu, set [Change Detail View] to [ON]. 4. Change the edit mode to physical line edit mode.

Select [Edit (M)] of [Physical Line] from the [Device (C)] menu. 5. Connect the ports that are actually connected.

Link the ports that are not displayed on the screen but are connected. Click to select the port and drag the port to the remote-side port and drop it. (This operation must be done in physical line edit mode.) The following figure shows a sample connection of switch Boston port 0 to GR740-SANMA IOB#01 S00 and GR710 #1 CA0 via the hub longmont. Since the SAN Resource Management cannot connect hubs, only the connections from switch Boston port 0 to the GR740 and GR710 is displayed.

100

Drag a switch Boston port 0 to hub longmont connection port 1. Move the mouse to a different location as soon as the connection is completed. Next, connect GR740-SANMA IOB#01 S00 of the GR740 and longmont port 2. Then connect GR710 #1 CA0 and longmont port 3.

6. Physical lines are checked for consistency by the SAN Resource Management and are redisplayed.

Execute [Refresh (R)] with [F5] or from [Device (D)]. In the example shown in the figure, the physical lines between the switch and GR are automatically deleted because the physical path from the switch Boston to the GR740 and GR710 are automatically identified via the hub.

101

7. To delete a created physical line:

Right-click to select the physical line and execute [Delete(R)] from [Physical Line] on the popup menu. (This operation must be done in physical line edit mode.)

8. Quit the manual incorporation frame. Select [Exit(X)] from [File(F)].

9. After termination of the manual incorporation frame, the [Do you want to update the SAN management information to the lastest one?] dialog box appears. Select the [OK] button to refresh the information.

It doesn't support composition of connecting between HUB and HUB using more than two of fibre cable.

8.4.8 Call Device Management Software

The device-side management software is called from the device icon of the SAN Resource Management function. Select the device icon and execute "Call Management Software" from the popup menu displayed by right-clicking. The device management software is executed.

For a device other than the one described above, call link with the device that retains the device management software function is enabled. See Chapter 8.2 Description And setup of Devices To Be Managed. (Both URL call and direct command execution are supported.)

8.4.9 Device Identification Method (Beacon Function)

The beacon function which blinks the LED of the selected device is provided as a way to identify the device selected with the device icon of the SAN Resource Management function. This function can be executed during operation.

The target device and corresponding function are shown below. Double-click the device icon of the SAN Resource Management function to switch to device view. In device view, select the following device and call [Start(S)] from [Blink Beacon] on the popup menu displayed by right-clicking. Let the beacon operate for three minutes. Selection of the menu is disabled for a device that does not support this function. To stop operation of the beacon, select [Stop (P)] from [Blink Beacon] on the popup menu. · Fibre Channel switch: All ports blink in order. · Fibre Channel hub (Gadzoox): The power display LED blinks. · HBA (GP7B8FC1): The two LEDs of the host bus adapter, LINK and CHK, blink simultaneously.

102

8.4.10 Deleting A Registered SAN Resource

The registration of a device managed by the SAN Resource Management function is deleted and is no longer a management target. It is used at the time of withdrawal of management device etc.

+Description of operation

1. Click to select the target device icon and select [Delete(D)] from [Device] on the [Operation (C)] menu. Alternatively, right-click to select the device icon and to display the popup menu, and select [Delete] from [Device] menu.

2. Click OK to continue the device task. 3. When the following dialog box appears, the access path setup for the device can be deleted. For example,

when a server is removed, the switch zoning and storage affinity setups for the server are no longer necessary. The SAN Resource Management can automatically delete these unnecessary security setups. Normally, however, the Manager does not delete these unnecessary setups. Use [Delete the access path.] to select access path deletion mode on this dialog box menu. All the setups for registered devices that are being deleted from the SAN Resource Management will be deleted. To continue operation with the device no longer a target of the SAN Resource Management and to retain the access path setups, select [Do not change the access path].

When SAN Resource Management automatic device detection detects a deleted device, the device is redisplayed.

8.4.11 Deleting A Registered CA, HBA (FC Adapter) Icon

The CA, HBA (FC adapter) icons of the manually incorporated device and in communication-disabled status can be deleted. The access path of the deleted CA and HBA (FC adapter) icons cannot be inherited.

+Description of operation

1. Click to select the target CA or HBA icon, and select [Delete] from [Device] on the [Operation(C)] menu. Alternatively, right-click to select the icon and to show the popup menu, and select [Delete] from [Device] menu.

2. Click [OK] to continue the device task. 3. When the following dialog box appears, the access path setup for the CA or HBA (FC adapter) can be deleted.

For example, when a CA or HBA (FC adapter) is removed, the switch zoning and storage affinity setups for the CA or HBA (FC adapter) are no longer necessary. The SAN Resource Management can automatically delete these unnecessary security setups. Normally, however, the Manager does not delete these unnecessary setups. Use [Delete the access path.] to select access path deletion mode from this dialog menu. All the setups for the registered devices that are being deleted from the SAN Resource Management will be deleted. To continue operation with the device no longer a target of the SAN Resource Management and to retain the access path setups, select [Do not change the access path].

8.4.12 Other Convenient Functions

1. Wallpaper Function

103

To make the following file a JPG file, so that it can be used as wallpaper of map view of SAN Resource Management screen. In addition, close/reopen the Web Browser for the wallpaper to reflect. Install directory ¥java¥icons¥san_backimage.jpg

8.5 Access Path Management

8.5.1 About An Access Path

In SAN Resource Management, the logical paths of servers and storages are defined as access paths.

Access paths are generated by the following access control functions of servers, Fibre Channel switches, and storages.

+Server storage affinity

The server storage affinity function is provided by Fibre Channel adapter manufacturers. By writing information such as the Fibre Channel world wide port name of the storage-side channel adapter (CA) to a definition file, the definition of target CA which can be accessed and setup ID of the host corresponding it. This function is also called as LUN mapping or WWPN binding, but is defined as storage affinity here. It is set in definition files such as /kernel/drv/sd.conf, /kernel/drv/fjpfca.conf (GP7B8FC1), /kernel/drv/sd.conf (SN10-FC01, JNI), and lpfc.conf (LP-7000/8000/9000).

All HBA operating in a Solaris environment supported by SAN Resource Management support this function, but HBA operating in a Windows environment do not support this function.

+Fibre Channel switch zoning

The Fibre Channel switch zoning function is provided by Fibre Channel switch manufacturers. This function combines information such as the Fibre Channel WWN/port numbers of HBA on the server side and the Fibre Channel WWN/port numbers of CAs on the storage side as a zone. It also restricts access that comes from a port not defined in the zone.

+Storage host affinity

The storage host affinity function is provided by storage manufacturers. The storage side recognizes the WWPN of HBA on the server side and restricts access. This function can also set up an association between the WWPN of HBA and areas in storages. In the GR series, this function is defined as zone definition/host affinity.

+Integrated path control of SAN resource management

SAN Resource Management easily achieves a setup that takes full advantage of SAN security and the characteristics of each function through uniform management of the integrated access path control functions.

Currently, SAN Resource Management supports storage affinity only for Solaris servers and host affinity only for the GR series. Support for more devices is scheduled, however. The Fibre Channel switch zoning function can be used alone to control access paths without storage affinity and host affinity. SAN resource management controls access paths according to the functions and setups of each device.

8.5.2 Displaying Access Paths (Displaying The Logical Relationship Between Servers And Storages)

SAN Resource Management collects information from each device and displays the status of the paths that can be accessed from the host or of the logical access paths that have been set, making the logical relationship between the servers and storages in a complicated SAN environment easy to understand. This function is therefore effective in verifying the validity of the system configuration setup and in identifying the effects of any resource problems that occur.

In Solaris versions, only GP7B8FC1 can display access paths in an FC-AL connection. In Windows versions, only native Fujitsu products and the Qlogic HBA can display the access paths in an FC-AL connection.

8.5.2.1 Displaying Access Paths With Server View Or Storage View

Server View or Storage View can be used for verification. You can access path display from the View (V) menu in each view. Only those access paths whose color is different from the color (black) of the physical path are displayed.

8.5.2.2 Displaying Access Paths From The Server

Clicking an HBA for which an access path has been created displays in light blue all the access paths managed by the HBA and the areas allocated to the HBA in the storage. (For the GR series, zone numbers are also displayed.)

104

The HBA property or the access path window can be used to check which device file on the server side seems to be this access path. You can display the access path window by pressing the [Access Path Information] button of the list display as shown in the figure below.

In Solaris device file cxtyd*s*, for example, the controller number of the HBA property is x and the target ID of the access path information in the HBA property is y. In the following figure, if the controller number of the selected HBA is 3, the target ID is 3, and the LUN is 0-4, it will be understood that the c3t3d4 device file is associated with c3t3d0.

As the following figure, the target ID and LUN can also be identified by right-clicking an access path directly and selecting Property on the pop-up menu. In addition, [Error Description] can be displayed from Property. [Error Description] provides the reason why the access path is faulty. (In some cases, a reason may not appear.)

105

As the following figure, selecting an access path and clicking it displays the physical paths constituting the access path in light blue. If switches are cascaded on an access path, the intermediate paths between switches cannot be displayed.

If the Fujitsu multipath disk control feature is being used in a Solaris or Windows environment, the device file name of the control feature is displayed on the server side. Clicking this device file enables the information for the access paths constituting the device file and storage areas to be displayed in light blue. Using this function, the system administrator can visually understand the relationship between storage media and server device files, resulting in efficient storage system operation management.

106

8.5.2.3 Access Path Display From Storage

Clicking the CA (FC port) of the storage where an access path has been created displays all the access paths and HBA managed by the CA in light blue.

Clicking the storage area (cylinder/zone) displays all the access paths and HBA managed by the related CA in light blue. If the Fujitsu multipath disk control feature is already set on the server, the corresponding device file name is also displayed in light blue.

8.5.2.4 Access Path Status Display

[Table 8.8 Access Path Status Display]

Access Path status Color Explanation of Status Action

Normal (WWPNBINDING) Green

The access path is normal.

It has already been confirmed that storage affinity (WWPN binding) is set on the server side.

None

107

(ANOTHERBINDING) Blue

The access path is normal.

Storage affinity (LUN mapping) is not set up on the server side. The access path is set up from the Fibre Channel switch zoning information or storage host affinity information. (If the HBA is an GP7B8FC1, this setup is not enough to access the path. The path must be set up from SAN resource management.)

None

However, this setup is not enough for the operation of the GP7B8FC1, which is a Solaris HBA. When the access path is added, the GP7B8FC1 must be placed in WWPN binding status.

Access path error Red

The access path is disconnected because it is faulty (valid only when the multipath control feature is installed).

Alternatively, a fault somewhere else is causing or may cause an error on the access path. (This status occurs if a device on the access path is faulty.)

This status also occurs if the Fibre Channel cable is disconnected.

Replace the faulty part and perform recovery processing.

-> 8.6.3 Screen when fault occurs and action to be taken

Access path definition conflict Yellow

The access path setup is incorrect (e.g., WWPN binding is set up on the server side but zoning is not set up on the Fibre Channel switch side.)

Alternatively, the access path cannot be confirmed because no Fibre Channel switch device is registered. For example, this status could occur if zoning information was carelessly set on the Fibre Channel switch.

If the Fibre Channel switch is not registered, register it.

If the Fibre Channel switch is already registered, right-click the access path, select Property on the pop-up menu, then check the access path status. If access path inheritance is necessary, see the next item in this column. In other cases, check Description of Fault and set up or delete the access path as required.

Access path inheritance is necessary (HBA only) Yellow

The access path must be inherited because the HBA has been replaced.

See Chapter 8.5.5, "Inheriting an access path"

The Solaris server uses a special file (/dev/rdsk/cXtX) to acquire WWPN binding information. For this reason, if the WWPN binding needs to be understood, this special file (device file) must be created in advance. Existence of an unused special file under /dev/rdsk/ or /dev/rmt/ also results in incorrect display of access paths. If the access path displayed in SAN Resource Management differs from that of the actual device, clarify the use the defined special files defined as follows:

In the case of Solaris 2.6

# touch /reconfigure

# /usr/sbin/shutdown -y -i6 -g0 (Reboot processing)

In the case of Solaris 7/8

# touch /reconfigure

# /usr/sbin/shutdown -y -i6 -g0 （Reboot processing）

After reboot processing

# disks -C

8.5.3 Setup An Access Path

As the following figure, SAN Resource Management automatically modifies the security setup supported by each device type when it sets up the access path. If the device side does not have the security feature, SAN Resource

108

Management does not set up the access path because it cannot set up the path. The access path is created, however, by the security feature of another device. If none of the devices constituting the access path is has the security feature, SAN Resource Management cannot set up security but it can access the path from the server. SAN Resource Management can set up the access path only in a Fibre Channel switch environment.

Even if the status of an access path is access path definition conflict, a correct access path can be generated by implementing this access path setup. Select the access path with the definition conflict from the screen and implement this setup.

Besides setup up the access path between a server (HBA) and a storage (CA), SAN Resource Management can set up the path between a server (HBA) and a bridge port and between a server (HBA) and another server (HBA). It can also set up the path between a storage (CA) and another storage (CA).

Each storage has restrictions on the conditions (e.g., HBA type) for guaranteeing operation based on the confirmed interface requirements. Set up the access path based on these conditions. For more information about these conditions, contact each storage vender.

[Table 8.9 Security information that SAN Resource Management sets up on each device when setup up an access path]

Device type Contents of setup by SAN Resource Management

Solaris server

Agent provided GP7B8FC1

[If the remote device is a disk device (The disk of a manual building in is excluded)]

Setup of LUN in sd.conf LUN/setup of relationship between TID and WWPN in fjpfca.conf

[If the remote device is tape/library/bridge/manual operation built-in disk]

setup of relationship between TID and WWPN in fjpfca.conf

[If the remote device is HBA]

109

Not set up

SN10-FC01, FC64-1063


Setup of relationship between TID, LUN, and WWPN in sd.conf

[If the remote device is tape/library/bridge/manual operation built-in disk/HBA]

Not set up

LP-7000/8000/9000


Setup of LUN in sd.conf/setup of relationship between TID and WWPN in lpfc.conf


Setup of relationship between TID and WWPN in lpfc.conf


Not set up

QLA-2200


Setup of LUN in sd.conf/setup of relationship between TID and WWPN in qla2200.conf


Setup of relationship between TID and WWPN in qla2200.conf


Not set up

Agent provided

Other HBAs Not set up

Solaris server

Agent not provided Not set up

Windows server Agent provided/not provided Not set up

Other servers Agent not provided Not set up

Zoning setup One-to-one zoning setup of WWPN(But if it is already set the zoning of port zoning to the switch, setup is needless.) Switch

No zoning setup Not set up

Security setup Setup of HBA WWPN in security

Zone setup Setup of HBA WWPN in zone GR

No security setup Not set up

Other storages/tapes/bridges Not set up

8.5.3.1 Preparation

+Storage setup

Check the setups for the storage side before setup up the access path. · For GR series

Setup up the zone (host affinity) function enables storage areas on the storage area network to be used efficiently. When this function is used, a zone must be set up on the storage side before the access path is set

110

up. Set up the zone with GRmgr or consult a Fujitsu CE. · SANRISE, Symmetrix, F649x, and Spectris/Platinum

If the host affinity functions(The name of the host affinity function depends on the company, e.g., LU mapping.) of these devices must be used, device management software must be used to set up these functions on the device side in advance. The reason is that SAN Resource Management cannot automatically control the host affinity function.

+Device status

· Each HBA must be connected to a Fibre Channel switch and operate on the N port or as NL public. · An HBA must be physically connected to a CA via a Fibre Channel switch. · All the Fibre Channel switches for which the setup of HBA, servers, CA, storages, and access paths don't

need to be in an unusual state.

+About the use of the [Solaris version] hard disk driver (HDDV) and multipath disk control (MPHD, MPLB)

· The access path setup function of SAN Resource Management writes access path setup information to /kernel/drv/sd.conf on the server. For this reason, if a hard disk driver (HDDV) and multipath disk control (MPHD, MPLB) are used, the function sets up access paths according to the sd.conf file rewrite timing during environment setup of each module.

· The access path setup function may set up the addition of logical unit access paths and the installation of additional logical units on a server that already operating under HDDV, MPHD, or MPLB. For this setup, the function implements MPHD/MPLB/HDDV in [Access Path Setup].

· When the number of versions of HDDV is considering as the state which can be activity extended by hddvadm -M or more by 2.2, in specific environment, activity extension of Logical unit is possible.

· Please set up manually beforehand with reference to the manual of HDDV about the edit method of hddv.conf/usage of hddvadm -M/specific environment. (SAN Resource Management does not carry out file edit to hddv.conf and sd.conf at the time of hddvadm -M use. It sets to fjpfca.conf automatically.)

+Other notes

· To change the HOSTID (TargetID) of an access path that has already been set up, you must delete the access path and then set the new ID.

· To change the specified GR-side zone name of an access path that has already been set up, you must delete the access path and then set a new zone.

· Select [Refresh] from the [View] menu and make sure that all the Fibre Channel switches cascaded to the Fibre Channel switch related to access path setup are correctly recognized. Changing the access path when a Fibre Channel switch is temporarily disconnected from the cascade makes easy recovery of the previous cascaded connection impossible. (If this situation occurs, you can restore the cascaded connection by deleting the zoning information for the Fibre Channel switch temporarily disconnected from the cascade with the switch's Cfgclear command.)

· If you control security setup of GR under the environment where GR is managed via GRSC, it is necessary to be in the state which can be recognized by GRSC via LAN from SAN Resource Management. When processing carries out a timeout at the time of an access path setup, check about the GRSC environment.

8.5.3.2 Actual Setup

Fibre channel access paths are set up. In addition to the setup a new access path be set up, the access path setup can contain specific definitions (modifications when an access path setup conflict occurs). In addition, the setup for the installation of additional logical units on an access path can be modified.

111

+Access path setup procedure

1. Set up the access path environment for storage expansion and connection of Fibre Channel cables. 2. [In the case of Solaris server] Preprocess the device driver definition file.

For an MPHD/MPLB/HDDV environment, you should execute #hddvadm -i at target server.(It is needless when you do hddvadm -M.)hddv.conf is moved to sd.conf, and the mphd.conf and mplb.conf files are saved. SAN Resource Management automatically edits sd.conf and the configuration definition file (*.conf) during access path setup. If a program that will be affected by editing of these files is running, stop it.

112

When setup a new access path, execute from Steps 3 to 7. If the target storage is already displayed, execute Step 6 and subsequent steps. To modify the setup of an existing access path, select the access path directly and execute Step 8 and subsequent steps.

3. Select the target server and open Server View. 4. Select [Add (N)] from [View Device] on the [Operation (C)] menu to display the addition display unit dialog box.

Select the storage for which the access path will be set up from the detected devices and move it to the addition display unit dialog box with the [>>] button. After the display unit has been added, click the [OK] button.

5. The selected storage is displayed on the screen.

113

6. Select the HBA on the server side for which an access path is to be created by clicking it. 7. Select the CA on the storage side where an access path is to be created by holding down the [Ctrl] key and

clicking the CA. 8. Display a menu by right-clicking and select [Connect] from [Access Path] on the menu.

Steps 6 to 8 can also be executed by dragging and dropping the icons of each port (e.g., drag the HBA port and drop it on the CA port.) After executing Steps 6 to 8, move the mouse.

114

After execution should move a mouse. (Drag and drop may not be decided)

9. [Storage GR] If zones are set up on the storage side, select the zone to be used by the access path. A function that automatically captures and selects the zones set up on the storage side is provided at this point. (At present, only GR series disk array devices support this function.)

10. [Solaris server (agent provided)] Enter the TargetID (X in /dev/rdsk/c?tXd?s? of Solaris special file)

corresponding to the access path.(This dialog is displayed only under the HBA-device environment where TargetID can be specified.)

11. [Solaris server (agent provided)] Enter the LUN used by the access path.( This dialog is displayed only under

the HBA-device environment where LUN can be specified.)

115

The LUN information that can already be accessed from the server is stored in the currently set location for LUN information. If a new access path is set up, no value is set in this location. The LUN set up in the zone of the selected storage side is stored in the [Specify a LUN*] location as the initial value. The entered LUN is added to the /kernel/drv/sd.conf file on the server. However, even though a LUN is deleted, another path may be using it. For this reason, SAN Resource Management does not automatically delete a LUN from /kernel/drv/sd.conf. If the definition must be deleted, directly edit the /kernel/drv/sd.conf file on the server side. Note, however, that in the activity extension environment of HDDV2.2 or later, the contents of the sd.conf file are not modified. For more information, refer to the handbook for HDDV2.2 or a later version.

12. [When zoning is not set up on the switch] Selecting [Set WWPN_Zoning when you set up an access path later.] when the switch is registered in SAN Resource Management displays the Zoning Setup Selection dialog box. If zoning is set up in an unzoned area, the switch's security function will operate. Note, therefore, that if there is an operating access path, its operation is disabled by the security function. In such a configuration, it is recommended that SAN Resource Management stop operation of other access paths and reset the these access paths. Selecting [Continue the Operation] when the switch is registered in SAN Resource Management does not display the Zoning Setup Selection dialog box. When changing operation to operation for WWPN zoning setup, modify the setup using the switch's the property zoning information.

13. When access path setup information is displayed, check whether it should be modified. If modification is not necessary, click the [OK] button.

<Set up access paths for the device.> If the storage area used in the associated access path setup is defined on another HBA, an area collision warning message is displayed. (Only GR series disk array devices on the storage side have this check feature.) Although this setup is only necessary when storage areas are defined from multiple HBAs in multipath disk control or in a cluster system, still check the setup for other configurations because the data may be garbled.

14. A message indicating the setup of the access path has ended normally is displayed. Verify the contents of the message and click [OK].

15. The status of the access path is now normal (blue). When setup up more than access path at the same time, execute Step 6 and subsequent steps for each access path that is added. (When access paths are set up, Windows2000 automatically recognizes as many devices as the number of LUN set up on the access paths and displays the message for adding devices.) However, it is a premise that the device deals with plug and play. Or the message of a device addition may be outputted to an event log as Removable Storage. However, it is a premise that the device deals with plug and play. (The GR series supports plug and play.)

116

16. [Access path setup for Solaris tape] Write the LUN number in the configuration definition file (e.g., st.conf) of

the target tape driver. If the HBA is SN10-FC01/FC64-1063, however, WWPN binding must also be written in the file. The tape drivers that can display LUN information after the access path has been set up are the following: st,ftla,fsct,,IBMtape,mt,lb

17. [GR720/GR730 (versions before V11L21)/GR740, GR820, GR840 (versions before V03L52P1939)] Reboot the GRs. Device reboot is necessary to reflect the GR set up from SAN Resource Management. Versions other than the specified versions and some P19 versions of the GR740, GR820, and GR840 (consult Fujitsu) do not require a device reboot because the GR side supports a function that reflects activity composition configuration setup information.

18. [When the HDDV activity extension function is set up on a Solaris server(hddvadm -M)] You should be recognized the storage to server using the following command, when you set the HDDV activity extension function(hddcadm -M) at Solaris server. But if not be supported the new frame adding, you should check the setup of hddv.conf/sd.conf the following HDDV manual and reboot the machine.

- Execute #/usr/sbin/hddvadmdr on the server to capture devices. 19. [Environment in which the Solaris server does not support the activity extension expansion function] Make the

server recognize storages with the following code: When it is not the HDDV environment(including tape environment)

- # touch /reconfigure - # /usr/sbin/shutdown -y -i6 -g0

When it is the HDDV environment - # touch /reconfigure - # /usr/sbin/shutdown -y -is -g0 (Start the server in single-user mode.) - #hddvadm-m (The required part of sd.conf is moved to hddv.conf, and the saved mphd.conf and

mplb.conf files are restored.) - # touch /reconfigure - # /usr/sbin/shutdown -y -i6 -g0 20. [For Solaris 7 or 8] Organize the files in /dev/rdsk with the #disks -C command.

[For Windows] Reboot to recognize devices in the case of NT. In the case of 2000, reboot only when reboot demand dialog is displayed.

21. [For Windows server] Reboot to recognize devices in the case of NT. When the device is automatically

117

recognized by Windows2000,the new recognition by reboot is recommended. 22. [Other servers] Execute the operation that recognizes devices. 23. Access path check from SAN Resource Management

[For Solaris server] /dev/rdsk/cXtX is created on the server side. Executing [Refresh] from SAN Resource Management displays the following access path. When WWPN BINDING is successful, the status of the access path changes to normal (green). [For Windows server] Devices are generated on the server side. An access path can also be set up by selecting "host" from "storage" in the same method.

In addition, an access path can be set up between servers (HBA) or between storages (CA) by dragging and dropping between ports in Server View. Since in this case one-to-one WWPN zoning needs to be set up on the switch, the capability of setting up WWPN zoning on the switch becomes a requirement. On the SAN Resource Management screen, the access path between servers (HBA) or between storages (CA) cannot be displayed in a figure. Check the access path using the switch property zoning information. Switch property zoning information is also used to delete access paths.

After setup of access path, when you define GR740, you should read the information of setup from GR and modify it and transfer it to GR. If you do not use the existing information of setup, it is possible to overwrite the setup which set by SAN Resource Management.

8.5.4 Deleting an access path

SAN resource management can delete access paths that have been set up when one-to-one WWPN zoning is set up on the switch, but only if the environment is a Fibre Channel switch environment.

SAN resource management can delete an access path even though its status is definition conflict. Select and delete the access path whose status is definition conflict from the screen.

If one-to-one WWPN zoning is set on the switch, use the switch property zoning information to delete an access path between servers (HBAs) or between storages (CAs).

8.5.4.1 Preparation

· The access paths defined in zoning setup other than one-to-one WWPN zoning setup on a Fibre Channel switch cannot be deleted. One-to-one WWPN zoning setup includes port zoning setup, WWNN zoning setup, and multiport WWPN zoning setup. (SAN resource management supports only one-to-one WWPN zoning setup.) In such cases, log on directly to the Fibre Channel switch and modify the setup.

· Select [Refresh (R)] from the [Device (D)] menu or [F5], and make sure that all the Fibre Channel switches cascaded to the Fibre Channel switch related to access path setup are correctly recognized. Changing the access path when a Fibre Channel switch temporarily disconnected from the cascade makes easy recovery of the previous cascaded connection impossible. (If this situation arises, you can restore the cascaded connection by deleting the zoning information for the Fibre Channel switch temporarily disconnected from the cascade with the switch's Cfgclear command)

· If multipath control for Windows2000 is being used as the Windows multipath driver, be sure to shut down the server before deleting an access path. If an access path is deleted while the server is operating, the next shutdown requires considerable time because Windows path detection logic functions.

· When you delete the access path of Multi-Path Control for Windows of Windows2000 in same server of SAN resource control, you should shutdown SAN resource control server and after cutting the target FC cable of access path, initiate SAN resource control and delete the access path.

· When the server is Unix server that is deleted the access path, "umount" command is executed for the deleted path before delete access path.

8.5.4.2 Actual setup

Fibre channel access paths are deleted. An access path whose status is [Config MisMatch] can also be deleted. 1. [Solaris (for MPHD or MPLB environment)] Releasing multipath setup

If multipath disk control (MPHD, MPLB) has been set up, delete the multipath definition of the access path that you want to delete from the server side with the #iompadm -c mphd/mplb destroy command (its arguments are necessary).

2. [Solaris (for MPHD, MPLB, or HDDV environment)] Releasing the HDDV Execute #hddvadm-i on the target server. hddv.conf is moved to sd.conf, and the mphd.conf and mplb.conf files are saved.

3. [Windows] If multipath disk control for Windows has been set up, shut down the Windows server. If the Windows server is being started in this environment, SAN source management suppresses access path deletion.

4. In SAN resource management, select the access path to be deleted by clicking it and then select [Delete (D)]

118

from [Access Path] on the [Operation (C)] menu. Alternatively, right-click the access path to be deleted and select [Delete] from [Access Path] on the pop-up menu.

5. Select the access path to be deleted and delete it by clicking [OK]. (If the access path used by Windows2000 is deleted, a warning message for as many devices the number of LUNs set up on the access path is displayed.)

6. [Solaris (agent provided)] The status of the deleted access path remains yellow ( Config miss Match) until the server is rebooted (valid when WWPN binding is set up on the server).

7. [GR720/GR730 (versions before V11L21)/GR740, GR820, GR840 (versions before V03L52P1939)] Reboot GRs. Device reboot is necessary to reflect the GRs set up from SAN resource management. Versions other than the specified versions and some P19 versions of the GR740, GR820, and GR840 (consult Fujitsu) do not require a device reboot because the GR side supports a function that reflects activity configuration setup information.

8. [Solaris] Make the server recognize storages with the following procedures: When it is not HDDV environment (includes tape environment).

- # touch /reconfigure - # /usr/sbin/shutdown -y -i6 -g0

When it is HDDV environment. - # touch /reconfigure - # /usr/sbin/shutdown -y -is -g0 (single user state) - #hddvadm -m (The required part of sd.conf is moved to hddv.conf, and the saved mphd.conf and

mplb.conf files are restored.) - # touch /reconfigure - # /usr/sbin/shutdown -y -i6 -g0 9. For Solaris 7 or 8, organize the files in /dev/rdsk with the #disks -C command. 10. Check the access paths from SAN resource management. 11. [Windows] Reboot the device. 12. [Other servers] Execute the operation that recognizes that devices have been deleted. - The storage affinity (WWPN binding) on the server side is deleted, but the LUN setup of the related

/kernel/drv/sd.conf file is not deleted for reasons of safety. If the setup must be deleted, edit the /kernel/drv/sd.conf file directly.

8.5.5 Inheriting an access path

SAN resource management sets up security based on the WWPNs for a device to form an access path. However, since WWPNs are unique names, they may change when an adapter (controller) is replaced.

When an adapter (controller) is replaced, WWPNs of all HBA types and of the DF400 bridge, LT120/300, and similar devices are changed, while WWPNs of GRs, the DF500, SANRISE1000/2000, and Symmetrix are not changed.

If a WWPN is not changed, operation can continue as is. However, if a WWPN is changed because the adapter (controller) has been replaced, the security function of the WWPN forming the access path must be changed to reflect the new WWPN. This operation is referred to as access path inheritance. Access path inheritance is a function that changes the WWPN security setup managed by SAN resource management to automatic re-setup.

The access path inheritance function can be executed even though other access paths are operating in SAN.

Select [ Refresh (R] from the [Device (D)] menu before starting work and make sure that all the Fibre Channel switches cascaded to the Fibre Channel switch related to access path setup are correctly recognized. Changing the access path when there is a Fibre Channel switch temporarily disconnected from the cascade makes easy recovery of the previous cascaded connection impossible. (If this situation arises, you can restore the cascaded connection by deleting the zoning information for the Fibre Channel switch temporarily disconnected from the cascade with the switch's Cfgclear command)

8.5.5.1 HBA status of " The access path must be inherited" resulting from replacement of server HBA

On servers on which the SAN resource management agent is installed, when an HBA (host bus adapter/SAN resource manager support type) is replaced, SAN resource manager automatically recognizes the HBA replacement and changes the HBA icon in Server View to [ The access path must be inherited.] (yellow). (The HBA replacement is detected because an HBA with a different WWPN is installed in the same slot [physical port number] of the server.) When this occurs, inherit the access path by following the procedure below. 1. From the [Device (D)] menu, select [Refresh (R)]. 2. From Server View, right click on the HBA icon and select Inherit of Access Path from operation (C) menu. 3. The following dialog box opens. Select and execute "Normal Mode." (In normal mode, access path inheritance

does not complete if an error occurs during access path inheritance processing. Select Forced Mode to

119

complete the access path inheritance even if an error occurs.)

4. According to the table below, delete in the applicable device the access path setting defined according to old

adapter information. Then, add to the applicable device an access path setting defined according to new adapter information. Device type Settings of SAN resource manager

With zoning setting

Delete the single-pair WWPN zoning created with the old adapter WWPN. Then, add the single-pair WWPN zoning created with a new adapter WWPN. (However, no setting is required if an access path need not be inherited using port zoning.) Switch

Without zoning setting specification

Without setting

Security setting Delete the old WWPN of HBA from the security setting, and add a new WWPN to the security setting.

Zone setting Delete the old WWPN of HBA from the security setting, and add a new WWPN to the zone setting. GR

Without security setting Without setting

Other storage, tape, and bridge devices Without setting

5. If the storage device is of the GR series, you may be required to reboot the system, depending on the firmware version.(This applies to the GR720/730 <for a version earlier than V11L21> and the GR740, 820, or 840 <for a version earlier than V03L52P1939>.)

8.5.5.2 HBA status other than " The access path must be inherited " that results from replacement of server HBA

If an HBA is replaced with an HBA in a different slot, or if a server HBA of a manually incorporated device or an unsupported HBA is replaced, SAN resource manager cannot generate the " The access path must be inherited " status for the HBA. In such an event, drag and drop the icon of the new HBA onto the icon of the old HBA in order to inherit the access path. For devices that must be set up on the server, however, you must manually specify this setting: 1. From the [Device (D)] menu, select [Refresh (R)]. 2. From All View, double-click the icon of the new device to display the view for the device. 3. You should select [Access Path (A)] and [Inherit (H)] and [Mode Start (S)] from [Operation (C)] of menu without

selecting any icons "The access path inheritance operation will be enabled. *" dialog box is displayed. 4. In this dialog box, drag and drop the icon of the new HBA onto the icon of the old HBA. This opens a dialog

box that requests confirmation of whether the access path is to be inherited. Click [OK] to inherit the access path. Then, according to the table below, inherit processing deletes in the applicable device the access path setting defined according to old HBA information. Next, it adds to the applicable device an access path setting defined according to new HBA information. However, no setting is added to the server. Add the StorageAffinity setting if it is required on the server. Device type Settings of SAN resource manager

Switch With zoning setting

Delete the single-pair WWPN zoning created with the old adapter WWPN. Then, add the single-pair WWPN zoning created with a new adapter WWPN. (However, no setting is required if an access path need not be inherited using port zoning.)

120


Without setting

Security setting Delete the old WWPN of HBA from the security setting, and add a new WWPN to the security setting.

Zone setting Delete the old WWPN of HBA from the security setting, and add a new WWPN to the zone setting. GR



5. Until you click [End] in the " The access path inheritance operation will be enabled. *" dialog box, you can continue to inherit access paths on multiple adapters by using drag-and-drop operations.

6. If the storage device is of the GR series, you may be required to reboot the system, depending on the firmware version.(This applies to the GR720/730 <for a version earlier than V11L21> and the GR740, 820, or 840 <for a version earlier than V03L52P1939>.)

8.5.5.3 Replacing a Windows server or a Solaris Server (other than by manually incorporating it) To replace a whole Windows server, inherit an access path by following the procedure described below. To replace a whole Solaris server, delete all access paths of the old server before SAN resource manager detects a new server and add access paths to the new server. 1. Set up a new server with a different IP address than that of the old server, and install the SAN management

agent. If you cannot set up a new server with a different IP address than that of the old server, delete all access paths of the old server before SAN resource manager detects the new server and adds access paths to the new server.

2. From the [Device (D)] menu, select [Refresh (R)]. 3. From All View, double-click the icon of the new device to display the view for the device. 4. From the [Operations (C)] menu, select [View Device] and [Add]. 5. You should select Access Path (A)] and [inherit (H)] and [Mode Start (S)] from [Operation (C)] of menu without

selecting any icons. This opens the " The access path inheritance operation will be enabled. ..." dialog box. 6. In this dialog box, drag and drop the icon of the new HBA onto the icon of the old HBA. This opens a dialog

box that requests confirmation of whether the access path is to be inherited. Click [OK] to inherit the access path. Then, inherit processing deletes in the applicable device the access path setting defined according to old HBA information. Next, it adds to the applicable device an access path setting defined according to new HBA information. For devices that must be set up on the server, however, you must manually specify this setting: Device type Settings of SAN resource manager

With zoning setting

Delete the single-pair WWPN zoning created with the old adapter WWPN. Then, add the single-pair WWPN zoning created with a new adapter WWPN. (However, no setting is required if an access path need not be inherited using port zoning.) Switch


Without setting

Security setting Delete the old WWPN of HBA from the security setting, and add a WWPN to the security setting.

Zone setting Delete the old WWPN of HBA from the security setting, and add a WWPN to the zone setting. GR




8. If the storage device is of the GR series, you may be required to reboot the system, depending on the firmware version. (This applies to the GR720/730 <for a version earlier than V11L21> and the GR740, 820, or 840 <for a version earlier than V03L52P1939>.)

121

8.5.5.4 Replacing a storage adapter (CA) and replacing a manually incorporated device

If a WWPN is changed because a storage adapter (CA) of the DF400, bridge, LT120/300, manually incorporated device, or other device is replaced, SAN resource manager cannot automatically detect the replacement event. Thus, drag and drop the icon of a new device onto that of an old device to inherit the access path. This procedure is not required for the GR, SANRISE, and Symmetrix machines because WWPNs are not changed after replacement. 1. From the [Device (D)] menu, select [Refresh (R)]. 2. From All View, double-click the device that has been replaced to display the view for the device. In the figures

below, those on the left are examples of before adapter (CA) replacement, and those on the right are examples of after adapter (CA) replacement. Since the switch can no longer recognize the old adapter, the icon of the old adapter indicates the "Unmonitored" state.

3. Go to step 5 if SAN resource manager automatically recognizes and displays an icon for the new adapter

(CA). 4. Install the new adapter in the target storage device. Bring up the manual-incorporating frame, find the new

adapter (Unknown) icon, and drag and drop the icon onto the device icon. After installation is complete, close the manual-incorporating frame. An example of the manual incorporating frame is shown below. The new adapter connected to Port 5 of the switch is installed in the storage device.

5. You should select [Access Path (A)] and [ Inherit (H)] and [Mode Start (S)] from [Operation (C)] of menu

without selecting any icons. It shows a dialog which shows message of " The access path inheritance operation will be enabled. *" , SAN resource control which is connecting to the switch shows as a square white icon which shows connection to the switch. If there is the port which cannot recognize connection equipment, it is set to UnknownPort. The new HBA correspond with this icon, it is set to new HBA and carry out to the next step.

122

6. In this dialog box, drag and drop the icon of the new adapter onto the icon of the old adapter. This opens a

dialog box that requests confirmation of whether the access path is to be inherited. Click [OK] to inherit the access path. Then, inherit processing deletes in the applicable device the access path setting defined according to old adapter information. Next, it adds to the applicable device an access path setting defined according to new adapter information. Device type Settings of SAN resource manager

GP7B8FC1 Change the setting of association between TID and WWPN in fjpfca.conf to the WWPN of the new adapter.

SN10-FC01, FC64-1063

[If the remote device is a disk device]

Change the setting of association among TID, LUN and WWPN in sd.conf to the WWPN of the new adapter.

[If the remote device is a tape or library device]

Without setting

LP-7000/8000/9000 Change the setting of association among TID, LUN and WWPN in lpfc.conf to the WWPN of the new adapter.

QLA-2200 Change the setting of association among TID, LUN and WWPN in qla2200.conf to the WWPN of the new adapter

With agent

HBA other than above Without setting

Solaris server

Without agent Without setting

Windows server With or without agent Without setting

Other server Without agent Without setting

With zoning setting


Switch

Without zoning setting specification Without setting


8. After the setting is changed, you must reboot the server if it does not support the activity configuration changes.

8.5.5.5 Replacing GR, SANRISE, Symmetrix, and Crossroads devices

To replace a whole GR, SANRISE, Symmetrix, or Crossroads device, inherit access paths as follows: 1. Set up the hardware configuration of the new device in the same way as for the old device. 2. Set up a new device with a different IP address than that of the old device, and register it in SAN resource

manager. If you cannot set up a new device with a different IP address than that of the old device, delete all

123

access paths of the old device before SAN resource manager detects the new device and add access paths to the new device.

3. From the [Device (D)] menu, select [Refresh (R)]. 4. From All View, double-click the icon of the new device to display the view for the device. 5. From the [Operations (C)] menu, select [View Device] and [Add] to display the icon of the old device. 6. From the [Operations (C)] menu and without any icon selected, select [Access Path] and [Inherit]. This opens

the " The access path inheritance operation will be enabled. *" dialog box. 7. In this dialog box, drag and drop the icon of the new adapter onto the icon of the old adapter. This opens a

dialog box that requests confirmation of whether the access path is to be inherited. Click [OK] to inherit the access path. Then, inherit processing deletes in the applicable device the access path setting defined according to old adapter information. Next, it adds to the applicable device an access path setting defined according to new adapter information. Device type Settings of SAN resource manager

GP7B8FC1 TID of fjpfca.conf and a WWPN correlation setup are changed into the new adapter WWPN.

SN10-FC01, FC64-1063

[If the remote device is a disk device]

Change the setting of association among TID, LUN and WWPN in sd.conf to the WWPN of the new adapter.

[If the remote device is a tape or library device]

Without setting

LP-7000/8000/9000 Change the setting of association among TID, LUN and WWPN in lpfc.conf to the WWPN of the new adapter.

QLA-2200 Change the setting of association among TID, LUN and WWPN in qla2200.conf to the WWPN of the new adapter.

With agent

HBA other than above Without setting

Solaris server

Without agent Without setting

Windows server With or without agent Without setting

Other server Without agent Without setting

With zoning setting


Switch

Without zoning setting specification Without setting


9. After the setting is changed, you must reboot the server if it does not support the activity configuration changes.

8.5.6 Switch zoning editing

Besides execution of one-to-one WWPN zoning in ordinary access path setup, SAN resource management provides a function that checks what kind of zonings are set up on the switch. If an unused zoning setting remains when a device is deleted because the access path was not deleted, this screen can be used to delete the setting.

The Zoning Information displayed in the switch property pertains to this function.

The zone name set on the switch and the WWPN defined in the zone are displayed here.

If one-to-one zoning has been set up, two WWPNs are stored in the zone. If zoning based on three or more WWNs and port information has been set up, the WWPNs that can be mutually accessed are displayed in the zone.

Deletion is possible for zone which the Delete check box is enable. Check the delete check box and click the [Delete the checked zoning information] button.

124

8.6 SAN Resource Fault Management

This chapter explains monitoring by SAN resource management for SAN device faults, the information displayed when a fault occurs, and the action to be taken for the fault. The support levels related to this chapter are explained in Chapter 1.5.1, "Hardware requirements."

8.6.1 Fault monitoring

SAN resource management corresponds to the SNMPTRAP fault reporting function of each device. The fault monitoring flow is described below. In addition, SNMP TRAP function is started by CIMOM service at the time of SAN resource manager starts. Since, When fault is announced by only Centric linkage or shell/batch linkage. It is not necessary to start SAN resource management window. 1. When a device detects a fault, the device sends SNMPTRAP to the SAN resource management server. a. Support levels A, B, and C

The SNMPTRAP send address is automatically set on the SAN resource management server when SAN resource management registers a device.

b. Support levels E, F, G, and J (device supporting SNMPTRAP) Manually set the SNMPTRAP send address for the device on the SAN resource management server. For information about setting the SNMPTRAP send address, see the user's guide supplied with the device that supports SNMPTRAP.

c. Support levels H and I Because the device side does not support the SNMPTRAP function, SAN resource management cannot monitor for faults.

2. SAN resource management takes one of the following actions for a fault according to the support level on the SAN resource management side:

a. Support levels A, B, and C Decodes and reports SNMPTRAP as is. Updates the icon status on the SAN resource management screen.

b. Support levels E, F, G, and J (device supporting SNMPTRAP) Reports SNMPTRAP as is. Does not update the icon status on the SAN resource management screen.

3. The event log and device event (which can be confirmed from the properties of a device) of SAN resource management are used to report SNMPTRAP as described in Item 2. An example of displaying an event log is shown below. Whether the event log is displayed can be selected from [Show/Hide][Event Log] on the [View (V)] menu. The device event can be confirmed from the properties of the device.

4. SAN resource management can also post the contents of the SNMPTRAP report to

SystemWalker/CentricMGR. See Chapter 8.9, "Linkage between SystemWalker/StorageMGR and SystemWalker/CentricMGR."

5. SAN resource management sets the contents of the SNMPTRAP report in the calling arguments of the

125

following shell file (UNIX) and batch file (Windows): [Solaris version] /etc/opt/FJSVswsam/trapop.sh argument1 argument2 argument3 [Windows version] environment-definition-directory¥etc¥san¥engine¥trapop.bat argument1 argument2 argument3 E-mail linkage with the description of a fault is possible by rewriting the shell and batch files. In SAN resource management, it is not essential for these shell and batch files to be set up. Argument1 : fault content is input. Argument2 : Device IP address is input. Argument3 : Host Name (FQDN) (If full domain name can not be got, IP address is input.)

SAN resource management supports only those faults occurring on a server that are related to path shutdown.

A switch can detect the ONLINE/OFFLINE state of a port. It can also report SNMPTRAP based on the ONLINE/OFFLINE state. Usually, however, SNMPTRAP is not reported based on ONLINE/OFFLINE state. (See Chapter 8.11, "SAN Resource Management Definition Files.")

The following is a sample Solaris trapop.sh for reporting a SAN resource management event in a mail message.

Executing grtraptest based on the above trapop.sh setup sends the following mail message to the addressee:

8.6.2 SNMPTRAP self-receive test

SAN resource management provides a command that issues SNMPTRAP for testing on the SAN resource management server. The command checks whether the SNMPTRAP receiver is correctly started and whether linked processing between SystemWalker/StorageMGR and SystemWalker/CentricMGR and linked processing between a shell file and a batch file are set up correctly. The command modifies SNMPTRAP internal information to make it look as if SNMPTRAP were sent from the device being monitored, and sends the information to the SNMPTRAP receive port.

Use the IP address of the device (GR or switch) registered in SAN resource management as the IP address in the argument. The information generated by the pseudo-SNMPTRAP is also recorded in the event log and as a device event (in the device properties).

The event log can be show by executed "F5" key or "Refresh ( R )" menu of "Device (D) " in SAN resource management window. (It may take time somewhat until it is reflected.)

* When SNMPTRAP of a GR registered in SAN resource management is generated in pseudo mode. (A fan fault is generated in pseudo mode, but the contents of the SNMPTRAP fault caused in pseudo mode differ from those of an actual SNMPTRAP fault that occurs. The difference occurs because the SNMPTRAP fault caused in pseudo mode is generated for testing purposes only.)

[Solaris version] # /opt/FJSVswsam/bin/grtraptest ip-address

126

* When SNMPTRAP of a switch registered in SAN resource management is generated in pseudo mode. (A port fault is generated in pseudo mode.)

[Solaris version] # /opt/FJSVswsam/bin/swtraptest ip-address

The following describes the possible cause of incorrect reception of SNMPTRAP.

8.6.3 Screen displayed when fault occurs and action to be taken

If a device fault occurs, information about the fault is displayed in the event log and as a device event. The icon of a faulty device whose support level is A, B, C, D, E, F, or G changes to [error](red) or [warning] (yellow). (Whether the color displayed is red or yellow depends on the definition of the device.) If an access path is affected by the SAN resource management fault, the status of the access path changes to [access path error] (red).

If SNMPTRAP is supported by a device whose support level is J and a device IP was specified during manual incorporation setup, SAN resource management displays the contents of the SNMPTRAP that will be received as is. The color of the device icon, however, does not change.

Right-clicking a device from the manual incorporation frame and setting the device status to "error" or "warning" manually from the device information change item of the displayed pop-up menu displays faults in red or yellow. These faults are displayed on the SAN management screen. Changing the icon color in advance allows devices to still be easily managed.

Take action for the fault as described below based on the status displayed on the screen. 1. When the status of a storage, library, or bridge is error or warning

On the SAN resource management screen, double-click the storage, library, or bridge to switch to the appropriate view and right-click the icon of the selected device. On the pop-up menu, execute [Call Management Software] (for a device able to work with the management software) to display the storage maintenance screen. Locate the faulty part using this screen. If necessary, have a Fujitsu CE replace the part. If a channel adapter (CA) is faulty, the error is displayed in Storage View. (Valid only for GRs)

2. When the status of a Fibre Channel switch/hub is error or warning On the SAN resource management screen, double-click the Fibre Channel switch/hub to switch to Switch/Hub View and right-click the icon of the selected switch/hub. On the pop-up menu, execute [Call Management Software] (for a device able to work with the management software) to display the storage maintenance screen. Locate the faulty part in the Fibre Channel switch using this screen. If necessary, have a Fujitsu CE replace the part. If the status of a port is abnormal because GBIC is faulty, the port is displayed in Switch/Hub View as [Fault]. In this case, the status of the affected access path is displayed as [access path error]. The name of the special file (device file) that is affected can also be identified by checking the access path properties. If the access path is defined in the access path settings of SAN resource management, the Fibre Channel switch zoning setup is defined in the WWPN zoning. As a result, even though the Fibre Channel switch port is faulty, operation can be continued as is by connecting the Fibre Channel cable to another Fibre Channel switch port.

3. When the status of the server is error or warning Check the physical route of the faulty access path ([access path error]) in Server View of SAN resource management. If no faulty device exists on the physical route, check whether an intermediate Fibre Channel cable is disconnected. If the cause cannot be determined, contact a Fujitsu CE.

4. Action to be taken for a faulty access path [access path error] In Server View, determine the name of the affected special file by checking the properties of the faulty access path [access path error]. The name (/dev/rdsk/cXtYd?s?) of the affected Solaris special file can be determined from X (controller number in the HBA properties) and Y (target ID in the access path properties). [Solaris server] For an access path configured using multipath disk control (MPLB, MPHD), take the following actions on the server after referring to the multipath disk control manual. (For MPHD, see the Multipath Disk Control Handbook. For MPLB, see the Multipath Disk Control Load Balance Option (MPLB) Handbook.)

a. Checking the access path status (iompadminfo) Check the configuration and status of the current access path. If a multipath disk has not been accessed, FAIL may not have been detected.

b. Halting I/O operation related to the faulty access path (iompadmchange) MPLB has a function that automatically halts any I/O operation that the location of the fault could affect.

c. Replacing the faulty part (when replacement is necessary) or taking action for the error When you need to replace the faulty part, contact a Fujitsu CE.

d. Restarting I/O operation of a halted access path (iompadm restart) For an access path that has not been configured using multipath disk control (MPLB, MPHD), the job in which the target special file is mounted is affected. Halt the job and take corrective action for the fault. If you need to replace the faulty part, contact a Fujitsu CE.

127

5. [For Solaris server] HBA (host bus adapter) replacement procedure For a server that does not support the activity replacement function, turn off the server power and replace the faulty HBA. Do not reboot or shut down the server in reconfiguration (reconfigure) mode while performing the HBA replacement procedure. (Executing the reboot -- -r or boot -r command changes the special file name.) For a server that supports the activity replacement function, operation can continue. It is only necessary to replace the faulty HBA and to execute access path inheritance (Chapter 8.5.5 Inheriting an access path). For more information about the activity replacement procedure, see the related manual.

a. Shutting down the server Confirm that the /reconfigure file does not exist and turn off the device. # ls /reconfigure /reconfigure: No such file or directory Confirm that the reconfigure file mentioned above does not exist. If a reconfigure file exists, delete it, replace the faulty HBA, re-create the file, and then restart the server. To delete the reconfigure file, enter the following command: # rm /reconfigure After deleting the reconfigure file, use the ls command confirm again that the file does not exist. Shut down the server without reconfiguring it. # /usr/sbin/shutdown -i0

b. Replacing the faulty HBA To replace a faulty HBA, contact a Fujitsu CE.

c. Starting the server Start the server. Note that the access path is not recovered at this point because the zoning based on the previous HBA information is defined on the storage and the Fibre Channel switch.

d. Inheriting the access path (resetting security) Execute access path inheritance (Chapter 8.5.5 Inheriting an access path) from SAN resource management. Then, define the zoning settings on the storage and Fibre Channel switch so that the access path can be accessed as in the previous access using the new HBA information.

e. Restarting the server Restart the server without reconfiguring it (execution of the reboot---r and boot-r commands is disabled). # /usr/sbin/shutdown -i6 Because the access path is recovered at this point, the multipath disk control path is also recovered.

6. [For Windows/other servers] HBA (host bus adapter) replacement procedure For a server that does not support the activity replacement function, turn off the server power and replace the faulty HBA. For a server that supports the activity replacement function, operation can continue. It is only necessary to replace the faulty HBA and to execute access path inheritance (Chapter 8.5.5 Inheriting an access path). For more information about the activity replacement procedure, see the related manual.

a. Shut down the server. b. Replace the faulty HBA. c. Start the server.

Note that the access path is not recovered at this point because the zoning based on the previous HBA information is defined on the storage and the Fibre Channel switch.

d. Inheriting the access path (resetting security) Execute access path inheritance (Chapter 8.5.5 Inheriting an access path) from SAN resource management. Then, define the zoning settings on the storage and Fibre Channel switch so that the access path can be accessed as in the previous access using the new HBA information.

e. Restart the server. 7. Action taken by SAN resource management after a part is replaced

Check the current device status by selecting [Refresh] from the [View] menu. If the device status is corrected by replacing the part, the status of the device is displayed as being normal. However, for an LT300, an LT120, and a device set up using the Manual Embedding frame, the display status must be manually restored to normal. This is done by right-clicking the device icon in the Manual Embedding frame and selecting Edit Device Information on the pop-up menu.

- When the storage and Fibre Channel switch have returned to normal status but the status of the server is still error or warning Recover the faulty multipath disk control path as described in the multipath disk control (MPHD, MPLB) manual. (For MPHD, see the Multipath Disk Control Handbook. For MPLB, see the Multipath Disk Control Load Balance Option (MPLB) Handbook.) After recovering the faulty path, select [Refresh] and check the current device status.

8.7 Access Path Diagnosis

SAN access path diagnosis is performed by issuing the SCSI command from the HBA on the server side to the CA on the storage side. The diagnosis checks whether storage control command processing flows correctly on an access path. (This function does not call the hardware diagnosis function.) Diagnosis is valid only for the access path between a server and a disk (array disk) in an SAN environment (connection via a Fibre Channel switch).

128

Access path diagnosis can also be executed when MPHD/MPLB/multipath disk control for Windows is defined.

HBAs that supports access path diagnosis

Server HBA

Solaris GP7B8FC1, Qlogic QLA2200, Emulex LP7000/LP8000/LP9000, SN10-FC01, or JNI FC64-1063

WINDOWS NT/2000 Qlogic QLA2100F, QLA2200, GP5-FC101/FC102, or PG-FC102

1. Display Server/Storage View. If no access path is displayed, select [Access Path] from [Display/Non-display] on the [View (V)] menu to display access paths.

2. Right-click an access path to display a pop-up menu and select [Diagnosis] from [Access Path] on the menu. Alternatively, click an access path and select [Diagnosis (I)] from [Access Path] on the [Operation (C)] menu.

3. Enter the number of the LUN to be diagnosed. If SAN resource management recognizes the LUN of the access path to be diagnosed, the number is displayed by default.

4. Check the diagnosis result.

If the result of the diagnosis indicates a problem, capture the current status by selecting [Refresh (R)] from [Device (D)] or selecting [F5] and check whether there is a problem on the storage area network. If you cannot determine the cause, contact a Fujitsu SE.

8.8 Stopping Services

Stop the service used by SAN resource management as described below.

8.8.1 Stopping a storage server service

For information about stopping a service of the SAN management agent operating on the transaction server, see Chapter 5 in the Installation Guide.

8.8.2 Stopping a storage management server service

Because SAN resource management operates on CIMOM, CIMOM must be stopped to stop a storage (operation) management server service. CIMOM usually stops automatically when Solaris server power is turned off.

Also, to stop the SNMP trap monitoring service activated for fault monitoring, by using stopping SystemWalker MpWksttr service. This SNMP trap service is common to SystemWalker/StorageMGR and SystemWalker/CentricMGR.

129

8.9 Linkage between SystemWalker/StorageMGR and SystemWalker/CentricMGR

Linkage between SystemWalker/StorageMGR and SystemWalker/CentricMGR enables SystemWalker/CentricMGR to perform centralized monitoring of storage (SAN) devices. Linkage also makes it easier to investigate storage (SAN) device errors.

8.9.1 Functions for linkage with SystemWalker/CentricMGR

+Centralized monitoring

Storage device icons are displayed on the monitoring screens (system, transaction , and Web console) of the SystemWalker/CentricMGR operation management client. If a fault occurs, it is posted to the corresponding icon.

SystemWalker/CentricMGR e-mail and pagers make fault monitoring possible even though a person is not physically present.

In addition, SAN resource manager decodes the contents of SNMPTRAP in detail based on the support level of the device. This information is posted without change and reported as an event to CentricMGR. Thus, the contents of an error can be easily identified in a CentricMGR window.

The icon of a device on the CentricMGR where an error occurred is displayed with an "X". The contents of an error are displayed for each event. After the contents of an event are checked and the error is corrected, "Handled" is set for this event. This clears the "X". Note that the "X" is not automatically cleared by error recovery.

+Screen linkage

On a SystemWalker/CentricMGR monitoring screen (system monitoring screen or transaction monitoring screen), select StorageMGR on the node pop-up menu of the faulty storage device to start the SystemWalker/StorageMGR Web screen. This procedure enables you to easily investigate storage (SAN) device faults.

8.9.2 Setup procedure for linkage between SystemWalker/StorageMGR and SystemWalker/CentricMGR

Execute setup on the SystemWalker/CentricMGR operation management server and client with the following procedure. On the operation management server, log in as the root user. On the operation management client, log in with a user name belonging the administrator group of the local group.

130

8.9.2.1 Setup procedure on the operation management server

1. Start SystemWalker/CentricMGR on the SystemWalker/CentricMGR operation management server. 2. Execute the operation management server setup command.

Insert the CD-ROM for SystemWalker/StorageMGR-MSE on the operation management server and execute the operation management server setup command with the following procedure.

3. Restart SystemWalker/CentricMGR on the operation management server.

· When MIB information file of CentricMGR is set up uniquely, it cannot be set up normally. In this case, please

execute the operation as follows. 1. Back up "mpnmkind50.ini.05" file. 2. Rename "mpnmkind50.ini" file to "mpnmkind50.ini.05". 3. Execute manset.bat module again.

8.9.2.2 Setup procedure on the operation management client

1. Execute the operation management client setup command.

Insert the CD-ROM for SystemWalker/StorageMGR-MSE on all the SystemWalker/CentricMGR operation management clients and execute the operation management client setup command with the following procedure.

2. Execute node detection for the subnet where the SAN device on the operation management client is located. 3. Register the SystemWalker/StorageMGR Web screen as an item on the node pop-up menu.

Use the SystemWalker/CentricMGR mpaplreg command to register the SystemWalker/StorageMGR Web

131

screen as an item on the node pop-up menu of the storage device. Add the storage device to the node pop-up menu by accessing the menuset.bat file under cd-rom-drive¥pc¥win32¥centric, as shown in the example below. For information about modifying the menuset.bat file, see Chapter 11.4.6, "SystemWalker/CentricMGR screen linkage command (mpaplreg)."

- Perform this operation each time a new storage (SAN) device is added. - If the IP address of the SystemWalker/StorageMGR management server is changed, delete the

registered menus with the command shown below and then re-register them.

After the setup procedure finishing, without changing the case of Windows or with rebooting CentrcMGR the case of Solaris, and To recognize the node of observation area change indication of the resistered icon.

8.9.3 Notes on linkage between SystemWalker/StorageMGR and SystemWalker/CentricMGR

Note the following regarding linkage between SystemWalker/StorageMGR and SystemWalker/CentricMGR in each server installation environment:

8.9.3.1 When the SystemWalker/CentricMGR operation management server and SystemWalker/StorageMGR management server are the same server

When the SystemWalker/CentricMGR operation management server and SystemWalker/StorageMGR management server are the same server, perform the following operation: 1. Suppress direct reception on the Centric side of SNMP traps of the device managed by

SystemWalker/CentricMGR. If the SystemWalker/CentricMGR operation management server and SystemWalker/StorageMGR management server are on the same host, suppress direct reception on the Centric side of SNMP traps of the device managed by SystemWalker/CentricMGR. SNMP traps are received and processed by StorageMGR and reported to CentricMGR.

a. Select [Event]-[Define Action] from System Monitoring on the SystemWalker/CentricMGR operation management client. -> The [Define Event Monitoring Conditions] dialog box opens.

132

b. Select [Event]-[Add Event] in the [Define Event Monitoring Conditions] dialog box.

-> The [Define Event] dialog box opens. Set the following items.

· Identify Host Name

Select "Do Not Identify."

133

· Identify Monitoring Event Type Select "Do Not Identify."

· Identify Error Type Select "Do Not Identify."

· Identify Message Number Select "Do Not Identify."

· Identify Significance (valid only in SystemWalker/CentricMGR5.1 and later) Select "Do Not Identify."

· Identify Label Select "Do Not Identify."

· Identify Message Text Set one of the following values for each event definition: A message text must be written only when individual devices are managed. None is required when individual devices are not managed. enterprise:aplNetStorage¥.1": Fujitsu GR series RAID enterprise:enterprises¥.116¥.3¥.11": Hitachi SANRISE enterprise:enterprises¥.1139¥.1":EMC Symmetrix (ECC Agent) enterprise:enterprises¥.11¥.2¥.3¥.9¥.7¥.1":LT120/HP Surestore enterprise:enterprises¥.1588¥.2¥.1¥.1":BrocadeFC-Switch enterprise:enterprises¥.1754¥.1¥.2¥.2":GadzooxFC-Hub enterprise:aplNetFunction¥.21¥.2: StorageMGR agent (Valid in SystemWalker/CentricMGR 5.) enterprise:aplNetFunction¥.55¥.1:LMF (LT300) agent enterprise:aplSANMgr¥.2: StorageMGR agent (valid in SystemWalker/CentricMGR 5.1 or after)

c. [Action]-[Set Action] for the event set in b -> The [Define Action] dialog box opens. Select the [Message Monitoring] tab and set the following items.

· Send to High-Order System

Select "No." Perform operations a to c for each of the above three message texts.

If the SNMP standard trap is reported from the storage (SAN) device as an event, suppress the trap depending on the operation to be implemented by using the above information.

134

8.9.3.2 When SystemWalker/CentricMGR operation management server and SystemWalker/StorageMGR management server are not the same server

When SystemWalker/CentricMGR operation management server and SystemWalker/StorageMGR management server are different servers, note the following.

· If the SystemWalker/CentricMGR operation management server and SystemWalker/StorageMGR

management server are managed by the same DNS server or if each /etc/hosts definition is not identical, node names cannot be detected correctly and linkage with SystemWalker/CentricMGR is not possible.

· The SystemWalker/CentricMGR agent must be installed on the SystemWalker/StorageMGR management server.

8.9.4 Versions required for linkage between SystemWalker/StorageMGR and SystemWalker/CentricMGR

Linkage between SystemWalker/StorageMGR and SystemWalker/CentricMGR assumes that the following SystemWalker/CentricMGR versions are used. · Windows SystemWalker/CentricMGR-M EE/SE V10.0

Combinations of SymfoWAREServer products on the SystemWalker/CentricMGR operation management server requires that conditions for combining SymfoWAREServer products be met and requires a SystemWalker/CentricMGR urgent fix. If an unsuitable SymfoWAREServer is installed or the required urgent fix is not applied, the SystemWalker/CentricMGR environment cannot be set up.

For the compatibility conditions between SystemWalker/CentricMGR versions and SymfoWAREServer versions, see Table 7.9.

[Table 7.9 Compatibility conditions between SystemWalker/CentricMGR versions and SymfoWAREServer versions]

SymfoWAREServer versions SystemWalker/CentricMGR versions

4.0

SystemWalker/CentricMGR-M EE/SE V10.0 Yes

8.10 Performance Management

8.10.1 Outline of performance management

SAN resource management supports performance management functions for the SN200/Silkworm Fibre Channel switch and for GR720 and higher. These functions give the system administrator a detailed understanding of the operating and the load status of each device. SAN resource management does not support performance management for GR820/GR480 mainframe volumes.

The following information can be managed: 1. SN200/Silkworm Fibre Channel switch - Performance of each port

Reception/transmission (MB/s) - Number of CRC errors per port 2. GR720 and higher - HLU and RLU (LUN_R)

- Read/write count (processing count, IOPS/s) - Read/write data transfer amount (MB/s) - Average read/write response time (ms) - Read/prefetch/write cache hit rate (%)

- Disk drive - Disk usage (busy) rate (%)

The performance-monitoring interval can be set to 30 seconds, one minute, or five minutes (five minutes only for GR devices).

135

In addition, graph windows in the following time units are provided. 1. Graph window by hour

A line graph covering a period of one hour is displayed using the average values for every 30 seconds, for every minute, or for every five minutes, depending on the performance-monitoring interval.

2. Graph window by day A line graph covering a period of one day is displayed using the average values for every ten minutes.

3. Graph window by week A line graph covering a period of one week is displayed using the average values for every hour.

· The performance management function is always started by the CIMOM daemon (service) when the SAN

resource management server is started. The performance management function starts in the background to obtain performance information of a target device of performance management. Therefore, performance information can be obtained regardless of whether the SAN Resource Manager window is displayed. To stop performance information acquisition, specify that SAN resource manager stop performance management.

· During performance management of GR devices, the performance of the GR devices may be impacted because of a performance information acquisition overhead.

8.10.2 Performance management flow

If SAN resource management directs a device on the SAN management screen to execute performance management, the performance management function periodically issues SNMP to the device via the LAN to collect device performance information. The collected information is stored on the storage management server as performance data. The function displays this performance data on the performance management screen for performance management.

1. Checking the disk capacity on the storage management server side

for execution of performance management, sufficient free disk space to store the performance data is required on the storage management server. Check whether sufficient free disk space has been allocated by using the disk space estimation method explained in Chapter 2 of Installation Guide. SAN resource management provides a function that deletes the performance data that exceeds the set retention period (usually 7 days). The data collected before this period is automatically deleted. The retention period is settable. See 8.11.3.

2. Ensuring adequate performance

136

Left-clicking the device on the SAN resource management screen of All View (O) and selecting [Performance Management Setup (S)] on the [Device (D)] menu in the bar menu opens the Monitoring Status Setup dialog box. The Monitoring Status Setup dialog box can also be opened by selecting [Performance Management Setup (S)] on the pop-up menu displayed by right-clicking the device icon. For a GR, enter minimum and maximum values for the OLU (LUN_V) whose performance is to be assured. LUN setup is implemented to eliminate adverse effects on the disk area where performance data is stored and reduce load caused in the acquisition of performance data. Since in this case, however, only the required minimum LUN assurance is implemented, only the required minimum OLU range needed to store performance data should be entered. Because performance data is internally acquired in 64 LUN units, LUN performance information that approximates the performance data entered here is also acquired. (For example, if OLU (LUN_V) is set within the range from 70 to 80 on the screen, OLU information from 64 to 127 is internally acquired.) For both a GR and a switch, enter a performance information acquisition interval of 30, 60, or 300 seconds. If 2,048 OLUs or more are reserved on the GR, however, only 60 seconds or 300 seconds can be set.

Executing [Start] in the Monitoring Status Setup dialog box issues the performance assurance instruction to the performance assurance function (see (a) in the above figure of 8.10.2 Performance management flow). When it receives this instruction, the performance assurance function acquires device performance information via the LAN and stores it as performance data. Because the performance assurance function is started as a storage management server daemon, when the storage management server is being started, the performance assurance function continues to acquire device performance information even though the SAN management screen has not started. Since, for a GR, the performance assurance function recognizes the logical configuration of the device and starts performance assurance, a logical configuration assurance time (tens of seconds to several minutes) is required from the first time that performance assurance starts to the time that performance information is actually acquired.

The table below lists the colors, statuses, and user actions for the P mark. The color may be different from that displayed in the current status box. From the SAN Resource Management window, select [Refresh] or press [F5] to check the latest status. Color of P mark Status User action

Green Performance being monitored (normal) Performance is being monitored

Yellow

Performance monitoring under recovery (device timeout, etc.)

The SAN resource management server cannot communicate with the device. Check the network status and the device status. If you have logged into a device of the GR series, log out.

Failure to write to performance information file

Check the write permission to the file and the free space of the file system.

Wrong registration password for a GR device

Use SAN resource manager to set up Change Account Information for Device Management ( C ), and start performance monitoring again.

Red

Internal error Contact a Fujitsu engineer. 3. Opening the Performance Monitoring window

To display the performance, open the Performance Monitoring window. To open the Performance Monitoring window, select [File (F)] in All View (O) and then [Performance Management Window (W)].

4. Displaying performance of the selected device Similar to the display of performance information in (b) in the figure Displaying performance of the selected device above, device performance information can be displayed on the performance management screen. To

137

display this information, drag the device icon displayed in All View of the SAN resource management screen and drop it on the performance management screen. Several performance management screens can also be created. Also, multiple devices can be dropped and displayed on one performance management screen.

5. Displaying switch performance a. Displaying switch port performance information

In the device tree displayed on the performance management screen, select the port number of the switch whose performance you want to display, and right-click to open the pop-up menu. On the pop-up menu, select [Show Performance Graph].

The Port Performance dialog box shown below opens. In the dialog box, select the box item that you want to display. * As Time Axis, select the time interval (1 hour, 1 day, 1 week) of the graph that you want to display. * Throughput displays the amount of data transferred (MB/s). Select the type of information here. Select whether to display a graph window showing port transmission performance, a graph window showing port reception performance, or a graph window showing both port transmission and port reception performance. Transmission and reception can be selected at the same time, but if transmission and reception check box has been selected, transmission and reception cannot be selected. * Error Information displays a graph window showing the number of CRC errors that have occurred on the port. Selecting Error Information displays the CRC Error graph window.

The following are the results displayed when the items in the above dialog box are selected. The graph windows of different throughputs on the transmission and reception sides are displayed in one-hour intervals. These graph windows make it possible to understand the port operating status.

138

Performance information for multiple ports can be displayed simultaneously. To do so, in the tree, hold down the [CTL] or [Shift] keys and click the desired ports, then right-click to display the graphs. In this case, as shown in the figure below, "Open Window for Every Port" is added to the Port Performance dialog box. When "Open Window for Every Port" is selected, a different window is opened for each port. If "Open Window for Every Port" is not selected, Total Throughput can be selected. Selecting Total Throughput displays the total throughput of the ports in a graph. If Total Throughput is not selected, the throughput of each port is displayed in the same graph window. If transmission/reception check box is selected, Total Throughput must be always selected.

The following is an example of port information display in which "Open Window for Every Port" and Total Throughput are not selected. Which graph lines belong to which port can be checked by opening the graph lines in the window. This example shows that the usage rates of port 0 and 4 are high.

139

6. Displaying GR performance

The following GR logical configuration tree can be displayed by dropping the GR icon on the performance management window. "ZONE" indicates the number of the GR ZONE function. "HLU" is the logical unit number of the host side. This number is represented as "HLU X(OLU X)" in the tree because it is assigned to "OLU (=LUN_V)," to which the unique device numbers managed on the GR are given. "RLU" positioned under "HLU" indicates the RLU (rank) to which the HLU belongs. "PLU" (physical drive) under "RLU" indicates the PLUs make up a rank. "OLU" under "RLU" indicates the numbers of other OLUs that belong to the same RLU. Values beginning with 0x are hexadecimal.

140

a. Displaying HLU and RLU performance information

In the device tree displayed on the performance management screen, select the number of the HLU or RLU whose performance you want to display, and right-click to open the pop-up menu. On the displayed pop-up menu, select [Show Performance Graph (G)]. Multiple HLUs and RLUs can also be selected. Select multiple HLUs and RLUs by clicking while you are holding down the [CTL] or [Shift] keys, then right-click to execute [Show Performance Graph (G)]. The dialog box shown below opens. In the dialog box, select the graph window that you want to display. * As Time Axis, select the time interval (1 hour, 1 day, 1 week) of the graph that you want to display. * IOPS indicates that how many I/Os were issued per second. * Throughput indicates the amount of data transferred (MB/s). * Response time indicates the average I/O processing time (ms). * You can select whether to display a read-direction graph window, write-direction graph window, or graph window that displays both read and write information (R/W). This selection can be made for individually for IPOS, Throughput, and Response Time. Read and write can be selected at the same time, but if R/W is selected, neither read nor write can be selected. * Cache Hit Rate indicates the rate (%) at which cache is hit. Four graph windows, each of which can be selected, are provided for Cache Hit Rate. The windows are a window showing the read-direction cache hit rate, a window showing the write-direction cache hit rate, a window showing the prefetch hit rate, and a window showing all information (R [read]/W [write]/P [prefetch]). Read, write, and prefetch can be selected at the same time, but if R/W/P is selected, none of read, write, and prefetch can be selected.

141

If multiple logical units are specified and graph display is executed, "Open Window per HLU" is displayed in the dialog box. Selecting "Open Window per HLU" displays a graph window for each HLU. If "Open Window Every HLU" is not selected, Total is displayed for IOPS and Throughput and Average is displayed for Response Time and Cache Hit rate in the dialog box. If Total is selected, the corresponding the graph windows is displayed. If Total is not selected, information for multiple units is displayed in the same graph window. However, if R/W/P is selected, Total and Average must be always selected.

b. Displaying PLU (physical drive) performance In the device tree displayed on the performance management screen, select the number of the PLU whose performance you want to display, and right-click to open the pop-up menu. On the displayed pop-up menu, select [Show Performance Graph (G)]. Multiple PLUs can also be selected. Select multiple PLUs by clicking while you are holding down the [CTL] or [Shift] keys, then right-click to execute [Show Performance Graph (G)]. The dialog box shown below opens. In the dialog box, select the graph window that you want to display. * As Time Axis, select the time interval (1 hour, 1 day, 1 week) of the graph that you want to display.

If multiple logical units are specified and graph display is executed, "Open Window Every PLU" is displayed in the dialog box. Selecting "Open Window Every PLU" displays a graph window for each PLU. If "Open Window Every PLU" is not selected, multiple PLUs are displayed in the same graph window.

7. Performance data Performance data is stored in a CSV file in any of the following storage management server directories: working-directory¥var¥san¥engine¥perf¥year-month-day¥enterprise-code-of-device-type¥device-id Information that is no longer needed can be deleted directly from year-month-day and later. This file can be also be saved for each directory as required, and whenever necessary, be restored and displayed in the same format.

8. Using graph windows If the amount of performance data becomes large (in particular, when several GR RLUs are selected) and LAN load is heavy, displaying a graph window with the [Previous Hour] or [Next Hour] button takes a long time. In this case, opening the pop-up menu by right-clicking the screen chapter of the graph window displays a command that can be used to display a graph window whose graph time interval has been modified. Select this command to display "One Day Graph Window" from the One hour graph window, move the mouse inside the One day graph window to the desired time, and right-click to redisplay the pop-up menu. If you select "One Hour Graph Window" on the pop-up menu in this state, you can easily move the mouse to the time graph

142

window that you want to check. 9. Example of using performance management

If an I/O delay occurs between a server and a storage, you can use the procedure below to investigate whether the cause of the delay is on the storage. Since this is only an example, you will not always be able to determine the cause of the I/O delay using this method.

a. Identify the time at which the I/O delay occurred and the access path. b. Using SAN resource management, check the zone and HLU numbers of the GR defined in the target

access path. c. Using performance management, display and check the target HLU performance. d. If the HLU response time is bad, check RLU performance. If the RLU response time is also bad, search

the RLU for other OLUs and determine to which HLU the found OLU is assigned. Next, check the I/O status of the HLU and whether the RLU load is heavy. If the load is heavy, take action such as moving the HLU to another RLU.

10. Stopping performance assurance On the SAN resource management screen (All View (O) ), click to select the device whose performance assurance you want to stop, then select [Performance Management Setup (S)] from the [Device (D)] menu. Alternatively, right-click to open a pop-up menu, select [Performance Management Setup (S)], and then select [Stop] on the Monitoring Status Setup screen.

When multiple SAN resource management window (clients) are started, if these performance managements are started with each different parameter to the object device, the performance is secured based on the parameter started at the very end.

8.11 SAN Resource Management Definition Files

8.11.1 Outline of definition files

Define the detailed setup used for SAN resource management internal control in the SAN resource management definition file (sanma.conf), performance management definition file (perf.conf) and bridge definition file (bcm.conf: See, Chapter 8.11.4). Edit these files as required, but do not modify any parameter values that are not included in Chapter 8.11.2 "Explanation of parameters" and Chapter 8.11.3 "Explanation of perf.conf parameter" 1. sanma.conf (SAN resource management definition file)

The sanma.conf file is stored in the following locations as the detailed setup file of the SAN management control chapter: environment-definition-directory¥etc¥san¥engine¥sanma.conf Select the Reread Definition File button from [Option (O)] on the [View (V)] menu or by restart CIMOM,, SAN resource management operates after reading and incorporating the contents of this file.

2. perf.conf (performance management definition file) The perf.conf file is stored in the following locations as the detailed setup file of the SAN management control chapter: environment-definition-directory¥etc¥san¥engine¥perf.conf The performance management chapter operates while reading this file every four hours and incorporating its contents.

8.11.2 Explanation of sanma.conf parameters

1. GRSC_GR Be sure to set GRSC_GR when GRSC-managed GRs are managed with SAN resource management. SAN resource management implements exclusive control by executing control for the GRs under GRSC management via GRSC. If all of the GRs managed by SAN resource management are under GRSC, set GRSC_GR as follows: GRSC_GR = "ALL" If only one GR is under GRSC management, set the IP of the GR. Example) GRSC_GR ="10.11.12.13"; If multiple GRs are under GRSC management, write their IPs delimited with the space character. Example) GRSC_GR ="10.11.12.13 10.11.12.14"

2. AUTODISCOVER_SUBNET Specify the address of the subnet to be searched in an automatic device search by SAN resource management. When writing more than one subnet address, delimit them by a comma (,). Example) AUTODISCOVER_SUBNET="10.12.13.255,133.134.13.255"; The storage management server issues an SNMP broadcast to automatically detect devices for these subnets. If restrictions are placed on this broadcast in the network setup, however, this function is not effective.

3. LOGICAL_MANAGER_IP You need to set up with this if you carry out SAN resource control with cluster or on a server which has

143

logical/physical IP. If you register this parameter and change the value after carrying out, you need to change the trap sending address of control device(support level A,B,C) with CLI command. If "LOGICAL_MANAGER_IP = "";" is specified, SAN resource control calculate IP address of control server automatically. But, it is impossible for SAN resource control to recognize logical IP address automatically. In this case, however, if the storage management server moves to the one with a different physical IP in cluster operation, SNMPTRAP cannot be correctly sent to the destination server. For this reason, in the cluster environment, the logical IP of the cluster must be set on the device side. Example) LOGICAL_MANAGER_IP = "10.12.13.14"; For cluster operation, the management device must be positioned in the network configuration so the device can always reach this logical IP. After this parameter is changed, the change must be reflected in the SAN resource management definition files and the trap transmission destination of the management device (support level A, B, or C) must the modified the CLI command.

4. SWITCH_PORT_OFFLINE_ONLINE_HANDLING_LEVEL Set the Online/Offline SNMPTRAP control of the switch port. Enter the decimal value that is equivalent to the sum of the set bits. Usually, if Online/Offline occurs, only the function that displays status change on the SAN resource management screen is enabled (that is, this value is 1). For 000b, port Online/Offline is ignored. For 001b, port Online/Offline displays the status on the screen. For 010b, port Online/Offline creates a device event (indicated in the device properties). For 100b, port Online/Offline creates an event log. Example) SWITCH_PORT_OFFLINE_ONLINE_HANDLING_LEVEL = 7; (All functions are enabled.)

5. SET_SW_ZONING_ALWAYS When the access path is set, the switch is set of port-zoning, and, the switch needs to add zoning setting, SAN resource management server does not set zoning setting to the switch normally. When "1" is set to this parameter, even in this case, SAN resource management server sets "1 to 1 WWPN-Zoning". (except No Security switch) Example) SET_SW_ZONING_ALWAYS = 1; ("0" default)

8.11.3 Explanation of perf.conf parameter

1. PERF_DATA_KEEP_DAYS Define the number of days that performance management will retain performance data. When the number of specified days elapses, the performance data is automatically deleted. If the number of retention days is set to 0, the performance data will not be deleted. The number of retention days does not include the current day. By default, the number of retention days is defined as seven days, as shown below. Modify this value as required. PERF_DATA_KEEP_DAYS = 7;

8.11.4 bcm.conf (bridge definition file) Device classification of the SCSI device connected to the bridge can be set in SAN Management. In the bcm.conf file, SCSI device VenderID, ProductID, Lun Number, device classification are wrote down. SAN Management compares SCSI information (VenderID,ProductID,LUN Number) set in bridge to bcm.conf file definition. If these data are in agreement, the device classification of the device information will be set up as a device classification of a SCSI device. The bcm.conf file is stored in the following locations as the detailed setup file of the SAN management control chapter: environment-definition-directory¥etc¥san¥engine¥bcm.conf

When SAN Management restart, SAN Management reflects and operates with bcm.conf definition.

Example)

# A comment line is started by '#'. #VenderID,ProductID,LUN,DeviceType(0:Unknown,1:Disk,2:Drive,3:Array,4:Robot) #Please describe data in order. IBM,03590B11,0,2 IBM,03590B11,1,4 FUJITSU,M8100AA2,0,2 FUJITSU,M8100AA2,1,4 Quantum,DLT4000,1,2 #STK,9730,1,4 IBM,ULT3580-TD1,0,2

8.12 SAN Management Agent

The SAN management agent enables SAN resource manager to manage Storage servers. Two management

144

methods are available in SAN resource manager: management with and without this agent installed on Storage servers. If this agent is used, SAN resource manager can manage Storage servers as explained below. 1. SAN management agent of Solaris server - Automatic detection and configuration load of devices (See Chapter 8.4, "SAN Resource Configuration

Management," in this chapter.) - Setup of access paths including binding of server HBAs (storage affinity) (See Chapter 8.5, "Access

Path Management," in this chapter.) - Error and status monitoring with the Fujitsu multi-path disk control feature (See Chapter 8.6, "SAN

Resource Fault Management," in this chapter.) - Access path diagnosis (See Chapter 8.7, "Access Path Diagnosis," in this chapter.) 2. SAN management agent of Windows NT/2000 server - Automatic detection and configuration load of devices (See Chapter 8.4, "SAN Resource Configuration

Management," in this chapter.) - Error and status monitoring with the Fujitsu multi-path disk control feature (See Chapter 8.6, "SAN

Resource Fault Management," in this chapter.) - Access path setup (not including binding of server HBAs) (See Chapter 8.5, "Access Path

Management," in this chapter.) - Access path diagnosis (See Chapter 8.7, "Access Path Diagnosis," in this chapter.) Precautions on using the SAN management agent are explained below for each platform, and user actions required for errors are described below.

For information on installation, starting, and stopping each type of agent, see Chapters 2, 3, and 5 in the SystemWalker/StorageMGR Installation Guide.

8.12.1 SAN management agent of Solaris server

8.12.1.1 Automatic update of a definition file

The SAN management agent automatically changes the following device definition files and fiber channel environment definition files on the server according to the access path setting of the SAN resource management function. · Path setting

Common to HBAs of different vendors: /kernel/drv/sd.conf · Storage affinity setting

If an HBA is the GP7B8FC1: /kernel/drv/fjpfca.conf If an HBA is the SN10-FC01 or FC64-1063 of JNI: /kernel/drv/sd.conf If an HBA is the LP7000, 8000, or 9000 of Emulex: /kernel/drv/lpfc.conf If an HBA is the GP5-FC102, PG-FC102, and QLA2200 of Qlogic: /kernel/drv/qla2200.conf If the server enters an error state after an access path is set up with the SAN resource management function, you can perform a recovery using the settings file that is backed up before the setup operation. The stored backup file is /var/opt/FJSVswsaa/backup. The backup file has the original file name plus ".san_bak001".

If device registration with the SAN resource management function enables recognition of the operation management server to which a detected error must be reported, the following file on the server is updated.

Access control file: /etc/snmp/conf/snmpdx.acl

8.12.1.2 User actions for errors in SAN management agent

If a SAN management agent error information is output to /var/adm/messages during device registration, the error may have occurred during the update of the access control file. Stop snmpdx and take the following action: 1. To stop snmpdx, make a root user enter the following command:

# /etc/init.d/init.snmpdx stop 2. To verify that snmpdx and sanad have stopped, enter the ps command.

# /bin/ps -ef|grep snmpdx

# /bin/ps -ef|grep sanad If the processes have not stopped, make a root user enter the following command again in order to stop snmpdx: # /etc/init.d/init.snmpdx stop

If the processes still have not stopped, execute the following command: # /usr/bin/kill -9 < process-id >

3. Save the following files to any desired directory as necessary: - /var/opt/FJSVswsaa/sanm.ip - /var/opt/FJSVswsaa/sana.id

145

- /etc/snmp/conf/snmpdx.acl 4. Delete the following file:

# rm /var/opt/FJSVswsaa/sana.id 5. Initialize the following file:

# cp /dev/null /var/opt/FJSVswsaa/sanm.ip 6. Restore the access control file:

# cp /var/opt/FJSVswsaa/backup/snmpdx.acl.san_bak001 /etc/snmp/conf/snmpdx.acl

7. Restart snmpdx to restart the SAN management agent. # /etc/init.d/init.snmpdx start

If a SAN management agent error information (Message ID = 3400) is output to /var/adm/messages during access path setup or access path deletion, the error may have occurred during the update of the definition file. Stop snmpdx temporarily, and take the following action:

8. To stop snmpdx, make a root user enter the following command: # /etc/init.d/init.snmpdx stop

9. To verify that snmpdx and sanad have stopped, enter the ps command. # /bin/ps -ef|grep snmpdx

# /bin/ps -ef|grep sanad If the processes have not stopped, make a root user enter the following command again in order to stop snmpdx: # /etc/init.d/init.snmpdx stop

If the processes still have not stopped, execute the following command: # /usr/bin/kill -9 < process-id >

10. Save the following files to any desired directory as necessary: - /kernel/drv/sd.conf - /kernel/drv/fjpfca.conf - /kernel/drv/lpfc.conf - /kernel/drv/qla2200.conf 11. Delete the following file:

# cp /var/opt/FJSVswsaa/backup/sd.conf.san_bak001 /kernel/drv/sd.conf

# cp /var/opt/FJSVswsaa/backup/fjpfca.conf.san_bak001 /kernel/drv/fjpfca.conf

# cp /var/opt/FJSVswsaa/backup/lpfc.conf.san_bak001 /kernel/drv/lpfc.conf

# cp /var/opt/FJSVswsaa/backup/qla2200.conf.san_bak001 /kernel/drv/qla2200.conf

12. Reboot the server. For Solaris 2.6 # touch /reconfigure

# shutdown -y -i6 -g0 For Solaris 7 or 8 # touch /reconfigure

# shutdown -y- i6 -g0

Enter the following command after the server is rebooted:

# disks -C Also, reboot the server if the following message is output to syslog and the SAN management agent cannot be started. Moreover, this message may be displayed in the environment which other SNMP demons other than Solaris EnterPrises Agent (SEA) are operating.In this case, in order to start SEA correctly, stopping the SNMP demon who is competing etc. needs to be corresponded. /var/adm/messages :

snmpdx:[ID333679daemon.error] bind() failed on UDP port161[errno: The address is already being used. (125)]

146

:

The following explains other major precautions and user actions. · Immediately after the SAN management agent is installed or reinstalled:

Confirm that the required setup operation has been completed according to chapter 5.2.2, "Setup of SAN management agent," in the Installation Guide.

· If a new HBA is added (not replaced) and the SAN management agent detects an environment error: The host may not start in the reconfiguration mode after the HBA is added. In this event, reboot the host in the reconfiguration mode.

· If a new HBA driver is installed and the SAN management agent detects an environment error: The host may not start in the reconfiguration mode after the HBA driver is installed. In this event, reboot the host in the reconfiguration mode.

8.12.1.3 Data required for troubleshooting SAN management agent

If a problem in the SAN management agent cannot be solved, collect the following information, and request a Fujitsu engineer (SE) to conduct a survey. · Date and time of problem occurrence · Version of the SAN management agent · System environment

Version of the operating system (Solaris) Type of HBA, and name and version of the HBA driver Type and version of the multi-path disk control driver (MPHD or MPLB)

· Internal information file (all generations) All files in /var/opt/FJSVswsaa/

· syslog file /var/adm/messages

· Definition file All files in /etc/snmp/conf/ /kernel/drv/sd.conf /kernel/drv/fcaw.conf /kernel/drv/fjpfca.conf /kernel/drv/lpfc.conf /kernel/drv/qla2200.conf

· Other file /core (if created) Note: When collecting files, collect files together with file permissions, such as the file permission at file creation or update (time).

8.12.1.4 Error messages of SAN management agent

For information on errors, see Appendix D, "Error Messages of SAN Management Agent (for Solaris)," in SystemWalker/StorageMGR Message.

8.12.2 SAN management agent on Windows NT/2000 server

8.12.2.1 User actions for errors in SAN management agent

This chapter explains the major errors in the SAN management agent on a Windows NT/2000 server, and the user actions for them. From the event viewer or the SAN Resource Management window, check the following errors: · Case where startup of the SNMP service fails

The SNMP service may not start immediately after the Windows NT SNMP service is installed or when the SNMP service is started for the first time. In such an event, reinstall Windows NT ServicePack after installing the SNMP service and rebooting the system. For details, see Appendix D.1.3, "Reinstalling Windows Service Pack," in SystemWalker/StorageMGR Installation Guide.

· Case where the SNMP service fails to start the SAN management agent The Storage server system setup environment or the SAN management agent environment may have been corrupted. If so, check the following points:

1. qlsdm.dll is not in C:¥winnt¥system32 Uninstall and install SystemWalker/StorageMGR-A/M.

2. The SAN management agent installation folder has been moved, or the contents have been corrupted. Uninstall and install SystemWalker/StorageMGR-A/M.

3. If the error cannot be corrected after the above steps have been taken, contact a Fujitsu engineer. · If the SAN resource management function cannot communicate with the SAN management agent: 1. Carry out the following recovery procedure if you delete by mistake all access paths under multi-path

147

control (see Chapter 8.5, "Access Path Management," in this chapter). (Only Windows 2000) · Reboot the target Windows server.

The target paths whose access paths have been deleted are then excluded from multi-path control, and the device is no longer recognized.

· If you execute "Refresh" in the SAN Management window, the monitoring status of the [HOST Property] in the Host Side View becomes normal.

· Set up again the access paths that you deleted by mistake. 2. If the SAN management agent cannot communicate when an access path is connected

If an access path is set up in the Windows 2000 environment, the SAN management agent may be unable to communicate depending on the environment. This occurs when an access path is connected at the same time that the plug-and-play function of Windows 2000 is activated, causing a temporary high load on the system. In such an event, select "Refresh (F5)" in the SAN Resource Management window again. If the SAN management agent still cannot communicate after the above action is taken, the event described in Item (3) may have occurred. See Item (3) for more information.

3. If too many devices are connected to a Windows server: If a Windows server recognizes too many devices, the SAN management agent cannot process them within the predetermined response time, causing it to be unable to communicate. In this event, review the connection configuration, and disconnect some devices from the Windows server.

As a guideline, assume that a single access path to about 100 devices can be set up per Windows NT/2000 server, although there is some variation depending on the server environment. · If the physical configuration differs from that displayed in the SAN Resource Management window: 1. If an HBA installed on a Windows NT/2000 server is not displayed in the host information in the SAN

Resource Management window: No wwpn for the newly installed HBA may have been entered in the SAN management agent settings file. Check the contents of wwpn.dat in the SAN management agent installation folder. Add a wwpn entry if required, and execute "Refresh (F5)" again. For more information on wwpn.dat, see Chapter 8.2.2, "Windows NT/2000 server."

2. If the monitoring status indicates an error occurred in an already installed Emulex HBA or the physical image is no longer displayed: Because a new HBA has been installed, the wwpn in the SAN management agent settings file may have been changed, the configuration of the HBA installed on the host may have been changed, or the logical HBA number may have been changed. Check the contents of wwpn.dat in the SAN management agent installation folder. Add a wwpn entry or modify an existing wwpn if required, and execute "Refresh (F5)" in SAN resource manager again. For more information on wwpn.dat, see Chapter 8.2.2, "Windows NT/2000 server."

3. If an access path from an Emulex HBA is no longer displayed: The registry may include an invalid topology value in the driver parameters. This occurs because the value in the registry is reset to its default at reinstallation of the driver or at installation of an HBA (such as the LP7000 or LP8000) with a different model number than the one installed in a Windows 2000 system, causing the driver to be automatically reinstalled. Use the registry editor to check the driver parameters of the target HBA. If a value is invalid, correct it and execute "Refresh (F5)." For more information on driver parameters, see Chapter 8.2.2, "Windows NT/2000 server."

· If the SAN management agent outputs an error information to the event log for another reason: Follow the instructions in Appendix E, "Error Messages of SAN Management Agent (for Windows)," in SystemWalker/StorageMGR Message.

8.12.2.2 Data required for troubleshooting SAN management agent

If a problem in the SAN management agent is not solved, collect the following information, and request a Fujitsu engineer (SE) to conduct a survey.

Information Breakdown of information Collected item Remarks

Problem example Date, time, and error contents -

OS type and version NT or Windows 2000 Service Pack version - System environment

Information on installed HBA

HBA type

Connection configuration -

148

HBA driver information Driver version Driver parameters

- (*3)

Multi-path control driver information

Presence of driver

Driver version (*4)

Windows event log System files

Application files -

Log sanalog*

sanalog_trp*

(*1,2)

(*1,2) SAN management agent information

Settings file Wwpn.dat (*1,2)

*1 When collecting files, also collect file property information such as file creation and update dates (time).

*2 The SAN management agent is installed in the folder specified when SystemWalker/StorageMGR-A/M is installed. Collect SAN management agent information from the folder.

The statuses of the SAN management agent when the default setting is specified during installation are listed below for your information.

(Note that the var¥san and etc¥san folders are moved onto shared disks in the environment set up on a cluster.)

C:¥Program Files¥Fujitsu¥StorageMGR¥

var¥san¥agent_log¥ sabkup_snmp_trap.reg : Empty file

var¥san¥agent_log¥ sabkup_fj_agent.reg : Empty file

var¥san¥agent_log¥ sanalog : SAN management agent log file

var¥san¥agent_log¥ sanalog.1 : Log file backup

var¥san¥agent_log¥ sanalog.2 : Log file backup

var¥san¥agent_log¥ sanalog_trp : SAN management agent log file

var¥san¥agent_log¥ sanalog_trp.1 : Log file backup

var¥san¥agent_log¥ sanalog_trp.2 : Log file backup

bin¥ sacom_eventlog.dll : SAN management agent DLL file 1

bin¥ sanad.dll : SAN management agent DLL file 2

etc¥san¥ wwpn.dat : SAN management agent settings file

*3 For more information on driver parameters, see Chapter 8.2.2, "Windows NT/2000 server."

*4 The multi-path control driver refers to the Fujitsu multi-path disk control feature. Check whether the multi-path control driver is installed as well as its version number.

149

Chapter 9 Space Management Operation

This chapter describes the space management operation for Windows NT/2000 systems. SystemWalker/StorageMGR manages spaces by partition. This manual refers to partitions as devices.

9.1 Overview

This chapter presents an overview of SystemWalker/StorageMGR space management.

The SystemWalker/StorageMGR space management operation obtains information about the usage of storage devices throughout the network and monitors space usage.

+[Features]

· Space management by job through the grouping of storage devices · Space management based on the operation policy for each job and for each device

+[Functions]

· Managing administrator information · Grouping storage devices · Managing policies · Centrally managing the status of the space usage · Monitoring space usage and automatically reporting space shortages · Studying and analyzing spaces · Issuing reports on space usage trends

9.1.1 Managing administrator information

SystemWalker/StorageMGR manages job managers based on authentication information provided by StorageMGR. This function ensures security for the space management function. In addition, the administrator authorization can also be managed in StorageMGR consistently.

[Figure 9.1 Managing administrator information]

9.1.2 Grouping storage devices

Multiple storage devices can be managed efficiently if they are grouped by job based on their attributes and other properties.

151

[Figure 9.2 Grouping storage devices]

9.1.3 Managing policies

Operation policies for space management can be set by job or by device. The space management operation is then performed according to the specified policy. Policies can also be set for the entire system, allowing a flexible arrangement in which spaces are managed system-wide (system policy), by job (job policy), and by device (device policy).

[Figure 9.3 Managing policies]

[Figure 9.4 Applying higher-level policies]

152

9.1.4 Centrally managing space usage

The capacity of each storage device in the storage system and the amount of space used on each device are listed and color-coded. This way, devices with problem can easily be found,like for instance,the threshold defined in the policy is exceeded.

9.1.5 Monitoring space usage and automatically reporting space shortages

When space becomes insufficient, a warning e-mail message is sent to the job manager who owns the device with the space shortage. Because SystemWalker/StorageMGR is linked to CentricMGR, the space shortage is reported to SystemWalker/CentricMGR, which then monitors space usage.

[Figure 9.5 Monitoring the space usage and automatically reporting a space shortage]

9.1.6 Studying and analyzing spaces

Conditions such as amount of space used and update dates can be used to study (search for) files on devices so that, when space has become insufficient, an investigation can be conducted and the usage status can be analyzed.

9.1.7 Space usage status trend report

Data on the space usage status can be periodically output to a report file, and transitions in the usage and use rate can be checked using graphs. As a result, items such as a transition in the space usage status can be clearly understood and efficient storage operations can be designed.

153

9.2 Operation Flow

This chapter provides an overview of the SystemWalker/StorageMGR space management operation.

9.2.1 Overview of the space management operation

The figure below shows the basic flow of space management operations.

[Figure 9.6 Overview of the space management operation]

Design and installation

Determine a layout of the storage and other devices that take actual job situations into consideration, and install StorageMGR on a server that handles space management.

Then, based on the actual job situations, use the space management GUI to register groups of the storage devices, and individual devices, and to set a space management policy.

The flow of operations using the space monitoring function in space management is described in this chapter.

The figure below illustrates the flow of operations.

9.2.1.1 Space monitoring operation

The operating flow that uses the space monitoring function is described here as part of the space management operation.

The figure below outlines the operating flow.

[Figure 9.7 Space monitoring operation ]

Monitoring

The space amount being used is monitored based on the policies set for jobs and devices.

Administrators and CentricMGR are notified if a space shortage occurs.

Study

If a space shortage occurs, use the space management GUI to check the space of the device where the space shortage occurred. Check for the cause of the space shortage.

In addition, the trend report graph can be a useful source of information on transitions in the amount of device space used. The information can serve as basis of clarification whether a plan for a disk expansion to correct such errors is necessary or not.

Action

Correct the cause of the space shortage by deleting files and/or expanding disk capacity. In addition, since disk expansion causes changes in space resources, reflect the changes to the space management definition by using the space management GUI.

154

9.2.1.2 Operation using space analysis

The flow of operations using the space information collection/analysis function in space management is described in this chapter.

The figure below illustrates the flow of operations.

[Figure 9.8 Space analysis operation]

Collection

Space information is collected based on the policies defined for jobs and devices, and a trend report is created.

Analysis

The graph is used to analyze changes in amount of space used on a device. Also, it is used in reviewing addition and allocation of disk space as well as in redesigning the storage system.

Modification

Construct the storage system again based on analysis results. In addition, using the space management GUI, reflect any system modifications to the management definitions.


The flow of space management design is described below under the following headings: · Determining jobs for the space management · Determining devices for the space management · Determining space administrators · Determining space management policies

9.3.1 Determining the space management jobs

Determine the jobs that will be managed.

In space management, because devices are grouped and managed as groups, jobs can be used to efficiently perform the space management operation. Listed below are examples of the ways jobs can be grouped: · By attribute · By purpose (actual job purpose) · By managing chapter or administrator · By physical allocation

9.3.2 Determining the space management target devices

Determine the devices to register for individual jobs. Devices operating under single or multiple servers can be registered to a job.

9.3.3 Management target devices

The following conditions apply to the target devices of space management in SystemWalker/StorageMGR: · Devices (partitions) in disk devices are physically connected to a storage server, and · Be a device that is mounted SystemWalker/StorageMGR manages each device meeting the above requirements using a unique name that is called the StorageMGR device name. See Chapter 1.6, "Managing a Device on SystemWalker/StorageMGR," for more information about StorageMGR device names.

The following devices are not managed in SystemWalker/StorageMGR: · FT disk: Volume set, striping set, mirroring set, and striping set with parity · Dynamic volume (for Windows 2000)

155

· Device with two or more mounting points (device mounted from two or more locations)

9.3.4 Target file systems

Devices that can be registered for jobs have the following file systems:

Ufs (Unix file system)

SafeFILE

· A single device cannot be registered for multiple jobs.

9.3.5 Determining space administrators

Determine the space administrators who can perform the operations of the space management function.

Space administrators must be registered using the StorageMGR authentication feature and have space management permission. See Chapter 3, "Security Operation Using Authentication Feature," for more information.

Also determine managers for each job as well

Each job manager must have an e-mail address so that the job manager can receive a warning e-mail message if a space shortage occurs.

9.3.6 Determining space management policies

Determine the policies for the space management operation.

The following items can be set in a space management policy.

[Table 9.1 Space management policy]

No. Item Value Description

1 Executing space management -

Specify whether to perform space management on target devices. Other policies cannot be set unless space management is performed.

2 Polling interval

Any one of (5, 10, 15, 20, 30) minutes or (1, 2, 3, 4, 6, 8, 12, 24) hours

Specify the polling interval for collecting space information of target devices, checking for space shortages, and collecting the system usage status log. For details, see Chapter 9.5.1, "Monitoring cycle."

3 Utilization notification level

0<ｎ<100

Warning < Error

Specify the space use rate for reporting space shortages of target devices, and display a list panel. For details, see Chapter 9.5.2, "Utilization notification level."

4 Notifying CentricMGR -

Set that CentricMGR is notified that space on the target device has become insufficient. See Chapter 9.5.4, "Insufficient space notification using CentricMGR notification," for more information.

5 Collecting the space usage status report log

- To collect the space usage status of target devices as a trend report, select this item. For details, see Chapter 9.6.1, "Report on trends."

6 Notifying the administrator -

Select this item so that if a space shortage occurs in a target device, the administrator of the job including the target device are notified of the event by mail. For details, see Chapter 9.5.3, "Notifying the administrator of space shortages by mail."

9.3.7 Policy types and application

Policies can be set for the entire system, for each job, and for each device. Determine policies for each type based on the operations performed. · System policy

This is the policy of the entire system applied to all space management. · Job policy

156

Policy for a job. A job policy applies to devices registered in a job. · Device policy

Policy for a device. A device policy applies only to a device. Policies are structured hierarchically as shown below. If a lower-level policy is not set, the higher-level policy applies.

[Figure 9.8 Hierarchy of policies]

9.4 Installation and Settings

The preparations below are required before the space management operation can start.

9.4.1 Starting daemons

Before space management is started, the SystemWalker/StorageMGR daemons on the storage management server and storage server must be started. Normally, the daemons start automatically when the system is started. However, if a daemon fails to start or a daemon is stopped, the daemon on each of the servers must be restarted. For information on starting the daemons, see Chapter 2, "Starting and Stopping a Daemons."

· In space management, the space management manager and space management agent communicate with

each other when the storage management server service and the storage server service start. At that time, if the communication partner (agent in the case of a manager, manager in the case of an agent) does not start or if a communication error occurs, the situation below occurs. Take any appropriate action that is necessary.

[Space management manager (StorageMGR GUI service of the storage management server)]

A device under the server with a space management agent that has failed to communicate becomes inactive. If the agent has not started, the device becomes active when the agent starts. When the agent has started, isolate the cause of the error, and then restart the agent.

[Space management agent (StorageMGR Spc service of the storage management server or storage server)]

If communication fails, space management does not start. Keep trying to establish communication with the manager regularly (every 60 minutes). When communication is established, space management starts. One of the following actions must be taken: · If the manager does not start, starting the manger establishes the communication with the agent, and space

management starts. · If the manager starts, isolate the cause of the error, and restart the agent if necessary. (If the agent does not

157

need to be restarted, the process is started when the retry operation is performed (every 60 minutes).)

9.4.2 Setting the access authority

Table 9.2 lists the access authorities that can be set in SystemWalker/StorageMGR.

For users registered as space management administrators, the access authority for space management must be set in advance.

For information on setting the access authority, see Chapter 3, "Security Operation Using Authentication Feature."

[Table 9.2 SystemWalker/StorageMGR access ]

Access permission Description

Update permission

Operating information (such as policy information) or a series of storage operations can be changed. Update permission includes execute permission and read permission. Only users belonging to the administrator group can set update permission.

Execute permission

Storage operations and reading are allowed. Execute permission includes read permission.

Read permission Information can only be read.

9.4.3 Starting the initial screen

Specify the following URL to start the initial screen of SystemWalker/StorageMGR.

Http://storage-management-server-address(:port-number)

The following GUI (Server List screen) appears.


Use the storage management server to register the storage servers used for management. Register the storage servers from a GUI. Select Add Server from the Operations menu. The screen shown in Figure 9.9 is then displayed.

158

[Figure 9.9 Add Server screen]

Specify the server name and IP address of the storage server to be added as well as the port number required for communication.

Specify as the port number the port number of the communication service specified when SystemWalker/StorageMGR-A was installed.

9.4.5 Obtaining information about devices operating under storage servers

To perform space management, information about devices operating under storage servers must first be saved to a repository. To fetch information about devices operating under the storage server, select Collect/Reflect Information about All Devices from the Operations menu. The screen shown in Figure Figure 9.10 is then displayed.

[Figure 9.10 Screen for collecting/reflecting information about all devices]

Confirm the server from which you want to get device information, and then click the OK button.

Get device information from individual servers. The dialog box shown in Figure 9.11 is then displayed.

159

[Figure 9.11 Device information confirmation screen]

The top list box is displayed when a new device is detected. Move the device that will be managed to the list box on the left. The middle list box lists any devices already being managed that cannot be detected this time. To stop management of a device, move the device to the list box on the right. The bottom list box lists devices whose device information has been updated (for example, a device whose mount point name has been changed).

The device name shown here is the StorageMGR device name.

After performing the above operation, click the OK button to update the configuration information.

9.4.6 Displaying the Space Management screen

To display the usage status list of space management, select [Space Management] from the [File] menu on the Server List screen.

160

[Figure 9.12 SystemWalker/StorageMGR (Space Management) screen]

9.4.7 Setting the mail server

Set the mail server (SMTP server) that will be used to automatically send e-mail messages if space becomes insufficient.

Set the mail server (SMTP server) to automatically send mail if a space shortage occurs. From the Space Management screen displayed from the StorageMGR Basic screen, display the Mail Server Settings screen. For information on setting the mail server, see Chapter 5.3.1, "SMTP Server Settings screen," in the SystemWalker/StorageMGR User's Guide.

[Figure 9.13 Mail Server Setting screen]

If the mail server is not set up, e-mail messages cannot be sent to an administrator. This setting must be made to use the function that sends e-mail messages to the administrator.

9.4.8 Registering an administrator

Register the administrators of space management jobs. The registered administrators are then notified if a space shortage occurs.

9.4.8.1 Registering a privileged user (mail send administrator)

During the initial setup, register the priviledged user of SystemWalker/StorageMGR, the startup account specified at SystemWalker/StorageMGR-installation. The said user will serve as the administrator of space management business as well as the mail send administrator.

All mail messages sent by space management are sent from this mail send administrator (privileged user) account.

161

· Other users cannot be registered unless a mail send administrator (privileged user) has been registered. · The mail send administrator (privileged user) cannot be deleted. And it cannot be changed.

9.4.8.2 Registering a space administrator

Select and register a space management administrator from the users for which space management authority is set by using the approval function of StorageMGR.

For information on specifying an administrator, see Chapter 5.3.2, "Space Administrator Settings screen," in the SystemWalker/StorageMGR User's Guide.

[Figure 9.14 Administrator Settings screen]

9.4.8.3 Administrator confirmation mail

When an administrator is registered or deleted, confirmation mail is sent to the registered mail address from the administrator (privileged user) registered during initial setup. a. Administrator registration notification mail

Title: [StorageMGR/space management] Administrator registration notification

From: Administrator mail address ... Mail send administrator (StorageMGR privileged user)

To: Administrator mail address ... Defined administrator

Message:

The user was defined as a StorageMGR/space management administrator. b. Administrator deletion notification mail

Title: [StorageMGR/space management] Administrator deletion notification

From: Administrator mail address ... Mail send administrator (StorageMGR privileged user)

To: Administrator mail address ... Defined administrator

Message:

The user was deleted as a StorageMGR/space management administrator.

If the administrator settings have not been made, no jobs can be registered. These settings are required.

162

9.4.9 Setting system-wide policies

Set policies that apply to the entire system that is subject to space management. · System policy is the initial value for setting a job policy. · System policy applies as the policy of a job for which no job policy has been set. See Chapter 9.3.6, "Determining space management policies," for more information about space management policies.

[Figure 9.15 System Policy Setting ]

See Chapter 5.5.1, "Setting system policy," in the SystemWalker/Storage MGR User's Guide for information about how to set a system policy.

9.4.10 Setting Jobs

Specify the jobs used in space management. Specify the jobs as explained below. · Registration of the job · Registration of the device · Setting of a job policy

9.4.10.1 Registering a job

Create the jobs used in space management. In space management, a job indicates a unit for grouping devices based on purpose of use and other conditions. A policy can be set for each job, and a job list can be displayed. For information on registering jobs, see Chapter 5.3.3.1, "Registering jobs," in the SystemWalker/StorageMGR User's Guide.

9.4.10.2 Registering devices

In the job, register a device whose space will be managed. Registering a device in a job indicates that the space for the device is to be managed. See Chapter 5.3.3.1, "Registering jobs," in the SystemWalker/StorageMGR User's Guide for more information about registering devices.

163

[Figure 9.16 Registering Job/Registering Devices ]

9.4.10.3 Setting job policies

Set a job policy (job policy) for each job registered for space management. If a job policy is not set for a job, a high-order policy (system policy) applies to the job. In such cases, if the high-order policy is changed, the change is reflected in the policy of the job.

The job policy is used as the set of initial values when the policy of a registered device is set.

If a device policy is not set for a device, the policy of the job to which the device is registered is applied.

For information on setting job policies, see Chapter 5.3.4.2, "Registering job policies," in the SystemWalker/StorageMGR User's Guide.

For the contents of space management policies, see Chapter 9.3.6, "Determining space management policies."

164

[Figure 9.17 Job Policy Registration screen]

9.4.11 Setting Devices

Specify the devices registered to jobs. Specify the devices as explained below.

9.4.11.1 Setting device policies

Set a policy for each device. Each device policy is valid only for a specific device.

If a device policy is not set for a device, a high-order policy (job policy) applies to the device.

For information on setting device policies, see Chapter 5.3.4.4, "Registering device policies," in the SystemWalker/StorageMGR User's Guide.

For the contents of space management policies, see Chapter 9.3.6, "Determining space management policies."

9.5 Space Monitoring

+Performing space monitoring

To perform space monitoring, register a device (mount point) as a monitoring target for a job.

For target devices of space management, information is collected at every specified polling interval, and the device space is monitored depending on the individual policies of the monitored devices.

For information on registering jobs, see Chapter 9.4.10, "Setting jobs."

To perform space monitoring of a device, the [Perform Space Monitoring] checkbox in the policy settings of the device must have a check.

9.5.1 Monitoring cycle

Specify the polling interval for collecting space information of target devices, checking for space shortages, and collecting the system usage status log.

If minutes is selected as the polling interval for space management, polling starts at the beginning of every hour. If hours is selected, polling starts at midnight of each day.

Any one of the values of 5, 10, 15, 20, or 30 minutes or 1, 2, 3, 4, 6, 8, 12, or 24 hours can be selected. The system policy default is 1 hour.

For example, if every 20 minutes is specified, a space is monitored at 0:00, 0:20, 0:40, 1:00, 1:20, and so on. If every two hours is specified, a space is monitored at 0:00, 2:00, 4:00, 6:00, 8:00, and so on.

You can change the monitoring cycle by setting each policy.

165

Immediately after a target device is registered for a job, space information is collected regardless of the polling interval. A space shortage check is performed and the space usage status log is collected starting from the next polling interval.

9.5.2 Utilization notification level The use rate notification level represents the amount of use of managed devices as a percentage. If the level is exceeded, this is notified of (CentricMGR) by mail and the contents of a list panel are changed. The following two types of standard percentages can be specified:

Alarm: Administrators are notified of any alarm-level space shortages. The applicable device and the job to which the device belongs are displayed in red in the Job or Device List panel. (The default value is 90%.)

"Warning": Administrators are notified of any attention-level space shortages. The applicable device and the job to which the device belongs are displayed in yellow in the Job or Device List panel. In addition, CentricMGR is notified if the [Notify CentricMGR] checkbox has a check in policy settings. (The default value is 80%.)

9.5.3 Notifying administrators of space shortages by mail

If usage exceeds the use rate notification level specified for a policy, the administrator registered for the associated job is notified of a space shortage by mail.

In order for space shortages to be reported, the [Notify Administrator] checkbox must have a check in policy settings.

A message is sent when the warning value of the utilization notification level is exceeded, and another message is sent when the error value is exceeded. Thereafter, each time that the amount of remaining available space drops below the utilization notification level or exceeds the warning level or the error level, a message is sent.

Also, when the space utilization of a device whose lack of space has already been reported drops below the warning level of the utilization notification level in the policy, a message indicating that the space is sufficient is sent.

9.5.3.1 Contents of notification messages

+Insufficient space message

· Space shortage (error) occurrence notification mail Title: [StorageMGR/space management] Space shortage (error) occurrence notification From: Administrator mail address ... Mail send administrator (StorageMGR privileged user) To: Administrator mail address ... Administrator of the device where the space shortage (error) occurred. Message: Space shortage (error) occurred. Job name: xxxx ... Job name of the device where the space shortage occurred. Server name: xxxx ... Server name of the device where the space shortage occurred. Device name: xxxx Current amount of space used (%): nn ... Name and space use rate of the device where the space shortage occurred. Space policy: Notification level alarm (%) nn ... Space policy value

· Insufficient space (warning) notification message Title: [StorageMGR/space management] Space shortage (warning) occurrence notification From: Administrator mail address ... Mail send administrator (StorageMGR privileged user) To: Administrator mail address ... Administrator of the device where the space shortage (warning) occurred. Message: Space shortage (warning) occurred. Job name: xxxx ... Job name of the device where the space shortage occurred. Server name: xxxx ... Server name of the device where the space shortage occurred. Device name: xxxx Current amount of space used (%): nn ... Name and space use rate of the device where the space shortage occurred. Space policy: Notification level warning (%) nn ... Space policy value

+Space shortage recovery mail Title: [StorageMGR/space management] Space shortage recovery notification

166

From: Administrator mail address ... Mail send administrator (StorageMGR privileged

user)

To: Administrator mail address ... Administrator of the device recovered from a space

shortage.

Message:

Space shortage recovery was completed.

Job name: xxxx ... Job name of the device recovered from a space shortage.

Server name: xxxx ... Server name of the device recovered from a space shortage.

Device name: xxxx ... Current amount of space used (%): nn

... Name and space use rate of device recovered from a space shortage.

Space policy: Notification level warning (%) nn... Space policy value

9.5.4 Reporting space shortages in CentricMGR notification

In CentricMGR notification, if the space use rate of a target device of space management exceeds the attention value specified as the use rate notification level, SystemWalker/CentricMGR is notified of a space shortage as a warning.

In this event, once the space use rate drops below the attention value specified as the use rate notification level, SystemWalker/CentricMGR is notified of the recovery. Only the attention value specified as the use rate notification level is valid for this SystemWalker/CentricMGR notification operation. (The alarm value is not checked.)

In order for space shortages to be reported, the [Notify CentricMGR] checkbox must have a check in policy settings.

In CentricMGR notification, the message shown below is posted as an event notification. For details about CentricMGR linkage, see Chapter 9.10, "SystemWalker/CentricMGR Linkage."

[Message]

[StorageMGR/Space Management] Insufficient space occurred. device name: %s

[Parameter]

%s: Name of the device where the space shortage occurred.

[Meaning of message]

The space use rate exceeded the threshold value specified in the applicable policy.

· In order for CentricMGR to be notified, SystemWalker/CentricMGR must be installed. · In space management, SystemWalker/CentricMGR notification depends on the warning level.

9.5.5 Usage Status List screen (Space Management screen)

The status of devices subject to space management can be checked from the Space Management screen.

The Space Management screen has a space management tree on the left side and different list screens on the right side.

167

[Figure 9.18 Space Management screen]

9.5.6 Job List screen (displayed at space management icon selection)

When a space management icon is selected, job information is displayed in a list screen (Job List screen) on the right.

When the space management icon is selected, registered job icons are displayed in Tree View, and information on the jobs is displayed in the list box (Job List screen).

[Figure 9.19 Job List Management screen]

9.5.7 Mount Point List screen (displayed at job icon selection)

When a job icon is selected using the space management tree on the left, mount point information (Mount Point List screen) registered for the job is displayed in a list screen on the right.

168

[Figure 9.20 Mount Point List screen]

9.5.8 Displaying the status on list screens

On the Job List screen and Mount Point List screen, the status of a job and the mount point is indicated as shown below.

[Table 9.3 Displaying the status on list screens]

Screen Status Description

Red At the mount point in a job, space becomes insufficient at the error level.

Job List screen Yellow At the mount point in a job, space becomes insufficient at the warning

level.

Red At the mount point in a job, space becomes insufficient at the error level.

Yellow At the mount point in a job, space becomes insufficient at the warning level.

Mount Point List screen

Gray The mount point is disabled.(*1)

*1 "Disabled" states are as follows: · The mount point state has been changed. (The device has been unmounted or changed.) · Collection of mount point information failed. · Communication with a server failed. Check the mount point state and error information of the relevant storage management server or storage server, and take appropriate action. For details about the error information, refer to the SystemWalker/StorageMGR Messages.

9.5.9 Checking spaces

To display the screen shown in Figure 9.21, select a mount point from the Mount Point List panel of the Space Management screen, and then select Check Space from the Operations menu.

To list files that match a specific condition, specify the search condition, and then select [Search].

169

[Figure 9.21 Examine Space screen]

[Table 9.4 Items to be input for examining ]

No. Item name Selection Value Description

1 Last update

Check box - Check this checkbox to use the latest update day

as a search condition.

2 Last update

Combo box

Select one from the following: 1 day 2 days Within 1 week Within 1 month Within 3 months 3 months ago or earlier 6 months ago or earlier One year ago or earlier Two years ago or earlier

Specify the file update date used as standard in searches. The default value is "within the last month." Unless the date is changed, the current update date is inherited.

One month is defined as 30 days.

3 Size Check box - Check this checkbox to use file size as a search

condition.

4 Size Input Setting range: maximum value between 0 and long

Enter a file size as a search condition.

The default is 512 MB.

5 Number of view items Spin box Setting range: 1 to

999 Specify a search count. The default is 10.

170

9.6 Analyzing Spaces

9.6.1 Report on trends

If "Obtain space usage status log data" is selected in a policy, the space usage data for each mount point collected during each space monitoring cycle is as a report on trends, and the changes in space usage status are presented in graph form.

Analysis of the space usage status allows more efficient storage systems to be designed.

9.6.2 Trend report graphs

A report on trends for a mount point and a job selected on the Space Management screen can be displayed as a graph.

[Figure 9.24 Trend report graph]

9.6.3 Trend report files

A report on trends is created as a CSV format file. The items listed below are the details of the CSV files that are created. · Output unit

A file is created for each device. · Output period

The file is switched every month. · Output directory

The following storage management server directory: working-directory/var/space/report

· CSV file name server-ip-address_mountpoint-name##start-time-and-date.csv [server-ip-address] : IP address of a server where a device is connected [mountpoint] : Mount point of a device [start-time-and-date]: Date and time when the trend data placed at the beginning of the file is collected The "##start date and time" is not added to the name of the latest trend report file. The "##start date and time" is added to the file name when the output interval is switched (monthly). In addition, the conversions are performed according to the following naming conventions:

- "." in an IP address is converted to "_". - Separators for mount points (such as "/," and "¥") are converted to XX. - If the mount point name is "/",it is replaced by "root". · CSV data

171

First line : Job name, server name, device name, and mount point name Subsequent lines: Time and date the data was collected, total capacity, and total amount of space used [Example]

- Device name : /dev/dsk/c0t1d0s0 - Job name: Job A - Server name (address) : solServer(172.23.77.23) - Mount point: /opt/data

Latest CSV file name : 172_23_77_23_opt__data__data.csv Old CSV file name : 172_23_77_23_opt__data__20010901120000.csv (data from 12:00:00 of Sep.01,2001) CSV data (within the latest CSV file above) : Job A,solServer,/dev/dsk/c0t1d0s0,/opt/data 20011001130000,231758932,39872639 20011001114000,231758932,39872650 20011001115000,231758932,39872739

· The unit for total capacity and total amount of space used is blocks (one block is 512 bytes).

9.6.3.1 Deleting trend report files

When necessary, delete trend reports that are no longer needed.

The deletion of unnecessary periods and data on devices saves disk space on the space management server.

Since a trend report file is switched every month, files can be deleted by month.

The maximum amount of data necessary for one month for a device in a trend report is as follows:

Base amount (1084) + Data to be acquired in each monitoring cycle (34) x Number of times monitoring executed (288) x 31

= (nearly) 300 KByte

· When deleting the latest CSV file, first stop the output of the trend report for the device. See Chapter 5.3.4,

"Setting screen for policies," in the SystemWalker/StorageMGR User's Guide for more information on the output settings for a trend report.

9.6.3.2 Using trend report files

To use trend report data, the user must copy the trend report file (CSV) before using the data.

· When copying the latest CSV file, first stop the output of the trend report file for the device. See Chapter 5.3.4,

"Setting screen for policies," in the SystemWalker/StorageMGR User's Guide for more information about the output settings for a trend report.

9.7 Operating Information

Because the space management daemon and space monitoring are automatically started and stopped, check the operating status as necessary..

Operating information of the space management daemon is output to Syslog.

9.8 Changing Setting Information

When any changes are made to the storage server or devices subject to the space management operation, the setting information of SystemWalker/StorageMGR must be changed. This Chapter describes how to change the setting information after changes have been made.

9.8.1 Changing server information

The following procedure describes how to addition/deletion of a storage management server or a storage server:

172

9.8.1.1 Adding a storage server

The following procedure describes how to add a new storage server for which space management is performed: 1. Display the initial screen. See Chapter 9.4.3, "Starting the initial screen," for more information. 2. Register the storage server. See Chapter 9.4.4, "Registering a storage server," for more information. 3. Acquire the information about all the devices connected to the added storage server. See Chapter 9.4.5,

"Obtaining information about a devices operating under storage servers," for more information. 4. Display the Space Management screen. See Chapter 9.4.6, "Displaying the Space Management screen," for

more information. 5. Register the device about which information was acquired in a job. Alternatively, create a new job, and register

the device in it. See Chapter 9.4.10, "Setting Jobs," for more information. 6. If necessary, set a policy for the job or device. See Chapter 9.3.6, "Determining space management policies,"

for more information.

9.8.1.2 Deleting a storage server

The following procedure describes how to delete a storage server subject to space management. This procedure must be executed before physically removing the storage server that is being deleted. 1. Display the Space Management screen. See Chapter 9.4.6, "Displaying the Space Management screen," for

more information. 2. From the job, delete the target device of deletion operating under the storage server. For details, see Chapter

5.3.3.2, "Updating jobs," in the SystemWalker/StorageMGR User's Guide. 3. Display the initial screen. See Chapter 9.4.3, "Starting the initial screen," for more information. 4. Delete the storage server. See Chapter 1.2.6, "Deleting servers," in the SystemWalker/StorageMGR User's

Guide for more information about deleting a storage server.

9.8.2 Changing devices

If a device has been added to or deleted from any storage server, or if the device state has been changed, follow the procedure below to reflect the modification to SystemWalker/StorageMGR space management operations.

9.8.2.1 Adding a device

1. Display the initial screen. See Chapter 9.4.3, "Starting the initial screen," for more information. 2. For the storage server to which a device has been added, acquire all device information. When the device

information is acquired, the newly added device is detected. Move the device to the [Device specified for addition] Chapter. See Chapter 9.4.5, "Obtaining information about devices under storage servers," for more information.

3. Display the Space Management screen. See Chapter 9.4.6, "Displaying the Space Management screen," for more information.

4. Register the acquired device in the job. Alternatively, create a new job and register the device in it. See Chapter 9.4.10, "Setting Jobs," for more information.

5. If necessary, set a policy for the job or device. See Chapter 9.3.6, "Determining space management policies," for more information.

9.8.2.2 Device update

Under the following states of space management, update the devices. For other configuration modifications (see Chapter 10.5.7, "Changing the device configuration"), delete and add the devices.

Capacity change of a partition (mainly re-creation of LUN mapping)

Start position change of a partition (mainly re-creation of LUN mapping) 1. Display the initial screen. For details, see Chapter 9.4.3, "Displaying the initial screen." 2. Acquire and/or reflect updated information on specific devices. For an explanation on capturing device

information, see Chapter 1.2.7.2, "Acquiring/reflecting information on specific devices," in the SystemWalker/StorageMGR User's Guide.

9.8.2.3 Deleting a device

The procedure below describes how to delete a device. This procedure must be executed before physically removing the device that is being deleted. 1. Display the Space Management screen. See Chapter 9.4.6, "Displaying the Space Management screen," for

more information. 2. Delete the device operating under the target storage server from the job. For details, see Chapter 5.3.3.2,

"Updating jobs," in the SystemWalker/StorageMGR User's Guide. 3. Display the initial screen. See Chapter 9.4.3, "Starting the initial screen," for more information. 4. See Chapter 1.2.9, "Deleting device information," in the SystemWalker/StorageMGR User's Guide for more

information about deleting the acquired device.

173

9.9 Stopping Operation

To stop space management, stop the daemons on the storage server. Normally, the daemons stop automatically when the system stops.

However, to stop daemons at another time, the daemons can be stopped individually. For information on stopping the daemons, see Chapter 2, "Starting and Stopping a Daemons."

When stopping a service on the storage management server, make sure that all the operations on the storage server that are being managed are stopped before stopping the service on the storage management server.

9.10 SystemWalker/CentricMGR Linkage

Linking with SystemWalker/CentricMGR enables centralized monitoring by SystemWalker/CentricMGR of a server for which a space shortage occurs. In addition, the checking after a space shortage occurrence can be done smoothly by using the screen linkage.

9.10.1 Function for linkage with SystemWalker/CentricMGR

+Centralized monitoring

The icons of servers subject to space management are displayed on each monitoring screen (System Monitoring, Job Monitoring, and Web Console screens) of a SystemWalker/CentricMGR operation management client. If a space shortage is detected in a disk device operating under a server registered for space management jobs, an alarm is posted on the screen. SystemWalker/CentricMGR can uniformly monitor for space shortages in disk devices. Moreover, the e-mail and beeper functions of SystemWalker/CentricMGR can be used to monitor for space shortages in disk devices, even from remote locations.

In CentricMGR, an [ X ] is displayed as the server icon of a disk device where a space shortage has occurred. Error contents are also displayed for the event. Once the cause of space shortage of the disk device is corrected, the [ X ] is automatically cleared and handling of the space shortage event is completed.

+Screen linkage

On each monitoring screen (System Monitoring and Job Monitoring screens) of SystemWalker/CentricMGR, select StorageMGR from the pop-up menu displayed for the node of the server where the error occurred in order to start the Web screen of SystemWalker/StorageMGR. As a result, the checking after an error occurs can be done smoothly.

9.10.2 Procedure of setting up SystemWalker/CentricMGR linkage

Follow the procedure below to set up CentricMGR linkage.

If CentricMGR linkage setup has already been completed in the SAN management operation procedure, the procedure given in Chapter 9.10.2.1, "Operation management server setup procedure," is not necessary.

In this event, start from the procedure in Chapter 9.10.2.2, "Operation management client setup procedure."

Follow the procedure below for the SystemWalker/CentricMGR operation management server and operation management clients. On the operation management server, log in as a root user. On an operation management client, log in with a user name belonging to the local administrators group.

174

9.10.2.1 Operation management server setup procedure

1. Start SystemWalker/CentricMGR on a SystemWalker/CentricMGR operation management server. 2. Execute the setup command of the operation management server.

Insert the SystemWalker/StorageMGR-M CD-ROM for operation management servers, and then execute the setup command of operation management servers. The method of executing the setup command is as follows:

3. Restart SystemWalker/CentricMGR on the operation management server. - The MIB information file of CentricMGR cannot be set correctly if it has been set independently. In this

event, do the following: 1. Back up the mpnmkind50.ini.05 file. 2. Rename the mpnmkind50.ini file as mpnmkind50.ini.05. 3. Execute the manset.bat module again.

9.10.2.2 Operation management client setup procedure

1. Execute the operation management client setup command.

For all operation management clients of SystemWalker/CentricMGR, insert the CD-ROM of SystemWalker/StorageMGR-M, and then execute the setup command for an operation management client. The method of executing the setup command is as follows:

2. Search for the relevant node in a subnet of a storage server of an operation management client. 3. Using the pop-up menu displayed for the node, register the Web screen of SystemWalker/StorageMGR.

Execute the mpaplreg command of SystemWalker/CentricMGR to register the Web screen of SystemWalker/StorageMGR on the pop-up menu of the node of the storage server. Refer to the menuset.bat file in the CD-ROM drive name¥pc¥win32¥centric, and add the Web screen to the pop-up menu of the node of the storage server as shown in the example below. For information about changing menuset.sh, see Chapter 11.4.6, "SystemWalker/CentricMGR screen linkage command (mpaplreg)."

175

· Perform these operations every time a storage server is added. · If the IP address of the SystemWalker/StorageMGR management server is changed, execute the following

command to delete the registered menu, and then register it again:

9.10.2.3 Notes on SystemWalker/CentricMGR and linkage

Note the following points if the SystemWalker/CentricMGR operation management server and SystemWalker/StorageMGR management server operate on different server machines.

· SystemWalker/CentricMGR cannot be linked unless the environments of the SystemWalker/CentricMGR

operation management server and SystemWalker/StorageMGR management server are managed using the same DNS server or unless each /etc/hosts has the same definitions. This is because node names cannot otherwise be correctly detected.

· The SystemWalker/CentricMGR agent must be installed on the SystemWalker/StorageMGR management server.

9.10.3 Required versions for SystemWalker/CentricMGR linkage

Take the following notes into consideration if the SystemWalker/CentricMGR operation management server and SystemWalker/StorageMGR management server are located on different servers. · Solaris SystemWalker/CentricMGR GEE 5.0 · Solaris SystemWalker/CentricMGR-M EE/SE 5.0,5.1,5.2,10.0

176

Chapter 10 Operation Maintenance

This chapter describes maintaining a database, performing troubleshooting, and changing the operation information.

10.1 Maintaining a Database

SystemWalker/StorageMGR stores various repositories with operation information. You are recommended to periodically back up repositories in preparation for unexpected accidents.

The following table lists instances when the acquisition timing is needed.

Server type Type Acquisition timing and method

Storage server Backup management list

After backup is completed

Resource backup command

Storage server Replication management list

After replication is completed

Resource backup command

Storage management server Database

When configuration information is changed due to, for example, addition of a storage server or fetching of device information, or when operation information for replication management is changed

Saving a database

Storage management server

SAN resource management repository

When SAN configuration settings are changed due to, for example, addition of a device or setting of zoning for execution of SAN management

Backing up a CIM database


Authentication management list

After authentication is set

Shell script for outputting definition information

Storage management sever/storage server

Registry

When a storage server is added or the server information (server name, IP address, or port number) on the storage management server is changed

Backing up a registry

10.1.1 Maintaining a backup a management list

This chapter describes maintenance of a backup management list. A backup management list is maintained on the server that performs the backup operation.

10.1.1.1 Backing up a backup management list and a recovery control file

Back up the backup management list and recovery control file that were created when the SymfoWARE database space was backed up.

For more information, see chapter 11.1.3.2, "Resource backup command (swstresback)."

10.1.1.2 Restoring a backup management list and recovery control file

Restore the backup management list and recovery control file that were created when the SymfoWARE database space was backed up.

For more information, see chapter 11.1.3.3, "Resource restore command (swstresrst)."

10.1.2 Maintaining a replication management list

This chapter describes maintenance of a replication management list.

10.1.2.1 Backing up a replication management list

To back up a replication management list, back up the repository of the storage management server. For information about backing up a repository, see chapter 10.1.3.1, "Database save command (saving a database)."

177

· Operation information for replication management is saved in a repository. · It is recommended that a replication management list be backed up when operation information for replication

management is changed with the replication volume information setting command (swsrpsetvol) or the replication volume information deletion command (swsrpdelvol).

10.1.2.2 Restoring a replication management list

Take the following steps to restore a replication management list. 1. Restore the repository on the storage management server. For information about restoring a repository, see

chapter 10.1.3.3, "Database recovery command (recovering a database)." 2. On the storage server, execute the resource adjustment command (swsrprecoverres) with the r option

specified. For details of the resource adjustment command, see chapter 11.3.3.1, "Resource match command."

· When the procedure above is performed, operation information for replication management of a repository is

copied to a storage server, where it is available for use. · When the operation information for replication management in the repository does not need to be changed and

only the operation information for replication management on the storage server is incorrect for some reason, perform the procedure above.

10.1.3 Maintaining a database

This chapter describes maintaining a database used by a storage management server.

10.1.3.1 Saving a database

Execute the database save command to save a database space.

Execute this command on the Storage management server.

· To execute the database save command, log in as a root user. · Processing may not end normally if a window operation is used or another command is executed while this

executed command is being processed. In this event, retry processing after waiting for a short period of time. · If no data is saved by this command, the respective database cannot be recovered with the database recovery

method if an error such as an input-output error occurs in the database space. a. Specification

# /opt/swstorage/bin/stgdbdmp -d Backup-Directory [ -y ] b. Explanation of options

Option Explanation

-d Specify the name of the directory in which to save a database space.

This directory must be created in advance.

-y

If saved contents remain in the specified directory, they are overwritten when the database space is saved.

If this option is omitted and saved contents remain in the specified directory, processing ends without saving the database space.

c. End status = 0: Normal en > 0: Abnormal termination

d. Execution example # /opt/FJSVswstf/setup/stgdbdmp -d /storage/dmpdir -y ///// SystemWalker/StorageMGR database save ///// ================================================================== DB data will be saved.

178

================================================================== Editing of the work file used for save processing is complete. . Update of the DB space is suppressed. Forced switching of archive log files is complete. ....................................... Save processing of DSI data is complete. Archive log files have been completely discarded. Save processing of RDB dictionary data is complete. Suppression of DB space updates has been completely canceled. ================================================================== Save processing of DB data is complete. ================================================================== Database save processing ended normally. #

· Use this save method only when configuration information is changed due to an addition of a storage server or

fetching of device information. You are recommended to periodically save a database, for example, once a day.

· To prepare for an input-output error in an external file while save data is being acquired, you are recommended to keep at least two generations of save data.

10.1.3.2 Finding an error in a database

Refer to the /var/opt/FJSVswstf/log/RDBSWSTF.log file, and beginning from the last line, search for any message with "rdb: ERROR: qdgXXXXX-" in its contents (also check the messages output at the same time). Then, obtain the value of "qdgXXXXX" to determine the recovery mode.

Table10.1 Relationships between the qdg message and recovery mode

qdg message

Description of error Target of checking Recovery

mode

qdg13039u Input-output error or detected damage

Raw device for storing data of a DB space in a repository

qdg03400u

qdg03401u Rollback disabled -

1

qdg13040u Input-output error or detected damage

qdg03121u Input-output error

Raw device for the RDB dictionary

qdg03420u Input-output error, detected damage, etc.

/SWSTFDB/rdbdir/DIR_FILE1

/SWSTFDB/rdbdir/DIR_FILE2

2

qdg12251e

qdg12443u Input-output error

qdg12434u File error

/SWSTFDB/rdbdir/rdblogmanage 3

qdg12111u

qdg12440u

qdg12441u

qdg12442u

Input-output error Raw device for RDB log files 4

qdg03815u

qdg12275W System call error

/SWSTFDB/rdbdir/archive1

/SWSTFDB/rdbdir/archive2

5

179

qdg12250u Damage detection

qdg12483u File read error

· If multiple errors occur simultaneously, recovery using recovery modes 1 to 5 may not be possible. To restore a

database to its state when it was last saved, re-create the database and execute the database save command in recovery mode 0. (Data reflected after the last time the database was saved cannot be recovered.)

· At this point, execute the resource adjustment command (see chapter 11.1.3.1, "Resource match command") with option -x on all the storage servers on which the backup operation is performed.

10.1.3.3 Recovering a database

Execute the database recovery command for database recovery if an input-output error occurs in a database space.

Execute this command on the Storage management server.

To execute the database recovery command, log in as a root user.

· After the database recovery command ends normally, acquire the latest save data using the database save

method. Fujitsu recommends using a different save data storage directory than the save data storage directory used by the recovery command.

· After the database recovery command ends normally, restart (start after stopping) the StorageMGR daemons. For an explanation on restarting the daemons, see chapter 11.5.8, "Starting and stopping the StorageMGR daemons," and Chapter 2, "Starting and Stopping Daemons."

a. Specification # /opt/swstorage/bin/stgdbrcv -m mode [-d Backup-Directory]

b. Explanation of options Option Explanation

-m

Specify a recovery mode based on the type of error that occurred in a database space.

For the relationship between types of errors and recovery modes, see Table 10.1.

-d Specify the name of the directory storing the saved data.

This option is required if 0, 1, 2, or 4 is specified in the -m option. c. End status

= 0: Normal end > 0: Abnormal termination

d. Execution example # /opt/FJSVswstf/setup/stgdbrcv -m 1 -d /storage/dmpdir ///// SystemWalker/StorageMGR database recovery ///// ================================================================== DSI recovery (FW mode) will start. ================================================================== Editing of the work file used for recovery is complete. DSI access inhibition is complete. ....................................... DSI data recovery is complete. ================================================================== DSI recovery (FW mode) is complete. ================================================================== Database recovery ended normally.

180

#

10.1.4 Maintaining a SAN resource management repository

The following chapter explains how to maintain the CIMOM repository used in the SAN resource management of StorageMGR EE.

10.1.4.1 Saving a database

The CIM database is saved in the following directory:

/var/opt/FJSVswsam/opencimom/logr

Backup copies can be created by copying the contents of this directory. 1. Stop CIMOM.

Enter the following command to stop CIMOM: # /opt/FJSVswsam/bin/cimserver stop

2. Create backup copies. Enter the following command to copy the CIM database to save location 1: # cp -Rp /var/opt/FJSVswsam/opencimom/logr/* Save location 1 To also create backup copies of the environment settings file (including such settings as that for icon location) for the SAN window, copy the following files to save location 2: # cp /etc/opt/FJSVswsag/san/gui/SANGui_<user name>.cfg Save location 2 # cp /etc/opt/FJSVswsag/san/gui/dispmode_<user name>.dat Save location 2 # cp /etc/opt/FJSVswsag/san/gui/point_<user name>.dat Save location 2

3. Restart CIMOM. Enter the following command to restart CIMOM: # /opt/FJSVswsam/bin/cimserver start Notice: CIMOM stops if the console used to start CIMOM is quitted. To prevent this event from occurring, start CIMOM from the console used to start /usr/bin/csh.

10.1.4.2 Restoring a database

Restore the data that has been backed up. 1. Stop CIMOM.

Enter the following command to stop CIMOM: # /opt/FJSVswsam/bin/cimserver stop

2. Restore the data that has been backed up. Enter the following command to copy the data at the save location into the database storage location: # cp -Rp save location 1/* /var/opt/FJSVswsam/opencimom/logr Also, copy the window environment settings file by entering the following commands: # cp save location 2/SANGui_<user name>.cfg /etc/opt/FJSVswsag/san/gui # cp save location 2/dispmode_<user name>.dat /etc/opt/FJSVswsag/san/gui # cp save location 2/point_<user name>.dat /etc/opt/FJSVswsag/san/gui

3. Restart CIMOM. Enter the following command to restart CIMOM: # /opt/FJSVswsam/bin/cimserver start Notice: CIMOM stops if the console used to start CIMOM is quitted. To prevent this event from occurring, start CIMOM from the console used to start /usr/bin/csh.

10.1.5 Maintaining authentication management list

This chapter describes maintenance of the authentication feature. Execute the command on the server (storage server) where the authentication feature is implemented.

10.1.5.1 Backing up an authentication management list

On a storage management server, execute the /opt/FJSVswssc/bin/smmkbat command to extract authentication management information. The root user must execute this command.

Smmkbat -f definition-information-output-shell-script-name Example : smmkbat -f acldata.bat

The definition information output shell script is extracted as a shell script in which the command example for reflecting definition information is described.

10.1.5.2 Restoring an authentication management list

Execute the definition information output shell script. The root user must execute the script.

181

10.1.6 Maintaining a registry

This chapter describes maintaining a registry. Perform this procedure on a storage management server or a storage server.

10.1.6.1 Backing up a registry

Back up the following file by executing the cp command. a. File names

/etc/opt/swstorage/swnode.ini b. Execution example

Save it in the /backup directory. # cp /etc/opt/swstorage/swnode.ini /backup

10.1.6.2 Restoring a registry

Restore the following file by executing the cp command: a. File names

/etc/opt/swstorage/swnode.ini b. Execution example

Restore the following file saved in the /backup directory: # cp /backup/swnode.ini /etc/opt/swstorage

10.2 Troubleshooting

10.2.1 Troubleshooting for insufficient free space in a repository

This chapter describes what to do if there is insufficient free space in a repository used by a storage management server.

Perform this procedure on a storage management server.

You can use this troubleshooting method when there is insufficient free space in a repository and if the operation status is significantly different from the initial installation time to prevent the occurrence of insufficient free space in the repository.

Extend the repository space as follows: 1. Stored data save processing (see chapter 10.2.1.1, "Database backup") 2. Releasing a repository (See chapter 6.1.2.4, "Database unsetup," of the Installation Guide.) 3. Re-estimating the database size (see chapter 4.3.1, "Estimating the database space," of the Installation

Guide). 4. Re-creating partitions (See chapter 4.3.2, "Creating partitions," of the Installation Guide.) 5. Creating a repository (See chapter 4.3.4, "Database setup," of the Installation Guide.) 6. Save data restore processing (see chapter 10.2.1.2, "Database restoration")

10.2.1.1 Database backup

This chapter describes saving data stored in a database to the specified directory collectively.

This method is mainly used for converting data. To save normal operation data, use the method described in chapter 10.1.3.1, "Saving a database."

· A directory in which data will be saved must be created in advance. · To start the database backup, log in as a root user. Back up a database as follows: 1. Start database backup.

Enter the following command to start database backup: # /opt/swstorage/bin/stgdbbackup

182

2. Confirm to continue processing. Enter "y" to continue processing or "n" to stop processing.

////////////////////////////////////////////////////////////////////

SystemWalker/StorageMGR Storage management server ( kiku )

Database backup

////////////////////////////////////////////////////////////////////

+----------------------------------------------------------------+

| |

| All of the stored data will be saved in an external file. |

| |

| [Notes] |

| Prepare a directory for storing the data to be saved. |

| |

+----------------------------------------------------------------+

Do you want to continue with processing? [y/n] ==> y 3. Enter the name of the save data storage directory.

Using an absolute pathname, enter the name of the directory in which to store save data.

If the directory already has save data, processing is not performed. Delete the save data in the directory or specify another directory, and then retry processing.

////////////////////////////////////////////////////////////////////


Database backup

////////////////////////////////////////////////////////////////////

Enter the absolute path name of the directory

for storing the data to be saved.

Enter ==> /export/home/storagem/backdata 4. To continue with database backup processing, enter a final confirmation.

Enter "y" to continue with database backup processing or "n" to stop it. If "y" is entered, the window display returns that of step 2.

////////////////////////////////////////////////////////////////////


Database backup

183

////////////////////////////////////////////////////////////////////

Directory containing the saved data : /export/home/storagem/backdata

Do you want to continue with processing? [y/n] ==> y 5. Database backup copies are created.

Database backup copies are created, and execution results are displayed on the window as necessary. An example of such execution results is shown below.

///// SystemWalker/StorageMGR database backup /////

==================================================================

DB data backup will start.

==================================================================

....

Unloading of data is complete.(base)

...

Unloading of data is complete.(backup)

.......

Unloading of data is complete.(space)

.

Unloading of data is complete.(repl)

==================================================================

Backup of DB data is complete.

==================================================================

Database backup ended normally.

#

10.2.1.2 Database restoration

This chapter describes restoring data that has been saved as described in chapter 10.2.1.1, "Database backup" to a database collectively.

· Data currently stored in a database will be lost in this processing because it will be overwritten by save data. · To start the database restoration, log in as a root user.

· When the database restoration is normally completed, the database is saved. Restore a database as follows: 1. Start database restore processing.

Enter the following command to start database restore processing:

184

# /opt/swstorage/bin/stgdbrestore 2. Confirm to continue processing.

Enter "y" to continue processing or "n" to stop processing.

////////////////////////////////////////////////////////////////////


Database restore

////////////////////////////////////////////////////////////////////

+----------------------------------------------------------------+

| |

| All of the saved data will be restored to database. |

| |

| [Notes] |

| Check the directory containing the saved data. |

| |

+----------------------------------------------------------------+

Do you want to continue with processing? [y/n] ==> y 3. Enter the name of the save data storage directory.

Using an absolute pathname, enter the name of the directory in which save data is stored.

If any part of save data in the directory is missing, processing is not performed because data consistency may not be maintained. ////////////////////////////////////////////////////////////////////


Database restore

////////////////////////////////////////////////////////////////////

Enter the absolute path name of the directory

in which the saved data is stored.

Enter ==> /export/home/storagem/backdata 4. To continue with database restore processing, enter the final confirmation.

Enter "y" to continue with database restore processing or "n" to stop it. If "n" is entered, the window display returns to that of step 2.

////////////////////////////////////////////////////////////////////


Database restore

////////////////////////////////////////////////////////////////////

185

Directory containing the saved data : /export/home/storagem/backdata

Do you want to continue with processing? [y/n] ==> y 5. Database restore processing is performed.

Database restore processing is performed, and execution results are displayed on the window as necessary. An example of such execution results is shown below.

////////// SystemWalker/StorageMGR database restore //////////////

==================================================================

DB data will be restored.

==================================================================

....

Loading of data is complete.(base)

....

Updating of the optimal information is complete.(base)

...

Loading of data is complete.(backup)

...

Updating of the optimal information is complete.(backup)

.......

Loading of data is complete.(space)

.......

Updating of the optimal information is complete.(space)

.

Loading of data is complete.(repl)

.

Updating of the optimal information is complete.(repl)

==================================================================

DB data has been completely restored.

==================================================================

Database restore processing ended normally.

#

10.2.2 Collecting maintenance information

10.2.2.1 Collecting information using a Web window

Collect information as follows:

186

1. Start the Java Plug-in control panel. Start the Java Plug-in control panel as follows: Select [Settings] - [Control Panel] - [Java Plug-in].

2. Make the startup settings of the Java console. On the Java control panel, access the [Basics] tag, mark the [Display Java Console] check box, click the [Apply] button, and exit the Java Plug-in control panel.

3. Start the Web window of SystemWalker/StorageMGR. 4. The Java console will be started and a message will be output. Save the message to a file, and attach the file

to your report.

10.2.2.2 Collecting error survey information

Log into the storage management server and the storage server. Collect the following information. 1. When an error occurs during backup management

Type Storage management server Storage server

Event log Must be collected. Must be collected.

Trace log Acquire the files under the following directory:

/var/FJSVswtrc/trc/

Acquire the files under the following directory:

/var/FJSVswtrc/trc/

Backup management list Need not be collected.

Acquire the files under the following directory:

/etc/opt/FJSVswsts 2. When an error occurs during SAN resource management


System log Must be acquired. Must be acquired.

Trace log

Get the files under the following directories:

/var/opt/FJSVswsam/

/var/opt/FJSVswsag/log/

/kernel/drv/sd.conf

/kernel/drv/fjpfca.conf(if it exists)

/kernel/drv/fcaw.conf(if it exists)

Get the files under the following directory:

/var/opt/FJSVswsaa/

/etc/snmp/conf/ 3. When an error occurs during replication management


System log Must be acquired. Must be acquired.

Trace log Get the files under the following directory:

/var/FJSVswtrc/trc


/var/FJSVswtrc/trc

Replication management list Replication management list


/etc/opt/FJSVswsrp

10.2.3 Troubleshooting for a failure in access to a repository database

This chapter describes finding a cause for a failure in access to a repository database and what to do in such a case.

Perform this procedure on the storage management server. 1. Check whether the RDB daemons have not stopped.

[Check method] Execute the following command to check for any processing related to the RDB daemons. # ps -ef | grep RDBSWSTF | grep -v grep

[Required action] If no processing related to the three RDB daemons exists, retry processing after restarting (start after stopping) the daemons. For an explanation on restarting the daemons, see chapter 11.5.3, "Starting and stopping the

187

RDB daemons." 2. Check that there is sufficient free space as required to update a repository database.

[Check method] Execute the following command to check the usage ratio of space required to update a repository. # /opt/swstorage/bin/stgdbloginf

[Required action] If the usage ratio is 100%, save the database space according to "Saving a database". (Consequently, there will be sufficient free space required to update a repository.) After using the database save method, restart (start after stopping) the RMI daemon. For an explanation on restarting the daemon, see chapter 11.5.2, "Starting and stopping the RMI daemon," and Chapter 2, "Starting and Stopping Daemons." Then, perform this step again.

3. Check whether the database save processing is in progress. [Check method] Execute the following command to check for any processing related to the database save command. # ps - ef | grep stgdbdmp | grep -v grep

[Required action] If processing related to the database save command exists, retry processing after waiting for the end of the database save command.

4. Check whether an input-output error or any other error has occurred in the database space. [Check method] Refer to the /var/opt/FJSVswstf/log/RDBSWSTF.log file, and beginning from the last line, search for any message with "rdb: ERROR: qdgXXXXX-" in its contents (also check the messages output at the same time). Then, obtain the value of "qdgXXXXX," and check for it in Table 10.1. [Required action] If "qdgXXXXX" is in the table, examine the target according to the error description corresponding to the qdg messages in Table 10.1, and determine if there is a problem. If a problem is found, take steps to solve the problem, and specify the appropriate settings. Then, recover the database space by using the database recovery method. After the database recovery command ends normally, acquire the latest save data by using the database save method. Then, restart (start after stopping) the StorageMGR daemons. For an explanation on restarting the daemons, see chapter 11.5.8, "Starting and stopping the StorageMGR daemons," and Chapter 2, "Starting and Stopping Daemons." Retry processing.

If the database recovery command is executed with 0 specified for option -m, execute the resource consistency command specified with option -x (see chapter 11.1.3.1, "Resource match command") on all Storage servers in a backup operation.

If an error such as an input-output error occurs in a database space, a file required for analyzing the cause of the error may be created in /SWSTFDB/core. If the corresponding recovery ends normally, delete the file in this directory.

5. Collect the files in /var/opt/FJSVswstf/log, and contact a Fujitsu SE.

10.3 Troubleshooting for a hardware error, etc. occurring during backup

This chapter describes what to do for a hardware error, etc. occurring during a backup using SystemWalker/StorageMGR.

10.3.1 Overview

While you perform backup using SystemWalker/StorageMGR, any of the following instances may occur: · When you perform backup using the backup execution command, the command abnormally terminates after a

swst0638 message is output. · When you check the copying execution status using the backup execution status display command, "failed" is

displayed in the Status field. · When you check the progress of copying using the backup synchronous processing progress display

command, "failed" appears in the Status field. · When you check the copying execution status using the restore execution status display command, "failed" is

188

displayed in the Status field. If any of the above instances has occurred, a hardware error may exist on the transaction volume or backup volume.

If any error has occurred on the transaction volume, do as described in "Troubleshooting for a hardware error, etc. on a transaction volume".

If you have checked that no error has occurred on the transaction volume, a hardware error may have occurred on the backup volume. In such a case, do as described in "Troubleshooting for a hardware error, etc. on a backup volume".

10.3.2 Troubleshooting

10.3.2.1 Troubleshooting for a hardware error, etc. on a transaction volume

If any error has occurred on a transaction volume, you can remove the error and restore the transaction volume using the restore execution command.

You cannot perform restoration using backup career information that was not successfully copied.

10.3.2.2 Troubleshooting for a hardware error, etc. on a backup volume

If any hardware error has occurred on a backup volume, to recover from the error, etc. follow the steps below: 1. Using the History information display command, check the generation number in the backup career

information that was not successfully copied and the device name of the backup volume as shown in the following example: Example: In the backup career information of a transaction volume (/dev/dsk/c1t0d0s6), check the generation number and the device name of the backup volume. # swsthistdisp /dev/dsk/c1t0d0s6

Server=node1 Device=/dev/dsk/c1t0d0s6 Mount-Point=/mnt/tran1

Generation Version Backup-Date Backup-Disk Status Execute

1 2 2000/02/2122:30 /dev/dsk/c1t0d1s6 failed ----

2 1 2000/02/2022:30 /dev/dsk/c1t0d2s6 succeeded ----

# Check that "failed" is displayed in the Status field. If any other status than "failed" is displayed, the following cause is possible. Find the cause and re-execute backup.

2. Delete the backup career information that was not successfully copied using the History information deletion command as follows: Example: Delete a career with relative generation number 1 from the backup career information of the transaction volume (/dev/dsk/c1t0d0s6). # swsthistdel -g 1 /dev/dsk/c1t0d0s6

/dev/dsk/c1t0d0s6 swsthistdel completed

# 3. You may not be able to use a backup volume that was not successfully copied, due to a hardware error, etc.

Using the device information setting command, delete the backup volume as follows: Example: Delete the backup volume (/dev/dsk/c1t0d1s6). # swstdevinfoset -o /dev/dsk/c1t0d1s6

Swstdevinfoset completed

# 4. Create a new backup volume with the same size as the transaction volume using the device information

setting command as follows: Example: Create a device (/dev/dsk/c1t0d3s6) with the same size as the transaction volume, as a backup volume. # swstdevinfoset -b /dev/dsk/c1t0d3s6

Swstdevinfoset completed

#

189

5. Back up the transaction volume using the backup execution command.

10.4 Troubleshooting for a Hardware Error or Other Error Occurring during Replication

This chapter describes the corrective action for hardware or other error occurring during SystemWalker/StorageMGR replication.

10.4.1 Overview

When you are using SystemWalker/StorageMGR to perform replication, any of the following situations may occur: · When you execute Synchronous processing start command (swsrpstartsync) or the replication creation

command (swsrpmake), the command outputs swsrp2606 or swsrp2648 and then terminates abnormally. · When you check the progress of copying using the operation status display command (swsrpstat), "failed,"

"halt," or "?????" appears in the Status field. Status display Corrective action

Failed A hardware error may have occurred.

Halt A hardware error may have occurred during box-to-box replication .

????? This indicates that volume information could not be obtained from a disk array device. If "?????" appears again after reexecution, a hardware error may have occurred.

If any of the above situations has occurred, a hardware error may have occurred.

Described below are corrective actions.

10.4.2 Troubleshooting

If a hardware error has occurred during the replication operation, follow the steps below to recover. 1. Using the operation status display command (swsrpstat), check the volume where an error has occurred as

shown in the following example. Example) Check the information for the replication volume for which "failed," "halt," or "?????" appears in the Status field. C:¥> C:¥Win32App¥StorageMGR¥bin¥swsrpstat

Server Original-Volume Replica-Volume Direction Status Execute

SV-1 g1d1p1@SV-1 g1d1p1@SV-2 regular replicated ----

SV-1 g1d2p1@SV-1 g1d2p1@SV-2 ---- ---- ----

SV-1 g1d3p1@SV-2 g1d3p1@SV-2 reverse failed ----

C:¥> In the example above, an error has occurred during copying from replication destination volume g1d3p1@SV-2 to replication source volume g1d3p1@SV-1.

2. Stop the copying using the replication cancellation command (swsrpcancel) as shown below. Example) Stop the incorrect copying. C:¥> C:¥Win32App¥StorageMGR¥bin¥swsrpcancel g1d3p1@SV-2 g1d3p1

FROM=g1d3p1@SV-2, TO=g1d3p1 swsrpcancel completed

C:¥> 3. If you cannot use the replication source and replication destination volumes due to a hardware error, delete the

replication volume information, as shown in the example below, using the replication volume information deletion command (swsrpdelvol). Example) Delete the incorrect replication volume information. C:¥> C:¥Win32App¥StorageMGR¥bin¥swsrpdelvol g1d3p1 g1d3p1@SV-2

swsrpdelvol completed

C:¥> 4. Correct the hardware error by, for example, replacing a disk. When a hardware error has occurred on a

replication source volume, register the replication destination volume and a new replication source volume using the replication volume information setting command (swsrpsetvol), and then restore them using the

190

replication creation command (swsrpmake) or other appropriate method. Example) Register the replication source volume (g1d3p1@SV-1) and the new replication destination volume (g1d3p1@SV-2). Next, perform replication from the replication source volume to the replication destination volume to restore the data. C:¥> C:¥Win32App¥StorageMGR¥bin¥swsrpsetvol -o ORG g1d3p1 g1d3p1@SV-2

C:¥> swsrpsetvol completed

C:¥> C:¥Win32App¥StorageMGR¥bin¥swsrpmake g1d3p1 g1d3p1@SV-2

C:¥> From=g1d3p1, To=g1d3p1@SV-2 swsrpmake completed

C:¥> When a hardware error has occurred on the replication destination volume, register the replication source volume and a new replication destination volume using the replication volume information setting command (swsrpsetvol). Example) Register the new replication source volume (g1d3p1@SV-1) and the replication destination volume (g1d3p1@SV-2). C:¥> C:¥Win32App¥StorageMGR¥bin¥swsrpsetvol -o ORG g1d3p1 g1d3p1@SV-2

C:¥> swsrpsetvol completed

C:¥> 5. Restart the replication operation.

10.5 Changing the Operating Environment

10.5.1 Changing the IP address of a storage management server

Change the IP address of a storage management server as follows: 1. On the storage management server, change the system IP address. 2. On the storage management server, execute the server information change command. For more information

on the server information change command, see chapter 11.2.1, "Server information change command (stgcmmodnode)".

3. On all the storage servers managed by the concerned storage management server, execute the server information change command. For more information on the server information change command, see chapter 11.2.1, "Server information change command (stgcmmodnode)".

4. On the storage management server, restart the services of SystemWalker/StorageMGR. For information on restarting a service, see Chapter 2, "Starting and Stopping a Daemons".

5. When the SAN management function monitors a device error using SNMP TRAP, the send destination for SNMP TRAP for each device must be changed. The SAN management function provides a command for automatically changing the send destination for SNMP TRAP set on each device. For more information, see chapter 4.9, "Command Line Interface (CLI)" in the SystemWalker/StorageMGR User's Guide.

10.5.2 Changing the IP address of a storage server

Change the IP address of a storage server as follows:

For more information on the Web window, see chapter 1.2.6.1, "Changing the IP address of a storage server" of the "SystemWalker/StorageMGR User's Guide". 1. On a target storage server, stop daemons of SystemWalker/StorageMGR. For more information on stopping a

service, see Chapter 2, "Starting and Stopping a Daemons". 2. On the storage server, change the system IP address. 3. On the storage server, start daemons of SystemWalker/StorageMGR. For more information on starting a

service, see Chaper 2, "Starting and Stopping a Daemons". 4. On the server list view on the initial window of SystemWalker/StorageMGR, select a server with information to

be changed, select [Change Server] from the [Operation] menu, and display the [Server change] window. 5. On the [Server change] window, change the IP address and click the [OK] button. 6. When a storage server is registered using SAN management, delete the device icon of the previous IP (do not

delete the access path), then detect the new IP device and register it.

10.5.3 Changing the port number of a storage management server

Change the port number of a storage management server as follows:

On the storage management server, change the port number of the communications daemon (stgxfws) described at /etc/services.

191

1. On the storage management server, execute the server information change command. For more information on the server information change command, see chapter 11.2.1, "Server information change command (stgcmmodnode)".

2. On all the storage servers managed by the concerned storage management server, execute the server information change command. For more information on the server information change command, see chapter 11.2.1, "Server information change command (stgcmmodnode)".

3. On the storage management server, restart the daemons of SystemWalker/StorageMGR. For information on restarting a service, see Chapter 2, "Starting and Stopping a Daemons".

10.5.4 Changing the port number of a storage server

Change the port number of a storage server as follows:

For more information on the Web window, see chapter 1.2.6.2, "Changing the port number of a storage server" of the "SystemWalker/StorageMGR User's Guide". 1. On a target storage server, stop services of SystemWalker/StorageMGR. For more information on stopping a

deamon, see Chapter 2, "Starting and Stopping a Daemons". 2. On the storage server, change the port number of the communications daemon (stgxfws) of

SystemWalker/StorageMGR. 3. On the storage server, start daemons of SystemWalker/StorageMGR. For more information on starting a

daemon, see Chapter 2, "Starting and Stopping a Daemons". 4. On the server list view on the initial window of SystemWalker/StorageMGR, select a server with information to

be changed, select [Change Server] from the [Operation] menu, and display the [Server change] window. 5. On the [Server change] window, change the port number and click the [OK] button. 6. When a storage server is registered by SAN management, delete the device icon of the previous server name

(however, do not delete the access path), search for the device icon of the new server name, and register it.

10.5.5 Changing the server name of a storage management server

Change the server name of a storage management server as follows:

For more information on the Web window, see chapter 1.2.6.3, "Changing the server name of a storage management server" of the "SystemWalker/StorageMGR User's Guide". 1. Check whether the target storage management server serves also as a storage server. If it does, do as

described in chapter 10.5.6, "Changing the server name of a storage server". 2. On the server list view on the initial window of SystemWalker/StorageMGR, select a server with information to

be changed, select [Change Server] from the [Operation] menu, and display the [Server change] window. 3. On the [Server change] window, change the server name and click the [OK] button. 4. On all the storage servers managed by the concerned storage management server, execute the server

information change command. For more information on the server information change command, see chapter 11.2.1, "Server information change command (stgcmmodnode)".

10.5.6 Changing the server name of a storage server

Change the server name of a storage server as follows:

For more information on the Web window, see chapter 1.2.6.4, "Changing the server name of a storage server" of the "SystemWalker/StorageMGR User's Guide". 1. Delete a storage server environment. For information on the deletion method, see chapter 4.6.4, "Deleting a

storage server ". 2. On the server list view on the initial window of SystemWalker/StorageMGR, select a server with information to

be changed, select [Change Server] from the [Operation] menu, and display the [Server change] window. 3. On the [Server change] window, change the server name and click the [OK] button. 4. During registration of a storage server as a SAN management target, the corresponding icon with a new server

name indicates the device is not registered (blinking). Register the device icon.

10.5.7 Changing the device configuration

Changing the device configuration refers to any of the following: · Mount name change · Change from File System operation to RawDevice operation · Capacity change of partitions (mainly for re-creation of LUN mapping) · Start position for change of partitions (mainly for re-creation of LUN mapping)

10.5.7.1 Backup management

Change the device configuration as shown below. This processing, when executed, applies to all the volumes in a disk that stores a volume with a device configuration to be changed. 1. Check whether there is a transaction volume on the target disk that needs to be backed up. If it does, delete

192

the transaction volume. For information on deleting a transaction volume, see chapter 4.6.2.1, "Deleting a transaction volume".

2. Check whether a backup volume exists in the target disk. If it does, delete the backup volume. For information on deleting a backup volume, see chapter 4.6.2.2, "Deleting a backup volume".

3. The new device configuration must be reflected on the management list of SystemWalker/StorageMGR. For information on adding a device, see chapter 4.6.1, "Adding a device".

10.5.7.2 Replication management

Change the device configuration as shown below. When executed, this processing applies to all the volumes on a disk on which a volume whose device configuration to be changed is stored. 1. Check whether there are any replication volumes on the target disk. If there are, delete them. For information

about deleting a replication volume, see chapter 7.6.2, "Deleting a replication source volume and replication destination volume."

10.5.7.3 Space management

Change the device configuration as shown below. Only the settings for space management do not have to be changed, since partition capacity and start position do not matter. 1. Check whether there are any volumes registered in a space management job on the target disk. If there are,

delete them. 2. The new device configuration must be reflected in the management list of SystemWalker/StorageMGR. Update

SystemWalker/StorageMGR on the device. For more information about the above processing, see chapter 9.8.2, "Changing a device."

10.5.8 Changing the IP address of an equipment supported by SAN resource management

When the IP address of the equipment to the equipment support level (from A to E) registered into SAN resource management is changed, SAN resource management can change the IP address part of the property of the same equipment automatically.

Carry out equipment detection by the new IP address from [operation (C)]-[equipment (D)]-[detection (F)] of the menu of a SAN resource management window. By this operation, SAN resource management detects that the equipment registered was changed into the new IP address, and changes the IP address part of equipment information automatically. In addition, the two or more equipments of a support level (from A to C) can be changed automatically by the operation [file (F)]-[the equipment detection in a subnetwork (B)] of the menu.

In addition, equipment managed software call information is not changed automatically. Rewrite manually from the property of the icon of each equipment.

193

Chapter 11 Commands

This chapter describes using commands.

11.1 Backup Management Commands

This chapter describes operations using backup management commands.

11.1.1 Environment definition commands

This chapter describes environment definition commands for backup management.

To define a backup management environment, use the following commands:

Function Command name Description

Storage server configuration information setting command swstsvrset Sets the configuration information of a storage

server.

Storage server configuration information display command swstsvrdisp Displays the configuration information of a

storage server.

Device information setting command swstdevinfoset Sets the use of a device.

Device usage status display command swstdevdisp Displays the information of a device.

Backup policy setting command swstbkpolset Sets a backup policy.

Backup policy display command swstbkpoldisp Displays a backup policy that has been set.

Backup policy deletion command swstbkpoldel Deletes a backup policy that has been set

11.1.1.1 Storage server configuration information setting command (swstsvrset)

This command sets configuration information of a storage server. a. Specification

[To be executed on a storage server] # /opt/FJSVswsts/bin/swstsvrset [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstsvrset [-h Server]

b. Description of options Option Description

-h

Specifies the name of a storage server to be subject to the backup operation. This option is valid only on a storage management server.

If this option is omitted, the storage server on which the command is entered will be subject to the processing.

c. End status = 0: Normal end > 0: Abnormal end

d. Execution example Set configuration information of a storage server. # /opt/FJSVswsts/bin/swstsvrset swstsvrset completed #

Set configuration information of a storage server (job1) from a storage management server. # /opt/FJSVswsts/bin/swstsvrset -h job1

swstsvrset completed

#

195

This command can be executed only while none of the following commands are running. · Backup policy setting command (swstbkpolset) · Backup policy deletion command (swstbkpoldel) · Backup execution command (swstbackup) · Restore execution command (swstrestore) · Restore cancellation command (swstcancelrest) · Backup synchronous processing start command (swststartsync) · Backup synchronous processing cancel command (swstcancelsync) · Device information setting command (swstdevinfoset) · History information deletion command (swsthistdel) · Resource backup command (swstresback) · Resource restore command (swstresrst) · Resource match command (swstsrsemtch)

11.1.1.2 Storage server configuration information display command (swstsvrdisp)

This command displays configuration information of a storage server, which has been set using the storage server configuration information setting command. a. Specification

[To be executed on a storage server]

# /opt/FJSVswsts/bin/swstsvrdisp

[To be executed on a storage management server]

# /opt/FJSVswsts/bin/swstsvrdisp [-h Server] b. Description of options

Option Description

-h Specifies a storage server name.

This option is valid only on a storage management server. c. End status

= 0: Normal end > 0: Abnormal end

d. Execution example Display configuration information of a storage server (Work1). # /opt/FJSVswsts/bin/swstsvrdisp Storage-Server = Work1 #

The following information will be displayed. Title Description

Storage-Server Displays a storage server name.

11.1.1.3 Device information setting command (swstdevinfoset)

Set a volume that has been allocated to the disk array unit GR series, as a transaction or backup volume.

A transaction volume refers to a volume that stores work data to be backed up.

A backup volume refers to a volume used to store a backup of this transaction data. When using transaction volumes to back up data, see chapter 4.2.2 "Deciding a backup target" in chapter 4 "Backup Oprations (Normal Transaction Volumes)" for information about the transaction volume. See chapter 4.2.4 "Preparing a backup volume" chapter 4 "Backup Oprations (Normal Transaction Volumes)" for information about the backup volume.

196

When backup/restore is operated in cooperation with the SP series, it is necessary to do the registration setting as a transaction volume by which the SP series is operated.

a. Specification method [To be executed on a storage server] # /opt/FJSVswsts/bin/swstdevinfoset -t [-f] | -b | -o Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstdevinfoset [-h Server] -t [-f] | -b | -o Device-Name



This option is valid only on a storage management server.

-t Register the specified device as a transaction volume.

Cannot be specified at the same time as the -b and -o options.

-f

Register the specified device as a transaction volume for operation with SP-series devices.

Specify this option together with the -t option.

Cannot be specified at the same time as the -b and -o options.

-b Register the specified device as a backup volume.

Cannot be specified at the same time as the -t and -o options.

-o Deregister the specified device if it has been registered as a work or backup volume.

Cannot be specified at the same time as the -t and -b options. c. Description of operand

Operand Description

Device-Name

Specify a device name.

Specify the name of a block device.

In the case of a SDX object, specify the name of a partition. d. End status


e. Execution example Register a device (/dev/dsk/c1t0d0s6) as a transaction volume. # /opt/FJSVswsts/bin/swstdevinfoset -t /dev/dsk/c1t0d0s6 swstdevinfoset completed #

Register a device (/dev/dsk/c1t0d2s6) as a backup volume. # /opt/FJSVswsts/bin/swstdevinfoset -b /dev/dsk/c1t0d2s6

swstdevinfoset completed

# Register a device (/dev/dsk/c1t1d0s6) as a transaction volume for operation with SP-series devices. # /opt/FJSVswsts/bin/swstdevinfoset -t -f /dev/dsk/c1t1d0s6


# Deregister a device (/dev/dsk/c1t0d0s6) that has been registered as a transaction volume. # /opt/FJSVswsts/bin/swstdevinfoset -o /dev/dsk/c1t0d0s6


197

#

No device can be registered as a transaction volume if: · Another device with the same logical volume information has already been registered as a transaction volume. · The space of the device to be registered overlaps the space of an already registered work or backup volume. · An attempt is made to specify a GR-series device in which no SP-series device is installed as a transaction

volume for operation with SP-series devices. · An attempt is made to specify some devices contained in a log group for operation with SP-series devices and

other devices in the log group for operation without SP-series devices.

No device can be registered as a backup volume if: · Another device with the same logical volume information has already been registered as a backup volume. · The space of the device to be registered overlaps the space of an already registered transaction or backup

volume. · The device to be set up is already mounted. · The device is an SDX object.

You must delete related backup history information before: · Changing a backup volume to a transaction volume · Canceling the setting of a backup volume

You must delete a backup policy specified on a transaction volume before: · Changing a transaction volume to a backup volume · Canceling the setting of a transaction volume · Changing the transaction volume to a transaction volume subject to the SP operation

The following changes are possible only after the backup policies managed with SP-series devices are deleted: · Change of a business volume for operation with SP-series devices into a transaction volume for any operation

other than for operation with SP-series devices · Change of a transaction volume for operation with SP-series devices into a backup volume · Cancellation of settings of a transaction volume for operation with SP-series devices

This command can be executed only while none of the following commands are running. · Storage server configuration information setting command (swstsvrset) · Backup policy setting command (swstbkpolset) · Backup policy deletion command (swstbkpoldel) · Backup synchronous processing start command (swststartsync) · Backup synchronous processing cancel command (swstcancelsync) · Backup execution command (swstbackup) · Restore execution command (swstrestore) · Restore cancellation command (swstcancelrest) · History information deletion command (swsthistdel) · Resource match command (swstsrsemtch) · Resource backup command (swstresback) · Resource restore command (swstresrst)

198

11.1.1.4 Device usage status display command (swstdevdisp)

This command displays information of a transaction or backup volume or any other definable device, which has been set using the device information setting command (swstdevinfoset). a. Specification method


# /opt/FJSVswsts/bin/swstdevdisp [-h Storage-Server] [-t] [-b] [-o] [Device-Name]


# /opt/FJSVswsts/bin/swstdevdisp [-h Server] [-t] [-b] [-o] [Device-Name] b. Description of options

Option Description


This option can be specified only on a storage management server.

-t Displays information on a device that has been set as a transaction volume.

Displays device information on all the transaction volumes if the device name in an operand is omitted.

-b Displays a device that has been set as a backup volume.

Displays device information on all the backup volumes if the device name in an operand is omitted.

-o Displays all the devices other than those set as a work or backup volume.

Displays all the devices other than those set as a transaction or backup volume if the device name in an operand is omitted.

Information on a device that has been set as a transaction volume will be displayed if all of the t, b, and o options are omitted.

c. Description of operand Operand Description

Device-Name

Specify a device name.


Displays device information on all the transaction volumes if this operand as well as the options are omitted.



e. Execution example Display the usage statuses of the registered devices. # /opt/FJSVswsts/bin/swstdevdisp -tb Server Device Size Device-Mode Mount-Point (Method) Backup-Engine Work 2 /dev/dsk/c1t0d0s6 1.0 Gbyte Transaction /mnt/tran1 (ufs) StorageMGR Work 2 /dev/dsk/c1t1d0s6 1.0 Gbyte Transaction /mnt/tran2 (ufs) SP Work 2 /dev/dsk/c1t0d2s6 1.0 Gbyte Backup (used) ---- (----) StorageMGR Work 2 /dev/dsk/c1t0d2s3 1.0 Gbyte Backup (free) ---- (----) StorageMGR Work 2 /dev/dsk/c1t0d7s6 2.0 Gbyte Backup (used) ---- (----) StorageMGR Work 2 /dev/dsk/c1t0d7s3 2.0 Gbyte Backup (free) ---- (----) StorageMGR : #


199

Server Displays a storage server name.

Device Displays a StorageMGR device name.

Size Displays the size of a partition allocated to a device.

Device-Mode

Displays a character string by which a device can be identified. · "Transaction": Represents a transaction volume. · "Backup": Represents a backup volume. · "Other": Represents a device that can be registered as a

work or backup volume. A backup volume is indicated as "Backup (used)" if it is being used or "Backup (free)" if it is not used.

Mount-Point (Method)

Displays the mount point of a device. The file system type of the mount point is displayed inside the parentheses.

Backup-Engine

Displays the operation type. · "StorageMGR": Backup operation using

SystemWalker/StorageMGR · "SP": Backup operation with an SP-series device

11.1.1.5 Backup policy setting command (swstbkpolset)

This command sets a backup policy (numbers of preservation generations and interval days).

The number of preservation generations means how many generations of backup data should be kept.

The number of interval days means the number of days after execution of backup in which the next backup should be performed.

Even if the number of interval days is specified, SystemWalker/StorageMGR does not automatically collect backup.

Setting a backup policy cannot be used for the transaction volume by which the SP series is operated.

When you specify a backup policy, there must be as many backup volumes required operating according to the specified backup policy. To view information on the number of backup volumes required to perform the backup operation of a regular transaction volume, see chapter 4.2.4, "Preparing a backup volume".

a. Specification method - Setting backup policies by specifying a transaction volume [To be executed on a storage server] # /opt/FJSVswsts/bin/swstbkpolset [-i Interval-Days] [-s Save-Number][Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstbkpolset [-h Server][-i Interval-Days] [-s Save-Number][Device-Name]




-i Specifies the number of interval days. You can specify a value between 1 and 366.

200

If this option is omitted during initial registration, 30 will be set. If this option is omitted during update, the existing value will be inherited.

-s Specifies the number of preservation generations. You can specify a value between 1 and 31. If this option is omitted during initial registration, 2 will be set. If this option is omitted during update, the existing value will be inherited.


Device-Name Specify a StorageMGR device name.

If the device name is omitted, the backup policy will be set for all the transaction volumes.

RDB-Name Specify the RDB system name after the log group name, using "/" as the delimiter.

This operand can be omitted if there is no RDB system name. d. End status


e. Execution example To set 3 as the save number of a transaction volume(/dev/dsk/c1t0d5s3) as a backup policy: # /opt/FJSVswsts/bin/swstbkpolset -s 3 /dev/dsk/c1t0d5s3 /dev/dsk/c1t0d5s3 swstbkpolset completed #

If this command without a transaction volume name is executed, backup policies are set for all transaction volumes excluding those targeted for operation with SP-series devices.

If backup history information is in a transaction volume, the number of preservation generations cannot be changed.

· No backup policy can be set if: · There are not as many backup volumes as the specified number of preservation generations. · Registration is attempted by specifying a transaction volume for operation with SP-series devices. · An option for more number of preservation generations than can be specified is specified. · An option for more interval days than can be specified is specified.

· This command can be executed only while none of the following commands is executed. · Resource match command (swstsrsemtch) · Device information setting command (swstdevinfoset) · Storage server configuration information setting command (swstsvrset) · Resource backup command (swstresback) · Resource restore command (swstresrst)

11.1.1.6 Backup policy display command (swstbkpoldisp)

This command displays a backup policy that has been set for a transaction volume.

This command cannot be used for the transaction volume by which the SP series is operated. a. Specification method

- Displaying backup policies by specifying a

201

transaction volume


# /opt/FJSVswsts/bin/swstbkpoldisp [Device-Name]


# /opt/FJSVswsts/bin/swstbkpoldisp [-h Server] [Device-Name]



This option can be specified only on a storage management server. c. Description of operand

Operand Description

Device-Name

Specify a StorageMGR device name.


If the device name is omitted, a backup policy for a transaction volume with a registered backup policy will be displayed.



e. Execution example To display the backup policies of a transaction volume(/dev/dsk/c1t0d5s3): # /opt/FJSVswsts/bin/swstbkpoldisp /dev/dsk/c1t0d5s3 Server Device Interval-Days Save-Number Mount-Point (Method) Transaction2 /dev/dsk/c1t0d5s3 30 2 /stg(ufs) #



Device Displays a device name.

Interval-Days Displays a number of interval days.

Save-Number Displays a number of preservation generations.

Mount-Point (Method)

Displays the mount point of a device. The file system type of the mount point will be displayed inside the parentheses.

11.1.1.7 Backup policy deletion command (swstbkpoldel)

This command deletes a backup policy that has been set.

If the transaction volume to be deleted has backup history information, delete the backup history information and then execute this command.

This command cannot be used for the transaction volume by which the SP series is operated. a. Specification method

- Deleting backup policies by specifying a transaction volume

202

[To be executed on a storage server] # /opt/FJSVswsts/bin/swstbkpoldel Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstbkpoldel [-h Server] Device-Name




Operand Description

Device-Name Specify a StorageMGR device name.

Specify the name of a block device. d. End status


e. Execution example To delete the backup policies of a transaction volume (/dev/dsk/c1t0d5s3): # /opt/FJSVswsts/bin/swstbkpoldel /dev/dsk/c1t0d5s3 /dev/dsk/c1t0d5s3 swstbkpoldel completed #

No backup policy can be deleted if: · The transaction volume to be deleted has backup history information. · A transaction volume whose backup policies are to be deleted has already started backup synchronous

processing.

This command can be executed only while none of the following commands are running. · Storage server configuration information setting command (swstsvrset) · Device information setting command (swstdevinfoset) · Resource match command (swstsrsemtch) · Resource backup command (swstresback) · Resource restore command (swstresrst)

11.1.2 Operation commands

This chapter describes operation commands for backup management.

To operate backup management, use the following commands:


Backup execution command swstbackup Performs the synchronous high-speed backup or snapshot-type high-speed backup operation.

Backup execution status display command swstbackstat Displays the backup progress status.

Restore execution command swstrestore Performs restoration.

Restore cancellation command swstcancelrest Cancels the execution of restoration.

Restore execution status display command swstreststat Displays the execution status of restoration.

203

History information display command swsthistdisp Displays the history information that has been

backed up.

History information deletion command swsthistdel Deletes the history information that has been

backed up.

Backup synchronous processing start command Swststartsync Starts backup synchronous processing.

Backup synchronous processing cancel command Swstcancelsync Aborts backup synchronous processing.

Backup synchronous processing progress display command

Swstsyncstat Displays the progress of the backup synchronous processing.

Execution status display command swstexecstat Displays the execution status of a command

executed on a transaction volume.

11.1.2.1 Backup execution command (swstbackup)

When you are not performing backup synchronous processing, the system registers information about the time at which OPC started copying from disk to a disk, the dates on which the backup command was executed, and the backup volumes to which data has been copied, as history information. This type of backup is called snap shot backup.

If you are performing backup synchronous processing, the system checks whether equivalency is maintained. When equivalency is maintained, backup synchronous processing is stopped, and then information about the dates on which the backup command was executed or the backup volumes to which data was copied is registered as backup history information. This type of backup is called synchronous high-speed backup.

SystemWalker/StorageMGR executes a backup preprocessing Shell script(OpcBackup.pre) before executing backup and then a backup post processing Shell script (OpcBackup.post) after executing backup. You can customize these Shell script. For more information, see Appendix A, "Preprocessing and Postprocessing of Backup and Restoration". a. Specification method

- Creating backup copies by specifying a business volume [To be executed on a storage server] # /opt/FJSVswsts/bin/swstbackup Device-Name [-Xdevmap Device-Map-File] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstbackup [-h Server] Device-Name [-Xdevmap Device-Map-File]




-Xdevmap

Specifies a target backup volume to perform the snapshot fast backup. In the operand, specify a device map file in which a combination of a transaction volume and a target backup volume is described. If this option is not specified, the target backup volume will be automatically selected. To execute this command on a remote basis using the -h option, specify a device map file (of a storage server) using an absolute pathname. A file name specified in Device-Map-File must not include any national character.


Device-Name

Specifies a device name.


The partition name is specified for the SDX object. d. End status


e. Execution example

204

Back up a business volume in operation with SP-series devices # /opt/FJSVswsts/bin/swstbackup /dev/dsk/c1t1d0s6

/dev/dsk/c1t1d0s6 swstbackup completed

#

To guarantee data, this command performs backup after inhibiting access to transaction and backup volumes from other processes. Thus, the drive letters of devices are not assigned. This command terminates with an error if a drive letter of a transaction volume is assigned or if:

· The mount point has directories to which other volumes are to be mounted. · The volume has a file in use.

To mount a transaction volume from a server other than the server on which this command is entered, unmount the transaction volume, using the authority of the backup administrator. If the transaction volume must not be unmounted, create backup copies with the following procedure:

· Execute the sync command to synchronize the transaction volume and file system. · Execute this command. · Execute the fsck command to check the file system.

You cannot perform backup in the following cases. In these cases, do as described in [System Administrator's Response] in a message that will be output. · No backup policy has been specified for the specified transaction volume. · Backup executed one generation earlier was unsuccessful. · A transaction volume on which OPC is in progress has been specified. · Synchronous backup processing is performed in a transaction volume or log group to be processed, but the

state of equivalence is not reached. · The mount point set at registration of a transaction volume has been changed. · A device containing SynfinityFILE resources consisting of multiple transaction volumes is mounted. · When the state of SDX object is not in the following states. - Mirror volume is ACTIVE. - A SDX disk is enabling. - A mirror slice is ACTIVE or TEMP. · Restoration is being executed using backup history information that will cause a generation overflow. · No unused backup volume to be used as the copying destination could be acquired. · Any of the cabinet information (cabinet identifier, OLU number, EXTENT start position, and EXTENT size) of a

transaction volume has been changed. · A backup volume defined as the copy destination is mounted.

This command can be executed only while none of the following commands are running.

· Storage server configuration information setting command (swstsvrset) · Device information setting command (swstdevinfoset) · Resource match command (swstsrsemtch) · Resource backup command (swstresback) · Resource restore command (swstresrst)

The processing script is not executed before and behind in the following cases.

· The mirror slice of the SDX object is TEMP.

205

11.1.2.2 Backup execution status display command (swstbackstat)

This command displays the completion status of backup that is being performed using the backup execution command.

Information on the execution situation is not displayed for the business volume to operate the SP series.

Please do not use the OPC stop function of GRmgr while executing the snap shot type high speed backup. When the OPC stop function of GRmgr is used, it is displayed in this command regardless of the success or failure of an actual backup as succeeded.

a. Specification method - Displaying the backup processing status by specifying a business volume [To be executed on a storage server] # /opt/FJSVswsts/bin/swstbackstat [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstbackstat [-h Server] [Device-Name]




Operand Description

Device-Name

Specifies a device name corresponding to a transaction volume.


If this operand is omitted, the backup execution statuses of all the transaction volumes will be displayed.



e. Execution example Display the actual copying execution status. # /opt/FJSVswsts/bin/swstbackstat Server Transaction-Disk Backup-Disk Status Execute Work 1 /dev/dsk/c1t0d0s3 /dev/dsk/c1t0d2s3 succeeded ---- Work 1 /dev/dsk/c1t0d0s4 /dev/dsk/c1t0d2s4 executing 70% Work 1 /dev/dsk/c1t0d0s5 /dev/dsk/c1t0d2s5 executing 30% : #

Display the execution status of transaction volumes in operation with SP-series devices. # /opt/FJSVswsts/bin/swstbackstat

Server Transaction-Disk Backup-Disk Status Execute

Work 3 /dev/dsk/c1t1d0s3 ---- ---- ----

Work 3 /dev/dsk/c1t1d0s4 ---- ---- ----

Work 3 /dev/dsk/c1t1d0s5 ---- ---- ----

:

206

# The following information will be displayed. Keyword Description


Transaction-Disk Displays the device name of a transaction volume.

Backup-Disk Displays a backup volume name.

If no backup has been collected, "----" will be displayed.

Status

Displays a backup completion status using one of the following character strings. · "----": No backup has been collected (no history exists). · "succeeded": Backup has been completed. · "executing": Copying using OPC is in progress. · "failed": Copying using OPC has been interrupted due to an error. · "halt": Copying using OPC has been halt status.

Execute Displays how much has been copied in percentage if "executing" is displayed in the Status field. Displays "----" unless "executing" is displayed.

If "failed" or "halt" is displayed in the "Status" field, a hardware error may have occurred. After removing the cause of the hardware error, delete the backup history information using the history deletion command.

11.1.2.3 Restore execution command (swstrestore)

The data which exists in backup history information is restored by using OPC.

Restoration of each individual file cannot be performed because copying between devices will be performed.

When the restore execution command is executed, SystemWalker/StorageMGR performs the restore preprocessing Shell script(OpcRestore.pre) before copying data using OPC and then the restore postprocessing Shell script(OpcRestore.post) after copying data using OPC. You can customize these Shell script. For more information, see Appendix A, "Preprocessing and Postprocessing for Backup and Restoration".

You can restore data to any device other than a transaction volume. When you do so, the device must not be registered as a transaction volume and the device must have the same space size as the specified transaction volume.

a. Specification method - Restoring a normal transaction volume [To be executed on a storage server] # /opt/FJSVswsts/bin/swstrestore [-g Generation-No | -v Version-No] [-r Restore-Device-Name] Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstrestore [-h Server] [-g Generation-No | -v Version-No] [-r Restore-Device-Name] Device-Name


207



-g Specifies the relative generation number of data to be restored.

Check the relative generation number using the history information display command (swsthistdisp).

-v Specifies the absolute generation number of data to be restored.

Check the absolute generation number using the history information display command (swsthistdisp).

-r Specifies a restore destination device name to restore data to any other device than a transaction volume.

This option cannot be specified for a transaction volume of SymfoWARE. Note: If neither the -g or -v option is specified, the latest information out of information under history management will be restored.


Device-Name





e. Execution example Restore data with relative generation number 2 (For information on the relative generation number, see data displayed using the history information display command). # /opt/FJSVswsts/bin/swstrestore -g 2 /dev/dsk/c1t0d0s6 /dev/dsk/c1t0d0s6 swstrestore completed #

Restore transaction volumes in operation with SP-series devices. # /opt/FJSVswsts/bin/swstrestore /dev/dsk/c1t1d0s6

/dev/dsk/c1t1d0s6 swstrestore completed

#

On a transaction volume on which a file system has been constructed, restore a specific file as follows: 1. Mount a backup volume. Check the backup volume by executing the Backup History List view/History

information display command. 2. Copy the file to be restored by executing, for example, the cp command. 3. Unmount the backup volume.

For the SynfinityFILE file system, follow the procedure below: 1. Execute the following commands for a backup volume:

# sfxadm RAW-device-name-of-the-backup-volume # fsck -F sfxfs -o f RAW-device-name-of-the-backup-volume

2. Mount the backup volume: # mount -F sfxsfs backup-volume-name mount-point-name

3. Copy the file to be restored by executing, for example, the cp command: 4. Unmount the backup volume:

# unmount backup-volume-name or mount-point-name

If a transaction volume is mounted from a server other than the server on which this command is entered, execute this command after unmounting the transaction volume, using the authority of the backup administrator.

208

You cannot perform restoration or recovery in the following cases. In these cases, do as described in [System Administrator's Response] in a message that will be output. · Both a relative and absolute generation numbers have been specified. · A device registered as a transaction volume has been specified in a parameter in the -r option. · When a device registered as a backup volume has been specified in a parameter in the -r option, the device

has been registered in the backup registration information of a certain transaction volume. If you restore data to a backup volume without registered backup data, and the backup volume is used to back up a certain transaction volume, then data will be overwritten. You are recommended not to specify a backup volume as a restore destination device.

· You perform restoration immediately after performing backup (the actual copying using OPC is in progress). In this case, perform restoration after the actual copying using OPC is completed. Alternatively, on a transaction volume on which a file system has been constructed, perform restoration according to the method described in Points.

· If the SynfinityFILE file system is already mounted before restoration of devices of the SynfinityFILE file system consisting of multiple partitions, unmount the SynfinityFILE file system, and then restore all devices that make up the SynfinityFILE file system.

· A transaction volume in the process of synchronous backup processing is specified. · Any of the cabinet information (cabinet identifier, OLU number, EXTENT start position, and EXTENT size) of a

transaction volume to be restored has been changed. · The mount point set at registration of a transaction volume has been changed. · An SDX object has been specified in a parameter in the -r option.


If the transaction volume is an SDX object, you cannot perform restoration using this command. If so, perform recovery as follows: 1. The backup volume is confirmed by backup history list view/History information display command. 2. copies onto the volume which is restore in the dd command

11.1.2.4 Restore cancellation command (swstcancelrest)

This command cancels OPC-based restoration. If you have executed the restore execution command and while data is copied using OPC, an abnormality due to a hardware error is detected. Then, remove the cause of the hardware error and perform restoration again using the restore execution command (swstrestore).

Check whether an abnormality has occurred using the restore execution status display command (swstreststat).

If you cancel OPC-based restoration using this command, the transaction volume will be in an incomplete status and can no longer be used because part of the data has already been copied. Perform restoration again using the restore execution command (swstrestore).

The restoration cannot be canceled by using this command for the transaction volume to operate the SP series. a. Specification method

- Canceling restore processing for the specified business volume [To be executed on a storage server] # /opt/FJSVswsts/bin/swstcancelrest [-g Generation-No | -v Version-No] [-r Restore-Device-Name] Device-Name

209

[To be executed on a storage management server] # /opt/FJSVswsts/bin/swstcancelrest [-h Server] [-g Generation-No | -v Version-No] [-r Restore-Device-Name] Device-Name




-g

Specifies the relative generation number of data being restored.

This option cannot be specified at the same time as the -v option.

Check the relative generation number using the restore execution status display command (swstreststat).

-v

Specifies the absolute generation number of data being restored.

This option cannot be specified at the same time as the -g option.

Check the absolute generation number using the restore execution status display command (swstreststat).

-r

Specifies the device name if data is restored to any other device than a transaction volume.

Check the device name using the restore execution status display command (swstreststat).

In the case of the operating volume of SymfoWARE, it cannot specify. Note: The restoration of the latest history information will be canceled if neither the -g or -v option is specified.


Device-Name





e. Execution example Cancel restore processing of a transaction volume (/dev/dsk/c1t0d0s6). # /opt/FJSVswsts/bin/swstcancelrest -g 1 /dev/dsk/c1t0d0s6 /dev/dsk/c1t0d0s6 swstcancelrest completed. #

Cancel restore processing of a business volume in operation with SP-series devices. # /opt/FJSVswsts/bin/swstcancelrest -g 1 /dev/dsk/c1t1d0s6

/dev/dsk/c1t1d0s6 swstcancelrest completed.

#

You cannot cancel restoration if: · The history specified in the -g or -v option does not exist. · Restoration is not performed on the device specified in the -r option. · Restoration is not performed from the specified history. In this case, processing is terminated with an

information message "swst0303 Restoration for specified restoration device is not performed". (The end status is a normal end.)

210


11.1.2.5 Restore execution status display command (swstreststat)

This command displays the execution status of restoration.

Information on the execution situation is not displayed for the transaction volume to operate the SP series.

Do not use the OPC stop function of GRmgr while the snapshot fast backup is in progress. If you use the OPC stop function of GRmgr, this command displays "succeeded" whether or not the restoration has actually been successful. a. Specification method

- Displaying the restore processing status by specifying a business volume


# /opt/FJSVswsts/bin/swstreststat [-g Generation-No | -v Version-No] [Device-Name]


# /opt/FJSVswsts/bin/swstreststat [-h Server ] [-g Generation-No | -v Version-No] [Device-Name]

b. Description of options

Option Description



-g Specifies the relative generation number of data whose restore execution status should be displayed.

-v Specifies the absolute generation number of data whose restore execution status should be displayed.

Note: The restore execution statuses of all the history will be displayed if both the -g and -v options are omitted.


Device-Name



If this operand is omitted, the restore execution statuses of all the transaction volumes will be displayed.



e. Execution example

211

Display the restore processing status of transaction volumes. # /opt/FJSVswsts/bin/swstreststat

Server Transaction-Disk Generation Version Backup-Disk Restore-Disk Status Execute

Work 2 /dev/dsk/c1t0d0s3 1 10 /dev/dsk/c1t0d2s3 /dev/dsk/c1t0d1s3 executing 75%

Work 2 /dev/dsk/c1t0d0s4 ---- ---- ---- ---- ---- ----

Work 2 /dev/dsk/c1t0d0s5 2 12 /dev/dsk/c1t0d2s5 ---- succeeded ---

Work 2 /dev/dsk/c1t0d0s6 3 13 /dev/dsk/c1t0d2s6 /dev/dsk/c1t0d1s6 executing 75%

:

# Display the restore processing status of transaction volumes in operation with SP-series. # /opt/FJSVswsts/bin/swstreststat

Server Transaction-Disk Generation Version Backup-Disk Restore-Disk Status Execute

Work 2 /dev/dsk/c1t1d0s3 ---- ---- ---- ---- ---- ----

Work 2 /dev/dsk/c1t1d0s4 ---- ---- ---- ---- ---- ----

:

# The following information will be displayed. Title Description


Transaction-Disk Displays the device name of a transaction volume.

Generation Displays the relative generation number of restored backup data.

"----" will be displayed if no generation number is specified in the -g or -v option and no history being restored exists.

Version Displays the absolute generation number of restored backup data.

"----" will be displayed if no generation number is specified in the -g or -v option and no history being restored exists.

Backup-Disk Displays the name of a backup volume from which data should be copied and restored.

"----" will be displayed if restoration is not in progress.

Restore-Disk

Displays a restore target device name unless data is copied and restored to a transaction volume.

"----" will be displayed if restoration is not in progress or data is restored to a transaction volume.

Status

Displays an execution status. · "----": No copying using OPC is in progress. · "executing": Copying using OPC is in progress. · "succeeded": Copying using OPC has been completed. · "failed": Copying using OPC has been interrupted due to an error. · "halt": Copying using OPC has been halt status.


212

If "failed" is displayed in the "Status" field, a hardware error may have occurred. After removing the cause of the hardware error, use the restore cancellation command (swstcancelrest) to cancel restoration.

If no generation number has been specified in the -v or -g option, the restore execution statuses of all the history will be displayed. If, at this time, restoration is not in progress from any of the history, "----" will be displayed in all the information fields other than "Server" and "Transaction-Disk".

11.1.2.6 History information display command (swsthistdisp)

This command displays history information that has been backed up.

Backup history information is not displayed for the transaction volume to operate the SP series. a. Specification method

- Displaying the backup history information by specifying a business volume [To be executed on a storage server] # /opt/FJSVswsts/bin/swsthistdisp [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swsthistdisp [-h Server] [Device-Name]




Operand Description

Device-Name



If this operand is omitted, the backup history information of all the transaction volumes will be displayed.



e. Execution example Display the backup history information of all the transaction volumes. # /opt/FJSVswsts/bin/swsthistdisp

Server=StrgSV01 Device=/dev/dsk/c1t0d0s6 Mount-Point=/mnt/Tran1 (ufs)

Generation Version Backup-Date Backup-Device Status Execute

1 10 2000/11/12 22:00 /dev/dsk/c1t0d2s6 Succeeded ----

2 9 2000/11/11 22:00 /dev/dsk/c1t0d4s6 Succeeded ----

:

# Display the backup history information of transaction volumes in operation with SP-series devices.

213

# /opt/FJSVswsts/bin/swsthistdisp

Server=StrgSV01 Device=/dev/dsk/c1t1d0s3 Mount-Point=/mnt/Tran1 (ufs)

:



Device Displays a device name.

Mount-Point Displays the mount point name of the device and the file system type in parentheses.

Generation Displays a relative generation number.

This item will not be displayed if no backup history information exists.

Version Displays an absolute generation number.


Backup-Date Displays a date at which backup has been completed.


Backup-Device Displays the name of a backup volume to which data has been backed up.


Status

Displays an actual copying execution status using one of the following character strings. · "succeeded": Copying using OPC has been completed. · "executing": Copying using OPC is in progress. · "failed": Copying using OPC has been interrupted due to an error. · "halt": Copying using OPC has been halt status. This item will not be displayed if no backup history information exists.



ArcSerial

The archive log serial number is displayed

"Reference" is displayed for history information backed up by the reference dump.

When backup history information does not exist, the archive log serial number is not displayed.

If "failed" is displayed in the "Status" field, a hardware error may have occurred. After removing the cause of the hardware error, use the history deletion command (swsthistdel) to delete the backup history information.

11.1.2.7 History information deletion command (swsthistdel)

This command deletes back history information.

If the history information display command displays "failed" in the "Status" field, a hardware error may have occurred. After removing the cause of the hardware error, use this command to delete backup history information. a. Specification method

- Deleting backup history information by specifying a business volume [To be executed on a storage server]

214

# /opt/FJSVswsts/bin/swsthistdel -g Generation-No| -v Version-No | -z Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swsthistdel [-h Server] -g Generation-No| -v Version-No | -z Device-Name




-g

Specifies the relative generation number of backup history information to be deleted.

This option cannot be specified at the same time as the -v or -z.

Check the relative generation number using the history information display command (swsthistdisp).

-v

Specifies the absolute generation number of backup history information to be deleted.

This option cannot be specified at the same time as the -g or -z.

Check the absolute generation number using the history information display command (swsthistdisp).

-z Specifies to delete all the backup history information.

This option cannot be specified at the same time as the -g or -v. c. Description of operand

Operand Description

Device-Name





e. Execution example Delete the backup history of absolute generation number 10 in a transaction volume (/dev/dsk/c1t0d0s6). # /opt/FJSVswsts/bin/swsthistdel -v 10 /dev/dsk/c1t0d0s6 /dev/dsk/c1t0d0s6 swsthistdel completed #

You cannot delete backup history information if: · The backup history information specified in the -g or -v option does not exist. · The specified backup history information is used in restoration.


11.1.2.8 Backup synchronous processing start command (swststartsync)

This command starts backup synchronous processing (starts disk-to-disk copy using EC). a. Specification method

215

- Starting synchronous backup processing by specifying a business volume


# /opt/FJSVswsts/bin/swststartsync Device-Name [-Xdevmap Device-Map-File]


# /opt/FJSVswsts/bin/swststartsync [-h Server] Device-Name [-Xdevmap Device-Map-File]

b. Description of options

Option Description

-h Specify the name of a Storage server.

This option can be specified only on the Storage management server.

-Xdevmap

Specifies a target backup volume to perform the backup synchronous processing. In the operand, specify a device map file in which a combination of a transaction volume and a target backup volume is described. If this option is not specified, the target backup volume will be automatically selected. To execute this command on a remote basis using the -h option, specify a device map file (of a storage server) using an absolute pathname. A file name specified in Device-Map-File must not include any national character.


Device-Name


Specify the name of a block device


= 0: Normally terminated > 0: Abnormally terminated

e. Execution example Start synchronous backup processing of a transaction volume (/dev/dsk/c1t0d0s6). # /opt/FJSVswsts/bin/swststartsync /dev/dsk/c1t0d0s6 /dev/dsk/c1t0d0s6 swststartsync completed. #

Start synchronous backup processing of transaction volumes in operation with SP-series devices. # /opt/FJSVswsts/bin/swststartsync /dev/dsk/c1t1d0s6

/dev/dsk/c1t1d0s6 swststartsync completed.

#

When you execute the backup synchronous processing start command for a transaction volume or log group to which the backup synchronous processing is being executed, the message, "swst0301 Backup synchronous processing is being executed." (for a log group, the message ID is swst0302) is output and then the command is terminated normally.

You cannot start backup synchronous processing in the following cases. In any of the cases below, take an action according to the "System administrator response" message. · When specifying a device that does not support the EC function.

216

· When the backup volumes required to start backup synchronous processing cannot be obtained. · When specifying a device that is being restored by OPC. · When mounting the backup volume to which data is copied.

When any of the following commands is running, this command cannot be executed: · Resource match command (swstsrsemtch) · Storage server configuration information setting command (swstsvrset) · Device information setting command (swstdevinfoset) · Resource backup command (swstresback) · Resource restore command (swstresrst)

11.1.2.9 Backup synchronous processing cancel command (swstcancelsync) This command cancels backup synchronous processing.

If the system detects an error while backup synchronous processing is being executed, the copying being performed at that time terminates abnormally. In such a case, use this command to cancel the backup synchronous processing. Use the backup synchronous processing progress display command (swstsyncstat) to check for the error. a. Specification method

- Canceling synchronous backup processing by specifying a business volume [To be executed on a storage server] # /opt/FJSVswsts/bin/swstcancelsync Device-Name [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstcancelsync [-h Server] Device-Name



This option can be specified only with a Storage management server. c. Description of operand

Operand Description

Device-Name





e. Execution example Cancel synchronous backup processing of a transaction volume (/dev/dsk/c1t0d0s6). # /opt/FJSVswsts/bin/swstcancelsync /dev/dsk/c1t0d0s6 /dev/dsk/c1t0d0s6 swstcancelsync completed. #

Cancel synchronous backup processing of transaction volumes in operation with SP-series devices. # /opt/FJSVswsts/bin/swstcancelsync /dev/dsk/c1t1d0s6

/dev/dsk/c1t1d0s6 swstcancelsync completed.

#

This command cannot be executed when any of the following commands is running: · Resource match command (swstsrsemtch) · Device information setting command (swstdevinfoset)

217

· Storage server configuration information setting command (swstsvrset) · Resource backup command (swstresback) · Resource restore command (swstresrst)

11.1.2.10 Backup synchronous processing progress display command (swstsyncstat)

This command displays the status of the backup synchronous processing.

Information on execution situation is not displayed for the transaction volume to operate the SP series. a. Specification method

- Displaying the synchronous backup processing status of a business volume [To be executed on a storage server] # /opt/FJSVswsts/bin/swstsyncstat [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstsyncstat [-h Server] [Device-Name]



This option can be specified only with the Storage management server. c. Description of operand

Operand Description

Device-Name



When you omit the device name, the system displays the status of backup synchronous processing for all of the transaction volumes.



e. Execution example Display the synchronous backup processing status of a transaction volume (/dev/dsk/c1t0d0s6). # /opt/FJSVswsts/bin/swstsyncstat /dev/dsk/c1t0d0s6


Work 1 /dev/dsk/c1t0d0s6 /dev/dsk/c1t0d2s6 executing 75%

# Display the synchronous backup processing status of all business volumes. # /opt/FJSVswsts/bin/swstsyncstat


Work 1 /dev/dsk/c1t0d0s3 /dev/dsk/c1t0d2s3 executing 75%

Work 1 /dev/dsk/c1t0d1s5 /dev/dsk/c1t0d3s5 equivalent 100%

Work 1 /dev/dsk/c1t0d0s6 /dev/dsk/c1t0d2s6 failed ----

Work 1 /dev/dsk/c1t0d1s4 ---- ---- ----

# Display information about a transaction volume (/dev/dsk/c1t1d5s6) in operation with SP-series devices. # /opt/FJSVswsts/bin/swstsyncstat /dev/dsk/c1t1d5s6


218

Work 2 /dev/dsk/c1t1d5s6 ---- ---- ----

# The table below lists the meaning of each title. Title Description

Server Indicates the name of the Storage server.

Transaction-Disk Indicates the name of the transaction volume.

Backup-Disk Indicates the name of the backup volume.

When backup synchronous processing is not being executed, the system displays "----".

Status

Indicates the status of backup synchronous processing: · "----": Backup synchronous processing is not being executed. · "executing": Backup synchronous processing is being executed but

equivalency maintain status has not been established. · "equivalent": Equivalency maintain status is established. · "failed": Backup synchronous processing was abnormally terminated. · "nosession": No session exists (inconsistent resource information). · "halt": Backup synchronous processing is being halt status.

Execute

Indicates the progress of the backup synchronous processing as a percentage (0 to 100%).

When backup synchronous processing is not being executed, the system displays "----".

If "failed" or "halt" is indicated as the status of the backup synchronous processing (in the Status field), a hardware failure is considered. First eliminate the hardware failure, then execute the backup synchronous processing cancel command (swstcancelsync) to cancel the backup synchronous processing executed.

If "nosession" is indicated as the status of the backup synchronous processing (in the Status field)," resource information having inconsistency is considered. Use the resource match command (swstsrsemtch) to remove the inconsistency from the resource information.

11.1.2.11 Execution status display command (swstexecstat)

This command displays the execution status of other commands executed on a transaction volume. The execution status of OPC/EC will be displayed if OPC/EC is being executed.

Information on execution situation is not displayed for the transaction volume to operate the SP series. a. Specification method

- Displaying the execution status by specifying a business volume [To be executed on a storage server] # /opt/FJSVswsts/bin/swstexecstat [-j] [Device-Name] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstexecstat [-h Server] [-j] [Device-Name]


219



-j Specifies to display information in another format. c. Description of operand

Operand Description

Device-Name



If this operand is omitted, the execution statuses of all the transaction volumes will be displayed.



e. Execution example Display the execution statuses of transaction volumes. # /opt/FJSVswsts/bin/swstexecstat Server Device Last-Backup-Date Interval Status Mount-Point (Method) Execute Work 1 /dev/dsk/c1t0d0s3 2000/12/11 12:20 OK IDLE /usr1 (ufs) ---- Work 1 /dev/dsk/c1t0d0s4 2000/12/10 12:20 DELAY=1 EXEC /usr2 (ufs) sync(22%) Work 1 /dev/dsk/c1t0d0s5 2000/12/09 12:20 DELAY=2 EXEC /usr3 (ufs) snapshot(45%) : #

Display the execution status of transaction volumes in operation with SP-series devices. # /opt/FJSVswsts/bin/swstexecstat

Server Device Last-Backup-Date Interval Status Mount-Point (Method) Execute

Work 3 /dev/dsk/c1t1s0s3 ----/--/-- --:-- ---- IDLE /mnt/usr1 (ufs) ----

Work 3 /dev/dsk/c1t1s0s4 ----/--/-- --:-- ---- IDLE /mnt/usr2 (ufs) ----

:



Device Displays a StorageMGR device name.

Last-Backup-Date Displays the last backup date.

* Displays the time when the backup execution command was accepted.

Interval

Displays how many days have passed after the specified number of interval days since the last backup date has been exceeded. This item will be displayed as "DELAY=number-of-days-passing". "OK" will be displayed if the number of interval days has not been exceeded.

Status

Displays whether any of the following commands is being executed on a transaction volume. If so, "EXEC" will be displayed. Otherwise, "IDLE" will be displayed. · Backup policy setting command (swstbkpolset) · Backup policy deletion command (swstbkpoldel) · Backup execution command (swstbackup) · Restore execution command (swstrestore) · History information deletion command (swsthistdel) · Backup synchronous processing start command (swststartsync) · Backup synchronous processing cancel command

(swstcancelsync) · Restore cancellation command (swstcancelrest)

220

Mount-Point(Method) Displays the mount point name of a transaction volume and FStype in parentheses.

Execute

Displays the name of a command being executed or the copying progress ratio. · "----": Neither a command or OPC/EC is being executed. · "swststartsync": Backup synchronous processing start command is

being executed. · "swstcancelsync": Backup synchronous processing cancel

command is being executed. · "swstbackup": The backup execution command is being

processed. · "swstrestore": The restore execution command is being processed. · "swstcancelrest": The restore cancellation command is being

processed. · "swstbkpolset": The backup policy setting command is being

processed. · "swstbkpoldel": The backup policy deletion command is being

processed. · "swsthistdel": The history information deletion command is being

processed. · "swstcancelrest": The restore cancellation command is being

processed. · "sync(xxx%)": How far the EC operation has progressed. · "sync(failed)": EC has been abnormally terminated. · "sync(halt)": EC has been halt status. · "snapshot(xxx%)": Progress ratio of backup using OPC · "snapshot(failed)": Backup using OPC has abnormally terminated. · "snapshot(halt)": Backup using OPC has been halt status. · "restore(xxx%)": Progress ratio of restoration using OPC · "restore(failed)": Restoration using OPC has abnormally

terminated. · "restore(halt)": Restoration using OPC has been halt status.

If multiple processes are performed on transaction volumes (for example, when the backup synchronous processing start command is issued while a real copy of the snap shot backup is being handled), the display in the Execute field conforms to the following rule:

- The display of a command name takes priority if both copying and command execution are in progress. - When a disk copy of the snap shot backup and a disk copy of the backup synchronous processing are

being handled simultaneously, the progress of the disk copy of the backup synchronous processing is displayed. (A disk copy for restoration is not performed during disk copy of the snap shot backup or backup synchronous processing due to a restriction of the GR series.)

The execution example of using the "-j" option is as follows: # /opt/FJSVswsts/bin/swstexecstat -j

Server Device Execute-Date Status Mount-Point (Method) Execute

Work 1 /dev/dsk/c1t0d0s3 2000/12/11 12:20 IDLE /usr1 (ufs) ----

Work 1 /dev/dsk/c1t0d0s4 2000/12/10 12:20 EXEC /usr2 (ufs) sync(22%)

Work 1 /dev/dsk/c1t0d0s5 2000/12/9 12:20 EXEC /usr3 (ufs) snapshot(45%)

:



Device Specifies a StorageMGR device name.

Execute-Date Displays the command execution time.

Status

Displays whether any of the following commands is being executed on a transaction volume. If so, "EXEC" will be displayed. Otherwise, "IDLE" will be displayed. · Backup policy setting command (swstbkpolset)

221

· Backup policy deletion command (swstbkpoldel) · Backup execution command (swstbackup) · Restore execution command (swstrestore) · History information deletion command (swsthistdel) · Backup synchronous processing start command (swststartsync) · Backup synchronous processing cancel command

(swstcancelsync) · Restore cancellation command (swstcancelrest)

Mount-Point(Method) Displays the mount point name of a transaction volume and FStype in parentheses.

Execute

Displays the name of a command being executed or the copying progress ratio. · "----": Neither a command or OPC/EC is being executed. · "swststartsync": Backup synchronous processing start command is

being executed. · "swstcancelsync": Backup synchronous processing cancel

command is being executed. · "swstbackup": The backup execution command is being

processed. · "swstrestore": The restore execution command is being processed. · "swstcancelrest"": The restore cancellation command is being

processed. · "swstbkpolset": The backup policy setting command is being

processed. · "swstbkpoldel": The backup policy deletion command is being

processed. · "swsthistdel": The history information deletion command is being

processed. · "swstcancelrest": The restore cancellation command is being

processed. · "sync(xxx%)": How far the EC operation has progressed. · "sync(failed)": EC has been abnormally terminated. · "sync(halt)": EC has been halt status. · "snapshot(xxx%)": Progress ratio of backup using OPC · "snapshot(failed)": Backup using OPC has abnormally terminated. · "snapshot(halt)": Backup using OPC has been halt

status."restore(xxx%)": Progress ratio of restoration using OPC · "restore(failed)": Restoration using OPC has abnormally

terminated. · "restore(halt)": Restoration using OPC has been halt status.

If "sync (failed),", "snapshot(failed)", or "restore(failed)", "sync (halt)", "snapshot(halt)" or "restore(halt)" is displayed in the "Execute" field, a hardware error may have occurred. After removing the cause of the hardware error, do as follows: · For "sync (failed)" · Execute the backup synchronous processing cancel command (swstcancelsync) to cancel the backup

synchronous processing. · If "snapshot(failed)" is displayed

Delete backup history information using the history information deletion command. · If "restore(failed)" is displayed

Cancel restoration using the restore cancellation command (swstcancelrest).

11.1.3 Maintenance commands

This chapter describes maintenance commands for backup management.

To operate backup management, use the following maintenance commands:


Resource match command swstsrsemtch Recovers the consistency of information in a backup management

list.

222

Resource backup command swstresback Backs up a backup management list and a recovery control file.

Resource restore command swstresrst Restores a backup management list and a recovery control file.

Resource migration command swstresconv Moves resources of StorageMGR 5.0 to the StorageMGR 5.1

operating environment.

11.1.3.1 Resource match command (swstsrsemtch)

This command makes recovery to make resource information consistent if a system failure, etc. has made the resource information inconsistent. a. Specification method

[To be executed on a storage server] # /opt/FJSVswsts/bin/swstsrsemtch [-x] [To be executed on a storage management server] # /opt/FJSVswsts/bin/swstsrsemtch [-x] [-h Server]

b. Description of operands Operand Description

-h Specifies a storage server name.This option can be specified only on a storage management server.

-x Gets consistency with a repository. Specify this option if the consistency between a backup management list and a repository comes to be inconsistent.

c. Execution example # /opt/FJSVswsts/bin/swstsrsemtch swstsrsemtch completed #


· Device information setting command (swstdevinfoset) · Backup policy setting command (swstbkpolset) · Backup policy deletion command (swstbkpoldel) · Backup synchronous processing start command (swststartsync) · Backup synchronous processing cancel command (swstcancelsync) · Backup execution command (swstbackup) · Restore execution command (swstrestore) · Restore cancellation command (swstcancelrest) · History information deletion command (swsthistdel) · Storage server configuration information setting command (swstsvrset)

11.1.3.2 Resource backup command (swstresback)

This command backs up a recovery control file to a specified directory. A recovery control file is created when the control resource information such as storage server configuration information are backed up. a. Specification method

# /opt/FJSVswsts/bin/swstresback Backup-Directory b. Description of operand

Operand Description

Backup-Directory Specifies the name of a directory to which resource control information should be saved.

c. Execution example Create backup copies of the backup management log and recovery control file in /home/backup. # /opt/FJSVswsts/bin/swstresback /home/backup swstresback completed

223

#

You cannot perform backup if:

· The specified directory does not exist. · Copying of data to the specified directory failed because of insufficient free space, etc.


· Device information setting command (swstdevinfoset) · Backup policy setting command (swstbkpolset) · Backup policy deletion command (swstbkpoldel) · Backup synchronous processing start command (swststartsync) · Backup synchronous processing cancel command (swstcancelsync) · Backup execution command (swstbackup) · Restore execution command (swstrestore) · Restore cancellation command (swstcancelrest) · History information deletion command (swsthistdel) · Storage server configuration information setting command (swstsvrset)

11.1.3.3 Resource restore command (swstresrst)

The recovery control file made when the data base space of the backup management list is backed up is restored from the specified directory. a. Specification method

# /opt/FJSVswsts/bin/swstresrst Backup-Directory b. Description of operand

Operand Description

Backup-Directory Specify the name of the directory to which to save the backup management log and recovery control file.

c. Execution example Create backup copies of the backup management log and recovery control file in /home/backup. # /opt/FJSVswsts/bin/swstresrst /home/backup swstresrst completed #

You cannot perform restoration if:

· The specified directory does not exist. · No backup management list exists in the specified directory. · Copying of data from the specified directory for restoration failed because of insufficient free

space, etc.


· Device information setting command (swstdevinfoset) · Backup policy setting command (swstbkpolset) · Backup policy deletion command (swstbkpoldel) · Backup synchronous processing start command (swststartsync) · Backup synchronous processing cancel command (swstcancelsync) · Backup execution command (swstbackup) · Restore execution command (swstrestore) · Restore cancellation command (swstcancelrest) · History information deletion command (swsthistdel)

224

· Storage server configuration information setting command (swstsvrset)

11.1.3.4 Resource migration command (swstresconv)

To succeed the environment of SystemWalker/StorageMGR 5.0 to SystemWalker/StorageMGR 5.1 when shifting from SystemWalker/StorageMGR 5.0 to SystemWalker/StorageMGR 5.1, this command is executed only once. Please refer to "Shift from appendix D old version" for details of the shift procedure. a. Specification method

# /opt/FJSVswsts/bin/swstresconv b. Execution example

# /opt/FJSVswsts/bin/swstresconv swstresconv completed #

11.2 Configuration Management Commands

This chapter describes operations using configuration management commands.

11.2.1 Server information change command (stgcmmodnode)

This command changes the server change information of the Storage management server. Concretely, execute this command for the following purposes: · To change the IP address of the Storage management server or the PORT number (stgxfws) used by the

communication daemon Follow the procedure below:

1. Change server information by executing this command on the Storage management server. 2. Change server information of the Storage management server by executing this command on every Storage

server. This command must be executed on all Storage servers managed by the Storage management server. · To change the server name of the Storage management server

Follow the procedure below: 1. Change the server name from the initial window of the Storage management server. 2. Change the server name of the Storage management server by executing this command on every Storage

server. This command must be executed on all Storage servers managed by the Storage management server. This command has the following two functions: · Displays storage management server information specified on the storage server on which this command is

currently executed · Changes storage management server information. a. Specification method

# /opt/FJSVswstf/bin/stgcmmodnode [-i IP-address] [-p PORT number] [-n server name]


None Displays the server information currently managed.

-i Specifies the IP address of a storage management server to change the IP address of the storage management server.

-p Specifies the port number of a storage management server to change the port number of the storage management server.

-n Specifies the server name of a storage management server to change the server name of the storage management server. This option cannot be specified if this command is executed on a storage management server.


d. Execution example Display server information. # /opt/FJSVswstf/bin/stgcmmodnode swstf2413 IP Addoress = 10.10.10.10 swstf2413 PORT Number = 1226 swstf2413 Storage Management Server's Name = fujitsu-storage-management-server #

Change the IP address of a storage management server to 10.12.13.14.

225

# /opt/FJSVswstf/bin/stgcmmodnode -i 10.12.13.14

swstf2401 StorageMGR registry updated.

The following lists notes on this command.

· This command can be executed only by root users. · As the PORT number of a storage management server, you can specify a value between 1 and

65535. · In this command, specify the same value as the one specified on a storage management server.

A error will occur in the operation if an invalid value is specified. · If this command is executed, restart the StorageMGR daemons.

11.2.2 Repository access user change command (stguserset)

This command changes a user name and/or password used to access a repository. This command must be executed on the Storage management server.

The change in the user-name and the password is executed according to the following procedures. 1. Close Web browser of StorageMGR. 2. Execute Repository access user change command (stguserset). 3. Stop StorageMGR daemons. 4. Start StorageMGR daemons. a. Specification method

# /opt/swstorage/bin/stguserset user-name password b. Description of options

Option Description

User name Specifies a user name to be used for repository access.

Password Specifies a user password to be used for repository access. c. End status


d. Execution example Change the user name and the password to be used for repository access to a1234 and Yfd1fz3, respectively. # /opt/swstorage/bin/stguserset a1234 Yfd1fz3

Password for accessing the repository has been registered.

The following lists notes on this command.

· This command can be executed only by root users.

11.3 Replication Management Command

This chapter describes operations using Replication Management Commands

11.3.1 Environment definition commands

This chapter describes environment definition commands for replication management. To define a replication management environment, use the following commands:


Replication volume information setting command swsrpsetvol Sets the information about a replication

volume.

Replication volume information display command swsrpvolinfo Displays the information about a replication

volume.

Replication volume information deletion command swsrpdelvol Deletes replication volume information that

has been set.

226

11.3.1.1 Replication volume information setting command (swsrpsetvol)）

This command sets the replication source and replication destination volumes that will be used in a replication operation. Execute this command to declare that the replication operation will performed using the specified replication volumes. a. Specification method


For replication on a server

/opt/FJSVswsrp/bin/swsrpsetvol [-n] [-u] Original-Volume-Name Replica-Volume-Name

For replication between servers

/opt/FJSVswsrp/bin/ swsrpsetvol [-n] [-u] -o (ORG|REP) Original-Volume-Name Replica-Volume-Name


For replication on a server

/opt/FJSVswsrp/bin/swsrpsetvol -h Server-Name [-n] [-u] Original-Volume-Name Replica-Volume-Name

For replication between servers

/opt/FJSVswsrp/bin/ swsrpsetvol -h Server-Name [-n] [-u] -o (ORG|REP) Original-Volume-Name Replica-Volume-Name


-h

Specifies the name of a storage server subject to the replication operation. This option is valid only on a storage management server.

If this option is omitted, the storage server on which the command is entered will be the target to the processing.

-u

Specifies the direction of copying.

If this option is specified, copying from a replication source volume to a replication destination volume is performed only in this direction. Copying from a replication destination volume to a replication source volume is prohibited.

If this option is omitted, copying between the replication source and replication destination volumes interactively is bidirectional.

-o

Specifies the operation server.

Specify one of the following for this operand:

ORG: Sets the replication source server as the operation server.

REP: Sets the replication destination server as the operation server.

On the server that is not specified as the operation server, only the following commands can be executed for a replication volume:

Replication volume information display command

Operation status display command

Replication cancellation command (The forcible stop option is required.)

This option is valid only for replication between servers.

-n

If this option is omitted, replication volume information cannot be set when the sizes of the replication source volume and replication destination volume are different.

When this option is specified, the sizes of the replication source volume and replication destination volume are not checked. Use this option when volume sizes are different (for example, for replication between different OSs).

When the volume sizes of the replication source volume and replication destination volume are different, copying is performed as follows:

The address at which copying starts is the first sector of the replication destination volume.

227

The copy data size is the size of the smaller volume. c. Description of operands

Operand Description

Original-Volume-Name Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name."

Replica-Volume-Name Specifies a replication destination volume name. For the volume names of other servers, use the format "volume-name@storage-server-name."

d. End status = 0: Normal end > 0: Abnormal end

e. Execution example Set replication volume information by specifying volume/dev/dsk/c1t2d0s3 of storage server SRC-SV as the replication source volume and volume /dev/dsk/c1t2d0s3 of storage server TARG-SV as the replication destination volume. In addition, specify one-way copying for the copy direction and specify the replication source server (SRC-SV) as the operation server. The example below shows the command executed on SRC-SV. # /opt/FJSVswsrp/bin/swsrpsetvol -u -o ORG /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3@TARG-SV swsrpsetvol completed #

When the same settings are made from TARG-SV, the example is as follows (be careful with the volume name): # /opt/FJSVswsrp/bin/swsrpsetvol -u -o ORG /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d0s3 swsrpsetvol completed #

Replication volume information cannot be set if: · Replication volume information has already been set. · The specified replication source volume and replication destination volume are set as the replication

destination volume and the replication source volume. · The n option is not specified when the sizes of the replication source volume and the replication destination

volume are different. · Two volumes that have the same cabinet information (cabinet identifier, OLU number, EXTENT start position,

and EXTENT size) as the cabinet information of the specified two volumes have already been set as replication volumes.

· The replication destination volume has been registered as a backup volume of the backup management function.

· The replication source volume has been registered as a backup volume of the backup management function and bi-directional copying is specified as a replication volume attribute.

· A volume belong to another server is specified in the format "volume-name@storage-server-name" in SystemWalker/StorageMGR Standard Edition.

· The specified replication destination volume and replication source volume are volumes belonging to other servers (at least one volume must be a volume on the local server).

· If the replication source volume and the replication destination volume are located on another disk array device, the remote copy function of the disk array device is not correctly set.

· Communication with the storage management server fails. · Communication with a destination server fails for replication between servers.

Note the following points about creating copy source volumes and copy destination volumes: · When creating multiple volumes (slices) on the same disk, volume areas must not overlap. · Create volumes (slices) so that VTOC is not contained in them. · Specify each volume defined in units of slices as a copy source volume or a copy destination volume. Do not

specify any volume defined as an entire disk.

228

When you change physical information on volumes (partition size, drive letter, and cabinet information on a disk array device) using such functions as an OS management tool (for example, Disk Administrator) or GRmgr provided by the disk array device, delete replication volume information and reregister the changed volumes.

When you use a replication destination volume by mounting or by allocating a drive letter after creating a replication, the size of the replication destination volume must exactly match the size of the replication destination volume to the byte. If you do not use a replication destination volume (for example, when you need copy data, you restore it to the replication source volume and then use it), the size of the replication destination volume can be larger than the size of the replication source volume.

This command cannot be executed while any of the following commands is running: · Replication volume information setting command (swsrpsetvol) · Replication volume information deletion command (swsrpdelvol) · Synchronous processing start command (swsrpstartsync) · Replication creation command (swsrpmake) · Replication cancellation command (swsrpcancel) · Operation status display command (swsrpstat) · Resource adjustment command (swsrprecoverres)

11.3.1.2 Replication volume information display command (swsrpvolinfo)

This command displays the replication volume information registered by the replication volume setting command. a. Specification method


/opt/FJSVswsrp/bin/swsrpvolinfo [Original-Volumue-Name]


/opt/FJSVswsrp/bin/swsrpvolinfo -h Server-Name [Original-Volume-Name] b. Description of options

Option Description


This option is valid only on a storage management server. c. Description of operands

Operand Description

Original-Volume-Name

Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name."

Displays all the replication volume information for the specified replication source volume. If this operand is omitted, all the replication volume information existing on the storage server on which this command is executed is displayed.


e. Execution example Direct that all the replication volume information on a storage management server be displayed on storage server SRC-SV. # /opt/FJSVswsrp/bin/swsrpvolinfo -h SRC-SV Server Original-Volume Size Replica-Volume Size Copy Op-Server SRC-SV /dev/dsk/c1t2d0s3@SRC-SV 4.0Gbyte /dev/dsk/c1t2d0s3@TARG-SV 4.0Gbyte uni-direction original SRC-SV /dev/dsk/c1t2d1s3@SRC-SV 4.0Gbyte /dev/dsk/c1t2d1s3@TARG-SV 5.0Gbyte bi-direction original SRC-SV /dev/dsk/c1t2d2s3@SRC-SV 9.1Gbyte /dev/dsk/c1t2d2s3@TARG-SV 9.1Gbte bi-direction replica #

229



Original-Volume Displays a replication source volume name.

Size Displays the volume size.

Replica-Volume Displays a replication destination volume name.

Copy

Displays the copying direction.

uni-direction: One-way copying from a replication source volume to a replication destination volume is allowed.

bi-direction: Bidirectional copying is allowed.

Op-Server

Displays the operation server of a pair of replication volumes.

original: The replication source server is the operation server.

replica: The replication destination server is the operation server.

Replication volume information cannot be displayed if: · The specified volume is not set as a replication source volume

This command cannot be executed while the following command is running: · Resource adjustment command (swsrprecoverres)

11.3.1.3 Replication volume information deletion command (swsrptdelvol) Delete the replication volume information that has been set.

If copy processing is being performed on a replication volume that is to be deleted, execute the command after the copy processing has stopped. a. Specification method


/opt/FJSVswsrp/bin/swsrpdelvol Original-Volume-Name Replica-Volume-Name


/opt/FJSVswsrp/bin/swsrpdelvol -h Server-Name Original-Volume-Name Replica-Volume-Name b. Description of options

Option Description


This option is valid only on a storage management server. c. Operand の Description

Operand Description

Original-Volume-Name Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name."

Replica-Volume-Name Specifies a replication destination volume name. For the volume names of other servers, use the format "volume-name@storage-server-name."


e. Execution example Delete replication volume information on storage server SRC-SV. # /opt/FJSVswsrp/bin/swsrpdelvol /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3@TARG-SV swsrpdelvol completed

230

#

Replication volume information cannot be deleted if: · The specified replication source volume and the replication destination volume are not set as replication

volumes. · The copy processing (synchronization processing and snapshot processing) is performed between replication

volumes. · For server-to-server replication, the storage server that executed the command is not the operation server of

the replication volume. · Communication with a storage management server fails. · For server-to-server replication, communication with a destination server fails.

This command cannot be executed while any of the following commands is running: · Replication volume information setting command (swsrpsetvol) · Replication volume information deletion command (swsrpdelvol) · Synchronous processing start command (swsrpstartsync) · Replication creation command (swsrpmake) · Replication cancellation command (swsrpcancel) · Operation status display command (swsrpstat) · Resource adjustment command (swsrprecoverres)

11.3.2 Operation commands

This chapter describes operation commands for replication management.

To operate replication management, use the following commands:


Synchronous processing start command swsrpstartsync Starts replication while the synchronous type replication function is

performed.

Replication creation command swsrpmake Creates replication while the snapshot type and the synchronous

type replication functions are performed.

Operation status display command swsrpstat Displays the status of replication operation

Replicatio cancellation command swsrpcancel Cancels the replication processing while the snapshot type and the

synchronous type replication functions are performed.

11.3.2.1 Synchronous processing start command (swsrpstartsync)

Start the synchronous type replication processing (copying between disks by EC and REC).

Copy all the specified replication destination and replication source volumes (start of the synchronization processing), or copy (restart of the synchronization processing) updated data (difference). Use this command at the start of operation or when you want to reflect updated data (difference) from the equivalency holding state. a. Specification method


/opt/FJSVswsrp/bin/swsrpstartsync [-y] [-t] [-m] From-Volume-Name To-Volume-Name


/opt/FJSVswsrp/bin/swsrpstartsync -h Server-Name [-y] [-t] [-m] From-Volume-Name To-Volume-Name


-h This option is valid only on a storage management server.


231

-y

Specifies that synchronization processing is started in synchronous write mode (mode in which data is copied to the replication destination volume synchronized with writing to the replication source volume). This option is valid only when total copy for intercabinet replication is started. If this option is omitted, asynchronous write mode (mode in data is copied to the replication destination volume unsynchronized with writing to the replication source volume) is used.

The synchronization processing of intracabinet replication is always performed in synchronous write mode.

-m

For server-to-server replication, specifies that communication processing with non-operation servers is not performed. When this option is specified, volume status check processing and the preprocessing for the replication destination volume of a non-operation server are not performed.

This option is valid only during server-to-server replication.

-t Specifies that preprocessing for the replication destination volume is not performed. c. Description of operands

Operand Description

From-Volume-NameSpecifies a replication source volume name. Specifies the replication source volume or the replication destination volume set with the replication volume information setting command.

To-Volume-Name Specifies a replication destination volume name. Specifies the replication source volume or the replication destination volume set with the copy volume information setting command.


e. Execution example Start replication from /dev/dsk/c12d0s3 of a storage management server to /dev/dsk/c1t2d0s3@TARG-SV of storage server SRC-SV. # /opt/FJSVswsrp/bin/swsrpstartsync -h SRC-SV /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3@TARG-SV

FROM=/dev/dsk/c1t2d0s3@SRC-SV,TO=/dev/dsk/c1t2d0s3@TARG-SV swsrpstartsync completed

#

Replication cannot be started if: · The specified replication source volume and replication destination volume are not set as replication volumes. · A replication source volume is specified as the replication destination volume and a replication destination

volume is specified as the replication source volume, and one-way copy is set as the copy attribute of the replication volume.

· Volume information (medium identifier, OLU, EXTENT start position, and EXTENT size) is changed after operation starts. In this case, operation cannot continue for the corresponding volume. Stop the replication operation for the corresponding volume, and then delete and set the replication volume information.

· For server-to-server replication, the storage server on which the command is executed is not the operation server of the replication volume.

· For server-to-server replication, communication with a destination server fails. · Replication cannot be started as a result of the preceding advanced copy function. For more information about

combinations copy processing that can be executed, see the GR Series SA/SE Handbook.

When the replication to perform corresponds to either of the following conditions, please perform drive character release or unmount of copy place volume before executing a command. · When a replication is performed between different OS's · When the sizes of replication source volume and replication destination volume differ · When the file systems of replication source volume and replication destination volume differ

232

When performing neither drive character release nor unmount in the above-mentioned case, post-processing of the copy place volume at the time of duplicate creation serves as an error.

Now, the replication which makes a SDX object (SynfinityDISK) replication source volume is not supported. Therefore, when one of replication destination volume and the duplicate place volumes is a SDX object, only the replication from a SDX object to a non-SDX object can be used.

Please use the dd command when you copy the slice data to the SDX object. (It is necessary to execute the copy to all physical slices which compose the SDX object.)

The processing of this command varies according to the status of the synchronization processing of the specified replication source and replication destination volumes.

Status of synchronization processing Processing

Unmount status Start of total copy

Total or incremental copy status Abnormal end

Equivalency maintain status Abnormal end

Replication established status (halt status) Start of incremental copy

Before starting the replication, run the replication preprocessing script for the replication destination volume. The contents of this script can be customized. For more information, see Appendix C, Replication Scripts. If you do not want to implement the preprocessing script, use the -t option.

To protect processing that accesses a replication destination volume, set the replication destination volume before starting replication so that other processes cannot access it. To do so, cancel the drive letter of the replication destination volume or execute unmount. If you cannot cancel the drive letter of the replication destination volume or execute unmount because of the situations described below, this command fails and terminates. · There is a directory in which other volumes are mounted under the mount point. · A file on the volume is being used. In addition, if the replication destination volume is being used from a server

other than the server on which this command is entered, the replication-operation administrator must disable access to the replication destination volume by cancellation of the share setting, unmounting, or some other method.

This command cannot be executed while any of the following commands is running: · Replication volume information setting command (swsrpsetvol) · Replication volume information deletion command (swsrpdelvol) · Resource adjustment command (swsrprecoverres)

11.3.2.2 Replication creation command (swsrpmake)

When synchronization processing (EC) is not performed, start snapshot processing (OPC) to create a replication volume.

When synchronization processing is performed, check whether the status of the processing is equivalency holding state. If the status is equivalency holding state, suspend the synchronization processing and create a replication volume. The status in which synchronization processing is suspended is referred to as the replication established status. After this command is executed, the replication volume (replication destination volume) can be accessed.

This command executes the replication preprocessing and postprocessing scripts before a replication is created. For details of these scripts, see Appendix C, "Replication Scripts."

233

a. Specification method [To be executed on a storage server]

/opt/FJSVswsrp/bin/swsrpmake [-f] [-t] [-m] From-Volume-Name To-Volume-Name


/opt/FJSVswsrp/bin/swsrpmake -h Server-Name [-f] [-t] [-m] From-Volume-Name To-Volume-Name




-m

For server-to-server replication, specifies that communication processing with the non-operation server is not performed. When this option is specified, volume status check processing and preprocessing and post processing are not performed for the non-operation server volume.


-f Specifies that the preprocessing and post processing for a replication source volume are not performed.

-t Specifies that the preprocessing and post processing for a replication destination volume are not performed.

c. Description of operands Operand Description

From-Volume-NameSpecifies a replication source volume. Specifies the replication source volume or the replication destination volume that was set with the replication volume information setting command.

To-Volume-Name Specifies a replication destination volume. Specifies the replication source volume or the replication destination volume that was set with the replication volume information setting command.


e. Execution example The Storage management server instructs Storage server: SRC-SV to create a copy of /dev/dsk/c12d0s3 in /dev/dsk/c1t2d0s3@TARG-SV. # /opt/FJSVswsrp/bin/swsrpmake -h SRC-SV /dev/dsk/c1t0d2s3 /dev/dsk/c1t2d0s3@TARG-SV

FROM=/dev/dsk/c1t2d0s3@SRC-SV,TO=/dev/dsk/c1t2d0s3@TARG-SV swsrpmake completed

#

Replication cannot be created if:

· The specified replication source and replication destination volumes are not set as replication volumes.

· The synchronization processing from the specified replication source volume to the replication destination volume is not in the equivalency maintain status.

· After operation starts, physical volume information (medium identifier, OLU, EXTENT start position, and EXTENT size) is changed. In this case, operation for the corresponding volume cannot continue. Stop the replication operation for the volume, and then delete and set the replication volume information.

· A replication source volume or a replication destination volume has multiple mount points. · If a replication source volume is an SDX object (SynfinityDISK), the status of the SDX object

does not match the following: 1. The mirror volume is ACTIVE or STOP. 2. The mirror slice status is ACTIVE or TEMP.

234

3. The SDX disk status is ENABLE. * When the mirror slice is TEMP, a reproduction former volume is not preprocessed.

· When copied material volume or copy place volume constitutes SafeFILE of multi-volume composition and the file system is mounted. In this case, please process all the volumes that perform unmount and constitute SafeFILE.

· For server-to-server replication, the storage server on which the command is executed is not the operation server of the replication volume.

· For server-to-server replication, communication with a destination server fails.

When the replication to perform corresponds to either of the following conditions, please perform drive character release or unmount of copy place volume before executing a command. · When a replication is performed between different OS's · When the sizes of replication source volume and replication destination volume differ · When the file systems of replication source volume and replication destination volume differ When performing neither drive character release nor unmount in the above-mentioned case, post-processing of the copy place volume at the time of duplicate creation serves as an error.

Now, the replication which makes a SDX object (SynfinityDISK) replication source volume is not supported. Therefore, when one of replication destination volume and the duplicate place volumes is a SDX object, only the replication from a SDX object to a non-SDX object can be used.

Please use the dd command when you copy the slice data to the SDX object.(It is necessary to execute the copy to all physical slices which compose the SDX object.)

Before a replication is created, the replication preprocessing and postprocessing scripts for the replication source volume are executed (for synchronized replication, only preprocessing script is executed). After the replication has been created, the replication postprocessing script for the replication source volume and replication destination volume is executed. The contents of the script can be customized. For more information, see Appendix C, "Replication Scripts" If you do not want to implement the preprocessing and postprocessing scripts, use the -f option and the -t option.

If this command is executed during execution of snapshot processing, stop the copy processing in progress and start the snapshot processing again.

To protect the data, set the replication source volume before creating a replication so that other processes cannot access the volume. To do so, cancel the drive letter of the replication source volume or execute unmount. If you cannot cancel the drive letter of the replication source volume or execute unmount because of the situations described below, this command fails and terminates. · There is a directory in which other volumes are mounted under the mount point. · A file on the volume is being used. In addition, if the replication source volume is being used from a server

other than the server on which this command is entered, the backup-operation administrator must disable access to the replication source volume by cancellation of the share setting, unmounting, or some other method. If for whatever reason you do not want to remove the share setting of the replication source volume or execute unmount or some other method, see Appendix C, "Replication Scripts" and note the following.

· When the replication source volume is being used by backup management or space management, unmount may not possible. If so, "swsrp2613 An error occurred on the preprocessing script at replication creation. Error code = 2" is output.

· For replication preprocessing, execute the UNIX sync command to synchronize volumes and the file system. · In replication post-processing, execute the fsck command to check the file system at the copy destination.

235

Copied material volume When you are the volume by which the SafeFILE file system was built, please perform mount of copy place volume in the following procedures.

# The list of RAW device names which constitute sfxadm SafeFILE

# fsck –F sfxfs [-y] Representation RAW device name of SafeFILE

# The representation RAW device name of mount –F sfxfs SafeFILE


11.3.2.3 Operation status display command (swsrpstat)

This command displays the operation status of the specified volume. If a volume is not specified, the operation status of each replication volumes is displayed. a. Specification method


/opt/FJSVswsrp/bin/ swsrpstat [Original-Volume-Name]


/opt/FJSVswsrp/bin/ swsrpstat -h Server-Name [Original-Volume-Name] b. Description of options

Option Description


This option can be specified only on a storage management server. c. Description of operands

Operand Description

Original-Volume-Name

Specifies a replication source volume name. For the volume names of other servers, use the format "volume-name@storage-server-name."

Displays all operation statuses for the specified replication source volume. If this operand is omitted, all the operation statuses of the storage server on which this command is executed are displayed.


e. Execution example Direct that all the replication operation statuses for storage server SRC-SV be displayed on the storage management server. #swsrpstat -h SRC-SV Server Original-Volume Replica-Volume Direction Status Execute SRC-SV /dev/dsk/c1t2d0s3@SRC-SV /dev/dsk/c1t2d0s3@TARG-SV regular replicated ---- SRC-SV /dev/dsk/c1t2d1s3@SRC-SV /dev/dsk/c1t2d1s3@TARG-SV ---- ---- ---- SRC-SV /dev/dsk/c1t2d2s3@SRC-SV /dev/dsk/c1t2d2s3@TARG-SV reverse snap 45% #



Original-Volume Displays a replication source volume name.

Replica-Volume Displays a replication destination volume name.

236

Direction

Displays the copy direction. · regular: Copying from the replication source to the replication

destination is being performed. · reverse: Copying from the replication destination to the replication

source is being performed. · ----: Copying is not performed.

Status

Displays the progress. · ---- : Copying is not being performed. · sync : Total copy or incremental copy is being performed. · equivalent : Equivalency maintain status · replicated : Replication established status · failed : Error suspend status · halt : Hard suspend status · snap : Snapshot processing is being performed. · ????? : NSP information cannot be acquired.

Execute Displays the rate of copying progress as a percentage. When copying is not being performed, "----" is displayed.

When the execution status (status displayed in the Status field) is one of the following, take appropriate action.

Status display Corrective action

Failed A hardware error may have occurred. Correct the hardware error, and then use the replication cancellation command to stop operation.

Halt A hardware error during replication operation between cabinets may occur. Correct the hardware error, and then use the replication cancellation command to stop the copy operation.

????? NSP information cannot be acquired. A hardware error may have occurred if the result is the same after reexecution. Correct the hardware error, and then reexecute the command.

The operation status cannot be displayed if: · The specified replication source and replication destination volumes are not set as replication volumes.

This command cannot be executed while the following command is running: · Resource adjustment command (swsrprecoverres)

11.3.2.4 Replication cancellation command (swsrpcancel)

This command stops snapshot processing (OPC) and synchronization processing (EC) of the specified replication volume. Use this command when an error is detected during the replication operation and when you want to stop replication processing. a. Specification method


/opt/FJSVswsrp/bin/swsrpcancel [-c] [-f] [-t] [-m] From-Volume-Name To-Volume-Name e


/opt/FJSVswsrp/bin/swsrpcancel -h Server-Name [-c] [-f] [-t] [-m] From-Volume-Name To-Volume-Name



237


-c

Specifies that the copy processing is forcibly stopped from a non-operation server when the operation server cannot be used because of a system failure. If this option is used, the copy processing is stopped without implementing preprocessing and postprocessing. If this option is used, a contradiction arises in the synchronization processing management information on the operation server. Therefore, after recovery of the operation server, enter the resource adjustment command on the operation server.

This option cannot be specified on the operation server.

-m

For server-to-server replication, specifies that communication processing with non-operation servers is not performed. When this option is specified, volume status check processing and preprocessing and postprocessing for the replication destination volume of a non-operation server are not performed.


-f Specifies that preprocessing and postprocessing for the replication source volume are not performed.

-t Specifies that preprocessing and postprocessing for the replication destination volume are not performed.

c. Description of operands Operand Description

From-Volume-NameSpecifies a replication source volume name. Specifies the replication source volume or the replication destination volume set with the replication volume information setting command.

To-Volume-Name Specifies a replication destination volume name. Specifies the replication source volume or the replication destination volume set with the copy volume information set command.


e. Execution example On the storage management server, direct that copying from /dev/dsk/c12d0s3 to /dev/dsk/c1t2d0s3@TARG-SV be stopped for storage server SRC-SV. #/opt/FJSVswsrp/bin/swsrpcancel -h SRC-SV /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3@TARG-SV FROM=/dev/dsk/c1t2d0s3@SRC-SV,TO=/dev/dsk/c1t2d0s3@TARG-SV swsrpcancel completed #

Copy processing cannot be performed if: · The specified replication source volume and replication destination volume are not set as replication volumes. · The copy processing is not performed for the specified replication source and replication destination volumes. · For server-to-server replication, the storage server on which the command is executed is not the operation

server of the replication volume. · For server-to-server replication, communication with a destination server fails.

The volume information for the specified volume is not checked (check for matching of the volume information in the management list and the actual physical information). Operation is canceled unconditionally using the volume information in the management list.

The following processing is performed depending on the operation status of the specified replication source volume and replication destination volume.

238

Operation status Processing

Reverse copy direction Suspends the processing.

Not operating yet Suspends the processing.

Total or incremental copy is performed

Suspends synchronization processing. The replication destination volume cannot be used.

Equivalency maintain status

Suspends synchronization processing. The replication destination volume can be used as a copy

Replication established status

Suspends synchronization processing. The replication destination volume can be used as a copy

Snapshot processing is being performed

Stops the snapshot processing. The replication destination volume cannot be used.

Preprocessing and postprocessing for a replication source and replication destination volumes are performed only when the status of synchronization processing is equivalency maintain.

Synchronization processing cannot be stopped in equivalency maintain status if:

· A replication source volume or a replication destination volume has multiple mount points. · When a replication source volume is an SDX object (SynfinityDISK), the status of the SDX

object is not one of the following: 1. The mirror volume is ACTIVE or STOP. 2. The mirror slice status is ACTIVE or TEMP. 3. The SDX disk status is ENABLE.

* When the mirror slice is TEMP, a reproduction former volume is not preprocessed. · When copied material volume or copy place volume constitutes SafeFILE of multi-volume

composition and the file system is mounted. In this case, please process all the volumes that perform unmount and constitute SafeFILE.


11.3.3 Maintenance commands

This chapter describes the maintenance commands for replication management.

Use the following maintenance commands for replication management.


Resource adjustment command swsrprecoverres Restores the consistency of information in a replication

management list.

11.3.3.1 Resource adjustment command (swsrprecoverres)

This command executes recovery to make replication management information consistent if a system failure or other problem has made the replication management information inconsistent. a. Specification method

239


/opt/FJSVswsrp/bin/ swsrprecoverres [-r] [-p] [-s]


/opt/FJSVswsrp/bin/ swsrprecoverres -h Server-Name [-r] [-p] [-s] b. Description of operands

Operand Description


This option can be used only on a storage management server.

-r

Specify this option when an incorrect status exists in the replication management list (for example, the replication volume information setting command or the replication volume information deletion command that update the replication management list terminate suddenly because of a forced stop or a system failure, or the replication management list has been deleted by mistake).

When this option is specified, the following processing to re-create the replication management list is performed.

Replication management information in the storage management server repository is downloaded to the storage server, and the replication volume information is restored.

The disk array device is queried, and the execution information for the synchronization processing is restored. (The processing with the -s option specified is performed. This option includes -s option processing.)

-p Specifies not to perform any postprocessing that has not been performed. This option can be used when the replication creation command processing terminates suddenly because of a forced stop or system failure.

-s

Specify this operand when the replication management list containing synchronization processing information has been deleted by mistake.

Querying the disk array device enables the execution information for synchronization processing to be restored.

In addition, when you use the -r option, you do not need to specify this option since specifying "-r -s" is the same as specifying "-r").


d. Execution example Perform resource adjustment. #/opt/FJSVswsrp/bin/swsrprecoverres swsrprecoverres completed #

The resource adjustment processing cannot be performed if: · Communication with a server fails, even though postprocessing that has not been performed must be

performed on the server. · Communication with a storage management server fails and the -r option is specified. · The -r option is not specified when this command is executed after processing by the replication volume

information setting command and the replication volume information deletion command has been forcibly terminated.

The consistency of resource information is restored only for the storage server on which this command is executed. When a resource inconsistency occurs during processing related to replication between servers, this command must be executed both on the storage server on which the processing was performed and on the storage server with which communication is being made.

240

This command cannot be executed while any of the following commands is running: · Replication volume information setting command (swsrpsetvol) · Replication volume information display command (swsrpvolinfo) · Replication volume information deletion command (swsrpdelvol) · Synchronous processing start command (swsrpstartsync) · Replication creation command (swsrpmake) · Replication status display command (swsrpstat) · Replication cancellation command (swsrpcancel) · Resource adjustment command (swsrprecoverres)

11.4 SAN Resource Management Command

This chapter describes operations that use the SAN resource management commands.

11.4.1 SAN resource management command line interface

SAN resource management supports the command line interface. For more information, see chapter 4.9, "Command Line Interface (CLI)" in the User's Guide.

11.4.2 Starting CIMOM

Enter the following command to start CIMOM:

# /opt/FJSVswsam/bin/cimserver start

(*1 CIMOM stops if the console used to start CIMOM is quitted. To prevent this event from occurring, start CIMOM from the console used to start /usr/bin/csh.)

11.4.3 Stopping CIMOM

Enter the following command to stop the CIMOM:

# /opt/FJSVswsam/bin/cimserver stop

11.4.4 SNMP TRAP test

Use the following commands to check whether SNMP TRAP is set correctly. Executing these commands creates a dummy SNMP TRAP (fan fault for GR and port fault for a switch) and issues it to the SAN resource administrator.

Create a dummy error related to GR that is registered in SAN resource management

# /opt/FJSVswsam/bin/grtraptest IP-address-of-GR

Create a dummy error related to a switch that is registered in SAN resource management

# /opt/FJSVswsam/bin/swtraptest IP-address-of-a-switch

11.4.5 SystemWalker/CentricMGR icon setup commands

Executing these commands on the SystemWalker/CentricMGR operation management server and a operation management client sets up an environment that includes an icon that links to SystemWalker/CentricMGR.

11.4.5.1 Operation management setup command

Execute this command on the SystemWalker/CentricMGR operation management server.

This command sets up a node and event type icon (for PC clients and web clients), and sets up MIB information for each node type. a. Specification method cd Mount-point-of-CD-ROM/solaris/centric

./manset.sh

241

The following are notes on this command: · This command can be executed only by root users. · SystemWalker/CentricMGR must have been started.

11.4.5.2 Operation management client setup command (cliset.exe)

Execute this command on the SystemWalker/CentricMGR operation management client.

Executing this command sets up a node icon and registers the icon type. a. Specification method

cd CD-ROM-drive-name ¥pc¥win32¥centric

cliset.exe

11.4.6 SystemWalker/CentricMGR screen linkage command (mpalreg)

Select SystemWalker/CentricMGR operation management client transaction monitoring, the operation menu for system monitoring, and a node on the map to add an operation item to the pop-up menu that is opened by right-clicking. For more information about commands, see mpaplreg in the SystemWalker/CentricMGR Reference Manual. To use mpaplreg, see the sample in the following directory on CD-ROM of SystemWalker/StorageMGR. a. Specification method

[Addition to the menu]

Run the following command from the command line.

#mpaplreg -a -m application-name -p host-name -c command-line -w

* Generally, edit cd-rom-drive-name¥pc¥win32¥centric¥menuset.sh with an editor.

Example of change:

mpaplreg -a -m StorageMGR -p tama -c http://1.1.1.1/swstorage/index.html -w

[Deletion from the menu]

Run the following command from the command line.

#mpaplreg -d application-name

* Generally, edit cd-rom-dirve-name¥pc¥win32¥centric¥unmenuset.sh with an editor.

Example of change:

mpaplreg -d StorageMGR b. Description of options

Option Description

-m Specifies a name to be registered on the menu.

Specifies StorageMGR.

-p Specifies the host name of the node managed by StorageMGR for which a menu is being added.

In the example above, "tama" is specified.

-c

Specifies the command line to be started when the menu is selected.

Specifies the URL of the SystemWalker/StorageMGR Web screen.

In the example above, "1.1.1.1" is specified for the IP address of the SystemWalker/StorageMGR Web screen, but specify the IP address of the server on which the SystemWalker/StorageMGR management server is installed.

-d Deletes the registered menu item.

Specifies StorageMGR.

The following are notes on this command: · Perform this operation whenever a new storage (SAN) device is added. · This operation must be carried out by a root user on the operation management server.

242

11.5 Starting and Stopping Daemons

StorageMGR daemons can be started in the ways explained in this chapter.

A note on this command is as follows: · Execute this command using the same LANG environment variable that of the code system used by the

system.

11.5.1 Starting and stopping the communication daemon

· Starting the communication daemon Enter the following command to stop the communication daemon: # /opt/FJSVswstf/bin/stgfwcom start

· Stopping the communication daemon Enter the following command to stop the communication daemon: # /opt/FJSVswstf/bin/stgfwcom stop

11.5.2 Starting and stopping the RMI daemon

· Starting the RMI daemon Enter the following command to start the RMI daemon: # /opt/FJSVswstf/bin/stgrmicom start

· Stopping the RMI daemon Enter the following command to stop the RMI daemon: # /opt/FJSVswstf/bin/stgrmicom stop

11.5.3 Starting and stopping the RDB daemon

· Starting the RDB daemon Enter the following command to start the RDB daemon: # /opt/FJSVswstf/bin/stgdbcom start

· Stopping the RDB daemon Enter the following command to stop the RDB daemon: # /opt/FJSVswstf/bin/stgdbcom stop

11.5.4 Starting and stopping the CIMOM daemon

· Starting the CIMOM daemon Enter the following command to start the CIMOM daemon: # /opt/FJSVswsam/bin/cimserver start

*1 CIMOM stops if the console used to start CIMOM is quitted. To prevent this event from occurring, start CIMOM from the console used to start /usr/bin/csh.

· Stopping the CIMOM daemon Enter the following command to stop the CIMOM daemon: # /opt/FJSVswsam/bin/cimserver stop

11.5.5 Starting and stopping the SNMP trap monitoring daemon

· Starting the SNMP trap monitoring daemon Enter the following command to start the SNMP trap monitoring daemon: # /opt/FJSVswstt/bin/mpnm-trapd start

· Stopping the SNMP trap monitoring daemon Enter the following command to stop the SNMP trap monitoring daemon: # /opt/FJSVswstt/bin/mpnm-trapd stop

11.5.6 Starting and stopping the space management daemon

· Starting the space management daemon Enter the following command to start the space management daemon: # /opt/FJSVswstp/bin/swstpcom start

243

244

· Stopping the space management daemon Enter the following command to stop the space management daemon: # /opt/FJSVswstp/bin/swstpcom stop

11.5.7 Starting and stopping the authentication daemon

· Starting the authentication daemon Enter the following command to start the authentication daemon: # /opt/FJSVswssc/bin/rc.smfwsec start

· Stopping the authentication daemon Enter the following command to stop the authentication daemon: # /opt/FJSVswssc/bin/rc.smfwsec stop

The authentication daemon is available only on the Storage management server.

11.5.8 Starting and stopping StorageMGR daemons

The daemons listed below are started and stopped together:

Server type Storage server Storage management server

Daemon name Communication daemon

Space management daemon

Communication daemon

RMI daemon

RDB daemon

CIMOM daemon

SNMP daemon

Space management daemon

Authentication daemon · Starting a StorageMGR daemon

Enter the following command to start a StorageMGR daemon: # /opt/swstorage/bin/sstoragemgr

· Stopping a StorageMGR daemon Enter the following command to stop a StorageMGR daemon: # /opt/swstorage/bin/pstoragemgr

11.5.9 Starting and stopping the SAN management agent

· Starting the SAN management agent Enter the following command to start the SAN management agent: # /etc/init.d/init.snmpdx start

· Stopping the SAN management agent Enter the following command to stop the SAN management agent: # /etc/init.d/init.snmpdx stop

Chapter 12 Notes on Operations

This chapter provides notes on the operations of SystemWalker/StorageMGR.

12.1 Notes on Backup Operation

This chapter provides notes on the backup operation.

12.1.1 General notes

This chapter provides general notes on the backup operation.

+Locale of a Storage Server

On all the storage servers, the locale of an internal code system to be used by SystemWalker/StorageMGR (a code system to be specified when SystemWalker/StorageMGR is installed on a storage management server) must be installed.

+Exclusion from Backup Targets

The following devices must not be subject to the backup operation. · Device on which the system is stored · Device on which SystemWalker/StorageMGR has been installed · Device on which the resource files of SystemWalker/StorageMGR exists · Device whose volume has been entirely defined

+Fetching of Device Information

Before starting the backup operation, fetch device information managed by all the storage servers on the Web window of SystemWalker/StorageMGR. This operation will take time proportional to the total number of devices defined on the selected storage servers. If many devices are involved, perform this operation while the CPU load or I/O load is low.

As a guide, about 0.5 seconds are required per device (partition) under a no-load condition.

+Running Software

· SystemWalker/StorageMGR space management Neither space watch nor Restoration and backup must be done at the same time.

+Slice containing VTOC

Slices containing VTOC (cylinder 0) cannot be registered as transaction volumes or backup volumes.

+SynfinityFILE

SynfinityFILE file systems consisting of multiple slices cannot be handled.

To back up or restore a SynfinityFILE file system consisting of multiple slices, handle the multiple slices simultaneously while the file system is unmounted.

12.1.2 Notes on the snapshot high-speed backup

This chapter provides notes on the snapshot high-speed backup.

+Number of Required Backup Volumes

The snapshot high-speed backup requires as many backup volumes as the number of specified generations. Thus, the snapshot backup is disabled if: · All the specified number of generations have been backed up, and · No new volume that can be used as a backup volume exists.

+Continuous Backup

Performing the snapshot high-speed backup continuously with the same transaction volume specified will perform the backup operation in parallel.

Performing the snapshot high-speed backup continuously more often than the number of preservation generations will

245

cancel the backup operations starting from the oldest one. In other words, you cannot simultaneously perform the backup operation more often than the specified number of generations.

12.1.3 Notes on synchronous high-speed backup

This chapter includes some notes on synchronous high-speed backup.

+Backup processing

The backup execution command cannot be executed before the transaction and backup volumes have become equivalency holding state.

Individual transaction volumes in a log group cannot be backed up.

+Backup policy settings

Backup policies can be set if the number of registered backup volumes is enough for snapshot-type high-speed backup operation even if the number is not enough for synchronous high-speed backup operation. In this event, high-speed backup may not be possible.

12.1.4 Notes on restoration

This chapter provides notes on restoration.

+Timing of Restoration

If data on a transaction volume has been rewritten since the latest backup data is collected to a backup volume and until restoration is performed, the rewritten data shall not be guaranteed.

[Figure 12.1 Notes on restoration of SystemWalker/StorageMGR]

246

12.2 Notes on the Web Window Environment

This chapter provides notes on the Web window environment.

+Settings of Java Plug-in Properties

After installing the Java Plug-in, display the Properties window of the Java Plug-in.

Select [Settings] - [Control Panel] - [Java Plug-in].

Table 12.1 shows the relationships between the settings on the Java Plug-in Properties window and the operations on the Web window. Depending on the settings made on the Properties window, the Web window may not normally operate. The Web window can operate by the default values that Plug-in has been installed. You need not change the settings in particular.

[Table 12.1 Settings of the Java Plug-in and operations on the Web window]

Tag name

Setting value name Setting Default

value Remarks

Enabling the Java Plug-in

Must be checked Checked

Unless this item is checked, a message "Java is disabled" will be displayed on the Java console and the Web window cannot be started.

Displaying the Java console Optional Not

checked

You are recommended to check this item although it is optional. The operating status of the Web window will be displayed on the "Java Console" and can be used as investigation information if any error occurs on the Web window.

Caching JAR to memory

Recommended to be checked Checked

If this item is checked, you can bring up more quickly from the initial window a management window that has been brought up once.

Basics

Parameter for Java execution

Not specified Not specified

This item will be meaningless if specified.

Java Run Time Environment

Using the Java Plug-in by default

Using the Java Plug-in by default

Specify the Run Time level at which the Web window should run. Do not specify any other level. If this item is not checked, a malfunction may occur.

Enabling the Just in Time Compiler

Must be checked Checked If this item is not checked, a

malfunction may occur.

Details

Enabling debugging

Must not be checked

Not checked

If this item is checked, a malfunction may occur.

Proxy Using the browser settings

Must be checked Checked If this item is not checked, a

malfunction may occur.

+Proxy Settings of Web Browser

Before using the Web window, specify an IP address or server name for a storage management server on the Web browser. At this time, do not specify the proxy of the Web browser as the IP address or server name. · For Navigator 4.5 Select the [Edit] menu and then [Settings] to display the Settings dialog box. From the category (tree), select [Details] and then [Proxy], check [Manually set up the proxy], and click the Display button to display the Manually Set Up Proxy dialog box. In the [Do not use the proxy for a domain starting with:] box, specify the IP address of a storage management server.

247

248

· For Explorer 4.0 Select the [View] menu and then [Internet Options] to display the Internet Options dialog box. From the dialog box, select the [Connection] tag and click the [LAN Connection] button. Then, the [Local Area Network (LAN) Settings] dialog will be displayed. Click the [Details] button to display the [Proxy Settings] dialog. Then, in the [Do not use the proxy for an address starting with:] box in the [Proxy Settings] dialog, specify the IP address of a storage management server. · For Explorer 5.0 and Explorer 5.5 Select the [Tools] menu and then [Internet Options] to display the Internet Options dialog box. From the dialog box, select the [Connection] tag and click the [LAN Connection] button. Then, the [Local Area Network (LAN) Settings] dialog will be displayed. Click the [Details] button to display the [Proxy Settings] dialog. Then, in the [Do not use the proxy for an address starting with:] box in the [Proxy Settings] dialog, specify the IP address of a storage management server.

Appendix A Preprocessing and Postprocessingof Backup and Restoration

This appendix describes shell scripts used for preprocessing and postprocessing of backup and restoration.

Note that a shell script described in this appendix has different linefeed positions due to formatting of this manual.

A.1 Overview

Shell scripts used for preprocessing and postprocessing of backup or restoration are started before and after backup or restoration when a backup or restore execution command is executed.

These shell scripts describe processing required by SystemWalker/StorageMGR to back up or restore a transaction volume.

This chapter describes the setup of preprocessing and postprocessing.

A.2 Preprocessing and Postprocessing of Backup

Backup on SystemWalker/StorageMGR must be performed basically while access to a transaction volume from other processes is inhibited.

Normally, the preprocessing acquires the mount status of a transaction volume using the transaction volume name and then performs the following processing:

Transaction volume status Preprocessing

Mounted Unmount a transaction volume.(*1)

Unmounted Take no action.

*1 If the transaction volume cannot be unmounted, however, customize the shell script for pre-processing. For information on this customization, see the section on "If you do not want to unmount a transaction volume."

What to do in the postprocessing must be determined depending on what has been done in the preprocessing.

Preprocessing Postprocessing

A transaction volume was unmounted. Remount the transaction volume.

Take no action. Take no action.

If no transaction volume has been mounted since the start of system operation (e.g., a transaction volume used as a database), neither pre- nor post-processing is performed.

If special preprocessing or postprocessing is required, you need to add the concerned processing to a shell script.

If post-processing was failed, execute the Resource match command because the consistency of resource information may be incomplete.

A.2.1 Preprocessing of backup

The name of the shell script for pre-processing before backup processing is /etc/opt/FJSVswsts/sh/OpcBackup.pre.

#!/bin/sh

# SystemWalker/StorageMGR

# All Rights Reserved, Copyright FUJITSU LIMITED, 2002

#

249

# Preprocessing of backup processing

#

# Argument: $1 Device name of transaction disk

# $2 Mount point of transaction disk

# $3 Device name of backup disk

#

# Error number

# 1: Argument error(system error)

# 2: umount error

# Argument check

case $# in

1)

;;

2)

;;

3)

;;

*)

exit 1

;;

esac

device="`echo $1`"

250

mount_point="ècho $2`"

bk_device="ècho $3`"

# Determination postprocessing file name

if [ "$SWSTGNODE" != "" ]

then

swstg_node="/ècho $SWSTGNODE`"

else

swstg_node=""

fi

trans="ècho $device | grep "/dev/dsk/"`"

if [ "$trans" != "" ]

then

dev="ècho $device | sed "s/¥/dev¥/dsk¥///"`"

post_file="/etc/opt/FJSVswsts"$swstg_node"/data/DEFAULT/"$dev".pre"

fstype_file="/etc/opt/FJSVswsts"$swstg_node"/data/DEFAULT/"$dev".fstype"

bd_file="/etc/opt/FJSVswsts"$swstg_node"/data/DEFAULT/"$dev".bd"

else

trans="ècho $device | grep "/dev/FJSV"`"

if [ "$trans" != "" ]

then

251

dev="ècho $device | cut -d/ -f5`"




else

trans="ècho $device | grep "/dev/sfdsk/"`"

if [ "$trans" != "" ]

then

dev="ècho $device | sed "s/¥/dev¥/sfdsk¥///"`"

dev="ècho $dev | sed "s/¥/dsk¥//_/"`"

dev="ècho $dev | sed "s/:/_/"`"




device="ècho $device | cut -d: -f1`"

else

exit 0

fi

fi

252

fi

if [ "$mount_point" != "" ]

then

# When device cannot be unmounted

#

# if [ $device = "/dev/dsk/c*t*d*s*" ]

# then

# if [ "$bk_device" != "" ]

# then

# echo $bk_device > $bd_file

# fi

# df -ln $mount_point | cut -f2 -d: | cut -f2 -d' ' > $fstype_file

# sync

# sync

# echo "fsck" > $post_file

#

# When device can be unmounted

#

# else

df -ln $mount_point | cut -f2 -d: | cut -f2 -d' ' > $fstype_file

/usr/sbin/umount $mount_point 2>/dev/null

if [ $? != 0 ]

253

then

exit 2

fi

echo "mount" > $post_file

# fi

# When device was not mounted

#

else

echo "none" > $post_file

fi

exit 0

+When you do not want to unmount operating volume

To operating volume not to unmount although mounted, please eliminate 81-90, and the comment ("#") of the 94,103rd line by the editor etc., and point to the target device in if sentence of the 81st line.

A.2.2 Postprocessing of backup

The name of the shell script for pre-processing before backup processing is /etc/opt/FJSVswsts/sh/OpcBackup.post.

#!/bin/sh



#

# Postprocessing of backup processing

254

#



#

# Error number

# 1: Argument error (system error)

# 2: mount error

# 3: fsck error

# Argument check

case $# in

1)

;;

2)

;;

*)

exit 1

;;

esac

device="`echo $1`"


# Determination of postprocessing file name

255


then


else

swstg_node=""

fi


if [ "$trans" != "" ]

then





else


if [ "$trans" != "" ]

then



256



else


if [ "$trans" != "" ]

then








else

exit 0

fi

fi

fi

# Confirmation of postprocessing

257

if [ ! -r $post_file ]

then

exit 0

fi

post="`cat $post_file`"

# Confirmation of Fstype

if [ ! -r $fstype_file ]

then

fs=""

else

fs="`cat $fstype_file`"

fi

# No processing

if [ $post = "none" ]

then

rm -rf $post_file 2> /dev/null

rm -rf $fstype_file 2> /dev/null

exit 0

fi

# mount processing

258

if [ $post = "mount" ]

then

/usr/bin/df -l $device > /dev/null 2>&1

if [ $? != 0 ]

then


then

/usr/sbin/mount $device $mount_point 2> /dev/null

else

if [ $fs = "" ]

then


else

/usr/sbin/mount -F $fs $device $mount_point 2> /dev/null

fi

fi

if [ $? != 0 ]

then

exit 2

fi

259

fi



exit 0

fi

# fsck processing

if [ $post = "fsck" ]

then

if [ -r $bd_file ]

then

bk_device="`cat $bd_file`"

dev="`echo $bk_device | sed "s/¥/dsk¥//¥/rdsk¥//"`"


then

fsck -m $dev > /dev/null 2>&1

else

if [ $fs = "" ]

then

fsck -m $dev > /dev/null 2>&1

else

fsck -m -F $fs $dev > /dev/null 2>&1

260

fi

fi

if [ $? != 0 ]

then

exit 3

fi

fi



rm -rf $bd_file 2> /dev/null

exit 0

fi

exit 0

A.3 Preprocessing and Postprocessing of Restoration

In SystemWalker/StorageMGR, restore processing must be performed while transaction volumes are unmounted.

Thus, in pre-processing, the mount state of the transaction volume is determined using its name, and the following processing is then performed:

Transaction volume status Preprocessing

Mounted Unmount the transaction volume.

Unmounted Take no action.

What to do in the postprocessing must be determined depending on what has been done in the preprocessing.

Preprocessing Postprocessing

A transaction volume was unmounted. Remount the transaction volume.

Take no action. Take no action.

If special preprocessing or postprocessing is required, you need to add the concerned processing to a shell script.

If pos-tprocessing was failed, execute the Resource match command because the consistency of resource information may be incomplete.

A.3.1 Preprocessing of restoration

The name of the shell script for pre-processing before restore processing is /etc/opt/FJSVswsts/sh/OpcRestore.pre.

#!/bin/sh



261

#

# Preprocessing of restoration processing

#



#

# Error number


# 2: umount error

# Argument check

case $# in

1)

;;

2)

;;

*)

exit 1

;;

esac

device="`echo $1`"


262



then


else

swstg_node=""

fi


if [ "$trans" != "" ]

then




else


if [ "$trans" != "" ]

then



263


else


if [ "$trans" != "" ]

then







else

exit 0

fi

fi

fi


then

# When device can be unmounted

264

#


/usr/sbin/umount $mount_point 2> /dev/null

if [ $? != 0 ]

then

exit 2

fi

echo "mount" > $post_file


#

else


fi

exit 0

Restore processing is not possible on a mounted transaction volume that cannot be unmounted. Specify a device at the restore destination.

A.3.2 Postprocessing of restoration

The name of the shell script for post-processing after restore processing is /etc/opt/FJSVswsts/sh/OpcRestore.post.

#!/bin/sh



#

# Postprocessing of restoration processing

265

#



#

# Error number


# 2: mount error

# Argument check

case $# in

1)

;;

2)

;;

*)

exit 1

;;

esac

device="`echo $1`"



266


then


else

swstg_node=""

fi


if [ "$trans" != "" ]

then




else


if [ "$trans" != "" ]

then



267


else


if [ "$trans" != "" ]

then







else

exit 0

fi

fi

fi



then

268

exit 0

fi

post="`cat $post_file`"

# Confirmation of Fstype


then

fs=""

else


fi

# No processing


then



exit 0

fi

# mount processing


then

269


if [ $? != 0 ]

then


then


else

if [ $fs = "" ]

then


else


fi

fi

if [ $? != 0 ]

then

exit 2

fi

fi


270


exit 0

fi

exit 0

271

Appendix B Sample Shell Script for Backup Operations

This appendix describes sample scripts for SystemWalker/StorageMGR.

A sample script allows you to back up data on a transaction volume to a tape using SystemWalker/StorageMGR and backup software in combination. You can hedge against risks by backing up data on a work disk not only to a disk but also to a tape.

B.1 Overview

Use SystemWalker/StorageMGR and backup software in combination to back up a transaction volume to a tape.

SystemWalker/StorageMGR provides some sample shell scripts for backup processing. The backup operation administrator must modify the sample shell scripts by adjusting them appropriately for the business at hand and then apply them to actual backup operations.

B.2 Backup and Restoration of a Transaction volume

B.2.1 Backup procedure

The following shows an overview of the backup procedure. 1. Checking the work operation status

Check whether work is in operation or not. 2. Business stoppage

For business in progress in 1, make contents of each transaction volume consistent. 3. Disk backup

Create backup copies of transaction volumes by using the backup function of SystemWalker/StorageMGR. 4. Business restart

For business in progress in 1, restart the business at hand. 5. Backup tape

Back up the backup volumes of SystemWalker/StorageMGR onto tape by running backup software.

[Figure B.1 Backup method]

B.2.2 Restoration procedure

The following shows an overview of performing restoration from a backup tape. 1. Checking the work stop status

Check that work is stopped. If work is in operation, completely stop the work. 2. Restore from tape

Run business software to restore transaction volumes from tape. 3. Business restart

273

[Figure B.2 Restore method]

B.3 Sample Shell Scripts

B.3.1 Overview of sample shell scripts

The sample shell scripts provided by SystemWalker/StorageMGR are summarized below. These sample shell scripts are stored in the /installation path/FJSVswsts/samp directory.

No. Type Script name Applied business name Applied backup software name

Target resource type

1 DB information collection swst_or_iv Oracle business - -

2 Backup swst_or_fs_bk_nb Oracle business and general file business VERITAS NetBackup File system

3 Backup swst_or_rd_bk_nb Oracle business VERITAS NetBackup Raw device

4 Backup swst_or_fs_bk_nw Oracle business and general file business NetWorker File system

5 Backup swst_or_rd_bk_nw Oracle business NetWorker Raw device

6 Backup swst_or_fs_bk_bs Oracle business and general file business

Tivoli Storage Manager File system

7 Backup swst_or_rd_bk_bs Oracle business Tivoli Storage Manager Raw device

B.3.2 Collecting DB information

swst_or_iv outputs the information of an Oracle database. This script outputs:

Output file names and their contents are as follows: · spdata.lst: List of table space names and storage destinations · spdata.srt: Sorted results of spdata.lst using the storage destination as the key · spdata.bgn: Command in the following format:

tablespace: Table-space-name begin backup: · spdata.end: Command in the following format:

tablespace: Table-space-name end backup: · spcont.lst: Control file information of an Oracle database · splog.lst: Log file information of an Oracle database The above files are used as references for creating shell scripts used for backup processing. a. Start

swst_or_iv b. Usage example

# swst_or_iv

swst_or_iv completed.

274

c. Result example spdata.lst

TABLESPACE-NAME DEVICE-NAME

-------------------- --------------------------------------------------

ORA10 /ora1/ora0.dbf

ORA20 /ora2/ora0.dbf

RBS /oracle/ora/oradata/rbs01.dbf

SYSTEM /oracle/ora/oradata/system01.dbf

TEMP /oracle/ora/oradata/temp01.dbf

TOOLS /oracle/ora/oradata/tools01.dbf

USERS /oracle/ora/oradata/users01.dbf

spdata.bgn

alter tablespace ORA10 begin backup;

alter tablespace ORA20 begin backup;

alter tablespace RBS begin backup;

alter tablespace SYSTEM begin backup;

alter tablespace TEMP begin backup;

alter tablespace TOOLS begin backup;

alter tablespace USERS begin backup;

spdata.end

alter tablespace ORA10 end backup;

alter tablespace ORA20 end backup;

275

alter tablespace RBS end backup;

alter tablespace SYSTEM end backup;

alter tablespace TEMP end backup;

alter tablespace TOOLS end backup;

alter tablespace USERS end backup;

spcont.lst

NAME TYPE VALUE

----------------------------------- ------- ------------------------------

control_files string /oracle/ora/oradata/control

splog.lst

NAME TYPE VALUE

----------------------------------- ------- ------------------------------

log_archive_dest string /oracle/ora/oradata/archive

d. Processing outline

#!/bin/sh

reterr() --- An error message is output before an error is returned.

sqldata()

{

sqlplus AAA/BBB <<!

SELECT --- Acquire Oracle table space information.

}

sqllog()

{

svrmgrl <<!

show --- Acquire Oracle log information.

}

sqlcont()

{

svrmgrl <<!

show --- Acquire Oracle control information.

276

}

# main()

# 0) Environmental variable setting

PATH=$PATH:/usr/bin:/usr/sbin:/opt/FJSVswsts/bin

# 1) Acquisition of Oracle table space information

sqldata() invocation --- Acquire Oracle table space information

# 2) Acquisition of Oracle log information

sqllog() invocation --- Acquire Oracle log information

# 3) Acquisition of Oracle control information

sqlcont() invocation --- Acquire Oracle control information

exit 0

B.3.2.1 File system backup

swst_or_fs_bk_nb, swst_or_fs_bk_nw, and swst_or_fs_bk_bs run backup software to back up an Oracle database on the file system and business data using general files.

Business data is copied to the backup volumes of SystemWalker/StorageMGR. The volumes at the copy destination are mounted at the mount points created by these scripts. The mount points created by these scripts are backed up by backup software.

These scripts applies to steps 2 to 5 in Appendix A.2.1, "Preprocessing Backup." a. Start

swst_or_fs_bk_nb {-a | -i} <mount-point-name>

swst_or_fs_bk_nw {-a | -i} <mount-point-name>

swst_or_fs_bk_bs {-a | -i}<mount-point-name> b. Explanation of operands

-a: Specify when business using an Oracle database is active. The start of backup processing is declared to the Oracle server.

-i: Specify when business using an Oracle database is stopped or the file is a general file. The start of backup processing is not declared to the Oracle server.

mount-point-name: Specify the name of the mount point targeted for backup. c. Example of using swst_or_fs_bk_nb

While business is active, back up /gyoumu_db in which an Oracle database is located.

# swst_or_fs_bk_nb -a /gyoumu_db

swst_or_fs_bk_nb completed. ( /gyoumu_db -> /gyoumu_db_SW at 23:00 on 1999.11.01 ) d. Processing outline of swst_or_fs_bk_nb

#!/bin/sh

usage() --- Command syntax is output before an error is returned.


chkmp() --- Check for a mount point

get_mp_blk() --- Conversion from a mount point to a device

getfs() --- Conversion from a mount point to a file system type

sqlbegin()

{

sqlplus AAA/BBB <<!

alter system switch logfile;

alter system flush shared_pool;

alter tablespace CCC begin backup; --- Notify Oracle of the start of backup.

277

}

sqlend()

{

sqlplus AAA/BBB <<!

alter tablespace CCC end backup; --- Notify Oracle of the stopping of backup.

}

getbd() --- Fetch the name of the backup (copy) destination device of SystemWalker/StorageMGR.

getdate() --- Fetch the backup (copy) date of SystemWalker/StorageMGR.

gettime() --- Fetch the backup (copy) time of SystemWalker/StorageMGR.

# main()

Parameter analysis and mount point check



# 1) Notification issued to Oracle of the start of backup

if [ "-a" operand specification ]

then

sqlbegin() invocation --- Notify Oracle of the start of backup.

Error handling

fi

# 2) Disk backup (copy) by SystemWalker/StorageMGR command

swstbackup $UDBLK --- Copy the disk.

Error handling

# 3) Notification issued to Oracle of the stopping of backup


then

sqlend() invocation --- Notify Oracle of the stopping of backup.

Error handling

fi

# 4) Acquisition of the backup (copy) destination of SystemWalker/StorageMGR

BDBLK="`getbd $UDBLK`" --- Fetch a backup volume as a character device.

BDDATE="`getdate $UDBLK`"--- Fetch the backup date.

BDTIME="`gettime $UDBLK`"--- Fetch the backup time.

# 5) Creation and mounting of a new mount point

MP_SW="${MP}_SW"

mkdir $MP_SW

Error handling

mount -F $FS -o ro $BDBLK $MP_SW --- Mount the backup (copy) destination.

Error handling

# 6) Backup to tape (NetBackup)

bpbackup -w $MP_SW

Error handling

# 7) Unmounting and deletion of a new mount point

278

umount $MP_SW

Error handling

rmdir $MP_SW

Error handling

exit 0

B.3.2.2 Raw device backup

swst_or_rd_bk_nb, swst_or_rd_bk_nw, and swst_or_rd_bk_bs run backup software to back up business data using an Oracle database on a raw device.

Business data is copied to work disks prepared by users. The work disks are backed up by backup software.

These scripts applies to steps 2 to 5 in Appendix A.2.1, "Preprocessing Backup." a. Start

swst_or_rd_bk_nb {-a | -i} <device name>

swst_or_rd_bk_nw {-a | -i} <device name>

swst_or_rd_bk_bs {-a | -i} <device name> b. Explanation of operands

-a: Specify when business using an Oracle database is active. The start of backup processing is declared to the Oracle server.

-i: Specify when business using an Oracle database is stopped or the file is a general file. The start of backup processing is not declared to the Oracle server.

device name: Specify the name of the raw device partition targeted for backup. c. Example of using swst_or_rd_bk_nb

While business is active, back up /dev/rdsk/c0t0d0s0 in which an Oracle database is located.

# swst_or_rd_bk_nb -a /dev/rdsk/c0t0d0s6

swst_or_rd_bk_nb completed. ( /dev/rdsk/c0t0d0s6 -> /dev/rdsk/c1t3d0s2 = /devices/pci0/scsi0/sd@1,0raw at 23:01 on 1999.11.01 )

d. Processing outline of swst_or_rd_bk_nb #!/bin/sh

usage() --- Command syntax is output before an error is returned.


get_chr_blk() --- Conversion from a character device to a block device

get_blk_chr() --- Conversion from a block device to a character device

sqlbegin()

{

sqlplus AAA/BBB <<!

alter system switch logfile;

alter system flush shared_pool;

alter tablespace CCC begin backup; --- Notify Oracle of the start of backup.

}

sqlend()

{

sqlplus AAA/BBB <<!

alter tablespace CCC end backup; --- Notify Oracle of the stopping of backup.

}

getbd() --- Fetch the name of the backup (copy) destination device of SystemWalker/StorageMGR.

279

getdate() --- Fetch the backup (copy) date of SystemWalker/StorageMGR.

gettime() --- Fetch the backup (copy) time of SystemWalker/StorageMGR.

get_chk_ln() --- Symbol link check

get_lgc_phy() --- Conversion from a logical node to a physical node

# main()

Parameter analysis and raw device check



# 1) Notification issued to Oracle of the start of backup


then

sqlbegin() invocation --- Notify Oracle of the start of backup.

Error handling

fi

# 2) Disk backup (copy) by SystemWalker/StorageMGR command

swstbackup $SRC --- Copy the disk.

Error handling

# 3) Notification issued to Oracle of the stopping of backup


then

sqlend() invocation --- Notify Oracle of the stopping of backup.

Error handling

fi

# 4) Acquisition of the backup (copy) destination of SystemWalker/StorageMGR

DSTBLK="`getbd $SRC`" --- Fetch a backup volume.

DST="`get_blk_chr $DSTBLK`"

BKDATE="`getdate $SRC`"

BKTIME="`gettime $SRC`"

# 5) Backup to tape (NetBackup)

CHR1="`get_chk_ln $DST`"

NBSRC="`get_lgc_phy $DST`"

bpbackup -w $NBSRC

Error handling

exit 0

B.3.3 Applying the sample shell scripts

B.3.3.1 DB information collection

+Sample shell script update

Update the procedures below of swst_or_iv to adjust them for actual operations. The following numbers correspond to those in the scripts.

0) Environmental variable setting

1) Acquisition of Oracle table space information

2) Acquisition of Oracle log information

280

3) Acquisition of Oracle control information

The above procedures 1) to 3) change Oracle account information.

These scripts can operate only on business servers of SystemWalker/StorageMGR.

B.3.3.2 File system backup

+SystemWalker/StorageMGR setup

Set up backup volumes so that the mount point targeted for backup is backed up correctly in SystemWalker/StorageMGR.

The generations of the backup volumes to be managed are arbitrary.

+Backup software setup

Set up the backup software. The generations of the tape to be managed are arbitrary.

If the unit of processing in SystemWalker/StorageMGR differs from that of backup software, delete execution steps of the backup software as required.


Update the procedures below of swst_or_fs_bk_nb, swst_or_fs_bk_nw, and swst_or_fs_bk_bs to adjust them for actual operations. The following numbers correspond to those in the scripts.


1) Notification issued to Oracle of the start of backup

3) Notification issued to Oracle of the stopping of backup

6) Backup to tape

The above procedures 1) and 3) refer to the spdata.bgn file and spdata.end file created by swst_or_iv.


B.3.3.3 Raw device backup

+SystemWalker/StorageMGR setup

Set up backup volumes so that the mount point targeted for backup is backed up correctly in SystemWalker/StorageMGR.

The generations of the backup volumes to be managed are arbitrary.

+Backup software setup

Set up the backup software. The generations of the tape to be managed are arbitrary.

If the unit of processing in SystemWalker/StorageMGR differs from that of backup software, delete execution steps of the backup software as required.


Update the procedures below of swst_or_rd_bk_nb, swst_or_rd_bk_nw, and swst_or_rd_bk_bs to adjust them for actual operations. The following numbers correspond to those in the scripts.


1) Notification issued to Oracle of the start of backup

3) Notification issued to Oracle of the stopping of backup

5) Backup to tape

The above procedures 1) and 3) refer to the spdata.lst file, spdata.srt file, spdata.bgn file, spdata.end file, splog.lst file, and spcont.lst file created by swst_or_iv.


281

+Recording and managing the backup volume name and processing time

After executing a shell script, a backup volume name and the processing time are output in a message. This backup volume name is a resource that is also backed up by backup software. The backup software is used for restore processing, and the backup volume name must be specified as the resource name for restore processing. Thus, the backup volume name and processing time output in a message after execution of a shell script must be recorded and managed.

B.3.4 Restore Method

B.3.4.1 File system

+If the generation to be restored is managed by SystemWalker/StorageMGR

Use the restore function of SystemWalker/StorageMGR for restore processing.

+If the generation to be restored is managed by backup software

After copying of backup volumes by SystemWalker/StorageMGR, swst_or_fs_bk_nb, swst_or_fs_bk_nw, and swst_or_fs_bk_bs mount the backup volumes at a new mount point and use backup software for processing. The new mount point name is "original mount point name" + "_SW". Therefore, if the backup software is used for restore processing, "original mount point name" + "_SW" is used instead of "original mount point name."

B.3.4.2 Raw device

+If the generation to be restored is managed by SystemWalker/StorageMGR

Use the restore function of SystemWalker/StorageMGR for restore processing.

+If the generation to be restored is managed by backup software

swst_or_rd_bk_nb, swst_or_rd_bk_nw, and swst_or_rd_bk_bs process backup volumes after copying of the volumes by SystemWalker/StorageMGR using backup software. In the backup software, resources are registered as separate resources even if their contents are the same. Thus, if the backup software is used for restore processing, refer to information recorded and managed after execution of the shell script, and determine the backup volume name based on the processing time. Then, perform restore processing as follows: · VERITAS NetBackup

Restore processing is performed directly on transaction volumes. · NetWorker and SystemWalker/BackupServer

Restore processing is performed on backup volumes. The restore function of SystemWalker/StorageMGR is then used for restore processing to transaction volumes.

B.3.5 Notes about using the sample shell scripts

+Oracle resource location

Store Oracle data files and files other than data files on separate disks or in separate slices.

+Backup operation of Oracle resources

1. Initialization parameter file a. Every time a change occurs, the cp command of the OS is executed for backup. 2. Control files a. You are recommended to use mirroring due to Oracle. b. If a change is made in the DB environment, use the following command to create a trace file. If a

control file is destroyed, execute the SQL statement in the trace file to recover the control file. Alter database backup control file to trace;

3. Data files a. Place the data files on raw devices. b. Create backup copies in SystemWalker/StorageMGR. c. The range of table spaces targeted for backup must be within the unit of synchronous backup

processing (begin backup/end backup) in Oracle and the unit of backup in SystemWalker/StorageMGR. For example, if backup copies must be created in units of LUNs in SystemWalker/StorageMGR, place one table space in one LUN.

d. Archive all of the latest logs by executing the following command after backing up all table spaces in the system:

e. Back up a data file copy destination (a backup volume on SystemWalker/StorageMGR) to a tape at the

282

same time as backing up an archive log file described later. Manage backup tapes of the data file and the archive log file as related tapes.

4. REDO files a. You are recommended to mirror online REDO log files and archive log files using Oracle or the OS. b. No online REDO log file needs to be backed up. c. Back up an archive log file to a tape. Normally, delete an archive log file after backing it up.

+Recovery of Oracle databases

After Oracle database has stopped, restore the database, and restart it. To recover the database to the latest state, use the recovery function of Oracle.

B.3.6 Applying the sample shell scripts

+Application to other businesses

Sample shell scripts can be applied to the following business instead of the Oracle business: · SymfoWARE · TeamWARE

283

Appendix C Replication script

This chapter explains the shell scripts that perform the pre- and post-processing of replication in SystemWalker/StorageMGR.

C.1 Overview

The shell scripts that perform the pre- and post-processing of replication start before and after replication (copy) processing.

These shell scripts contain processing code required by SystemWalker/StorageMGR for the copy source volume and copy destination volume.

This chapter describes the setup of preprocessing and postprocessing.

C.2 Preprocessing and Postprocessing of Replication

The replication preprocessing and postprocessing in SystemWalker/StorageMGR needs to be performed for both the replication source volume and the replication destination volume. However, the purpose for each is different. · Preprocessing and postprocessing for a replication source volume

The purpose of the processing is to freeze the replication source data in a state in which consistency is temporarily ensured. Replication source data is frozen temporarily in preprocessing, and after the replication has been created, the frozen status is released in postprocessing.

· Preprocessing and postprocessing for a replication destination volume The purpose of the processing is to prevent any application from accessing a replication destination volume during replication (copy) processing. In preprocessing, replication data for the destination is placed in access-disabled status, and after the replication has been created, this status is released in postprocessing.

Specific processing performed in preprocessing and postprocessing varies according to the data on the volume. The next section describes the preprocessing and postprocessing of a file system and a database.

C.2.1 Preprocessing and postprocessing for a file system

The preprocessing and postprocessing for a file system is the unmount processing and mount processing of the file system. (For Windows, the processing consists of allocating and canceling a drive letter.) The preprocessing and postprocessing for the replication source volume ensure the integrity of the replication source data. The preprocessing and postprocessing for the replication destination volume are performed to make access from other processes during synchronization processing and snapshot copying impossible. If no volume is mounted, the preprocessing and postprocessing are not performed.

The implementation status of the preprocessing and postprocessing for a file system is shown below. This table shows whether preprocessing and postprocessing are performed depending on the command type .It also shows the copy status upon execution of the command.

[Table C.1 Preprocessing and postprocessing for a file system]

Command Copy status Source/target Preprocessing Postprocessing

Source X X Replication start command

(swsrpstartsync)

uncopy or

replication establishment target O--*1 X

Source O O Replication making command

(swsrpmake) equivalence maintenance target X O--*2

Source O O equivalence maintenance target X O--*2

Source X X Replication establishment target X X

Source X X

Replication cancellation command

(swsrpcancel)

copying target X X

Snap shot replication making uncopy Source O O

285

command

(swsrpmake) target O O

O : executed, X : not executed

The postprocessing for the preprocessing performed in (1) is performed in (2). In the postprocessing in (2), re-mount is performed for the mount point where unmount was performed in the preprocessing in (1).

The preprocessing and postprocessing for a file system can be customized. The processing is started in accordance with the table above when a replication management command is executed. For replication between servers, these scripts are executed by remote execution by TCP/IP in the preprocessing and postprocessing of a volume that is not connected.

The operation image before and after processing is shown in Figure D.1.

[Figure C.1 Snapshot replication processing of snapshot]

If processing other than the standard preprocessing and postprocessing is required in the preprocessing and postprocessing, customize the scripts.

Note!! · SystemWalker/StorageMGR does not support any functions for the preprocessing and postprocessing of a

database. You will need to perform your own preprocessing and postprocessing before and after the execution of a SystemWalker/StorageMGR command.

C.2.2 Preprocessing when replication is executed

In the pre-processing script, prepare a copy source volume (RepSrc.Pre) and a copy destination volume (RepDst.Pre). The script is stored in the /etc/opt/FJSVswsrp/sh directory. Customize the script as required for processing. · RepSrc.Pre (copy source volume script)

#!/bin/sh

286



#

# Preprocessing of Replication(Source) processing

#

# Argument: $1 Device name of Source disk

# $2 Mount point of Source disk

#

# Error number


# 2: umount error

# Argument check

case $# in

2)

;;

*)

exit 1

;;

esac

device=$1

mount_point=$2



if [ "$trans" != "" ]

then

# /dev/dsk/c?t?d?s? -> c?t?d?s?


post_file="/etc/opt/FJSVswsrp/"$SWSTGNODE"/data/DEFAULT/"$dev".spre"

fstype_file="/etc/opt/FJSVswsrp/"$SWSTGNODE"/data/DEFAULT/"$dev".sfstype"

else


if [ "$trans" != "" ]

then

# /dev/FJSVmphd/dsk/mplb?s? -> /dev/FJSVmphd/dsk/mplb?s?

# /dev/FJSVmphd/dsk/mphd?s? -> /dev/FJSVmphd/dsk/mphd?s?




287

else


if [ "$trans" != "" ]

then

# /dev/sfdsk/class/dsk/volume:c?t?d? -> class_volume_c?t?d?







else

exit 0

fi

fi

fi


# When device was mounted

#

then



if [ $? != 0 ]

then

exit 2

fi

echo "mount,$mount_point" > $post_file


#

else


fi

exit 0 · RepDst.Pre (copy destination volume script)

#!/bin/sh

288



#

# Preprocessing of Replication(Destination) processing

#

# Argument: $1 Device name of Destination disk

# $2 Mount point of Destination disk

#

# Error number


# 2: umount error

# Argument check

case $# in

2)

;;

*)

exit 1

;;

esac

device=$1

mount_point=$2



if [ "$trans" != "" ]

then



post_file="/etc/opt/FJSVswsrp/"$SWSTGNODE"/data/DEFAULT/"$dev".dpre"

fstype_file="/etc/opt/FJSVswsrp/"$SWSTGNODE"/data/DEFAULT/"$dev".dfstype"

else


if [ "$trans" != "" ]

then






else

289


if [ "$trans" != "" ]

then








else

exit 0

fi

fi

fi


# When device was mounted

#

then



if [ $? != 0 ]

then

exit 2

fi

echo "mount,$mount_point" > $post_file


#

else


fi

exit 0

C.2.3 Postprocessing when replication is executed

In the post-processing script, prepare a copy source volume (RepSrc.Post) and a copy destination volume (RepDst.Post). The script is stored in the /etc/opt/FJSVswsrp/sh directory. Customize the script as required for processing.

290

· RepSrc.Post (copy source volume script) #!/bin/sh



#

# Postprocessing of Replication(Source) processing

#

# Argument: $1 Device name of Source disk

#

# Error number


# 2: mount error

# Argument check

case $# in

1)

;;

*)

exit 1

;;

esac

device=$1



if [ "$trans" != "" ]

then





else


if [ "$trans" != "" ]

then






291

else


if [ "$trans" != "" ]

then








else

exit 0

fi

fi

fi



then

exit 0

fi

post="`cat $post_file | cut -d',' -f1`"

mount_point="`cat $post_file | cut -d',' -f2`"

# Confirmation of FStype


then

fs=""

else


fi

# No processing


then



exit 0

fi

# mount processing


then


292

if [ $? != 0 ]

then


then


else

if [ $fs = "" ]

then


else


fi

fi

if [ $? != 0 ]

then

exit 2

fi

fi



exit 0

fi

exit 0 · RepDst.Post (copy destination volume script)

#!/bin/sh



#

# Postprocessing of Replication(Destination) processing

#

# Argument: $1 Device name of Destination disk

#

# Error number


# 2: mount error

# Argument check

case $# in

1)

293

;;

*)

exit 1

;;

esac

device=$1



if [ "$trans" != "" ]

then





else


if [ "$trans" != "" ]

then






else


if [ "$trans" != "" ]

then








else

exit 0

fi

fi

fi


294


then

exit 0

fi

post="`cat $post_file | cut -d',' -f1`"

mount_point="`cat $post_file | cut -d',' -f2`"

# Confirmation of FStype


then

fs=""

else


fi

# No processing


then



exit 0

fi

# mount processing


then


if [ $? != 0 ]

then


then


else

if [ $fs = "" ]

then


else


fi

fi

if [ $? != 0 ]

then

exit 2

295

296

fi

fi



exit 0

fi

exit 0

Appendix D Upgrading from Previous version

This appendix explains the upgrading from SystemWalker/StorageMGR 5.0/5.1 to 10.0.

D.1 Need for Updating

SystemWalker/StorageMGR retains management resources on servers. Since more information must be added to the management resources because SE/EE 10.0 has additional functions, the resources must be converted to the SE/EE 10.0 format.

Migration enables management resources to be converted to the format for SE/EE 10.0 and inherit accumulated management information.

D.1.1 Migrated resources of Storage servers

The servers have the following management resources: · Backup management resource files · Preprocessing and postprocessing scripts · Sample scripts

D.1.1.1 Backup management resource files

The management information (device, policy, and history) of backup management is stored in the following format:

/etc/opt/FJSVswsts/data/<node-name>

Execute the resource backup command (swstresback) to save the backup management resource files, and execute the resource restore command (swstresrst) to restore it.

The resource restore command restores the backup management resource files and reflects it to a repository. If the resource restore command is restoring a backup management resource files that is in the 5.0/5.1 formats, it converts it to the new format at the same time.

D.1.1.2 Preprocessing and postprocessing scripts

The preprocessing and postprocessing scripts for backup and restoration are stored in the following formats:

/etc/opt/FJSVswsts/sh

OpcBackup.pre

OpcBackup.post

OpcRestore.pre

OpcRestore.post

No function is provided to save or restore preprocessing and postprocessing scripts. Since scripts may be changed by an upgrade, scripts that were customized must be customized again.

D.1.1.3 Sample scripts

Sample scripts for Oracle linkage and physical copying completion wait are stored in the following files:

/etc/opt/FJSVswsts/samp

swst_or_fs_bk_bs

swst_or_fs_bk_nb

swst_or_fs_bk_nw

swst_or_iv

swst_or_rd_bk_bs

swst_or_rd_bk_nb

swst_or_rd_bk_nw

swststartsyncwait

swstsyncbackup

297

No function is provided to save or restore preprocessing and postprocessing scripts. Since scripts may be changed by an upgrade, scripts that were customized must be customized again.

D.1.1.4 Recovery control file

[deleted]

D.1.1.5 Work directory

[deleted]

D.1.2 Migration of Storage management server

The resource listed below is used for migration of the StorageMGR management server.

Note that migration of the resource is required only for the Storage management server and not for a Storage server. Also note that the following resource is required for a migration from Version 5.1 and not for a migration from Version 5.0. · Repository Note: Only the above resource can be migrated.

D.1.2.1 Repository

Follow the procedure below to migrate a repository. 1. Back up data by following the instructions in chapter 9.2.1.1, "Database backup," in the Operator's Guide for

Version 5.1. 2. Unsetup and uninstall the DB. 3. Install and set up the DB. 4. Restore the data by following the instructions in chapter 10.2.1.2, "Database restoration," in the Operator's

Guide for Version 10.0. Note: If the server name, IP address, or port number of the Storage management server or a Storage server is changed during a migration, take the action explained in chapter 10.5, "Changing the Operating Environment," in the Operator's Guide for Version 10.0 after the migration has completed.

298

D.2 Upgrade procedure

D.2.1 Overview of upgrade procedure

[Figure D.1 Operating procedure]

Use the above procedure for all Storage servers on which SystemWalker/StorageMGR 5.0/5.1 is installed.

If the Storage management server is also used as a Storage server in operations, follow the Storage server upgrade procedure on the Storage management server too.

Steps 3) to 7) are the same as those for servers on which SystemWalker/StorageMGR is newly installed.

D.2.2 Saving migrated resources

+For a storage server

· Backup management resource files Save the backup management resource files for SystemWalker/StorageMGR 5.0/5.1. To save the resource files, execute the following command: # /opt/FJSVswsts/bin/swstresback Backup-Directory

+For the storage management server

· Repository

299

Back up data by following the instructions in chapter 5.2.1.1, "Database backup," in the Operator's Guide for Version 5.1.

D.2.3 Unsetup and uninstallation of SystemWalker/StorageMGR

For information, see chapter 9.4, "Unsetup procedure," in the Operator's Guide of SystemWalker/StorageMGR 5.0/5.1.

D.2.4 Installing SystemWalker/StorageMGR

For information, refer to the Installation Guide of SystemWalker/StorageMGR 10.0.

D.2.5 Customizing individual Storage servers

Customize individual Storage servers by following the instructions in Chapter 5, "Customization of Storage Servers," in the SystemWalker/StorageMGR Installation Guide.

D.2.6 Customizing the storage management server

Customize the Storage management server by following the instructions in Chapter 4, "Customization of Storage Management Server," in the SystemWalker/StorageMGR Installation Guide.

D.2.7 Registering storage servers

Register the Storage servers. For information, see chapter 4.4.4, "Registering a Storage servers," in the SystemWalker/StorageMGR Operator's Guide.

D.2.8 Acquisition of device information

Only the shift to 10.0 from SystemWalker/StorageMGR 5.0 is needed.

Device information is acquired.. For information, see chapter 4.4.5, " Fetching device information on a storage server," in the SystemWalker/StorageMGR Operator's Guide.

D.2.9 Restoring migrated resources

+For storage servers

· Backup management resource files To restore the backup management resource files specified below and convert it to the backup management resource files for Version 5.1, enter the command shown below. For information on the command, see chapter 11.1.3.3, "Resource restore command (swstresrst)." # /opt/FJSVswsts/bin/swstresrst Backup-Directory

If the backup management resource files has a SymfoWARE transaction volume, the swst0305 message is output but the command ends normally. The resource migration command need not be executed. On devices for which the swst0305 message has been output, migrate the devices by following the procedure for migrate operations in linkage with SymfoWARE. Otherwise, migration has been completed.

+For the storage management server

· Repository Restore data by following the instructions in chapter 10.2.1.2, "Database restoration," in the Operator's Guide for Solaris 10.0. If a dialog box appears during restoration processing and it indicates that no backup data exists for space management and replication management, click [OK] to continue processing.

· The file for screens The backed up file is restored in each directory unit of a /opt/swstorage/java/data subordinate.

D.2.10 Execution of resource migration command

If an error occurs during restoration of the backup management resource files, correct the cause of the error, and then enter the command shown below. If restoration of the backup management resource files has completed normally, enter no command. For information on the command, see chapter11.1.3.4, "Resource migration command (swstresconv)."

# /opt/FJSVswsts/bin/swstresconv

300

D.3 Notes in Upgrading

D.3.1 Preprocessing and postprocessing scripts for backup and restoration

The backup and restoration preprocessing and postprocessing scripts used in SystemWalker/StorageMGR 5.0/5.1 cannot be used unless they are changed. Customize scripts provided with SystemWalker/StorageMGR 10.0. For information on the preprocessing and postprocessing scripts for backup and restoration, see Appendix A, "Preprocessing and Postprocessing of Backup and Restoration."

301

Glossary

The special terms used in this manual are explained below.

Backup management agent

Generic term for backup management applications in a Storage server

Backup manager

Generic term for backup management applications in a Storage management server

Backup management list

Profile backed up for each Storage server

DSI (Data Structure Instance)

Data expressed logically as a table column or row is located physically in a database space. The space holding the data is called a DSI. A DSO (Data Structure Organization) is also used for this purpose. For details, refer to the SymfoWARE(R) Server RDB Administrator's guide.

EC

Abbreviation of "equivalent copy." This is a hardware function of a Fujitsu disk array device (GR740). It holds information about how mirroring is done between disks in hardware. A disk is copied by executing disconnection control from software.

GR series

Generic name for Fujitsu disk array devices (GR720/730/740/820/840)

GR manager, GRmgr

GR720/730/740 storage management software

HDDV

See "Hard disk driver."

303

LUN (Logical Unit Number)

Logical unit defined under channel adapter in storage device

MPHD

See "Multipath disk control."

MPLB

See "Multipath disk control load balance option."

OPC

Abbreviation of "one point copy." This is a hardware function of a Fujitsu disk array device (GR740). It copies a disk at high speed in hardware. When copying is requested from software, physical copying is done in hardware. This function emulates the status of the software when the copying is completed.

SAN

Abbreviation of "storage area network." A SAN connects a server to the storage. Generally, this term covers storage concentration, data sharing between servers of different types, and the realization of unified storage management.

StorageMGR client

Generic term for Web-GUIs which operate in storage management clients

StorageMGR manager

Generic term for services and applications which are related to StorgaeMGR in a storage management server

Storage management client

This term corresponding to the term "storage management server" and indicates a machine in which StorageMGR Web-GUI operates.


Server where SystemWalker/StorageMGR-M is present

304

StorageMGR profile

Generic term for registry, SymfoDB, and CIM in StorageMGR

Storage server

Server where SystemWalker/StorageMGR-A is present

Advanced copy function

Generic term for hardware functions EC and OPC of a Fujitsu disk array device (GR740)

Initial window

First window displayed when the browser is activated by writing StorageMGR URL. This window is used to control information about servers and devices managed as StorageMGR.

Storage

External storage device such as a disk array device or tape unit. The GR720, GR730, GR740, F649x series, and Spectris/Platinum are external storage devices.

Snapshot backup

Backup using GR series disk array device one point copy (OPC) function

Generation overflow

If the total number of volumes backed up equals the maximum number of save generations, the oldest backup volume becomes a nontarget of generation management. This is called generation overflow. The maximum number of save generations can be set with a backup policy setup command.

General transaction volume

A backup target volume in which no database space is created

Hard disk driver

Hard disk driver software of the host server

This driver controls a disk array device in place of an sd driver. This driver must be installed for multipath disk control.

305

Backup management window

Web window for backup management

Framework

Generic term for applications (e.g., service and configuration management) which are the bases of StorageMGR

Multipath disk control

Driver software which executes multipath disk control in the host server

This fail-over type driver software sets two physical access paths as one logical path to prevent disk array device accesses from being stopped when either of the physical access paths fails.

Multipath disk control load balance option

Driver software which executes multipath disk control in host server. In addition to the fail-over function, this driver software supports a load balance (path load distribution) function and multipath function covering two to eight paths. These functions improve the reliability, operability, and performance of multipath disk control and makes multipath disk control the most suitable method for SAN operation servers.

Registry

StorageMGR environment definition file

306

systemwalker/storagemgr operator's guide -...

Documents