ETERNUS SF AdvancedCopy Manager Operator's Guide for cluster environment 13.0 -Microsoft(R) Windows(R) 2000/Microsoft(R) Windows Sever(TM) 2003-, -Solaris-, -HP-UX-, -Linux-, -AIX-

Contents Index

Chapter 3 Preparations for Customizing Storage Management Server Transactions, Storage Server Transactions, and Tape Server Transactions

This chapter explains the resources and input items that are required to customize Storage Management Server transactions, Storage Server transactions, and Tape Server transactions.

3.1 Resource

The following resources are necessary to install AdvancedCopy Manager on a cluster system:

For details on Solaris version SynfinityCLUSTER /PRIMECLUSTER, see "Resources required for Solaris version SynfinityCLUSTER /PRIMECLUSTER" in this manual.

For details on Solaris version VERITAS Cluster Server, see "Resources required for Solaris version VERITAS Cluster Server" in this manual.

For details on Linux version PRIMECLUSTER, see "Resources required for Linux version PRIMECLUSTER" in this manual.

For details on Windows version MSCS, see "Resources required for Windows version MSCS" in this manual.

For details on HP version MC/ServiceGuard, see "Resources required for HP version MC/ServiceGuard" in this manual.

For details on HP version VERITAS Cluster Server, see "Resources required for HP ersion VERITAS Cluster Server" in this manual.

For details on AIX version VERITAS Cluster Server, see "Resources required for AIX version VERITAS Cluster Server" in this manual.

For details on AIX version High Availability Cluster Multi-Processing, see "Resources required for AIX version High Availability Cluster Multi-Processing" in this manual.

3.1.1 Resource required for Solaris version SynfinityCLUSTER/PRIMECLUSTER

The following resources are required when installing AdvancedCopy Manager on the Solaris edition of SynfinityCluster or PRIMECLUSTER.

1. Takeover IP address for AdvancedCopy Manager

   Allocate an IP address that is used during cluster system operations and that is unique on the network. This IP address is required for each AdvancedCopy Manager transaction.
   Fujitsu recommends preparing and adding a new logical IP address to be used by AdvancedCopy Manager.
   When allocating a new IP address, confirm that adding the IP address will not adversely affect other transactions, by checking whether any existing transactions use the IP address as a takeover resource.
   If an existing logical IP address is used, ensure that there are no problems (for example, restrictions) as a result of sharing the logical IP address between AdvancedCopy Manager and existing products already using the address.

2. Partition where shared data for AdvancedCopy Manager is stored

   Prepare a partition on the shared disk that stores the shared data used by AdvancedCopy Manager.The number of partitions required is shown in the following table. Make sure that the required number of partitions are prepared for each AdvancedCopy Manager transaction.Refer to "Capacity of a shared disk" for information on the disk space that should be reserved on the shared disk.

   Name	Storage Management Server transaction	Storage Server transaction	Tape Server transaction
   Shared disk for AdvancedCopy Manager repository	4 or 3 or 2 or 1 or 0	0	0
   Shared disk for AdvancedCopy Manager shared data	1	1	0
   Shared disk for TSM shared data	0	0	1
   Total number of partitions	5 or 4 or 3 or 2 or 1	1	1+a*1

   
   

   *1If a Tape Server transaction coexists with a Storage Management Server transaction, "a" is the total number of partitions for the Storage Management Server transaction.
   If a Tape Server transaction coexists with a Storage Server transaction, "a" is the total number of partitions for the Storage Server transaction.

   Each of the partitions of the shared disk for the AdvancedCopy Manager repository is used for the database area stored in the following four directories:

• The directory for database file (This can be created on the shared disk for AdvancedCopy Manager shared data.)

• The directory for RDB dictionary (This can be created on the shared disk for AdvancedCopy Manager shared data.)

• The directory for RDB log file (This can be created on the shared disk for AdvancedCopy Manager shared data.)

• The directory for repository data storage database space (This can be created on the shared disk for AdvancedCopy Manager shared data.)

  

• Define the shared disks for AdvancedCopy Manager shared data and the AdvancedCopy Manager repository as SynfinityCluster or PRIMECLUSTER shared disks.

• Allocate shared disks for AdvancedCopy Manager shared data and the AdvancedCopy Manager repository that are not involved in AdvancedCopy Manager backups or replication

