Install Considerations

Pre-Install

Post-Install

General

• The following loopback address must be present in the /etc/hosts file for all Unix clients:

  127.0.0.1     localhost

NetApp NAS File Servers

• For information on connecting the storage devices, refer to your vendor's documentation.
• After attaching the NetApp NAS file server and MediaAgent machine to the library and before you begin your installation, verify that the NDMP service is enabled in the NetApp file server.

Libraries and Drives

• Any removable-media library being used contains at least one, preferably more, media cartridges.
• The storage device and SCSI adapter drivers are installed and loaded on the MediaAgent computer. For more information on understanding the driver configurations, see Driver Configurations.

HP-UX

If you are installing on a HP-UX computer, you must manually mount the installation disc as described in Mount the Software Installation Disc.

General

You must configure the libraries and drives before using the MediaAgent for data protection operations. (For more information, see Library and Drive Configuration.)

The MediaAgent software supports various types of libraries and library configurations. See the following sections for more information:

• Blind Libraries
• Centera Clusters
• Direct-Attached Libraries
• Direct-Attached Shared Libraries
• HDS Data Retention Utility (DRU)
• IP Libraries (Like libraries attached to ACSLS Server)
• Disk Libraries
• NAS Libraries
• Optical Libraries
• SAN-Attached Libraries
• Stand-Alone Drives
• Virtual Tape Libraries

Pre-Install

Post-Install

General

• Be sure to obtain the necessary number of DB2 iDataAgent licenses. Each DB2 iDataAgent that you install requires one license. Licenses are used as the DB2 iDataAgent is configured as described in Create an Instance. The license type can be used on any supported Unix platform.

Cluster Specific

Complete the following steps:

1. Ensure that the affected database is installed only on the virtual machine.
2. If both the database and its application files are installed on the virtual machine, install the Base software and the required agents only on the virtual machine.
3. If the database application files are installed on the physical machine, install the Base software and the required agents only on all the affected physical nodes; you do not need to install these items on the virtual machine in this case. See Installation for more information.
4. Be sure to install your software to the appropriate directories per the directives in UNIX Clusters.
5. Verify that all of the computers to which software will be installed satisfy the minimum requirements specified in the appropriate System Requirements.
6. Ensure that services are up and running on the remote hosts.

General

• Once the DB2 iDataAgent is installed from CommCell Console, run the following command from <calypso >/iDataAgent on the client computer:

  Db2_Install.sh

  For example:

  root@orasolaris #./Db2_install.sh

  DB2 Instance Configuration Script:

  To integrate Calypso with a DB2 server we need to create a set of links under lib subdirectory of the DB2 installation directory.

  Please specify the Db2 Instance User Name that was selected when DB2 Instance was installed.DB2 Instance User Name: [db2inst1] db2inst3

  Calypso links will be created in  /Sybase/db2/V9.5B64/db2inst3/sqllib/lib.Executing /Sybase/db2/V9.5B64/db2inst3/sqllib/bin/db2level db2inst3 is not 7.x. No need to create flag file... Proceeding

  Press <ENTER> to continue ...

  DB2 Instance Configuration Script

  Would you like to configure another DB2 instance?

  Configure? [no]

  Creating Calypso links under /Sybase/db2/V9.5B64/db2inst3/sqllib/lib ... Creating Calypso links under /Sybase/db2/V9.5B64/db2inst3/sqllib/bin ...done.

• For a non-default (i.e., non-English language) system, be sure to disable the following parameters and restart the client services. Ensure that these parameters have the same value for root and the DB2 instance user. For example:

  LC_MESSAGES=

  LC_ALL=

  export LC_MESSAGES LC_ALL

  Also, ensure that LC_MESSAGE and LC_ALL have the same value as en_US under /etc/environment.

  Thereafter, run the following commands:

  Calypso stop

  Calypso start

• For DB2 on Unix, additional configuration is required if both of the following are true:

  • You are using the iDataAgent in support of the DB2 Version 7.2 or 8 32-bit application on any Solaris platform
  • You are planning to use the iDataAgent for several DB2 servers on the same machine, and each associated instance has at least one Unix user that is not associated with the other instance(s)

  If all of this is true, complete the following steps. Otherwise, various permission errors will occur, and backups will not work.

  1. Ensure that all the instance groups include all the instance users (e.g., if instance group "dba1" includes user "db2inst1", and if instance group "dba2" includes user "db2inst2", be sure to include both users in each instance group). To this purpose, edit the /etc/group file as appropriate.
  2. Ensure that the .profile of each instance user contains a umask 002 command at the end of the file. This will allow all the files created by one database user to be opened for writing by the other database users.

• 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.

Cluster

• The cvclusternotify script should be added as part of the normal cluster startup/shutdown procedure. The script is provided as a generic template, and it must be run at the beginning of node shutdown and at the end of new active node startup. In both cases, data protection services must be up and running.

  Run the following command to notify Calypso that the specified "virtual node" is going up or down because of a cluster failover:

  Usage:

  cvclusternotify -inst <Instance> -cn <Client Name> -start|-shutdown

  Where:

  cvclusternotify - Program to notify Calypso of cluster failovers

  Example:

  For two-node cluster, if the virtual client name is "virtual" and the application instance is "Instance001", run the following command:

  • To shutdown:

    cvclusternotify -inst Instance001 -cn "virtual" -shutdown

  • To start up:

    cvclusternotify -inst Instance001 -cn "virtual" -start

• On failover of a Linux cluster, Services may be killed by cluster services during a virtual machine failover. To insure that the Services are re-started on the passive node, add commands in failover scripts to start Services.
• 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.

Post-Install

General

• The following configuration tasks are required before you can begin using the software for data protection operations:
  1. Configure a supported Snapshot Environment for this agent.
  2. Create a New Subclient.

• 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.

Use of QSnap

• Upon installation of QSnap, the QSnap block-filter is activated by default for all volumes. This means that the QSnap block filter driver automatically monitors all volumes on the server. For more information, see The Block-Filter Driver and Bitmaps on the QSnap Overview page.

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.

Pre-Install

Post-Install

General

Complete the following steps:

1. Ensure that the affected database is installed only on the virtual machine.
2. If both the database and its application files are installed on the virtual machine, install the Base software and the required agents only on the virtual machine.
3. If the database application files are installed on the physical machine, install the Base software and the required agents only on all the affected physical nodes; you do not need to install these items on the virtual machine in this case. See Installation for more information.
4. Be sure to install your software to the appropriate directories per the directives in UNIX Clusters.
5. Verify that all of the computers to which software will be installed satisfy the minimum requirements specified in the appropriate System Requirements.
6. Ensure that services are up and running on the remote hosts.

General

• After the installation, you must configure the Informix iDataAgent in order to perform the backup and restore operations. The basic configuration details are described in Create an Instance.
• Once the Informix instance has been created and configured, in the CommCell Console, right-click the subclient, select Properties, then select the Subclient Properties (Content) tab to browse and populate all the objects that are available in the Informix database on the client. If you do not do this, Informix backups will not succeed, and the maximum number of streams available for backups will not display on the Informix Subclient Properties (Storage Device) tab.

• 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.

• If Informix server is using a language other that US English or if the database is using a different code page than that of the locale client and you want Informix to convert the language for both, update the following environment variables in the root profile:

  For Example Informix Data that use the Chinese code page GB 18030 then uses the following values: 

  DBLANG=zh_cn.GB18030-2000

  CLIENT_LOCALE=zh_cn.GB18030-2000

  DB_LOCALE=zh_cn.GB18030-2000

  SERVER_LOCALE=zh_cn.GB18030-2000

  Recycle Calypso Services.

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.

Cluster specific

• On failover of a Linux cluster, Services may be killed by cluster services during a virtual machine failover. To insure that the Services are re-started on the passive node, add commands in failover scripts to start Services.

• The cvclusternotify script should be added as part of the normal cluster startup/shutdown procedure. The script is provided as a generic template, and it must be run at the beginning of node shutdown and at the end of new active node startup. In both cases, data protection services must be up and running.

  Run the following command to notify Calypso that the specified "virtual node" is going up or down because of a cluster failover:

  Usage:

  cvclusternotify -inst <Instance> -cn <Client Name> -start|-shutdown

  Where:

  cvclusternotify - Program to notify Calypso of cluster failovers

  Example:

  For two-node cluster, if the virtual client name is "virtual" and the application instance is "Instance001", run the following command:

  • To shutdown:

    cvclusternotify -inst Instance001 -cn "virtual" -shutdown

  • To start up:

    cvclusternotify -inst Instance001 -cn "virtual" -start

Pre-Install

Post-Install

General

