Given your symptoms, my first line of attack would be to assume that those clients do not have resourceutitization set to 1 and are taking the default of 2 sessions per client. How have you confirmed that your server client option setting is being honored?
David >>> "Gill, Geoffrey L." <[EMAIL PROTECTED]> 9/4/2006 3:31:26 PM >>> I was on late the other night watching this and noticed approximately 3 sessions per server. With a server client option file that has a setting for resourceutilization to 1 it seems odd to see this. This particular setting is configured to override a client setting so I'm a bit confused. In order to get around this I extended the backup window 3 hours. This seems to have taken care of the missed backups. Weird though because it almost looks as if a session has somehow dropped, yet not dropped, and another one started, which eventually causes all 64 to be used. Thanks, Geoff Gill TSM Administrator PeopleSoft Sr. Systems Administrator SAIC M/S-G1b (858)826-4062 Email: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alexander Verkooijen Sent: Monday, September 04, 2006 5:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: missed backups oddity Maybe you could try running a shell script that does a 'query session' every 5 minutes and redirects the output to a log file. That should tell you where all the sessions come from. Something like this should work: --- CUT HERE --- #!/usr/bin/ksh while true do /usr/bin/dsmadmc -id="xxx" -pass="xxx" "q ses" >> mylogfile sleep 300 done ---CUT HERE--- Regards, Alexander ------------------------------------------------------------ Alexander Verkooijen Senior Systems Programmer High Performance Computing SARA Computing & Networking Services
