Softek AdvancedCopy Manager Operator's Guide for cluster

Softek AdvancedCopy Manager Operator's Guide

for cluster environment

VERITAS Cluster Server

10.2

-Solaris OE-

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 eight chapters:

+Chapter 1 Overview

This chapter provides an overview of cluster systems.

+Chapter 2 Installation of Manager function of Softek AdvancedCopy Manager

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

+Chapter 3 Customization of Storage Management Server Transactions

This chapter explains how to customize Storage management server transactions.

+Chapter 4 Installation of Agent function of Softek AdvancedCopy Manager

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

+Chapter 5 Customization of Storage Server Transactions

This chapter explains how to customize Storage server transactions.

+Chapter 6 Starting and Stopping a Service

This chapter explains how to start and stop a service.

+Chapter 7 Operation

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

+Chapter 8 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 User's Guide

This manual explains Web-GUI operation in 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)

i

ii

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.

- 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.

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.

Any cluster belongs one of the following classes: · Failover Groups

In the Failover Groups, a standby node on standby exists to take over transactions from an active node, where transactions are being performed. The following three arrangements are possible:

a. 1:1 active/standby system The cluster consists of one active node and one standby node. The active node performs transactions while the standby node is prepared to become the active node.

b. n:1 active/standby system The cluster consists of n active nodes and one standby node. Each of the n active nodes performs separate transactions while a separate standby node stands by to take over for any failing active nodes.

c. Mutual standby system The cluster consists of two nodes, each operating as an active and a standby node. The two nodes perform separate transactions simultaneously, and each stands by for the other node. If either node fails, the other node takes over the transactions on both nodes.

· Parallel Groups In the scalable class, the cluster is designed for performance improvement and degraded operation when a failure occurs by means of parallel processing on multiple server machines. In contrast to the Failover Groups, nodes in this class of cluster are not divided into active and standby nodes. If a server in a cluster fails, the remaining servers in the cluster operate at a degraded level so that the transaction continues.

For more information, refer to the cluster software manuals.

1.2 Support

Softek AdvancedCopy Manager runs on the following operating systems: · Solaris (TM) 9 Operating Environment · Solaris (TM) 8 Operating Environment · Solaris (TM) 7 Operating Environment · Solaris (TM) 2.6 Operating Environment 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

VERITAS Cluster Server 2.0 · Supported type

Mutual standby system of the Failover Groups 1:1 active/standby system of the Failover Groups

Softek AdvancedCopy Manager does not support the Parallel Groups.

· Storage management server transactions on the storage management server are supported only for

active/standby system operation. None of the functions for Storage management server transactions can be

1

used in mutual standby operation. For information about AdvancedCopy Manager transactions, see Chapter 1.3.1,"Service Groups and transactions."

1.3 Types of Operation

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

1.3.1 Service Groups and transaction

In VERITAS Cluster Server, the unit of cluster system configuration is the Service Groups, and the unit of Service Groups configuration is the resource. Examples of concrete resources are disks, IP addresses, and applications that can be used in a cluster system. These are referred to as disk resources, IP address resources, and application resources, respectively. When these resources are combined, transactions are created in the Service Groups. When such transactions are combined, the Service Groups performs one server transaction. The following figure shows the concept of Service Groups, transactions, and resources in a cluster system.

Cluster operation in Softek AdvancedCopy Manager means to make AdvancedCopy Manager functions available to transactions in a Service Group by incorporating them into the Service Groups. In a Service Group, 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, and a transaction is performed by a storage management server is called a Storage management server transaction.

· There is only one Service Group in a 1:1 active/standby cluster system. Thus, all transactions for cluster

operation are brought together in a Service Group. If you want to use multiple Service Groups, you must build a mutual standby cluster system.

· 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 AdvancedCopy Manager transactions.

1.3.2 Storage server types and server transaction types

In Softek AdvancedCopy Manager, there are two types of servers: storage servers and storage management servers. Similarly, a cluster system in which Manager function of Softek AdvancedCopy Manager is installed is called a storage management server, and 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 and a transaction performed by a storage management server is called a Storage management server transaction (see Chapter 1.3.1, "Service Groups and transactions"). Server transaction type refers to this classification. Server transaction types that can operate on a Storage server are listed in the following table:

2

Storage management server transaction

Storage server transaction

Storage management server (Manager function of Softek AdvancedCopy Manager) Yes Yes(*1)

Storage server (Agent function of Softek AdvancedCopy Manager) No Yes(*1)

Yes(*1): Transaction that can operate in a cluster. In mutual standby operation, this type of transaction can operate in multiple Service Groups. Yes: Transaction that can operate in a cluster. In mutual standby operation, this type of transaction can operate only in one Service Group. No: Transaction that is not contained in the package

A Storage server transaction can be incorporated into multiple Service Groups in a cluster system. Consequently, storage server functions can be used in each Service Group. 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.

A Storage management server transaction, however, cannot be incorporated into multiple Service Groups. As a result, each Storage management server transaction is operated in a single Service Group of the cluster system.

The Storage management server of Softek AdvancedCopy Manager can also use the function of a Storage server. See Chapter 1.2, "Overview of Installation Procedure Depending on Operating Environment," in the Solaris OE Softek AdvancedCopy Manager Installation Guide. The Storage management server transaction can also use the function of a Storage server transaction.

1.3.3 Logical servers and node types

When AdvancedCopy Manager transactions are performed in multiple Service Groups of a mutual standby cluster system, an IP address can be set for each Service Group. This type of IP address, called a logical IP address, makes the server corresponding to a AdvancedCopy Manager transaction appear to exist in the network. This type of server are called a logical server or logical node. In a 1:1 active/standby system, since all transactions for cluster operation must be gathered up in one Service Group in a cluster system, there is only one logical IP address (that is, there is only one logical server). The following figure shows an example of a storage management server in a mutual standby cluster system.

3

A cluster system consists of two physical nodes. In a 1:1 active/standby 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 mutual standby cluster system, on the other hand, the concept of the primary node/secondary node is different in each Service Group because the nodes for active/standby can be selected in each Service Group. In the above figure, for example, the primary node for transaction A and the secondary node for transaction B are physically the same.

· Because a 1:1 active/standby cluster system has only one Service Group, the active node for the Service

Group is also called, physically, the primary node.

1.3.4 Transaction types of applications

The transaction types of a 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 management server transaction


AdvancedCopy Manager local transaction

Configuration management Manager

Active on primary nodeStandby on secondary node

- -

Transaction configuration management Agent


Active on primary node Standby on secondary node

-

Local configuration management Agent - - Active on each node

Repository Active on primary node - -

4

Standby on secondary node

Authentication management


- -

Transaction replication management



-

Local replication management - - Active on each node

Transaction backup management



-

Local backup management - - Active on each node

When a mutual standby cluster system using the storage management servers is built, all Storage management server transactions must be operated on the same logical server in a cluster. It is not possible to divide for operation the resources of Storage management server transactions between two or more logical servers.

The resources of 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. AdvancedCopy Manager 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 an active/standby cluster system

The following explains the state when a failover occurs for a failure in a 1:1 active/standby cluster system.

The above figure shows the concept of failover when it occurs after a failure on the primary node of the logical server operating Storage management server transactions in a storage management server active/standby cluster system. The unit for failover in a cluster system is the logical server. Particularly in an active/standby cluster system, a failover occurs for all transactions because all transactions in cluster operation are together on the logical server.

5

1.3.6 Failover in a mutual standby cluster system

The following explains the state when a failover occurs for a failure in a mutual standby 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 Storage management server transactions in a storage management server mutual standby cluster system. The unit for failover in a cluster system is the logical server. Thus, in a mutual standby 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.

6

Chapter 2 Installation of Manager function of Softek AdvancedCopy Manager

This chapter explains the installation of Manager 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 VERITAS Cluster Server installation and environment settings

