Download pdf - Softek AdvancedCopy Manager Operator's Guide for cluster ... · - Softek AdvancedCopy Manager running on Windows is referred to as the Windows version of Softek AdvancedCopy ... concept

Softek AdvancedCopy Manager Operator's Guide

for cluster environment

MC/ServiceGuard

10.2

for HP-UX

Preface

++Purpose

This manual explains the installation, customization, and operation of Softek AdvancedCopy Manager when it is used in a cluster system.

++Audience

This manual is intended for system managers responsible for managing storage with Softek AdvancedCopy Manager in a cluster system.

++Organization

This manual consists of the following six chapters:

+Chapter 1 Overview

This chapter provides an overview of cluster systems.

+Chapter 2 Installation of Agent function of Softek AdvancedCopy Manager

This chapter explains how to install Agent function of Softek AdvancedCopy Manager.

+Chapter 3 Customization of Storage Server Transactions

This chapter explains how to customize Storage server transactions.

+Chapter 4 Starting and Stopping a Daemon

This chapter explains how to start and stop a daemon.

+Chapter 5 Operation

This chapter explains the operation of Softek AdvancedCopy Manager when it is used in a cluster system.

+Chapter 6 Deleting a Cluster Environment

This chapter explains how to delete a cluster environment.

++Positioning of This Manual

This manual is a separate volume provided to only users who use Softek AdvancedCopy Manager in a cluster system environment. Before reading this manual, first read the following Softek AdvancedCopy Manager manuals and to gain an overall understanding of Softek AdvancedCopy Manager:

- Softek AdvancedCopy Manager Installation Guide

This manual explains how to install Softek AdvancedCopy Manager.

- Softek AdvancedCopy Manager Operator's Guide

This manual explains the operation of Softek AdvancedCopy Manager.

- Softek AdvancedCopy Manager Messages

This manual explains the messages output by Softek AdvancedCopy Manager and the action that the operator should take in response to them.

++Conventions for Product Names

- Microsoft(R) Windows NT(R) Server network operating system Version 4.0 and Microsoft(R) Windows NT(R) Workstation network operating system Version 4.0 are referred to as Windows NT.

- The Microsoft(R) Windows(R) 95 operating system is referred to as Windows 95.

- The Microsoft(R) Windows(R) 98 operating system is referred to as Windows 98.

- Microsoft(R) Windows(R) 2000 Professional, Microsoft(R) Windows(R) 2000 Server, and Microsoft(R) Windows(R) 2000 Advanced Server are referred to as Windows 2000.

- Microsoft(R) Windows(R) Millennium Edition is referred to as Windows ME.

- Microsoft(R) Windows(R) XP Professional, and Microsoft(R) Windows(R) XP Home Edition are abbreviated as Windows XP.

- Solaris (TM) Operating Environment is referred to as Solaris OE.

- Softek AdvancedCopy Manager running on Solaris OE is referred to as the Solaris OE version of Softek AdvancedCopy Manager.

i

ii

- Softek AdvancedCopy Manager running on Windows is referred to as the Windows version of Softek AdvancedCopy Manager.

- Softek AdvancedCopy Manager running on Linux is referred to as the Linux version of Softek AdvancedCopy Manager.

- Manager function of Softek AdvancedCopy Manager is referred to as Manager function of AdvancedCopy Manager.

- Agent function of Softek AdvancedCopy Manager is referred to as Agent function of AdvancedCopy Manager.

++Trademarks

Windows, Windows NT, SQL Server, Internet Explorer, and Microsoft Cluster Server are the registered trademarks of Microsoft Corporation in the U.S.A. and other countries.

Netscape logos and Netscape product and service names are the trademarks or registered trademarks of Netscape Communications Corporation in the U.S.A. and other countries.

Sun, Sun Microsystems, the Sun Logo, Solaris and all Solaris based marks and logos are trademarks of Sun Microsystems, Inc. in the United States and other countries, and are used under license.

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

ORACLE is a registered trademark of Oracle Corporation.

HP-UX is a registered trademark of Hewlett-Packard Company.

Linux is a trademark or registered trademark of Mr. Linus Torvalds in the United States and other countries.

Chapter 1 Overview

This chapter provides an overview of cluster systems.

1.1 What Is a Cluster System?

A cluster system uses two or more server machines as a single virtual server machine to provide high level of availability.

In single-server machine operation, if the server machine or an application running on the server machine stops, the machine or the application must be restarted. During this time, operation stops.

A cluster system, however, uses two or more server machines. If a failure occurs on one server machine or an application running on the server machine, the transaction can be resumed immediately by restarting the application on the other server machine. As a result, transaction down time is reduced. The switching a transaction from a server with a problem to another server that is operating normally is referred to as failover.

In the cluster system, the server machines are collectively called a cluster, and each server machine in the cluster is called a node.

For more information, refer to the cluster software manuals.

1.2 Support

Softek AdvancedCopy Manager runs on the following operating systems: · HP-UX 11.00, 11i Softek AdvancedCopy Manager cluster operation is supported by the following packages: · Softek AdvancedCopy Manager 10.2 Softek AdvancedCopy Manager supports only the following cluster systems: · Supported product

MC/ServiceGuard A.11.13 · Supported type

Failover · Volume manager

