BEBWN ClientAgent

Client Agent Guide
Windows and UNIX

BrightStor
Enterprise Backup

This documentation and related computer software program (hereinafter referred to as the Documentation) is for
the end users informational purposes only and is subject to change or withdrawal by Computer Associates
International, Inc. (CA) at any time.
This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without
the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright
laws of the United States and international treaties.
Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for
their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only
authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the
license for the software are permitted to have access to such copies.
This right to print copies is limited to the period during which the license for the product remains in full force and
effect. Should the license terminate for any reason, it shall be the users responsibility to return to CA the reproduced
copies or to certify to CA that same have been destroyed.
To the extent permitted by applicable law, CA provides this documentation as is without warranty of any kind,
including without limitation, any implied warranties of merchantability, fitness for a particular purpose or
noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or
indirect, from the use of this documentation, including without limitation, lost profits, business interruption,
goodwill, or lost data, even if CA is expressly advised of such loss or damage.
The use of any product referenced in this documentation and this documentation is governed by the end users
applicable license agreement.
The manufacturer of this documentation is Computer Associates International, Inc.
Provided with Restricted Rights as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or
DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.
2003 Computer Associates International, Inc.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

Chapter 1: Introduction
Features .................................................................................... 1-2
Benefits ..................................................................................... 1-4
Push Technology ............................................................................ 1-4
Multi-Stream Processing ..................................................................... 1-5
Snapshot and DirectIO Support ............................................................... 1-6
Using File System Snapshot and DirectIO Technology ....................................... 1-6
Chapter 2: Installing and Using the Client Agent
Installing the Client Agent .................................................................... 2-1
Installing the Client Agent for Windows ................................................... 2-1
Installing the Client Agent for NetWare .................................................... 2-6
Installing the Client Agent for UNIX/Linux ................................................ 2-8
Installing the Client Agent for AS/400 .................................................... 2-10
Installing the Client Agent for OpenVMS.................................................. 2-12
Configuring the Client Agent ................................................................ 2-17
Configuring the Client Agent for Windows................................................ 2-18
Configuring the Client Agent for NetWare ................................................ 2-27
Configuring the Client Agent for UNIX/Linux............................................. 2-29
Configuring the Client Agent for AS/400.................................................. 2-40
Configuring the Client Agent for OpenVMS ............................................... 2-42
General Client Agent Configuration Issues ................................................ 2-42
Configuring the Port Address for the Client Agent ............................................. 2-43
Configuring the Port Address for the Client Agent for Windows ............................ 2-43
Configuring the Port Address for the Client Agent for UNIX/Linux ......................... 2-43
Configuring the Port Address for the Client Agent for OpenVMS............................ 2-44
Access Control List (ACL) for Client Agents................................................... 2-44
ACL for the Client Agent for Windows.................................................... 2-44
ACL for the Client Agent for UNIX/Linux ................................................ 2-45
Contents iii

iv
Getting Information from the Client Agent ....................................................2-46
Getting Information from the Client Agent for Windows ....................................2-46
Getting Information from the Client Agent for NetWare.....................................2-46
Client Agent Activity Log ................................................................2-47
Adding Client Agent Objects .................................................................2-48
Adding a Windows Client Agent Object ...................................................2-48
Adding a Windows Client Agent Object Using Auto-Discovery..............................2-50
Adding a NetWare Client Agent Object....................................................2-51
Adding a UNIX/Linux Client Agent Object ................................................2-52
Implementing the Use Agent Option ......................................................2-53
Adding a Client Object Using the Command Line ..........................................2-54
Starting and Stopping the Client Agent ........................................................2-54
Starting and Stopping the Client Agent for Windows .......................................2-54
Starting and Stopping the Client Agent for NetWare ........................................2-55
Starting and Stopping the Client Agent for UNIX/Linux ....................................2-55
Starting and Stopping the Client Agent for AS/400 .........................................2-56
Starting and Stopping the Client Agent for OpenVMS.......................................2-56
Index

Chapter
1
Introduction

BrightStor Enterprise Backup Client Agents provide administrators with
powerful solutions to back up heterogeneous environments from multiple
BrightStor Enterprise Backup platforms. Using the Client Agents, you can
administer complete data protection for Windows, UNIX, NetWare, Linux,
AS/400, and OpenVMS client machines from multiple BrightStor Enterprise
Backup managers. All Client Agents use Push Technology, allowing the filtering
and packaging of data by the client before sending that data to the BrightStor
Enterprise Backup server.
The Client Agent is a service you install on a network client machine to help
BrightStor Enterprise Backup retrieve and send data to and from the
workstation. This improves data transfer and provides network security, job
monitoring, real-time directory browsing, and cross-platform backup support.
The Client Agent contains separate internal client engines that help reduce the
resource-intensive processes for the BrightStor Enterprise Backup host. It is a
go-between that allows BrightStor Enterprise Backup to efficiently back up
machines running various operating systems.
When the Client Agent is properly installed and configured, you can use
BrightStor Enterprise Backup to retrieve data from remote clients. The Client
Agent browses the targeted directories and packages the data across the wire in
pulses of large data packets. The BrightStor Enterprise Backup host server then
prepares the data for storage on the designated storage devices. These
simultaneous processes between the client machine and host backup system
create a more efficient backup.
Introduction 11
Features
BrightStor Enterprise Backup Client Agents are available for the following
systems:
WindowsWindows 9x and ME; Windows NT/2000/XP; Windows XP
64-Bit Edition
UNIXAll major UNIX derivatives including Solaris, HP-UX, AIX, Tru64,
SGI IRIX, and SCO
NetWare
LinuxMajor Linux distributions such as Red Hat, SuSE, Caldera, Turbo
Linux, and Debian.
AS/400
OpenVMS
Note: Information or procedures (or both) that pertain to the Client Agent covers
all the Client Agent platforms listed above unless explicitly stated otherwise.
Features
The following is a list of Client Agent features:
Push TechnologyWith push technology (described in more detail in the
section Push Technology in this chapter), the backup job is completed
more efficiently by processing the data locally at the workstations, which
off-loads the system resources from the BrightStor Enterprise Backup host
server and minimizes network traffic by sending data in large pulses of data
packets during backup jobs.
Real-time Remote BrowsingWith the Client Agent installed, the system
administrator can view detailed file and directory information about the
remote target machine in real-time.
Multi-stream processing (Windows and UNIX)One Client Agent can
handle different requests and perform multiple jobs at the same time.
Compression Support (Windows and UNIX)BrightStor Enterprise
Backup supports software compression for data transport and archival
needs.
Encryption SupportAll Client Agent backup jobs can be encrypted with a
session/encryption password to enhance network security. This feature is
supported on Windows and encrypted versions of UNIX.
Auto-discoveryFor BrightStor Enterprise Backup servers installed on the
Windows platform, you can automatically discover installed Windows and
UNIX clients on the network. BrightStor Enterprise Backup servers installed
on the UNIX platform, however, are not able to utilize auto-discovery.
12
Features
Remote InstallationThe Client Agent can be installed remotely from most
Windows machine on your networksee the section Known Installation
Issues for the Client Agent for Windows in the chapter Installing and
Using the Client Agent.
Virus ScanningIntegrated Client Agent-level virus scanning support for
most client platforms.
CRC (Cyclic Redundancy Check) Verification Support (Windows and
NetWare only)The Client Agent generates CRC codes for all the files that
it sends for backup to the BrightStor Enterprise Backup server. This is so the
files can be verified without requiring the original source files.
Password Security OptionSupports Client Agent-level passwords for the
Windows platform. UNIX agent uagent supports UNIX-level system security
and No Password mode.
Access Control List (ACL)Allows you to control which BrightStor
Enterprise Backup server accesses the machine through the Client Agent.
This is supported on Windows and UNIX only.
Volume Shadow Copy Service support (Windows XP only)Allows a
snapshot to be taken of a disk at a point in time, and to back up the data
from that snapshot. This support provides access to files that are open,
reduces the likelihood of data integrity problems that may be caused when
changes occur to a file during its backup, and applications can modify files
while those files are being backed up.
Virtual Interface (VI) ProtocolBrightStor Enterprise Backup supports the
VI protocol to provide faster remote backup and restore. By using VI, the
Agent is able to move the data retrieved from the client faster over the
network and on to BrightStor Enterprise Backup, and also to receive the data
from BrightStor Enterprise Backup. This feature is for Windows
NT/2000/XP only.
Snapshot and DirectIO support (Solaris and HP-UX systems only)
BrightStor Enterprise Backup supports tighter integration with Veritas File
System (VxFS) and UNIX File System (UFS) by supporting their Snapshot
and DirectIO capabilities. The Snapshot capability supports point in time
data backup and open file backup. The DirectIO capability enhances the
performance of backup and restore operations. Snapshot and DirectIO
support are applicable at the volume level only. See the section Snapshot
and DirectIO Support later in this chapter for more details on this feature.
Introduction 13
Benefits
Benefits
Using BrightStor Enterprise Backup and the Client Agent provide the following
benefits:
Minimized load on your communications network
Increased efficiency for your BrightStor Enterprise Backup server by
off-loading the processing of data to the client machine
Detailed file and directory information on the remote client in the BrightStor
Enterprise Backup Browser
Push Technology
The Client Agent runs on a remote machine and enables communications
between the BrightStor Enterprise Backup host server and the remote machine.
The Client Agent utilizes Push technology to help perform Backup and Compare
jobs and can be described as a remote processing agent. All filtering of files and
directories is done on the client machine prior to pushing the data to the
BrightStor Enterprise Backup host server (the server running BrightStor
Enterprise Backup) for Backup or Compare jobs.
Push technology minimizes the transfer of data to the BrightStor Enterprise
Backup host, because the Client Agent sends only the data needed for backup,
which reduces the load on your communications network and accelerates
backup. The BrightStor Enterprise Backup host server can operate more
efficiently since it no longer has to filter the data for the backup job.
Specifically, backups of a remote machine without the Client Agent operate on
the basis of a series of per file requests. The remote client essentially regards
this mode as a passive mode. The host server requests files from the remote
client, one file at a time.
In contrast, the Client Agent operates on the basis of a per job request. In this
mode, the host server sends an entire list of files to the remote client at one time.
The Client Agent then enables the remote machine to take an active role in the
process by pushing all requested files to the host server (rather than having
them pulled one at a time by the host server).
In this way, use of the Client Agent results in considerable savings in both
network traffic and time, because it eliminates the series of
request/acknowledge packets that otherwise must be transmitted for each file.
The Client Agent also reduces the host servers processing load by taking over
the file processing task.
14
Multi-Stream Processing
To take full advantage of the remote backup capabilities of BrightStor Enterprise
Backup, the Client Agent must be installed on each client that you want to
include in your backup schedule.
Multi-Stream Processing
Multi-stream processing allows you to take advantage of all the available tape
devices on the system, by splitting a single backup job into multiple jobs using
all the tape devices. As a result, it increases of the overall backup throughput
compared with the sequential method. If you have more than one drive and
more than one volume in the system you can choose the Multi-stream option.
Multi-stream processing works for both local and remote computers, and is
supported by the Agent as well.
You can use all of the devices, or you can specify only a single group of devices
(if you have mixed types of devices in the system). If the Tape Library Option is
installed, Multi-stream processing (when selected) uses all the library devices. If
the Tape Library Option is not installed, you should put the devices into separate
groups. Total number of streams (slave jobs) created depends on the number of
tape devices and device groups.
Multi-stream processing is performed at the volume level for regular file systems
(two volumes can run simultaneously on two separate devices), and at the
database/tablespace level for local database servers. Multi-stream processing is
performed at node level for Preferred Shared Folder, remote database servers,
and the Windows NT/2000/XP Agent.
You can have only as many jobs running simultaneously as the number of
devices/groups that are on the system. With the Multi-stream processing option,
one master job is created which triggers slave jobs for as many volumes as you
have. When a job is finished on one device, another job is executed until there are
no more jobs to run.
See the BrightStor Enterprise Backup Administrator Guide for more information on
Multi-stream processing.
Introduction 15
Snapshot and DirectIO Support
The Snapshot and DirectIO support can be applied in the following
environments:
Snapshot In Solaris with:
Advanced version of VxFS file system (Solaris 7, 8, and 9)
UFS file system with the fssnap package installed (Solaris 8 and 9)
In HP-UX 11.0 with:
Advanced version of VxFS file system or Online JFS file system
DirectIO In Solaris with:
Advanced version of VxFS file system or UFS file system (Solaris 7, 8, and 9)
In HP-UX 11.0 with:
Using File System Snapshot and DirectIO Technology
Certain file systems like VxFS, Online JFS, and UFS with the fssnap utility
support the capability of Snapshot and DirectIO.
The BrightStor Enterprise Backup file system agent takes the Snapshot on
Advanced version of VxFS, Online JFS in HP-UX 11.0, and UFS with fssnap
installed on Solaris 8 and above. It mounts the Snapshot to a temporary directory
created in the root volume. Then it performs the Snapshot backup. After
completion of the Snapshot backup, it dismounts from the temporary directory
and then deletes the Snapshot.
To perform a Snapshot backup, you need to specify a Snapshot buffer. A
Snapshot buffer is the buffer that is used for storing the original data before it is
overwritten in the snapped volume. For UFS on the Solaris platform (using
fssnap), the Snapshot buffer can be a file name, a directory name, or a raw
partition. However, you need to consider a few things regarding the Snapshot
buffer:
The Snapshot buffer needs to be large enough to store all the data that
changes in the snapped volume for the duration of the backup. If the
Snapshot buffer runs out of space, then the Snapshot becomes invalid and
the backup fails.
16
The snapped volume and the Snapshot buffer should not be on the same file
system.
For better performance, the snapped volume and the Snapshot buffer should
be on separate physical disks.
For DirectIO backup or restore, you need to check the client environment and
edit the caagperf.cfg file. DirectIO is supported by the VxFS, Online JFS, and UFS
file systems. The BrightStor Enterprise Backup file system agent supports the
DirectIO capability, and you can observe improvement in the performance
during backup and restore.
You can view Snapshot and DirectIO on the file systems that are shown in the
caagperf.cfg configuration file by executing the mount command at the command
line after submitting the backup or restore job.
For Snapshot, the output that appears after executing the mount command is a
new, read-only file system with the mount point starting with the prefix
SNAP_HOME_ . A DirectIO user can observe the changes in the mount options
on that particular file system.
You can also see the detailed messages in the caagperf.log file if you enabled the
logging flag in the caagperf.cfg file.
For information on the procedure to utilize Snapshot backup or DirectIO backup
or restore, see the subsection, Using the Snapshot or DirectIO Feature under
the section Configuring the Client Agent for UNIX/Linux in Chapter 2 of this
guide.
Introduction 17

