softek advancedcopy manager installation guide 10 › jp › manual › fm_e › d025c...when a new...

Solaris OE

Softek AdvancedCopy Manager Installation Guide

10.2

Preface ++Purpose

This manual explains the installation and customization of the Softek AdvancedCopy Manager.

++Audience

This manual is intended for the system manager in charge of managing the storage by using Softek AdvancedCopy Manager

++Organization

This manual consists of the following chapters 1 through 6 and appendix A through C

+ Chapter 1 Overview of Installation and Environment Setting

This chapter describes the overview of the installation of the Softek AdvancedCopy Manager in different operating environments, as well as the settings of these environments.

+ Chapter 2 Installation of Manager of Softek AdvancedCopy Manager

This chapter describes the procedure of installing of Manager of Softek AdvancedCopy Manager.

+ Chapter 3 Installation of Agent of Softek AdvancedCopy Manager

This chapter describes the procedure of installing of Agent of Softek AdvancedCopy Manager.

+ Chapter 4 Customization of Storage Management Server

This chapter describes the procedure to Customization of the Storage Management Server.

+ Chapter 5 Customization of Storage Server

This chapter describes the procedure to Customization of the Storage Server.

+ Chapter 6 Uninstallation

This chapter describes the procedure to uninstall Softek AdvancedCopy Manager.

+ Appendix A Notes on Customization

This appendix describes notes when Customization works.

+ Appendix B Program Components of Softek AdvancedCopy Manager

This appendix describes Program Components of Softek AdvancedCopy Manager.

+ Appendix C JRE Use Conditions

This appendix describes JRE Use Conditions.

++Softek AdvancedCopy Manager Titles

The set of manuals related to the Softek AdvancedCopy Manager consists of the following: · Softek AdvancedCopy Manager Installation Guide

This manual explains the installing of the Softek AdvancedCopy Manager. · Softek AdvancedCopy Manager operator's Guide

This manual explains the operation of the Softek AdvancedCopy Manager. · Softek AdvancedCopy Manager User's Guide

This manual explains the operation of the Web-GUI for Softek AdvancedCopy Manager. · Softek AdvancedCopy Manager Messages

This manual describes the Softek AdvancedCopy Manager generated messages, and the operator's responses to them.

· Softek AdvancedCopy Manager Operator's Guide for cluster environment This manual explains the installation, customization, and operation of Softek AdvancedCopy Manager when it is used in a cluster system.

It is recommended to familiarize oneself with the operations of the System Walker by first reading the "Softek AdvancedCopy Manager Administrator's Guide", before getting into other manuals of the set.

++ Notes on abbreviations · Microsoft(R) Windows NT(R) Server network operating system Version 4.0 and Microsoft(R) Windows NT(R)

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

i

ii

· Microsoft(R) Windows(R) 2000 Professional, Microsoft(R) Windows(R) 2000 Server, and Microsoft(R) Windows(R) 2000 Advanced Server are abbreviated as Windows2000.

· Microsoft(R) Windows(R) Millennium Edition is abbreviated as Windows Me. · Microsoft(R) Windows(R) XP Home Edition operating system is abbreviated as Windows XP Home Edition. · Microsoft(R) Windows(R) XP Professional operating system is abbreviated as Windows XP Professional. · Solaris (TM) Operating Environment is referred to as Solaris OE. · Softek AdvancedCopy Manager's Manager is abbreviated as AdvancedCopy Manager's Manager. · Softek AdvancedCopy Manager's Agent is AdvancedCopy Manager's Agent. ++Trademarks

Windows, WindowsNT, WindowsXP, SQLserver and Internet Explorer are registered trademarks of Microsoft Corporation.

Netscape logo marks, Netscape product and service names are registered trademarks of Netscape Communications Corporation.

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 a registered trademark exclusively licensed for X/Open Company Limited.

ORACLE is a registered trademark of Oracle Corporation.

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

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

Chapter 1 Overview of Installation and Environment Setting This chapter is an overview of the installation of Softek AdvancedCopy Manager. This chapter also gives a brief description of the environment settings for Softek AdvancedCopy Manager under each operating environment.

In this chapter, the Agent of Softek AdvancedCopy Manager is abbreviated as Agent of AdvancedCopy Manager, and the Manager of Softek AdvancedCopy Manager as Manager of AdvancedCopy Manager.

1.1 Installation Type The Softek AdvancedCopy Manager installation type depends on the operating environment. The operating environment is explained in Section 1.2.

1.1.1 Storage server (Agent of AdvancedCopy Manager) The Storage server is a server which executes the backup business and the replication business that AdvancedCopy Manager offers. The Agent of softek AdvancedCopy Manager is introduced into the Storage server. However, only when the Storage server is one, the Manager of Softek AdvancedCopy Manager is introduced on the system.

1.1.2 Storage management server (Manager of AdvancedCopy Manager) The Storage management server manages the Storage servers and only one Storage management server can be set in the system.

1.2 Overview of Installation Procedure Depending on Operating Environment 1.2.1 When only one Storage server is set In this operating environment, only Manager of AdvancedCopy Manager needs to be installed (Manager of AdvancedCopy Manager includes the Agent functions of AdvancedCopy Manager).

Figure 1.1 When only one Storage server is set

+Installation procedure 1. Install of Manager of Softek AdvancedCopy Manager. For details, see "Chapter 2, Installation of Manager of

Softek AdvancedCopy Manager." 2. Customize the Storage management server. For details, see "Chapter 4, Customization of Storage

Management Server."

1.2.2 When two or more Storage servers are set When two or more AdvancedCopy Manager servers are available, set only one of them up as the Storage management server or set up a new server with no disk drive connected as the Storage management server. Each operation environment is explained below.

1

1.2.2.1 When the Storage server is operated as a Storage management server One of the servers functions as a Storage management server. The Storage management server has a repository where the information on operating and management of all Storage servers is stored.

When many Storage servers exist, all of them compete for accesses to the repository. This will affect other applications running on to the same server. Therefore, the Storage management server should be considered as a dedicated server. For more details see chapter 1.2.2.2 "Setting up the special Storage management server".

When a special Storage management server cannot be prepared with the system configuration, becomes an operation form shown in Figure 1.2. (One Storage management server and others becomes a Storage server.)

Figure 1.2 When the Storage server is operated as a Storage management server

+Installation procedure 1. Install "Manager of Softek AdvancedCopy Manager" on the Storage management server. For details, see

"Chapter 2, Installation of Manager of Softek AdvancedCopy Manager." 2. Customize the Storage management server. For details, see "Chapter 4,Customization of Storage