• While the Lotus Notes Database iDataAgent supports all logging styles (disabled, archive, circular, linear) it is strongly recommended that Archive Logging be used. For information on how to set the transaction logging style see Configuring the Lotus Domino Server for Transaction Logging.

  Logging methods should not be changed once the software has been installed. Changing logging methods after the software has been installed may result in unexpected results when data aging operations are performed.

  For overview information on transaction logging, refer to Domino Server Transaction Logs.

• The public name and address book (names.nsf) must be using the R5 or R6 template, in order for the required transaction logging settings to appear on the Server document.

• For the Lotus Notes Database iDataAgent, installation requires the Notes user's primary group to be provided.

General

• Before you back up data with the Notes Document iDataAgent, create a Restore View Name for each partition configured as described in Add a Restore View Name.
• If you did not install all the partitions with your initial install, remember to add the needed partitions to the iDataAgent afterward. To add a new partition to the iDataAgent, see either Add a Lotus Domino Server Partition on Windows or Add a Lotus Notes Database Partition on Unix for more detail.
• Schedule appropriate backups for the default and transaction log subclients based upon server activity and business requirements:
  • For default and user-defined subclients schedule incrementals based upon how often new databases are added to the Domino server.
  • For the transaction log subclient, create schedules based upon the volume of data that is changed or added. For more information on transaction logging, see Domino Server Transaction Logs.

• 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.

Pre-Install

Post Install

General

• For Macintosh, before installing/upgrading the product, log on to the client as a valid user. In the terminal window, issue the su - root command to substitute your user identity with that for the root user. Then enter the valid root user password.
• The install package requires super-user permissions to execute.

General

For Macintosh File System, set up the Macintosh kernel to allow it to find any shared libraries required to run any dependent program or tools (e.g., NameChangeTool). To this end, run the /cvprofile script before running any such programs or tools.  For example:

. /<software installation path>/Base/cvprofile

This will set the DYLD_LIBRARY_PATH. If you do not run /cvprofile, you will encounter errors.

Post-Install

General

• After the installation, you must create a MySQL Server on the CommCell Console. The basic configuration details are described in Create an Instance.
• Before running your first backup, you must do one of the following: open the Subclient Properties dialog box in the CommCell Console, click the Content tab, and click Configure to add or modify content; or, open the MySQL Instance Properties box and click the Enable Auto Discovery option. This action is required to browse and populate all the objects that are available in the MySQL Server on the client. Newly created databases will be automatically added to the default subclient.

• 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 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.

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.

Pre-Install

Post Install

General

• When Installing Oracle iDataAgent make, sure that Calypso is installed with appropriate group that is part of the Oracle user account, or any other account with permissions set to read-write-execute.
• 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.
• Agents should be installed only after the CommServe and at least one MediaAgent have been installed in the CommCell. Also, make sure that the CommServe and MediaAgent are installed and running (but not necessarily on the same computer).
• Ensure that the Oracle Database application has been installed on the client.
• This software should be installed in a CommCell with current versions of the CommServe and MediaAgent software.
• The install package requires super-user permissions to execute.

Cluster specific

• Complete the following steps:

  1. Ensure that the affected database is installed only on the virtual machine.
  2. If both the database and its application files are installed on the virtual machine, install the Base software and the required agents only on the virtual machine.
  3. If the database application files are installed on the physical machine, install the Base software and the required agents only on all the affected physical nodes; you do not need to install these items on the virtual machine in this case. See Installation for more information.
  4. Be sure to install your software to the appropriate directories per the directives in UNIX Clusters.
  5. Verify that all of the computers to which software will be installed satisfy the minimum requirements specified in the appropriate System Requirements.
  6. Ensure that services are up and running on the remote hosts.
  Ensure that the Base software is installed in the same base directory on all physical nodes in the cluster. Otherwise, the Oracle configuration for the passive nodes will be corrupted and will need to be relinked.
•  The software in a Unix cluster can be installed from the active node in the cluster group. Note that for a passive node in a Unix cluster, you need to install the software separately on the passive node in the cluster group.
• The install package requires super-user permissions to execute.

General

If you did not enable the Download latest update pack(s) during the install/upgrade, install post-release updates or Service Packs that may have been released after the release of the software. When you are installing a Service Pack, 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.

Cluster

The cvclusternotify script should be added as part of the normal cluster startup/shutdown procedure. The script is provided as a generic template, and it must be run at the beginning of node shutdown and at the end of new active node startup. In both cases, data protection services must be up and running.

