Oh, I forgot about the lack of replicate. Not sure what would cause the registry key replication to be grayed over, I've never seen that in a cluster that didn't have other more serious issues.
See Ya' Howard Coles Jr. John 3:16! -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Christian Svensson Sent: Wednesday, January 25, 2012 9:35 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: Windsows 2008 failover cluster, SQL Server and TSM Have you put the dsm.opt file on the cluster disk? And have you recognize the password registry key? Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Supported Platform for CPU2TSM:: http://www.cristie.se/cpu2tsm-supported-platforms ________________________________________ Från: Bill Boyer [bjdbo...@comcast.net] Skickat: den 25 januari 2012 15:58 Till: ADSM-L@VM.MARIST.EDU Ämne: Windsows 2008 failover cluster, SQL Server and TSM Windows 2008 R2 failover cluster with SQL as a resource. All the cluster disks are "owned" by the SQL resource. I need to install a client scheduler for the cluster backups. The documentation for doing that is assuming you will just be doing backups of the cluster drives and adding the generic resource you add the cluster drives so it all fails over together. I need to make it so that the generic service is part of the SQL resource and gets failed over with that. Anyone out there done this type of configuration? I have the generic service installed and the TDP SQL backups run fine, but last night the SQL resource failed over and my service didn't. Have failed SQL backups this morning. If I try to add a generic service to the SQL resource, it doesn't appear to give me the option to replicate registry keys. Any help would be appreciated. Bill Boyer DSS, Inc. (610) 927-4407 "Enjoy life. It has an expiration date." - ?? DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. Please consider the environment before printing this e-mail.