Click on a link below to go to a specific section of the software installation:
Overview |
|
The remote install feature allows you
to install or upgrade the Base software, supported agents, and
MediaAgent in one procedure to multiple Unix-based or Mac OS X-based
hosts from a single Unix-based (or Mac OS X-based) host in one
iteration. The single host from which the install originates can be any
of the Unix (or Mac OS X) operating systems supported (see
System Requirements.) Once you provide all of the required
information, the remote install can run unattended. Remote installs are supported for the following agents:
Remote installs on a cluster are supported for any of these agents that are supported on a cluster. This feature also allows you to create and use the following in lieu of entering the required information at the install prompts:
If you want to use a file that includes host names with or without passwords, be sure to create this file before you start the install. If you want this file to include just host names, be sure to enter these names in a single column within the file. For example:
Using a file that just contains host names requires that there be a common root password for all of the hosts. You will be prompted for this password during the install. If you want the file to include both the host names and the password for each host, be sure to enter these items in two separate columns within the file. For example:
In either case, comments and empty lines are not allowed. Do not use the configuration file for silent installs to run a remote install. The remote install will not work if you use this configuration file. |
|
Install Requirements |
|
The agent is installed on the computer
from which the iDataAgent
secures data. (This computer is referred to as the Client
computer in this install procedure.) The Unix MediaAgent is installed on
a computer to manage data transfer and storage. Verify that the computers in which you wish to install the software satisfies the minimum requirements specified in one of the following:
Review the following Install Requirements before installing the software: General
Firewall
Cluster
All Agents
MediaAgent
AIX
FreeBSDA FreeBSD install requires that the libiconv library be present. To this end, complete the following steps:
Using remote installs requires root access to the system(s) being installed. However, attempting a remote install to FreeBSD produces a "login incorrect" error when you enter the root password unless you delete from the client FreeBSD computer the root user from the ftp-disallow lists in /etc/ftpusers. Also, see Post-install Considerations once you complete the remote install. HP-UX
Macintosh
Red Hat Linux
Solaris
Tru64
Ubuntu Linux
|
|
Install Checklist |
|
Collect the following information before installing the software. (Use the space provided at the right to record the information. Retain this information in your Disaster Recovery binder.) | |
1. |
Network host name:____________________________________
Client name:____________________________________ For example, green.domainname.com and green. See Step 5 for more information. |
2. |
Install directory location:________________________________________________________________
The default is /opt, but you may designate any location you want. See Interactive Setup for more information. |
3. |
Log files directory location:________________________________________________________________
The default is /var/log, but you may designate any location you want. See Interactive Setup for more information. |
4. |
CommServe Name and the CommServe Host Name:______________________________________
For example, orange and orange.domainname.com. See Interactive Setup for more information. |
5. |
Job result directory location:________________________________________________________________
The default is /opt, but you may designate any location you want. See Interactive Setup for more information. |
6. |
Group name__________________________________________________________
See Interactive Setup for more information. |
7. |
If the CommServe Server and the client computer communicate across a firewall:
Firewall ports: ______________________________________________________________________ Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the other side of the firewall:______________ Keep Alive Interval minutes:____________________________________________________________ Hostname for outgoing tunnel connections:_________________________________________________ Tunnel Initialization Interval seconds:_____________________________________________________ See Firewall Configuration for more information. |
8. |
Storage Policy used by the default subclient:________________________________________________
See Storage Policy Selection for more information. |
9. |
Index Cache directory
location:_____________________________________________________________ The default is /opt, but you may designate any location you want. See Administer Client-Related Items and Save the Settings for more information. |
10. |
ACSLS server host
name:_____________________________________________________________
See Administer Client-Related Items and Save the Settings for more information. |
SAP for Oracle Specific Information | |
11. |
SAPEXE directory:_____________________________________________________________________ See Administer Client-Related Items and Save the Settings for more information. |
Before You Begin |
|
|
Install Procedure |
||
Getting Started |
||
1. |
Place the software
installation disc for the Unix platform into the disc drive. You can also install the product using a disc drive mounted on another computer on the network.
NOTES
|
|
2. |
The product banner and other information is displayed.
Press Enter to continue. |
|
3. | Read the license agreement. Type y and press Enter to continue. | |
4. | The system prompts you either to import a
cvpkgpush express configuration file (if
you have previously created one) or to start an interactive setup to
perform the install. You are informed that the interactive setup option
will allow you to create a cvpkgpush
file for future installs.
|
If you already have a
cvpkgpush express configuration file for the installation that you would
like to perform, we can import it now. This will allow you to skip all
configuration questions and save time. If you do not have such a file, enter 2 below. We will collect all the required information from you and will offer you a chance to create this file later. 1) Import a cvpkgpush express configuration file 2) Proceed with interactive setup Your selection: [1] |
5. | Type the path of the cvpkgpush express configuration file and press Enter. | Please enter the name
of the cvpkgpush express configuration file below: Config file name: /tmp/expconfig |
6. | If you had encrypted any passwords in the express
configuration file, type the secret phrase that you had created to
decrypt the passwords and press Enter. If you did not encrypt any passwords in the express configuration file, you will not see this prompt. Go to Setup Complete. |
Some passwords in the
express configuration file are encrypted. Please provide a secret phrase to decrypt them. Phrase: Again: Successfully read configuration for 1 host(s). Press <ENTER> to continue ... |
Interactive Setup |
||
7. | Select the desired protocol for remote operations.
|
We begin by choosing
a method for remote file copy and remote command execution. Currently
Calypso supports two protocols: rexec and ssh. The advantage of the
"rexec" protocol is that you can find it pre-configured on many
platforms such as HP-UX, Solaris, AIX, etc. The advantage of the "ssh"
is that it's much more secure, and we are seeing more and more Linux and
Apple installations with "ssh" support being the only one available out
of the box. If you decide to follow the "rexec" path, you'll need to enter root password for every remote host. For "ssh" method, depending on how ssh access is configured, you'll need to enter either the remote root password or the passphrase to unlock the local private RSA/DSA keyring 1) Use "rexec" method (remote root password required) 2) Use "ssh" method (remote root password or keyring passphrase needed) 3) Exit Transport: [1] |
8. | Accept or type 2 to install the software and then press Enter. | Please specify
whether you want to upgrade existing installations of Bull
Calypso FileSystem iDataAgent and/or MediaAgents, or you would like to install Calypso on a new computer. 1) Upgrade Calypso on one or more computers 2) Install Calypso on one or more computers Upgrade or Install: [2] |
9. | Establish target hosts for the install if necessary.
NOTES
|
Let’s start from
establishing a list of target hosts on which you would like to install
Calypso File System iDataAgent, Oracle SAP Agent, SAPMAXDB, or
MediaAgent. Which list would you like to specify now? 1) The list of FS iDataAgents 2) The list of MediaAgents 3) The list of Oracle SAP Agent 4) The list of SAPMAXDB Agent 5) I'm done with the host lists. Let's carry on! Your selection: [1] |
10. | In addition to the options presented, if all of the
hosts have the same root password, another option is to include just the
host names in the file. In such a case, the system will eventually
prompt you for the hosts’ common root password.
|
Let's compose the
list of hosts where Calypso File System iDataAgent (MediaAgent) should
be installed. We are going to need the list of target hosts and passwords for root accounts on those hosts. If the number of hosts is not too large, it’s easier to enter this information directly in this terminal. Otherwise you can prepare a text file with the list that we will read in the next step. If you're using ssh transport with RSA/DSA authentication, you'll need to supply a passphrase to unlock the private ssh keyring. 1) Enter host names in this
terminal Selection [1] |
11. | Type all of the host names in a single line with a space between each name and press Enter. | Please provide the
names of the target hosts on which you would like to install Calypso.
Enter the names in one line, use space character as a separator. Hit
<ENTER> at the end. Note that the host names here should be as complete
as possible (including domain suffix, if any). If you want to install the target host as a virtual node in a cluster, you can input the virtual host name after its physical hostname followed by a comma as in the form of physical_hostname,virtual_hostname. Note that no space is allowed before or after the comma. To return to the previous menu just hit <ENTER>. Host list: lunchbox |
12. | Enter the password for the root account on each remote host, press Enter, and go to Interactive Setup Step 9. | Please enter password
for root account on host lunchbox. Hit <ENTER> two times to return back to the previous menu. Password: Again: |
13. | If you opted to have the system read at least the host
names from a file, indicate how you want to provide the password(s) for
each host.
|
You have chosen to
import the list of Calypso File System iDataAgent (MediaAgent) hosts from
an ASCII file. Are you willing to provide root passwords as the second column in this file, or do all hosts have the same root password (in which case you’ll be able to enter it in the command line)? 1) Passwords from the second column
in the ASCII file Selection [1] |
14. | Enter the name of the file containing both the names of
the hosts targeted for the remote installs and the corresponding
password for each host, in the format shown in the example.
Type the file path, press Enter, and go to Interactive Setup Step 9. |
Please enter the name
of the file with the list of hosts and passwords. The file should
contain two columns as in the following example. Comments and empty
lines are not allowed. machine1.company.com password1 machine2.company.com password2 ... machineX.company.com passwordX File name: /tmp/list Successfully read 1 hosts. Press <ENTER> to continue ... |
15. | Enter the name of the file containing the names of the
hosts targeted for the remote installs, in the format shown in the
example.
Type the file path and press Enter. |
Please enter the name
of the file with the list of hosts below. The host names should be
arranged in a single column like shown below. Comments and empty lines
are not allowed. machine1.company.com machine2.company.com ... machineX.company.com File name: /tmp/list Successfully read 1 hosts. Press <ENTER> to continue ... |
16. | Type the common root password for all of the specified
hosts, press Enter, then repeat this sequence as indicated. However, if you realize that the root account password is not the same on all of the hosts, press Enter twice to provide the appropriate password selection method. If you do this, go back to Interactive Setup Step 12 and continue. Otherwise, go to Interactive Setup Step 9. |
Please enter password
for root accounts on the specified hosts. If root account password is
not the same on all of the hosts, hit <ENTER> two times, and use a
different host selection method. Password: Again: |
17. | The system prompts you to make the software
distribution available on each remote host by using one of two methods.
NOTES
|
We need to make
Calypso distribution available on each of the install hosts. The
recommended way to do it is to NFS-mount this DVD under the same
directory on every host. We can also copy the distribution to each of the target hosts: a completely automatic, but time consuming approach. Please specify what you would like us to do: 1) Access Calypso DVD using an
NFS-mounted partition (YOU need to mount it) What would you like us to do? [1] |
18. | Type the directory path of the distribution on each remote machine, press Enter, and go to Interactive Setup Step 21. | Please enter the
directory name where Calypso distribution can be found on each of the
target machines. We assume that you have either NFS-mounted the Calypso
DVD under this directory, or made a copy of it there. Distribution Directory Name: [ ] |
19. | Ensure that each remote host has enough disk space.
Type the directory path where the distribution is to be copied and press Enter. |
Please enter the
directory name where Calypso distribution is to be copied. This
directory does not have to exist: we will create it for you. Please make sure that each of the target hosts has enough disk space. Distribution Directory Name: /tmp/distr |
20. | If you would like the binary files removed after a
successful installation, accept the yes default; if not, type
no.
Press Enter. |
Do you want us to
remove the copied binaries after successful installation? Remove? [yes] |
21. | Press Enter. | We are now going to
ask you a set of questions related to the configuration of Calypso IDA
or MA on each of the target machines. Press <ENTER> to continue ... |
22. | Either accept or type the port numbers for the instance and then press Enter. |
Every instance of Calypso should use a
unique set of network ports to avoid interfering with other instances
running on the same machine. The port numbers selected must be from the
reserved port number range and have not been registered by another
application on this machine. If you are installing on a cluster, make
sure all nodes share the same cvd port number and the same EvMgrC port
number.
Please be careful while making your input. We have no means of checking it. Please enter the port numbers. Port Number for CVD : [8400] Port Number for EvMgrC: [8402] |
23. | Either accept the default installation directory or type the desired directory name and press Enter. | Please specify where
we should install Calypso on the remote machines.
There must be at least 80MB of free space available. All files will be
installed in a "calypso" subdirectory, so if you enter "/opt" here, the
files will actually be copied into "/opt/calypso". Calypso Installation Directory: [/opt]/calypso |
24. | Either accept the default log file directory or type the desired directory name and press Enter. |
Please specify where you want to keep
Calypso log files.
There must be at least 100MB of
free space available. All files will be created in a "calypso/Log_Files"
subdirectory, so if you enter "/var/log", we will write into
"/var/log/calypso/Log_Files". Calypso Log Directory: [/var/log]/calypso |
25. | Either accept the default Job Results file directory or type the desired directory name and press Enter. |
Please specify where you want to keep
Job Results files.
Please be careful while making your input. We have no means of checking it. Job Results Directory: [/opt]/calypso |
26. | Type the short or long name of the CommServe and press Enter. |
Please enter the Calypso CommServe
name.
It can be either short or long. The only requirement is that it has to be resolvable by the name services configured on this machine. CommServe Name: darth |
27. |
Indicate whether you would like to launch processes with inherent database
access rights.
Press Enter to
assign a new group, or |
Most of Calypso processes run with root
privileges, but some are launched by databases and inherit database access
rights. To make sure that registry and log files can be written to by both kinds
of processes we can either make such files world-writeable or we can grant write
access only to processes belonging to a particular group, e.g. a "calypso" or a "dba"
group.
We highly recommend now that you create a new user group on each of the remote machines and enter its name in the next setup screen. If you choose not to assign a dedicated group to Calypso processes, all temporary and configuration files will be created with -rw-rw-rw permissions. If you're planning to backup Oracle DB you should use "dba" group. Would you like to assign a specific group to Calypso? [yes] |
28. |
If you indicated Yes in the previous step, you will be prompted for
the group name that must be used to launch processes.
Enter the group name and then press Enter to continue. Press Enter again to continue. |
Please enter the name of the group which
will be assigned to all Calypso files and on behalf of which all Calypso processes
will run.
In most of the cases it's a good idea to create a dedicated "calypso" group. However, if you're planning to use Oracle iDataAgent or SAP Agent, you should enter Oracle's "dba" group here. Group name: dba REMINDER If you are planning to install Calypso
Informix, DB2, Sybase or Lotus Notes iDataAgent, please make sure to include
Informix, DB2, etc. users into group "dba". |
Firewall Configuration |
||
29. |
If this computer communicates with the CommServe, MediaAgent and/or other
clients across a
firewall, type Yes, and then press Enter to continue. Proceed to
the next Step. Press Enter, if you do not wish to configure the firewall services. Proceed to the next section. |
If some of other Calypso machines (including
the CommServe, IDA or MA) will be located on the other side of a firewall, and
installed computers will be expected to communicate with them, we need to setup
Calypso firewall services at this time. If you answer "yes" to the following question, you will further be asked to provide the list of open firewall ports, and the list of Calypso machines located behind the firewall. Would you like to configure Calypso firewall services? [no] |
30. |
Enter the port range(s), and then press Enter to continue.
NOTES
|
For Calypso to work
properly across a firewall, your system administrator should open ports
8400, 8401, 8402 and a range of 20 ports (e.g. 8600- 8620) for traffic
between all firewall-separated Calypso machines. The opening should be symmetrical and allow traffic for any connection with one end bound to an open port. For example, for Linux ipchains the following two commands will open port 8600 correctly for all Calypso TCP traffic between machines mach1 and mach2: ipchains -A input -b -p tcp -s
mach1 8600 -d mach2 -j ACCEPT Please specify the range of 20 ports that Calypso can use besides ports 8400, 8401 and 8402. Accepted input is one or more strings like 8600-8620 separated with spaces. Port range: 8600-8620 |
31. | Enter the host name(s) of the computers that will need to be contacted through a firewall, and then press Enter to continue. | Please specify which
hosts will be separated from the installed machines by a firewall. You
can either list all hosts/IP addresses separating them with a space
character, or provide a wildcard, such as 192.168.* or *.company.com. List of firewalled hosts: *.company.com |
32. |
If desired, modify the Keep Alive interval, and then press Enter to
continue, or Press Enter to accept the default. |
Many firewalls,
especially those that perform Network Address Translation, cut idle
connections after some timeout. Some of the Calypso Services need to be
continuously connected, so Calypso keeps such connections active by
sending periodic keepalive packets. Time between two consecutive
keep-alive packets is called keep-alive interval, and its default is 10
minutes.
Please consult the documentation of your firewall for the exact value of the timeout after which idle connections will be closed by it. Then subtract one minute from that value and enter it below: Keep-alive interval, minutes [10] |
33. |
To configure advanced
firewall settings, type Yes, and then press Enter. Proceed to
the next Step. If you do not want to configure advanced firewall settings, type No, and then press Enter. Proceed to the next section. |
The Generic part of the Calypso Firewall Config has been completed
successfully. There are some additional advanced settings that you may want to
review now. All of them can be customized later by editing the .properties file
under /etc/CommVaultRegistry/Galaxy/Instance003/Firewall. Would you like to review the advanced settings now? [no] |
34. |
To bind the local end of tunnel connections to a specified interface, type Yes, and then press Enter. Proceed to
the next Step. If you do not want to bind the local end of tunnel connections to a specified interface, type No, and then press Enter. Skip the next Step. |
Normally Calypso Firewall code doesn't bind
local end of TCP/IP sockets when establishing outgoing tunnel connections
relying on the OS to pick correct interface and arbitrary port automatically.
Usually this doesn't cause connectivity problems because we require that the
firewall must allow connections for as long as 1meither source or destination
socket end is bound to one of the ports in the open range.
Sometimes, however, on hosts with several NICs it's important to force the OS to bind the local socket end to a specific network interface. There is a Calypso setting called 1mnBIND_BEFORE_CONNECT_IFACEm, which enables this behavior. If present, Calypso will bind the local end of tunnel connections to the specified interface. Would you like to configure nBIND_BEFORE_CONNECT_IFACE? [no] |
35. |
Type a number corresponding to one of the listed network interfaces, to use for outgoing tunnel connections through
the firewall. Press Enter to continue. |
Please select network interface that should
be used for all outgoing tunnel connections:
1) <ip_address> Interface number: [1] |
36. |
If desired, modify the Tunnel Initialization interval by typing a number. Press Enter to continue. |
When tunnel to a destination machine cannot be
established because the machine is down or is not accepting connections, Calypso
will retry the connection after some time. Tunnels piercing one-way firewalls are
1mPERSISTENTm meaning that Calypso will keep on trying to initialize them until
success. These attempts can generate a lot of network traffic if a central machine
(e.g. CommServe) suddenly goes down.
Here you can adjust the interval (called 1mnTUNNEL_INIT_INTERVALm in registry) between tunnel init attempts. Tunnel Init Interval, seconds, [5] |
Kernel Parameters |
||
37. |
Enter the appropriate number of streams, and then press Enter to
continue, or Press Enter to accept the default number of streams and continue. NOTES
This prompt is relevant only when you install/upgrade on a Macintosh or Solaris computer as appropriate. |
Please enter the total
number of streams that you plan to run at the same time. We need to make
sure that you have enough semaphores and shared memory segments configured
in /etc/system on Solaris computers.
This parameter is important for Solaris computers only. If neither of the remote hosts runs Solaris, simply press <ENTER> here. To prevent install script from changing /etc/system, enter 0 here. Number of streams [10] 3 |
Storage Policy Selection |
||
38. | If possible and desired, type yes, press Enter to assign a new storage policy to all the subclients, and go to the next step. Otherwise, accept the no default, press Enter, and then go to either Administer Client-Related Items and Save the Settings for a MediaAgent install. | Storage Policies If you are reinstalling the IDA, there may be subclients available which are associated with valid storage policies in the CommServe database. If so, you can now assign a new storage policy to all the subclients. This input is not considered in case of a fresh IDA installation. Would you like to assign a new storage policy to all subclients? [no] |
39. |
Enter the name of the storage policy through which you want to back up
the Agent and then press Enter to continue.
NOTES
For a MediaAgent install, go to the next step. For a SAP for Oracle iDataAgent install, go to Administer Client - Related Items and Save the Settings Step 44. For any other agent install, go to Step 45. |
Storage Policies Please specify the name of the storage policy, which the configured data agents are supposed to use. You can find this name in the Java GUI on the CommServe. In case of reinstalling an IDA, this input is ignored if you have chosen not to assign the new SP in the previous screen. This SP will be considered only if we have a problem assigning the existing SPs. Please be careful while making your input. We have no means of checking it. Storage Policy Name: arca817 |
Administer Client-Related Items and Save the Settings |
||
40. | Accept or type the path for the index cache directory and press Enter. | Please specify where
on the MediaAgent you want to keep the cache of indices for completed backups. Please be careful while making your input. We have no means of checking it Cache Directory: [/test1/calypso/MediaAgent/IndexCache] |
41. | To remote-install the WA drivers to all Solaris MediaAgents, accept or type yes and press Enter. Otherwise, type no and press Enter. | If one of the target
MediaAgents is a Solaris box and you plan to use a tape library on it,
Bull WA driver will have to be installed there. Do you want to push-install the WA driver to all Solaris MAs? [yes] |
42. | To configure StorageTek ACSLS Enabled Libraries on the
MediaAgents, type yes, press Enter, and go to the next step.
Otherwise, accept or type no, press Enter, and skip the next
step. ACSLS is supported only on the Solaris MediaAgent. |
Would you like to configure
StorageTek ACSLS Enabled Libraries on the MediaAgents? Note that ACSLS is
currently supported on Solaris MediaAgents only, so this option will have
no effect on other platforms. Configure? [no] |
43. | Type the name of the ACSLS server host and press Enter. | Please enter the name
of the host running ACSLS server daemons. ACSLS server host name: |
44. | Type the path of the SAPEXE directory and then press Enter. |
Please specify the location of SAPEXE directory. SAPEXE: /usr/sap/CER.920/SYS/exe/run |
45. | Type the client name for each host and press Enter. | Please provide client
name for host lunchbox. Client name can be anything that would identify this client host on the CommServe. Usually it’s the host name without domain suffix. Client name: [lunchbox] |
46. | To save these settings, type yes, press Enter,
and go to the next step.
To start the install without saving the settings, type no, press Enter, and go to Setup Complete. |
We are done collecting
information from you. The next step will be to perform the actual installation
on the hosts that you have selected. At this point we recommend saving the settings to a cvpkgpush express config file, which will allow you to repeat this installation later at any time. Would you like to create express config file? [yes] |
47. | Type the path and name for the cvpkgpush express configuration file and press Enter. | Please enter the name
of the cvpkgpush express configuration file where you would like to save
the installation parameters.
Config File Name: /tmp/expconfig |
48. | To encrypt the passwords for the root accounts, type
yes, press Enter, and go to the next step.
Otherwise, type no, press Enter (the messages indicated at the end of the next step appear) and skip the next step. |
The express configuration
file will contain passwords for root accounts that you have provided before.
For your protection we can encrypt these passwords before storing them to
the file.
Would you like us to encrypt the passwords? [yes] |
49. | To encrypt the root account passwords, type the secret phrase twice and press Enter. | Please provide a secret
phrase that will be used to encrypt root account passwords before saving
them to the express config file. Phrase: Again: Messages similar to the following should appear: Creating /tmp/expconfig ... done. Successfully created /tmp/expconfig. |
50. | If you would like to customize the express configuration
file by using a text editor, quit the installation by pressing ^C
and then edit the file; once you complete the edits, restart
cvpkgpush.
Otherwise, press Enter to continue. |
If you’d like to, you
can further customize this file in a text editor. For example, you can assign
different Storage Policies or different CommServe names to individual clients.
You can tell cvpkgpush to use NFS only for a group of hosts, use a different
mount path on some of the client machines, etc.
If you decide to follow the path of customization, quit the installation now by hitting ’^C’, edit the file and restart cvpkgpush. Press <ENTER> to continue or ^C to abort ... |
Setup Complete |
||
51. | To start the unattended installs to the specified remote hosts, press Enter. The install program now starts copying the software to the computer. The progress of the operation is displayed. | We are now ready to install
Calypso on the specified hosts. The installation can proceed unattended from
this point. Press <ENTER> to continue ... |
52. | The installation is now complete. | Performing silent install
on the remote host ... ... Installation completed successfully on the following hosts: muse skicat Press <ENTER> to continue... |
53. |
Enter Yes to download and install the latest service packs and post packs from the software provider. NOTES
Press Enter to continue. |
Download and Install Latest Service Pack If you choose to download the latest service pack from the software provider website now, please make sure you have internet connectivity at this time. This process may take some time depending on the internet connectivity. Do you want to download the latest service pack now ? [no] Press <ENTER> to continue ... |
Post-Install Considerations |
||
All Agents
FreeBSD
MediaAgent
|