• The four directories can be created on the same shared disk that includes both the shared disk for the AdvancedCopy Manager repository and the shared disk for AdvancedCopy Manager shared data. However, in consideration of replicability and update performance, Fujitsu recommends each directory be created in a separate partition.

• The shared disk for AdvancedCopy Manager shared data and the shared disk for the AdvancedCopy Manager repository are used for file systems. Make arrangements so that these disks can be mounted.

• Refer to "GDS initial settings" in the PRIMECLUSTER Installation Guide for information on how to set up PRIMECLUSTER shared disks and file systems.
  Register these file systems (both the shared disk for AdvancedCopy Manager shared data and the shared disk for the AdvancedCopy Manager repository) as Fsystem resources in the procedure described in "Customization operation details" in this manual.Perform the steps described in "Prior settings" under "Setting up Fsystem resources" in the PRIMECLUSTER Installation Guide.

• Refer to "Setting up shared disk devices" in the SynfinityCluster Installation Guide for information on how to set up SynfinityCluster shared disks and file systems.
  Use the shared disk for the AdvancedCopy Manager repository and the shared disk for AdvancedCopy Manager shared data as file systems.Perform the procedure in "Using as file systems" under "Setting up Slice and Mount Information" in the SynfinityCluster Installation Guide.

• Refer to the TSM manuals for information about TSM shared disks.

3.1.2 Resource required for Solaris version VERITAS Cluster Server

The following resources are necessary to install AdvancedCopy Manager on a Solaris version VERITAS Cluster Server:

1. Takeover IP address for 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.
   Fujitsu recommends preparing and adding a new logical IP address for AdvancedCopy Manager.
   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.
   To use an existing logical IP address, make sure that sharing the logical IP address with AdvancedCopy Manager does not cause a problem in (does not restrict) existing products that already use the logical IP address.

2. Partition where shared data for AdvancedCopy Manager is stored

   Prepare partitions on the shared disks on which to store shared data for 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 "Capacity of a shared disk".

   Name	Storage management server transaction	Storage server transaction
   Shared disk for AdvancedCopy Manager repository	4 or 3 or 2 or 1 or 0	0
   Shared disk for AdvancedCopy Manager shared data	1	1
   Total number of partitions	5 or 4 or 3 or 2 or 1	1

   Each of the partitions of the shared disk for the AdvancedCopy Manager repository is used for the database area stored in the following four directories:

• The directory for database file (This can be created on the shared disk for AdvancedCopy Manager shared data.)

• The directory for RDB dictionary (This can be created on the shared disk for AdvancedCopy Manager shared data.)

• The directory for RDB log file (This can be created on the shared disk for AdvancedCopy Manager shared data.)

• The directory for repository data storage database space (This can be created on the shared disk for AdvancedCopy Manager shared data.)

  

• Define the shared disk for AdvancedCopy Manager shared data and the shared disk for the AdvancedCopy Manager repository as the shared disk used by VERITAS Cluster Server.

• Assign a disk that is not backed up or replicated using AdvancedCopy Manager as the shared disk for AdvancedCopy Manager shared data and the shared disk for the AdvancedCopy Manager repository.

• The four directories can be created on the same shared disk that includes both the shared disk for the AdvancedCopy Manager repository and the shared disk for AdvancedCopy Manager shared data. However, in consideration of replicability and update performance, Fujitsu recommends each directory be created in a separate partition.

• The shared disk for AdvancedCopy Manager shared data and the shared disk for the AdvancedCopy Manager repository are used for file systems. Make arrangements so that these disks can be mounted.

3.1.3 Resource required for Linux version PRIMECLUSTER

The following resources are necessary to install AdvancedCopy Manager on a Linux version PRIMECLUSTER:

1. Takeover IP address for AdvancedCopy Manager

   Allocate a new IP address that is unique in the network for use in cluster system operations.
   Fujitsu recommends preparing and adding a new logical IP address for AdvancedCopy Manager.
   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 Gls resource has no adverse effect on transactions. To use an existing logical IP address, make sure that sharing the logical IP address with AdvancedCopy Manager does not cause a problem in (does not restrict) existing products that already use the logical IP address.

2. Partition where shared data for AdvancedCopy Manager is stored

   Prepare partitions on the shared disks on which to store shared data for 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 for AdvancedCopy Manager shared data, see "Capacity of a shared disk".

   Name	Storage management server transaction	Storage server transaction
   Shared disk for AdvancedCopy Manager repository	4 or 3 or 2 or 1 or 0	0
   Shared disk for AdvancedCopy Manager shared data	1	1
   Total number of partitions	5 or 4 or 3 or 2 or 1	1

   
   

   Each of the partitions of the shared disk for the AdvancedCopy Manager repository is used for the database area stored in the following four directories:

• The directory for database file (This can be created on the shared disk for AdvancedCopy Manager shared data.)

• The directory for RDB dictionary (This can be created on the shared disk for AdvancedCopy Manager shared data.)

• The directory for RDB log file (This can be created on the shared disk for AdvancedCopy Manager shared data.)

• The directory for repository data storage database space (This can be created on the shared disk for AdvancedCopy Manager shared data.)

  

• Define the shared disk for AdvancedCopy Manager shared data and that for the AdvancedCopy Manager repository as the shared disk used by PRIMECLUSTER.

• Assign a disk that is not backed up or replicated using AdvancedCopy Manager as the shared disk for AdvancedCopy Manager shared data and the shared disk for the AdvancedCopy Manager repository.

• The four directories can be created on the same shared disk that includes both the shared disk for the AdvancedCopy Manager repository and the shared disk for AdvancedCopy Manager shared data. However, in consideration of replicability and update performance, Fujitsu recommends each directory be created in a separate partition.

• The shared disk for AdvancedCopy Manager shared data and the shared disk for the AdvancedCopy Manager repository are used for file systems. Make arrangements so that these disks can be mounted.

• For information on how to set up the PRIMECLUSTER shared disk and file system, see the "Initial GDS Setup" section in the "PRIMECLUSTER Installation and Administration Guide."
  Register the file system (the shared disk for AdvancedCopy Manager shared data or the DB file system) as an Fsystem resource by following the procedure provided in "Customization Procedure". Follow the instructions for "Preparatory settings" in the "Setting Up Fsystem Resources" section in the "PRIMECLUSTER Installation and Administration Guide."

3.1.4 Resources required for Windows version MSCS

The following resources are necessary to install AdvancedCopy Manager on a Windows-version MSCS:

1. Takeover IP address for 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.
   Fujitsu recommends preparing and adding a new logical IP address for AdvancedCopy Manager.
   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. To use an existing logical IP address, make sure that sharing the logical IP address with AdvancedCopy Manager does not cause a problem in (does not restrict) existing products that already use the logical IP address.

2. Drive letter where shared data for AdvancedCopy Manager is stored

   Prepare drive letter on the shared disks on which to store shared data for AdvancedCopy Manager. The table below lists the numbers of required drive letter. Note that the listed values indicate the numbers of drive letter required for every AdvancedCopy Manager transaction. For more information about the size of the shared disks for AdvancedCopy Manager shared data, see "Capacity of a shared disk".

   Name	Storage management server transaction	Storage server transaction
   Shared disk for AdvancedCopy Manager repository	1 or 0	0
   Shared disk for AdvancedCopy Manager shared data	1	1
   Total number of drive letter	2 or 1	1

   
   

   

• A shared disk for the AdvancedCopy Manager repository and a shared disk for AdvancedCopy Manager shared data can be the same. If so, the shared disk capacity for AdvancedCopy Manager shared data must also include free space for the shared disk capacity of the AdvancedCopy Manager repository.

• Assign a disk that is not backed up or replicated using AdvancedCopy Manager as the shared disk for AdvancedCopy Manager shared data and the shared disk for the AdvancedCopy Manager repository.

• The shared disk used with AdvancedCopy Manager must use disks other than the Quorum disk.

3.1.5 Resources required for HP version MC/ServiceGuard

The following resources are necessary to install AdvancedCopy Manager on a HP-version MC/ServiceGuard:

1. Takeover IP address for 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.
   Fujitsu recommends preparing and adding a new logical IP address for AdvancedCopy Manager.
   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. To use an existing logical IP address, make sure that sharing the logical IP address with AdvancedCopy Manager does not cause a problem in (does not restrict) existing products that already use the logical IP address.

