Install the SAP for Oracle or SAP for MAXDB iDataAgent - Unix

Click on a link below to go to a specific section of the software installation:

Install Requirements
The SAP for Oracle or SAP for MAXDB iDataAgent is installed on the computer from which the iDataAgent secures data. (This computer is referred to as the Client computer in this install procedure.)

Note that on HP-UX, the SAP for Oracle or SAP for MAXDB iDataAgent can be used to secure data from both the Oracle and MAXDB databases. Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements - SAP for Oracle iDataAgent, System Requirements - SAP for MAXDB  iDataAgent, and System Requirements - Unix File System iDataAgent.

The following procedure describes the steps involved in installing the SAP for Oracle or SAP for MAXDB and Unix File System iDataAgents. If you choose to install multiple components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component. Note that when you install multiple components, the sequence of the install steps may vary.

Review the following Install Requirements before installing the software:

General

  • Agents should be installed only after the CommServe and at least one MediaAgent have been installed in the CommCell. Also, keep in mind that the CommServe and MediaAgent must be installed and running (but not necessarily on the same computer), before you can install the Agent.
  • This software should be installed in a CommCell with current versions of the CommServe and MediaAgent software.
  • Ensure there is an available license on the CommServe for the Agent.
  • Verify that you have the software installation disc that is appropriate to the destination computer’s operating system.

    Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider.

Firewall

  • If the CommServe® Server, MediaAgent and/or Clients communicate across two-way firewall(s):
    • Ensure port 8400 is allowed connections through the firewall.
    • In addition a range of bi-directional ports (consecutive or discrete) must also be allowed connections through the firewall.

     For information on configuring the range of ports, see Port Requirements for Two-way Firewall.

  • If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s):
    • Identify a range of outbound ports (consecutive or discrete) for use by the software.

     For information on configuring the range of ports, see Port Requirements for One-way Firewall.

  • If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before installing the necessary software on the MediaAgent/Client computer.

Red Hat Linux

  • Red Hat Linux will create an entry in the /etc/hosts file when it is first installed, in the following format:

    <ip_address> <host name> localhost

    For example, if the host name of your computer is bluesky, the entry will look something like this:

    192.168.1.111 bluesky localhost

    If you have not already done so, edit the /etc/hosts file. The edited entry should look like this:

    127.0.0.1 localhost

    Depending upon your environment, and using the above example again, you may also need an entry similar to this:

    192.168.1.111 bluesky

Agent Specific

  • For a database Agent, you may be required or be given the option to shut down the instances/databases for the agent before or during the following procedure. See Shut Down Instances for more information.

HP-UX

Install Checklist
Collect the following information before installing the software. Use the space provided to record the information, and 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 Base Software Installation for more information.
3. Log files directory location:________________________________________________________________

The default is /var/log, but you may designate any location you want.

See Base Software Installation for more information.
4. Network TCP port number for the Communications Service (CVD):_____________________________

Network TCP port number for the Client Event Manager Service (EvMgrC):___________________________

See Base Software Installation for more information.
5. 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.
6. CommServe Name and the CommServe Host Name:______________________________________

For example, orange and orange.domainname.com.

See Base Software Installation (continued) for more information.
7. Job result directory location:________________________________________________________________

The default is /opt, but you may designate any location you want.

See Base Software Installation (continued) for more information.
8. Storage Policy used by the default subclient:________________________________________________

See Storage Policy Selection for more information.

9. Client Group to which this Client will be associated:_____________________________________________

See Client Group Selection for more information.
10. SAPEXE directory:_____________________________________________________________________

See Configure SAP for Oracle-Specific Information for more information.

Before You Begin
  • SAP application has been installed on the client.
  • Log on to the client as root.
  • The install package requires super-user permissions to execute.

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.

  • On Solaris, double-click the cvpkgadd program from the File Manager window.
  • On other Unix platforms, open the Terminal window, navigate to the software installation disc and then enter cvpkgadd. 
  
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. This prompt is displayed only when you are installing on AIX, HP-UX, Linux, or Solaris computers.

