Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 May 2001 17:32:31 -0400
From:      "C. Pinson @ KA International" <pinson@ka.com>
To:        "'freebsd-stable@freebsd.org'" <freebsd-stable@freebsd.org>
Subject:   RE: Veritas Backup Exec UNIX agent
Message-ID:  <000201c0e3cf$e0960f40$9793a8c0@mountain.corp.ka.com>
In-Reply-To: <4BC10D47D7ACD3119FA800104B1F883668ECCC@exchange.cigital.com>

next in thread | previous in thread | raw e-mail | index | archive | help
How to make Veritas BackupExec 7.3 for NT work with FreeBSD UNIX clients:

Note:
	This procedure assumes that you do not need to run other linux programs.
	Otherwise, instead of steps 5-7, just make a link in /usr/compat/linux
	called "FreeBSD" or something which points to your data.  Be sure you don't
	create recursive backup loops by linking to / and then try to backup /

0. Forget about the install script -- they don't work with FreeBSD

1. Get the unix agent tar file from Veritas web site or CD

	Backup Exec -- Unix Agent, Version 5.01

2. Untar and find agent.linux

	MD5 (agent.linux) = f53d6d42546184a6f69b31fcd8516995

	agent.linux size is 98670

3. Create the agent.cfg file:

name THIS_MACHINE
password SECRET-1
export /  as ROOT password SECRET-2 include_remote
tell BACKUP_SERVER
tell_interval 30
exclude_dir /dev
exclude_dir /proc


	(Change SECRET-1 etc as needed.)


4. Copy agent.linux and agent.cfg in /usr/local/bkupexec

5. make install linux_base-6.1 in ports/emulators, then copy these files to
a new directory /lib

-rwxr-xr-x  1 root  wheel   344890 ld-linux.so.2
-rwxr-xr-x  1 root  wheel    16438 libNoVersion.so.1
-rwxr-xr-x  1 root  wheel  4118299 libc.so.6
-rwxr-xr-x  1 root  wheel   247348 libnss_files.so.2

6. Now to get rid of the megs of linux stuff you don't need:
	rm -rf /compat/linux

7. Make a link as follows:    ln -s / linux

8. Add this line to the end of /etc/services
	grfs            6101/tcp        # Backup Exec Agent


9. Put this in /etc/rc.local

#!/bin/sh
/usr/local/bkupexec/agent.linux -c /usr/local/bkupexec/agent.cfg  >
/dev/null &


10. If you have problems, cd to /usr/local/bkupexec and run it with debug
on:
		./agent.linux -d -c agent.cfg

	or

		./agent.linux -nd -c agent.cfg

	for network debugging.

11.  It's ok if you see complaints about 'host' and 'bind' when agent.linux
starts up.
	This comes from /etc/hosts.conf differences between linux and FreeBSD


12. Be sure your BackupExec host is listed in the TELL line and in
/etc/hosts

13. Either reboot the FreeBSD machine OR restart inetd & manually start
agent.linux

13. From BackupExec, select Unix agents, enter SECRET-1, select ROOT, and
enter SECRET-2

		You can't backup the BSD machine from the list of machines in the
domain/workgroup.

Other thoughts:

	The FreeBSD machine does not have to be in the domain of the BackupExec
machine.

	BE security is very questionable, because the authentication is done by
Veritas softare.
		Probably something like xor with 0xAA55 or something :-)

	When you do backups this way, you lose the unix permissions, owner and
group info.

	Check into using dump(8) or tar(1) from cron to make a single giant backup
file. 'man periodic'

	Backups run at 150MB/min, restores are much slower.

	Be sure that /usr/local/bkupexec/agent.cfg is r/w only by root since it has
passwords
		in the clear.  Scheesh!!!

	In version 8.x, Veritas has enhanced their cost structure, yet has
maintained 100% of
	the the same bugs. Suggestion: Don't buy anything from Veritas if you can
help it.

	Even better, just forget all this and use unix backup tools.  Hello Amanda!

	Good luck!

C. Pinson
Knowledge Access International, Inc.
www.ka.com pinson@ka.com



-----Original Message-----
From: owner-freebsd-stable@FreeBSD.ORG
[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Yanek Korff
Sent: Wednesday, May 23, 2001 3:48 PM
To: 'freebsd-stable@freebsd.org'
Subject: Veritas Backup Exec UNIX agent


Has anyone had any experience with the aforementioned backup product with
FreeBSD?  Its linux agent doesn't appear to work quite right with FreeBSD...
I have to specify include_remote to get a full filesystem listing, but even
then there are some notable exceptions.  If I were to, say, export / as root
include_remote, you'd note that there was no /usr/local listed.

-Yanek.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000201c0e3cf$e0960f40$9793a8c0>