Top
ETERNUS SF AdvancedCopy Manager 14.2 Installation and Setup Guide
Chapter 2 Installation of the Manager > 2.2 Prerequisites for Solaris/Linux Platform > 2.2.2 Software requirements
PreviousNext

2.2.2 Software requirements

2.2.2.1 Basic software

Manager of AdvancedCopy Manager can only be installed in one of the following environments. Any other version of Solaris is not supported.

Solaris

Linux

Note

Manager of AdvancedCopy Manager is not supported in an environment where SELinux (Security-Enhanced Linux) is enabled.
Disable SELinux at servers that operate Manager of AdvancedCopy Manager.

2.2.2.2 Exclusion Software

AdvancedCopy Manager cannot coexist with the following software.

Solaris

If any of the above-mentioned software is installed, it must be uninstalled first.

Refer to "2.2.4.1 Items to check before Installation" for further detail.

Linux

It cannot coexist with the following software.

If any of the abovementioned software is installed, it must be uninstalled first.

2.2.2.3 Symfoware confirmation

Symfoware components are internally bundled with the Manager of AdvancedCopy Manager.

No problems arise if Symfoware is not installed in the install destination system.

If Symfoware is installed, the Symfoware status must be confirmed after installation. Check that the installed Symfoware server is the following level:

Solaris

If it was installed previously at another level it needs to be uninstalled and the appropriate level installed.

Note that the software versions and levels differ in accordance with the system environment where Symfoware is installed. Refer to the related software manuals for details.

Note

Symfoware cannot operate in an environment where standard security operations are selected during installation.

Linux

If it was installed previously at another level it needs to be uninstalled and the appropriate level installed.

2.2.2.4 Estimation of Database area

The following database areas are required in order for the Manager of AdvancedCopy Manager to operate:

Point

When configuring a Tape Server on the Storage Management Server (Solaris version)

You must also estimate the dynamic resources used by the Tape Server. For details, see "7.3.2 Dynamic Disk Resources".

Repository

A database domain is needed in the directory of the following repositories.

The following Table 2.10 Capacity of required database areas provides information on the minimum space required for each database.

Table 2.10 Capacity of required database areas

Type

Necessary size on filesystem

Directory for Database file system

200 MB

Directory for RDB dictionary

50 MB

Directory for RDB log file

50 MB

Directory for repository data storage database space

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

Note

  • Note the following when you store the above mentioned directory in the new device.

    A management block is required for operation with the filesystem when the filesystem is created. The size of the filesystem must be less than the size of the defined device.
    The capacity of the management block is specified using the relevant option to when the filesystem it is created.

  • Confirm the capacity of the filesystem by the df command etc., and confirm using the table above whether there is enough free space to support the requirements as listed.

The formula for estimating space requirements for repository data storage is set out below.
Capacity (MB) = {[(number of servers x 6 + total number of devices x 11) / 40] x 17+ 512}/ 1024
Table 2.11 Storage Server OS type and meaning of "device"

Storage server type

Correspondence to the "device"

Windows

Partition

Solaris

Slice

HP-UX

LUN

Linux

Partition

AIX

LUN

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

The total number of mirror slices is the number of devices multiplied by the number of disks comprising the mirror group.

Note

  • Although the four directories can be created on the same device, for reliability and performance considerations, Fujitsu recommends preparing these directories on another partition.

  • 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 used, 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 the calculated capacity and the prepared partition free space are the same, then after the database is created, the directory usage rate (capacity) may be 100%. This is not a problem.

  • When the calculated capacity and the free space in the prepared partition are the same size, the directory usage rate (capacity), displayed by the df command or similar, may be 100%, but this is not a problem.

Point

If there is a possibility that the number of servers or number of partitions will be increased in future, specify a size that is greater than the estimated size.

If there is a possibility that the number of mirrors or number of devices will be increased in future and SynfinityDISK or PRIMECLUSTER Global Disk Services are used, also specify a size that is greater than the estimated size.

PreviousNext
Copyright FUJITSU LIMITED 2010