Yes, it is all working ok now. One gotcha we found was that our NT guy set up the option file for the local drive clients with
cluster no This was a mistake as you dont want the option there at all on the local clients. Specifying the option just caused duplicate backups of the cluster drive. Jon Adams <[EMAIL PROTECTED]> on 07/08/2002 06:21:06 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: John Naylor/HAV/SSE) Subject: Re: Win2K cluster question I see you have your answer (in short, it is YES), but wanted to bring to your attention of an issue I had to find out the hard way: Follow the directions in the book for proper installation and configuration of the cluster-aware "generic service" resource but, be aware that there is a typo in the book, page 23 - you also require the switch /CLUSTERNODE:YES in order for that CLI command to properly install and configure that service. I had to call support on that one, but I do not remember the APAR for it. -----Original Message----- From: Zlatko Krastev [mailto:[EMAIL PROTECTED]] Sent: Friday, July 05, 2002 4:48 AM To: [EMAIL PROTECTED] Subject: Re: Win2K cluster question Gianluca, if you have MSCS cluster set-up according to the TSM client docs you have to define 3 nodes for active/passive and 4 nodes for active/active cluster: - Machine 1 - node A (local, small) - Machine 2 - node B (local, small) - Cluster group X - node X (shared, might be big) - (optional) Cluster group Y - node Y (shared, might be big) Assuming local drives and cluster groups Y, Z, etc. are small and we have to focus only on group X which is 200 GB. Nodes A, B (local), Y, Z go to small_domain and node X gets registered in big_domain. Or use management class pointing to another pool as Alexander suggested. This is according to books. If we make something proprietary we are on our own. Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Win2K cluster question John, I'm not sure I understand your question. are you saying you want one machine in a cluster to be registered to one policy domain and the other machine in the cluster to be registered to another policy domain? you would not be using a cluster this way, what would happen in case of failover? you would failover to a machine with a different nodename and different policy domain, so you would, effectively, be working on a stand alone basis. Cordiali saluti Gianluca Mariani Tivoli TSM Global Response Team, Roma Via Sciangai 53, Roma phones : +39(0)659664598 +393351270554 (mobile) [EMAIL PROTECTED] John Naylor <john.naylor@SCOTTISH-SOUT To: [EMAIL PROTECTED] HERN.CO.UK> cc: Sent by: "ADSM: Dist Stor Subject: Win2K cluster question Manager" <[EMAIL PROTECTED]> 03-07-02 11.27 Please respond to "ADSM: Dist Stor Manager" We are looking at setting up some win2k clustered TSM clients. Most of them are fairly small but there is one client with 200gb of data to be backed up. I want to point all the small clients to use our standard tapepool, with the big one pointing to a different tapepool So the question is :- Can you have clients within the same cluster registered to different policy domains? Thanks, John ********************************************************************** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **********************************************************************