Chapter
2
Installing and Using the Client
Agent

This chapter describes how to install and use the Client Agent. It also describes
general configuration issues.
When the Client Agent is started, the machine is ready to communicate with the
BrightStor Enterprise Backup server if a Backup or Restore job is initiated. If the
Client Agent is stopped during a Backup or Restore job, the job will fail.
Installing the Client Agent
This section covers the installation procedures of the available Client Agents.
Any known issues (if applicable) of which you should be aware are described as
well.
Installing the Client Agent for Windows
The Client Agent for Windows can be installed on machines running Windows
9x, ME, NT 4.0, Windows 2000, Windows XP, Windows XP 64-Bit, and Windows
Server 2003. These are the recommended minimum hardware requirements:
CPU200 MHz or higher
Memory128 MB or higher
Disk Space20 MB
The Client Agent can use any one of these network protocolsTCP/IP,
Windows direct sock, RPC, or SNMP. Before you can run the Client Agent for
Windows, you must install one of these network protocols.
The Client Agent for Windows also supports Terminal service, Content Indexing
service, and Removable Storage Management (RSM) databases.
Installing and Using the Client Agent 21
To install the Client Agent for Windows, follow these steps:
1. From the BrightStor Enterprise Backup CD, select Install Products, and then
Install BrightStor Enterprise Backup agents, options and more.

2. After the License Agreement and Customer Information dialogs appear, the
Select Install Type dialog appears:

22
Three install types are shown, select the one that is appropriate for your
environment:
Local InstallYou can select which BrightStor Enterprise Backup
products to install on the local machine.
Remote InstallYou can select which BrightStor Enterprise Backup
products to install on one or more remote machines.
Create a response fileYou can create a response file that can be used in
a zero administration installation.
3. After you select the Install Type, you are prompted to select the BrightStor
Enterprise Backup products that you wish to install. Select the Client Agent
for Windows, as follows:

This dialog shows how to select the Client Agent for Windows installation
for a Windows NT, 2000, or XP (32-Bit) machine.
If you wish to change the Install Path, click Change Folder.
Click Disk Information to check available disk space for the hard drive(s) on
your computer before you install.
To install the Client Agent for Windows on a Windows 9x or ME machine, or
to a machine running Windows XP 64-Bit, see the following dialog:

Note the two separate selections to install the Client Agent for Windows on
these platforms. To select either of these, you must scroll down to the bottom
of the Products list.
24
4. After you make your selection and click Next, the Product List dialog
appears, showing the list of the product(s) and the Install Path(s) that you
selected for installation.

Click Install to begin the installation of the Client Agent for Windows. When
installation is complete an Install Summary dialog appears to confirm that
the installation has completed.
Known Installation Issues for the Client Agent for Windows
The following describes known issues that you should be aware of when
installing the Client Agent for Windows.
Remote setup for Windows XPIf the Force Network Logons Using Local
Accounts to Authenticate as Guest local security policy is enabled on a
remote Windows XP machine, remote setup to that machine is not
supported.
Remote setup for Windows 9x and MERemote installation is not
supported on Windows 9x and Millennium Edition machines.
Alternative installationYou can choose to install the Windows Client
Agents directly from the Client Agents Installation Browser CD.
Installing the Client Agent for NetWare
This section describes the procedures for installing the BrightStor Enterprise
Backup Client Agent on NetWare.
The Client Agent for NetWare can be installed on machines running the
following versions of NetWare:
4.1x with Service Pack 9
4.2 with Service Pack 9
To install the Client Agent for NetWare, follow these steps:
1. From the BrightStor Enterprise Backup CD, select Install Products, and then
Install BrightStor Enterprise Backup Client Agent for NetWare.

2. The Welcome screen appears. To begin installation, click Next.
3. You are prompted to choose where to install the Client Agent. You must
have Supervisor rights on the machine on which you want to install this
product.
4. Specify the path to install this product.
26
5. A screen appears showing the components that will be installed. Click
Finish.
6. An Installation Complete dialog appears at the end of installation. Click
Close.
Installation Considerations for the Client Agent for NetWare
We recommend that you use the latest NetWare CLIB and SMS modules. The
NLMs are found at the Novell Website at http://support.novell.com.
Alternatively, you can choose to install the NetWare Client Agent directly from
the Client Agents Installation Browser.
Installing the Client Agent for UNIX/Linux
Backup Client Agent on a UNIX or Linux platform.
The BrightStor Enterprise Backup Client Agent for UNIX/Linux supports the
following platforms:
IBM AIX 4.33, 5L (32- and 64-bit), and 5.1
HP-UX 10.20, 11.0, and 11.11
Linux (Red Hat 6.1, 6.2, 7.0, 7.1, 7.2; SuSE 6.3, 6.4, 7.0, 7.3; Caldera eServer 2.3,
3.0, 3.1, eDesktop 2.4; Turbo Linux 6.0, 6.5, 7.0; and Debian Linux 2.2, 2.3)
SCO OpenServer 3.2, 5.00, 5.05, 5.06
SCO UNIXWare 2.1 and 7.1.1
Silicon Graphics (SGI) IRIX 6.5
Sun Solaris Intel 2.6
Sun Solaris SPARC 2.5, 2.5.1, 2.6, 7, 8, and 9
HP Tru64 4.0E, 4.0F, 4.0G, 5.0, 5.1, and 5.1A
The installation instructions for installing the Client Agent on a UNIX or Linux
platform can be selected from the BrightStor Enterprise Backup CD, Client
Agents Installation Browser. Click on Install BrightStor Enterprise Backup Client
Agents.

28
Click Client Agent for UNIX installation instructions, as shown:

This launches your web browser where you can view the webpage that contains
links to the installation and release notes file for each of the supported UNIX and
Linux Client Agents.

Installing the Client Agent for AS/400
Backup Client Agent on the AS/400 platform.
The BrightStor Enterprise Backup Client Agent for AS/400 supports version
V4R4M0 and above.
The installation instructions for installing the Client Agent on the AS/400
Agents.

210
Click Client Agent for AS/400 installation instructions, as shown:

This launches your web browser where you can view the HTML file that
contains all the information you need to install the Client Agent for AS/400.

Installing the Client Agent for OpenVMS
Backup Client Agent on the OpenVMS platform.
The BrightStor Enterprise Backup Client Agent for OpenVMS supports the
following versions of OpenVMS:
Alpha OpenVMS 6.2, 7.1, 7.2, and 7.3
VAX OpenVMS 6.2, 7.1, 7.2, and 7.3
On a machine running either of the above, you can use either the TCP or UDP
protocol, with any of the following protocol software:
Compaq UCX 4.2 eco 3 or higher (on Alpha)
Compaq UCX 3.3 eco 13 or higher (on VAX)
Compaq TCPIP v5.0 or higher
Process Software Multinet v4.1B (with patches) or higher
Process Software TCPWARE 5.3 or higher
Important! If desired, you can install two or more of the protocol software products
listed above on the same machine. However, you can run only one protocol software
product at any one time on a machine. You must not run two or more protocol software
products simultaneously on the same machine.
Warning! If you change stacks at any time, you must reinstall Unicenter Data
Transport!
Pre-Installation Information
The Client Agent for OpenVMS is provided on the CD in ISO9660 format, which
can be read across multiple platforms. To mount the CD, use a standard
OpenVMS mount command, such as:
mount /over=id device
where device is the CD-ROM device. The installation files are organized as two
setup executables, one for VAX and one for ALPHA, and an archive file that
contains the Client agent for OpenVMS components.
It is strongly recommended that you back up your OpenVMS system disk before
installing the Client Agent for OpenVMS. The area in which you run the setup
file must have at least 10 blocks of free space. The setup procedure verifies that
the temporary area is large enough before starting the actual product install. The
space is required to extract the setup command file. The file is deleted when the
installation is complete.
212
The install script prompts you to supply a location for the temporary storage
area required to unzip the installation files, 80000 blocks of temporary space is
needed.
Installation
Verification
Procedure (IVP)
You are prompted whether or not to run the Installation Verification Procedure
(IVP), which checks to see if the installation was successful. It is recommended
that you choose Yes. If you choose Yes, after the installation process is finished,
the IVP will validate. If the test is successful, the installation completes
successfully. If the test fails, the installation aborts, and you should try
installing again. If the problem persists, consult your systems administrator or
contact Computer Associates Technical Support.
Important! Ensure that SYSUAF is defined and pointing to the correct security file on
the system.
Purge File You are asked whether you would like to purge the files that were replaced by
the installation. It is recommended that you choose Yes. Choosing No leaves
old versions of the files on your system.
For Previous
Installations
The installation procedure checks to see if BrightStor enterprise Backup Client
Agent for OpenVMS was previously installed on this machine. If it was, the
default location is the location of the previous installation. It is recommended
that you continue to use this location for the new installation.
For New Installations If BrightStor Enterprise Backup Client Agent for OpenVMS was not previously
installed on this machine, the default installation location is:
SYS$SYSDEVICE:[ASO$AGENT]. If you want to change the installation
location, enter the new location when prompted.
Important! If you are installing on a cluster that has mixed version, mixed
architectures, or uses different IP stacks in the cluster, you must install on
SYS$SPECIFIC.
You can either accept the default location or specify an alternate location. The
install script checks to see if the location you choose has sufficient disk space. If
the disk space is sufficient, the install script extracts the save-sets from the
archive; otherwise, the installation asks you to specify an alternate location, until
you specify a location that has sufficient space. If the installation aborts, free
enough disk space to meet the requirements noted and then start the installation
again.
The installation procedure checks for the TCP/IP files required on this machine.
Depending upon which TCP/IP software is installed, you may receive error
messages stating that a file could not be found. You may safely ignore these
messages, unless one or more of the required TCP/IP stacks is not running on
this machine. In this case, the installation will abort. The messages will tell you
which stack is running.
If the installation aborts for that reason, make sure that one of the required
TCP/IP stacks is installed and running on the machine. You may then continue
to do the installation.
The install script runs a registry check to determine what version, if any, of
BrightStor Enterprise Backup Client Agent for OpenVMS was previously
installed on this machine. You are warned that the version you are attempting to
install is newer, older, or the same as the version currently installed on the
system. You are prompted whether or not to continue the installation.
Important! If you decided to abort the installation at this point, please remember to
restart BrightStor Enterprise Backup Client Agent for OpenVMS by entering the
following command at a DCL prompt: @sys$startup:beb$startup
When the installation completes, a message is generated indicating that the
installation has successfully completed.
If you chose to run the Installation Verification Procedure when you were
prompted earlier during the installation process, the procedure will run at this
time. Follow the output for any potential errors.
214
The installation instructions for installing the Client Agent on the OpenVMS
Agents.

Click Client Agents for OpenVMS installation instructions, as shown:

This launches your web browser where you can view the HTML file that
contains additional information you need to install the Client Agent for Open
VMS.

216
Configuring the Client Agent
This section describes the procedures for configuring the various Client Agents.
Any known issues (if applicable) of which you should be aware are described as
well.
Configurations for the Client Agent(s) begin from the BrightStor Backup Agent
Admin screen, shown below.

Configuring the Client Agent for Windows
To configure the Windows Client Agent machine, in the BrightStor Backup
Agent Admin dialog, select Options, then Configuration. The following screen
appears:

Note: The screen may appear slightly different for each client, depending upon
the platform used.
Configuration allows you to configure the agent service, and provides the
following configuration options:
System SecurityUses Windows security to perform Backup, Compare, and
Restore operations. The agent impersonates the logged-on user. When you
specify the account to use, it may be necessary to distinguish between two
accounts with the same name (such as Administrator) by indicating where
Windows can find this account. To do this, specify the domain or machine
the account is part of as:
domain_name\user_name or machine_name\user_name
For example, for a domain named NTDEV containing a workstation named
ENGINEER, the respective administrators are:
NTDEV\Administrator
ENGINEER\Administrator
Password SecurityYou can set individual passwords for security. This
allows the Client Agent to run under the local system account. By default,
Password Security is disabled.
218
Backup/Restore/Compare PriorityDetermines the priority given to the
processes needed for the Backup, Copy, or Compare operation:
HighForeground processing performs Agent functions before other
processes.
NormalStandard processing performs Agent functions without special
status.
LowStandard processing performs Agent functions when other
processes are idle.
Pre/Post execution programsEnter the name of any batch programs (for
example, C:\WINAGENT\PRE.CMD) that you want to automatically
execute before or after the Backup or Restore operation:
Pre-executionRun a batch program before the job.
Post-executionRun a batch program after the job is completed.
Execution DelayPeriod of time the Agent waits before or after the job
and the execution of the batch job.
Important! The configuration options you select are saved once you click OK. If you
want to change your options later, then you must go back to the Configuration screen.
You can also view your configuration selections in the BrightStor Backup Agent
Admin window by simply clicking the plus (+) sign next to Options, and then
clicking on Configuration.

Once you select the configuration options, configure a port number and IP
address. In the BrightStor Backup Agent Admin window, select Options, then
Network Configuration. The Backup Agent Admin screen opens:

Specify Port NumberAccept the defaults, or enter the port values you
want the Backup Agent to use.
Virtual Interface (VI) ProtocolIf you want to use Virtual Interface Protocol
for Backups and Restores, select Enable VI support. Selecting this enables
faster remote Backups and Restores. Note: This option is for Windows NT,
2000, XP, and XP 64-Bit Edition clients only, and you must use a NIC card
that supports VI.
Select IP AddressThe Agent supports the use of multiple Network
Interface Cards (NICs). For machines with more than one network card, the
Agent listens to all enabled NIC cards in the system. You can manually
override this selection by entering a new IP address of the NIC card that you
want to dedicate for backup purposes. Once this is done, the Agent will
listen using only this NIC card. All other NIC cards will be ignored and you
will not be able to use their IP addresses to connect to the Agent. Note: This
option is for Windows NT, 2000, XP, and XP 64-Bit Edition clients only.
Note: If you use the Agent to perform the remote client Backups and Restores,
the password set for the Agent overrides any sharing password set for the
workstation. If you do not use the Agent for the BrightStor Enterprise Backup
jobs, you are prompted for the sharing passwords on the BrightStor Enterprise
Backup Manager. Make sure that the password on the BrightStor Enterprise
Backup Manager and the share level password both match.
220
Setting a Workstation Password
If you specified a password for the client workstation (through the Agent
Preferences screen), you must specify the password in BrightStor Enterprise
Backup as follows:
1. From the Browser, right-click on the client.
2. Select Security from the pop-up menu. The Security dialog opens.
3. Enter the password and click OK.
Functions of the Client Agent for Windows
The following lists the functions of the Client Agent for Windows:
Data Compression SupportThe Client Agent for Windows supports
compression. When this option is selected from BrightStor Enterprise
Backup, data packets are compressed during transport through the network.
Data Encryption SupportData packets transported during a BrightStor
Enterprise Backup job can be encrypted. This option ensures that transported
or archived data is secured with a password.
Auto-Discovery of Client AgentBrightStor Enterprise Backup allows you
to auto-discover all machines running the Client Agent. This allows you to
build the list of machines in the Windows Systems tree automatically.
Use the following procedure to add the Client Agents:
1. In the Backup Manager, right-click Windows Systems.
2. Select Add Using Auto-Discovery from the pop-up menu.
3. The Agent Select dialog opens. In the dialog, select the Agent you want
to add, and click Add.
4. Click Close.
Multi-stream Restore and CompareThe Client Agent for Windows
supports multi-streaming operations. See the section Registry Settings for
information on enabling this option.
Computer Name Resolution SupportThe following describes the steps for
computer name resolution support for the Client Agent:
In the Preferred Shares/Machines tree or Network tree, right-click the
machine name in the Backup Manager. Select the Use Agent option from
the menu and select Use Computer Name Resolution. BrightStor
Enterprise Backup automatically enters 0.0.0.0 for the TCP/IP address.
In the Windows Systems tree, right-click Windows Systems. Select the
Add Object option from the menu and select Use Computer Name
Resolution. BrightStor Enterprise Backup automatically enters 0.0.0.0 for
the TCP/IP address.
Security OptionsThe following list describes the security options available
for the Client Agent:
When using the Client Agent Password Security, enter the password at
the node level. In the Backup Manager, right-click the machine name.
Select Security from the menu and enter the password you specified for
the Client Agent.
When using System Security, the Client Agent service uses the user
name and the password to log on. This user should be a valid user in the
local workstation users database or in the domain database, if the
workstation is a member of a domain.
When entering password security on the Backup Manager, enter
information in the Username field to make the Password field accessible.
Support for Registry Backup in Detail ModeDetail mode allows registry
keys and values to be captured to media and, in the BrightStor Enterprise
Backup database, to provide a much more granular level of Backup and
Restore than registry hive level. This enables selective Backup and Restore of
the registry.
By default, when the entire machine is selected for backup, the Client Agent
for Windows does NOT backup registry in detail mode. See the Registry
Settings section for more information on enabling this option.
Virus Scanning SupportIntegrated agent level virus scanning is now
supported by the Client Agent for Windows.
Customizable Local OptionsWhen you explicitly select a parent object,
you can right-click an agent to customize local backup agent options. See the
Packaging Your Jobs section in Chapter 1 of the Windows part of the
BrightStor Enterprise Backup Getting Started guide for more information on
explicit job packaging. For more information on how to select sources when
customizing local options, see the Local Options section in Chapter 3 of the
BrightStor Enterprise Backup Administrator Guide for Windows.
Agent Log File DeletionYou can delete agent log files from the Client
Agent for Windows Admin window. Click the Garbage Bin icon on the
toolbar to open a window with a list of agent log files. To select the agent
logs to delete, click the check box on the right side.
Access Control ListYou can limit the servers authorized to back up using
the Client Agent for Windows. Select this feature by clicking on the
Computer icon on the toolbar, and then click the Add button to add a server
to the list. For more information, see the section Access Control List (ACL)
for Client Agents.
222
Known Configuration Issues for the Client Agent for Windows
General information pertaining to the configuration of the Client Agent for
Windows:
Restoring System StateThe System State supports the Restore to Original
Location option only. If another location is selected, the System State is still
restored to the original location.
When restoring the System State to its original place, the error message
Time out, all active Compare processes will be terminated, is generated at
the end of the job. However, the job is completed successfully.
Shares supportShares, other than administrator shares for agent backups,
are not supported. To back up shares, you should back up the directory level.
Restoration of the System hiveThe Client Agent protects sensitive system
registry keys during a regular restore of the System hive, using the feature
KeysNotToRestore.
Note: This feature is not currently supported if you restore individual
system keys from a Client Agent Registry session.
Registry Settings
The Client Agent for Windows allows you to customize the product by adding or
modifying settings in the Windows Registry. While some common settings can
be set using the Client Agent for Windows Admin, additional settings can be set
using the Windows REGEDT32 utility. The Client Agent settings are listed in the
HKEY_LOCAL_MACHINE window under the following key:
SOFTWARE\ComputerAssociates\BrightStor Enterprise Backup\ClientAgent\Parameters
The following lists the descriptions of the various registry settings:

Registry Setting Description
AsyncBufferNumbers Sets the number of buffers used for
asynchronized I/O operations. The value can
range from 2 to 32. Each buffer size is the same
as FileBufferSize. If UseAsyncIO is FALSE,
this value has no effect. The default is 4.
AsyncMinimumFileSize Sets the file size threshold of the files that can
use asynchronized I/O operations. If the file
size is greater than or equal to this value, the
file is backed up using the asynchronized I/O
method. If UseAsyncIO is FALSE, this value
has no effect. The default is 1024 (KB).
BackUpRegistryAsVal To enable detail mode registry, set the
following:
BackUpRegistryAsVal:REG_DWORD:1 (TRUE)
The default is 0 (FALSE).
Note: This applies only when the entire
machine is selected at the machine level.
FileBufferSize Size of buffers for file read operations. The
default is 512 (KB).
MaxBufferSendDaemonHigh Maximum size of the buffer on which data is
stored before being sent to the BrightStor
Enterprise Backup server. The default is 32768
(KB).
NoBufferingFileSize Sets the file size threshold that determines
whether the No Buffering option is enabled. If
the file size is smaller than the setting, the
option is not enabled. The default is 1 (KB).
224
ReceiveTimeOut The length of time (in seconds) after which the
Client Agent for Windows times out if it has
not received any data packets from BrightStor
Enterprise Backup within the specified amount
of time.
The default is 1200 seconds (20 minutes).
Note: If 0 is entered as a value, the Client
Agent for Windows never times out.
ResetFileAccessTime To prevent BACKUP from resetting the date
and time the file was last accessed each time a
file is backed up, set the following:
ResetAccessTime:REG_DWORD:1 (TRUE)
Note: If the drive is enabled to use the Data
Migration Option, this value is set to 0.
SendTimeOut The length of time (in seconds) after which the
Client Agent for Windows times out if it has
not sent any data packets to BrightStor
Enterprise Backup within the specified amount
of time.
The default is 1200 seconds (20 minutes).
Note: If 0 is entered as a value, the Client
Agent for Windows never times out.
SingleRestoreOrCompare To disable multi-stream Restores and
Compares (more than one Restore or Compare
operation at a time), set the following:
SingleRestoreOrCompare:REG_DWORD:1 (TRUE)
The default is 1 (TRUE).
SkipMigratedFiles To prevent BACKUP from backing up files that
were migrated, set the following:
SkipMigratedFiles:REG_DWORD:1 (TRUE)
UseAsyncIO To disable asynchronized I/O operations
during Backup, set the following:
UseAsyncIO:REG_DWORD:0 (FALSE)
We recommend that you enable it for high-end
machines. The default is 1 (TRUE).
UseSnapshots Volume Shadow Copy Service (VSS) feature.
This is currently for a Windows XP or
Windows XP 64-Bit Edition machine only. The
default value is set to 1, indicating that
Snapshot is enabled. To disable Snapshot, set
the value to 0.

226
Configuring the Client Agent for NetWare
To configure the Client Agent for NetWare, you need to edit the ASCONFIG.INI
file. The agent allows a BrightStor Enterprise Backup administrator to assign the
IP address that agent will use. This feature is especially useful in a server with
multiple IP addresses, where before only the first bound address was used. The
agent uses the ASCONFIG.INI file to find the IP address to use.
Follow these steps to edit the ASCONFIG.INI file:
1. From a text editor, open the ASCONFIG.INI file in the agent home directory.
2. Add the following line to the NetWare Agent section of the file:
IPAddress = xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the IP address that you want the Client Agent to
use.
If a NetWare Agent section does not exist, create one by adding the line
[NetWare Agent] at the end of the ASCONFIG.INI file.
3. Save the file and exit from the editor.
4. Unload and restart the Client Agent. Unloading is necessary for your
changes to the ASCONFIG.INI file to take effect.
To unload the Client Agent, use the Agent menu option, Unload and Exit or
at the server console type:
unload nwagent
Once the Client Agent is unloaded, start the Client Agent at the server
prompt by typing:
nwagent
5. A message appears at the server prompt, confirming the use of the specified
IP address:
IP Address xxx.xxx.xxx.xxx from ASCONFIG.INI file will be used.
A similar message is displayed on the Agent Runtime message screen:
IP Address xxx.xxx.xxx.xxx is bound for use by NetWare Push Agent.
The agent is now ready to service backup jobs using the IP address specified in
the ASCONFIG.INI file.
Backing Up Novell Directory Services (NDS)
The full NDS name must be given when entering the NDS Login name
information, to properly back up the NDS. For example:
.cn=admin.o=organization_name
When restoring any NetWare sessions, you must supply the full NDS name
when prompted for security information.
Known Configuration Issues for the Client Agent for NetWare
configuring the Client Agent on the NetWare platform.
Multiple jobs are not supportedThe Client Agent for NetWare can service
only one job at a time. Trying to submit jobs to the Agent from multiple
BrightStor Enterprise Backup servers at the same time may cause the current
job to fail.
Restoring to NSS volumesRestoring compressed files backed up from
non-NSS volumes to NSS volumes is not supported. These jobs result in
errors during the Restore operation.
Restoring space restrictions to NSS volumes from directories backed up from
non-NSS volumes is not supported. The space restrictions are not restored to
NSS, but the directory and files are restored.
Open files skipped during backupWhen backing up NetWare files using
the Client Agent for NetWare, in some cases multiple files are detected as
open and are skipped during the backup. Should this happen, select the
Retry tab in the Backup Options dialog. In the File Sharing section, select the
Use Lock Mode if Deny Write Fails option and resubmit the job.
255-character path limitNetWare has a 255-character path limit (for
example, DIR1\DIR2\DIRx, where the total size of the path can be up to
255 characters only). This does not apply to other platforms, such as
Windows or UNIX. The Client Agents running on these platforms can
support longer paths. Therefore, backup and restore operations work
properly, but the browsing of larger path entries in the database is truncated.
You cannot browse more than 255 characters deep in the Restore Manager.
However, the Restore to Original or Alternate Location options still work, if
you have the same type of agents.