Press Enter to continue

NOTES

  • When you install on non-clustered computer, you must select the number associated with the option Install on a physical machine.
 Certain Calypso packages can be associated with a virtual IP, or in other words, installed on a "virtual machine" belonging to some cluster. At any given time the virtual machine's services and IP address are active on only one of the cluster's servers. The virtual machine can "fail-over" from one server to another, which includes stopping services and deactivating IP address on the first server and activating the IP address/services on the other server.

You now have a choice of performing a regular Calypso install on the physical host or installing Calypso on a virtual machine for operation within a cluster.

Most users should select "Install on a physical machine" here.

1) Install on a physical machine

2) Install on a virtual machine

3) Exit

Your choice: [1]
5. If you have only one network interface, press Enter to accept the default network interface name and continue.

If you have multiple network interfaces, enter the number corresponding to the network interface that you wish to use as default, and then press Enter to continue.

NOTES

  • The interface name and IP addresses depend on the computer in which the software is installed and may be different from the example shown.
 Network interface with the following IPs have been found available on your system. One of these interfaces should be associated with the physical machine being installed. It will also be used by the CommServe to initiate connections to the physical machine. Note that you will be able to additionally customize Datapipe Interface Pairs used for the backup data traffic later in the Calypso Java GUI.

Please select the correct network interface below.
1) client (201.42.33.598)
2) hk97::489:9glg:hk8d:9490
3) client.company.com (hr90:8842:2:78:013:8ghh:hg8k:9x54)

Interface number: [1]
  Verify the default network interface name.

Press Enter to accept the default network interface name and continue, or
Type the default network interface name, and then press Enter to continue.

NOTES

  • This prompt will be displayed only when you have multiple network interfaces for the computer.
 Please verify the physical machine interface name below. Make it as complete (with fully qualified domain name) as possible:

Physical Machine Host Name: [angel.company.com]
6. Specify the client name for the computer.

Press Enter to accept the default name and continue, or
Enter a new client name for the computer and then press Enter to continue.

 Please specify the client name for this machine. It does not have to be the network host name: you can enter any word here without spaces. The only requirement is that it must be unique on the CommServe.

Client name: [angel]

Select Components for Installation
7. Enter the number corresponding to the module you are installing:
  • Choose the CVGxOrSAP module for SAP for Oracle.
  • Choose the CVGxSAPMAXDB module for SAP for MAXDB.

NOTES

  • Your screen may look different from the example shown.
  • Components that either have already been installed, or which cannot be installed, will not be shown.
  • In addition, the list of modules that appear depends on the specific Unix File System in which the package is installed. (e.g., CVGxWA will appear only when the installation package is run on a Solaris computer.)

Press Enter to continue.

 Install Calypso on physical machine client.company.com

Select the Calypso module that you would like to install

1) Media Agent             <= CVGxMA
2) FileSystem iDataAgent   <= CVGxIDA
3) Exit this menu

Module number: [1]

Base Software Installation
8. Select from the following:
  • If this is the first package to be installed on the computer, press Enter to continue.
  • If this is NOT the first package to be installed on the computer, this screen will not be displayed. Skip to Storage Policy Selection.
 Here is a list and status of the dependent modules:

     1) Calypso Base0 Module                     NOT installed

    2) Calypso Base Module                      NOT installed

 If there are any modules listed as NOT installed/upgraded, they will be installed/upgraded first.

 Press <ENTER> to proceed ...
9. Specify the location where you want to install the software.

NOTES

  • The amount of free space required depends on the components selected for install, and may look different from the example shown.

Press Enter to accept the default path and continue, or
Enter a path and then press Enter to continue.

Press Enter again to confirm the path.

 Please specify where you want us to install Calypso binaries.

