I had the 6.2.3 client on a SQL Server as well, and it kept giving me a
"path not found" trying to backup the registry (system state), and then
wouldn't backup the drives. After I downgraded the Registry still gave
me issues, but at least the disk drives will backup.
See Ya'
Howard Coles Jr., RHCE, CNE, CDE
John 3:16!
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rainer Holzinger
Sent: Tuesday, April 26, 2011 5:28 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] ANS1575E Journal Daemon Communications Error.
Hello Howard,
thanks for your recommendation. I had no issues so far with other TSM
clients not using the JBB method.
However, I will follow your suggestion with this particular server and
'downgrade' to version 6.2.2.0.
Thanks again and best regards,
Rainer
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Howard Coles
> Sent: Tuesday, April 26, 2011 3:29 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] ANS1575E Journal Daemon Communications Error.
>
> Rainer, I don't think the 6.2.3 client for windows if fit for
> production
> use. I would go back to 6.2.2. It has shown all kinds of weirdness
> for
> me. If you run a scheduled command using "c:\progra~1\tivoli\tsm"
> it'll
> change it to "C:\progra\~1\tivoli\tsm", and it didn't help on the vmdk
> backup situation either. So, I'd say try the 6.2.2, and see if it
> performs like you expect, and stick with that until they come out with
> 6.2.4 or 6.3. :D
>
>
> See Ya'
> Howard Coles Jr., RHCE, CNE, CDE
> John 3:16!
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Rainer Holzinger
> Sent: Tuesday, April 26, 2011 6:32 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] ANS1575E Journal Daemon Communications Error.
>
> Hi all,
>
>
>
> I'm having a TSM Windows client which has errors using the JBB method.
>
>
>
> Windows: 2003 SP2 (32-bit)
>
> TSM client: 6.2.3.0
>
>
>
> The backups have been working for about 3 weeks without any problems.
> Now the following messages appear in TSM client error log when the TSM
> Journal service is being started:
>
> 04/26/2011 14:15:41 ANS0361I DIAG: jnlPing(): Invalid ping response:
> verb=0x0a, length=5.
>
> 04/26/2011 14:15:41 ANS0361I DIAG: jnlRead(): Ping failed, Journal
> Daemon not responding.
>
> 04/26/2011 14:15:41 ANS0361I DIAG: JnlQueryResponseThread(tid 4600):
> Error Reading query response, jnlRead(): rc=-1.
>
> 04/26/2011 14:15:41 ANS0361I DIAG: BaJournaled(): jnlNextQueryResp():
> returned journal read error.
>
> 04/26/2011 14:15:41 ANS1575E Journal Daemon Communications Error.
>
>
>
> These messages are in 'jbberror' log:
>
> 04/26/2011 14:25:15 NpWrite(): Connection has been closed.
>
> 04/26/2011 14:25:15 sendClientResponse(): error sending response -
> client severed pipe connection.
>
> 04/26/2011 14:25:15 processJournalQuery(): Error sending Query Results
> Query response.
>
>
>
> 'tsmjbbd.ini' looks like:
>
> ; Journal Service configuration for FORCLUSTER-MAPS on disk L:
>
> :
>
> [JournalSettings]
>
> Nlsrepos=dscameng.txt
>
> Errorlog=jbberror.forcluster-maps.log
>
> JournalDir=L:\TSM
>
> JournalPipe=\\.\pipe\forcluster-maps
>
> ;
>
> [JournalExcludeList]
>
> %SystemRoot%\System32\Config\*
>
> %SystemDrive%\Adsm.Sys\*
>
> %TEMP%\*
>
> %TMP%\*
>
> %USERPROFILE\*\index.dat
>
> *.jdb.dir
>
> *.jdb.pag
>
> *.jdbinc.dir
>
> *.jdbinc.pag
>
> *:\pagefile.sys
>
> *:\*.crmlog
>
> *:\hiberfil.sys
>
> *:\RECYCLED\*
>
> *:\RECYCLER\*
>
> %SystemRoot%\csc\*
>
> %SystemRoot%\System32\DTCLog\MSDTC.LOG
>
> %SystemRoot%\netlogon.chg
>
> %SystemRoot%\schedlgu.txt
>
> %SystemRoot%\registration\*.clb
>
> %WINDIR%\debug\*
>
> %SystemDrive%\Documents and Settings\NetShowServices\ntuser.dat
>
> %SystemDrive%\Documents and Settings\NetShowServices\Local
> Settings\Application Data\Microsoft\Windows\UsrClass.dat
>
> %USERPROFILE%\ntuser.dat
>
> %USERPROFILE%\Local Settings\Application
> Data\Microsoft\Windows\UsrClass.dat
>
> ;
>
> [JournaledFileSystemSettings]
>
> JournaledFileSystems=L:
>
> JournalDBSize=0x00000000
>
> DeferFsMonStart=1
>
> DeferRetryInterval=120
>
> DirNotifyBufferSize=0x00001000
>
> logFsErrors=0
>
> NotifyBufferSize=0x000010000
>
> NotifyFilter=0x00000117
>
> PreserveDBOnExit=1
>
> ;
>
> ;
>
> [JournaledFileSystemSettings.L:\]
>
> JournalDir=L:\TSM
>
>
>
> Has anyone seen these errors before?
>
>
>
> Thanks in advance,
>
> Rainer
>
>
>
> --------------------------------
>
> RHo-Consulting
>
> Rainer Holzinger
>
> Bachstr. 10
>
> D-93105 Tegernheim
>
> phone: +49 9403 969174
>
> mobile: +49 162 2807 888
>
> email: <mailto:RainerHolzinger AT gmx DOT de> RainerHolzinger AT gmx DOT
> de
>
>
>
> CONFIDENTIALITY NOTICE:
>
> This e-mail is confidential and may also be privileged. If you are not
> the intended recipient, please notify the sender IMMEDIATELY; you
> should
> not copy the e-mail or use it for any purpose or disclose its contents
> to any other person.
>
>
>
> VIRUSES:
>
> Although there have been taken steps to ensure that this e-mail and
> attachments are free from any viruses, the recipient should at its
> sole
> discretion take the necessary measures to ensure that the received
> messages are actually virus free.
|