LVM Softek AdvancedCopy Manager does not support the SYSTEM_MULTI_NODE.

· In HP-UX, since Manager function of Softek AdvancedCopy Manager cannot be introduced, it cannot operate

Storage management server transaction.

1.3 Types of Operation

This chapter explains the ways in which Softek AdvancedCopy Manager operates in a cluster system.

1.3.1 Package and transaction

With a MC/ServiceGuard cluster, the host system called node is packed into one group on a network. Application service is summarized in the group as a package. The composition unit of a cluster system is called package. Moreover, the composition unit of a package is called package resource. With a package resource, a disk, an IP address, application, etc. which can be used by the cluster system are mentioned. The following figure shows the concept of cluster and transactions in a cluster system.

1

Cluster operation in Softek AdvancedCopy Manager means to make AdvancedCopy Manager functions available to transactions in a Package by incorporating them into the Package. In a Package, Softek AdvancedCopy Manager itself is also treated as a transaction. In particular, a transaction that is performed by a storage server is called a Storage server transaction.

· In Softek AdvancedCopy Manager, some transactions operate on a physical node and are therefore not

supported for cluster operation. Transactions of this type are called local Storage transactions.

1.3.2 AdvancedCopy Manager server types and server transaction types

In Softek AdvancedCopy Manager, a system in which Agent function of Softek AdvancedCopy Manager is installed is called a storage server. Server type refers to this classification. In Softek AdvancedCopy Manager cluster operation, a transaction performed by a storage server is called a Storage server transaction (see Chapter 1.3.1, "Package and transaction "). Server transaction type refers to this classification.

In HP-UX, since Manager function of Softek AdvancedCopy Manager cannot be introduced, it cannot operate Storage management server transaction.

A Storage server transaction can be incorporated into multiple packages in a cluster system. Consequently, storage server functions can be used in each package. Since whether a system is a cluster system or not makes no difference in a network, multiple storage servers appear to exist even though a cluster system is physically just a single system.

1.3.3 Logical servers and node types

When AdvancedCopy Manager transactions are performed in multiple package of a cluster system, an IP address can be set for each package. This type of IP address, called a logical IP address, makes the server corresponding to a

2

AdvancedCopy Manager transaction appear to exist in the network. This type of server is called a logical server or logical node. The following figure shows an example of a storage server in a cluster system.

A cluster system consists of two physical nodes. In a cluster system, the node on which a transaction operates is generally called the primary node and the standby node is called the secondary node. Node type refers to this classification. In a MC/ServiceGuard cluster system, on the other hand, the concept of the primary node/secondary node is different in each package because the nodes for active/standby can be selected in each package. In the above figure, for example, the primary node for transaction A and the secondary node for transaction B are physically the same.

1.3.4 Transaction types of applications

The transaction types of an AdvancedCopy Manager application in AdvancedCopy Manager cluster operation are listed in the following table. The table describes, for each applicable transaction, the active and the standby states.

Application (function) Storage server transaction

Storage local transaction

Transaction configuration management Agent

Active on primary node Standby on secondary node

-

Local configuration management Agent - Active on each

node

Transaction replication management

Active on primary node Standby on secondary node

-

Local replication management - Active on each node

Transaction backup management Active on primary node

-

3

Standby on secondary node

Local backup management - Active on each node

The Storage server transactions can be divided for operation on two or more logical servers. That is, whether a Storage server transaction is to be operated can be selected for each logical server. Storage local transactions cannot operate in a cluster.

· Primary node and secondary node in the table are not physical nodes. Each of type of node refers to a

different logical node type for each logical server. See Chapter 1.3.3, "Logical servers and node types."

1.3.5 Failover in a cluster system

The following explains the state when a failover occurs for a failure in a cluster system.

The above figure shows the concept of a failover when it occurs after a failure on the primary node of logical server3, which operates transaction C in a storage server cluster system. The unit for failover in a cluster system is the logical server. Thus, in a cluster system, a failover occurs only on the failed logical server. A failover does not occur on logical servers on which a failure has not occurred.

4

Chapter 2 Installation of Agent function of Softek AdvancedCopy Manager

This chapter explains how to install Agent function of Softek AdvancedCopy Manager in a cluster system.

In this chapter, one node is called the primary node and the other the secondary node in order to distinguish two physical nodes. These expressions are not the logical concepts explained in Chapter 1.3.3, "Logical servers and node types."

2.1 Preparations

This chapter explains the preparations required before Softek AdvancedCopy Manager installation.

2.1.1 MC/ServiceGuard installation and environment settings

In order for Storage server transaction to operate on a cluster system, MC/ServiceGuard must be installed on each node and the respective environment settings must be made. Confirm the device name and mount point name in the settings for each shared disk.

For details about MC/ServiceGuard, refer to the "MC/ServiceGuard Manual."

2.1.2 Preparing resources

The following resources are necessary to install Softek AdvancedCopy Manager on a cluster system: 1. Takeover IP address and subnet for Softek AdvancedCopy Manager

Allocate a new IP address that is unique in the network for use in cluster system operations. However, to use an IP address that is already in use for transactions, no new IP address for AdvancedCopy Manager need be allocated. One IP address is required per AdvancedCopy Manager transaction. When allocating a new IP address, check whether existing transactions use the IP address as a takeover resource, and make sure that adding the corresponding IP address has no adverse effect on transactions. Moreover, check a subnet.