It must be a local directory and there should be at least 209MB of free space available. All files will be installed in a "calypso" subdirectory, so if you enter "/opt", the files will actually be placed into "/opt/calypso".

Installation Directory: [/opt]

..

Calypso will be installed in /opt/calypso.
Press ENTER to continue ...

10. Specify the location for the log files.

NOTES

  • All the modules installed on the computer will store the log files in this directory.
  • The amount of free space required depends on the components selected for install, and may look different from the example shown.

Press Enter to accept the default path and continue, or
Enter a path and then press Enter to continue.

Press Enter again to confirm the path.

 Please specify where you want to keep Calypso log files.

It must be a local directory and there should be at least 100MB of free space available. All log files will be created in a "calypso/Log_Files" subdirectory, so if you enter "/var/log", the logs will actually be placed into "/var/log/calypso/Log_Files".

Log Directory: [/var/log]

..

Calypso log files will be created in /var/log/calypso/Log_Files.
Press ENTER to continue ...

11. Indicate whether you would like to launch processes with inherent database access rights.

Press Enter to assign a new group, or
Type No and then press Enter to continue.

 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 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]
12. 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.

For installs on a Solaris computer, proceed to the next step. Otherwise, skip to Storage Policy Selection.

 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".
Press <ENTER> to continue ...

13. Type a network TCP port number for the Communications Service (CVD) and press Enter.

Type a network TCP port number for the Client Event Manager Service (EvMgrC) and press Enter.

NOTES

 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.

Please enter the port numbers.

Port Number for CVD : [8400]

Port Number for EvMgrC: [8402]

Firewall Configuration
14. 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.

 Various Calypso components need to communicate with each other: iDataAgents and MediaAgents establish connections to CommServe and talk to each other as well. If any of the involved parties are situated on the opposite sides of a firewall, Calypso should be made aware of it so that it could bind its pipeline sockets to open ports and could establish tunnels for control traffic.

You must configure Calypso firewall services if there are other Calypso machines, which are expected to communicate with this one.

Do you want to configure Calypso firewall services? [no]
15. Enter the port range(s), and then press Enter to continue.

NOTES

 Calypso needs to know which TCP ports of this machine are available for connections initiated by machines on the other side of the firewall.

If this machine is not reachable from the other side of the firewall at all (because the FW is one-way and allows only outgoing connections), enter any unused port number here (e.g. 8600).
Otherwise please consult your FW configuration for the list of open incoming ports and enter all of them here (with the exception of port 8400).

Currently there are no ports configured. Please enter a single port number or a port range (like 8600-8620) to be added to the FW configuration:

Port range: [8600-8620]
16. Enter the number corresponding to the option you wish to perform.

NOTES

  • If you choose option 1, refer the previous step.
  • If you choose option 3, proceed to the next step.
 What would you like to do:

  1) Add another open port or a range of ports

  2) Delete an existing port or a range of ports

  3) Continue with the firewalled host setup

Your choice: [3]
17. Enter the host name(s) of the computers that will need to be contacted through a firewall, and then press Enter to continue. We need to know which Calypso hosts are located on the other side of the firewall, and whether the firewall will allow direct or reverse connections to/from those hosts.

You can specify hosts by either entering their names, IP addresses or name/IP wildcards. The wildcards are available only if the firewall is symmetrical, i.e. allows to open connections to certain ports both ways.

Currently there are no firewall hosts configured.

Please enter the name or IP address of a host on the other side of the firewall. If the firewall is symmetrical, you are allowed to use wildcards, i.e. things like 192.168.* or *.firewall.company.com:

Firewalled Host: lavender.company.com
18. Choose the option associated with type of firewall configuration based on the firewall setup in your environment.

