Guys,
Installed and configured the TSM Client (5.5.0.6) on a 3-node Windows 2008 x64 cluster today for over 10 resource groups and everything went fine with install, config and testing..... until.....
After testing the failover, I got one of my guys to test the web client interface from a remote machine, and then I proceeded to fail that resource group to another server. The failover "hung" while it was trying to take down the TSM Generic Service (configured for the CAD service). I have the CAD managing the webclient and the schedule.
Upon closer inspection, found that both the TSM Remote Agent and TSM CAD were showing as STARTED under the services tab, but once I manually stopped the TSM Remote Service the cluster resource group failedover as normal.
Anyone ever seen this before? The TSM Remote Agent stops after about 20mins - but waiting that long isnt really an option. I could script it, but I really want to avoid going there and continue with using the single generic service.
Thoughts?
Installed and configured the TSM Client (5.5.0.6) on a 3-node Windows 2008 x64 cluster today for over 10 resource groups and everything went fine with install, config and testing..... until.....
After testing the failover, I got one of my guys to test the web client interface from a remote machine, and then I proceeded to fail that resource group to another server. The failover "hung" while it was trying to take down the TSM Generic Service (configured for the CAD service). I have the CAD managing the webclient and the schedule.
Upon closer inspection, found that both the TSM Remote Agent and TSM CAD were showing as STARTED under the services tab, but once I manually stopped the TSM Remote Service the cluster resource group failedover as normal.
Anyone ever seen this before? The TSM Remote Agent stops after about 20mins - but waiting that long isnt really an option. I could script it, but I really want to avoid going there and continue with using the single generic service.
Thoughts?