2. Partition where shared data for AdvancedCopy Manager is stored

   Prepare partitions on the shared disks on which to store shared data for AdvancedCopy Manager. The table below lists the numbers of required partitions. Note that the listed values indicate the numbers of partitions required for every AdvancedCopy Manager transaction. For more information about the size of the shared disk for AdvancedCopy Manager shared data, see "Capacity of a shared disk."

   Name	Storage server transaction
   Shared disk for AdvancedCopy Manager share data	1
   Total number of partitions	1

   
   

   

• The shared disk for AdvancedCopy Manager share data is defined as a shared disk of MC/ServiceGuard.

• Assign a disk that is not backed up or replicated using AdvancedCopy Manager as the shared disk for AdvancedCopy Manager shared data and the shared disk for the AdvancedCopy Manager repository.

• The shared disk for AdvancedCopy Manager shared data is used as a file system. Make arrangements to enable mounting of the shared disk for AdvancedCopy Manager shared data.

3.1.6 Resource required for HP version VERITAS Cluster Server

The HP edition of VERITAS Cluster Server has not supported.

3.1.7 Resource required for AIX version VERITAS Cluster Server

The AIX edition of VERITAS Cluster Server has not supported.

3.1.8 Resource required for AIX version High Availability Cluster Multi-Processing

The following resources are necessary to install AdvancedCopy Manager on an AIX version High Availability Cluster Multi-Processing:

1. Takeover IP address for 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.
   Fujitsu recommends preparing and adding a new logical IP address for AdvancedCopy Manager.
   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.
   To use an existing logical IP address, make sure that sharing the logical IP address with AdvancedCopy Manager does not cause a problem in (does not restrict) existing products that already use the logical IP address.

2. Partition where shared data for AdvancedCopy Manager is stored

   Prepare partitions on the shared disks on which to store shared data for 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 "Capacity of a shared disk".

   Name	Storage server transaction
   Shared disk for AdvancedCopy Manager shared data	1
   Total number of partitions	1

   
   

   

• Define the shared disk for AdvancedCopy Manager shared data as the shared disk used by High Availability Cluster Multi-Processing.

• Assign a disk that is not backed up or replicated using AdvancedCopy Manager as the shared disk for AdvancedCopy Manager shared data.

• The shared disk for AdvancedCopy Manager shared data is used as a file system. Make arrangements to enable mounting of the shared disk for AdvancedCopy Manager shared data.

3.2 Capacity of a shared disk

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

3.2.1 Shared disk capacity for the AdvancedCopy Manager repository 

There is no difference in the size of the AdvancedCopy Manager repository between ordinary operation and cluster operation. For information about estimating the shared disk for the AdvancedCopy Manager repository, see "Calculation of Database space" in the ETERNUS SF AdvancedCopy Manager Installation Guide.

3.2.2 Shared disk capacity for AdvancedCopy Manager shared data 

The capacity required for the shared disk used to store AdvancedCopy Manager shared data is as follows:

1. Security operations

   • For the Windows edition of MSCS and the Windows edition of SynfinityCluster:

     Number of transactions * 7 + number of devices/3 + number of cabinets + 13,319 + (number of users)/20 [KB]

   • For all other cases:

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

2. Replication operations

   • If the number of paired replication source/replication destination volumes used for a replication operation is p, use the following formula:
     1.1 * p [KB]

3. Backup operations

   • For the Solaris edition of SynfinityCluster/PRIMECLUSTER, the Solaris edition of VERITAS Cluster Server and the Linux edition of PRIMECLUSTER:

     If the number of backup disks is "a", the number of transaction disks is "b" and the number of DSIs for all database spaces being backed up is "c":

     • To back up Symfoware:
       {(a + b*35) + (b + c*0.5)}/1024 [MB]

     • Without backing up Symfoware:
       {(a + b*35) + (b + c*0.5)}/1024 [MB]

   • For all other cases:

     If the number of backup disks is "a" and the number of transaction disks is "b":
     (a + b*35)/1024 [MB]

4. Capacity required for cluster operation management data

   1,024[KB]

