Operating System - HP-UX
1833866 Members
2291 Online
110063 Solutions
New Discussion

OmniBack II 3.5 and Compaq Tru 64 Unix V 5.1

 
Ashish Tripathi
Advisor

OmniBack II 3.5 and Compaq Tru 64 Unix V 5.1

Hi Admins,
I am using OmniBack II 3.5 and wud like to take backups of
Compaq Tru 64 V 5.1Unix servers.I added them as the client successfully
(Only Disk Agent and Cell Console) and tested some small backups(with the
DLT Library on HP Cell Server)....worked fine.....but now I am having
problems....when I try to take larger backups (like 4 separate file
systems)..it starts 4 disk agents and runs only one and after some time
Backup is aborted with the error "ERROR READING NET MESSAGES..ABORTING".
Please note that Compaq server is in Compaq Cluster of two nodes.
I am suspecting any network issue but not able to find any.......Is any one
out there who can show me some light on this as It is really very URGENT
.......
Ashish Tripathi
The best way to make dreams true is to wake up.
2 REPLIES 2
A. Clay Stephenson
Acclaimed Contributor

Re: OmniBack II 3.5 and Compaq Tru 64 Unix V 5.1

I vaguely remember having a problem like this about 3 years ago under OmniBack 2.55 and Digital Unix 4.0d. I wish that I could remember more but the root cause appeared on the Digital UNIX's console and system logs.
Also check the OmniBack logs on the Compaq server. I think I increased the kernel parameters sb_max, tcp_sendspace, and tcp_recvspace. (I had increased the block size and Disk Agent Buffers of the backup device beyond default values for performance reasons and this caused the problems on the DEC box.)
I also noticed that 5.1 is not listed in the disk agent support matrix.
If it ain't broke, I can fix that.
Chin Guan
Valued Contributor

Re: OmniBack II 3.5 and Compaq Tru 64 Unix V 5.1

Version 5.1 is not supported by Omniback 3.5 yet. You can refer to supported platform at :
http://www.openview.hp.com/Uploads/Support_matrix_112700.pdf

Anyway, normally that message is related to network. I have a similar case before, but it was on HP-UX machines. I cannot find error anywhere. But I tune down "concurrency" of the devices helps. You may want to give it a try

Regards,
Chin Guan