Run the following command to notify Calypso that the specified "virtual node" is going up or down because of a cluster failover:

Usage:

cvclusternotify -inst <Instance> -cn <Client Name> -start|-shutdown

Where:

cvclusternotify - Program to notify Calypso of cluster failovers

Example:

For two-node cluster, if the virtual client name is "virtual" and the application instance is "Instance001", run the following command:

• To shutdown:

  cvclusternotify -inst Instance001 -cn "virtual" -shutdown

• To start up:

  cvclusternotify -inst Instance001 -cn "virtual" -start

Post Install

General

• After the installation, you must create a PostGreSQL Server on the CommCell Console. The basic configuration details are described in Create an Instance.
• Before running your first backup, you must do one of the following: open the Subclient Properties dialog box in the CommCell Console, click the Content tab, and click Configure to add or modify content. This action is required to browse and populate all the objects that are available in the PostGreSQL Server on the client. Newly created databases will be automatically added to the default subclient.
• Ensure that the PostGreSQL database is in "Archive Mode" before taking a File system/Log backup.

• 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 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.

Pre-Install

Post-Install

 General

• If you will be using Unix QSnap with the Quick Recovery Agent, and you plan to install QSnap before installing the Quick Recovery Agent, then you must enable QSnap when you install it (or before installing the Quick Recovery Agent). Quick Recovery Agent installation will fail if QSnap is installed but not enabled. To enable QSnap when you install it, type Yes or Y when asked whether you want to activate the snapshot functionality of CXBF. (See Install QSnap - Unix.)

• In addition to a license for the agent, you must also have a license for the following components if you intend to use them:
  • Unix QSnap
  • Enablers
• If you intend to use LAN copy manager with the agent, the MediaAgent must be installed on both the source and destination clients.

 General

• The following configuration tasks are required before you can begin using the Quick Recovery Agent for data protection operations:
  1. Configure a supported Snapshot Environment for this Agent. See Snapshot Environments for more information. For SnapVault, see the Configuration section of ONTAP SnapVault for the Quick Recovery Agent or OSSV SnapVault for the Quick Recovery Agent.
  2. Create a Scratch Volume Pool.
  3. Create a QR Policy.
  4. Create a New Subclient.
  5. Configure Pre/Post Binding Scripts for the Quick Recovery Agent.

• 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.

Pre-Install

Post-Install

General

• 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.

General

• After the installation you must configure the SAP for MAXDB iDataAgent in order to perform the backup and restore operations. The basic configuration details are described in Configuration - SAP for MAXDB iDataAgent.

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.

Pre-Install

Post-Install

General

• Be sure to obtain the necessary number of Sybase iDataAgent licenses. Each Sybase iDataAgent that you install requires one license. Licenses are used as the Sybase iDataAgent is configured as described in Create an Instance. The license type can be used on any supported Unix platform.
• Users will require the login name and password for a Sybase account (this account is used by the Sybase iDataAgent).

General

• Once the Sybase iDataAgent is installed from CommCell Console, run the following command from <calypso >/iDataAgent on the client computer:

  Syb_install.sh

  For example:

  root@clientlnx#./Syb_install.sh

• After the installation, you must create a Sybase Server on the CommCell Console. The basic configuration details are described in Create an Instance.
• Once the Sybase Server is installed and configured, you must open the Sybase Server Properties box and click a backup server from the appropriate list.
• Before running your first backup, you must do one of the following: open the subclient Properties dialog box in the CommCell Console, click the Content tab, and click Configure to add or modify content; or, open the Sybase Server Properties box and click the Enable Auto Discovery option. This action is required to browse and populate all the objects that are available in the Sybase database on the client.

• 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.

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.

Pre-Install

Post-Install

General

• Log on to the client as root.
• The install package requires super-user permissions to execute.

• 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.
• If you are performing the remote install in a PowerBroker^TM environment, make sure to follow the steps described in Install Software in a PowerBroker™Environment from CommCell Console.

Cluster

• Refer to Supported Unix Cluster Installations for important overview information about installing MediaAgent or Agent software in a Unix clustered environment.
• If you are installing a File System iDataAgent in a cluster group, a Virtual File System license is required. For more information about cluster license requirements, refer to Clustering Support - License Requirements.
• Check the following on the cluster computer in which you wish to install the software:
  • Cluster software is installed and running.
  • Active and passive nodes are available.