NOTES

  • Choose Two-way (symmetrical) firewall if you can open certain ports as bi-directional ports.
  • Choose One-way firewall; <port> is reachable from here if this computer communicates with MediaAgent/Client on the other side of the firewall.
  • Choose One-way firewall; this machine is reachable from <port> when the CommServe and any Clients/MediaAgents) communicates with this computer.
 Please specify the type of the firewall separating this machine from 172.19.61.89.

  1) Two-way (symmetrical) firewall

  2) One-way firewall, 172.19.61.89 is reachable from here

  3) One-way firewall, this machine is reachable from 172.19.61.89

Your choice: [1]

19. Enter the number corresponding to the option you wish to perform.

NOTES

  • If you choose option 1, refer the previous two steps.
  • If you choose option 3, proceed to the next step.
 What would you like to do:

 1) Configure another host

 2) Delete an existing host

 3) Continue with the firewall keep-alive setup

Your choice: [3] 1
20. If desired, modify the Keep Alive interval, and then press Enter to continue, or
Press Enter to accept the default. 		Please specify Keep Alive interval for Calypso firewall services.

Many firewalls disconnect idle Network connections after some period of time. Some of the Calypso Services need continuous connections. Calypso keeps such connections active by sending periodic "keep-alive" packets.
Consult your firewall documentation, or contact your Network Administrator, for the exact value after which idle connections will be closed (snip time). Then enter a value, which is at least one minute less than the snip time.

Keep-alive interval, minutes [5]
21. 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]
22. 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]
23. 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]
24. 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]

Base Software Installation (continued)
25. Type the name of the CommServe computer and press Enter to continue.

NOTES

  • Ensure that the CommServe is accessible before typing the name; otherwise the installation will fail.
  • If you enter a short name which resolves to the same IP address as the fully qualified CommServe name, you will be asked if you would prefer to use the fully qualified name.
 Please enter the hostname of the Calypso CommServe. It can be either short or long; the only requirement is that it must be resolvable by the name services configured on this machine.

CommServe Name:
26. Enter the username and password information for an external domain user account or a CommCell user account. This authorizes the installation of an agent on the CommCell.

NOTES

  • This is only displayed when the Authentication for Agent feature is enabled in the CommCell Properties. Users must belong to a User Group with Agent Management capabilities to enable this feature. For more information, see Authentication for Agent Installs.

Click Enter to continue.

 Enter your CommCell user name and password:

User Name :

Password :

Press <ENTER> to continue ...

27. Specify the location of the job results directory.

NOTES

  • All the agent modules installed on the computer uses the job results directory to store the backup and restore job results.
  • The amount of free space required depends on the components selected for install, and may look different from the example shown.

Press Enter to accept the default path and continue, or
Enter a path and then press Enter to continue.

 Please specify the name for the JobResults directory.

It must be a local directory and there should be at least 20MB of free space available. It will be used to store intermediate data that should be passed from one backup phase to another.

JobResults Directory: [/test1]

Kernel Parameters
28. 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.

Number of streams: [10]
29. Indicate whether you would like modifications to be made to the /etc/system configuration file.

Type Yes, and then press Enter to automatically update the file and continue, or
Press Enter to accept the default No and continue (if you do not want to automatically update the file).

This prompt is displayed only when you install/upgrade on a Solaris or Macintosh computer.

 We now need to modify the /etc/system configuration file on this computer. It is done to make sure that there will be enough shared memory and semaphores available for Calypso programs.

Please review the changes below and answer "yes" if you want us to apply them to the /etc/system file. Otherwise, the installation will proceed, the changes will be saved to some other file, and you will have to apply them manually.

set shmsys:shminfo_shmmni=8570 (was 7930)
set shmsys:shminfo_shmseg=8420 (was 7780)
set semsys:seminfo_semmns=10320 (was 9680)
set semsys:seminfo_semmni=8570 (was 7930)
set semsys:seminfo_semmsl=8570(was 7930)

Do you want us to apply these changes now? [no]

Changes saved into /etc/system.gal.1744