Management Server." 3. Install the "Agent of Softek AdvancedCopy Manager" on all Storage servers. For details, see "Chapter 3,

Installation of Agent of Softek AdvancedCopy Manager." 4. Customize all Storage servers. For details, see "Chapter 5,Customization of Storage Server."

1.2.2.2 Setting up the special Storage management server This setup composes of two or more Storage servers with a dedicated Storage management server.

Figure 1.3 When a special Storage server is a Storage management server

2

+Installation procedure 1. Install "Manager of Softek AdvancedCopy Manager " on the Storage management server. For details, see

"Chapter 2,Installation of Manager of Softek AdvancedCopy Manager." 2. Customize the Storage management server. For details, see "Chapter 4,Customization of Storage

Management Server." 3. Install "Softek AdvancedCopy Manager's Agent" on all Storage servers. For details, see "Chapter 3,Installation

of Agent of Softek AdvancedCopy Manager." 4. Customize all Storage servers. For details, see "Chapter 5,Customization of Storage Server."

3

Chapter 2 Installation of Manager of Softek AdvancedCopy Manager 2.1 Pre-installation Requirements 2.1.1 System environment The Solaris-version Manager of Softek AdvancedCopy Manager can only be installed under any one of the following Solaris (TM) Operating environments listed below. Any other system environment is not supported. · Solaris (TM) 9 Operating Environment · Solaris (TM) 8 Operating Environment · Solaris (TM) 7 Operating Environment · Solaris (TM) 2.6 Operating Environment

2.1.1.1 Exclusion Software It cannot coexist with the following software. · SystemWalker/StorageMGR-M · SystemWalker/StorageMGR-A Reference to "5.1.1 Check of system environment" of an installation guide, it checks that SystemWalker/StorageMGR is not installed. It uninstalls, when installed.

2.1.2 Symfoware Components Manager of Softek AdvancedCopy Manager contains the internal Symfoware components. Installation of Manager of Softek AdvancedCopy Manager includes the installation of Symfoware. However, if the Symfoware has been previously installed the Symfoware version needs verification.

2.1.2.1 Symfoware Server Component Please confirm the thing whose Symfoware Server is the following levels when Symfoware Server has already been introduced into the server which starts introducing the manager of Softek AdvancedCopy Manager. · 32 bit correspondence version - Symfoware Server Enterprise Edition 2.1.1 or later · 64 bit correspondence version - Symfoware Server Enterprise Edition 3.2 or later - Symfoware Server Enterprise Extended Edition 4.0 or later Please install after Symfoware Server Enterprise Edition 2.1.1 after uninstalling Symfoware Server when Symfoware Server at the level before the above-mentioned since Symfoware Server Enterprise Edition 2.1.1 is introduced.

2.1.3 Other Required Software To operate the Manager of Softek AdvancedCopy Manager, confirm that the following required software has been installed.

2.1.3.1 Web Server Component When the Web screen is used, verify that one of the following Web servers has been installed. If it has not been installed, install it. If only the command is used without the Web screen used, the Web server need not be installed. · InfoProvider Pro2.0 or later · Sun WebServer 1.0/2.0/2.1 · Apache 1.3.3/1.3.4/1.3.9

2.1.4 Calculation of Database space · Repository

Repository for managing the information of devices managed by Softek AdvancedCopy Manager This repository also contains management information regarding backup and replication.

2.1.4.1 Repository The following database areas are required for repositories. · Database file system (An existing filesystem can be used)

5

· Raw device for RDB dictionary · Raw device for RDB log file · Raw device for repository data storage database space (An existing filesystem can be used) Table 2.1 gives the minimum space required for each database.

Table 2.1 Capacity of required database areas

Type Size

Database file system 200(MB)

Raw device for RDB dictionary 50(MB)

Raw device for RDB log file 50(MB)

Raw device for repository data storage database space

See the estimation expression (minimum: 65 MB) given below.

Calculating repository capacity

Capacity (MB) = {[(number of servers x 6 + total number of devices x 11) / 40] x 17+ 512}/ 1024

Number of servers: The total of Storage management servers and managing Storage servers

Total of devices: The total of devices (*1) to be managed by the Softek AdvancedCopy Manager. Note that this total is not the total of devices connected to all the Storage servers.

*1: Depending on the Storage server to be managed, the "device" corresponds to the following:

Storage server type Correspondence to the "device"

Windows Partition

Solaris (TM) Operating Environment Slice

HP-UX LUN

Linux Operating Environment Partition

When the Storage server to be managed is executing mirroring with the SynfinityDISK or PRIMECLUSTER Global Disk Services, the number of devices is equivalent to the total of mirror slices.

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

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 an existing file-system.

· When there are two or more Storage servers, define the number to be estimated as the total number on all Storage servers. When cluster operation is performed, consider not only logical servers but also physical servers.

· Round up any fractions in the calculation results for the terms in the square brackets. · When the calculated capacity is less than 65 MB, use 65 MB as the minimum required size.

If any resulting value from the formula may increase in the future, use a higher memory allotment.

2.2 Installation Refer to the "Solaris OE version Softek AdvancedCopy Manager Install Guide".

6

Chapter 3 Installation of Agent of Softek AdvancedCopy Manager 3.1 Items to check before Installation 3.1.1 Software Environment

3.1.1.1 System environment The Agent of Softek AdvancedCopy Manager can only be installed under any one of the following Solaris (TM) Operating environments listed below. Any other system environment is not supported. · Solaris (TM) 9 Operating Environment · Solaris (TM) 8 Operating Environment · Solaris (TM) 7 Operating Environment · Solaris (TM) 2.6 Operating Environment

3.1.1.2 Exclusive software It is not possible to coexist with the following software. · SystemWalker/StorageMGR-M · SystemWalker/StorageMGR-A Please uninstall it if it is confirmed that SystemWalker/StorageMGR is not installed referring to chapter 3.2.1.1 "Checking the system environment", and is installed.

3.1.2 Hardware Environment To use this software product, the following hardware is required.

3.1.2.1 Memory At least 64 megabytes.

3.1.2.2 Essential hardware The following I/O devices are required to run this software:

Component name Remarks

ETERNUS3000 disk array, GR720, GR730, GR740, GR820, or GR840 disk array

Any one is required.

LAN Card

3.1.3 Static Disk Resources The following section describes the disk space required for this software product.

3.1.3.1 Disk space requirement The following table lists the amount of disk space required for each directory. If necessary, expand the size of the file system.

