Your TSM client does not need to be at the same level as your Data Protection for Exchange.
It seems like you already read Chapter 6 titled "Using the Tivoli Storage Manager scheduler" in the Data Protection for Exchange User's Guide since it covers the things to pay attention to when setting up in a cluster environment. It seems like there are quite a few details on this. It may be a good idea to open PMR to help you get to the answer more quickly. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 11/19/2010 01:11:06 PM: >> From: cc1702004 <[email protected]> >> To: [email protected] >> Date: 11/19/2010 01:13 PM >> Subject: Having problem generating TDP Exchange scheduler in cluster >> Sent by: "ADSM: Dist Stor Manager" <[email protected]> >> >> Hi, >> >> Sorry, I just copy and paste quickly the sample and made some >> misallignment in my sample. The clusternode command is in separate >> line in the dsm.opt file and the node and password is correct (I >> just use different name in the sample command). I have installed >> client scheduler and CAD services in the physical node to backup >> cluster drives using the same set of dsmcutil command and there is >> no issue. Only issue is when trying to generate the TDP Exchange >> scheduler in the cluster environment. >> >> Anyway, the TSM client in the server is 5.5.3 and the TDP Exchange >> is 6.1.0. Do you think this could be the cause? Is there a need for >> the TSM client and TDP exchange to be on the same version? >> >> Funny thing is on a standalone Windows server, installed with >> standalone Exchange server, I have no problem installing the TDP >> exchange scheduler. In the standalone environment, I also used TSM >> client version 5.5.3 and TDP Exchange 6.1.0. I only hit the problem >> when setting up the TDP exchange in the cluster environment. >> >> Thanks