Press <ENTER> to continue.
30. If you indicated No in the previous step, the file to which the changes have been saved is displayed.
Make sure that these values are established later to ensure that all the requirements for this setup is satisfied.

NOTES

  • The settings that are displayed are the maximum or minimum required settings. Value ’640’, which is provided for various shared memory segment or semaphore requirements, is a maximum value based on 10 streams.

Press Enter to continue.

This prompt is displayed only when you install/upgrade on a Solaris computer, in cases where the install detects that the computer does not have the maximum or minimum required shared memory settings.

 Although a ’no’ answer can be selected to this question during install, the user should make sure the min requirements (below) for shared memory are met, otherwise the backups may fail (the message in logs is ’could not start the pipeline’).

set shmsys:shminfo_shmmax=4199304
set shmsys:shminfo_shmmin=1
set semsys:shminfo_shmmni=640
set semsys:shminfo_shmseg=640
set semsys:seminfo_semmns=640
set semsys:seminfo_semmni=640
set semsys:seminfo_semmsl=640
set maxusers=256

Storage Policy Selection
31. Enter the number corresponding to the storage policy through which you want to back up the File System iDataAgent and then press Enter to continue.

NOTES

  • A storage policy directs backup data to a media library. Each library has a default storage policy.
  • When you install an Agent, the install program creates a default subclient for most Agents.
  • If desired, you can change your storage policy selection at any time after you have installed the client software.
  • If this screen appears more than once, it is because you have selected multiple agents for installation and are configuring storage policy association for each of the installed agents.
 Please select one storage policy for this IDA from the list below:

1) SP_StandAloneLibrary2_2
2) SP_Library3_3
3) SP_MagLibrary4_4
4) fornax_fornax_HWCmp
5) ranger_ranger_HWCmp
6) fornax_fornax_ClntCmp
7) fornax_fornax_MACmp
8) fornax_fornax_NoCmp

Storage Policy: [3]

Enable Global Filters
32. Type the appropriate number for configuring Global Filters for the default subclient and press Enter to continue.

NOTES

  • Select Use Cell level Policy to inherit the global filter policy configuration set for the CommCell, i.e., if the Use Global Filters on All Subclients option is selected in the Global Filters dialog box (from the CommCell Console’s Control Panel), then this policy will be applied to the default subclient as well. If is not selected, then the global filters will not be applied to the default subclient.
  • Select Always use Global filters to always apply the global filters policy to the default subclient regardless of the policy set for the CommCell.
  • Select Do not use Global filters to disregard applying the global filters to the default subclient regardless of the policy set for the CommCell.
 Commcell Level Global Filters are set through Calypso GUI's Control Panel in order to filter out certain directories or files from backup Commcell-widely. If you turn on the Global filters, they will be effective to the default subclient. There are three options you can choose to set the filters.

1) Use Cell level policy
2) Always use Global filters
3) Do not use Global filters

Please select how to set the Global Filters for the default subclient? [1]

Client Group Selection
33. Type the number of a Client Group and press Enter.

A confirmation screen will mark your choice with an "X". Type the number for Done with the Selection, and press Enter to continue.

NOTES

  • This screen will be displayed only if Client Groups are configured for the CommCell. For more information, see Client Computer Groups.
 Client Group(s) is currently configured on CommServe cs.company.com. Please choose the group(s) that you want to add this client client.company.com to. The selected group(s) will be marked (X) and can be deselected if you enter the same number again. After you are finished with the selection, select "Done with the Selection".

1) Unix
2) DR
3) DKS
4) Done with the selection

Please enter a number to select/deselect: [1]  
34. The install program now starts copying the software to the computer. The progress of the operation is displayed.

Press Enter to continue.

 .....
.....
.....
.....

Successfully copied xx files

.....
.....

Successfully installed <package_name>.

Press ENTER to continue ...

Administer Database Instances
35. If you have multiple instances of the database, ensure that the items listed are satisfied. Press Enter. IMPORTANT

