cancel
Showing results for 
Search instead for 
Did you mean: 

Disk Agents failing

Shannon Petry
Honored Contributor

Disk Agents failing

Running Omniback 3.5 with the cell manager on HP-UX 11.0. I have followed all the steps I could find on how to configure redhat linux 7.2 as a omniback client, and all looks good. I can telnet to port 5555, all software is there, unrestricted remsh and rlogin access.

The omniback inet probram responds, and allows connection. But, when I run omniback I am constantly getting an error "All of the Disk agents failed for lxhost" All objects on "lxhost" will be skipped.

I can view the file systems, so the previewer works, I can select the objects from tree to backup.

Anyway, any Ideas would be appreciated.

Thanks!
Shannon
Microsoft. When do you want a virus today?
4 REPLIES
Kodjo Agbenu
Honored Contributor

Re: Disk Agents failing

Hi Shannon,

First of all, you can put back restrictions on remsh, rlogin, rexec and securetty. Once installed, OmniBack only needs TCP/5555 connection for everything.

Now let's examine the situation :

=> Do you have firewall or advanced router between the Linux box and the HP-UX cell manager ?

=> Do you have ipchains or iptables firewalling rules on Linux (type iptables -L or ipchains -L) ?

To flush all ipchains/iptables rules :

iptables -t filter -F
iptables -t filter -X
iptables -t filter -Z
iptables -t nat -F
iptables -t nat -X
iptables -t nat -Z

or

ipchains -F
ipchains -X
ipchains -Z

Good luck.

Kodjo



Learn and explain...
Shannon Petry
Honored Contributor

Re: Disk Agents failing

It's not a connection issue. I can telnet to port 5555, no issues at all. No firewall, same LAN, light security as the LAN is behind a firewall.

The omni inet daemon starts, it will launch the file system browser. Disk Agent is the daemon not working for some reason. Since it is called by inet, Im not sure how to debug it.

Regards,
Shannon
Microsoft. When do you want a virus today?
Shannon Petry
Honored Contributor

Re: Disk Agents failing

Well, I fixed my own problem, so I'll post my answer here ;) Too bad I cant give myself a 10 for fixing this!


In the directory /usr/omni/bin there is a hidden script called .util which is called by the Omni inet daemon. In the linux getBDF function there is no file type specified for ext3, so the file system was not stat'ed properly and therefor could not be backed up.


I simply added a file type -t ext3 into the string to check for with df, and it worked. Not sure why the disk agent does not care but the script does, but all is well now.

I hope Omni verions higher than version 3.5 include ext3 support as the journaling and logging is important.

Regards,
Shannon
Microsoft. When do you want a virus today?
Chris DePetro
Occasional Advisor

Re: Disk Agents failing

Just poking around and saw this post. Just an FYI, I'm running Omniback 4.1 and the manual modification to the .util file is still needed. No native support for ext3 yet.