Client install on a MS Cluster with SQL 2000
We will be setting up a new cluster server running Win2k and MS SQL 2000. We are at 5.1 on our TSM server. We are backing up another cluster server running the same OS but without any SQL on it. And we are backing up SQL 2000 running on a non-cluster server. Both have the newest clients installed and running fine. Is there anything that's not in the book on running a SQL client on a MS cluster that I might need to know? Thanks... David Tyree Microcomputer Specialist South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: Client install on a MS Cluster with SQL 2000
Hi David, my experience with MS Cluster and SQL backup is as follows: Follow the book. If things does not work, remove TSM services and TSM cluster resources and start over, going by the book. I have never had to do it more than twice, and I know that the times I had to do it more than once, was when I tried to be smart and figure things out by myself, instead of running it step by step (by the book). rgds G. Halvorsen -Original Message- From: Tyree, David [mailto:[EMAIL PROTECTED] Sent: 25. februar 2003 17:58 To: [EMAIL PROTECTED] Subject: Client install on a MS Cluster with SQL 2000 We will be setting up a new cluster server running Win2k and MS SQL 2000. We are at 5.1 on our TSM server. We are backing up another cluster server running the same OS but without any SQL on it. And we are backing up SQL 2000 running on a non-cluster server. Both have the newest clients installed and running fine. Is there anything that's not in the book on running a SQL client on a MS cluster that I might need to know? Thanks... David Tyree Microcomputer Specialist South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: Client install on a MS Cluster with SQL 2000
I totally agree! Follow the book! It makes life a lot easier. -- Bruce Kamp Midrange Systems Analyst II Memorial Healthcare System E: [EMAIL PROTECTED] P: (954) 987-2020 x4597 F: (954) 985-1404 --- -Original Message- From: Halvorsen Geirr Gulbrand [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 3:39 AM To: [EMAIL PROTECTED] Subject: Re: Client install on a MS Cluster with SQL 2000 Hi David, my experience with MS Cluster and SQL backup is as follows: Follow the book. If things does not work, remove TSM services and TSM cluster resources and start over, going by the book. I have never had to do it more than twice, and I know that the times I had to do it more than once, was when I tried to be smart and figure things out by myself, instead of running it step by step (by the book). rgds G. Halvorsen -Original Message- From: Tyree, David [mailto:[EMAIL PROTECTED] Sent: 25. februar 2003 17:58 To: [EMAIL PROTECTED] Subject: Client install on a MS Cluster with SQL 2000 We will be setting up a new cluster server running Win2k and MS SQL 2000. We are at 5.1 on our TSM server. We are backing up another cluster server running the same OS but without any SQL on it. And we are backing up SQL 2000 running on a non-cluster server. Both have the newest clients installed and running fine. Is there anything that's not in the book on running a SQL client on a MS cluster that I might need to know? Thanks... David Tyree Microcomputer Specialist South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