5. Capacity required for Tape Server transaction management data

   A + 300[MB]

   "A" is the value that is given by the formula below, rounded up to the nearest multiple of 20 megabytes.

   If "m", "n" and "o" are the following values:

   m	The number of backups held per transaction volume, including both generation management backups and day number management backups. Add up the number of generation management backups and day number management backups held.
   n	The number of transaction volumes for which tape backups are performed. For Symfoware backup operations, this value is the total number of database spaces.
   o	The total number of backups, restorations, and copies to tape that will be executed simultaneously. For Symfoware backup operations, this value is the total number of database spaces.

   
   

   • To back up Symfoware:
     ((13 + 3 x (n + 1)) x m) + (50 x o x 3) [KB]

   • Without backing up Symfoware:
     ((10+ 3 x (n + 1)) x m) + (50 x o x 2) [KB]

   

   • If a single shared disk is to be used for both the AdvancedCopy Manager repository and the AdvancedCopy Manager shared data, add the size of the shared disk for the AdvancedCopy Manager repository (partition, etc.) that will coexist on the shared disk for AdvancedCopy Manager shared data to the above-mentioned value.

3.2.3 Capacity of Shared Disks for TSM

The capacity required for TSM shared disks is as follows:

Size of TSM database [MB] + 512 MB

The size of the TSM database is the value given by the formula below, rounded up to the nearest multiple of 4 megabytes, plus 1 MB.

If "m", "n" and "o" are the following values:

• To back up Symfoware:
  (n + 1) x m x 700 [byte]

• Without backing up Symfoware:
  (n + 1) x (m x 2) x 700 [byte]

The size of the TSM database can also be used as the value when the TSM database is formatted.

3.3 Confirmation of items

When customizing it, the following items are needed in the Storage management server transaction and the Storage server transaction.
After understanding the meaning of each item, prepare and confirm the information to be entered for each cluster transaction to be set up.

• Storage management server transaction

  Items	Solaris		Linux	Windows
  	SynfinityCluster PRIMECLUSTER	VERITAS Cluster Server	PRIMECLUSTER	Microsoft(R) Cluster Server
  Logical node name	Required	Required	Required	Required
  Port number for the transaction communication daemon	Required	Required	Required	Required
  Service name	Required	Required	Required	Required
  Logical IP address	Required	Required	Required	Required
  Shared disk information for AdvancedCopy Manager share data	Required	Required	Required	Required
  Shared disk information for AdvancedCopy Manager repository	Required	Required	Required	Required
  The user name and password for repository access	Required	Required	Required	Required
  User when installing	Unnecessary	Unnecessary	Unnecessary	Required
  Cluster Name	Unnecessary	Unnecessary	Unnecessary	Required
  Disk resource of the shared disk for AdvancedCopy Manager share data	Unnecessary	Unnecessary	Unnecessary	Required
  Network Name	Unnecessary	Unnecessary	Unnecessary	Required
  IP Address Resource	Unnecessary	Unnecessary	Unnecessary	Required
  External Connection Network	Unnecessary	Unnecessary	Unnecessary	Required

  
  

• Storage server transaction

  Items	Solaris		Linux	Windows	HP	AIX
  	SynfinityCluster PRIMECLUSTER	VERITAS Cluster Server	PRIMECLUSTER	Microsoft(R) Cluster Server	MC/ServiceGuard	High Availability Cluster Multi-Processing
  Logical node name	Required	Required	Required	Required	Required	Required
  Port number for the transaction communication daemon	Required	Required	Required	Required	Required	Required
  Service name	Required	Required	Required	Required	Required	Required
  Logical IP address	Required	Required	Required	Required	Required	Required
  Shared disk for AdvancedCopy Manager share data	Required	Required	Required	Required	Required	Required
  User when installing	Unnecessary	Unnecessary	Unnecessary	Required	Unnecessary	Unnecessary
  Cluster Name	Unnecessary	Unnecessary	Unnecessary	Required	Unnecessary	Unnecessary
  Disk resource of the shared disk for AdvancedCopy Manager share data	Unnecessary	Unnecessary	Unnecessary	Required	Unnecessary	Unnecessary
  Network Name	Unnecessary	Unnecessary	Unnecessary	Required	Unnecessary	Unnecessary
  External Connection Network	Unnecessary	Unnecessary	Unnecessary	Required	Unnecessary	Unnecessary
  IP Address Resource	Unnecessary	Unnecessary	Unnecessary	Required	Unnecessary	Unnecessary
  Volume Group Name	Unnecessary	Unnecessary	Unnecessary	Unnecessary	Required	Unnecessary

  
  

