Top
ETERNUS SF Storage Cruiser V16.9.1 / AdvancedCopy Manager V16.9.1 Cluster Environment Setup Guide
FUJITSU Storage

4.1 Confirmation of Customization Items

The Management Server transaction needs the following items for customization. Confirm and prepare items required for a cluster transaction which you use.

Table 4.1 Items Required During Customization

Items

OS

Windows

Solaris

Linux

Transaction name

Required

Required

Required

Logical IP address

Required

Required

Required

Shared disk for shared data

Required

Required

Required

Disk resource of shared disk for shared data

Required

Required

Required

Resource type

Unnecessary

Required

Required

Cluster name

Required

Unnecessary

Unnecessary

Network name

Required

Unnecessary

Unnecessary

Network for external connections

Required

Unnecessary

Unnecessary

IP address resource

Required

Unnecessary

Unnecessary

Installing user

Required

Unnecessary

Unnecessary

Logical node name

Required

Required

Required

Communication service/daemon port number for transaction

Required

Required

Required

Access volume

Required

Required

Required

Generic script

Required

Required

Required

Each item is explained below.

Transaction name

Name of cluster transaction.

Logical IP address

IP address for data communication with Web Console and Managed Servers.
It is recommended that you use a new logical IP address for ETERNUS SF Manager.

When allocating a new logical IP address, make sure that existing transactions use the IP address as a failover resource and that adding the IP address resource has no adverse effects on transactions.

If you use an existing logical IP address, share it with ETERNUS SF Manager in order to make sure that no trouble occurs with any other product already using this logical IP address.

Shared disk for shared data

Volume for storing shared data of ETERNUS SF Manager.
With regard to such factors as reliability and update performance, it is recommended that you use a new volume created only for ETERNUS SF Manager.

Note

When you specify a shared disk for shared data, be careful about the following points:

  • Define the shared disk for shared data as a shared disk of a clustered system.

  • Allocate a disk that does not use AdvancedCopy Manager to carry out backup and replication.

  • Allocate a disk that is not used by AdvancedCopy Manager CCM as a copy source, copy destination, or access volume.

  • On the shared disk for shared data, create a file system.

  • In order to be used by the file system, make the shared disk mountable.

  • Use a disk that is not used as a Quorum disk. (for Windows only)

Refer to "Required Disk Space for Operation" in "Operating Environment for ETERNUS SF Manager" in the Installation and Setup Guide for information on the disk space required for ETERNUS SF Manager.

Disk resource of shared disk for shared data

Disk resource name of shared disk for shared data.

Resource type

Cmdline resource for registering scripts that start or stop services/daemons (generic scripts).

Cluster name

Cluster name specified in Windows Server Failover Clustering.

Network name

Dedicated network name for ETERNUS SF Manager that is specified when using a new logical IP address.
ETERNUS SF Manager creates a network resource under this network name.

Network for external connections

Network name for external communication specified in Windows Server Failover Clustering, to be specified when using a new logical IP address.

IP address resource

IP address resource name in which logical IP address is set up, to be specified when using an already existing logical IP address.

Installing user

User name and password that were used when installing ETERNUS SF Manager.

Logical node name

Name of logical server for AdvancedCopy Manager.
The user can freely set any logical node name, consisting of alphanumeric characters up to 8 bytes.

In order to determine to which cluster transaction an executed AdvancedCopy Manager function (e.g. backup management command) belongs, AdvancedCopy Manager assigns a unique name (logical node name) to each cluster transaction. If you specify this logical node name in the environment variable SWSTGNODE and execute an AdvancedCopy Manager command, the executed command identifies the applicable cluster transaction and carry out processing accordingly.

When "Logical IP address" and "Communication service/daemon port number for transaction" (stgxfws_logicalNodeName) are set in the processing for adding the AdvancedCopy Manager server, the applicable cluster transaction is added as a server of AdvancedCopy Manager.

Note

13-character strings of the following list cannot be made into a logical node name for PRIMECLUSTER:
audit, cluster, cmdevs, config, daemon, data, java, log, pid, report, samp, sh, tmp

Communication service/daemon port number for transaction

Port number allocated to the communication service/daemon for transactions of AdvancedCopy Manager. Note that the same port number needs to be specified on both the primary and secondary nodes.
Specify the unused number (the number not used for ports of other daemons/services) between 1024 and 65535.

Point

Ensure that the port number of the communication service/daemon for transaction is different from the port number of the communication service/daemon for local transaction or the other communication services/daemons for transaction.

Access volume

This is a volume for issuing Advanced Copy from the CCM Server to ETERNUS Disk storage systems.
It is required for issuing Advanced Copy to ETERNUS Disk storage systems that operate with Copy command via SAN.

From among the logical volumes in the ETERNUS Disk storage system to be backed up for AdvancedCopy Manager CCM, connect one logical volume as an access volume to all nodes making up a clustered system.

Point

When specify a device file of ETERNUS Multipath Driver to an access volume in Solaris or Linux, setup the device file name and system. Refer to the ETERNUS Multipath Driver manual for details.

Generic script

Script for starting or stopping services/daemon.