Hi Rick As I understand it, when in polling mode, the first scheduler to come up grabs port1500, the next one finds that in use and grabs 1501, the one after that will try 1502 and so on.
This is one of the better reasons to give up active control, use polling and let the machine sort itself out. The other reason to use polling is that its is less sensitive to firewall rules - if the client can see the server it can back up - whereas for prompted the firewall has to let the server see the client as well. The other thing to consider is whether you really need to run multiple schedulers at all. Now that proxy nodes are here, you could have one scheduler and two schedules. One schedule runs the local disk backup. The other runs a script to check whether the shared disk is mounted on this machine, then if it is starts dsmc with asnode and the shared options file to backup the shared disk. Its less complex to set up, but requires some scripting, and of course you are limited to one active schedule per scheduler at any one time. I'm starting to think that the detect-and-backup approach is better for complex situations, like 4 way SQL Server clusters with multiple instances for example. It might be nice if some of this ability were built into the BA and SQL Server clients rather than each of us having to re-invent the wheel. Regards Steve Steven Harris TSM Admin Paraparaumu New Zealand. Robert Clark wrote:
Some of the clustering solutions alias an IP address that travels with the resource group. The scheduler can be configured to listen on this specific address instead of "*". The easiest way to check is to look at the output from "netstat -an | grep -i list". [RC] From: Richard Rhodes <[email protected]> To: [email protected] Date: 07/16/2010 07:16 AM Subject: [ADSM-L] multiple schedulers Sent by: "ADSM: Dist Stor Manager" <[email protected]> We have a bunch of AIX clusters, all setup in TSM with the standard 3 node config (local node/scheduler for local disk, and cluster node/scheduler for shared disk filesystems). So, where the application is currently running there are 2 schedulers (dsmcad) running. I working on another problem I notice that all client setups are set for PROMPTED, but do NOT specify TCPCLIENTPORT. So on the cluster node with 2 schedulers running, both schedulers must be listening on 1501. Isn't this wrong? If using PROMPTED mode, shouldn't each scheduler have it's own port to listen on specified by TCPCLIENTPORT? I wonder how our setup is working? All three tsm nodes are set to the same schedule time, and all backups are working good . . .somehow. Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message. U.S. BANCORP made the following annotations --------------------------------------------------------------------- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. --------------------------------------------------------------------- ------------------------------------------------------------------------ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.830 / Virus Database: 271.1.1/3008 - Release Date: 07/16/10 06:35:00
