Wanda, Your symptoms sound similar to an issue I'm having, only mine is on a TDP-SQL machine. If you are running x64, MS seems to have "broken" their VSS when used with 32bit apps (in my case SQL2000).
If running an ntbackup of the systemstate results in a hang followed by this message, you may need an MS hotfix for VSS: Volume shadow copy creation: Attempt 1. Timeout before function completed Error returned while creating the volume shadow copy: 0xffffffff. Error returned while creating the volume shadow copy:ffffffff Aborting Backup. Or you could trace the tsm cmd line client and look for this: 04/21/2006 12:39:51.377 [004556] [3132] : vssreq.cpp (8228): VssRequestor::QueryStatus(): VSS - waiting for asynchronous operation to complete for caller 'VssQuerySystemWriters()' 04/21/2006 13:12:27.978 [004556] [3132] : vssreq.cpp (3201): VssQuerySystemWriters(): Asynchronous GatherWriterMetadata finished. Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-752-6574 (desk) 423-785-7347 (cell) ***public*** -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, Wanda Sent: Tuesday, April 25, 2006 4:29 PM To: ADSM-L@VM.MARIST.EDU 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. Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm