This chapter explains how to install Manager function.
Note
At installation, all the nodes must be installed in the same environment (i.e., the local drive name, port number, and install directory must be the same for both).
Do not install the Manager function on a shared disk.
Because the database environment is created with the cluster setup command, be sure to respond with "No" to any prompt about whether to create a database environment as an extension of installation process.
The port number for the communication service to be specified by installation is for communication service for local transactions. Set the port number for cluster transactions in the following location according to the operation method.
Perform the "Customization" procedure for the cluster system in "Chapter 4 Customization of Storage Management Server Transactions and Storage Server Transactions".
The installation flow is shown below. The node on which installation is performed first is called the primary node; the other node becomes the secondary node.
For a cascade topology, follow the procedure given for the secondary node on every other secondary node.
Install the Manager function of the Windows version AdvancedCopy Manager with the following procedure.
Note
Executing this process with the service listed below must be paid attention.
Terminal service (via a remote desktop connection)
If the Storage Management Server is running on Windows Server 2003, the Terminal Service must be used by making a console session connection to it. Refer to the following link for information on how to make console session connections:
http://support.microsoft.com/kb/947723
http://support.microsoft.com/kb/278845
Do not use service listed below, as it will not work properly.
Telnet server service
For a user belonging to the domain Administrators group to perform the installation tasks under Windows Server 2008 or Windows Server 2008 R2, the Windows service "Computer Browser service" must be started.
If the "Computer Browser service" has not been started, start this service in order to perform the installation tasks.
The following table shows the intended users for user creation, user authentication, and service execution for each server type being used.
Server type | ||
|---|---|---|
Domain controller | Machine belonging to a domain | WORKGROUP |
Domain user | Local user | Local user |
Log on to the primary node.
Log on to the primary node as the administrator. Ignore "(Secondary node)" in the following explanation.
Confirm and Install the ETERNUS SF License Manager.
For Windows Server 2003
Double-click on the [Add or Remove Programs] icon in the Control Panel. On the "Add or Remove Programs" window, check whether [ETERNUS SF License Manager] is displayed or not.
For Windows Server 2008 or Windows Server 2008 R2
Double-click on the [Programs and Features] icon in the Control Panel. On the "Programs and Features" window, check whether [ETERNUS SF License Manager] is displayed or not.
If the [ETERNUS SF License Manager] is not displayed, install the ETERNUS SF License Manager by referring the "Installation of License Manager" in the "ETERNUS SF AdvancedCopy Manager Installation and Setup Guide".
Insert the AdvancedCopy Manager CD-ROM (Manager Program) into the drive and an initial [ETERNUS SF] window will be displayed. Click on [Install Function for Storage Management Server].
At the following (InstallShield) window click the [Next] button.
Accept the use permission contract displayed on the [License Agreement] window by clicking on [Yes].
Confirm the displayed contents, and click the [Yes] button.
Click "Default" or "Custom" on the [Welcome] window, and then click [Next].
If [Default] is selected
The install information on the following windows need not be set (steps 6 to 8 are not required):
[Set install destination] window
[Startup/Account registration] window
[Register port number] window
An error check is performed automatically for the default install information in the omitted screens.
If an error is detected: A warning dialog is displayed and the display switches back to that window.
If no errors are detected: A warning dialog is displayed and the [Start copying files] window is displayed.
For details on default installation information and error check contents, refer to the "ETERNUS SF AdvancedCopy Manager Installation and Setup Guide", section "Installation of the Manager" > "Prerequisites for Windows Platform" > "Installation".
If [Custom] is selected
Installation information must be set in all the installation windows.
Enter the required information in the windows displayed in step 8 and subsequent steps.
Specify the system to be installed.
(Primary node)
If this product is to be installed in directories other than those displayed (default directories), click the [Browse] button to select the desired directories. After all the correct directories have been selected, click the [Next] button. Note: directories with spaces their names (e.g., Program Files) must not be specified. Do not install the Manager function on a shared disk.
(Secondary node)
Specify the same drive and directories as those specified for the primary node.
When the [Browse] button is clicked, the following window is displayed, allowing the selection of other than the defaulted directories.
Input the startup account on the [Startup/Authentication feature manager] window.
(Primary node)
Input the account name belonging to the Administrator's group with a password, and click the [Next] button. The account name and password must satisfy the following conditions:
An account name and password that can be specified in the operating system.
For details on the startup account, refer to the "ETERNUS SF AdvancedCopy Manager Installation and Setup Guide", section "Installation of the Manager" > "Prerequisites for Windows Platform" > "Startup account".
If the account name is not registered, the system adds this account with Administrative rights with the password set not to expire. In addition, the system sets the following user authority:
Log on as a service
Function as part of the operating system
Adding a quota
Replace the process level token
(Secondary node)
Specify the same account name and password as those specified for the primary node.
Input the number of the port to be allocated to the service on the [Registering a port number] window.
(Primary node)
Enter the port number to be allocated to each service within the following range:
5001 to 32767
The first displayed value is a recommended value in a non-cluster environment and is not always unique.
To perform cluster operation with Windows Server 2003, change all port numbers so that they are within the range as indicated above.
After the port number entry is completed, click the [Next] button. This window will be redisplayed with the accepted port number.
(Secondary node)
Specify the same values for all items as the values specified for the primary node.
If the AdvancedCopy Manager service name is defined with an ALIAS, the following window will be displayed and the port number specified on the previous screen is ignored. The installation proceeds anyway.
Configure the port number manually by editing the file C:\WINDOWS\system32\drivers\etc\Services.
Confirm the settings in the [Start Copying Files] window.
If no errors are detected, click the [Next] button. To correct or otherwise change any settings, click the [Back] button.
Copying starts.
The file transfer that is in progress can be viewed on the [Setup Status] window.
Confirm the environment settings.
When the following [Environment setup] window opens, click the [No] button.
Finish the installation.
Select the [restart the computer] option and click the [Finish] button to complete the installation.
(Primary node)
Next, start installation on the secondary node by continuing with step 13.
(Secondary node)
Installation of both nodes is now complete. To provide the cluster construction for a Storage Server transaction, see "Chapter 3 Preparations for Customizing Storage Management Server Transactions, Storage Server Transactions, and Tape Server Transactions".
Log on to the secondary node.
Log on to the secondary node as the administrator.
Go back to 2.
Starting with step 2, perform the same installation procedure for the secondary node that you did for the primary node. Ignore (Primary node) in the following explanation.