• For Tape Server transactions

  Prepare and check the items required for any Storage Management Server transactions or Storage Server transactions that coexist with the Tape Server transaction.

Content of each item

• Logical node name

  It is a name of the logical server in the AdvancedCopy Manager. The user can set any logical node name that does not exceed eight alphanumeric characters.
  For logical node name, see "Cluster transaction and local transaction of AdvancedCopy Manager" in this manual.

  

  13 character strings of the following table cannot be made into a logical node name for Solaris-version SynfinityCluster/PRIMECLUSTER, Solaris-version VERITAS Cluster Server, Linux-version PRIMECLUSTER, HP-version MC/ServiceGuard and AIX-version High Availability Cluster Multi-Processing.

  audit	cluster	cmdevs	config	daemon	data	java
  log	pid	report	samp	sh	tmp

  
  

• Port number for the transaction communication daemon

  Prepare the port number to be allocated to the transaction communication daemon.
  A port number must be an integer from 1024 to 65535 (from 5001 to 65535, in case of Windows-version MSCS) 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.

  

  Make the port number of the communication daemon for Storage management server transaction into a different number from the port number of the communication daemon for local storage server transaction.

• Service name

  It is a name of the cluster transaction.

• Logical IP address

  Refer to the paragraph of "resource required" corresponding to the cluster system of "Resource" in this manual.

  

  The subnet mask is confirmed for Windows-version Microsoft(R) Cluster Server and HP-version MC/ServiceGuard.

• Shared disk information for AdvancedCopy Manager share data

  Refer to the paragraph of "resource required" corresponding to the cluster system of "Resource" in this manual.

• Shared disk information for AdvancedCopy Manager repository

  Refer to the paragraph of "resource required" corresponding to the cluster system of "Resource" in this manual.

• The user name and password for repository access

  Prepare the user name and password for repository access.

  

  The local logon authority is needed for Windows-version Microsoft(R) Cluster Server. When the prepared user name is not registered into a system, register it in the system and add the local logon authority to it by cluster setup command. A user name is registered in a primary node and a secondary node.
  

  It is necessary to register beforehand by all nodes for Solaris-version SynfinityCluster/PRIMECLUSTER, Solaris-version VERITAS Cluster Server, and Linux-version PRIMECLUSTER.

• User when installing

  The user and the password that installs AdvancedCopy Manager are confirmed.

• Cluster Name

  The cluster name specified with Microsoft(R) Cluster Server is confirmed. Refer to the manual of Microsoft(R) Cluster Server for details.

• Disk resource of the shared disk for AdvancedCopy Manager share data

  The disk resource name of the shared disk for AdvancedCopy Manager share data is confirmed.

• Network Name

  When new logical IP address is used, the network name for AdvancedCopy Manager is prepared. AdvancedCopy Manager makes the network resource by this network name. Refer to the manual of Microsoft(R) Cluster Server for details.

• External Connection Network

  When new logical IP address is used, the network name for the external connection specified with Microsoft(R) Cluster Server is confirmed. Refer to the manual of Microsoft(R) Cluster Server for details.

• IP Address Resource

  When existing logical IP address is used, the IP address resource name to which logical IP address is set is confirmed.

• Volume Group Name

  The volume group name of the shared disk for the share data is confirmed.

3.4 Preparing the TSM Cluster Setup Information File 

When TSM server transactions are customized, the sizes of the TSM log and TSM database that are specific to the TSM server must be set in the TSM cluster setup information file (/opt/tivoli/tsm/ CLUS /tsmclsetup.ini), together with the parameters for the server option file (dsmserv.opt).First understand each of the following items, then prepare and check a TSM cluster setup information file for each cluster service (userApplication) set up.

The TSM cluster setup information file (/opt/tivoli/tsm/CLUS/tsmclsetup.ini) records information using the "ini" file format.The information recorded is as follows:
Refer to the "ETERNUS SF TSM Administrator's Guide (Solaris version)" for the detailed information about the value corresponding to each key.

File coding example

[service1]
DBsize=101
RLOGsize=33
TCPPort=1501
SHMPort=1510
TCPNODELAY=yes
BUFPoolsize=32768
LOGPoolsize=2048
TXNGroupmax=256
VOLUMEHistory=/tmp/volhistory.log
DEVCONFig=/tmp/devconfig.log

Contents Index