In order to operate AdvancedCopy Manager transactions on a cluster system, VERITAS Cluster Server must be installed on each node and the respective environment settings must be made. Confirm the settings of the device name and mount point name for each shared disk.

For details about VERITAS Cluster Server, refer to the "VERITAS Cluster Server 2.0 User's Guide" and the "VERITAS Cluster Server 2.0 Installation Guide".

2.1.2 Preparing resources

The following resources are necessary to install Softek AdvancedCopy Manager on a cluster system: 1. Takeover IP address 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.

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 disks, see Chapter 2.1.3, "Shared disk for AdvancedCopy Manager shared data."

Name Storage management server transaction


Shared disk for AdvancedCopy Manager repository 4 or 3 or 2 0

Shared disk for AdvancedCopy Manager shared data 1 1

Total number of partitions 5 or 4 or 3 1

Each of the four partitions of the shared disk for the AdvancedCopy Manager repository is used for the following four database areas: · Database file system (Shared disk for AdvancedCopy Manager shared data can be substituted.) · Raw device for RDB dictionary · Raw device for RDB log file (Shared disk for AdvancedCopy Manager shared data can be substituted.) · Raw device for repository data storage database space

· Define the shared disk for AdvancedCopy Manager shared data and that for the AdvancedCopy Manager

repository as the shared disk used by VERITAS Cluster Server. · The AdvancedCopy Manager backup function must not be used for the shared disk for AdvancedCopy

Manager shared data. · Please use four new partitions in consideration of the performance etc. when you update reliability. However,

7

when a new partition is insufficient because of the restriction of the environment etc., it is possible to substitute it only for a low device for the DB file system and the RDB log file by the shared disk for AdvancedCopy Manager shared data.

· The mount point for the database file system must be "/SWSTFDB". However, the mount point for the database file system is the mount point for AdvancedCopy Manager shared data, if the shared disk for AdvancedCopy Manager shared data is substituted for the database file system.

2.1.3 Shared disk for AdvancedCopy Manager shared data

The capacity of the shared disk of AdvancedCopy Manager is explained.

2.1.3.1 Shared disk capacity for the AdvancedCopy Manager repository

See Chapter 2.1.4, "Calculation of Database space", in the Solaris OE Softek AdvancedCopy Manager Installation Guide.

2.1.3.2 Shared disk capacity for AdvancedCopy Manager shared data

The capacity required as a shared disk for AdvancedCopy Manager share data is as follows. · In the case of Storage management server transaction

The capacity which totaled 1-5 of the following is needed. 1. Security operations

Number of transactions X 2 + number of devices/3 + number of cabinets + 13,319 + number of users/20 [KB]

2. Replication operation Calculate the shared disk space required for replication operations according to the following formula, 1.1Xp [KB]

3. 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]

4. Cluster management 1,024[KB]

5. When the shared disk for AdvancedCopy Manager shared data is substituted for the database file system or the RDB log file.

Space for the database file system or the RDB log file. See Chapter 2.1.4, "Calculation of Database space", in the Solaris OE Softek AdvancedCopy Manager Installation Guide.

· In the case of Storage server transactions See Chapter 4.1.3, "Capacity of a shared disk."

2.2 Installation and customize of Manager function of Softek AdvancedCopy Manager

Install Manager function of Softek AdvancedCopy Manager. Refer to the Solaris OE installation guide, and install Manager function of Softek AdvancedCopy Manager so that both the primary node and secondary node have the same environment.

Set up the environment of Storage management server. See Chapter 4, "Customization of Storage Management Server," in the Solaris OE Softek AdvancedCopy Manager Installation Guide. Set up the respective environment of Storage management server so that both the primary node and secondary node have the same environment.

· Do not install Manager function of Softek AdvancedCopy Manager on a shared disk. · Execute the cluster setup command to create a database environment. Take care to not create a database

environment (see Chapter 4.3.3, "Database creation," in the Solaris OE Softek AdvancedCopy Manager Installation Guide) in an extension of the installation process.

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

8

Chapter 3 Customization of Storage Management Server Transactions

This chapter explains how to customize Storage management server transactions.

· The database environment is created with the cluster setup command. Do not create a database environment

before executing the cluster setup command. · Before starting customization, decide whether to create a new Service Group for performing Storage

management server transactions or to add the Storage management server transactions to an existing Service Group.

· Do not move Storage management server transactions from a Service Group after setup to another Service Group.

3.1 Preparations

This Chapter explains the preparations required before customization.

3.1.1 Allocating space on the shared disk

For information on checking the amount of space to allocate as a shared disk used for a Service Group, see Chapter 2.1.2, "Preparing resources," and Chapter 2.1.3, "Shared disk for AdvancedCopy Manager shared data."

3.1.2 Confirmation of input items

The cluster setup command prompts for entry 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 Service Group 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 Service Group. 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.

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

· Takeover IP address 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."

· The user name and password for repository access Prepare the user name and password for repository access. Register the user name and password by all the nodes that create Storage management server transaction.

3.2 Flow of Customizing Storage Management Server Transactions

This Chapter describes the flow of setup. Throughout this chapter, the primary node is an active node in a Service Group performing Storage management server transactions, and the secondary node is the standby node in the same group.

9

3.3 Storage Management Server Transaction Customization Procedure

To set up a Storage management server transaction, use the following procedure:

10

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 Management Server Transactions." If the system is restarted in an extension of the installation process of Softek AdvancedCopy Manager, proceed to step 2.

2. Check the preparations. Check each item of Chapter 3.1, "Preparations," for the Service Group to be set up.

3. Mount the shared disk on the primary node. Mount the shared disk for AdvancedCopy Manager shared data (one partition) and that for the AdvancedCopy Manager repository (database file system) on the primary node.

The mount point for the database file system of the shared disk for AdvancedCopy Manager repository must be "/SWSTFDB". However, when the shared disk for AdvancedCopy Manager share data is substituted for database file system, it becomes the mount point of the shared disk for AdvancedCopy Manager share data.

4. Stop the Service Groups. To add a Storage management server transaction to an existing Service Group, stop the applicable Service Group. # hagrp -offline User-Service-Group -sys system-name

system-name: The node name by which the user service group is started 5. Register port numbers.

Register the port numbers 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.

6. Execute the cluster setup command on the primary node. On the primary node, execute the cluster setup command shown below after blocking other users from accessing the shared disk for AdvancedCopy Manager shared data and that for the AdvancedCopy Manager repository. When this command is executed, a repository is created in addition to the cluster being set up. For more information, see the chapter on database creation. # /opt/swstorage/bin/stgclset_vcs -k Primary -m AdvancedCopy-Manager-Shared-Data-Mount-Point -i IP-Address -n Logical-Node-Name -s Service-Name -f mgr

7. Check the setup object. Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key. # /opt/swstorage/bin/stgclset_vcs -k Primary -m /STGMGRDISK -n nodemgr -s manager_service -i 10.10.10.10 -f mgr

AdvancedCopy Manager settings are as follows.

Cluster system : VERITAS Cluster Server

Node type : Primary

IP Address : 10.10.10.10

Mount point : /STGMGRMNT

Node name : nodemgr

Service : STGMGRSRV

Function : Management Server

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

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

8. Start the creation of a common environment for Storage management server transactions. The initial window for setting the common environment opens. Confirm the displayed information, enter "y", and press the Enter key. +--------------------------------------------------------------------+

11

| A common environment for the AdvancedCopy Manager |

| Storage management server will be created. |

| [Notes] |

| Prepare the following partition before starting processing. |

| ================================================================== |

| |

| 1) Partition for the DB file system |

| 2) Partition for the RDB dictionary |

| 3) Partition for the RDB log file |

| 4) Partition for the DB space to store the repository data |

| |

+--------------------------------------------------------------------+

Do you want to continue with processing? [y/n] ==> y 9. Specify the DB device.

The window shown below opens. Enter the device name for the DB file system according to the information in [Note], and press the Enter key. A logical volume name is specified, once pushing the Enter key, a logical volume name is inputted. [When creating on a partition] -----------------------< DB device setting >----------------------

Enter the device name for the DB file system.

( ex. : /dev/dsk/c0t0d0s0 )

[Notes]

For creating on the existing file system,

enter the absolute path name of the directory.

Enter ==> /dev/dsk/c2t0d0s4 [When the shared disk for AdvancedCopy Manager share data is substituted] When the shared disk for AdvancedCopy Manager share data is substituted for database file system, once pushing the Enter key, the mount point name of the shared disk for AdvancedCopy Manager share data is absolutely inputted with a path. -----------------------< DB device setting >----------------------



[Notes]



Enter ==> /STGMGRDISK A similar setting window opens for input of the raw device names for the RDB dictionary, RDB log file, and DB space where repository data is stored. Enter a device name for each item, and press the Enter key after each entry.

12

To enter the name of a device other than a normal device, press the Enter key and then enter the device name.

10. Check the DB device settings. The four device names specified in step 9 are displayed. Confirm the displayed information, enter "y", and press the Enter key. ====================================================================

Device name for the DB file system ......../dev/dsk/c2t0d0s4

Raw device name for the RDB dictionary ..../dev/rdsk/c2t0d0s5

Raw device name for the RDB log file ....../dev/rdsk/c2t0d0s6

Raw device name for the DB space

used to save repository data ..../dev/rdsk/c2t0d0s7

====================================================================

Okay? [y/n] ==> y 11. Confirm the continuation of processing.

After the window for confirming the continuation of processing opens, enter "y", and press the Enter key. +--------------------------------------------------------------------+

| Creation of the AdvancedCopy Manager Storage management |

| server environment will start. |

| ================================================================== |

| |

| Once processing has started, system information is rewritten. |

| Make sure that the environment allows execution |

| before proceeding. |

| |

+--------------------------------------------------------------------+

Do you want to continue with processing? [y/n] ==> y 12. Make the repository access settings.

The window for setting Softek AdvancedCopy Manager repository access opens. Enter a user name and password, and press the Enter key. Enter the user name and password for accessing

the repository of AdvancedCopy Manager.

[Notes]

We recommend you to input a general user other than root.

Username : user

Password :

Password(Re-enter) :

For the point of security, it recommends using not a root user but a general user.

When you delete a user on OS, perform a re-setup with reference to Chapter 7.5.7, "Change of

13

deletion/password of the user who specified it as the repository access user." When you change a password, perform a re-setup with reference to Chapter 7.5.7, "Change of deletion/password of the user who specified it as the repository access user."

13. Terminate the cluster setup command on the primary node. The window indicating password registration and cluster setup command completion opens. Password for accessing the repository has been registered.

Database integrated setup ended normally.

swstf8100 The cluster setup of the primary node has been completed. Next, create

the cluster environment of the secondary node.

# 14. Unmount the shared disks on the primary node.

Unmount the shared disk for AdvancedCopy Manager shared data and that for the AdvancedCopy Manager repository on the primary node.

15. Mount the shared disks on the secondary node. Mount the shared disk for AdvancedCopy Manager shared data and that for the AdvancedCopy Manager repository on the secondary node.

The mount point for the database file system of the shared disk for AdvancedCopy Manager repository must be "/SWSTFDB". However, when the shared disk for AdvancedCopy Manager share data is substituted for database file system, it becomes the mount point of the shared disk for AdvancedCopy Manager share data.

16. Execute the cluster setup command on the secondary node. On the secondary node, execute the cluster setup command shown below after blocking other users from accessing the shared disk for AdvancedCopy Manager shared data and that for the AdvancedCopy Manager repository. When this command is executed, a repository is created in addition to the cluster being set up. For more information, see the chapter on database creation. # /opt/swstorage/bin/stgclset_vcs -k Secondary -m AdvancedCopy-Manager-Shared-Data-Mount-Point

17. Check the setup object. Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key. # /opt/swstorage/bin/stgclset_vcs -k Secondary -m /STGMGRDISK



Node type : Secondary

IP Address : 10.10.10.10


Node name : nodemgr

Service : STGMGRSRV

Function : Management Server



18. Start the creation of a common environment for Storage management server transactions. The initial window for setting the common environment opens. Confirm the displayed information, enter "y", and press the Enter key. +--------------------------------------------------------------------+

14

| A common environment for the AdvancedCopy Manager |

| Storage management server will be created. |

| [Notes] |

| Prepare the following partition before starting processing. |

| ================================================================== |

| |

| 1) Partition for the DB file system |

| | +--------------------------------------------------------------------+

Do you want to continue with processing? [y/n] ==> y 19. Specify the DB device.

The window shown below opens. Enter the device name for the DB file system according to the information in [Note], and press the Enter key. -----------------------< DB device setting >----------------------



[Notes]



Enter ==> /dev/dsk/c2t0d0s3

To enter the name of a device other than a normal device, press the Enter key and then enter the device name.

20. Check the DB device settings. The device name specified in step 19 is displayed. Confirm the displayed information, enter "y", and press the Enter key. ====================================================================

Device name for the DB file system ......../dev/dsk/c2t0d0s3

====================================================================

Okay? [y/n] ==> y 21. Confirm the continuation of processing.

After the window for confirming the continuation of processing opens, enter "y", and press the Enter key. +--------------------------------------------------------------------+

| Creation of the AdvancedCopy Manager Storage management |

| server environment will start. |

| ================================================================== |

| |

| Once processing has started, system information is rewritten. |


15


| |

+--------------------------------------------------------------------+

Do you want to continue with processing? [y/n] ==> y 22. Terminate the cluster setup command on the primary node.

The window indicating cluster setup command completion opens. swstf8101 The cluster setup of the secondary node has been completed.

# 23. Unmount the shared disks on the secondary node.

Unmount the shared disk for AdvancedCopy Manager shared data and that for the AdvancedCopy Manager repository on the secondary node.

24. Create and register a Service Group. Service of AdvancedCopy Manager create and register at a User Service Group. Please add the following types as a resource of AdvancedCopy Manager.

- Application Specify a "/opt/FJSVswstf/cluster/clproc/vcsStart_Logical-Node-Name" to be StartProgram. Specify a "/opt/FJSVswstf/cluster/clproc/vcsStop_Logical-Node-Name" to be StopProgram. Specify a "/opt/FJSVswstf/cluster/clproc/vcsMoni_Logical-Node-Name" to be MonitorProgram.

- MountPoint Register the shared disk for AdvancedCopy Manager share data, and DB file system. When the shared disk for AdvancedCopy Manager share data is substituted for DB file system, it becomes only a shared disk for AdvancedCopy Manager share data.

- IP Register the logic IP address for AdvancedCopy Manager. When using the logic IP address already used on business, it is not necessary to register newly.

Application should set up a dependency after MountPoint and IP to become on-line. Refer to VERITAS Cluster Server User's Guide about a user service group and the creation/registration method of a resource. The User Service Group by the command of VERITAS Cluster Server and the example of creation/registration of a resource are as follows. In this example, User Service Group name is set to "STGMGRSRV", active system node name is set to "node1", standby system node name is set to "node2", and resource (application) name is set to "AdvancedCopy_Manager_appl." VCS config table is saved by another file-name. (It performs by all nodes.) # mv /etc/VRTSvcs/conf/config/main.cf /etc/VRTSvcs/conf/config/main.cf.bk

Place VCS into the read-write enabled state. # haconf -makerw

Define a list of systems used at occurrence of fail-over. Already, when set up into the User Service Group, it is not necessary to set up. The following commands perform a check. # hagrp -display STGMGRSRV -attribute SystemList

# hagrp -display STGMGRSRV -attribute AutoStartList A User Service Group is newly created (it is unnecessary when already set up into the User Service Group). As the system priority sequence, active node has priority over standby node. # hagrp -add STGMGRSRV

