Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot connect to vmd errors

Status
Not open for further replies.

kmgaines

Technical User
Jan 27, 2004
8
0
0
US
Currently running NB 4.5 in Solaris 2.8 environment.
1-master
1-media server Solaris 2.8
1-media server Solaris 2.9
1 ADIC Scalar 1000 (8 LTO1 drives, SSO option)

Backup client environment is approx. 175 mixed platform (win2k,winnt,unx,lnx) servers.

Currently receiving extended periods of the following error:

unable to obtain db handle for Media Manager query on host nbmaster, cannot connect to vmd

Receiving status code 58's and 25's as well as 134's causing many clients to miss backup window.

Thanx in advance as always,
Kmgaines
 
check your kernal tunable parameters

Minimum system requirements for the Solaris kernel when used with VERITAS NetBackup (tm), defined in /etc/system


Details:
This document states the minimum system requirements for tuning Solaris kernel parameters to work with NetBackup. VERITAS only provides this information as a basic starting point, as this is actually a Solaris OS configuration issue that is also impacted by other applications running on the system.

If /etc/system already contains one of these entries, use whichever value is larger for that setting. Before modifying /etc/system, use the sysdef command to view the current kernel parameters. Add the following lines to /etc/system and reboot for the settings to take effect. After rebooting the sysdef command should display the new settings:

---------------------------------------
* Message queues
set msgsys:msginfo_msgmap=500
set msgsys:msginfo_msgmax=8192
set msgsys:msginfo_msgmnb=65536
set msgsys:msginfo_msgmni=256
set msgsys:msginfo_msgssz=32
set msgsys:msginfo_msgtql=500
set msgsys:msginfo_msgseg=8192

* Semaphores
set semsys:seminfo_semmap=64
set semsys:seminfo_semmni=1024
set semsys:seminfo_semmns=1024
set semsys:seminfo_semmnu=1024
set semsys:seminfo_semmsl=300
set semsys:seminfo_semopm=32
set semsys:seminfo_semume=64

* Shared memory
set shmsys:shminfo_shmmax=16777216
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=230
set shmsys:shminfo_shmseg=100
---------------------------------------

The parameters listed below are obsolete in Solaris 8, but are still valid in Solaris 2.6 and 2.7:

set msgsys:msginfo_msgssz = The size of the message segment in bytes (multiple of word size).
set msgsys:msginfo_msgmap = number of elements in the map that is used to allocate message segments message map.
set msgsys:msginfo_msgseg = maximum number of message segments. The kernel reserves a total of msgssz * the msgseg bytes for message segments and must be less than 128 Kilobytes. Together msgssz and msgseg limit the amount of text for all outstanding messages.
set semsys:seminfo_semmap = number of entries in semaphore map
set shmsys:shminfo_shmmin = minimum shared memory segment size
set shmsys:shminfo_shmseg = maximum number of shared memory segments that can be attached to a given process at one time

If the values are present in the /etc/system file on a Solaris 8 or 9 system, the operating system will ignore them.

Any further or more detailed assistance with kernel tuning should be sought directly from Sun Microsystems.


Related Documents:

242060: Explanation of semaphore, message queue and shared memory settings in /etc/system


246860: NetBackup 4.5 DataCenter Installation Guide for UNIX


264256: VERITAS NetBackup (tm) 5.0 Installation Guide for UNIX


264967: 3rd PARTY: Additional tuning information/suggestions for Solaris 9 systems running NetBackup 4.5


268087: VERITAS NetBackup (tm) 5.1 Installation Guide for UNIX



Bob Stump
Just because the VERITAS documentation states a certain thing does not make it a fact and that is truth.
 
Also look into changing the tcp time wait interval:

1. Check:

ndd /dev/tcp tcp_time_wait_interval

2. Change:

ndd -set /dev/tcp tcp_time_wait_interval 60000

Note: The default is 240000...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top