Item No. Directory Disk space requirements (Unit: megabytes) Remarks

1 /$DIR1 70

2 /$DIR2 0.2

3 /$DIR3 2.2

4 /opt 1.0 · "$DIR1" is the program directory name to be specified when you install this software product. · "$DIR2" is the environment setup directory name to be specified when you install this software product. · "$DIR3" is the variable data storage directory name to be specified when you install this software product.

7

Refer to the initial value of the character code of an install directory for specification of a directory name.

3.1.4 Dynamic Disk Resources The following section describes the amount of dynamic disk space required for this software product.

3.1.4.1 Disk space requirement To use this software product under the following conditions, the space listed in the following table is required for each directory, in addition to that described in Section 3.1.3, "Static Disk Resources," for installation. If there is not enough space, expand the size of the file system.

Item No. Directory Disk space requirement (Unit: megabytes) Operation

1 /$DIR2 (a+35 x b)/1024 For Backup Management

2 /$DIR2 (1.1 x c)/1024 For Replication Management

3 /$DIR2 0.1 Does not exist.

4 /$DIR3 5 Does not exist.

5 /var 13 Does not exist. · "$DIR2" is the program directory name to be specified when you install this software product. · "$DIR3" is the program directory name to be specified when you install this software product. · a: Number of backup disks; b: Number of transaction disks · c: Number of volume pairs for replication management

3.1.5 Memory Requirements To operate this software product under the following conditions, the amount of storage space listed in the following table is required.

Item No.

Memory requirement (Unit: megabytes)

Operation

1 13 Does not exist.

2 10 Executing a 1-slice backup command in 16 slices of transaction volume and 60 slices of backup volume

3.1.6 Swap Space Requirements To operate this software product under the following conditions, the swap space listed in the following table is required. If the requirements exceed the provided swap area, expand it.

Item No.

Swap area (Unit: megabytes)

Operation

1 3.2 Does not exist.

2 11 Executing a 1-slice backup command in 16 slices of transaction volume and 60 slices of backup volume

3.2 Installation The following section explains how to install this software.

3.2.1 Preparation Prior to Installation

3.2.1.1 Checking the system environment 1. Confirm SystemWalker/StorageMGR or Softek AdvancedCopy Manager is not installed.

# pkginfo -l FJSVswsts Uninstall it if the package is output by this operation by the following methods. a. If displayed in the output result as SystemWalker/StorageMGR, SystemWalker/StorageMGR is installed. Distinguish M/A and SE/EE from this output result, confirm the version, and uninstall it referring to installation instructions to which SystemWalker/StorageMGR corresponds.

8

b. Softek AdvancedCopy Manager is installed if displayed in the output result as Softek AdvancedCopy Manager. Uninstall it referring to Chapter 6 "Uninstallation". Whether Softek AdvancedCopy Manager which has already been installed is a manager function or an agent function can be confirmed by the following commands. # pkginfo -l FJSVswscm

If the package is output by this operation, it is a manager function, and an agent function if not output. 2. Confirm whether there is becoming empty enough for the disk to install this software. See 3.1.3 "static disk

resource" for the size of the disk that this software uses. Please set the partition composition of the disk again when there is not an enough becoming empty.

3.2.2 Software Installation 1. Log in to the system as a root (superuser), and then terminate the system.

# shutdown -y -g0 -i0 2. Activate the system in single user mode.

[ok prompt] boot -s Input the following command at the ok prompt. Type Ctrl-d to proceed with normal startup.

(or give root password for system maintenance): superuser password

