Wanda, I don't have experience with this exact configuration, but in the past anti-virus s/w has caused me problems on clusters. Obviously, the local A/V sw is not a problem as it only occurs when you bring the exchange resources online to the node. However, you might have specific Exchange related AV resources coming across.
Your system administrators may not be keen to do this, if the box is live, but you could try to take any AV cluster resources offline and see if this solves the problem. Just a thought. Regards the clusternode setting, it does not need to be set to yes for the local backup and the 5.3.3.0 client will actually give you an error saying that it will not allow you to backup the local drives with clusternode yes. Leigh -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: 25 April 2006 21:29 To: [email protected] Subject: [ADSM-L] TSM BA client on Exchange 4-way cluster hangs 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.