# hagrp -modify STGMGRSRV SystemList node1 0 node2 1

# hagrp -modify STGMGRSRV AutoStartList node1 node2 Register applications. A resource (application) is registered into a User Service Group. # hares -add AdvancedCopy-Manager_appl Application STGMGRSRV

Place resources into the enabled state. # hares -modify AdvancedCopy-Manager_appl Enabled 1

Specify a super-user(root) who starts StartProgram, StopProgram, MonitorProgram. # hares -modify AdvancedCopy-Manager_appl User root

16

Specify a start application. When a logical node name is nodemgr, the path of the application for starting becomes "/opt/FJSVswstf/cluster/clproc/vcsStart_nodemgr." # hares -modify AdvancedCopy-Manager_appl StartProgram /opt/FJSVswstf/cluster/clproc/vcsStart_nodemgr

Specify a stop application. When a logical node name is nodemgr, the path of the application for a stop becomes "/opt/FJSVswstf/cluster/clproc/vcsStop_nodemgr." # hares -modify AdvancedCopy-Manager_appl StopProgram /opt/FJSVswstf/cluster/clproc/vcsStop_nodemgr

Specify a monitor application. When a logical node name is nodemgr, the path of monitor application becomes "/opt/FJSVswstf/cluster/clproc/vcsMoni_nodemgr." # hares -modify AdvancedCopy-Manager_appl MonitorProgram /opt/FJSVswstf/cluster/clproc/vcsMoni_nodemgr

The mount information on the shared disk for AdvancedCopy Manager share data is registered. In this example, aresource (mount) name is set to "AdvancedCopy_Manager_mount", and the mount point of shared disk for AdvancedCopy Manager share data is set to "/STGMGRDISK". Register resource into User Service Group. # hares -add AdvancedCopy-Manager_mount Mount STGMGRSRV

Place the resource into the enabled state. # hares -modify AdvancedCopy-Manager_mount Enabled 1

A mount pointer is set as a resource. # hares -modify AdvancedCopy-Manager_mount MountPoint /STGMGRDISK

Specify a block device to be mounted. In this example, the block device of a shared disk is set to "/dev/dsk/c2t0d0s4". # hares -modify AdvancedCopy-Manager_mount BlockDevice /dev/dsk/c2t0d0s4

Specify a file system type for the shared disk. In this example, a file system type is set to vxfs. # hares -modify AdvancedCopy-Manager_mount FSType vxfs

The mount information on AdvancedCopy Manager repository is registered. This operation is not required when the shared disk for AdvancedCopy Manager share data is substituted for DB file system of repository. In this example, a resource (mount) name is set to "AdvancedCopy_Manager_DB". Register resource in User Service Group. # hares -add AdvancedCopy-Manager_DB Mount STGMGRSRV

Place the resource into the enabled state. # hares -modify AdvancedCopy-Manager_DB Enabled 1

The mount pointer of a resource is set up. # hares -modify AdvancedCopy-Manager_DB MountPoint /SWSTFDB

Specify a block device to be mounted. In this example, the block device of a shared disk is set to "/dev/dsk/c0t0d0s4". # hares -modify AdvancedCopy-Manager_DB BlockDevice /dev/dsk/c0t0d0s4

Specify a file system type for the shared disk. In this example, a file system type is set to "vxfs". # hares -modify AdvancedCopy-Manager_DB FSType vxfs

Register a logical address. Already, when set up into the User Service Group, it is not necessary to set up. In this example, a resource (IP address) name is set to "sybase_ip". A resource is registered into a User Service Group. # hares -add sybase_ip IP STGMGRSRV

Place the resource into the enabled state. # hares -modify sybase_ip Enabled 1

Specify a device. In this example, a device is set to "hme0". # hares -modify sybase_ip Device hme0

17

Specify an address. In this example, an IP address is set to "10.10.10.10". # hares -modify sybase_ip Address "10.10.10.10"

Specify the dependency of a resource. # hares -link AdvancedCopy-Manager_appl AdvancedCopy-Manager_DB

# hares -link AdvancedCopy-Manager_appl AdvancedCopy-Manager_mount

# hares -link AdvancedCopy-Manager_appl sybase_ip Reflect the VCS setting and set VCS into the read only mode. # haconf –dump -makero

25. Make the WebServer settings. If WebServer operation requires use of a physical IP address, specify settings so that multiple IP addresses can be used to access WebServer: that is, a physical IP address and a logical IP address. This is necessary because Softek AdvancedCopy Manager in cluster operations accesses WebServer through a logical IP. For the required settings, refer to the applicable WebServer manual. Make the settings as shown below, depending on the server type being used:

- For SunWebServer If a failover occurs, the http service must be restarted so that the corresponding logical IP address is enabled. Modify the following file so that the restart does not occur when a script is executed: /opt/FJSVswstf/cluster/webreset

- For Apache There is no need for settings related to the logical IP address.

- For InfoProvider Pro Because multiple IP addresses cannot be used, set up WebServer so that the logical IP address is used. In such a case, WebServer cannot be accessed using a physical IP address.

26. Start the Service Groups. Start the new User Service Group or the User Service Group stopped in step 4. Please refer to VERITAS Cluster Server User's Guide about the starting method of a User Service Group. The example of starting of the User Service Group by the command of VERITAS Cluster Server is as follows. In this example, a User Service Group name is set to "STGMGRSRV", and an active system node name is set to "node1". # hagrp -online STGMGRSRV -sys node1

27. Create an environment for Storage management server transaction. Use the GUI of AdvancedCopy Manager to create an environment for Storage management server transaction. In using storage server transaction function in storage management server transaction, create an environment for Storage server transaction.

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

For construction of a mutual standby cluster system, see Chapter 5, "Customization of Storage Server Transactions," and construct a cluster for Storage server transactions. This completes customization for an active/standby cluster system.

18

Chapter 4 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."

4.1 Preparations

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

4.1.1 VERITAS Cluster Server installation and environment settings

In order for AdvancedCopy Manager transactions to operate on a cluster system, VERITAS Cluster Server 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 VERITAS Cluster Server, refer to the "VERITAS Cluster Server 2.0 User's Guide" and the "VERITAS Cluster Server 2.0 Installation Guide".

4.1.2 Preparing resources

The following resources are necessary to install Softek AdvancedCopy Manager on a cluster system: 1. Takeover IP address 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.

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. One partition per AdvancedCopy Manager transaction is required. Define the shared disk for AdvancedCopy Manager shared data as a shared disk for VERITAS Cluster Server. However, the AdvancedCopy Manager backup function must not be used on the shared disk for AdvancedCopy Manager shared data. For information about the size of the shared disk for AdvancedCopy Manager shared data, see Chapter 4.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 VERITAS Cluster

Server. · The shared disk for AdvancedCopy Manager share data must not use a AdvancedCopy Manager backup

function and replication function.

4.1.3 Capacity of a shared disk

Capacity required as a shared disk for AdvancedCopy Manager share data of Storage server 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

19

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]

4.2 Installation and customize of Agent function of Softek AdvancedCopy Manager

Install Agent function of Softek AdvancedCopy Manager. Refer to the Solaris OE 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 5, "Customization of Storage Server," in the Solaris OE 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 5, "Customization of Storage Server Transactions."

20

Chapter 5 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 Service

Group. To build a mutual standby cluster system, execute the procedure for the AdvancedCopy Manager cluster setup command as many times as necessary.

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

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

5.1 Preparations

This chapter explains the preparations required before customization.

5.1.1 Allocating space on the shared disk

Please confirm the secured space capacity as a shared disk which each Service Group uses referring to Chapter 4.1.2, "Preparing resources" and Chapter 4.1.3 "Capacity of a shared disk."

5.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 Service Group 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 Service Group. 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 Service Group that performs Storage server transactions independently, prepare a new service name for the Service Group. The user can specify any service name. To add a Storage server transaction to an existing Service Group, confirm in advance the service name of that Service Group.

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

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

5.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 Service Group 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 Service Group that will be set up. This interpretation applies throughout the chapter.

21

5.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 17 for every Service Group 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 5.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.

22

2. Check the preparations. Check each item of Chapter 5.1, "Preparations," for the Service Group to be set up.

3. Mount the shared disk on the primary node. Mount the shared disk for AdvancedCopy Manager shared data on the primary node.

4. Stop the Service Groups. To add a Storage server transaction to an existing Service Group, stop the applicable Service Group. # hagrp -offline User-Service-Group -sys system-name

System-name: The node name by which the user service group is started 5. Register port numbers.

Register the port number for the transaction communication daemon in /etc/services. The /etc/service file looks like the following example:

- Transaction communication daemon: stgxfws_Logical-Node-Name

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

6. 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_vcs -k Primary -m AdvancedCopy-Manager-Shared-Data-Mount-Point -n Logical-Node-Name -s Service-Name

7. Check the setup object. Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key. # /opt/swstorage/bin/stgclset_vcs -k Primary -m /STGAGTMNT -n nodeagt -s STGAGTSRV



Node type : Primary

Mount point : /STGAGTMNT

Node name : nodeagt

Service : STGAGTSRV

Function : Server



8. The cluster setup command is executed on the primary node. The window indicating cluster setup command completion opens. clset_FJSVswstf completed

clset_FJSVswsts completed

clset_FJSVswsrp completed

swstf8100 The cluster setup of the primary node has been completed. Next, create

the cluster environment of the secondary node.

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

Unmount the shared disk for AdvancedCopy Manager shared data on the secondary node. 10. Mount the shared disk on the secondary node.

Mount the shared disk for AdvancedCopy Manager shared data on the secondary node. 11. 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_vcs -k Secondary -m AdvancedCopy-Manager-Shared-Data-Mount-Point

12. Check the setup object.

23

Information about the logical node specified by the command is displayed. After confirming the displayed information, press the Enter key. # /opt/swstorage/bin/stgclset_vcs -k Secondary -m /STGAGTMNT




Mount point : /STGAGTMNT

Node name : nodeagt

Service : STGAGTSRV

Function : Server



13. The cluster setup command is executed on the secondary node. The window indicating cluster setup command completion opens. clset_FJSVswstf completed



swstf8101 The cluster setup of the secondary node has been completed.

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

Unmount the shared disk for AdvancedCopy Manager share data on the secondary node. 15. Create and register a Service Group.

Please add the following types as a resource of AdvancedCopy Manager. - Application

Specify a "/opt/FJSVswstf/cluster/clproc/vcsStart_Logical-Node-Name" to be StartProgram. Specify a "/opt/FJSVswstf/cluster/clproc/vcsStop_Logical-Node-Name" to be StopProgram. Specify a "/opt/FJSVswstf/cluster/clproc/vcsMoni_Logical-Node-Name" to be MonitorProgram.

- MountPoint Register the shared disk for AdvancedCopy Manager share data.

- IP Register the logic IP address for AdvancedCopy Manager. When using the logical IP address already used on business, it is not necessary to register newly.

Application should set up a dependency after MountPoint and IP to become on-line. Refer to VERITAS Cluster Server User's Guide about a user service group and the creation/registration method of a resource. The User Service Group by the command of VERITAS Cluster Server and the example of creation/registration of a resource are as follows. In this example, User Service Group name is set to "STGMGRSRV", active system node name is set to "node1", standby system node name is set to "node2", and resource (application) name is set to "AdvancedCopy_Manager_appl." VCS config table is saved by another file-name. (It performs by all nodes.) # mv /etc/VRTSvcs/conf/config/main.cf /etc/VRTSvcs/conf/config/main.cf.bk


Define a list of systems used at occurrence of fail-over. The following commands perform a check. # hagrp -display STGAGTSRV -attribute SystemList

# hagrp -display STGAGTSRV -attribute AutoStartList A User Service Group is newly created (it is unnecessary when already set up into the User Service Group). As the system priority sequence, active node has priority over standby node. # hagrp -add STGAGTSRV

# hagrp -modify STGAGTSRV SystemList node1 0 node2 1

24

# hagrp -modify STGAGTSRV AutoStartList node1 node2 Register applications. A resource (application) is registered into a User Service Group. # hares -add AdvancedCopy-Manager_appl Application STGAGTSRV

Place resources into the enabled state. # hares -modify AdvancedCopy-Manager_appl Enabled 1

Specify a super-user(root) who starts StartProgram, StopProgram, MonitorProgram. # hares -modify AdvancedCopy-Manager_appl User root

Specify a start application. When a logical node name is nodeagt, the path of the application for starting becomes "/opt/FJSVswstf/cluster/clproc/vcsStart_nodeagt." # hares -modify AdvancedCopy-Manager_appl StartProgram /opt/FJSVswstf/cluster/clproc/vcsStart_nodeagt

Specify a stop application. When a logical node name is nodeagt, the path of the application for a stop becomes "/opt/FJSVswstf/cluster/clproc/vcsStop_nodeagt." # hares -modify AdvancedCopy-Manager_appl StopProgram /opt/FJSVswstf/cluster/clproc/vcsStop_nodeagt

Specify a monitor application. When a logical node name is nodeagt, the path of monitor application becomes "/opt/FJSVswstf/cluster/clproc/vcsMoni_nodeagt." # hares -modify AdvancedCopy-Manager_appl MonitorProgram /opt/FJSVswstf/cluster/clproc/vcsMoni_nodeagt

The mount information on the shared disk for AdvancedCopy Manager share data is registered. In this example, aresource (mount) name is set to "AdvancedCopy_Manager_mount", and the mount point of shared disk for AdvancedCopy Manager share data is set to "/STGMGRDISK". Register resource into User Service Group. # hares -add AdvancedCopy-Manager_mount Mount STGAGTSRV

Place the resource into the enabled state. # hares -modify AdvancedCopy-Manager_mount Enabled 1

A mount pointer is set as a resource. # hares -modify AdvancedCopy-Manager_mount MountPoint /STGAGTMNT

Specify a block device to be mounted. In this example, the block device of a shared disk is set to "/dev/dsk/c2t0d0s4". # hares -modify AdvancedCopy-Manager_mount BlockDevice /dev/dsk/c2t0d0s4

Specify a file system type for the shared disk. In this example, a file system type is set to vxfs. # hares -modify AdvancedCopy-Manager_mount FSType vxfs

Register a logical address. Already, when set up into the User Service Group, it is not necessary to set up. In this example, a resource (IP address) name is set to "sybase_ip". A resource is registered into a User Service Group. # hares -add sybase_ip IP STGAGTSRV

Place the resource into the enabled state. # hares -modify sybase_ip Enabled 1

Specify a device. In this example, a device is set to "hme0". # hares -modify sybase_ip Device hme0

Specify an address. In this example, an IP address is set to "10.12.13.14". # hares -modify sybase_ip Address "10.12.13.14"

Specify the dependency of a resource. # hares -link AdvancedCopy-Manager_appl AdvancedCopy-Manager_mount

# hares -link AdvancedCopy-Manager_appl sybase_i Reflect the VCS setting and set VCS into the read only mode.

25

# haconf -dump -makero 16. Start the Service Groups.

Start the new User Service Group or the User Service Group stopped in step 4. Please refer to VERITAS Cluster Server User's Guide about the starting method of a User Service Group. The example of starting of the User Service Group by the command of VERITAS Cluster Server is as follows. In this example, a User Service Group name is set to "STGMGRSRV", and an active system node name is set to "node1". # hagrp -online STGMGRSRV -sys node1

17. 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 7, "Operation."

26

Chapter 6 Starting and Stopping a Daemon

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

6.1 Daemons that Configure Softek AdvancedCopy Manager

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

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

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 Authentication Daemon Manages the authentication feature

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

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

Daemon type Description

The Communication Daemon