3. Mount the local file system. [# /usr/sbin/mountall -l

4. Activate the volume-manager, and then mount the CD-ROM(Agent Program DISC2) for this software product. # /etc/init.d/volmgt start

5. When you execute the installation command (swsetup) for this software, multiple packages are installed at one time. The swsetup command calls the pkgadd command, and installs all the packages listed in B.1, " Program Components of Softek AdvancedCopy Manager." # cd CD-ROM mounting-point/agent/solaris

# ./swsetup 6. If SystemWalker/StorageMGR or Softek AdvancedCopy Manager has been installed, either of the following

messages are output, and processing is discontinued. # swsetup: ERROR: SystemWalker/StorageMGR is already installed.

# swsetup: ERROR: Softek AdvancedCopy Manager is already installed.

Uninstall it see section 2.2.1.1, "Checking the system environment" if the above-mentioned message is output. 7. The install directory and the initial value of the character code are displayed. To change the following

information, input "y." To leave the information as is, input "n" or press the Return key. - Install directory for the packages (Program install directory)

The initial value is /opt. - Install directory for the environment setup file (Fixed configuration directory)

The initial value is /etc/opt. - Install directory for the files to be modified, such as log file or temporary file (Modifying configuration

directory) The initial value is /var/opt. # ./swsetup

swsetup: Installer is preparing for installation...

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

| Softek AdvancedCopy Manager |

| 10.2 |

| All Right Reserved, Copyright (C) |

| FUJITSU LIMITED 2003 |

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

Welcome to Softek Setup.

This program will install "Softek AdvancedCopy Manager" on your

9

10

system.

Agent setup...

Default installation settings for this setup are as follows:

Program install directory : /opt

Fixed configuration directory : /etc/opt

Modifying configuration directory : /var/opt

Do you want to change the installation settings? (default: n) [y,n,?,q]

8. When you specify "y" in step 7, also specify the install directory and the character code. Please specify install directory: (default: /opt) [?,q] /opt

Please specify fixed configuration directory: (default: /etc/opt) [?,q] /etc/opt

Please specify modifying configuration directory: (default: /var/opt) [?,q] /var/opt

9. To confirm the message, input "n," or press the Return key. To make any other changes, input "y." Installation settings for this setup are as follows:

Program install directory : /opt

Fixed configuration directory : /etc/opt

Modifying configuration directory : /var/opt

Do you want to change the installation settings? (default: n) [y,n,?,q] 10. To confirm the final message and start the installation, input "y." To cancel the installation, input "n."

Do you want to continue with the installation of this package? [y,n,?] 11. Installation begins. An example of the display is shown below.

swsetup: Starting installation of Softek AdvancedCopy Manager...

Installation of was successful.



. . . 12. When the installation terminates normally, the system outputs the following message.

swsetup: Softek AdvancedCopy Manager was installed successfully. 13. Execute the following commands, and then remove the CD-ROM from the drive.

# cd /

# eject cdrom 14. Reboot the system.

# /usr/sbin/shutdown -y -i6 -g0

3.2.3 Environment Setup after Installation For details on how to set up the environment, see Chapter5, "Customization of Storage Server".

Chapter 4 Customization of Storage Management Server This chapter explains the customization of the Storage management server.

To install and customize the storage management server in AdvancedCopy Manager on an SP series system, refer to the SP Series Installation Guide and the SP Series Operations Guide.

4.1 Flow of Customizing Storage Management Server Set up the storage management server according to the following procedure:

4.2 Setting up the port number (/etc/services file) Operation of the storage management server requires the following port numbers listed below.

Therefore, prepare the port numbers to be used in the storage management server and save them to the/etc/services file.

Figure 4.1 shows the port numbers to be written to the /etc/services file.

[Figure 4.1 Contents of the /etc/services file]

#service-name port-number/protocol-name

stgxfws 1226/tcp

rdaswstf 2004/tcp

rmiswstf 9851/tcp

semswstf 9852/tcp

smaclmgr 4660/tcp

If the port numbers in Figure 4.1 have already been used in the installed system, assign other numbers of available ports.

11

The following messages are outputted when a setup of a port number is mistaken. Check a setup.

Example:

component start : sh /opt/FJSVswstf/bin/stgdbcom start SymfoWARE/RDB for AdvancedCopy Manager has been successfully started !! RDA-SV for AdvancedCopy Manager failed to start !!

4.3 Setting up the Repository This section explains how to set up the repository used to operate the storage management server.

Use the following procedure to set up the repository: 1. Estimation of database area 2. Partition on creation 3. Kernel parameter tuning 4. Database creation

4.3.1 Estimation of database area See Section 2.1.4.1 "Repository"and estimate the size of the database area.

4.3.2 Partition creation As explained in Section 2.1.4.1 " Repository"the following database areas are required: · Database file system (An existing filesystem can be used) · Raw device for RDB dictionary · Raw device for RDB log file (An existing filesystem can be used) · Raw device for repository data storage database space To reserve these database areas, create a partition having the capacity listed in Section 2.1.4.1 "Repository"

For details on creating the partition, refer to the Solaris manuals.

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

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 filesystem and the RDB log file by an existing filesystem

· Do not specify cylinder 0 during raw device creation. · Do not use slice 2 because it generally represents the entire disk. · If the repository is used on a cluster system, create the partitions on a shared disk.

4.3.3 Kernel parameter tuning In the storage management server, the kernel parameters required during operation must be tuned.

To edit the kernel parameters, add a record for tuning to the /etc/system file.

Table 4.1 lists the values for kernel parameter tuning.

If the parameters listed in Table 4.1 have already been set, do the following. For a parameter listed as "Maximum value" in "If parameters have already been set," specify the larger of the current value and the tuning value. For a parameter listed as "Addition," specify the value obtained by adding the tuning value to the current value.

[Table 4.1 Kernel parameter tuning values]

Resource Parameter Description Turning value If parameters have already been set

Shared shmmax Maximum size of 0x25000000(hexadecimal) Maximum value

12

memory shared memory segment

Semaphore semmap Number of entries in semaphore map 300(decimal) Addition

semmni V Number of semaphore IDs 1024(decimal) Addition

semmns Number of semaphores in system

1500(decimal) Addition

semmnu Number of undo structures in system 1024(decimal) Addition

semmsl Maximum number of semaphores for each semaphore ID

200(decimal) Maximum value

Message msgmap Number of entries in message map 300 Addition

msgmax Maximum size of message 4096 Maximum value

msgmnb Maximum number of bytes in queue 8192 Maximum value

msgmni Number of IDs waiting for messages 128 Addition

msgseg Number of message segments (*1) 4096 Addition

msgtql Number of message headers 256 Addition

(*1) The number of message segments is limited to 32,768.

The following is an example of an edited /etc/system file.

set shmsys:shminfo_shmmax = 0x25000000

set semsys:seminfo_semmap = 300

set semsys:seminfo_semmni = 1024

set semsys:seminfo_semmns = 1500

set semsys:seminfo_semmnu = 1024

set semsys:seminfo_semmsl = 200

set msgsys:msginfo_msgmap = 300

set msgsys:msginfo_msgmax = 4096

set msgsys:msginfo_msgmnb = 8192

set msgsys:msginfo_msgmni = 128

set msgsys:msginfo_msgseg = 4096

set msgsys:msginfo_msgtql = 256

To register the new kernel parameter values in the system, reboot the system.

Use the following command to reboot the system:

# cd /


4.3.4 Database creation Use the following procedure to activate the database integration setup and define a database environment and database.

13

· In advance, refer to Section 4.3.1 "Estimation of database area" Section 4.3.2 "Partition creation" and Section

4.3.3 "Kernel parameter tuning" and verify the IP address of the storage management server. · To activate the database integration setup, log in as the root user. · After finishing database creation, refer to Section 8.1.3.1, "Saving databases," in the Softek AdvancedCopy

Manager Operations Guide and save the created database area. · Please use four new partitions in consideration of the performance etc. when you update reliability. However,

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 filesystem and the RDB log file by an existing filesystem

1. Activate the database integration setup. Enter the following command to activate the database integration setup. # /opt/swstorage/bin/stgdbset

If the primary node is to be used on the cluster system, the command need not be entered because it is executed from the cluster setup command.

2. Confirm whether to continue processing. To continue processing, enter "y." To not continue processing, enter "n." In the following display example, the machine name is displayed in parentheses on the second line. ////////////////////////////////////////////////////////////////////

AdvancedCopy Manager Storage management server ( kiku )

Common environment creation

////////////////////////////////////////////////////////////////////

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

| 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 3. Enter the name of the device to contain the database file system.

Enter the device name of the partition that is to be created as a device for the database file system, as described in Section 4.3.2, "Partition creation" if you specify a logical volume name, enter the logical volume name after entering the Enter key without any inputs. If you specify the existing file system in place of a new device for the database file system, enter the absolute path name of the directory on the existing file system after entering the Enter key without any inputs. Execution example when making it on partition ////////////////////////////////////////////////////////////////////


14


////////////////////////////////////////////////////////////////////

-----------------------< DB device setting >----------------------

Enter the device name for the DB file system.

( ex. : /dev/dsk/c0t0d0s0 )

[Notes]

Press the Enter key before entering information

on something other than normal devices.

Enter ==> /dev/dsk/c0t0d0s4 Execution example when substituting it by existing filesystem ////////////////////////////////////////////////////////////////////



////////////////////////////////////////////////////////////////////


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 ==> /aaa 4. Enter the name of a raw device for the RDB dictionary.

Enter the device name of the partition that is to be created as a raw device for the RDB dictionary, as described in Section 4.3.2, "Partition creation" if you specify a logical volume name, enter the logical volume name after entering the Enter key without any inputs. ////////////////////////////////////////////////////////////////////



////////////////////////////////////////////////////////////////////


Enter the raw device name for the RDB dictionary.

( ex. : /dev/rdsk/c0t0d0s1 )

15

[Notes]



Enter ==> /dev/rdsk/c0t0d0s5 5. Enter the name of the raw device for the RDB log file.

Enter the device name of the partition that is to be created as a raw device for the RDB log file, as described in Section 4.3.2, "Partition creation" if you specify a logical volume name, enter the logical volume name after entering the Enter key without any inputs. if you specify the existing file system in place of a new raw device for the RDB log file, enter the absolute path name of the directory on the existing file system after entering the Enter key without any inputs. Execution example when making it on partition ////////////////////////////////////////////////////////////////////



////////////////////////////////////////////////////////////////////


Enter the raw device name for the RDB log file.


[Notes]



Enter ==> /dev/rdsk/c0t0d0s6 Execution example when substituting it by existing filesystem ////////////////////////////////////////////////////////////////////



////////////////////////////////////////////////////////////////////


Enter the raw device name for the RDB log file.


[Notes]

For creating on the existing file system,

enter the absolute path name of the directory.

Enter ==> /bbb 6. Enter the name of a raw device for the repository data storage database space.

16

Enter the device name of the partition that is to be created as a raw device for the repository data storage database space, as described in Section 4.3.2, "Partition creation" if you specify a logical volume name, enter the logical volume name after entering the Enter key without any inputs. ////////////////////////////////////////////////////////////////////



////////////////////////////////////////////////////////////////////


Enter the raw device name for the DB space used to

save repository data.


[Notes]



Enter ==> /dev/rdsk/c0t0d0s7

7. Verify the entered contents.

If the entry is correct, press "y." To reenter the contents, press "n." After "y" is pressed, the entry is checked. If an error is detected, an error message is displayed and control returns to step 2. If "n" is pressed, control returns to step 2. ////////////////////////////////////////////////////////////////////



////////////////////////////////////////////////////////////////////

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

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

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

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

Raw device name for the DB space

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

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

Okay? [y/n] ==> y 8. Confirm whether to continue the creation of the common environment for the storage management server.

To continue creation of the environment for the storage management server, press "y." To stop the process, press "n." ////////////////////////////////////////////////////////////////////

17



////////////////////////////////////////////////////////////////////

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

| 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 9. The common environment of the storage management server is created.

The common environment of the storage management server is created and the results are displayed periodically. An example of the exaction results is shown below.

If the confirmation message for overwriting the RDA-SV definition file is displayed on the screen during the process, press "y."

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

Creation of the database disk environment has started.

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

File system creation in the partition is complete.

Mount point creation and mounting are complete.

Symbolic link creation in the raw device is complete.

The next line is added to /etc/vfstab.

/dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /SWSTFDB ufs 2 yes -

/etc/vfstab data addition is complete.

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

Creation of the database disk environment is complete.

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

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

Creation of database disk environment will start.

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

Creation of a file system in a partition is complete.

Creation of a mounting point and mounting is complete.

Creation of a symbolic link to a raw device is complete.

The following line was added to /etc/vfstab.

18

/dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /SWSTFDB ufs 2

yes -

Data has been added to /etc/vfstab.

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

Creation of database disk environment is complete.

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

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

Creation of database operating environment will start.

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

Copying of the DB definition and setting files are complete.

Creation of a log management file is complete.

Creation of a RDB temporary log file is complete.

Creation of a RDB archive log file is complete.

Creation of a RDB dictionary and RDB directory file is complete.

Activation of RDB is complete.

Definition of the settings for the RDA server definition file is complete.

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

Creation of database operating environment is complete.

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

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

Creation of database will start (basic section).

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

Definition of database is complete.

Definition of database space is complete.

Table definition will start.

..................

Table definition is complete.

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

Creation of database is complete (basic section).

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

・

・

・

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

Setup for replication management is complete.

================================================================== 10. Enter the IP address of the storage management server

If the procedure is not to be used on a cluster system, enter the IP address of the storage management server. If the primary node is used on the cluster system, enter an inheritance IP address. If the contents have been entered correctly, the database integration setup ends.

19

////////////////////////////////////////////////////////////////////


Database integrated setup

////////////////////////////////////////////////////////////////////

Enter the IP address of the Storage management server.

[Notes]

For operating by a logical IP address,

enter a logical IP address.

( format : ???.???.???.??? )

Enter ==> 1.10.11.100

Storage management server has been registered. 11. Enter the user name and password for repository access.

Enter the user name and password for repository access. Enter the registered user name and password.

We will recommend not the root user with high frequency of the password change but a general user to be used by the viewpoint of security. If the contents have been entered correctly, the database integration setup ends. ////////////////////////////////////////////////////////////////////


Database integrated setup

////////////////////////////////////////////////////////////////////

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) :