2. Partition where shared data for Softek AdvancedCopy Manager is stored Prepare partitions on the shared disks on which to store shared data for Softek AdvancedCopy Manager. The table below lists the numbers of required partitions. Note that the listed values indicate the numbers of partitions required for every AdvancedCopy Manager transaction. For more information about the size of the shared disk for AdvancedCopy Manager shared data, see Chapter 2.1.3, "Capacity of a shared disk." Name Number of partitions

Shared disk for AdvancedCopy Manager share data 1

· The shared disk for AdvancedCopy Manager share data is defined as a shared disk of MC/ServiceGuard . · The shared disk for AdvancedCopy Manager share data must not use an AdvancedCopy Manager backup

function or replication function.

2.1.3 Capacity of a shared disk

Capacity required as a shared disk for AdvancedCopy Manager share data of Storage server transaction is the value which totaled following 1-3. 1. Replication operation

If the number of paired replication source/replication destination volumes used for a replication operation is p, calculate the shared disk space required for replication operations according to the following formula, 1.1 X p [KB]

2. Backup operation It is assumed that a is the number of backup disks, b is the number of transaction disks. (a + b X 35)/1024 [KB]

3. Cluster management 1024[KB]

5

2.2 Installation and customize of Agent function of Softek AdvancedCopy Manager

Install Agent function of Softek AdvancedCopy Manager. Refer to the HP-UX Softek AdvancedCopy Manager Installation Guide, and install Agent function of Softek AdvancedCopy Manager in the primary and secondary nodes with the same environment.

Set up the environment of the Storage server. For details, refer to Chapter 3, "Customization of Storage Servers," in the HP-UX Softek AdvancedCopy Manager Installation Guide. Set up the Storage server in the primary and secondary nodes with the same environment.

Do not install Agent function of Softek AdvancedCopy Manager on a shared disk.

After the installation is completed, restart both nodes. For information on constructing a cluster for Storage server transactions, see Chapter 3, "Customization of Storage Server Transactions."

6

Chapter 3 Customization of Storage Server Transactions

This chapter explains how to customize Storage server transactions.

· Each execution of the AdvancedCopy Manager cluster setup command creates the settings for one package.

To build two or more packages, execute the procedure for the AdvancedCopy Manager cluster setup command as many times as necessary.

· Before starting customization, decide whether to create a new package for performing Storage server transactions or to add the Storage server transactions to an existing package.

· Do not move the Storage server transactions from a package after setup to another package.

3.1 Preparations

This chapter explains the preparations required before customization.

3.1.1 Allocating space on the shared disk

Please confirm the secured space capacity as a shared disk which each package uses referring to Chapter 2.1.2, "Preparing resources" and Chapter 2.1.3 "Capacity of a shared disk."

3.1.2 Confirmation of input items

The cluster setup command prompts for input of the following items specific to cluster settings. After understanding the meaning of each item, prepare and confirm the information to be entered for each package to be set up. · Logical node name

Name of the logical server in a cluster system (see Chapter 1.3.3,"Logical servers and node types") The user can set any logical node name that does not exceed eight alphanumeric characters. However, 13 character strings of the following table cannot be made into a logical node name. Specify this name to release the package. audit cluster cmdevs config daemon data java

log pid report samp sh tmp · Port number for the transaction communication daemon

Prepare the port numbers to be allocated to the transaction communication daemon. A port number must be an integer from 1024 to 65535 that is currently not being used by another port. Also, a port number must be the same on both the primary node and secondary node because operations are cluster transactions.

· Transaction name To create a new package that performs Storage server transactions independently, prepare a new package name for the package. The user can specify any package name. To add a Storage server transaction to an existing package, confirm in advance the package name of that package.

· Takeover IP address and subnet for AdvancedCopy Manager Refer to Item 1 in Chapter 2.1.2, "Preparing resources."

· Mount point of the shared disk used by AdvancedCopy Manager Refer to Item 2 in Chapter 2.1.2, "Preparing resources."

3.2 Flow of Customizing Storage Server Transactions

This chapter describes the flow of setup. Throughout this chapter, the primary node is an active node in a package that has been set by the cluster setup command, and the secondary node is the standby node in the same group. Therefore, when building a mutual standby cluster system, the primary node and secondary node are different in each package that will be set up. This interpretation applies throughout the chapter.

7

3.3 Details of Storage Server Transaction Customization

To set up a Storage server transaction, use the procedure below. In a mutual standby cluster system, repeat steps 2 to 13 for every package to be set up: 1. Restart the system.

Restart the primary node and secondary node. For an explanation of the primary node and secondary node, see Chapter 3.2, "Flow of Customizing Storage Server Transactions." If the system is restarted in an extension of the installation process of Softek AdvancedCopy Manager, proceed to step 2.

8

2. Transaction environment is checked / created. Please refer to the manual of MC/ServiceGuard about the check method of a package, and the creation method. The Transactions (package) which adds Storage server Transactions is checked. In the case of new Transactions, it checks that a package is created, a package is started and a package can move between nodes.

The type of a package must be FAILOVER.

3. Check the preparations. Check each item of Chapter 3.1, "Preparations," for the package to be set up.

