Search:  
Gentoo Wiki

HOWTO_Legacy_Veritas_Backup_Exec_Remote_Agent_for_Linux_and_Unix

Contents

Introduction

This is the Legacy BackupExec Remote Agent. There is no RALUS License needed for Backup Exec to recognise the Legacy remote agent. The Legacy Symantec Backup Exec Remote Agent for Linux and Unix Servers enables Windows Server network administrators to perform backup and restore operations on Linux, Unix and Solaris hosts that are connected to the network.

Location of the Legacy Agent

This agent can be found under installation directory of the Veritas (Symantec) Backup Exec Program.

\\BackupServer\C$\Program Files\VERITAS\Backup Exec\NT\Agents\Legacy Unix Agent\be_agnt.tar

Or you can download the latest version here.

http://seer.entsupport.symantec.com/docs/262592.htm

I will be using the one from my Veritas installation folder in this tutorial.

Copy the be_agent.tar

Copy the be_agnt.tar to your Linux/Gentoo server. I used the WinSCP program to transfer the tar to my /tmp/be_agnt folder.

I created a folder under /tmp/be_agnt and then extracted the tar.

# mkdir /tmp/be_agnt

You will need to manually create these directories - for somereason these do not get created.

# mkdir /etc/rc.d
# mkdir /etc/rc.d/rc2.d

For Backup Exec version 8.5, also create these directories.

# mkdir /etc/rc.d/init.d
# mkdir /etc/rc.d/rc3.d
# mkdir /etc/rc.d/rc5.d

Move the be_agnt.tar to the /tmp/be_agnt directory using the WinSCP

# cd /tmp/be_agnt  
# tar -xvf be_agnt.tar
# ./INSTALL

The Install

File: Step by Step Installation
Backup Exec Unix Agent Language Selection v4.3


Backup Exec UNIX Agent Install v3.7
Copyright 2001 VERITAS Software Corporation.  All Rights Reserved.

Operating systems supported:
 1. Solaris Sparc 2.6, 2.7, 8, 9
 2. Solaris Intel x86 2.6, 7, 8
 3. HP UX 10.20, 11.x
 4. IBM AIX 4.3.x, 5.x
 5. Linux 2.4 (RedHat7.1+, SuSE7.1+, Caldera3.1+, Turbo7.0+, Mandrake8.0+)
 6. Linux 2.2, 2.0 (RedHat7.0-, SuSE7.1-, Caldera2.4-, Turbo6.5-, Mandrake7.2-)
 7. SCO UnixWare 7.x

Operating system detected:
Linux 2.2, 2.0 (RedHat7.0-, SuSE7.1-, Caldera2.4-, Turbo6.5-, Mandrake7.2-)

Is this correct? (y/n) y

Operating system selected:
Linux 2.2, 2.0 (RedHat7.0-, SuSE7.1-, Caldera2.4-, Turbo6.5-, Mandrake7.2-)

Installing the Backup Exec UNIX Agent for system type: linux

Please enter the full directory path where the Backup Exec Agent should
be installed: [/etc/bkupexec] HIT ENTER HERE

Your system's initialization procedure has been modified to
automatically start the Agent the next time your system is started.

All necessary Backup Exec Agent files have been copied to: /etc/bkupexec

Adding the following line to /etc/services:
grfs            6101/tcp        # Backup Exec Agent

The configuration for the Backup Exec Agent is stored in
/etc/bkupexec/agent.cfg.  You may edit this file at any time to
change the configuration for the Agent.

You will now be prompted to enter the initial values for the
Agent configuration.

Press Enter to continue

0+1 records in
0+1 records out
31 bytes (31 B) copied, 7.3794e-05 s, 420 kB/s

Please enter the name for this workstation [WORKSTATIONNAME.DOMAIN.COM]:

Do you require a password for this workstation? (y/n) y

Please enter the password for this workstation: YOURPASSWORD

Does this workstation have 2 or more network interfaces? (y/n) n

Please enter a directory path you want to export as a published path: /var

Please enter a unique resource name for this published path: [var]

Do you want to allow files to be restored to this published path? (y/n) y

Do you require a password for this published path? (y/n) n

Do you want to publish another directory path? (y/n) n

You must enter the names of the Backup Exec media servers which will
access this workstation.  The media server's internet addresses must be
defined in the /etc/hosts file or accessible via a naming service.

Please enter a media server name: YOURBACKUPSERVER

Locating eabackup....located and added to media server list.

Do you want to add another media server? (y/n) n

The Backup Exec Agent must periodically send advertisement messages
to the media servers to inform them that this workstation is
accessible.  Please enter the frequency (in seconds) that these
advertisements should be sent: [30] HIT ENTER HERE

Symbolic links to directories may be backed up in one of two ways.

Method 1:  The symbolically linked directory is handled as a special file
           and only the information required to recreate the symbolic
           link is backed up.

Method 2:  The symbolically linked directory is backed up as a normal
           directory.  All files and subdirectories within the
           symbolically linked directory are also backed up.

Method 1 is preferred because it minimizes the amount of data which must
be backed up.

Which method do you want to use? (1 or 2) [1] 2

Backup Exec Agent configuration complete.

Note: You may edit the file /etc/bkupexec/agent.cfg to change your Backup
        Exec Agent configuration at any time.  Configuration changes for the
        Backup Exec Agent will take effect after the host is restarted.

Check Your Configuration

