mail server plz help

fotoguy · 06-13-2005, 08:40 AM

Quote:

Originally posted by jtdodge
are most external drives linux compatible?

i think most are compatible, although my 120 gb drive under mandrake 10 was only recognised as 110 gb so i lost 10 gb, but that's no problem really. I haven't tried any larger drives than that so i cant say for sure.

jtdodge · 06-15-2005, 01:37 PM

how do i locate an installation file to load with linux. i downloaded amanda to test as a backup util...but i can't for the life of me figure out how to locate it in order to load the app.

got any input for me on this one?

thanks again

jtdodge

bentz · 06-15-2005, 02:06 PM

I have experience with Backup Exec, both 8.6 and 9.1. They provide a Backup Exec Agent for Unix in the AGENTS directory on the installation media.

The Agent for Unix installation is a little clunkly, but overall it works well, and makes your system appear in the "Unix Agents" group in the Backup (or Restore) selection list window.

Once you're up and running Veritas Backup Exec works satisfactorily for backing up both Linux and Windows machines to the same set.

Note that Differential backups are not possible with a Unix agent due to the fact that Veritas still uses the old-school MSDOS Archive Bit.

jtdodge · 06-15-2005, 02:22 PM

my backupexec has a hage problem connecting to the linux box and is set up with the unix agent like you mentioned. it worked mediocre for some time and now i have two good backups in two weeks. it just won't connect to the drive.

do you have any input for me?

jtdodge

bentz · 06-15-2005, 02:42 PM

Is the agent.init/agent.be service still running?

ps -auxwww | grep 'agent'

Is there are firewall or some other troublesome device between the server and Veritas?

Can you try and kill/restart the agent.be service?
Can you try and reinstall the agent.be service?

jtdodge · 06-15-2005, 07:45 PM

it does connect about every 4 days or so

and i can stop and restart the service and that use to help with the next night's backup...but, alas, not anymore.

sound like anything obviose to you...i'm pretty new to full on linux administration...so i'm shooting in the dark here.

bentz · 06-16-2005, 09:07 AM

I think the only advice I can give is to double-check the settings in /etc/bkupexec/agent.cfg. It should look something like this:

Code:

name LINUX-SERVER-NAME
export / as root write_protect
tell VERITAS_SERVER_IP_OR_HOSTNAME
tell_interval 120
exclude_dir /dev
exclude_dir /proc

The tell_interval parameter is super important. If you don't provide it, the agent defaults to nothing, and it will infinately try to connect to the Veritas server with no delay between attempts, therefore DoS-ing yourself with a barage of open sockets. It's a pretty goofy thing for Veritas to have released code with such a stupid bug in it.

Also, check out netstat, and see if you can find any connection between the two servers.