If you are planning to use Calypso <package> with several instances of the database, each running on behalf of different UNIX users, you must make sure that:

1) All database users have been added to each of the database groups involved. For example, if there is a "db2inst1" user from group "dba1" and "db2inst2" user from group "dba2", then both "db2inst1" and "db2inst2" should be included into "dba1" and "dba2" groups. On most UNIXes this can be accomplished by editing the /etc/group file.

2) The .profile of each database user must contains a "umask 002" command at the end, which will guarantee that all files created by one database user can be open for writing by other database users.

3) All database users should be added to the "dba" group that you have chosen for Calypso at the time of CVGxBase install.

If all of the above requirements are not fulfilled, Calypso will run into various "Permission denied" errors, and backups will not work.

Press <ENTER> to continue ...
36. Press Enter to continue. .....
.....

Successfully installed <package_name>.

Press ENTER to continue ...

Setup Complete
37. Press Enter to continue.

NOTES

  • Schedules help ensure that the data protection operations for the Agent are automatically performed on a regular basis without user intervention. For more information, see Scheduling.

If you are installing the SAP for Oracle iDataAgent, go to Configure SAP for Oracle-Specific Information. Otherwise, go to the next step.

 +---------------------+

IMPORTANT:

In addition to installing Calypso on this computer, you will also need to create a Job Schedule for each iDataAgent that has been installed on this client computer.

Job Schedules are required to allow the Calypso iDataAgents to perform automated backup and restore operations.

Job Schedule creation can be accomplished through the Calypso CommCell Console administration interface.

+---------------------+

Successfully installed CVGxIDA.
Press ENTER to continue ...
38. This menu may be displayed only when you are installing on HP-UX, Linux, or Solaris computers. If this is the last package that you wish to install/upgrade, enter the number corresponding to the Return option and then press Enter to continue.

NOTES

  • Only modules that are not installed/upgraded appear in the list.
  • Your screen may appear different from the example shown.
  • If you are installing on AIX, FreeBSD, IRIX or Tru64 computers, if this module was the last possible module to install, you are automatically exited from the program. Otherwise, type the number for the Exit option and then press Enter. The installation is completed.
 Select the Calypso module that you would like to install.

1) Proxy FileSystem iDataAgent <= CVGxProxyIDA
2) Oracle iDataAgent           <= CVGxOrIDA
3) DB2 iDataAgent              <= CVGxDB2
4) Return

Module number: [1]

39. Enter Yes to download and install the latest service packs and post packs from the software provider.

NOTES

  • Internet connectivity is required to download updates.
  • This step is applicable for multi instancing.

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 ...
40. This prompt is displayed only when you are installing on HP-UX, Linux, or Solaris computers. Enter the number corresponding to the Exit option and then press Enter to continue.

The installation is now complete.

 Certain Calypso packages can be associated with a virtual IP, or in other words, installed on a "virtual machine" belonging to some cluster. At any given time the virtual machine's services and IP address are active on only one of the cluster's servers. The virtual machine can "fail-over" from one server to another, which includes stopping services and deactivating IP address on the first server and activating the IP address/services on the other server.

Currently you have Calypso installed on physical node stone.company.com.

Now you have a choice of either adding another package to the existing installation or configure Calypso on a virtual machine for use in a cluster.

1) Add another package to stone.company.com
2) Install Calypso on a virtual machine
3) Exit

Your choice: [1]

Configure SAP for Oracle-Specific Information
41. Type the path of the SAPEXE directory and then press Enter.

Go to Administer Database Instances.

 Please specify the location of SAPEXE directory.

SAPEXE: /usr/sap/CER.920/SYS/exe/run

Post-Install Considerations