228
Configuring the Client Agent for UNIX/Linux
The UNIX/Linux Client Agent configuration file, uag.cfg, is located on the
remote client workstation in the $UAG_HOME directory. This file (which is
scanned for entries whenever a job is submitted to the workstation) can be
utilized to set multiple options associated with the Agent.
Important: Do not change any of the variables within the agent modules configuration
file, unless instructed to do so by a member of Computer Associates Technical Support.
Options are available only when used along with the Client Agents
configuration file, uag.cfg. When specifying options within this file, each option
should be listed on its own line.
Note: Any options that are set from the front-end through the BrightStor
Enterprise Backup Manager take precedence over the options set in the
configuration file.
An example of the uag.cfg file is shown below:
# ===============================================================================
# "uag.cfg": the File System Agent configuration file. This configuration # file
should be in agent's home directory. This file (which is scanned # for entries
whenever a job is submitted) can be utilized to set # multiple options associated
with the File System Agent. Options # entered # at job submission will take
precedence over options entered # in this file.
#
# Example of some of the options that can be set in this file are
#
# -b <bufsize> Disk I/O buffer size in bytes
# -f follow symbolic links
# -S Single user mode option
# -ALLOW Defines IP addresses that are allowed to
# access this agent
# -DENY Defines IP addresses that are denied access
# to this agent
# -s SocketMode use sockets even for local backups
# (local backups use shared memory by default)
# -Prebackup <filename> Execute <filename> script pre backup
# default name is uag_pre_backup
# -Postbackup <filename> Execute <filename> script post backup
# default name is uag_post_backup
#
# -P <n> Specify time-out for the pre-script
#
# When specified options within this file, each option should be
# listed on its own line. For example
#
# -s 65536
# -b 8192
# -m 128
# -s SocketMode
# -v
# ===============================================================================

-b 65536
-c 50
Options for the Client Agent for UNIX/Linux
Options are used to optimize and customize the operation of the UNIX/Linux
Client Agent. They are not required in order for the UNIX/Linux Client Agent to
run and should be used with caution. A complete list of options available for use
when starting the UNIX/Linux Client Agent is shown in the table below:

Option Description
-b <bufsize> Disk I/O buffer size in bytes. (16384 to 65536) Default [16384]
-c <n> Sleep n milliseconds while waiting. (0 to 1000) Default [0]
-S Single User Mode option.
-CAUSER USER Sets the ALLOW/DENY list per BrightStor Enterprise Backup username.
For example:
-BrightStor Enterprise Backup_USER A:BrightStor Enterprise Backup_USER1
N:BrightStor Enterprise Backup_USER2
where A corresponds to -ALLOW and N corresponds to -DENY.
Note: This option is used with Single User Mode along with the -S or
-NOPASSWORD option.
-ALLOW Defines the IP Addresses that are allowed the access to the agents.
For example: ALLOW N:192.35.100.0(255.255.255.0) H:141.1.100.10
where N denotes a network address and H denotes a hosts IP Address. An
optional subnet mask can be set.
Note: This option is used with Single User Mode along with the -S or
-NOPASSWORD option.
-s <async|nonblocking> Set socket I/O to asynchronous/nonblocking mode
-s SocketMode Use socket mode for backup
-s <bufsiz> Socket buffer size option. Specifies the size of the socket buffer. (4096 to
65536) Default [system dependent]
-l Causes the agent to check for advisory locks. Default [mandatory locks
only]
-m <maxbuf> Number of buffers allocated for I/O. (2 to 1024) Default [128]
-NOPASSWORD Enables the -ALLOW, -DENY, and -CAUSER options to be used. Same as
the -S option where no password is required in Single User Mode.
-v Enables detailed debugging messages to the console (Verbose mode).
230
Option Description
-DENY Host or Network IP Address Deny list. The DENY option defines the IP
Addresses that are not allowed access to the agents.
For example: -DENY N:.35.100.0(255.255.255.0) H:141.1.100.10
Where N denotes a network address (an optional subnet mask can be set)
and H denotes a hosts IP Address.
Note: This option is used with Single User Mode along with the S or
-NOPASSWORD option.
-P <n>

Specify the default time-out, followed by a variable number <n>, which is
user defined and measured in minutes (0 to 10). Default [5]
For example: The option -P 10 assigns a wait time period for the pre-script
(backup or restore) of 10 minutes.
Note: If the -P option is used but <n> is not specified, an error occurs.
-sparse Sparse file operation. The sparse option causes BrightStor Enterprise
Backup to differentiate between sparse file and regular file operations. It
increases the efficiency of sparse file backups and restores.
Note: Quota files are always treated as sparse files in backup and restore
operations, regardless of whether the sparse option is specified.
-Prebackup <filename>
-Postbackup <filename>
-Prerestore <filename>
-Postrestore <filename>
To execute the default pre/post-scripts associated with the type of job being
run (backup or restore). The default script associated with each option is
listed below:
-Prebackup = uag_pre_backup
-Postbackup = uag_post_backup
-Prerestore = uag_pre_restore
-Postrestore = uag_post_restore
To substitute a specific default pre/post-script with one that is user defined,
you must specify its corresponding option, followed by the new script
name:
uagent -Prebackup <AAA> -P <10>
In this example, the user-defined pre-script AAA would be substituted for the
default backup script with a wait time of 10 minutes.
When creating a user-defined pre/post-script, the contents should conform
to the Bourne Shell syntax. If no parent path is specified, all scripts are
relative to $UAG_HOME. Otherwise you are required to list the full path
name. All options specified remain in effect until the Client Agent program
is stopped and then restarted.
UNIX/Linux File System Agent Control Files
The UNIX/Linux File System Agent control files provide a means of specifying
which directories, file systems, or file system types will be excluded from backup
operations on a particular workstation. There are two packages that must be
installed for the UNIX/Linux File System AgentCA Uagent and CA Common
Agent. The CA Common Agent must be installed prior to the CA Uagent. The
control files installed for both packages are described below.
The Directory Control file, uag.cntl, and the File System Control file, fs.cntl, exist
for each UNIX/Linux workstation running the Agent. Both files are stored on the
Agent workstation in the <uagenthome> directory.
Note: Only the System Administrator can edit Agent control files. However,
other users may be able to append the files, depending on the file access rights
the System Administrator has assigned to the file.

Directory Control file The Directory Control file, uag.cntl, should list all directories or file systems (or
both) to exclude from backup operations on that workstation. The syntax for
specifying directories and file systems within this file, are a one-line, complete
path name, beginning with a slash (/). For example: /opt/account1
File System Control file The File System Control file, fs.cntl, lists the file system types on that
workstation to exclude from backup operations. Excluding a particular file
system type is accomplished by listing the file system type on its own line.
Browser
Configuration File
The Browser Configuration file, cabr.cfg, enables raw devices to be viewed within
the browser once the absolute name of the raw device is entered on its own line
within the cabr.cfg file.
Global
Configuration File
The global configuration file, agent.cfg, keeps track of each agent installed on
your system. This file is located in the /opt/CA/BEBcmagt directory, and
receives the agent information when the uagentsetup script is run. This script is
run automatically after the uagent is installed.
Structure of the
agent.cfg File
Each grouping of fields directly corresponds to an installed agent. All fields are
pre-determined with the exception of the agent home directory, which is set
when configuring the agent. If required, the environment variable field will be
determined during installation and configuration of the agent.
Saving Modifications
to the agent.cfg File
Variables may be entered into the file manually, such as an additional
environment field associated with a particular database. For modifications
made to the agent.cfg file to take effect, you must stop and then restart the
CAagent from the command line.
232
<uagenthome> denotes the directory under which the UNIX File System Agent
is installed. The default directory for this is /opt/CA/BEBuagent, however, you
can specify a different directory. You can find <uagenthome> by looking at the
agent.cfg file under the Common Agent installation directory
/opt/CA/BEBcmagt. In earlier versions of BrightStor Enterprise Backup, the
fixed installation directory for the Common Agent was /usr/CAagent. In the
agent.cfg file, look under the BEBagntux section for the HOME variable (which
contains the uagent home directory information).
An example of the agent.cfg file is shown below, accompanied by a description of
each sub-agent field. HOME denotes the uagent home directory.

File Contents Field Description

[0]
Object typepre-defined number of a specific
agent
NAME agntux
Name of the agent
VERSION nn.n
Version number of the agent
HOME
/opt/CA/BEBuagent
Home directory for the agent
#ENV
CA_ENV_DEBUG_LEVEL=2
Environment variables passed to the agent
BROWSER cabr
Browser module for the agent
AGENT uagentd
Backup module for the agent daemon
MERGE umrgd
Merge daemon
VERIFY umrgd
Scan daemon
BrightStor Enterprise Backup Common Agent for UNIX
The BrightStor Enterprise Backup Common Agent is a common component for
all UNIX Database Agents and File System Agents. It is installed automatically
during the first installation of any of the Database Agents or File System Agents.
It is installed in the /opt/CA/BEBcmagt directory. Earlier versions of BrightStor
Enterprise Backup installed this component in the /usr/CAagent directory. The
Common Agent uses a configuration file, agent.cfg, which resides in its
installation directory to keep track of the agents that are installed on the system.
During the installation of a new Database or File System Agent, this agent.cfg file
is updated with the new Database or File System Agents information. You will
seldom need to modify this configuration file. Manual modification of this file is
required only to enable some debugging messages, or to change the default
TCP/IP port on which the Common Agent runs.
A sample agent.cfg file with a File System Agent installed is shown below.
[0]
#[BEBagntux]
NAME BEBagntux
VERSION 10.5
HOME /opt/CA/BEBuagent
ENV CA_ENV_DEBUG_LEVEL=4:$CA_ENV_DEBUG_LEVEL
ENV LD_LIBRARY_PATH=/opt/CA/CAlib:/opt/CA/BEBcmagt:$LD_LIBRARY_PATH
ENV SHLIB_PATH=/opt/CA/CAlib:/opt/CA/BEBcmagt:$SHLIB_PATH
ENV LIBPATH=/opt/CA/CAlib:/opt/CA/BEBcmagt:$LIBPATH
BROWSER cabr
AGENT uagentd
MERGE umrgd
VERIFY umrgd