#nano -w /etc/bkupexec/agent.cfg
File: /etc/bkupexec/agent.cfg
#
# This is the config file for the Backup Exec Unix Agent.  It specifies what 
# directories are published, the access privileges, and which media server
# machines should receive the advertisements for these resources.  
#
# The "-c <filename>" command line option for the Agent program can be 
# used to specify an agent config file for the Agent to use.  Otherwise, the 
# Agent will use the agent.cfg file in the current directory.
#
# The format for this file is line oriented.  Each line contains a keyword
# which corresponds to a specific configuration command.  Some configuration
# commands require additional parameters which are entered on the line with
# the command.  Blank lines or lines beginning with a '#' are ignored.
#
# Parameters enclosed in the symbols <> are required fields.  The
# user MUST supply values for these parameters. 
# 
# Parameters enclosed in the symbols [] are optional fields.  The 
# user is not required to specify these parameters. 
#
# The allowable commands are:
#
#     name <workstation name>			
#     password <passwd>
#     export <directory> as <resourcename> [write_protected] [password <passwd>] [include_remote] [no_nfs_locking]
#     tell <machine name>
#     tell_interval <number of seconds>
#     follow_symdirs
#     exclude_file <filename>
#     exclude_dir <directory name>
#
# The commands are described below:
#
# name <workstation name>
#   - This command is used to define the name which the agent program will 
#     advertise to media servers and clients. The workstation name is limited to upper-case
#     alphabet characters (A-Z), the digits (0-9), and the underscore (_) character.
#     The agent program will automatically modify the workstation name if it reads
#     the configuration file and detects illegal characters in the workstation name.
#     The agent program will uppercase lowercase characters, and it will replace all
#     other illegal characters with the underscore (_) character.  After the agent has
#     read its configuration file, it will display the workstation name as it will 
#     appear in Backup Exec client source selection screens.  
#
# password <passwd>
#   - In order to access this workstation from the Backup Exec Client, 
#     the user must enter the password, "passwd".  This command is 
#     optional and if it is not present, then the password for the
#     workstation is simply the [ENTER] key.
#
# export <directory> as <resourcename> [write_protected] [password <passwd>] [include_remote] [no_nfs_locking]
#   - export is used to specify a directory tree to publish 
#     so that it may be accessed by the Backup Exec Client.
#     "resourcename" will appear in the Backup Exec Client's sub-device
#     selection screens.
#     If "write_protected" is specified, the directory can be accessed 
#     for backup operations but not for restore operations.
#     If "password <passwd>" is specified the user will be required to
#     enter the password, <passwd> before accessing the directory. 
#     If "include_remote" is specified, any remotely mounted file systems with 
#     mount points within the directory tree will also be accessible for 
#     backup and restore operations.
#     If "no_nfs_locking" is specified, files will not be locked during 
#     backup operations if they are located in remotely mounted file systems
#     with mount points within the directory tree. 
#
#   Examples:
#     export / as ROOT write_protected
#     export /usr as USR password SARAFINA
#
# tell <machine name>
#   - The TELL command takes a machine name as an argument.  This
#     machine will be added to the list of machines that advertisements
#     will be sent to.  This machine name MUST be found in the /etc/hosts
#     file.
#
# tell_interval <number_of_seconds>
#   - This command specifies the delay time between advertisements.
#     This number shouldn't be too large (more than several minutes)
#     or it will take a long time before the backup application learns
#     about it, it should also not be too small or there will be excessive
#     network traffic.  Each advertisement transaction requires 8 network 
#     packets.
#	  
# follow_symdirs
#   - By default symbolically linked directories are not backed up.  Only
#     the "link" itself is backed up.  If "follow_symdirs" is specified,
#     then the "link" is not backed up, instead the entire linked directory
#     tree is backed up.  This option is not available with the SCO agent.
#
# exclude_file <filename>
#   - This command prevents the named file from being accessible for backup.  The
#     filename must use a fully specified path.
#
# exclude_dir <directory name>
#   - This command prevents the named directory from being accessible for backup.
#     The directory name must use a fully specified path.
#
# preserve_ctime
#   - This option forces the agent to ignore the message which sets object's (files,
#     directorys) attributes when a backup occurs.  Normally during a backup, the
#     backup engine preserves an object's last access timestamp by resetting the 
#     last access timestamp to the value before the backup occurred.  When the
#     agent modifies the object's last access timestamp, the OS internally updates
#     the object's "ctime". An object's "ctime" is the time when an object's
#     attributes (permissions, timestamps, etc) have been modified.  By not
#     attempting to reset the attributes after a backup, the object's ctime is
#     not updated.  This option does not effect setting object attributes during
#     restore operations.
#
# force_address <IP address>
#   - When a system has 2 or more network interfaces, this option can be used
#     to specify which interface will be used by the agent.
#


File: /etc/bkupexec/agent.cfg
name COMPUTERNAME.DOMAIN.COM
password YOURPASSWORD
export / as root
export /var as VAR
force_address THE IP OF THE COMPUTER THE REMOTE AGENT IS INSTALLED ON
tell YOURBACKUPSERVER OR THE IP OF THE BACKUPSERVER
tell_interval 30
follow_symdirs
exclude_dir /dev
exclude_dir /proc

The Startup

Add the script to your local.start

File: nano /etc/conf.d/local.start

/etc/rc.d/agent.init start


Add the script to your local.stop

File: nano /etc/conf.d/local.stop

/etc/rc.d/agent.init stop


For Backup Exec version 8.5, use the path /etc/rc.d/init.d/agent.init

Restart local.start

#/etc/init.d/local restart

Firewall

If there is a firewall involved, be sure to open port 6101.

If I missed anything please add. Everything seems to working for me with this setup.

Enjoy!

Related Articles

HOWTO_Symantec_Backup_Exec_Remote_Agent_for_Linux_and_Unix_Servers You must have a RALUS license.

Retrieved from "http://www.gentoo-wiki.info/HOWTO_Legacy_Veritas_Backup_Exec_Remote_Agent_for_Linux_and_Unix"

Last modified: Fri, 05 Sep 2008 06:40:00 +0000 Hits: 6,736