General

  • Install post-release updates or Service Packs that may have been released after the release of the software. If you are installing a Service Pack, verify and ensure that it is the same version as the one installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and easy installation of updates in the CommCell component.
  • After installing the Agent, you may want to configure the Agent before running a data protection operation. The following list includes some of the most common features that can be configured:
    • Configure your subclients - see Subclients for more information.
    • Schedule your data protection operations - see Scheduling for more information.
    • Configure Alerts - See Alerts and Monitoring for more information.
    • Schedule Reports - See Reports for more information.

The software provides many more features that you will find useful. See the Index for a complete list of supported features.

Agent Specific

  • After the installation you must configure the SAP for Oracle or SAP for MAXDB iDataAgent in order to perform the backup and restore operations. The basic configuration details are described in Create an Instance.

  • For the AIX, FreeBSD, HP-UX, IRIX, Linux, Solaris, and Tru64 File System iDataAgents, a registry key is available to allow you to define where core files will be generated in the unlikely event of an application process crash. Generating core files in filesystems other than root will help maintain system integrity. Refer to dCOREDIR for information about implementing this registry key.

  • For SAP for Oracle on Unix, if your backups will be using the RMAN utility, be sure to do the following before you run any backups:

    1. Ensure that $ORACLE_HOME/lib and $ORACLE_HOME/lib64 are in the LD_LIBRARY_PATH environment variable.
    2. Modify the SAP database init file (init<SID>.sap) under $ORACLE_HOME/dbs by adding the following:

      RMAN_PARMS="SBT_LIBRARY=/<install path>/<Base directory version>/libobk.<xx>,ENV=(CvClientName=<client name>,CvInstanceName=<instance name>"

      For example:

      RMAN_PARMS="SBT_LIBRARY=/opt/hds/Base64/libobk.so,ENV=(CvClientName=aha,CvInstanceName=Instance001)"

  • For SAP for MAXDB on Unix, to associate the SAP MAXDB database with the product software, be sure to run each of the following commands:

    dbm_configset -raw BSI_ENV /<software install path>/SapMaxDbAgent/backint.conf

    dbm_configset -raw set_variable_0 LD_LIBRARY_PATH=/<software install path>/Base

    dbm_configset -raw set_variable_1 SHLIB_PATH=/<software install path>/Base

    Thereafter, from the root directory, include the following lines in .profile:

    • For AIX and HP-UX:

      SHLIB_PATH=/<software install path>/Base:/<software install path>/Base64

      export SHLIB_PATH

    • For Linux and Solaris:

      LD_LIBRARY_PATH=/<software install path>/Base:/<software install path>/Base64

      export LD_LIBRARY_PATH

  • If you are running multiple stream backups and restores for the SAP for MAXDB iDataAgent, you should define the path for each pipe that is used for the storage media.

    For Unix, you can specify any file path as a pipe, and you can create the pipes in the operating system.  For example:

    medium_put BackData2\mem1 /space/sdb/data/cert1/files/pipe_mem1 PIPE DATA  0 0 NO NO '' BACK

    medium_put BackData2\mem2 /space/sdb/data/cert1/files/pipe_mem2 PIPE DATA 0 0 NO NO '' BACK

    medium_put BackPages2\mem1 /space/sdb/data/cert1/files/pipe_mem3 PIPE PAGES 0 0 NO NO '' BACK

    medium_put BackPages2\mem2 /space/sdb/data/cert1/files/pipe_mem4 PIPE PAGES 0 0 NO NO '' BACK

    medium_put BackLog\mem1 /space/sdb/data/cert1/files/pipe_mem5 PIPE LOG 0 0 NO NO '' BACK

    medium_put CompleteF\mem1 /space/sdb/data/cert1/files/complete FILE DATA 0 0 YES

Disaster Recovery Considerations

  • Before you use your agent, be sure to review and understand the associated full system restore (or disaster recovery) procedure. The procedure for some agents may require that you plan specific actions or consider certain items before an emergency occurs.  See Disaster Recovery for more information regarding your agent.