Thanks for your input. I got a great idea from a colleague at Laiki Bank that suggested to have different .opt files (specifying different nodenames) and rename them accordingly before each backup.
I tested it and it works fine. Thanks Yiannakis -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Karel Bos Sent: 08 December 2003 15:06 To: [EMAIL PROTECTED] Subject: Re: Second nodename for same server And use different port numbers... Regard, Karel -----Oorspronkelijk bericht----- Van: Daniel Sparrman [mailto:[EMAIL PROTECTED] Verzonden: maandag 8 december 2003 13:54 Aan: [EMAIL PROTECTED] Onderwerp: Re: Second nodename for same server Hi As I understand it, you have problems using different nodes, with different settings and different scheduler services. This is due to the fact that both scheduler services read their settings from the same opt-file. You should create a second opt-file for your second node, and then register the second scheduler service with the /optfile:"full path to optfile" setting. This way, you could use separat nodenames and separat settings for your two nodes, and the scheduler services will read different opt-files. Best Regards Daniel Sparrman ----------------------------------- Daniel Sparrman Exist i Stockholm AB Propellerv�gen 6B 183 62 T�BY V�xel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Yiannakis Vakis <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2003-12-08 10:45 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Second nodename for same server Hi, I have registered a second node name for the same Win2000 server and also defined a second scheduler service on the server to use the second nodename in order to schedule backups using a different policy set. So, I have nodename BOCOVS2 (original name in policy domain A) and SYSBOCOVS2 (new registered nodename in policy domain B) for the same server. To define the second scheduler service I have defined a new dsm.opt file with the option NODENAME SYSBOCOVS2 and associated that .opt file with the second scheduler service. When I change the name of the node in the backup/archive client (Edit/Preferences/General tab) to the new node name and stop/start the scheduler service associated with the new .opt file the schedule works perfectly. The backup completes successfully, uses the correct management class associated with the policy domain B and the data goes to SYSSTORAGEPOOL. When I change the nodename in the backup/archive client back to BOCOVS2, the TSM server still polls both nodenames. If a backup is executed it goes to the storage pool associated with the management class of policy domain A. Is there a way to solve this problem ? Thanks Yiannakis