Password for accessing the repository has been registered.

Database integrated setup ended normally.

Restart the system.

20

# 12. Reboot the system.

Use the following command to reboot the system. # cd /


4.4 Setting up the Web Server The following setting needs to be made to display data from the Web screen. If only the command is used without the Web screen used, the setting does not need to be made. · Web server user settings · Automatic startup of web server

4.4.1 Web server user settings The web server user settings are dependent on web server to be used.

The following sections explain how to set up the directory (alias) for each major web server

The following example of settings is explained with the default installation destination and file name of each web server. If the Web server is used with custom (nondefault) settings, be sure those settings conform to the installation destination and file name used.

4.4.1.1 Setting up SunWebServer 1.0 This section provides an example of setting up the directory (alias) for SunWebServer1.0.

Modify the contents of settings file "/etc/http/httpd.conf" as shown below.

Add the following lines inside the "server( )" section of the settings file:

cache_enable "no"

map /swstorage/ /opt/swstorage/inet/wwwroot/

map /swstorage-j/ /opt/swstorage/java/

map /swstorage-cgi/ /opt/swstorage/inet/cgi-bin/ cgi

map /swstorage-d/ /opt/swstorage/java/data/

Add the following line inside the "url( )" or "url virtual server URL( )" section of the settings file. Rewrite any record containing this line.

cgi_enable "yes"

Note: To use the Softek AdvancedCopy Manager as a virtual server, put the additional line inside the "url virtual server URL( )" section; otherwise, put it inside the "url( )" section.

