 | |
Reporting Services on a Cluster
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Reporting Services on a Cluster -
04-16-2008
, 12:37 PM
#2
| |||
| |||
|
|
Greetings all, We need some help understanding our options. We have a 64bit W2003 SP2 & SQL 2005 SP2 currently running as a single instance. We know that Reporting Services (RS) is not cluster aware. We currently have RS running on the inactive node & SQL Server running on the active node. I'd like to understand how this happened and how to correct it. I believe the RS difference noted is because we performed a manual failover to test the cluster and because RS is not cluster aware it continues to run on the inactive server. Is this correct. Now on to what we can do about it. Our thoughts are: 1. Failover the server to the inactive node so SQL Server & RS are both running on the active server. 2. Remove the inactive node out of the SQL cluster & rebuild it - including an RS installation that mirrors the now active server's installation. 3. Add the rebuilt server back into the cluster. (is there a link available to this procedure?) *Is the above a viable solution? Is there a software release for RS already at SP2? Or is it only available at SP1 level? We had tried this first on a stand-alone test server and the RS install failed because we were trying to install a version (SP1) older than the currently installed SQL Server version (SP2). Is RS cluster aware in SQL 2008? How does it work and is there an available procedure/link for changing the single instance cluster to a multi-instance cluster? How about from a single instance cluster to an N+1 cluster? Is it correct to perform the SQL install on the server node prior to adding it to the existing cluster? How does this work? Otherwise, how do they sync up, and use the shared array? Thanks in advance for any assistance you can provide!  - Lori |
#3
| |||
| |||
|
|
Greetings all, We need some help understanding our options. We have a 64bit W2003 SP2 & SQL 2005 SP2 currently running as a single instance. We know that Reporting Services (RS) is not cluster aware. We currently have RS running on the inactive node & SQL Server running on the active node. I'd like to understand how this happened and how to correct it. I believe the RS difference noted is because we performed a manual failover to test the cluster and because RS is not cluster aware it continues to run on the inactive server. Is this correct. Now on to what we can do about it. Our thoughts are: 1. Failover the server to the inactive node so SQL Server & RS are both running on the active server. 2. Remove the inactive node out of the SQL cluster & rebuild it - including an RS installation that mirrors the now active server's installation. 3. Add the rebuilt server back into the cluster. (is there a link available to this procedure?) *Is the above a viable solution? Is there a software release for RS already at SP2? Or is it only available at SP1 level? We had tried this first on a stand-alone test server and the RS install failed because we were trying to install a version (SP1) older than the currently installed SQL Server version (SP2). Is RS cluster aware in SQL 2008? How does it work and is there an available procedure/link for changing the single instance cluster to a multi-instance cluster? How about from a single instance cluster to an N+1 cluster? Is it correct to perform the SQL install on the server node prior to adding it to the existing cluster? How does this work? Otherwise, how do they sync up, and use the shared array? Thanks in advance for any assistance you can provide! - Lori |
#4
| |||
| |||
|
|
Greetings all, We need some help understanding our options. We have a 64bit W2003 SP2 & SQL 2005 SP2 currently running as a single instance. We know that Reporting Services (RS) is not cluster aware. We currently have RS running on the inactive node & SQL Server running on the active node. I'd like to understand how this happened and how to correct it. I believe the RS difference noted is because we performed a manual failover to test the cluster and because RS is not cluster aware it continues to run on the inactive server. Is this correct. Now on to what we can do about it. Our thoughts are: 1. Failover the server to the inactive node so SQL Server & RS are both running on the active server. 2. Remove the inactive node out of the SQL cluster & rebuild it - including an RS installation that mirrors the now active server's installation. 3. Add the rebuilt server back into the cluster. (is there a link available to this procedure?) *Is the above a viable solution? Is there a software release for RS already at SP2? Or is it only available at SP1 level? We had tried this first on a stand-alone test server and the RS install failed because we were trying to install a version (SP1) older than the currently installed SQL Server version (SP2). Is RS cluster aware in SQL 2008? How does it work and is there an available procedure/link for changing the single instance cluster to a multi-instance cluster? How about from a single instance cluster to an N+1 cluster? Is it correct to perform the SQL install on the server node prior to adding it to the existing cluster? How does this work? Otherwise, how do they sync up, and use the shared array? Thanks in advance for any assistance you can provide! - Lori |
#5
| |||
| |||
|
|
Greetings all, We need some help understanding our options. We have a 64bit W2003 SP2 & SQL 2005 SP2 currently running as a single instance. We know that Reporting Services (RS) is not cluster aware. We currently have RS running on the inactive node & SQL Server running on the active node. I'd like to understand how this happened and how to correct it. I believe the RS difference noted is because we performed a manual failover to test the cluster and because RS is not cluster aware it continues to run on the inactive server. Is this correct. Now on to what we can do about it. Our thoughts are: 1. Failover the server to the inactive node so SQL Server & RS are both running on the active server. 2. Remove the inactive node out of the SQL cluster & rebuild it - including an RS installation that mirrors the now active server's installation. 3. Add the rebuilt server back into the cluster. (is there a link available to this procedure?) *Is the above a viable solution? Is there a software release for RS already at SP2? Or is it only available at SP1 level? We had tried this first on a stand-alone test server and the RS install failed because we were trying to install a version (SP1) older than the currently installed SQL Server version (SP2). Is RS cluster aware in SQL 2008? How does it work and is there an available procedure/link for changing the single instance cluster to a multi-instance cluster? How about from a single instance cluster to an N+1 cluster? Is it correct to perform the SQL install on the server node prior to adding it to the existing cluster? How does this work? Otherwise, how do they sync up, and use the shared array? Thanks in advance for any assistance you can provide! - Lori |
#6
| |||
| |||
|
|
Greetings all, We need some help understanding our options. We have a 64bit W2003 SP2 & SQL 2005 SP2 currently running as a single instance. We know that Reporting Services (RS) is not cluster aware. We currently have RS running on the inactive node & SQL Server running on the active node. I'd like to understand how this happened and how to correct it. I believe the RS difference noted is because we performed a manual failover to test the cluster and because RS is not cluster aware it continues to run on the inactive server. Is this correct. Now on to what we can do about it. Our thoughts are: 1. Failover the server to the inactive node so SQL Server & RS are both running on the active server. 2. Remove the inactive node out of the SQL cluster & rebuild it - including an RS installation that mirrors the now active server's installation. 3. Add the rebuilt server back into the cluster. (is there a link available to this procedure?) *Is the above a viable solution? Is there a software release for RS already at SP2? Or is it only available at SP1 level? We had tried this first on a stand-alone test server and the RS install failed because we were trying to install a version (SP1) older than the currently installed SQL Server version (SP2). Is RS cluster aware in SQL 2008? How does it work and is there an available procedure/link for changing the single instance cluster to a multi-instance cluster? How about from a single instance cluster to an N+1 cluster? Is it correct to perform the SQL install on the server node prior to adding it to the existing cluster? How does this work? Otherwise, how do they sync up, and use the shared array? Thanks in advance for any assistance you can provide! - Lori |
#7
| |||
| |||
|
|
Greetings all, We need some help understanding our options. We have a 64bit W2003 SP2 & SQL 2005 SP2 currently running as a single instance. We know that Reporting Services (RS) is not cluster aware. We currently have RS running on the inactive node & SQL Server running on the active node. I'd like to understand how this happened and how to correct it. I believe the RS difference noted is because we performed a manual failover to test the cluster and because RS is not cluster aware it continues to run on the inactive server. Is this correct. Now on to what we can do about it. Our thoughts are: 1. Failover the server to the inactive node so SQL Server & RS are both running on the active server. 2. Remove the inactive node out of the SQL cluster & rebuild it - including an RS installation that mirrors the now active server's installation. 3. Add the rebuilt server back into the cluster. (is there a link available to this procedure?) *Is the above a viable solution? Is there a software release for RS already at SP2? Or is it only available at SP1 level? We had tried this first on a stand-alone test server and the RS install failed because we were trying to install a version (SP1) older than the currently installed SQL Server version (SP2). Is RS cluster aware in SQL 2008? How does it work and is there an available procedure/link for changing the single instance cluster to a multi-instance cluster? How about from a single instance cluster to an N+1 cluster? Is it correct to perform the SQL install on the server node prior to adding it to the existing cluster? How does this work? Otherwise, how do they sync up, and use the shared array? Thanks in advance for any assistance you can provide! - Lori |
#8
| |||
| |||
|
|
Greetings all, We need some help understanding our options. We have a 64bit W2003 SP2 & SQL 2005 SP2 currently running as a single instance. We know that Reporting Services (RS) is not cluster aware. We currently have RS running on the inactive node & SQL Server running on the active node. I'd like to understand how this happened and how to correct it. I believe the RS difference noted is because we performed a manual failover to test the cluster and because RS is not cluster aware it continues to run on the inactive server. Is this correct. Now on to what we can do about it. Our thoughts are: 1. Failover the server to the inactive node so SQL Server & RS are both running on the active server. 2. Remove the inactive node out of the SQL cluster & rebuild it - including an RS installation that mirrors the now active server's installation. 3. Add the rebuilt server back into the cluster. (is there a link available to this procedure?) *Is the above a viable solution? Is there a software release for RS already at SP2? Or is it only available at SP1 level? We had tried this first on a stand-alone test server and the RS install failed because we were trying to install a version (SP1) older than the currently installed SQL Server version (SP2). Is RS cluster aware in SQL 2008? How does it work and is there an available procedure/link for changing the single instance cluster to a multi-instance cluster? How about from a single instance cluster to an N+1 cluster? Is it correct to perform the SQL install on the server node prior to adding it to the existing cluster? How does this work? Otherwise, how do they sync up, and use the shared array? Thanks in advance for any assistance you can provide! - Lori |
#9
| |||
| |||
|
|
Greetings all, We need some help understanding our options. We have a 64bit W2003 SP2 & SQL 2005 SP2 currently running as a single instance. We know that Reporting Services (RS) is not cluster aware. We currently have RS running on the inactive node & SQL Server running on the active node. I'd like to understand how this happened and how to correct it. I believe the RS difference noted is because we performed a manual failover to test the cluster and because RS is not cluster aware it continues to run on the inactive server. Is this correct. Now on to what we can do about it. Our thoughts are: 1. Failover the server to the inactive node so SQL Server & RS are both running on the active server. 2. Remove the inactive node out of the SQL cluster & rebuild it - including an RS installation that mirrors the now active server's installation. 3. Add the rebuilt server back into the cluster. (is there a link available to this procedure?) *Is the above a viable solution? Is there a software release for RS already at SP2? Or is it only available at SP1 level? We had tried this first on a stand-alone test server and the RS install failed because we were trying to install a version (SP1) older than the currently installed SQL Server version (SP2). Is RS cluster aware in SQL 2008? How does it work and is there an available procedure/link for changing the single instance cluster to a multi-instance cluster? How about from a single instance cluster to an N+1 cluster? Is it correct to perform the SQL install on the server node prior to adding it to the existing cluster? How does this work? Otherwise, how do they sync up, and use the shared array? Thanks in advance for any assistance you can provide! - Lori |
#10
| |||
| |||
|
|
Greetings all, We need some help understanding our options. We have a 64bit W2003 SP2 & SQL 2005 SP2 currently running as a single instance. We know that Reporting Services (RS) is not cluster aware. We currently have RS running on the inactive node & SQL Server running on the active node. I'd like to understand how this happened and how to correct it. I believe the RS difference noted is because we performed a manual failover to test the cluster and because RS is not cluster aware it continues to run on the inactive server. Is this correct. Now on to what we can do about it. Our thoughts are: 1. Failover the server to the inactive node so SQL Server & RS are both running on the active server. 2. Remove the inactive node out of the SQL cluster & rebuild it - including an RS installation that mirrors the now active server's installation. 3. Add the rebuilt server back into the cluster. (is there a link available to this procedure?) *Is the above a viable solution? Is there a software release for RS already at SP2? Or is it only available at SP1 level? We had tried this first on a stand-alone test server and the RS install failed because we were trying to install a version (SP1) older than the currently installed SQL Server version (SP2). Is RS cluster aware in SQL 2008? How does it work and is there an available procedure/link for changing the single instance cluster to a multi-instance cluster? How about from a single instance cluster to an N+1 cluster? Is it correct to perform the SQL install on the server node prior to adding it to the existing cluster? How does this work? Otherwise, how do they sync up, and use the shared array? Thanks in advance for any assistance you can provide! - Lori |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.