• The software in a Unix cluster can be installed from the active node in a cluster group. Note that for a passive node in a Unix cluster, you need to install the software separately on the passive node in a cluster group.

• If the installation will have /tmp mounted with the NOEXEC option, the GX_TMP_DIR environment variable must be set to a directory with execute privileges and then exported (for example: export GX_TMP_DIR=/space/tmp).

General

• 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.

• To run Backup or Data Collection job successfully when this Agent is installed on a freshly installed Linux computer that has SELinux enabled, set SELinux enforcing to 0 as /usr/sbin/setenforce 0.

Solaris

• For the Solaris File System iDataAgent, if the Bull Calypso Communications Service is on an IPv4-only stack (e.g., you do not have a local host IPv6 configured), be sure to do the following before you run a data protection operation:
  1. Enable the IPv6 stack.
  2. Change nPreferredIPFamily to 1 (i.e., force IPv4).
  3. Remove or comment out ‘::1’ from /etc/inet/ipnodes.
  4. Alter startup to run on just the local host IPv6. For example:

     ifconfig lo0 inet6 plumb

     route add –inet6 ::1/128 localhost

     ifconfig lo0 inet6 up

Cluster

• Complete the following steps:

  1. Install the Base software and the required agents on all the nodes that are included in the cluster service. See Installation for more information.
  2. Be sure to install your software to the appropriate directories per the directives in UNIX Clusters.
  3. Verify that all of the computers to which software will be installed satisfy the minimum requirements specified in the appropriate System Requirements.
  4. Ensure that services are up and running on the remote hosts.

• The cvclusternotify script should be added as part of the normal cluster startup/shutdown procedure. The script is provided as a generic template, and it must be run at the beginning of node shutdown and at the end of new active node startup. In both cases, data protection services must be up and running.

  Run the following command to notify Calypso that the specified "virtual node" is going up or down because of a cluster failover:

  Usage:

  cvclusternotify -inst <Instance> -cn <Client Name> -start|-shutdown

  Where:

  cvclusternotify - Program to notify Calypso of cluster failovers

  Example:

  For two-node cluster, if the virtual client name is "virtual" and the application instance is "Instance001", run the following command:

  • To shutdown:

    cvclusternotify -inst Instance001 -cn "virtual" -shutdown

  • To start up:

    cvclusternotify -inst Instance001 -cn "virtual" -start

• On failover of a Linux cluster, Services may be killed by cluster services during a virtual machine failover. To insure that the Services are re-started on the passive node, add commands in failover scripts to start Services.

Cluster/Global File Systems

For Cluster/Global File System iDataAgents, it is highly recommended that you do the following before you back up data (see Subclients for more information):

• Filter out any clustered file systems from your physical node(s). Examples of such file systems include Global File systems or file systems that are part of a failover resource group.
• Ensure that the clustered file systems will be backed up only from the virtual node(s). To this end, change the default subclient contents as appropriate or create separate subclients for the clustered file system data.

Doing this will ensure that your data will be protected by just one instance of the iDataAgent and therefore will not be duplicated. It will also provide a single source from which to restore clustered data.

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.

GENTOO

Once the software is installed on Gentoo client computer, it is recommended that you do the following on the Gentoo client computer:

1. Create a text file with file name as galaxy, include the following script and save this file under /etc/init.d.Make sure that the users have 755 permissions on this file.

   #!/sbin/runscript

   start() {

   ebegin "Starting Calypso Service"

   /etc/init.d/Galaxy start

   eend 0

   }

   stop() {

   ebegin "Stopping Calypso Service"

   /etc/init.d/Galaxy stop

   eend 0

   }

2. Login to the client computer as root, and run the following command from the commandline:

   rc-update add galaxy

Post Install

The cvclusternotify script should be added as part of the normal cluster startup/shutdown procedure. The script is provided as a generic template, and it must be run at the beginning of node shutdown and at the end of new active node startup. In both cases, data protection services must be up and running.

Run the following command to notify Calypso that the specified "virtual node" is going up or down because of a cluster failover:

Usage:

cvclusternotify -inst <Instance> -cn <Client Name> -start|-shutdown

Where:

cvclusternotify - Program to notify Calypso of cluster failovers

Example:

For two-node cluster, if the virtual client name is "virtual" and the application instance is "Instance001", run the following command:

• To shutdown:

  cvclusternotify -inst Instance001 -cn "virtual" -shutdown

• To start up:

  cvclusternotify -inst Instance001 -cn "virtual" -start

Pre-Install

Post-Install

General

• If you have edited the Domino servers local host file to resolve Notes port mapping issues, make sure that the network interface names are recognized by the DNS server and are not just local host file entries. Check the default values before accepting them. Otherwise, the CommServe and MediaAgent may not be able to access the client using the interface names that you have entered.
• Ensure that the Domino Server ID does not have an associated password. If the Domino Server ID has a password associated with it, you must enable the option on the ID called Dont prompt for password from other Notes based programs. For more information on the subject, see Domino Server ID.

• For the Lotus Notes Database iDataAgent, installation requires the Notes user's primary group to be provided.

General

• After installing the Domino Mailbox Archiver Agent, restart the Domino Server by typing the command restart server from the Domino Server Console.

• After installing the Domino Mailbox Archiver Agent, the Lotus Notes Mailbox master template should be configured to display a stub icon for each message archived. When this configuration is performed, the Lotus Notes client mailbox will automatically display archived messages with a stub icon. Users can then recall the archived message by opening the message in the Lotus Notes client mailbox.

  See Configure Stub Icons for Lotus Notes Mailboxes for step-by-step instructions.

• Create a Subclient - see Subclients - Domino Mailbox Archiver for more information.
• The Domino Server should be up and running while performing discoveries of mail databases.
• Archiving Rules are initially disabled by default. You must clear the Disable All Rules option in the Subclient Properties (Archiving Rules) or (Rules) tab and configure the archiving rules before conducting rules-based Archive Operations.

• The Domino Mailbox Archiver Agents provides three modes which further direct how archive and recovery operations behave for each subclient. These modes can be selected using the General tab of the Subclient Properties dialog box and should be configured prior to running the first archive operation.

  See Operation Modes for more information.

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.

Pre-Install

Post-Install

SGI

The SGI platform requires that the XFS file system used with File Archiver for IRIX be mounted with the "dmi" option (dmapi). For example, here is a sample entry from /etc/fstab:

/dev/dsk/dks1d2s0 /testfs xfs rw,dmi 1 1

Solaris

General

Complete the following steps:

1. Install the Base software and the required agents on all the nodes that are included in the cluster service. See Installation for more information.
2. Be sure to install your software to the appropriate directories per the directives in UNIX Clusters.
3. Verify that all of the computers to which software will be installed satisfy the minimum requirements specified in the appropriate System Requirements.
4. Ensure that services are up and running on the remote hosts.

HP-UX

If you are installing on a HP-UX computer, you must manually mount the installation disc as described in Mount the Software Installation Disc.

Solaris

General

• The following configuration tasks are required before performing an Archive Operation using this Archiver Agent:
  • Create a Subclient - see Getting started - Unix File Archiver Agent Configuration for more information.
  • Archiving Rules are initially disabled by default. You must clear the Disable All Rules option in the Subclient Properties (Archiving Rules) or (Rules) tab and configure the archiving rules before conducting rules-based Archive Operations.
• Any application that has open files or directories on the CXFS mount point (CXFS is a special file system type for File Archiver on Unix) must be shut down prior to the first migration archiving operation, or prior to restarting the CommCell application on the client. Any applications that access files on the CXFS mount point must be started after the CommCell application has started.

• 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 computers running OES Linux, the following parameter needs to be added in the Calypso Services script to ensure NSS is loaded before Calypso Services:

  • Navigate to the following directory: /etc/init.d
  • Open the file Galaxy, and locate the following entry:
    ###BEGIN INIT INFO
  • At the end of the line Required-Start: $all, append novell-nss so that the entire line reads:
    Required-Start: $all novell-nss
  • Save and Close the file.
  • Run the following command in the terminal:
    insserv -f /etc/init.d/Galaxy

Cluster

• On failover of a Linux cluster, Services may be killed by cluster services during a virtual machine failover. To insure that the Services are re-started on the passive node, add commands in failover scripts to start Services.

Pre-Install

CDR Driver for Linux

• A compiled version of the CDR driver is supplied only for the versions and kernels listed in System Requirements - ContinuousDataReplicator. If you perform online updates of Linux, you may encounter a situation where the supplied CDR driver will not load after a reboot because the kernel has been updated to a new version.