Add the following line to settings file "/etc/http/mime.types." If "policy" has already been registered, the line need not be added.

application/x-swstf-policy policy

4.4.1.2 Setting up SunWebServer 2.0/2.1 This section provides an example of setting up the directory (alias) for SunWebServer2.0/2.1.

In SunWebServer2.0/2.1, Web server instances can be created, and two or more Web server processes can be activated. Therefore, create instances for Softek AdvancedCopy Manager and set up the server in the settings file for each instance. (The following explanation uses an instance created with the name "swstf.")

Add the following lines to settings file "/var/http/swstf/websites/default_site/conf/map.conf":

map /swstorage/ /opt/swstorage/inet/wwwroot/

map /swstorage-j/ /opt/swstorage/java/

map /swstorage-cgi/ /opt/swstorage/inet/cgi-bin/ cgi

map /swstorage-d/ /opt/swstorage/java/data/

Add the following line to settings file "/var/http/swstf/websites/default_site/conf/default_site.site.conf." Rewrite any line containing this item.

21

22

cgi_enable "yes"

Add the following lines to the section enclosed with "server( )" in settings file "/etc/http/swstf.httpd.conf." Rewrite any record containing these lines.

cache_enable "no"

mime_file "/etc/http/mime.types"

Add the following line to settings file "/etc/http/mime.types." If "policy" has already been registered, the line need not be added.


4.4.1.3 Setting up Apache This section provides an example of setting up the directory (alias) for Apache.

Add the following lines to settings file "/usr/local/apache/etc/srm.conf."("/etc/apache/srm.conf" for Apache 1.3.9)

Lines to be added:

Alias /swstorage/ /opt/swstorage/inet/wwwroot/

Alias /swstorage-j/ /opt/swstorage/java/

Alias /swstorage-d/ /opt/swstorage/java/data/

ScriptAlias /swstorage-cgi/ /opt/swstorage/inet/cgi-bin/

Add the following line to setting file "/usr/local/apache/etc/mime.types" ("/etc/apache/etc/mime.types" for Apache 1.3.9). If "policy" has already been registered, the line need not be added.


4.4.1.4 Setting up InfoProviderPro This section provides an example of setting up InfoProviderPro2.0/3.0.

An alias cannot be set up for InfoProviderPro2.0/3.0. Instead, use the symbolic link function of the UNIX file system.

Move to the accessible directory defined by "acstop" in settings file "/etc/opt/FSUNprovd/HTTPD.conf" and enter the following commands.

Commands to be entered

# ln -s /opt/swstorage/inet/wwwroot swstorage

# ln -s /opt/swstorage/java swstorage-j

# ln -s /opt/swstorage/java/data swstorage-d

Add the following line to settings file "/etc/opt/FSUNprovd/HTTPD.conf."

cgi-path-idnt: /opt/swstorage/inet/cgi-bin swstorage-cgi

Add the following line to setting file "/etc/opt/FSUNprovd/mine." If "policy" has already been registered, the line need not be added.


4.4.2 Setting up automatic startup of the web server The Web server must be operating before it can be used. Therefore, Fujitsu recommends that the web server be started automatically when the storage server machine is started.

For details on automatic starting of the machine, refer to the handbook of the web server program to be used.

4.5 Automatic Activation of Daemons Accessing data from the web screen in the storage management server requires the activation of several daemons of the storage management server. However, the system determines the setup so that all the daemons are automatically activated during database setup and installation. However, separately set up the web server so that it starts up automatically. For more information on setting up the web server, refer to the manual of the relevant web server.

Chapter 5 Customization of Storage Server This chapter explains the customization of the Storage server.

To install and customize the storage server in AdvancedCopy Manager on the SP series, refer to the SP Series Installation Guide and the SP Series Operations Guide.

5.1 Flow of Customizing Storage Server Use the following procedure to set up the storage server:

5.2 Setting up the port number (/etc/services File) Operation of the storage server requires the assignment of port numbers.

Therefore, prepare the port numbers to be used in the storage server and write them in the /etc/services file.

Figure 5.1 shows the contents to be written in the /etc/services file.

[Figure 5.1 Content written to the /etc/services file]

#Service-name port-number/protocol-name stgxfws 1226/tcp

If the port numbers included in Figure 5.1 have already been used in the system, designate unassigned port numbers.

5.3 Automatic Activation of Daemon In the storage server, a variety of daemons must be activated for communication with the storage management server and other storage servers. These daemons are set during installation to be activated automatically.

5.4 Checking Hardware Settings The following setup is required for hardware so that an advanced copy function can be used. Please check to the FUJITSU engineer for details. · A setup of an OPC license. · A setup of OPC table size.

23

Chapter 6 Uninstallation This chapter has described the solution when uninstallation and the maintenance method of a database, and a trouble occur.

6.1 Uninstallation Procedure 6.1.1 Storage server uninstallation In the storage server, execute uninstallation by using the following procedures.

In being cluster operation, it is necessary to delete the environment of all Storage server transaction of Softek AdvancedCopy Manager currently created by the node to uninstall.

6.1.1.1 Deletion of a storage server The Storage server which uninstalls is deleted from a Softek AdvancedCopy Manager management subordinate.

Please refer to "1.2.7 Server deletion method of Softek AdvancedCopy Manager user's guide of server the OS version" of a Storage management server about the deletion method of the Storage server in a Web client.

Please refer to "Server information deletion command (stgxfwcmdelsrv) of Softek AdvancedCopy Manager Operator's guide" about the deletion method of the Storage server in a command.

Please judge the chapter number of the employment guide to refer to by OS of a Storage management server.

6.1.1.2 Evacuation of a script Uninstallation also deletes the shell script used by order [backup restoration] processing and processing before and after a replication. Please evacuate the shell script, when the shell script currently customized is reused.

6.1.1.3 Daemon deactivation Deactivate the daemon of the storage management server with the following command:

# /opt/swstorage/bin/stopacm

6.1.1.4 Cancellation of /etc/services file settings Delete the service that was set as described in Section 5.2,"Setting up the /etc/services File"

25

6.1.1.5 Uninstallation 1. Place the system in superuser mode.

# su 2. Execute the swunsetup command. By executing the swuset command, most of the packages listed in Section

B.1, "Program Components of Agent of Softek AdvancedCopy Manager" are deleted. # /opt/swstorage/setup/stg/swunsetup

- To re-install into another directory after executing the swunsetup command, confirm whether the directory of the package shown in B.1"Program Components of Agent of Softek AdvancedCopy Manager" remains. When the directory remains even if the swunsetup command is executed, remove the directories after saving data if necessary.