4. Stop the transaction. Stop the target transaction (stop a package ). Please refer to the manual of MC/ServiceGuard about the stop method of transaction.

5. Mount the shared disk on the primary node. The shared disk for AdvancedCopy Manager share data checks that it is in the state of unmount on the primary node and the secondary node. Then, Mount the shared disk for AdvancedCopy Manager shared data on the primary node.

6. Register port numbers. Register the port number for the transaction communication daemon in /etc/services.

- Transaction communication daemon: stgxfws_Logical-Node-Name

Register the same port number on the primary node and the secondary node.

7. Execute the cluster setup command on the primary node. On the primary node, execute the following cluster setup command after blocking other users from accessing the shared disk for AdvancedCopy Manager shared data: # /opt/swstorage/bin/stgclset_mcsg -k Primary -m AdvancedCopy-Manager-Shared-Data-Mount-Point -n Logical-Node-Name -s Service-Name -v Volume-Group-Name -i IP-Address -u Subnet

The example of an input: # /opt/swstorage/bin/stgclset_mcsg -k Primary -m /stgmount -n nodepr -s serv1 -v vg01 -i 10.10.10.10 -u 10.10.10.0

- Check the setup object. The contents set up on the primary node are displayed. AdvancedCopy Manager settings are as follows.

Cluster system : MC/ServiceGuard

Node type : Primary

IP Address : 10.10.10.10

SUBNET : 10.10.10.0

Mount point : /stgmount

Device Name : /dev/vg01/lvol1

Volume Group : vg01

Node name : nodepr

Service : serv1

Function : Server

Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] y

It asks whether continue setting processing. When interrupting cluster environmental setting processing, "n" is inputted, when continuing processing, "y" is inputted, or press the Enter key.

- The completion of a cluster environmental setting swstf8100 The cluster setup of the primary node has been completed. Next, create the cluster environment of the secondary node. #

8. Mount the shared disk on the secondary node.

9

Unmount the shared disk on the primary node. Then, Mount the shared disk for AdvancedCopy Manager shared data on the secondary node.

9. Execute the cluster setup command on the secondary node. On the secondary node, execute the following cluster setup command after blocking other users from accessing the shared disk for AdvancedCopy Manager shared data: # /opt/swstorage/bin/stgclset_mcsg -k Secondary -m AdvancedCopy-Manager-Shared-Data-Mount-Point

The example of an input: # /opt/swstorage/bin/stgclset_mcsg -k Secondary -m /stgmount

- Check the setup object. In the case of a secondary node, the contents set up by the primary node are displayed. AdvancedCopy Manager settings are as follows.


Node type : Secondary

IP Address : 10.10.10.10

SUBNET : 10.10.10.0



Volume Group : vg01

Node name : nodepr

Service : serv1

Function : Server

Do you want to continue with setting of AdvancedCopy Manager cluster? [default:y] y

It asks whether continue setting processing. When interrupting cluster environmental setting processing, "n" is inputted, when continuing processing, "y" is inputted, or press the Enter key. swstf8101 The cluster setup of the secondary node has been completed.

# 10. Unmount the shared disk on the secondary node.

Unmount the shared disk for AdvancedCopy Manager share data on the secondary node. 11. Edit and register a package information. - When business is newly created in Procedure 2, the sample control script created by the cluster

environmental setting command is copied to the control script of a package. When resources other than AdvancedCopy Manager are set as the package control script (AdvancedCopy Manager was added to the existing business), with reference to the sample control script created by the cluster environmental setting command, the information on AdvancedCopy Manager is set as the existing control script. The information on AdvancedCopy Manager in a sample control script can be searched with " Softek AdvancedCopy Manager."

Sample control scripts are /var/opt/swstorage/cluster/samp_Logical-Node-Name.sh. - The timeout value of a daemon stop of AdvancedCopy Manager is 300 seconds. When the timeout

value is set up by the package composition file, a timeout value should check or enough. - After replacing / editing a package control script, verification of a package composition file, registration,

and a check are carried out. Refer to the manual of MC/ServiceGuard for the method of verification of a package composition file, registration, and a check.

12. Start the transaction. Start the transaction stopped in step 4. ( A package is made into on-line.) Please refer to the manual of MC/ServiceGuard about the starting method of transaction.

13. Create an environment for Storage server transaction. Use the GUI of AdvancedCopy Manager to create an environment for Storage server transaction.

Create an environment for Storage server transaction with reference to the "Softek AdvancedCopy Manager Operator's Guide" and Chapter 5, "Operation."

10

Chapter 4 Starting and Stopping a Daemon

This chapter explains how to start and stop the daemons provided by Softek AdvancedCopy Manager in a cluster system.

4.1 Daemons that Configure Softek AdvancedCopy Manager

Agent function of Softek AdvancedCopy Manager is configured with the following daemons:

[Table 4.1 Types of daemons that configure Agent function of Softek AdvancedCopy Manager]

Daemon type Description

The Communication Daemon

Communicates with the Storage management server and the Storage server

4.2 Daemons Composing a AdvancedCopy Manager Transaction

A Storage server transaction consists of the following daemons:

[Table 4.2 Daemons composing a Storage server transaction]

Daemon Description

The Communication Daemon for transaction

A transaction daemon that communicates with a Storage management server and a Storage server

