ADSM-L
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers

2009-11-16 10:47:10
Subject: Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers
From: Howard Coles <Howard.Coles AT ARDENTHEALTH DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 16 Nov 2009 09:44:23 -0600 
You will lose access to all the files backed up with a higher version of
the client, but you'll get better backups going forward. (if the client
version is a problem.)  


See Ya'
Howard


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Zoltan Forray/AC/VCU
> Sent: Monday, November 16, 2009 9:20 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers
> 
> We are having too many issues with the V6.1 client on mostly Windoz
> servers.
> 
> So, we are looking at dropping back to V5.5.2.3 (still don't see a 5.3
> client), the pre-Java client, for those problem servers.
> 
> What is the impact of downleveling a client?
> 
> Is it going to force a complete backups?  What about the inactives?
> 
> 
> 
> From:
> Grigori Solonovitch <G.Solonovitch AT BKME DOT COM>
> To:
> ADSM-L AT VM.MARIST DOT EDU
> Date:
> 11/13/2009 01:30 PM
> Subject:
> Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers
> Sent by:
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 
> 
> 
> Hello Zoltan,
> We have started upgrade process from 6.1.0.2 to 6.1.2.0. 5 or 6
servers
> Win2003R2 have been upgraded already.
> We faced similar problem on one of them. I have fixed it by:
de-install
> client --> reboot server --> install client  --> reboot server -->
> configure client services by setup wizard (existing dsm.opt).
> Ithink it is a little bit long process, but what to do?
> Regards,
> Grigori
> ________________________________________
> From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
> Zoltan
> Forray/AC/VCU [zforray AT VCU DOT EDU]
> Sent: Friday, November 13, 2009 8:19 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Problems with 6.1.2.0 on Windows servers
> 
> We started pushing out 6.1.2.0 since our security officer read about
> the
> security vulnerabilitys in 6.1.x
> 
> Now we are starting to see rashes of problems on W2K3 (both regular
and
> R2) servers.  Yet we have plenty of servers that have upgraded with no
> issues.
> 
> ALL of these servers were running just fine with 6.1.0.0 and older
> versions of the client.
> 
> Most are manifesting as crashes in dsmagent and/or communications
> errors
> (which I know from previous issues I have seen with 6.x, is often a
> "red
> herring").
> 
> Yes, we have tried complete un/reinstalls,  completely deleted the
> *:\program files\Tivoli\TSM\directory
> 
> No luck googling for the obvious (dsmagent cXMLiterator)
> 
>  Anyone seeing similar problems?
> 
> Excerpts from the various error logs:
> 
> dsmj.log
> ---------------
> 11/13/2009 09:23:11: ANS2613S A communications protocol error occurred
> between the web browser and the client.Could not get JDOM tree !!!
> *** commOpen: java.net.ConnectException: Connection refused: connect
> 11/13/2009 09:23:16: ANS2613S A communications protocol error occurred
> between the web browser and the client.Could not get JDOM tree !!!
> *** commOpen: java.net.ConnectException: Connection refused: connect
> 11/13/2009 09:24:47: ANS2613S A communications protocol error occurred
> between the web browser and the client.Could not get JDOM tree !!!
> *** commOpen: java.net.ConnectException: Connection refused: connect
> 11/13/2009 09:24:50: ANS2613S A communications protocol error occurred
> between the web browser and the client.Could not get JDOM tree !!!
> *** commFlush: java.net.SocketException: Connection reset by peer:
> socket
> write error
> *** commFlush: java.net.SocketException: Connection reset by peer:
> socket
> write error
> *** commOpen: java.net.ConnectException: Connection refused: connect
> 11/13/2009 09:27:24: ANS2610S TCP/IP communications failure between
the
> client and the server machine.*** commFlush: java.net.SocketException:
> Connection reset by peer: socket write error
> *** commOpen: java.net.ConnectException: Connection refused: connect
> 11/13/2009 11:30:25: ANS2610S TCP/IP communications failure between
the
> client and the server machine.*** commFlush: java.net.SocketException:
> Connection reset by peer: socket write error
> *** commOpen: java.net.ConnectException: Connection refused: connect
> 11/13/2009 11:42:30: ANS2610S TCP/IP communications failure between
the
> client and the server machine.*** commFlush: java.net.SocketException:
> Connection reset by peer: socket write error
> *** commOpen: java.net.ConnectException: Connection refused: connect
> *** commFlush: java.net.SocketException: Connection reset by peer:
> socket
> write error
> *** commFlush: java.net.SocketException: Connection reset by peer:
> socket
> write error
> *** commOpen: java.net.ConnectException: Connection refused: connect
> 11/13/2009 11:45:47: ANS2610S TCP/IP communications failure between
the
> client and the server machine.
> 
> dsmcrash.log
> -----------------------
> 2009/11/13 11:43:03
> IBM Tivoli Storage Manager
> Version: 6.1.2.00
> Build date:  Thu Oct 22 15:11:11 2009
> 
> dsmagent.exe caused exception C0000005 (EXCEPTION_ACCESS_VIOLATION) at
> 001B:0053C4A4
> 
> Register dump:
> EAX=00000013  EBX=00000000  ECX=00000000  EDX=009891BA  ESI=0471FBB8
> EDI=78552B7E  EBP=009891CD  ESP=0471FA1C  EIP=0053C4A4  FLG=00010202
> CS=001B   DS=0023  SS=0023  ES=0023   FS=003B  GS=0000
> 
> Crash dump successfully written to file 'D:\Program
> Files\Tivoli\TSM\baclient\dsmcrash.dmp'
> 
> Stack Trace:
> 001B:0053C4A4 (0x00393030 0x333A3531 0x32323A35 0x31003600)
> dsmagent.exe,
> cXMLiterator::cXMLiterator()+1234948 bytes
> 
> tsmstats.ini
> -------------------
> [fileSystemStatistics.\\dominodc3\c$]
> maxPath=193
> totalLocalFiles=30471
> totalLocalDirs=3059
> maxDirCount=5958
> maxDirName=C:\I386
> [fileSystemStatistics.\\dominodc3\e$]
> maxPath=68
> totalLocalFiles=24
> totalLocalDirs=10
> maxDirCount=7
> maxDirName=E:\8241623edffcba54df4fdc\amd64
> [fileSystemStatistics.\\dominodc3\d$]
> maxPath=92
> totalLocalFiles=423
> totalLocalDirs=45
> maxDirCount=211
> maxDirName=D:\Program Files\Tivoli\TSM\baclient\jvm50\jre\bin
> 
> dsm.opt
> --------------
> PASSWORDACCESS  GENERATE
> TCPSERVERADDRESS        tsmlinux4.ucc.vcu.edu
> SCHEDLOGR 30 D
> ERRORLOGR 30 D
> QUIET
> TCPClientAddress        192.168.20.58
> 
> Please consider the environment before printing this Email.
> 
> "This email message and any attachments transmitted with it may
contain
> confidential and proprietary information, intended only for the named
> recipient(s). If you have received this message in error, or if you
are
> not the named recipient(s), please delete this email after notifying
> the
> sender immediately. BKME cannot guarantee the integrity of this
> communication and accepts no liability for any damage caused by this
> email
> or its attachments due to viruses, any other defects, interception or
> unauthorized modification. The information, views, opinions and
> comments
> of this message are those of the individual and not necessarily
> endorsed
> by BKME."
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [ADSM-L] tape library for TSM, Howard Coles
Next by Date:  Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers, Richard Sims
Previous by Thread:  Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers, Zoltan Forray/AC/VCU
Next by Thread:  Re: [ADSM-L] Problems with 6.1.2.0 on Windows servers, Richard Sims
Indexes:  [Date] [Thread] [Top] [All Lists]