3. An FJSVgrapi (GR Series Access API) package should delete this package function after checking not using except Softek AdvancedCopy Manager. # pkgrm FJSVgrapi

4. An FJSVgrapi (GR Series Access API) package should delete this package function after checking not using except Softek AdvancedCopy Manager. # pkgrm FJSVswtrc

6.1.2 Uninstallation of the storage management server Please carry out unset up the following procedures by the Storage management server.

In being cluster operation, it is necessary to delete the environment of all Storage server transaction / Storage management server transaction of Softek AdvancedCopy Manager currently created by the node to uninstall.

6.1.2.1 Evacuation of a script Uninstallation also deletes the shell script used by order [ backup restoration ] processing and processing before and after a replication. Please evacuate the shell script, when the shell script currently customized is reused.

6.1.2.2 Daemon deactivation Deactivate the daemon of the storage management server with the following command:

# /opt/swstorage/bin/stopacm

6.1.2.3 Cancel of repository settings Uninstall the database integration, delete the database and its environment, and cancel the repository settings.

· To uninstall the database integration, log in as a root user. · When the Storage management server is being operated on the cluster system, a repository is deleted by

26

deletion of Storage management server transaction. Therefore, it is not necessary to carry out this operation. 1. Place the system in superuser mode.

# su 2. Uninstall the database integration.

Enter the following command to uninstall the database integration. # /opt/swstorage/bin/stgdbunset

3. Confirm whether to continue processing. To continue processing, enter "y." To stop processing, enter "n." ////////////////////////////////////////////////////////////////////


Database unsetup

////////////////////////////////////////////////////////////////////

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

| |

| All of database environments of AdvancedCopy Manager |

| will be deleted. |

| |

| [Notes] |

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

| Make sure that the environment allows execution |

| before proceeding. |

| |

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

Do you want to continue with processing? [y/n] ==> y 4. Deletion of the storage management server database is complete.

During deletion of the storage management server database, the result is displayed on the screen from time to time. The following is an example of the results of execution.

If an overwrite confirmation message is displayed on the screen during processing, enter "y." ////// AdvancedCopy Manager database unsetup //////

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

The replication management will be deleted.

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

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

Clearing of database will start. (replication management)

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

.

Tables have been deleted. (replication management)

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

Clearing of database is complete. (replication management)

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

27

28

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

The replication management has been deleted.

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

.

.

.

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

Clearing of database environment is complete.

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

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

The basic section has been deleted.

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

Database unsetup ended normally.

#

6.1.2.4 Cancel of /etc/services file settings Delete the service that is set in the description in Section 4.2, "Setting up the port number (/etc/services file)"

6.1.2.5 Uninstallation 1. Place the system in superuser mode.

# su 2. Execute the swunsetup command. By executing the swuset command, most of the packages listed in B.2,

"Program Components of Manager of Softek AdvancedCopy Manager" are deleted. # /opt/swstorage/setup/stg/swunsetup

- To re-install into another directory after executing the swunsetup command, confirm whether the directory of the package shown in B.2 " Program Components of Manager of Softek AdvancedCopy Manager" remains. When the directory remains even if the swunsetup command is executed, remove the directories after saving data if necessary.

3. Before deleting the SymfoWARE (FSUNrdasv,FSUNrdb2b,FSUNiconv) package, some of the functions of which are used by Softek AdvancedCopy Manager, confirm that the package functions are not used by a system other than Softek AdvancedCopy Manager. # pkgrm FSUNrdasv FSUNrdb2b FSUNiconv

4. If Softek AdvancedCopy Manager uses some of the functions of the GR Series Access API (FJSVgrapi) package, the package cannot be deleted by the swunsetup command. Confirm that no other software is using the functions of this package before deleting it. # pkgrm FJSVgrapi

5. A FJSVswtrc package should delete this package function after checking not using except Softek AdvancedCopy Manager. # pkgrm FJSVswtrc

Appendix A Notes on Customization A.1 Repository Database Size The repository database size is estimated by using the [Calculating repository capacity]. Following should be noted: · When the estimation result includes a decimal point, round it up. · If the estimation result is less than 65(MB), use at least 65(MB) as the estimated repository size. · When the number of servers and the number of partitions may increase, please calculate for the figure. · If the Storage server to be managed uses SynfinityDISK or PRIMECLUSTER Global Disk Services and when

the number of mirrors and the number of devices may increase, please calculate for the figure.

29

Appendix B Program Components of Softek AdvancedCopy Manager B.1 Program Components of Agent of Softek AdvancedCopy Manager Each of the program units that constitute a system is called a package. Agent of Softek AdvancedCopy Manager product consists of the following packages.

Item No. Package name Version No. Function

1 FJSVgrapi 2.03 GR Series Access API

2 FJSVswsrp 10.1 Replication Management

3 FJSVswstf 10.1 AdvancedCopy Manager Basic

4 FJSVswsts 10.1 Backup Management

5 FJSVswtrc 10.1 Common Trace

B.2 Program Components of Manager of Softek AdvancedCopy Manager Each of the program units that constitute a system is called a package. Manager of Softek AdvancedCopy Manager product consists of the following packages.

Item No. Package name Version No. Function

1 FJSVgrapi 2.03 GR Series Access API

2 FJSVswscm 10.2 AdvancedCopy Manager Online Manual

3 FJSVswsrp 10.2 Replication Management

4 FJSVswssc 10.2 Security Framwork

5 FJSVswstf 10.2 AdvancedCopy Manager Basic

6 FJSVswsts 10.2 Backup Management

7 FJSVswtrc 10.2 Common Trace

8 FSUNiconv 1.1 Iconv Standard Code Converter

9 FSUNrdasv V20L16 SymfoWARE RDA-SV

10 FSUNrdb2b V24L09 SymfoWARE/RDB

31

Appendix C JRE Use Conditions Before using this software product, you must agree to the following articles regarding the handling of the JRE packaged together with this software product.

If you do not agree to these articles, you cannot use this software product.

(1) Observe the JRE use conditions described in the license text file.

The license text file is stored in the following directory:

/opt/FJSVswstf/jre/LICENSE

(2) The JRE packaged together with Softek AdvancedCopy Manager cannot be used for purposes other than Softek AdvancedCopy Manager operation.

Fujitsu shall not be liable for loss or damage caused by using JRE under conditions other than (1) and (2) above.

33

Glossary The special terms used in this manual are explained below.

Advanced copy function