The following daemons cannot become a Storage server transaction: · Softek AdvancedCopy Manager Communication Daemon(for local)

4.3 Starting a Daemon

This chapter explains the methods of starting different kinds of Softek AdvancedCopy Manager daemons in a cluster system.

4.3.1 Starting daemons composing a AdvancedCopy Manager transaction

Listed in Tables 4.2, the different kinds of daemons composing a AdvancedCopy Manager transaction are automatically started from the package start command.

When starting individually the daemon who constitutes the transactions of AdvancedCopy Manager from a certain reason, the method of starting is as follows.

It is necessary to start per AdvancedCopy Manager transaction (for AdvancedCopy Manager for local node to be included). Please repeat the following procedures for every transaction. 1. The following commands are executed at a command line.

# ps -ef | grep stgxfws This result /opt/FJSVswstf/bin/stgxfws Logical-Node-Name

What is not displayed is checked. When displayed, the daemon has already started. 2. The logical node name which performs applicable transaction to an environment variable SWSTGNODE is set

up. 3. A communication daemon is started.

Please refer to a HP-UX Softek AdvancedCopy Manager Operator's Guide "8.4 Starting and Stopping

11

Daemons" about a starting command.

4.3.2 Starting the local daemons

The local daemons of AdvancedCopy Manager can be started by executing the following daemon batch start command:

# /opt/swstorage/bin/startacm

4.4 Stopping a Daemon

Different kinds of Softek AdvancedCopy Manager daemons are automatically stopped when the system is stopped. However, to stop an individual daemon, it must be stopped manually. The following chapter explain how to stop different kinds of Softek AdvancedCopy Manager daemons in a cluster system.

4.4.1 Stopping daemons composing a AdvancedCopy Manager transaction

Listed in Tables 4.2, the different kinds of daemons composing a AdvancedCopy Manager transaction can be stopped from the cluster system. For the stopping method, refer to the appropriate cluster software manual.

When stopping individually the daemon who constitutes the transactions of AdvancedCopy Manager from a certain reason, the method of stopping is as follows.

It is necessary to stop per AdvancedCopy Manager transaction (for AdvancedCopy Manager for local node to be included). Please repeat the following procedures for every transaction. 1. The following commands are executed at a command line.

# ps -ef | grep stgxfws This result /opt/FJSVswstf/bin/stgxfws Logical-Node-Name

What is displayed is checked. When not displayed, the daemon has already stopped. 2. The logical node name which performs applicable transaction to an environment variable SWSTGNODE is set

up. 3. A communication daemon is stopped.

Please refer to a Solaris Softek AdvancedCopy Manager Operator's Guide "8.4 Starting and Stopping Daemons" about a stop command.

4.4.2 Stopping the local daemons

The local daemons of AdvancedCopy Manager can be stopped by executing the following daemon batch stop command:

# /opt/swstorage/bin/stopacm

12

Chapter 5 Operation

This chapter provides notes on the operation of Softek AdvancedCopy Manager in a cluster system and describes differences from ordinary Softek AdvancedCopy Manager operation.

5.1 Using Web-GUI

For information about how to use Web-GUI provided by Softek AdvancedCopy Manager, refer to the following manuals: · For a Solaris OE Storage management server

Solaris OE Softek AdvancedCopy Manager User's Guide · For a Windows Storage management server

Windows Softek AdvancedCopy Manager User's Guide · For a Linux Storage management server

Linux Softek AdvancedCopy Manager User's Guide

· Please input a logical IP address into the IP address column of the [Addition of server], in Softek

AdvancedCopy Manager User's Guide "1.2.5 Server registration method." When a physical IP address is inputted into the IP address column, the operation of Softek AdvancedCopy Manager in a cluster system is not performed normally.

· Please input a port number to the transaction communication daemon (stgxfws_Logical-Node-Name) who registered at the time of customize of server transaction into the Port number column of the [Addition of server], in Softek AdvancedCopy Manager User's Guide "1.2.5 Server registration method." When a port number to the server transaction communication daemon is not inputted into the Port number column, the operation of Softek AdvancedCopy Manager in a cluster system is not performed normally.

5.2 Backup Operation

The following notes apply to the backup operation in a cluster system when operation differs from ordinary operation: · If a failover occurs while the backup command is being executed, recovery processing using the resource

adjustment command is required to maintain consistency. · It is necessary to define the volume group of the volume for backup as "VOLUME GROUPS" of a transactions

package control script. Example:VG[1]=vg02

· In cluster system, AdvancedCopy Manager belongs to the package. Therefore, carry out backup operation by the active node of a package. Backup operation cannot be performed from standby node and another packages.

For information about other backup operations, see Chapter 4, "Backup Operations", in the " HP-UX Softek AdvancedCopy Manager Operator's Guide".

5.3 Replication Operation

The following notes apply to the replication operation in a cluster system when operation differs from ordinary operation: · To use a shared disk for a replication (copy), specify a shared disk and the replication pair that is to be

configured for the device. · If a failover occurs while the replication command is being executed, recovery processing using the resource

adjustment command is required to maintain consistency. · It is necessary to define the volume group of the volume for backup as "VOLUME GROUPS" of a transactions

package control script. Example:VG[1]=vg02

