August 16, 2018 at 7:20 am
HI Experts,
We are moving our Production server to a two node cluster server and i am worried about how am i going to make the report server work.I was reading about Reporting service not being cluster aware.Anyone with an idea please help?
Many thanks
T.
November 1, 2018 at 11:18 am
Without knowing more information, the best I can offer is this solution: make your SSRS server standalone (unless the idea is to make the SSRS install in a cluster of itself -which I would suggest starting here: https://www.mssqltips.com/sqlservertip/2778/how-to-add-reporting-services-to-an-existing-sql-server-clustered-instance/). If it is standalone, then you can create a data source which references the Cluster's Public IP address (or DNS name) and then you are not stuck having to handle the fail over situation.
I hope this helps.
November 1, 2018 at 11:30 am
Typical installations are for Report Services to be installed on a standalone server. These days that is usually a Virtual Machine on a cluster, so you get some high availability from the VM cluster. If you need to scale out (done more for spreading out load, rather than for high availability), you should be able to put a series of Reporting Services machines behind a load balancer. I have not done this, but ReportServer is basically a web server. The largest considerations will be configuring the DNS name so the individual Report Servers can recognize the requests properly.
I would go back to the users, and see if the uptime provided by your current environment for a standalone server will meet their needs, or if they really want to spend the money of setting up a load balancer, and a series of ReportServers. My guess is when shown the price tag, they will agree to the 99.9% uptime option, rather than the 99.999%.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply