Re: TSM BA client on Exchange 4-way cluster hangs
2006-04-26 11:25:00
Andy, thanks for the reply -
It's an unremarkable Dell Xeon 320 Mhz 32bit host.
Windows 2003 server SP1
Exchange 2003, no service packs.
If we start ntbackup from the command line, it opens up OK. Didn't try to
actually back anything up.
I'm seeing these errors occasionally in the NT event log, which look ugly, but
I can't relate them directly to trying to start the TSM client:
event id 8194
Volume Shadow Copy Serivces Unexpected error queryihng for iVSSWriteCallback
interface
________________________________
From: ADSM: Dist Stor Manager on behalf of Andrew Raibeck
Sent: Tue 4/25/2006 4:41 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM BA client on Exchange 4-way cluster hangs
Hi Wanda, which SP are you running, and on what processor architecture?
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
IBM Tivoli Storage Manager support web page:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2006-04-25
13:28:38:
> Windows 2003, Exchange 2003, 4-node cluster, 3 active 1 passive.
> BAclient 5.3.2.2.
> TDP For Exchange NOT installed yet.
>
> Have installed the Windows baclient, trying to get a backup of the
> C: drive and system state before we start installing the TDP for
> Exchange and all the appropriate schedulers.
>
> On NODE4 (the passive node), got the baclient installed and backed
> up the C: drive.
> Then used the cluster admin app to move Exchange resources from one
> of the other nodes to NODE4.
>
> Now the Baclient won't open. Just hangs at the splash screen with
> msg "initializing".
> Domain is C:, E;, SYSTEM SERVICES, SYSTEM STATE.
>
> A reboot clears things up. But once the resources get moved back to
> NODE4, same result - GUI hangs.
> (And this is the baclient, not the TDP client....)
>
> Results are the same whether I have CLUSTERNODE YES in the dsm.opt
> file or not. (Is CLUSTERNODE YES required for the client instance
> that is to back up the local resources only?)
>
> Any hints? No error messages, eventually have to kill the process
> with Task Manager.
>
>
|
|
|