· In cluster system, AdvancedCopy Manager belongs to the package. Therefore, carry out replication operation by the active node of a package. Replication operation cannot be performed from standby node and another packages.

For information about other replication operations, see Chapter 6, "Replication Operation", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide".

5.4 Operation Maintenance

About Operation Maintenance other than Changing the Operating Environment, see Chapter 7, "Operation Maintenance", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide".

13

About Changing the Operating Environment, refer to subsequent clauses.

5.4.1 Changing the IP address of a storage server transaction

Change the IP address of a storage server transaction as follows: 1. Check the operation of storage server transaction.

When having stopped, storage server transaction is started. About the starting method, refer to the cluster software manuals.

2. Delete the original volume and replica volume that are set, when the Replication Operation is being used. About deleting an original volume or replica volume, see Chapter 6.6.2, "Deleting an original volume or replica volume", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands".

3. Stop storage server transaction. About the stopping method, refer to the cluster software manuals.

4. Change IP address resource. About the method of changing IP address resource, refer to the cluster software manuals.

5. Check the operation of storage server transaction. When having stopped, start storage server transaction. About the starting method, refer to the cluster software manuals.

6. Select the server whose information is to be changed on the server list view, and select [Change of server...] on the [Operation] menu. Change the IP address and select [OK] on the "Change of server" dialog. Or an IP address is changed by the server information change command (stgxfwcmmodsrv) on storage management server. About the server information change command, see the chapter of commands in the "Softek AdvancedCopy Manager Operator's Guide" corresponding to OS, or see the chapter of commands in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to cluster system.

7. When using the Replication Operation, set the environment of Replication Operation.

5.4.2 Changing the port number of a storage server transaction

Change the port number of a storage server transaction as follows: 1. Check the operation of storage server transaction.


2. Delete the original volume and replica volume that are set, when the Replication Operation is being used. About deleting an original volume or replica volume, see Chapter 6.6.2, "Deleting an original volume or replica volume", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands".

3. Stop storage server transaction. About the stopping method, refer to the cluster software manuals.

4. On primary node and secondary node, change the port number of the communications daemon for storage server transaction (stgxfws_Logical-Node-Name) described at /etc/services.

5. Start storage server transaction. About the starting method, refer to the cluster software manuals.

6. Select the server whose information is to be changed on the server list view, and select [Change of server...] on the [Operation] menu. Change the port number and select [OK] on the "Change of server" dialog. Or the port number is changed by the server information change command (stgxfwcmmodsrv) on storage management server. About the server information change command, see the chapter of commands in the "Softek AdvancedCopy Manager Operator's Guide" corresponding to OS, or see the chapter of commands in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to cluster system.

7. When using the Replication Operation, set the environment of Replication Operation.

5.4.3 Changing the server name of a storage server transaction

Change the server name of a storage server transaction as follows. When you make a server name and a logical node name into the same name (when you also change a logical node name), carry out Chapter 5.4.4, "Changing the logical node name." 1. Check the operation of storage server transaction.


2. Delete the environment of Replication Operation or the environment of Backup Operation. Delete the device when the Backup Operation is being used. About deleting a device, see Chapter 4.6.2, "Deleting a device ", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands". Delete the original volume and replica volume that are set when the Replication Operation is being used. About deleting an original volume or replica volume, see Chapter 6.6.2, "Deleting an original volume or replica volume", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands".

3. Select the server whose information is to be changed on the server list view, and select [Change of server...]

14

on the [Operation] menu. Change the server name and select [OK] on the "Change of server" dialog. Or the server name is changed by the server information change command (stgxfwcmmodsrv) on storage management server. About the server information change command, see the chapter of commands in the "Softek AdvancedCopy Manager Operator's Guide" corresponding to OS, or see the chapter of commands in the "Softek AdvancedCopy Manager Operator's Guide for cluster environment" corresponding to cluster system.

4. When using the Backup Operation, set the environment of Backup Operation. When using the Replication Operation, set the environment of Replication Operation.

5.4.4 Changing the logical node name

Change the logical node name of a storage server transaction as follows: 1. Check the operation of storage server transaction.


2. Delete the environment of Replication Operation or the environment of Backup Operation. Delete the device when the Backup Operation is being used. About deleting a device, see Chapter 4.6.2, "Deleting a device ", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands". Delete the original volume and replica volume that are set when the Replication Operation is being used. About deleting an original volume or replica volume, see Chapter 6.6.2, "Deleting an original volume or replica volume", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands".

3. Back up the AdvancedCopy Manager data. Back up the following data.

- The shell script Back up the shell scripts for the Backup Operation and the Replication Operation.

4. Delete /etc/opt/swstorage/Logical-Node-Name/swnode.ini on active node. 5. Delete a cluster environment.

About deleting a cluster environment, see Chapter 6, "Deleting a Cluster Environment."

- Do not perform Step 1 in Chapter 6.2, "Procedure for Deleting a Cluster Environment." 6. Customize Storage server transactions.

About customization, see Chapter 3, "Customization of Storage Server Transactions."

- Specify a new logical node name in the value of -n option of a cluster setup command. - Do not perform Step 13 in Chapter 3.3, "Details of Storage Server Transaction Customization." 7. Start Storage server transactions.

About the starting method, refer to the cluster software manuals. 8. Restore the AdvancedCopy Manager data.

Restore the following data. - The shell script

Restore the shell scripts for the Backup Operation and the Replication Operation. 9. Change server name.

Perform Step 3 in Chapter 5.4.3, "Changing the server name of a storage server transaction." 10. When using the Backup Operation, set the environment of Backup Operation.

When using the Replication Operation, set the environment of Replication Operation.

5.4.5 Changing the service name

Change the service name of a storage server transaction as follows: 1. Check the operation of storage server transaction.



- The management file of AdvancedCopy Manager Back up /etc/opt/swstorage/Logical-Node-Name/swnode.ini on active node.

- The backup management list. Back up a backup management list. About backing up a backup management list, see Chapter 7.1.1.1, "Backing up a backup management list", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands."

15




- Do not perform Step 1 in Chapter 6.2, "Procedure for Deleting a Cluster Environment." 5. Change the package name on cluster system.

About the changing method, refer to the cluster software manuals. 6. Customize Storage server transactions.


- Do not perform Step 13 in Chapter 5.3, "Details of Storage Server Transaction Customization." - Do not change any information other than a service name by the cluster setup command. 7. Start Storage server transactions.


Restore the following data. - The management file of AdvancedCopy Manager

Restore /etc/opt/swstorage/Logical-Node-Name/swnode.ini on active node. - The backup management list.

Restore a backup management list. About restoring a backup management list, see Chapter 7.1.1.2, "Restoring a backup management list", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands."

- The shell script Restore the shell scripts for the Backup Operation and the Replication Operation.

- When the Replication Operation is being used, make replication management information consistent by Resource adjustment command (swsrprecoverres). Specify -r option when you execute the resource adjustment command. About the resource adjustment command, see Chapter 8.3.3.1, "Resource adjustment command (swsrprecoverres)", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands."

5.4.6 Changing the shared disk for AdvancedCopy Manager shared data

Change the shared disk for AdvancedCopy Manager shared data as follows: 1. Check the operation of storage server transaction.



- The management file of AdvancedCopy Manager Back up /etc/opt/swstorage/Logical-Node-Name/swnode.ini on active node.

- The backup management list. Back up a backup management list. About backing up a backup management list, see Chapter 7.1.1.1, "Backing up a backup management list", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands."




- Do not perform Step 1 in Chapter 6.2, "Procedure for Deleting a Cluster Environment." 5. Customize Storage server transactions.


16

- When a mount point is changed, specify a new mount point in the value of -m option of a cluster setup command.

- When a disk is changed, mount the new disk. - Change the information about the shared disk of a cluster system. - Do not perform Step 13 in Chapter 5.3, "Details of Storage Server Transaction Customization." 6. Start Storage server transactions.


Restore the following data. - The management file of AdvancedCopy Manager

Restore /etc/opt/swstorage/Logical-Node-Name/swnode.ini on active node. - The backup management list.

Restore a backup management list. About restoring a backup management list, see Chapter 7.1.1.2, "Restoring a backup management list", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands."

- The shell script Restore the shell scripts for the Backup Operation and the Replication Operation.

- When the Replication Operation is being used, make replication management information consistent by Resource adjustment command (swsrprecoverres). Specify -r option when you execute the resource adjustment command. About the resource adjustment command, see Chapter 8.3.3.1, "Resource adjustment command (swsrprecoverres)", in the "HP-UX Softek AdvancedCopy Manager Operator's Guide" and see Chapter 5.5, "Commands."

5.5 Commands

About the various commands which Softek AdvancedCopy Manager offers, the execution method in cluster operation is explained. For information about details of each command, see Chapter 8, "Commands", in the " HP-UX Softek AdvancedCopy Manager Operator's Guide".

The command in cluster operation is executed in the following procedure. 1. Set the logical node name of applicable transaction as an environment variable SWSTGNODE if needed. In

the case of bsh the environment variable is set by the following commands. # SWSTGNODE=Logical-Node-Name <Enter> # export SWSTGNODE

2. Execute a command. The node which executes the command in cluster operation, and the need or needless of an environment variable setup, and a command is as follows. Notes at the time of executing a command etc. are described to the Note column.

Command Need or needless of an environment variable

Command execution node Note

swstsvrset Required Transaction operation node -

swstsvrdisp Required Transaction operation node -

swstdevinfoset Required Transaction operation node -

swstdevdisp Required Transaction operation node -

swstbkpolset Required Transaction operation node -

swstbkpoldisp Required Transaction operation node -

swstbkpoldel Required Transaction operation node -

swstbackup Required Transaction operation node -

Backup management

swstbackstat Required Transaction operation node -

17

18

swstrestore Required Transaction operation node -

swstcancelrest Required Transaction operation node -

swstreststat Required Transaction operation node -

swsthistdisp Required Transaction operation node -

swsthistdel Required Transaction operation node -

swststartsync Required Transaction operation node -

swstcancelsync Required Transaction operation node -

swstsyncstat Required Transaction operation node -

swstexecstat Required Transaction operation node -

swstsrsemtch Required Transaction operation node -

swstresback Required Transaction operation node -

swstresrst Required Transaction operation node -

Configuration management stgcmmodnode Required Transaction

operation node -

swsrpsetvol Required Transaction operation node -