[36] DISABLED
#[BEBcmagt]
#NAME BEBcmagt
#HOME /opt/CA/BEBcmagt
#TCP_PORT 6051
#UDP_PORT 6051
When Database Agents are installed, there will be separate sections similar to
those shown in the above example.
Common Agent
Components
The Common Agent (caagentd binary) runs all the time as a daemon listening for
requests on behalf of all the agents that are installed on the system. During each
agents installation, the BROWSER/BACKUP/RESTORE/
BROWSER/MERGE/VERIFY components are registered with the Common
Agent in a separate section. Not all agents may have all these components. For
example, in the above sample configuration file, you can see the BROWSER
component cabr, the BACKUP/RESTORE component uagentd, and the
MERGE/VERIFY component umrgd, for the section of the UNIX File System
Agent. Similarly, there are BROWSER/AGENT components for other Database
Agents.
Connecting to the
Common Agent
Whenever a request comes in for a particular agent and for a particular
component, the Common Agent first accepts the connection, and then verifies the
users credentials for the system. Upon validating the user, it checks the
configuration file for the required agent and its component, and then launches
that particular component. Common Agent then passes the connection that was
established to the newly created component so that it can communicate with the
BrightStor Enterprise Backup Server that is initiating the request. Then the
Common Agent returns to a state of waiting for additional requests.
234
Starting and Stopping
the Common Agent
Whenever an agent (File System or Database) is started or stopped, its
corresponding section in the agent.cfg file is marked as ENABLED/DISABLED.
For example, uagent stop for a UNIX File System Agent marks the BEBagntux
section above as DISABLED. Because there are no other sections that are enabled
in the configuration file (because there are no other agents installed on this
system), the Common Agent is stopped. uagent start removes DISABLED from
the corresponding section, and instead it is marked as ENABLED. In summary,
when a particular agent is started or stopped, the scripts modify the agent.cfg file
accordingly, and notify the Common Agent. Then the Common Agent decides
whether to continue running or not, depending upon the number of sections that
are still enabled in the configuration file.
Common Agent Port
Numbers
By default, the Common Agent uses port number 6051 for both TCP and UDP.
To change the default port, you need to modify the BEBcmagt section above with
the new port numbers, and then restart the Common Agent using caagent stop
and then caagent start. Under normal conditions, this method should not be
used to start or stop the Common Agentinstead you should run the start/stop
scripts of the individual agents installed on the system which handles starting
and stopping of Common Agents.
Here is a sample of the configuration file, before and after these changes are
made:
Before the change:
[36] DISABLED
#[BEBcmagt]
#NAME BEBcmagt
#HOME /opt/CA/BEBcmagt
#TCP_PORT 6051
#UDP_PORT 6051
After the change:
[36]
#[BEBcmagt]
NAME BEBcmagt
HOME /opt/CA/BEBcmagt
TCP_PORT 9051
UDP_PORT 9051
The new port changes take effect only after restarting the Common Agent. If you
configure the Common Agent to run on a non-default port, you should also
configure the BrightStor Enterprise Backup server to access this agent. You can
do this by making an entry for this agent in the port.cfg file (this file is in
$BEB_HOME/config/on the BrightStor Enterprise Backup server where
BEB_HOME is the BrightStor Installation directory on the server).
The Common Agent uses another UDP port, 0xA234 (41524), to receive Windows
BrightStor Enterprise Backup Manager broadcast requests for auto-discovery of
UNIX agents. To auto-discover a UNIX agent by the Windows BrightStor
Enterprise Backup Manager, the Common Agent on the UNIX machine must be
up and running, and listening for the broadcast request on port number 0xA234.
User Access While checking the user credentials, the Common Agent gives preference to host
equivalence settings of the system. A UNIX system can be set up to allow access
for specific users from specific hosts without providing any credentials by
adding entries in /etc/hosts.equiv or .rhosts file. The Common Agent follows these
rules, and then checks the password of the user. The Common Agent can be put
in No Password or Single User Mode with a set of Access Control Lists if
necessary. See the ACL for the Client Agent for UNIX/Linux section for more
details.
Log Messages All the log messages relating to the Common Agent are found in the
/opt/CA/BEBcmagt/logs/caagentd.log file.
Using the Snapshot or DirectIO Feature
Before you can take advantage of a Snapshot backup or a DirectIO backup and
restore, ensure that one of the following environments exist on the client (file
system agent) machine:
Snapshot Supported
Platforms
In Solaris with:
Advanced version of VxFS file system installed on either Solaris 7, 8, or 9
UFS file system with the fssnap package installed on either Solaris 8 or 9
In HP-UX 11.0 with:
DirectIO Supported
Platforms
In Solaris with:
Advanced version of VxFS file system or UFS file system on either Solaris 7,
8, or 9
In HP-UX 11.0 with:
236
To take a Snapshot backup or a DirectIO backup or restore (or both), follow these
steps:
1. Enable the environment variable by editing the agent.cfg file that exists in the
/opt/CA/BEBcmagt directory. The environment variable is
CAAGPERF_ENABLE. Add the following line in the agent.cfg file:
ENV CAAGPERF_ENABLE=1
After you enable the above environment variable, the file system agent
portion of the agent.cfg file looks like this:
[0]
NAME BEBagentux
VERSION X.X
HOME /opt/uagent
ENV LD_LIBRARY_PATH=/usr/local/Calib:/usr/CAagen
ENV CAAGPERF_ENABLE=1

2. Prepare the configuration file named caagperf.cfg in the /opt/CA/BEBcmagt
directory. You need to specify the type(s) of operation(s) to be completed on
the specified file systems in the caagperf.cfg file. The format of the
configuration file is similar to a Windows .inf file. It has sections and key
value pairs. The section names are the names inside the square brackets and
key value pairs are in KEY=VALUE format with one pair on each line. All the
entries in the configuration file are case sensitive. The key value pairs are under
the volumes to which they belong, and the section names are the names of
those volumes. So, the section name can be like [/], [/export/home] and so
on. If there are multiple entries for the same volume the behavior of the
agent is undefined. The key value pairs are used to set parameters for the
volume under which they belong. By default, all options are disabled. If no
special processing is needed for a volume, that volume should not be in this
file. On the next page, the keys and their values are described.

Key Value
DOSNAP Used to enable Snapshot in a volume.
The value should be BACKUP,
meaning that a Snapshot should be
taken during the backup operation.
SNAPSHOTBUFFER The buffer is used for storing original
data before it is overwritten in the
snapped volume. The value should be a
file name or partition. The file may be a
file or a directory from a different
volume. The value does depend on the
file system type. For the Advanced
version of VxFS or Online JFS, the
value is the name of an empty
partition. For UFS, the value is a file
name, a directory name, or a partition
name.
DOUBIO Used to enable DirectIO in a volume.
The possible values are BACKUP,
RESTORE, or BACKUP_RESTORE.
You can use any of these values
depending upon your requirements.
Configuration File Examples for Snapshot and DirectIO
The following are some examples of configuration files that you may find useful.
Example 1 This is a sample /opt/CA/BEBcmagt/caagperf.cfg file for a Solaris 8 or Solaris 9
operating system with a UFS file system and fssnap installed. This file contains
three sections. The first line contains a debugging flag that enables debugging.
Sections mentioned in this file are /opt, /export/home and / volumes. Sections
for /opt and /export/home have Snapshot enabled during backup, and the /
volume has DirectIO enabled for backup and restore.
##DEBUG
[/opt]
DOSNAP=BACKUP
SNAPSHOTBUFFER=/garbage/snapbufferfile_1

[/export/home]
DOSNAP=BACKUP
SNAPSHOTBUFFER=/garbage/snapbufferfile_2

[/]
DOUBIO=BACKUP_RESTORE
238
Example 2 This is a sample /opt/CA/BEBcmagt/caagperf.cfg file for a Solaris 8 operating system
with Advanced version of VxFS file system installed. This file contains three
sections. The first line contains a debugging flag that enables debugging. Sections
mentioned in this file are /opt, /export/home and / volumes. Sections for /opt
and /export/home have Snapshot enabled during backup, and the / volume has
DirectIO enabled for backup and restore.
##DEBUG
[/opt]
DOSNAP=BACKUP
SNAPSHOTBUFFER=/dev/dsk/c0t0d0s4

[/export/home]
DOSNAP=BACKUP
SNAPSHOTBUFFER=/dev/dsk/c0t0d0s4

[/]
Example 3 This is a sample configuration file for the HP-UX 11.0 operating system that can
have either Advanced version of VxFS file system or Online JFS file system
installed. This file contains four sections. The first line contains a debugging flag
which enables debugging. Sections mentioned in this file are /, /var, /usr and
/export volumes. In this file the / volume is enabled for DirectIO during backup
and restore, and rest of the volumes are enabled for Snapshot during backup.
##DEBUG
[/]

[/var]
DOSNAP=BACKUP
SNAPSHOTBUFFER=/dev/vg00/lvol7

[/usr]
DOSNAP=BACKUP

[/export]
DOSNAP=BACKUP
Known Configuration Issues for the Client Agent for UNIX/Linux
configuring the Client Agent on the UNIX/Linux platform.
Session passwordsSession passwords cannot be longer than 22 bytes for
UNIX/Linux sessions.
Single character directory namesYou may experience display issues in
restore views when restoring single character directory names. The data
appears correctly in the database view.
Traverse Symbolic Links and Traverse NFSThe options Traverse
Symbolic Links and Traverse NFS are not supported for Restore operations.
We recommend that this option not be used at this time.
Configuring the Client Agent for AS/400
The Client Agent for AS/400 start and stop preferences are configured using
STRASO and ENDASO.
To configure start preferences for the Client Agent for AS/400, follow these
steps:
1. From the command line, type:
straso
2. Press F4. The options that you can choose appear on the configuration
screen.

3. Type your preferences and press Enter.
240
To configure stop preferences for the Client Agent for AS/400, follow these
steps:
1. From the command line, type:
endaso
2. Press F4. The options that you can choose appear on the configuration
screen.

3. Type your preferences and press Enter.
Configuring the Client Agent for OpenVMS
The Client Agent on OpenVMS does not require any additional configuration on
OpenVMS after installation.
Optimizing the TCP/IP Stack
The performance of the Client Agent is impacted by the configuration of the
TCP/IP stack. Typically the Send and Receive quotas for TCP are set to 4096. It is
recommended that these values be set to the largest value allowed by the specific
stack installed on the OpenVMS system.
Changing the Logging Levels
The Client Agent is implemented in such a way that agent activity can be logged
in detail. The following control the trace levels within the Client Agent:

Logical Description
ASO$TRACE This controls the trace depth of the
agent. Valid values are from 0 to
0xFFFFFFFF. Setting the ASO$TRACE
value to 1 logs the most detail.
ASO$TRACE_AST This is a toggle. If it is defined, ASTs
are traced.
ASO$TRACE_IDENT This is a formatting parameter. The
recommended value is between 0 and 5
(default is 3).
ASO$TRACE_DATA This controls the number of bytes of
each packet that is logged. The range is
anything from 0 and up (default is 300).
Note: Tracing levels will affect the backup performance. It is recommended that
these values only be set if requested to do so by Computer Associates Technical
Support.
General Client Agent Configuration Issues
The option Delete Files After Backup is not supported for agent backups.
242
Configuring the Port Address for the Client Agent
Configuring the Port Address for the Client Agent
The benefit of configuring the port addresses is to restrict access to specific ports,
particularly when a firewall is involved.
Note: This is applicable for the Windows, UNIX/Linux, and OpenVMS Client
Agents only.
Configuring the Port Address for the Client Agent for Windows
The Client Agent framework services are shared across all the configured agents.
The Client Agent by default listens to the port 6050 (TCP/UDP). You can change
this behavior by modifying the following line option in the Backup Agent Admin
menu:
Backup Agent Admin\Options\Network Configuration Menu
This information also needs to be modified in the CAPortConfig.cfg file, and
copied to the BrightStor Enterprise Backup home directory.
An example of the CAPortConfig.cfg file is shown below:
#Hostname IP address (optional) TCP port UDP port
#myhost xxx.xxx.xxx.xxx 6051 6051
mymachine 141.202.123.25 7090 7085
Configuring the Port Address for the Client Agent for UNIX/Linux
The default TCP port and UDP port are both 6051. The TCP port is used for
communication and data transfer between the cprocess and the agent. The UDP
port is used for the GUI to browse hosts. If you want to configure either the TCP
port, UDP port, or both, the configuration files (below) must be modified on both
the BrightStor Enterprise Backup server (port.cfg) and the agent (UNIX/Linux
backup, NT backup, and so on) side (agent.cfg). The values must match in order
for communication between the server and the agent to succeed.
An example of the port.cfg file is shown below:
#Hostname IP address (optional) TCP port UDP port
#myhost xxx.xxx.xxx.xxx 6051 6051
mymachine 141.202.123.25 7090 7085
An example of the agent.cfg file is shown below:
[36]
NAME CAagent
HOME /opt/CA/BEBcmagt
TCP_PORT 7090
UDP_PORT 7085
Access Control List (ACL) for Client Agents
Configuring the Port Address for the Client Agent for OpenVMS
The default TCP port and UDP port are both 6050. The TCP port is used for
communication and data transfer between the cprocess and the agent. The UDP
port is used for the GUI to browse hosts. If you want to configure the TCP
port/UDP port, the following command should be executed and added to the
beb$startup.com file:
DEFINE /SYSTEM ASO$PORT_NUMBER xxxx
where xxxx is the port number of the backup manager.
Note: OpenVMS requires that both the UDP and TCP ports be assigned the same
port number.
An access control list (ACL) for the Client Agent was addedthis allows you to
control which BrightStor Enterprise Backup server accesses the machine through
the agent.
By default, there is no include list or exclude list, so all of the BrightStor
Enterprise Backup servers are able to backup or restore data through the agent.
Note: This is applicable for the Windows and UNIX/Linux Client Agents only.
ACL for the Client Agent for Windows
By creating the ACL list and its type in the registry, only the BrightStor
Enterprise Backup servers allowed in the list are able to backup or restore data
through that agent. The ACL type can be:
0default, no ACL used
1include list
2exclude list
The Agent Administrator will provide a user interface to edit the ACL list. Each
agent has an ACL list.
244
ACL for the Client Agent for UNIX/Linux
For UNIX/Linux Client Agents, the ACLs are supported in Single User Mode
only. It is also known as No Password Mode. A UNIX/Linux File
System/Database agent can be put in Single User Mode by specifying a
NOPASSWORD entry in its corresponding section in the Common Agents
configuration file /opt/CA/BEBcmagt/agent.cfg. A UNIX/Linux File System Agent
can also be put in Single User Mode by specifying -S or -NOPASSWORD option
in the uag.cfg.
There are two types of Access Control Lists:
1. An Access Control List that denies or allows specific users to do Backup or
Restore. For example, a partial portion of the File System Agent section in
/opt/CA/BEBcmagt/agent.cfg is shown below. You need to make similar
changes for other agent sections if you want to apply ACLs to those agents as
well.
[0]
NAME BEBagentux
VERSION nn.n.n
HOME /opt/uagent
NOPASSWORD
CAUSER A:CAUSER1 N:CAUSER2
Where NOPASSWORD enables the Single User Mode, and CAUSER
specifies the users allowed or not allowed. In above example, A:CAUSER1
specifies to allow CAUSER1 to perform jobs and N:CAUSER2 specifies to
deny access to CAUSER2 (A equals ALLOW and N equals DENY).
2. An Access Control List that denies or allows jobs from specific IP addresses.
For example, a partial portion of the FileSystem Agent section in
/opt/CA/BEBcmagt/agent.cfg is shown below. You need to make similar
changes for other agent sections if you want to apply ACLs to those agents as
well.
[0]
NAME BEBagentux
VERSION nn.n.n
HOME /opt/uagent
NOPASSWORD
ALLOW N:192.35.100.0(255.255.255.0) H:141.1.100.10
DENY N:192.35.100.0(255.255.255.0) H:141.1.100.10
Where NOPASSWORD enables the Single User Mode and ALLOW/DENY
specifies whether or not a specific network or IP address is allowed to access
the system. In above example, N denotes a network address and H denotes a
hosts IP address. An optional SubNet mask can follow a Network address as
shown above, in parentheses.
For a UNIX/Linux File System Agent, the above ACLs can also be specified in
uag.cfg as well as using the -S, -NOPASSWORD, -CAUSER, -ALLOW -DENY
options. See the section in this chapter, Options for the UNIX/Linux Client
Agent for more details.
Getting Information from the Client Agent
The two types of ACLs can be applied concurrently. In both cases DENY takes
the precedence over ALLOW. In the Single User Mode, all operations on the File
System Agent are performed with Super User privileges. The
/opt/CA/BEBcmagt/logs/caagentd.log has information about the Users/IP/Network
addresses denied during Single User Mode.
This section describes the type of information that can be obtained by the various
Client Agents, and the procedures for obtaining this information.
The Runtime screen displays the real time statistics, or progress of the Backup
and Restore jobs that are being processed by the Client Agent.
Note: This does not apply to the UNIX/Linux, OpenVMS, or AS/400 Client
Agent.
Getting Information from the Client Agent for Windows
To open the Runtime screen, follow these steps:
1. From the Program menu, select the BrightStor Enterprise Backup Agent
program. The Agent Admin dialog opens.
2. Click on Connections.
3. The last 10 jobs processed are displayed. If the job is still active, you can click
on it to display the runtime statistics. If the job has completed, it displays
completed statistics for that job.
Note: The statistics are kept in memory, so if you close the Agent and the
Agent Admin, the connection statistics will be lost. You will, however, still
be able to view the results of the job in the activity log.
Getting Information from the Client Agent for NetWare
If the Runtime screen is not in view and you are running RCONSOLE.EXE to
view the Server Console, press the ALT and F3 keys simultaneously to switch
screens until you get to the Runtime screen. If you are at the Server Console, you
can press either ALT and ESC keys simultaneously to switch screens, or press
CTRL and ESC which displays a list of Current Screens from which you can
choose the Runtime message screen.
246
Client Agent Activity Log
The Activity Log displays information about the jobs that were processed by the
Client Agent. The following shows how to display the Activity Log for each
Client Agent.
Displaying the Activity Log for the Client Agent for Windows
Select the Activity Log tab from the Job Status Manager.
Displaying the Activity Log for the Client Agent for NetWare
The Client Agent for NetWare writes to the nwagent.log, which is created in the
Client Agent home directory. This can be viewed from Windows explorer by
opening up the file in the Client Agent home directory. Alternatively, you can
choose View NWAgent Log from the Client Agent console on the Server to
display the contents of the log file.
Displaying the Activity Log for the Client Agent for UNIX/Linux
As soon as the Client Agent begins running on a workstation, an activity log file,
uag.log is created and stored under the logs directory. This directory resides
under the workstations Agent home directory, $UAG_HOME/logs. This file
records all activities and errors that occur during workstation jobs.
Note: For each job and every subsequent startup of the Client Agent, a new
version of the aso$log file is created.
Displaying the Activity Log for the Client Agent for AS/400
The AS/400 Client Agent creates a Log file inside of the BrightStor Enterprise
Backup Library. The two file members are AGENT and ASBR.
File member AGENT records the activities and errors relating to agent
operations.
File member ASBR records information on BrightStor Enterprise Backup
browsing activities.
Adding Client Agent Objects
Displaying the Activity Log for the Client Agent for OpenVMS
As soon as the Agent begins running on the server, an activity log file,
aso$agent_<nodename>.log is created and is stored in the logs directory. When a
job is run, a job log file, aso$job.log, is created. The log directory resides in the
Agent home directory, which is defined by the logical aso$log:. The file content is
determined on the level of tracing enabled on the agent.
Note: For each job and every subsequent startup of the agent, a new version of
the aso$log file is created.
In order to back up or restore a workstation using BrightStor Enterprise Backup
and a Client Agent, you must:
Make sure that the Client Agent software is properly installed and started on
the client workstation.
Add the client workstation to the BrightStor Enterprise Backup Manager.
Set a workstation password (optional).
Adding a Windows Client Agent Object
To add a Client Agent object to the BrightStor Enterprise Backup Manager,
follow these steps:
1. Open the Backup window in the BrightStor Enterprise Backup Manager.
2. Select the Source tab.
3. Right-click on the appropriate Windows systems listing.
248
4. Select Add Machine/Object from the pop-up menu. The Add Agent dialog
opens:

5. Enter a host name or a TCP/IP protocol address for the client workstation.
You can enter any name you would like for the host name.
If you want to use an IP address for the client machine, type the IP address in
the fields provided. You will be prompted to provide a host name. You may
enter any name you wish for a host name.
Note: If you select the Use Computer Name Resolution option in the Add
Agent dialog, BrightStor Enterprise Backup will attempt to connect to the
client machine using the Machine Name of the client computer, and accept
the IP address assigned. This option allows the administrators to use either
static or dynamic IP addresses to connect to the Agent.
If you are using Use Computer Name Resolution, make sure you have the
correct Machine Name for the workstation. The Agent uses the specific
Machine Name on the network to locate the workstations IP address. If the
machine name is incorrect, your BrightStor Enterprise Backup job targeted to
the client machine may fail.
Select Attempt to use VI protocol if you want BrightStor Enterprise Backup
to utilize the VI protocol for backup and restore.
6. Click Add. The client workstation is added to the machine tree.
Once the workstation is successfully added, you can back up and restore the
workstation like any other machine. See the BrightStor Enterprise Backup
Administrator Guide for further information on backing up and restoring.
Adding a Windows Client Agent Object Using Auto-Discovery
To add a Windows Client Agent object using Auto-Discovery, follow these steps:
3. Right-click on the appropriate Windows systems listing.
4. Select Add Using Auto-Discovery from the pop-up menu.

5. The Agent Select dialog opens. Highlight the Agents you wish to add and
click Add.

250
Adding a NetWare Client Agent Object
To add a NetWare Client Agent object to BrightStor Enterprise Backup, follow
these steps:
3. Right-click on the NetWare Systems Tree.
4. Select Add Machine/Object from the pop-up menu. The Add Agent dialog
opens:

5. In the Host Name field enter the name of the NetWare server upon which the
Client Agent is installed. It is important that the Host Name entered matches
the NetWare server name upon which the agent is running. If the names do
not match, the backup jobs that use this agent will not run successfully.
6. You can enter the TCP/IP address of the NetWare server that you would like
BrightStor Enterprise Backup to connect to the Client Agent for NetWare.
7. You can choose IPX/SPX and enter the IPX address. This consists of the IPX
internal network number and the node number is 000000000001. You can
find the IPX internal network number by typing config at the NetWare server
console.
8. Click Add to add the client workstation to the NetWare Systems tree. Click
Close to close the dialog.
Adding a UNIX/Linux Client Agent Object
From the Source tab in the BrightStor Enterprise Backup Manager, right-click on
the UNIX/Linux System. Enter the appropriate information for the client
machine.
Adding a Workstation Using a UNIX/Linux Operating System
To add a workstation to the Client Database, follow these steps:
1. From the Database Manager, select the Clients Database view.
2. Click Add. The Add Client dialog opens:

3. Enter the information about this workstation and click OK. The workstation
is added to the BrightStor Enterprise Backup Browser.
Important! If you are not sure of the IP address, enter only the host name. As an option,
you can display additional information for the client.
252
Note: All fields other than the Host Name field are optional and appear for
reference only. They do not correspond to where the new client is displayed
within the Backup and Restore Manager browser window. The Client icon
displayed for the new client is determined by the Agent running or installed on
that machine.
Implementing the Use Agent Option
You may view the machines on your network by expanding the Network branch
in BrightStor Enterprise Backup Manager. If you installed a Client Agent on one
of these machines, you may still back up through that Client Agent by following
these steps:
3. Expand the Network tree and then the Microsoft Windows Network in the
BrightStor Enterprise Backup Manager until you have located the client
machine.
4. Right-click on the client machine. Select Use Agent from the pop-up menu.
The Agent Information dialog opens:

5. Select the Use Agent check box.
6. Enter either the TCP/IP address for the client machine or select Use
Computer Name Resolution; or, select IPX/SPX and enter the IPX/SPX
address. Select Attempt to use VI protocol if you want BrightStor Enterprise
Backup to utilize the VI protocol for backup and restore.
Starting and Stopping the Client Agent
7. Click OK. The Agent is now selected.
8. If you are prompted for security, enter the appropriate security for your
environment.
Adding a Client Object Using the Command Line
You can also add a client from the command line using the ca_dbmgr command.
The syntax is:
ca_dbmgr client add <hostname> [ -ip <xxx.xxx.xxx.xxx> ] [ -os <type>]
For example:
ca_dbmgr client add UnixName -ip 141.202.123.192 -os UNIX
See the BrightStor Enterprise Backup Administrator Guide for more details on the
command line options.
This section describes the procedures for starting and stopping the various Client
Agents.
Starting and Stopping the Client Agent for Windows
If you placed the Agent in your Startup program group, it starts automatically
each time you boot up your machine. You can also manually start or stop the
Agent from the Agent program group.
To start or stop the Client Agent for Windows, follow these steps:
1. From the Agent program group, select the Agent Admin program. The
Agent Admin dialog opens.
2. From the menu bar, select Options and then Services. Or, you can just click
Agent Services. The Agent Service dialog opens.
3. Click on the Arrow to start the service or the Red Dot to stop the service.
4. Click OK.
254
Starting and Stopping the Client Agent for NetWare
The Client Agent for NetWare includes a module called CSLOADER.NLM that
carries out a number of monitoring functions when the Client Agent for NetWare
is loaded. CSLOADER.NLM displays on screen and records in log files the
results of this process as a series of informational messages. These messages can
be very useful when you are tracking down the source of a problem.
CSLOADER.NLM also works with the Pre-Flight Check (PFC.NLM), which
evaluates the environment under which the agent will be running. If the
environment fails to meet its requirements, it signals CSLOADER.NLM to abort
the loading sequence.
When you installed the agent with the Agent Setup program, it created an
NWAGENT.NCF file in the SYSTEM directory on the SYS volume of the server
where the agent was installed.
To start the Client Agent and CSLOADER.NLM, type the following at the remote
server console prompt:
nwagent
To stop the Client Agent, at the NetWare Server console prompt type the
following:
unload nwagent
Starting and Stopping the Client Agent for UNIX/Linux
To start the Client Agent, log in as root and type the following at the command
line:
# uagent start
Note: If this command fails, the Client Agent may need to be configured by
running the following script:
# <uagenthome>/uagentsetup
where <uagenthome> is /opt/CA/BEBuagent.
To stop the Client Agent, log in as root and type the following at the command
line:
# uagent stop
256
Checking the Status of the Client Agent for UNIX/Linux
To check the status of the Client Agent for UNIX/Linux, log in as root and type
the following at the command line:
# uagent status
Note: If this command fails, the Client Agent may need to be configured by
running the following script:
# <uagenthome>/uagentsetup
where <uagenthome> is /opt/CA/BEBuagent.
Starting and Stopping the Client Agent for AS/400
To start the Client Agent, log on to the AS/400 machine and type the following
at the command line:
straso
Note: You must have *JOBCTL authority to start the client.
To stop the Client Agent, log on to the AS/400 machine and type the following at
the command line:
endaso
Note: You must have *JOBCTL authority to stop the client.
Starting and Stopping the Client Agent for OpenVMS
To start the Client Agent, log in as system and type the following at the
command line:
@sys$startup:beb$startup.com
To stop the Client Agent, log in as system and type the following at the
command line:
@sys$startup:beb$shutdown.com
Checking the Status of the Client Agent for OpenVMS
To check the status of the Client Agent, log in and type the following at the
command line:
show sys /proc=aso$*

Index

A D
access control list, 1-3 DirectIO
types for UNIX/Linux, 2-45 overview, 1-6
add agent dialog, 2-49 DirectIO feature, using, 2-36
adding objects
NetWare objects, 2-51
E UNIX/Linux objects, 2-52
using auto-discovery, 2-50
using the command line, 2-54
encryption support, 1-2
Windows objects, 2-48
adding UNIX/Linux objects
using UNIX/Linux operating system, 2-52
I
AS/400 configuration, 2-40
ASCONFIG.INI
install types, Windows, 2-3
editing, 2-27
installation issues
auto-discovery, 1-2
NetWare, 2-7
adding objects using, 2-50
Windows, 2-5
installation verification procedure, 2-13, 2-14
C IVP, 2-13, 2-14
compression support, 1-2
L
configuration
general information, 2-42
local options
CRC verification support, 1-3
customizing, 2-22
CSLOADER.NLM, 2-55
M
multi-stream processing, 1-2, 1-5
Index1

N S
NetWare configuration share level password, 2-20
ASCONFIG.INI file, 2-27
Snapshot
known issues, 2-28
overview, 1-6
NDS, 2-28
Snapshot feature, using, 2-36
O
T
OpenVMS
pre-installation, 2-12 Tape Library Option, 1-5
OpenVMS configuration, 2-42 transfer protocol support
changing the logging levels, 2-42 OpenVMS, 2-12
optimizing the TCP/IP stack, 2-42
OpenVMS Installation Verification Procedure, 2-13,
2-14 U
uag.cfg file, 2-29
P
UNIX/Linux configuration
agent.cfg file structure, 2-32
password security option, 1-3 agent.cfg sub-agent fields, 2-33
browser configuration file, 2-32
platform support
directory control file, 2-32
AS/400, 2-10
file system agent control files, 2-32
NetWare, 2-6
file system control file, 2-32
OpenVMS, 2-12
global configuration file, 2-32
UNIX and Linux, 2-8
known issues, 2-40
Windows, 2-1
options for, 2-30
pre/post execution programs, 2-19 uag.cfg file, 2-29
using DirectIO, 2-36
push technology, 1-2, 1-4
using Snapshot, 2-36
UNIX/Linux file system agent control files, 2-32
R use agent option
implementing, 2-53
real-time remote browsing, 1-2
V
registry settings, 2-24
remote installation, 1-3
VI protocol, 1-3, 2-20
Virtual Interface protocol, 1-3, 2-20
virus scanning, 1-3
volume shadow copy service, 1-3

W
Windows configuration
Access Control List, 2-22
agent log file deletion, 2-22
auto-discovery, 2-21
backup/restore/compare priority, 2-19
computer name resolution, 2-21
customizing local options, 2-22
data compression, 2-21
data encryption, 2-21
execution delay, 2-19
IP address, 2-20
known issues, 2-23
multi-stream restore and compare, 2-21
password security, 2-18
pre/post execution programs, 2-19
registry backup, 2-22
security options, 2-22
specify port number, 2-20
system security, 2-18
VI protocol, 2-20
virus scanning, 2-22
Windows registry, 2-24

Index3

BEBWN ClientAgent

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BEBWN ClientAgent

Caricato da

Copyright:

Formati disponibili

Client Agent Guide

Windows and UNIX

Potrebbero piacerti anche