Communicates with the Storage management server and Storage server

6.2 Daemons Composing a Storage Transaction

A Storage management server transaction consists of the following daemons:

[Table 6.3 Daemons composing a Storage management server transaction]

Daemon Description

The Communication Daemon for transaction

A transaction daemon that communicates with a storage server

The RMI Daemon A daemon that manages GUI windows

The RDB Daemon A daemon that performs repository access

The Authentication Daemon A daemon that manages authentication feature

A Storage server transaction consists of the following daemons:

[Table 6.4 Daemons composing a Storage server transaction]

Daemon Description

The Communication Daemon for transaction

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

The following daemons cannot become a Storage management server transaction or Storage server transaction: · The Communication Daemon for local node

6.3 Starting a Daemon

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

27

6.3.1 Starting daemons composing a AdvancedCopy Manager transaction

Listed in Tables 6.3 and 6.4, the different kinds of daemons composing a AdvancedCopy Manager transaction can be started from a cluster system. For the starting method, refer to the applicable cluster software manual.

When starting individually the daemon who constitutes the transaction of AdvancedCopy Manager from a certain reason, the method of starting is as follows. · In the case of a Communication Daemon

It is necessary to start per transaction of AdvancedCopy Manager (for AdvancedCopy Manager local transaction 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 Solaris OE Softek AdvancedCopy Manager Operator's Guide "9.4 Starting and Stopping Daemons" about a starting command.

· In the case of daemons other than Communication Daemons Please start with reference to a Solaris OE Softek AdvancedCopy Manager Operator's Guide "9.4 Starting and stopping Daemons." However, a logical node name is set as an environment variable SWSTGNODE, and a daemon starting command is executed.

6.3.2 Starting the local daemons

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

# /opt/swstorage/bin/startacm

6.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.

6.4.1 Stopping daemons composing a AdvancedCopy Manager transaction

Listed in Tables 6.3 and 6.4, 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 transaction of AdvancedCopy Manager from a certain reason, the method of stopping is as follows. · In the case of a Communication Daemon

It is necessary to stop per transaction of AdvancedCopy Manager (for AdvancedCopy Manager local transaction 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 OE Softek AdvancedCopy Manager Operator's Guide "9.4 Starting and Stopping Daemons" about a stop command.

· In the case of daemons other than Communication Daemons

28

Please stop with reference to a Solaris OE Softek AdvancedCopy Manager Operator's Guide "9.4 Starting and Stopping Deamons." However, a logical node name is set as an environment variable SWSTGNODE, and a daemon stop command is executed.

6.4.2 Stopping the local daemons

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

# /opt/swstorage/bin/stopacm

29

30

Chapter 7 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.

7.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 Use'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 which registered at the time of customize of server transaction and which to the communication demon (stgxfws_Logical-Node-Name) into the Port number column of the [Addition of server], in Softek AdvancedCopy Manager Use's Guide "1.2.5 Server registration method."When numbers other than the port number to the communication demon are inputted into the Port number column, the operation of Softek AdvancedCopy Manager in a cluster system is not performed normally.

· Note that the IP address is editted as a logical IP address in Step 2 of Softek AdvancedCopy Manager use guide "1.2.12.2 Downloading Authentication-Related Files." When a physical IP address is editted, the operation of Softek AdvancedCopy Manager in a cluster system is not performed normally.

7.2 Security Operation Using Authentication Feature

The following notes apply to operation using the authentication feature in a cluster system when operation differs from ordinary operation: · The account information (such as user account, password, group, and user privileges) for the primary node

and for the secondary node must be identical. · The authentication management window size after failover is not inherited. · Use the following procedure to inherit authentication information from the storage management server in a

cluster state to the storage management server in a non-cluster state. 1. Before releasing the cluster environment of Storage management server transactions, execute the

/opt/FJSVswssc/bin/smmkbat command on the primary node of Storage management server transactions in order to extract the definition information. Execute this command as a root user. The extracted information is output as a shell script that includes a command sequence reflecting the definition information. /opt/FJSVswssc/bin/smmkbat -f DEFINITION_INFORMATION_OUTPUT_SHELL_SCRIPT

2. Execute the AdvancedCopy Manager cluster setup command on the Storage management server transaction to release the cluster environment.

3. Execute the definition information output shell script extracted within the Storage management server. In this case, please execute by the root user.

For information about other security operations, see Chapter 3, "Security Operation Using Authentication Feature", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide"

7.3 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. · When you use synchronous high-speed backup, do not register backup volume into cluster transaction. · In cluster system, AdvancedCopy Manager belongs to the service group. Therefore, carry out backup

operation by the active node of a service group. Backup operation cannot be performed from standby node and another service groups.

31

· Before and after processing with the backup/restore by Softek AdvancedCopy Manager, unmount/mount processing of operating volume is fundamentally needed. When operating volume is registered into cluster transaction, carry out the offline/online of an operating volume resource from cluster transaction as substitution of mount/unmount. Or change into offline/online processing from unmount/mount processing performed with the processing script before and after backup/restore. The examples of change of a processing script are shown below. Details about a processing script, see Appendix A, "Preprocessing and Postprocessing of Backup and Restoration", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide". Details of the command used for the offline/online of a resource, refer to the manual of a cluster system.

[Example] the shell script for pre-processing of backup processing(OpcBackup.pre) line97

before /usr/sbin/umount $mount_point 2>/dev/null

after /opt/VRTSvcs/bin/hares -offline <resource name> -sys <system name>

[Example] the shell script for post-processing of backup processing(OpcBackup.post) line103,107,109

before /usr/sbin/mount $device $mount_point 2> /dev/null else

/usr/sbin/mount -F $fs $device $mount_point 2> /dev/null

after /opt/VRTSvcs/bin/hares online <resource name> -sys <system name>

[Example] the shell script for pre-processing of restore processing(OpcRestore.pre) line75

before /usr/sbin/umount $mount_point 2> /dev/null


[Example] the shell script for post-processing of restore processing(OpcRestore.post) line99,103,105




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

7.4 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. · When you use synchronous high-speed backup, do not register replication-destination volume into cluster

transaction. · In cluster system, AdvancedCopy Manager belongs to the service group. Therefore, carry out replication

operation by the active node of a service group. Replication operation cannot be performed from standby node and another service groups.

· In a replication, unmount/mount processing is needed to a replication-source and a replication-destination volume with a command before and after processing. When a replication-source and a replication-destination volume is registered into cluster transaction, carry out the offline/online of a replication-source and a replication-destination volume resource from cluster transaction as substitution of unmount/mount. Or change into offline/online processing from unmount/mount processing performed with the processing script before and after replication. The examples of change of a processing script are shown below. The kinds of the commands which needs unmount/mount processing and details about a processing script, see Appendix C, "Replication script", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide". Details of the command used for the offline/online of a resource, refer to the manual of a cluster system.

[Example] the shell script for preprocessing replication-Source processing(RepSrc.pre) line69



[Example] the shell script for preprocessing replication-Destination processing(RepDst.pre) line69

32



[Example] the shell script for postprocessing of replication-Source processing(RepSrc.post) line92,96,98




[Example] the shell script for postprocessing of replication-Destination processing(RepDst.post) line92,96,98




For information about other replication operations, see Chapter 7, "Replication Operation", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide".

7.5 Operation Maintenance

About Operation Maintenance other than subsequent items, see Chapter 8, "Operation Maintenance", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide".

The following notes apply to database maintenance and to the steps to be taken for a problem when operation differs from ordinary operation: · When saving a database area, allocate a save directory on the shared disk. About Changing the Operating Environment, refer to subsequent clauses.

7.5.1 Changing the IP address of a storage management server transaction

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

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

2. Check whether the function of storage server transaction is used by storage management server transaction. Delete the original volume and replica volume that are set, when the function of storage server transaction is being used, and when the Replication Operation is being used. About deleting an original volume or replica volume, see Chapter 7.6.2, "Deleting an original volume or replica volume", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands".

3. Stop storage management 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 management server transaction. When having stopped, start storage management server transaction. About the starting method, refer to the cluster software manuals.

6. On the storage management server transaction, execute the management server information change command (stgcmmodnode). For the management server information change command, see Chapter 7.6, "Commands".

7. On all the storage servers managed by the concerned storage management server transaction, execute the management server information change command. About the management 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.

8. Restart storage management server transaction. About the method of a stop and starting, refer to the cluster software manuals.

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

- The IP address displayed by the cluster unsetup command is the address specified by the cluster

setup command. It is not a value after IP address change. - When the logical IP address is set as the saved file by Chapter 1.2.12.2, "Downloading

Authentication-Related Files" in "Softek AdvancedCopy Manager User's Guide", it is necessary to reset it as a new logical IP address.

33

7.5.2 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 7.6.2, "Deleting an original volume or replica volume", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "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.5.3 Changing the port number of a storage management server transaction

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


2. Check whether the function of storage server transaction is used by storage management server transaction. Delete the original volume and replica volume that are set, when the function of storage server transaction is being used, and when the Replication Operation is being used. About deleting an original volume or replica volume, see Chapter 7.6.2, "Deleting an original volume or replica volume", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands".

3. Stop storage management 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 management server transaction (stgxfws_Logical-Node-Name) described at /etc/services.

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

6. On the storage management server transaction, execute the management server information change command (stgcmmodnode). For the management server information change command, see Chapter 7.6, "Commands".

7. On all the storage servers managed by the concerned storage management server transaction, execute the management server information change command. About the management 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.

8. Restart storage management server transaction. About the method of a stop and starting, refer to the cluster software manuals.


7.5.4 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 7.6.2, "Deleting an original volume or replica volume", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands".

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

34

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.5.5 Changing the server name of a storage management server transaction

Change the server name of a storage management 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 7.5.8, "Changing the logical node name." 1. Check the operation of storage management server transaction.


2. Check whether the function of storage server transaction is used by storage management server transaction. Perform the following operations when the function of storage server transaction is being used. Delete the device when the Backup Operation is being used. About deleting a device, see Chapter 4.6.2, "Deleting a device ", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "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 7.6.2, "Deleting an original volume or replica volume", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands".

3. 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 server name and select [OK] on the "Change of server" dialog. Or the server name is changed by the server information change command (stgxfwcmmodsrv). About the server information change command, see Chapter 7.6, "Commands".

4. On all the storage servers managed by the concerned storage management server transaction, execute the management server information change command (stgcmmodnode). About the management 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.

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

7.5.6 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 7.5.8, "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 "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "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 7.6.2, "Deleting an original volume or replica volume", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands".

3. 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 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.


35

7.5.7 Change of deletion/password of the user who specified it as the repository access user

Change of deletion/password of the user who specified it as the repository access user as follows: 1. Check the operation of storage management server transaction.


2. Change the repository access user. For more information, see Chapter 8.5.9, "Change of deletion/password of the user who specified it as the repository access user", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands".

7.5.8 Changing the logical node name

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

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

2. In storage management server transaction, check whether the function of storage server transaction is used. Progress to Step 3 when the function of storage server transaction is being used. Progress to Step 4 when the function of storage server transaction is not being used.

3. 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 "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "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 7.6.2, "Deleting an original volume or replica volume", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands".

4. Back up the AdvancedCopy Manager data. In storage management server transaction, backup the following data.

- The repository data. Back up the repository data. About backing up a repository data, see Chapter 8.2.1.1, "Database backup", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide"

- The authentication management list. Back up the authentication management list. About backing up an authentication management list, see Chapter 8.1.4.1, "Backing up an authentication management list", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide"

- The screen file. Back up the screen file. Back up all directories in /opt/swstorage/java/data on active node of storage management server transaction. And back up /etc/opt/FJSVswssc/data/security/root.ini on primary node and secondary node.

In storage server transaction, backup the following data. Or in storage management server transaction that uses the function of storage server transaction, backup the following data.

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

5. In storage server transaction, delete /etc/opt/swstorage/Logical-Node-Name/swnode.ini on active node. 6. Delete a cluster environment.

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

- Do not perform Step 1 in Chapter 8.2, "Procedure for Deleting a Cluster Environment." 7. Customize Storage management server transactions or Storage server transactions.

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

- Specify a new logical node name in the value of -n option of a cluster setup command. - In Storage management server transactions, do not perform Step 27 in Chapter 3.3, "Storage

Management Server Transaction Customization Procedure." In Storage server transactions, do not perform Step 17 in Chapter 5.3, "Details of Storage Server Transaction Customization."

36

8. Start Storage management server transactions or Storage server transactions. About the starting method, refer to the cluster software manuals.

9. Restore the AdvancedCopy Manager data. In storage management server transaction, restore the following data.

- The repository data. Restore the repository data. About backing up a repository data, see Chapter 8.2.1.2, "Database restoration", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide"

- The authentication management list. Restore the authentication management list. About restoring an authentication management list, see Chapter 8.1.4.2, "Restoring an authentication management list", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide"

- The screen file. Restore the screen file. Restore all directories in /opt/swstorage/java/data on active node of storage management server transaction. And restore /etc/opt/FJSVswssc/data/security/root.ini on primary node and secondary node.

In storage server transaction, restore the following data. Or in storage management server transaction that uses the function of storage server transaction, restore the following data.

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

10. Change server name. In Storage management server transactions, perform Step 3 and Step 4 in Chapter 7.5.5, "Changing the server name of a storage management server transaction." In Storage server transactions, perform Step 3 in Chapter 7.5.6, "Changing the server name of a storage server transaction."


7.5.9 Changing the service name

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




- The authentication management list. Back up the authentication management list. About backing up an authentication management list, see Chapter 8.1.4.1, "Backing up an authentication management list", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide."


In storage server transaction, backup the following data. In storage management server transaction, backup the following data.

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


- The backup management list and the recovery control file. Back up a backup management list and a recovery control file. About backing up a backup management list and a recovery control file, see Chapter 8.1.1.1, "Backing up a backup management list and a recovery control file", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands."




37

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

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


- In Storage management server transactions, do not perform Step 27 in Chapter 3.3, "Storage


- Do not change any information other than a service name by the cluster setup command. 7. Start Storage management server transactions or Storage server transactions.

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

In storage management server transaction, restore the following data. - The repository data.

Restore the repository data. About backing up a repository data, see Chapter 8.2.1.2, "Database restoration", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide"



In storage server transaction, restore the following data. In storage management server transaction, 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 and the recovery control file. Restore a backup management list and a recovery control file. About restoring a backup management list and a recovery control file, see Chapter 8.1.1.2, "Restoring a backup management list and recovery control file", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands."


- 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 9.3.3.1, "Resource adjustment command (swsrprecoverres)", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands."

7.5.10 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 management server transaction or storage server transaction.




- The authentication management list.

38

Back up the authentication management list. About backing up an authentication management list, see Chapter 8.1.4.1, "Backing up an authentication management list", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide."


In storage server transaction, backup the following data. In storage management server transaction, backup the following data.







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


- 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 a information about the shared disk of a cluster system. - In Storage management server transactions, do not perform Step 27 in Chapter 3.3, "Storage


6. Start Storage management server transactions or Storage server transactions. About the starting method, refer to the cluster software manuals.

7. Restore the AdvancedCopy Manager data. In storage management server transaction, restore the following data.

- The repository data. Restore the repository data. About backing up a repository data, see Chapter 8.2.1.2, "Database restoration", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide"



In storage server transaction, restore the following data. In storage management server transaction, restore the following data.



- The backup management list and the recovery control file.

39

Restore a backup management list and a recovery control file. About restoring a backup management list and a recovery control file, see Chapter 8.1.1.2, "Restoring a backup management list and recovery control file", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands."



7.5.11 Changing the shared disk for AdvancedCopy Manager repository

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


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


- The authentication management list. Back up the authentication management list. About backing up an authentication management list, see Chapter 8.1.4.1, "Backing up an authentication management list", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide."



In storage management server transaction that uses the function of storage server transaction, back up the following data.



3. Delete a cluster environment. About deleting a cluster environment, see Chapter 8, "Deleting a Cluster Environment."

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

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

- In Storage management server transactions, do not perform Step 27 in Chapter 3.3, "Storage

Management Server Transaction Customization Procedure." 5. Start Storage management server transactions.

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

Restore the following data. - The repository data.

Restore the repository data. About backing up a repository data, see Chapter 8.2.1.2, "Database restoration", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide"

- The authentication management list.

40

Restore the authentication management list. About restoring an authentication management list, see Chapter 8.1.4.2, "Restoring an authentication management list", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide"



In storage management server transaction that uses the function of storage server transaction, restore the following data.

- The backup management list and the recovery control file. Restore a backup management list and a recovery control file. About restoring a backup management list and a recovery control file, see Chapter 8.1.1.2, "Restoring a backup management list and recovery control file", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide" and see Chapter 7.6, "Commands."



7.6 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 9, "Commands", in the "Solaris OE 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

-

Backup management

swstbkpoldisp Required Transaction operation node

-

41

swstbkpoldel Required Transaction operation node

-

swstbackup Required Transaction operation node

-

swstbackstat Required Transaction operation node

-

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

-

stgcmmodnode Required Transaction operation node

-

stgguiipset Unnecessary Transaction operation node

Execute only with Storage management server transaction.

Configuration management

stguserset Unnecessary Transaction operation node


42

stgxfwcmaddsrv Unnecessary Transaction operation node


stgxfwcmmodsrv Unnecessary Transaction operation node


stgxfwcmdelsrv Unnecessary Transaction operation node


stgxfwcmsetdev Unnecessary Transaction operation node


stgxfwcmdeldev Unnecessary Transaction operation node


stgxfwcmdispsrv Unnecessary Transaction operation node


stgxfwcmdispdev Unnecessary Transaction operation node


stgxfwcmdisppat Unnecessary 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

-

43

44

7.7 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 10, "Notes on Operations", in the "Solaris OE Softek AdvancedCopy Manager Operator's Guide".

7.8 Messages

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

Chapter 8 Deleting a Cluster Environment

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

8.1 Flow of the Procedure for Deleting a Cluster Environment

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

8.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. For a Storage management server transaction, however, this operation is not necessary.

45

2. Stop the Service Group. Stop the transaction to be deleted. Please refer to VERITAS Cluster Server User's Guide about the stop method of a user service group. The example of a stop of the user service group by the command of VERITAS Cluster Server is as follows. In this example, a User Service Group name is set to "STGMGRSRV", and an active system node name is set to "node1". # hagrp -offline STGMGRSRV -sys node1

3. Delete resources. Delete the AdvancedCopy Manager resources registered for the target transaction. If Service Groups have been created using only AdvancedCopy Manager resources, delete the whole Service Group. Please refer to VERITAS Cluster Server User's Guide about the deletion method of a user service group and a resource. The user service group by the command of VERITAS Cluster Server and the example of deletion of a resource are as follows. In this example, a user service group name is set to "STGMGRSRV". Moreover, each resource name is carried out as follows.

- Resource name (Application): AdvancedCopy_Manager_appl - Resource name (MountPoint of the shared disk for AdvancedCopy Manager share data):

AdvancedCopy_Manager_mount - Resource name (MountPoint for AdvancedCopy Manager RIPOJITORI): AdvancedCopy_Manager_DB

The resource concerned exists only on Storage management server business. - Resource (name IP):sybase_ip

VCS config table is saved by another file-name. # mv /etc/VRTSvcs/conf/config/main.cf /etc/VRTSvcs/conf/config/main.cf.bk


Delete a resource (Application, MountPoint). # hares -delete AdvancedCopy-Manager_appl

# hares -delete AdvancedCopy-Manager_mount

# hares -delete AdvancedCopy_Manager_DB A resource (IP) is deleted when not using it on transaction. # hares -delete sybase_ip

When deleting transaction, a user service group is deleted. # hagrp -delete STGMGRSRV

Reflect the VCS setting and set VCS into the read only mode. # haconf -dump -makero

4. Mount the shared disk on the secondary node. Mount the shared disk for AdvancedCopy Manager shared data on the secondary node. For a Storage management server transaction, also mount the repository shared disk in the secondary node.

5. 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_vcs -n Logical-Node-Name

6. 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. # /opt/swstorage/bin/stgclunset_vcs -n nodemgr

AdvancedCopy Manager settings were as follows.



IP Address : 10.10.10.10 (In the case of Storage server transaction, it is not displayed.)


46

Node name : nodemgr

Service : STGMGRSRV

Function : Management Server (In the case of Storage server transaction, it is displayed as Server.)

MODE : Normal

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

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

7. Delete the database. For a Storage management server transaction, a window for confirming database deletion opens. Confirm the displayed information, enter "y", and press the Enter key. The window is not displayed in the case of a Storage server transaction. +--------------------------------------------------------------------+

| |

| All of database environments of AdvancedCopy Manager |

| will be deleted. |

| |

| [Notes] |

| Once processing has started, all stored data is discarded. |



| |

+--------------------------------------------------------------------+

Do you want to continue with processing? [y/n] ==> y 8. The cluster unsetup command is executed on the secondary node.

The window indicating cluster unsetup command completion opens. clset_FJSVswssc completed



clset_FJSVswstf completed

swstf8103 The cluster deletion of the secondary node has been completed. Next, delete the cluster environment of the primary node.

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

Unmount the shared disk for AdvancedCopy Manager share data on the secondary node. For a Storage management server transaction, also unmount the repository shared disk on the secondary node.

10. Mount the shared disk on the primary node. Mount the shared disk for AdvancedCopy Manager shared data on the primary node. For a Storage management server transaction, also mount the repository shared disk on the primary node.

11. 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_vcs -n Logical-Node-Name

12. 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. # /opt/swstorage/bin/stgclunset_vcs -n nodemgr

47

48

AdvancedCopy Manager settings were as follows.


Node type : Primary

IP Address : 10.10.10.10 (In the case of Storage server transaction, it is not displayed.)


Node name : nodemgr

Service : STGMGRSRV

Function : Management Server (In the case of Storage server transaction, it is displayed as Server.)

MODE : Normal

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

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

13. Delete the database. For a Storage management server transaction, a window for confirming database deletion opens. Confirm the displayed information, enter "y", and press the Enter key. The window is not displayed in the case of a Storage server transaction. +--------------------------------------------------------------------+

| |

| All of database environments of AdvancedCopy Manager |

| will be deleted. |

| |

| [Notes] |

| Once processing has started, all stored data is discarded. |



| |

+--------------------------------------------------------------------+

Do you want to continue with processing? [y/n] ==> y 14. The cluster unsetup command is executed on the primary node.

The window indicating cluster unsetup command completion opens. clset_FJSVswsrp completed


clset_FJSVswstf completed

swstf8102 The cluster deletion of the primary node has been completed.

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

Unmount the shared disk for AdvancedCopy Manager share data on the primary node. For a Storage management server transaction, also unmount the repository shared disk on the primary node.

16. Delete port numbers. Delete the following services defined in /etc/services during cluster setup. Delete the services on the primary node and the secondary node.

- Communication daemon for transactions: stgxfws_Logical-Node-Name 17. Start the Service Group.

Start the transaction stopped in step 2. This operation is not necessary if the Service Group was deleted in step 3. # hagrp -online User-Service-Group -sys system-name

system-name: The node name which wants to start a user service group

Documents

Softek AdvancedCopy Manager Operator's Guide for cluster