Hardware function of Fujitsu's disk array unit (GR740). Generic name of EC and OPC.

AdvancedCopy Manager client

Generic name of Web-GUIs that operate in a storage management client.

AdvancedCopy Manager library

Database in entire AdvancedCopy Manager including a registry, and SymfoDB.

AdvancedCopy Manager manager

Generic name of AdvancedCopy Manager-related services and applications existing in a storage management server.

Attestation management book

General term of the file where attestation management saves the information in employment.

There are two or more kinds. It is kept for every Storage server with repository.

Backup management agent

Generic name of backup management applications existing in a storage server.

Backup management library

Management library whose backup exists in each storage server.

Backup management manager

Generic name of backup management applications existing in a storage management server.

Backup management screen

Web screen for backup management.

35

Backup server employment

Employment which prepared the server of the exclusive use which only the volume of a copy place is connected and uses a copy place for the purpose of evacuating to tape equipment.

Backup synchronous processing

Processing for matching a transaction volume and backup volume in preparation for synchronous backup operation

CA (Channel adapter)

The adapter card used as an interface with server HBA / switch carried in a Storage side.

EC

Short for Equivalent Copy. The hardware functions of the disk array equipment (GR740) of our company. The function to hold the mirror state between disks within hardware. The duplicate of a disk is created by carrying out separation control from software.

Equivalency maintenance state

A state in which the EC function maintains the contents of a transaction volume and backup volume equivalent

Fabric

Topology using the fiber channel interface. A fiber channel switch is used and two or more communications between nodes can be performed simultaneously.

FC-AL (Fiber Channel Arbitrated Loop)

Topology using the fiber channel interface. a fiber channel -- by using a hub, it is realizable of connection between two or more nodes Topology most used by 1 to 1 connection now. A port is NL port or an L port.

FL port

The port of the fabric (fiber channel switch) connected to NL port.

F port

The port of the fabric (fiber channel switch) connected to N port.

36

Framework

Generic name of applications such as communication services and configuration management that operate as the foundation of AdvancedCopy Manager

Generation overflow

When a number of backups specified as backup generations have already been collected, if the next backup is performed, the backup volume having the oldest backup history is deleted from the generation management. This is called generation overflow. The number of backup generations is specified in the backup policy setting command.

GR series

Generic name of Fujitsu's disk array units (GR720/730/740/820/840).

GRmgr

Storage management software of GR720/730/740.

HAB (Host path adapter)

The adapter card used as an interface with the storage port / switch CA carried in a server.

Hard disk driver

Hard disk driver software of a host server. Controls a disk array unit instead of the sd driver. This driver must be installed to perform multipath control.

HDDV

See "Hard disk driver."

Initial screen

Screen displayed first when a browser is started with AdvancedCopy Manager's URL described. Screen that controls a server operating as AdvancedCopy Manager and device information.

LUN (Logical Unit Number)

Abbreviation for Logical Unit Number. Logical unit defined under a channel adapter on a storage unit.

37

LUN Mapping

Assign and set up LUN which shows Logical unit LUN (Logical Unit Number) defined as the channel adapter subordinate in GR720/GR730/GR740 storage equipment from the HOST side, and real LUN (mapping). Thereby, HOST to LUN0 and visible Logical unit can be set up with real Logical unit LUNxx.

MPHD

See "Multipath disk control."

MPLB

See "Multipath disk control, load balance option."

Multipath disk control

Driver software that performs multipath disk control of the host server.

Failover driver software that merges two physical access paths into one logical path to avoid stopping access to a disk array unit because of the failure of one physical access path.

Multi path disk control, load balance option

Driver software that performs multipath disk control of the host server. This driver has a load balance (path load distribution) function and multipath (two to eight paths) function in addition to the multipath disk control failover function. Therefore, it is superior in terms of reliability, operability, and performance enhancement and the most suitable driver software for a SAN operation server.

NL-Private port

The port of the FC-AL topology which has not made fiber channel switch connection.

NL-Public port

The port of the FC-AL topology which is making fiber channel switch connection.

N port

The port used by Fabric topology (switch environment) or Point-to-Point in a fiber channel.

OPC

Abbreviation of one point copy. Hardware function of a Fujitsu's disk array unit (GR740). This function executes disk copy at high speeds in hardware. When software issues a copy request, a physical copy operation is performed in hardware; however, the emulation function makes it look like the copy is completed at the software level.

38

Ordinary transaction volume

Volume to be backed up and not provided with a database space.

Point-to-point

Topology using the fiber channel interface. Although it is the topology of 1 to 1 connection of N port, the mainstream of the 1 to 1 present connection is 1 to 1 connection of FC-AL.

Registry

AdvancedCopy Manager environment definition file.

Replication management book

General term of the file where replication management saves the information in employment.

There are two or more kinds. It is kept for every Storage server with repository.

Repository

The information managed for employment of Softek AdvancedCopy Manager, or its domain.

It is data of the database in a Storage management server.

The information on the device to employ, the information on backup management, the information on replication management, etc. are stored in repository.

Repository is created at the time of Softek AdvancedCopy Manager Installation.

RMI daemon

The RMI server to an AdvancedCopy Manager client.

SAN (storage area network)

Abbreviation of storage area network. Server-storage connection network. In a broad sense, this also refers to the implementation of centralized storage, data sharing among different servers, and storage-integrated management.

Snap shot type high-speed backup

Backup using the one point copy (OPC) function of a GR-series disk array unit.

39

Storage

External storage devices such as disk array and tape units. These devices include GR730, GR740, and F649x series and Spectris/Platinum

Storage management client

Counterpart term for "Storage management server." Machine on which a AdvancedCopy Manager Web-GUI operates.

Storage management server

Server in which SystemWalker/AdvancedCopy Manager's Manager exists.

Storage server

Server in which SystemWalker/AdvancedCopy Manager's Agent exists.

Synchronous backup

Using the Equivalent Copy (EC) function of the disk array GR series to make a backup

40

Top PagePrefaceChapter 1 Overview of Installation and Environment SettingChapter 2 Installation of Manager of Softek AdvancedCopy ManagerChapter 3 Installation of Agent of Softek AdvancedCopy ManagerChapter 4 Customization of Storage Management ServerChapter 5 Customization of Storage ServerChapter 6 UninstallationAppendix A Notes on CustomizationAppendix B Program Components of Softek AdvancedCopy ManagerAppendix C JRE Use ConditionsGlossary

softek advancedcopy manager installation guide 10 › jp › manual › fm_e › d025c...when a new...

Documents