swsrpvolinfo Required Transaction operation node -

swsrpdelvol Required Transaction operation node -

swsrpstartsync Required Transaction operation node -

swsrpmake Required Transaction operation node -

swsrpstat Required Transaction operation node -

swsrpcancel Required Transaction operation node -

Replication management

swsrprecoverres Required Transaction operation node -

5.6 General Notes

The following notes apply to the cluster operation in a cluster: · Do not carry out registration of SWSTGNODE by which an environment variable is set as the whole system. For notes that are not specific to cluster operation, see Chapter 9, "Notes on Operations", in the " HP-UX Softek AdvancedCopy Manager Operator's Guide".

5.7 Messages

For messages output by Softek AdvancedCopy Manager, refer to " Softek AdvancedCopy Manager Message Guide".

Chapter 6 Deleting a Cluster Environment

This chapter explains how to delete the cluster environment of a Storage server transaction.

6.1 Flow of the Procedure for Deleting a Cluster Environment

The following figure shows the flow of deleting the cluster environment of a Storage server transaction in cluster operation:

6.2 Procedure for Deleting a Cluster Environment

To delete the cluster environment, use the following procedure: 1. Delete the node.

Use the GUI of the AdvancedCopy Manager to delete the node. 2. Stop the transaction.

Stop the transaction (package) to be deleted. Refer to the manual of MC/ServiceGuard about the stop method of transaction.

3. Mount the shared disk on the secondary node.

19

The shared disk for AdvancedCopy Manager share data checks that it is in the state of unmount on the primary node and the secondary node. Then, Mount the shared disk for AdvancedCopy Manager shared data on the secondary node.

4. Execute the cluster unsetup command on the secondary node. On the secondary node, execute the following command after blocking other users from accessing the shared disk for AdvancedCopy Manager shared data: # /opt/swstorage/bin/stgclunset_mcsg -n Logical-Node-Name

The example of an input: # /opt/swstorage/bin/stgclunset_mcsg -n nodepr

- Check the objects to be deleted. Information about the logical node specified by the command is displayed. Confirm the displayed information, and press the Enter key. AdvancedCopy Manager settings were as follows.


Node type : Secondary

IP Address : 10.10.10.10

SUBNET : 10.10.10.0



Volume Group : vg01

Node name : nodepr

Service : serv1

Function : Server

MODE : Normal

Do you want to continue with un-setting of AdvancedCopy Manager cluster? [default:y] y

When interrupting cluster environmental unsetup processing, "n" is inputted, when continuing processing, "y" is inputted, or press the Enter key.

- The cluster unsetup command is executed on the secondary node. The window indicating cluster unsetup command completion opens. swstf8103 The cluster deletion of the secondary node has been completed. Next, delete the cluster environment of the primary node.

# 5. Mount the shared disk on the primary node.

Unmount the shared disk for AdvancedCopy Manager share data on the secondary node. Then, Mount the shared disk for AdvancedCopy Manager shared data on the primary node.

6. Execute the cluster unsetup command on the primary node. On the primary node, execute the following command after blocking other users from accessing the shared disk for AdvancedCopy Manager shared data: # /opt/swstorage/bin/stgclunset_mcsg -n Logical-Node-Name

The example of an input: # /opt/swstorage/bin/stgclunset_mcsg -n nodepr

- Check the objects to be deleted. Information about the logical node specified by the command is displayed. Confirm the displayed information, and press the Enter key. AdvancedCopy Manager settings were as follows.


Node type : Primary

IP Address : 10.10.10.10

SUBNET : 10.10.10.0



20

Volume Group : vg01

Node name : nodepr

Service : serv1

Function : Server

MODE : Normal

Do you want to continue with un-setting of AdvancedCopy Manager cluster? [default:y] y

When interrupting cluster environmental unsetup processing, "n" is inputted, when continuing processing, "y" is inputted, or press the Enter key.

- The cluster unsetup command is executed on the primary node. The window indicating cluster unsetup command completion opens. swstf8102 The cluster deletion of the primary node has been completed.

# 7. Unmount the shared disk on the primary node.

Unmount the shared disk for AdvancedCopy Manager share data on the primary node. 8. Delete port numbers.

On the primary node and the secondary node, delete the following services defined in /etc/services during cluster setup:

- Communication daemon for transactions: stgxfws_Logical-Node-Name 9. Delete transaction environment.

The starting stop command of Storage server transaction is deleted from the CUSTOMER DEFINE FUNCTIONS section of the package control script of object transaction. The following commands (the start option is included) are deleted from the section at the time of starting. /opt/FJSVswstf/cluster/clproc/SmgrMCSG_Logical-Node-Name start The following commands (the stop option is included) are deleted from the section at the time of a stop. /opt/FJSVswstf/cluster/clproc/SmgrMCSG_Logical-Node-Name stop When not using on transaction the shared disk prepared for AdvancedCopy Manager, the information on a shared disk is also deleted. Moreover, transaction (package) is deleted when transaction will not be used from now on. Refer to the manual of MC/ServiceGuard about the edit method of a control script, the reflection method to other nodes, and the deletion method of a package.

10. Object transaction (package) is started. It carries out this operation and is not required when transaction is deleted in Procedure 9. Refer to the manual of MC/ServiceGuard about the starting method of transaction.

21